Terminal, wireless communication method, and base station

Abstract

A terminal according to an aspect of the present disclosure comprises: a reception unit that receives an activation command for event evaluation in a UE-initiated beam report (UEIBR); and a control unit that controls a trigger of the event evaluation on the basis of the activation command.

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), it is being considered to use L1L2-triggered mobility (LTM) defined in Rel. 18 when a terminal (user terminal, User Equipment (UE)) moves between cells.

[0006] Various use cases are expected for mobility after Rel. 19. For example, in industrial communication systems, cases such as remote control of industrial equipment and factory automation can be mentioned. In addition, in real-time interactive services, AI-based / XR services can be mentioned.

[0007] Additionally, it is being considered that future wireless communication systems will support event-based beam reporting.

[0008] Event-triggered beam reporting can be supported for MIMO / mobility in Rel. 19 and later. Conditional handover (CHO) can also be supported as an aspect of mobility.

[0009] That is, the event-triggered beam report can be used for measurement reporting / beam switching / cell switching. The event-triggered beam report may also be called a UE-initiated beam report (UEIBR).

[0010] In UEIBR, the UE needs to measure many beams to evaluate an event, which is expected to increase the load on the UE.

[0011] In addition, in UEIBR, at least L1-RSRP can be supported as a reporting quantity in SSB for intra-cell / inter-cell (mobility) or periodic CSI-RS for beam management.

[0012] The beam report may also include multiple measurements, which may be used as quality metrics to trigger a UEIBR.

[0013] As target RSs, support for semi-persistent / non-periodic CSI-RS as well as periodic CSI-RS is being considered.

[0014] Also, as UE operation in UEIBR, the UE is expected to perform event evaluation in addition to measuring CSI-RS.

[0015] However, the provisions for supporting these features are not clear in UEIBR. If these are not clear, UEIBR cannot be appropriately controlled, and communication with lower latency cannot be achieved, which may lead to a suppression of improvement in communication quality / throughput.

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

[0017] A terminal according to one aspect of the present disclosure has a receiving unit that receives an activation command for event evaluation in a UE-initiated beam report (UEIBR), and a control unit that controls the triggering of the event evaluation based on the activation command.

[0018] According to one aspect of the present disclosure, communication quality / throughput can be improved.

[0019] Figure 1A is a diagram showing an example of UE mobility in Rel. 17. Figure 1B is a diagram showing an example of UE mobility in Rel. 18. Figure 2 is a diagram showing an example of a Rel. 18 LTM (Long-Term Management) procedure. Figure 3 is a diagram showing a first example of conditional LTM operation. Figure 4 is a diagram showing a second example of conditional LTM operation. Figure 5 is a diagram showing an example of target cell operation in conditional LTM. Figure 6 is a diagram showing a third example of conditional LTM operation. Figure 7 is a diagram showing a fourth example of conditional LTM operation. Figure 8 is a diagram showing a fifth example of conditional LTM operation. Figures 9A and 9B are diagrams showing examples of counting active CSI-RS. Figure 10 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. Figure 11 is a diagram showing an example of a base station configuration according to an embodiment. Figure 12 is a diagram showing an example of a user terminal configuration according to an embodiment. Figure 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 illustrating an example of a vehicle according to an embodiment.

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

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

[0022] (1) The UE receives from the serving cell the SSB configuration for beam measurement of the TRP corresponding to a PCI different from that of the serving cell, and the configuration required to use radio resources for data transmission and reception (including 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 a UE-dedicated channel 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).

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

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

[0025] The additional cell is a cell that has an additional PCI different from the PCI of the serving cell. The UE can receive / transmit a UE-dedicated channel (UE-dedicated CH) from the additional cell. On the other hand, 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 switch (e.g., a process such as RRC reconfiguration) is required due to handover (also called L3 mobility).

[0026] <Scenario 2> Scenario 2 applies L1 / L2 inter-cell mobility (e.g., L1L2-triggered mobility (LTM)). L1 / L2 inter-cell mobility enables the serving cell to be changed using functions such as beam control without RRC reconfiguration. In other words, transmission and reception with a candidate cell / additional cell is possible without handover. Since handover requires RRC reconnection and creates a period when data communication is unavailable, applying L1 / L2 inter-cell mobility that does not require handover makes it possible to continue data communication 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.

[0027] (1) The UE receives configuration information (e.g., SSB configuration, etc.) for a cell with a different PCI (additional cell / candidate cell / target serving cell) from the serving cell (current serving cell) for beam measurement / serving cell change. (2) The UE performs beam measurement of the cell using the different PCI and reports the measurement results to the serving cell. (3) The UE may receive the configuration of the cell with a different PCI (serving cell / candidate 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 the configuration in (1) or separately. (4) Based on the above report, the TCI state of the cell with the different PCI may be activated via L1 / L2 signaling according to the serving cell change. The activation of the TCI state and the serving cell change may be performed separately. (5) The UE changes the serving cell (assumed serving cell) and starts receiving / transmitting using the pre-configured UE-specific channel and TCI state.

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

[0029] 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). Here, the example shows a case where the serving cell is switched from PCI #1 corresponding to the current serving cell (e.g., current serving cell) to PCI #3 corresponding to the target serving cell (e.g., target serving cell) by L1 / L2 signaling.

