User equipment, wireless communication method, and base station

Abstract

A user equipment according to one aspect disclosed herein comprises: a transmission / reception unit that receives a handover trigger instruction based on location information about the user equipment or transmits a notification that the handover has been triggered; and a control unit that controls the operation of the handover on the basis of the trigger instruction or the notification. According to one aspect disclosed herein, it is possible to perform power control suitable for a network and perform more flexible communication.

Description

Terminal, wireless communication method and base station

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

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

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

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

[0005] In future wireless communication systems (e.g., Rel. 20 and later), cell-free communication is being considered, in which terminals (user terminals, User Equipment (UE)) communicate using units smaller than existing cells.

[0006] However, specific consideration of cell-free communication has not been sufficient. If this consideration is insufficient, it may not be possible to control the network (NW) according to communication traffic, etc., and improvement of communication throughput may be inhibited.

[0007] Therefore, one of the objects of the present disclosure is to provide a terminal, a wireless communication method, and a base station that are capable of performing suitable power control in a network and performing more flexible communication.

[0008] A terminal according to one aspect of the present disclosure has a transceiver unit that receives a handover trigger instruction based on the terminal's location information or sends a notification that the handover has been triggered, and a control unit that controls the operation of the handover based on the trigger instruction or the notification.

[0009] According to one aspect of the present disclosure, it is possible to perform suitable power control of a network, thereby enabling more flexible communication.

[0010] FIGS. 1A and 1B are diagrams illustrating an overview of MIMO. FIG. 2A is a diagram illustrating an overview of a cellular system. FIG. 2B is a diagram illustrating an overview of a cell-free system. FIGS. 3A to 3C are diagrams illustrating examples of overviews of various assumed cell-free configurations. FIG. 4 is a diagram illustrating an example of a pattern of one PCI component. FIGS. 5A to 5E are diagrams illustrating an example of a first cell configuration. FIG. 6 is a diagram illustrating an example of a pattern of one area component. FIG. 7A is a diagram illustrating an example of a first / second cell configuration according to Option 1.1. FIG. 7B is a diagram illustrating an example of a first / second cell configuration according to Option 1.2. FIG. 8A is a diagram illustrating an example of a first / second cell configuration according to Option 2 / 4.1. FIG. 8B is a diagram illustrating an example of a first / second cell configuration according to Option 2 / 4.2. FIG. 9A is a diagram illustrating an example of a first / second cell configuration according to Option 3 / 5.1. FIG. 9B is a diagram illustrating an example of a first / second cell configuration according to Option 3 / 5.2. FIG. 10 is a diagram illustrating an example of a change in the configuration of a second cell. FIGS. 11A to 11C are diagrams illustrating an example of a configuration of a second cell according to Option 0.3. FIG. 12 is a diagram illustrating an example of a mobility scenario. FIGS. 13A to 13C are diagrams illustrating an example of RRC parameter settings according to embodiment 1-1. FIG. 14 is a diagram illustrating an example of an instruction by a MAC CE according to Option 1-2-1. FIG. 15 is a diagram illustrating an example of an instruction by a MAC CE according to Option 1-2-2. FIG. 16 is a diagram illustrating an example of an instruction by a MAC CE according to Option 1-2-3. FIG. 17 is a diagram illustrating an example of an instruction by a MAC CE according to Option 1-2-4. FIGS. 18A to 18C are diagrams illustrating an example of an instruction field according to Options 1-3-1 / 1-3-2 / 1-3-3. FIGS. 19A to 19F are diagrams illustrating an example of RRC parameter settings according to Option 2-1-2. 20A and 20B are diagrams showing an example of an instruction by a MAC CE according to option 2-2-1. FIGS. 21A and 21B are diagrams showing an example of an instruction by a MAC CE according to option 2-2-2. FIGS. 22A and 22B are diagrams showing an example of an instruction by a MAC CE according to option 2-2-3.23A and 23B are diagrams showing an example of an instruction by a MAC CE according to Option 2-2-4. FIGS. 24A to 24C are diagrams showing an example of an instruction field according to Options 2-3-1 / 2-3-2 / 2-3-3. FIGS. 25A and 25B are diagrams showing an example of a MAC CE according to Options 3-1-1 / 3-1-2. FIGS. 26A and 26B are diagrams showing an example of a MAC CE according to Options 3-2-1 / 3-2-2. FIG. 27 is a diagram showing an example of a procedure for a second cell change / handover according to the fifth embodiment. FIG. 28 is a diagram showing another example of a procedure for a second cell change / handover according to the fifth embodiment. FIG. 29 is a diagram showing another example of a procedure for a second cell change / handover according to the fifth embodiment. FIG. 30 is a diagram showing an example of a location of a UE according to Option 5-1-2-1. FIG. 31 is a diagram showing an example of a location of a UE according to Option 5-1-2-2. FIG. 32 is a diagram showing an example of the location of a UE according to option 5-1-2-3. FIG. 33 is a diagram showing an example of the location of a UE according to option 5-1-2-4. FIG. 34 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 35 is a diagram showing an example of the configuration of a base station according to an embodiment. FIG. 36 is a diagram showing an example of the configuration of a user terminal according to an embodiment. FIG. 37 is a diagram showing an example of the hardware configuration of a base station and a user terminal according to an embodiment. FIG. 38 is a diagram showing an example of a vehicle according to an embodiment.

[0011] (Cell-free) Existing wireless communication systems (e.g., 5G NR) have adopted a cellular system in which one cell is formed by one antenna / transmitting / receiving point (TRP). The area formed by the cell is fixed / static.

[0012] In addition, existing wireless communication systems (e.g., Rel. 16 and later) have introduced distributed multi-input multi-output (Distributed MIMO, e.g., multi-TRP using multiple TRPs), which forms a communication area using the coverage of multiple antennas / TRPs. Distributed MIMO allows simultaneous communication using multiple antennas / TRPs and communication using one antenna / TRP.

[0013] By adopting distributed MIMO, it is possible to create a more favorable line-of-sight environment and improve MIMO performance.

[0014] 1A and 1B are diagrams illustrating an overview of MIMO. Fig. 1A illustrates an example of co-located MIMO. In co-located MIMO, one UE communicates with one antenna / TRP.

[0015] On the other hand, Figure 1B illustrates an example of distributed MIMO, in which one UE communicates with multiple antennas / TRPs in cooperation with each other.

[0016] In future wireless communication systems (e.g., Rel. 20 and later), the introduction of cell-free communication is being considered with the aim of further improving performance and energy efficiency through reducing interference between multiple antennas / TRPs, creating a line-of-sight environment for high-frequency use, improving frequency utilization efficiency throughout the system, and applying equal, high-quality communication to each user.

[0017] Self-Free may also be referred to as cell-free massive MIMO (mMIMO) or large-scale distributed MIMO (D-MIMO). Self-Free uses coherent cooperation of multiple access points. Self-Free may include at least one of ultra-dense deployment, scalable cooperation, user-centric clustering, super-carrier aggregation, and analog fronthaul. The user plane for cell-free may perform more flexible scheduling than existing scheduling. The control plane for cell-free may maintain some form of cell to facilitate signaling.

[0018] In cell-free, unlike conventional cellular systems, one area (which may be called a cell / sub-cell, etc.) may be formed by multiple antennas / TRPs. In other words, the area may mean a cell that is independent of the location of the antenna / TRP.

[0019] In cell-free, the set of antennas / TRPs used to form a coverage area may be changed according to the needs of UEs. For example, the set of antennas / TRPs may be changed based on the number of UEs, the number of traffic, communication purposes (e.g., initial access, data communication, measurement, reporting, etc.), etc., rather than the coverage of the antennas / TRPs.

[0020] In other words, in cell-free, the coverage between multiple antennas / TRPs may overlap.

[0021] In cell-free mode, the direction in which a synchronization signal (which may also be called, for example, a synchronization signal block (SSB), a synchronization signal / physical broadcast channel (SS / PBCH) block, etc.) is transmitted may be controlled for each antenna / TRP.

[0022] In addition, in cell-free, a central unit (CU) / distributed unit (DU) may be virtualized for each antenna, or each antenna may be managed by only the CU.

[0023] Fig. 2A is a diagram showing an overview of a cellular system, in which cells formed by each antenna / TRP are shown, and UEs communicate based on these cells.

[0024] On the other hand, Figure 2B is a diagram showing an overview of a cell-free system. In the example shown in Figure 2B, the installed antennas / TRPs do not form fixed / static cells in a cellular system. As shown in Figure 2B, in a cell-free system, one or more antennas / TRPs form areas according to conditions. Therefore, in a cell-free system, each antenna / TRP does not need to correspond to the same physical cell ID, and the areas between multiple antennas / TRPs may overlap.

[0025] Self-regulation may be achieved, for example, by coordinating a set of antennas / TRPs controlled by a central control unit (e.g., CU).

[0026] In a cell-free system, a first cell (which may be called, for example, a cell / super cell / macro cell / large cell, etc.) with a fixed physical range like a cell in a 5G NR system, and a second cell (which may be called, for example, a subcell / area / micro cell / cell / small cell / second cell within the first cell, etc.) with a quasi-static / dynamic physical range that varies based on conditions may be formed.

[0027] For example, a first cell may be referred to as a supercell to distinguish it from a second cell. When a supercell is composed of multiple second cells, the second cells may have the same definition / operation / coverage as existing cells in NR. For example, a second cell may be referred to as a subcell to distinguish it from a first cell. When a supercell or a cell is composed of multiple subcells, the subcells may have the same definition / operation / coverage as existing cells in NR.

[0028] The first cell may be a cell that is newly defined in a future wireless communication system, or may be a cell defined in an existing wireless communication system that is reused.

[0029] The configurations of the first cell and the second cell can be considered as follows: Assumption 1 and Assumption 2: The first cell is composed of multiple TRPs with one cell ID (physical cell ID (PCI)). The multiple TRPs can transmit and receive in coordination. Assumption 2: The first cell is composed of multiple TRPs (or sub-cells) with different cell IDs. The multiple TRPs / sub-cells can transmit and receive in coordination.

