Terminal, wireless communication method, and base station

Abstract

A terminal according to one aspect of the present disclosure comprises: a reception unit that receives downlink control information (DCI) which instructs execution of a specific operation for network energy saving (NES) related to conditional L1 / L2 triggered mobility (CLTM); and a control unit that controls monitoring of the DCI.

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] However, for certain use cases of future mobility, network energy saving (NES) is being considered.

[0006] As an operation related to NES, for example, support for turning off access to a certain cell and moving the UE to another cell is being considered.

[0007] However, the rules for supporting NES in specific mobility use cases are not clear enough, which may affect the throughput in mobility.

[0008] Therefore, one of the objects of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can realize optimization of communication in mobility.

[0009] A terminal according to one aspect of the present disclosure has a receiving unit that receives downlink control information (DCI) that instructs the execution of a specific operation related to network power saving (NES) related to conditional L1 / L2 triggered mobility (CLTM), and a control unit that controls monitoring of the DCI.

[0010] According to one aspect of the present disclosure, flexible communication can be performed while reducing communication overhead.

[0011] Figure 1A is a diagram showing an example of UE mobility in Rel. 17. Figure 1B is a diagram showing an example of UE mobility in Rel. 18. Figure 2 is a diagram showing an example of a Rel. 18 LTM (R18 LTM) procedure. Figure 3 is a diagram showing a first example of conditional LTM operation. Figure 4 is a diagram showing a second example of conditional LTM operation. Figure 5 is a diagram showing an example of a target cell's operation in conditional LTM. Figure 6 is a diagram showing a third example of conditional LTM operation. Figure 7 is a diagram showing a fourth example of conditional LTM operation. Figure 8 is a diagram showing a fifth example of conditional LTM operation. Figure 9 is a diagram showing an example of a bit field of group-common DCI of the present disclosure. Figure 10 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. Figure 11 is a diagram showing an example of a base station configuration according to an embodiment. Figure 12 is a diagram showing an example of a user terminal configuration according to an embodiment. Figure 13 is a diagram showing an example of 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.

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

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

[0014] (1) The UE receives from the serving cell the 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).

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

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

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

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

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

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

[0021] Figure 1B shows an example of UE mobility in Rel. 18. In Rel. 18, the serving cell is switched by L1 / L2 (e.g., DCI / MAC CE). 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0136] (Analysis) In the above-mentioned CHO, support for turning off access to a certain cell and moving the UE to another cell is being considered for the purpose of network energy saving (NES).

[0137] To indicate such a CHO operation (which may be referred to as NES CHO), a specific DCI (eg, DCI format 2_9) may be utilized.

[0138] According to NES CHO, radio link failure (RLF) can be prevented by setting candidate cells and conditions in the UE in the same way as CHO before the NW turns off the cell. Also, when the UE receives a cell-off instruction from the NW, the UE can immediately perform handover to a specific cell (destination / handover destination / target cell) from among the candidate cells.

[0139] As described above, mobility in Rel. 19 and later can support conditional long-term mobile maintenance (CLTM) as a function similar to that of CHO.

[0140] In CLTM, candidate cells and events can be configured for the UE, and the UE pre-synchronizes the UL and DL to the candidate cell, identifies the beam to be used in the candidate cell, etc. before performing handover.

[0141] This reduces the downtime that may occur during handover and maintains throughput during handover.

[0142] Supporting NES in CLTM is also being considered. However, the rules for supporting NES in CLTM are not clear enough. This lack of clarity could affect the throughput of mobility.

[0143] Therefore, the present inventors came up with a method for solving the above problem.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0158] In the present disclosure, cell, PCI, serving cell, source serving cell, source cell, CC, BWP, BWP within CC, and band may be read interchangeably.

[0159] In the present disclosure, the terms cell, PCI, cell with additional PCI, additional cell, other cell, non-serving cell, cell with different PCI, candidate cell, candidate serving cell, cell with 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.

[0160] In the present disclosure, a cell, a base station (gNB) within a cell, a base station (gNB) of a cell, and a base station (gNB) may be read interchangeably.

[0161] In the present disclosure, handover, handover defined in Rel. 15, CHO, DAPS handover, LTM, CLTM, and cell switching may be read interchangeably.

[0162] In the present disclosure, turning off a cell and disconnecting / disabling / deactivating a connection (access) to a cell may be interpreted as interchangeable.

[0163] In the present disclosure, the terms configuration, upper layer signaling, upper layer parameters, RRC parameters (which may simply be referred to as parameters), RRC configuration, etc. may be read interchangeably.

