Terminal, wireless communication method, and base station

Abstract

A terminal according to one aspect of the present disclosure comprises: a reception unit that receives a DL signal transmitted from one or more candidate cells; and a control unit that performs measurement on the basis of the DL signal. The control unit determines, on the basis of the measurement, a target beam that satisfies at least one of an event and an execution condition used for beam selection or evaluation, and a target cell associated with the target beam, and performs control so as to perform a cell switch to the target cell.

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), the use of L1L2-triggered mobility (LTM) defined in Rel. 18 when a terminal (user terminal, User Equipment (UE)) moves between cells is being considered. If the LTM of Rel. 18 is applied, the interruption time of cell switching can be shortened.

[0006] It is assumed that UE-initiated or UE-triggered LTM (e.g., conditional LTM (CLTM)) will be supported / introduced in Rel. 19 and later. However, sufficient consideration has not been given to how to control cell switching when conditional LTM is supported.

[0007] Therefore, one of the objectives of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately perform cell switching even when UE-initiated or UE-triggered LTM is supported / introduced.

[0008] A terminal according to one aspect of the present disclosure has a receiving unit that receives DL signals transmitted from one or more candidate cells, and a control unit that performs measurements based on the DL signals, and the control unit determines, based on the measurements, a target beam that satisfies at least one of the events and implementation conditions used for beam selection or evaluation, and a target cell associated with the target beam, and controls a cell switch to be performed to the target cell.

[0009] According to one aspect of the present disclosure, cell switching can be performed appropriately even when UE-initiated or UE-triggered LTM is supported / implemented.

[0010]

[0033] Fig. 1A is a diagram showing an example of UE mobility in Rel. 17. Fig. 1B is a diagram showing an example of UE mobility in Rel. 18. Fig. 2 is a diagram showing an example of a procedure for LTM (Long-Term Management) in Rel. 18 (R18 Long-Term Management). Fig. 3 is a diagram showing an example of a cell switch (UE-triggered LTM / UE-initiated LTM / CLTM) according to the first embodiment. Fig. 4 is a diagram showing an example of RRC parameter configuration according to the first embodiment. Figs. 5A to 5C are diagrams showing an example of a layer in which an event / implementation condition is evaluated according to the second embodiment. Fig. 6 is a diagram showing an example of target cell selection according to the second embodiment. Figs. 7A to 7C are diagrams showing an example of a layer in which a target beam is selected according to the second embodiment. Figs. 8A and 8B are diagrams showing other examples of a layer in which a target beam is selected according to the second embodiment. Fig. 9 is a diagram showing another example of a layer in which a target beam is selected according to the second embodiment. Fig. 10 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. Fig. 11 is a diagram showing an example of a configuration of a base station according to an embodiment. Fig. 12 is a diagram illustrating an example of a configuration of a user terminal according to an embodiment. Fig. 13 is a diagram illustrating an example of a hardware configuration 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.

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

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

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

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

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

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

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

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

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

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

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

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

[0023] <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) prepares an LTM candidate (e.g., LTM candidate preparation) based on the measurement report transmitted from the UE.

[0024] The base station performs LTM candidate configuration (e.g., LTM candidate configuration) through RRC (e.g., RRC reconfiguration). Information about candidate cells may be configured in the UE through the LTM candidate configuration.

[0025] <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 measurement (e.g., L1 measurement) or measurement report (e.g., L1 measurement report) transmission in the LTM implementation step.

[0026] <LTM Execution> The UE performs measurements (e.g., L1 measurements) on the configured candidate cells and transmits a measurement report. The measurement report may be an L1 measurement report. The base station (or source base station / serving cell) makes an LTM decision (e.g., an LTM decision) based on the measurement report transmitted from the UE. The base station transmits a cell switch command (e.g., a MAC CE) to the UE.

[0027] The UE may perform a cell switch by a cell switch command (e.g., MAC CE). For example, based on the cell switch command, the UE may detach from a source (e.g., source cell) and apply the target configurations of the target cell.

