Terminal, radio communication method, and base station

Abstract

To improve communication quality / throughput.SOLUTION: A terminal according to an aspect of the present disclosure has: a control section that determines the order of priority of a first uplink (UL) channel in a first mode in which a response signal to the first UL channel is transmitted and a first UL channel in a second mode in which the response signal is not transmitted, in a beam report started by the terminal; and a transmission section that transmits one of the first UL channel in the first mode and the first UL channel in the second mode, on the basis of the order of priority.SELECTED DRAWING: Figure 2

Description

[Technical Field]

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

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

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

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

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

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

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

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

[0009] A terminal according to one aspect of the present disclosure has a control unit that determines the priority of a first uplink (UL) channel in a first mode in which a response signal to a first UL channel is transmitted, and a first UL channel in a second mode in which the response signal is not transmitted, in a beam report initiated by the terminal, and a transmission unit that transmits either the first UL channel in the first mode or the first UL channel in the second mode based on the priority. [Effects of the Invention]

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

[0011] [Figure 1] Fig. 1A is a diagram showing an example of UE movement in Rel. 17. Fig. 1B is a diagram showing an example of UE movement in Rel. 18. [Figure 2] FIG. 2 is a diagram illustrating an example of a timer / counter related to the UEIBR. [Figure 3] FIG. 3 is a diagram illustrating another example of a timer / counter related to the UEIBR. [Figure 4] FIG. 4 is a diagram illustrating an example of a backward sliding window related to the UEIBR. [Figure 5] FIG. 5 is a diagram illustrating another example of a backward sliding window related to UEIBR. [Figure 6] FIG. 6 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of the configuration of a base station according to an embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of a vehicle according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

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

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

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

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

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

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

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

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

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

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

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

[0023] UEIBR / UE initiated beam management (UEIBM) can be used for measurement reporting / beam switching / cell switching etc.

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

[0025] When a specific event occurs (in this disclosure, it may be read as when specific conditions are met / not met, when it conforms to a specific event, etc.), the UE may report measurement results (for example, at least L1-RSRP / L1-SINR and corresponding resource indicators / RS indexes) to the NW.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0102] <Event instance counter / timer> It is contemplated that in UEIBR / event-triggered beam reporting, a counter / timer (or may be called an evaluation window / time window) will be used to determine / determine the triggering / occurrence of an event.

[0103] The counter / timer may be used for each MIMO / mobility use case. For example, in the case of event-triggered beams for mobility (LTM), the timer may be TTT (time to trigger).

