Terminal, wireless communication method, and base station

Abstract

One aspect of the present disclosure is a terminal that has a reception unit that receives first setting information related to event-based beam reporting and a control unit that evaluates an event on the basis of the first setting information and controls the event-based beam reporting when there is a beam that satisfies the event. The control unit performs control such that the first setting information used for evaluation of the event is reset on the basis of at least one of the reception timing of specific information, the transmission timing of specific information, and the timing at which a specific procedure is completed.

Description

Terminal, wireless communication method and base station

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

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

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

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

[0005] In future wireless communication systems (e.g., NR, Rel. 19 and later), it is being considered to support a beam report initiated by a terminal (user terminal, User Equipment (UE)) (UE-initiated Beam Report (UEIBR)). UEIBR may also be called a UE-initiated beam report / event-based beam report.

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

[0007] However, there are cases where sufficient consideration is not given to how to control UE-initiated / event-based beam reporting. If this consideration is not given sufficiently, the UE-initiated / event-based beam reporting may not be performed appropriately, which may result in suppression of improvement in communication quality / throughput.

[0008] Therefore, one of the objectives of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately control UE-initiated / event-based beam reporting.

[0009] A terminal according to one aspect of the present disclosure has a receiving unit that receives first setting information regarding an event-based beam report, and a control unit that evaluates an event based on the first setting information and controls the event-based beam report when a beam that satisfies the event exists, and the control unit controls to reset the first setting information used to evaluate the event based on at least one of the timing of receiving specific information, the timing of transmitting specific information, and the timing of completing a specific procedure.

[0010] According to one aspect of the present disclosure, UE-initiated / event-based beam reporting can be appropriately controlled.

[0011] Figure 1A is a diagram showing an example of UE movement in Rel. 17. Figure 1B is a diagram showing an example of UE movement in Rel. 18. Figure 2 is a diagram showing an example of RS configuration for a new beam. Figures 3A and 3B are diagrams showing an example of resource configuration for a first UL channel and a second UL channel. Figures 4A and 4B are diagrams showing an example of resource configuration for a first UL channel and a second UL channel. Figures 5A and 5B are diagrams showing an example of the size of a beam report using resources of a second UL channel in which common resources are configured for multiple CCs according to the first embodiment. Figures 6A and 6B are diagrams showing an example of CCs transmitted in resources of a first UL channel in which common resources are configured for multiple CCs according to the second embodiment. Figures 7A and 7B are diagrams showing another example of CCs transmitted in resources of a first UL channel in which common resources are configured for multiple CCs according to the second embodiment. 8A and 8B are diagrams showing an example of CCs transmitted using resources of a second UL channel in which common resources are configured for multiple CCs according to the second embodiment. FIG. 9 is a diagram showing an example of a case in which event evaluation based on predetermined setting information according to the third embodiment is reset / stopped / cancelled based on predetermined timing. FIG. 10 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 11 is a diagram showing an example of a configuration of a base station according to an embodiment. FIG. 12 is a diagram showing an example of a configuration of a user terminal according to an embodiment. FIG. 13 is a diagram showing an example of hardware configurations of a base station and a user terminal according to an embodiment. FIG. 14 is a diagram showing an example of a vehicle according to an embodiment.

[0012] (L1 / L2 Inter-Cell Mobility) A 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, a serving cell may be interpreted as a TRP in the serving cell. Layer 1 / layer 2 (L1 / L2) and DCI / Medium Access Control Control Element (MAC CE) may be interpreted as interchangeable. In the present disclosure, a physical cell identity (PCI) different from the physical cell identity (PCI) of the current serving cell may be simply referred to as a "different PCI." A non-serving cell, a cell having a different PCI, and an additional cell may be interpreted as interchangeable.

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

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

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

[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 serving cells 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, such as by handover (also called 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, which results in a period when data communication is unavailable, by applying L1 / L2 inter-cell mobility that does not require handover, data communication can be continued even when the serving cell is changed. Scenario 2 may be applied, for example, in Rel. 18. In scenario 2, for example, the following procedure is performed.

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

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

[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] (Beam Report Types) <Intra-cell beam reporting in Rel. 15 / 16> In Rel. 15 / 16, intra-cell beam reporting is supported. For example, L1-RSRP / SINR reporting can be configured by higher layer signaling (RRC).

[0023] For example, in calculating the L1-RSRP, the UE may be configured with either or both of the CSI-RS resource and the SS / PBCH block resource if the resource is associated with QCL Type C / Type D.

[0024] A UE may also be configured with up to 16 CSI-RS resource sets, with a maximum of 64 resources in each set, and the total number of different CSI-RS resources across all resource sets may not exceed 128.

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

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

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

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

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

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

[0031] If the higher layer parameter nrofReportedRS is set to be greater than 1, or if the higher layer parameter groupBasedBeamReporting is set to "enabled", the UE uses the differential value-based L1-SINR value for reporting.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0047] (Event-Based Beam Reporting) It is being considered that future wireless communication systems will support event-based beam reporting. Event-based beam reporting may also be called event-triggered beam reporting, and may mean UE-initiated beam reporting.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0073] (Events / Containers for UEIBR) In Rel. 19 and later, support for event-based beam reporting (UE-initiated beam reporting (UEIBR)) / UE-initiated beam management (UEIBM) is being considered. UEIBR / UEIBM can be used for measurement reporting, beam switching, cell switching, etc.

[0074] In UEIBR, it is considered that the beam report includes at least one of the following information as report content: Beam / reference signal index (e.g., CSI-RS / SSB resource index / indicator) Measurement result (e.g., L1-RSRP / SINR (absolute value / relative value)) Number of beams / RSs to be reported Whether the serving beam is included in the beam report.

[0075] Regarding the information regarding the number of beams / RSs to be reported, since the base station / network and the UE need to have a common understanding of the size of the beam report (e.g., UCI), it is preferable that this information be included in the beam report reported from the UE.

[0076] In this case, the UCI may be reported in two parts, for example, the UCI (which may have a fixed size) transmitted in the first part (step) may indicate the size (e.g., the number of beams) of the UCI transmitted in the second part (step).

[0077] In this case, the UCI may be coded in two parts, for example, the size of the second part of the UCI may be indicated by the first part of the UCI (which may have a fixed size).

[0078] Events related to UEIBR (the events mentioned above) 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 becomes better than a certain threshold. Event 4: The quality of the current beam becomes worse than a first threshold and the quality of at least one new beam becomes better than a second threshold. Event 5: The absolute value of the difference between the quality of the current beam and the quality of at least one new beam becomes smaller than a certain threshold. Event 6: The current beam is no longer included in the best K (greater than 1: K>1) beams (among the beams configured for measurement / reporting). Event 7a: The quality of at least one new beam (e.g., L1-RSRP) becomes a threshold better than the RS derived from the activated (active) TCI state with the worst quality. Event 7b: The quality (e.g., L1-RSRP) of at least one new beam reaches a threshold better than the RS derived from the best quality activated (active) TCI state. Event 8: The quality (e.g., L1-RSRP) of M (more than 1: M>1) new beams reaches a threshold better than the current beam. Event 9: The quality (e.g., L1-RSRP) of at least one new beam reaches a threshold better than the configured reference RS (which may be SSB / CSI-RS).

[0079] It should be noted that such event types do not exclude the events described above. For example, such event types may be appropriately interpreted as the events described above.