[0028] After receiving the cell switch command, the UE may perform a random access procedure. For example, if the UE does not have a valid timing advance for the target cell / candidate cell (or a 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 cell / candidate cell (or a destination cell), the UE may not perform the random access procedure (or may omit / skip the random access procedure).

[0029] The UE operation for TA acquisition for the target cell / candidate cell (or a cell to which switching is to be performed) may be performed before receiving the cell switch command. For TA acquisition for the candidate cell, at least one of a plurality of TA acquisition methods, such as TA acquisition using RACH (e.g., RACH-based solutions) and TA acquisition without using RACH (RACH-less solutions), may be supported.

[0030] For TA acquisition using RACH, a method with RAR monitoring and a method without RAR monitoring may be supported. A TA acquisition method may be interpreted as a TA acquisition scheme, a TA acquisition type, or a TA acquisition procedure. In the present disclosure, TA acquisition, TA measurement, TA calculation, TA computation, and TA determination may be interpreted as interchangeable terms.

[0031] For example, the UE may acquire the TA of a candidate cell by transmitting a RACH (e.g., a PDCCH ordered RACH) indicated / triggered by the PDCCH to the candidate cell. Information about the TA of the candidate cell (e.g., a TA value) may be included in a response signal (e.g., an RAR) of the RACH. The RAR may be transmitted from the serving cell or the candidate cell. Alternatively, the TA of the candidate cell may be acquired using a RACH triggered by the UE or a RACH triggered by a higher layer from the network. The PDCCH order may be triggered only by the source cell (or the serving cell).

[0032] Alternatively, the UE may acquire the TA of the candidate cell by transmitting a signal other than the RACH to the candidate cell. Information about the TA of the candidate cell (e.g., the TA value) may be indicated to the UE from the base station. As the signal other than the RACH, for example, the SRS may be applied (e.g., SRS-based TA measurement).

[0033] Alternatively, the UE may measure / calculate / obtain the TA for the candidate cell based on DL signals (e.g., downlink reference signals) transmitted from each cell (e.g., candidate cell / serving cell). A method in which the UE obtains the TA for the candidate cell based on DL signals transmitted from one or more cells may be called UE-based TA measurement.

[0034] In the UE-based TA measurement, the downlink reference signal may be a predetermined DL signal (e.g., a synchronization signal block (e.g., SSB) / CSI-RS, etc.). For example, the UE may measure the difference / difference in reception timing of DL signals from multiple cells (or two cells) and obtain the TA of the candidate cell.

[0035] The multiple cells may include a reference cell (e.g., a serving cell). In this case, the UE may calculate the TA required for the candidate cell based on the reception timing of the reference cell (and the TA value of the reference cell) and the timing difference between the reference cell and the candidate cell. The UE may acquire the TA of the candidate cell using a timing advance command (TAC) transmitted from the serving cell. Note that TA acquisition without using RACH may also be performed before receiving a cell switch command. TA acquisition may also be performed during UL synchronization (e.g., early UL synchronization).

[0036] <LTM Completion> The UE may complete the LTM cell switch procedure by sending a predetermined message to the target cell / candidate cell. The predetermined message may be an RRC reconfiguration complete message (e.g., an RRCReconfigurationComplete message).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0069] (Analysis) In the LTM of existing systems (e.g., Rel. 18), the UE reports an L1 measurement report to the network (e.g., base station), and based on the L1 measurement report, the network determines the target cell / target beam for cell switching in the LTM.

[0070] On the other hand, in LTM of Rel. 19 and later, it is assumed that UE operation (e.g., UE-triggered LTM / UE-initiated LTM) in which the UE performs a cell switch autonomously (or UE-initiated / UE-triggered) is supported. UE-triggered LTM / UE-initiated LTM may also be called conditional LTM (e.g., CLTM). For example, it is assumed that an execution condition (e.g., execution condition) / predetermined event of a candidate cell is set in the UE, and the UE autonomously performs a cell switch to a cell / beam that satisfies the execution condition / predetermined event.

[0071] In this case, it is conceivable that beam-based events may be prescribed / defined / applied as implementation conditions / predetermined events (or events used in implementation conditions) in addition to / instead of L3-based events supported in existing systems. Beam-based events may be interpreted as events used in event-based beam reporting.

[0072] In UE-triggered LTM / UE-led LTM / CLTM, when an event / implementation condition used for beam selection / evaluation is applied, the UE needs to determine not only the target beam but also the target cell (e.g., the cell to switch to).

[0073] However, in the UE-triggered LTM / UE-initiated LTM / CLTM, when events / implementation conditions used for beam selection / evaluation are applied, how the UE determines the target cell becomes an issue. If the target cell is not selected appropriately, communication quality may deteriorate.

[0074] Therefore, the inventors noticed that UE-triggered LTM / UE-led LTM / CLTM support events / implementation conditions used for beam selection / evaluation, and studied the determination of the target cell to come up with one aspect of this embodiment.

[0075] Hereinafter, embodiments of 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.

[0076] (Various Reinterpretations, etc.) 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.

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

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

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

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

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

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

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

[0084] L1 / L2, L1 / L2 signaling, and DCI / MAC CE may be interchangeable. A serving cell may be replaced with a cell transmitting 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.

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

[0086] (Wireless communication method) <First embodiment> The first embodiment describes an example in which a UE controls a cell switch based on a beam / corresponding cell derived from an event (e.g., a beam-based event) used to select / evaluate a beam.

[0087] In the following description, events / implementation conditions in terminal-triggered LTM / terminal-initiated LTM / CLTM will be described using examples, but the present embodiment is not limited thereto. The present embodiment may also be applied to event-triggered L1 measurement reporting.

