Terminal, wireless communication method, and base station
The implementation of UE-initiated beam reporting and conditional L1/L2 triggered mobility in wireless communication systems addresses the inadequacies of CSI measurement/reporting in mobility applications, enhancing communication quality and throughput by facilitating efficient cell switching and continuous data transmission.
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- NTT DOCOMO INC
- Filing Date
- 2025-10-08
- Publication Date
- 2026-04-23
AI Technical Summary
Existing wireless communication systems, particularly in next-generation mobile communication systems like 5G and beyond, have inadequate consideration for CSI measurement/reporting in mobility applications, leading to potential hindrances in achieving lower latency communication and impacting communication quality and throughput.
A terminal and base station implementation that supports UE-initiated beam reporting and conditional L1/L2 triggered mobility (CLTM) using uplink resources, with control units managing UL cell switching commands through UCI or MAC control elements to enhance communication quality and throughput.
Improves communication quality and throughput by enabling seamless and efficient cell switching without handover, maintaining data communication continuity during cell changes.
Smart Images

Figure JP2025035716_23042026_PF_FP_ABST
Abstract
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] In a Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) was specified for the purpose of achieving a higher data rate, lower latency, etc. (Non-Patent Document 1). Also, for the purpose of further increasing the capacity and enhancing the performance of LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9), LTE-Advanced (3GPP Rel. 10-14) was specified.
[0003] Successor systems to LTE (for example, also referred to as 5th generation mobile communication system (5G), 5G+(plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 and later) are also under consideration.
[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 a future wireless communication system (for example, NR, Rel. 19 and later), it is being considered to support UE-initiated Beam Report (UEIBR) that is initiated by a terminal (user terminal, User Equipment (UE)) based on an event (event-based).
[0006] Such beam reporting (CSI measurement / reporting) is being considered for support in MIMO / mobility systems from Rel. 19 onwards. For example, support for conditional LTM (CLTM) is being considered as a mobility use case.
[0007] However, there are cases where CSI measurement / reporting (event-triggered beam reporting) for mobility applications has not been adequately considered. If this consideration is insufficient, it may not be possible to achieve lower latency communication, potentially hindering improvements in communication quality and throughput.
[0008] Therefore, one of the objectives of this disclosure is to provide a terminal, a wireless communication method, and a base station that can improve communication quality / throughput.
[0009] A terminal according to one aspect of the present disclosure includes a receiving unit that receives settings for UL resources for an uplink (UL) cell switching command that triggers conditional L1 / L2 triggered mobility (CLTM), and a control unit that controls the transmission of the UL cell switching command based on the UL resources, wherein the UL cell switching command is transmitted using uplink control information (UCI) or MAC control elements (MAC CE) as a container.
[0010] According to one aspect of this disclosure, communication quality / throughput can be improved.
[0011] Figure 1A shows an example of UE movement in Rel. 17. Figure 1B shows an example of UE movement in Rel. 18. Figure 2 shows an example of the LTM (R18 LTM) procedure for Rel. 18. Figure 3 shows a first example of conditional LTM operation. Figure 4 shows a second example of conditional LTM operation. Figure 5 shows an example of target cell operation in conditional LTM. Figure 6 shows a third example of conditional LTM operation. Figure 7 shows a fourth example of conditional LTM operation. Figure 8 shows a fifth example of conditional LTM operation. Figure 9 shows an example of RS configuration for a new beam of UEIBR. Figure 10 shows an example of an existing cell switching command MAC CE. Figure 11 shows an example of the UL cell switching command UCI of this disclosure. Figures 12A to 12C show examples of transmission timing for UL cell switching commands for each case. Figure 13 shows an example of a schematic configuration of a wireless communication system according to one embodiment. Figure 14 shows an example of a base station configuration according to one embodiment. Figure 15 shows an example of a user terminal configuration according to one embodiment. Figure 16 shows an example of the hardware configuration of a base station and user terminal according to one embodiment. Figure 17 shows an example of a vehicle according to one embodiment.
[0012] (L1 / L2 Inter-Cell Mobility) A UE may perform UL transmissions to one or more cells / TRPs. In this case, the following Scenario 1 or Scenario 2 procedures are possible. In this disclosure, a serving cell may be interpreted as a TRP within a serving cell. Layer 1 / layer 2 (L1 / L2) and DCI / Medium Access Control Control Element (MAC CE) may be interpreted as mutually exclusive. In this disclosure, a PCI different from the Physical Cell Identity (PCI) of the current serving cell may be simply referred to as a "different PCI". Non-serving cells, cells with different PCIs, and additional cells may be interpreted as mutually exclusive.
[0013] <Scenario 1> Scenario 1 is, for example, a scenario that corresponds to inter-cell mobility in a multi-TRP, but it may also be a scenario that does not correspond to inter-cell mobility in a multi-TRP.
[0014] (1) The UE receives from the serving cell the SSB settings for beam measurement of the TRP corresponding to a PCI different from that of the serving cell, and the settings necessary to use wireless resources for data transmission and reception, including the resources of the different PCI. (2) The UE performs beam measurement of the TRP corresponding to the different PCI and reports the beam measurement results to the serving cell. (3) Based on the above report, the Transmission Configuration Indication (TCI) status 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 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. The UE must use a common channel from the serving cell (Broadcast Control Channel (BCCH), Paging Channel (PCH)), etc., as in conventional systems.
[0015] In Scenario 1, when the UE sends and receives signals with the additional cell / TRP (the TRP corresponding to the PCI of the additional cell), the serving cell (the UE's assumption of the serving cell) remains unchanged. The UE sets higher-layer parameters related to the PCI of the non-serving cell from the serving cell. Scenario 1 may be applied, for example, in Rel. 17.
[0016] Figure 1A shows an example of UE movement in Rel. 17. It assumes a UE moving from a PCI#1 cell (serving cell) to a PCI#3 cell (additional cell) (overlapping with the serving cell). In this case, Rel. 17 does not support L1 / L2 switching of serving cells.
[0017] An additional cell is a cell with an additional PCI that is different from the PCI of the serving cell. UEs can receive and transmit UE-dedicated channels from additional cells. UEs need to be within the coverage of the serving cell to receive UE common channels (e.g., system information / paging / short messages). If a UE moves outside the coverage of the serving cell, a cell switch is required, such as through a handover (also called L3 mobility).
[0018] <Scenario 2> In Scenario 2, L1 / L2 cell mobility is applied. With L1 / L2 cell mobility, serving cell changes can be made using functions such as beam control without RRC reconfiguration. In other words, transmission and reception with additional cells are possible without handover. Since handover requires RRC reconnection and other factors, resulting in a period of no data communication, applying L1 / L2 cell mobility that does not require handover allows data communication to continue even when the serving cell is changed. Scenario 2 may be applied, for example, in Rel. 18. In Scenario 2, for example, the following procedure is performed.
[0019] (1) The UE receives the SSB configuration of a cell with a different PCI (additional cell) from the serving cell for beam measurement / serving cell change. (2) The UE performs beam measurement on 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 the different PCI (serving cell configuration) by upper layer signaling (e.g., RRC). In other words, a pre-configuration regarding 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 by L1 / L2 signaling in accordance with the serving cell change. The activation of the TCI state and the serving cell change may be performed separately. (5) The UE changes the serving cell (assumed serving cell) and starts receiving / transmitting using the pre-configured UE-specific channel and TCI state.
[0020] In other words, in Scenario 2, the serving cell (the assumed serving cell in the UE) is updated by L1 / L2 signaling. Scenario 2 may also be applied in Rel. 18.
[0021] Figure 1B shows an example of UE movement in Rel. 18. In Rel. 18, serving cells are switched by L1 / L2 (e.g., DCI / MAC CE). UEs can receive / transmit UE-dedicated / common channels to and from the new serving cell (or target serving cell). UEs may leave the coverage of the current serving cell (e.g., Current serving cell).
[0022] (L1-L2-triggered mobility (LTM) in Rel. 18) Figure 2 shows an example of LTM being considered in Rel. 18. Here, the LTM operation is shown in the steps of LTM preparation (e.g., LTM preparation), early sync (e.g., Early sync), LTM execution (e.g., LTM execution), and LTM completion (e.g., LTM completion), but the steps of LTM are not limited to these. Some steps (or actions included in the steps) may be omitted, the order of actions included in some steps and other actions included in other steps may be swapped, and other steps (or other actions) may be added. In this disclosure, early sync may be read as sync.
[0023] <LTM preparation> 1: The UE sends a measurement report message to the gNB. The gNB determines the LTM settings and begins preparing one or more candidate cells.
[0024] 2: The gNB sends an RRC reconfiguration message to the UE that includes the LTM candidate cell settings for one or more candidate cells.
[0025] 3. The UE saves its LTM candidate cell configuration and sends an RRC reconstruction completion 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 prior to the cell switch command may be supported to be performed at least on an SSB basis.
[0027] 4b: When requested from the network, the UE performs early TA acquisition with one or more candidate cells before receiving a cell switch command. This is triggered via CFRA by a PDCCH order from the source cell. The UE then sends a preamble to the designated candidate cell. To minimize data interruption to the source cell by Contention Free Random Access (CFRA) to the candidate cell, the UE does not receive RARs intended for acquiring the TA value. 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 cell and guarantees the validity of the TA based on the network implementation.
[0028] <LTM execution> 5: The UE performs the L1 measurement set for the candidate cell and sends the L1 measurement report for gNB. The L1 measurement is performed insofar as the RRC rearrangement 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 candidate settings for the target cell's index. The UE switches to the target cell and applies the settings indicated by the candidate setting index.
[0030] 7. If the UE does not have a valid TA for the target cell, it performs a random access procedure on the target cell.
[0031] <LTM Completion> 8: The UE completes the LTM cell switch procedure by sending an RRC reconfiguration completion message. The UE performs the RA procedure in step 7, and if the random access procedure completes successfully, it considers the LTM execution to be successfully completed. In a RACH-less LTM, the UE considers the LTM execution to be successfully completed if it determines that the network has successfully received the first UL data. The UE determines the success of the first UL data reception 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] (Conditional Handover (CHO)) Conditional Handover (CHO) from Rel. 16 onwards is described below. CHO is applied, for example, to Non-Terrestrial Networks (NTN). NTN supports the following additional trigger conditions for a UE to perform CHO to a candidate cell: - Radio Resource Management (RRM) measurement-based event A4. - Time-based trigger conditions. - Location-based trigger conditions.
[0033] Time-based or location-based trigger conditions are always set in conjunction with one of the measurement-based trigger conditions (CHO events A3 / A4 / A5 described below). How the UE evaluates time-based or location-based trigger conditions together with RRM measurement-based events depends on the UE implementation.
[0034] (Rel. 18 LTM and Rel. 16 CHO) Early sync / early L1 measurement report is supported in the above-mentioned LTM (e.g., Rel. 18 LTM), but early sync / early measurement report is not supported in CHO (e.g., Rel. 16 CHO). 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 measurement results and CHO conditions).
[0035] In LTM, a MAC CE for cell switch commands is transmitted from the base station to the UE. In CHO, after the UE receives the CHO configuration via RRC signaling, it begins evaluating the conditions for implementing CHO for the candidate cell. After determining mobility (or cell switch), RACH is required in CHO, but may not be required in LTM.
[0036] (Conditional LTM) When conditional LTM (e.g., conditional LTM (CLTM)) is supported, examples of providing / signaling / evaluating execution conditions for candidate cells are described.
[0037] Execution conditions may be set for each candidate cell by RRC signaling / MAC CE. The execution conditions (or simply called "conditions") may include at least one of the following: event, reference signal type (RS type), reference signal configuration (RS configuration), and measurement quantity. The reference signal type (RS type) may indicate SSB / CSI-RS. The measurement quantity may indicate L1-RSRP / L3-RSRP / SINR / RSRQ.
[0038] The execution conditions may be set separately for each candidate cell (for example, different conditions may be supported). Alternatively, the execution conditions may be set in common for multiple candidate cells (for example, a group of candidate cells) or for all candidate cells. Alternatively, some of the execution conditions may be set in common for each candidate cell, while the rest are set separately. Some of the execution conditions may be events, and the rest may be condition values, etc. Of course, this is not limited to these.
[0039] The number of candidate cells for which implementation conditions are provided may be defined in advance by the specification, set by the UE from the network (e.g., base stations), or determined based on UE capabilities. For example, the number of cells for which implementation conditions are provided may be the same as the set candidate cells, or it may be less than the total number of set candidate cells.
[0040] The settings for the implementation conditions (e.g., detailed settings) may be the same as the settings for the existing system. The settings for the existing system may be, for example, the settings supported by CHO supported in Rel. 16 (e.g., settings based on L3 measurement).
[0041] Alternatively, the setting for the implementation conditions may apply a new condition setting similar to the L1 report by an event trigger (e.g., event triggered L1 report). An example of a condition (or event) is shown below. Event A2: The measurement result of the serving cell is worse than the threshold. Event A3: The measurement result of an adjacent 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 an adjacent cell (the value obtained by adding an offset to the measurement result) is better than the threshold. Event A5: The measurement result of the SpCell is worse than the first threshold, and the measurement result of an adjacent cell (the value obtained by adding an offset to the measurement result) is better than the second threshold. Event A6: The measurement result of an adjacent 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 measurement result of interference is higher than the threshold. Event A4': The measurement result of one beam from an adjacent cell is better than the threshold. Event A4'': The statistical value (e.g., average value, total value, etc.) of the measurement results of multiple beams (e.g., the best X beams) is better than the threshold. X may be fixed or may be set by upper layer signaling or the like. Event A4''': The L1-RSRP measurement result of one beam from an adjacent cell is better than the threshold. Event A4''''': The L1-RSRP of each of the X beams from an adjacent cell is better than the threshold.
[0042] Note that the applicable conditions / events are not limited to this, and the above multiple events may be combined and applied, or other events may be applied.
[0043] Regarding the conditions for each candidate cell (or the conditions 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.
[0044] [Option 1] One condition may be set for each candidate cell (or for each of a plurality / all of the candidate cells). The condition may correspond to only one event. That is, one condition having only one event may be set for each candidate cell (or for each of a plurality / all of the candidate cells).
[0045] When the condition corresponding to each candidate cell (or the event corresponding to the condition) is satisfied, the UE / base station may be controlled to perform the LTM procedure / operation for the candidate cell.
[0046] [Option 2] A plurality (for example, a maximum of X) of conditions may be set for each candidate cell (or for each of a plurality / all of the candidate cells). X may be, for example, 2 or 3, or may be 4 or more. X may be defined in the specification, may be set from the base station to the UE, or may be determined based on the UE capability.
[0047] When at least one of the plurality of conditions corresponding to each candidate cell (or the events corresponding to each condition) is satisfied, the UE / base station may be controlled to perform the LTM procedure / operation for the candidate cell.
[0048] When the setting of a plurality (for example, X) of conditions is supported for each candidate cell, restrictions may be provided between the plurality of conditions. The restrictions between the conditions may be, for example, RS setting (RS configuration) / RS type / event / measurement quantity. As an example, the same RS setting / RS type may be set between the plurality of conditions, and the event / measurement quantity may be set differently between the conditions.
[0049] When different conditions correspond to each candidate cell, restrictions may be provided between the conditions, or the configuration may be such that no restrictions are provided between the conditions.
[0050] The supported conditions (for example, RS setting / RS type / event / measurement quantity) and the number of conditions to be set may follow the UE capability.
[0051] The following describes an example of the operation of the conditional LTM, but for parts that are not specifically described, the procedure may be the same as that of the Rel. 18 LTM (R18 LTM) shown in Figure 2.
[0052] [Example of Conditional LTM Operation 1] Figure 3 shows a first example of conditional LTM operation. In Figure 3, the steps of conditional LTM operation are shown as LTM preparation (e.g., CLTM preparation), early sync (e.g., Early sync), LTM execution (e.g., CLTM execution), and LTM completion (e.g., CLTM completion), but the steps of LTM are not limited to these. Some steps (or actions included in steps) may be omitted, the order of actions included in some steps and other actions included in other steps may be swapped, and other steps (or other actions) may be added.
[0053] 《LTM preparation》 In LTM preparation, a UE connected to a serving cell via RRC (e.g., UE in RRC_CONNECTED) transmits a measurement report. The measurement report may be an L3 measurement report. The base station (or source base station / serving cell) performs LTM candidate preparation (e.g., LTM candidate preparation) based on the measurement report transmitted from the UE.
[0054] The base station performs LTM candidate configuration (e.g., LTM candidate configuration) and execution conditions for candidate cells using RRC (e.g., RRC reconfiguration). LTM candidate configuration may include information about candidate cells in the UE. Execution conditions may be set in the UE for each candidate cell (or for multiple / all candidate cells) through the setting of execution conditions for candidate cells.
[0055] The setting of implementation conditions for candidate cells may be subject to either Option 1 or Option 2.
[0056] Early sync: The UE performs early sync with candidate cells (e.g., Early sync). DL / UL early sync with candidate cells may be performed by the UE after the RRC setting of the LTM candidate cells (e.g., RRC reset).
[0057] 《LTM Execution》 The UE performs measurements (e.g., L1 measurements) on the configured candidate cells and sends a measurement report. The measurement report may be an L1 measurement report.
[0058] The base station (or source base station / serving cell) makes a conditional LTM (CLTM) determination based on the measurement report transmitted from the UE. For example, the base station determines the conditional LTM for one or more candidate target cell(s) for which the implementation conditions can be evaluated (or for which the UE needs to evaluate the implementation conditions). The one or more candidate target cells for which the implementation conditions can be evaluated may be determined based on the measurement report transmitted from the UE.
[0059] The base station may transmit a predetermined MAC CE to the UE. The base station may use the predetermined MAC CE to instruct the UE about one or more candidate target cells for conditional LTM (or those subject to evaluation of implementation conditions). The predetermined MAC CE may trigger the UE to evaluate the implementation conditions.
[0060] The UE may initiate an implementation evaluation for candidate target cells indicated by a designated MAC CE. If there are target cells that meet the implementation conditions, the UE may perform an LTM (or mobility) on those target cells. For example, if there are candidate cells that meet the implementation conditions, the UE may detach from the source (e.g., source cell) and apply the settings (e.g., target configurations) of the target cell to which it will switch.
[0061] For example, if a predetermined MAC CE indicates multiple candidate cells (or candidate target cells), the UE may consider the implementation conditions corresponding to each candidate cell (or implementation conditions common to multiple candidate cells) to determine the specific target cell for mobility / cell switching. The predetermined MAC CE may also indicate implementation conditions / events corresponding to each candidate cell (or common to multiple candidate cells).
[0062] The UE may perform a random access procedure on the selected target cell (for example, the cell to which the switch will occur) (RACH-based CLTM).
[0063] For example, if the UE does not have a valid Timing Advance (TA) for the target cell / candidate cell (or the cell to which it will switch), a random access procedure may be performed to obtain the TA value for the target cell. On the other hand, if the UE has a valid Timing Advance for the target cell / candidate cell (or the cell to which it will switch), the random access procedure does not need to be performed (or the random access procedure may be omitted / skipped). Note that the random access procedure may be performed if there is a valid TA for the target cell.
[0064] The UE may determine whether to apply a random access procedure after receiving a predetermined MAC CE based on at least one of the predetermined MAC CE and RRC parameters (for example, RRC parameters related to setting the TA acquisition method). For example, the UE may determine whether to apply a random access procedure based on the value of a predetermined field included in the predetermined MAC CE (for example, the timing advance command field). Alternatively, the UE may determine whether to apply a random access procedure based on the TA acquisition method set by the RRC parameters (or the TA acquisition method and the value of the predetermined field of the predetermined MAC CE).
[0065] Note that while Figure 3 shows a case where MAC CE is used to specify candidate target cells for conditional LTM (or candidate target cells for evaluating implementation conditions), this is not the only possible case. For example, DCI may be used to specify information about candidate target cells for conditional LTM to the UE. Alternatively, MAC CE may be used to specify the correspondence (or mapping) between information about multiple candidate target cells for conditional LTM (or multiple candidate target cells and implementation conditions for conditional LTM) and code points in predetermined fields of DCI, and DCI may then specify a particular candidate target cell for conditional LTM.
[0066] 《LTM Completion》 The LTM cell switching procedure may be completed when the UE sends a predetermined message to the target cell / candidate cell.
[0067] In the case of a RACH-based LTM, the UE may determine that the LTM has been successfully executed if the random access procedure completes successfully.
[0068] In the case of a RACH-less LTM, the UE may determine that the LTM has been successfully completed when the UE determines that the network has successfully received the initial UL data. For example, in a RACH-less LTM, the UE may send an RRC reconfiguration complete message and the initial data to the target cell. The UE may determine that it has successfully received the initial UL data by receiving a PDCCH addressing the UE's C-RNTI in the target cell. This PDCCH corresponds to a PDCCH that schedules a new transmission following the initial UL data.
[0069] [Conditional LTM Operation Example 2] Figure 4 shows a second example of conditional LTM operation. In Figure 4, the steps of conditional LTM operation are shown as LTM preparation (e.g., CLTM preparation), early sync and CLTM execution (e.g., Early sync and CLTM execution), and LTM completion (e.g., CLTM completion), but the steps of LTM are not limited to these. Some steps (or actions included in steps) may be omitted, the order of actions included in some steps and other actions included in other steps may be swapped, and other steps (or other actions) may be added.
[0070] 《LTM preparation》 This can be performed in the same manner as the LTM preparation shown in Figure 3.
[0071] Early sync and LTM execution: The UE performs early sync with candidate cells (e.g., Early sync) and LTM execution.
[0072] The UE may perform early DL synchronization with candidate cells after setting the RRC of LTM candidate cells (e.g., resetting the RRC). For example, the UE may perform DL synchronization on the configured candidate cells.
[0073] The UE performs measurements (e.g., L1 measurements) on the configured candidate cells and sends a measurement report. The measurement report may be an L1 measurement report.
[0074] The base station (or source base station / serving cell) makes a conditional LTM (CLTM) determination based on the measurement report transmitted from the UE. For example, the base station determines the conditional LTM for one or more candidate target cell(s) for which the implementation conditions can be evaluated (or for which the UE needs to evaluate the implementation conditions). The one or more candidate target cells for which the implementation conditions can be evaluated may be determined based on the measurement report transmitted from the UE.
[0075] The base station may transmit a predetermined MAC CE to the UE. The base station may use the predetermined MAC CE to instruct the UE about one or more candidate target cells for conditional LTM (or those subject to evaluation of implementation conditions). The predetermined MAC CE may trigger the UE to evaluate the implementation conditions.
[0076] The UE may perform DL synchronization with the candidate cell after setting the RRC of the LTM candidate cell (e.g., RRC reset). In this case, the UE may perform UL synchronization with the candidate target cell for the conditional LTM instructed by a predetermined MAC CE. By performing UL synchronization after receiving a predetermined MAC CE in this way, it is possible to reduce the number of cells to which UL synchronization is performed.
[0077] Furthermore, the UE may initiate an implementation evaluation for candidate target cells indicated by a predetermined MAC CE. If there are target cells that meet the implementation conditions, the UE may perform an LTM (or mobility) on those target cells. For example, if the implementation conditions are met, the UE may detach from the source (e.g., source cell) and apply the settings (e.g., target configurations) of the target cell to which it will switch. The UE may also perform UL synchronization after the implementation evaluation.
[0078] For example, if a predetermined MAC CE indicates multiple candidate cells (or candidate target cells), the UE may consider the implementation conditions corresponding to each candidate cell (or implementation conditions common to multiple candidate cells) to determine the specific target cell for mobility / cell switching. The predetermined MAC CE may also indicate implementation conditions / events corresponding to each candidate cell (or common to multiple candidate cells).
[0079] The UE may perform a random access procedure on the selected target cell (for example, the cell to which the switch will occur) (RACH-based CLTM).
[0080] For example, if the UE does not have a valid Timing Advance (TA) for the target cell / candidate cell (or the cell to which it will switch), a random access procedure may be performed to obtain the TA value for the target cell. On the other hand, if the UE has a valid Timing Advance for the target cell / candidate cell (or the cell to which it will switch), the random access procedure does not need to be performed (or the random access procedure may be omitted / skipped). Note that the random access procedure may be performed if there is a valid TA for the target cell.
[0081] The UE may determine whether to apply a random access procedure after receiving a predetermined MAC CE based on at least one of the predetermined MAC CE and RRC parameters (for example, RRC parameters related to setting the TA acquisition method). For example, the UE may determine whether to apply a random access procedure based on the value of a predetermined field included in the predetermined MAC CE (for example, the timing advance command field). Alternatively, the UE may determine whether to apply a random access procedure based on the TA acquisition method set by the RRC parameters (or the TA acquisition method and the value of the predetermined field of the predetermined MAC CE).
[0082] Note that while Figure 4 shows a case where MAC CE is used to specify candidate target cells for conditional LTM (or candidate target cells for evaluating implementation conditions), it is not limited to this. For example, DCI may be used to specify information about candidate target cells for conditional LTM to the UE. Alternatively, MAC CE may be used to specify the correspondence (or mapping) between information about multiple candidate target cells for conditional LTM (or multiple candidate target cells and implementation conditions for conditional LTM) and code points in predetermined fields of DCI, and DCI may then specify a particular candidate target cell for conditional LTM.
[0083] 《LTM Completion》 This can be performed in the same way as the LTM completion shown in Figure 3.
[0084] [Example of Target Cell Operation in Conditional LTM] Figure 5 shows an example of target cell operation in conditional LTM. In Figure 5, the steps of conditional LTM operation are shown as LTM preparation (e.g., CLTM preparation), early sync (e.g., Early sync), LTM execution (e.g., CLTM execution), and LTM completion (e.g., CLTM completion) (example in Figure 3), but the steps of LTM are not limited to these. Some steps (or operations included in steps) may be omitted, the order of operations included in some steps and other operations included in other steps may be swapped (e.g., example in Figure 4), or other steps (or other operations) may be added.
[0085] 《LTM preparation》 During LTM preparation, a UE connected to the serving cell via RRC (e.g., UE in RRC_CONNECTED) sends a measurement report. The measurement report may be an L3 measurement report.
[0086] The base station (or source base station / serving cell) prepares LTM candidates (e.g., LTM candidate preparation) based on the measurement report transmitted from the UE. In this case, information may be exchanged / shared among multiple candidate cells (which may include serving cells). The information exchanged / shared among multiple candidate cells may include at least one of the following: information regarding the measurement report reported by the UE, information regarding the configuration of the candidate cells to be set, and information regarding the implementation conditions for each candidate cell.
[0087] The base station performs LTM candidate configuration (e.g., LTM candidate configuration) and execution conditions for candidate cells using RRC (e.g., RRC reconfiguration). LTM candidate configuration may include information about candidate cells in the UE. Execution conditions may be set in the UE for each candidate cell (or for multiple / all candidate cells) through the setting of execution conditions for candidate cells.
[0088] The setting of implementation conditions for candidate cells may be governed by Option 2-1 or Option 2-2.
[0089] Early sync: The UE performs early sync with the candidate cell. DL / UL early sync with the candidate cell may be performed by the UE after the RRC setting of the LTM candidate cell (e.g., RRC reset). UL early sync may be performed after the transmission of the measurement report (e.g., L1 measurement report) of the LTM implementation step, or after receiving a predetermined MAC CE.
[0090] 《LTM Execution》 The UE performs measurements (e.g., L1 measurements) on the configured candidate cells and sends a measurement report. The measurement report may be an L1 measurement report.
[0091] The base station (or source base station / serving cell) makes a conditional LTM (CLTM) determination based on the measurement report transmitted from the UE. For example, the base station determines the conditional LTM for one or more candidate target cell(s) for which the implementation conditions can be evaluated (or for which the UE needs to evaluate the implementation conditions). The one or more candidate target cells for which the implementation conditions can be evaluated may be determined based on the measurement report transmitted from the UE.
[0092] The base station may transmit a predetermined MAC CE to the UE. The base station may use the predetermined MAC CE to instruct the UE about one or more candidate target cells for conditional LTM (or those subject to evaluation of implementation conditions). The predetermined MAC CE may trigger the UE to evaluate the implementation conditions.
[0093] Furthermore, the base station may notify candidate cells of information regarding the conditional LTM (CLTM) determination. For example, the base station may notify candidate cells of information regarding one or more candidate target cells for the conditional LTM (or those subject to evaluation of implementation conditions). The candidate cells to which this information is notified may be limited to those selected as candidate cells for the conditional LTM (CLTM), or not (for example, candidate cells not selected as candidate cells for the conditional LTM (CLTM) may also be notified).
[0094] The UE may initiate an implementation evaluation for candidate target cells indicated by a designated MAC CE. If there are target cells that meet the implementation conditions, the UE may perform an LTM (or mobility) on those target cells. For example, if the implementation conditions are met, the UE may detach from the source (e.g., source cell) and apply the settings (e.g., target configurations) of the target cell to which it will switch.
[0095] The UE may perform a random access procedure on the selected target cell (for example, the cell to which it will switch). For example, if the UE does not have a valid timing advance for the target cell / candidate cell (or the cell to which it will switch), it may perform a random access procedure to obtain the TA value for the target cell. On the other hand, if the UE has a valid timing advance (TA) for the target cell / candidate cell (or the cell to which it will switch), it does not need to perform a random access procedure (or may omit / skip the random access procedure).
[0096] The UE may determine whether to apply a random access procedure after receiving a predetermined MAC CE based on at least one of the predetermined MAC CE and RRC parameters (for example, RRC parameters related to setting the TA acquisition method). For example, the UE may determine whether to apply a random access procedure based on the value of a predetermined field included in the predetermined MAC CE (for example, the timing advance command field). Alternatively, the UE may determine whether to apply a random access procedure based on the TA acquisition method set by the RRC parameters (or the TA acquisition method and the value of the predetermined field of the predetermined MAC CE).
[0097] Note that while this example shows the specification of candidate target cells for conditional LTM (or candidate target cells for evaluating implementation conditions) using MAC CE, it is not limited to this. For example, information regarding candidate target cells for conditional LTM may be specified to the UE via DCI. Alternatively, MAC CE may specify the correspondence (or mapping) between information regarding multiple candidate target cells for conditional LTM (or multiple candidate target cells and implementation conditions for conditional LTM) and code points in predetermined fields of DCI, and a specific candidate target cell for conditional LTM may be specified via DCI.
[0098] 《LTM Completion》 The LTM cell switching procedure may be completed when the UE sends a predetermined message to the selected (for example, the target cell / candidate cell to which the switch will be made) cell.
[0099] In the case of a RACH-based LTM, the UE may determine that the LTM has been successfully executed if the random access procedure completes successfully.
[0100] [Conditional LTM Operation Example 3] Figure 6 shows a third example of conditional LTM operation. In Figure 6, the steps of conditional LTM operation are shown as LTM preparation (e.g., CLTM preparation), early sync (e.g., Early sync), LTM execution (e.g., CLTM execution), and LTM completion (e.g., CLTM completion), but the steps of LTM are not limited to these. Some steps (or operations included in the steps) may be omitted, the order of operations included in some steps and other operations included in other steps may be swapped, and other steps (or other operations) may be added. Furthermore, Figure 6 may be suitably applied to RACH-less CLTM.
[0101] 《LTM preparation》 In LTM preparation, a UE connected to a serving cell via RRC (e.g., UE in RRC_CONNECTED) transmits a measurement report. The measurement report may be an L3 measurement report. The base station (or source base station / serving cell) performs LTM candidate preparation (e.g., LTM candidate preparation) based on the measurement report transmitted from the UE.
[0102] The base station performs LTM candidate configuration (e.g., LTM candidate configuration) and execution conditions for candidate cells using RRC (e.g., RRC reconfiguration). LTM candidate configuration may include information about candidate cells in the UE. Execution conditions may be set in the UE for each candidate cell (or for multiple / all candidate cells) through the setting of execution conditions for candidate cells.
[0103] The setting of implementation conditions for candidate cells may be subject to either Option 1 or Option 2.
[0104] Early sync: The UE performs early sync with the candidate cell. DL / UL early sync with the candidate cell may be performed by the UE after the RRC setting of the LTM candidate cell (e.g., RRC reset). UL early sync may be performed after the transmission of the measurement report (e.g., L1 measurement report) of the LTM implementation step, or after receiving a predetermined MAC CE.
[0105] 《LTM Execution》 The UE performs measurements (e.g., L1 measurements) on the configured candidate cells and sends a measurement report. The measurement report may be an L1 measurement report.
[0106] The base station (or source base station / serving cell) makes a conditional LTM (CLTM) determination based on the measurement report transmitted from the UE. For example, the base station determines the conditional LTM for one or more candidate target cell(s) for which the implementation conditions can be evaluated (or for which the UE needs to evaluate the implementation conditions). The one or more candidate target cells for which the implementation conditions can be evaluated may be determined based on the measurement report transmitted from the UE.
[0107] The base station may transmit a predetermined MAC CE to the UE. The base station may use the predetermined MAC CE to instruct the UE about one or more candidate target cells for conditional LTM (or those subject to evaluation of implementation conditions). The predetermined MAC CE may trigger the UE to evaluate the implementation conditions.
[0108] The UE may initiate an implementation evaluation for candidate target cells indicated by a designated MAC CE. If there are target cells that meet the implementation conditions, the UE may perform an LTM (or mobility) on those target cells. For example, if the implementation conditions are met, the UE may detach from the source (e.g., source cell) and apply the settings (e.g., target configurations) of the target cell to which it will switch.
[0109] After evaluating the implementation conditions, the UE may determine mobility or cell switching (or select a new target cell) and then send at least one of the following messages to the new target cell: a message indicating the completion of RRC reconfiguration (e.g., RRCReconfigurationComplete) and a MAC CE (e.g., a new MAC CE). The MAC CE may then instruct the new target cell to make a CLTM decision by the UE.
[0110] 《LTM Completion》 The LTM cell switching procedure may be completed when the UE sends a predetermined message / MAC CE to the target cell / candidate cell.
[0111] In the case of a RACH-less LTM, the UE may determine that the LTM has been successfully completed when the UE determines that the network has successfully received the initial UL data. For example, in a RACH-less LTM, the UE may send an RRC reconfiguration complete message / MAC CE and the initial data to the target cell. The UE may determine that it has successfully received the initial UL data by receiving a PDCCH addressing the UE's C-RNTI in the target cell. This PDCCH corresponds to a PDCCH that schedules a new transmission following the initial UL data.
[0112] [Conditional LTM Operation Example 4] Figure 7 shows a fourth example of conditional LTM operation. In Figure 7, the steps of conditional LTM operation are shown as LTM preparation (e.g., CLTM preparation), early sync (e.g., Early sync), LTM execution (e.g., CLTM execution), and LTM completion (e.g., CLTM completion), but the steps of LTM are not limited to these. Some steps (or operations included in the steps) may be omitted, the order of operations included in some steps and other operations included in other steps may be swapped, and other steps (or other operations) may be added. Furthermore, Figure 7 may be suitably applied to RACH-less CLTM.
[0113] 《LTM preparation》 This can be done in the same way as the LTM preparation shown in Figure 6.
[0114] Early sync can be performed in the same way as the early sync shown in Figure 6.
[0115] 《LTM Execution》 The UE performs measurements (e.g., L1 measurements) on the configured candidate cells and sends a measurement report. The measurement report may be an L1 measurement report.
[0116] The base station (or source base station / serving cell) makes a conditional LTM (CLTM) determination based on the measurement report transmitted from the UE. For example, the base station determines the conditional LTM for one or more candidate target cell(s) for which the implementation conditions can be evaluated (or for which the UE needs to evaluate the implementation conditions). The one or more candidate target cells for which the implementation conditions can be evaluated may be determined based on the measurement report transmitted from the UE.
[0117] The base station may transmit a predetermined MAC CE to the UE. The base station may use the predetermined MAC CE to instruct the UE about one or more candidate target cells for conditional LTM (or those subject to evaluation of implementation conditions). The predetermined MAC CE may trigger the UE to evaluate the implementation conditions.
[0118] The UE may initiate an implementation evaluation for candidate target cells indicated by a designated MAC CE. If there are target cells that meet the implementation conditions, the UE may perform an LTM (or mobility) on those target cells. For example, if the implementation conditions are met, the UE may detach from the source (e.g., source cell) and apply the settings (e.g., target configurations) of the target cell to which it will switch.
[0119] After the UE has determined mobility or cell switching (or selected a new target cell) based on an evaluation of the implementation conditions, it may transmit a predetermined MAC CE to the current serving cell (e.g., the serving cell before the cell switch). The MAC CE may instruct the current serving cell to make a CLTM decision by the UE. The predetermined MAC CE may include at least one of the following: information about the selected target cell and information about the latest L1 beam measurement / event-triggered L1 beam measurement / reported results of the L1 beam measurement.
[0120] The UE may, after sending a predetermined MAC CE to the current serving cell, start a predetermined timer (or a new timer) and begin monitoring the PDCCH transmitted from the newly reported / instructed target cell. For example, the UE may start a predetermined timer after sending a predetermined MAC CE and control the monitoring of the PDCCH until the predetermined timer expires.
[0121] 《LTM Completion》 If the UE detects a DCI format with C-RNTI applied (e.g., DCI format 1_0 / 0_0, etc.) from the target cell before the predetermined timer expires, it may determine that the CLTM was successful (or completed). Otherwise, it may determine that the CLTM failed.
[0122] [Conditional LTM Operation Example 5] Figure 8 shows a fifth example of conditional LTM operation. In Figure 8, the steps of CLTM operation are shown as LTM preparation (e.g., CLTM preparation), early sync (e.g., Early sync), and LTM execution (e.g., CLTM execution), but the steps of LTM are not limited to these. Some steps (or operations included in steps) may be omitted, the order of operations included in some steps and other operations included in other steps may be swapped, and other steps (or other operations) may be added. For example, at least some of the processes in Figures 3 to 7 may be added.
[0123] 《LTM preparation》 During LTM preparation, a UE connected to a serving cell via RRC (e.g., UE in RRC_CONNECTED) transmits a measurement report. The measurement report may be an L3 measurement report. The base station (or source base station / serving cell) decides to perform LTM based on the measurement report transmitted from the UE.
[0124] The base station (Source gNB) sends an RRC reconfiguration message to the UE containing the LTM candidate cell settings for one or more candidate cells. The UE saves the LTM candidate cell settings and sends an RRC reconfiguration complete message to the gNB. The base station (Source gNB) sends signaling containing the LTM candidate cell settings to the base station (Candidate gNB) of the candidate cell.
[0125] Early sync: The UE performs early sync with candidate cells (e.g., Early sync). DL / UL early sync with candidate cells may be performed by the UE after the RRC setting of the LTM candidate cells (e.g., RRC reset).
[0126] 《LTM Execution》 The UE evaluates whether the event is met, and if so, sends a second UL signal (e.g., UL cell switch command, event trigger report) to the base station (Source gNB) indicating the possibility of a cell switch using the RS / TCI state of the candidate cell. The base station (Source gNB) then sends a signaling signal including the target cell ID and TCI state ID to the base station (Candidate gNB) of the candidate cell.
[0127] Since the UE can send a UL signal notifying of the possibility of a cell switch before the cell switch decision is made, it does not need to send a UL signal when the LTM makes a cell switch decision. In other words, it is possible to avoid the situation where the gNB cannot receive a UL signal when the UE is at the cell edge. The base station (Source gNB) can forward the above signaling, including the target cell ID and TCI status ID, to the base station (Candidate gNB) (Target gNB) before the cell switch decision is made, so that the Target gNB can secure the UE's resources early. Note that in Rel8 LTMs, this signaling is forwarded when the LTM makes a cell switch decision.
[0128] The UE evaluates whether the second event is met, and if so, determines whether to perform an LTM cell switch. The second event may be the same as or different from the first event. For example, the UE may determine whether to perform an LTM cell switch and execute the cell switch procedure if the event is met for a predetermined time, or if all events are met within the predetermined time.
[0129] The UE applies the target cell configuration. Then, the UE, base station (Source gNB), base station (Candidate gNB), and (Target gNB) perform the cell switch procedure.
[0130] The event for sending the first UL signal and the event for sending the second UL signal may be the same or different. The event for sending the first UL signal and the condition for performing the cell switch procedure after sending the second UL signal may be the same.
[0131] (TA acquisition) When a UE sends a UL for a candidate cell, it is also possible to consider the TA corresponding to that candidate cell when sending the UL. If the TA of a candidate cell is considered, the UE will need to acquire the TA of the candidate cell (for example, TA acquisition of candidate cells).
[0132] Several methods for obtaining the TA of candidate cells are possible, including TA acquisition using RACH (e.g., RACH-based solutions) and TA acquisition without RACH (RACH-less solutions). TA acquisition using RACH may support methods with and without RAR monitoring. The TA acquisition method may be interpreted as a TA acquisition scheme, TA acquisition type, or TA acquisition procedure. In this disclosure, TA acquisition, TA measurement, TA calculation, TA determination, and TA determination may be interpreted interchangeably.
[0133] For example, the UE may obtain the candidate cell's TA by sending a RACH (e.g., PDCCH ordered RACH) instructed / triggered by the PDCCH to the candidate cell. Information about the candidate cell's TA (e.g., TA value) may be included in the RACH response signal (e.g., RAR). The RAR may be transmitted from the serving cell or from the candidate cell. Alternatively, the candidate cell's TA may be obtained using a RACH triggered by the UE or a RACH triggered at a higher layer in the network. The PDCCH order may be triggered by the source cell (or serving cell) alone.
[0134] Alternatively, the UE may obtain the TA of a candidate cell by transmitting a signal other than RACH to the candidate cell. Information regarding the candidate cell's TA (e.g., TA value) may be provided to the UE by the base station. As a signal other than RACH, for example, SRS may be applied (SRS-based TA measurement (e.g., SRS-based TA measurement)).
[0135] Alternatively, the UE may measure / calculate / acquire the TA for a candidate cell based on DL signals (e.g., downlink reference signals) transmitted from each cell (e.g., candidate cell / serving cell). The method by which the UE acquires the TA for a candidate cell based on DL signals transmitted from one or more cells may be called UE-based TA measurement.
[0136] In UE-based TA measurement, the downlink reference signal may be a predetermined DL signal (e.g., a synchronization signal block (e.g., SSB) / CSI-RS, etc.). For example, the UE may measure the difference in reception timing of DL signals from multiple cells (or two cells) and obtain the TA of a candidate cell.
[0137] Multiple cells may include a reference cell (e.g., a serving cell). In this case, the UE may calculate the required TA for the candidate cell based on the reception timing of the reference cell (and the TA value of the reference cell) and the timing difference (e.g., T) between the reference cell and the candidate cell. The UE may also obtain the TA of the candidate cell using a timing advance command (TAC) sent from the serving cell.
[0138] (UE-initiated Beam Report (UEIBR)) In future wireless communication systems (e.g., Rel. 19 and beyond), support for event-based beam reporting is being considered. Event-based beam reporting may also be called event-triggered beam reporting, or UE-initiated beam reporting (UEIBR).
[0139] Beam management (UEIBM) initiated by UEIBR / UE can be used for measurement reporting, beam switching, cell switching, etc.
[0140] At UEIBR, the report content is being considered to include at least one of the following pieces of information in the beam report: • Beam / reference signal index (e.g., CSI-RS / SSB resource index / indicator). • Measurement result (e.g., L1-RSRP / SINR (absolute / relative)). • Number of beams / RSs reported. • Whether or not serving beams are included in the beam report.
[0141] Regarding the reported beam / RS number information, the base station / network and the UE need to have a common understanding of the size of the beam report (e.g., UCI), so it is preferable that this information is included in the beam report reported by the UE.
[0142] In this case, the UCI may be reported in two parts. For example, the size of the UCI transmitted in the second part (step), which may be a fixed size, may indicate the size of the UCI transmitted in the second part (step).
[0143] In this case, the UCI may be encoded in two parts. For example, the size of the second part of the UCI may be indicated by the first part of the UCI (which may have a fixed size).
[0144] Events related to UEIBR (the events mentioned above) may be broadly categorized into the following event types: • Event 1: The quality of the current beam falls below a certain threshold. • Event 2: The quality of at least one new beam (e.g., L1-RSRP) is better than a certain threshold compared to the quality of the current beam. • Event 3: The quality of a new beam is better than a certain threshold. • Event 4: The quality of the current beam falls below a first threshold, and the quality of at least one new beam is better than a second threshold. • Event 5: The absolute difference between the quality of the current beam and the quality of at least one new beam falls below a certain threshold. • Event 6: The current beam is no longer included in the best K beams (more than 1: K > 1) (of the beams set up for measurement / reporting). - Event 7: The quality of at least one new beam (e.g., L1-RSRP) is above the threshold of the RS derived from the best quality activated TCI state up to the Mth (M is 1 or greater, and M may be set by RRC). - Event 8: The quality of M (more than 1: M > 1) new beams (e.g., L1-RSRP) is above the threshold of the current beam. - Event 9: The quality of at least one new beam (e.g., L1-RSRP) is above the threshold of the set reference RS (which may be SSB / CSI-RS).
[0145] Note that this type of event does not exclude the events described above. For example, this type of event may be interpreted as a substitute for the events described above as appropriate.
[0146] Furthermore, at least two of the above events may be combined and defined.
[0147] <<Beam / UCI Format / RS Settings in UEIBR>> In addition, in a specific event (e.g., Event 2), the "current beam" may be determined / derived based on the QCL RS of the indicated TCI state (e.g., QCL source RS). In this case, the QCL RS of the indicated TCI state may support at least one of SSB and CSI-RS.
[0148] For example, for the "current beam" in a specific event (e.g., event 2), at least one of the following beam options 2a and 2c may be supported: • Beam option 2a: The RS corresponding to the current beam is implicitly derived / determined based on the QCL RS of the indicated TCI state. • Beam option 2c: The RS corresponding to the current beam is explicitly set / indicated using RRC signaling / MAC CE.
[0149] For example, for a "new beam" in Event 2, at least one of the following beam options 3a to 3c may be supported: • Beam option 3a: The RS corresponding to the new beam is [explicitly] set using RRC signaling (e.g., resetting of existing RS measurements, or setting parameters for the TCI state (e.g., TCI-State)) / MAC CE. • Beam option 3b: The RS corresponding to the new beam is [implicitly] derived / determined based on the QCL RS of the activated TCI state (active TCI state). • Beam option 3c: The RS corresponding to the new beam is [implicitly] derived / determined based on the QCL RS of one or more set TCI states (set TCI states).
[0150] The beam option names used in this disclosure are merely examples and are not limited to those used in this disclosure.
[0151] Furthermore, for beam reports (UCI format) for specific events (e.g., Event 2), it is being considered to allow for variable or fixed beam report sizes.
[0152] For example, regarding the UCI format / content (which may also be called the reporting format / content), support for the following format options 1 / 1a / 1b / 2 / 3 is being considered: • Format option 1: The UCI size is variable, and N beams are reported in one reporting instance (where N is from 1 to N max ). N beams satisfy the conditions for event 2. Maximum number of N (N max ) is set by the base station. • Format option 1a: UCI size is variable and N beams are reported in one reporting instance (N is from 1 to N max ). At least one of the N reported beams satisfies the conditions for event 2. Maximum number of N (N max ) is set by the base station. • Format option 1b: The UCI size is fixed (independent of N), and N beams are reported in one reporting instance (N is from 1 to N) max ). N reported beams satisfy the conditions for event 2. Maximum number of N (N max ) is set by the base station. ・Format option 2: The UCI size is fixed, and one beam is reported in one reporting instance. The reported beam satisfies the conditions for event 2. ・Format option 3: The UCI size is fixed, and N beams are reported in one reporting instance (N is a number greater than 1). At least one of the N reported beams satisfies the conditions for event 2. N is set by the base station.
[0153] Please note that the above format options are merely examples, and other options may also be supported.
[0154] For the N beams in the above format option 3 (for example, dependent on event 2), a method for reporting the "current beam" is being considered.
[0155] For example, RRC signaling may be used to configure / enable / disable whether or not to always report the current beam to the UE in the beam report.
[0156] For example, if activation is set by the RRC signaling, the current beam and N beams based on RS measurements for new beams may be reported. In this case, the current beam may or may not be included in the N beams.
[0157] For example, if deactivation is set by the RRC signaling, N beams based on RS measurements for new beams may be reported.
[0158] RS configuration for new beams for Event 2 is being considered. At least one of the following configuration options 1 to 3 may be supported for the method of configuring the RS: • RS configuration option 1: The RS for the new beam is [explicitly] configured in a single RS resource set associated with the CSI reporting configuration. • RS configuration option 2: A list of RS for new beam measurements is configured using RRC signaling, and a subset of this list is activated for new beam measurements using MAC CE. • RS configuration option 3: A list of RS resources for new beam measurements is configured using RRC signaling, and a subset of this list is provided for new beam measurements by an indicated TCI state.
[0159] Figure 9 shows an example of RS configuration for a new beam at UEIBR. In the example shown in Figure 9, the CSI Report Configuration (CSI-ReportConfig) includes the CSI Resource Configuration (CSI-ResourceConfig), and the CSI Resource Configuration includes the CSI Resource Set List. The CSI Resource Set List also includes (CSI) Resource Sets #0 to #M, of which Resource Set #0 includes RS #0 to #N as CSI-RS resources.
[0160] In the example shown in Figure 9, RS setting option 1 configures the RS for the new beam in a single RS resource set associated with a single CSI reporting setting. Note that in RS setting option 1, MAC CE may be used to update the RS.
[0161] In the example shown in Figure 9, RS setting option 2 sets up a list of RSs for the new beam using RRC signaling, and MAC CE activates a portion of this list (RS #0 and #1 in the example in Figure 9) for the new beam measurement. In other words, in RS setting option 2, MAC CE may be used to activate the RSs.
[0162] In the example shown in Figure 9, RS setting option 3 sets a list of RS resources (multiple RS resource sets) for the new beam using RRC signaling, and a subset of this list is provided for the new beam measurement based on the indicated TCI status. The selection rules for the RS resource sets in this case require further consideration.
[0163] RS configuration option 1 has the advantage of being simple from an implementation standpoint and being able to follow existing CSI frameworks. On the other hand, there are concerns that the load on measurement by UE will increase, and that separate RS resource configuration will be required for UEIBR execution. However, this disadvantage can be resolved by using multiple events for a single CSI resource set.
[0164] RS setting option 2 can reduce the load on UE measurement, and for example, UEIBR can be executed by activation via MAC CE. On the other hand, there are concerns that such MAC CE definition will be required, and that the selection of RS to be activated by the network will be necessary.
[0165] RS configuration option 3 can reduce the load on the UE when the number of RSs in the CSI resource set is small, and allows UEIBR to be run using different resource sets depending on the indicated TCI state. On the other hand, it is necessary to define new rules for identifying subsets of RS resources within the CSI resource set, and there are concerns that the load on UE measurement will depend on the size of the CSI resource set.
[0166] Although Event 2 was used as the main example in the above explanation, the same principles apply to any other event.
[0167] By utilizing such UEIBR / UEIBM, delays and UL resource overhead can be reduced compared to existing beam reporting.
[0168] Furthermore, the following modes may be supported in UCI-based UEIBR procedures.
[0169] <<Mode A>> Mode A relates to the dynamic scheduling of UCI by NW (gNB). That is, in Mode A, resources for UCI are scheduled by gNB. Mode A may be a basic function of the UE (a UE that supports UEIBR may naturally support this function).
[0170] Step 1: The UE transmits a first UL channel (e.g., PUCCH). The first UL channel is a UL channel that pre-notifies / requests a second UL channel (e.g., PUCCH) for transmitting beam reports, and may consist of one or more bits.
[0171] Step 2: The UE detects the DCI format indicating the second UL channel resource.
[0172] Step 3: The UE transmits the beam report using the resource (UCI) on the second UL channel.
[0173] In mode A, a 1-bit instruction in at least the first UL channel (PUCCH) may be supported to request resources on the second UL channel for transmitting beam reports.
[0174] In this case, periodic PUCCH resources (PUCCH format 0 / 1) can be set up by dedicated upper-layer signaling.
[0175] <<Mode B>> Mode B relates to the UCI in the pre-configured resources for the second UL channel.
[0176] Step 1: The UE transmits a first UL channel (e.g., PUCCH). The first UL channel is a UL channel that notifies a second UL channel for transmitting beam reports, and may consist of one or more bits.
[0177] Step 2: The UE transmits a beam report on the second UL channel (for example, using a specific resource (UCI) within the channel).
[0178] Note that the notification in Step 1 may be included in a separate reporting instance from the beam report in Step 2.
[0179] In mode B, a one-bit instruction on at least the first UL channel (PUCCH) may be supported to indicate that the second UL channel will transmit a beam report.
[0180] In this case, periodic PUCCH resources (PUCCH format 0 / 1) can be set up by dedicated upper-layer signaling.
[0181] In either mode A or B as described above, cross-CC (component carrier) beam reporting may be supported.
[0182] (Event-Triggered Beam Reporting for Mobility) The above-mentioned UEIBR (Event-Triggered Beam Reporting) can also be extended for mobility.
[0183] For example, the following LTM events are supported as L1 LTM measurement events, based on the beam quality of the serving cell and candidate cell: • Event LTM2: The serving cell's beam falls below the absolute threshold. • Event LTM3: The candidate cell's beam is offset better than the serving cell's beam. • Event LTM4: The candidate cell's beam is better than the absolute threshold. • Event LTM5: The serving cell's beam falls below absolute threshold 1 (first absolute threshold), and the candidate cell's beam is better than another absolute threshold 2 (second absolute threshold).
[0184] In addition to the events mentioned above, consideration is being given to which beams in the serving cell and adjacent cells should be used for event evaluation, as well as the necessity of event LTM1.
[0185] (Analysis) <Analysis 1> Examples of UL signaling (which may also be called UL cell switching commands) for requesting a trigger for cell switching in the CLTM mentioned above include MAC CE / UCI / PRACH / SRS, etc.
[0186] For example, if UCI is used as a UL cell switching command, it is conceivable to use the UEIBR specifications for MIMO for mobility (i.e., CLTM). The specific details of this case have not been sufficiently considered.
[0187] <Analysis 2> The CLTM described above can be used to improve the robustness of the LTM. To achieve this, it is desirable to avoid receiving DL cell switching commands. In this case, it is necessary to consider UL resources for UL cell switching commands. The specific details of this case have not been sufficiently examined.
[0188] Thus, the regulations concerning CLTM (regulations concerning event-triggered beam reporting) are not sufficiently clear. Without clear regulations, it may be impossible to achieve lower latency communication, potentially hindering improvements in communication quality and throughput.
[0189] Therefore, the inventors of this invention conceived a way to solve these problems.
[0190] The embodiments of this disclosure will be described in detail below with reference to the drawings. Each wireless communication method according to the embodiments may be applied individually or in combination.
[0191] (Various substitutions) In this disclosure, words enclosed in parentheses () may indicate an explanation of the preceding word (e.g., an explanation of spelling), a paraphrase, a specific example, or supplementary explanation. Also, in this disclosure, words enclosed in square brackets [] may be interpreted as part of the overall meaning of the text, or they may be interpreted as being excluded (ignored). Note that parentheses () and square brackets [] may be used for purposes / meanings other than those described above.
[0192] In this disclosure, "A / B" and "at least one of A and B" may be interpreted as mutually exclusive. In this disclosure, "A / B / C" may mean "at least one of A, B, and C".
[0193] In this disclosure, terms such as notice, activate, deactivate, indicate (or specify), select, configure, update, and determine may be interpreted interchangeably. In this disclosure, terms such as support, control, controllable, operate, and capable of operating may be interpreted interchangeably.
[0194] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-layer parameters, fields, Information Elements (IE), settings, etc., may be interpreted interchangeably. In this disclosure, Medium Access Control elements (MAC Control Elements (CE)), update commands, activation / deactivation commands, etc., may be interpreted interchangeably.
[0195] In this disclosure, the upper layer signaling may be any or a combination thereof, such as Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, and other messages (e.g., messages from the core network, such as positioning protocol messages (e.g., NR Positioning Protocol A (NRPPPa) / LTE Positioning Protocol (LPP)) messages).
[0196] In this disclosure, MAC signaling may include, for example, MAC Control Elements (MAC CEs) and MAC Protocol Data Units (PDUs). Broadcast information may include, for example, Master Information Blocks (MIBs), System Information Blocks (SIBs), Remaining Minimum System Information (RMSIs), and Other System Information (OSIs).
[0197] In this disclosure, physical layer signaling may include, for example, Downlink Control Information (DCI) and Uplink Control Information (UCI).
[0198] In this disclosure, terms such as drop, suspend, cancel, puncture, rate match, postpone, and not send may be interpreted interchangeably.
[0199] In this disclosure, terms such as index, identifier (ID), indicator, and resource ID may be interpreted interchangeably. In this disclosure, terms such as sequence, list, set, group, cluster, subset, and pool may be interpreted interchangeably.
[0200] In this disclosure, the terms used include: panel, UE panel, panel group, beam, beam group, precoder, Uplink (UL) transmit entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relationship, SRS Resource Indicator (SRI), Control Resource Set (CORESET), Physical Downlink Shared Channel (PDSCH), Codeword (CW), Transport Block (TB), Reference Signal (RS), Antenna port (e.g., Demodulation Reference Signal (DMRS) port), Antenna port group (e.g., DMRS port group), Group (e.g., Spatial relationship group, Code Division Multiplexing (CDM) group, Reference Signal group, CORESET group, Physical Uplink Control The following terms may be interchangeable: Channel (PUCCH) group, PUCCH resource group), resource (e.g., reference signal resource, SRS resource), resource set (e.g., reference signal resource set), CORESET pool, downlink Transmission Configuration Indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, quasi-co-location (QCL), QCL assumption, etc.
[0201] In this disclosure, base station, gNB, and network (NW) may be interpreted as interchangeable.
[0202] In this disclosure, cell group, serving cell group, master cell group (MCG), and secondary cell group (SCG) may be interpreted interchangeably. L1 / L2, L1 / L2 signaling, and DCI / MAC CE may be interpreted interchangeably. A serving cell may be replaced with a cell that transmits PDSCH. A candidate cell may mean a candidate cell that becomes a serving cell through L1 / L2 inter-cell mobility. L1 / L2-triggered mobility (LTM) and L1 / L2 inter-cell mobility may be interpreted interchangeably.
[0203] In this disclosure, cell, PCI, serving cell, source serving cell, source cell, CC, BWP, BWP within CC, and band may be interpreted interchangeably. In this disclosure, cell, PCI, cell with 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 current serving cell's PCI, another serving cell, and target cell may be interpreted interchangeably. A target cell may be a cell selected from among several candidate cells. In this disclosure, switch, change, and update may be interpreted interchangeably. A serving cell may be interpreted as a serving cell before a switch or a serving cell after a switch.
[0204] In this disclosure, event-based beam reporting, event-triggered beam reporting, UE-triggered beam reporting, UE-initiated beam reporting, event-triggered reporting / measurement, and UE-initiated beam management (UEIBM) are interchangeable.
[0205] In this disclosure, event-triggered [beam] reports may be interpreted interchangeably with beam reports, CSI reports, L1-RSRP beam reports, and L1-SINR beam reports. These reports may also be simply referred to as reports.
[0206] In this disclosure, the CSI report and the CSI report for LTMs Rel. 18 may be interpreted as mutually interchangeable.
[0207] In this disclosure, tables, mappings, associations, lists, formats, content, reports, etc., may be interpreted interchangeably.
[0208] In this disclosure, the (new) MAC CE, UCI, cell switching command, beam switching command, MAC CE for beam reporting, and MAC CE for cell switching may be interpreted as interchangeable.
[0209] In this disclosure, "report," "reporting resources," and "resources" may be interpreted interchangeably. For example, the first resource and the first report may be interpreted interchangeably, and the second resource and the second report may be interpreted interchangeably.
[0210] In this disclosure, the number of beams and the number of resources may be interpreted interchangeably.
[0211] In this disclosure, "Serving" may be interpreted as "Serving beam," "Serving cell," or "SpCell."
[0212] In this disclosure, "Neighbor" may be interpreted as any beam or cell other than a serving beam / serving cell / SpCell / SCell.
[0213] In this disclosure, the RS index and the L1-RSRP / SINR pair may be referred to as the L1 measurement report. That is, the L1 measurement report may include the RS index and the L1-RSRP / SINR pair.
[0214] In this disclosure, candidate cells, target cells, adjacent cells, cells, etc., may be interpreted interchangeably.
[0215] In this disclosure, the phrases "an event occurred" and "the conditions for the event were met" may be interpreted interchangeably.
[0216] In this disclosure, the beam, RS, and [L1 / L3] measurement results may be interpreted interchangeably.
[0217] In this disclosure, the measured RS may be the QCL source RS in an active TCI state / indicated TCI state.
[0218] In this disclosure, spatial domain filters, temporal domain filters, and domain filters may be interpreted as interchangeable.
[0219] In this disclosure, NW / BS / gNB may be interpreted as interchangeable.
[0220] In this disclosure, the current beam / new beam may correspond to at least one of the following: indicated TCI state, indicated TCI state, active TCI state, activated TCI state, set TCI state, and RS set in RRC.
[0221] In this disclosure, indicated TCI state, active TCI state, activated TCI state, set TCI state, configured TCI state, and RS configured in RRC may be interpreted interchangeably.
[0222] In this disclosure, the number of current beams / new beams may be one or more.
[0223] In this disclosure, the terms "new beam / RS," "candidate beam / RS," "measurement beam / RS," "beam for measurement / RS," etc., may be interpreted interchangeably.
[0224] In this disclosure, a novel type of UCI (novel UCI) may mean a UCI that is transmitted in multiple bits (and multiple steps / parts).
[0225] Each embodiment of this disclosure is applicable to any event.
[0226] In this disclosure, L1-RSRP may be interpreted as L1-SINR.
[0227] In this disclosure, conditions and thresholds may be interpreted interchangeably.
[0228] In this disclosure, the filtered value (measured value: L1-RSRP), the filtered value, and the L1-RSRP to which filtering by NW settings has been applied (NW-filtered L1-RSRP) may be interpreted interchangeably.
[0229] In this disclosure, CC, carrier, cell, serving cell, frequency, frequency carrier, carrier frequency, etc., may be interpreted interchangeably. In this disclosure, reporting of multiple CCs may be interpreted interchangeably with reporting of multiple events.
[0230] In this disclosure, reporting of a (current / measured) beam may mean reporting of the RS index (e.g., CSI-RS resource indicator (CRI) / SSB resource indicator (SSBRI)) and measurement results (e.g., L1-RSRP / RSRQ / SINR) corresponding to the (current / measured) beam. In this disclosure, information about a beam may mean the RS index / measurement results corresponding to the beam.
[0231] In this disclosure, “current beam” may mean “current beam of the current serving cell” in mobility.
[0232] In this disclosure, beam, RS, RS resource, RS resource set, RS index, RS indicator, RS ID, etc. may be interpreted interchangeably. In this disclosure, RS resource set, subset of RS resource, subset of RS, etc. may be interpreted interchangeably.
[0233] In this disclosure, the type of CSI reporting may be periodic, semi-persistent, or aperiodic. In other words, this disclosure is applicable to any type of CSI reporting.
[0234] In this disclosure, multiplexing (to multiplex / to be multiplexed) and mapping (to map / to be mapped) may be interpreted interchangeably.
[0235] In this disclosure, the multiple events may be any of the events described above (or a combination of multiple events).
[0236] In this disclosure, handover, handover as defined in Rel. 15, CHO, DAPS handover, LTM, CLTM, and cell switching may be interpreted as mutually exclusive.
[0237] In this disclosure, settings, upper layer signaling, upper layer parameters, RRC parameters (which may also be simply called parameters), RRC settings, etc., may be interpreted interchangeably.
[0238] (Wireless Communication Method) Embodiments of this disclosure can be broadly classified as follows: • First embodiment: UL cell switching command [UCI] for CLTM. • Second embodiment: UL cell switching command [UCI] for CLTM. • Third embodiment: Cancellation of UL resources and CLTM for UL cell switching command. • Fourth embodiment: Priority of UL cell switching command. The following will be explained based on these.
[0239] The UE may execute / control the CLTM and related operations by applying the provisions described above and the embodiments described below. The NW / BS / gNB may provide / transmit to the UE settings / instructions, etc., for the UE to implement such control. Furthermore, the NW / BS / gNB may perform various controls necessary to receive information, etc., transmitted from the UE.
[0240] This disclosure is applicable to both MIMO and mobility use cases. Beam reporting for MIMO may be handled by UEIBR, while beam reporting for mobility may be handled by event-triggered beam reporting.
[0241] In this disclosure, the terms "cell switching command," "UL cell switching command [UCI / MAC CE]," "DL cell switching command," and simply "UCI / MAC CE" may be interpreted interchangeably.
[0242] In this disclosure, each embodiment / option may be applied individually or in combination with others.
[0243] This disclosure clarifies the cell switching commands (UCI / MAC CE) for CLTMs and related regulations. Based on these regulations, the UE can appropriately control the CLTM. As a result, lower latency communication can be achieved, and communication quality / throughput can be improved.
[0244] <First Embodiment> The first embodiment corresponds to Analysis 1 and relates to a UL cell switching command [UCI] for CLTM.
[0245] The above-mentioned provisions regarding the UCI for the MIMO UEIBR may be used / applied as the UL cell switching command [UCI] for the CLTM. That is, the above-mentioned UCI for the UEIBR may be interpreted as the cell switching command [UCI] for the CLTM of this disclosure.
[0246] For example, the UCI / second UL channel (PUSCH) of the UEIBR may be interpreted as the UL cell switching command [UCI] in this disclosure.
[0247] Alternatively, the UCI / second UL channel (PUSCH) of the UEIBR may be interpreted as a signal / channel for transmitting / carrying the UL cell switching command [UCI] of this disclosure.
[0248] Furthermore, the DCI in step 2 of the UEIBR in mode A may be interpreted as a DCI that triggers / schedules a UL channel / UL resource for the UL cell switching command [UCI] of this disclosure.
[0249] The CSI reporting settings (CSI-ReportConfig) and resource settings (ResourceConfig) for UEIBR may be interpreted as the Conditional LTM settings (Conditional LTM config) in this disclosure.
[0250] The UEIBR's provisions regarding UCI content / bit size may be interpreted as being in accordance with the content of the second embodiment of this disclosure described later.
[0251] In this disclosure, whether to use UCI or MAC CE as the UL cell switching command for CLTM may be switched / configured / instructed by upper layer signaling / physical layer signaling, or may be determined according to UE capabilities.
[0252] According to this embodiment, the provisions for the UEIBR [and its UCI] for MIMO can be applied to the UL cell switching command for CLTM.
[0253] <Second Embodiment> The second embodiment corresponds to Analysis 1 and relates to a UL cell switching command [UCI] for CLTM.
[0254] <<Aspect 2-1>> Aspect 2-1 relates to the content of the UL cell switching command [UCI].
[0255] Figure 10 shows an example of an existing cell switching command MAC CE. Figure 11 shows an example of the UL cell switching command UCI of this disclosure.
[0256] As a UL cell switching command [UCI] for CLTM (referred to simply as UCI in the second embodiment), at least a portion of the content of an existing (e.g., Rel. 18) LTM cell switching command [MAC CE] may be used (see Figures 10 and 11). Note that the number of bits in the fields shown in Figure 11 is merely an example and is not limited to this, and can be changed as appropriate.
[0257] • Target setting ID. • Timing Advance Command (TAC). • TCI status ID. • UL TCI status ID.
[0258] Furthermore, the UCI does not need to include fields related to C, S / U, random access preamble index, SS / PBCH index, or PRACH mask index.
[0259] Furthermore, under certain conditions, the UCI may not include fields related to TAC and UL TCI status ID.
[0260] For example, whether or not the UCI contains a UL TCI status ID may be determined based on at least one of the following options. That is, the UE may decide / determine whether or not to include the UL TCI status ID in the UCI based on at least one of the following options.
[0261] (Opt1) Whether the UCI contains a UL TCI status ID may be set / indicated / determined by upper layer signaling (RRC / MAC CE) / physical layer signaling (DCI) before the UE transmits the UCI.
[0262] For example, if specific settings / instructions are provided to the UE, the UE may include the UL TCI status ID in the UCI. In other words, if specific settings / instructions are not provided to the UE, the UE does not need to include the UL TCI status ID in the UCI.
[0263] (Example 1) Whether the UCI includes the UL TCI status ID may be determined based on whether RACH-less LTM / early RACH setting / UE-based TA measurement parameters are set for the target cell. If at least one of the above is set, the UE may include the UL TCI status ID in the UCI.
[0264] (Example 2) Whether the UCI includes a UL TCI state ID may be determined based on whether the unified TCI state type (unifiedTCI-StateType) is joint / separate.
[0265] More specifically, if the type of Unified TCI state is Joint, the UE does not need to include the UL TCI state ID in the UCI. On the other hand, if the type of Unified TCI state is Separate, the UE may include the UL TCI state ID in the UCI.
[0266] (Example 3) Whether the UCI contains a UL TCI status ID may be determined based on whether at least one of the PDCCH order (e.g., DCI format 1_0) and MAC CE indicating the TA of the target cell has been received.
[0267] More specifically, if the UE receives at least one of the PDCCH order and the MAC CE, the UE may include the UL TCI status ID in the UCI. On the other hand, if the UE does not receive either the PDCCH order or the MAC CE, the UE does not need to include the UL TCI status ID in the UCI.
[0268] (Opt2) Whether the UCI contains a UL TCI status ID may be determined based on specific conditions / events.
[0269] The specific condition / event may be whether the UE obtained a TA for the target cell before sending the UL cell switching command [UCI].
[0270] For example, if the UE obtains the TA for the target cell before sending the UL cell switching command [UCI], the UE may include the UL TCI status ID in the UCI. On the other hand, if the UE does not obtain the TA for the target cell before sending the UL cell switching command [UCI], the UE does not need to include the UL TCI status ID in the UCI.
[0271] In Opt2, the network needs to know the bit size of the UCI [in advance].
[0272] (Opt3) Whether the UCI includes the UL TCI status ID may be determined according to the UE capability.
[0273] The content of the UL cell switching command in this disclosure is applicable not only to UCI but also to MAC CE.
[0274] <<Aspect 2-2>> Aspect 2-2 relates to the bit size of the UL cell switching command [UCI].
[0275] The bit size of the UL cell switching command [UCI] may be determined based on at least one of the following options:
[0276] (OptA) The bit size of the UCI may be fixed.
[0277] The UE may always report X bits as the bit size of the UCI. If there are unnecessary (additional / surplus) fields based on opt2 of the above-described aspect 2-1, the UE may add fields for zero padding. In the case of the TAC field, a specific value (e.g., FFF) may be included in the UCI, similar to the existing (Rel. 18) cell switching command MAC CE for LTM.
[0278] When Opt1 / Opt3 of Embodiment 1-1 is applied, the value of X (bit size) may be predefined by the specification, set / indicated by upper layer signaling / physical layer signaling, or determined according to UE capabilities.
[0279] (OptB) The bit size of the UCI may be variable.
[0280] OptB may be applied when Opt2 of Embodiment 1-1 is applicable.
[0281] The UE may report Y bits as the bit size of the UCI. The value of Y may be less than or equal to X.
[0282] In order for NW to identify Y, specific information about Y may be reported [from UE] before the transmission or reception of the UL cell switching command [UCI].
[0283] The information regarding Y may be, for example, the actual value of Y, or an indicator showing whether TA has been obtained.
[0284] According to this embodiment, the content and bit size of the UL cell switching command [UCI] for CLTM become clear.
[0285] <Third Embodiment> The third embodiment relates to the cancellation of UL resources and CLTM for UL cell switching commands.
[0286] <<Aspect 3-1>> In CLTM, certain UL channels (e.g., PUCCH, PUSCH, PRACH) may be considered UL resources.
[0287] As mentioned above, CLTM can be used to improve the robustness of LTM, specifically to avoid handover failures. This requires performing cell switching at the appropriate time.
[0288] On the other hand, if the conditions for triggering CLTM at the appropriate cell switching timing are met, DL signaling will be avoided after those conditions are met. Otherwise, it may behave similarly to the existing (Rel. 18) LTM.
[0289] Therefore, we propose limiting the UL resources used for UL cell switching commands.
[0290] The following constraints may be applied to the UL resource of the UL cell switching command, depending on the container type.
[0291] When UCI is used as a container for UL cell switching commands, PUCCH, or a type 1 / type 2 configuration grant PUSCH (CG-PUSCH), may be configured as the UL resource for the UL cell switching command.
[0292] When MAC CE is used as a container for UL cell switching commands, a Type 1 / Type 2 configuration grant PUSCH (CG-PUSCH) may be configured as the UL resource for the UL cell switching command.
[0293] Furthermore, whether other UL resources (e.g., dynamic granPUSCH (DG-PUSCH)) are available may be predefined by the specification, configured / instructed by upper-layer signaling / physical-layer signaling, or determined according to UE capabilities.
[0294] Additionally, a dedicated UL resource may be set up for the UL cell switching command.
[0295] PUCCH, or Type 2 CG-PUSCH, may be activated based on at least one of the following options:
[0296] (Opt1) Activated by an existing MAC CE (e.g., the LTM cell switching command in Rel. 18).
[0297] (Opt2) Activated by MAC CE / DCI other than Opt1. Examples include the PDCCH order (DCI format 1_0) and MAC CE that instructs the TA of the target cell.
[0298] (Opt3) The UE is expected to be activated based on any [specific] conditions, for example, when an LTM or an L1 measurement report (UCI) is sent for an event-triggered beam report (MAC CE).
[0299] Furthermore, the timing at which certain conditions are satisfied may be a predetermined time (e.g., X symbol / slot / milliseconds) after transmission or after receiving an ACK for transmission.
[0300] (Specific Example) Figures 12A to 12C show examples of the timing for sending UL cell switching commands for each case.
[0301] (Case 1) Case 1 illustrates a case in DG-PUSCH where the UE does not have (receives) an UL grant.
[0302] As shown in Figure 12A, in Case 1, if the event is satisfied, the UE transmits an SR at a predetermined timing. This SR may be transmitted, for example, by a PUCCH.
[0303] Subsequently, the UE receives a DCI transmitted from the base station. This DCI may be one that triggers / schedules a UL channel (e.g., PUSCH) for a UL cell switching command.
[0304] Subsequently, the UE sends a UL cell switching command at a predetermined timing [based on the DCI].
[0305] (Case 2) Case 2 illustrates a case in DG-PUSCH where UE has (is receiving) an UL grant.
[0306] As shown in Figure 12B, in Case 2, if the event is satisfied, the UE sends a UL cell switching command at a predetermined timing.
[0307] (Case 3) Case 3 illustrates a case in which a UL cell switching command is sent in PUCCH or CG-PUSCH.
[0308] As shown in Figure 12B, in Case 3, the UE sends a UL cell switching command at a predetermined timing. This predetermined timing may be after the event is satisfied or before the event is satisfied.
[0309] <<Aspect 3-2-1>> In Case 1 of the above-described aspect 3-1 (Figure 12A), the event conditions may be looser than in the other cases (Case 2 / Case 3) in order to avoid failure to receive DCI. In other words, it is assumed that Case 1 is more likely to be triggered than Case 2 / Case 3. Therefore, there may be cases where the handover occurs too early (early handover).
[0310] Therefore, I propose a method for canceling CLTM.
[0311] If the UE detects a handover that is too early, it may cancel the CLTM after sending the SR but before sending the UL cell switching command.
[0312] To detect premature handover, the UE may continue evaluating the cancellation conditions for the target cell's RS index / TCI state ID until a UL cell switching command is sent. If the cancellation conditions are met during that period (the time during which the cancellation conditions are being evaluated), the UE may perform a specific cancellation action.
[0313] Specific cancellation conditions can be exemplified below. These conditions may be applied individually or in combination.
[0314] (Opt1) The same event that is satisfied to trigger CLTM (trigger condition) may be applied as the cancellation condition. Specific examples are listed below.
[0315] ((Opt1-1)) The trigger condition and the cancellation condition may have the same event type and the same associated parameters.
[0316] For example, consider a case where an offset value X and a TTT (time until trigger) length Y are specified / set. In the case of a trigger condition, if a certain parameter (measured value, etc.) becomes X or greater within a period of Y, it can be determined that the event (trigger condition) has been satisfied.
[0317] In the case of a cancellation condition, an event (cancellation condition) may be considered satisfied if a certain parameter (such as a measured value) falls below X within a period of Y.
[0318] ((Opt1-2)) The trigger condition and the cancellation condition may have the same event type, but the associated parameters may be different.
[0319] For example, consider a case where an offset value X and a TTT (time until trigger) length Y are specified / set. In the case of a trigger condition, if a certain parameter (measured value, etc.) becomes greater than or equal to X within a period of Y, it may be considered that the event (trigger condition) has been satisfied.
[0320] In the case of a cancellation condition, an event (cancellation condition) may be considered satisfied if a certain parameter (measured value, etc.) becomes less than M (M > X) within a period N (N < Y).
[0321] (Opt2) A cancellation condition may be an event different from the event that is satisfied to trigger CLTM (trigger condition). Specific examples are listed below.
[0322] ((Opt2-1)) The trigger condition and the cancellation condition may have different event types.
[0323] ((Opt2-2)) A counter for the cancellation condition may be applied.
[0324] A counter (M) may be set for cancellation. When the counter reaches M or greater, the cancellation condition may be considered to have been met.
[0325] The condition for incrementing the counter may be the same as the trigger condition, or it may be a different condition.
[0326] The cancellation conditions described above may be predefined by the specifications, set / instructed by upper-layer signaling / physical layer signaling, or determined according to UE capabilities.
[0327] <<Aspect 3-2-2>> The following are examples of specific cancellation operations. The following operations may be applied individually or in combination.
[0328] (Opt1) The UE may send a cell switching command [MAC CE / UCI]. Specific examples are listed below.
[0329] ((Opt1-1)) The UE may use one bit in the UL cell switching command to notify / report / send a cancellation [instruction].
[0330] ((Opt1-2)) The UE may report specific bits within the UL cell switching command. For example, the specific bits may all contain the value "0".
[0331] (Opt2) The UE may use dedicated UL signaling to notify / report / transmit a cancellation [instruction].
[0332] A single bit such as PUCCH-SR, MAC CE, or PRACH may be used as a dedicated UL signaling.
[0333] (Opt3) The UE does not need to send the cell switching command [MAC CE / UCI]. Specific examples are listed below.
[0334] ((Opt3-1)) The UE does not need to send anything.
[0335] ((Opt3-2)) The UE may send UL signaling other than the UL cell switching command [MAC CE / UCI].
[0336] <<Aspect 3-2-3>> If different candidate cells satisfy events for different RS index / TCI status IDs, at least one of the following options may be applied.
[0337] (OptA) The UE may use UL resources to send UL cell switching commands for different RS index / TCI status IDs for different candidate cells.
[0338] (OptB) By utilizing UL resources, the UE does not need to send UL cell switching commands for different RS indexes / TCI status IDs for different candidate cells.
[0339] This embodiment clarifies the provisions regarding the cancellation of UL resources and CLTMs for UL cell switching commands.
[0340] <Fourth Embodiment> The fourth embodiment relates to the priority of UL cell switching commands.
[0341] For new UL cell switching commands [MAC CE] for CLTM, a priority order should be defined among all MAC CEs.
[0342] For example, the following can be given as an example of the priority order for the new UL cell switching command. Note that the position of the new UL cell switching command is not limited to the example shown below, and may be placed in any position (priority order).
[0343] Logical channels may be prioritized in the following order (the highest priority may be placed first): • MAC CE for CLTM. • MAC CE for C-RNTI, or data from the Uplink Common Control Channel (UL-CCCH). [• MAC CE for CLTM.] • [Extended] MAC CE for Beam Fault Recovery (BFR), or MAC CE for Setting Grant (CG) Verification, or MAC CE for Multiple Entry CG Verification [, or MAC CE for CLTM]. • MAC CE for Sidelink (SL) CG Verification. • MAC CE for Listen Before Talk (LBT) failure. • MAC CE for SL LBT failure according to specific specifications. • MAC CE for Timing Advance Reporting. - MAC CE for Buffer Status Report (BSR) included for padding. - MAC CE for SL-BSR included for padding.
[0344] The prioritization of MAC CEs with the same priority level may depend on the UE implementation.
[0345] As described above, the MAC CE (UL cell switching command) for CLTM in this disclosure may have the highest priority, or it may have a higher / lower / same priority as the MAC CE for BFR.
[0346] According to this embodiment, the UE has a clear priority for the placement of UL cell switching commands.
[0347] <Supplement> <<Notification of Information to UE>> In the embodiments described above, notification of any information from the Network (NW) (e.g., Base Station (BS)) to the UE (in other words, reception of any information from the BS at the UE) may be performed using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.
[0348] If the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new Logical Channel ID (LCID) not defined in existing standards in the MAC subheader.
[0349] If the above 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 the Cyclic Redundancy Check (CRC) bits assigned to the DCI, or the format of the DCI.
[0350] Furthermore, the notification of arbitrary information to the UE in the above-described embodiment may be periodic, semi-persistent, or aperiodic.
[0351] <<Notification of Information from UE>> Notification of any information from the UE to the NW in the embodiments described above (in other words, transmission / reporting 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), specific signals / channels (e.g., PUCCH, PUSCH, PRACH, reference signals), or a combination thereof.
[0352] If the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new LCID not specified in existing standards in the MAC subheader.
[0353] If the above notice is made by the UCI, the notice may be transmitted using PUCCH or PUSCH.
[0354] Furthermore, the notification of any information from the UE in the above-described embodiment may be periodic, semi-persistent, or aperiodic.
[0355] <<Regarding the Application of Each Embodiment>> In UE / BS, specific (one or more) processes / operations / controls / assumptions / information for at least one of the embodiments described above may be applied (or used) if any or more of the following conditions are met: - A higher-layer parameter indicating the specific process / operation / control / assumption / information is set. - The specific process / operation / control / assumption / information is determined based on the relevant higher-layer parameter. - The specific process / operation / control / assumption / information is designated / activated / triggered by MAC CE / DCI / UCI / Resource / Channel / RS. - A specific UE capability indicating (or related to) the specific process / operation / control / assumption / information is reported or supported. - The application of the specific process / operation / control / assumption / information is determined based on specific conditions.
[0356] The specific UE capabilities described above may include at least one of the following: • Supporting specific processing / operations / controls / information for at least one of the embodiments described above; • Supporting the CSI reporting framework for LTMs in Rel. 18; • Supporting MIMO / mobility (e.g., CLTMs) in Rel. 19 and later; • Supporting MAC CE-based event-triggered beam reporting (UEIBR); • Supporting event-triggered beam reporting for CLTMs using UCI / MAC CE; • Supporting CLTM cancellation.
[0357] Furthermore, the above-mentioned specific UE capability may be a capability that applies across all frequencies (commonly regardless of frequency), a capability per frequency (e.g., one or a combination thereof, such as cell, band, band combination, BWP, component carrier, etc.), a capability per frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), a capability per subcarrier spacing (SCS), or a capability per feature set (FS) or feature set per component-carrier (FSPC).
[0358] Furthermore, the specific UE capabilities described above may be capabilities that apply across all duplexing schemes (common to all duplexing schemes regardless of the duplexing scheme), or they may be capabilities specific to each duplexing scheme (e.g., Time Division Duplex (TDD), Frequency Division Duplex (FDD)).
[0359] If the above conditions are not met, UE / BS may follow the behavior specified in existing 3GPP releases.
[0360] (Note) The following inventions are added with respect to one embodiment of the present disclosure. [Note 1] A terminal having: a receiving unit that receives settings for UL resources for an uplink (UL) cell switching command that triggers conditional L1 / L2 triggered mobility (CLTM); and a control unit that controls the transmission of the UL cell switching command based on the UL resources, wherein the UL cell switching command is transmitted using uplink control information (UCI) or MAC control elements (MAC CE) as a container. [Note 2] The terminal according to Note 1, wherein the control unit evaluates a cancellation condition for a target cell's reference signal (RS) index or transmit setting instruction (TCI) state ID before transmitting the UL cell switching command, and performs a specific cancellation operation if a specific cancellation condition is satisfied. [Note 3] The terminal according to Note 1 or Note 2, wherein the MAC CE of the UL cell switching command is arranged according to a specific priority order. [Note 4] The UCI of the UL cell switching command includes at least one of the following terminals: target setting ID, timing advance command (TAC), transmission setting instruction (TCI) status ID, and UL TCI status ID, as described in any of Notes 1 to 3.
[0361] (Wireless Communication System) The configuration of a wireless communication system according to one embodiment of this disclosure will be described below. In this wireless communication system, communication is performed using any of the wireless communication methods according to the above embodiments of this disclosure, or a combination thereof.
[0362] Figure 13 shows an example of a schematic configuration of a wireless communication system according to one embodiment. The wireless communication system 1 (which may also be simply called system 1) may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc., as specified by the Third Generation Partnership Project (3GPP).
[0363] Furthermore, the wireless communication system 1 may 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)), and the like.
[0364] In EN-DC, the LTE (E-UTRA) base station (eNB) is the Master Node (MN), and the NR base station (gNB) is the 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.
[0365] The wireless communication system 1 may support dual connectivity between multiple base stations within the same RAT (for example, dual connectivity where both MN and SN are NR base stations (gNB) (NR-NR Dual Connectivity (NN-DC))).
[0366] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with relatively wide coverage, and base stations 12 (12a-12c) located within the macrocell C1 that form a small cell C2 that is narrower than the macrocell C1. User terminals 20 may be located within at least one cell. The arrangement, number, shape, size, etc., of each cell and user terminal 20 are not limited to the configuration shown in the figure. Hereinafter, when base stations 11 and 12 are not distinguished, they will be collectively referred to as base station 10.
[0367] 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 by multiple antennas / base stations 10. One [virtual] cell (which may be called a supercell, for example) may be composed of multiple [virtual] cells (which may be called subcells, for example). A supercell may correspond to a cell with a fixed physical range, and a subcell may correspond to a cell whose physical range fluctuates quasi-statically / dynamically. In this case, the wireless communication system 1 may be called a cell-free system.
[0368] 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 (CC) and Dual Connectivity (DC).
[0369] Each CC may be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). A macrocell C1 may be included in FR1, and a 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 above 24 GHz. Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may be in a frequency band higher than FR2.
[0370] Furthermore, the user terminal 20 may communicate in each CC using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD).
[0371] Multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with Common Public Radio Interface (CPRI), X2 / Xn interface, etc.) or wireless (e.g., NR communication). For example, when NR communication is used as a backhaul between base stations 11 and 12, base station 11, which is the upstream station, may be called an Integrated Access Backhaul (IAB) donor, and base station 12, which is the relay station, may be called an IAB node.
[0372] Base station 10 may be connected to the core network 30 via other base stations 10 or directly. The core network 30 may include at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), etc.
[0373] The core network 30 may include network functions (NF) such as User Plane Function (UPF), Access and Mobility Management Function (AMF), Session Management Function (SMF), Unified Data Management (UDM), Application Function (AF), Data Network (DN), Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). Multiple functions may be provided by a single network node. Furthermore, communication with an external network (e.g., the Internet) may occur via the DN.
[0374] The user terminal 20 may be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.
[0375] In the wireless communication system 1, an orthogonal frequency division multiplexing (OFDM)-based wireless access scheme may be used. 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-OFDM), etc., may be used in at least one of the downlink (DL) and uplink (UL).
[0376] The wireless access method may also be called a waveform. In wireless communication system 1, other wireless access methods (for example, other single-carrier transmission methods, other multi-carrier transmission methods) may be used for the UL and DL wireless access methods.
[0377] In the wireless communication system 1, a Physical Downlink Shared Channel (PDSCH), a Broadcast Channel (PBCH), or a Physical Downlink Control Channel (PDCCH) may be used as the downlink channel, which is shared by each user terminal 20.
[0378] Furthermore, in the wireless communication system 1, the uplink channel may include a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), a Physical Random Access Channel (PRACH), or the like, all of which are shared by each user terminal 20.
[0379] User data, higher-layer control information, and System Information Blocks (SIBs) are transmitted via PDSCH. User data and higher-layer control information may also be transmitted via PUSCH. Furthermore, Master Information Blocks (MIBs) may be transmitted via PBCH.
[0380] Lower-layer control information may be transmitted by PDCCH. The lower-layer control information may include, for example, Downlink Control Information (DCI) which includes scheduling information for at least one of PDSCH and PUSCH.
[0381] Furthermore, the DCI that schedules PDSCH may be called DL assignment, DL DCI, etc., and the DCI that schedules PUSCH may be called UL grant, UL DCI, etc. Furthermore, PDSCH may be read as DL data, and PUSCH may be read as UL data.
[0382] PDCCH detection may utilize a Control Resource Set (CORESET) and a search space. A CORESET corresponds to the resources used to search for DCIs. A search space corresponds to the search area and search method for PDCCH candidates. A single CORESET may be associated with one or more search spaces. A UE may monitor CORESETs associated with a given search space based on the search space configuration.
[0383] A single search space may correspond to one or more PDCCH candidates corresponding to aggregation levels. One or more search spaces may be referred to as a search space set. In this disclosure, "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," and "CORESET configuration" may be interpreted interchangeably.
[0384] PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), delivery acknowledgment information (for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). PRACH may transmit a random access preamble for establishing a connection with the cell.
[0385] In this disclosure, downlinks, uplinks, etc., may be expressed without the prefix "link." Also, the prefix "physical" may be omitted from the names of various channels.
[0386] 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, the DL-RS may include 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.
[0387] 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 SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS / PBCH block, SS Block (SSB), etc. Note that SS, SSB, etc. may also be called reference signals.
[0388] Furthermore, in the wireless communication system 1, the uplink reference signal (UL-RS) may include a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. The DMRS may also be called a user-specific reference signal (UE-specific Reference Signal).
[0389] (Base Station) Figure 14 shows an example of the configuration of a base station according to one embodiment. The base station 10 includes a control unit 110, a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission line interface 140. Note that one or more of the control unit 110, the transmitting / receiving unit 120, the transmitting / receiving antenna 130, and the transmission line interface 140 may be provided.
[0390] In this example, the functional blocks of the characteristic parts of this 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 part described below may be omitted.
[0391] The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, control circuit, etc., as described based on common understanding in the technical field related to this disclosure.
[0392] The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may also control transmission and reception, measurement, etc., using the transmitting / receiving unit 120, transmitting / receiving antenna 130, and transmission path interface 140. The control unit 110 may generate data to be transmitted as signals, control information, sequences, etc., and transfer them to the transmitting / receiving unit 120. The control unit 110 may also perform call processing of communication channels (setting, releasing, etc.), status management of the base station 10, management of wireless resources, etc.
[0393] The transmitting / receiving 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 transmitting / receiving unit 120 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.
[0394] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 1211 and an RF unit 122. The receiving unit may consist of a receiving processing unit 1212, an RF unit 122 and a measuring unit 123.
[0395] The transmitting and receiving antenna 130 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.
[0396] The transmitting / receiving unit 120 may transmit the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 120 may also receive the uplink channel, uplink reference signal, etc.
[0397] The transmitting / receiving unit 120 may use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like to form at least one of the transmitting beam and the receiving beam.
[0398] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform processing on data and control information acquired from the control unit 110, for example, at the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer (e.g., RLC retransmission control), and the Medium Access Control (MAC) layer (e.g., HARQ retransmission control), to generate a bit sequence to be transmitted.
[0399] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform transmission processing on the bit sequence to be transmitted, 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, and output a baseband signal.
[0400] The transmitting / receiving unit 120 (RF unit 122) may perform modulation, filtering, amplification, etc., of the baseband signal to the radio frequency band and transmit the signal in the radio frequency band via the transmitting / receiving antenna 130.
[0401] On the other hand, the transmitting / receiving unit 120 (RF unit 122) may perform amplification, filtering, demodulation to a baseband signal, etc., on the radio frequency band signal received by the transmitting / receiving antenna 130.
[0402] The transmitting / receiving unit 120 (receiving 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 (may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to acquire user data, etc.
[0403] The transmitting / receiving unit 120 (measurement unit 123) may perform measurements related to 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 also measure received power (e.g., Reference Signal Received Power (RSRP)), reception 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.
[0404] The transmission path interface 140 may send and receive signals (backhaul signaling) with 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.
[0405] In this disclosure, the transmitting and receiving units of the base station 10 may consist of at least one of a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission path interface 140.
[0406] 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 physical layer functions (precoding, IFFT, FFT, etc.). The DU may implement higher-level physical layer functions (coding to resource element mapping, etc.), MAC layer functions, and RLC layer functions. The CU may implement PDCP layer, Service Data Adaptation Protocol (SDAP) layer, and RRC layer functions.
[0407] In this disclosure, base station 10 may include a single device that implements all the functions of RU, DU, and CU, or it may include multiple devices that each implement some of the functions of RU, DU, and CU and are connected to each other. In this disclosure, base station 10 may be interpreted as RU / DU / CU.
[0408] The transmitting / receiving unit 120 may transmit settings for UL resources for an uplink (UL) cell switching command that triggers conditional L1 / L2 triggered mobility (CLTM). The control unit 110 may control the reception of the UL cell switching command transmitted from the terminal based on the UL resource. The UL cell switching command may be transmitted using uplink control information (UCI) or MAC control elements (MAC CE) as a container.
[0409] (User Terminal) Figure 15 shows an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Note that one or more of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may be provided.
[0410] In this example, the functional blocks of the characteristic parts of this 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 part described below may be omitted.
[0411] The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., as described based on common understanding in the technical field related to this disclosure.
[0412] The control unit 210 may control signal generation, mapping, etc. The control unit 210 may also control transmission and reception, measurement, etc., using the transmitting / receiving unit 220 and the transmitting / receiving antenna 230. The control unit 210 may generate data to be transmitted as signals, control information, sequences, etc., and transfer them to the transmitting / receiving unit 220.
[0413] The transmitting / receiving 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 transmitting / receiving unit 220 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.
[0414] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 2211 and an RF unit 222. The receiving unit may consist of a receiving processing unit 2212, an RF unit 222 and a measuring unit 223.
[0415] The transmitting and receiving antenna 230 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.
[0416] The transmitting / receiving unit 220 may receive the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 220 may also transmit the uplink channel, uplink reference signal, etc.
[0417] The transmitting / receiving unit 220 may use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like to form at least one of the transmitting beam and the receiving beam.
[0418] The transmitting / receiving 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 and control information acquired from the control unit 210 to generate a bit sequence to be transmitted.
[0419] The transmitting / receiving unit 220 (transmission processing unit 2211) may perform transmission processing on the bit sequence to be transmitted, 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, and output a baseband signal.
[0420] Whether or not to apply DFT processing may be based on the transform precoding settings. The transmitting / receiving unit 220 (transmission processing unit 2211) may perform DFT processing as part of the transmission process to transmit a channel (for example, PUSCH) using a DFT-s-OFDM waveform if transform precoding is enabled for that channel, or it may not perform DFT processing as part of the transmission process if transform precoding is not enabled for that channel.
[0421] The transmitting / receiving unit 220 (RF unit 222) may perform modulation, filtering, amplification, etc., of the baseband signal to the radio frequency band and transmit the signal in the radio frequency band via the transmitting / receiving antenna 230.
[0422] On the other hand, the transmitting / receiving unit 220 (RF unit 222) may perform amplification, filtering, demodulation to a baseband signal, etc., on the radio frequency band signal received by the transmitting / receiving antenna 230.
[0423] The transmitting / receiving unit 220 (receiving processing unit 2212) may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to acquire user data, etc.
[0424] The transmitting / receiving unit 220 (measuring unit 223) may perform measurements related to the received signal. For example, the measuring unit 223 may perform RRM measurement, CSI measurement, etc., based on the received signal. The measuring unit 223 may also 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.
[0425] The measurement unit 223 may derive channel measurements for CSI calculation based on channel measurement resources. Channel measurement resources may be, for example, Non Zero Power (NZP) CSI-RS resources. The measurement unit 223 may also derive interference measurements for CSI calculation based on interference measurement resources. Interference measurement resources may be at least one of the following: NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, etc. CSI-IM may also be called CSI-Interference Management (IM), and may be interpreted interchangeably with Zero Power (ZP) CSI-RS. In this disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc., may be interpreted interchangeably.
[0426] In this disclosure, the transmitting unit and receiving unit of the user terminal 20 may be composed of at least one of a transmitting / receiving unit 220 and a transmitting / receiving antenna 230.
[0427] The control unit 210 may perform at least a part of the processing of the control unit as described above.
[0428] The transmitting / receiving unit 220 may perform at least a part of the processing of the transmitting / receiving unit as described above.
[0429] The MAC CE of the UL cell switching command may be arranged according to a specific priority. The UCI of the UL cell switching command may include at least one of the target setting ID, timing advance command (TAC), transmit setting instruction (TCI) status ID, and UL TCI status ID.
[0430] (Hardware Configuration) The block diagram used in the description of the above embodiment shows functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software.
[0431] Here, functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission may be called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.
[0432] For example, a base station, user terminal, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 16 is a diagram showing an example of the hardware configuration of a base station and user terminal according to one embodiment. The base station 10 and user terminal 20 described above may be physically configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc.
[0433] In this disclosure, terms such as apparatus, circuit, device, section, and unit are interchangeable. The hardware configuration of the base station 10 and the user terminal 20 may include one or more of the devices shown in the figure, or it may be configured without some of the devices.
[0434] For example, although only one processor 1001 is shown in the diagram, there may be multiple processors. Furthermore, the processing may be performed by one processor, or it may be performed by two or more processors simultaneously, sequentially, or by other means. Note that the processor 1001 may be implemented using one or more chips.
[0435] Each function in the base station 10 and the user terminal 20 is realized, for example, by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations and control communication via the communication device 1004, or control at least one of reading and writing data in the memory 1002 and storage 1003.
[0436] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, at least a part of the control unit 110 (210) and the transmitting / receiving unit 120 (220) described above may be implemented by the processor 1001.
[0437] Furthermore, the processor 1001 reads programs (program code), 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 accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. 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 other functional blocks may be implemented similarly.
[0438] The memory 1002 is a computer-readable recording medium and may consist of at least one of the following: Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. The memory 1002 may also be called a register, cache, or main memory. The memory 1002 can store executable programs (program code), software modules, etc., for carrying out a wireless communication method according to one embodiment of the present disclosure.
[0439] The storage 1003 is a computer-readable recording medium and may consist of at least one of the following: a flexible disk, a floppy disk, a magneto-optical disk (e.g., a Compact Disk (Compact Disc ROM (CD-ROM)), a Digital Use Disk, a Blu-ray (registered trademark) disk), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, stick, key drive), a magnetic stripe, a database, a server, or other suitable storage medium. The storage 1003 may also be called an auxiliary storage device.
[0440] The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include, for example, a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmitting / receiving unit 120 (220), transmitting / receiving antenna 130 (230), etc., may be implemented by the communication device 1004. The transmitting / receiving unit 120 (220) may be implemented with physically or logically separated transmitting unit 120a (220a) and receiving unit 120b (220b).
[0441] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, light-emitting diode (LED) lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).
[0442] 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 different buses may be configured for each device.
[0443] 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), and a field programmable gate array (FPGA), and some or all of each functional block may be implemented using such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.
[0444] Furthermore, devices included in the core network 30 (for example, network nodes that provide NF) may also be implemented using the functional block / hardware configuration described above.
[0445] (Variations) Terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol and signal (signal or signaling) may be used interchangeably. Also, a signal may be a message. A reference signal may be abbreviated as RS and may be called a pilot, pilot signal, etc., depending on the applicable standard. Also, a component carrier (CC) may be called a cell, frequency carrier, carrier frequency, etc.
[0446] 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 the radio frame may be called a sub-frame. Further, a sub-frame may be composed of one or more slots in the time domain. The sub-frame may have a fixed time length (e.g., 1 ms) independent of numerology.
[0447] Here, numerology may be a communication parameter applied to at least one of transmission and reception of a certain signal or channel. Numerology may indicate, for example, at least one of sub-carrier spacing (SubCarrier Spacing (SCS)), bandwidth, symbol length, cyclic prefix length, transmission time interval (Transmission Time Interval (TTI)), number of symbols per TTI, radio frame configuration, specific filtering processing performed by a transceiver in the frequency domain, specific windowing processing performed by a transceiver in the time domain, etc.
[0448] A slot may be composed of one or more symbols (such as Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.) in the time domain. Also, a slot may be a time unit based on numerology.
[0449] A slot may include a plurality of mini-slots. Each mini-slot may be composed of one or more symbols in the time domain. Also, a mini-slot may be called a sub-slot. A mini-slot may be composed of a smaller number of symbols than a slot. The PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may be called PDSCH (PUSCH) mapping type A. The PDSCH (or PUSCH) transmitted using a mini-slot may be called PDSCH (PUSCH) mapping type B.
[0450] A radio frame, sub-frame, slot, mini-slot, and symbol all represent time units for transmitting signals. Different names may be used for the radio frame, sub-frame, slot, mini-slot, and symbol respectively. Note that the time units such as frames, sub-frames, slots, mini-slots, and symbols in this disclosure may be read as each other.
[0451] For example, one sub-frame may be called a TTI, or a plurality of consecutive sub-frames may be called a TTI, or one slot or one mini-slot may be called a TTI. That is, at least one of the sub-frame and the TTI may be the sub-frame (1 ms) in the existing LTE, or 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, a mini-slot, etc. instead of a sub-frame.
[0452] Here, the TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in an LTE system, the base station performs scheduling to allocate radio resources (frequency bandwidth, transmission power, etc. that can be used in each user terminal) to each user terminal in units of TTI. Note that the definition of the TTI is not limited to this.
[0453] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), code block, codeword, etc., or may be a processing unit for scheduling, link adaptation, etc. Note that when the TTI is given, the time interval (for example, the number of symbols) in which the transport block, code block, codeword, etc. are actually mapped may be shorter than the TTI.
[0454] Furthermore, if one slot or one mini-slot is referred to as a TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit for scheduling. In addition, the number of slots (number of mini-slots) that constitute this minimum time unit for scheduling may be controlled.
[0455] A TTI with a time length of 1 ms may be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc.
[0456] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.
[0457] A Resource Block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology.
[0458] Furthermore, an RB may contain one or more symbols in the time domain and may have the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.
[0459] One or more RBs may also be called Physical RBs (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.
[0460] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.
[0461] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a given neurology in a given carrier. These common RBs may be identified by an index of the RBs relative to a common reference point of the carrier. The PRBs may be defined and numbered within a given BWP.
[0462] A BWP may include UL BWP (BWP for UL) and DL BWP (BWP for DL). One or more BWPs may be configured within a single carrier for a UE.
[0463] At least one of the configured BWPs may be active, and the UE does not need to assume that it will transmit or receive a predetermined signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".
[0464] The structures of wireless frames, subframes, slots, minislots, and symbols described above are merely examples. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless 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, and the number of symbols, symbol length, and cyclic prefix (CP) length within the TTI can be varied in various ways.
[0465] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values from a predetermined value, or corresponding other information. For example, wireless resources may be indicated by a predetermined index.
[0466] The names used for parameters and other elements in this disclosure are not restrictive in any way. Furthermore, mathematical formulas and other elements using these parameters may differ from those expressly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.
[0467] The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.
[0468] Furthermore, information, signals, etc., can be output from upper layers to lower layers and from lower layers to upper layers, or to at least one of the two. Information, signals, etc., may also be input and output via multiple network nodes.
[0469] Input and output information and signals may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information and signals may be overwritten, updated, or appended to. Output information and signals may be deleted. Input information and signals may be transmitted to other devices.
[0470] Any information described in this disclosure (e.g., variables, constants, parameters) may be communicated from any first device (e.g., UE / base station) to any second device (e.g., base station / UE) that indicates / specifies (or relates to) the value of such any information, even if not specifically stated in the embodiments described above.
[0471] Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification in this disclosure may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof.
[0472] Physical layer signaling may also be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. RRC signaling may also be called RRC messages, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc. MAC signaling may also be communicated using, for example, MAC Control Elements (CEs).
[0473] Furthermore, notification of the specified information (for example, notification that "X is the case") is not limited to explicit notification, but may also be made implicitly (for example, by not notifying the specified information or by notifying other information).
[0474] The determination may be made by a value represented by one bit (0 or 1), by a boolean value represented as true or false, or by a numerical comparison (for example, a comparison with a predetermined value).
[0475] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.
[0476] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or Digital Subscriber Line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.
[0477] The terms “system” and “network” as used in this disclosure may be used interchangeably. “Network” may also mean the equipment included in the network (e.g., base stations).
[0478] 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,” and “receiving entity” may be used interchangeably.
[0479] Note that in the present disclosure, an antenna port may be mutually read as an antenna port for any signal / channel (e.g., a Demodulation Reference Signal (DMRS) port). In the present disclosure, a resource may be mutually read as a resource for any signal / channel (e.g., a reference signal resource, an SRS resource, etc.). Note that the resource may include time / frequency / code / space / power resources. Also, the spatial domain transmission filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.
[0480] The above group may include at least one of, for example, a spatial relation 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, etc.
[0481] Also, in the present disclosure, a beam, an SRS Resource Indicator (SRI), a CORESET, a CORESET pool, a PDSCH, a PUSCH, a Codeword (CW), a Transport Block (TB), an RS, etc. may be mutually read.
[0482] Also, in the present disclosure, a TCI state, a downlink TCI state (DL TCI state), an uplink TCI state (UL TCI state), a unified TCI state, a common TCI state, a joint TCI state, etc. may be mutually read.
[0483] Furthermore, in this disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) properties," and "specific QCL type (e.g., Type A, Type D)" may be interpreted interchangeably.
[0484] In this disclosure, terms such as index, identifier (ID), indicator, indication, and resource ID may be interpreted interchangeably. In this disclosure, terms such as sequence, list, set, group, cluster, subset may be interpreted interchangeably.
[0485] Furthermore, the spatial relationship information Identifier (ID) (TCI state ID) and spatial relationship information (TCI state) may be interpreted as mutually exclusive. "Spatial relationship information (TCI state)" may be interpreted as mutually exclusive as "a set of spatial relationship information (TCI state)," "one or more pieces of spatial relationship information," etc. TCI state and TCI may be interpreted as mutually exclusive. Spatial relationship information and spatial relationship may be interpreted as mutually exclusive.
[0486] In this disclosure, terms such as “Base Station (BS),” “wireless 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,” and “component carrier” may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.
[0487] A base station may house one or more (e.g., three) cells. If a base station houses multiple cells, the entire coverage area of the base station may be divided into several smaller areas, each of which may also be provided with communication services 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 at least one of the base station and / or base station subsystems that provide communication services in that coverage.
[0488] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform a control / operation based on said information.
[0489] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.
[0490] A mobile station may also be called 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 appropriate term.
[0491] 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. At least one of the base station and the mobile station may also be a device mounted on a moving object, the moving object itself, etc.
[0492] The term "mobile object" refers to any movable object, regardless of its speed, and naturally includes cases where the mobile object is stationary. Examples of such mobile objects include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and items carried on them. Furthermore, such mobile objects may be autonomously driven objects operating based on operational commands.
[0493] The mobile entity may be a vehicle (e.g., a car, an airplane), an unmanned mobile entity (e.g., a drone, an autonomous vehicle), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does 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.
[0494] Figure 17 shows an example of a vehicle according to one 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, an axle 48, an electronic control unit 49, various sensors (including a current sensor 50, a rotation speed sensor 51, a pneumatic 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.
[0495] The drive unit 41 consists of, for example, at least one of an engine, a motor, or an engine-motor hybrid. 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 the user.
[0496] The electronic control unit 49 consists of a microprocessor 61, memory (ROM, RAM) 62, and communication ports (e.g., input / output (IO) ports) 63. Signals from various sensors 50-58 installed in the vehicle are input to the electronic control unit 49. The electronic control unit 49 may also be called an Electronic Control Unit (ECU).
[0497] Signals from various sensors 50-58 include current signals from current sensor 50 for sensing motor current, rotational speed signals of front wheels 46 / rear wheels 47 acquired by rotational speed sensor 51, air pressure signals of front wheels 46 / rear wheels 47 acquired by air pressure sensor 52, vehicle speed signals acquired by vehicle speed sensor 53, acceleration signals acquired by acceleration sensor 54, accelerator pedal depression amount signals acquired by accelerator pedal sensor 55, brake pedal depression amount signals acquired by brake pedal sensor 56, operation signals of shift lever 45 acquired by shift lever sensor 57, and detection signals acquired by object detection sensor 58 for detecting obstacles, vehicles, pedestrians, etc.
[0498] The information service unit 59 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, display, television, and radio, and one or more ECUs that control these devices. The information service unit 59 uses information acquired from external devices via a communication module 60 or the like to provide various types of information / services (for example, multimedia information / multimedia services) to the occupants of the vehicle 40.
[0499] The information service unit 59 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) or output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.).
[0500] The driver assistance system unit 64 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, 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 Unit (IMU), Inertial Navigation System (INS)), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driver assistance functions or autonomous driving functions.
[0501] 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 sends and receives data (information) via the communication port 63 to 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, axle 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and various sensors 50-58 provided in the vehicle 40.
[0502] 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 external devices. For example, it can send and receive various types of information to and from external devices 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. Alternatively, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 (it may function as at least one of the base station 10 and the user terminal 20).
[0503] The communication module 60 may transmit at least one of the following to an external device via wireless communication: signals from the various sensors 50-58 input to the electronic control unit 49, information obtained based on said signals, and information based on input from an external source (user) obtained via the information service unit 59. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc., may also be called input units that accept input. For example, the PUSCH transmitted by the communication module 60 may include the information based on the above input.
[0504] The communication module 60 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 59 installed in the vehicle. The information service unit 59 may also be called an output unit, which outputs information (for example, it outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 60).
[0505] 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, axle 48, various sensors 50-58, etc., which are provided in the vehicle 40.
[0506] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this 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), Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may have the functions of the base station 10 described above. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "sidelink"). For example, uplink channel, downlink channel, etc., may be interpreted as sidelink channel.
[0507] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station 10 may be configured to have the same functions as the user terminal 20 described above.
[0508] In this disclosure, operations performed by a base station may, in some cases, be performed by its upper node. In a network including one or more network nodes having base stations, it is clear that various operations performed for communication with terminals may be performed by the base station, one or more network nodes other than the base station (for example, a Mobility Management Entity (MME), a Serving Gateway (S-GW), etc., but not limited to these), or a combination thereof.
[0509] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between as needed during execution. Furthermore, the processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be rearranged in order, provided they are consistent. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented.
[0510] Each aspect / embodiment described in this disclosure is 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 (where x is, for example, an integer or decimal)), 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®), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, systems utilizing Ultra-WideBand (UWB), Bluetooth®, or other appropriate wireless communication methods, and next-generation systems extended, modified, created, or defined based thereon may also be applied. Furthermore, multiple systems may be applied in combination (for example, a combination of LTE or LTE-A and 5G).
[0511] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."
[0512] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, the references to the first and second elements do not imply that only two elements may be employed or that the first element must precede the second element in any way.
[0513] The term “determining” as used in this disclosure may encompass a wide variety of actions. For example, “determining” may be considered to mean judging, calculating, computing, processing, deriving, investigating, looking up, searching, or inquiring (e.g., searching in tables, databases, or other data structures), ascertaining, etc.
[0514] Furthermore, "judgment (decision)" may be considered as "judging (deciding)" things like receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory).
[0515] Furthermore, “judgment (decision)” may be considered as “judgment (decision)” of resolving, selecting, choosing, establishing, comparing, etc. In other words, “judgment (decision)” may be considered as “judgment (decision)” of some action. In this disclosure, “judgment (decision)” may be interpreted as mutually interchangeable with the actions described above.
[0516] Furthermore, in this disclosure, “determine / determining” may be interpreted as “assume / assuming,” “expect / expecting,” or “consider / considering.” In addition, in this disclosure, “not expecting to do…” may be interpreted as “expecting not to do….”
[0517] In this disclosure, "expect" may be rephrased as "be expected." For example, "expect(s) ..." (where "..." may be expressed as a that clause, an infinitive, etc.) may be rephrased as "be expected ..." or "do (the verb without "to" if "..." is an infinitive)." Similarly, "does not expect ..." may be rephrased as "be not expected ..." or "do not (the verb without "to" if "..." is an infinitive)." Furthermore, "An apparatus A is not expected ..." may be rephrased 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).
[0518] The term "maximum transmit power" as used in this disclosure may mean the maximum transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.
[0519] As used in this disclosure, the terms “connected,” “coupled,” and any variations thereof mean any direct or indirect connection or coupling between two or more elements, and may include one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be replaced with “access.”
[0520] In this disclosure, when two elements are connected, they can be considered to be "connected" or "coupled" to each other using one or more wires, cables, printed electrical connections, etc., and, in some non-exclusive and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.
[0521] In this 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 "combine" may be interpreted similarly to "different."
[0522] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.
[0523] In this disclosure, if articles are added by translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.
[0524] In this disclosure, "less than or equal to," "less than," "greater than or equal to," "more than," and "equal to" may be interpreted interchangeably. In addition, in this disclosure, words meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees. In addition, in this disclosure, words meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees, by adding "i-th" (where i is any integer) to the expression (for example, "highest" may be interpreted interchangeably with "i-th highest").
[0525] In this disclosure, "of," "for," "regarding," "related to," and "associated with" may be interpreted as being interchangeable.
[0526] In this disclosure, phrases 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. Furthermore, A, B, etc., may be replaced with appropriate expressions such as nouns, gerunds, or regular sentences depending on the context. The time difference between A and B may be approximately zero (immediately after or immediately before). Additionally, a time offset may be applied to the time when A occurs. For example, "A" may be interpreted as "before / after the time offset when A occurs". The time offset (e.g., one or more symbols / slots) may be predetermined or determined by the UE based on notified information.
[0527] In this disclosure, timing, time, duration, time instance, any unit of time (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc., may be interpreted interchangeably.
[0528] Although the invention described herein has been explained in detail above, it will be clear to those skilled in the art that the invention described herein is not limited to the embodiments described herein. The descriptions herein are illustrative and not intended to be restrictive in any way to the invention described herein.
[0529] This application is based on Japanese Patent Application No. 2024-179609, filed on October 15, 2024. All of its contents are included herein.
Claims
1. A terminal having a receiving unit that receives settings for UL resources for an uplink (UL) cell switching command that triggers conditional L1 / L2 triggered mobility (CLTM), and a control unit that controls the transmission of the UL cell switching command based on the UL resources, wherein the UL cell switching command is transmitted using uplink control information (UCI) or MAC control elements (MAC CE) as a container.
2. The terminal according to claim 1, wherein the control unit evaluates a cancellation condition for the reference signal (RS) index or transmit setting instruction (TCI) status ID of the target cell before transmitting a UL cell switching command, and performs a specific cancellation operation if a specific cancellation condition is satisfied.
3. The MAC CE of the UL cell switching command is arranged according to claim 1, in a terminal according to a specific priority order.
4. The terminal according to claim 1, wherein the UCI of the UL cell switching command includes at least one of a target setting ID, a timing advance command (TAC), a transmission setting instruction (TCI) status ID, and a UL TCI status ID.
5. A wireless communication method for a terminal, comprising the steps of: receiving a setting for an uplink (UL) cell switching command that triggers conditional L1 / L2 triggered mobility (CLTM); and controlling the transmission of the UL cell switching command based on the UL resource, wherein the UL cell switching command is transmitted using uplink control information (UCI) or MAC control elements (MAC CE) as a container.
6. A base station having: a transmitting unit that transmits settings for UL resources for an uplink (UL) cell switching command that triggers conditional L1 / L2 triggered mobility (CLTM); and a control unit that controls the reception of the UL cell switching command transmitted from a terminal based on the UL resource, wherein the UL cell switching command is transmitted using uplink control information (UCI) or MAC control elements (MAC CE) as a container.
Citation Information
Patent Citations
Methods for managing measurement configurations with l1 / l2 based mobility
WO2024015300A1
Method and apparatus for layer 1 / layer 2 triggered and layer 3 triggered mobility coexistence
WO2024097292A1