[0030] 3A is a diagram showing an example of the outline of the cell-free configuration assumption 1. In the example shown in FIG. 3A, each TRP included in the first cell (super cell / cell) has the same PCI (PCI #0). Multiple TRPs can communicate with one UE in a coordinated manner.

[0031] Figure 3B is a diagram showing an example of the outline of the cell-free configuration assumption 2. In the example shown in Figure 3B, each TRP included in the first cell (super cell / cell) has a different PCI (PCI #0 to #9). Multiple TRPs can communicate cooperatively with one UE.

[0032] Figure 3C is a diagram showing another example of the outline of the cell-free configuration assumption 2. In the example shown in Figure 3C, a PCI is assigned to each TRP included in the first cell (supercell / cell). In the example shown in Figure 3C, unlike the example in Figure 3B, the same PCI may correspond to multiple TRPs. Multiple TRPs can communicate cooperatively with one UE.

[0033] Transmission / reception with TRP / subcell coordination may be based on at least one of the following schemes supported in NR: - Transmission of a single TRP / subcell with dynamic TRP / subcell switching (single-TRP transmission). - Joint transmission using multiple TRPs / subcells (multi-TRP joint transmission). The joint transmission may be based on a single DCI or multiple DCIs. The joint transmission may be non-coherent joint transmission (NCJT) or coherent joint transmission (CJT).

[0034] For cell-free, assuming ideal backhaul and tight coordination, in the joint transmission scheme, CJT may be prioritized over NCJT, and single DCI-based joint transmission may be prioritized over multi-DCI-based joint transmission.

[0035] (Each Configuration of Self-Free) An example of the configuration of Self-Free will be described below.

[0036] In the present disclosure, a cell with a fixed physical range, an unchanging cell, a first cell, a super cell, a cell, a macro cell, a large cell, etc. may be read as interchangeable.

[0037] In the present disclosure, a cell whose physical range changes quasi-statically / dynamically based on conditions, a cell that changes, a second cell, a cell, an area, a microcell, a small cell, a second cell within a first cell, etc. may be read interchangeably.

[0038] In the present disclosure, the terms area, cell, coverage, range, etc. may be read interchangeably.

[0039] The first cell may include one or more second cells.

[0040] One second cell may be included in multiple first cells, and different first cells may share one second cell.

[0041] The different first cells may or may not overlap.

[0042] The UE may transmit and receive signals using a second cell included in the first cell, and may receive a configuration for the second cell and transmit and receive signals based on the configuration.

[0043] Components of one Physical Cell ID (PCI) may include at least one of the following: Number of TRPs per PCI, TRP coverage layout, Number of synchronization signals (e.g., SSB, SS / PBCH blocks) per TRP.

[0044] The configuration of the first cell may be associated with a component of the PCI. The first cell may be configured based on the component of the PCI.

[0045] 4 is a diagram showing an example of a pattern of a PCI component. As shown in FIG. 4, the PCI component is composed of the number of TRPs per PCI, the TRP coverage layout, and the number of SSBs per TRP.

[0046] As shown in FIG. 4, the number of TRPs per PCI may take one or multiple values, the TRP coverage layout may be either non-overlapping or overlapping in TRP coverage, and the number of SSBs per TRP may take one or multiple values.

[0047] In the present disclosure, the pattern related to the PCI component may be any one of patterns 1 to 5 shown in Fig. 4. The pattern numbers shown in Fig. 4 are all examples and are not limited to these examples. Furthermore, the PCI component may include elements other than those shown in Fig. 4.

[0048] 5A is a diagram showing an example of a cell configuration according to pattern 1. In the cell configuration shown in FIG. 5A, the number of TRPs included in PCI / cell is one, the TRP coverage does not overlap, and the number of SSBs per TRP is multiple. In the cell configuration shown in FIG. 5A, the coverage of the TRP may coincide with the coverage of the cell (first cell) (therefore, the coverage of the TRP is not shown in FIG. 5A).

[0049] For example, an inter-cell multi-TRP operation can be performed using a cell configuration according to Pattern 1 as shown in FIG. 5A.

[0050] 5B is a diagram showing an example of a cell configuration according to Pattern 2. In the cell configuration shown in FIG. 5B, the number of TRPs included in the PCI / cell is multiple, the TRP coverage does not overlap, and the number of SSBs per TRP is one. In the cell configuration shown in FIG. 5B, the coverage of the TRP may coincide with the coverage of the SSB (therefore, the coverage of the TRP is not shown in FIG. 5B).

[0051] For example, inter-cell multi-TRP operation can be performed using a cell configuration according to pattern 2 as shown in FIG. 5B.

[0052] 5C is a diagram showing an example of a cell configuration according to Pattern 3. In the cell configuration shown in FIG. 5C, the number of TRPs included in the PCI / cell is multiple, the TRP coverage does not overlap, and the number of SSBs per TRP is multiple.

[0053] For example, a cell configuration according to pattern 3 as shown in FIG. 5C can be used to perform inter-cell multi-TRP operation.

[0054] 5D is a diagram showing an example of a cell configuration according to Pattern 4. In the cell configuration shown in FIG. 5D, the number of TRPs included in the PCI / cell is multiple, the TRP coverage overlaps, and the number of SSBs per TRP is one. Note that in the cell configuration shown in FIG. 5D, the coverage of the TRP may coincide with the coverage of the SSB (therefore, the coverage of the TRP is not shown in FIG. 5D).

[0055] For example, inter-cell / intra-cell multi-TRP operation can be performed using a cell configuration according to Pattern 3 as shown in FIG. 5D.

[0056] 5E is a diagram showing an example of a cell configuration according to Pattern 5. In the cell configuration shown in FIG. 5E, the number of TRPs included in the PCI / cell is multiple, the TRP coverage overlaps, and the number of SSBs per TRP is multiple.

[0057] For example, inter-cell / intra-cell multi-TRP operation can be performed using a cell configuration according to pattern 3 as shown in FIG. 5D.

[0058] Furthermore, the components of one second cell (e.g., area) may include at least one of the following: - Number of CU / DUs per second cell - Number of PCIs per second cell - Number of TRPs per second cell - Number of synchronization signals (e.g., SSB, SS / PBCH blocks) per second cell.

[0059] The configuration of the second cell may be associated with the components of the second cell, and the second cell may be configured based on the components of the second cell.

[0060] 6 is a diagram showing an example of a pattern of the elements (area components) of one area. As shown in FIG. 6, the area components are composed of the number of CU / DUs per area, the number of PCIs per area, the number of TRPs per area, and the number of synchronization signals per area.

[0061] As shown in Figure 6, the number of CU / DUs per second cell, the number of PCIs per second cell, the number of TRPs per second cell, and the number of synchronization signals per second cell can each take one or more values.

[0062] In the present disclosure, a pattern related to an area component may be any of patterns A to E shown in Fig. 6. The pattern symbols shown in Fig. 6 are all examples and are not limited to these examples. Furthermore, an area component may include elements other than those shown in Fig. 6.

[0063] For example, the second cells according to the above patterns A, D, and E may be configurable in any first cell (cell configuration).

[0064] The following describes configurations related to the first cell / second cell when different cells overlap and when they do not overlap, and at least one of the following configurations related to the first cell / second cell may be defined / set.

[0065] <<Configuration of First Cell / Second Cell According to Pattern 1>> [Option 1.1] Different first cells do not have to (physically) overlap.

[0066] In this option, the second cell may be configured according to at least one of the patterns A, B, D and E above.

[0067] 7A is a diagram showing an example of a first / second cell configuration according to Option 1.1. In the example shown in FIG. 7A, two different cells (first cells) do not overlap.

[0068] In the example shown in FIG. 7A, a second cell (coverage of the second cell) related to pattern A, a second cell (coverage of the second cell) related to pattern B, and a second cell (coverage of the second cell) related to pattern D / E are shown.

[0069] In the cell configuration in FIG. 7A, the coverage of the TRP may match the coverage of the cell (first cell) (therefore, the coverage of the TRP is not shown in FIG. 7A).

[0070] In this optional configuration, only single-TRP operation may be possible in each secondary cell.

[0071] This optional configuration allows for better network energy saving (NES).

[0072] [Option 1.2] Different first cells may (physically) overlap.

[0073] In this option, the second cell may be configured according to at least one of the patterns A, B, D and E above.

[0074] 7B is a diagram showing an example of a first / second cell configuration according to Option 1.2. In the example shown in FIG. 7B, two different cells (first cells) overlap.

[0075] In the example shown in FIG. 7B, a second cell (coverage of the second cell) related to pattern A, a second cell (coverage of the second cell) related to pattern B, and a second cell (coverage of the second cell) related to pattern D / E are shown.

[0076] In the cell configuration in Figure 7B, the coverage of the TRP may match the coverage of the cell (first cell) (therefore, the coverage of the TRP is not shown in Figure 7B).

[0077] In this optional configuration, for example, inter-cell multi-TRP operation may be enabled in the second cell according to pattern D / E.

[0078] This optional configuration can, for example, increase the coverage within overlapping cells, thereby improving the uniformity of communication quality.

[0079] Furthermore, this optional configuration can increase frequency utilization efficiency by, for example, reducing coverage in overlapping cells.

[0080] In addition, in the configuration of this option, by reusing existing NR-specification antennas / TRPs, operation can be achieved by modifying the antenna / TRP devices so that they overlap with the coverage deployed by existing NR, thereby reducing station installation costs.

[0081] <<Configuration of First Cell / Second Cell According to Pattern 2 / Pattern 4>> [Option 2 / 4.1] Different first cells do not have to overlap (physically).

[0082] In this option, the second cell may be configured according to at least one of the patterns A, C, D and E above.

[0083] 8A is a diagram showing an example of the configuration of the first and second cells according to Option 2 / 4.1. In the example shown in FIG. 8A, two different cells (first cells) do not overlap.

[0084] In the example shown in FIG. 8A, a second cell (coverage of the second cell) related to pattern A, a second cell (coverage of the second cell) related to pattern C, and a second cell (coverage of the second cell) related to pattern D / E are shown.

[0085] In the cell configuration in FIG. 8A, the coverage of the TRP may coincide with the coverage of the SSB (therefore, the coverage of the TRP is not shown in FIG. 8A).

[0086] Also, in this optional configuration, only single TRP operation may be possible in each second cell.

[0087] According to this optional configuration, for example, by increasing the number of TRPs per first cell, it is possible to improve the uniformity of communication quality and frequency utilization efficiency.

[0088] [Option 2 / 4.2] Different first cells may (physically) overlap.

[0089] In this option, the second cell may be configured according to at least one of the patterns A, C, D and E above.

[0090] 8B is a diagram showing an example of the configuration of the first / second cells according to Option 2 / 4.2. In the example shown in FIG. 8B, two different cells (first cells) overlap.

[0091] In the example shown in FIG. 8B, a second cell (coverage of the second cell) related to pattern A, a second cell (coverage of the second cell) related to pattern C, and a second cell (coverage of the second cell) related to pattern D / E are shown.

[0092] In the cell configuration in FIG. 8B, the coverage of the TRP may coincide with the coverage of the SSB (therefore, the coverage of the TRP is not shown in FIG. 8B).

[0093] In this optional configuration, for example, inter-cell multi-TRP operation may be enabled in the second cell according to pattern D / E.

[0094] This optional configuration can, for example, increase the coverage within overlapping cells, thereby improving the uniformity of communication quality.

[0095] Furthermore, this optional configuration can increase frequency utilization efficiency by, for example, reducing coverage in overlapping cells.

[0096] Furthermore, according to the configuration of this option, for example, by increasing the number of TRPs per first cell, it is possible to improve the uniformity of communication quality and frequency utilization efficiency.

[0097] <<Configuration of First Cell / Second Cell According to Pattern 3 / Pattern 5>> [Option 3 / 5.1] Different first cells do not have to overlap (physically).

[0098] In this option, the second cell may be configured according to at least one of the patterns A, B, C, D and E above.

[0099] 9A is a diagram showing an example of the configuration of the first and second cells according to Option 3 / 5.1. In the example shown in FIG. 9A, two different cells (first cells) do not overlap.

[0100] In the example shown in FIG. 9A, a second cell (second cell coverage) related to pattern A, a second cell (second cell coverage) related to pattern B, a second cell (second cell coverage) related to pattern C, and a second cell (second cell coverage) related to pattern D / E are shown.

[0101] 9A shows an example in which the second cell according to pattern B is included only in the coverage of antenna / TRP#0, and FIG. 11A shows an example in which the second cell according to pattern C corresponds to the overlapping portion between the coverage of antenna / TRP#1 and the coverage of antenna / TRP#2.

[0102] In this optional configuration, single TRP operation may be possible in each second cell.

[0103] In addition, in this optional configuration, in the second cell where the coverage of multiple TRPs overlap, intra-cell multi-TRP operation may be enabled, which can improve frequency utilization efficiency.

[0104] Furthermore, according to the configuration of this option, for example, by increasing the number of TRPs per first cell, it is possible to improve the uniformity of communication quality and frequency utilization efficiency.

[0105] [Option 3 / 5.2] Different first cells may (physically) overlap.

[0106] In this option, the second cell may be configured according to at least one of the patterns A, B, C, D and E above.

[0107] 9B is a diagram showing an example of the configuration of the first / second cells according to Option 3 / 5.2. In the example shown in FIG. 9B, two different cells (first cells) overlap.

[0108] In the example shown in FIG. 9B, the second cell (coverage of the second cell) related to pattern A, the second cell (coverage of the second cell) related to pattern B, the second cell (coverage of the second cell) related to pattern C, and the second cell (coverage of the second cell) related to pattern D / E are shown.

[0109] 9B shows an example in which the second cell according to pattern B is included only in the coverage of antenna / TRP#0, and the second cell according to pattern C shown in FIG. 9B shows an example in which the second cell corresponds to the overlapping portion between the coverage of antenna / TRP#1 and the coverage of antenna / TRP#2.

[0110] In this optional configuration, for example, inter-cell multi-TRP operation may be enabled in the second cell according to pattern D / E.

[0111] In addition, in this optional configuration, in the case of the cell configuration of Pattern 5, intra-cell multi-TRP operation may be possible. By configuring in this way, it is possible to improve frequency utilization efficiency.

[0112] According to the configuration of this option, for example, it is possible to improve the uniformity of communication quality and frequency utilization efficiency compared to the above-mentioned option 1.2, and it is possible to reduce station placement costs compared to the above-mentioned option 2 / 4.2.

[0113] <<Flexibility of the Second Cell>> The second cell may be configured / reconfigured based on a specific condition / trigger. An example of the definition of the second cell will be described in detail below.

[0114] The configuration of the second cell may be changed / updated based on certain conditions / trigger(s).

[0115] The specific condition / trigger may be, for example, at least one of a condition / trigger related to UE distribution, a condition / trigger related to traffic, a condition / trigger related to a specific event, and a condition / trigger based on specific information (for example, at least one of information related to time, location information related to UE / TRP, and information related to the season).

[0116] For example, the condition / trigger related to the distribution of UEs may be a condition / trigger based on the distribution / number of UEs in the first cell / second cell.

[0117] For example, the traffic-related conditions / triggers may be conditions / triggers based on at least one of the traffic volume / communication volume within the first cell / second cell, the traffic volume / communication volume for TRP, and the traffic volume / communication volume for SSB.

[0118] For example, a specific event related to a condition / trigger for a specific event may be predefined in a specification or may depend on the implementation of the network.

[0119] For example, the condition / trigger based on specific information may be a condition / trigger based on at least one of information regarding the time of day, information regarding a specific timer, location information regarding the UE / TRP, and information regarding the time of year (e.g., date, time, day of the week, weather, etc.).

[0120] The second cell may be configured based on the particular condition / trigger, or statically, regardless of the particular condition.

[0121] The second cell may be dynamically / semi-statically configured based on the specific condition / trigger. By configuring in this manner, it is possible to reduce power consumption in the network and provide communication quality that meets the demands of the UE.

[0122] Restrictions on the change / update of the second cell may be defined. The NW may decide not to change / update the second cell in certain cases.

[0123] Fig. 10 is a diagram illustrating an example of a change in the configuration of the second cell. The example illustrated in Fig. 10 illustrates a case in which the range of the second cell (area) is changed according to the distribution of UEs and the change in time (from time #1 to time #2).

[0124] <<Definition of Second Cell>> An example of the configuration / definition of the second cell will be described below.

[0125] Regarding the configuration / definition of the second cell, at least one of the following options 0.1 and 0.2 may be appropriately and consistently combined with the above description of the second cell.

[0126] [Option 0.1] The second cell may consist of one cell (first cell) / PCI.

[0127] For example, the second cell may be identified by a PCI (similar to the existing NR). For example, the second cell may be configured with a PCI similar to the existing NR.

[0128] The PCI may be defined, for example, in the same way as the PCI defined in the existing NR.

[0129] This option may correspond to scenario 1 above.

[0130] [[Option 0.1.1]] A second cell may be configured with one TRP for one cell, in other words, one second cell may correspond to one TRP.

[0131] [[[Option 0.1.1.1]]] A second cell may be configured with one synchronization signal (e.g., SSB and / or SS / PBCH blocks) for one cell. In other words, one second cell may correspond to one synchronization signal. Such a configuration corresponds, for example, to a second cell according to Pattern A in at least one of Options 1.1, 1.2, 2 / 4.1, 2 / 4.2, 3 / 5.1, and 3 / 5.2.

[0132] [[[Option 0.1.1.2]]] A second cell may be configured with multiple synchronization signals (e.g., portions of synchronization signals) for one cell. In other words, one second cell may correspond to multiple synchronization signals (portions of synchronization signals for one cell). Such a configuration corresponds, for example, to a second cell according to Pattern B in at least one of Options 1.1, 1.2, 3 / 5.1, and 3 / 5.2.

[0133] [[[Option 0.1.1.3]]] A second cell may be configured with multiple synchronization signals for one cell (e.g., all synchronization signals for one cell). In other words, one second cell may correspond to multiple synchronization signals (all synchronization signals for one cell). Such a configuration corresponds, for example, to a second cell according to Pattern B in at least one of Options 1.1 and 1.2 above.

[0134] [[Option 0.1.2]] A second cell may be configured with multiple TRPs (e.g., portions of TRPs) for one cell. In other words, one second cell may correspond to multiple TRPs (portions of TRPs) for one cell.

[0135] [[[Option 0.1.2.1]]] A second cell may be configured with multiple synchronization signals (e.g., portions of a synchronization signal) intended for one cell. In other words, one second cell may correspond to multiple synchronization signals (portions of a synchronization signal intended for one cell). Such a configuration corresponds, for example, to a second cell according to Pattern C in at least one of Options 2 / 4.1, 2 / 4.2, 3 / 5.1, and 3 / 5.2.

[0136] [[Option 0.1.3]] A second cell may be configured with multiple TRPs for one cell (e.g., all TRPs for one cell). In other words, one second cell may correspond to multiple TRPs (all TRPs for one cell).

[0137] [[[Option 0.1.3.1]]] A second cell may be configured with one synchronization signal (e.g., SSB and / or SS / PBCH blocks) for one cell. In other words, one second cell may correspond to one synchronization signal. Such a configuration corresponds, for example, to a second cell according to Pattern A in at least one of Options 1.1 and 1.2 above.

[0138] [[[Option 0.1.3.2]]] A second cell may be configured with multiple synchronization signals (e.g., portions of synchronization signals) intended for one cell. In other words, one second cell may correspond to multiple synchronization signals (portions of synchronization signals intended for one cell). Such a configuration applies, for example, to a second cell according to Pattern B in at least one of Options 1.1 and 1.2 above, and to a second cell according to Pattern C in at least one of Options 3 / 5.1 and 3 / 5.2 above.

[0139] [[[Option 0.1.3.3]]] A second cell may be configured with multiple synchronization signals for one cell (e.g., all synchronization signals for one cell). In other words, one second cell may correspond to multiple synchronization signals (all synchronization signals for one cell). Such a configuration applies, for example, to a second cell according to Pattern B in at least one of Options 1.1 and 1.2 above, and to a second cell according to Pattern C in at least one of Options 2 / 4.1, 2 / 4.2, 3 / 5.1, and 3 / 5.2 above.

[0140] [Option 0.2] The second cell may be composed of multiple cells (first cells) / PCIs.

[0141] The PCI may be defined, for example, in the same way as the PCI defined in the existing NR.

[0142] This option may correspond to scenario 2 above.

[0143] [[Option 0.2.1]] The second cell may be configured with multiple TRPs, in other words, one second cell may correspond to multiple TRPs.

[0144] The TRP may be defined, for example, in the same way as the TRP defined in the existing NR.

[0145] [[[Option 0.2.1.1]]] The second cell may be configured with multiple synchronization signals. In other words, one second cell may correspond to multiple synchronization signals. Such a configuration corresponds, for example, to the second cell of Pattern D / E in at least one of Options 1.1, 1.2, 2 / 4.1, 2 / 4.2, 3 / 5.1, and 3 / 5.2.

[0146] Each of the above options may be selected / determined based on the above-mentioned conditions / triggers (for example, conditions / triggers based on time / number of UEs / traffic, etc.).

[0147] The change / update of each of the above options may be configured / instructed / notified to the UE based on at least one of system information (e.g., SIB / MIB), higher layer signaling (RRC parameters / MAC CE), and DCI.

[0148] The above options may be changed / updated based on the above conditions / triggers (e.g., timers / events) or based on the implementation of the NW / UE.

[0149] The second cell may be identified by a specific ID.

[0150] The particular ID may have a fixed value.

[0151] The specific ID may be a virtual ID. In other words, the specific ID may be an ID that can be dynamically changed, and the configuration / scope / position of the second cell may be dynamically changed in accordance with the change in the ID.

[0152] Common / dedicated configurations / parameters for multiple second cells may be signaled to the UE, and the configurations / parameters may be signaled using higher layer (RRC) parameters, for example.

[0153] The settings / parameters may be, for example, PCI / TRP / SSB related settings / parameters.

[0154] The second cell may be used for a particular purpose / property, or in other words, the second cell may be defined / configured / identified with a particular purpose / property.

[0155] The specific purpose may be, for example, at least one of the following: control plane, user plane, paging, measurement, reporting, measurement reporting, beam indication / activation, transmission / reception of specific channels / signals (e.g., PUCCH / PUSCH / SRS / PDCCH / PDSCH / CSI-RS), initial access, on-demand signals, and handover trigger signals.

[0156] The particular characteristic may be, for example, at least one of Doppler shift, Doppler spread, mean delay, mean spread, band / component carrier, subcarrier spacing, TCI state, spatial relationship, QCL type, timing advance value, downlink transmission timing, and RNTI.

[0157] The number (e.g., the maximum number) of PCIs / TRPs / SSBs in one second cell may be predefined in a specification, may be configured / instructed / notified to a UE using higher layer signaling (RRC / MAC CE) / DCI, may be determined based on a report of UE capability information, or may be determined by a combination of at least two of these.

[0158] The second cells may be arranged contiguously (physically / spatially), or the second cells may be arranged discontinuously (physically / spatially) from one another.

[0159] Sharing Between Second Cells [Option 0.3.1] Synchronization signals (e.g., SSBs and / or SS / PBCH blocks) may be shared between multiple second cells. A UE may assume that it can receive the same (shared / common) synchronization signal in different second cells.

[0160] In this case, the information contained in the synchronization signal may be configurable as second cell-specific information.

[0161] In option 0.3.1, the TRP / PCI may be shared among multiple second cells.

[0162] In Option 0.3.1, at least one of the following may be used among multiple second cells: an ID for the same synchronization signal (e.g., SSB ID / SSB index / candidate SSB index), an ID for the same TRP (e.g., at least one of an ID for identifying a TRP, a TRP ID, and a CORESET pool index), and the same PCI.

[0163] FIG. 11A is a diagram showing an example of an area according to Option 0.3.1. FIG. 11A shows one cell including TRP#0-TRP#3. In the example shown in FIG. 11A, Area#1 and Area#2 are formed within the coverage of TRP#0. Area#1 and Area#2 overlap in the overlapping area, and therefore Area#1 and Area#2 can share the same SSB coverage. In other words, in the overlapping area, Area#1 and Area#2 can share the same SSB / TRP / PCI.

[0164] By enabling a configuration such as option 0.3.1, the most flexible configuration of the second cell is possible.

[0165] [Option 0.3.2] Synchronization signals may not be shared among multiple second cells. The UE may assume that it does not receive the same (shared / common) synchronization signal in different multiple second cells.

[0166] In this case, the information included in the synchronization signal may be configurable as information specific to the second cell, and in this case, the second cell may be identified using an index related to the synchronization signal.

[0167] In option 0.3.2, the TRP / PCI may be shared among multiple second cells.

[0168] In option 0.3.2, at least one of the same TRP ID (e.g., at least one of an ID for identifying a TRP, a TRP ID, and a CORESET pool index) and the same PCI may be used between multiple second cells.

[0169] FIG. 11B is a diagram showing an example of an area according to Option 0.3.2. FIG. 11B shows one cell including TRP#0-TRP#3. In the example shown in FIG. 11B, Area#1 and Area#2 are formed within the coverage of TRP#1. Area#1 and Area#2 do not overlap with each other, so Area#1 and Area#2 have different SSB coverage. Therefore, areas included in Area#1 or Area#2 do not share the same SSB, but can share the same TRP / PCI.

[0170] In a configuration such as Option 0.3.2, the maximum number of second cells within a first cell may be the number of synchronization signals (SSB / SSB coverage), or, if the second cell spans multiple SSB coverages, the maximum number of second cells within a first cell may be the number of spanning SSBs (SSB groups).

[0171] [Option 0.3.3] Synchronization signals and TRPs may not be shared among multiple second cells. The UE may assume that it does not transmit / receive signals for the same TRP and does not receive the same (shared / common) synchronization signals in different multiple second cells.

[0172] In this case, the information included in the synchronization signal may be set as information specific to the second cell. Also, in this case, the second cell may be identified using an index related to the synchronization signal. Also, in this case, the second cell may be identified using an ID related to the TRP (an ID for identifying the TRP).

[0173] In option 0.3.3, the PCI may be shared among multiple second cells.

[0174] In option 0.3.3, the same PCI may be used among multiple second cells.

[0175] FIG. 11C is a diagram illustrating an example of an area according to Option 0.3.3. FIG. 11C shows one cell including TRP#0-TRP#3. In the example shown in FIG. 11C, Area#1 is formed within the coverage of TRP#2, and Area#2 is formed within the coverage of TRP#3. Area#1 and Area#2 do not overlap with each other, so Area#1 and Area#2 have different SSB coverage. Therefore, areas included in Area#1 or Area#2 may not share the same SSB, may not share the same TRP, and may share the same PCI.

[0176] In a configuration such as Option 0.3.3, the maximum number of second cells in a first cell may be the number of TRPs. Also, if the second cells span multiple TRPs, the maximum number of second cells in a first cell may be the number of spanning TRPs (TRP groups).

[0177] [Option 0.3.4] Synchronization signals, TRPs and PCIs may not be shared among multiple second cells. The UE may assume that it does not transmit / receive signals to / from the same cell (first cell / PCI), the same TRP, or receive the same (shared / common) synchronization signal among different multiple second cells.

[0178] In this case, the information included in the synchronization signal may be set as information specific to the second cell. Also, in this case, the second cell may be identified using an index related to the synchronization signal. Also, in this case, the second cell may be identified using an ID related to the TRP (an ID for identifying the TRP). Also, in this case, the second cell may be identified using a PCI.

[0179] In a configuration such as Option 0.3.4, the maximum number of second cells in a first cell may be 1. Also, when a second cell spans multiple first cells, the total maximum number of second cells may be the number of spanned first cells / PCIs (PCI groups).

[0180] Each of the above options may be selected / determined based on the above-mentioned conditions / triggers (for example, conditions / triggers based on time / number of UEs / traffic, etc.).

[0181] The change / update of each of the above options may be configured / instructed / notified to the UE based on at least one of system information (e.g., SIB / MIB), higher layer signaling (RRC parameters / MAC CE), and DCI.

[0182] The above options may be changed / updated based on the above conditions / triggers (e.g., timers / events) or based on the implementation of the NW / UE.

[0183] The ID in each of the above options (e.g., an ID related to a synchronization signal, an ID related to a TRP, and / or a PCI) may be a global ID (e.g., common to all networks) or a local ID (e.g., unique to a part of networks).

[0184] The number (e.g., the maximum number) of multiple second cells using at least one of the same synchronization signal ID, the same TRP ID, and the same PCI may be predefined in a specification, may be configured / instructed / notified to a UE using higher layer signaling (RRC / MAC CE) / DCI, may be determined based on a report of UE capability information, or may be determined by a combination of at least two of these.

[0185] (Analysis) An example of a mobility scenario in a future wireless communication system (for example, Rel. 20 or later) is shown in FIG.

[0186] In the present disclosure, a source / serving (e.g., source area / serving) may refer to a (current) target (e.g., area) before handover, and a target (e.g., target area) may refer to a target (e.g., area) to which handover is to be performed.

[0187] 12 shows patterns (patterns F-M) related to mobility scenarios in a cell-free configuration. The mobility scenario may be determined based on whether the target CU is the same as the source CU, whether the target PCI is the same as the source PCI, and whether the target TRP is the same as the source TRP.

[0188] The example shown in Figure 12 describes patterns for moving between second cells (here, areas) (i.e., when the source area and target area are different) or within a second cell (i.e., when the source area and target area are the same).

[0189] In the example shown in FIG. 12, pattern F is a mobility scenario in which the target CU is the same as the source CU, the target PCI is the same as the source PCI, and the target TRP is the same as the source TRP.

[0190] In addition, in pattern F, it is expected that the beam management operations of the existing system (defined up to Rel. 18) and operations related to changing the second cell in the case of mobility between second cells (i.e., when the source area and target area are different) will be used.

[0191] In the example shown in FIG. 12, pattern G is a mobility scenario in which the target CU is the same as the source CU, the target PCI is the same as the source PCI, and the target TRP is different from the source TRP.

[0192] In addition, in pattern G, it is expected that the beam management operations of the existing system (defined up to Rel. 18) and operations related to changing the second cell in the case of mobility between second cells (i.e., when the source area and target area are different) will be used.

[0193] In the example shown in FIG. 12, pattern H is a mobility scenario in which the target CU is the same as the source CU, the target PCI is different from the source PCI, and the target TRP is the same as the source TRP.

[0194] In addition, in pattern H, the handover is intra-CU (intra-CU) and the same TRP is shared by different PCIs. Also, in pattern H, it is assumed that an operation related to the change of the second cell is used in the case of mobility between second cells (i.e., when the source area and the target area are different).

[0195] In the example shown in FIG. 12, pattern I is a mobility scenario in which the target CU is the same as the source CU, the target PCI is different from the source PCI, and the target TRP is different from the source TRP.

[0196] In addition, in pattern I, it is assumed that intra-CU handover operations and operations related to changing the second cell in the case of mobility between second cells (i.e., when the source area and target area are different) are used.

[0197] In the example shown in FIG. 12, pattern J is a mobility scenario in which the target CU is different from the source CU, the target PCI is the same as the source PCI, and the target TRP is the same as the source TRP.

[0198] In addition, in pattern J, handover is performed within a CU, and the same TRP / PCI is shared by different CUs. In addition, in pattern J, it is assumed that an operation related to a change of the second cell is used in the case of mobility between second cells (i.e., when the source area and the target area are different).

[0199] In the example shown in FIG. 12, pattern K is a mobility scenario in which the target CU is different from the source CU, the target PCI is the same as the source PCI, and the target TRP is different from the source TRP.

[0200] In addition, in pattern K, handover is performed within a CU, and the same PCI is shared by different CUs. Also, in pattern K, it is assumed that an operation related to a change of the second cell is used in the case of mobility between second cells (i.e., when the source area and the target area are different).

[0201] In the example shown in FIG. 12, pattern L is a mobility scenario in which the target CU is different from the source CU, the target PCI is different from the source PCI, and the target TRP is the same as the source TRP.

[0202] In addition, in pattern L, the handover is an intra-CU handover, and the same TRP is shared by different CUs / PCIs. Also, in pattern L, it is assumed that an operation related to the change of the second cell is used in the case of mobility between second cells (i.e., when the source area and the target area are different).

[0203] In the example shown in FIG. 12, pattern M is a mobility scenario in which the target CU is different from the source CU, the target PCI is different from the source PCI, and the target TRP is different from the source TRP.

[0204] In addition, in pattern M, it is assumed that intra-CU handover operations and operations related to changing the second cell in the case of mobility between second cells (i.e., when the source area and target area are different) are used.

[0205] As such, multiple mobility scenarios are expected in future wireless communication systems (e.g., Rel. 20 and later), but there has been insufficient consideration of the operation, settings, etc. of the network (NW, e.g., base station) / UE to accommodate these scenarios.

[0206] Specifically, there has been insufficient consideration of the configuration related to the second cell (RRC configuration) and the method of indicating / detecting movement between the second cells.

[0207] Furthermore, within the second cell (e.g., when the PCI is the same / different between TRPs / antennas), the existing beam management framework is possible, but when crossing the boundary of the second cell (e.g., even if the PCI is the same / different between TRPs / antennas), handover operation is required.

[0208] In particular, when performing cell-free communication, it is likely that the signal strength from each TRP / antenna will be uniform at the boundary between the second cells, which may result in complex interference at the boundary, making it difficult to determine handover operation based solely on signal reception quality.

[0209] For example, in a cellular system such as that shown in Figure 2A, the signal quality from the source cell decreases at the cell edge, making it possible to clearly determine the target cell. On the other hand, in a cell-free system such as that shown in Figure 2B, an area is constructed using multiple antennas / TRPs, so the communication quality within the area is uniform, and the signal strength may change significantly at the boundary between the second cells, making it difficult to determine the handover operation.

[0210] As a method for dealing with such problems, the introduction of handover operations based on UE location information has been considered, but the consideration has not been sufficient.

[0211] If these considerations are not sufficient, it may not be possible to carry out appropriate communication using cells / areas that change dynamically / semi-statically, which may hinder improvement in communication throughput.

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

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

[0214] In the present disclosure, "A / B" and "at least one of A and B" may be interpreted interchangeably. Also, in the present disclosure, "A / B / C" may mean "at least one of A, B, and C."

[0215] In the present disclosure, terms such as notify, activate, deactivate, indicate (or indicate), select, configure, update, and determine may be read interchangeably. In the present disclosure, terms such as support, control, controllable, operate, and operate may be read interchangeably.

[0216] In the present disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher layer parameters, fields, information elements (IEs), settings, etc. may be interchangeable. In the present disclosure, Medium Access Control (MAC) control elements (CEs), update commands, activation / deactivation commands, etc. may be interchangeable.

[0217] In the present disclosure, the higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, other messages (e.g., messages from the core network such as positioning protocol (e.g., NR Positioning Protocol A (NRPPa) / LTE Positioning Protocol (LPP)) messages), or a combination thereof.

[0218] In the present disclosure, MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. Broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.

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

[0220] In the present disclosure, synchronization signals, SSBs, SS / PBCH blocks, etc. may be read interchangeably.

[0221] (Wireless communication method) In the present disclosure, PCI, target setting ID, candidate cell ID, cell ID, ID for identifying a cell (first cell), etc. may be read as interchangeable terms.

[0222] The RRC parameter / information element names and MAC CE / DCI field names in the present disclosure are merely examples and are not limited to the examples shown.

[0223] Note that the embodiments of the present disclosure are applicable without being limited to the cell-free configuration, in other words, the embodiments of the present disclosure are applicable even in cases where the cell-free configuration is not adopted.

[0224] <Tenth Embodiment> In this embodiment, the setting of the second cell will be described.

[0225] The present embodiment is roughly divided into embodiments 0-1 and 0-2. The UE / NW may apply the following embodiments 0-1 / 0-2 alone or in combination.

[0226] Furthermore, the UE / NW may switch and apply modes corresponding to the following embodiments 0-1 / 0-2 based on specific settings / parameters / instructions.

[0227] <<Embodiment 0-1>> One PCI may correspond to the second cell.

[0228] This embodiment may correspond to the above assumption 1.

[0229] A single PCI may correspond to multiple TRP / SSBs.

[0230] By adopting a configuration such as that of embodiment 0-1, more flexible communication becomes possible.

[0231] [Option 0-1-1] One secondary cell may be configured for the UE.

[0232] This configuration may be performed, for example, using higher layer signaling (for example, RRC signaling).

[0233] [Option 0-1-2] A plurality of second cells (for example, a list / set including a plurality of second cells) may be configured for the UE.

[0234] The plurality of second cells may be, for example, a plurality of second cells corresponding to one PCI.

[0235] This configuration may be performed, for example, using higher layer signaling (for example, RRC signaling).

[0236] [Option 0-1-3] The second cell may be configured for the UE using a configuration related to the serving cell (for example, ServingCellConfig).

[0237] For example, the configuration for the serving cell may include an ID (e.g., an area ID) for identifying the second cell.

[0238] In embodiment 0-1, the configuration regarding the second cell (for example, CellFree-AreaConfig) may be notified to the UE.

[0239] The configuration for the second cell may include at least one of the following information: ID for identifying the second cell, Serving cell index, PCI, (list of) indices for TRPs that constitute the second cell, and (list of) indices for reference signals (e.g., SSBs) that constitute the second cell.

[0240] The ID for identifying the second cell may indicate a unique value in the entire network, or may have a unique value within the PCI corresponding to the second cell.

[0241] In addition, the TRPs constituting the second cell may be associated with reference signals. For example, (a list of) reference signal indices may be set in a list of TRP-related indices.

[0242] <<Embodiment 0-2>> A plurality of PCIs may correspond to one second cell.

[0243] This embodiment may correspond to the above assumption 2.

[0244] A single PCI may correspond to multiple TRP / SSBs.

[0245] By adopting a configuration such as that of embodiment 0-2, it is possible to reduce the number of PCI / SSBs corresponding to one PCI.

[0246] [Option 0-2-1] One secondary cell may be configured for the UE.

[0247] This configuration may be performed, for example, using higher layer signaling (for example, RRC signaling).

[0248] [Option 0-2-2] A plurality of second cells (for example, a list / set including a plurality of second cells) may be configured for the UE.

[0249] This configuration may be performed, for example, using higher layer signaling (for example, RRC signaling).

[0250] [Option 0-2-3] The second cell may be configured for the UE using at least one of a cell group configuration (eg, CellGroupConfig) and an RRC reconfiguration (eg, RRC Reconfiguration).

[0251] For example, at least one of the configuration related to the cell group and the RRC reconfiguration may include an ID (e.g., an area ID) for identifying the second cell.

[0252] In embodiment 0-2, the configuration regarding the second cell (for example, CellFree-AreaConfig) may be notified to the UE.

[0253] The configuration for the second cell may include at least one of the following information: ID for identifying the second cell, Serving cell index, PCI, (list of) indices for TRPs that constitute the second cell, and (list of) indices for reference signals (e.g., SSBs) that constitute the second cell.

[0254] The ID for identifying the second cell may indicate a unique value in the entire network, or may have a unique value within the PCI corresponding to the second cell.

[0255] In addition, the PCI corresponding to the second cell may be associated with the TRP constituting the second cell. For example, (a list of) indices related to the TRP may be set in (a list of) the PCI corresponding to the second cell.

[0256] In addition, the TRPs constituting the second cell may be associated with reference signals. For example, (a list of) reference signal indices may be set in a list of TRP-related indices.

[0257] According to the 0th embodiment described above, the settings related to the second cell can be appropriately defined.

[0258] First Embodiment The first embodiment relates to movement / handover of a UE between second cells.

[0259] The UE may configure / instruct / trigger a change / handover to the second cell using higher layer signaling (RRC signaling / MAC CE) / DCI received from the NW (base station).

[0260] <<Embodiment 1-1>> The UE may configure / instruct / trigger a change / handover to the second cell using specific RRC parameters.

[0261] The specific RRC parameter may be, for example, an RRC reconfiguration.

[0262] [Option 1-1-1] For example, if the specific RRC parameters include a configuration for the second cell (for example, CellFree-AreaConfig), the UE may determine to perform a change / handover for the second cell.

[0263] This option may be applied, for example, to the above options 0-1-1 / 0-2-1.

[0264] For example, if the specific RRC parameters do not include a configuration for the second cell (e.g., CellFree-AreaConfig), the UE may decide not to perform a change / handover for the second cell, and in this case, the UE may decide to perform a change / handover for the (existing) first cell.

[0265] [Option 1-1-2] For example, the specific RRC parameters may include an ID for identifying the second cell.

[0266] For example, if the specific RRC parameters include an ID for identifying the second cell, the UE may determine to perform a change / handover to the second cell based on (according to) the ID.

[0267] This option may be applied, for example, to the above options 0-2-3.

[0268] For example, the UE may decide to perform a change / handover to the second cell if the current ID (e.g., serving area ID) of the second cell is different from the ID of the second cell included in the particular RRC parameter.

[0269] The UE may also receive an RRC parameter indicating whether to perform a change / handover to the second cell, and the UE may determine whether to perform a change / handover to the second cell based on the RRC parameter.

[0270] For example, if the RRC parameter indicates a first value (e.g., 0 (or 1) or false), the UE may determine not to perform a change / handover for the second cell. Also, for example, if the RRC parameter indicates a second value (e.g., 1 (or 0) or true), the UE may determine to perform a change / handover for the second cell.

[0271] The RRC parameters may be included in the specific RRC parameters together with an ID for identifying the second cell.

[0272] In this option, for example, if the UE decides not to perform a change / handover to the second cell, the UE may decide to perform a change / handover to the (existing) first cell.

[0273] [Option 1-1-3] For example, the specific RRC parameters may include at least one of a configuration related to a cell group (eg, CellGroupConfig) and a configuration related to a serving cell (eg, ServingCellConfig).

[0274] The configuration related to the cell group (e.g., CellGroupConfig) and the configuration related to the serving cell (e.g., ServingCellConfig) may be the configuration for the second cell after the change.

[0275] At least one of the configuration related to the cell group (e.g., CellGroupConfig) and the configuration related to the serving cell (e.g., ServingCellConfig) may include an ID for identifying the second cell.

[0276] For example, if the specific RRC parameters include an ID for identifying the second cell, the UE may determine to perform a change / handover to the second cell based on (according to) the ID.

[0277] This option may be applied, for example, to the above options 0-1-3 / 0-2-3.

[0278] For example, the UE may decide to perform a change / handover to the second cell if the current ID (e.g., serving area ID) of the second cell is different from the ID of the second cell included in the particular RRC parameter.

[0279] The UE may also receive an RRC parameter indicating whether to perform a change / handover to the second cell, and the UE may determine whether to perform a change / handover to the second cell based on the RRC parameter.

[0280] For example, if the RRC parameter indicates a first value (e.g., 0 (or 1) or false), the UE may determine not to perform a change / handover for the second cell. Also, for example, if the RRC parameter indicates a second value (e.g., 1 (or 0) or true), the UE may determine to perform a change / handover for the second cell.

[0281] The RRC parameters may be included in the specific RRC parameters together with an ID for identifying the second cell.

[0282] In this option, for example, if the UE decides not to perform a change / handover to the second cell, the UE may decide to perform a change / handover to the (existing) first cell.

[0283] 13A to 13C are diagrams illustrating an example of RRC parameter settings according to embodiment 1-1.

[0284] In FIG. 13A , the RRC reconfiguration includes a configuration for the second cell (CellFree-AreaConfig), an ID of the second cell (Area ID), and a parameter (area switch indicator) indicating whether or not to perform a change / handover for the second cell.

[0285] In FIG. 13A, the RRC reconfiguration includes a configuration for the second cell (CellFree-AreaConfig) corresponding to the above option 1-1-1, and the RRC reconfiguration includes an ID (Area ID) of the second cell and a parameter (area switch indicator) indicating whether to perform a change / handover for the second cell corresponding to the above option 1-1-1.

[0286] 13B shows an example in which the RRC reconfiguration includes a cell group configuration (CellGroupConfig) for changing the second cell (area). The cell group configuration (CellGroupConfig) includes a cell group ID, an ID (Area ID) of the second cell, and a parameter (area switch indicator) indicating whether to perform a change / handover for the second cell.

[0287] In FIG. 13B, the RRC reconfiguration includes a cell group configuration (CellGroupConfig) corresponding to the above option 1-1-3, and the cell group configuration includes the ID (Area ID) of the second cell and a parameter (area switch indicator) indicating whether or not to perform a change / handover regarding the second cell corresponding to the above option 1-1-3.

[0288] 13C shows an example in which the RRC reconfiguration includes a serving cell configuration (ServingCellConfig) of a second cell (area). The serving cell configuration (ServingCellConfig) includes an ID (Area ID) of the second cell and a parameter (area switch indicator) indicating whether to perform a change / handover to the second cell.

[0289] In FIG. 13C, the RRC reconfiguration includes a serving cell configuration (ServingCellConfig) corresponding to the above option 1-1-3, and the serving cell configuration includes the ID (Area ID) of the second cell and a parameter (area switch indicator) indicating whether or not to perform a change / handover regarding the second cell, corresponding to the above option 1-1-3.

[0290] According to the above embodiment 1-1, it is possible to appropriately trigger a change / handover regarding the second cell by utilizing the setting by RRC.

[0291] Embodiment 1-2 The UE may configure / instruct / trigger a change / handover to the second cell using a specific MAC CE.

[0292] This MAC CE may be, for example, a new MAC CE (defined in Rel. 20 or later) or a MAC CE that is an extension of the MAC CE for L1L2-triggered mobility (LTM) defined in Rel. 18.

[0293] [Option 1-2-1] The MAC CE may include a field related to an ID for identifying the second cell.

[0294] The UE may decide to perform a change / handover to the second cell based on (according to) the field.

[0295] This field may be included in the MAC CE in addition to or instead of the ID of the target configuration (handover destination configuration).

[0296] This option may be applied, for example, to the above options 0-1-2 / 0-2-2.

[0297] The IDs of the second cells that can be indicated by the MAC CE may be IDs of multiple (e.g., all) second cells that are set in advance using RRC signaling, or may be IDs of at least one second cell that is indicated by another MAC CE (e.g., a MAC CE for activation of a TCI state) that is received in advance.

[0298] Fig. 14 is a diagram showing an example of an instruction by a MAC CE according to option 1-2-1. Fig. 14 shows a MAC CE that is an extension of the MAC CE for LTM.

[0299] The MAC CE shown in Fig. 14 includes at least a target configuration ID field (Target Config ID) and an area ID field (Area ID). Note that the example shown in Fig. 14 illustrates a case where three area candidates are set for the UE, and an example in which the area ID field is 2 bits is shown. The area ID field may be determined based on the number of area candidates set for the UE.

[0300] The UE may determine whether to perform an area change based on the value of the area ID field included in the MAC CE as shown in Fig. 14. For example, if the field indicates "00", the UE may determine not to perform an area change, and if the field indicates "01", "10", or "11", the UE may determine to perform an area change to "Area #1", "Area #2", or "Area #3", respectively.

[0301] In the figures relating to MAC CE in the present disclosure, the field names, bit numbers, and field positions are merely examples, and are not limited to the examples shown here.

[0302] In this option, for example, if the UE decides not to perform a change / handover to the second cell, the UE may decide to perform a change / handover to the (existing) first cell.

[0303] [Option 1-2-2] The MAC CE may include a target configuration ID and a field indicating whether to perform a change / handover to the second cell.

[0304] For example, if the field indicates a first value (e.g., 0 (or 1)), the UE may determine not to perform a change / handover for the second cell. Also, for example, if the field indicates a second value (e.g., 1 (or 0)), the UE may determine to perform a change / handover for the second cell based on the target configuration ID.

[0305] The target configuration identified by the target configuration ID may include an ID for identifying the second cell, and the UE may perform a change / handover to the second cell based on the ID for identifying the second cell.

[0306] Fig. 15 is a diagram showing an example of an instruction by a MAC CE according to option 1-2-2. Fig. 15 shows a MAC CE that is an extension of the MAC CE for LTM.

[0307] The MAC CE shown in FIG. 15 includes at least a target configuration ID field (Target Config ID) and a field (flag) indicating whether or not to perform a change / handover to the second cell.

[0308] The UE may determine whether to perform an area change based on the value of a flag field included in a MAC CE as shown in Fig. 15. For example, if the field indicates "0", the UE may determine not to perform an area change, and if the field indicates "1", the UE may determine to perform an area change to an area corresponding to the target setting ID.

[0309] In this option, for example, if the UE decides not to perform a change / handover to the second cell, the UE may decide to perform a change / handover to the (existing) first cell.

[0310] [Option 1-2-3] The MAC CE may include a target setting ID.

[0311] The UE may decide whether to perform a change / handover to the second cell based on the target configuration identified by the target ID.

[0312] This option may be applied in combination with the operations of options 1-1-1 / 1-1-2 / 1-1-3 above, for example.

[0313] Fig. 16 is a diagram showing an example of an instruction by a MAC CE according to option 1-2-3. Fig. 16 shows a MAC CE that is an extension of the MAC CE for LTM.

[0314] The MAC CE shown in Fig. 16 includes at least a target configuration ID field (Target Config ID). Also, as shown in Fig. 16, the target configuration ID may be associated with an ID (e.g., an LTM candidate ID) that identifies RRC parameters related to the LTM candidate. The RRC parameters related to the LTM candidate may include the LTM candidate ID, a parameter indicating whether or not to perform a change / handover to the second cell (e.g., an area change indicator), and an ID of the second cell (area ID).

[0315] The UE may determine whether to change the area based on the value of the target setting ID included in the MAC CE as shown in FIG. 16, in accordance with the setting of the LTM candidate associated with the target setting ID.

[0316] In this option, for example, if the UE decides not to perform a change / handover to the second cell, the UE may decide to perform a change / handover to the (existing) first cell.

[0317] [Option 1-2-4] The MAC CE may include a target setting ID.

[0318] The UE may also be notified of at least one of the ID of the TCI state (joint / UL / DL TCI state), the Timing Advance (TA) value, and the random access (Contention Free Random Access (CFRA)) resource / SSB index / random access preamble index using the MAC CE.

[0319] If the ID of the second cell associated with at least one of the ID of the TCI state (joint / UL / DL TCI state), the TA value, and the random access (Contention Free Random Access (CFRA)) resource / SSB index / random access preamble index is different from the ID of the current second cell (serving area), the UE may decide to perform a change / handover to the second cell.

[0320] The target configuration ID may be associated with a handover / LTM candidate. The handover / LTM candidate may include at least one of an RRC configuration related to a TCI state (joint / UL / DL TCI state), an RRC configuration related to a TA value, and an RRC configuration related to a random access (CFRA) resource. At least one of the RRC configuration related to the TCI state (joint / UL / DL TCI state), an RRC configuration related to a TA value, and an RRC configuration related to a random access (CFRA) resource may include an ID of the second cell.

[0321] The UE may also receive an RRC parameter indicating whether to perform a change / handover to the second cell, and the UE may determine whether to perform a change / handover to the second cell based on the RRC parameter.

[0322] For example, if the RRC parameter indicates a first value (e.g., 0 (or 1) or false), the UE may determine not to perform a change / handover for the second cell. Also, for example, if the RRC parameter indicates a second value (e.g., 1 (or 0) or true), the UE may determine to perform a change / handover for the second cell.

[0323] The RRC parameter indicating whether or not to perform a change / handover to the second cell may be included in the RRC parameters for handover / LTM candidate / candidate TCI state or may be associated with any parameter included in the RRC parameters for handover / LTM candidate / candidate TCI state.

[0324] Fig. 17 is a diagram showing an example of an instruction by a MAC CE according to option 1-2-4. Fig. 17 shows a MAC CE that is an extension of the MAC CE for LTM.

[0325] The MAC CE shown in Fig. 17 includes at least a Target Config ID field and a TCI state ID field / UL TCI state ID field. The Target Config ID may be associated with an ID (e.g., an LTM candidate ID) that identifies RRC parameters related to an LTM candidate.

[0326] 17 , the RRC parameters related to the candidate TCI state / candidate UL TCI state may include a TCI state ID, a parameter indicating whether to perform a change / handover to the second cell (e.g., an area change indicator), and the ID (area ID) of the second cell. The RRC parameters related to the candidate TCI state / candidate UL TCI state may be included in the RRC parameters related to the LTM candidate. For example, a parameter related to a list of TCI states may be included in the KTM candidate, and the parameter related to the TCI state ID indicated in the list of TCI states may refer to the RRC parameters related to the candidate TCI state / candidate UL TCI state.

[0327] The UE may determine whether to perform an area change according to the TCI state in the configuration of the LTM candidate associated with the target configuration ID based on the value of the target configuration ID included in the MAC CE as shown in FIG. 17 and the indicated TCI state ID.

[0328] For example, the UE determines the TCI state / UL TCI state indicated by the TCI state list in the LTM candidate configuration associated with the target configuration ID indicated by the MAC CE, and determines whether to perform an area change based on the RRC parameters for the candidate TCI state / candidate UL TCI state including the ID of the TCI state / UL TCI state. The RRC parameters for the candidate TCI state / candidate UL TCI state may include the ID of the TCI state / UL TCI state, a parameter indicating whether to perform a change / handover to the second cell (e.g., an area change indicator), and the ID of the second cell (area ID).

[0329] In this option, for example, if the UE decides not to perform a change / handover to the second cell, the UE may decide to perform a change / handover to the (existing) first cell.

[0330] According to the above-described first and second embodiments, it is possible to appropriately trigger a change / handover regarding the second cell by utilizing the setting by RRC and the instruction by MAC CE.

[0331] <<Embodiment 1-3>> The UE may configure / instruct / trigger a change / handover regarding the second cell using at least one of a specific MAC CE and a specific DCI.

[0332] The MAC CE may be, for example, a new MAC CE (defined in Rel. 20 or later), a MAC CE that is an extension of the MAC CE defined in Rel. 18, or a MAC CE defined up to Rel. 18.

[0333] The UE may activate / deactivate the TCI state using the specific MAC CE and / or the specific DCI. The UE may be instructed about the TCI state using the specific MAC CE and / or the specific DCI.

[0334] [Option 1-3-1] A specific MAC CE / DCI may include an ID field for identifying the second cell.

[0335] The UE may perform a change / handover to the second cell based on the value of the field of that ID.

[0336] The IDs of the second cells that can be indicated by the MAC CE may be IDs of multiple (e.g., all) second cells that are set in advance using RRC signaling, or may be IDs of at least one second cell that is indicated by another MAC CE (e.g., a MAC CE for activation of a TCI state) that is received in advance.

[0337] The UE may decide to use the indicated TCI state after the second cell change.

[0338] 18A is a diagram showing an example of an instruction field related to Option 1-3-1. The UE may determine whether to perform an area change based on the value of the instruction field included in a specific MAC CE / DCI as shown in FIG. 18A. For example, if the field indicates "00", the UE may determine not to perform an area change, and if the field indicates "01", "10", or "11", the UE may determine to perform an area change to "Area #1", "Area #2", or "Area #3", respectively.

[0339] In this option, for example, if the UE decides not to perform a change / handover to the second cell, the UE may decide to perform a change / handover to the (existing) first cell.

[0340] [Option 1-3-2] A specific MAC CE / DCI may include a field indicating whether or not to perform a change / handover to the second cell.

[0341] For example, if the field indicates a first value (e.g., 0 (or 1)), the UE may determine not to perform a change / handover for the second cell. Also, for example, if the field indicates a second value (e.g., 1 (or 0)), the UE may determine to perform a change / handover for the second cell.

[0342] The indicated TCI state may be associated with a second cell, and the UE may determine whether to perform a change / handover to the second cell associated with the indicated TCI state based on the indicated TCI state and the field indicating whether to perform a change / handover to the second cell.

[0343] 18B is a diagram showing an example of an indication field related to Option 1-3-2. The UE may determine whether to perform an area change based on the value of the indication field included in a specific MAC CE / DCI as shown in FIG. 18B. For example, if the field indicates "0", the UE may determine not to perform an area change, and if the field indicates "1", the UE may determine to perform an area change to an area related to the indicated TCI state.

[0344] In this option, for example, if the UE decides not to perform a change / handover to the second cell, the UE may decide to perform a change / handover to the (existing) first cell.

[0345] [Option 1-3-3] The UE may decide whether to perform a change / handover to the second cell based on the TCI status indicated using the specific MAC CE / DCI.

[0346] For example, the UE may determine to perform a change / handover to the second cell if the ID of the second cell associated with the indicated TCI state (TCI state ID) is different from the ID of the current second cell (serving area ID).

[0347] The ID of the second cell may be included in the RRC parameters related to the TCI state for the serving cell / area.

[0348] The UE may also receive an RRC parameter indicating whether to perform a change / handover to the second cell, and the UE may determine whether to perform a change / handover to the second cell based on the RRC parameter.

[0349] For example, if the RRC parameter indicates a first value (e.g., 0 (or 1) or false), the UE may determine not to perform a change / handover for the second cell. Also, for example, if the RRC parameter indicates a second value (e.g., 1 (or 0) or true), the UE may determine to perform a change / handover for the second cell.

[0350] The RRC parameter indicating whether or not to perform a change / handover for the second cell may be included in the RRC parameters for the TCI state or may be associated with any parameter included in the RRC parameters for the TCI state.

[0351] 18C is a diagram illustrating an example of an indication field according to Option 1-3-3. The UE may determine whether to perform an area change based on the value of the indication field included in a specific MAC CE / DCI as illustrated in FIG. 18C.

[0352] For example, if the field indicates "00", the UE may refer to the RRC parameters corresponding to TCI state ID #0 and determine whether to perform an area change to the corresponding area based on the area change indicator and area ID included in the RRC parameters.

[0353] In this option, for example, if the UE decides not to perform a change / handover to the second cell, the UE may decide to perform a change / handover to the (existing) first cell.

[0354] According to the above-described first to third embodiments, it is possible to appropriately trigger a change / handover regarding the second cell by utilizing the indication by the MAC CE / DCI.

[0355] According to the first embodiment, it is possible to appropriately perform a change / handover regarding the second cell based on a notification from the NW.

[0356] Second Embodiment The second embodiment relates to movement / handover of a UE between second cells.

[0357] The UE may decide whether to change / handover to the second cell based on certain conditions.

[0358] Embodiment 2-1 The UE may be configured with the specific condition using a specific RRC parameter.

[0359] The specific RRC parameter may be, for example, an RRC reconfiguration.

[0360] The UE may use the specific RRC parameters to configure an event for triggering a change / handover to the second cell, and the UE may determine whether to perform a change / handover to the second cell based on the configured event.

[0361] The UE may also determine whether to perform a change / handover to the second cell based on an event related to a trigger for the change / handover to the second cell, which is predefined in the specifications.

[0362] The event may be, for example, a common event for multiple (for example, all) UEs / second cells, or may be, for example, a specific event for each UE / second cell.

[0363] [Option 2-1-1] For example, if an event related to triggering a change / handover regarding the second cell is met and the specific RRC parameters include a configuration regarding the second cell (e.g., CellFree-AreaConfig), the UE may determine to perform a change / handover regarding the second cell.

[0364] This option may be applied, for example, to the above options 0-1-1 / 0-2-1.

[0365] For example, if the specific RRC parameters do not include a configuration for the second cell (e.g., CellFree-AreaConfig), the UE may decide not to perform a change / handover for the second cell, and in this case, the UE may decide to perform a change / handover for the (existing) first cell.

[0366] [Option 2-1-2] For example, the specific RRC parameters or any parameter included in the specific RRC parameters may include an ID for identifying the second cell.

[0367] The arbitrary parameter included in the specific RRC parameters may be, for example, at least one of a parameter related to conditional reconfiguration (e.g., ConditionalReconfiguration), a measurement configuration (e.g., MeasConfig), a CSI reporting configuration (e.g., CSI report Config), and a CSI resource configuration (e.g., CSI resource Config).

[0368] For example, if an event for triggering a change / handover to the second cell is met and the specific RRC parameters include an ID for identifying the second cell, the UE may decide to perform a change / handover to the second cell based on (according to) the ID.

[0369] This option may be applied, for example, to the above options 0-2-3.

[0370] For example, the UE may decide to perform a change / handover to the second cell if the current ID (e.g., serving area ID) of the second cell is different from the ID of the second cell included in the particular RRC parameter.

[0371] The UE may also receive an RRC parameter indicating whether to perform a change / handover to the second cell, and the UE may determine whether to perform a change / handover to the second cell based on the RRC parameter.

[0372] For example, if the RRC parameter indicates a first value (e.g., 0 (or 1) or false), the UE may determine not to perform a change / handover for the second cell. Also, for example, if the RRC parameter indicates a second value (e.g., 1 (or 0) or true), the UE may determine to perform a change / handover for the second cell.

[0373] The RRC parameters may be included in the specific RRC parameters together with an ID for identifying the second cell.

[0374] In this option, for example, if the UE decides not to perform a change / handover to the second cell, the UE may decide to perform a change / handover to the (existing) first cell.

[0375] 19A to 19F are diagrams showing an example of RRC parameter settings related to Option 2-1-2.

[0376] In the example shown in FIG. 19A , the conditional reconfiguration (ConditionalReconfiguration) includes the ID (Area ID) of the second cell and a parameter (area switch indicator) indicating whether or not to perform a change / handover regarding the second cell.

[0377] In the example shown in FIG. 19B , the conditional reconfiguration list (CondReconfigToAddModList) includes the ID (Area ID) of the second cell and a parameter (area switch indicator) indicating whether or not to perform a change / handover regarding the second cell.

[0378] In the example shown in Figure 19C, the parameter (condExecutionCond) related to the execution condition of conditional reconfiguration in the list of conditional reconfiguration (CondReconfigToAddModList) includes the ID of the second cell (Area ID) and a parameter (area switch indicator) indicating whether to perform a change / handover regarding the second cell.

[0379] In the example shown in FIG. 19D, the measurement configuration (MeasConfig) includes the ID (Area ID) of the second cell and a parameter (area switch indicator) indicating whether or not to perform a change / handover regarding the second cell.

[0380] In the example shown in Figure 19E, the parameter (MeasObjectNR) of the measurement object included in the list of measurement objects (MeasObjectToAddModList) in the measurement configuration (MeasConfig) includes the ID (Area ID) of the second cell and a parameter (area switch indicator) indicating whether or not to perform a change / handover regarding the second cell.

[0381] In the example shown in Figure 19F, the list of measurement IDs (MeasIDToAddModList) in the measurement configuration (MeasConfig) includes the ID (Area ID) of the second cell and a parameter (area switch indicator) indicating whether or not to perform a change / handover regarding the second cell.

[0382] [Option 2-1-3] For example, the specific RRC parameters or any parameters included in the specific RRC parameters may include at least one of a configuration related to a cell group (e.g., CellGroupConfig) and a configuration related to a serving cell (e.g., ServingCellConfig).

[0383] Any parameter included in the specific RRC parameters may be a parameter related to conditional reconfiguration for the target cell / area (e.g., ConditionalReconfiguration).

[0384] The specific RRC parameters may be included in a conditional RRC reconfiguration (eg, CondRRCReconfig).

[0385] The configuration related to the cell group (e.g., CellGroupConfig) and the configuration related to the serving cell (e.g., ServingCellConfig) may be the configuration for the second cell after the change.

[0386] At least one of the configuration related to the cell group (e.g., CellGroupConfig) and the configuration related to the serving cell (e.g., ServingCellConfig) may include an ID for identifying the second cell.

[0387] For example, if an event for triggering a change / handover to the second cell is met and the specific RRC parameters include an ID for identifying the second cell, the UE may decide to perform a change / handover to the second cell based on (according to) the ID.

[0388] This option may be applied, for example, to the above options 0-1-3 / 0-2-3.

[0389] For example, the UE may decide to perform a change / handover to the second cell if the current ID (e.g., serving area ID) of the second cell is different from the ID of the second cell included in the particular RRC parameter.

[0390] The UE may also receive an RRC parameter indicating whether to perform a change / handover to the second cell, and the UE may determine whether to perform a change / handover to the second cell based on the RRC parameter.

[0391] For example, if the RRC parameter indicates a first value (e.g., 0 (or 1) or false), the UE may determine not to perform a change / handover for the second cell. Also, for example, if the RRC parameter indicates a second value (e.g., 1 (or 0) or true), the UE may determine to perform a change / handover for the second cell.

[0392] The RRC parameters may be included in the specific RRC parameters together with an ID for identifying the second cell.

[0393] In this option, for example, if the UE decides not to perform a change / handover to the second cell, the UE may decide to perform a change / handover to the (existing) first cell.

[0394] In addition, the settings / parameters related to RRC in this embodiment may be set in at least one of the settings / parameters related to L1 UE triggered measurement reporting, the settings / parameters related to (Rel. 19) conditional LTM, the settings / parameters related to L3 UE triggered measurement reporting, and the settings / parameters related to (Rel. 16) conditional handover.

[0395] According to the above embodiment 2-1, it is possible to appropriately determine a change / handover regarding the second cell by utilizing the settings by RRC.

[0396] <<Embodiment 2-2>> The UE may use a specific MAC CE to perform at least one of a change / handover report regarding the second cell and a beam report.

[0397] The MAC CE may be, for example, a new MAC CE (specified in Rel. 20 or later), a MAC CE that is an extension of the MAC CE for L1 / L3 UE triggered beam reporting, or a MAC CE that is an extension of the MAC CE for LTM (Rel. 19).

[0398] [Option 2-2-1] The MAC CE may include a field related to an ID for identifying the second cell.

[0399] The UE may use this field to report to the second cell corresponding to the field value that it will perform a change / handover regarding the second cell.

[0400] This option may be applied, for example, to the above options 0-1-2 / 0-2-2.

[0401] The IDs of the second cells that can be reported by the MAC CE may be IDs of multiple (e.g., all) second cells that are pre-configured using RRC signaling, or may be IDs of at least one second cell that is indicated by another MAC CE that is pre-received (e.g., a MAC CE for activation of a TCI state).

[0402] 20A is a diagram showing an example of an instruction by a MAC CE according to Option 2-2-1, in which a MAC CE that is an extension of a MAC CE for LTM is described.

[0403] The MAC CE shown in FIG. 20A includes at least a target configuration ID field (Target Config ID) and an area ID field (Area ID).

[0404] The UE may use the value of the area ID field included in the MAC CE as shown in FIG. 20A to report that it will change areas to the area corresponding to the field.

[0405] 20B is a diagram showing another example of an instruction by a MAC CE according to Option 2-2-1, in which a MAC CE that is an extension of the MAC CE for beam reporting is described.

[0406] The MAC CE shown in FIG. 20B includes at least an area ID field (Area ID).

[0407] The UE may use the value of the area ID field included in the MAC CE as shown in FIG. 20B to report that the area will be changed to the area corresponding to the field.

[0408] In this option, for example, if the UE decides not to perform a change / handover to the second cell, the UE may report that it will perform a change / handover to the (existing) first cell.

[0409] [Option 2-2-2] The MAC CE may include a field indicating whether or not to perform a change / handover to the second cell.

[0410] For example, when the field indicates a first value (e.g., 0 (or 1)), it may mean that the UE does not perform a change / handover to the second cell. Also, when the field indicates a second value (e.g., 1 (or 0)), it may mean that the UE performs a change / handover to the second cell.

[0411] The UE may report at least one of a target cell / area configuration (target configuration) and a target reference signal (RS) configuration, and may perform a change / handover for the second cell to a second cell included in the reported target cell / area configuration and / or the target reference signal configuration.

[0412] 21A is a diagram showing an example of an instruction by a MAC CE according to Option 2-2-2, in which a MAC CE that is an extension of a MAC CE for LTM is described.

[0413] The MAC CE shown in FIG. 21A includes at least a target configuration ID field (Target Config ID) and a field (flag) indicating whether or not to perform a change / handover to the second cell.

[0414] The UE may use the value of the flag field included in the MAC CE as shown in FIG. 21A and the value of the target configuration ID to report whether to perform an area change to the area corresponding to the target configuration ID.

[0415] 21B is a diagram showing another example of an instruction by a MAC CE according to Option 2-2-2, in which a MAC CE that is an extension of the MAC CE for beam reporting is described.

[0416] The MAC CE shown in FIG. 21B includes a field (flag) indicating whether or not to perform a change / handover regarding at least the second cell.

[0417] The UE may use the value of the area ID field included in the MAC CE as shown in FIG. 21B to report whether or not to perform an area change for the area corresponding to the RS ID (e.g., RS ID corresponding to the best reception quality) reference signal included in the MAC CE.

[0418] In this option, for example, if the UE decides not to perform a change / handover to the second cell, the UE may report that it will perform a change / handover to the (existing) first cell.

[0419] [Option 2-2-3] The MAC CE may include a target setting ID.

[0420] The UE may report whether to perform a change / handover to the second cell based on the target configuration identified by the target ID and / or the PCI.

[0421] For example, the UE may report whether to perform a change / handover to the second cell based on the ID of the second cell associated with the target configuration / PCI.

[0422] This option may be applied in combination with the above options 2-1-1 / 2-1-2 / 2-1-3, for example.

[0423] Fig. 22A is a diagram showing an example of an instruction by a MAC CE according to Option 2-2-3. Fig. 22A shows a MAC CE that is an extension of the MAC CE for LTM.

[0424] The MAC CE shown in FIG. 22A includes at least a target configuration ID field (Target Config ID).

[0425] The UE may report whether to change the area by using the value of the target setting ID included in the MAC CE as shown in FIG. 22A and the area ID associated with the target setting ID.

[0426] 22B is a diagram showing another example of an instruction by a MAC CE according to Option 2-2-3. In FIG. 22B, a MAC CE in which the MAC CE for beam reporting is extended is described.

[0427] The MAC CE shown in FIG. 22B includes at least a PCI field (PCI).

[0428] The UE may use a value of the PCI field (for example, PCI1) included in the MAC CE as shown in FIG. 22B to report whether to perform an area change to the area associated with the PCI.

[0429] In this option, for example, if the UE decides not to perform a change / handover to the second cell, the UE may report that it will perform a change / handover to the (existing) first cell.

[0430] [Option 2-2-4] The MAC CE may include a target setting ID.

[0431] The UE may also use the MAC CE to report at least one of the ID of the TCI state (joint / UL / DL TCI state), the Timing Advance (TA) value, the random access (CFRA) resource / SSB index / random access preamble index, the RS index, and the PCI.

[0432] The reported target setting ID may be associated with the LTM candidate.

[0433] The ID of the second cell may be included in at least one of the following settings associated with (included in) the LTM candidate: ID of the TCI state (joint / UL / DL TCI state), TA value, and random access (CFRA) resource / SSB index / random access preamble index.

[0434] Additionally, the ID of the second cell may be included in the CSI reporting configuration / CSI resource configuration associated with the reported PCI / RS index.

[0435] If the ID of the second cell associated with at least one of the ID of the TCI state (joint / UL / DL TCI state), the TA value, the random access (CFRA) resource / SSB index / random access preamble index, the RS index, and the PCI is different from the ID of the current second cell (serving area), the NW may determine that the UE will perform a change / handover to the second cell.

[0436] Furthermore, the UE may transmit an RRC parameter indicating whether or not to perform a change / handover regarding the second cell. The NW may determine whether or not the UE performs a change / handover regarding the second cell based on the RRC parameter.

[0437] For example, if the RRC parameter indicates a first value (e.g., 0 (or 1), or false), the NW may determine that the UE will not perform a change / handover regarding the second cell. Also, for example, if the RRC parameter indicates a second value (e.g., 1 (or 0), or true), the NW may determine that the UE will perform a change / handover regarding the second cell.

[0438] Fig. 23A is a diagram showing an example of an instruction by a MAC CE according to Option 2-2-4. Fig. 23A shows a MAC CE that is an extension of the MAC CE for LTM.

[0439] The MAC CE shown in Fig. 23A includes at least a Target Config ID field and a TCI state ID field / UL TCI state ID field. The Target Config ID may be associated with an ID (e.g., an LTM candidate ID) that identifies RRC parameters related to an LTM candidate.

[0440] The UE may use the value of the target configuration ID and the TCI state ID included in the MAC CE as shown in FIG. 23A to report whether to perform an area change to the area corresponding to the target configuration ID / TCI state ID.

[0441] 23B is a diagram showing another example of an instruction by a MAC CE according to Option 2-2-4. In FIG. 23B, a MAC CE in which the MAC CE for beam reporting is extended is described.

[0442] The MAC CE shown in FIG. 23B includes at least an RS ID field (RS ID).

[0443] The UE may report whether to change areas using the value of the RS ID field (for example, RS ID1) included in the MAC CE as shown in FIG. 23B.

[0444] In this option, for example, if the UE decides not to perform a change / handover to the second cell, the UE may decide to perform a change / handover to the (existing) first cell.

[0445] In addition, in at least one of the above options 2-2-1 to 2-2-4, when CSI of multiple PCIs is reported, the UE may report the area change using a specific PCI / RS ID.

[0446] The specific PCI / RS ID may be, for example, the PCI / RS ID with the best quality (RSRP / SINR), the first PCI / RS ID, or the PCI / RS ID corresponding to the quality reported using an absolute value (e.g., a specific number of bits (e.g., 7 bits)).

[0447] In addition, in at least one of the above-mentioned options 2-2-1 to 2-2-4, when CSI of multiple PCIs is reported, the UE may report to which area the area will be changed using a bit (e.g., 1 bit) indicating the PCI / RS ID for the area change.

[0448] According to the above-described embodiment 2-2, it is possible to appropriately report a change / handover regarding the second cell by using the MAC CE.

[0449] <<Embodiment 2-3>> The UE may use a specific UCI to perform at least one of a change / handover report regarding the second cell and a beam report.

[0450] [Option 2-3-1] A specific UCI may include an ID field for identifying the second cell.

[0451] The UE may use the ID field to report to the second cell corresponding to the field value that it will perform a change / handover regarding the second cell.

[0452] The IDs of the second cells that can be reported by the UCI may be IDs of multiple (e.g., all) second cells that are pre-configured using RRC signaling, or may be IDs of at least one second cell that is indicated by another MAC CE (e.g., a MAC CE for activation of the TCI state) that is pre-received.

[0453] 24A is a diagram showing an example of an instruction field related to Option 2-3-1. The UE may report whether to perform an area change using the value of the instruction field included in a specific UCI as shown in FIG. 24A. For example, if the field indicates "00", the UE may report that it will not perform an area change. If the field indicates "01", "10", or "11", the UE may report that it will perform an area change to "Area #1", "Area #2", or "Area #3", respectively.

[0454] In this option, for example, if the UE decides not to perform a change / handover to the second cell, the UE may report that it will perform a change / handover to the (existing) first cell.

[0455] [Option 2-3-2] A specific UCI may include a field indicating whether or not to perform a change / handover to the second cell.

[0456] For example, when the field indicates a first value (e.g., 0 (or 1)), it may mean that a change / handover regarding the second cell is not performed. Also, for example, when the field indicates a second value (e.g., 1 (or 0)), it may mean that a change / handover regarding the second cell is performed.

[0457] The UE may report the cell ID (PCI) / RS ID to the NW. The ID of the second cell may be associated with an RRC parameter associated with the cell ID (PCI) / RS ID.

[0458] The NW may determine the second cell to which the UE changes / hands over based on the ID of the second cell associated with the reported cell ID / RS ID.

[0459] In addition, the UE may report the ID of the second cell to be changed using at least one of the methods described in Option 2-3-1 above.

[0460] 24B is a diagram showing an example of an indication field related to Option 2-3-2. The UE may report whether to perform an area change using a value of an indication field included in a specific UCI as shown in FIG. 24B. For example, when the field indicates "0", it may mean that the UE does not perform an area change, and when the field indicates "1", it may mean that the UE performs an area change to the corresponding area.

[0461] In this option, for example, if the UE decides not to perform a change / handover to the second cell, the UE may report that it will perform a change / handover to the (existing) first cell.

[0462] [Option 2-3-3] The UE may report the PCI / RS ID using a specific UCI.

[0463] The PCI / RS ID reported using a particular UCI may be associated with the ID of the second cell.

[0464] The UE may report a PCI / RS ID using a specific UCI to report a change / handover to a second cell associated with the PCI / RS ID.

[0465] For example, the ID of the second cell may be included / associated in the CSI reporting configuration / CSI resource configuration associated with the PCI / RS ID being reported.

[0466] For example, the NW may determine that the UE will perform a change / handover to the second cell if the reported second cell ID is different from the current second cell ID (serving area ID).

[0467] The UE may also transmit an RRC parameter indicating whether to perform a change / handover to the second cell, and the UE may use the RRC parameter to report whether to perform a change / handover to the second cell.

[0468] For example, when the RRC parameter indicates a first value (e.g., 0 (or 1) or false), it may mean that the UE does not perform a change / handover regarding the second cell. Also, for example, when the RRC parameter indicates a second value (e.g., 1 (or 0) or true), it may mean that the UE performs a change / handover regarding the second cell.

[0469] 24C is a diagram showing an example of an indication field according to Option 2-3-3. The UE may report whether to change the area by using a value of the indication field included in a specific UCI as shown in FIG. 24C.

[0470] For example, if the field indicates "00", the UE may report that it will change the area to the area corresponding to PCI#0 / RS ID#0 (area#3 in this case).

[0471] In this option, for example, if the UE decides not to perform a change / handover to the second cell, the UE may report that it will perform a change / handover to the (existing) first cell.

[0472] According to the above-described embodiment 2-3, the change / handover regarding the second cell can be appropriately reported by utilizing the instruction by the UCI.

[0473] According to the second embodiment described above, a change / handover regarding the second cell can be appropriately performed based on a report from the UE.

[0474] The UE / NW may switch between the modes corresponding to the first and second embodiments based on specific settings / parameters / instructions.

[0475] Third Embodiment The third embodiment relates to a MAC CE for configuring / activating / deactivating a second cell.

[0476] This embodiment is roughly divided into embodiments 3-1 and 3-2. The UE / NW may apply the following embodiments 0-1 / 0-2 alone or in combination.

[0477] Furthermore, the UE / NW may switch and apply modes corresponding to the following embodiments 3-1 / 3-2 based on specific settings / parameters / instructions.

[0478] <<Embodiment 3-1>> The second cell may be configured by a cell (first cell) group, a cell (first cell), a TRP, and an SSB.

[0479] The cell group / cell / TRP / SSB that constitutes the second cell may be activated / deactivated by the MAC CE.

[0480] [Option 3-1-1] The UE may be instructed which cell groups / cells / TRPs / SSBs to activate / deactivate using a bitmap format.

[0481] The UE may activate / deactivate the corresponding cell group / cell / TRP / SSB based on the indicated bit.

[0482] The UE may determine that the corresponding cell group / cell / TRP / SSB is deactivated when the bit in the MAC CE indicates a first value (e.g., 0 (or 1)), and may determine that the corresponding cell group / cell / TRP / SSB is activated when the bit in the MAC CE indicates a second value (e.g., 1 (or 0)).

[0483] The number of bits / octets used in the MAC CE may be determined based on the number of cell groups / cells / TRPs / SSBs configurable for the UE, which is based on at least one of the configuration by RRC signaling and the reported UE capability information.

[0484] Fig. 25A is a diagram showing an example of a MAC CE according to Option 3-1-1. In the example shown in Fig. 25A, eight SSBs are configured for a UE. The UE may activate / deactivate the SSBs that make up an area using a field (bitmap) of the MAC CE as shown in Fig. 25A.

[0485] 25A is merely an example. The number of SSBs may be the number specified in the existing specifications (e.g., 64), or may be a number greater than the number specified in the existing specifications (e.g., 128 or 256), and the number may be determined for each second cell.

[0486] [Option 3-1-2] The UE may be explicitly instructed to specify one or more cell group IDs / cell IDs / TRP IDs / SSB IDs.

[0487] For the indicated cell group ID / cell ID / TRP ID / SSB ID (included in the MAC CE), the UE may activate the corresponding cell group / cell / TRP / SSB.

[0488] For cell group IDs / cell IDs / TRP IDs / SSB IDs that are not indicated (not included in the MAC CE), the UE may deactivate the corresponding cell group / cell / TRP / SSB.

[0489] The UE may assume that the SSB corresponding to the deactivated SSB ID will not be transmitted.

[0490] The number of bits used in the MAC CE may be determined based on the number of cell groups / cells / TRPs / SSBs that can be configured for the UE, which is based on at least one of the following: configuration by RRC signaling, reported UE capability information, and values ​​previously defined in a specification.

[0491] The number of octets used in the MAC CE may be determined based on the number of cell groups / cells / TRPs / SSBs that can be activated, which may be determined based on at least one of the following: configuration by RRC signaling, reported UE capability information, and values ​​predefined in a specification.

[0492] Figure 25B is a diagram showing an example of a MAC CE according to Option 3-1-2. The example shown in Figure 25B shows a case where N SSBs are activated for a UE. The UE may activate / deactivate the SSBs that make up the area using the fields of the MAC CE shown in Figure 25B.

[0493] Note that the MAC CE in the above-mentioned options 3-1-1 / 3-1-2 may be read as DCI.

[0494] When a cell is activated / deactivated using a MAC CE / DCI, the MAC CE / DCI may include a cell group ID (or a bitmap related to the cell group).

[0495] When activating / deactivating a TRP using a MAC CE / DCI, the MAC CE / DCI may include a PCI / cell group ID (or a bitmap related to a cell / cell group).

[0496] When activating / deactivating SSB using MAC CE / DCI, the MAC CE / DCI may include TRP / PCI / cell group ID (or bitmap related to TRP / cell / cell group).

[0497] Embodiment 3-2 The UE may receive a MAC CE for activating / deactivating the second cell.

[0498] [Option 3-2-1] The UE may be indicated the secondary cell to be activated / deactivated using a bitmap format.

[0499] The UE may activate / deactivate the corresponding cell group / cell / TRP / SSB based on the indicated bit.

[0500] The UE may determine that the corresponding second cell is deactivated when the bit in the MAC CE indicates a first value (e.g., 0 (or 1)), and may determine that the corresponding second cell is activated when the bit in the MAC CE indicates a second value (e.g., 1 (or 0)).

[0501] The number of bits / octets used in the MAC CE may be determined based on the number of second cells configurable for the UE, which is based on at least one of configuration via RRC signaling and reported UE capability information.

[0502] Fig. 26A is a diagram showing an example of a MAC CE according to Option 3-2-1. In the example shown in Fig. 26A, a case where eight areas are configured for a UE is shown. The UE may activate / deactivate the area configuration using a field (bitmap) of the MAC CE as shown in Fig. 26A.

[0503] 26A is merely an example. The number of second cells (areas) included in a MAC CE may be determined for each first cell.

[0504] [Option 3-2-2] The UE may be explicitly instructed of the IDs of one or more second cells.

[0505] The UE may activate the corresponding second cell for the indicated second cell ID (included in the MAC CE).

[0506] For the IDs of second cells that are not indicated (not included in the MAC CE), the UE may deactivate the corresponding second cells.

[0507] The number of bits used in the MAC CE may be determined based on the number of second cells configurable for the UE, which is based on at least one of a setting by RRC signaling, reported UE capability information, and a value predefined in a specification.

[0508] The number of octets used in the MAC CE may be determined based on the number of second cells that can be activated, which is based on at least one of the following: a configuration by RRC signaling, reported UE capability information, and a value predefined in a specification.

[0509] Figure 26B is a diagram showing an example of a MAC CE according to Option 3-2-2. The example shown in Figure 26B shows a case in which N second cells (areas) are activated for a UE. The UE may activate / deactivate areas using fields in the MAC CE as shown in Figure 26B.

[0510] Note that the MAC CE in the above-mentioned options 3-2-1 / 3-2-2 may be read as DCI.

[0511] According to the third embodiment described above, it is possible to appropriately configure / activate / deactivate a second cell using MAC CE (or DCI).

[0512] Fourth Embodiment The fourth embodiment relates to the operation of a UE moving between second cells.

[0513] In this embodiment, an operation relating to the change of the second cell of the UE in each pattern (pattern FM) of the mobility scenario in FIG. 12 described above will be described.

[0514] The UE may perform at least one of the following operations in each pattern (pattern F-M): Change the RRC configuration of the destination second cell. Switch the beam (e.g., TCI state ID / RS index).

[0515] The UE may receive an RRC reconfiguration when changing the RRC configuration, and may apply the changed RRC configuration that the UE previously holds / acquired.

[0516] The RRC setting after the change may have the same configuration as the RRC setting before the change, or may be configured with information about the difference from the RRC setting before the change.

[0517] When switching beams, the UE may switch to a beam instructed by the network, or the UE may select / decide on the beam to switch to and report the selected / decided beam to the network.

[0518] In Pattern F, the UE does not need to perform DL / UL synchronization (e.g., random access procedure) with the target area. The UE may assume that the same TA as in the serving area is used, or may use the indicated TA / TAG.

[0519] In pattern G, the UE may perform DL / UL synchronization with the target area (e.g., random access procedure / UE-based TA measurement, etc.).

[0520] In Pattern H, the UE does not need to perform DL / UL synchronization with the target area (e.g., random access procedure / UE-based TA measurement, etc.). The UE may assume that the same TA as in the serving area is used, or may use the indicated TA / TAG.

[0521] In pattern I, the UE may perform DL / UL synchronization with the target area (e.g., random access procedure / UE-based TA measurement, etc.).

[0522] In Pattern J, the UE may or may not perform DL / UL synchronization with the target area (e.g., random access procedure / UE-based TA measurement, etc.). The UE may assume that the same TA as in the serving area is used, or may use the indicated TA / TAG.

[0523] In pattern K, the UE may perform DL / UL synchronization with the target area (e.g., random access procedure / UE-based TA measurement, etc.).

[0524] In Pattern L, the UE may or may not perform DL / UL synchronization with the target area (e.g., random access procedure / UE-based TA measurement, etc.). The UE may assume that the same TA as in the serving area is used, or may use the indicated TA / TAG.

[0525] In pattern M, the UE may perform DL / UL synchronization with the target area (e.g., random access procedure / UE-based TA measurement, etc.).

[0526] As mentioned above, the UE behavior for each pattern may be predefined in a specification.

[0527] In addition, for each pattern, the UE may be configured / instructed / notified using RRC signaling / MAC CE / DCI whether or not to perform DL / UL synchronization with the target area (e.g., random access procedure / UE-based TA measurement, etc.).

[0528] For example, the UE may use a particular parameter / field / bit to determine whether to perform DL / UL synchronization with the target area (e.g., random access procedure / UE-based TA measurements, etc.).

[0529] For example, if the specific parameter / field / bit indicates a first value (e.g., 0 (or 1) or false), the UE may determine not to perform DL / UL synchronization with the target area (e.g., random access procedure / UE-based TA measurement, etc.). Also, for example, if the specific parameter / field / bit indicates a second value (e.g., 1 (or 0) or true), the UE may determine to perform DL / UL synchronization with the target area (e.g., random access procedure / UE-based TA measurement, etc.).

[0530] Furthermore, for example, the UE may determine whether to perform DL / UL synchronization with the target area (e.g., random access procedure / UE-based TA measurement, etc.) based on whether it receives a TA value for the target area using RRC signaling / MAC CE / DCI.

[0531] Also, for example, based on the reported UE capability information, it may be determined whether or not to perform DL / UL synchronization with the target area (e.g., random access procedure / UE-based TA measurement, etc.) in each pattern.

[0532] If the frequency / subcarrier spacing is different between the second cells, the UE may assume that the TA offset value configured using RRC signaling will be changed.

[0533] In this embodiment, the UE operation accompanying the movement of the UE between the second cells has been described, but this embodiment may also be applied to the UE operation accompanying the movement of the UE within the second cell.

[0534] According to the fourth embodiment described above, the operation of a UE moving between / within the second cell can be appropriately defined.

[0535] Fifth Embodiment The fifth embodiment relates to a second cell change / handover operation based on UE location information.

[0536] The UE may be triggered to change / handover to the second cell from the NW (e.g., the base station of the source cell / area), in which case the first embodiment described above is applicable.

[0537] The change / handover may be triggered, for example, using an RRC reconfiguration message and / or a MAC CE in a cell switch command.

[0538] For example, the NW (e.g., a base station in the source cell / area) may measure / obtain location information of the UE and trigger a change / handover of the UE to a second cell based on the location information (see Figure 27).

[0539] After the second cell change / handover is triggered, the UE may perform DL / UL synchronization to the target cell / area and perform the first UL transmission.

[0540] Also, for example, the UE may measure / obtain its own location information, and when a specific condition is satisfied, request a change / handover to the second cell and / or report the location information. Then, the NW (e.g., a base station of the source cell / area) may trigger the UE to change / handover to the second cell based on the location information (see FIG. 28 ).

[0541] After the second cell change / handover is triggered, the UE may perform DL / UL synchronization to the target cell / area and perform the first UL transmission.

[0542] The UE may also determine to change / handover to the second cell without an explicit instruction from the NW, in which case the second embodiment is applicable.

[0543] For example, the UE may measure / acquire its own location information and determine to perform a change / handover to the second cell when a specific condition is met. Then, the UE may transmit a notification (handover trigger notification) to the NW (e.g., a base station of the source cell / area) to perform a change / handover to the second cell (see FIG. 29 ).

[0544] After triggering the second cell change / handover, the UE may perform DL / UL synchronization to the target cell / area and make the first UL transmission.

[0545] Note that the timelines for handover operations shown in Figures 27 to 29 are merely examples and are not limited to these examples. For example, at least two operations shown in Figures 27 to 29 may be performed before or after each other. For example, the DL / UL synchronization operation by the UE and the transmission / reception operation of the handover trigger / handover trigger notification may be interchanged.

[0546] The following describes specific operations based on location information.

[0547] The UE / NW may use the location information based on the reference point to perform a change / handover to the second cell.

[0548] <<Handover Trigger Timing>> [Option 5-1-1] The NW may trigger a handover using a specific signal based on the location information of the UE reported from or measured by the NW.

[0549] The specific signal may be, for example, RRC signaling / MAC CE / DCI.

[0550] [[Option 5-1-1-1]] The UE may be triggered to handover using a signal containing explicit information.

[0551] The explicit information may be, for example, a cell / area identifying ID / TCI state ID / BWP ID for the target cell / area.

[0552] [[Option 5-1-1-2]] The UE may be triggered to handover using a signal containing implicit information.

[0553] The implicit information may be, for example, a predefined / configured TCI state ID / RS ID, a TCI state ID / RS ID associated with a cell / area different from the serving cell / area, or information about a random access channel for a cell / area different from the serving cell / area.

[0554] In addition, the UE may receive signals containing the explicit / implicit information from the target cell / source cell / target area / serving area / other area.

[0555] The other area may be, for example, an area where only specific signals (for example, at least one of signals related to handover and control signals) are transmitted.

[0556] [Option 5-1-2] The UE may measure the distance between the UE and the reference point using its own location information and the reference point that is configured / defined.

[0557] The UE may then trigger a handover based on certain conditions (eg, when certain conditions are met).

[0558] The reference point may be indicated based on the coordinates of the origin.

[0559] In the present disclosure, the reference point / origin / UE location may be represented in a Cartesian coordinate system or a polar coordinate system. Also, in the present disclosure, the reference point / origin / UE location may be represented in a global coordinate system (GCS) or a local coordinate system (LCS). Information related to conversion from GCS to LCS may be configured / instructed to the UE.

[0560] At least one of the coordinates of the reference point / origin and the specific condition may be specified in advance in a specification, may be configured / indicated / notified to the UE using RRC signaling / MAC CE / DCI, may be determined based on UE capability information, or may be determined by a combination of these.

[0561] The coordinates of the reference point / origin and at least one of the specific conditions may be set / indicated / determined UE specific, or may be set / indicated / determined UE common.

[0562] The coordinates of the reference point / origin and / or the specific condition may be set / indicated / determined per BWP / CC / cell / cell group / area / UE.

[0563] The coordinates of the reference point / origin and the configurable maximum number of specific conditions may be determined based on UE capability information or may be configured using RRC signaling.

[0564] In the present disclosure, the specific condition may include at least one of a condition related to the location information of the UE and a condition related to the speed / acceleration / measurement results (e.g., L1 / L3-RSRP / SINR) of the UE. At least one of these conditions may be a condition based on an actual measurement value or a condition based on a predicted value. An AI (Artificial Intelligence) / ML (Machine Learning) model on the UE / NW side may be used to calculate the predicted value.

[0565] The following describes the location information and specific conditions of the UE: The location information and specific conditions of the UE related to the handover operation may be determined according to at least one of the following options 5-1-2-1 to 5-1-2-4.

[0566] [[Option 5-1-2-1]] One specific condition (for example, a threshold / magnitude relationship regarding distance / coordinate) and one reference point may be set.

[0567] For example, if the specific condition is distance (a positive value (e.g., which may be the square of the distance)), handover may be triggered if the distance condition between the reference point and the UE is greater / less than a threshold.

[0568] In this case, the distance condition between the reference point and the UE may be set separately for each axis of the Cartesian coordinate system (x-axis, y-axis, z-axis).

[0569] In this case, the distance condition between the reference point and the UE may be set with respect to any of the axes in the Cartesian coordinate system (x-axis, y-axis, z-axis).

[0570] For example, if the specific condition is a coordinate (positive or negative value), a handover may be triggered if the UE's location coordinate is greater than / less than the specific coordinate.

[0571] In this case, handover may be triggered if the UE's location coordinates are large / small in any of the components (x component, y component, z component) of a particular coordinate.

[0572] In this case, handover may be triggered if the UE's location coordinates are larger or smaller than any of the specific coordinate components (x component, y component, z component).

[0573] In this case, the value of each component of the specific coordinate may be set to either positive or negative.

[0574] When each coordinate is expressed in a Cartesian coordinate system, the coordinate of the reference point #n (n may be a natural number) is expressed as (x ｎ , y ｎ , z ｎ ) and the coordinates of the UE are (x', y', z'), the distance l from the reference point #n to the UE is ｎ is {(x ｎ -x') ２ +(y ｎ -y') ２ +(z ｎ -z') ２} １／２ Whether to perform handover or not can be determined by ｎ and the condition L for each reference point #n ｎ (And L ｎ ') may be compared.

[0575] FIG. 30 is a diagram illustrating an example of the location of a UE according to Option 5-1-2-1. In the example shown in FIG. 30, handover for a second cell is performed using one reference point (reference point #1) and a threshold distance (L １ ) and the UE's position (distance from the reference point l １ ) is determined based on the

[0576] [[Option 5-1-2-2]] One specific condition (for example, a threshold / magnitude relationship regarding distance / coordinates) and multiple reference points may be set.

[0577] For the conditions for each reference point, option 5-1-2-1 above may be applied.

[0578] For each reference point, a trigger for a different UE action (e.g., handover action, event-related decision, signal quality measurement, and / or starting / stopping of a specific timer) may be configured.

[0579] FIG. 31 is a diagram showing an example of the location of a UE according to Option 5-1-2-2. In the example shown in FIG. 31, handover for the second cell is performed using multiple reference points (reference points #1 and #2) and distance thresholds (L １ and L ２ ,In addition, L １ =L ２ ), and the UE's position (distance l from reference point #1). １ , and the distance l from reference point #2 ２ ) is determined based on the

[0580] [[Option 5-1-2-3]] A plurality of specific conditions (for example, thresholds / magnitude relationships related to distance / coordinates) and one reference point may be set.

[0581] For each condition, option 5-1-2-1 above may be applied.

[0582] For each condition, a different UE action may be triggered (eg, handover action, event-related decision, signal quality measurement, and / or starting / stopping of a specific timer).

[0583] FIG. 32 is a diagram illustrating an example of the location of a UE according to Option 5-1-2-3. In the example shown in FIG. 32, handover for the second cell is performed using one reference point (reference point #1) and a threshold distance (L １ and L １ ') and the UE's position (distance l from reference point #1). １ ) is determined based on the

[0584] [[Option 5-1-2-4]] A plurality of specific conditions (for example, thresholds / magnitude relationships related to distance / coordinates) and a plurality of reference points may be set.

[0585] For each condition for each reference point, option 5-1-2-1 above may be applied.

[0586] For each condition for each reference point, a different UE action may be triggered (e.g., handover action, event decision, signal quality measurement, and / or starting / stopping of a specific timer).

[0587] FIG. 33 is a diagram showing an example of the location of a UE according to Option 5-1-2-4. In the example shown in FIG. 33, handover for the second cell is performed using multiple reference points (reference point #1) and distance thresholds from each reference point (for reference point 1, L １ and L １ ', and for reference point #2, L ２ ), and the UE's position (distance l from reference point #1). １ , and the distance l from reference point #2 ２ ) is determined based on the

[0588] In the present disclosure, the object / action triggered by the UE or the object / action triggered by the UE may be at least one of a handover operation, a request for handover to the NW, an event-related measurement, a signal quality measurement, and starting / stopping a specific timer.

[0589] In this embodiment, information / conditions regarding an event may be set to the UE from the NW, or the event may be specified in advance in specifications.

[0590] <<Type of Origin / Reference Point>> The type of origin / reference point may be specified in advance in a specification, may be configured / instructed / notified to the UE using RRC signaling / MAC CE / DCI, may be determined based on reported UE capability information, or may be determined based on a combination of these.

[0591] The origin / reference point may be defined / set as the location of a physical object.

[0592] For example, the origin / reference point may be the location / coordinates of a particular base station / TRP / UE.

[0593] For example, multiple candidates for origin / reference points may be configured / defined in advance. In this case, which of the multiple candidates to use as an origin / reference point may be configured / indicated / notified using RRC signaling / MAC CE / DCI, may be defined in advance in a specification, may be determined based on reported UE capability information, or may be determined by a combination of these.

[0594] The origin / reference point may also be defined / set as a position calculated using a particular method.

[0595] For example, the origin / reference point may be at least one of the position / coordinates of the cell edge / area edge, the position / coordinates a specific distance away from a specific base station / TRP / UE, and the center of gravity / centre of the coordinates of multiple base stations / TRPs / UEs.

[0596] For example, multiple candidates for origin / reference point / specific distance may be configured / defined in advance. In this case, which of the multiple candidates for origin / reference point / specific distance to use may be configured / indicated / notified using RRC signaling / MAC CE / DCI, may be defined in advance in a specification, may be determined based on reported UE capability information, or may be determined by a combination of these.

[0597] The origin / reference point may also be defined / set as an arbitrary location, in which case the origin / reference point may be determined by the UE or based on coordinates (e.g., longitude / latitude / altitude) used by other services.

[0598] The origin / reference point may be set / defined in common for non-terrestrial networks (NTN) and terrestrial networks (TN), or may be set / defined separately.

[0599] <<Notification to NW about Trigger>> The UE may use a specific UL signal to transmit a notification about triggering handover (handover trigger notification) to the NW.

[0600] The specific UL signal may be, for example, a PUCCH / PUSCH / PRACH / SRS / other signal.

[0601] For example, the UE may transmit a handover trigger notification to the NW using a scheduling request (SR). In this case, the UE may use an SR configuration / SR resource dedicated for the notification. If an SR configuration / SR resource dedicated for the notification is not configured for the UE, the UE may use a normal (non-dedicated) SR configuration / SR resource.

[0602] For example, the UE may transmit a handover trigger notification to the NW using a MAC CE. In this case, the UE may transmit the MAC CE on the PUSCH if there is an UL grant (e.g., an available resource on the PUSCH), or may transmit an SR to request an UL grant if there is not.

[0603] For example, the UE may transmit a handover trigger notification to the NW using UCI. In this case, the UE may use resources allocated in periodic / aperiodic / semi-persistent CSI reporting. To distinguish / identify from existing CSI reporting, a bit for identifying the use of CSI may be set, or one or more specific bits may be used for the handover trigger notification.

[0604] The UE may send a handover trigger notification to the base station / TRP of the serving cell / area or to the base station / TRP of the target cell / area (a cell / area with a different frequency / CU / DU from the serving cell / area).

[0605] The handover trigger notification may include at least one of information / number for identifying the conditions related to the trigger, information / number for identifying the triggered content, information / number of the target cell / area, TCI state ID, TA, TAG ID, measured quality of the signal (L1 / L3-RSRP / SINR), and an index of the reference signal corresponding to the measured quality.

[0606] <UE Actions After Handover Trigger> After handover is triggered, the UE may perform at least one of the following actions: Transmit PRACH to the target cell / area Monitor PDCCH in the target cell / area Stop transmitting / receiving signals to / from the source cell / area Perform RRC reconfiguration.

[0607] The UE may not transmit a PRACH to the target cell / area (i.e., the UE may not perform a random access procedure) in certain cases, which may be at least one of the following cases: the UE already has / acquires the TA of the target cell / area, the TA of the source cell / area is the same as the TA of the target cell / area, and the TA of the target cell / area is included in the signal for triggering handover.

[0608] <<Method for measuring location information>> The location information of a UE may be measured / determined based on at least one of the time / phase (e.g., time / phase shift) of a PDCCH / PDSCH / reference signal (e.g., SSB / CSI-RS / TRS) transmitted from the network, the PUCCH / PUSCH / reference signal (e.g., SRS) transmitted from the UE, and the TA.

[0609] In addition, the location information of the UE may be measured / determined based on information (e.g., the UE's movement route, the UE's stay time / time at a specific point) obtainable from a specific service (e.g., Mobility as a Service (MaaS) / Global Positioning System (GPS)) / node (e.g., Location Management Function (LMF)) in a higher layer.

[0610] In addition, the location information of the UE may be determined based on (existing) positioning / sensing related information.

[0611] The location information of the UE may be measured by the UE and reported to the NW, or may be measured by the NW.

[0612] The location information of the UE may be an actual measurement value or a predicted value. The measurement / prediction of the location information of the UE may use an AI / ML model on the UE / NW side.

[0613] In this embodiment, the information may be interchangeably read as location information, destination base station information (e.g., PCI, etc.), information estimated on the network side based on information from L1 / L3 reports, information about a continuous route predicted on the UE side, and time information about the location where the UE is located.

[0614] According to the fifth embodiment described above, by changing / handing over the second cell based on the location information of the UE, it is possible to appropriately change / hand over the second cell even when the quality changes suddenly / complexly at the boundary of the second cell.

[0615] <Supplementary Information> [Notification of Information to UE] In the above-described embodiments, any information may be notified to the UE (from a network (NW) (e.g., a base station (BS))) (in other words, reception of any information from the BS by the UE) using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.

[0616] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new Logical Channel ID (LCID) in the MAC subheader, which is not defined in existing standards.

[0617] When the notification is made by DCI, the notification may be made by a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used to scramble Cyclic Redundancy Check (CRC) bits assigned to the DCI, the format of the DCI, etc.

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

[0619] [Notification of Information from UE] In the above-described embodiments, notification of any information from the UE (to the NW) (in other words, transmission / report of any information from the UE to the BS) may be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PUCCH, PUSCH, PRACH, reference signal), or a combination thereof.

[0620] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new LCID, which is not defined in existing standards, in the MAC subheader.

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

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

[0623] [Application of Each Embodiment] At least one of the above-described embodiments may be applied when a specific condition is met. The specific condition may be defined in a standard or may be notified to a UE / BS using higher layer signaling / physical layer signaling.

[0624] At least one of the above-described embodiments may be applied only to UEs that have reported or support a particular UE capability.

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

[0626] Furthermore, the above-mentioned specific UE capability may be a capability that is applied across all frequencies (commonly regardless of frequency), or may be a capability for each frequency (e.g., one or a combination of a cell, a band, a band combination, a BWP, a component carrier, etc.), or may be a capability for each frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), or may be a capability for each subcarrier spacing (SubCarrier Spacing (SCS)), or may be a capability for each Feature Set (FS) or Feature Set Per Component-carrier (FSPC).

[0627] Furthermore, the specific UE capability may be a capability that is applied to all duplexing methods (commonly regardless of the duplexing method), or may be a capability for each duplexing method (e.g., Time Division Duplex (TDD) or Frequency Division Duplex (FDD)).

[0628] Furthermore, at least one of the above-described embodiments may be applied when the UE configures / activates / triggers specific information related to the above-described embodiments (or performs the operations of the above-described embodiments) through higher layer signaling / physical layer signaling. For example, the specific information may be information indicating that cell-free operation is enabled, any RRC parameter for a specific release (e.g., Rel. 20 or later), etc.

[0629] If the UE does not support at least one of the specific UE capabilities or is not configured with the specific information, the UE may apply the behavior of, for example, Rel. 15-19.

[0630] (Supplementary Notes) The following inventions are supplemented with respect to one embodiment of the present disclosure. [Supplementary Note 1-1] A terminal having a transceiver unit that receives a handover trigger instruction based on location information of the terminal or transmits a notification that the handover has been triggered, and a control unit that controls the handover operation based on the trigger instruction or the notification. [Supplementary Note 1-2] The terminal described in Supplementary Note 1-1, wherein the trigger instruction is transmitted based on location information of the terminal measured by a network or the terminal. [Supplementary Note 1-3] The terminal described in Supplementary Note 1-1 or Supplementary Note 1-2, wherein the notification is transmitted to a cell before handover or a cell after handover. [Supplementary Note 1-4] The terminal described in any of Supplements 1-1 to 1-3, wherein the control unit controls the handover operation in accordance with location information of the terminal that is based on one or more reference points and one or more conditions corresponding to the reference points. [Supplementary Note 2-1] A terminal having a receiving unit that receives a Radio Resource Control (RRC) configuration related to a cell whose physical range is to be changed, and a control unit that controls handover operations between a plurality of the cells based on the RRC configuration. [Supplementary Note 2-2] The terminal according to Supplementary Note 2-1, in which one physical cell identifier (PCI) related to a cell whose physical range is not to be changed corresponds to one cell whose physical range is to be changed. [Supplementary Note 2-3] The terminal according to Supplementary Note 2-1 or Supplementary Note 2-2, in which one cell whose physical range is to be changed corresponds to a plurality of physical cell identifiers (PCI) related to cells whose physical range is not to be changed. [Supplementary Note 2-4] The terminal according to any of Supplements 2-1 to 2-3, in which the RRC configuration includes at least one of an identifier of a cell whose physical range is to be changed, an identifier of a cell whose physical range is not to be changed, an identifier of a serving cell, a transmission / reception point index, and a reference signal index. [Supplementary Note 3-1] A terminal having a receiver that receives trigger information related to handover, and a controller that controls at least one of uplink synchronization and downlink synchronization for a cell whose physical range is changed based on the trigger information. [Supplementary Note 3-2] The terminal according to Supplementary Note 3-1, wherein the trigger information is transmitted using Radio Resource Control (RRC) reconfiguration.[Supplementary Note 3-3] The terminal according to Supplementary Note 3-1 or Supplementary Note 3-2, wherein the trigger information is transmitted using a specific Medium Access Control (MAC) control element. [Supplementary Note 3-4] The terminal according to any of Supplementary Note 3-1 to Supplementary Note 3-3, wherein the trigger information is transmitted using downlink control information. [Supplementary Note 4-1] A terminal comprising: a control unit that determines whether to perform an operation related to a handover to a cell whose physical range is changed, based on a trigger condition related to the handover, and a transmission unit that transmits a report related to the handover if the handover operation is to be performed. [Supplementary Note 4-2] The terminal according to Supplementary Note 4-1, wherein the trigger condition is set using Radio Resource Control (RRC) reconfiguration. [Supplementary Note 4-3] The terminal according to Supplementary Note 4-1 or Supplementary Note 4-2, wherein the report related to the handover is transmitted using a specific Medium Access Control (MAC) control element or uplink control information. [Supplementary Note 4-4] The terminal according to any one of Supplementary Note 4-1 to Supplementary Note 4-3, wherein the operation related to the handover is at least one of uplink synchronization and downlink synchronization for the cell. [Supplementary Note 5-1] A terminal comprising: a receiver that receives Medium Access Control (MAC) control elements for activation of at least one of: a first cell whose physical range does not change, including a second cell whose physical range is changed; a group of the first cells; a transmission / reception point that constitutes the second cell; a synchronization signal transmitted within the second cell; and the second cell; and a controller that determines at least one of activation of the first cell, activation of the group of first cells, activation of the transmission / reception point, activation of the synchronization signal, and activation of the second cell based on the MAC control elements. [Supplementary Note 5-2] The MAC control element, in a bitmap format, indicates at least one of activation of the first cell, activation of the group of the first cell, activation of the transmission / reception point, activation of the synchronization signal, and activation of the second cell. The terminal according to Supplementary Note 5-1.[Supplementary Note 5-3] The terminal according to Supplementary Note 5-1 or Supplementary Note 5-2, wherein the MAC control element includes at least one of an identifier of the first cell, an identifier of the group of the first cell, an identifier of the transmission / reception point, an index of the synchronization signal, and an identifier of the second cell. [Supplementary Note 5-4] The terminal according to any of Supplementary Notes 5-1 to 5-3, wherein when the first cell is activated by the MAC control element, the MAC control element includes an identifier of the group of the first cell, when the transmission / reception point is activated by the MAC control element, the MAC control element includes an identifier of the group of the first cell and an identifier of the first cell, and when the synchronization signal is activated by the MAC control element, the MAC control element includes an identifier of the group of the first cell, an identifier of the first cell, and an identifier of the transmission / reception point.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0675] The transceiver 120 may transmit a Radio Resource Control (RRC) configuration for a cell whose physical range is to be changed. The controller 110 may use the RRC configuration to issue instructions for handover operations between the cells (a zeroth embodiment).

[0676] The transceiver 120 may transmit trigger information related to handover, and the controller 110 may use the trigger information to instruct at least one of uplink synchronization and downlink synchronization for a cell whose physical range is changed (first and fourth embodiments).

[0677] The transceiver 120 may transmit a setting of a trigger condition for a handover to a cell whose physical range is to be changed, and the controller 110 may control reception of a report on the handover transmitted based on the trigger condition (second embodiment).

[0678] The transceiver 120 may transmit a Medium Access Control (MAC) control element for activating at least one of a first cell whose physical range is not changed, including a second cell whose physical range is changed, a group of the first cells, a transmission / reception point constituting the second cell, a synchronization signal transmitted within the second cell, and the second cell. The control unit 110 may use the MAC control element to instruct at least one of activation of the first cell, activation of the group of the first cells, activation of the transmission / reception point, activation of the synchronization signal, and activation of the second cell (third embodiment).

[0679] The transmitting / receiving unit 120 may transmit a handover trigger instruction based on the location information of the terminal or receive a notification that the handover has been triggered. The control unit 110 may determine the handover operation based on the trigger instruction or the notification (fifth embodiment).

[0680] (User terminal) Fig. 36 is a diagram showing an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transceiver unit 220, and a transceiver antenna 230. Note that the user terminal 20 may include one or more of each of the control unit 210, the transceiver unit 220, and the transceiver antenna 230.

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

[0682] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be configured from a controller, a control circuit, etc., which are described based on common understanding in the technical field to which the present disclosure relates.

[0683] The control unit 210 may control signal generation, mapping, etc. The control unit 210 may control transmission and reception, measurement, etc. using the transceiver unit 220 and the transceiver antenna 230. The control unit 210 may generate data, control information, sequences, etc. to be transmitted as signals and transfer them to the transceiver unit 220.

[0684] The transceiver unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transceiver unit 220 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

[0685] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may be composed of a transmission processing unit 2211 and an RF unit 222. The receiving unit may be composed of a reception processing unit 2212, an RF unit 222, and a measurement unit 223.

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

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

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

[0689] The transceiver unit 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 210, and generate a bit string to be transmitted.

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

[0691] Whether or not to apply DFT processing may be based on the setting of transform precoding. When transform precoding is enabled for a certain channel (e.g., PUSCH), the transceiver unit 220 (transmission processing unit 2211) may perform DFT processing as the transmission processing to transmit the channel using a DFT-s-OFDM waveform, and if not, it may not be necessary to perform DFT processing as the transmission processing.

[0692] The transceiver unit 220 (RF unit 222) may perform modulation, filtering, amplification, etc. on the baseband signal to a radio frequency band, and transmit the radio frequency band signal via the transceiver antenna 230.

[0693] On the other hand, the transceiver unit 220 (RF unit 222) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transceiver antenna 230.

[0694] The transceiver unit 220 (reception processing unit 2212) may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, and acquire user data, etc.

[0695] The transceiver 220 (measurement unit 223) may perform measurements on the received signal. For example, the measurement unit 223 may perform RRM measurements, CSI measurements, etc. based on the received signal. The measurement unit 223 may measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 210.

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

[0697] The transmitting unit and receiving unit of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting / receiving unit 220 and the transmitting / receiving antenna 230.

[0698] The transceiver 220 may receive a Radio Resource Control (RRC) configuration for a cell whose physical range is to be changed, and the controller 210 may control handover operations between the cells based on the RRC configuration (a zeroth embodiment).

[0699] One physical cell identifier (PCI) for a cell whose physical range is not changed may correspond to one cell whose physical range is changed (0th embodiment).

[0700] A cell whose physical range is changed may correspond to a plurality of physical cell identifiers (PCIs) relating to cells whose physical range is not changed (0th embodiment).

[0701] The RRC configuration may include at least one of an identifier of a cell whose physical range is changed, an identifier of a cell whose physical range is not changed, an identifier of a serving cell, an index of a transmission / reception point, and an index of a reference signal (embodiment 0).

[0702] The transceiver 220 may receive trigger information related to handover, and the controller 210 may control at least one of uplink synchronization and downlink synchronization for a cell whose physical range is changed based on the trigger information (first and fourth embodiments).

[0703] The trigger information may be transmitted using Radio Resource Control (RRC) reconfiguration (first embodiment).

[0704] The trigger information may be transmitted using a specific Medium Access Control (MAC) control element (first embodiment).

[0705] The trigger information may be transmitted using downlink control information (first embodiment).

[0706] The control unit 210 may determine whether to perform an operation related to the handover based on a trigger condition related to the handover for the cell whose physical range is changed. If the handover operation is to be performed, the transceiver unit 220 may transmit a report related to the handover (second embodiment).

[0707] The trigger condition may be configured using a Radio Resource Control (RRC) reconfiguration (second embodiment).

[0708] The handover report may be sent using a specific Medium Access Control (MAC) control element or uplink control information (second embodiment).

[0709] The handover-related operation may be at least one of uplink synchronization and downlink synchronization for the cell (fourth embodiment).

[0710] The transceiver unit 220 may receive Medium Access Control (MAC) control elements for activating at least one of a first cell whose physical range is not changed, including a second cell whose physical range is changed, a group of the first cells, a transmission / reception point constituting the second cell, a synchronization signal transmitted within the second cell, and the second cell. Based on the MAC control elements, the control unit 210 may determine at least one of activation of the first cell, activation of the group of the first cells, activation of the transmission / reception point, activation of the synchronization signal, and activation of the second cell (third embodiment).

[0711] The MAC control element may instruct, in a bitmap format, at least one of activating the first cell, activating the group of first cells, activating the transmission / reception point, activating the synchronization signal, and activating the second cell (third embodiment).

[0712] The MAC control element may include at least one of an identifier of the first cell, an identifier of the group of the first cell, an identifier of the transmission / reception point, an index of the synchronization signal, and an identifier of the second cell (third embodiment).

[0713] When the MAC control element activates the first cell, the MAC control element may include an identifier of a group of the first cell. When the MAC control element activates the transmission / reception point, the MAC control element may include an identifier of the group of the first cell and an identifier of the first cell. When the MAC control element activates the synchronization signal, the MAC control element may include an identifier of the group of the first cell, an identifier of the first cell, and an identifier of the transmission / reception point (third embodiment).

[0714] The transceiver 220 may receive a handover trigger instruction based on the location information of the terminal, or may transmit a notification that the handover has been triggered. The controller 210 may control the handover operation based on the trigger instruction or the notification (fifth embodiment).

[0715] The trigger instruction may be transmitted based on location information of the terminal measured by the network or the terminal (fifth embodiment).

[0716] The notification may be sent to the cell before the handover or the cell after the handover (fifth embodiment).

[0717] The control unit 210 may control the handover operation according to location information of the terminal based on one or more reference points and one or more conditions corresponding to the reference points (fifth embodiment).

[0718] (Hardware Configuration) Note that the block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining software with the single device or the multiple devices.

[0719] Here, the functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission may be called a transmitting unit, transmitter, etc. As described above, the implementation method of each is not particularly limited.

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

[0721] In the present disclosure, the terms apparatus, circuit, device, section, unit, etc. may be used interchangeably. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.

[0722] For example, although only one processor 1001 is shown, there may be multiple processors. Furthermore, processing may be performed by one processor, or processing may be performed by two or more processors simultaneously, serially, or in other ways. Furthermore, processor 1001 may be implemented by one or more chips.

[0723] Each function in the base station 10 and the user terminal 20 is realized, for example, by loading specified software (programs) onto hardware such as a processor 1001 and a memory 1002, causing the processor 1001 to perform calculations, control communication via the communication device 1004, and control at least one of reading and writing data in the memory 1002 and the storage 1003.

[0724] The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, at least a part of the above-mentioned control unit 110 (210), transceiver unit 120 (220), etc. may be realized by the processor 1001.

[0725] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and the other functional blocks may be implemented in a similar manner.

[0726] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EEPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. The memory 1002 may also be referred to as a register, cache, main memory, etc. The memory 1002 may store executable programs (program codes), software modules, etc. for implementing a wireless communication method according to an embodiment of the present disclosure.

[0727] Storage 1003 is a computer-readable recording medium and may be composed of at least one of, for example, a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disc (e.g., a Compact Disc ROM (CD-ROM)), a digital versatile disc, a Blu-ray disc), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, a stick, a key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be referred to as an auxiliary storage device.

[0728] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmission / reception unit 120 (220), transmission / reception antenna 130 (230), etc. may be realized by the communication device 1004. The transmission / reception unit 120 (220) may be implemented as a transmission unit 120a (220a) and a reception unit 120b (220b) that are physically or logically separated.

[0729] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, a light emitting diode (LED) lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0730] Furthermore, each device, such as the processor 1001 and the memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0731] Furthermore, the base station 10 and the user terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized using this hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0732] (Modifications) Note that terms described in the present disclosure and terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, a channel, a symbol, and a signal (signal or signaling) may be interchangeable. A signal may also be a message. A reference signal may be abbreviated as RS, and may also be called a pilot, pilot signal, etc. depending on the applicable standard. A component carrier (CC) may also be called a cell, frequency carrier, carrier frequency, etc.