[0080] (Beam / UCI Format / RS Configuration in UEIBR) In addition, in a specific event (e.g., Event 2), the "current beam" may be determined / derived based on the QCL RS (e.g., QCL source RS) of the indicated TCI state. In this case, the QCL RS of the indicated TCI state may support at least one of SSB and CSI-RS.

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

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

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

[0084] Additionally, for beam reports (UCI format) for specific events (e.g., Event 2), it is being considered to make the beam reports variable size / fixed size.

[0085] For example, support for the following format options 1 / 1a / 1b / 2 / 3 for the UCI format is being considered: Format option 1: The UCI size is variable, and N beams are reported in one reporting instance (N is 1 to N ｍａｘ ). N beams satisfy the condition of Event 2. The maximum number of N (N ｍａｘ ) is set by the base station. Format option 1a: UCI size is variable and N beams are reported in one reporting instance (N is 1 to N ｍａｘ ). At least one beam of the N reported beams satisfies the condition of Event 2. The maximum number of N (N ｍａｘ ) is set by the base station. Format option 1b: UCI size is fixed (independent of N), and N beams are reported in one reporting instance (N ranges from 1 to N ｍａｘ ). N reported beams satisfy the condition of Event 2. The maximum number of N (N ｍａｘ ) is configured by the base station. Format option 2: The UCI size is fixed and one beam is reported in one reporting instance. The reported beam satisfies the condition of event 2. Format option 3: The UCI size is fixed and N beams are reported in one reporting instance (N is a number greater than 1). At least one beam of the N reported beams satisfies the condition of event 2. N is configured by the base station.

[0086] Note that the above format options are merely examples, and options other than these may also be supported.

[0087] For N beams in format option 3 above (eg, dependent on event 2), a method for reporting on the "current beam" is being considered.

[0088] For example, whether or not the UE should [always] report the current beam in the beam report may be configured / enabled / disabled using RRC signaling.

[0089] For example, when the RRC signaling sets the enablement, the current beam and N beams based on RS measurements for the new beam may be reported, where the N beams may or may not include the current beam.

[0090] For example, if the disablement is configured by the RRC signaling, N beams based on RS measurements for the new beam may be reported.

[0091] RS configuration for a new beam for event 2 is being considered. At least one of the following configuration options 1 to 3 may be supported for the RS configuration method: RS configuration option 1: RS for the new beam is explicitly configured in one RS resource set associated with the CSI reporting configuration. RS configuration option 2: A list of RSs for new beam measurements is configured using RRC signaling, and a subset of the list is activated for new beam measurements using MAC CE. RS configuration option 3: A list of RS resources for new beam measurements is configured using RRC signaling, and a subset of the list is provided for new beam measurements by the indicated TCI state.

[0092] 2 is a diagram showing an example of RS configuration for a new beam. In the example shown in FIG. 2, a CSI resource configuration (CSI-ResourceConfig) is included in a CSI report configuration (CSI-ReportConfig), and the CSI resource configuration includes a CSI resource set list. Furthermore, the CSI resource set list includes (CSI) resource sets #0 to #M, of which resource set #0 includes RSs #0 to #N as CSI-RS resources.

[0093] In the example shown in Fig. 2, in RS configuration option 1, an RS for a new beam is configured in one RS resource set associated with one CSI reporting configuration. Note that in RS configuration option 1, a MAC CE may be used to update the RS.

[0094] In the example shown in Fig. 2, in RS configuration option 2, a list of RSs for a new beam is configured using RRC signaling, and a part of the list (RSs #0 and #1 in the example of Fig. 2) is activated for new beam measurement using MAC CE. That is, in RS configuration option 2, MAC CE may be used to activate RSs.

[0095] In the example shown in Fig. 2, in RS configuration option 3, a list of RS resources (multiple RS resource sets) for the new beam is configured using RRC signaling, and a subset of the list is provided for new beam measurement by the indicated TCI state. The selection rule for the RS resource set in this case needs to be considered.

[0096] The advantage of RS configuration option 1 is that it is simple to implement and can follow the existing CSI framework. However, there are concerns that it increases the load on the UE in measurements and requires separate RS resource configuration for UE IBR execution. This disadvantage can be resolved by using multiple events for one CSI resource set.

[0097] RS configuration option 2 can reduce the load on the UE in terms of measurements, and for example, enables the execution of UE IBR by activation by MAC CE. On the other hand, there is a concern that such MAC CE needs to be specified and that RSs activated by the NW need to be selected.

[0098] RS Configuration Option 3 can reduce the UE load when the number of RSs included in the CSI resource set is small, and UE IBR can be performed using different resource sets depending on the indicated TCI state. On the other hand, it is necessary to define new rules for identifying the subset of RS resources in the CSI resource set, and there is a concern that the UE measurement load will depend on the size of the CSI resource set.

[0099] Although the above description has been given mainly with respect to Event 2 as an example, the same applies to any other event.

[0100] By utilizing such UEIBR / UEIBM, delay and UL resource overhead can be reduced compared to existing beam reporting.

[0101] (Beam report transmission procedure for UE-initiated / event-based beam reporting) In the beam report transmission procedure for UE-initiated / event-based beam reporting, the following modes may be supported.

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

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

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

[0105] Step 3: The UE transmits the beam report using resources (UCI) on a second UL channel, which may be a PUCCH / PUSCH.

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

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

[0108] The DCI format in step 2 may be configured with a DCI format corresponding to an UL grant, and the second UL channel in step 3 may be configured with at least a PUSCH. Alternatively, the DCI format in step 2 may be configured with a DCI format corresponding to a DL grant, and the second UL channel in step 3 may be configured with at least a PUCCH. In the DCI format of the DL grant, a field (e.g., a 1-bit field) for indicating transmission of a UE IBR may be introduced. The PUCCH resource for HARQ-ACK transmission (e.g., HARQ-ACK corresponding to the DCI of the DL grant) may be applied to transmission of both the HARQ-ACK and the beam report.

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

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

[0111] Step 2: The UE transmits a beam report in a second UL channel (e.g., using a specific resource in the channel (UCI)), which may be a PUCCH / PUSCH.

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

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

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

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

[0116] (Analysis) As described above, it is expected that UE-initiated / event-based beam reporting will be supported in MIMO / mobility after Rel. 19. However, there are cases where sufficient consideration has not been given to how to control UE-initiated / event-based beam reporting.

[0117] For example, it is assumed that multiple CCs / candidate cells are configured for UE-initiated / event-based beam reporting (UEIBR). In this case, when multiple CCs / candidate cells simultaneously satisfy a predetermined condition / event, how to control beam reporting (e.g., beam measurement report / RS index report) becomes an issue.

[0118] Therefore, the inventors focused on cases where multiple CCs / candidate cells are configured for UE-initiated / event-based beam reporting (UEIBR), studied beam reporting in such cases, and came up with one aspect of this embodiment.

[0119] Alternatively, in UE-initiated / event-based beam reporting (UEIBR), the question arises as to how to control the switching / updating of event evaluation.

[0120] Therefore, the inventors studied switching / updating of event evaluation in UE-initiated / event-based beam reporting (UEIBR) and came up with one aspect of this embodiment.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0142] In the present disclosure, ACK may be referred to as a positive response, and NACK may be referred to as a negative response. In the present disclosure, NACK may be information indicating a first value (e.g., 0 (or 1)), and ACK may be information indicating a second value (e.g., 1 (or 0)).

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

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