[0164] In the present disclosure, UE-common PDCCH, UE common configuration, UE-common PDCCH configuration, PDCCH-ConfigCommon, common PDCCH, group-common PDCCH, and common PDCCH for specific functions / operations may be read interchangeably.

[0165] The group-common PDCCH may be at least one of a PDCCH for notifying TDD setting / slot format, a PDCCH for notifying Channel Occupancy Time (COT) duration / available resource block set, a PDCCH for notifying a search space set group, a PDCCH for notifying preemption, a PDCCH for notifying UL transmit power control (TPC) commands, a PDCCH for notifying UL cancellation, a PDCCH for notifying UE power saving / Discontinuous Reception (DRX) / SCell dormancy, a PDCCH for notifying paging early indication, a PDCCH for notifying beams / time resources of a network-controlled repeater (NCR), and a PDCCH for notifying Discontinuous Transmission (DTX) / DRX of a cell. The group-common PDCCH may refer to a PDCCH received in a common search space.

[0166] (Wireless communication method) The embodiments of the present disclosure can be broadly categorized as follows: - 0th embodiment: configuration / instruction for NES CLTM. - 1st embodiment: method for configuring candidate cells / criteria for NES LTM / CHO. - 2nd embodiment: signaling (instruction) for executing NES LTM / CHO. - 3rd embodiment: monitoring of signaling (instruction). - 4th embodiment: UE operation after execution of LTM / CHO. Each embodiment will be described based on these. Each embodiment and each option within each embodiment can be applied in appropriate combination.

[0167] The UE may perform LTM / CHO by applying the present disclosure. The NW / BS / gNB may provide / send to the UE settings / instructions for the UE to realize the control. Furthermore, the NW / BS / gNB may perform various controls necessary to receive various signaling related to the control from the UE.

[0168] In this disclosure, application of NES to LTM (particularly CLTM) is illustrated as a specific use case of mobility, but is not limited to this. The present disclosure can be applied to any use case of mobility (other than existing use cases such as CHO). In other words, CHO, LTM, and CLTM may be read as interchangeable terms.

[0169] <Tenth Embodiment> The tenth embodiment relates to settings / instructions for the NES CLTM.

[0170] <<Aspect 0-1>> Aspect 0-1 relates to RRC configuration of NES CLTM.

[0171] The UE may receive a configuration of at least one of the following options and control the execution of the NES CLTM based on the configuration:

[0172] (Opt1) NES CLTM (dedicated) settings. This setting may be used as a setting for the CLTM.

[0173] (Opt2) NES CLTM (dedicated / unique) settings. These settings are used only for the NES CLTM and not for the CLTM. In other words, these settings may be configured / defined separately from the settings for the CLTM.

[0174] (Opt2-1) The settings for NES CLTM may be configured / defined by the same settings (RRC parameters) as CLTM.

[0175] (Opt2-2) The settings for the NES CLTM may be configured / defined by the CLTM and part of the settings (RRC parameters). That is, the parameters for the NES CLTM may include part of the parameters for the CLTM.

[0176] For example, if the UE performs beam level switching, it needs to notify the target cell of the TCI state ID used in the target cell. On the other hand, if the UE does not perform beam level switching, it is not necessary to notify the TCI state ID. In this case, it is possible to reduce the communication overhead for configuration by using only a part of the CLTM (i.e., the necessary parameters).

[0177] According to this aspect, the settings for the NES CLTM can be clarified.

[0178] <<Aspect 0-2>> Aspect 0-2 relates to the instruction of NES CLTM.

[0179] The UE may receive an indication of at least one of the following options and control the execution of the NES CLTM based on the indication:

[0180] The UE may receive the instruction simultaneously with a predetermined operation related to the NES. The instruction may be included in a specific DL signal / channel (common PDCCH (group common DCI)) transmitted to the UE configured with the NES CLTM. Examples of the predetermined operation include an instruction for NES CHO, an instruction for activating / deactivating DTX / DRX of the cell, an instruction for changing the transmission signal and resources of common signals such as on-demand SSB, SSB / PRACH / SIB, etc.

[0181] (Opt1) DCI format (e.g., DCI format 2_9) indicating NES CHO (NES for CHO).

[0182] The DCI format may include a 1-bit field (flag) for indicating NES CHO, which may also be used to indicate NES CLTM (NES for CLTM).

[0183] That is, in Opt1, the DCI format for indicating an existing NES for CHO may be used as is to indicate an NES for CLTM.

[0184] (Opt2) New DCI format for indicating NES CLTM.