[0088] In the present disclosure, an event may be read as an execution condition (e.g., an execution condition). In the present disclosure, derivation of a beam / cell may be read as selection or determination of a beam / cell. In the present disclosure, a beam may be read as a reference signal, a reference signal ID, a reference signal resource, a reference signal resource ID, or the like.

[0089] The UE may perform terminal-triggered LTM / terminal-driven LTM / CLTM based on an event (e.g., a beam-based event) / implementation condition used for beam selection / evaluation. For example, the UE may perform measurements on one or more candidate cells, derive a beam that satisfies the event / implementation condition and a candidate cell corresponding to the beam, and perform cell switching as the target beam / target cell.

[0090] The network (e.g., a base station) may notify / configure information (e.g., configuration information) about candidate cells to the UE using RRC parameters. The configuration information may include information about beams corresponding to / associated with each candidate cell.

[0091] The base station may instruct the UE, using the RRC / MAC CE / PDCCH (DCI), whether the base station or the UE derives a target cell based on a target beam that satisfies at least one of an event and an implementation condition. The base station may instruct the UE to apply / configure a cell switch triggered by the terminal based on at least one of an event and an implementation condition.

[0092] The UE may control the cell switch based on at least one of the following options 1-1 to 1-2.

[0093] [Option 1-1] An event (eg, a beam-based event) used to select / evaluate a beam may derive a beam that satisfies the conditions.

[0094] For example, the UE may perform measurements and derive one or more beams that satisfy the conditions in the measurements. The measurements may be L1 measurements.

[0095] In addition, the UE may derive a cell corresponding to the beam from the beam that satisfies the event (or the implementation condition). The UE may perform a cell switch (e.g., UE-triggered LTM / UE-initiated LTM / conditional LTM) using the derived cell as a target cell.

[0096] [Option 1-2] An event (eg, a beam-based event) used to select / evaluate a beam may derive the cell to which the beam corresponds from a beam that satisfies a condition.

[0097] For example, the UE may perform measurements and derive one or more beams that satisfy a condition in the measurements and cells corresponding to the beams. The measurements may be L1 measurements.

[0098] Furthermore, the UE may perform a cell switch (for example, UE-triggered LTM / UE-initiated LTM / conditional LTM) using a cell derived by the event (or implementation condition) as a target cell.

[0099] [UE Operation] Figure 3 illustrates an example of UE operation when performing a cell switch based on a target beam / target cell derived from an event / implementation condition used for beam selection.

[0100] <<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) makes an LTM decision (e.g., an LTM decision) based on the measurement report transmitted from the UE.

[0101] The base station performs LTM candidate configuration (e.g., LTM candidate configuration) through RRC (e.g., RRC reconfiguration). Information about candidate cells may be configured in the UE through the LTM candidate configuration.

[0102] The base station may include information regarding the execution condition (e.g., execution condition) in the RRC and transmit it to the UE. For example, when configuring at least one candidate cell (or target cell) and candidate beam (or target beam), the execution condition (e.g., a condition for satisfying a certain event) may be set separately for each candidate cell / each candidate beam. Alternatively, when configuring at least one candidate cell (or target cell) and candidate beam (or target beam), the execution condition (e.g., a condition for satisfying a certain event) may be set commonly for multiple candidate cells / multiple candidate beams.

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

[0104] Early DL synchronization (e.g., Early DL sync) may be achieved by a TCI state activation / deactivation procedure corresponding to the candidate cell, and early UL synchronization (e.g., Early UL sync) may be achieved by a Timing Advance (TA) acquisition procedure corresponding to the candidate cell.

[0105] Early UL synchronization may be performed after a measurement (e.g., an L1 measurement) or a measurement report (e.g., an L1 measurement report) transmission in the LTM implementation step.

[0106] <<LTM Execution>> The UE may perform measurements (for example, L1 measurements) on configured candidate cells.

[0107] Based on the measurement, a target beam that satisfies the event / implementation condition may be determined, and the UE may derive a target cell from the determined target beam (option 1-1).

[0108] Alternatively, based on the measurement, a target beam that satisfies the event / implementation conditions and a target cell corresponding to the target beam may be determined (option 1-2).

[0109] The UE may decide to perform a cell switch to a target cell determined based on measurements / events / implementation conditions (e.g., LTM cell switch decision). For example, the UE may perform a cell switch to a target beam of the target cell.

[0110] When multiple beams simultaneously satisfy an event / action condition (e.g., beams corresponding to different cells satisfy the event / action condition), the target cell may be selected based on the number of beams that satisfy the event / action condition. For example, a cell with a larger number of beams that satisfy the event / action condition may be preferentially selected as the target cell.

