Terminal, wireless communication method, and base station

Abstract

A terminal according to one aspect of the present disclosure comprises: a reception unit that receives a radio resource control (RRC) information element for configuring a channel state information (CSI) resource including a reference signal index used for L1 measurement for a cell switch based on a report of a layer 1 (L1) or a layer 2 (L2), and one or more execution conditions for triggering the cell switch; and a control unit that controls the cell switch when the one or more execution conditions are satisfied.

Description

Terminal, wireless communication method and base station

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

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

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

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

[0005] In future wireless communication systems (e.g., NR), the use of L1L2-triggered mobility (LTM) defined in Rel. 18 when a terminal (user terminal, User Equipment (UE)) moves between cells is being considered. If the LTM of Rel. 18 is applied, the interruption time of cell switching can be shortened.

[0006] It is expected that conditional LTM (CLTM) will be supported / introduced in Rel. 19 and later. However, there has been insufficient consideration on how to control CLTM.

[0007] Therefore, one of the objects of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately perform a cell switch even when CLTM is supported.

[0008] A terminal according to one aspect of the present disclosure includes a receiver that receives radio resource control (RRC) information elements for configuring a channel state information (CSI) resource including a reference signal index used for L1 measurements for a cell switch based on a Layer 1 (L1) or Layer 2 (L2) report, and one or more execution conditions for triggering the cell switch; and a controller that controls the cell switch when the one or more execution conditions are satisfied.

[0009] According to one aspect of the present disclosure, cell switching can be performed appropriately even when CLTM is supported.

[0010] Figure 1A is a diagram illustrating an example of UE mobility in Rel. 17. Figure 1B is a diagram illustrating an example of UE mobility in Rel. 18. Figure 2 is a diagram illustrating an example of a procedure for LTM (Long-Term Management) in Rel. 18 (R18 Long-Term Management). Figure 3 illustrates an example of an existing CSI measurement configuration. Figure 4 illustrates an example of a CSI reporting configuration according to embodiment A1. Figure 5 illustrates an example of an event-triggered configuration according to embodiment A1. Figure 6 illustrates an example of a CSI reporting configuration according to embodiment A2. Figure 7 illustrates an example of a CSI measurement configuration according to embodiment A3. Figure 8 illustrates an example of an event-triggered CSI reporting configuration according to embodiment A3. Figure 9 illustrates an example of an LTM configuration according to example 1 of embodiment A4. Figure 10 illustrates an example of an LTM CSI reporting configuration according to example 2 of embodiment A4. Figure 11 illustrates an example of a CSI reporting configuration according to example 1 of embodiment A5. Figure 12 illustrates an example of an event-triggered reporting configuration according to example 1 of embodiment A5. FIG. 13 shows an example of a CSI measurement configuration according to Example 2 of embodiment A5. FIG. 14 shows an example of a CSI reporting configuration according to Example 2 of embodiment A5. FIG. 15 shows an example of a CSI measurement configuration according to embodiment A6. FIG. 16 shows an example of an existing subsequent condition reconfiguration. FIG. 17 shows an example of a CSI measurement configuration according to position 1 of embodiment B1A. FIG. 18 shows an example of an LTM configuration according to position 2 of embodiment B1A. FIG. 19 shows an example of an LTM candidate configuration according to Example 1 of position 3 of embodiment B1A. FIG. 20 shows an example of an LTM candidate configuration according to Example 2 of position 3 of embodiment B1A. FIG. 21 shows an example of an LTM candidate configuration according to Example 1 of embodiment B1B. FIG. 22 shows an example of a CSI reporting configuration according to Example 1 of embodiment B1B. FIG. 23 shows an example of an LTM candidate configuration according to Example 2 of embodiment B1B. FIG. 24 shows an example of an event-triggered CSI reporting configuration according to Example 2 of embodiment B1B. Fig. 25 shows an example of CSI reporting configuration according to Example 3 of Embodiment B1B. Fig. 26 shows an example of CSI resource configuration according to Example 4 of Embodiment B1B. Fig. 27 shows an example of CSI resource configuration for LTM according to Example 5 of Embodiment B1B. Fig. 28 shows an example of LTM candidate configuration according to Example 1 of Embodiment B2. Fig. 29 shows an example of LTM configuration according to Example 2 of Embodiment B2. Fig. 30 shows an example of LTM configuration according to Example 3 of Embodiment B2.Fig. 31 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. Fig. 32 is a diagram showing an example of a configuration of a base station according to an embodiment. Fig. 33 is a diagram showing an example of a configuration of a user terminal according to an embodiment. Fig. 34 is a diagram showing an example of a hardware configuration of a base station and a user terminal according to an embodiment. Fig. 35 is a diagram showing an example of a vehicle according to an embodiment.

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

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

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

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

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

[0016] The additional cell is a cell that has an additional PCI different from the PCI of the serving cell. The UE can receive / transmit a UE-dedicated channel (UE-dedicated CH) from the additional cell. On the other hand, the UE needs to be within the coverage of the serving cell to receive UE common channels (e.g., system information / paging / short messages). When the UE moves out of the coverage of the serving cell, a cell switch (e.g., a process such as RRC reconfiguration) is required due to handover (also called L3 mobility).

[0017] <Scenario 2> Scenario 2 applies L1 / L2 inter-cell mobility (e.g., L1L2-triggered mobility (LTM)). L1 / L2 inter-cell mobility enables the serving cell to be changed using functions such as beam control without RRC reconfiguration. In other words, transmission and reception with a candidate cell / additional cell is possible without handover. Since handover requires RRC reconnection and creates a period when data communication is unavailable, applying L1 / L2 inter-cell mobility that does not require handover makes it possible to continue data communication even when the serving cell is changed. Scenario 2 may be applied, for example, in Rel. 18. In scenario 2, for example, the following procedure is performed.

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

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