[0104] The UE may count the number of event instances (e.g., measurements that meet the event's entering conditions) and determine / confirm that the event has occurred / triggered / satisfied when the number reaches a certain number.

[0105] The number of event instances may refer to, for example, a count for an event trigger. The counting of the number of event instances may be performed within a timer / time window.

[0106] The counter / timer may be specified in advance in a specification, may be set / indicated using RRC signaling / MAC CE / DCI, or may be determined based on a report of UE capability information.

[0107] Of the above events, it is being considered that for Event 2, the event instance will be counted for each new beam.

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

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

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

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

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

[0113] 2 is a diagram illustrating an example of a timer / counter related to a UEIBR. In the example illustrated in FIG. 2, counting of event instances for determining triggering of an event / UEIBR is performed using a timer and a counter (which may be called a count-up timer).

[0114] In the example shown in Figure 2, when an event instance is satisfied (e.g., when the event's entering condition is met), a timer of a specific length is started, and the timer is restarted each time the event instance is satisfied thereafter (a timer that is already running does not need to be stopped when a timer is started / restarted).

[0115] It should be noted that in the present disclosure, the evaluation window may include a timer and a counter.

[0116] Also, in the present disclosure, at least one of an event being matched, an event being triggered, and an event instance being satisfied may be determined with respect to the current beam [only], with respect to the current beam and one new beam, with respect to the current beam and at least one new beam, or with respect to the current beam and multiple (e.g., all) new beams.

[0117] In the example shown in FIG. 2, if the count number of event instances reaches or exceeds a certain number M (M=3 in the example shown in FIG. 2) within one evaluation window, an event / UEIBR is triggered.

[0118] In the example shown in Figure 2, the timer is reset by the expiration of the timer and the triggering of an event / UEIBR by an event instance in the timer. In the example shown in Figure 2, the timer is also reset when the timer is restarted after the timer is started, but the timer itself continues when the timer is restarted.

[0119] 3 is a diagram showing another example of a timer / counter related to the UEIBR. In the following, only the differences between FIG. 3 and FIG. 2 will be described.

[0120] In the example shown in Figure 3, multiple evaluation windows may overlap. That is, unlike Figure 2, in Figure 3, a timer is not reset when another timer is restarted after the start of that timer (that is, multiple timers may operate overlappingly). When each timer starts, the count of event instances in that timer may be 0.

[0121] In the example shown in Figure 3, an Event / UEIBR is triggered when the count of an Event Instance is greater than or equal to a certain number M (M=3 in the example shown in Figure 3) in an evaluation window. In the example shown in Figure 3, the satisfaction of an Event Instance within evaluation windows starting at T+3, T+4, and T+7 triggers an Event / UEIBR.

[0122] Note that in the example shown in FIG. 3, a timer is reset by the expiration of the timer and the triggering of an event / UEIBR by an event instance within the timer.

[0123] In addition, to determine the triggering of an event / UEIBR, a backward sliding window may be applied / utilized instead of just a count-up timer as described in Figures 2 / 3.

[0124] The backward sliding window evaluates the number of times an event instance is satisfied over a specific period of time from a certain point in time in the past. The backward sliding window may correspond to the time of satisfaction / dissatisfaction of each event instance.

[0125] 4 is a diagram showing an example of a backward sliding window related to a UEIBR. In the example shown in FIG. 4, counting of event instances for determining triggers of an event / UEIBR is performed using a backward sliding window.

[0126] In the example shown in Figure 4, an Event / UEIBR is triggered if the count of the Event Instance is greater than or equal to a certain number M (M=3 in the example shown in Figure 4) within the backward sliding window at the time the Event Instance is satisfied. In the example shown in Figure 4, the Event / UEIBR is triggered by the satisfaction of the Event Instance at times T+4, T+7, and T+11.

[0127] As shown in Figure 4, once an event / UEIBR is triggered, the event instance count and backward sliding window may be reset / cleared / restarted.

[0128] 5 is a diagram showing another example of a backward sliding window related to UEIBR. In the following, only the differences between FIG. 5 and FIG.

[0129] In the example shown in Figure 5, multiple backward sliding windows may overlap. That is, in Figure 5, unlike Figure 4, the backward sliding window (and the count of event instance satisfaction) exists / maintains regardless of event instance satisfaction and event / UEIBR triggering (i.e., multiple backward sliding windows are evaluated simultaneously / overlappingly).

[0130] In the example shown in Figure 5, an Event / UEIBR is triggered when the count number of event instances is equal to or exceeds a certain number M (M=3 in the example shown in Figure 5) in one backward sliding window. In the example shown in Figure 5, an Event / UEIBR is triggered by the satisfaction of event instances in the backward sliding windows corresponding to T+4, T+5, T+7, T+8, T+9, T+10, and T+11.

[0131] Note that in the example shown in FIG. 5, a timer is reset by the expiration of the timer and the triggering of an event / UEIBR by an event instance within the timer.

[0132] As shown in Figure 5, once an event / UEIBR is triggered, the event instance count and backward sliding window are reset / cleared / restarted.

[0133] (analysis) In UEIBR, it is considered that at least one of the following candidate 1 to candidate 6 be specified / introduced as a reset condition for the event evaluation counter. The event evaluation counter may be reset in at least one of the following candidate 1 to candidate 6: Candidate 1: RS reconfiguration / update for new beam is received. · Option 2: The command TCI state is updated [based on the measured current beam] (or the measured current beam based on the command TCI state is updated). Candidate 3: A beam report (second UL channel) related to the UEIBR is transmitted. Candidate 4: A response from the network (e.g., DCI in step 2 of Mode A) is detected. · Candidate 5: The time window expires. · Candidate 6: Thresholds for event evaluation are reconfigured by RRC signaling.

[0134] However, there are cases where sufficient consideration has not been given to the operation of the event-triggered beam report / UEIBR described above.

[0135] <Issue 1> For example, it is conceivable that the minimum counter reset conditions required may differ depending on the implementation method applied to the event evaluation window (e.g., a count-up timer or a backward sliding window), but this has not been sufficiently considered.

[0136] <Issue 2> Also, for example, in order to ensure the validity of event evaluation in the UEIBR, additional / detailed reset conditions to the reset conditions described above need to be considered, but this consideration is insufficient.

[0137] <Issue 3> Also, for example, in the case where an event / UEIBR is triggered and the corresponding transmission of the first UL channel is pending or being retransmitted, the details of processing the triggered state of the event are not sufficiently considered.

[0138] <Issue 4> For example, when a reporting configuration for Mode A and a reporting configuration for Mode B are configured simultaneously for a UE, When different SR (Scheduling Request) IDs are configured for Mode A / B and Mode A / B share the same SR resource, and If a new UCI type is applied to the first UL channel and the first UL channel for Mode A / B shares the same UL channel, In at least one of the above cases, it is necessary to consider collision between the first UL channel for Mode A and the first UL channel for Mode B. Otherwise, the UE cannot determine which first UL channel to transmit. However, this has not been sufficiently considered.

[0139] If these considerations are not sufficient, UEIBR cannot be executed properly, and low-latency communication that takes advantage of the benefits of the beam report cannot be achieved, which may result in suppression of improvements in communication quality / throughput.

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

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

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

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

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

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

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

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

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

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

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

[0151] In this disclosure, the terms panel, UE panel, panel group, beam, beam group, precoder, Uplink (UL) transmitting entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relation, SRS Resource Indicator (SRI), Control Resource Set (CORESET), Physical Downlink Shared Channel (PDSCH), Codeword (CW), Transport Block (TB), Reference Signal (RS), antenna port (e.g., Demodulation Reference Signal (DMRS) port), antenna port group (e.g., DMRS port group), group (e.g., spatial relation group, Code Division Multiplexing (CDM) group, reference signal group, CORESET group, Physical Uplink Control Channel (PUCCH) group, PUCCH resource group), resource (e.g., reference signal resource, SRS resource), resource set (e.g., reference signal resource set), CORESET pool, downlink Transmission Configuration Indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, Quasi-Co-Location (QCL), QCL assumption, etc. may be read as interchangeable.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0183] This disclosure is applicable to mobility / MIMO use cases.

[0184] In the present disclosure, each operation / option may be applied alone or in combination.

[0185] In the present disclosure, each operation / option may be applied in at least one of Case 1 and Case 2 described above.

[0186] In the present disclosure, each operation / option may be applied in at least one of Mode A and Mode B described above.

[0187] In the present disclosure, the number of RS / beam reports [included in a beam report] may include the number of sets of RS indices (e.g., CRI / SSBRI) and corresponding measurement results (e.g., L1-RSRP) included in the beam report, or may include the number of either RS ​​indices or corresponding measurement results.

[0188] <0th embodiment> The zeroth embodiment relates to a count-up timer / backward sliding window for UEIBR.

[0189] The UE may use a specific window to determine the triggering of an event / UEIBR.

[0190] The particular window may be, for example, a count-up timer (timer / evaluation window and counter), in which case the UE may count the satisfaction of the event instance within the timer / evaluation window and determine that the event / UE IBR is triggered when the count is equal to or exceeds a particular number (e.g., M, which may be referred to as a reference number).

[0191] The specific window may be, for example, a backward sliding window, in which case the UE may count the occurrence of an event instance within a specific period (window) from a certain point in time in the past, and determine that an event / UE IBR is triggered if the count is equal to or greater than a specific number (e.g., M, which may be referred to as a reference number).

[0192] This embodiment can be applied to any of the event types described above (for example, events 2 / 7 / 1).

[0193] Furthermore, the application of this embodiment may be applied independently (e.g., separately / differently) to each event type. For example, a method involving a count-up timer may be applied to one event, and a method involving a backward sliding window may be applied to another event.

[0194] Furthermore, the application of this embodiment (for example, the application of embodiment 0-1 / 0-2) may be specified in advance in a specification, may be set / instructed using higher layer signaling / physical layer signaling, may be determined based on a report of UE capability information, or may be determined based on a combination of at least two of these.

[0195] <<Embodiment 0-1>> In embodiment 0-1, a count-up timer will be described.

[0196] Upon satisfaction (occurrence) of an event instance at a particular time, a timer / evaluation window may be started / restarted.

[0197] Parameters related to the timer / evaluation window may be set from the network (NW, for example, a base station).

[0198] The parameter may be, for example, a parameter relating to at least one of the (time) width of the window, the reference number M, and the maximum number of windows that are allowed to overlap.

[0199] While the timer / evaluation window is running, a count of the number of (satisfaction of) the event instances may be continued.

[0200] When the timer / evaluation window is started, the count number / counter may be initialized to 0.

[0201] Each time an event instance is satisfied, a counter corresponding to the timer / evaluation window may be incremented by one.

[0202] When the counter is incremented, the timer may be restarted (eg, Figure 2 / Figure 3 above).

[0203] The event / UEIBR may be triggered, for example, at least one of the following times: when the count number in one timer / evaluation window becomes equal to or exceeds a reference number M; and when the timer / evaluation window expires.

[0204] The evaluation window may be reset / cleared at least one of the following times: when a timer expires, when an event / UEIBR is triggered, and when a specific reset condition is met.

[0205] The specific reset conditions will be described in detail in the second and third embodiments below.

[0206] <<Embodiment 0-2>> In embodiment 0-2, a backward sliding window (hereinafter, may be simply referred to as a window or an evaluation window) will be described.

[0207] At certain periodic times, an evaluation of the number of (satisfaction of) event instances within a window may be performed.

[0208] Parameters related to the window / evaluation window may be set from the NW.

[0209] The parameter may be, for example, a parameter relating to at least one of a period relating to the window, a (time) width of the window, and a reference number M.

[0210] The period for the window may be the same as or different from the evaluation period for the event instance, for example.

[0211] At a specific evaluation timing, the number of event instances (satisfied) may be counted by tracing back to the evaluation timing of the event instance for a length equivalent to the width of the window.

[0212] For example, if the count number in the window is greater than or equal to a reference number M, an event / UEIBR may be triggered.

[0213] Evaluations / event instances stored outside the window of event evaluation may be cleared.

[0214] Once an event / UEIBR is triggered (as shown in Figure 4 above), the event instance count and backward sliding window may be reset / cleared / restarted.

[0215] Additionally, (as shown in Figure 5 above) the backward sliding window (and event instance satisfaction count) may exist / maintain regardless of event instance satisfaction and event / UEIBR triggering (i.e., event instance satisfaction may be evaluated simultaneously / overlappingly for multiple backward sliding windows).

[0216] According to the above-described 0th embodiment, it is possible to appropriately define a counter / timer / window for evaluating an event / UEIBR trigger.

[0217] First Embodiment The first embodiment relates to the reset conditions of counters for the implementation of a window for event evaluation.

[0218] Depending on the implementation method / type of the window for event evaluation (eg, applying either a count-up timer or a backward sliding window), the reset conditions for the applicable counter may be determined.

[0219] The UE may determine / determine / assume the reset conditions for applicable counters based on the implementation method / type of the window for event evaluation (e.g., applying either a count-up timer or a backward sliding window).

[0220] For example, depending on the implementation method / type of window for event evaluation (e.g., applying either a count-up timer or a backward sliding window), the reset conditions of the applicable counters may be the same or different.

[0221] For example, the UE may determine / determine / assume that the reset conditions for applicable counters are the same / different based on the implementation method / type of the window for event evaluation (e.g., application of either a count-up timer or a backward sliding window).

[0222] For example, if a count-up timer is applied to the event evaluation, the reset condition of the applicable counter may be at least one of the above candidates 1, 2, and 5.

[0223] In this case, resetting the counter (based on a reset condition) may mean that the count value corresponding to the event's evaluation window is set to 0, and the evaluation window is ended.

[0224] For example, if a backward sliding window is applied to event evaluation, the reset condition for the applicable counter may be at least one of the above candidates 1 and 2.

[0225] In this case, resetting the counter (based on the reset condition) may mean clearing evaluation instances (event instances that are determined to be satisfied / not satisfied) that are saved before the reset timing.

[0226] According to the first embodiment described above, it is possible to define an appropriate counter reset condition in accordance with the implementation method of the window related to event evaluation, which can contribute to solving the above-mentioned issue 1.

[0227] <Second embodiment> The second embodiment relates to additional / detailed counter reset conditions.

[0228] Instead of / in addition to at least one of the above candidates 1 to 6, at least one of the following additional candidates 1 to 4 may be added to the counter reset conditions. The event evaluation counter may be reset in at least one of the following additional candidates 1 to 6: · Additional candidate 1: UEIBR is triggered by the corresponding counter in the window. · Additional candidate 2: The first UL channel triggered by the corresponding counter in the window is transmitted. Additional candidate 3: UEIBR (second UL channel) is transmitted. Additional candidate 4: A response from the network (e.g., signaling equivalent to an ACK for the second UL channel) is detected.

[0229] In the case of additional candidate 1, the reset operation may be performed regardless of whether the first UL channel corresponding to this triggering operation is transmitted or not.

[0230] In the case of additional candidate 2, the reset operation may be performed after the first UL channel corresponding to this trigger operation is transmitted (or after the transmission of the first UL channel is confirmed).

[0231] In the case of the above candidate 4, the reset operation may be executed after it is confirmed that the first UL channel corresponding to this trigger operation has been normally received in the NW.

[0232] In the case of additional candidate 3, the reset operation may be performed after the second UL channel corresponding to this trigger operation is transmitted (or after the transmission of the second UL channel is confirmed).

[0233] In the case of additional candidate 4, the reset operation may be performed after confirming that the second UL channel corresponding to this trigger operation has been successfully received in the NW (i.e., that all corresponding UEIBR procedures have been completed).

[0234] At least one of the above candidates 1 to 6 and additional candidates 1 to 4 may be applied as a window reset condition.

[0235] The reset timing of the counter and the reset timing of the timer / window may be the same timing or may be different timings.

[0236] In addition, for the application of at least one of the above candidates 1 to 6 and additional candidates 1 to 4, the timer / counter of the new beam that satisfies the trigger condition may be reset [only].

[0237] In addition, for the application of at least one of the above candidates 1 to 6 and additional candidates 1 to 4, the timers / counters of multiple (e.g., all) new beams may be reset.

[0238] According to the second embodiment described above, it is possible to guarantee the validity of event evaluation in the UEIBR, which can contribute to solving the above-mentioned Issue 2.

[0239] <Third embodiment> The third embodiment relates to handling of event trigger conditions.

[0240] The UE may trigger an event / UEIBR based on evaluation of the event instance / event.

[0241] The UE may suspend transmission of the first UL channel related to the triggered event / UE IBR [due to a specific reason (e.g., due to at least one of an error in transmission of the first UL channel and contention for UL resources)], and then wait for an opportunity to retransmit the first UL channel.

[0242] In this case, the UE may perform at least one of the operations in the following embodiments 3-1 and 3-2.

[0243] <<Embodiment 3-1>> The UE may indicate / hold information indicating that "an event is triggered by the result of the evaluation and waits for the next transmission (opportunity) of the first UL channel."

[0244] <<<Embodiment 3-1-1>>> The UE may indicate this information by continuing to count even if the number of (satisfied) event instances exceeds the criterion number M.

[0245] In this case, for example, the UE may confirm that transmission of the first UL channel corresponding to the first event trigger has been completed and / or that the NW has correctly received the first UL channel, and may reset the counter / timer (for example, the above candidate 4 / additional candidates 2 / 3 / 4 may be applied).

[0246] If the counter / timer is reset before the next transmission opportunity for the first UL channel, the first UL channel corresponding to the event trigger that was pending transmission may not be transmitted.

[0247] According to embodiment 3-1-1, as long as the counter number is equal to or greater than the reference number M, it is possible to confirm that the trigger condition has been met once but the first UL channel has not yet been transmitted / retransmitted.

[0248] For UEIBRs where multiple CC / event / reporting configurations are used, the counter value may be used as a priority metric for the transmission of the first UL channel. A larger counter value is considered to indicate a larger air time or a more frequent satisfaction of the event instance.

[0249] <<Embodiment 3-1-2>> The UE may indicate a "new" indicator to indicate that the first UL channel is in a pending / retransmission state.

[0250] In this case, for example, the UE may reset the counter / timer upon an event trigger regardless of whether the first UL channel is transmitted / retransmitted (for example, the above candidate 3 / 4 / additional candidate 1 / 2 / 3 / 4 may apply).

[0251] When the first UL channel corresponding to the first event trigger has been transmitted and / or the first UL channel has been correctly received by the network, the indicator may be set to an initial value, which may indicate, for example, that the first UL channel is not in a waiting / retransmission state.

[0252] <<Embodiment 3-2>> The UE may not take into consideration information indicating that "an event is triggered by the result of the evaluation, and the UE waits for the next transmission (opportunity) of the first UL channel."

[0253] For example, the UE may not indicate / hold information indicating that "an event is triggered by the result of the evaluation, and the UE waits for the next transmission (opportunity) of the first UL channel."

[0254] The UE may not transmit the first UL channel corresponding to the event trigger that was pending transmission if the counter / timer is reset before the next transmission opportunity for the first UL channel.

[0255] A new window is started without considering the waiting state and if the trigger condition is met again, the transmission procedure for the first UL channel may be initiated.

[0256] According to the third embodiment described above, even when the first UL channel is in a transmission waiting / retransmission state, appropriate handling can be performed, and this can be used to resolve the above issue 3.

[0257] <Fourth embodiment> The fourth embodiment relates to the priority of the first UL channel between the modes.

[0258] The reporting configuration for Mode A and the reporting configuration for Mode B may be configured for the UE at the same time.

[0259] Different SR IDs may be configured for Mode A / B, and the same SR resources may be shared in Mode A / B.

[0260] A new UCI type may be applied to the first UL channel, and the first UL channel for Mode A / B may share the same UL channel.

[0261] Alternatively, the UE may not assume / expect that the same UL resources are configured for the first UL channel for Mode A and the first UL channel for Mode B.

[0262] The UE / NW may determine whether to transmit the first UL channel for Mode A or the first UL channel for Mode B based on a priority rule between each first UL channel / each mode.

[0263] In this way, based on the priority rule, it is possible to appropriately determine the first UL channel to be transmitted.

[0264] For example, the priority of the first UL channel for Mode A may be higher (or lower) than the priority of the first UL channel for Mode B.

[0265] In the case of a UEIBR where multiple CCs / events / reporting settings are used, the priority may be determined separately for each CC / event / reporting setting.

[0266] Also, in the case of a UEIBR where multiple CC / event / reporting settings are used, priority may be set for a specific CC / event / reporting setting, and the settings for that specific CC / event / reporting setting may be applied to other CC / event / reporting settings.

[0267] The priority rules may be specified in advance, may be set / indicated using higher layer signaling / physical layer signaling, may be determined based on reports of UE capability information, or may be determined based on a combination of at least two of these.

[0268] The UE / NW may also process the UE-IBR procedure assuming that one mode is configured, for example, Mode A or Mode B. This allows the UE to properly transmit the first UL channel.

[0269] According to the above-described fourth embodiment, the transmission of the first UL channel can be appropriately performed, which can contribute to the solution of the above issue 4.

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

[0271] When the above notification is performed by MAC CE, the MAC CE may be identified by including a new logical channel ID (Logical Channel ID (LCID)) that is not defined in the existing standard in the MAC sub-header.

[0272] When the above notification is performed by DCI, the above notification may be performed by a specific field of the DCI, a radio network temporary identifier (Radio Network Temporary Identifier (RNTI)) used for scrambling the cyclic redundancy check (Cyclic Redundancy Check (CRC)) bits assigned to the DCI, the format of the DCI, etc.

[0273] Also, the notification of any information to the UE in the above-described embodiment may be performed periodically, semi-persistently, or aperiodically.

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

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

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

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

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

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

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

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

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

[0283] (Addendum) The following inventions are added regarding one embodiment of the present disclosure. [Appendix 1] A terminal having a control unit that determines a reset condition for a counter of an event instance based on a window type for evaluation of a beam report event initiated by the terminal, and triggers the beam report based on the reset condition, and a transmitting unit that transmits the triggered beam report. [Appendix 2] A terminal having a control unit that determines the priority of a first uplink (UL) channel in a first mode in which a response signal to a first UL channel is transmitted, and a first UL channel in a second mode in which the response signal is not transmitted, in a beam report initiated by the terminal, and a transmission unit that transmits either the first UL channel in the first mode or the first UL channel in the second mode based on the priority.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0331] The control unit 110 may determine a reset condition for the counter of the event instance based on the type of window for evaluation of the beam report event initiated by the terminal. The transceiver unit 120 may receive the beam report triggered based on the reset condition (first, second, or third embodiment).