[0185] (Opt2-1) The DCI format may include a 1-bit field (flag) for indicating NES CLTM.

[0186] (Opt2-2) The DCI format may include a 1-bit field for indicating NES CLTM and a 1-bit field for indicating NES CHO, so that the UE can simultaneously configure / instruct NES for both LTM and CHO.

[0187] 9 is a diagram illustrating an example of a bit field of the group-common DCI of the present disclosure. As shown in Fig. 9, the group-common DCI may include, as specific bit fields, an information block (which may also be referred to as a bit field) for the PCell for UE #1, an information block for the SCell for UE #1, and an information block for the PCell for UE #2.

[0188] The information block for the PCell for UE #1 may include a 1-bit field indicating DRX and a 1-bit field indicating CHO / CLTM (i.e., NES).

[0189] The information block for the SCell for UE #1 may include a 1-bit field indicating DTX and a 1-bit field indicating DRX, i.e., the field indicating CHO / CLTM may not be included for the SCell.

[0190] The information block for the PCell for UE #2 may include a 1-bit field indicating DTX, a 1-bit field indicating DRX, and a 1-bit field indicating CHO / CLTM (i.e., NES).

[0191] The field for instructing the execution of NES may use the field for instructing CHO / CLTM in FIG. 9, or a separate field dedicated to NES may be added.

[0192] In FIG. 9, a bit value "0" may mean that the corresponding instruction is not applied (not indicated), and a bit value "1" may mean that the corresponding instruction is applied (indicated).

[0193] The order of the bit fields of the DCI shown in Figure 9 is not limited to this and can be changed as appropriate. The bit size of the DCI may be variable depending on the amount of information required for the instruction (the same or different size may be specified). The DCI may be configured in any format (the same applies to the second embodiment described below).

[0194] UE Actions After Receiving an Indication After receiving an indication of at least one of the above options, the UE may perform at least one of the following actions:

