Terminal, wireless communication method, and base station

Abstract

A terminal according to one aspect of the present disclosure which has a reception unit that receives a reference signal, and a control unit which, when a first event based on the reference signal occurs within a first time window, determines whether or not to transmit a first physical uplink control channel (PUCCH) in a PUCCH resource after the first time window, wherein the control unit cancels the first PUCCH transmission when the PUCCH resource overlaps a specific period after transmission of a specific signal, or when the transmission of the specific signal overlaps the first time window.

Description

Terminal, wireless communication method, and base station

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

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

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

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

[0005] In future wireless communication systems (e.g., NR, Rel. 19 and later), support for event-based beam reporting (or possibly called event-triggered beam reporting / UE-initiated Beam Report (UEIBR)) initiated by a terminal (user terminal, user equipment (UE)) is being considered.

[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 adequately considered. If this consideration is insufficient, it may not be possible to achieve lower latency communication, potentially hindering improvements in communication quality and throughput.

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

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

[0010] According to one aspect of this disclosure, communication quality / throughput can be improved.

[0011] Figure 1A shows an example of UE movement in Rel. 17. Figure 1B shows an example of UE movement in Rel. 18. Figure 2 shows an example of a time window related to options 0-2. Figures 3A-3C show an example of association between an event / setting and the first UL channel related to Embodiment 1-1. Figure 4 shows an example of the operation of the prohibit timer related to option 1.1A. Figure 5 shows an example of the operation of a time window related to option 1.1A. Figure 6 shows an example of the operation of the prohibit timer related to options 1.2A / 1.3A. Figure 7 shows an example of the operation of a time window related to options 1.2A / 1.3A. Figures 8A-8C show an example of association between a CC and the first UL channel related to Embodiment 1-2. Figures 9A-9D show an example of association between an event / setting, CC, and the first UL channel related to Embodiment 1-3. Figure 10 shows an example of cancellation of the first PUCCH related to option 1-2 in Embodiment B2. Figure 11 shows an example of a measurement window according to Embodiment C1. Figure 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 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 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 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-3. Figure 16 shows an example of the overlap of multiple measurement windows according to Embodiment C3. Figure 17 shows an example of the operation of a counter according to Embodiment C4. Figure 18 is a diagram showing an example of the schematic configuration of a wireless communication system according to one embodiment. Figure 19 is a diagram showing an example of the configuration of a base station according to one embodiment. Figure 20 is a diagram showing an example of the configuration of a user terminal according to one embodiment. Figure 21 is a diagram showing an example of the hardware configuration of a base station and a user terminal according to one embodiment. Figure 22 shows an example of a vehicle according to one embodiment.

[0012] (L1 / L2 Inter-Cell Mobility) A UE may perform UL transmission to one or more cells / TRPs. As the procedure in this case, the following Scenario 1 or Scenario 2 is conceivable. In the present disclosure, a serving cell may be read as a TRP in the serving cell. layer1 / layer2 (L1 / L2), and DCI / Medium Access Control Control Element (MAC CE) may be read interchangeably with each other. In the present disclosure, a 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 read interchangeably with each other.

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

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

[0015] In Scenario 1, when a 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 assumption of the serving cell at the UE) is not changed. The UE is configured with upper layer parameters related to the PCI of a non-serving cell from the serving cell. Scenario 1 may be applied, for example, in Rel. 17.

[0016] FIG. 1A is a diagram illustrating an example of UE movement in Rel. 17. It is assumed that a UE moves from a cell of PCI #1 (serving cell) to a cell of PCI #3 (additional cell) (overlapping with the serving cell). In this case, Rel. 17 does not support serving cell switching by L1 / L2.

[0017] An additional cell is a cell having an additional PCI different from the PCI of the serving cell. The UE can receive / transmit a UE-dedicated channel from / to the additional cell. The UE needs to be within the coverage of the serving cell to receive a UE common channel (e.g., system information / paging / short messages). When the UE moves outside the coverage of the serving cell, cell switching is required, such as by handover (also referred to as L3 mobility).

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

[0019] (1) The UE receives the SSB configuration of a cell with a different PCI (additional cell) from the serving cell for beam measurement / serving cell change. (2) The UE performs beam measurement on the cell using the different PCI and reports the measurement results to the serving cell. (3) The UE may receive the configuration of the cell with the different PCI (serving cell configuration) by upper layer signaling (e.g., RRC). In other words, a pre-configuration regarding the 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 state of the cell with the different PCI may be activated by L1 / L2 signaling in accordance with the serving cell change. The activation of the TCI state and the serving cell change may be performed separately. (5) The UE changes the serving cell (assumed serving cell) and starts receiving / transmitting using the pre-configured UE-specific channel and TCI state.

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

[0021] Figure 1B shows an example of UE movement in Rel. 18. In Rel. 18, serving cells are switched by L1 / L2 (e.g., DCI / MAC CE). UEs can receive / transmit UE-dedicated / common channels to and from the new serving cell (or target serving cell). UEs may leave the coverage of the current serving cell (e.g., Current serving cell).

[0022] (Beam reporting type) <Intra-cell beam reporting in Rel. 15 / 16> Intra-cell beam reporting is supported in Rel. 15 / 16. For example, L1-RSRP / SINR reporting can be configured by upper-layer signaling (RRC).

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

[0024] Furthermore, the UE may configure up to 16 CSI-RS resource sets, each containing up to 64 resources. In all resource sets, the total number of different CSI-RS resources is 128 or less.

[0025] In L1-RSRP reporting, if the upper layer parameter nrofReportedRS (for example, in CSI-ReportConfig) is set to 1, 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.

[0026] Here, the maximum measurement 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. The difference value of L1-RSRP is quantized to a 4-bit value.

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

[0028] For example, in L1-SINR calculation and channel measurement, the UE may configure either an NZP CSI-RS resource and / or an SS / PBCH block resource. Furthermore, for interference measurement, the UE may configure either an NZP CSI-RS resource or a CSI-IM resource.

[0029] For channel measurement, the UE can configure CSI resource settings for up to 64 CSI resources or up to 16 CSI-RS resource sets having SS / PBCH block resources.

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

[0031] If the upper layer parameter nrofReportedRS is set to a value greater than 1, or if the upper layer parameter groupBasedBeamReporting is set to "enabled", the UE will use the difference-based L1-SINR value for reporting.

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

[0033] In this disclosure, the intra-cell beam report of Rel. 15 / 16 (which may also be simply called the intra-cell beam report) may be called a type 1 beam report (beam report type 1), or a beam report for intra-cell beam switching.

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