[0733] A radio frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting a radio frame may be called a subframe. Furthermore, a subframe may be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0734] Here, the numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel, and may indicate at least one of, for example, Subcarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame structure, specific filtering performed by a transceiver in the frequency domain, and specific windowing performed by a transceiver in the time domain.

[0735] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol) in the time domain. A slot may also be a time unit based on numerology.

[0736] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (PUSCH) mapping type B.

[0737] A radio frame, a subframe, a slot, a minislot, and a symbol all represent time units for transmitting signals. The radio frame, the subframe, the slot, the minislot, and the symbol may be referred to by other names corresponding to the radio frame, the subframe, the slot, the minislot, and the symbol. Note that the time units such as a frame, a subframe, a slot, a minislot, and a symbol in the present disclosure may be interchangeable.

[0738] For example, one subframe may be referred to as a TTI, or multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.

[0739] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. Note that the definition of TTI is not limited to this.

[0740] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0741] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0742] A TTI having a time length of 1 ms may be called a regular TTI (TTI in 3GPP Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0743] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and greater than or equal to 1 ms.

[0744] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may be determined based on numerology.

[0745] In addition, an RB may include one or more symbols in the time domain and may have a length of one slot, one minislot, one subframe, or one TTI, each of which may be composed of one or more resource blocks.