[0020] Figure 1B shows an example of UE mobility in Rel. 18. In Rel. 18, the serving cell is switched by L1 / L2 (e.g., DCI / MAC CE). Here, the example shows a case where the serving cell is switched from PCI #1 corresponding to the current serving cell (e.g., current serving cell) to PCI #3 corresponding to the target serving cell (e.g., target serving cell) by L1 / L2 signaling.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0057] (Event-based beam reporting) It is being considered that event-based beam reporting will be supported in future wireless communication systems. Event-based beam reporting may also be called event-triggered beam reporting, and may mean UE-initiated beam reporting.

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

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

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

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

[0062] (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 primary cell (PCell) / primary secondary cell (PSCell) may be replaced with serving cell, neighboring cell, and PCell / PSCell measurement results (L1-RSRP / L1-SINR, etc.).

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

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

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

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

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

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

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

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

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

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

[0073] In UE-triggered LTM / UE-initiated LTM / CLTM, when events / implementation conditions used for beam selection / evaluation are applied, the UE needs to determine not only the target beam but also the target cell (e.g., the cell to switch to).

[0074] (CLTM) When CLTM is supported, an example of providing / signaling / evaluating execution conditions (e.g., execution conditions) for candidate cells will be described.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0089] (Analysis) Rel. 18 supports intra-CU LTM during non-dual connectivity (DC) and intra-SN PSCell LTM without master node (MN) involvement during DC.

[0090] In Rel. 19, in order to expand mobility, support for inter-CU (inter-CU) LTM and LTM while maintaining DC is being considered. For inter-CU LTM, the following cases are being considered: * Case where CU behaves as MN when DC is not configured * Case where NR-DC is configured, CU behaves as SN, and master cell group (MCG) is not changed * Case where NR-DC is configured, CU behaves as SN, and master cell group (MCG) is not changed

[0091] However, RRC signaling for L1 measurements, inter-CU LTM, DC LTM, execution conditions, subsequent LTM, etc. has not been sufficiently considered. If such signaling is not sufficiently considered, it may lead to degradation of communication quality / throughput.

[0092] Therefore, the present inventors have studied the setting method for L1 measurement / CLTM and have come up with an idea for one aspect of the present embodiment.

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

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

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

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

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

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

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

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

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

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

[0103] In the present disclosure, the terms cell, PCI, serving cell, source serving cell, source cell, CC, BWP, BWP within a CC, and band may be interchangeable. In the present disclosure, the terms cell, PCI, cell with an additional PCI, additional cell, other cell, non-serving cell, cell with a different PCI, candidate cell, candidate serving cell, cell with a PCI different from the PCI of the current serving cell, another serving cell, and target cell may be interchangeable. The target cell may be a cell selected from multiple candidate cells. In the present disclosure, the terms cell, base station (gNB) within a cell, base station (gNB) of a cell, and base station (gNB) may be interchangeable.

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

[0105] The terms event-triggered beam report, event-triggered report, beam report, CSI report, report, and L1 measurement report may be interchangeable. In the present disclosure, an event-triggered beam report may be an L1 / L3 beam report. An event-triggered beam report may be a report transmitted when an event / condition of an L1 measurement or a condition / event for CLTM is met. The base station may make a decision regarding LTM based on the event-triggered beam report. The terms beam report and CSI report may be interchangeable.

[0106] In the present disclosure, the terms event-based beam report, event-triggered beam report, event-based measurement report, event-based L1 measurement report, L1 measurement, and L1 measurement report may be interchangeable. In the present disclosure, the terms event, L1 measurement event, L1 event, and execution condition may be interchangeable.

[0107] (Wireless Communication Method) (Embodiment A) <Issues> In Rel. 18, the report configuration type (reportConfigType, report type) of an L1 measurement report indicates the time-domain behavior of the report configuration. The time-domain behavior indicates one of periodic reporting, semi-persistent reporting on PUCCH, semi-persistent reporting on PUSCH, and aperiodic reporting. The existing report configuration types are included in each CSI-ReportConfig in csi-ReportConfigToAddModList in the CSI measurement configuration (CSI-MeasConfig) or in each LTM-CSI-ReportConfig in ltm-CSI-ReportConfigToAddModList in CSI-MeasConfig, as shown in FIG. 3 .

[0108] Embodiment A relates to a method for configuring a report configuration type (reportConfigType) for an event-triggered L1 measurement report.

[0109] The target beam and event for event-triggered L1 measurement reporting may be configured using any of the following structures: ◆ Structure a: Either the CSI resource configuration (CSI-ResourceConfig) or the CSI resource configuration for LTM (LTM-CSI-ResourceConfig) includes the configuration of the target beam. Either the CSI reporting configuration (CSI-ReportConfig) or the CSI reporting configuration for LTM (LTM-CSI-ReportConfig) includes the configuration of the event. ◆ Structure b: Either the CSI resource configuration or the CSI resource configuration for LTM includes the configuration of the target beam. A new RRC IE for event-triggered CSI reporting configuration (e.g., EventTriggered-CSI-ReportConfig) includes the configuration of the event. The new RRC IE may include configuration related to the event. ◆ Structure c: A new RRC IE for event-triggered CSI reporting configuration (e.g., EventTriggered-CSI-ReportConfig) includes the configuration of the target beam and the event. The new RRC IE may include settings related to the target beam or may include settings related to the event.

[0110] According to embodiment A, event-based L1 measurement reporting can be suitably configured.

[0111] Event-triggered L1 measurement reporting may be configured using any of several embodiments Ax below.

[0112] <Embodiment A1> This embodiment relates to structure a.

[0113] As in the example of Figure 4, a reporting configuration type (e.g., reportConfigType) within a CSI reporting configuration (e.g., CSI-ReportConfig) may include an event-triggered configuration (e.g., eventTriggered, eventTriggered) for event-triggered L1 measurement reporting. As in the example of Figure 5, the event-triggered configuration may include an event-triggered reporting configuration (e.g., eventTriggered, eventTriggeredReportConfig) in addition to an existing reporting configuration type. The event-triggered configuration may indicate one or more events (e.g., eventA1, eventA2, ...). The event-triggered configuration may include a reporting configuration type (e.g., reportConfigType) similar to an existing reporting configuration type. An existing reporting configuration type and a reporting configuration type within the event-triggered configuration may be configured simultaneously.