[0030] The UE can receive / transmit common channels (e.g., system information / paging / short messages) / UE-dedicated channels to / from the new serving cell (target serving cell #3), which may cause the UE to move out of the coverage of the previous serving cell PCI #1.

[0031] (L1L2-triggered mobility (LTM) in Rel. 18) FIG. 2 is a diagram showing an example of LTM considered in Rel. 18. Here, the steps of LTM are shown, including LTM preparation (e.g., LTM preparation), early synchronization (e.g., early sync), LTM execution (e.g., LTM execution), and LTM completion (e.g., LTM completion), but the LTM steps are not limited to these. Some steps (or operations included in steps) may be omitted, the order of operations included in some steps may be reversed with other operations included in other steps, or other steps (or other operations) may be added. Note that in the present disclosure, early synchronization may be read as synchronization.

[0032] <LTM preparation> 1: The UE sends a measurement report message to the gNB. The gNB determines the LTM configuration and starts preparation of one or more candidate cells.

[0033] 2: The gNB sends an RRC reconfiguration message to the UE including LTM candidate cell configurations for one or more candidate cells.

[0034] 3: The UE saves its LTM candidate cell configuration and sends an RRC reconfiguration complete message to the gNB.

[0035] <Early sync> 4a: The UE performs DL synchronization with one or more candidate cells before receiving a cell switch command. DL synchronization for candidate cells before a cell switch command may be supported at least for SSB-based implementation.

[0036] 4b: If requested by the network, the UE performs early TA acquisition with one or more candidate cells before receiving a cell switch command. This is triggered by a PDCCH order from the source cell via a CFRA. The UE then transmits a preamble to the indicated candidate cells. To minimize data interruption in the source cell due to Contention Free Random Access (CFRA) to the candidate cells, the UE does not receive a RAR intended for TA value acquisition. The TA value of the candidate cell is indicated in the cell switch command. The UE does not maintain a TA timer for the candidate cells and ensures the validity of the TA based on the network implementation.

[0037] <LTM execution> 5: The UE performs L1 measurements configured on the candidate cells and sends an L1 measurement report to the gNB. L1 measurements are performed as long as the RRC reconfiguration in step 2 is applied.

[0038] 6: The gNB decides to perform a cell switch to the target cell and sends a MAC CE (Cell Switch Command) to trigger the cell switch. The MAC CE includes a candidate configuration for the index of the target cell. The UE switches to the target cell and applies the configuration indicated by the candidate configuration index.

[0039] 7: If the UE does not have a valid TA for the target cell, it performs a random access procedure to the target cell.

[0040] <LTM completion> 8: The UE completes the LTM cell switch procedure by sending an RRC reconfiguration complete message. The UE performs the RA procedure in step 7, and considers the LTM execution to be completed successfully if the random access procedure is successfully completed. In RACH-less LTM, the UE considers the LTM execution to be completed successfully if the network determines that the first UL data has been successfully received. The UE determines the successful reception of the first UL data by receiving a PDCCH specifying the UE's C-RNTI in the target cell that schedules the next new transmission of the first UL data.

[0041] (Reporting Configuration (ReportConfigNR)) The RRC information element ReportConfigNR specifies the trigger criteria for an NR measurement reporting event, CHO, Conditional PSCell Addition (CPA), Conditional PSCell Change (CPC) event, or Layer 2 UE-to-Network (L2U2N) relay measurement reporting event. For events labeled AN (N is 1 or 2) as shown below, the measurement reporting event and CHO, CPA, and CPC events are based on cell measurement results derived based on SS / PBCH blocks or CSI-RS. Note that serving, neighboring, and PCell / PSCell may be replaced with the measurement results (L1-RSRP / L1-SINR, etc.) of the serving cell, neighboring cell, and PCell / PSCell.

[0042] Event A1: Serving becomes better than an absolute threshold. Event A2: Serving becomes worse than an absolute threshold. Event A3: Neighbor has a better offset than the PCell / PSCell. Event A4: Neighbor becomes better than an absolute threshold. Event A5: PCell / PSCell becomes worse than absolute threshold 1 and neighbor / SCell becomes better than another absolute threshold 2. Event A6: Neighbor cell becomes a larger offset than the SCell.

[0043] Event D1: The distance between the UE and the reference location (referenceLocation1) becomes larger than a set threshold (distanceThreshFromReference1), and the distance between the UE and the reference location (referenceLocation2) becomes smaller than a set threshold (distanceThreshFromReference2). Conditional event A3: The conditional reconfiguration candidate has a better offset than the PCell / PSCell. Conditional event A4: The conditional reconfiguration candidate becomes better than an absolute threshold. Conditional event A5: The PCell / PSCell becomes worse than absolute threshold 1, and the conditional reconfiguration candidate becomes better than another absolute threshold 2. Conditional event D1: The distance between the UE and the reference location (referenceLocation1) becomes larger than a set threshold (distanceThreshFromReference1), and the distance between the UE and the reference location (referenceLocation2) of the conditional reconfiguration candidate becomes smaller than a set threshold (distanceThreshFromReference2).

[0044] Condition Event T1: The duration measured at the UE exceeds the configured threshold t1-Threshold but is less than t1-Threshold+duration. Event X1: The UE of the serving L2U2N relay becomes worse than absolute threshold 1 and the NR cell becomes better than another absolute threshold 2. Event X2: The UE of the serving L2U2N relay becomes worse than the absolute threshold. For Event I1, the measurement reporting event is based on Cross Link Interference (CLI) measurement results, which are derived based on SRS-RSRP or CLI-RSSI. Event I1: The interference becomes higher than the absolute threshold.

[0045] (Conditional Handover (CHO)) This section describes conditional handover (CHO) in Rel. 16 and later. CHO is applied to, for example, non-terrestrial networks (NTN). In NTN, the following additional trigger conditions are supported for the UE to perform CHO to a candidate cell: Radio Resource Management (RRM) measurement-based event A4. Time-based trigger conditions. Location-based trigger conditions.

[0046] A time-based or location-based trigger condition is always configured together with one of the measurement-based trigger conditions (CHO events A3 / A4 / A5 described below). How the UE evaluates the time-based or location-based trigger conditions together with the RRM measurement-based events is up to the UE implementation.

[0047] (Rel. 18 LTM and Rel. 16 CHO) While the above-mentioned LTM (e.g., Rel. 18 LTM) supports early sync / early L1 measurement report, CHO (e.g., Rel. 16 CHO) does not support early sync / early measurement report. In LTM, mobility decisions are made by the network (based on L1 beam reports), while in CHO, they are made by the UE (based on L3 measurements and CHO conditions).

[0048] In LTM, a MAC CE for cell switch command is sent from the base station to the UE. In CHO, the UE starts evaluating the CHO implementation conditions for the candidate cells after receiving the CHO configuration through RRC signaling. After deciding on mobility (or cell switch), RACH is required in CHO, but RACH may not be required in LTM.

[0049] (Conditional LTM) In the case where conditional LTM (eg, conditional LTM (CLTM)) is supported, an example of providing / signaling / evaluating execution conditions (eg, execution conditions) for candidate cells will be described.

[0050] Execution conditions may be set for each candidate cell by RRC signaling / MAC CE. The execution conditions (or may simply be called "conditions") may include at least one of an event, a reference signal type (RS type), a reference signal configuration (RS configuration), and a measurement quantity. The reference signal type (RS type) may indicate SSB / CSI-RS. The measurement quantity may indicate L1-RSRP / L3-RSRP / SINR / RSRQ.

[0051] The implementation conditions may be set separately for each candidate cell (e.g., the setting of different conditions may be supported). Alternatively, the implementation conditions may be set commonly for multiple candidate cells (e.g., a candidate cell group) or all candidate cells. Alternatively, some of the implementation conditions may be set commonly for each candidate cell, and the remaining implementation conditions may be set separately. Some of the implementation conditions may be events, and the remaining implementation conditions may be condition values, etc. Of course, this is not limited to this.

[0052] The number of candidate cells for which the enabling condition is provided may be predefined in a specification, may be configured in the UE by a network (e.g., a base station), or may be determined based on UE capabilities. For example, the number of cells for which the enabling condition is provided may be the same as the configured candidate cells, or may be less than all the configured candidate cells.

[0053] Settings for implementation conditions (e.g., detailed settings) may be the same as the condition settings of the existing system, which may be, for example, condition settings supported by CHO supported in Rel. 16 (e.g., condition settings based on L3 measurements).

[0054] Alternatively, the setting of the implementation conditions may be a new condition setting similar to that of an event-triggered L1 report (e.g., an event-triggered L1 report). Examples of conditions (or events) are as follows: Event A2: The measurement result of the serving cell is worse than a threshold. Event A3: The measurement result of the neighboring cell (the value obtained by adding an offset to the measurement result) is better than the measurement result of the SpCell (the value obtained by adding an offset to the measurement result). Event A4: The measurement result of the neighboring cell (the value obtained by adding an offset to the measurement result) is better than a threshold. Event A5: The measurement result of the SpCell is worse than a first threshold, and the measurement result of the neighboring cell (the value obtained by adding an offset to the measurement result) is better than a second threshold. Event A6: The measurement result of the neighboring cell (the value obtained by adding an offset to the measurement result) is better than the measurement result of the serving cell (Secondary Cell (SCell)) (the value obtained by adding an offset to the measurement result). Event I1: The interference measurement result is higher than a threshold. Event A4': The measurement result of one beam from a neighboring cell is better than a threshold. Event A4'': The statistic (e.g., average, sum, etc.) of the measurement results of multiple beams (e.g., the best X beams) is better than a threshold. X may be fixed or may be configurable by higher layer signaling, etc. Event A4''': The L1-RSRP measurement result of one beam from a neighboring cell is better than a threshold. Event A4'''': The L1-RSRP of each of the X beams from the neighboring cells is better than a threshold.

[0055] It should be noted that the applicable conditions / events are not limited to these, and a combination of the above events may be applied, or other events may be applied.

[0056] For each condition for each candidate cell (or for multiple / all candidate cells), the conditions (or events) to be set may be determined based on at least one of the following options 1 and 2.

[0057] [Option 1] One condition may be set for each candidate cell (or for multiple / all candidate cells), and the condition may correspond to only one event, i.e., one condition with only one event may be set for each candidate cell (or for multiple / all candidate cells).

[0058] When a condition (or an event corresponding to the condition) corresponding to each candidate cell is satisfied, the UE / base station may control to perform an LTM procedure / action for the candidate cell.

[0059] [Option 2] Multiple (e.g., up to X) conditions may be configured for each candidate cell (or for multiple / all candidate cells). X may be, for example, 2 or 3, or may be 4 or more. X may be defined in a specification, configured by the base station to the UE, or determined based on UE capabilities.

[0060] When at least one of a plurality of conditions (or events corresponding to each condition) corresponding to each candidate cell is satisfied, the UE / base station may be controlled to perform an LTM procedure / action for the candidate cell.

[0061] When multiple (e.g., X) conditions are supported for each candidate cell, restrictions may be set between the multiple conditions. The restrictions between the conditions may be, for example, RS configuration / RS type / event / measurement quantity. As an example, the same RS configuration / RS type may be set between the multiple conditions, and different event / measurement quantities may be set between the multiple conditions.

[0062] When different conditions correspond to different candidate cells, restrictions may be imposed between the conditions, or no restrictions may be imposed between the conditions.

[0063] The supported conditions (eg, RS configuration / RS type / event / measurement quantity), the number of conditions to be set may be according to the UE capability.

[0064] An example of the operation of the conditional LTM will be described below, but parts that are not particularly described may be the same as the procedure of the Rel. 18 LTM (R18 LTM) shown in FIG.

[0065] [Conditional LTM Operation Example 1] Fig. 3 is a diagram showing a first example of conditional LTM operation. Fig. 3 shows the steps of LTM preparation (e.g., LTM preparation), early synchronization (e.g., early sync), LTM execution (e.g., LTM execution), and LTM completion (e.g., LTM completion) as the conditional LTM operation, but the LTM steps are not limited to these. Some steps (or operations included in steps) may be omitted, the order of operations included in some steps and other operations included in other steps may be reversed, or other steps (or other operations) may be added.

[0066] <<LTM Preparation>> In LTM preparation, a UE RRC-connected to a serving cell (e.g., a UE in RRC_CONNECTED) transmits a measurement report. The measurement report may be an L3 measurement report. The base station (or source base station / serving cell) performs LTM candidate preparation (e.g., LTM candidate preparation) based on the measurement report transmitted from the UE.

[0067] The base station performs an LTM candidate configuration (e.g., an LTM candidate configuration) and configuration of execution conditions (e.g., execution conditions) for a candidate cell by RRC (e.g., RRC reconfiguration). By the LTM candidate configuration, information about the candidate cell may be configured in the UE. By configuring the execution conditions for the candidate cell, the execution conditions may be configured in the UE for each candidate cell (or for multiple / all candidate cells).

[0068] Option 1 / Option 2 may be applied to the setting of implementation conditions for candidate cells.

[0069] Early sync: The UE performs early synchronization (e.g., early sync) with a candidate cell. DL / UL early synchronization with a candidate cell may be performed by the UE after RRC configuration (e.g., RRC reconfiguration) of the LTM candidate cell.

[0070] LTM execution: The UE performs measurements (e.g., L1 measurements) on configured candidate cells and sends measurement reports, which may be L1 measurement reports.

[0071] The base station (or source base station / serving cell) makes a conditional LTM (CLTM) decision based on the measurement report transmitted from the UE. For example, the base station determines the conditional LTM for one or more candidate target cells for which the enabling condition can be evaluated (or for which the UE needs to evaluate the enabling condition). The one or more candidate target cells for which the enabling condition can be evaluated may be determined based on the measurement report transmitted from the UE.

[0072] The base station may transmit a predetermined MAC CE to the UE, which may be used to indicate to the UE information about one or more candidate target cells for conditional LTM (or for which the implementation conditions are to be evaluated). The predetermined MAC CE may trigger the UE to evaluate the implementation conditions.

[0073] The UE may initiate an implementation evaluation for candidate target cells indicated by a predetermined MAC CE. If a target cell satisfies the implementation condition, the UE may implement LTM (or mobility) for the target cell. For example, if a candidate cell satisfies the implementation condition, the UE may detach (e.g., detach) from a source (e.g., source cell) and apply the configurations (e.g., target configurations) of the target cell to which the handover is to be performed.

[0074] For example, when a plurality of candidate cells (or candidate target cells) are indicated by a given MAC CE, the UE may determine a specific target cell to be subjected to mobility / cell switch by considering the implementation conditions corresponding to each candidate cell (or the implementation conditions common to the plurality of candidate cells).The given MAC CE may indicate the implementation conditions / events corresponding to each candidate cell (or the implementation conditions common to the plurality of candidate cells).

[0075] The UE may perform a random access procedure (RACH-based CLTM) to the selected (e.g., switched to) target cell.

[0076] For example, if the UE does not have a valid Timing Advance (TA) for the target cell / candidate cell (or a destination cell), it may perform a random access procedure to obtain a TA value for the target cell. On the other hand, if the UE has a valid Timing Advance for the target cell / candidate cell (or a destination cell), it may not perform the random access procedure (or may omit / skip the random access procedure). Note that the random access procedure may be performed when the UE has a valid TA for the target cell.

[0077] After receiving a predetermined MAC CE, the UE may determine whether to apply a random access procedure based on at least one of the predetermined MAC CE and an RRC parameter (e.g., an RRC parameter related to the setting of a TA acquisition method). For example, the UE may determine whether to apply a random access procedure based on a value of a predetermined field (e.g., a timing advance command field) included in the predetermined MAC CE. The UE may also determine whether to apply a random access procedure based on a TA acquisition method set by an RRC parameter (or the TA acquisition method and the value of a predetermined field in the predetermined MAC CE).

[0078] Note that, although Fig. 3 shows a case where a candidate target cell for conditional LTM (or a candidate target cell for evaluating an implementation condition) is indicated by a MAC CE, this is not limiting. For example, information on a candidate target cell for conditional LTM may be indicated to a UE by a DCI. Alternatively, the MAC CE may indicate a correspondence (or mapping) between information on multiple candidate target cells for conditional LTM (or multiple candidate target cells and implementation conditions for conditional LTM) and a codepoint in a predetermined field of the DCI, and a specific candidate target cell for conditional LTM may be indicated by the DCI.

[0079] <LTM Completion> The LTM cell switch procedure may be completed by the UE sending a predetermined message to the target cell / candidate cell.

[0080] In the case of RACH-based LTM, the UE may determine that the LTM implementation has been completed successfully if the random access procedure has been completed successfully.

[0081] In the case of RACH-less (e.g., RACH-less) LTM, the UE may determine that the LTM has been successfully performed if the UE determines that the network has successfully received the first UL data. For example, in the case of RACH-less LTM, the UE may transmit the first data to the target cell along with sending an RRC reconfiguration complete message. The UE may determine that the first UL data has been successfully received by receiving a PDCCH in the target cell that addresses the UE's C-RNTI. This PDCCH corresponds to the PDCCH that schedules a new transmission following the first UL data.

[0082] [Conditional LTM Operation Example 2] Figure 4 is a diagram showing a second example of conditional LTM operation. Figure 4 shows the steps of LTM preparation (e.g., LTM preparation), early sync and LTM execution (e.g., early sync and LTM execution), and LTM completion (e.g., LTM completion) as the conditional LTM operation, but the LTM steps are not limited to these. Some steps (or operations included in steps) may be omitted, the order of operations included in some steps and other operations included in other steps may be reversed, or other steps (or other operations) may be added.

[0083] <LTM Preparation> This can be performed in the same manner as the LTM preparation in FIG.

[0084] <Early sync and LTM execution> The UE performs early synchronization (e.g., early sync) and LTM execution with the candidate cell.

[0085] The UE may perform DL early synchronization with the LTM candidate cell after RRC configuration (e.g., RRC reconfiguration) of the candidate cell. For example, the UE may perform DL synchronization with the configured candidate cell.

[0086] The UE performs measurements (e.g., L1 measurements) on the configured candidate cells and sends a measurement report, which may be an L1 measurement report.

[0087] The base station (or source base station / serving cell) makes a conditional LTM (CLTM) decision based on the measurement report transmitted from the UE. For example, the base station determines the conditional LTM for one or more candidate target cells for which the enabling condition can be evaluated (or for which the UE needs to evaluate the enabling condition). The one or more candidate target cells for which the enabling condition can be evaluated may be determined based on the measurement report transmitted from the UE.

[0088] The base station may transmit a predetermined MAC CE to the UE, which may be used to indicate to the UE information about one or more candidate target cells for conditional LTM (or for which the implementation conditions are to be evaluated). The predetermined MAC CE may trigger the UE to evaluate the implementation conditions.

[0089] The UE may perform DL synchronization with the LTM candidate cell after RRC configuration (e.g., RRC reconfiguration) of the candidate cell. In this case, the UE may perform UL synchronization with the candidate target cell for conditional LTM indicated by a predetermined MAC CE. In this way, by performing UL synchronization after receiving the predetermined MAC CE, it is possible to reduce the number of cells for which UL synchronization is performed.

[0090] The UE may also start an implementation evaluation for a candidate target cell indicated by a predetermined MAC CE. If there is a target cell that satisfies the implementation condition, the UE may perform LTM (or mobility) for the target cell. For example, if the implementation condition is satisfied, the UE may detach (e.g., detach) from a source (e.g., source cell) and apply the configuration (e.g., target configurations) of the target cell to which the handover is to be performed. Note that the UE may perform UL synchronization after the implementation evaluation.

[0091] For example, when a plurality of candidate cells (or candidate target cells) are indicated by a given MAC CE, the UE may determine a specific target cell to be subjected to mobility / cell switch by considering the implementation conditions corresponding to each candidate cell (or the implementation conditions common to the plurality of candidate cells).The given MAC CE may indicate the implementation conditions / events corresponding to each candidate cell (or the implementation conditions common to the plurality of candidate cells).

[0092] The UE may perform a random access procedure (RACH-based CLTM) to the selected (e.g., switched to) target cell.

[0093] For example, if the UE does not have a valid Timing Advance (TA) for the target cell / candidate cell (or a destination cell), it may perform a random access procedure to obtain a TA value for the target cell. On the other hand, if the UE has a valid Timing Advance for the target cell / candidate cell (or a destination cell), it may not perform the random access procedure (or may omit / skip the random access procedure). Note that the random access procedure may be performed when the UE has a valid TA for the target cell.

[0094] After receiving a predetermined MAC CE, the UE may determine whether to apply a random access procedure based on at least one of the predetermined MAC CE and an RRC parameter (e.g., an RRC parameter related to the setting of a TA acquisition method). For example, the UE may determine whether to apply a random access procedure based on a value of a predetermined field (e.g., a timing advance command field) included in the predetermined MAC CE. The UE may also determine whether to apply a random access procedure based on a TA acquisition method set by an RRC parameter (or the TA acquisition method and the value of a predetermined field in the predetermined MAC CE).

[0095] While Fig. 4 illustrates a case in which a candidate target cell for conditional LTM (or a candidate target cell for evaluating implementation conditions) is indicated by a MAC CE, this is not limiting. For example, information on a candidate target cell for conditional LTM may be indicated to a UE by a DCI. Alternatively, the MAC CE may indicate a correspondence (or mapping) between information on multiple candidate target cells for conditional LTM (or multiple candidate target cells and implementation conditions for conditional LTM) and a codepoint in a predetermined field of the DCI, and a specific candidate target cell for conditional LTM may be indicated by the DCI.

[0096] <LTM Completion> This can be done in the same way as the LTM completion in FIG.

[0097] [Example of Operation of Target Cell in Conditional LTM] Fig. 5 is a diagram showing an example of operation of a target cell in conditional LTM. Fig. 5 shows steps of LTM preparation (e.g., LTM preparation), early synchronization (e.g., early sync), LTM execution (e.g., LTM execution), and LTM completion (e.g., LTM completion) as the operation of conditional LTM (the example of Fig. 3 ), but the steps of LTM are not limited to these. Some steps (or operations included in steps) may be omitted, the order of operations included in some steps and other operations included in other steps may be swapped (e.g., the example of Fig. 4 ), or other steps (or other operations) may be added.

[0098] <<LTM Preparation>> In LTM preparation, a UE that is RRC connected to a serving cell (e.g., a UE in RRC_CONNECTED) transmits a measurement report. The measurement report may be an L3 measurement report.

[0099] The base station (or source base station / serving cell) prepares an LTM candidate (e.g., LTM candidate preparation) based on the measurement report transmitted from the UE. In this case, information may be exchanged / shared among multiple candidate cells (which may include the serving cell). The information exchanged / shared among multiple candidate cells may be at least one of information about the measurement report reported from the UE, information about the configuration of the candidate cell to be configured, and information about the implementation conditions for each candidate cell.

[0100] The base station performs an LTM candidate configuration (e.g., an LTM candidate configuration) and configuration of execution conditions (e.g., execution conditions) for a candidate cell by RRC (e.g., RRC reconfiguration). By the LTM candidate configuration, information about the candidate cell may be configured in the UE. By configuring the execution conditions for the candidate cell, the execution conditions may be configured in the UE for each candidate cell (or for multiple / all candidate cells).

[0101] Option 2-1 / Option 2-2 may be applied to the setting of implementation conditions for candidate cells.

[0102] <Early Sync> The UE performs early synchronization (e.g., early sync) with a candidate cell. DL / UL early synchronization with a candidate cell may be performed by the UE after RRC configuration (e.g., RRC reconfiguration) of the LTM candidate cell. UL early synchronization may be performed after transmitting a measurement report (e.g., L1 measurement report) of the LTM implementation step or after receiving a predetermined MAC CE.

[0103] LTM execution: The UE performs measurements (e.g., L1 measurements) on configured candidate cells and sends measurement reports, which may be L1 measurement reports.

[0104] The base station (or source base station / serving cell) makes a conditional LTM (CLTM) decision based on the measurement report transmitted from the UE. For example, the base station determines the conditional LTM for one or more candidate target cells for which the enabling condition can be evaluated (or for which the UE needs to evaluate the enabling condition). The one or more candidate target cells for which the enabling condition can be evaluated may be determined based on the measurement report transmitted from the UE.

[0105] The base station may transmit a predetermined MAC CE to the UE, which may be used to indicate to the UE information about one or more candidate target cells for conditional LTM (or for which the implementation conditions are to be evaluated). The predetermined MAC CE may trigger the UE to evaluate the implementation conditions.

[0106] The base station may also notify the candidate cell of information related to the conditional LTM (CLTM) decision. For example, the base station may notify the candidate cell of information related to one or more candidate target cells for the conditional LTM (or for which the implementation conditions are to be evaluated). The candidate cells to which the information is notified may be limited to candidate cells selected as candidate cells for the conditional LTM (CLTM) or may not be limited to candidate cells (for example, the information may also be notified to candidate cells that are not selected as candidate cells for the conditional LTM (CLTM)).

[0107] The UE may initiate an implementation evaluation for candidate target cells indicated by a predetermined MAC CE. If a target cell satisfies an implementation condition, the UE may implement LTM (or mobility) for the target cell. For example, if the implementation condition is met, the UE may detach (e.g., detach) from a source (e.g., source cell) and apply the configurations (e.g., target configurations) of the target cell to which the handover is to be performed.

[0108] The UE may perform a random access procedure to the selected (e.g., target) cell. For example, if the UE does not have a valid timing advance for the target / candidate cell (or destination cell), the UE may perform the random access procedure to obtain a TA value for the target cell. On the other hand, if the UE has a valid timing advance (TA) for the target / candidate cell (or destination cell), the UE may not perform the random access procedure (or may omit / skip the random access procedure).

[0109] After receiving a predetermined MAC CE, the UE may determine whether to apply a random access procedure based on at least one of the predetermined MAC CE and an RRC parameter (e.g., an RRC parameter related to the setting of a TA acquisition method). For example, the UE may determine whether to apply a random access procedure based on a value of a predetermined field (e.g., a timing advance command field) included in the predetermined MAC CE. The UE may also determine whether to apply a random access procedure based on a TA acquisition method set by an RRC parameter (or the TA acquisition method and the value of a predetermined field in the predetermined MAC CE).

[0110] Note that, although the case where a candidate target cell for conditional LTM (or a candidate target cell for evaluating implementation conditions) is indicated by MAC CE has been shown here, this is not limiting. For example, information on a candidate target cell for conditional LTM may be indicated to a UE by DCI. Alternatively, the MAC CE may indicate a correspondence (or mapping) between information on multiple candidate target cells for conditional LTM (or multiple candidate target cells and implementation conditions for conditional LTM) and a code point in a predetermined field of the DCI, and a specific candidate target cell for conditional LTM may be indicated by the DCI.

[0111] <<LTM Completion>> The LTM cell switch procedure may be completed by the UE sending a predetermined message to the selected (e.g., switched to) target cell / candidate cell.

[0112] In the case of RACH-based LTM, the UE may determine that the LTM implementation has been completed successfully if the random access procedure has been completed successfully.

[0113] [Conditional LTM Operation Example 3] Fig. 6 is a diagram showing a third example of conditional LTM operation. Fig. 6 shows the steps of LTM preparation (e.g., LTM preparation), early synchronization (e.g., early sync), LTM execution (e.g., LTM execution), and LTM completion (e.g., LTM completion) as the conditional LTM operation, but the LTM steps are not limited to these. Some steps (or operations included in steps) may be omitted, the order of operations included in some steps and other operations included in other steps may be reversed, or other steps (or other operations) may be added. Fig. 6 may also be suitably applied to RACH-less CLTM.

[0114] <<LTM Preparation>> In LTM preparation, a UE RRC-connected to a serving cell (e.g., a UE in RRC_CONNECTED) transmits a measurement report. The measurement report may be an L3 measurement report. The base station (or source base station / serving cell) performs LTM candidate preparation (e.g., LTM candidate preparation) based on the measurement report transmitted from the UE.

[0115] The base station performs an LTM candidate configuration (e.g., an LTM candidate configuration) and configuration of execution conditions (e.g., execution conditions) for a candidate cell by RRC (e.g., RRC reconfiguration). By the LTM candidate configuration, information about the candidate cell may be configured in the UE. By configuring the execution conditions for the candidate cell, the execution conditions may be configured in the UE for each candidate cell (or for multiple / all candidate cells).

[0116] Option 1 / Option 2 may be applied to the setting of implementation conditions for candidate cells.

[0117] <Early Sync> The UE performs early synchronization (e.g., early sync) with a candidate cell. DL / UL early synchronization with a candidate cell may be performed by the UE after RRC configuration (e.g., RRC reconfiguration) of the LTM candidate cell. UL early synchronization may be performed after transmitting a measurement report (e.g., L1 measurement report) of the LTM implementation step or after receiving a predetermined MAC CE.

[0118] LTM execution: The UE performs measurements (e.g., L1 measurements) on configured candidate cells and sends measurement reports, which may be L1 measurement reports.

[0119] The base station (or source base station / serving cell) makes a conditional LTM (CLTM) decision based on the measurement report transmitted from the UE. For example, the base station determines the conditional LTM for one or more candidate target cells for which the enabling condition can be evaluated (or for which the UE needs to evaluate the enabling condition). The one or more candidate target cells for which the enabling condition can be evaluated may be determined based on the measurement report transmitted from the UE.

[0120] The base station may transmit a predetermined MAC CE to the UE, which may be used to indicate to the UE information about one or more candidate target cells for conditional LTM (or for which the implementation conditions are to be evaluated). The predetermined MAC CE may trigger the UE to evaluate the implementation conditions.

[0121] The UE may initiate an implementation evaluation for candidate target cells indicated by a predetermined MAC CE. If a target cell satisfies an implementation condition, the UE may implement LTM (or mobility) for the target cell. For example, if the implementation condition is met, the UE may detach (e.g., detach) from a source (e.g., source cell) and apply the configurations (e.g., target configurations) of the target cell to which the handover is to be performed.

[0122] After the UE decides on mobility or cell switch (or selects a new target cell) based on the evaluation of the implementation conditions, the UE may send at least one of an RRC reconfiguration completion message (e.g., RRCReconfigurationComplete) and a MAC CE (e.g., new MAC CE) to the new target cell, which may indicate the UE's CLTM decision to the new target cell.

[0123] <LTM Completion> The LTM cell switch procedure may be completed by the UE sending a predetermined message / MAC CE to the target cell / candidate cell.

[0124] In the case of RACH-less (e.g., RACH-less) LTM, the UE may determine that the LTM has been successfully performed if the UE determines that the network has successfully received the first UL data. For example, in the case of RACH-less LTM, the UE may transmit the first data to the target cell along with an RRC reconfiguration complete message / MAC CE. The UE may determine that the first UL data has been successfully received by receiving a PDCCH in the target cell that addresses the UE's C-RNTI. This PDCCH corresponds to the PDCCH that schedules a new transmission following the first UL data.

[0125] [Conditional LTM Operation Example 4] Fig. 7 is a diagram showing a fourth example of conditional LTM operation. Fig. 7 shows the steps of LTM preparation (e.g., LTM preparation), early synchronization (e.g., early sync), LTM execution (e.g., LTM execution), and LTM completion (e.g., LTM completion) as the conditional LTM operation, but the LTM steps are not limited to these. Some steps (or operations included in steps) may be omitted, the order of operations included in some steps and other operations included in other steps may be reversed, or other steps (or other operations) may be added. Fig. 7 may also be suitably applied to RACH-less CLTM.

[0126] <LTM Preparation> This can be performed in the same manner as the LTM preparation in FIG.

[0127] <Early Sync> This can be performed in the same manner as the early sync in FIG.

[0128] LTM execution: The UE performs measurements (e.g., L1 measurements) on configured candidate cells and sends measurement reports, which may be L1 measurement reports.

[0129] The base station (or source base station / serving cell) makes a conditional LTM (CLTM) decision based on the measurement report transmitted from the UE. For example, the base station determines the conditional LTM for one or more candidate target cells for which the enabling condition can be evaluated (or for which the UE needs to evaluate the enabling condition). The one or more candidate target cells for which the enabling condition can be evaluated may be determined based on the measurement report transmitted from the UE.

[0130] The base station may transmit a predetermined MAC CE to the UE, which may be used to indicate to the UE information about one or more candidate target cells for conditional LTM (or for which the implementation conditions are to be evaluated). The predetermined MAC CE may trigger the UE to evaluate the implementation conditions.

[0131] The UE may initiate an implementation evaluation for candidate target cells indicated by a predetermined MAC CE. If a target cell satisfies an implementation condition, the UE may implement LTM (or mobility) for the target cell. For example, if the implementation condition is met, the UE may detach (e.g., detach) from a source (e.g., source cell) and apply the configurations (e.g., target configurations) of the target cell to which the handover is to be performed.

[0132] After the UE makes a mobility or cell switch decision (or selects a new target cell) based on the evaluation of the implementation conditions, the UE may transmit a predetermined MAC CE to the current serving cell (e.g., the serving cell before the cell switch). The MAC CE may indicate the UE's CLTM decision to the current serving cell. The predetermined MAC CE may include at least one of information about the selected target cell and information about the latest L1 beam measurement, event-triggered L1 beam measurement, or L1 beam measurement report result.

[0133] After transmitting a predetermined MAC CE to the current serving cell, the UE may start a predetermined timer (or a new timer) and start monitoring the PDCCH transmitted from the reported / instructed new target cell. For example, the UE may start a predetermined timer after transmitting a predetermined MAC CE and control to monitor the PDCCH until the predetermined timer expires.

[0134] <<LTM Completion>> If the UE detects a DCI format (e.g., DCI format 1_0 / 0_0, etc.) to which the C-RNTI is applied from the target cell before a predetermined timer expires, the UE may determine that the CLTM is successful (or that the CLTM is completed). Otherwise, the UE may determine that the CLTM is unsuccessful.

[0135] [Conditional LTM Operation Example 5] Figure 8 is a diagram showing a fifth example of conditional LTM operation. While Figure 8 shows the steps of LTM preparation (e.g., LTM preparation), early synchronization (e.g., early sync), LTM execution (e.g., LTM execution), and LTM completion (e.g., LTM completion) as the CLTM operation, the LTM steps are not limited to these. Some steps (or operations included in steps) may be omitted, the order of operations included in some steps may be reversed with other operations included in other steps, or other steps (or other operations) may be added. For example, at least some of the processes shown in Figures 3 to 7 may be added.

[0136] <<LTM Preparation>> In LTM preparation, a UE connected to a serving cell via RRC (e.g., a UE in RRC_CONNECTED) transmits a measurement report. The measurement report may be an L3 measurement report. The base station (or source base station / serving cell) determines whether to perform LTM based on the measurement report transmitted from the UE.

[0137] The base station (Source gNB) sends an RRC reconfiguration message to the UE, including LTM candidate cell configurations for one or more candidate cells. The UE saves the LTM candidate cell configurations and sends an RRC reconfiguration complete message to the gNB. The base station (Source gNB) sends signaling including the LTM candidate cell configurations to the base station (Candidate gNB) of the candidate cell.

[0138] Early sync: The UE performs early synchronization (e.g., early sync) with a candidate cell. DL / UL early synchronization with a candidate cell may be performed by the UE after RRC configuration (e.g., RRC reconfiguration) of the LTM candidate cell.

[0139] LTM Execution: The UE evaluates whether the event is met, and if so, transmits a second UL signal (e.g., UL Cell Switch Command, Event Trigger Report) to the base station (Source gNB) indicating the possibility of a cell switch using the RS / TCI state of the candidate cell. The base station (Source gNB) then transmits signaling including the target cell ID and TCI state ID to the base station (Candidate gNB) of the candidate cell.

[0140] Since the UE can transmit an UL signal notifying the possibility of a cell switch before the cell switch decision, there is no need to transmit an UL signal when the LTM cell switch decision is made. In other words, it is possible to avoid the gNB being unable to receive the UL signal when the UE is at the cell edge. The base station (Source gNB) can forward the above signaling, including the target cell ID and TCI state ID, to the base station (Candidate gNB) (target gNB) before the cell switch decision is made, so that the target gNB can quickly secure resources for the UE. Note that in Rel8 LTM, this signaling is forwarded when the LTM cell switch decision is made.

[0141] The UE evaluates whether a second event is met, and if so, decides to perform an LTM cell switch. The second event may be the same as the first event or may be different. This is to avoid the ping-pong problem. For example, the UE may decide to perform an LTM cell switch and perform the cell switch procedure when the event is met for a predetermined time, or when all events are met within a predetermined time.

[0142] The UE applies the target cell configuration, and the UE, the base station (Source gNB), and the base station (Candidate gNB) (Target gNB) perform a cell switch procedure.

[0143] The event for transmitting the first UL signal and the event for transmitting the second UL signal may be the same or different, and the event for transmitting the first UL signal and the condition for performing the cell switch procedure after transmitting the second UL signal may be the same.

[0144] In the present disclosure, the UE determines whether to perform a cell switch and the target cell to switch to, so that the cell switch can be performed more quickly than when the base station makes the decision.

[0145] (CSI Reporting) In NR, a UE measures the channel state using a predetermined reference signal (or a resource for the reference signal) and feeds back (reports) channel state information (CSI) to a base station.

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

[0147] The CSI-RS resource may include at least one of a non-zero power (NZP) CSI-RS and a CSI-Interference Management (IM). An SS / PBCH block is a block including a synchronization signal (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)) and a PBCH (and corresponding DMRS), and may be referred to as an SS block (SSB). An SSB index may be assigned to the time position of the SSB within a half-frame.

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

[0149] The CSI may have multiple parts. A first part of the CSI (CSI Part 1) may include information with a relatively small number of bits (e.g., RI). A second part of the CSI (CSI Part 2) may include information with a relatively large number of bits (e.g., CQI), such as information determined based on CSI Part 1.

[0150] As CSI feedback methods, (1) periodic CSI (P-CSI) reporting, (2) aperiodic CSI (A(AP)-CSI) reporting, and (3) semi-persistent (semi-persistent, semi-persistent) CSI reporting (Semi-Persistent CSI: SP-CSI) reporting are being considered.

[0151] The UE may be notified of information related to CSI reporting (which may be referred to as CSI reporting configuration information) using higher layer signaling, physical layer signaling (e.g., Downlink Control Information (DCI)), or a combination thereof. The CSI reporting configuration information may be configured, for example, using the RRC information element "CSI-ReportConfig."

[0152] The CSI reporting configuration information may include, for example, information regarding a reporting period, an offset, etc., which may be expressed in a predetermined time unit (slot unit, subframe unit, symbol unit, etc.). The CSI reporting configuration information may include a configuration ID (CSI-ReportConfigId). The configuration ID may identify parameters such as the type of CSI reporting method (whether it is SP-CSI, etc.), the reporting period, etc. The CSI reporting configuration information may include information (CSI-ResourceConfigId) indicating which signal (or which signal resource) is used to report the measured CSI.

[0153] (TCI, spatial relationship, QCL) In NR, it is considered to control the reception processing (e.g., at least one of reception, demapping, demodulation, and decoding) and transmission processing (e.g., at least one of transmission, mapping, precoding, modulation, and encoding) in a UE of at least one of a signal and a channel (referred to as a signal / channel) based on a transmission configuration indication state (TCI state).

[0154] The TCI state may represent that which is applied to a downlink signal / channel, and the equivalent of the TCI state that is applied to an uplink signal / channel may be expressed as a spatial relation.

[0155] The TCI state is information about the Quasi-Co-Location (QCL) of signals / channels, and may also be called spatial reception parameters, spatial relation information, etc. The TCI state may be configured in the UE for each channel or signal.

[0156] The QCL is an index indicating the statistical properties of signals / channels. For example, if a signal / channel has a QCL relationship with another signal / channel, it may mean that it can be assumed that at least one of a Doppler shift, a Doppler spread, an average delay, a delay spread, and a spatial parameter (e.g., a spatial Rx parameter) is the same between these different signals / channels (i.e., the signals / channels have a QCL with respect to at least one of these).

[0157] The spatial reception parameters may correspond to a reception beam (e.g., a reception analog beam) of the UE, and the beam may be identified based on a spatial QCL. The QCL (or at least one element of the QCL) in the present disclosure may be replaced with sQCL (spatial QCL).

[0158] A plurality of types (QCL types) of QCL may be defined. For example, four QCL types A to D may be provided, each having different parameters (or parameter sets) that can be assumed to be the same. The parameters (which may be referred to as QCL parameters) are as follows: QCL type A (QCL-A): Doppler shift, Doppler spread, mean delay, and delay spread QCL type B (QCL-B): Doppler shift and Doppler spread QCL type C (QCL-C): Doppler shift and mean delay QCL type D (QCL-D): Spatial reception parameters.

[0159] The QCL information as shown in the above QCL types A to D may be called a QCL property.

[0160] The UE's assumption that a Control Resource Set (CORESET), channel, or reference signal has a specific QCL (e.g., QCL type D) relationship with another CORESET, channel, or reference signal may be referred to as a QCL assumption.

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

[0162] The TCI state may be, for example, information about the QCL between the channel of interest (in other words, the Reference Signal (RS) for that channel) and another signal (e.g., another RS). The TCI state may be set (indicated) by higher layer signaling, physical layer signaling, or a combination thereof.

[0163] The physical layer signaling may be, for example, Downlink Control Information (DCI).

[0164] The channel for which the TCI state or spatial relationship is set (specified) may be, for example, at least one of a downlink shared channel (Physical Downlink Shared Channel (PDSCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), an uplink shared channel (Physical Uplink Shared Channel (PUSCH)), and an uplink control channel (Physical Uplink Control Channel (PUCCH)).

[0165] Furthermore, the RS that has a QCL relationship with the channel may be, for example, at least one of a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), a sounding reference signal (SRS), a tracking CSI-RS (also called a tracking reference signal (TRS)), and a QCL detection reference signal (also called a QRS).

[0166] An SSB is a signal block including at least one of a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a Physical Broadcast Channel (PBCH). An SSB may also be referred to as an SS / PBCH block.

[0167] An RS of QCL type X in a TCI state may refer to an RS that has a QCL type X relationship with a certain channel / signal (DMRS), and this RS may be called a QCL source of QCL type X in the TCI state.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0192] 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}.

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

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

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

[0196] When a specific event occurs (which in the present disclosure may be interpreted as a specific condition being met / not being met), the UE may report measurement results (e.g., L1-RSRP / L1-SINR) to the NW (e.g., base station).

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

[0198] <<Events for Case 1>> An example of an event for the above-mentioned Case 1 will be described. The event may mean, for example, an event related to a serving cell and an additional cell, or an event related to a beam report including the PCI of the serving cell and the PCI of the additional cell.

[0199] [Option 1] A beam report (e.g., an aperiodic CSI report) may be triggered by reusing one or more existing events of Radio Resource Management (RRM) (e.g., at least one of the following events A2 to A6 and I1). That is, when at least one of the following events A2 to A6 and I1 occurs (when the condition of the event is satisfied), both the RRM report and the CSI report may be triggered, and the UE may transmit both the RRM report and the CSI report.

[0200] In addition, in the present disclosure, the RRM report may be read interchangeably with the L3 measurement report.

[0201] The UE determines whether an event (for example, at least one of the following events A2 to A6 and I1) has occurred (S1). If the result of S1 is YES, the UE transmits an aperiodic CSI report (and an RRM report) (S2). If the result of S1 is NO, the UE terminates the process related to the event-based beam report. Each of the above processes may be repeatedly performed at predetermined intervals.

[0202] In the present disclosure, triggering an aperiodic CSI report and a UE transmitting an aperiodic CSI report may be interchangeable. A CSI report, an L1 beam report, and a beam report may be interchangeable.

[0203] In the following events A2 to A6, the measurement result may be at least one of RSRP (L1-RSRP / L3-RSRP), RSRQ, and SINR (RS-SINR). In the conditions of the following events A2 to A6, "bad" may mean "low" and "good" may mean "high". In the conditions of the following events A2 to A6, SpCell means a special cell and may mean at least one of a Primary Cell (PCell) and a Primary Secondary Cell (PSCell). In the following events A2 to A6 and I1, a parameter corresponding to hysteresis may be added / subtracted from the measurement result. Each threshold may be the same or different. A neighboring cell may be a non-serving cell.

[0204] Event A2: The measurement result of the serving cell is worse than the threshold. Event A3: The measurement result of the neighboring cell (the measurement result plus an offset) is better than the measurement result of the SpCell (the measurement result plus an offset). Event A4: The measurement result of the neighboring cell (the measurement result plus an offset) is better than the threshold. Event A5: The measurement result of the SpCell is worse than the first threshold, and the measurement result of the neighboring cell (the measurement result plus an offset) is better than the second threshold. Event A6: The measurement result of the neighboring cell (the measurement result plus an offset) is better than the measurement result of the serving cell (Secondary Cell (SCell)) (the measurement result plus an offset). Event I1: The interference measurement result is higher than the threshold.

[0205] Option 1 simplifies configuration because the trigger for RRM reporting can be reused as the trigger for beam reporting.

[0206] [Option 2] One or more new events (separate from the events for RRM reporting) may be defined to trigger aperiodic L1 beam reporting (CSI reporting). The events may be similar to the above-mentioned events A2 to A6 and I1 that also apply to triggering RRM reporting, but may differ from any of the events A2 to A6 and I1 (triggering RRM reporting) in at least one of the following options 2-1 to 2-4.

[0207] [Option 2-1] The thresholds may be different, i.e., events A2 to A6 and I1 may be used for L1 beam reporting (CSI reporting) using thresholds different from those for RRM reporting.

[0208] [Option 2-2] The event may be triggered based on the measurement result of the reference signal received power (L1-RSRP) at Layer 1. That is, the comparison may be based on L1-RSRP instead of L3-RSRP. Alternatively, a new filtered L1-RSRP may be applied, whose timescale (period of update / measurement) is between L1-RSRP and L3-RSRP (or the same as L1-RSRP or L3-RSRP). Alternatively, other metrics, such as L1-SINR, L3-RSRQ, etc., may be applied. For example, the following event A2' may be applied as a new event: Event A2': The L1-RSRP measurement result of the serving cell is worse than a threshold.

[0209] [Option 2-3] This may be based on a comparison of measurements at a single beam level, at multiple beam levels (combining independent measurements of multiple beams into a single value), or at a cell level. For example, the following events A4' or A4'' may apply: Event A4': Measurements of one beam from a neighboring cell are better than a threshold. Event A4'': A statistic (e.g., average, sum, etc.) of measurements of multiple beams (e.g., the best X beams) is better than a threshold. X may be fixed or configurable, e.g., by higher layer signaling.

[0210] [Option 2-4] The number of beams that satisfy a condition (e.g., any of events A2 to A6 and I1) may be considered. For example, if X beams satisfy event A4' (if the measurement results of X beams from neighbor cells are better than a threshold), the UE may report CSI.

[0211] Note that examples combining at least two of the above 2-1 to 2-4 may also be applied. For example, A4''' can be considered as an event combining 2-2 and 2-3. Also, A4'''' can be considered as an event combining 2-2, 2-3, and 2-4: Event A4''': The L1-RSRP measurement result of one beam from an adjacent cell is better than the threshold. Event A4''': The L1-RSRP of each of X beams from adjacent cells is better than the threshold.

[0212] According to option 2, CSI reporting can be performed at a higher speed than when using existing RRM reporting events using RRC.

[0213] [Option 3] Any combination of two or more events from Option 1 and Option 2 above may be used to trigger aperiodic L1 beam reporting (CSI reporting).

[0214] An existing event for RRM reporting may be combined with one or more events of option B. For example, a CSI report may be triggered if both event A4 and new event A4''' occur.

[0215] Two or more events in option 2 may be combined. For example, a CSI report may be triggered if both event A2′ and new event A4′″ are met.

[0216] <<Event for Case 2>> A description will be given of an example of an event for the above-mentioned Case 2. The event may mean, for example, an event related to only the serving cell, or an event related to a beam report including only the PCI of the serving cell.

[0217] One or more new events (separate from the events for RRM reporting) may be defined to trigger aperiodic L1 beam reporting (CSI reporting). The event may be at least one of the following events B2 to B6 and K1: Event B2: The measurement result of the current beam is worse than a threshold. Event B3: The measurement result of another beam (the measurement result plus an offset) is better than the measurement result of the current beam (the measurement result plus an offset). Event B4: The measurement result of another beam (the measurement result plus an offset) is better than a threshold. Event B5: The measurement result of the current beam is worse than a first threshold, and the measurement result of another beam (the measurement result plus an offset) is better than a second threshold. Event B6: The measurement result of the current beam (the measurement result plus an offset) is worse than a threshold, and the measurement result of another beam (the measurement result plus an offset) is better than the measurement result of the current beam (the measurement result plus an offset). Event K1: The interference measurement is higher than the threshold.

[0218] Note that the names / codes of events in this disclosure (e.g., A2-A6, B2-B6, I1, K1, etc.) are merely examples and are not limited to these. For example, the name of an event for Case 2 may be the same as the name of the event (numbered) corresponding to Case 1.

[0219] For at least one of the events (events related to Case 1 / Case 2) in the present disclosure, a duration / counter during which the event (condition) is satisfied may be specified. The UE / NW may determine that the condition of each event is satisfied when at least one of the conditions of each of the above events satisfies a condition related to a specific duration / counter. For example, the UE may determine that the condition of the above event B3 is satisfied when the measurement result of another beam is better than the measurement result of the current beam in a 100 ms time window. Furthermore, for example, the UE may determine that the condition of the above event B3 is satisfied when the measurement result of another beam is better than the measurement result of the current beam 10 times per multiple samples.

[0220] In the present disclosure, the "current beam" may refer to, for example, an SSB / CSI-RS that is QCL-related (QCLed) with the PDCCH.

[0221] The PDCCH may be, for example, a PDCCH corresponding to a CORESET determined by a specific rule / higher layer parameter setting, for example, a CORESET of a specific (e.g., lowest / highest) CORESET ID.

[0222] The CSI-RS may be, for example, a periodic / semi-persistent / aperiodic CSI-RS, and the SSB / CSI-RS may be, for example, limited to a periodic CSI-RS / SSB.

[0223] In the present disclosure, the "current beam" may be, for example, an indicated TCI state (joint / DL / UL TCI state) in the current unified TCI state. Also, the "current beam" may be, for example, a QCL source RS (QCL type D / A) related to the current indicated TCI state.

[0224] Also, in the present disclosure, a "current beam" may be, for example, a beam / resource index (e.g., CRI / SSBRI) reported in a particular (e.g., recent / latest) L1-RSRP / L1-SINR.

[0225] In the present disclosure, "other beams" may be, for example, beams / SSB / CSI-RS / TCI states other than the "current beam."

[0226] A set of multiple beams (candidate beam set) may be configured for the UE, and the UE may select / decide on an "other beam" from the set.

[0227] In this disclosure, "worse / better" may mean, for example, lower / higher measurement results (e.g., RSRP / SINR / RSRQ).

[0228] The threshold may be predefined in the specification, configured / indicated / signaled using higher layer signaling (RRC / MAC CE) / DCI, reported by UE capabilities, or a combination thereof. For example, the threshold may be reused from an existing threshold (e.g., a threshold used in RRM / Case 1).

[0229] The offset with respect to the threshold may be predefined in the specification, configured / indicated / signaled using higher layer signaling (RRC / MAC CE) / DCI, reported by UE capabilities, or a combination thereof.

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

[0231] In the present disclosure, the reported beam, the reporting beam, and the UE reporting beam may be read interchangeably.

[0232] (Cell Switch Command (MAC CE) in Rel. 18) The cell switch command sent by the MAC CE may include at least the following information: Information to identify the target cell, Information about the Timing Advance (TA), One joint TCI state index for the target cell or a set of DL / UL TCI state indices for the target cell, Active DL / UL BWPs of the target cell.

[0233] Regarding the presence of beam indication in the cell switch command, the following may be supported for at least some scenarios: There is always a field in the cell switch command indicating one joint TCI state index for the target cell or a set of DL / UL TCI state indices for the target cell. UE behavior with respect to the beam indication field for RACH-based handover scenarios after a cell switch command.

[0234] (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:

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

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

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

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

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

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

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

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

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

[0244] <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:

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

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

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

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

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

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

[0251] <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:

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

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

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

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

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

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

[0258] (Use Cases of UEIBR) In Rel. 19 and later, support for event-based beam reporting (UE-initiated beam reporting (hereinafter referred to as UEIBR)) is being considered. UEIBR can be used for measurement reporting, beam switching, cell switching, etc.

[0259] For example, if a UE moves at a nonlinear speed, it is difficult for the network to accurately predict the UE movement (position change). In addition, cases where potential beam switches occur frequently are also assumed.

[0260] In such a case, when using conventional (existing) CSI reporting (CSI reporting scheduled by the NW), the NW may set the CSI reporting period to be shorter or longer.

[0261] For example, in cases where frequent beam switching occurs (when the UE's moving speed is fast / beam quality fluctuations are large), the NW can configure periodic CSI reporting with a relatively short periodicity.

[0262] On the other hand, in cases where beam switching does not occur frequently (rarely) (when the UE's moving speed is slow / beam quality fluctuations are small), the NW can configure periodic CSI reporting with a relatively long periodicity.

[0263] However, the existing CSI reporting alone cannot adequately handle all cases. For example, in aperiodic cases, switching the reporting configuration by RRC is not very desirable from the viewpoint of efficiency, and as mentioned above, it is currently considered difficult for the network to predict [sudden] speed changes of the UE.

[0264] Therefore, a case where the UE supports both the existing CSI reporting and UEIBR (Alt1 / Alt2), or a case where the UE supports only UEIBR (Alt3) is under consideration. The contents of Alt1 to Alt3 can be exemplified as follows.

[0265] (Alt1) A UE may support both the existing CSI reporting with a relatively short periodicity and UEIBR. In this case, timely reporting (beam reporting applicable to the case where frequent beam switching occurs (case where the UE moving speed is fast / beam quality fluctuations are large)) may be realized by the existing CSI reporting.

[0266] (Alt2) The UE may support both the existing long periodic CSI reporting and UEIBR. In this case, timely reporting (as described above) may be achieved by UEIBR. Also, occasional beam switches may be achieved by the existing CSI reporting.

[0267] Note that the UEIBR may be transmitted periodically multiple times while certain conditions are met.

[0268] (Alt3) The UE may support only UEIBR. For example, in UEIBR, there are multiple events (types) that are satisfied in the low-speed / high-speed cases. In this case, it is assumed that the UE behavior after each event (condition) is satisfied is different. That is, the subsequent UE behavior may change depending on the type of event that is satisfied. For example, while a certain condition is satisfied, the UE may transmit a beam report once or periodically multiple times.

[0269] UEIBR enables timely reporting tailored to specific use cases.

[0270] (Analysis) In the above-described UEIBR, the UE needs to measure many beams to evaluate an event, which is expected to increase the load on the UE.

[0271] In UEIBR, at least L1-RSRP can be supported as a reporting quantity in SSB for intra-cell / inter-cell (mobility) or periodic CSI-RS for beam management.

[0272] The beam report may also include multiple measurements, which may be used as quality metrics to trigger a UEIBR.

[0273] As target RSs, support for semi-persistent / non-periodic CSI-RS as well as periodic CSI-RS is being considered.

[0274] Furthermore, whether or not to support L1-SINR measurement, or as a method for doing so, it may be possible to utilize existing RS / RS combinations (CMR only / CMR+ZP / NZP-IMR, etc.) for existing (e.g., Rel. 16) SINR.

[0275] Furthermore, it is necessary to clarify the method of filtering operation for L1-RSRP.

[0276] Even if existing specifications are used, there is likely to be room for further consideration in terms of application to UEIBR.

[0277] For example, for aperiodic NZP CSI-RS, the UE behavior (eg, termination timing) when the CSI-RS does not satisfy any of the events is unclear.

[0278] In the case of periodic / semi-persistent CSI-RS, the UE operation may be subject to existing specifications.

[0279] In addition, as a UE operation, the UE is expected to perform event evaluation in addition to CSI-RS measurement. If an event is met, the UE needs to transmit a measurement report for the corresponding beam (CSI-RS). The measurement report may include a pair of L1-RSRP / SINR and RS index indicating whether the event is met / not met.

[0280] If these are not clear, it may be impossible to appropriately control UEIBR, making it impossible to achieve communication with lower latency, which may result in suppression of improvements in communication quality / throughput.

[0281] Therefore, the present inventors have studied specific UE operations in UEIBR and have come up with an aspect of the present embodiment.

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

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

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

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

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

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

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

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

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

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

[0292] 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 cell, base station (gNB) within a cell, base station (gNB) of a cell, and base station (gNB) may be interchangeable.

[0293] In the present disclosure, the terms "event," "event condition," and "implementation condition" may be interchangeable. The terms "event condition" and "implementation condition" may refer to conditions for a cell switch. The terms "candidate cell," "target cell," and "base station / gNB of the candidate cell / target cell" may be interchangeable. The term "cell switch" in the present disclosure may refer to a switch of the serving cell (a switch to the target cell).

[0294] In the present disclosure, an event-triggered beam report may be an L1 / L3 beam report. The event-triggered beam report may be a report transmitted when the event condition set by the above-mentioned report configuration (ReportConfigNR) or the condition / event for the above-mentioned conditional LTM (CLTM) is satisfied. The base station may make a decision regarding LTM based on the event-triggered beam report. The terms beam report / report and CSI report may be interchangeable.

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

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

[0297] In the present disclosure, Type 1 beam report and beam report for intra-cell beam switching may be read interchangeably.

[0298] In the present disclosure, Type 2 beam report and inter-cell beam report may be read interchangeably.

[0299] In the present disclosure, Type 2-1 beam report and beam report for inter-cell beam switching may be read interchangeably.

[0300] In the present disclosure, Type 2-2 beam report and beam report for cell switching may be read interchangeably.

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

[0302] In the present disclosure, the terms list and pool may be read interchangeably.

[0303] In the present disclosure, the (new) MAC CE, UCI, cell switch command, beam switch command, beam report MAC CE, and cell switch MAC CE may be read as interchangeable terms.

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

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

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

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

[0308] In this disclosure, ACK may be referred to as a positive acknowledgement, and NACK may be referred to as a negative acknowledgement.

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

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

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

[0312] The contents of this disclosure are also applicable to existing CSI reports.

[0313] In this disclosure, reporting criteria, criteria, time / spatial domain filters, domain filters, etc. may be read interchangeably.

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

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

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

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

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

[0319] In this disclosure, cell-by-cell filtering may refer to spatial domain filters, and beam-by-beam filtering may refer to temporal / spatial domain filters.

[0320] In the present disclosure, NW / BS / gNB may be interpreted interchangeably.

[0321] (Wireless Communication Method) The embodiments of the present disclosure can be broadly divided as follows: First embodiment: Activation of event evaluation Second embodiment: Method for counting active CSI-RSs Each embodiment will be described below based on these.

[0322] The UE may perform beam measurement / reporting (e.g., activating event evaluation / counting active CSI-RS) by applying each embodiment described below. The NW / BS / gNB may provide / send to the UE settings / instructions, etc. for the UE to realize the control. Furthermore, the NW / BS / gNB may perform various controls necessary to receive the beam report / CSI report from the UE.

[0323] The event-based beam reporting of the present disclosure can be applied to any MIMO / mobility scenario after Rel. 19. For example, in the mobility case, the UE may determine the cell to switch to based on the determined current beam.

[0324] In the present disclosure, CSI reports and beam reports may be read interchangeably.

[0325] In the present disclosure, the terms event-based beam reporting (for Rel. 19), event-triggered beam reporting, UE-triggered beam reporting, UE-initiated beam reporting (UEIBR), and beam reporting may be interchangeable.

[0326] In the present disclosure, existing CSI reporting may refer to CSI reporting (beam reporting) other than the event-based beam reporting described above.

[0327] In the present disclosure, the existing CSI report and the CSI report (beam report) scheduled by the NW may be read as interchangeable.

[0328] In addition, in this disclosure, the existing CSI report (beam report) may be referred to as a first CSI report / beam report, whereas the event-based beam report (UEIBR, etc.) for Rel. 19 and later may be referred to as a second CSI report / beam report or a new CSI report / beam report.

[0329] In the present disclosure, QCL Type A and QCL Type D may be read interchangeably.

[0330] In the present disclosure, the active TCI state list, the TCI state, and the active TCI state may be read interchangeably.

[0331] In the present disclosure, the terms TCI state, RS (source RS), beam, and L1-RSRP / SINR may be interchangeable.

[0332] The present disclosure is applicable to each of the MIMO / mobility use cases.

[0333] In the present disclosure, each embodiment / option may be applied alone or in combination with other embodiments / options.

[0334] First Embodiment The first embodiment relates to activation of event evaluation. The first embodiment can be classified into aspects 1-1 and 1-2 depending on the type of measurement RS.

[0335] <<Aspect 1-1>> When periodic CSI-RS / SSB is configured as the measurement RS for UE IBR, the UE may apply at least one of the following Opt1-1 to Opt1-2.

[0336] (Opt1-1) The UE may always evaluate the event associated with the measurement RS.

[0337] (Opt1-2) The UE may start (trigger / activate) event evaluation when it receives a command (MAC CE / DCI) to activate event evaluation. That is, the UE may determine / control the activation of event evaluation based on the reception of the command. The command may be called an activation command for event evaluation.

[0338] The command (MAC CE / DCI) may include at least one of the following information: - A flag (e.g., 1 bit) indicating activation / deactivation of the event (a bit value "0" may mean deactivation and a bit value "1" may mean activation, or vice versa); - Event ID; - CSI reporting configuration ID; - CSI resource configuration ID; - RS index; - Measurement count / actual time required for evaluation.

[0339] The UE may control the timing of ending the evaluation based on at least one of the following Opt2-1 to Opt2-5.

[0340] (Opt2-1) The UE may continue evaluating the [current / evaluating] event until the event (the event to be evaluated or another event different from this) is satisfied, i.e., the UE may terminate / stop the evaluation of a certain event when a specific event is satisfied.

[0341] (Opt2-2) The UE may continue to evaluate an event within a certain time (from the start of evaluation of the event), i.e., the UE may terminate / stop evaluation of an event when a specific event is met.

[0342] The value of the certain time (duration of event evaluation) X may be set / indicated by higher layer signaling / physical layer signaling, may be predefined by a specification, or may be determined according to UE capabilities.

[0343] (Opt2-3) The UE may continue evaluating the event until a predetermined counter meets a threshold. That is, the UE may terminate / stop the event evaluation when the predetermined counter meets a threshold. The predetermined counter may be a counter for event evaluation (e.g., the number of measurements of the RS), and may be set / instructed by higher layer signaling / physical layer signaling, predefined by a specification, or determined according to the UE capability.

[0344] (Opt2-4) The UE may continue evaluating the event until it receives a specific DL signal / channel or transmits a specific UL signal / channel, i.e., the UE may terminate / stop evaluating the event when it receives a specific DL signal / channel or transmits a specific UL signal / channel.

[0345] The particular DL signal / channel may be, for example, a MAC CE (Cell Switch Command) indicating activation / deactivation of a new event evaluation.

[0346] The specific UL signal / channel may be, for example, beam report, MAC CE (cell switch command) for UL.

[0347] (Opt2-5) The UE may continue evaluating events until a predetermined setting related to event evaluation (e.g., a setting related to UEIBR) is released. That is, the UE may terminate / stop the evaluation of events when the setting is released.

[0348] <<Aspect 1-2>> When a semi-persistent / aperiodic CSI-RS is configured as the measurement RS for the UE IBR, the UE may control event evaluation by applying the following Opt3.

[0349] (Opt3) When the UE receives the above mentioned activation command (MAC CE / DCI), it may start evaluating the event if the activation command triggers semi-persistent / aperiodic CSI-RS.

[0350] In this case, existing signaling may be utilized to trigger semi-persistent / aperiodic CSI-RS.

[0351] For example, if multiple events are associated with a CSI-RS, the activation command may include an event ID or a CSI-RS configuration ID.

[0352] The UE may control the timing of ending the evaluation based on at least one of the following Opt3-1 to Opt3-5.

[0353] (Opt3-1) The UE may continue evaluating the [current / evaluating] event until the event (the event to be evaluated or another event different from this) is satisfied, i.e., the UE may terminate / stop the evaluation of a certain event when a specific event is satisfied.

[0354] (Opt3-2) The UE may continue to evaluate an event within a certain time (from the start of evaluation of the event), i.e., the UE may terminate / stop evaluation of an event when a specific event is met.

[0355] The value of the certain time (duration of event evaluation) X may be set / indicated by higher layer signaling / physical layer signaling, may be predefined by a specification, or may be determined according to UE capabilities.

[0356] (Opt3-3) The UE may continue evaluating the event until a predetermined counter meets a threshold. That is, the UE may terminate / stop the event evaluation when the predetermined counter meets a threshold. The predetermined counter may be a counter for event evaluation (e.g., the number of measurements of the RS), and may be set / instructed by higher layer signaling / physical layer signaling, predefined by a specification, or determined according to the UE capability.

[0357] (Opt3-4) The UE may continue evaluating the event until it receives a specific DL signal / channel or transmits a specific UL signal / channel, i.e., the UE may terminate / stop evaluating the event when it receives a specific DL signal / channel or transmits a specific UL signal / channel.

[0358] The particular DL signal / channel may be, for example, a MAC CE (Cell Switch Command) indicating activation / deactivation of a new event evaluation.

[0359] The specific UL signal / channel may be, for example, beam report, MAC CE (cell switch command) for UL.

[0360] (Opt3-5) The UE may continue evaluating the event until the semi-persistent CSI-RS is deactivated or the aperiodic CSI-RS is terminated, i.e., the UE may terminate / stop evaluating the event once the semi-persistent CSI-RS is deactivated or the aperiodic CSI-RS is terminated.

[0361] (Note) In the case of aperiodic CSI-RS, the scheduled PUSCH may include a beam report associated with the aperiodic CSI-RS, which may include information about non-candidate beams when the aperiodic CSI-RS does not satisfy the event.

[0362] (Modification) Even if an aperiodic CSI-RS is configured as the measurement RS for the UEIBR, the beam report resource may follow the configuration of the UEIBR. That is, the UE may preferentially apply the configuration of the UEIBR to the beam report resource configuration, regardless of the type of CSI-RS (periodic / aperiodic / semi-persistent).

[0363] In this case, the PUSCH [configuration] for aperiodic CSI reporting is not for UE IBR but is a configuration for aperiodic CSI reporting that may be configured by the NW, i.e., the measurement resources and the reporting resources may be different (but not necessarily the same).

[0364] The activation commands of the present disclosure may be utilized to direct the activation / deactivation of a candidate cell.

[0365] According to this embodiment, the UE can appropriately control the activation of event evaluation depending on the type of measurement RS.

[0366] Second Embodiment The second embodiment relates to a method for counting active CSI-RSs.

[0367] In existing specifications, a UE is not expected to be configured / instructed to have more active CSI-RS ports / CSI-RS resources than its reported capabilities.

[0368] As mentioned above, in UEIBR, multiple measurement results may be included in the beam report, so it is necessary to clarify how to count active CSI-RS in UEIBR.

[0369] Therefore, the following counting method is proposed: The UE may apply at least one of the following options 1 to 6 to control the counting of active CSI-RS.

[0370] <<Option 1>> If a CSI-RS is measured as the current beam for event evaluation for UE IBR, the UE may count the CSI-RS (measured as the current beam for event evaluation) as an active CSI-RS according to at least one of the following Options Opt1-1 to Opt1-5. Options Opt1-1 to Opt1-5 may apply to periodic / aperiodic / semi-persistent CSI-RS.

[0371] (Opt1-1) The UE may always count the CSI-RS as an active CSI-RS. This option is useful for periodic CSI-RS.

[0372] (Opt1-2) After receiving the above-mentioned activation command (MAC CE / DCI), the UE may count as active CSI-RS the CSI-RS measured within a certain time (e.g., X symbols / slots / ms) or a predetermined number of times. This option is useful for aperiodic / semi-persistent CSI-RS.

[0373] Note that the certain time X / predetermined number of times for measurement (number of measurements) may be set / indicated by higher layer signaling / physical layer signaling, may be predefined by specifications, or may be determined according to UE capabilities.

[0374] (Opt1-3) After receiving the above-mentioned activation command (MAC CE / DCI), the UE may count the semi-persistent CSI-RS as an active CSI-RS until the semi-persistent CSI-RS is deactivated or the aperiodic CSI-RS is terminated. This option is useful for aperiodic / semi-persistent CSI-RS.

[0375] (Opt1-4) The UE may count a target CSI-RS as an active CSI-RS until an event for the target CSI-RS is met.

[0376] (Opt1-5) After the UE meets the event for the target CSI-RS, it may count the CSI-RS as an active CSI-RS.

[0377] <<Option 2>> When a CSI-RS is measured as the current beam for event evaluation for UE IBR, the UE may not count the CSI-RS (measured as the current beam for event evaluation) as an active CSI-RS according to at least one of the following Options 2-1 to 2-2. Options 2-1 to 2-2 may be applied to periodic / aperiodic / semi-persistent CSI-RS.

[0378] (Opt2-1) If a CSI-RS is not transmitted from the NW to the UE, the UE may not count the CSI-RS as an active CSI-RS. This option is useful for aperiodic / semi-persistent CSI-RS.

[0379] (Opt2-2) If the event for the target CSI-RS is not met, the UE may not count the CSI-RS as an active CSI-RS.

[0380] <<Option 3>> When a CSI-RS is measured as a new beam for event evaluation for UE IBR, the UE may count the CSI-RS (measured as a new beam for event evaluation) as an active CSI-RS according to at least one of Opt1-1 to Opt1-5 described above. Option 3 may be applied to periodic / aperiodic / semi-persistent CSI-RS.

[0381] <<Option 4>> When a CSI-RS is measured as a new beam for event evaluation for UE IBR, the UE may not count the CSI-RS (measured as a new beam for event evaluation) as an active CSI-RS according to at least one of Options 2-1 to 2-2 described above. The options may be applied to periodic / aperiodic / semi-persistent CSI-RS.

[0382] Incidentally, whether a CSI-RS is counted as an active CSI-RS depends on the CSI-RS associated with an existing CSI report, or may be the same as the CSI-RS configured for an existing CSI report, i.e., both an existing CSI report and a UEIBR may be configured for a certain CSI-RS.

[0383] Therefore, in consideration of the case where the existing CSI reporting and UE IBR are configured for the CSI-RS, the following options 5 and 6 are proposed: Figures 9A and 9B are diagrams showing examples of counting active CSI-RSs.

[0384] <<Option 5>> If a CSI-RS is configured with a setting other than UEIBR (e.g., existing CSI reporting) in addition to UEIBR (when settings other than UEIBR and UEIBR are applied to the same CSI-RS), the UE may count the CSI-RS as one active CSI-RS.

[0385] For example, as shown in FIG. 9A, if CSI-RS #1 is configured for UE IBR and CSI-RS #1 is configured for existing CSI reporting (i.e., if the same CSI-RS #1 is configured for UE IBR and existing CSI reporting), the active CSI-RS may be counted as one as a result of being counted in common between the different configurations.

[0386] <<Option 6>> If a CSI-RS is configured with a setting other than UEIBR (e.g., existing CSI reporting) in addition to UEIBR (when a setting other than UEIBR and UEIBR is applied to the same CSI-RS), the UE may count the CSI-RS separately as an active CSI-RS [for each different setting].

[0387] For example, as shown in FIG. 9B, if CSI-RS #1 is configured for UE IBR and CSI-RS #2 is configured for existing CSI reporting, the active CSI-RS may be counted as two, counted for each configuration.

[0388] In the present disclosure, the maximum number of active CSI-RSs may be set / indicated by higher layer signaling / physical layer signaling, may be predefined by a specification, may be determined according to UE capabilities, or may be set / indicated individually for each UE.

[0389] According to this embodiment, the UE can appropriately control the count of active CSI-RS.

[0390] <<Modification>> The counting of active CSI-RSs in the second embodiment can also be applied to counting the number of occupied CSI processing units (CPUs). In this case, one or more active CSI-RSs may be interpreted as one or more CPU occupied numbers.

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

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

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

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

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

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

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

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

[0399] <<Regarding Application of Each Embodiment>> In a UE / BS, specific (one or more) processes / operations / controls / assumptions / information for at least one of the above-mentioned 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.

[0400] The specific UE capability may indicate at least one of the following: - Supporting the specific process / operation / control / assumption / information; - Supporting application of CLTM; - Supporting event-triggered beam reporting in LTM; - Supporting setting of implementation conditions per candidate cell; - Supporting RACH-less procedure in CLTM; - The maximum number of TCI state IDs, RS IDs, and L1-RSRPs included in one MAC CE for the first / second UL signal; - Supporting MAC CEs for the first / second UL signal; - Supporting activation of TCI states of candidate cells by MAC CE; - The maximum number of candidate cell IDs included in one MAC CE; - The maximum number of TCI state IDs corresponding to one candidate cell ID included in a MAC CE; - The number of supported active TCI states; - The number of L1-RSRPs / SINRs for calculating the average value. Value of X for L1-RSRP / SINR selection. Supporting event evaluation. Maximum number of supported active CSI-RS.

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

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

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

[0404] (Supplementary Notes) The following inventions are supplementary notes regarding the first embodiment of the present disclosure. [Supplementary Note 1] A terminal comprising: a receiver that receives an activation command for event evaluation in a UE-initiated beam report (UEIBR); and a controller that controls triggering of the event evaluation based on the activation command. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein the controller controls the event evaluation according to a type of a channel state information reference signal (CSI-RS) that is set as a reference signal (RS) to be measured. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein the activation command includes at least one of a flag indicating activation or deactivation of an event, an event ID, a CSI reporting configuration ID, a CSI resource configuration ID, an RS index, the number of measurements, and a time required for evaluation. [Supplementary Note 4] When a periodic, aperiodic, or semi-persistent channel state information reference signal (CSI-RS) is set as the reference signal (RS) to be measured, the control unit controls the end timing of the event evaluation according to a specific condition. The terminal according to any one of Supplementary Note 1 to Supplementary Note 3.

[0405] (Supplementary Notes) The following inventions are supplemented with respect to the second embodiment of the present disclosure. [Supplementary Note 1] A terminal having: a receiver that receives a configuration related to measurement of a channel state information reference signal (CSI-RS) for event evaluation in a UE-initiated beam report (UEIBR); and a controller that controls counting of active CSI-RSs based on the configuration. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein, when the CSI-RS is measured as a current or a new beam, the controller controls counting of the active CSI-RSs according to a specific condition. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein, after the receiver receives an activation command for event evaluation, the controller continues counting the active CSI-RSs for a certain period of time or until the target CSI-RS is deactivated or terminated. [Supplementary Note 4] When both the UEIBR setting and the CSI reporting setting scheduled by the base station are configured, the control unit counts the active CSI-RS commonly between the settings or for each setting. The terminal according to any one of Supplementary Note 1 to Supplementary Note 3.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0453] In the present disclosure, the base station 10 may be a source gNB, a target gNB (a gNB of a target cell), or a candidate gNB (a gNB of a candidate cell).

[0454] The transceiver 120 may transmit an activation command for event evaluation in a UE-initiated beam report (UEIBR). The controller 110 may control generation of the activation command for the terminal to control triggering of the event evaluation.

[0455] The transceiver 120 may transmit a configuration related to measurement of a channel state information reference signal (CSI-RS) for event evaluation in a UE-initiated beam report (UEIBR). The controller 110 may control generation of the configuration for controlling the counting of active CSI-RS by the terminal.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0474] The transceiver unit 220 may perform at least one of the processes of the transmitter / receiver unit in any of the above appendices.

[0475] The control unit 210 may execute at least one of the processes of any of the control units described above.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0574] 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 an activation command for event evaluation in a UE-initiated beam report (UEIBR); and a control unit that controls the triggering of the event evaluation based on the activation command.

2. The terminal according to claim 1, wherein the control unit controls the event evaluation according to the type of channel state information reference signal (CSI-RS) set as the reference signal (RS) to be measured.

3. The terminal according to claim 1, wherein the activation command includes at least one of a flag indicating activation or deactivation of an event, an event ID, a CSI reporting configuration ID, a CSI resource configuration ID, an RS index, a measurement count, and a time required for evaluation.

4. The terminal of claim 1, wherein when a periodic, aperiodic, or semi-persistent channel state information reference signal (CSI-RS) is set as the reference signal (RS) to be measured, the control unit controls the end timing of the event evaluation according to specific conditions.

5. A wireless communication method for a terminal, comprising: receiving an activation command for event evaluation in a UE-initiated beam report (UEIBR); and controlling the triggering of the event evaluation based on the activation command.

6. A base station having: a transmitting unit that transmits an activation command for event evaluation in a UE-initiated beam report (UEIBR); and a control unit that controls the generation of the activation command for a terminal to control the triggering of the event evaluation.

Images