[0746] In addition, one or more RBs may be referred to as a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

[0747] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0748] A Bandwidth Part (BWP), which may also be referred to as a partial bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a Common Reference Point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

[0749] The BWP may include a UL BWP (BWP for UL) and a DL BWP (BWP for DL). One or more BWPs may be configured for a UE within one carrier.

[0750] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0751] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

[0752] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by a predetermined index.

[0753] The names used for parameters and the like in this disclosure are not intended to be limiting in any way. Furthermore, the mathematical expressions and the like using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0754] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0755] Furthermore, information, signals, etc. may be output from a higher layer to a lower layer and / or from a lower layer to a higher layer. Information, signals, etc. may be input / output via multiple network nodes.

[0756] Input and output information, signals, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information, signals, etc. may be overwritten, updated, or added. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.

[0757] The notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information in the present disclosure may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof.

[0758] Note that the physical layer signaling may be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be referred to as an RRC message, such as an RRC Connection Setup message or an RRC Connection Reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, a MAC Control Element (CE).

[0759] Furthermore, notification of specified information (e.g., notification that "it is X") is not limited to explicit notification, but may be made implicitly (e.g., by not notifying the specified information or by notifying other information).

[0760] The determination may be made by a value represented by one bit (0 or 1), by a Boolean value represented by true or false, or by a comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0761] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0762] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), these wired and / or wireless technologies are included within the definition of transmission media.