[0114] In this example, events A1 and A2, which are L3 measurement events, are also introduced / repurposed into L1 events (L1 measurement events). Events configured in the event-triggered configuration may be reused existing events (e.g., L3 measurement events) or new events introduced for event-triggered L1 measurement reporting.

[0115] The event-triggered configuration may include a configuration for an L1 measurement report that is sent only once (non-periodically) by being triggered by an event.

[0116] If the event triggered configuration includes a reporting configuration type indicating periodic reporting, the UE may send L1 measurement reports periodically by triggering periodic reporting while the conditions of the configured event are met. The triggered periodic reporting may then be terminated when the conditions of the event are no longer met, when a specified number of reports have been sent, when a specified timer expires, etc.

[0117] <Embodiment A2> This embodiment relates to structure a.

[0118] As in the example of Fig. 6, a CSI reporting configuration (e.g., CSI-ReportConfig) may include an event-triggered reporting configuration (e.g., eventTriggeredReportConfig) for event-triggered L1 measurement reporting in addition to an existing reporting configuration type (e.g., reportConfigType). In this case, the event-triggered reporting configuration indicates one or more events (e.g., eventA1, eventA2, ...) and does not include a reporting configuration type.

[0119] The reporting configuration type may include reporting configurations that are sent only once (non-periodically). L1 measurement reports triggered by events in the event-triggered reporting configuration may be sent based on the existing reportConfigType.

[0120] If the reporting configuration type includes a reporting configuration type indicating periodic reporting, the UE may periodically transmit L1 measurement reports by triggering periodic reporting while a configured event condition is satisfied. The triggered periodic reporting may then be terminated when the event condition is no longer satisfied, a specified number of reports have been transmitted, a specified timer has expired, etc.

[0121] <Embodiment A3> This embodiment relates to structure b.

[0122] As in the example of Fig. 7, the CSI measurement configuration (e.g., CSI-MeasConfig) may include an add-mod list (e.g., eventTriggered-CSI-ReportConfigToAddModList) of an event-triggered CSI reporting configuration for an event-triggered L1 measurement report, in addition to an existing CSI-ReportConfig list (e.g., csi-ReportConfigToAddModList), or may include a release list (e.g., eventTriggered-CSI-ReportConfigToReleaseList) of an event-triggered CSI reporting configuration. The add-mod list may include one or more event-triggered CSI reporting configurations (e.g., EventTriggered-CSI-ReportConfig) to be added. The release list may include IDs (e.g., EventTriggered-CSI-ReportConfigId) of one or more event-triggered CSI reporting configurations to be released. As shown in the example of Fig. 8, the event-triggered CSI reporting configuration may include a reporting configuration type (e.g., reportConfigType) similar to an existing reporting configuration type and an event-triggered reporting configuration (e.g., eventTriggeredReportConfig). The event-triggered reporting configuration indicates one or more events (e.g., eventA1, eventA2, ...). The existing reporting configuration type and the reporting configuration type in the event-triggered configuration may be configured simultaneously.

[0123] In the example shown in this figure, the eventTriggered-CSI-ReportConfigToAddModList is included in the CSI-MeasConfig. The eventTriggered-CSI-ReportConfigToAddModList may be included in the LTM-Config in an RRCReconfiguration message. The eventTriggered-CSI-ReportConfig may be included in an LTM-Candidate in a list of LTM-Candidates (ltm-CandidateToAddModList) in the LTM-Config.

[0124] The event-triggered CSI reporting configuration may include the same content as the existing CSI reporting configuration, or may include the event-triggered configuration based on embodiment A1 or embodiment A2.

[0125] <Embodiment A4> This embodiment relates to any one of structures a to c.

[0126] The event-triggered setting or event setting for the L1 measurement report sent by the UCI (carried by the PUCCH or PUSCH) and the event-triggered setting or event setting for the L1 measurement report sent by the MAC CE (carried by the PUSCH) may be configured separately.

[0127] Any of embodiments A1 to A3 may be applied to an event-triggered configuration or event configuration for an L1 measurement report using UCI. Any of embodiments A1 to A3 may be applied to an event-triggered configuration or event configuration for an L1 measurement report using MAC CE. Two different embodiments from embodiments A1 to A3 may be applied to an event-triggered configuration or event configuration for an L1 measurement report using UCI and an event-triggered configuration or event configuration for an L1 measurement report using MAC CE, or the same one of embodiments A1 to A3 may be applied.

[0128] This embodiment may be implemented based on any of the following examples.

[0129] Example 1: Embodiment A1 may be applied to an L1 measurement report using UCI, and embodiment A3 may be applied to an L1 measurement report using MAC CE. The example of embodiment A1 may be applied to an L1 measurement report using UCI. A CSI reporting configuration (e.g., CSI-ReportConfig) may include a reporting configuration type (e.g., reportConfigType) similar to embodiment A1. The reporting configuration type may include an event-triggered reporting configuration (e.g., eventTriggered, eventTriggeredReportConfig) in addition to the existing reporting configuration types. For an L1 measurement report using MAC CE, embodiment A3 may be applied to an LTM configuration (LTM-Config) as shown in FIG. 9. The LTM configuration may include a list for adding or changing the event-triggered CSI reporting configuration (e.g., eventTriggered-CSI-ReportConfigToAddModList) similar to embodiment A3, or may include a list for releasing the event-triggered CSI reporting configuration (e.g., eventTriggered-CSI-ReportConfigToReleaseList) similar to embodiment A3.

[0130] Example 2 Embodiment A2 may be applied to an L1 measurement report using UCI, and embodiment A2 may be applied to an L1 measurement report using MAC CE. For an L1 measurement report using UCI, a CSI reporting configuration (e.g., CSI-ReportConfig) may include an event-triggered reporting configuration (e.g., eventTriggeredReportConfig) in addition to an existing reporting configuration type (e.g., reportConfigType) as in the example of embodiment A2. For an L1 measurement report using MAC CE, a CSI reporting configuration for LTM (e.g., LTM-CSI-ReportConfig) may include an event-triggered reporting configuration (e.g., eventTriggered) similar to embodiment A2 in addition to an existing reporting configuration type (e.g., reportConfigType), as in the example of FIG. 10 .