[0035] In the L1-RSRP report, the absolute value / difference value of L1-RSRP may be used, as in Rel. 15 / 16. In the inter-cell beam report of Rel. 17 (Type 2-1 beam report 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 / instructed by upper-layer signaling / physical-layer signaling.

[0036] The configuration using upper-layer signaling supports up to seven additional cells. Note that ID=0 indicates the PCI of the serving cell.

[0037] In this disclosure, inter-cell beam reporting (in Rel. 17 / 18) may be referred to as Type 2 beam reporting (Beam reporting type 2). Type 2 beam reporting can be further classified into types 2-1 and 2-2, as described below.

[0038] In this disclosure, the beam report of Rel. 17 may be referred to as a type 2-1 beam report, or a beam report for inter-cell beam switching.

[0039] <Inter-cell beam reporting for Rel. 18> Furthermore, beam reporting for Rel. 18 is only supported as SSB-based L1-RSRP reporting (beam reporting). Here, the number of candidate cells L is one of 1 to 4, and the number of beams M per cell may be one of 1 to 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 difference values.

[0040] Regarding beam selection in SSB-based L1-RSRP reporting, the maximum value of M*L and the combination of M and L that can be set in RRC may vary depending on the UE capabilities.

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

[0042] In L1-RSRP reporting, 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 measurement 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. The difference value of L1-RSRP is quantized to a 4-bit value.

[0044] The difference value is calculated with a step size of 2 dB, referencing 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. In other words, the L1-RSRP report includes the SSBRI of the configured candidate cells and the corresponding L1-RSRP. The format may be the same as the existing specification.

[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 PCI information (PCI ID). Instead, the SSBRI may include PCI information. For example, if four cells have 64 SSBs, the SSBRI will be one of {0, 1, ..., 255}.

[0047] The additional PCIs that are configured are re-indexed by their IDs. RRC IE can configure up to seven additional PCIs. An ID value of 0 corresponding to a PCI represents a serving cell.

[0048] M x L ​​beams are reported within a single reporting instance. The UE reports M beams for each of the L cells from the configured set of cells.

[0049] (Event-Triggered Beam Reporting / UE-Initiated Beam Report (UEIBR)) In future wireless communication systems (e.g., Rel. 19 and beyond), support for event-based beam reporting is being considered. Event-based beam reporting may also be called event-triggered beam reporting, or UE-initiated beam reporting (UEIBR).

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

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

[0052] The UE may report the measurement results (e.g., at least L1-RSRP / L1-SINR and the corresponding resource indicator / RS index) to the NW when a specific event occurs (which may be interpreted in this disclosure as a specific condition being met / not met, a specific event being matched, etc.).

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

[0054] <UEIBR Trigger Conditions / Events for Rel. 19> The UEIBR may be triggered when certain conditions (events) are met. For example, the UE may apply different / same conditions / events to the triggers of the following beam reports.

[0055] UE Feature #1: UEIBR for MIMO in Rel. 19. UE Feature #2: UEIBR for mobility in Rel. 19.

[0056] Different UE capabilities may be introduced / defined between UE features #1 and #2. Furthermore, different higher-level parameters may be set to enable each UE feature. UE features and UE capabilities may be interchangeable.

[0057] UE does not expect UE features #1 and #2 to be set simultaneously in a given BWP / CC / band / frequency range / frequency (or per UE).

[0058] A UE may have UE features #1 and #2 set simultaneously in a given BWP / CC / band / frequency range / frequency (or per UE). For example, a UE may have predefined which events (which UE features) to prioritize, if set, and this may be set / instructed by upper-layer signaling / physical-layer signaling.

[0059] This disclosure may be applied within the Unified TCI Framework.

[0060] This disclosure may apply only if the corresponding UE capability is reported, or if the corresponding higher-layer parameter (e.g., RRC) is notified / reported.

[0061] <UEIBR for MIMO> The following may apply to the UEIBR for MIMO in Rel. 19.

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

[0063] The report content may be essentially the same as existing L1 beam measurement reports, and may include at least one of the following, for example: • SSBRI / CRI. • Number of beams to be reported (X). • Method for selecting X beams. • L1-RSRP / SINR (absolute value / difference value) for each SSBRI / CRI. If MAC CE is used, • Indicator indicating whether the following octets are included. If MAC CE / UCI is used, • Serving cell ID, BWP ID (if the report requires activation of the TCI state or beam switching).

[0064] Events related to the UEIBR for MIMO may be broadly categorized into the following event types: • Event 1: The quality of the current beam falls below a certain threshold. • Event 2: The quality of at least one new beam (e.g., L1-RSRP) is better than a certain threshold compared to the quality of the current beam. • Event 3: The quality of a new beam is better than a certain threshold. • Event 4: The quality of the current beam falls below a first threshold, and the quality of at least one new beam is better than a second threshold. • Event 5: The absolute 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 included in the best K beams (more than 1: K > 1) (of the beams set up for measurement / reporting). - Event 7: The quality of at least one new beam (e.g., L1-RSRP) improves by a threshold beyond the RS derived from the Q-th (Q may be M; Q or M is 1 or greater; Q or M may be set in the RRC (based on UE capability reporting)) quality good activated (active) TCI state. - Event 8: The quality of M (more than 1: M > 1) new beams (e.g., L1-RSRP) improves by a threshold beyond the current beam. - Event 9: The quality of at least one new beam (e.g., L1-RSRP) improves by a threshold beyond the set reference RS (which may be SSB / CSI-RS).

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

[0066] Priorities may be assigned to events 1 through 9. For example, one of events 1 through 9 (e.g., event 2) may have the highest priority (e.g., event 2 may be given priority in the decision-making process).

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

[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 in the indicated TCI state. • Beam option 2b: The RS corresponding to the current beam is an SSB that is QCL'd with the QCL RS in the indicated TCI state. • Beam option 2c: The RS corresponding to the current beam is explicitly set / indicated using RRC signaling / MAC CE.

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

[0070] For example, multiple schemes may be supported for the reference signal measurement (RS measurement) of the current beam for event 2 (and beam option 2a): • 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 of QCL type D.

[0072] At least one of CSI-RS and SSB may be supported as a QCL RS to be set / applied to the indicated TCI state. When CSI-RS is set / 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 a CSI-RS used for L1-RSRP / L1-SINR or a CSI-RS used for beam management (BM).

[0073] In Scheme 1, only a TRS (e.g., one tracking CSI-RS) may be set as the QCL-RS (e.g., type A / D) for the indicated TCI state.

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

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

[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 further supported as the measured RS for the current beam to determine the L1-RSRP. • Processing Option 3: An additional scheme is introduced. The RS for the current beam is explicitly set / indicated by the RRC or MAC CE. • Processing Option 4: No further extensions are made.

[0077] Explicit RS settings for measuring new beams in Event 2 may be configured in a single RS resource set associated with the CSI reporting settings.

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

[0079] The RS within that single RS resource set may be updated by MAC CE.

[0080] UEIBR for MIMO may be transmitted using UCI.

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

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

[0083] Step 1: The UE transmits a first UL channel (e.g., PUCCH). The first UL channel is a UL channel that pre-notifies / requests a second UL channel (e.g., PUCCH) for transmitting beam reports, 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 the beam report using the resource (UCI) on the second UL channel.

[0086] In mode A, a 1-bit instruction in at least the first UL channel (PUCCH) may be supported to request resources on the second UL channel for transmitting beam reports.

[0087] In this case, periodic PUCCH resources (PUCCH format 0 / 1) can be set up by dedicated upper-layer signaling.

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

[0089] Furthermore, an RRC parameter (e.g., firstPUCCHResourceConfig-ModeA-UEIBR) for periodic PUCCH resource configuration corresponding to the 1-bit instruction may be defined. This RRC parameter does not need to be associated with the SR ID (e.g., SchedulingRequestId).

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

[0091] These RRC parameter specifications may also apply to cases using at least one CC (single CC).

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

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

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

[0095] 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 the UCI in the 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 a UL channel that notifies a second UL channel for transmitting beam reports, and may consist of one or more bits.

[0098] Step 2: The UE transmits a beam report on the second UL channel (for example, 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] In mode B, a one-bit instruction on at least the first UL channel (PUCCH) may be supported to indicate that the second UL channel will transmit a beam report.

[0101] In this case, periodic PUCCH resources (PUCCH format 0 / 1) can be set up by dedicated upper-layer signaling.

[0102] In either mode A or B as described above, cross-CC (component carrier) beam reporting may be supported.

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

[0104] Furthermore, an RRC parameter (e.g., firstPUCCHResourceConfig-ModeB-UEIBR) for periodic PUCCH resource configuration corresponding to the 1-bit instruction may be defined. This RRC parameter does not need to be associated with the SR ID (e.g., SchedulingRequestId).

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

[0106] These RRC parameter specifications may also apply to cases using at least one CC (single CC).

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

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

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

[0110] 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: an indicator showing whether or not a cell switch has occurred, or TA-related information. Otherwise (if the measurement report is not used for cell switching reporting): the same information as MIMO-related information (the only difference being whether it is within a cell or between cells).

[0111] The supported events may be the same as those for a Conditional Hand-Over (CHO).

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

[0113] If the report is used for cell switching commands, specific domain filters (e.g., time / frequency / space) may be considered / applied to prevent frequent switching.

[0114] It may also be specified whether flexibility in the trigger time (e.g., 5 milliseconds, 10 milliseconds, 20 milliseconds) is required.

[0115] In the case of L1 measurements using 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 serving cell's beam quality falls below an (absolute) threshold. • Event LTM3: The candidate cell's beam quality improves beyond a certain offset amount compared to the serving cell's beam quality. • Event LTM4: The candidate cell's beam quality falls below an (absolute) threshold. • Event LTM5: The serving cell's beam quality falls below a first (absolute) threshold, AND the candidate cell's beam quality improves above a second (absolute) threshold.

[0117] It should be noted that the events exemplified in this way do not exclude other events. Furthermore, the MIMO-oriented events described above may be reused as appropriate (in this case, "current beam" may be replaced with "serving cell beam," and "new beam" with "candidate cell beam"). These reused / re-interpreted events may be called mobility / LTM-oriented events corresponding to MIMO-oriented events.

[0118] In the LTM configuration, the L1 measurement resource setting may support both SSB and CSI-RS beam settings.

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

[0120] In mobility event evaluation, at least one of the following may be applied: TimeToTrigger (TTT), hysteresis for entering / leaving, and beam-specific / cell-specific offsets.

[0121] UEIBR for mobility may be transmitted using MAC CE.

[0122] <Definition of wording for specific events> In the existing events described above, the definitions of Serving [cell] and Neighbor [cell] may be reinterpreted / updated as follows in the UEIBR for Rel. 19.

[0123] For example, in existing L3 events, Serving [Cell], SpCell, and PCell may be interpreted interchangeably with the current beam (e.g., the RS ID associated with the indicated [Joint / DL]TCI state) in event-triggered beam reports for MIMO in Rel. 19.

[0124] Furthermore, in existing L3 events, Serving [Cell], SpCell, and PCell may be interpreted interchangeably with the current beam (e.g., the RS ID associated with the indicated [Joint / DL] TCI state) or the serving cell's beam (e.g., the RS ID associated with the serving cell's PCI TCI state) in the event-triggered beam reports for mobility in Rel. 19.

[0125] In existing L3 events, adjacent [cells] may be interpreted interchangeably with 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 the L1 beam measurement) in event-triggered beam reports for MIMO (which may be mobility) in Rel. 19.

[0126] Furthermore, adjacent [cells] in existing L3 events may be interpreted as corresponding to beams of non-serving cells / target cells / candidate cells (e.g., RS IDs associated with the TCI status of the PCI of target cells / candidate cells) in event-triggered beam reports for mobility in Rel. 19.

[0127] The measured values ​​of each reference signal (RS) may be RSRP / SINR, L3-RSRP / SINR, L1-RSRP / SINR, or the average of multiple L1-RSRP / SINR values.

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

[0129] <UEIBR in Multi-CC / Cross-CC Cases> A UEIBR that utilizes multiple CCs may be set for a UE.

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

[0131] A UEIBR that utilizes multiple CCs may also be called a multi-CC case UEIBR.

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

[0133] Regarding cross-CC operation in UEIBR, the CC where an event occurs / satisfies may be, for example, the CC in which the reporting settings including the triggered event are configured.

[0134] The reporting setting in question may be, for example, an existing reporting setting (as defined up to Rel. 18) that is being extended.

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

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

[0137] Alternatively, for example, the reporting setting may be the CSI reporting setting [as defined in Rel. 15] (e.g., CSI-ReportConfig).

[0138] The CSI reporting settings may be applied / used, for example, in specific scenarios (e.g., the MIMO case).

[0139] Alternatively, for example, the reporting setting may be the CSI reporting setting for UEIBR (e.g., UEIBR-CSI-ReportConfig-r19), which will be newly defined in Rel. 19 and later.

[0140] The CSI reporting settings may be applied / used in specific scenarios, for example (e.g., the mobility / LMT / MIMO case).

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

[0142] Furthermore, the CC to which the reporting settings including the triggered event are configured and the CC to which the RS set as the measurement target in the triggered event belong (corresponding CC) may be determined separately. For example, the CC to which the reporting settings including the triggered event are configured and the CC to which the RS set as the measurement target in the triggered event belong (corresponding CC) may be different.

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

[0144] Furthermore, with respect to cross-CC operation in UEIBR, the CC that triggers / satisfies an event may be, for example, a CC set / instructed by higher-layer signaling (RRC signaling / MAC CE).

[0145] The first / second UL channel may contain the CC / cell ID of the CC where the event occurs / satisfies.

[0146] Of the following multiple CCs, CC#1 may correspond to a special cell (SpCell, e.g., PCell / PSCell) / PUCCH SCell, and CC#2 through #N may correspond to SCell.

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

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

[0149] For example, a cross-CC operation in UEIBR may include at least one of the following: • Operation 1: A report is triggered in CC#1 by a reporting setting (measurement in CC#1), a first UL channel is transmitted in CC#1, and a second UL channel is transmitted in CC#1. • Operation 2: A report is triggered in CC#1 by a reporting setting (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 CC#2 through #N. • Operation 3: A report is triggered in CC#1 by a reporting setting (measurement in CC#1), a first UL channel is transmitted in at least one of CC#2 through #N, and a second UL channel is transmitted in CC#1. - Operation 4: A report is triggered in CC#1 by the reporting setting (measurement in CC#1), the first UL channel is transmitted in at least one of CC#2 through #N, and the second UL channel is transmitted in at least one of CC#2 through #N. - Operation 5: A report is triggered in CC#1 by the reporting setting (measurement in at least one of CC#2 through #N), the first UL channel is transmitted in CC#1, and the second UL channel is transmitted in CC#1. - Operation 6: A report is triggered in CC#1 by the reporting setting (measurement in at least one of CC#2 through #N), the first UL channel is transmitted in CC#1, and the second UL channel is transmitted in at least one of CC#2 through #N. - Operation 7: A report is triggered in CC#1 based on the reporting setting (measurement in at least one of CC#2 through #N), the first UL channel is transmitted in at least one of CC#2 through #N, and the second UL channel is transmitted in CC#1. - Operation 8: A report is triggered in CC#1 based on the reporting setting (measurement in at least one of CC#2 through #N), the first UL channel is transmitted in at least one of CC#2 through #N, and the second UL channel is transmitted in at least one of CC#2 through #N. - Operation 9: A report is triggered in at least one of CC#2 through #N based on 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.- Operation 10: A report is triggered in at least one of CC#2 through #N based on 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 through #N. - Operation 11: A report is triggered in at least one of CC#2 through #N based on the reporting setting (measurement in CC#1), the first UL channel is transmitted in at least one of CC#2 through #N, and the second UL channel is transmitted in CC#1. - Operation 12: A report is triggered in at least one of CC#2 through #N based on the reporting setting (measurement in CC#1), the first UL channel is transmitted in at least one of CC#2 through #N, and the second UL channel is transmitted in at least one of CC#2 through #N. - Operation 13: A report is triggered in at least one of CC#2 through #N by a reporting setting (measurement in at least one of CC#2 through #N), the first UL channel is transmitted in CC#1, and the second UL channel is transmitted in CC#1. - Operation 14: A report is triggered in at least one of CC#2 through #N by a reporting setting (measurement in at least one of CC#2 through #N), the first UL channel is transmitted in CC#1, and the second UL channel is transmitted in at least one of CC#2 through #N. - Operation 15: A report is triggered in at least one of CC#2 through #N by a reporting setting (measurement in at least one of CC#2 through #N), the first UL channel is transmitted in at least one of CC#2 through #N, and the second UL channel is transmitted in CC#1. Operation 16: A report is triggered in at least one of CC#2 to #N by a reporting setting (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.

[0150] In UEIBR, cross-CC operation may mean, for example, that the CC to which the reporting settings are configured and the CC to which the RS set as the measurement target in the reporting settings belong (corresponding to) are different.

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

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

[0153] In this disclosure, the case in which a second UL channel is transmitted in the CC of a serving cell where reporting settings (e.g., CSI reporting settings) are configured may be referred to as cross-CC case A.

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

[0155] Whether to apply Cross CC Case A or B may be predetermined in the specifications, determined using higher-layer signaling (RRC signaling / MAC CE), determined based on UE capability reports, or determined based on a combination of at least two of these.

[0156] <Considerations Regarding Event-Triggered Beam Reporting> In MIMO and mobility in Rel. 19, UEIBR L1 beam reporting is being considered. In mobility in Rel. 19, conditional LTM (CLTM) is being considered. UEIBR reporting may be used for at least one of the following: measurement reporting, beam switching, and cell switching.

[0157] A common framework may be supported between Rel. 19 MIMO and Rel. 19 Mobility, or different frameworks may be supported. 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 reducing overhead and / or latency. This assumes a unified TCI and aims to utilize the existing CSI measurement and reporting setup framework [as much as possible], targeting FR2 and sTRP using intra-cell and inter-cell beam management. The extensions include: a. UL signaling content [and, if necessary, procedures] for UE-initiated / event-driven beam reporting to facilitate rapid 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 transmission.

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

[0160] To support conditional LTMs, the following are being considered: ◆ Conditions evaluated by the UE to trigger an LTM. ◆ The aim is to support conditional LTMs, including subsequent LTMs. ◆ Prioritizing LTMs within the CU.

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

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

[0163] ServingCellConfig can include MIMOParam-r17. MIMOParam-r17 can include one or more SSB-MTC-AdditionalPCI-r17 lists (additionalPCI-ToAddModList-r17). SSB-MTC-AdditionalPCI-r17 can include additionalPCIIndex-r17, additionalPCI-r17 (PhysCellId). additionalPCI is an additional SSB PCI, distinct from the ServingCell PCI.

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

[0165] (Analysis A) For the trigger of the above UEIBR, the event instance is evaluated / determined / counted.

[0166] For example, in Event 2 of the above events, it is being considered that the event instance count will be performed for each new beam.

[0167] Furthermore, the evaluation cycle for the event instance of event 2 mentioned above is being considered.

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

[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] Furthermore, for example, the RS period of the current beam and the RS period of the new beam may be different (and 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 period of the current beam's RS. • The evaluation period of the event instance is the same as the period of the new beam's RS. • The evaluation period of the event instance is the same as the shortest period among the periods of the current beam's RS and the new beam's RS. • The evaluation period of the event instance is the larger of the shortest period among the periods of the current beam's RS and the new beam's RS, and Xms (the maximum value). • The evaluation period of the event instance is the same as the longest period among the periods of the current beam's RS and the new beam's RS.

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

[0173] Furthermore, the introduction of new UCI types (for example, UCI types other than those defined up to Rel. 18) for the first UL channel in Mode A / Mode B is being considered.

[0174] In particular, the introduction of at least one of the following is being considered for transmission / retransmission of the first UL channel related to the new UCI type: a prohibit timer and a maximum number of transmissions / retransmissions. While the prohibit timer is operating, transmission on the first UL channel will not occur even if the event conditions are met. By introducing at least one of the prohibit timer and the 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 sufficiently considered. If this consideration is insufficient, there is a risk that transmission latency / delay caused by the first UL channel will increase (Issue 1).

[0176] (Analysis B) Regarding the determination of the triggering event for Event 2, the following options are being considered for the measurement window to initiate the UE-start / 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 occasion for the first PUCCH transmission. T_proc is set by the RRC. ◆ Option 2: The measurement window is from T_Instance-T_window to T_Instance. T_Instance is set by the RRC. T_Instance is the opportunity to evaluate the event instance. The UEIBR in the second PUCCH is based on recent measurements of the RS of the new / current beam. ◆ Option 3: The length of the measurement window, slot offset, and period are set by the NW for each CSI reporting setting. ◆ Option 4: If an Event 2 instance for the new beam is obtained at time t, the UE starts (restarts) the timer for the new beam. The timer's expiration time is equal to the length set by the network (NW) of the time window (T_window).

[0177] T_window is a time window parameter for measurement. This does not exclude other options. Option 4 is an implementation similar to BFR, where multiple windows do not overlap in the time domain for a given new beam.

[0178] Thus, a time window for event evaluation (a measurement window for UE initiation / initiation of event-driven beam reporting procedures) has been considered. However, the specific operation of the first PUCCH transmission has not been sufficiently examined. Insufficient examination of this could lead to a suppression of improvements in communication quality / throughput.

[0179] Therefore, the inventors of this invention conceived a way to solve these problems.

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

[0181] (Various substitutions) In this disclosure, words enclosed in parentheses () may indicate an explanation of the preceding word (e.g., an explanation of spelling), a paraphrase, a specific example, or supplementary explanation. Also, in this disclosure, words enclosed in square brackets [] may be interpreted as part of the overall meaning of the text, or they may be interpreted as being excluded (ignored). Note that parentheses () and square brackets [] may be used for purposes / meanings other than those described above.

[0182] In this disclosure, "A / B" and "at least one of A and B" may be interpreted as mutually exclusive. In this disclosure, "A / B / C" may mean "at least one of A, B, and C".

[0183] In this disclosure, terms such as notice, activate, deactivate, indicate (or specify), select, configure, update, and determine may be interpreted interchangeably. In this disclosure, terms such as support, control, controllable, operate, and capable of operating may be interpreted interchangeably.

[0184] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-layer parameters, fields, Information Elements (IE), settings, etc., may be interpreted interchangeably. In this disclosure, Medium Access Control elements (MAC Control Elements (CE)), update commands, activation / deactivation commands, etc., may be interpreted interchangeably.

[0185] In this disclosure, the upper-layer signaling may be any or a combination thereof, such as Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, and other messages (e.g., messages from the core network, such as positioning protocol messages (e.g., NR Positioning Protocol A (NRPPPa) / LTE Positioning Protocol (LPP)) messages).

[0186] In this disclosure, MAC signaling may include, for example, MAC Control Elements (MAC CEs) and MAC Protocol Data Units (PDUs). Broadcast information may include, for example, Master Information Blocks (MIBs), System Information Blocks (SIBs), Remaining Minimum System Information (RMSIs), and Other System Information (OSIs).

[0187] In this disclosure, physical layer signaling may include, for example, Downlink Control Information (DCI) and Uplink Control Information (UCI).

[0188] In this disclosure, A b The notations A_b, Ab, and A with a b placed to the lower right may be interpreted as interchangeable. In this disclosure, A c The notation A^c, with a c superscripted above A, may be interpreted as interchangeable. In this disclosure, A b c The notation A_b^c, where b is placed to the lower right of A and c is placed to the upper right of A, may be interpreted as being interchangeable. In this disclosure, x ~x may be represented by placing a ~ above x, or it may be called x tilde. In this disclosure, x - x may be represented by placing a hyphen above it, or it may be called an x-bar. In this disclosure, x ＾ This can also be represented by placing a caret (^) above x, or it may be called an x-hat.

[0189] In this disclosure, terms such as drop, suspend, cancel, puncture, rate match, postpone, and not send may be interpreted interchangeably.

[0190] In this disclosure, terms such as index, identifier (ID), indicator, and resource ID may be interpreted interchangeably. In this disclosure, terms such as sequence, list, set, group, cluster, subset, and pool may be interpreted interchangeably.

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

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

[0193] In this disclosure, cell, PCI, serving cell, source serving cell, source cell, CC, BWP, BWP within CC, and band may be interpreted interchangeably. In this disclosure, 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 current serving cell's PCI, another serving cell, and target cell may be interpreted interchangeably. A target cell may be a cell selected from among several candidate cells. In this disclosure, switch, change, and update may be interpreted interchangeably. A serving cell may be interpreted as a serving cell before a switch or a serving cell after a switch.

[0194] In this disclosure, "transmission" and "reception" may be interpreted interchangeably.

[0195] In this disclosure, tables, mappings, associations, lists, formats, content, reports, etc., may be interpreted interchangeably.

[0196] In this disclosure, MAC CE, UCI, cell switching command, beam switching command, MAC CE for beam reporting, and MAC CE for cell switching may be interpreted as interchangeable.

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

[0198] In this disclosure, "Serving" may be interpreted as "Serving beam," "Serving cell," or "SpCell."

[0199] In this disclosure, "Neighbor" may be interpreted as any beam or cell other than a serving beam / serving cell / SpCell / SCell.

[0200] In this disclosure, candidate cells, target cells, adjacent cells, cells, etc., may be interpreted interchangeably.

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

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

[0203] In this disclosure, the terms event-based beam reporting, event-triggered beam reporting, UE-triggered beam reporting, UE-initiated beam reporting (UEIBR), UE-initiated beam management (UEIBMM), beam reporting, etc., [for Rel. 19] may be interpreted interchangeably.

[0204] In this disclosure, indicated TCI state, active TCI state, activated TCI state, configured TCI state, and RS set in RRC may be interpreted interchangeably.

[0205] Each embodiment of this disclosure is applicable to any event.

[0206] In this disclosure, rules, cases, factors, conditions, thresholds, etc., may be interpreted as interchangeable.

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

[0208] In this disclosure, beam report, CSI report, UEIBR, CSI relating to UEIBR, UEIBR-CSI, UEIBR-UCI, report, etc. may be interpreted interchangeably.

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

[0210] In this disclosure, multiplexing (to multiplex / to be multiplexed) and mapping (to map / to be mapped) may be interpreted interchangeably.

[0211] In this disclosure, the UL channel for transmitting UEIBR-CSI, CG PUSCH, type 1 CG PUSCH, type 2 CG PUSCH, DG PUSCH, and PUSCH may be interpreted as being interchangeable.

[0212] In this disclosure, other UL channels (for transmitting other UCIs), PUCCH, and PUSCH may be interpreted as interchangeable.

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

[0214] In this disclosure, beam indicator (DCI / MAC CE), TCI status indicator (DCI / MAC CE), TCI status switching command (DCI / MAC CE), cell switch command (DCI / MAC CE), DCI, MAC CE, etc., may be interpreted interchangeably.

[0215] In this disclosure, the terms "report content," "field," "ID," "measurement result," and "reported quantity" may be interpreted interchangeably.

[0216] In this disclosure, beam report, report, MAC CE, beam report MAC CE, UCI, and PUSCH may be interpreted as interchangeable.

[0217] In this disclosure, beam, beam ID, beam identifier, RS index, SSBRI, and CRI may be interpreted as interchangeable.

[0218] In this 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 interpreted interchangeably.

[0219] In this disclosure, beam and beam ID, RS and RS ID, TCI state and TCI state ID may be interpreted as mutually interchangeable.

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

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

[0222] In this disclosure, the first UL channel resource may mean a resource for the first UL channel that is set up / allocated regardless of whether or not the first UL channel is actually transmitted.

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

[0224] In this disclosure, Mode B may be interpreted as a second mode in which no DCI is transmitted to schedule / trigger the UEIBR / Beam Report (Second UL Channel).

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

[0226] (Wireless communication method) The UE may apply each embodiment of the disclosure in conjunction with the performance of beam measurement / reporting (e.g., UEIBR). The NW / BS / gNB may provide / transmit to the UE settings / instructions etc. for the UE to perform the operations / controls described in each embodiment of the disclosure. Furthermore, the NW / BS / gNB may perform various operations / controls necessary to receive event-triggered beam reports / UEIBR from the UE.

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

[0228] One or more embodiments / options may be applied individually or in combination.

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

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

[0231] In this disclosure, the terms "specific period," "prohibition timer," "operating period / operating," "measurement window," and "time window" may be interpreted as interchangeable.

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

[0233] In this disclosure, the terms "evaluation occasion" and "resources / opportunities for new / current RS transmission / measurement" may be interpreted as mutually exclusive.

[0234] In this disclosure, the occurrence of an event, the fulfillment of a trigger condition, the fulfillment of an event [instance] condition, the occurrence of M event instances within a measurement window, and the counter [relative to the measurement window] reaching M may be interpreted interchangeably. In this disclosure, the evaluation of an event [instance], the determination of an event instance [condition] in an event evaluation opportunity, and the determination of the measurement result of a new / current beam [RS] may be interpreted interchangeably. In this disclosure, the occurrence / occurrence of an event instance and the fulfillment of an event [instance] condition in an event evaluation opportunity may be interpreted interchangeably.

[0235] The UE may receive a configuration for the CSI report (e.g., CSI-ReportConfig). This configuration may indicate, or be associated with, at least one of the following: the RS of the new / current beam (period / timing), the ID / period / timing of the first PUCCH resource, the period / timing of the evaluation opportunity, mode A or B, and the 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 a prohibit timer for the first UL channel.

[0237] The UE may determine whether or not to allow transmission on the first UL channel based on the prohibition timer / time window related to the first UL channel.

[0238] <<Option 0-1>> A prohibit timer for the first UL channel may be [explicitly] set for the UE.

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

[0240] The prohibit timer may be configured, for example, using a specific RRC parameter (e.g., 1stPUCCH-ProhibitTimer).

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

[0242] The value of this prohibit timer may be set to be the same as the value of other prohibit timers (for example, the SR-ProhibitTimer).

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

[0244] The start timing of the prohibit timer may be a specific timing based on the first / second UL channel associated with the prohibit timer.

[0245] The specific timing in question may be, for example, at least one of the following: - The first symbol after the termination of the first UL channel. - The first symbol after the termination of the second UL channel.

[0246] A common start timing for the prohibit timer may be applied to both Mode A and Mode B.

[0247] Different start timings for the prohibit timer may be applied to Mode A and Mode B. In other words, separate start timings for the prohibit timer may be set / applied to Mode A and Mode B.

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

[0249] For example, in mode B, the start timing of the prohibit timer may be the first symbol after the end of the first UL channel.

[0250] <<Option 0-2>> The prohibit timer for the first UL channel may be [implicitly] specified / set.

[0251] For example, the prohibition 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 a UE.

[0253] The time window may be used for at least one of the following purposes, for example: ・An event evaluation period corresponding to a first UL channel [resource]. ・A first UL channel [transmission] prohibition period for another first UL channel.

[0254] In a case where the time window is used as a first UL channel [transmission] prohibition period for another first UL channel, when a first UL channel A and a first UL channel B are arranged in chronological order, and the first UL channel A is transmitted within the time window corresponding to the first UL channel B, the transmission of the first UL channel B may be omitted.

[0255] FIG. 2 is a diagram illustrating an example of a time window according to Alternatives 0-2. In the example illustrated in FIG. 2, the length of the time window is T ｗｉｎｄｏｗ . In the example illustrated in FIG. 2, time t-T ｗｉｎｄｏｗ to time t is the time window corresponding to PUCCH A (resource), and time t'-T ｗｉｎｄｏｗ to time t' is the time window corresponding to PUCCH B (resource). Each PUCCH resource starts after a processing time (T ｐｒｏｃ ) for PUCCH preparation elapses from the end of each time window.

[0256] In a case where the time window is used as a first UL channel [transmission] prohibition period for another first UL channel, in the example illustrated in FIG. 2, when PUCCH A is transmitted within the time window from time t'-T ｗｉｎｄｏｗ to time t', the transmission of PUCCH B corresponding to the time window is prohibited (PUCCH B is not transmitted).

[0257] In this 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 mutually exclusive. For example, in this option, "the first UL channel is transmitted within the time window" may be interpreted as "the second UL channel is transmitted within the time window."

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

[0260] For example, in mode B, the prohibition criterion 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 a prohibition timer / time window.

[0263] For a new UCI (e.g., UEIBR-UCI / CSI) for the first UL channel, the prohibition timer / time window may be associated with at least one of the following: • One first UL channel resource. • Multiple first 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 related to the prohibited timer / time window may be determined based on rules specified in the specifications beforehand, set using RRC signaling, determined based on UE capability information reporting, or determined based on a combination of at least two of these.

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

[0266] For example, a UEIBR may be set for a UE using a single CC.

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

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

[0269] The association between the first UL channel and 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 / configurations are associated with one first UL channel resource. • Case 1-1-2 (see Figure 3B): Multiple events / configurations are associated with multiple first UL channel resources. One event / configuration is associated with one first UL channel resource. • Case 1-1-3 (see Figure 3C): Multiple events / configurations are associated with multiple first UL channel resources. One event / configuration may be associated with multiple first UL channel resources, or multiple events / configurations may be associated with one first UL channel resource.

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

[0271] In this case, considering cases 1-1-1 / 1-1-2 / 1-1-3 above, there is concern that transmission latency / delay will occur due to the occurrence of more transmissions on the first UL channel (Issue 1A). The solution to this problem will be explained below.

[0272] The implementation / operation of the prohibit timer / time window may be at least one of the following options 1.1A to 1.4A: • Option 1.1A: The prohibit timer / time window operates for each first UL channel resource. • Option 1.2A: The prohibit timer / time window operates for each event / setting associated with one first UL channel resource. • Option 1.3A: The prohibit timer / time window operates for each event / setting set in one CC. • Option 1.4A: The prohibit timer / time window is not applied.

[0273] For example, the application of options 1.1A / 1.2A / 1.4A is preferable for Case 1-1-1.

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

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

[0276] For example, the UE does not need to evaluate other events while the prohibit timer is running. After the prohibit timer expires, the UE may resume evaluating events.

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

[0278] In this case, if the event conditions for the other event are met while the prohibit timer is operating, the UE may transmit a first UL channel corresponding to the other event immediately after the prohibit timer expires.

[0279] Furthermore, in this case, if the event conditions for the other event are met while the prohibit timer is operating, the UE may drop the transmission on the first UL channel corresponding to the other event.

[0280] In this case, if the event conditions for the other event are met while the prohibit timer is operating, the UE may decide whether to transmit or drop the first UL channel based on the priority of the event related to the prohibit timer and the priority of the other event.

[0281] Figure 4 shows an example of the operation of the prohibit timer related to option 1.1A. The example shown in Figure 4 shows an example in which each event (number of event instances) is evaluated for the RS of the current beam and the RS of the new beam (RS#0-RS#N). In the example shown in Figure 4, the UE triggers transmission on the corresponding first UL channel when the event condition is met a certain number of times (e.g., M) within the evaluation window of each event instance (the number of event instances reaches M). 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 event instances (e.g., the value of M) are the same in the following similar diagrams, so the explanation will not be repeated.

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

[0284] In the example shown in Figure 4, even if the trigger conditions for 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 prohibit timer is operating, the other first UL channels will not transmit.

[0285] Figure 5 shows an example of the operation of the time window related to option 1.1A. In the example shown in Figure 5, the time window corresponding to each first UL channel resource is shown. In the example shown in Figure 5, at a certain time, the event instance of event 2 of RS#0 reaches M, and the corresponding first UL channel is triggered. Also, at other times after that time, the trigger conditions for 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.

[0286] In the example shown in Figure 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 Figure 5, a time window corresponding to each first UL channel resource may also be in operation.

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

[0289] Furthermore, while the prohibit timer for event 2 is operating, the trigger conditions for other first UL channels (the first UL channel for event 7 in RS#0, and the first UL channel for event 2 in RS#1) are met. 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 in RS#1. This is because the prohibit timer is set / applied for each event / setting.

[0290] Figure 7 shows an example of the operation of the time window related to option 1.2A / 1.3A. In the example shown in Figure 7, the time window for each event corresponding to each first UL channel resource is shown. In the example shown in Figure 7, at a certain time, the event instance of event 2 of RS#0 reaches M, and the corresponding first UL channel is triggered. Also, at other times after that time, the trigger conditions for 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.

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

[0292] Although not shown in Figure 7, time windows (for Event 2 and Event 7) corresponding to each first UL channel resource may also be in operation.

[0293] For example, in option 1.3A, if the prohibit timer for a certain event is activated, transmission on multiple (e.g., all) configured first UL channels associated with that event may be prohibited.

[0294] Furthermore, for example, in option 1.3A, if a transmission occurs on the first UL channel within a time window corresponding to a plurality of first UL channel resources that are set, even if the event instance satisfies the trigger condition again, transmission on the first UL channel related to the event for which the trigger condition is satisfied may be prohibited among the plurality of first UL channel resources that are set.

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

[0296] Furthermore, in options 1.2A / 1.3A, the start position / length of the prohibition timer / time window for each event / setting may be set / defined commonly or separately (for example, they may be different).

[0297] According to Embodiment A1-1, even in the case of single CC and multi-event cases, the operation related to the prohibition timer / time window of the first UL channel can be appropriately defined.

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

[0299] For example, a UEIBR may be set for a single event in a UE.

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

[0301] The association between the first UL channel and 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 Figure 8A): Multiple CCs are associated with one first UL channel resource. • Case 1-2-2 (see Figure 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 Figure 8C): Multiple CCs are associated with multiple first UL channel resources. One CC may be associated with multiple first UL channel resources, or multiple CCs may be associated with one first UL channel resource.

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

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

[0304] The implementation / operation related to 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 for each first UL channel resource. • Option 1.2B: The prohibition timer / time window operates for each CC associated with one first UL channel resource. • Option 1.3B: The prohibition timer / time window operates for each CC among multiple CCs that are set. • Option 1.4B: The prohibition timer / time window is not applied.

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

[0306] For Case 1-2-2, for example, the application of option 1.1B / 1.4B is preferable.

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

[0308] With respect to Embodiment A1-2, Embodiment A1-1 may be applied by replacing "Event / Setting" with "CC".

[0309] According to Embodiment A1-2, the operation related to the prohibition timer / time window of the first UL channel can be appropriately defined even in the case of multi / cross CC and single event cases.

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

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

[0312] For example, a UEIBR (UEI Block Rating) may be set for a UE (User Account) that uses multiple CCs (multi-CC / cross-CC).

[0313] The association between the first UL channel and 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 / configurations are associated with one first UL channel resource. • Case 1-3-2 (see Figure 9B): One CC from among multiple CCs is associated with one first UL channel resource. Multiple (or one) events / configurations are associated with one first UL channel resource. • Case 1-3-3 (see Figure 9C): Multiple (or one) CCs are associated with one first UL channel resource. One event / configuration is associated with one first UL channel resource. • Case 1-3-4 (see Figure 9D): Multiple CCs are associated with one first UL channel resource. Multiple events / configurations are associated with one first 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 concern that transmission latency / delay will occur due to the occurrence of more transmissions on the first UL channel (Issue 1C). The solution to this problem will be explained below.

[0315] The implementation / operation of the prohibit timer / time window may be at least one of the following options 1.1C to 1.6C: • Option 1.1C: The prohibit timer / time window operates for each first UL channel resource. • Option 1.2C: The prohibit timer / time window operates for each CC associated with one first UL channel resource. • Option 1.3C: The prohibit timer / time window operates for each event / setting associated with one first UL channel resource. • Option 1.4C: The prohibit timer / time window operates for each CC among multiple CCs that is configured. • Option 1.5C: The prohibit timer / time window operates for each event / setting configured in one CC. • Option 1.6C: The prohibit timer / time window is not applied.

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

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

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

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

[0320] Embodiment A1-3 may be applied in combination with Embodiments A1-1 and A1-2.

[0321] According to Embodiment A1-3, even in the case of multi / cross CC and multi-event cases, the operation related to the prohibition timer / time window of the first UL channel can be appropriately defined.

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

[0323] In this case, a prohibition timer / time window may be triggered for each combination of events / settings.

[0324] The prohibition timer / time window may support multiple events (for example, events 1 / 2 / 7).

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

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

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

[0328] Furthermore, for each of the above cases, which option applies may be specified in advance in the specifications, set / instructed using RRC signaling / MAC CE / DCI, determined based on UE capability reports, or determined based on a combination of at least two of these. For example, for each of the above cases, which option applies may be set / instructed [quasi-statically / dynamically] using RRC signaling / MAC CE / DCI [based on UE capability], or it may be switched [implicitly] based on NW / UE settings.

[0329] Alternatively, the applicable option may be determined for each mode / first UL channel resource.

[0330] For example, if one first UL channel resource is associated with mode A of an event (e.g., events 2 and 7), and another first UL channel resource is associated with mode B of another event (e.g., event 1), then an option (e.g., option 1.2A) may be applied to that first UL channel resource, and another option (e.g., option 1.4A) may be applied to that other first UL channel resource.

[0331] The event / mode / option described herein is merely an example, and any event / mode / option (or combination thereof) described herein may be applied.

[0332] According to this embodiment A1, the operation related to the prohibition timer / time window of the first UL channel can be appropriately defined, and the transmission waiting time / delay caused by the first UL channel can be reduced.

[0333] <Analysis B0> Option 1 may count how many event instances are contained within a measurement window in which one measurement window corresponds to (associates) one first PUCCH resource, and the measurement window starts from a point that is T_window further back from T_PUCCH (the transmission timing of the first PUCCH, PUCCH transmission timing), with the endpoint being T_proc (the PUCCH preparation time). An event instance may occur if the event instance conditions are 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 set by the RRC [reported as UE capability and based on that report].

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

[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 all 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 all larger 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 one of the following options:

[0337] ◆Option 1 All of relations 1 through 3 may be defined in the specification. All of relations 1 through 3 may be assumed. There may be no constraints between the event evaluation cycle, new beam RS cycle, current beam RS cycle and the first PUCCH resource cycle. According to Option 1, flexibility in resource configuration can be ensured and adapted to various use cases and requirements.

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

[0339] Which of relations 1 through 3 is enabled / assumed may be specified in the specification, or it may be notified from the network to the user via 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> A prohibition timer, or a method equivalent to a prohibition timer, may be applied to any of the above-described options 1 to 4 regarding the measurement window.

[0344] The UE may apply a first PUCCH transmission prohibition process that prohibits / cancels the transmission of a specific first PUCCH if the first PUCCH transmission prohibition condition is met.

[0345] A prohibition timer may be applied to any option related to the measurement window.

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

[0347] In designing the condition for prohibiting the transmission of the first PUCCH, false alarms (false detections) may be considered. A false alarm may occur when the network mistakenly detects the first PUCCH and schedules the second PUCCH, even though the trigger condition is not met. Including the second PUCCH caused by a false alarm in a specific signal may cause the prohibition / cancellation of the first PUCCH transmission even after the transmission of the second PUCCH due to the false alarm. It may not be possible to send a report immediately after the event is triggered.

[0348] To prevent excessive frequency of first PUCCH transmissions, at least one of the following options x may be applied.

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

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

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

[0352] The condition for prohibiting transmission of the first PUCCH may be that the resource of the first PUCCH overlaps (or is included in) a specific period (prohibition timer operation period) after the transmission / resource of a specific signal.

[0353] ◆Option 1-2 The method using a measurement window (or dedicated window) is applied. If a particular measurement window contains the transmission of a specific signal triggered by an event in another measurement window, the UE may cancel the first PUCCH transmission to that particular measurement window. If a particular measurement window does not contain the transmission of a specific signal triggered by an event in another measurement window, the UE may transmit the first PUCCH to that particular measurement window.

[0354] The condition for prohibiting transmission of the first PUCCH may be that the transmission / resource of a specific signal overlaps (or is included in) part or all of the measurement window (first time window) corresponding to the first PUCCH (of the event that triggers the first PUCCH (first event)). 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] Figure 10 shows an example of canceling 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 condition for prohibiting the transmission of the first PUCCH for the first PUCCH#B is that the transmission / resource of the specific signal (first PUCCH#A) overlaps with a part of measurement window #B corresponding to the first PUCCH#B. Since the condition for prohibiting the transmission of the first PUCCH for the first PUCCH#B is met, the UE may cancel the transmission of the first PUCCH#B.

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

[0357] If T_window < 1st PUCCH resource period (or T_prohibitwindow < 1st PUCCH resource period) and the setting indicates (guarantees) that no specific signal is included within the measurement window, then the UE does not need to transmit the 1st PUCCH (new UCI) if the following additional condition is met: ◆ Additional condition: A specific signal is transmitted between the end of that measurement window and the end of the previous measurement window.

[0358] <<Option 2>> For each parameter of the following multiple options 2-x, option 1-x may be applied. The CSI-ReportConfig may be associated with a first PUCCH resource [ID] (and may include information indicating the first PUCCH resource). The first PUCCH resource [ID] may be associated with an event type (the information for 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 specific signal may be defined in the specification or set / indicated by RRC IE / MAC CE / DCI. The type of specific signal may include at least one of the following options 3-x.

[0360] ◆Option 3-1: First PUCCH.

[0361] ◆Option 3-2: Second PUCCH. The second PUCCH may be any of the following options 3-2-x. —◆Option 3-2-1: Any second PUCCH. —◆Option 3-2-2: A second PUCCH requested / triggered by an active first PUCCH. Whether the first PUCCH is active or inactive may be any of the following options 3-2-2-x. —◆Option 3-2-2-1: If the first PUCCH is within the request period prior to the transmission of the second PUCCH, the UE may consider (or determine) that the first PUCCH is active (that the second PUCCH is requested / triggered by an active first PUCCH, or that the second PUCCH is a specific signal). Otherwise, the UE may consider its first PUCCH to be invalid (its second PUCCH is not requested / triggered by an active first PUCCH, or its second PUCCH is due to a false alarm). The request period [length / start / end / timing] may be specified in the specification or set / instructed by 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 (a set). The second PUSCH may be any of the options 3-2-x mentioned above.

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

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

[0365] For mode A, all options 3 except 3-2-2 can be applied. For mode B, all options 3-x of option 3 can be applied.

[0366] <<Option 4>> When option 3-2 or option 3-3 is applied to mode A, the specific signal may include the DCI that schedules the second PUSCH in addition to the second PUSCH itself.

[0367] When option 2-4 applies (for each first PUCCH resource), a specific signal may be restricted by at least one of the following options 4-x: ◆Option 4-1: The specific signal is set by the configuration of the first PUCCH resource (e.g., firstPUCCHResourceConfig-UEIBR) based on the occurrence of an event (fulfillment of a trigger condition) within the measurement window [corresponding to its second PUCCH]. ◆Option 4-2: The specific signal is triggered by the same beam [RS] used (measured) in the occurrence of the event (fulfillment of a trigger condition) within the measurement window. ◆Option 4-3: The specific signal is associated with the configuration (CSI-ReportConfig pointing to that first PUCCH resource) associated with the first PUCCH [resource] based on the occurrence of an event (fulfillment of a trigger condition) within the measurement window. ◆Option 4-4: The specific signal is associated with the event type (of the event) associated with the first PUCCH [resource] based on the occurrence of an event (fulfillment of a trigger condition) within the measurement window.

[0368] According to this embodiment, it is possible to prevent excessive frequency of first PUCCH transmissions 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 occasion for the first PUCCH transmission. T_proc is set by RRC.

[0370] Figure 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 measurement window #A is t=T_PUCCH-T_proc, and the start time of measurement window #A is t-T_window. When an event occurs within measurement window #A (the trigger condition is met within measurement window #A), the UE may send a first PUCCH using the first PUCCH resource #A, and then send a second PUSCH using the second PUSCH resource #A.

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

[0372] <<Embodiment C1-1>> In modes A / B, the UE may be unable to transmit a first PUCCH using a pre-configured first PUCCH resource (because the first PUCCH resource is unavailable) depending on the circumstances.

[0373] In this disclosure, the statements that the first PUCCH resource is unavailable, that the first PUCCH resource overlaps with the transmission / reception of other channels / signals, that the priority of the first PUCCH resource is lower than the priority of the other overlapping channel / signal transmission / reception, and that the first PUCCH resource is set / instructed as a DL resource / symbol / slot may be interpreted as mutually exclusive.

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

[0375] <<Embodiment C1-2>> In Mode B, the UE may be unable to transmit the second PUSCH in the pre-configured second PUSCH resource (CG-PUSCH resource) depending on the circumstances.

[0376] In this disclosure, the statements that the second PUSCH resource is unavailable, that the second PUSCH resource overlaps with the transmission / reception of other channels / signals, that the priority of the second PUSCH resource is lower than the priority of the other overlapping channel / signal transmission / reception, and that the second PUSCH resource is set / instructed as a DL resource / symbol / slot may be interpreted as mutually exclusive.

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

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

[0379] If it is determined before the start of the measurement window for the first PUCCH corresponding to that second PUSCH resource that a second PUSCH resource is unavailable, the UE may evaluate the event in the measurement window for that first PUCCH, and if the trigger condition is met, send that first PUCCH, and then send the second PUSCH at the first available second PUSCH (CG-PUSCH) resource after that [unavailable] second PUSCH resource.

[0380] In the example in Figure 11 above, when the configured second PUCCH resource #B is unavailable, an event evaluation may be performed in measurement window #B for the corresponding first PUCCH resource #B. If the trigger condition is met, the first PUCCH may be sent in the first PUCCH resource #B, and then the second PUCCH may be sent in the next available second PUCCH resource #C. This operation may be based on at least one of the following examples: ◆Example: When the event evaluation in measurement window #B for the first PUCCH resource #B does not meet the trigger condition, the UE may include in the second PUCCH in the available second PUCCH resource #C a report that should be sent in the [unavailable] second PUCCH resource #B (a report based on the event in measurement window #B for the corresponding first PUCCH resource #B). ◆Example: When an event evaluation in measurement window #C for the first PUCCH resource #C satisfies the trigger condition, the UE may include at least one of the following reports in the second PUCCH of the [available] second PUCCH resource #C: —◆Report: A report to be sent in the [unavailable] second PUCCH resource #B (a report based on an event in measurement window #B for the corresponding first PUCCH resource #B). —◆Report: A report based on an event in the measurement window for the first PUCCH resource #C corresponding to the [available] second PUCCH resource #C. —◆Report: A report based on the event with the higher priority among the event in measurement window #B corresponding to the [unavailable] second PUCCH resource #B (corresponding first PUCCH resource #B) and the event in measurement window #C corresponding to the [available] second PUCCH resource #C (corresponding first PUCCH resource #C).

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

[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, and the first PUCCH resource period may be based on at least one of the following multiple embodiments C2-x.

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

[0385] The measurement window may contain one or more evaluation opportunities, so T_window ≥ event evaluation period. When the value of M is set, T_window ≥ M * event evaluation period.

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

[0387] If the event evaluation cycle ≤ T_window < 1st PUCCH resource cycle, some evaluation opportunities may not be included in any measurement window. In this case, the behavior of the UE may be based on one of the following options x: ◆Option 1: The UE measures RS for all evaluation opportunities and does not use RS outside of measurement windows for event evaluation. ◆Option 2: The UE does not measure RS for evaluation opportunities that are not included in any measurement window.

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

[0389] If the event evaluation cycle < the first PUCCH resource cycle ≤ T_window, then all evaluation opportunities are included in one of the measurement windows. In this case, the UE may measure RS for all evaluation opportunities. In the example in Figure 13, the event evaluation cycle < the first PUCCH resource cycle = T_window, and multiple measurement windows are consecutive. In this case, all evaluation opportunities are included in one of the measurement windows.

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

[0391] Since the measurement window contains one or more evaluation opportunities, T_window ≥ event evaluation period = first PUCCH resource period may also be the case. When the value of M is set, T_window ≥ M * event evaluation period = M * first PUCCH resource period may also be the case.

[0392] In the example shown in Figure 14, the event evaluation cycle = 1st PUCCH resource cycle = T_window, and multiple measurement windows are consecutive. In this case, all evaluation opportunities are included in one of the measurement windows.

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

[0394] The measurement window may contain one or more evaluation opportunities, so T_window ≥ event evaluation period. When the value of M is set, T_window ≥ M * event evaluation period.

[0395] If the first PUCCH resource period < event evaluation period ≤ T_window, then multiple measurement windows for multiple consecutive first PUCCH resources may contain the same evaluation opportunity, resulting in redundancy of the first PUCCH resources. In the example in 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 contain 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: The first PUCCH is transmitted in only one of the multiple first PUCCH resources for multiple measurement windows containing the same evaluation opportunity.

[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 also be applied to option 2 below. ◆Option 2: The measurement window is from T_Instance-T_window to T_Instance. T_Instance is set by RRC. T_Instance is an opportunity to evaluate an event instance. The UEIBR in the second PUSCH is based on recent measurements of the RS of the new / current beam.

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

[0399] <<Measurement Window Constraint>> In order for the measurement window to include one or more evaluation opportunities, T_window ≥ the first PUCCH resource period may be used.

[0400] <<Constraint on the number of overlapping measurement windows>> If there is no constraint, the number of evaluation opportunities included in the measurement windows will overlap.

[0401] The number of overlapping measurement windows (overlap count) may be limited. The maximum value of T_window may be limited. There may be a constraint that 1st PUCCH resource cycle * number of possible overlaps > T_window. The number of possible overlaps may be the maximum value of the overlap count. The number of possible overlaps may be from UE capability reporting information or may be set by RRC [based on UE capability].

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

[0403] A new parameter indicating the number of possible overlaps may be set.

[0404] The number of overlaps does not need to 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 also 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 the timer 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 a count reset: ◆Candidate #1: RS reset / update or MAC CE signaling is received for a new beam. ◆Candidate #2: The indicated TCI state [current beam measured based on it] is updated. ◆Candidate #3: A UEIBR is transmitted. ◆Candidate #4: A NW response (e.g., 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 reset by RRC signaling.

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

[0409] If, after a particular new beam has met the trigger conditions, the UE has not been able to transmit the corresponding first PUCCH, or if the UE has transmitted the corresponding first PUCCH but has not received a DCI, and no event instance occurs in subsequent evaluation opportunities, the UE may cancel the retransmission of the first PUCCH. The UE may also cancel the retransmission of the first PUCCH based on a counter reset or timer expiration. 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 will remain greater than or equal to M unless a counter reset operation is performed due to other factors. If the prohibit timer is not running, the UE may attempt to transmit the first PUCCH again. The first PUCCH may be transmitted even if the situation has changed from one where the trigger condition is met to one where the trigger condition is not met by the time the first PUCCH is transmitted.

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

[0412] The value of X in options 2-2 and 2-3 may be specified in the specifications or set / indicated by 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 also 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 a measurement window, it is assumed that the following procedure is performed if an error occurs in the first PUCCH transmitted by the UE. ―◆The UE transmits the first PUCCH to the NW. ―◆The NW cannot correctly receive the first PUCCH. ―◆The NW does not transmit the first DL channel (DCI for scheduling a 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 NW cannot receive the second PUSCH.

[0417] ◆Case 2 When Option 1 is applied to a measurement window, it is assumed that the following procedure is performed if an error occurs in the first DL channel (DCI) transmitted by the NW. ―◆The UE transmits the first PUCCH to the NW. ―◆The NW receives the first PUCCH. ―◆The NW transmits the first DL channel (DCI for scheduling a second PUSCH) to the UE. ―◆The UE cannot correctly receive the first DL channel. ―◆The UE does not transmit the second PUSCH to the NW. ―◆The NW cannot receive the second PUSCH.

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

[0419] <<Embodiment C5-1>> In Cases 1 / 2, if the event is not satisfied in the first or up to the X-th measurement window (Measurement Window #B) after the measurement window (Measurement Window #A) that triggered the first PUCCH corresponding to the untransmitted report, any one of the following plurality of operations x may be performed for the report.

[0420] ◆Operation 1 The UE may not transmit the first PUCCH on the first PUCCH resource corresponding to Measurement Window #B, and drop the untransmitted report [corresponding to Measurement Window #A].[|END]]

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

[0422] Under the condition for transmitting the first PUCCH (first PUCCH transmission condition), the following exceptions may be provided. ―◆When an event evaluation condition is not satisfied within a measurement window, the first PUCCH has been transmitted in the first or up to the X-th first PUCCH resource after the first PUCCH resource corresponding to the measurement window, and DCI corresponding to the first PUCCH has not been received, or a second PUSCH corresponding to the first PUCCH has not been transmitted (is not scheduled), the UE may transmit the first PUCCH in the first PUCCH resource corresponding to the measurement window.

[0423] A condition for prohibiting / canceling transmission of the first PUCCH (first PUCCH transmission prohibition condition) may be configured or may be specified in the specification. Under the first PUCCH transmission prohibition condition, the following exception (condition for transmitting the first PUCCH) may be provided. ―◆When the first PUCCH has been transmitted within a measurement window, and DCI corresponding to the first PUCCH has not been received, or a second PUSCH corresponding to the first PUCCH has not been transmitted (is not scheduled), the UE may transmit the first PUCCH in the first PUCCH resource corresponding to the measurement window.

[0424] When the first PUCCH is transmitted, the subsequent second PUSCH scheduled accordingly may transmit / carry the content of the untransmitted report as it is, or may transmit / carry the latest report content at that time point based on the same configuration as the untransmitted report.

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

[0426] <<Embodiment C5-2>> In Case 1 / 2, if an event is fulfilled in the first or Xth measurement window (Measurement Window #B) after the measurement window (Measurement Window #A) that triggered the first PUCCH corresponding to the report that was not transmitted, one of the following multiple actions x may be performed on that report.

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

[0428] This operation may also occur when the first PUCCH transmission disable process is applied / set. The first PUCCH transmission disable condition for a particular first PUCCH may be that the measurement window corresponding to that particular first PUCCH contains other first PUCCHs [triggered by the same beam [RS] as the beam [RS] that triggered that first PUCCH]. The first PUCCH transmission disable process may be that, if the first PUCCH transmission disable condition for a particular first PUCCH is met, the UE does not transmit the particular first PUCCH.

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

[0430] This operation may also occur when the first PUCCH transmission disable process is applied / set. The first PUCCH transmission disable condition for a particular first PUCCH may be that the measurement window corresponding to the particular first PUCCH contains another second PUCCH [triggered by the same beam [RS] as the beam [RS] that triggered the first PUCCH]. The first PUCCH transmission disable process may also be that, if the first PUCCH transmission disable condition for a particular first PUCCH is met, the UE does not transmit the particular first PUCCH.

[0431] If the first PUCCH transmission prohibition process is applied / configured, the following exceptions may be provided in the first PUCCH transmission prohibition condition: The first PUCCH transmission prohibition condition for a particular first PUCCH may be that there are other first PUCCHs [triggered by the same beam [RS] as the beam [RS] that triggered the first PUCCH] within the measurement window corresponding to the particular first PUCCH. The first PUCCH transmission prohibition process may also be that if the first PUCCH transmission prohibition condition for a particular first PUCCH is met, the UE will not transmit the particular first PUCCH. —If a first PUCCH has been transmitted within a measurement window and the DCI corresponding to that first PUCCH has not been received, or the second PUCCH corresponding to that first PUCCH has not been transmitted (not scheduled), the UE may transmit the first PUCCH in the first PUCCH resource corresponding to that measurement window.

[0432] When the first PUCCH is transmitted, the subsequent second PUCCH scheduled accordingly may transmit / carry one of the following: - The second PUCCH may transmit / carry the content of the report that was not transmitted [corresponding to measurement window #A]. - The second PUCCH may transmit / carry the content of the latest report at that time, based on the same settings as the report that was not transmitted [corresponding to measurement window #A]. - The second PUCCH may transmit / carry the content of the report with higher priority among the report that was not transmitted [corresponding to measurement window #A] and the report based on measurement window #B.

[0433] For reports that were not sent, one of the following actions may be taken: - The UE discards the reports that were not sent. - The UE retains the reports that were not sent until the next second PUSCH transmission opportunity. - The UE retains the reports that were not sent until the specified / configured retention period expires.

[0434] Priority may be based on one of the following priorities: -◆ Priority based on the CSI-ReportConfig in which each report's settings are stored is applied. -◆ Priority based on the CSI-ReportConfig in which each report's settings are stored may be determined by one of the following determination methods: -◆ Event type priority may be defined in the specification or 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 reports triggered earlier or later take precedence may be specified in the specification or set by a higher-layer parameter.

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

[0436] The lower the priority value of a report, the higher its priority can be.

[0437] Prioritization based on CSI-ReportConfig may be based on several calculation methods, including the following:

[0438] ◆Calculation Method 1: The priority value is calculated using the formula Pri for the priority value of existing CSI reports. iCSI (y,k,c,s) = 2・N Cells ・M s ・y+N cells ・M s ・k+M s - c+s may be reused. Here, y=0 for aperiodic CSI reports transported on PUSCH, y=1 for semi-persistent CSI reports transported on PUSCH, y=2 for semi-persistent CSI reports transported on PUCCH, and y=3 for periodic CSI reports transported on PUCCH. k=0 for CSI reports transporting L1-RSRP, and k=1 for CSI reports that do not transport L1-RSRP. c may be the index of the serving cell, N Cellsc may be the value of the upper layer parameter maxNrofServingCells (maximum number of serving cells). For CSI reports configured using ltm-CSI-ReportConfig, c may be the serving cell index in which the report settings are configured. s may be reportConfigID (ID of CSI-ReportConfig), and M s This 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 ltm-CSI-ReportConfigId, and M s This may also be the value of the upper-layer parameter maxNrofLTM-CSI-ReportConfigurations (the maximum number of CSI reporting configurations for LTM). The ascending order of priority values ​​may also be the ascending order of reportConfigID, and the descending order of priority may also be the ascending order of reportConfigID.

[0439] In the case of UEIBR, y may be 0, or it may be any other value {1, 2, 3}.

[0440] Since a smaller reportConfigID indicates higher priority, it may be expected that a CSI-ReportConfig that should have higher priority will have a smaller ID.

[0441] ◆Calculation Method 2 The priority value is calculated using the formula Pri for the priority value of existing CSI reports. iCSI (y,k,c,s) = 2・N Cells ・M s ・y+N cells ・M s ・k+M s - You may modify and reuse parts of c+s. Events may be reflected in priority.

[0442] To ensure that reporting priorities differ depending on the event configured by CSI-ReportConfig, a variable indicating the event type may be added to the priority value calculation formula.

[0443] In the case of UEIBR, y may be 0, or it may be any other value {1, 2, 3}.

[0444] The variable indicating the event type may be e, where e=0 for the highest priority event type, e=1 for the next highest priority event type, and e=2 for the lowest priority event type. In this case, the formula for calculating the priority value may be any 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+3・N 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+3・N Cells ・M s ・k+3・M s ・c+M s ・e+s ―◆Pri iCSI (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 scheduling the first PUCCH or the second PUCCH in mode A of option 1, the UE can operate properly.

[0446] <Supplement> <<Notification of Information to UE>> In the embodiments described above, notification of any information from the Network (NW) (e.g., Base Station (BS)) to the UE (in other words, reception of any information from the BS at the UE) may be performed using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE, RRC messages, LTE positioning protocol (LPP) messages), specific signals / channels (e.g., DCI, PDCCH, PDSCH, reference signals), or a combination thereof.

[0447] When the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new Logical Channel ID (LCID) not defined in existing standards in the MAC subheader. The MAC CE may be an extension of an existing MAC CE. For example, the MAC CE may introduce a new octet into an existing MAC CE.

[0448] If the above notification is made by DCI, the notification may be made by a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used to scramble the Cyclic Redundancy Check (CRC) bits assigned to the DCI, or the format of the DCI. 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 arbitrary information to the UE in the above-described embodiments may be performed periodically, semi-persistently (triggered by the UE or a gNB), or aperiodically (triggered by the UE or a gNB).

[0450] In the above-described embodiments, the UE may receive information (QCL information) on at least one of the following several QCL rules / QCL types from the NW. ◆QCL Type A (Doppler shift, Doppler spread, average delay and delay spread) ◆QCL Type B (Doppler shift and Doppler spread) ◆QCL Type C (Doppler shift and average delay) ◆QCL Type D (spatial reception parameter)

[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 of PDCCH / PDSCH

[0452] In the above-described embodiments, the information from the NW may be configured / indicated by the following methods. ◆Common to a plurality of UEs, or UE-specific ◆Cell-specific, or common to a plurality of cells ◆Per UE / Per CC / Per BWP / Per band / Per cell / Per cell group (CG)

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

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

[0455] If the above notice is made by the UCI, the notice may be transmitted using PUCCH or PUSCH.

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

[0457] <<Regarding the Application of Each Embodiment>> In UE / BS, specific (one or more) processes / operations / controls / assumptions / information for at least one of the embodiments described above may be applied (or used) if any or more of the following conditions are met: - A higher-layer parameter indicating the specific process / operation / control / assumption / information is set. - The specific process / operation / control / assumption / information is determined based on the relevant higher-layer parameter. - The specific process / operation / control / assumption / information is designated / activated / triggered by MAC CE / DCI / UCI / Resource / Channel / RS. - A specific UE capability indicating (or related to) the specific process / operation / control / assumption / information is reported or supported. - The application of the specific process / operation / control / assumption / information is determined based on specific conditions.

[0458] The specific UE capabilities described above may include at least one of the following: • Supporting specific processing / operations / controls / information for at least one of the embodiments described above; • Supporting event-triggered beam reporting / UEIBR; • Supporting MIMO / mobility from Rel. 19 onwards; • Supporting UEIBR using MAC CE / UCI; • Supporting event combinations (e.g., events 1 / 2 / 7); • Total number of beams reported; • Number of beams that meet the conditions; • Supporting prohibition timers / time windows related to specific events (e.g., events 2 / 7 / 1); • Supporting cancellation of the first UL channel.

[0459] Furthermore, the above-mentioned specific UE capability may be a capability that applies across all frequencies (commonly regardless of frequency), a capability per frequency (e.g., one or a combination thereof, such as cell, band, band combination, BWP, component carrier, etc.), a capability per frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), a capability per subcarrier spacing (SCS), a capability per feature set (FS) or feature set per component-carrier (FSPC), or a capability per functionality / model.

[0460] Furthermore, the specific UE capabilities described above may be capabilities that apply across all duplexing schemes (common to all duplexing schemes regardless of the duplexing scheme), or they may be capabilities specific to each duplexing scheme (e.g., Time Division Duplex (TDD), Frequency Division Duplex (FDD)).

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

[0462] Information regarding 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 set 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 indicated by 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 conditions described / defined in the specification. • The information is determined by a combination of several of the above methods. For example, the information is determined by the setting / indication of higher-layer parameters / MAC CE / DCIs and reported by UE capabilities.

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

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

[0465] (Note) The following inventions are added with respect to one embodiment of the present disclosure. <Note 1> A terminal having a receiving unit that receives a reference signal, and a control unit that determines whether to transmit a first PUCCH in a physical uplink control channel (PUCCH) resource after the first time window if a first event based on the reference signal occurs within a first time window, wherein the control unit cancels the transmission of the first PUCCH if the PUCCH resource overlaps with a specific period after the transmission of a specific signal, or if the transmission of the specific signal overlaps with the first time window. <Note 2> The terminal according to Note 1, wherein the specific period begins from the end of the transmission of the specific signal. <Note 3> The terminal according to Note 1 or Note 2, wherein the specific signal is transmitted based on the occurrence of a second event in a second time window different from the first time window. <Note 4> The terminal according to any one of Notes 1 to 3, wherein the specific signal includes any of the following: a PUCCH other than the first PUCCH, any physical uplink sharing channel (PUCCH), and a PUCCH triggered by a PUCCH within the requested period. <Note A> A base station having a transmitting unit that transmits a reference signal, and a control unit that controls the reception of the first PUCCH in a physical uplink control channel (PUCCH) resource after the first time window if a first event based on the reference signal occurs within the first time window, wherein the transmission of the first PUCCH is canceled if the PUCCH resource overlaps with a specific period after the transmission of the specific signal, or if the transmission of the specific signal overlaps with the first time window.

[0466] <Supplement> The terminal in Appendix 1 to Appendix 4 may be a user terminal 20. The receiving / transmitting unit in Appendix 1 to Appendix 4 may be a transmitting / receiving unit 220. The control unit in Appendix 1 to Appendix 4 may be a control unit 210. The base station in Appendix A may be a base station 10. The receiving / transmitting unit in Appendix A may be a transmitting / receiving unit 120. The control unit in Appendix A may be a control unit 110.

[0467] The UE may receive and measure the RS of a new / current beam [in the RS resource / evaluation opportunity for a new / current beam]. If a first event based on the RS occurs within the first time window (measurement window), the UE may decide whether to transmit a first PUCCH in the 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 one embodiment of this disclosure will be described below. In this wireless communication system, communication is performed using any of the wireless communication methods according to the above embodiments of this disclosure, or a combination thereof.

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

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

[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 where both MN and SN are NR base stations (gNB) (NR-NR Dual Connectivity (NN-DC))).

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

[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 by multiple antennas / base stations 10. One [virtual] cell (which may be called a supercell, for example) may be composed of multiple [virtual] cells (which may be called subcells, for example). A supercell may correspond to a cell with a fixed physical range, and a subcell may correspond to a cell whose physical range fluctuates quasi-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 the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). A macrocell C1 may be included in FR1, and a small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and FR2 may be a frequency band above 24 GHz. Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may be in a frequency band higher than FR2.

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

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

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

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

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

[0482] In the wireless communication system 1, an orthogonal frequency division multiplexing (OFDM)-based wireless access scheme may be used. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-OFDM), etc., may be used in at least one of the downlink (DL) and uplink (UL).

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

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

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

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

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

[0488] Furthermore, the DCI that schedules PDSCH may be called DL assignment, DL DCI, etc., and the DCI that schedules PUSCH may be called UL grant, UL DCI, etc. Furthermore, PDSCH may be read as DL data, and PUSCH may be read as UL data.

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

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

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

[0492] In this disclosure, downlinks, uplinks, etc., may be expressed without the prefix "link." Also, the prefix "physical" may be omitted from the names of various channels.

[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, the DL-RS may include 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.

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

[0495] Furthermore, in the wireless communication system 1, the uplink reference signal (UL-RS) may include a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. The DMRS may also be called a user-specific reference signal (UE-specific Reference Signal).

[0496] (Base Station) Figure 19 shows an example of the configuration of a base station according to one embodiment. The base station 10 includes a control unit 110, a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission line interface 140. Note that one or more of the control unit 110, the transmitting / receiving unit 120, the transmitting / receiving antenna 130, and the transmission line interface 140 may be provided.

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

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

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

[0500] The transmitting / receiving unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transmitting / receiving unit 120 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

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

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

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

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

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

[0506] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform transmission processing on the bit sequence to be transmitted, such as channel coding (which may include error correction coding), modulation, mapping, filtering, discrete Fourier transform (DFT) processing (if necessary), inverse fast Fourier transform (IFFT) processing, precoding, and digital-to-analog conversion, and output a baseband signal.

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

[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 130.

[0509] The transmitting / receiving unit 120 (receiving 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 (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.

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

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

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

[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 implement RF processing (digital beamforming, digital-to-analog conversion, analog beamforming, etc.) and lower-level physical layer functions (precoding, IFFT, FFT, etc.). The DU may implement higher-level physical layer functions (coding to resource element mapping, etc.), MAC layer functions, and RLC layer functions. The CU may implement PDCP layer, Service Data Adaptation Protocol (SDAP) layer, and RRC layer functions.

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

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

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

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

[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 transmitting / receiving unit 220 and the transmitting / receiving antenna 230. The control unit 210 may generate data to be transmitted as signals, control information, sequences, etc., and transfer them to the transmitting / receiving unit 220.

[0519] The transmitting / receiving unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transmitting / receiving unit 220 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

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

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

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

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

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

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

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

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

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

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

[0531] The measurement unit 223 may derive channel measurements for CSI calculation based on channel measurement resources. 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 interference measurement resources. Interference measurement resources may be at least one of the following: NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, etc. CSI-IM may also be called CSI-Interference Management (IM), and may be interpreted interchangeably with Zero Power (ZP) CSI-RS. In this disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc., may be interpreted interchangeably.

[0532] In this disclosure, the transmitting unit and receiving unit of the user terminal 20 may be composed of at least one of a transmitting / receiving unit 220 and a transmitting / receiving antenna 230.

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

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

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

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

[0537] For example, although only one processor 1001 is shown in the diagram, there may be multiple processors. Furthermore, the processing may be performed by one processor, or it may be performed by two or more processors simultaneously, sequentially, or by other means. Note that the processor 1001 may be implemented using 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 the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations and control communication via the communication device 1004, or control at least one of reading and writing data in the memory 1002 and storage 1003.

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

[0540] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly.

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

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

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

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

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

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

[0547] Furthermore, devices included in the core network 30 (for example, network nodes that provide NF) may also be implemented using the functional block / hardware configuration described above.

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

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

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

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

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

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

[0554] For example, one subframe may be called a TTI, multiple consecutive subframes may be called a TTI, and one slot or one mini-slot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe in existing LTE (1 ms), a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing a TTI may be called a slot, mini-slot, 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, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

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

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

[0558] A TTI with a time length of 1 ms may be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc.

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

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

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

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

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

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

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

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

[0567] The structures of wireless frames, subframes, slots, minislots, and symbols described above are merely examples. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless 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, and the number of symbols, symbol length, and cyclic prefix (CP) length within the TTI can be varied in various ways.

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

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

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

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

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

[0573] Any information described in this disclosure (e.g., variables, constants, parameters) may be communicated from any first device (e.g., UE / base station) to any second device (e.g., base station / UE) that indicates / specifies (or relates to) the value of such any information, even if not specifically stated in the embodiments described above.

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

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

[0576] Furthermore, notification of the specified information (for example, notification that "X is the case") is not limited to explicit notification, but may also be made implicitly (for example, by not 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 as true or false, or by a numerical comparison (for example, a comparison with a predetermined value).

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

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

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

[0581] In this disclosure, terms such as “precoding,” “precoder,” “weight (precoding weight),” “quasi-co-location (QCL),” “transmission configuration indication state (TCI state),” “spatial relation,” “spatial domain filter,” “transmit power,” “phase rotation,” “antenna port,” “layer,” “number of layers,” “rank,” “resource,” “resource set,” “beam,” “beam width,” “beam angle,” “antenna,” “antenna element,” “panel,” “UE panel,” “transmitting entity,” and “receiving entity” may be used interchangeably.

[0582] In this disclosure, "antenna port" may be interpreted interchangeably with "antenna port for any signal / channel" (e.g., a Demodulation Reference Signal (DMRS) port). In this disclosure, "resource" may be interpreted interchangeably with "resource for any signal / channel" (e.g., a reference signal resource, an SRS resource, etc.). Resources may include time / frequency / code / spatial / power resources. Furthermore, a spatial domain transmit filter may include at least one of a spatial domain transmit filter and a spatial domain receive filter.

[0583] The above group may include, for example, at least one of the following: 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, or a panel group.

[0584] Furthermore, in this disclosure, terms such as beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, Codeword (CW), Transport Block (TB), and RS may be interpreted interchangeably.

[0585] Furthermore, in this disclosure, 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 interpreted interchangeably.

[0586] Furthermore, in this disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) properties," and "specific QCL type (e.g., Type A, Type D)" may be interpreted interchangeably.

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

[0588] Furthermore, the spatial relationship information Identifier (ID) (TCI state ID) and spatial relationship information (TCI state) may be interpreted as mutually exclusive. "Spatial relationship information (TCI state)" may be interpreted as mutually exclusive as "a set of spatial relationship information (TCI state)," "one or more pieces of spatial relationship information," etc. TCI state and TCI may be interpreted as mutually exclusive. Spatial relationship information and spatial relationship may be interpreted as mutually exclusive.

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

[0590] A base station may house one or more (e.g., three) cells. If a base station houses multiple cells, the entire coverage area of ​​the base station may be divided into several smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0591] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform a control / operation based on said information.

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

[0593] A mobile station may also be called a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other appropriate term.

[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. At least one of the base station and the mobile station may also be a device mounted on a moving object, the moving object itself, etc.

[0595] The term "mobile object" refers to any movable object, regardless of its speed, and naturally includes cases where the mobile object is stationary. Examples of such mobile objects include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and items carried on them. Furthermore, such mobile objects may be autonomously driven objects operating based on operational commands.

[0596] The mobile entity may be a vehicle (e.g., a car, an airplane), an unmanned mobile entity (e.g., a drone, an autonomous vehicle), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication 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] Figure 22 shows an example of a vehicle according to one embodiment. The vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, an axle 48, an electronic control unit 49, various sensors (including a current sensor 50, a rotation speed sensor 51, a pneumatic 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 consists of, for example, at least one of an engine, a motor, or an engine-motor hybrid. 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 consists of a microprocessor 61, memory (ROM, RAM) 62, and communication ports (e.g., input / output (IO) ports) 63. Signals from various sensors 50-58 installed in the vehicle are input to the electronic control unit 49. The electronic control unit 49 may also be called an Electronic Control Unit (ECU).

[0600] Signals from various sensors 50-58 include current signals from current sensor 50 for sensing motor current, rotational speed signals of front wheels 46 / rear wheels 47 acquired by rotational speed sensor 51, air pressure signals of front wheels 46 / rear wheels 47 acquired by air pressure sensor 52, vehicle speed signals acquired by vehicle speed sensor 53, acceleration signals acquired by acceleration sensor 54, accelerator pedal depression amount signals acquired by accelerator pedal sensor 55, brake pedal depression amount signals acquired by brake pedal sensor 56, operation signals of shift lever 45 acquired by shift lever sensor 57, and detection signals acquired by object detection sensor 58 for detecting obstacles, vehicles, pedestrians, etc.

[0601] The information service unit 59 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, display, television, and radio, and one or more ECUs that control these devices. The information service unit 59 uses information acquired from external devices via a communication module 60 or the like to provide various types of 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 that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) or output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.).

[0603] The driver assistance system unit 64 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, 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 Unit (IMU), Inertial Navigation System (INS)), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driver 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 sends and receives data (information) via the communication port 63 to 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, axle 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and various sensors 50-58 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 external devices. For example, it can send and receive various types of information to and from external devices via wireless communication. The communication module 60 may be located either inside or outside the electronic control unit 49. The external device may be, for example, the base station 10 or the user terminal 20 described above. Alternatively, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 (it may function as at least one of the base station 10 and the user terminal 20).

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

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

[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, axle 48, various sensors 50-58, etc., which are provided in the vehicle 40.

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

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

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

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

[0613] Each aspect / embodiment described in this disclosure is Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (where x is, for example, an integer or decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM®), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, systems utilizing Ultra-WideBand (UWB), Bluetooth®, or other appropriate wireless communication methods, and next-generation systems extended, modified, created, or defined based thereon may also be applied. Furthermore, multiple systems may be applied in combination (for example, a combination of LTE or LTE-A and 5G).

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

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

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

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

[0618] Furthermore, “judgment (decision)” may be considered as “judgment (decision)” of resolving, selecting, choosing, establishing, comparing, etc. In other words, “judgment (decision)” may be considered as “judgment (decision)” of some action. In this disclosure, “judgment (decision)” may be interpreted as mutually interchangeable with the actions described above.

[0619] Furthermore, in this disclosure, “determine / determining” may be interpreted as “assume / assuming,” “expect / expecting,” or “consider / considering.” In addition, in this disclosure, “not expecting to do…” may be interpreted as “expecting not to do….”

[0620] In this disclosure, "expect" may be rephrased as "be expected." For example, "expect(s) ..." (where "..." may be expressed as a that clause, an infinitive, etc.) may be rephrased as "be expected ..." or "do (the verb without "to" if "..." is an infinitive)." Similarly, "does not expect ..." may be rephrased as "be not expected ..." or "do not (the verb without "to" if "..." is an infinitive)." Furthermore, "An apparatus A is not expected ..." may be rephrased 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 term "maximum transmit power" as used in this disclosure may mean the maximum transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

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

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

[0624] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

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

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

[0627] In this disclosure, "less than or equal to," "less than," "greater than or equal to," "more than," and "equal to" may be interpreted interchangeably. In addition, in this disclosure, words meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees. In addition, in this disclosure, words meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees, by adding "i-th" (where i is any integer) to the expression (for example, "highest" may be interpreted interchangeably with "i-th highest").

[0628] In this disclosure, "of," "for," "regarding," "related to," and "associated with" may be interpreted as being interchangeable.

[0629] In this disclosure, phrases 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. Furthermore, A, B, etc., may be replaced with appropriate expressions such as nouns, gerunds, or regular sentences depending on the context. The time difference between A and B may be approximately zero (immediately after or immediately before). Additionally, a time offset may be applied to the time when A occurs. For example, "A" may be interpreted as "before / after the time offset when A occurs". The time offset (e.g., one or more symbols / slots) may be predetermined or determined by the UE based on notified information.

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

[0631] Although the invention described herein has been explained in detail above, it will be clear to those skilled in the art that the invention described herein is not limited to the embodiments described herein. The descriptions herein are illustrative and not intended to be restrictive in any way to the invention described herein.

[0632] This application is based on Japanese Patent Application No. 2025-053526, filed on March 27, 2025. All of its contents are included herein.

Claims

1. A terminal comprising: a receiving unit that receives a reference signal; and a control unit that determines whether to transmit a first PUCCH on a physical uplink control channel (PUCCH) resource after the first time window if a first event based on the reference signal occurs within a first time window, wherein the control unit cancels the transmission of the first PUCCH if the PUCCH resource overlaps with a specific period after the transmission of a specific signal, or if the transmission of the specific signal overlaps with the first time window.

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

3. The terminal according to claim 1, 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.

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

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

6. A base station comprising: a transmitting unit that transmits a reference signal; and a control unit that controls the reception of a first PUCCH in a physical uplink control channel (PUCCH) resource after the first time window if a first event based on the reference signal occurs within the first time window, wherein the transmission of the first PUCCH is canceled if the PUCCH resource overlaps with a specific period after the transmission of a specific signal, or if the transmission of the specific signal overlaps with the first time window.

Images