[0763] As used in this disclosure, the terms "system" and "network" may be used interchangeably. A "network" may refer to devices included in the network (e.g., base stations).

[0764] In this disclosure, terms such as "precoding," "precoder," "weight (precoding weight)," "Quasi-Co-Location (QCL)," "Transmission Configuration Indication state (TCI state)," "spatial relation," "spatial domain filter," "transmit power," "phase rotation," "antenna port," "layer," "number of layers," "rank," "resource," "resource set," "beam," "beam width," "beam angle," "antenna," "antenna element," "panel," "UE panel," "transmitting entity," "receiving entity," etc. may be used interchangeably.

[0765] In the present disclosure, the term "antenna port" may be interchangeably read as an antenna port for any signal / channel (e.g., a demodulation reference signal (DMRS) port). In the present disclosure, the term "resource" may be interchangeably read as a resource for any signal / channel (e.g., a reference signal resource, an SRS resource, etc.). The resource may include time / frequency / code / space / power resources. Furthermore, the spatial domain transmission filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.

[0766] The group may include, for example, at least one of a spatial relationship group, a Code Division Multiplexing (CDM) group, a Reference Signal (RS) group, a Control Resource Set (CORESET) group, a PUCCH group, an antenna port group (e.g., a DMRS port group), a layer group, a resource group, a beam group, an antenna group, a panel group, and the like.