[0131] <Embodiment A5> This embodiment relates to a variation of embodiments A1 to A4.

[0132] In any of embodiments A1 to A4, the configuration for event-triggered L1 measurement reporting may indicate only one L1 event (L1 measurement event) (may include only one event-triggered configuration / event configuration), or may indicate multiple L1 events (L1 measurement events) (may include multiple event-triggered configuration / event configuration).

[0133] This embodiment may be implemented based on any of the following examples.

[0134] Example 1 As in the example of Figure 11, a CSI reporting configuration (e.g., CSI-ReportConfig) may include one or more event-triggered reporting configurations (e.g., eventTriggeredReportConfig1, eventTriggeredReportConfig2, ...) or may include a list including one or more event-triggered reporting configurations, based on embodiment A2. As in the example of Figure 12, each event-triggered reporting configuration indicates one or more events (e.g., eventA1, eventA2, ...). When one CSI reporting configuration includes multiple event-triggered reporting configurations, the event of L1 measurement may be an AND condition of the multiple events indicated by the multiple event-triggered reporting configurations, respectively.

[0135] Example 2 As in the example of FIG. 13 , a CSI measurement configuration (e.g., CSI-MeasConfig) may include an event configuration add-mod list (e.g., eventConfigToAddModList) for event-triggered L1 measurement reporting, or may include an event configuration release list (e.g., eventConfigToReleaseList). The add-mod list includes one or more event configurations (e.g., ventConfig) to be added. The release list includes IDs (e.g., EventConfigId) of one or more event configurations to be released. The event configuration includes an event configuration ID (e.g., EventConfigId) and an event. The event indicates one or more events (e.g., eventA1, eventA2, ...). As in the example of FIG. 14 , a CSI reporting configuration (e.g., CSI-ReportConfig) includes an event-triggered reporting configuration (e.g., eventTriggeredReportConfig) in addition to an existing reporting configuration type (e.g., reportConfigType) based on embodiment A2. An event-triggered reporting configuration references one or more event configurations by including one or more event configuration IDs.

[0136] <Embodiment A6> This embodiment relates to the structure c.

[0137] Apart from the CSI resources configured by the existing CSI-ResourceConfig and LTE-CSI-ResourceConfig for L1 measurements, CSI resources for at least one of event-triggered L1 measurement reporting and CLTM may be configured.

[0138] In the example of Figure 15, the CSI measurement configuration (e.g., CSI-MeasConfig) may include an addition modification list (e.g., event-CSI-ResourceConfigToAddModList) for event-triggered L1 measurement reporting and a release list (e.g., event-CSI-ResourceConfigToReleaseList) for event-triggered L1 measurement reporting in addition to an addition update list (e.g., csi-ResourceConfigToAddModList) / release list (e.g., csi-ResourceConfigToReleaseList) for CSI resource configurations (e.g., CSI-ResourceConfig). The addition modification list includes one or more CSI resource configurations (e.g., CSI-ResourceConfig) to be added for event-triggered L1 measurement reporting. The release list includes IDs (CSI-ResourceConfigId) of one or more CSI resource configurations to be released for event-triggered L1 measurement reporting. An LTM configuration (e.g., LTM-Config) may include an add-mod list (e.g., eventConfigToAddModList) of event configurations for event-triggered L1 measurement reporting, or may include a release list (e.g., eventConfigToReleaseList) of event configurations. The add-mod list includes one or more event configurations (e.g., EventConfig) to be added. The release list includes IDs (e.g., EventConfigId) of one or more event configurations to be released. An event configuration includes an event configuration ID (e.g., EventConfigId), a corresponding LTM candidate ID (e.g., LTM-CandidateId), a corresponding execution condition configuration (e.g., condExecutionCond), and a corresponding CSI resource configuration ID (e.g., CSI-ResourceConfigId) for event-triggered L1 measurement reporting. The CSI resource configuration ID refers to a CSI resource configuration in the add-mod list for event-triggered L1 measurement reporting in the CSI measurement configuration.

[0139] In this example, a list of CSI resource configurations for event-triggered L1 measurement reporting is included in the CSI measurement configuration. A list of CSI resource configurations for event-triggered L1 measurement reporting may also be included in the LTM configuration.

[0140] The CSI resource configuration may include some or all of the content of the CSI reporting configuration for LTM (LTM-CSI-ReportConfig) based on any of embodiments A1 to A3. In this case, the event configuration in the CSI resource configuration may indicate that a corresponding event is an execution condition (e.g., LTM-ExecutionEvent) for which candidate ID (e.g., LTM-CandidateId).

[0141] An RRC IE (eg, maxNrofEventConfigs) may be defined that indicates the maximum number of execution conditions included in one LTM configuration.

[0142] (Embodiment B) In order to perform CLTM, the RRC configures for each LTM candidate which beam a cell switch to be triggered when certain conditions are met.

[0143] How to set the execution condition for a subsequent CLTM has not been fully considered. In Rel. 18, a subsequent condition reconfiguration (SubsequentCondReconfig-r18) for a subsequent conditional PSCell addition or change (CPAC) is introduced as shown in Fig. 16. Once a conditional PSCell change is performed, the execution condition is updated based on SubsequentCondReconfig-r18.

[0144] Embodiment B relates to a method for setting conditional LTM (CLTM).

[0145] The target beam and event for CLTM may be configured using any of the following structures. ◆ Structure e: Either the CSI resource configuration (CSI-ResourceConfig) or the CSI resource configuration for LTM (LTM-CSI-ResourceConfig) includes the configuration of the target beam. Either the CSI reporting configuration (CSI-ReportConfig) or the CSI reporting configuration for LTM (LTM-CSI-ReportConfig) includes the configuration of the event. The execution condition may refer to the configuration of the event. ◆ Structure f: Either the CSI resource configuration or the CSI resource configuration for LTM includes the configuration of the target beam. A new RRC IE for configuring the execution condition includes the configuration of the event. The new RRC IE may include the configuration related to the event. ◆ Structure g: A new RRC IE for configuring the execution condition includes the configuration of the target beam and the event. The new RRC IE may include the configuration related to the target beam or the configuration related to the event.