[0111] If the number of beams that satisfy the event / execution condition is the same among multiple cells, the target cell may be determined based on other conditions, such as at least one of a cell index (e.g., the first cell index or the largest cell index is prioritized) and a beam index (e.g., the smallest beam index or the largest beam index is prioritized).

[0112] The UE may notify the network (e.g., base station) of information about the target beam / target cell determined based on measurements / events / implementation conditions. For example, the UE may transmit information about the target beam / target cell using at least one of a MAC CE (e.g., UL LTM cell switch MAC CE), a PUCCH, and a PUSCH.

[0113] The information about the target beam / target cell may be at least one of identification information of the target cell / target beam for which cell switching is to be performed and whether or not the target cell exists (or whether or not cell switching is applied).

[0114] When the UE transmits information regarding the target beam / target cell, the UE may be controlled to perform a cell switch (e.g., detach from the source cell / apply the target cell configuration) after transmitting the information.

[0115] The UE may perform a random access procedure to the selected target cell (RACH-based CLTM), for example, if the UE does not have a valid Timing Advance (TA) for the target cell, it may perform the random access procedure to obtain a TA value for the target cell.

[0116] On the other hand, if the UE has a valid timing advance for the target cell, the random access procedure may not be performed (or the random access procedure may be omitted / skipped). Note that the random access procedure for the target cell may be performed even if the UE has a valid TA for the target cell.

[0117] [Variation] The UE may perform measurements (e.g., L1 measurements) on configured candidate cells and then transmit a measurement report to the network (e.g., base station).

[0118] The base station (or source base station / serving cell) may make a conditional LTM (CLTM) decision based on the measurement report transmitted from the UE. For example, the base station may determine the conditional LTM for one or more target beams / target cells to be evaluated for an event / execution condition. The one or more target beams / target cells to be evaluated for the event / execution condition may be determined based on the measurement report transmitted from the UE.

[0119] The base station may use a predetermined MAC CE to indicate to the UE information about one or more target beams / target cells for conditional LTM (or for which an event / execution condition is to be evaluated), and the predetermined MAC CE may trigger the UE to evaluate the event / execution condition.

[0120] The UE may start evaluating the event / action conditions for the target beam / target cell indicated by the predetermined MAC CE. The UE may derive the target beam / target cell that satisfies the event / action conditions (applying Option 1-1 / Option 1-2 above). If a target cell that satisfies the event / action conditions exists, the UE may detach (e.g., detach) from the 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.

[0121] When a plurality of candidate cells (or candidate target cells) are indicated by a predetermined MAC CE notified from a base station, the UE may determine a specific target beam / target cell to be subjected to mobility / cell switch by taking into consideration an event / implementation condition corresponding to each candidate cell (or an implementation condition common to the plurality of candidate cells). The predetermined MAC CE may indicate an event / implementation condition corresponding to each candidate cell (or an implementation condition common to the plurality of candidate cells).