[0767] In addition, in the present disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, codeword (CW), transport block (TB), RS, etc. may be read as interchangeable terms.

[0768] In addition, in the present disclosure, the terms TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, joint TCI state, etc. may be read interchangeably.

[0769] Furthermore, in the present disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) property," and "specific QCL type (e.g., Type A, Type D)" may be interchangeable.

[0770] In the present disclosure, terms such as index, identifier (ID), indicator, indication, and resource ID may be interchangeable. In the present disclosure, terms such as sequence, list, set, group, cluster, and subset may be interchangeable.

[0771] Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and the spatial relationship information (TCI state) may be interchangeable. The "spatial relationship information (TCI state)" may be interchangeable with "set of spatial relationship information (TCI state)", "one or more pieces of spatial relationship information", etc. The TCI state and the TCI may be interchangeable. The spatial relationship information and the spatial relationship may be interchangeable.

[0772] In the present disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNB (eNodeB)," "gNB (gNodeB)," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "cell," "sector," "cell group," "carrier," "component carrier," etc. may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.

[0773] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication service within that coverage.

[0774] In the present disclosure, a base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control / operate based on the information.

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

[0776] A mobile station may also be referred to as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0777] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. Note that at least one of the base station and the mobile station may be a device mounted on a moving object, the moving object itself, etc.