[0146] According to embodiment B, the CLTM can be set appropriately.

[0147] The CLTM may be configured using any of the following embodiments Bx.

[0148] <Embodiment B1> An event setting for an event-triggered L1 measurement report and an L1 event (execution condition) for CLTM may be set in common (setting method A) or may be set separately (setting method B).

[0149] <<Embodiment B1A>> This embodiment relates to setting method A.

[0150] If the event configuration for event-triggered L1 measurement reporting and the execution conditions for CLTM are configured separately, the L1 event (execution conditions) for CLTM may be configured by an RRC IE in any of the following locations:

[0151] Position 1: As shown in the example of FIG. 17 , an IE in the CSI measurement configuration (CSI-MeasConfig) (in the serving cell configuration (ServingCellConfig)) indicates an L1 event (execution condition) for CLTM. The IE may include a corresponding LTM candidate ID (LTM-CandidateId). For example, the IE may be an execution condition configuration list (e.g., executionConditionConfigList). The execution condition configuration list includes one or more execution condition configurations (e.g., ExecutionConditionConfig). The execution condition configuration may include the ID (e.g., LTM-CandidateId) of the corresponding LTM candidate, a CSI resource configuration ID (e.g., CSI-ResourceConfigId), or an event configuration (e.g., eventConfig) for the L1 event (execution condition). The event configuration may indicate one or more events (e.g., eventA1, eventA2, ...). In the example shown in this figure, the configuration of the beam to be measured based on the L1 event is indicated by the CSI resource configuration (CSI-ResourceConfig) outside the event configuration (ExecutionConditionConfig) (structure e). The execution condition configuration references the CSI resource configuration by including the CSI resource configuration ID.

[0152] Position 2: As shown in the example of FIG. 18 , an IE in the LTM-Config (in the RRCReconfiguration message) indicates an L1 event (execution condition) for the CLTM. For example, the IE may be an execution condition configuration list (e.g., executionConditionConfigList). The execution condition configuration list includes one or more execution condition configurations (e.g., ExecutionConditionConfig). The execution condition configuration may include a corresponding LTM candidate ID (e.g., LTM-CandidateId), a CSI resource configuration ID (e.g., CSI-ResourceConfigId), or an event configuration (e.g., eventConfig) for the L1 event (execution condition). The event configuration may indicate one or more events (e.g., eventA1, eventA2, ...). - In the example of this figure, the configuration of the beam for the L1 measurement target based on the L1 event is indicated by the CSI resource configuration (CSI-ResourceConfig) outside the execution condition configuration (ExecutionConditionConfig) for the configuration of the L1 event (execution condition) (structure e). The execution condition configuration references the CSI resource configuration by including the CSI resource configuration ID.

[0153] Position 3: As shown in Example 1 of FIG. 19 , an IE in the LTM candidate configuration (LTM-Candidate) in the list (ltm-CandidateToAddModList) in the LTM configuration (LTM-Config) indicates an L1 event (execution condition) for CLTM. The IE may be an execution condition configuration list (e.g., executionConditionConfigList). The execution condition configuration list includes one or more execution condition configurations (e.g., ExecutionConditionConfig). The execution condition configuration may include a corresponding serving cell index (e.g., ServingCellIndex), a CSI resource configuration ID (e.g., CSI-ResourceConfigId), or an event configuration (e.g., eventConfig) for the L1 event (execution condition). The event configuration may indicate one or more events (e.g., eventA1, eventA2, ...). -◆ In the example of this figure, the configuration of the beam for the L1 measurement target based on the L1 event is indicated by the CSI resource configuration (CSI-ResourceConfig) outside the execution condition configuration (ExecutionConditionConfig) for the configuration of the L1 event (structure e). The execution condition configuration references the CSI resource configuration by including a CSI resource configuration ID. -◆ In example 2 of FIG. 20, the LTM configuration is the same as in example 1. The execution condition configuration may include a corresponding serving cell index (e.g., ServingCellIndex), a CSI resource configuration (e.g., CSI-ResourceConfig), or an event configuration (e.g., eventConfig) for the L1 event (execution condition). The event configuration may indicate one or more events (e.g., eventA1, eventA2, ...). The configuration of the beam for the L1 measurement target based on the L1 event is indicated by the CSI resource configuration (CSI-ResourceConfig) within the event configuration (ExecutionConditionConfig) (structure f).

[0154] The setting of the L1 event (execution condition) indicated by any of positions 1 to 3 may include at least one of the following pieces of information:

[0155] Information about beams to be measured in L1. The information may be a list of SSB indices or CSI-RS resource IDs, or may include some or all of the contents of the CSI resource configuration (CSI-ResourceConfig) or the CSI resource configuration for LTM (LTM-CSI-ResourceConfig).

[0156] Information about an L1 event. The information may include some or all of the contents of the CSI resource configuration or the CSI resource configuration for LTM. The information may indicate beams to be measured for L1 based on the L1 event.

[0157] The configuration of the beam to be measured based on the L1 event may be included in the configuration of the L1 event (execution condition) (structure f), or the configuration may be referenced by indicating the ID of a configuration outside the configuration of the L1 event (execution condition) (e.g., an event-triggered CSI resource configuration, EventTriggered-CSI-ResourceConfig) (structure e).

[0158] <<Embodiment B1B>> This embodiment relates to setting method B.

[0159] When the event setting for event-triggered L1 measurement reporting and the L1 event (execution condition) for CLTM are set in common, the setting of the L1 event (execution condition) for CLTM may be based on at least one of the following characteristics: ◆ The ID of the L1 event (L1 measurement event) setting set for event-triggered L1 measurement reporting is referenced as the L1 event (execution condition) of CLTM. ◆ As with setting method A, the position of the IE for the L1 event (execution condition) is either position 1, position 2, or position 3.