[0332] The control unit 110 may determine a priority between a first uplink (UL) channel in a first mode in which a response signal to a first UL channel is transmitted and a first UL channel in a second mode in which the response signal is not transmitted in a beam report initiated by the terminal. The transceiver unit 120 may receive either the first UL channel in the first mode or the first UL channel in the second mode based on the priority (fourth embodiment).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0351] The control unit 210 may determine a reset condition for the counter of the event instance based on the type of window for evaluation of the beam report event initiated by the terminal, and may trigger the beam report based on the reset condition. The transceiver unit 220 may transmit the triggered beam report (first, second, or third embodiment).

[0352] The control unit 210 may determine a priority between a first uplink (UL) channel in a first mode in which a response signal to a first UL channel is transmitted and a first UL channel in a second mode in which the response signal is not transmitted in a beam report initiated by the terminal. The transceiver unit 220 may transmit either the first UL channel in the first mode or the first UL channel in the second mode based on the priority (fourth embodiment).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. a control unit that determines a priority of a first uplink (UL) channel in a first mode in which a response signal to a first UL channel is transmitted and a first UL channel in a second mode in which the response signal is not transmitted in a beam report initiated by a terminal; a transmitter configured to transmit either the first UL channel in the first mode or the first UL channel in the second mode based on the priority.

2. determining a priority of a first uplink (UL) channel in a first mode in which a response signal for a first UL channel is transmitted and a priority of a first UL channel in a second mode in which the response signal is not transmitted in a beam report initiated by the terminal; transmitting either the first UL channel in the first mode or the first UL channel in the second mode based on the priority.

3. a control unit that determines a priority of a first uplink (UL) channel in a first mode in which a response signal to a first UL channel is transmitted and a first UL channel in a second mode in which the response signal is not transmitted in a beam report initiated by a terminal; a receiving unit configured to receive either the first UL channel in the first mode or the first UL channel in the second mode based on the priority.

Images