[0778] The mobile body is a movable object that can move at any speed and naturally includes cases where the mobile body is stationary. Examples of the mobile body include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and objects mounted thereon. The mobile body may also be a mobile body that moves autonomously based on an operation command.

[0779] The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Note that at least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0780] 38 is a diagram showing an example of a vehicle according to an embodiment. The vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, an electronic control unit 49, various sensors (including a current sensor 50, an RPM sensor 51, an air pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58), an information service unit 59, and a communication module 60.

[0781] The drive unit 41 is configured with at least one of an engine, a motor, and a hybrid of an engine and a motor, for example. The steering unit 42 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels 46 and the rear wheels 47 based on the operation of the steering wheel operated by a user.

[0782] The electronic control unit 49 is composed of a microprocessor 61, memory (ROM, RAM) 62, and a communication port (for example, an input / output (IO) port) 63. Signals are input to the electronic control unit 49 from various sensors 50-58 provided in the vehicle. The electronic control unit 49 may also be called an Electronic Control Unit (ECU).

[0783] The signals from the various sensors 50-58 include a current signal from a current sensor 50 that senses the current of the motor, a rotation speed signal of the front wheels 46 / rear wheels 47 obtained by a rotation speed sensor 51, an air pressure signal of the front wheels 46 / rear wheels 47 obtained by an air pressure sensor 52, a vehicle speed signal obtained by a vehicle speed sensor 53, an acceleration signal obtained by an acceleration sensor 54, a depression amount signal of the accelerator pedal 43 obtained by an accelerator pedal sensor 55, a depression amount signal of the brake pedal 44 obtained by a brake pedal sensor 56, an operation signal of the shift lever 45 obtained by a shift lever sensor 57, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 58.