[0160] The configuration of an L1 event may have one of several forms: ◆ ID of the CSI resource configuration (CSI-ResourceConfig) or the CSI resource configuration for LTM (LTM-CSI-ResourceConfig) of the L1 measurement target. ◆ Information about the beam of the L1 measurement target. The information may be a list of SSB indices or CSI-RS resource IDs, or may include some or all of the contents of the CSI resource configuration (CSI-ResourceConfig) or the CSI resource configuration for LTM (LTM-CSI-ResourceConfig). ◆ Information about the L1 event. The information may include some or all of the contents of the CSI resource configuration or the CSI resource configuration for LTM.

[0161] This embodiment may be implemented based on any of the following examples.

[0162] Example 1 The location of the IE for configuring an L1 event (execution condition) is based on location 3. As in the example of FIG. 21 , each LTE candidate configuration (LTM-Candidate) may include an execution condition configuration (e.g., executionConditionConfig) indicating an L1 event (execution condition) for CLTM. The execution condition configuration includes one or more CSI reporting configuration IDs (e.g., (LTM-)CSI-ReportConfigId). The CSI reporting configuration ID references a corresponding CSI reporting configuration (CSI-ReportConfig). In the example of FIG. 22 , the structure of the CSI reporting configuration is based on structure a (embodiment A1). A list of (LTM-)CSI-ReportConfigs may be included in CSI-MeasConfig or LTM-Config, and the (LTM-)CSI-ReportConfig may be managed by an LTM-CandidateId or (LTM-)ReportConfigId.

[0163] Example 2 The location of the IE for configuring an L1 event (execution condition) is based on location 3. As in the example of FIG. 23 , each LTE candidate configuration (LTM-Candidate) may include an execution condition configuration (e.g., executionConditionConfig) indicating an L1 event (execution condition) for CLTM. The execution condition configuration includes one or more event-triggered CSI reporting configuration IDs (e.g., EventTriggered-CSI-ReportConfigId). The event-triggered CSI reporting configuration IDs refer to corresponding event-triggered CSI reporting configurations (EventTriggered-CSI-ReportConfig). In the example of FIG. 24 , the structure of the event-triggered CSI reporting configuration is based on structure b (embodiment A3). A list of event-triggered CSI reporting configurations may be included in CSI-MeasConfig or LTM-Config, and the event-triggered CSI reporting configuration may be managed by LTM-CandidateId or EventTriggered-CSI-ReportConfigId.

[0164] Example 3 The location of the IE for configuring an L1 event (execution condition) is based on location 3. As in Example 2, each LTE candidate configuration (LTM-Candidate) may include an execution condition configuration (e.g., executionConditionConfig) indicating an L1 event (execution condition) for CLTM. The execution condition configuration includes one or more event-triggered CSI reporting configuration IDs (e.g., EventTriggered-CSI-ReportConfigId). The event-triggered CSI reporting configuration IDs refer to corresponding event-triggered CSI reporting configurations (EventTriggered-CSI-ReportConfig). In the example of FIG. 25 , the structure of the CSI reporting configuration is based on structure c (embodiment A6). A list of event-triggered CSI reporting configurations may be included in CSI-MeasConfig or LTM-Config, and the event-triggered CSI reporting configuration may be managed by LTM-CandidateId or EventTriggered-CSI-ReportConfigId.

[0165] The information about beams to be measured in L1 may be a list of beams that differ for each candidate cell, or may indicate a combination of candidate cells and beams. The information about beams to be measured in L1 may be realized based on any of the following examples.

[0166] 26, information about beams to be measured in L1 is a CSI resource configuration (e.g., CSI-ResourceConfig). The CSI resource configuration is a list (csi-RS-ResourceSetList) of beams (SSB indexes or CSI-RS resource IDs) that differ for each candidate cell (a combination of an LTM candidate ID (e.g., LTM-CandidateId) and a physical cell ID (e.g., targetPCI)).

[0167] 27, the information about the beam to be measured for L1 is a CSI resource configuration for LTM (e.g., LTM-CSI-ResourceConfig). The CSI resource configuration for LTM indicates a combination (LTM-CSI-SSB-ResourceSet) of a candidate cell (e.g., LTM-CandidateId in ltm-CandidateIdList) and a beam (SSB-Index in ltm-CSI-SSB-ResourceList).

[0168] The LTM-Config or LTM-Candidate for the CLTM may be configured separately from the configuration for the NW-triggered LTM. For example, the LTM-Config or LTM-Candidate for the CLTM may be called a CondLTM-Config or a CondLTM-Candidate.

[0169] The structure of the target beam and event setting for the event-triggered L1 measurement report may be any of the structures a to c described above.

[0170] <Embodiment B2> The configuration for event-triggered L1 measurement reporting (event-triggered reporting configuration) may include, in addition to the L1 event configuration, an indication indicating an L1 event (execution condition) for CLTM. When the L1 event expires and CLTM is configured for a cell to which a beam corresponding to the L1 event belongs, the UE may trigger an LTM cell switch for the beam.

[0171] If the subsequent CLTM is set, after a cell switch is executed once, the execution conditions may be updated for the next cell switch.

[0172] The settings for updating the execution conditions may specify the settings (before the update) that require updating (e.g., at least one of LTM-Candidate, CSI-ReportConfig, and CSI-ResourceConfig) or their IDs, and may also specify the new (updated) settings (e.g., at least one of LTM-Candidate, CSI-ReportConfig, and CSI-ResourceConfig) or their IDs.

[0173] The configuration for updating the execution conditions may include a list of configurations or configuration IDs before the update and a list of configurations or configuration IDs after the update. The configuration for updating the execution conditions may be included in (Cond)LTM-Candidate, may be included in CSI-MeasConfig, or may be included in (Cond)LTM-Config. The list of configurations for updating the execution conditions may be included in CSI-MeasConfig or may be included in (Cond)LTM-Config. Each configuration in the list may include or be associated with a corresponding LTM candidate ID (e.g., LTM-CandidateId).