[0145] In this disclosure, the pair of RS index and L1-RSRP / SINR may be referred to as an L1 measurement report, i.e., the L1 measurement report may include the pair of RS index and L1-RSRP / SINR.

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

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

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

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

[0150] In the present disclosure, the spatial domain filter, the time domain filter, and the domain filter may be read interchangeably.

[0151] In the present disclosure, the current beam / new beam may correspond to at least one of an indicated TCI state, an indicated TCI state, an active TCI state, an activated TCI state, a configured TCI state, a configured TCI state, and an RS configured in RRC.

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

[0153] In the present disclosure, the number of current beams / new beams may be one or more.

[0154] In the present disclosure, new beam / RS, candidate beam / RS, measurement beam / RS, measurement beam / RS, etc. may be read interchangeably.

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

[0156] In the present disclosure, L1-RSRP may be interchangeably read as L1-SINR.

[0157] In the present disclosure, the terms condition and threshold may be interpreted as interchangeable.

[0158] In the present disclosure, the filtered value (measured value: L1-RSRP), the filter value, and the L1-RSRP to which filtering by NW settings has been applied (NW-filtered L1-RSRP) may be read interchangeably.

[0159] In the present disclosure, CC, carrier, cell, serving cell, frequency, frequency carrier, carrier frequency, etc. may be read interchangeably.

[0160] In the present disclosure, reporting a (current / measured) beam may mean reporting an RS index (e.g., CSI-RS resource indicator (CRI) / SSB resource indicator (SSBRI)) and measurement results (e.g., L1-RSRP / RSRQ / SINR) (corresponding to the (current / measured) beam). In the present disclosure, information about a beam may mean the RS index / measurement results (corresponding to the beam).

[0161] In this disclosure, "current beam" may mean "current beam of the current serving cell" in mobility.

[0162] In the present disclosure, the terms beam, RS, RS resource, RS resource set, RS index, RS indicator, RS ID, etc. may be interchangeable. In the present disclosure, the terms RS resource set, RS resource subset, RS subset, etc. may be interchangeable.

[0163] (Wireless communication method) One CC (single CC) may be configured for UE-initiated / event-based beam reporting (UEIBR), or multiple CCs may be configured. CC may be read as a candidate cell.

[0164] When multiple CCs are configured for UE-initiated / event-based beam reporting (UEIBR), it is also assumed that multiple CCs (or beams / reference signals in multiple CCs) simultaneously satisfy a predetermined condition / event. In such a case, the beam report (e.g., measurement result / RS index / beam report) may be controlled based on at least one of the following cases 1 and 2.

[0165] <Case 1> It may be supported that measurement results / reference signal indices (RS indices) of multiple CCs are included in one report instance. In the present disclosure, the RS index and the beam (or the beam index) may be interchangeable.

[0166] For example, one CSI reporting configuration (CSI-ReportConfig) may be configured for multiple target CCs. The multiple target CCs (or CSI reporting configuration) may be configured under a serving cell configuration (ServingCellConfig) of a specific cell (e.g., SpCell). Multiple CSI resource configurations / sets (CSI-ResourceConfig / Set) may be associated with one CSI reporting configuration (CSI-ReportConfig).

[0167] In case 1 UE-initiated / event-based beam reporting (UEIBR), when at least one of the first UL channel and the second UL channel in the above-mentioned Mode A / Mode B is applied, the resource configuration of the first UL channel and the resource configuration of the second UL channel may be configured as follows.

[0168] [First UL Channel] In resource configuration of the first UL channel, at least one of the following options 1 and 2 may be applied / supported. A common option may be applied to Mode A and Mode B, or different options may be applied.

[0169] <<Option 1>> A common resource (e.g., a common resource) may be configured for multiple target CCs. For example, the network (base station) may configure multiple target CCs for the UE and configure common UL channel resources for the multiple CCs.

[0170] <<Option 2>> Separate resources can be configured for each CC. For example, the network (base station) may configure multiple target CCs for the UE and configure separate UL channel resources for each of the multiple CCs.

[0171] [Second UL Channel] In resource configuration of the second UL channel, the following option 3 may be applied / supported.

[0172] <<Option 3>> A common resource (for example, a common resource) may be configured for multiple target CCs. For example, the network (base station) may configure a common UL channel resource for multiple CCs.

[0173] In Case 1, the payload size of the second UL channel may be variable (or have different configurations) depending on the number of CCs (or the number of beams per CC (the number of RS resources corresponding to each CC)) that satisfy a predetermined condition / event. For example, if the number of CCs is L and the number of beams per CC (or the number of RS resources corresponding to each CC) is N, L×N beams (or RS resources) may be reported. The UE may notify the network of the payload size by using bits (e.g., multi-bits) of the first UL channel / part of the CSI (e.g., two-part CSI) of the second UL channel.

[0174] A CC ID / cell ID may be required to identify a CC for each beam / RS resource (or a mapping between beams / RS resources and CCs). If it is necessary to include a current beam in a report (or a report instance), L beams may be added in addition to the L×N beams in the report (L×(N+1) beams). Alternatively, in addition to the L×N beams, only the current beam of a specific cell (e.g., SpCell) may be included in the report (or report instance).

[0175] <Case 2> A configuration may be adopted in which a measurement result / reference signal index (RS index) of a single CC is included in one report instance.

[0176] For example, one CSI reporting configuration (CSI-ReportConfig) may be configured for one CC (single CC). The one CC (or CSI reporting configuration) may be configured under each serving cell configuration (ServingCellConfig). One CSI-ResourceConfig / Set may be associated with one CSI reporting configuration (One CSI-ReportConfig).

[0177] As another example, one CSI reporting configuration (CSI-ReportConfig) may be configured for multiple target CCs. The multiple target CCs (or CSI reporting configurations) may be configured under a serving cell configuration (ServingCellConfig) of a specific cell (e.g., SpCell). A CSI resource configuration / set (CSI-ResourceConfig / Set) for each CC may be associated with one CSI reporting configuration (CSI-ReportConfig).

[0178] In case 2 UE-initiated / event-based beam reporting (UEIBR), when at least one of the first UL channel and the second UL channel in the above-mentioned Mode A / Mode B is applied, the resource configuration of the first UL channel and the resource configuration of the second UL channel may be configured as follows.

[0179] [First UL Channel] In resource configuration of the first UL channel, at least one of the following options 1 and 2 may be applied / supported. A common option may be applied to Mode A and Mode B, or different options may be applied.

[0180] <<Option 1>> A common resource (e.g., a common resource) can be configured for multiple target CCs. For example, the network (base station) may configure multiple target CCs for the UE and configure common UL channel resources for the multiple CCs.

[0181] <<Option 2>> Separate resources can be configured for each CC. For example, the network (base station) may configure multiple target CCs for the UE and configure separate UL channel resources for each of the multiple CCs.

[0182] [Second UL Channel] In resource configuration of the second UL channel, at least one of the following options 3 to 4 may be applied / supported. A common option may be applied to Mode A and Mode B, or different options may be applied.

[0183] <<Option 3>> A common resource (e.g., a common resource) can be configured for multiple target CCs. For example, the network (base station) may configure multiple target CCs for the UE and configure common UL channel resources for the multiple CCs.