[0784] The information service unit 59 is composed of various devices, such as a car navigation system, an audio system, speakers, a display, a television, and a radio, for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 59 uses information acquired from external devices via the communication module 60 or the like to provide various information / services (e.g., multimedia information / multimedia services) to the occupants of the vehicle 40.

[0785] The information service unit 59 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

[0786] The driving assistance system unit 64 includes various devices for providing functions to prevent accidents and reduce the driver's driving burden, such as millimeter-wave radar, Light Detection and Ranging (LiDAR), cameras, positioning locators (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyro systems (e.g., Inertial Measurement Units (IMUs), Inertial Navigation Systems (INSs)), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driving assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driving assistance functions or autonomous driving functions.

[0787] The communication module 60 can communicate with the microprocessor 61 and components of the vehicle 40 via the communication port 63. For example, the communication module 60 transmits and receives data (information) via the communication port 63 to and from the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and the various sensors 50-58, which are provided in the vehicle 40.

[0788] The communication module 60 is a communication device that can be controlled by the microprocessor 61 of the electronic control unit 49 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 60 may be located either inside or outside the electronic control unit 49. The external device may be, for example, the base station 10 or the user terminal 20 described above. Furthermore, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 described above (or may function as at least one of the base station 10 and the user terminal 20).

[0789] The communication module 60 may transmit at least one of signals from the above-mentioned various sensors 50-58 input to the electronic control unit 49, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 59 to an external device via wireless communication. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 60 may include information based on the above-mentioned input.

[0790] The communication module 60 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from an external device and displays it on an information service unit 59 provided in the vehicle. The information service unit 59 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH received by the communication module 60 (or data / information decoded from the PDSCH)).

[0791] Furthermore, the communication module 60 stores various information received from external devices in a memory 62 that can be used by the microprocessor 61. Based on the information stored in the memory 62, the microprocessor 61 may control the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, various sensors 50-58, and the like provided in the vehicle 40.

[0792] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple user terminals (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "sidelink"). For example, terms such as an uplink channel and a downlink channel may be read as a sidelink channel.

[0793] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station 10 may be configured to have the functions of the user terminal 20 described above.

[0794] In the present disclosure, an operation described as being performed by a base station may be performed by its upper node in some cases. It is apparent that in a network including one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (such as, but not limited to, a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc.), or a combination thereof.

[0795] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, the order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0796] Each aspect / embodiment described in the present disclosure may be a technology other than Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (x is, for example, an integer or decimal number)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802. The present invention may be applied to systems that use IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable wireless communication methods, or to next-generation systems that are expanded, modified, created, or defined based on these. Furthermore, the present invention may be applied to a combination of multiple systems (e.g., a combination of LTE or LTE-A and 5G).

[0797] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0798] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0799] The term "determining" as used in this disclosure may encompass a wide variety of actions. For example, "determining" may be considered to be judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., looking up in a table, database, or another data structure), ascertaining, etc.

[0800] Additionally, "determining" may be considered to be "determining" receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), etc.

[0801] Furthermore, "determination" may be considered to be "determining" resolving, selecting, choosing, establishing, comparing, etc. In other words, "determination" may be considered to be "determining" some kind of action. In the present disclosure, "determination" may be read interchangeably with the above-mentioned actions.

[0802] Furthermore, in this disclosure, "determine / determining" may be interchangeably read as "assume / assuming," "expect / expecting," "consider / considering," etc. Furthermore, in this disclosure, "does not expect to do..." may be interchangeably read as "assumes not to do...."

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

[0804] The "maximum transmit power" in this disclosure may mean the maximum value of transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0805] As used in this disclosure, the terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access."

[0806] In this disclosure, when two elements are connected, they may be considered to be "connected" or "coupled" to one another using one or more wires, cables, printed electrical connections, etc., as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range, light (both visible and invisible) range, etc., as some non-limiting and non-exhaustive examples.

[0807] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0808] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0809] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

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

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

[0812] In the present disclosure, terms such as "when A, B," "if A, (then) B," "B upon A," "B in response to A," "B based on A," "B during / while A," "B before A," "B at (the same time as) / on A," "B after A," "B since A," and "B until A" may be interchangeable. Note that A, B, and the like herein may be replaced with appropriate expressions such as nouns, gerunds, and regular sentences, depending on the context. Note that the time difference between A and B may be approximately zero (immediately after or immediately before). A time offset may also be applied to the time at which A occurs. For example, "A" may be interchangeable with "before / after a time offset at which A occurs." The time offset (eg, one or more symbols / slots) may be predefined or may be specified by the UE based on signaled information.

[0813] In the present disclosure, timing, time, duration, time instance, any time unit (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc. may be read interchangeably.

[0814] Although the invention according to the present disclosure has been described in detail above, it will be apparent to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure.

Claims

1. A terminal comprising: a transceiver that receives a handover trigger instruction based on the position information of the terminal or transmits a notification indicating that the handover has been triggered; and a controller that controls the operation of the handover based on the trigger instruction or the notification.

2. The terminal according to claim 1, wherein the trigger instruction is transmitted based on the position information of the terminal measured by the network or the terminal.

3. The terminal according to claim 1, wherein the notification is transmitted to the cell before the handover or the cell after the handover.

4. The terminal according to claim 1, wherein the controller controls the operation of the handover according to the position information of the terminal based on one or more reference points and one or more conditions corresponding to the reference points.

5. A wireless communication method of a terminal, comprising: receiving a handover trigger instruction based on the position information of the terminal or transmitting a notification indicating that the handover has been triggered; and controlling the operation of the handover based on the trigger instruction or the notification.

6. A base station comprising: a transceiver that transmits a handover trigger instruction based on the position information of the terminal or receives a notification indicating that the handover has been triggered; and a controller that determines the operation of the handover based on the trigger instruction or the notification.

Images