[0174] This embodiment may be implemented based on any of the following examples.

[0175] 28 , an LTM candidate setting (e.g., LTM-Candidate) includes an LTM candidate ID (e.g., LTM-CandidateId) before the update and a physical cell ID (e.g., ltm-CandidatePCI, PhysCellId), and may also include a setting for updating the corresponding execution condition (e.g., subsequent CLTM reconfiguration, SubsequentCondLTMReconfig). The subsequent CLTM setting may include an add / update list (e.g., CondLTMExecutionCondToAddModList) of the execution condition setting after the update, or may include a release list (e.g., CondLTMExecutionCondToReleaseList) of the execution condition setting after the update. The add / update list includes one or more add / update LTM execution condition settings (e.g., CondLTMExecutionCondToAddMod). The updated and added LTM execution condition setting includes a corresponding LTM candidate ID (LTM-CandidateId) and may include an execution condition setting (e.g., executionConditionConfig). The execution condition setting includes one or more CSI reporting setting IDs (e.g., CSI-ReportConfigId). The release list includes one or more LTM candidate IDs (e.g., LTM-CandidateId). - Information on the updated execution condition may be set directly. In this case, the execution condition setting may include a CSI reporting setting (e.g., CSI-ReportConfig) instead of a CSI reporting setting ID.

[0176] Example 2: A configuration for updating an execution condition may specify the configuration before the update (LTM candidate configuration, CSI reporting configuration, and CSI resource configuration) and specify the updated execution condition by an updated configuration ID. The LTM configuration may include a list of configurations for updating the execution condition. Each configuration in the list may be associated with an LTM candidate ID. In the example of FIG. 29 , the LTM configuration (e.g., LTM-Config) includes a list of configurations for updating the execution condition (e.g., subsequent condition reconfiguration list, subsequentCondReconfigList). The subsequent condition reconfiguration list may include one or more subsequent CLTM reconfiguration items (e.g., SubsequentCondLTMReconfigItem). Each subsequent CLTM reconfiguration item may include a corresponding LTM candidate ID (LTM-CandidateId) before the update and a corresponding subsequent CLTM reconfiguration (e.g., SubsequentCondLTMReconfig). The subsequent CLTM reconfiguration may include an add-mod list (e.g., CondLTMExecutionCondToAddModList) of updated execution condition settings, or may include an updated release list (e.g., CondLTMExecutionCondToReleaseList) of execution conditions. The add-mod list includes one or more execution condition setting add-mods (e.g., CondLTMExecutionCondToAddMod) to be added. The execution condition setting add-mod may include an LTM candidate ID (e.g., LTM-CandidateId) and a corresponding execution condition configuration (e.g., executionConditionConfig). The execution condition configuration includes one or more CSI reporting configuration IDs (e.g., CSI-ReportConfigId). The release list includes one or more LTM candidate IDs (e.g., LTM-CandidateId).

[0177] Example 3: A configuration for updating an execution condition may specify the configurations before the update (LTM candidate configuration, CSI reporting configuration, and CSI resource configuration) and specify the updated execution condition by an updated configuration ID. The LTM configuration may include a list of configurations for updating the execution condition. Each configuration in the list may be associated with an LTM candidate ID. In the example of Figure 30, the LTM configuration (e.g., LTM-Config) includes a list of configurations for updating the execution condition (e.g., subsequent condition reconfiguration list, subsequentCondReconfigList). The subsequent condition reconfiguration list may include one or more subsequent CLTM reconfigurations (e.g., SubsequentCondLTMReconfig). Each subsequent CLTM reconfiguration includes a corresponding pre-update LTM candidate ID (LTM-CandidateId) and may include an updated execution condition configuration add / change list (e.g., CondLTMExecutionCondToAddModList) or an updated execution condition release list (e.g., CondLTMExecutionCondToReleaseList). The add / change list includes one or more execution condition configuration add / changes (e.g., CondLTMExecutionCondToAddMod) to be added. The execution condition configuration add / change includes an LTM candidate ID (e.g., LTM-CandidateId) and may include a corresponding execution condition configuration (e.g., executionConditionConfig). The execution condition configuration includes one or more CSI reporting configuration IDs (e.g., CSI-ReportConfigId). The release list includes one or more LTM candidate IDs (e.g., LTM-CandidateId).

[0178] <Supplement to Embodiment A / Embodiment B> In the present disclosure, CSI-ReportConfig may be read as LTM-CSI-ReportConfig. In the present disclosure, CSI-ResourceConfig may be read as LTM-CSI-ResourceConfig. In the present disclosure, CSI-ReportConfig may be read as EventTriggered-CSI-ReportConfig. In the present disclosure, CSI-ResourceConfig may be read as EventTriggered-CSI-ResourceConfig.

[0179] ((Supplementary Note)) <<Notification of Information to UE>> In the above-described embodiments, any information may be notified 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) 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.

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

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

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

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

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

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

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

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

[0188] The specific UE capability may indicate at least one of the following: - Supporting the specific processing / operation / control / assumption / information - Supporting the application of CLTM - Supporting event-triggered beam reporting in LTM - Supporting setting of implementation conditions per candidate cell - Supporting RACH-less procedure in CLTM - The maximum number of TCI state IDs, RS IDs, and L1-RSRPs included in one MAC CE for the first / second UL signal - Supporting MAC CEs for the first / second UL signal - Supporting activation of the TCI state of a candidate cell by a MAC CE - The maximum number of candidate cell IDs included in one MAC CE - The maximum number of TCI state IDs corresponding to one candidate cell ID included in a MAC CE.

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

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

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