[0122] The base station may notify the target 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 target beams / target cells for the conditional LTM (or for which an event / execution condition is 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 selected as candidate cells for the conditional LTM (CLTM) (for example, the information may also be notified to candidate cells not selected as candidate cells for the conditional LTM (CLTM)).

[0123] [Derivation of a target cell based on a target beam] In Fig. 3, the case where the UE side derivates a target cell based on a beam that satisfies an event (e.g., a beam-based event) / implementation condition is shown, but this is not limited thereto. The target cell may be derived on the network (e.g., a base station) side.

[0124] A network (e.g., a base station) may instruct whether the network side or the UE side performs the derivation of a target cell based on a beam that satisfies an event (e.g., a beam-based event) / execution condition. The instruction may be configured / instructed to the UE by the network using at least one of RRC, MAC CE, and PDCCH (DCI).

[0125] In order to derive a target cell from a target beam, predetermined higher layer parameter settings and operations may be supported. The UE may derive a target cell based on the predetermined higher layer parameter settings and at least one of the following operation examples 1 and 2.

[0126] An example of setting predetermined higher layer parameters is shown in Fig. 4. The higher layer parameters shown in Fig. 4 may be set by RRC from the network (e.g., base station) to the UE.

[0127] FIG. 4 shows higher layer parameters related to the configuration of conditional LTM (e.g., ConditionalLTMReconfiguration), and channel state information resource configuration (e.g., CSI-ResourceConfig) and channel state information report configuration (e.g., CSI-ReportConfig) included in higher layer parameters related to the configuration of channel state information measurement (e.g., CSI-MeasConfg).

[0128] 4 illustrates a case where a predetermined channel state information reporting configuration ID (e.g., CSI-ReportConfigId) is included in an execution condition (e.g., Execution condition) included in higher layer parameters related to the configuration of conditional LTM. CSI-ReportConfig may include a parameter (e.g., CondTriggerConfig included in ReportConfigType) used to configure an event / execution condition.

[0129] The CSI-ReportConfig includes a CSI-ResouceConfigID, and the CSI-ResourceConfig may include a CSI-ResourceSetList and a CondLTMCandidateIdList corresponding to each CSI-ResourceConfigID. One or more beams may be configured by the CSI-ResourceSetList, and one or more candidate cells may be configured by the CondLTMCandidateIdList. Also, an association between each beam (reference signal index) and a candidate cell may be indicated.

[0130] The upper layer parameters shown in FIG. 4 are an example, and the setting contents of each parameter and the position / location where each parameter is set are not limited to these.

[0131] <<Operation Example #1>> A beam in a channel state information resource set list (e.g., CSI-ResourceSetList) in a channel state information resource configuration ID (e.g., CSI-ResourceConfigId) associated with a channel state information report configuration ID (e.g., CSI-ReportConfigId) set in an upper layer parameter related to an execution condition (Execution condition) may be considered as an applicable beam. Also, a candidate ID (CandidateId) associated with the beam may be considered as an applicable cell.

[0132] The UE may evaluate the event / implementation conditions for the applicable beam.

[0133] The UE may identify the target beam and target cell from the SSB-RI (e.g., a list of SSB-index and CandidateId) of the CSI-ReportConfigId that meets the event / implementation conditions.

[0134] The UE may perform a cell switch to a candidate cell having the ID of the target cell in LTM-candidateId using the TCI state ID associated with the target beam.

[0135] For example, specifically, the following (Pattern 1) steps 1-1 to 1-4 may be applied: Step 1-1: Read LTM-Config>LTM-Candidate and identify the event and candidate beam that each LTM-Candidate references as an execution condition (pre-association of candidate cells and candidate beams is completed), Step 1-2: Evaluate the beam set in CSI-ResourceConfig based on the event set in CSI-ReportConfig, Step 1-3: When the candidate beam that each LTM-Candidate references as an execution condition has completed the event associated with that candidate beam, recognize one of the beams that has completed the event as a target beam, and recognize the LTM-Candidate associated with that target beam as the configuration of the target cell, Step 1-4: Execute LTM for the target beam / target cell.

[0136] <<Operation Example #2>> A beam in a channel state information resource set list (e.g., CSI-ResourceSetList) in a channel state information resource configuration ID (e.g., CSI-ResourceConfigId) associated with a channel state information report configuration ID (e.g., CSI-ReportConfigId) set in an upper layer parameter (Execution condition) related to the execution condition may be considered as a target beam.

[0137] The UE may evaluate the event / implementation conditions for the target beam.

[0138] The UE may consider the candidate ID (CandidateId) associated with the target beam from the SSB-RI (e.g., list of SSB-index and CandidateId) of the CSI-ReportConfigId that meets the event / implementation conditions as the target cell.

[0139] The UE may perform a cell switch to a candidate cell having the ID of the target cell in LTM-candidateId using the TCI state ID associated with the target beam.

[0140] For example, specifically, the following (Pattern 2) steps 2-1 to 2-4 may be applied: Step 2-1: Evaluate the beam set in CSI-ResourceConfig based on the event set in CSI-ReportConfig, Step 2-2: If the evaluated beam satisfies the event, recognize one of the beams that satisfied the event as the target beam, Step 2-3: Recognize the ID of the NHS cell associated with the target beam (for example, the candidate ID associated with the target beam by SSBRI) as the target cell, and recognize the LTM-Candidate associated with the target cell as the target cell configuration, Step 2-4: Execute LTM for the target beam / target cell.

[0141] Each step of Pattern 1 / Pattern 2 may be performed by RRC / MAC CE / PHY (PDCCH / DCI). For example, in Pattern 1, step 1 may be performed by RRC, step 2 by MAC, step 3 by MAC, and step 4 by RRC (Option A). Alternatively, in Pattern 1, step 1 may be performed by RRC, step 2 by MAC, step 3 by RRC, and step 4 by RRC (Option B). Alternatively, in Pattern 1, step 1 may be performed by RRC, step 2 by RRC, step 3 by RRC, and step 4 by RRC (Option C).

[0142] In Option A, the following operations may be performed in each layer. The physical layer (PHY) may send L1meas to the MAC layer for each SSBRI. The MAC layer may evaluate L1meas received from the physical layer based on the CSI-ReportConfig event, select the SSBRI with the highest quality that satisfies the event, and send a set of the associated CSI-ReportConfigID and SSBRI to the RRC layer. The RRC layer may recognize candidate cells and candidate beams from the CSI-ReportConfigID and measurement target beams specified as execution conditions by each LTM-Candidate. After receiving the CSI-ReportConfigID and SSBRI with the event from the MAC layer, a cell switch may be performed using the candidate cell and candidate beam associated with the CSI-ReportConfigID and SSBRI as the target cell and target beam, respectively.

[0143] By applying the first embodiment, the UE can appropriately select a target beam and target cell even when performing a cell switch (e.g., UE-triggered LTM / UE-initiated LTM / conditional LTM) based on an event / implementation condition used for beam selection.

[0144] Second Embodiment The second embodiment relates to a layer where an event / execution condition is evaluated (or beam selection / cell selection). The second embodiment may be applied in combination with the first embodiment (e.g., Option 1-1 / Option 1-2).

[0145] The evaluation of the event (e.g., beam-based event) / implementation condition may be performed in at least one of the PHY layer, the MAC layer, and the RRC layer. The UE may evaluate the event / implementation condition based on beam measurements (e.g., L1 measurements) in at least one of the PHY layer, the MAC layer, and the RRC layer (see FIGS. 5A-C).

[0146] [Evaluation at the Physical Layer] When an event (hereinafter also referred to as a beam event) / implementation condition is evaluated at the physical layer (see FIG. 5A), a beam satisfying the beam event / implementation condition may be derived at the physical layer and instructed / transmitted to the MAC layer and the RRC layer. Based on the beam derived at the physical layer, a corresponding cell (e.g., a target cell) may be selected at the RRC layer.

[0147] In the present disclosure, a beam event may be triggered by a measurement (e.g., an L1 measurement). A beam event may be interpreted as a new event at the beam level. Cell selection may refer to the operation of identifying a target cell from a target beam.

[0148] 5A shows a case where the UE performs beam measurements on beams #A, #B, and #C corresponding to cell #1, beams #D, #E, and #F corresponding to cell #2, and beams #G and #H corresponding to cell #3, and evaluates beam events / implementation conditions in the physical layer based on the beam measurements. Here, the case where beams #A and #B corresponding to cell #1 satisfy the beam event / implementation conditions is shown by the evaluation of the beam events / implementation conditions in the physical layer.

[0149] Beams #A and #B that satisfy the beam event / implementation conditions may be instructed / transmitted from the physical layer via the MAC layer to the RRC layer, and cell #1 corresponding to beams #A and #B may be selected in the RRC layer.

[0150] [Evaluation at MAC Layer] When the evaluation of beam events / execution conditions is performed at the MAC layer (see FIG. 5B), a beam that satisfies the beam event / execution condition may be derived at the MAC layer and indicated / transmitted to the RRC layer. Based on the beam derived at the MAC layer, a corresponding cell (e.g., a target cell) may be selected at the RRC layer.

[0151] 5B shows a case where the UE performs beam measurements on beams #A, #B, #C corresponding to cell #1, beams #D, #E, #F corresponding to cell #2, and beams #G, #H corresponding to cell #3, and evaluates beam events / implementation conditions in the MAC layer based on the beam measurements. Here, the case where beams #A and #B corresponding to cell #1 satisfy the beam event / implementation conditions is shown by the evaluation of the beam events / implementation conditions in the MAC layer.

[0152] Beams #A and #B that satisfy the beam event / implementation conditions may be instructed / transmitted from the MAC layer to the RRC layer, and cell #1 corresponding to beams #A and #B may be selected in the RRC layer.

[0153] [Evaluation at RRC Layer] When the evaluation of beam events / execution conditions is performed at the RRC layer (see FIG. 5C), a beam that satisfies the beam event / execution condition may be derived at the RRC layer. Based on the beam derived at the RRC layer, a corresponding cell (e.g., a target cell) may be selected at the RRC layer.

[0154] 5C shows a case where the UE performs beam measurements on beams #A, #B, and #C corresponding to cell #1, beams #D, #E, and #F corresponding to cell #2, and beams #G and #H corresponding to cell #3, and evaluates beam events / implementation conditions in the RRC layer based on the beam measurements. Here, the case where beams #A and #B corresponding to cell #1 satisfy the beam event / implementation conditions as a result of evaluation of the beam events / implementation conditions in the RRC layer is shown. Also, cell #1 corresponding to beams #A and #B may be selected in the RRC layer.

[0155] [When Multiple Beams / Multiple Cells Satisfy the Event] When multiple beams (e.g., multiple beams corresponding to different cells) satisfy the beam event / execution condition, the target cell may be selected based on the number of beams that satisfy the beam event / execution condition. For example, when multiple beams satisfy the beam event / execution condition and each beam is associated with a different cell, the cell with the largest number of beams that satisfy the beam event / execution condition may be selected as the target cell.

[0156] For example, a cell with a large number of beams that satisfy the beam event / implementation condition may be preferentially selected as the target cell (see Figure 6). Figure 6 shows a case where the beam event / implementation condition is evaluated in the MAC layer, and beams #A and #B corresponding to cell #1 and beam #E corresponding to cell #2 satisfy the beam event / implementation condition as a result of the evaluation of the beam event / implementation condition in the MAC layer.

[0157] Beams #A, #B, and #E that satisfy the beam event / implementation condition may be instructed / transmitted from the MAC layer to the RRC layer, and a cell may be selected in the RRC layer. For example, cell #1 with a large number of beams that satisfy the beam event / implementation condition may be selected as the target cell.

[0158] Figure 6 shows a case where the evaluation of beam events / implementation conditions is performed at the MAC layer, but even when the evaluation of beam events / implementation conditions is performed at the physical layer or RRC layer, cell selection may be based on the number of beams that satisfy the beam event / implementation conditions.

[0159] If the number of beams that satisfy the event / execution condition is the same among multiple cells, the target cell may be determined based on other conditions, such as at least one of a cell index (e.g., the first cell index or the largest cell index is prioritized) and a beam index (e.g., the smallest beam index or the largest beam index is prioritized).

[0160] The selection of the target beam based on the evaluation of beam measurements / events (e.g., beam-based events) / implementation conditions may be performed in at least one of the PHY layer, the MAC layer, and the RRC layer. The UE may perform the target beam selection in at least one of the PHY layer, the MAC layer, and the RRC layer.

[0161] 7A-C show an example of beam selection when beam event / execution condition evaluation is performed at the physical layer.

[0162] [Beam Selection at RRC Layer] Evaluation of beam events / implementation conditions may be performed at the physical layer and target beam selection may be performed at the RRC layer (see Figure 7A).

[0163] Figure 7A shows a case where beams #A and #B corresponding to cell #1 satisfy the beam event / implementation conditions based on evaluation of the beam event / implementation conditions in the physical layer.

[0164] Beams #A and #B that satisfy the beam event / execution condition are instructed / transmitted from the physical layer to the RRC layer via the MAC layer, and cell #1 (corresponding to the target cell) and beam #B (corresponding to the target beam) may be selected in the RRC layer. The target beam may be selected based on predetermined conditions (e.g., at least one of beam quality, received power, and beam index).

[0165] Beam Selection at the MAC Layer Evaluation of beam events / implementation conditions may be performed at the physical layer and target beam selection may be performed at the MAC layer (see FIG. 7B).

[0166] Figure 7B shows a case where beams #A and #B corresponding to cell #1 satisfy the beam event / implementation conditions based on evaluation of the beam event / implementation conditions in the physical layer.

[0167] Beams #A and #B that satisfy the beam event / execution conditions may be instructed / transmitted from the physical layer to the MAC layer, and beam #B (corresponding to the target beam) may be selected in the MAC layer. Beam #B selected in the MAC layer may be instructed / transmitted to the RRC layer, and cell #1 (corresponding to the target cell) corresponding to beam #B (corresponding to the target beam) may be selected in the RRC layer.

[0168] Beam Selection at the Physical Layer Evaluation of beam events / execution conditions may occur at the physical layer, and target beam selection may occur at the physical layer (see FIG. 7C).

[0169] In Figure 7C, beam #B (corresponding to the target beam) may be selected by evaluating beam events / execution conditions in the physical layer. Beam #B selected in the physical layer may be indicated / transmitted to the RRC layer via the MAC layer, and cell #1 (corresponding to the target cell) corresponding to beam #B (corresponding to the target beam) may be selected in the RRC layer.

[0170] 8A and 8B show an example of beam selection when beam event / implementation condition evaluation is performed at the MAC layer.

[0171] [Beam Selection at RRC Layer] Evaluation of beam events / implementation conditions may be performed at the MAC layer and target beam selection may be performed at the RRC layer (see Figure 8A).

[0172] Figure 8A shows a case where beams #A and #B corresponding to cell #1 satisfy the beam event / implementation conditions based on evaluation of the beam event / implementation conditions in the MAC layer.

[0173] Beams #A and #B that satisfy the beam event / execution condition may be instructed / transmitted from the MAC layer to the RRC layer, and cell #1 (corresponding to the target cell) and beam #B (corresponding to the target beam) may be selected in the RRC layer. The target beam may be selected based on predetermined conditions (e.g., at least one of beam quality, received power, and beam index).

[0174] [Beam Selection at MAC Layer] Evaluation of beam events / execution conditions may be performed at the MAC layer, and target beam selection may also be performed at the MAC layer (see FIG. 8B).

[0175] In Figure 8B, beam #B (corresponding to the target beam) may be selected by evaluation of beam events / implementation conditions at the MAC layer.

[0176] Beam #B selected in the MAC layer may be instructed / transmitted to the RRC layer, and cell #1 (corresponding to the target cell) corresponding to beam #B (corresponding to the target beam) may be selected in the RRC layer.

[0177] Figure 9 shows an example of beam selection when evaluation of beam events / implementation conditions is performed at the RRC layer.

[0178] [Beam Selection at RRC Layer] Evaluation of beam events / implementation conditions may be performed at the RRC layer, and target beam selection may also be performed at the RRC layer (see Figure 9).

[0179] In Figure 9, beam #B (corresponding to the target beam) may be selected by evaluating beam events / execution conditions in the RRC layer. Furthermore, cell #1 (corresponding to the target cell) corresponding to beam #B (corresponding to the target beam) may be selected in the RRC layer.

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

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

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

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

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

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

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

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

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

[0189] The specific UE capability may indicate at least one of the following: - Supporting the specific processing / operation / control / assumption / information (e.g., UE-triggered LTM / UE-initiated LTM / CLTM); - Supporting UE-triggered LTM / UE-initiated LTM / CLTM; - Supporting beam-based events / implementation conditions.

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

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

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

[0193] (Supplementary Notes) The following inventions are supplemented with respect to one embodiment of the present disclosure. [Supplementary Note 1] A terminal including: a receiving unit that receives DL signals transmitted from one or more candidate cells; and a control unit that performs measurements based on the DL signals, wherein the control unit determines, based on the measurements, a target beam that satisfies at least one of an event and an implementation condition used for beam selection or evaluation, and a target cell associated with the target beam, and controls to perform a cell switch to the target cell. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein, when multiple beams corresponding to different cells satisfy at least one of the event and the implementation condition, the control unit determines the target cell based on the number of beams corresponding to each cell in the multiple beams. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein the control unit controls to report information regarding at least one of the target beam and the target cell determined based on at least one of the event and the implementation condition. [Supplementary Note 4] The terminal according to any one of Supplementary Notes 1 to 3, wherein the control unit selects a target beam based on at least one of the event and the implementation condition, and selects a target cell based on the target beam, in different layers.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0241] The transceiver 120 may transmit information about one or more candidate cells and information about at least one of an event and an implementation condition used for selecting or evaluating a beam. The information about the candidate cells may be configuration information about the candidate cells (e.g., predetermined RRC parameters about the candidate cells).