[0184] <<Option 4>> Separate resources can be configured for each CC. For example, the network (base station) may configure multiple target CCs for the UE and configure separate UL channel resources for each of the multiple CCs.

[0185] In Case 2, the payload size of the second UL channel may be fixed. In this case, one bit may be applied in the first UL channel since there is no need to indicate the payload size of the second UL channel. In the beam report, CC ID / cell ID may be required to identify the CC.

[0186] [Resource Configuration of First UL Channel / Second UL Channel] FIGS. 3A and 3B and FIGS. 4A and 4B are diagrams showing an example of resource configuration of the first UL channel and resource configuration of the second UL channel.

[0187] 3A shows an example of a case where common resources common to multiple CCs (candidate cells or target cells) are configured in resource configuration of the first UL channel and the second UL channel (a combination of Option 1 and Option 3 of Case 1 / Case 2). Here, a case where multiple CCs (e.g., CC #1 to CC #3) are configured for UE IBR and configuration of common first UL channel resources and second UL channel resources for the multiple CCs is supported is shown.

[0188] Figure 3B shows an example of a case where, in the resource configuration of the first UL channel, separate resources are configured for multiple CCs (e.g., CC #1 to CC #3), and in the resource configuration of the second UL channel, common resources are configured that are common among multiple CCs (candidate cells or target cells) (a combination of Option 2 and Option 3 of Case 1 / Case 2).

[0189] Figure 4A shows an example of a case where, in the resource configuration of the first UL channel, common resources are configured that are common to multiple CCs (e.g., CC #1 to CC #3), and, in the resource configuration of the second UL channel, separate resources are configured for multiple CCs (e.g., CC #1 to CC #3) (a combination of option 1 and option 4 in case 2).

[0190] Figure 4B shows an example of a case where separate resources are configured for multiple CCs (e.g., CC #1 to CC #3) in the resource configuration of the first UL channel and the second UL channel (a combination of Option 2 and Option 4 in Case 2).

[0191] 3A and 3B, 4A and 4B show the case where the plurality of first UL channel resources are different from each other in the time domain, but this is not limited thereto, and they may be set differently in the frequency domain / orthogonal code / antenna port. 3A and 3B, 4A and 4B show the case where the plurality of second UL channel resources are different from each other in the time domain, but this is not limited thereto, and they may be set differently in the frequency domain / orthogonal code / antenna port.

[0192] In at least one of Case 1 and Case 2, when multiple CCs / candidate cells simultaneously satisfy a predetermined condition / event, the UE may determine CCs / candidate cells (or beams corresponding to CCs / candidate cells) to include in the beam report based on at least one of the number of CCs / candidate cells that satisfy the event, the size of the beam report, and the priority corresponding to the CCs / candidate cells that satisfy the event (first embodiment). The size of the beam report may be the number of CCs / candidate cells that can be included in one beam instance (or the number of beam / RS indices corresponding to CCs / candidate cells). This makes it possible to appropriately select beams (or RS resource IDs) / CCs to include in the beam report even if the number of CCs that satisfy the predetermined condition / event exceeds a predetermined threshold. The predetermined threshold may be configured by the RRC, defined in a specification, or determined based on UE capabilities.

[0193] In at least one of Case 1 and Case 2, when a configuration of common resources common to multiple CCs / candidate cells is supported for at least one of the first UL channel and the second UL channel (for example, a case other than the combination of Option 2 and Option 4 ( FIG. 4B )), a CC that uses the common resources may be determined based on a predetermined condition (second embodiment). This makes it possible to appropriately select a CC to which the common resources are applied, even when resources common to multiple CCs / candidate cells are configured in at least one of the first UL channel resource configuration and the second UL channel resource configuration.

[0194] <First embodiment> The first embodiment relates to an example of beam report control when multiple CCs (or one or more beams / reference signals corresponding to the multiple CCs) satisfy a predetermined condition / event. A beam report may be read as a measurement result / RS index / beam report.

[0195] The first embodiment may be suitably applied when it is supported to include measurement results / RS indices / beams of multiple CCs in one report (e.g., a single report instance) (e.g., Case 1 (FIG. 3A / B)), or when the payload size of the second UL channel is variable based on the number of CCs that satisfy a predetermined condition / event. Of course, the application of the first embodiment is not limited to this.

[0196] The base station may configure the UE with information about one or more CCs / candidate cells to which UE-initiated / event-based beam reporting (e.g., UEIBR) is applied. The UE may evaluate whether a predetermined condition / event is satisfied for the CC / candidate cell configured for UEIBR, and if the predetermined condition / event is satisfied, may trigger UEIBR to control beam reporting (e.g., measurement result / RS index / beam reporting) using at least one of the first UL channel and the second UL channel.

[0197] In the beam reporting in this embodiment, at least one of the above-mentioned Mode A and Mode B may be applied / supported. The same options may be applied to Mode A and Mode B (or the first UL channel and the second UL channel), or different options may be applied.

[0198] In the following description, an example will be described in which the number of CCs set as target CCs (or CCs set for candidate CCs / UEIBR) is set to L (L>1). The number of beams / RS indices (e.g., N) to be reported for each CC may be set. N (e.g., N≧1) may be set by the base station. N may be set commonly for multiple CCs, or may be set separately (e.g., differently) for each CC.

[0199] When the UE reports N reporting beam / RS indices for each CC, the UE may control the inclusion of at least one beam / RS index among the N that satisfies a predetermined condition / event.

[0200] When multiple CCs (or one or more beams / reference signals corresponding to multiple CCs) meet a specified condition / event, the UE may control beam reporting by applying at least one of the following options 1-1 to 1-5.

[0201] [Option 1-1] The number of beams / RS indices (or the maximum number of beams / RS indices) in a report (or one report instance) may be determined based on the number of CCs (e.g., L) configured for UE IBR. In other words, the size of the beam report may depend on the number of CCs (e.g., L) configured.

[0202] For example, the maximum number of beams / maximum number of RS indices (or beam report size) that can be included in one report may be greater than or equal to the number of CCs (e.g., L) configured for UE IBR (see Figures 5A and 5B).

[0203] 5A shows an example of a case where common resources are configured among a plurality of CCs (candidate cells or target cells) in resource configuration of a first UL channel and a second UL channel (a combination of case 1, options 1 and 3). FIG. 5B shows an example of a case where separate resources are configured among a plurality of CCs (e.g., CC #1 to CC #3) in resource configuration of the first UL channel, and common resources are configured among a plurality of CCs (candidate cells or target cells) in resource configuration of the second UL channel (a combination of case 1, options 2 and 3).

[0204] Here, a case is shown in which multiple CCs (e.g., L CCs) are configured for UEIBR and configuration of a common second UL channel resource for the multiple CCs is supported. In this case, the maximum number of beams / RS indices (or beam report size) that can be included in one report using the second UL channel resource may be equal to or greater than the number of CCs (e.g., L) configured for UEIBR.

[0205] The UE may control the reporting to include at least one beam / RS index (e.g., a beam / RS index whose L1-RSRP is greater than or equal to a predetermined value) for each CC that meets a predetermined condition / event.

[0206] The number of beams included in the report may be a multiple of L. The multiple of L may be, for example, L×N, or another value. In this case, the same number of beams may be included in the report for each CC to be reported. Alternatively, a different number of beams may be included in the report for each CC to be reported based on a predetermined condition (e.g., measurement result, priority).

[0207] When the resource configuration of the first UL channel includes dedicated resources for each CC and the resource configuration of the second UL channel includes common resources for each CC (a combination of Option 2 and Option 3 (see FIG. 5B )), the UE may include a variable number of beams in the report without transmitting an indication bit corresponding to the number of CCs or an indication bit for the payload size of the second UL channel. The number of variable beams may correspond to X×N (X: the number of CCs that satisfy the condition).

[0208] In this way, by setting the maximum value of the beam / RS index (or the maximum number of beams / maximum number of RS indices) to be included in the report to be greater than or equal to the number of CCs set for UE IBR, it becomes possible to report at least one measurement result / RS index / beam corresponding to each CC that satisfies the specified condition / event using the second UL channel, regardless of the number of CCs that satisfy the specified condition / event.

[0209] [Option 1-2] CC / beam / RS indexes to be included in a report (or one reporting instance) may be determined based on the index of each CC (or the cell type corresponding to each CC). For example, a beam / RS index corresponding to a CC with a lower (or higher) index may be preferentially included in the report. Alternatively, a beam / RS index corresponding to a specific cell (e.g., SpCell) may be preferentially included in the report.

[0210] Option 1-2 may be applied when the number of beams / RS indices (or the maximum number) that can be included in the report is less than L, which corresponds to the number of CCs configured (or the total number of beams / RS indices (L x N) to be reported for the CCs configured), or when a different number of beams / RS indices is included in the report for each CC.

[0211] [Options 1-3] Beam / RS indices to be included in a report (or one reporting instance) may be determined based on the position (e.g., position in the time direction) of the first UL channel corresponding to each CC. For example, a beam / RS index corresponding to a CC whose first UL channel is located earlier (or later) may be preferentially included in the report.

[0212] Options 1-3 may also be applied when multiple occasions of a first UL channel corresponding to each CC are associated with one occasion of a second UL channel (e.g., a combination of options 2 and 3 (see Figure 3B)).

[0213] [Option 1-4] Regardless of the index of each CC (or the cell type corresponding to each CC), beam / RS indexes to be included in a report (or one report instance) may be determined based on measurement results (e.g., L1-RSRP / SINR). For example, beam / RS indexes with larger L1-RSRP / SINR may be preferentially included in the report.

[0214] [Option 1-5] The UE may autonomously (by UE implementation) determine the beam / RS index to include in the report (or one reporting instance).

[0215] In at least one of Option 1-2 to Option 1-5, the base station may set P×N (P≦L) as the number of beams that can be included in the report (e.g., the maximum number of beams). In this case, if the number of CCs that satisfy a predetermined condition / event is greater than P (or if beam reporting is triggered for more than P CCs), the UE may determine P CCs to include in the report based on predetermined priorities in Option 1-2 to Option 1-5.

[0216] Alternatively, in at least one of Option 1-2 to Option 1-5, the base station may set X as the number of beams that can be included in a report (e.g., the maximum number of beams). In this case, the UE may select all beams from multiple CCs that satisfy a predetermined condition / event based on a predetermined order and drop beams until X is reached. In this case, beams may be dropped from one CC first, or one beam may be dropped for each CC.

[0217] In at least one of Option 1-1 to Option 1-5, if all beams that satisfy the predetermined condition / event are not transmitted (e.g., if there are beams that satisfy the predetermined condition / event that are not included in the report), the remaining beams / CCs may be transmitted on the next occasion for the second UL channel. When transmitting the remaining beams / CCs using the second UL channel, the UE may transmit the first UL channel before transmitting the second UL channel.

[0218] In at least one of Case 1 and Case 2 (e.g., FIG. 3A / B), when the number of CCs that satisfy a predetermined condition / event is greater than a predetermined threshold that can be included in a beam report, how the UE selects a beam (or RS resource ID) / CC becomes an issue. By applying the first embodiment, even when the number of CCs that satisfy a predetermined condition / event is greater than a predetermined threshold, it becomes possible to appropriately select a beam (or RS resource ID) / CC to be included in a beam report.

[0219] <Second embodiment> In a second embodiment, an example of reporting control of measurement results / RS indices when a common resource configuration is supported for multiple CCs (e.g., target multi-CCs) in resource configuration of at least one of a first UL channel and a second UL channel will be described.

[0220] The second embodiment may be applied alone or in combination with the first embodiment.

[0221] The second embodiment may be suitably applied to cases where a common resource configuration for multiple CCs is supported in resource configuration of at least one of the first UL channel and the second UL channel (for example, the combination of options 1 and 3 (see FIG. 3A), the combination of options 1 and 4 (see FIG. 4A), or the combination of options 2 and 3 (see FIG. 3B) in case 1 / case 2). In other words, the second embodiment may be applied to cases where a configuration other than a case where individual resources are configured for multiple CCs is supported in resource configuration of the first UL channel and the second UL channel (for example, other than the combination of options 2 and 4 (see FIG. 4B)). Of course, the application of the second embodiment is not limited to this.

[0222] In the following description, an example will be given in which the number of CCs set as target CCs (or CCs set for candidate CCs / UEIBR) is set to L. The number of beams / RS indices (e.g., N) to be reported for each CC may be set. N (e.g., N≧1) may be set by the base station. At least one of the N reporting beams reported by the UE for each CC may be selected to satisfy a predetermined condition / event. N may be set commonly for multiple CCs, or may be set separately (e.g., differently) for each CC.

[0223] When the resource configuration of at least one of the first UL channel and the second UL channel supports common resource configuration for multiple CCs, the UE may apply at least one of the following options 2-1 to 2-7 to control reporting of beam measurement results / RS indices. Options 2-1 to 2-3 may be applied to transmissions using the first UL channel, and options 2-4 to 2-7 may be applied to transmissions using the second UL channel.

[0224] Any one of Option 2-1 to Option 2-3 and any one of Option 2-4 to Option 2-7 may be applied in combination as appropriate.

[0225] [Option 2-1] The CC to be transmitted / notified by the first UL channel may be determined based on the index of each CC (or the cell type to which each CC corresponds). For example, the first UL channel transmission corresponding to a CC with a lower (or higher) index may be prioritized (see FIGS. 6A and 6B). Alternatively, the first UL channel transmission corresponding to a specific cell (e.g., SpCell) may be prioritized.

[0226] 6A shows an example of a case where common resources common to multiple CCs (candidate cells or target cells) are configured in resource configuration of the first UL channel and the second UL channel (a combination of options 1 and 3 in case 1 / case 2). FIG. 6B shows an example of a case where common resources common to multiple CCs (candidate cells or target cells) are configured in resource configuration of the first UL channel (a combination of options 1 and 4 in case 2).

[0227] Here, a case is shown in which multiple CCs (e.g., L CCs) are configured for UE IBR and a common first UL channel resource is supported for the multiple CCs. In this case, information about a CC with a smaller index (e.g., CC #1) may be transmitted using a certain first UL channel resource (e.g., the earliest resource in the time domain after a beam report trigger).

[0228] Option 2-1 may be applied when the resource configuration of at least the first UL channel supports the configuration of common resources for multiple CCs (e.g., a combination of options 1 and 3, or a combination of options 1 and 4).

[0229] The first UL channel corresponding to the remaining CC (e.g., CC #2 / CC #3) may be transmitted on the next transmission occasion for the first UL channel or on the next occasion for the first UL channel associated with the next occasion for the second UL channel.

[0230] [Option 2-2] Multiple CCs (or all CCs) that satisfy a predetermined condition / event may be multiplexed into the same UL resource for the first UL channel (see Figures 7A and 7B). Figures 7A / 7B show a case where multiple CCs (e.g., L CCs) are configured for a UE IBR, and configuration of a common first UL channel resource for the multiple CCs is supported. In this case, information about the multiple CCs that satisfy the event may be transmitted using a certain first UL channel resource.

[0231] The UE may use the same / common first UL channel (or first UL channel resource) to transmit / notify multiple CCs (or all CCs) that satisfy a predetermined condition / event.

[0232] Option 2-2 may be applied when the resource configuration of at least the first UL channel supports the configuration of common resources for multiple CCs (e.g., a combination of options 1 and 3, or a combination of options 1 and 4).

[0233] [Option 2-3] The UE may autonomously (by UE implementation) determine the CC to be transmitted / notified by the first UL channel.

[0234] [Option 2-4] The CC to be transmitted / notified by the second UL channel may be determined based on the index of each CC (or the cell type to which each CC corresponds). For example, a second UL channel transmission corresponding to a CC with a lower (or higher) index may be prioritized (see FIGS. 8A and 8B). Alternatively, a second UL channel transmission corresponding to a specific cell (e.g., SpCell) may be prioritized.

[0235] 8A shows an example of a case where common resources common to multiple CCs (candidate cells or target cells) are configured in resource configuration of the first UL channel and the second UL channel (a combination of options 1 and 3 in case 1 / case 2). FIG. 8B shows an example of a case where common resources common to multiple CCs (candidate cells or target cells) are configured in resource configuration of the second UL channel (a combination of options 2 and 3 in case 1 / case 2).

[0236] Here, a case is shown in which multiple CCs (e.g., L CCs) are configured for UE IBR and configuration of a common second UL channel resource for the multiple CCs is supported. In this case, a beam report for a CC with a smaller index (e.g., CC #1) may be transmitted using a certain second UL channel resource (e.g., the earliest resource in the time domain among the second UL channel resources corresponding to the first UL channel transmission).

[0237] Options 2-4 may be applied when the resource configuration of at least the second UL channel supports the configuration of common resources for multiple CCs (e.g., a combination of options 1 and 3, or a combination of options 2 and 3).

[0238] The second UL channel corresponding to the remaining CC may be transmitted at the next transmission occasion for the second UL channel.

[0239] [Option 2-5] The CC to be transmitted / notified by the second UL channel may be determined based on the position (e.g., position in the time direction) of the first UL channel corresponding to each CC. For example, a second UL channel transmission corresponding to a CC whose first UL channel is located earlier (or later) may be prioritized.

[0240] Options 2-5 may be applied when the resource configuration of at least the second UL channel supports the configuration of common resources for multiple CCs (e.g., a combination of options 1 and 3, or a combination of options 2 and 3).

[0241] [Option 2-6] Multiple CCs (or all CCs) that satisfy a predetermined condition / event may be multiplexed into the same UL resource for the second UL channel. In this case, the UE may report beam / RS indices of the multiple CCs (or all CCs) that satisfy the predetermined condition / event using the same / common second UL channel (or second UL channel resource).

[0242] Options 2-6 may be applied when the resource configuration of at least the second UL channel supports the configuration of common resources for multiple CCs (e.g., a combination of options 1 and 3, or a combination of options 2 and 3).

[0243] [Option 2-7] The UE may autonomously (by UE implementation) determine the CC to be transmitted / reported by the second UL channel.

[0244] When a case other than the case where the resources for the first UL channel and the resources for the second UL channel are individually configured for each CC (for example, a case other than the combination of Option 2 and Option 4) is supported, and when multiple CCs satisfy a predetermined condition / event, the question arises as to which UL resource to apply to each CC. By applying the second embodiment, even when a resource common to multiple CCs / candidate cells is configured in at least one of the first UL channel resource configuration and the second UL channel resource configuration, it becomes possible to appropriately select a CC to which the common resource is applied.

[0245] Third Embodiment The third embodiment relates to resetting / stopping / cancelling the evaluation of a predetermined condition / event.

[0246] The third embodiment may be applied to a case where one CC / candidate cell is configured for UEIBR and a case where multiple CCs / candidate cells are configured for UEIBR. When the third embodiment is applied to a case where multiple CCs / candidate cells are configured for UEIBR, the third embodiment may be applied in combination with the first embodiment / second embodiment.

[0247] The UE evaluates an event based on the first configuration information in the UEIBR, and when a predetermined condition / event is satisfied, the UE performs a beam report (for example, a measurement result / RS index / beam report). The first configuration information may be configured / instructed from the base station to the UE by RRC / MAC CE / DCI.

[0248] The configuration information may be information / parameters related to (or applied to) evaluation of an event. For example, the configuration information may include at least one of information on a reference signal (or RS resource) corresponding to a current beam, information on an activated reference signal (or RS resource) corresponding to a new beam, information on a counter / timer applied to event evaluation (e.g., for filtering), and information on one or more CCs / candidate cells to which UE IBR is applied.

[0249] The UE may reset / stop / cancel the evaluation of the event under a previous condition (e.g., the first configuration information) at a predetermined timing (see FIG. 9).

[0250] In this case, information / parameters related to event evaluation may be updated (e.g., second configuration information may be applied / configured) after a predetermined time. The information / parameters related to event evaluation may be, for example, at least one of an RS corresponding to a current beam, an activated RS resource corresponding to a new beam, and a counter / timer for filtering. After the predetermined time, the UE may stop evaluating the event based on the previous condition (e.g., the first configuration information) and evaluate the event based on the updated condition (e.g., the second configuration information).

[0251] For example, in evaluating an event based on the first configuration information, the number of times the current beam / new beam exceeds a predetermined condition (or a predetermined threshold) may be counted, and the event may be determined to be satisfied if the count value exceeds a specific value within a predetermined period (or until a predetermined timer expires). In this case, if a predetermined timing occurs before the count value exceeds the specific value (or before the predetermined timer expires), the UE may reset / stop / cancel the count value / predetermined timer. After the predetermined timing, the UE may apply the count / predetermined timer based on the second configuration information.

[0252] The predetermined timing may be at least one of the following options 3-1 to 3-6.

[0253] [Option 3-1] The predetermined timing may be a timing when the UE receives an RRC reconfiguration message (e.g., an RRC reconfiguration message). When the UE receives the RRC reconfiguration message, the UE may reset / stop / cancel the evaluation of the event based on the previous condition.

[0254] The RRC reconfiguration message may include information / parameters related to event evaluation (e.g., second configuration information). If the information / parameters related to event evaluation are updated by the RRC reconfiguration message, the UE may perform event evaluation (or a UEIBR procedure) based on the updated information / parameters (e.g., conditions).

[0255] If the RRC reconfiguration message does not include information / parameters related to event evaluation (e.g., second configuration information), the UE may perform event evaluation (or UEIBR procedure) based on information / parameters related to new event evaluation indicated by other signals / channels / messages.

[0256] [Option 3-2] The predetermined timing may be when the UE receives information about activation / deactivation of a TCI state (e.g., a candidate TCI state). The information about activation / deactivation of the TCI state may be indicated in a MAC CE (e.g., a TCI state activation / deactivation MAC CE). When the UE receives the information about activation / deactivation of the TCI state, the UE may reset / stop / cancel the evaluation of the event based on the previous conditions.

[0257] The MAC CE indicating the activation / deactivation of the TCI state may include information / parameters related to the evaluation of the event (e.g., second configuration information). If the information / parameters related to the evaluation of the event are updated by the information (e.g., MAC CE) related to the activation / deactivation of the TCI state, the UE may perform the evaluation of the event (or the UEIBR procedure) based on the updated information / parameters (e.g., conditions).

[0258] If the information indicating the activation / deactivation of the TCI state does not include information / parameters related to the evaluation of the event (e.g., second configuration information), the UE may perform the event evaluation (or the UEIBR procedure) based on information / parameters related to the evaluation of a new event indicated by another signal / channel / message.

[0259] [Option 3-3] The predetermined timing may be the timing when the UE receives information (e.g., a TCI state indication) indicating a TCI state (e.g., a unified TCI state). The information indicating the TCI state may be indicated by a DCI / MAC CE. When the UE receives the information indicating the TCI state, the UE may reset / stop / cancel the evaluation of the event based on the previous conditions.

[0260] The DCI / MAC CE indicating the TCI state may include information / parameters related to the evaluation of the event (e.g., second configuration information). If the information / parameters related to the evaluation of the event are updated by the information indicating the TCI state (e.g., DCI / MAC CE), the UE may perform the event evaluation (or the UEIBR procedure) based on the updated information / parameters (e.g., conditions).

[0261] If the information indicating the TCI status does not include information / parameters related to the evaluation of the event (e.g., second configuration information), the UE may perform the event evaluation (or the UEIBR procedure) based on information / parameters related to the evaluation of a new event indicated by another signal / channel / message.

[0262] [Option 3-4] The predetermined timing may be the timing when the UE receives information about a cell switch command. The information about the cell switch command may be indicated in a MAC CE (e.g., cell switch command MAC CE). When the UE receives the information about the cell switch command, the UE may reset / stop / cancel the evaluation of the event based on the previous conditions.

[0263] The MAC CE for the cell switch command may include information / parameters related to the evaluation of the event (e.g., second configuration information). If the information / parameters related to the evaluation of the event are updated by the information (e.g., MAC CE) related to the cell switch command, the UE may perform the evaluation of the event (or the UEIBR procedure) based on the updated information / parameters (e.g., conditions).

[0264] If the information about the cell switch command (e.g., MAC CE) does not include information / parameters related to event evaluation (e.g., second configuration information), the UE may perform event evaluation (or UEIBR procedure) based on new information / parameters related to event evaluation indicated by other signals / channels / messages.

[0265] [Option 3-5] The predetermined timing may be the timing when a cell switch due to L1L2-triggered mobility (LTM) (e.g., an LTM cell switch) is completed. When the cell switch is completed, the UE may reset / stop / cancel the evaluation of the event based on the previous condition.

[0266] In the cell switch operation / procedure, information / parameters related to event evaluation (e.g., second configuration information) may be indicated to the UE. For example, the cell switch command (e.g., MAC CE) may include the information / parameters related to event evaluation. If the information / parameters related to event evaluation are updated in the cell switch procedure, the UE may evaluate the event (or perform the UEIBR procedure) based on the updated information / parameters (e.g., conditions) after the cell switch is completed.

[0267] [Option 3-6] The predetermined timing may be a timing when the UE transmits an RRC reconfiguration complete message (e.g., an RRC reconfiguration complete message). When the UE transmits the RRC reconfiguration complete message, the UE may reset / stop / cancel the evaluation of the event based on the previous condition.

[0268] In the RRC reconfiguration operation / procedure, information / parameters related to event evaluation (e.g., second configuration information) may be indicated to the UE. For example, the information / parameters related to event evaluation may be included in an RRC reconfiguration message. If the information / parameters related to event evaluation are updated in the RRC reconfiguration procedure, the UE may perform event evaluation (or a UEIBR procedure) based on the updated information / parameters (e.g., conditions) after the cell switch is completed.

[0269] In Options 3-1 to 3-6, the specified timing may be the timing when the UE receives / transmits the specified information, or the timing when the specified operation / procedure is completed, or it may be a specific time (e.g., X) after the timing when the specified information is received / transmitted, or a specific time after the timing when the specified operation / procedure is completed.

[0270] The predetermined information may be, for example, at least one of an RRC reconfiguration message, a TCI state activation / deactivation MAC CE, a DCI / MAC CE indicating the TCI state, a cell switch command MAC CE, and an RRC reconfiguration complete message. The predetermined operation / procedure may be an LTM cell switch operation / procedure.

[0271] The particular time (eg, X) may be configured by the RRC, defined by a specification, or determined based on UE capabilities.

[0272] When multiple CCs / candidate cells are configured for UEIBR, a common predetermined timing may be applied to the multiple CCs / candidate cells. For example, when a predetermined timing is applied to a specific CC / candidate cell, the predetermined timing may also be applied to other CCs / candidate cells.

[0273] Alternatively, different predetermined timings (e.g., resetting / stopping / canceling event evaluation at different timings) may be applied to each of a plurality of CCs / candidate cells. In this case, it becomes possible to flexibly update the setting information applied to the event evaluation for each CC / candidate cell.

[0274] [UE Operation] The UE may reset the counter / timer corresponding to the event evaluation (for example, reset to 0 (or 1)) at a predetermined timing.

[0275] The reference signal corresponding to the current beam (e.g., the beam of the current serving cell) may be implicitly changed. The reference signal corresponding to the new beam (e.g., the beam of the candidate cell) may be implicitly changed.

[0276] The UE may apply UE IBR configuration (e.g., CSI resource configuration) after a beam / cell switch without RRC reconfiguration (e.g., RRC reconfiguration).

[0277] By applying the third embodiment, it is possible to appropriately control the update of information related to the evaluation of an event, thereby enabling the evaluation / beam reporting of an event based on appropriate setting information.

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

[0279] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new Logical Channel ID (LCID) in the MAC subheader, which is not defined in existing standards.

[0280] When the notification is made by DCI, the notification may be made by a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used to scramble Cyclic Redundancy Check (CRC) bits assigned to the DCI, the format of the DCI, etc.

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

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

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

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

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

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

[0287] The specific UE capabilities may indicate at least one of the following: - Supporting specific processing / operation / control / information for at least one of the above embodiments. - Supporting event-based beam reporting. - Supporting common resource configuration for multiple CCs in resource configuration of the first UL channel / second UL channel. - Supporting individual resource configuration for multiple CCs in resource configuration of the first UL channel / second UL channel. - Supporting reset / stop / cancellation of event evaluation (or configuration information applied to event evaluation). - Total number / aggregate number of CCs / beams to be reported. - Number of CCs / beams that meet the conditions.

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

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

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

[0291] (Supplementary Notes) The following inventions are supplementary notes regarding one embodiment (first embodiment to second embodiment) of the present disclosure. [Supplementary Note 1-1] A terminal having: a receiving unit that receives information on a plurality of candidate cells; a transmitting unit that transmits an event-based beam report for the plurality of candidate cells using at least one of a first UL channel and a second UL channel; and a control unit that determines at least one of a candidate cell and a beam corresponding to the candidate cell to be included in the beam report, based on at least one of the number of candidate cells that satisfy an event, the size of the beam report, and a priority corresponding to the candidate cell that satisfies the event. [Supplementary Note 1-2] The terminal according to Supplementary Note 1-1, in which the size of the beam report is set to be equal to or greater than the number of the plurality of candidate cells. [Supplementary Note 1-3] The terminal according to Supplementary Note 1-1 or Supplementary Note 1-2, in which the control unit determines at least one of a candidate cell and a beam corresponding to the candidate cell to be included in the beam report, based on at least one of an index corresponding to the candidate cell and an occasion of the first UL channel corresponding to the candidate cell. [Supplementary Note 1-4] When a common resource is set among the plurality of candidate cells for at least one of the first UL channel and the second UL channel, the control unit controls the terminal to perform beam reporting of the plurality of candidate cells using a certain common resource.

[0292] (Supplementary Note) The following inventions are supplemented with respect to one embodiment (third embodiment) of the present disclosure. [Supplementary Note 2-1] A terminal including: a receiving unit that receives first setting information related to an event-based beam report; and a control unit that evaluates an event based on the first setting information and controls the event-based beam report when a beam that satisfies the event exists, wherein the control unit controls to reset the first setting information used for evaluating the event based on at least one of a timing of receiving specific information, a timing of transmitting specific information, and a timing of completing a specific procedure. [Supplementary Note 2-2] The terminal according to Supplementary Note 2-1, wherein, when the control unit resets the first setting information, the control unit evaluates the event based on second setting information included in the specific information and the second setting information acquired in the specific procedure. [Supplementary Note 2-3] The terminal according to Supplementary Note 2-1 or Supplementary Note 2-2, wherein the control unit starts evaluating the event based on the second setting information a predetermined time after at least one of a timing of receiving specific information, a timing of transmitting specific information, and a timing of completing a specific procedure. [Supplementary Note 2-4] The terminal according to any one of Supplementary Note 2-1 to Supplementary Note 2-3, wherein the specific information is at least one of information on RRC reconfiguration, information on a transmission configuration indicator (TCI) state, and information on a cell switch.

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

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

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

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

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

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

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

[0300] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of carrier aggregation (CA) using multiple component carriers (CCs) and dual connectivity (DC).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0315] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be referred to as a search space set. Note that the terms "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," "CORESET configuration," and the like in the present disclosure may be read interchangeably.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0329] The transceiver 120 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

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

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

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

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

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

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

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

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

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

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

[0340] The transceiver 120 may transmit information regarding a plurality of candidate cells to the terminal. The transceiver 120 may receive an event-based beam report for a plurality of candidate cells transmitted from the terminal using at least one of the first UL channel and the second UL channel. The control unit 110 may set the size of the event-based beam report to be equal to or larger than the plurality of candidate cells.

[0341] The transceiver 120 may transmit first configuration information related to an event-based beam report to the terminal. The transceiver 120 may receive an event-based beam report transmitted from the terminal when a beam that satisfies an event evaluated based on the first configuration information exists. The control unit 110 may instruct the terminal to use second configuration information to evaluate an event after at least one of the timing of receiving specific information, the timing of transmitting specific information, and the timing of completing a specific procedure.

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

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

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

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

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

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

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

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

[0350] The transceiver unit 220 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

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

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

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

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

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

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

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

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

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

[0360] The transceiver 220 may receive information about multiple candidate cells. The transceiver 220 may transmit event-based beam reports for the multiple candidate cells using at least one of a first UL channel and a second UL channel. The control unit 210 may determine at least one of candidate cells and beams corresponding to the candidate cells to include in the beam report based on at least one of the number of candidate cells that satisfy the event, the size of the beam report, and the priority corresponding to the candidate cells that satisfy the event.

[0361] The size of the beam report may be set to be equal to or greater than the number of candidate cells. The control unit 210 may determine at least one of the candidate cells and the beams corresponding to the candidate cells to be included in the beam report based on at least one of an index corresponding to the candidate cell and an occasion of the first UL channel corresponding to the candidate cell.

[0362] When common resources are configured among multiple candidate cells for at least one of the first UL channel and the second UL channel, the control unit may control beam reporting of multiple candidate cells using a certain common resource.

[0363] The transceiver 220 may receive first setting information related to event-based beam reporting. The controller 210 may evaluate an event based on the first setting information, and control event-based beam reporting when a beam that satisfies the event exists. The controller 210 may perform control to reset the first setting information used to evaluate an event based on at least one of the timing of receiving specific information, the timing of transmitting specific information, and the timing of completing a specific procedure.

[0364] When the control unit 210 resets the first setting information, the control unit 210 may evaluate an event based on the second setting information included in the specific information and the second setting information acquired in the specific procedure. The control unit 210 may start evaluating the event based on the second setting information a predetermined time after at least one of the timing of receiving the specific information, the timing of transmitting the specific information, and the timing of completing the specific procedure. The specific information may be at least one of information regarding RRC reconfiguration, information regarding a transmission configuration indicator (TCI) state, and information regarding a cell switch.

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

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

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

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

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

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

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

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

[0373] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EEPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. The memory 1002 may also be referred to as a register, cache, main memory, etc. The memory 1002 may store executable programs (program codes), software modules, etc. for implementing a wireless communication method according to an embodiment of the present disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0394] In addition, one or more RBs may be referred to as a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

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

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

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

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

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

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

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

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

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

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

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

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

[0407] Note that the physical layer signaling may be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be referred to as an RRC message, such as an RRC Connection Setup message or an RRC Connection Reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, a MAC Control Element (CE).

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

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

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

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

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

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

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

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

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

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

[0418] Furthermore, in the present disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) property," and "specific QCL type (e.g., Type A, Type D)" may be interchangeable.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A terminal having a receiving unit that receives first setting information regarding event-based beam reporting; and a control unit that evaluates an event based on the first setting information and controls the event-based beam reporting when a beam that satisfies the event exists, wherein the control unit controls to reset the first setting information used to evaluate the event based on at least one of the timing of receiving specific information, the timing of transmitting specific information, and the timing of completing a specific procedure.

2. The terminal according to claim 1, wherein when the control unit resets the first setting information, the control unit evaluates the event based on the second setting information included in the specific information and the second setting information acquired in the specific procedure.

3. The terminal according to claim 1, wherein the control unit starts evaluating the event based on second setting information a predetermined time after at least one of the timing of receiving specific information, the timing of transmitting specific information, and the timing of completing a specific procedure.

4. The terminal of claim 1, wherein the specific information is at least one of information regarding RRC reconfiguration, information regarding a transmission configuration indicator (TCI) state, and information regarding a cell switch.

5. A wireless communication method for a terminal, comprising the steps of: receiving first configuration information regarding event-based beam reporting; evaluating an event based on the first configuration information; and controlling the event-based beam reporting if a beam that satisfies the event exists, and controlling to reset the first configuration information used to evaluate the event based on at least one of the timing of receiving specific information, the timing of transmitting specific information, and the timing of completion of a specific procedure.

6. A base station having a transmitting unit that transmits first configuration information regarding event-based beam reporting to a terminal; a receiving unit that receives an event-based beam report transmitted from the terminal when there is a beam that satisfies an event evaluated based on the first configuration information; and a control unit that instructs the terminal on second configuration information to be used for evaluating the event after at least one of the timing of receiving specific information, the timing of transmitting specific information, and the timing of completing a specific procedure.

Images