[0192] (Supplementary Notes) The following inventions are supplementary notes with respect to one embodiment of the present disclosure (particularly, embodiment A). [Supplementary Note 1] A terminal comprising: a receiver unit that receives radio resource control (RRC) information elements for configuring channel state information (CSI) resources including reference signal indexes used for layer 1 (L1) measurements and one or more events that trigger the L1 measurements; and a controller that controls transmission of a report of the L1 measurements based on occurrence of the one or more events. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein the RRC information element is a CSI reporting configuration, the CSI reporting configuration including a reporting configuration type, and the reporting configuration type including a configuration of a time domain behavior of the report and a configuration of the one or more events. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein the RRC information element is a CSI reporting configuration, the CSI reporting configuration including a reporting configuration type and a configuration of the one or more events. [Supplementary Note 4] The terminal according to any one of Supplementary Notes 1 to 3, wherein the RRC information element is a CSI measurement configuration, the CSI measurement configuration includes a list of one or more CSI reporting configurations for L1 measurement, and one CSI reporting configuration for L1 measurement includes a reporting configuration type and the one or more event configurations.

[0193] (Supplementary Note) The following invention is supplementary with respect to one embodiment of the present disclosure (particularly, embodiment B). [Supplementary Note 1] A terminal having: a receiver unit that receives radio resource control (RRC) information elements for configuring a channel state information (CSI) resource including a reference signal index used for L1 measurement for a cell switch based on a Layer 1 (L1) or Layer 2 (L2) report and one or more execution conditions for triggering the cell switch; and a controller that controls the cell switch when the one or more execution conditions are satisfied. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein the RRC information element is any one of a CSI measurement configuration, a configuration of the cell switch, and a candidate configuration for the cell switch, and the RRC information element includes one or more execution condition configurations indicating the one or more execution conditions. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein the RRC information element includes one or more candidate configurations of the cell switch, wherein one candidate configuration includes one or more execution condition configurations indicating the one or more execution conditions, and wherein one execution condition configuration indicates one or more events for the L1 measurement. [Supplementary Note 4] The terminal according to any of Supplementary Note 1 to Supplementary Note 3, wherein the RRC information element indicates the cell switch candidates and the reference signal index.

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

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

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

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

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

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

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

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

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

[0203] Furthermore, the user terminal 20 may perform communication using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0242] The transceiver 120 may transmit a radio resource control (RRC) information element for configuring a channel state information (CSI) resource including a reference signal index used for Layer 1 (L1) measurements and one or more events that trigger the L1 measurements. The controller 110 may control reception of reports of the L1 measurements based on the occurrence of the one or more events.

[0243] The transceiver 120 may transmit a radio resource control (RRC) information element for configuring a channel state information (CSI) resource including a reference signal index used for L1 measurement for a cell switch based on a Layer 1 (L1) or Layer 2 (L2) report, and one or more execution conditions for triggering the cell switch. The controller 110 may control the cell switch if the one or more execution conditions are satisfied.

[0244] (User terminal) Fig. 33 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0261] Note that 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.

[0262] The transceiver 220 may receive radio resource control (RRC) information elements for configuring channel state information (CSI) resources including reference signal indices used for Layer 1 (L1) measurements and one or more events that trigger the L1 measurements. The controller 210 may control transmission of reports of the L1 measurements based on the occurrence of the one or more events.

[0263] The RRC information element may be a CSI reporting configuration. The CSI reporting configuration may include a reporting configuration type. The reporting configuration type may include a configuration of a time domain behavior of the report and a configuration of the one or more events.

[0264] The RRC information element may be a CSI reporting configuration, which may include a reporting configuration type and a configuration of the one or more events.

[0265] The RRC information element may be a CSI measurement configuration. The CSI measurement configuration may include a list of one or more CSI reporting configurations for L1 measurements. One CSI reporting configuration for L1 measurements may include a reporting configuration type and the one or more event configurations.

[0266] The transceiver 220 may receive a radio resource control (RRC) information element for configuring a channel state information (CSI) resource including a reference signal index used for L1 measurements for a cell switch based on a Layer 1 (L1) or Layer 2 (L2) report, and one or more execution conditions for triggering the cell switch. The controller 210 may control the cell switch if the one or more execution conditions are satisfied.

[0267] The RRC information element may be any one of a CSI measurement configuration, a configuration of the cell switch, and a candidate configuration of the cell switch. The RRC information element may include one or more execution condition configurations indicating the one or more execution conditions.

[0268] The RRC information element may include one or more candidate configurations for the cell switch. One candidate configuration may include one or more execution condition configurations indicating the one or more execution conditions. One execution condition configuration may indicate one or more events for the L1 measurement.

[0269] The RRC information element may indicate the cell switch candidates and the reference signal index.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A terminal having: a receiver for receiving a radio resource control (RRC) information element for setting a channel state information (CSI) resource including a reference signal index used for L1 measurements for a cell switch based on a Layer 1 (L1) or Layer 2 (L2) report, and one or more execution conditions for triggering the cell switch; and a controller for controlling the cell switch when the one or more execution conditions are satisfied.

2. The terminal according to claim 1, wherein the RRC information element is any one of a CSI measurement configuration, a configuration of the cell switch, and a candidate configuration of the cell switch, and the RRC information element includes one or more execution condition configurations indicating the one or more execution conditions.

3. The terminal according to claim 1, wherein the RRC information element includes one or more candidate settings for the cell switch, one candidate setting includes one or more execution condition settings indicating the one or more execution conditions, and one execution condition setting indicates one or more events for the L1 measurement.

4. The terminal according to claim 1, wherein the RRC information element indicates the cell switch candidates and the reference signal index.

5. A wireless communication method for a terminal, comprising: a step of receiving a radio resource control (RRC) information element for configuring a channel state information (CSI) resource including a reference signal index used for L1 measurements for a cell switch based on a Layer 1 (L1) or Layer 2 (L2) report, and one or more execution conditions for triggering the cell switch; and a step of controlling the cell switch if the one or more execution conditions are satisfied.

6. A base station having: a transmitter that transmits a radio resource control (RRC) information element for setting a channel state information (CSI) resource including a reference signal index used for L1 measurement for a cell switch based on a Layer 1 (L1) or Layer 2 (L2) report, and one or more execution conditions that trigger the cell switch; and a controller that controls the cell switch when the one or more execution conditions are satisfied.

Images