[0195] (Action #1) The UE selects a specific target cell.Which target cell the UE selects may be up to the UE implementation.

[0196] (Action #2) If the UE acquires the Timing Advance (TA) of the target cell, the UE may perform cell switch without using RACH.

[0197] (Action #3) If the UE acquires the TA of the target cell, the UE may perform cell switch using RACH. In this case, the UE may transmit PRACH to the target cell.

[0198] That is, the UE may determine whether to apply operation #2 / #3 based on whether or not a TA has been acquired for the target cell (may perform cell switching by determining whether or not to use RACH).

[0199] According to this aspect, it is possible to clarify the instructions for the NES CLTM.

[0200] First Embodiment The first embodiment relates to a method for setting candidate cells / criteria for NES LTM / CHO.

[0201] The UE may be configured by RRC with specific information associated with the NES usage, which may be information related to LTM / CHO candidate cells / reference / measurement resources.

[0202] The UE may perform certain measurements based on the configured L1 / L3 measurement resources / configurations, and may perform specific actions related to the implementation of LTM / CHO based on the configured resources / cells.

[0203] In the present disclosure, LTM / CHO means LTM in which cell switching is triggered based on a configured event, and may be interchangeably read as conditional LTM (CLTM).

[0204] The subject (specific information) associated with the use of the NES may be at least one of the following options. That is, the specific information shown in the following options may be associated with the use of the NES. Also, any combination of the following options may be applied.

[0205] (Opt1) Settings for LTM.

[0206] (Opt2) CHO settings / CLTM settings.

[0207] (Opt3) Settings for CHO / CLTM events (for example, settings for events A2 to A5 described above).

[0208] Note that the event may be at least one of the following: An event used in L3 measurements; An event defined / specified for L1 measurements (e.g. UE Initiated Beam Reporting (UEIBR) / Event Triggered Beam Reporting); An event defined / specified for CLTM; An event defined / specified for NES CLTM.

[0209] (Opt4) Metrics (e.g., [L1 / L3] RSRP / SINR / RSRQ).

[0210] Information regarding thresholds / L3 filters (filtering values) / offsets for the calculation of metrics may be associated with the NES application.

[0211] The metric may be interchangeably read as a threshold for an event.

[0212] Timers / times used for events (e.g., time to trigger (TTT)), counters may be associated with the NES application.

[0213] Information regarding novel filtering (which may be referred to as an L1 filter, filtering value, etc.) performed on the L1 measurements may be associated with the use of the NES.

[0214] (Opt5) Measurement resources.

[0215] The measurement resource may include information (ID / index, or a list of these) indicating at least one of the following: TCI state ID / BWP ID / CC ID; Cell / frequency ID; SSB ID (defined in cell / not defined in cell); CSI-RS resource ID / CSI-RS resource set ID.

[0216] (Opt6) Specific resources that can implement LTM / CHO.

[0217] A specific resource may include information (ID / index, or a list thereof) indicating at least one of the following: - Candidate cell; - Candidate TCI state / candidate beam; - Candidate reference signal; - Candidate PRACH resource; - Candidate TA.

[0218] The specific resources mentioned above may be interchangeably read as resources relating to candidates.

[0219] <<Modifications>> In the present disclosure, settings that are shared / common with another use (each of the above-mentioned options or NE CHO) different from the use of the NES may be applied / referenced. Furthermore, a unique ID / index may be defined for the setting for the other use. Furthermore, an association between the setting for the NES use and the setting for the other use may be defined / assumed. For example, a lower-level (subordinate) setting having the same ID / index as a setting corresponding to a certain ID / index may include the same settings / parameters.

[0220] According to this embodiment, the configuration of candidate cells / criteria for NES LTM / CHO becomes clear, and the UE can appropriately control the NES-related operations based on the configuration.

[0221] Second Embodiment The second embodiment relates to signaling (instructions) for performing NES LTM / CHO.

[0222] The UE may receive signaling (e.g., physical layer signaling such as DCI) to perform NES LTM / CHO, and the indication may be associated with the use of the NES.

[0223] The UE may control the execution of NES LTM / CHO based on the instruction. For example, when the UE receives the instruction, the UE may determine the cell / beam / PRACH resource based on the specified condition and perform the specified operation related to LTM / CHO.

[0224] More specifically, the UE may determine / select a target cell / beam / PRACH resource according to a specific set condition, and may then use the determined / selected cell / beam / PRACH resource to perform specific operations related to NES LTM / CHO.

[0225] <<Signaling Content>> The instruction regarding (to execute) NES LTM / CHO may include information, i.e., content (ID / index or a list thereof), indicating at least one of the following options: Any combination of the following options may also be applied: Also, the ID / index / sequence of a parameter previously configured by RRC may be indicated.

[0226] The "target" shown below may mean "the target of execution of NES LTM / CHO."

[0227] (Opt1) The target cell, e.g., the cell indicator field. Alternatively, PRACH may be transmitted to indicate the candidate cell.

[0228] (Opt2) Reference signal / beam [of interest].

[0229] (Opt3) [Target] PRACH resource. Note that the PRACH resource may be used only if the UE has not previously performed a RACH. Also, a PRACH retransmission indication field may be included. This field may indicate the performance of power ramping if the PDCCH order indicates a retransmission of a PRACH with the same SSB ID / cell ID as the previous PRACH.

[0230] (Opt4) [Apply] TA value.

[0231] (Opt5) Whether LTM / CHO can be performed (see, for example, FIG. 9). Whether LTM / CHO can be performed may be indicated by a 1-bit field. The 1-bit field may be set for each resource. Alternatively, each bit field [set for each resource] may correspond to each cell / beam. Alternatively, the [target] cell / beam may be indicated by a pre-configured codepoint.

[0232] (Opt6) Whether a specific ACK [response] is required.

[0233] The specific ACK [response] may be at least one of the following: PRACH; CSI report; HARQ ACK; specific UL signal / channel using PUCCH / PUSCH; BSR (Buffer Status Report) using MAC CE. The BSR may mean a buffer status report indicating the buffer amount (buffer size); ACK to a cell switch command [MAC CE]; RRC parameters indicating the completion of RRC reconfiguration (e.g., RRCReconfigurationComplete), parameters related to RRC setup (RRCSetup).

[0234] The necessity of a specific ACK may be indicated by a 1-bit field. The 1-bit field may be configured for each resource. Alternatively, each bit field (configured for each resource) may correspond to a respective cell / beam. Alternatively, the target cell / beam may be indicated by a pre-configured codepoint.

[0235] Alternatively, the need for a specific ACK may be signaled by indicating the resources required for transmitting a given UL ACK (e.g., indicating an ID / index) or by indicating the cell / beam from which the UL ACK is to be transmitted, e.g., HARQ ACK resources may be signaled in the same way as in the scheduling DCI.

[0236] The specific ACK described above may include a parameter indicating that the LTM / CHO is intended for the NES. Alternatively, the LTM intended for the NES, the CHO intended for the NES, or the LTM and CHO intended for the NES may be notified separately.

[0237] Alternatively, the UE may be configured by RRC to signal at least one of the following indications in the same signaling: Alternatively, the UE may be notified / configured (pre-configured) with the start position / end position / order (ascending / descending) of the bits indicating each of the following information, for example, the order of DTX, DRX, NES CHO, NES LTM / CHO of the cell (or the reverse order).

[0238] - Activation / deactivation of DTX / DRX in a particular cell. - Indication of NES CHO in a particular cell. - Indication of LTM / CHO in a particular cell.

[0239] The specific cell mentioned above may be any of a PCell (primary cell), an SCell (secondary cell), a serving cell, and a PSCell.

[0240] <<Container for Signaling>> The signaling content for executing NES LTM / CHO may be notified using at least one container of the following options. Any combination of the following options may also be applied. The UE may receive an instruction regarding the execution of NES LTM / CHO via the container shown below. Note that the container shown below itself may represent an instruction regarding the execution of NES LTM / CHO.

[0241] (Opt1) Specific DCI (see, for example, FIG. 9 ). The specific DCI may be, for example, a group-wide DCI (DCI format 2_X) (X is an arbitrary integer). Alternatively, the specific DCI may be any other DCI format (0_X, 1_X, etc.). Alternatively, a new DCI format for NES LTM / CHO may be defined.

[0242] In a specific DCI, an existing field in the short message may be utilized to indicate the execution of NES LTM / CHO.

[0243] (Opt2) Specific MAC CE. The specific MAC CE may be, for example, a cell switch command. The specific MAC CE may include a new field for instructing the execution of NES LTM / CHO. Alternatively, the execution of NES LTM / CHO may be instructed by utilizing an existing field in the specific MAC CE.

[0244] A specific MAC CE may be called an activation command that instructs (enables) the execution of NES LTM / CHO.

[0245] (Opt3) Specific higher layer signaling (RRC). The specific higher layer signaling may be, for example, cell-wide RRC signaling or UE-specific / dedicated RRC signaling (for example, SIB1, SIBX, parameters related to RRC reconfiguration (RRCReconfiguration), etc.).

[0246] In the present disclosure, the terms instruction, DCI, PDCCH, MAC CE, and RRC may be interchangeable.

[0247] According to this embodiment, the signaling (instruction) for performing NES LTM / CHO becomes clear, and the UE can appropriately control the operation related to the NES based on the instruction.

[0248] Third Embodiment The third embodiment relates to monitoring of signaling (instructions).

[0249] The UE may be configured / instructed to monitor signaling (e.g., DCI / PDCCH) for performing the NES LTM / CHO described in the second embodiment. The UE may perform / control monitoring of the signaling based on the configured / instructed parameters.

[0250] <<Monitoring Target>> (Cell) The monitoring target cell (monitored by the UE) may be at least one of the following, or any combination of the following: PCell. Serving cell [configured / meets a predetermined event (condition) / any]. SCell (e.g., PUCCH-SCell). PSCell.

[0251] (DCI) The monitored DCI may be CRC-scrambled (have a CRC scrambled by a specific RNTI (Radio Network Temporary Identifier)). The UE may assume / expect the monitored DCI to be CRC-scrambled (have a CRC scrambled by a specific RNTI). The specific RNTI may be at least one of the following:

[0252] - SI-RNTI (System Information-Radio Network Temporary Identifier). ・P-RNTI (paging-RNTI). - PEI-RNTI (Paging early indication-RNTI). ・RA-RNTI (Random access-RNTI). ・MsgB-RNTI. ・SFI-RNTI. ・INT-RNTI. ・TPC-RNTI. ・TPC-PUSCH / PUCCH / SRS-RNTI. ・C-RNTI. ・TC-RNTI. - NES-RNTI ((NES exclusive / specific) RNTI for NES). - RNTI for other uses.

[0253] In this disclosure, a particular RNTI may be referred to as an RNTI for / associated with an NES.

[0254] (Search Space) The search space (SS) to be monitored may be a common search space (CSS) / UE-specific search space (USS). At least one of the following may be configured for the search space:

[0255] Monitoring period, Offset / duration / symbol within the monitoring period, Associated CORESET[ID], Aggregation level (for example, possible settings are 1, 2, 3, 8, and 16).

[0256] The same search space / aggregation level as / shared with other uses may be set / used.

[0257] <<DCI Payload>> The payload size of the DCI may be set.

[0258] The payload size [of the DCI indicating NES] may be the same as or different from the DCI [format] for other uses. The UE may assume / expect that the payload size [of the DCI indicating NES] is the same / different from the DCI [format] for other uses.

[0259] The payload size (e.g., maximum size) may be predefined by a specification, or the UE may assume / expect the payload size to be zero-padded up to the maximum size.

[0260] The UE may be configured with bit positions (start position / end position / length) for determining the NES-indicating bit. The UE may also be configured with information / usage of cell / beam resources associated with each bit. The UE may determine the specific bit (the NES-indicating bit) based on the configuration.

[0261] For example, the UE may be configured such that the Xth bit indicates cell DTX / DRX activation / deactivation and the X+Yth (e.g. Y=1)th bit indicates NES LTM / CHO (see e.g. Fig. 9). The ordering of the bits (per application / per cell) may be signaled explicitly or may be implicitly determined by the UE.

[0262] <<Monitoring Unnecessary Period>> A UE may be configured with a predetermined period during which it does not monitor the DCI (PDCCH) indicating the above-mentioned NES (which may also be called a monitoring unnecessary (or impossible) period), or may report this period in its UE capabilities. The predetermined period may be at least one of the following options, or may be any combination of the following options: If the UE supports the predetermined period, it does not monitor the DCI (PDCCH) indicating the NES during the predetermined period.

[0263] (Opt1) Time for UE to turn off DRX (UE DRX off duration).

[0264] (Opt2) Period during which the cell is DTX inactive.

[0265] (Opt3) Sleep period for UEs configured / supporting Low Power Wake-Up Signal (LP-WUS).

[0266] (Opt4) The period during which SSB / SIB1 (CORESET0) is set.

[0267] (Opt5) [Configured] Radio Resource Management (RRM) period.

[0268] (Opt6) A period specified for receiving a beam of a different type (e.g., a specific QCL type (Type D)) [from the CORESET of the target DCI / PDCCH (indicating the NES)].

[0269] (Opt7) The period during which the RACH procedure is being performed (is being performed).

[0270] (Opt8) The period during which handover (cell switching) is being performed (is being performed).

[0271] (Opt9) The period during which the CLTM event (condition) is met.

[0272] (Modification) A predetermined delay time (which may be called a processing delay time / application delay time, etc.) may be added to the period of each of the above-mentioned options. The UE may control monitoring by treating the predetermined period of each of the above-mentioned options plus the delay time as a monitoring-free period. In other words, the UE does not monitor the DCI (PDCCH) indicating NES during the predetermined period.

[0273] In addition, the UE may be controlled not to perform the monitoring if some / all of the target DCI / PDCCH / CORESET / SS overlap in the time domain / frequency domain during the period of each of the above options.

[0274] According to this embodiment, the method of monitoring the DCI (PDCCH) indicating the NES becomes clear, and the UE can appropriately control the monitoring of the DCI (PDCCH).

[0275] <Fourth embodiment> The fourth embodiment relates to UE operation after receiving signaling.

[0276] When the UE receives signaling (e.g., DCI / PDCCH) for performing the NES LTM / CHO according to the second embodiment, the UE may perform specific operations related to the LTM / CHO based on the following specific conditions.

[0277] For example, when the UE receives the above-mentioned signaling, it may determine the cell / beam / PRACH resource based on the specific conditions set and perform specific actions related to LTM / CHO.

[0278] <<Specific Conditions>> The specific conditions may be at least one of the following options, or any combination of the following options. The specific conditions may refer to conditions for performing specific operations related to NES LTM / CHO. More specifically, the specific conditions may be conditions for selecting / determining a cell / beam / PRACH resource related to the execution of the operations.

[0279] (Opt1) The cell / beam (reference signal) measured by the UE meets the configured LTM / CHO criteria.

[0280] (Opt2) The signaling (second embodiment) for executing NES LTM / CHO includes / is expected to include information about monitoring (third embodiment).

[0281] (Opt3) The TA value measured / calculated by the UE is equal to or less than / greater than a predetermined threshold, or a predetermined relationship is satisfied between the TA value measured / calculated by the UE and the configured / instructed TA value.

[0282] For example, the difference between the TA value calculated by the UE and the indicated (notified) TA value may be equal to or less than Z (milliseconds / slots / symbols), where Z may be predefined by a specification, set / indicated by higher layer signaling / physical layer signaling, or determined according to UE capabilities.

[0283] (Opt4) A predetermined relationship is satisfied between the transmit / receive beams of the serving cell / PCell and the transmit / receive beams of the target cell.

[0284] For example, the power is less than or equal to X in the QCL relationship, or the difference in time / frequency synchronization is less than or equal to Y. In this case, the values ​​of X and Y may be predefined by a specification, set / indicated by higher layer signaling / physical layer signaling, or determined according to UE capabilities.

[0285] (Opt5) Resources of a specific signal / channel associated with the target cell / TCI state (beam) are acquired (received) / enabled. The specific signal / channel may be a dynamic grant PUSCH / PUCCH, a configured grant PUSCH / PUCCH, or a common / dedicated PUCCH.

[0286] (Opt6) The UE holds any TA value among the candidate cells configured for the UE.

[0287] (Opt7) Any of the candidate cells configured for the UE has an activated TCI state.

[0288] (Opt8) The higher layer signaling (RRC) for configuring candidate cells includes parameters that support the execution of NES CLTM.

[0289] <<Specific Action>> The specific action related to NES LTM / CHO may be at least one of the following options, or any combination of the following options: The specific action may refer to an action performed on a cell / beam / PRACH resource selected / determined based on a set specific condition.

[0290] (Opt1) Activation of TCI state.

[0291] (Opt2) Obtain TA [value].

[0292] (Opt3) Transmission of a predetermined UL signal / channel. The predetermined UL signal / channel may be any of PRACH / CSI report / HARQ ACK (or may be any other UL signal / channel).

[0293] For example, the ACK may be a response to an RRC / MAC CE (Cell Switch Command) that includes a parameter indicating NES LTM / CHO.

[0294] (Opt4) Cell search / cell identification / auto gain control (AGC) / DL synchronization / UL synchronization.

[0295] (Opt5) Predetermined action related to TA. The predetermined action may include, for example, applying the TA [value] to the PTAG (Primary Timing Advance Group), starting the TAT (Timing Advance Timer), starting a predetermined timer (T340), etc.

[0296] (Opt6) Apply TCI state to target cell.

[0297] (Opt7) Terminate access to current serving cell.

[0298] (Opt8) Reset path loss accumulation.

[0299] (Opt9) Reset MAC.

[0300] (Opt10) Apply path loss of target cell.

[0301] (Opt11) Sending a Buffer Status Report (BSR).

[0302] (Note) Each of the above operations may be performed in the current serving cell or in the target cell.

[0303] When performing the specific operations described above, the UE may assume / expect cell DTX in the target cell / beam, or may assume / expect cell DTX / DRX in the target cell / beam, or may assume / expect cell DTX / DRX in the target cell / beam. Alternatively, the UE may assume / expect cell DTX / DRX, UE DRX, or NES LTM / CHO configuration in the previous / past serving cell.

[0304] According to this embodiment, the specific operation to be performed after receiving signaling (e.g., DCI / PDCCH) indicating NES is made clear, and the UE can appropriately control the execution of the specific operation.

[0305] According to the above-described embodiments, the rules regarding network energy saving (NES) in LTM (including CLTM) / CHO are clarified, and the UE / NW can appropriately control the operation of NES in mobility. As a result, it is possible to realize optimization of communication in mobility (for example, improvement of throughput by effective power (power saving) control in communication).

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

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

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

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

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

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

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

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

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

[0315] The particular UE capability may indicate support for particular processes / operations / controls / information for at least one of the above embodiments.

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

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

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

[0319] (Supplementary Notes) The following inventions are supplementary notes regarding an embodiment (0th / 1st / 2nd embodiment) of the present disclosure. [Supplementary Note 1] A terminal comprising: a receiver that receives a configuration or an instruction related to network energy saving (NES) for a specific use case of mobility; and a controller that controls execution of a specific operation related to the NES based on the configuration or instruction, wherein the specific use case is conditional L1 / L2 triggered mobility (CLTM). [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein the receiver receives the instruction through group-common downlink control information (DCI). [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein the instruction is a MAC control element (MAC CE) or downlink control information (DCI) including a specific field indicating the NES. [Supplementary Note 4] The terminal according to any one of Supplements 1 to 3, wherein the controller determines at least one of a cell, a beam, and a resource on which the NES is to be executed, based on the instruction associated with a use of the NES.

[0320] (Supplementary Notes) The following inventions are supplementary notes regarding one embodiment (third embodiment) of the present disclosure. [Supplementary Note 1] A terminal comprising: a receiver that receives downlink control information (DCI) instructing execution of a specific operation related to network power saving (NES) for conditional L1 / L2 triggered mobility (CLTM); and a controller that controls monitoring of the DCI. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein the controller assumes that the DCI to be monitored is CRC scrambled with a specific radio network temporary identifier (RNTI). [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein the receiver receives a configuration related to a payload size of the DCI to be monitored or a bit position for determining a bit in the DCI that indicates the NES, and the controller determines the payload size or the bit based on the configuration. [Supplementary Note 4] The terminal according to any one of Supplementary Note 1 to Supplementary Note 3, wherein the receiving unit receives a setting related to a monitoring-unnecessary period, and the control unit controls, based on the setting, not to monitor the DCI during the monitoring-unnecessary period.

[0321] (Supplementary Notes) The following inventions are supplementary notes regarding one embodiment (fourth embodiment) of the present disclosure. [Supplementary Note 1] A terminal comprising: a receiving unit that receives an instruction to perform a specific operation related to network energy saving (NES) for conditional L1 / L2 triggered mobility (CLTM); and a control unit that controls execution of the specific operation related to the NES based on the instruction, wherein the control unit determines at least one of a cell, a beam, and a resource as a target for execution of the NES based on a set specific condition. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein the control unit controls execution of the specific operation based on the determined target for execution of the NES. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein the specific condition is based on at least one of: a measurement result of a cell or beam; a timing advance (TA) value; and a predetermined correspondence relationship for beams between a serving cell and a target cell. [Supplementary Note 4] The terminal according to any one of Supplementary Notes 1 to 3, wherein the specific operation is at least one of: activating a transmission configuration indication (TCI) state; obtaining a timing advance (TA) value; transmitting a predetermined uplink (UL) channel; transmitting a response to the instruction; cell search; stopping access to the current serving cell; resetting path loss accumulation; MAC reset; applying path loss of the target cell; and transmitting a buffer status report (BSR).

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

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

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

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

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

[0327] 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 locations and numbers of the cells and user terminals 20 are not limited to the embodiment shown in the figure. Hereinafter, when there is no need to distinguish between the base stations 11 and 12, they will be collectively referred to as base station 10.

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

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

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

[0331] The multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with the Common Public Radio Interface (CPRI), an X2 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0368] The transceiver 120 may transmit a configuration or instruction related to network energy saving (NES) for a specific use case of mobility. The controller 110 may control generation of the configuration or instruction for the terminal to perform a specific operation related to the NES. The specific use case may be conditional L1 / L2 triggered mobility (CLTM).

[0369] The transceiver 120 may transmit downlink control information (DCI) instructing execution of a specific operation related to network energy saving (NES) for conditional L1 / L2 triggered mobility (CLTM). The controller 110 may control generation of a configuration for monitoring the DCI.

[0370] The transceiver 120 may transmit an instruction to perform a specific operation related to network energy saving (NES) for conditional L1 / L2 triggered mobility (CLTM). The controller 110 may control generation of the instruction for the terminal to perform the specific operation related to the NES.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0387] The measurement unit 223 may derive channel measurements for CSI calculation based on 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 interference measurement resources. The interference measurement resources may be at least one of NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, 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.

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

[0389] The control unit 210 may perform at least part of the processing of the control unit in the above appendix.

[0390] The transceiver unit 220 may perform at least part of the processing of the transmitter / receiver unit in the above appendix.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0476] 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 ...." "does not expect ..." may be interchangeably read as "be not expected ...." 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" (e.g., if apparatus A is a UE, apparatus B may be a base station).

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

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

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

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

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

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

[0483] 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 any integer) attached (for example, "highest" may be interchangeable with "i-th highest").

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

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

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

[0487] Although the invention according to the present disclosure has been described in detail above, it will be apparent 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.

Claims

1. A terminal having: a receiving unit that receives downlink control information (DCI) that instructs the execution of a specific operation related to network power saving (NES) for conditional L1 / L2 triggered mobility (CLTM); and a control unit that controls monitoring of the DCI.

2. The terminal of claim 1, wherein the control unit assumes that the DCI to be monitored is CRC-scrambled with a specific radio network temporary identifier (RNTI).

3. The terminal of claim 1, wherein the receiving unit receives a setting regarding a bit position for determining the payload size of the DCI to be monitored or a bit in the DCI that indicates the NES, and the control unit determines the payload size or the bit based on the setting.

4. The terminal according to claim 1, wherein the receiving unit receives a setting regarding a monitoring-unnecessary period, and the control unit controls, based on the setting, not to monitor the DCI during the monitoring-unnecessary period.

5. A wireless communication method for a terminal, comprising: a step of receiving downlink control information (DCI) instructing execution of a specific operation related to network power saving (NES) for conditional L1 / L2 triggered mobility (CLTM); and a step of controlling monitoring of the DCI.

6. A base station having: a transmitter that transmits downlink control information (DCI) that instructs the execution of a specific operation related to network power saving (NES) for conditional L1 / L2 triggered mobility (CLTM); and a controller that controls the generation of settings for monitoring the DCI.

Images