[0242] The control unit 110 may also control the terminal to select a target cell based on a target beam that satisfies at least one of an event and an implementation condition, or to instruct the terminal to apply a terminal-triggered cell switch based on at least one of an event and an implementation condition.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0261] The transceiver 220 may receive DL signals transmitted from one or more candidate cells. The DL signals may be reference signals (e.g., CSI-RS, SSB (SS / PBCH block)).

[0262] The control unit 210 may perform control to perform measurements based on DL signals transmitted from one or more candidate cells. The control unit 210 may determine, based on the measurements, a target beam that satisfies at least one of an event and an implementation condition used for beam selection or evaluation, and a target cell associated with the target beam, and perform control to perform a cell switch to the target cell.

[0263] When a plurality of beams corresponding to different cells satisfy at least one of the event and implementation conditions, the control unit 210 may determine the target cell based on the number of beams corresponding to each cell in the plurality of beams.

[0264] The control unit 210 may control to report information regarding at least one of the target beam and the target cell determined based on at least one of an event and an implementation condition.

[0265] The control unit 210 may control the selection of a target beam based on at least one of an event and an implementation condition and the selection of a target cell based on the target beam to be performed on different layers or the same layer.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0364] 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 DL signals transmitted from one or more candidate cells; and a control unit that performs measurements based on the DL signals, wherein the control unit determines, based on the measurements, a target beam that satisfies at least one of the events and implementation conditions used for beam selection or evaluation, and a target cell associated with the target beam, and controls a cell switch to be performed to the target cell.

2. The terminal according to claim 1, wherein the control unit determines the target cell based on the number of beams corresponding to each cell in the plurality of beams when the plurality of beams corresponding to different cells satisfy at least one of the event and implementation conditions.

3. The terminal according to claim 1, wherein the control unit controls to report information regarding at least one of the target beam and the target cell determined based on at least one of an event and an implementation condition.

4. The terminal according to claim 1, wherein the control unit selects a target beam based on at least one of the event and the implementation condition and selects a target cell based on the target beam at different layers.

5. A wireless communication method for a terminal, comprising the steps of: receiving DL signals transmitted from one or more candidate cells; and performing measurements based on the DL signals; determining, based on the measurements, a target beam that satisfies at least one of the events and implementation conditions used for beam selection or evaluation, and a target cell associated with the target beam; and controlling a cell switch to the target cell.

6. A base station having: a transmitting unit that transmits information regarding one or more candidate cells and information regarding at least one of an event and an implementation condition used for selecting or evaluating a beam to a terminal; and a control unit that instructs the terminal to select a target cell based on a target beam that satisfies at least one of the event and implementation condition, or to apply a terminal-triggered cell switch based on at least one of the event and implementation condition.

Images