WO2025141792A1 - User equipment, wireless communication method, and base station - Google Patents

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

This disclosure relates to terminals, wireless communication methods, and base stations in next-generation mobile communication systems.

Long Term Evolution (LTE) was specified for Universal Mobile Telecommunications System (UMTS) networks with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). In addition, LTE-Advanced (3GPP Rel. 10-14) was specified for the purpose of achieving higher capacity and greater sophistication over LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9).

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 and later, etc.) are also under consideration.

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

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

However, there has been insufficient concrete consideration of cell-free communication. If this consideration is insufficient, it will not be possible to control the network (NW) in response to communication traffic, etc., and there is a risk that improvements in communication throughput will be hindered.

Therefore, one of the objectives of this disclosure is to provide a terminal, a wireless communication method, and a base station that can perform suitable power control for a network and can perform more flexible communications.

A terminal according to one aspect of the present disclosure has a transceiver unit that receives a handover trigger instruction based on the location information of the terminal or transmits 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.

According to one aspect of the present disclosure, it is possible to perform optimal power control of the network, enabling more flexible communication.

1A and 1B are diagrams showing an overview of MIMO. 2A is a diagram showing an overview of a cellular system, and FIG 2B is a diagram showing an overview of a cell-free system. 3A to 3C are diagrams showing an example of an outline of each assumed cell-free configuration. FIG. 4 is a diagram showing an example of a pattern of one PCI component. 5A to 5E are diagrams showing an example of the configuration of the first cell. FIG. 6 is a diagram showing an example of a pattern of components (area components) of one area. Fig. 7A is a diagram showing an example of a configuration of a first/second cell according to option 1.1. Fig. 7B is a diagram showing an example of a configuration of a first/second cell according to option 1.2. Fig. 8A is a diagram showing an example of a configuration of a first/second cell according to option 2/4.1 Fig. 8B is a diagram showing an example of a configuration of a first/second cell according to option 2/4.2 Fig. 9A is a diagram showing an example of a configuration of a first/second cell according to option 3/5.1 Fig. 9B is a diagram showing an example of a configuration of a first/second cell according to option 3/5.2 FIG. 10 is a diagram showing an example of a change in the configuration of the second cell. 11A to 11C are diagrams showing an example of the configuration of a second cell according to option 0.3. FIG. 12 illustrates an example of a mobility scenario. 13A to 13C are diagrams showing an example of RRC parameter settings relating to embodiment 1-1. Figure 14 is a diagram showing an example of an instruction by a MAC CE relating to option 1-2-1. Figure 15 is a diagram showing an example of an instruction by a MAC CE relating to option 1-2-2. Figure 16 shows an example of an instruction by a MAC CE relating to option 1-2-3. Figure 17 is a diagram showing an example of an instruction by a MAC CE relating to option 1-2-4. 18A-18C are diagrams showing an example of an instruction field relating to options 1-3-1/1-3-2/1-3-3. 19A to 19F are diagrams showing an example of RRC parameter settings relating to Option 2-1-2. Figures 20A and 20B are diagrams showing an example of an instruction by a MAC CE relating to option 2-2-1. Figures 21A and 21B are figures showing an example of an instruction by a MAC CE relating to option 2-2-2. Figures 22A and 22B are figures showing an example of an instruction by a MAC CE relating to option 2-2-3. Figures 23A and 23B are figures showing an example of an instruction by a MAC CE relating to option 2-2-4. 24A to 24C are diagrams showing an example of an instruction field relating to options 2-3-1/2-3-2/2-3-3. Figures 25A and 25B are diagrams showing an example of a MAC CE relating to options 3-1-1/3-1-2. Figures 26A and 26B are diagrams showing an example of a MAC CE relating to options 3-2-1/3-2-2. FIG. 27 is a diagram showing an example of a second cell change/handover procedure according to the fifth embodiment. FIG. 28 is a diagram showing another example of the procedure of the second cell change/handover according to the fifth embodiment. FIG. 29 is a diagram showing another example of the procedure of the second cell change/handover according to the fifth embodiment. FIG. 30 is a diagram showing an example of the location of a UE according to option 5-1-2-1. FIG. 31 is a diagram showing an example of the 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 illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 35 is a diagram illustrating an example of the configuration of a base station according to an embodiment. FIG. 36 is a diagram illustrating 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 illustrating an example of a vehicle according to an embodiment.

(Selfie)
In existing wireless communication systems (e.g., 5G NR), a cellular system has been adopted in which one cell is formed by one antenna/transmitting/receiving point (TRP) in principle. The area formed by the cell is fixed/static.

Also, in existing wireless communication systems (e.g., Rel. 16 and later), distributed multi-input multi-output (Distributed MIMO, e.g., multi-TRP using multiple TRPs) has been introduced, which forms a communication area by the coverage of multiple antennas/TRPs. Distributed MIMO allows simultaneous communication using multiple antennas/TRPs, as well as communication using one antenna/TRP.

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

Figures 1A and 1B are diagrams showing an overview of MIMO. Figure 1A shows an example of Co-located MIMO. In Co-located MIMO, one UE communicates with one antenna/TRP.

On the other hand, Figure 1B shows an example of distributed MIMO. In distributed MIMO, one UE communicates with multiple antennas/TRPs that are linked together.

In future wireless communication systems (e.g., Rel. 20 and later), the introduction of cell-free communication is being considered for the purpose 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.

Self-free may 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 provide more flexible scheduling than existing scheduling. The control plane for cell-free may maintain some form of cells to facilitate signaling.

Unlike conventional cellular systems, in cell-free, one area (which may be called a cell/sub-cell, etc.) may be formed by multiple antennas/TRPs. In other words, the area may refer to a cell that is not dependent on the position of the antenna/TRP.

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

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

In cell-free, the direction in which a synchronization signal (which may 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.

In addition, in cell-free, the central unit (CU)/distributed unit (DU) may be virtualized for each antenna. Alternatively, each antenna may be managed by the CU alone.

Figure 2A is a diagram showing an overview of a cellular system. Figure 2A shows the cells formed by each antenna/TRP, and the UE communicates based on these cells.

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

Selfie may be achieved, for example, by adjusting a set of antennas/TRPs controlled by a central control unit (e.g., CU).

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 sub cell/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.

For example, a first cell may be called a supercell to distinguish it from a second cell. If a supercell is composed of multiple second cells, the second cells may have a similar definition/operation/coverage to existing cells in NR. For example, a second cell may be called a subcell to distinguish it from a first cell. If a supercell or cell is composed of multiple subcells, the subcells may have a similar definition/operation/coverage to existing cells in NR.

The first cell may be a cell that is newly defined in a future wireless communication system, or the definition of a cell in an existing wireless communication system may be reused.

The configurations of the first cell and the second cell are considered as follows:
Assumption 1: The first cell is composed of multiple TRPs having one cell ID (physical cell ID (PCI)). The multiple TRPs can transmit and receive in cooperation with each other.
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 a coordinated manner.

FIG. 3A is a diagram showing an example of an overview 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 cooperatively with one UE.

Figure 3B is a diagram showing an example of an overview 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.

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

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

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.

(Each component in the cell-free system)
An example of a configuration in the cell-free system will be described below.

In this disclosure, a cell with a fixed physical range, a cell that does not change, a first cell, a super cell, a cell, a macro cell, a large cell, etc. may be interpreted as interchangeable.

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 interpreted as interchangeable.

In this disclosure, area, cell, coverage, range, etc. may be interpreted as interchangeable.

The first cell may include one or more second cells.

A single second cell may be included in multiple first cells. Different first cells may share a single second cell.

The different first cells may or may not overlap.

The UE may transmit and receive signals using a second cell included in the first cell. The UE may receive a configuration related to the second cell and transmit and receive signals based on the configuration.

A Physical Cell ID (PCI) Component 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.

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.

Figure 4 shows an example of a pattern of a single PCI component. As shown in Figure 4, a PCI component is composed of the number of TRPs per PCI, the TRP coverage layout, and the number of SSBs per TRP.

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

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. In addition, the PCI component may include elements other than the elements shown in FIG. 4.

FIG. 5A is a diagram showing an example of a cell configuration relating to pattern 1. In the cell configuration shown in FIG. 5A, the number of TRPs included in the PCI/cell is one, the TRP coverage does not overlap, and the number of SSBs per TRP is multiple. Note that in the cell configuration in FIG. 5A, 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. 5A).

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

Figure 5B is a diagram showing an example of a cell configuration relating to pattern 2. In the cell configuration shown in Figure 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. Note that in the cell configuration in Figure 5B, the coverage of the TRP may match the coverage of the SSB (so the coverage of the TRP is not shown in Figure 5B).

For example, inter-cell multi-TRP operation can be performed using a cell configuration related to pattern 2 as shown in Figure 5B.

FIG. 5C is a diagram showing an example of a cell configuration related 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.

For example, inter-cell multi-TRP operation can be performed using a cell configuration related to pattern 3 as shown in Figure 5C.

Figure 5D is a diagram showing an example of a cell configuration related to pattern 4. In the cell configuration shown in Figure 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 in Figure 5D, the TRP coverage may match the SSB coverage (therefore, the TRP coverage is not shown in Figure 5D).

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.

FIG. 5E is a diagram showing an example of a cell configuration related 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.

For example, inter-cell/intra-cell multi-TRP operation can be performed using a cell configuration related to pattern 3 as shown in Figure 5D.

Additionally, components of one second cell (e.g., area) may include at least one of the following:
- Number of CU/DU per second cell.
PCI number per second cell.
- Number of TRPs per second cell.
Number of synchronization signals (eg, SSBs, SS/PBCH blocks) per second cell.

The configuration of the second cell may be associated with the components of the second cell. The second cell may be configured based on the components of the second cell.

Figure 6 shows an example of a pattern of the components (area components) of one area. As shown in Figure 6, the area components are composed of the number of CUs/DUs per area, the number of PCIs per area, the number of TRPs per area, and the number of synchronization signals per area.

As shown in FIG. 6, the number of CUs/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.

In the present disclosure, the pattern related to the area component may be any one 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. In addition, the area component may include elements other than the elements shown in FIG. 6.

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

Below, configurations related to the first cell/second cell in cases where different cells overlap and in cases where they do not overlap will be described. At least one of the configurations related to the first cell/second cell described below may be defined/set.

Configuration of the first cell/second cell according to pattern 1
[Option 1.1]
The different first cells may not (physically) overlap.

In this option, a second cell relating to at least one of the above patterns A, B, D, and E may be configured.

FIG. 7A is a diagram showing an example of the configuration of the first and second cells according to option 1.1. In the example shown in FIG. 7A, the two different cells (first cells) do not overlap.

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

Note that 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).

In this optional configuration, only single-TRP operation may be possible in each second cell.

This optional configuration allows for more optimal network energy saving (NES).

[Option 1.2]
The different first cells may (physically) overlap.

In this option, a second cell relating to at least one of the above patterns A, B, D, and E may be configured.

FIG. 7B is a diagram showing an example of the configuration of the first and second cells related to option 1.2. In the example shown in FIG. 7B, two different cells (first cells) overlap.

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

Note that in the cell configuration in FIG. 7B, the coverage of the TRP may match the coverage of the cell (first cell) (so the coverage of the TRP is not shown in FIG. 7B).

In this optional configuration, for example, inter-cell multi-TRP operation may be possible in the second cell related to pattern D/E.

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

In addition, this optional configuration can improve frequency utilization efficiency, for example, by reducing the coverage in overlapping cells.

In addition, with this optional configuration, existing NR-specification antennas/TRPs can be reused, allowing operation by modifying the antenna/TRP equipment so that it overlaps with the coverage deployed with existing NR, reducing station installation costs.

Configuration of the first cell/second cell according to Pattern 2/Pattern 4
[Option 2/4.1]
The different first cells may not (physically) overlap.

In this option, a second cell relating to at least one of the above patterns A, C, D, and E may be configured.

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

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

Note that in the cell configuration in Figure 8A, the coverage of the TRP may match the coverage of the SSB (so the coverage of the TRP is not shown in Figure 8A).

In addition, in this optional configuration, only single-TRP operation may be possible in each second cell.

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.

[Option 2/4.2]
The different first cells may (physically) overlap.

In this option, a second cell relating to at least one of the above patterns A, C, D, and E may be configured.

FIG. 8B is a diagram showing an example of the configuration of the first and second cells related to option 2/4.2. In the example shown in FIG. 8B, two different cells (first cells) overlap.

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

Note that in the cell configuration in Figure 8B, the coverage of the TRP may match the coverage of the SSB (so the coverage of the TRP is not shown in Figure 8B).

In this optional configuration, for example, inter-cell multi-TRP operation may be possible in the second cell related to pattern D/E.

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

In addition, this optional configuration can improve frequency utilization efficiency, for example, by reducing the coverage in overlapping cells.

Furthermore, with this optional configuration, for example, it is possible to increase the uniformity of communication quality and frequency utilization efficiency by increasing the number of TRPs per first cell.

Configuration of the first cell/second cell according to Pattern 3/Pattern 5
[Option 3/5.1]
The different first cells may not (physically) overlap.

In this option, a second cell may be configured that corresponds to at least one of the above patterns A, B, C, D, and E.

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

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.

Note that the second cell according to pattern B shown in FIG. 9A is an example that is included only in the coverage of antenna/TRP#0. Also, the second cell according to pattern C shown in FIG. 11A is an example that corresponds to the overlapping portion of the coverage of antenna/TRP#1 and the coverage of antenna/TRP#2.

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

In addition, in this optional configuration, intra-cell multi-TRP operation may be possible in a second cell where the coverage of multiple TRPs overlap. By configuring in this way, it is possible to improve frequency utilization efficiency.

Furthermore, with this optional configuration, for example, it is possible to increase the uniformity of communication quality and frequency utilization efficiency by increasing the number of TRPs per first cell.

[Option 3/5.2]
The different first cells may (physically) overlap.

In this option, a second cell may be configured that corresponds to at least one of the above patterns A, B, C, D, and E.

FIG. 9B is a diagram showing an example of the configuration of the first and second cells related to option 3/5.2. In the example shown in FIG. 9B, two different cells (first cells) overlap.

In the example shown in FIG. 9B, 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.

Note that the second cell of pattern B shown in FIG. 9B is an example that is included only in the coverage of antenna/TRP#0. Also, the second cell of pattern C shown in FIG. 9B is an example that falls in the overlapping area between the coverage of antenna/TRP#1 and the coverage of antenna/TRP#2.

In this optional configuration, for example, inter-cell multi-TRP operation may be possible in the second cell relating to pattern D/E.

In addition, in the configuration of this option, 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.

The configuration of this option can improve the uniformity of communication quality and frequency utilization efficiency compared to the above-mentioned option 1.2, and can reduce station placement costs compared to the above-mentioned option 2/4.2.

Flexibility of the second cell
The second cell may be configured/reconfigured based on certain conditions/triggers, an example of a definition of the second cell is described in detail below.

The configuration of the second cell may be changed/updated based on specific conditions/triggers.

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 season).

For example, the condition/trigger regarding the distribution of UEs may be a condition/trigger based on the distribution/number of UEs in the first cell/second cell.

For example, the traffic-related condition/trigger may be a condition/trigger based on at least one of the traffic volume/communication volume in the first cell/second cell, the traffic volume/communication volume for the TRP, and the traffic volume/communication volume for the SSB.

For example, specific events related to the conditions/triggers for a specific event may be predefined in the specifications or may depend on the network implementation.

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

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

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

Restrictions on changing/updating the second cell may be specified. The NW may decide not to change/update the second cell in certain cases.

FIG. 10 is a diagram showing an example of a change in the configuration of a second cell. The example shown in FIG. 10 shows 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).

<<Definition of the second cell>>
An example of the configuration/definition of the second cell will be described below.

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

[Option 0.1]
The second cell may be constituted by one cell (the first cell)/PCI.

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.

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

This option may address scenario 1 above.

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

[[[Option 0.1.1.1]]]
The second cell may be configured with one synchronization signal (e.g., SSB and/or SS/PBCH block) for one cell. In other words, one second cell may correspond to one synchronization signal. Such a configuration corresponds, for example, to the 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.

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

[[[Option 0.1.1.3]]]
The 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 the second cell according to Pattern B in at least one of Options 1.1 and 1.2 above.

[[Option 0.1.2]]
The second cell may be configured by multiple TRPs for one cell (e.g., a portion of the TRP for one cell). In other words, one second cell may correspond to multiple TRPs (a portion of the TRP for one cell).

[[[Option 0.1.2.1]]]
The second cell may be configured with multiple synchronization signals (e.g., parts of the synchronization signal) for one cell. In other words, one second cell may correspond to multiple synchronization signals (parts of the synchronization signal for one cell). Such a configuration corresponds, for example, to the 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.

[[Option 0.1.3]]
A second cell may be configured by 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).

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

[[[Option 0.1.3.2]]]
The second cell may be configured by multiple synchronization signals (e.g., parts of a synchronization signal) for one cell. In other words, one second cell may correspond to multiple synchronization signals (parts of a synchronization signal for one cell). Such a configuration corresponds, for example, to the second cell according to the pattern B in at least one of the above options 1.1 and 1.2, and to the second cell according to the pattern C in at least one of the above options 3/5.1 and 3/5.2.

[[[Option 0.1.3.3]]]
The 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 the second cell according to the pattern B in at least one of the above options 1.1 and 1.2, and the second cell according to the pattern C in at least one of the above options 2/4.1, 2/4.2, 3/5.1, and 3/5.2.

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

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

This option may address scenario 2 above.

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

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

[[[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 to, for example, the second cell according to the pattern D/E in at least one of the above options 1.1, 1.2, 2/4.1, 2/4.2, 3/5.1 and 3/5.2.

Each of the above options may be selected/determined based on the above-mentioned conditions/triggers (e.g., conditions/triggers based on time/number of UEs/traffic, etc.).

Changes/updates to each of the above options may be set/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.

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.

The second cell may be identified by a specific ID.

The particular ID may have a fixed value.

The specific ID may also 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 conjunction with the change in the ID.

　Common/dedicated settings/parameters for multiple second cells may be notified to the UE. The settings/parameters may be notified, for example, using higher layer (RRC) parameters.

The settings/parameters may be, for example, settings/parameters related to PCI/TRP/SSB.

The second cell may be used for a particular purpose/property. In other words, the second cell may be defined/configured/identified with a particular purpose/property.

The specific purpose may be, for example, at least one of the following: control plane, user plane, paging, measurement, reporting, measurement reporting, beam instruction/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.

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

The number of PCIs/TRPs/SSBs (e.g., maximum number) in one second cell may be predefined in the specifications, may be configured/instructed/notified to the 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.

The second cells may be arranged (physically/spatially) contiguous. Also, the second cells may be arranged (physically/spatially) discontinuous to one another.

Sharing Between Second Cells
[Option 0.3.1]
A synchronization signal (e.g., SSB and/or SS/PBCH block) may be shared among multiple second cells. The UE may assume that it can receive the same (shared/common) synchronization signal in different multiple second cells.

In this case, the information contained in the synchronization signal may be configurable as information specific to the second cell.

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

In option 0.3.1, at least one of the following may be used between 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.

FIG. 11A is a diagram showing an example of an area related 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. The area where area #1 and area #2 overlap has the same SSB coverage. In other words, in the overlapping area, area #1 and area #2 can share the same SSB/TRP/PCI.

Allowing a configuration like option 0.3.1 allows for the most flexible configuration of the second cell.

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

In this case, the information contained in the synchronization signal may be configurable 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.

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

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

FIG. 11B is a diagram showing an example of an area related 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.

In a configuration such as option 0.3.2, the maximum number of second cells in a first cell may be the number of synchronization signals (SSB/SSB coverage). Also, if the second cell spans multiple SSB coverages, the maximum number of second cells in a first cell may be the number of SSBs (SSB groups) spanned.

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

In this case, the information included in the synchronization signal may be configurable 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 (ID for identifying the TRP).

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

In option 0.3.3, the same PCI may be used between multiple second cells.

FIG. 11C is a diagram showing an example of an area related 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 do not share the same SSB, do not share the same TRP, and can share the same PCI.

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 cell spans multiple TRPs, the maximum number of second cells in a first cell may be the number of spanned TRPs (TRP groups).

[Option 0.3.4]
The synchronization signal, TRP and PCI may not be shared among the second cells. The UE may assume that the UE 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 the different second cells.

In this case, the information included in the synchronization signal may be configurable 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 (ID for identifying the TRP). Also, in this case, the second cell may be identified using a PCI.

In a configuration such as option 0.3.4, the maximum number of second cells in a first cell may be one. Also, if a second cell spans multiple first cells, the total maximum number of second cells may be the number of spanned first cells/PCI (PCI group).

Each of the above options may be selected/determined based on the above-mentioned conditions/triggers (e.g., conditions/triggers based on time/number of UEs/traffic, etc.).

Changes/updates to each of the above options may be set/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.

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.

The IDs in each of the above options (e.g., at least one of the ID for the synchronization signal, the ID for the TRP, and the PCI) may be global IDs (e.g., common to all networks) or local IDs (e.g., unique to a portion of networks).

The number (e.g., 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 the specifications, may be set/instructed/notified to the 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.

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

In addition, in this disclosure, source/serving (e.g., source area/serving) may refer to the (current) target (e.g., area) before handover. Also, in this disclosure, target (e.g., target area) may refer to the target (e.g., area) of the handover destination.

FIG. 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.

The example shown in FIG. 12 shows a pattern 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).

In the example shown in FIG. 12, pattern F is a mobility scenario where 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.

In addition, in Pattern F, it is assumed that the beam management operations of the existing system (defined by 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.

In the example shown in FIG. 12, pattern G is a mobility scenario where 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.

In addition, in pattern G, it is assumed that the beam management operations of the existing system (defined by 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.

In the example shown in FIG. 12, pattern H is a mobility scenario where 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.

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

In the example shown in FIG. 12, pattern I is a mobility scenario where 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.

In addition, in pattern I, it is assumed that an intra-CU handover operation and an operation 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.

In the example shown in FIG. 12, pattern J is a mobility scenario where 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.

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

In the example shown in FIG. 12, pattern K is a mobility scenario where 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.

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 changing the second cell is used in the case of mobility between second cells (i.e., when the source area and target area are different).

In the example shown in FIG. 12, pattern L is a mobility scenario where 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.

In addition, in pattern L, handover is performed within a CU, and the same TRP is shared by different CUs/PCIs. Also, in pattern L, it is assumed that operations related to changing the second cell are used in the case of mobility between second cells (i.e., when the source area and target area are different).

In the example shown in FIG. 12, pattern M is a mobility scenario where 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.

In addition, in pattern M, it is assumed that an intra-CU handover operation and an operation 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.

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 and settings of the network (NW, e.g., base station)/UE for these scenarios.

Specifically, there has been insufficient consideration given to the settings related to the second cell (RRC settings) and the methods related to indicating/detecting movement between the second cells.

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.

In particular, when performing cell-free communication, the signal strength from each TRP/antenna is likely to be uniform at the boundary between the second cells, so there is a possibility that the boundary may be affected by complex interference, making it difficult to determine handover operation based solely on the signal reception quality.

For example, in a cellular system such as that shown in FIG. 2A, the quality of the signal from the source cell is reduced 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 FIG. 2B, an area is constructed using multiple antennas/TRPs, so the communication quality within the area is uniform, and at the boundary between the second cells, the signal strength can change significantly, making it difficult to determine the handover operation.

As a way to deal with this problem, the introduction of handover operations based on UE location information is being considered, but the study has not been sufficient.

If these considerations are not sufficient, appropriate communication using dynamically/semi-statically changing cells/areas may not be possible, which may hinder improvements in communication throughput.

The inventors therefore came up with a method to solve the above problem.

Embodiments of the present disclosure will now be described in detail with reference to the drawings. The wireless communication methods according to the embodiments may be applied independently or in combination.

In this disclosure, "A/B" and "at least one of A and B" may be interpreted as interchangeable. Also, in this disclosure, "A/B/C" may mean "at least one of A, B, and C."

In this disclosure, terms such as notify, activate, deactivate, indicate, select, configure, update, and determine may be read as interchangeable terms. In this disclosure, terms such as support, control, capable of control, operate, and capable of operating may be read as interchangeable terms.

In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher layer parameters, fields, information elements (IEs), settings, etc. may be interchangeable. In this disclosure, Medium Access Control (MAC Control Element (CE)), update commands, activation/deactivation commands, etc. may be interchangeable.

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 protocols (e.g., NR Positioning Protocol A (NRPPa)/LTE Positioning Protocol (LPP)) messages), or a combination of these.

In the present disclosure, the MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. The 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.

In the present disclosure, the physical layer signaling may be, for example, Downlink Control Information (DCI), Uplink Control Information (UCI), etc.

In this disclosure, synchronization signal, SSB, SS/PBCH block, etc. may be interpreted as interchangeable.

(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.

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

Note that each embodiment of the present disclosure can be applied without being limited to a cell-free configuration. In other words, each embodiment of the present disclosure can be applied even in cases where a cell-free configuration is not adopted.

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

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

The UE/NW may also switch between modes corresponding to the following embodiments 0-1/0-2 based on specific settings/parameters/instructions.

<<Embodiment 0-1>>
For the second cell, one PCI may correspond.

This embodiment may correspond to Assumption 1 above.

Multiple TRPs/SSBs may correspond to one PCI.

By using a configuration like that of embodiment 0-1, more flexible communication becomes possible.

[Option 0-1-1]
A second cell may be configured for the UE.

This configuration may be performed, for example, using higher layer signaling (e.g., RRC signaling).

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

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

This configuration may be performed, for example, using higher layer signaling (e.g., RRC signaling).

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

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

In embodiment 0-1, the configuration regarding the second cell (e.g., CellFree-AreaConfig) may be notified to the UE.

The configuration for the second cell may include at least one of the following information:
An ID for identifying the second cell.
-Serving cell index.
・PCI.
- (A list of) indices for the TRPs that constitute the second cell.
(A list of) indices of reference signals (eg, SSBs) that constitute the second cell.

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.

The TRP constituting the second cell may be associated with the reference signal. For example, a list of indexes for the reference signal may be set in a list of indexes for the TRP.

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

This embodiment may correspond to assumption 2 above.

Multiple TRPs/SSBs may correspond to one PCI.

By using a configuration like that of embodiment 0-2, it is possible to reduce the number of PCI/SSBs corresponding to one PCI.

[Option 0-2-1]
A second cell may be configured for the UE.

This configuration may be performed, for example, using higher layer signaling (e.g., RRC signaling).

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

This configuration may be performed, for example, using higher layer signaling (e.g., RRC signaling).

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

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

In embodiment 0-2, the configuration regarding the second cell (e.g., CellFree-AreaConfig) may be notified to the UE.

The configuration for the second cell may include at least one of the following information:
An ID for identifying the second cell.
-Serving cell index.
・PCI.
- (A list of) indices for the TRPs that constitute the second cell.
(A list of) indices of reference signals (eg, SSBs) that constitute the second cell.

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.

The PCI corresponding to the second cell may be associated with the TRP constituting the second cell. For example, an index (list) relating to the TRP may be set in the PCI (list) corresponding to the second cell.

The TRP constituting the second cell may be associated with the reference signal. For example, a list of indexes for the reference signal may be set in a list of indexes for the TRP.

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

First Embodiment
The first embodiment relates to the movement/handover of the UE between the second cells.

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).

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

The particular RRC parameter may be, for example, an RRC reconfiguration.

[Option 1-1-1]
For example, if the particular RRC parameter includes a configuration for the second cell (e.g., CellFree-AreaConfig), the UE may determine to perform a change/handover for the second cell.

This option may also be applied, for example, to options 0-1-1/0-2-1 above.

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

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

For example, if the particular RRC parameter includes an ID for identifying the second cell, the UE may determine to perform a change/handover to the second cell based on (in accordance with) the ID.

This option may also be applied, for example, to option 0-2-3 above.

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

The UE may also receive an RRC parameter indicating whether or not to perform a change/handover to the second cell. The UE may determine whether or not to perform a change/handover to the second cell based on the RRC parameter.

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 to 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 to the second cell.

The RRC parameters may be included in the specific RRC parameters along with an ID for identifying the second cell.

In this option, for example, if the UE determines not to perform a change/handover to the second cell, the UE may determine to perform a change/handover to the (existing) first cell.

[Option 1-1-3]
For example, 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).

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.

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.

For example, if the particular RRC parameter includes an ID for identifying the second cell, the UE may determine to perform a change/handover to the second cell based on (in accordance with) the ID.

This option may also be applied, for example, to options 0-1-3/0-2-3 above.

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

The UE may also receive an RRC parameter indicating whether or not to perform a change/handover to the second cell. The UE may determine whether or not to perform a change/handover to the second cell based on the RRC parameter.

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 to 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 to the second cell.

The RRC parameters may be included in the specific RRC parameters along with an ID for identifying the second cell.

In this option, for example, if the UE determines not to perform a change/handover to the second cell, the UE may determine to perform a change/handover to the (existing) first cell.

FIGS. 13A to 13C are diagrams showing an example of RRC parameter settings related to embodiment 1-1.

In FIG. 13A, the RRC reconfiguration includes a configuration for the second cell (CellFree-AreaConfig), the 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.

In FIG. 13A, the RRC reconfiguration includes a configuration for the second cell (CellFree-AreaConfig) in response to the above option 1-1-1, and the RRC reconfiguration includes the 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 in response to the above option 1-1-1.

FIG. 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 or not to perform a change/handover regarding the second cell.

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 related to the second cell corresponding to the above option 1-1-3.

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

In FIG. 13C, the RRC reconfiguration includes a serving cell configuration (ServingCellConfig) in response 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 in response to the above option 1-1-3.

According to embodiment 1-1 above, it is possible to appropriately trigger a change/handover regarding the second cell by using the settings by RRC.

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

The MAC CE may be, for example, a new MAC CE (defined in Rel. 20 or later), or an extended MAC CE for L1L2-triggered mobility (LTM) defined in Rel. 18.

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

The UE may decide to perform a change/handover to the second cell based on (in accordance with) this field.

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

This option may also be applied, for example, to options 0-1-2/0-2-2 above.

The ID of the second cell that can be indicated by the MAC CE may be the IDs of multiple (e.g., all) second cells that are set in advance using RRC signaling, or may be the ID 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 received in advance.

Figure 14 shows an example of an instruction by a MAC CE related to option 1-2-1. In Figure 14, a MAC CE that is an extension of the MAC CE for LTM is described.

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 shows a case where three area candidates are set for the UE, and an example where the area ID field is two bits is shown. The area ID field may be determined based on the number of area candidates set for the UE.

The UE may determine whether to change areas 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 change areas, and if the field indicates "01", "10", or "11", the UE may determine to change areas to "Area #1", "Area #2", or "Area #3", respectively.

Note that in the diagrams relating to MAC CE in this disclosure, the field names, bit numbers, and field positions are merely examples and are not limited to the examples shown.

In this option, for example, if the UE determines not to perform a change/handover to the second cell, the UE may determine to perform a change/handover to the (existing) first cell.

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

For example, if the field indicates a first value (e.g., 0 (or 1)), the UE may determine not to perform a change/handover to 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 to the second cell based on the target configuration ID.

The target configuration identified by the target configuration ID may include an ID for identifying the second cell. The UE may perform a change/handover regarding the second cell based on the ID for identifying the second cell.

Figure 15 shows an example of an instruction by a MAC CE related to option 1-2-2. In Figure 15, a MAC CE that is an extension of the MAC CE for LTM is described.

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.

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 the area corresponding to the target setting ID.

In this option, for example, if the UE determines not to perform a change/handover to the second cell, the UE may determine to perform a change/handover to the (existing) first cell.

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

The UE may determine whether or not to perform a change/handover to the second cell based on the target configuration identified by the target ID.

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

Figure 16 shows an example of an instruction by a MAC CE related to option 1-2-3. In Figure 16, a MAC CE that is an extension of the MAC CE for LTM is described.

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 the ID of the second cell (area ID).

The UE may determine whether to change areas according to the settings of the LTM candidate associated with the target setting ID based on the value of the target setting ID included in the MAC CE as shown in FIG. 16.

In this option, for example, if the UE determines not to perform a change/handover to the second cell, the UE may determine to perform a change/handover to the (existing) first cell.

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

The UE may also be notified of at least one of the following using the MAC CE: 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.

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.

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 for a TCI state (joint/UL/DL TCI state), an RRC configuration for a TA value, and an RRC configuration for a random access (CFRA) resource. At least one of an RRC configuration for a TCI state (joint/UL/DL TCI state), an RRC configuration for a TA value, and an RRC configuration for a random access (CFRA) resource may include an ID of the second cell.

The UE may also receive an RRC parameter indicating whether or not to perform a change/handover to the second cell. The UE may determine whether or not to perform a change/handover to the second cell based on the RRC parameter.

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 to 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 to the second cell.

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

Figure 17 shows an example of an instruction by a MAC CE related to option 1-2-4. In Figure 17, a MAC CE that is an extension of the MAC CE for LTM is described.

The MAC CE shown in FIG. 17 includes at least a target configuration ID field (Target Config ID) and a TCI state ID field (TCI state ID)/UL TCI state ID field (UL TCI state ID). 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.

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

The UE may determine whether to change areas according to the TCI state in the LTM candidate configuration 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.

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).

In this option, for example, if the UE determines not to perform a change/handover to the second cell, the UE may determine to perform a change/handover to the (existing) first cell.

According to the above embodiment 1-2, it is possible to appropriately trigger a change/handover regarding the second cell by using the settings by the RRC and the instructions by the MAC CE.

<<Embodiment 1-3>>
The UE may configure/indicate/trigger a change/handover to the second cell using a specific MAC CE and/or a specific DCI.

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.

The UE may activate/deactivate the TCI state using at least one of the specific MAC CE and the specific DCI. The UE may be instructed on the TCI state using at least one of the specific MAC CE and the specific DCI.

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

The UE may make a change/handover to the second cell based on the value of the ID field.

The ID of the second cell that can be indicated by the MAC CE may be the IDs of multiple (e.g., all) second cells that are set in advance using RRC signaling, or may be the ID 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 received in advance.

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

FIG. 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.

In this option, for example, if the UE determines not to perform a change/handover to the second cell, the UE may determine to perform a change/handover to the (existing) first cell.

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

For example, if the field indicates a first value (e.g., 0 (or 1)), the UE may determine not to perform a change/handover to 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 to the second cell.

The indicated TCI state may be associated with a second cell. 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 a field indicating whether to perform a change/handover to the second cell.

Figure 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 Figure 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.

In this option, for example, if the UE determines not to perform a change/handover to the second cell, the UE may determine to perform a change/handover to the (existing) first cell.

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

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 current ID of the second cell (serving area ID).

The RRC parameters related to the TCI state for the serving cell/area may include the ID of the second cell.

The UE may also receive an RRC parameter indicating whether or not to perform a change/handover to the second cell. The UE may determine whether or not to perform a change/handover to the second cell based on the RRC parameter.

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 to 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 to the second cell.

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

FIG. 18C is a diagram showing an example of an indication field related to option 1-3-3. The UE may determine whether to change areas based on the value of an indication field included in a specific MAC CE/DCI, as shown in FIG. 18C.

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

In this option, for example, if the UE determines not to perform a change/handover to the second cell, the UE may determine to perform a change/handover to the (existing) first cell.

According to the above embodiments 1 to 3, it is possible to appropriately trigger a change/handover regarding the second cell by utilizing the instructions from the MAC CE/DCI.

According to the first embodiment described above, it is possible to appropriately perform changes/handovers regarding the second cell based on notifications from the network.

Second Embodiment
The second embodiment relates to the movement/handover of the UE between the second cells.

The UE may decide whether or not to perform a change/handover to the second cell based on certain conditions.

<<Embodiment 2-1>>
The UE may be configured with the specific conditions using specific RRC parameters.

The particular RRC parameter may be, for example, an RRC reconfiguration.

The UE may use the specific RRC parameters to configure an event for triggering a change/handover to the second cell. The UE may determine whether or not to perform a change/handover to the second cell based on the configured event.

The UE may also determine whether to perform a change/handover to the second cell based on an event that triggers a change/handover to the second cell, which is predefined in the specifications.

The event may be, for example, a common event for multiple (e.g., all) UEs/second cells. Also, the event may be, for example, a specific event for each UE/second cell.

[Option 2-1-1]
For example, if an event for triggering a change/handover to the second cell is met and the particular RRC parameter includes a configuration for the second cell (e.g., CellFree-AreaConfig), the UE may decide to perform a change/handover to the second cell.

This option may also be applied, for example, to options 0-1-1/0-2-1 above.

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

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

The arbitrary parameter included in the specific RRC parameter 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 report configuration (e.g., CSI report Config), and a CSI resource configuration (e.g., CSI resource Config).

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 determine to perform a change/handover to the second cell based on (in accordance with) the ID.

This option may also be applied, for example, to option 0-2-3 above.

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

The UE may also receive an RRC parameter indicating whether or not to perform a change/handover to the second cell. The UE may determine whether or not to perform a change/handover to the second cell based on the RRC parameter.

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 to 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 to the second cell.

The RRC parameters may be included in the specific RRC parameters along with an ID for identifying the second cell.

In this option, for example, if the UE determines not to perform a change/handover to the second cell, the UE may determine to perform a change/handover to the (existing) first cell.

Figures 19A to 19F show an example of RRC parameter settings related to option 2-1-2.

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

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

In the example shown in FIG. 19C, the parameter (condExecutionCond) related to the execution condition of the 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 or not to perform a change/handover related to the second cell.

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

In the example shown in FIG. 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.

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

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

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

The specific RRC parameters may be included in a conditional RRC reconfiguration (e.g., CondRRCReconfig).

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.

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.

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 determine to perform a change/handover to the second cell based on (in accordance with) the ID.

This option may also be applied, for example, to options 0-1-3/0-2-3 above.

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

The UE may also receive an RRC parameter indicating whether or not to perform a change/handover to the second cell. The UE may determine whether or not to perform a change/handover to the second cell based on the RRC parameter.

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 to 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 to the second cell.

The RRC parameters may be included in the specific RRC parameters along with an ID for identifying the second cell.

In this option, for example, if the UE determines not to perform a change/handover to the second cell, the UE may determine to perform a change/handover to the (existing) first cell.

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, (Rel. 19) settings/parameters related to conditional LTM, settings/parameters related to L3 UE triggered measurement reporting, and (Rel. 16) settings/parameters related to conditional handover.

According to embodiment 2-1 described above, it is possible to appropriately determine whether to change/handover the second cell by using the settings by RRC.

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

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 in the L1/L3 UE triggered beam report, or a MAC CE that is an extension of the MAC CE for LTM (Rel. 19).

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

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

This option may also be applied, for example, to options 0-1-2/0-2-2 above.

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 (e.g., a MAC CE for activation of the TCI state) that is received in advance.

FIG. 20A is a diagram showing an example of an instruction by a MAC CE related to option 2-2-1. FIG. 20A shows a MAC CE that is an extension of the MAC CE for LTM.

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).

The UE may use the value of the area ID field included in the MAC CE as shown in FIG. 20A to report that an area change will be made to the area corresponding to that field.

Figure 20B is a diagram showing another example of an instruction by a MAC CE relating to option 2-2-1. Figure 20B shows a MAC CE that is an extension of the MAC CE for beam reporting.

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

The UE may use the value of the area ID field included in the MAC CE as shown in FIG. 20B to report that an area change will be made to the area corresponding to the field.

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.

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

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, for example, 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.

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

FIG. 21A is a diagram showing an example of an instruction by a MAC CE related to option 2-2-2. FIG. 21A shows a MAC CE that is an extension of the MAC CE for LTM.

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.

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 setting ID to report whether to perform an area change to the area corresponding to the target setting ID.

Figure 21B is a diagram showing another example of an instruction by a MAC CE relating to option 2-2-2. Figure 21B shows a MAC CE that is an extension of the MAC CE for beam reporting.

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

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., the RS ID corresponding to the best reception quality) reference signal included in the MAC CE.

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.

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

The UE may report whether or not to perform a change/handover to the second cell based on at least one of the target configuration identified by the target ID and the PCI.

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

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

FIG. 22A is a diagram showing an example of an instruction by a MAC CE relating to option 2-2-3. FIG. 22A shows a MAC CE that is an extension of the MAC CE for LTM.

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

The UE may report whether to change areas 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.

Figure 22B is a diagram showing another example of an instruction by a MAC CE relating to option 2-2-3. Figure 22B shows a MAC CE that is an extension of the MAC CE for beam reporting.

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

The UE may use the value of the PCI field (e.g., PCI1) included in the MAC CE as shown in FIG. 22B to report whether to perform an area change to the area associated with that PCI.

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.

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

The UE may also use the MAC CE to report at least one of the following: TCI state (joint/UL/DL TCI state) ID, Timing Advance (TA) value, Random Access (CFRA) resource/SSB index/Random Access Preamble index, RS index, and PCI.

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

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

The ID of the second cell may also be included in the CSI reporting configuration/CSI resource configuration associated with the reported PCI/RS index.

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.

The UE may also transmit an RRC parameter indicating whether or not to perform a change/handover to the second cell. The NW may determine whether or not the UE will perform a change/handover to the second cell based on the RRC parameter.

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 to 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 to the second cell.

FIG. 23A is a diagram showing an example of an instruction by a MAC CE relating to option 2-2-4. FIG. 23A shows a MAC CE that is an extension of the MAC CE for LTM.

The MAC CE shown in FIG. 23A includes at least a target configuration ID field (Target Config ID) and a TCI state ID field (TCI state ID)/UL TCI state ID field (UL TCI state ID). 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 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.

Figure 23B is a diagram showing another example of an instruction by a MAC CE relating to option 2-2-4. Figure 23B shows a MAC CE that is an extension of the MAC CE for beam reporting.

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

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

In this option, for example, if the UE determines not to perform a change/handover to the second cell, the UE may determine to perform a change/handover to the (existing) first cell.

Note that in at least one of the above options 2-2-1 to 2-2-4, if CSI for multiple PCIs is reported, the UE may report the area change using a specific PCI/RS ID.

The particular 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 that corresponds to the quality reported using an absolute value (e.g., a particular number of bits (e.g., 7 bits)).

In addition, in at least one of the above options 2-2-1 to 2-2-4, if CSI for 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.

According to embodiment 2-2 above, the MAC CE can be used to appropriately report changes/handovers related to the second cell.

<<Embodiment 2-3>>
The UE may use the specific UCI to report a change/handover to the second cell and/or to perform a beam report.

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

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 to the second cell.

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 received in advance.

FIG. 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 the area change will not be performed, and if the field indicates "01", "10", or "11", the UE may report that the area change will be performed to "Area #1", "Area #2", or "Area #3", respectively.

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.

[Option 2-3-2]
The particular UCI may include a field indicating whether or not a change/handover to the second cell is to be performed.

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

The UE may report the cell ID (PCI)/RS ID to the NW. The ID of the second cell may be associated with the RRC parameters associated with the cell ID (PCI)/RS ID.

The NW may determine the second cell to which the UE should change/handover based on the ID of the second cell associated with the reported cell ID/RS ID.

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.

FIG. 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 the 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 will not perform an area change, and when the field indicates "1", it may mean that the UE will perform an area change to the corresponding area.

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.

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

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

The UE may report a PCI/RS ID using a specific UCI and report a change/handover to a second cell associated with that PCI/RS ID.

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

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

The UE may also transmit an RRC parameter indicating whether or not to perform a change/handover to the second cell. The UE may use the RRC parameter to report whether or not to perform a change/handover to the second cell.

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 to 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 to the second cell.

FIG. 24C is a diagram showing an example of an indication field related to option 2-3-3. The UE may report whether to perform an area change using the value of an indication field included in a specific UCI, as shown in FIG. 24C.

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

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.

According to the above embodiment 2-3, the change/handover regarding the second cell can be appropriately reported using the instruction from the UCI.

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

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

Third Embodiment
A third embodiment relates to a MAC CE for configuring/activating/deactivating a second cell.

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

The UE/NW may also switch between modes corresponding to the following embodiments 3-1/3-2 based on specific settings/parameters/instructions.

<<Embodiment 3-1>>
The second cell may be composed of a cell (first cell) group, a cell (first cell), a TRP, and an SSB.

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

[Option 3-1-1]
The UE may be indicated the cell groups/cells/TRPs/SSBs to be activated/deactivated using a bitmap format.

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

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)).

The number of bits/octets 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, based on at least one of the settings by RRC signaling and the reported UE capability information.

FIG. 25A is a diagram showing an example of a MAC CE related to option 3-1-1. The example shown in FIG. 25A shows a case where eight SSBs are configured for a UE. The UE may use a field (bitmap) of a MAC CE as shown in FIG. 25A to activate/deactivate the SSBs that make up an area.

Note that the number of SSBs shown in FIG. 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.

[Option 3-1-2]
The UE may be explicitly indicated one or more of the Cell Group ID/Cell ID/TRP ID/SSB ID.

The UE may activate the corresponding cell group/cell/TRP/SSB for the indicated cell group ID/cell ID/TRP ID/SSB ID (included in the MAC CE).

The UE may deactivate the corresponding cell group/cell/TRP/SSB for cell group IDs/cell IDs/TRP IDs/SSB IDs that are not indicated (not included in the MAC CE).

The UE may assume that no SSBs corresponding to the deactivated SSB IDs will be transmitted.

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, based on at least one of the following: settings by RRC signaling, reported UE capability information, and values predefined in the specifications.

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, based on at least one of the following: settings by RRC signaling, reported UE capability information, and values predefined in the specifications.

Figure 25B is a diagram showing an example of a MAC CE related 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 use a field in a MAC CE as shown in Figure 25B to activate/deactivate SSBs that make up an area.

Note that the MAC CE in the above options 3-1-1/3-1-2 may be interpreted as DCI.

When activating/deactivating a cell using a MAC CE/DCI, the MAC CE/DCI may include a cell group ID (or a bitmap relating to the cell group).

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

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).

<<Embodiment 3-2>>
The UE may receive a MAC CE that activates/deactivates the second cell.

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

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

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)).

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

FIG. 26A is a diagram showing an example of a MAC CE related to option 3-2-1. The example shown in FIG. 26A shows a case where eight areas are configured for a UE. The UE may use a field (bitmap) of a MAC CE as shown in FIG. 26A to activate/deactivate the area configuration.

Note that the number of second cells (areas) shown in FIG. 26A is merely an example. The number of second cells included in a MAC CE may be determined for each first cell.

[Option 3-2-2]
The UE may be explicitly indicated the identity of one or more second cells.

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

The UE may deactivate the corresponding second cell for any second cell ID that is not indicated (not included in the MAC CE).

The number of bits used in the MAC CE may be determined based on the number of second cells that can be configured for the UE, which is based on at least one of the following: settings by RRC signaling, reported UE capability information, and a value previously specified in the specifications.

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

FIG. 26B is a diagram showing an example of a MAC CE related to option 3-2-2. The example shown in FIG. 26B shows a case where N second cells (areas) are activated for a UE. The UE may activate/deactivate areas using the fields of the MAC CE shown in FIG. 26B.

Note that the MAC CE in the above options 3-2-1/3-2-2 may be interpreted as DCI.

According to the third embodiment described above, the second cell can be appropriately configured/activated/deactivated using the MAC CE (or DCI).

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

In this embodiment, we will explain the operation related to changing the second cell of a UE in each pattern (pattern F-M) of the mobility scenario in Figure 12 above.

The UE may perform at least one of the following actions in each pattern (Pattern F-M):
- Change to the RRC settings of the second cell to which the change is made.
Beam (e.g. TCI state ID/RS index) switching.

The UE may receive an RRC reconfiguration when changing the RRC configuration. The UE may also apply the new RRC configuration that the UE previously retains/acquired.

The new RRC settings may have the same configuration as the RRC settings before the change, or may be configured with information indicating the difference from the RRC settings before the change.

When switching beams, the UE may switch to a beam instructed by the NW, or the UE may select/decide the beam to switch to and report the selected/decided beam to the NW.

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.

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

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 measurements, etc.). The UE may assume that the same TA as in the serving area is used or may use the indicated TA/TAG.

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

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 measurements, etc.). The UE may assume that the same TA as in the serving area is used, or may use the indicated TA/TAG.

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

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 measurements, etc.). The UE may assume that the same TA as in the serving area is used, or may use the indicated TA/TAG.

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

As mentioned above, the UE behavior for each pattern may be predefined in the specifications.

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

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

For example, if the particular 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 particular 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.).

Also, 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.

Furthermore, 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 in each pattern (e.g., random access procedure/UE-based TA measurement, etc.).

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

Note that, although this embodiment describes UE operations associated with UE movement between second cells, this embodiment may also be applied to UE operations associated with UE movement within the second cell.

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

Fifth embodiment
The fifth embodiment relates to a second cell change/handover operation based on the UE's location information.

The UE may be triggered to change/handover to the second cell from the network (e.g., the base station of the source cell/area). In this case, the first embodiment described above is applicable.

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

For example, the network (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 the second cell based on the location information (see FIG. 27).

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.

Also, for example, the UE may measure/obtain its own location information, and when a certain condition is met, at least one of requesting a change/handover to the second cell and reporting the location information. Then, the NW (e.g., a base station of the source cell/area) may trigger a change/handover to the second cell for the UE based on the location information (see FIG. 28).

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.

The UE may also decide to change/handover to the second cell without any explicit instruction from the network. In this case, the second embodiment described above is applicable.

For example, the UE may measure/obtain its own location information and determine to change/handover to the second cell when certain conditions are met. The UE may then transmit a notification (handover trigger notification) to the NW (e.g., the base station of the source cell/area) to change/handover to the second cell (see FIG. 29).

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

Note that the timeline for handover operations shown in Figures 27 to 29 is merely an example, and is 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.

　Specific location-based operations are explained below.

The UE/NW may use the location information based on the reference point to change/handover to the second cell.

<Handover trigger timing>
[Option 5-1-1]
The NW may trigger a handover using a specific signal based on the UE's location information reported by the UE or measured by the NW.

The particular signal may be, for example, RRC signaling/MAC CE/DCI.

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

The explicit information may be, for example, a cell/area identifying ID/TCI status ID/BWP ID for the target cell/area.

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

The implicit information may be, for example, a TCI state ID/RS ID that is predefined/set, a TCI state ID/RS ID associated with a cell/area different from the serving cell/area, or information regarding a random access channel for a cell/area different from the serving cell/area.

The UE may receive signals containing the explicit/implicit information from the target cell/source cell/target area/serving area/other areas.

The other area may be, for example, an area where only specific signals (e.g., at least one of a signal related to handover and a control signal) are transmitted.

[Option 5-1-2]
The UE may use its location information and the configured/defined reference points to measure the distance between the UE and the reference points.

The UE may then trigger a handover based on certain conditions (e.g., when certain conditions are met).

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

In addition, in the present disclosure, the reference point/origin/UE position may be indicated in a Cartesian coordinate system or a polar coordinate system. Also, in the present disclosure, the reference point/origin/UE position may be indicated in a global coordinate system (GCS) or a local coordinate system (LCS). Information regarding conversion from GCS to LCS may be set/instructed to the UE.

The coordinates of the reference point/origin and at least one of the specific conditions may be predefined in the specifications, may be set/instructed/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.

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.

The coordinates of the reference point/origin and at least one of the specific conditions may be set/indicated/determined per BWP/CC/cell/cell group/area/UE.

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

In the present disclosure, the specific conditions may include at least one of the following: 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.

The following describes the UE's location information and specific conditions. The UE's location information and specific conditions 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.

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

For example, if the particular condition is distance (which may be a positive value (e.g., 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.

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).

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

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

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

In this case, handover may be triggered if the UE's location coordinates are larger/smaller than any of the components of a particular coordinate (x component, y component, z component).

In this case, the value of each component of a particular coordinate may be set to either positive or negative.

When each coordinate is expressed in a Cartesian coordinate system, if the coordinates of reference point #n (n may be a natural number) are ( _xn , _yn , _zn ) and the coordinates of the UE are (x', y', z'), the distance _ln from reference point #n to the UE may be expressed as {(xn _- x') ²⁺ ( _yn -y') ²⁺ ( _zn - _z ') ² } ^1/2 . Whether or not to perform handover may be determined by comparing _ln with a condition _Ln (and Ln') for each reference point #n.

Fig. 30 is a diagram showing an example of a UE location according to option 5-1-2-1. In the example shown in Fig. 30, a handover for a second cell is determined based on one reference point (reference point #1), a threshold distance (L ₁ ) from the reference point, and the UE location (distance l ₁ from the reference point).

[Option 5-1-2-2]
One specific condition (eg, a threshold/larger/smaller relationship regarding distance/coordinate) and multiple reference points may be set.

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

For each reference point, triggers for different UE actions (e.g., at least one of handover actions, event-related decisions, signal quality measurements, and starting/stopping certain timers) may be configured.

Fig. 31 is a diagram showing an example of a UE location according to option 5-1-2-2. In the example shown in Fig. 31, a handover for a second cell is determined based on a number of reference points (reference points # ₁ and #2), distance thresholds from the respective reference points (L1 and _L2 , where _L1 = _L2 ), and the UE location (distance _l1 from reference point #1 and distance l2 from reference point # ₂ ).

[Option 5-1-2-3]
A number of specific conditions (eg, thresholds/larger/smaller relationships regarding distance/coordinates) and one reference point may be set.

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

For each condition, a trigger for a different UE action (e.g., at least one of a handover action, an event-related decision, a signal quality measurement, and starting/stopping a specific timer) may be configured.

Fig. 32 is a diagram showing an example of a UE location according to option 5-1-2-3. In the example shown in Fig. 32, a handover for a second cell is determined based on one reference point (reference point #1), threshold distances from the reference point ( _L1 and _L1 '), and the UE location (distance l1 from reference point # ₁ ).

[Option 5-1-2-4]
A number of specific conditions (eg, distance/coordinate thresholds/magnitude relationships) and a number of reference points may be set.

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

For each condition for each reference point, a trigger for a different UE action (e.g., at least one of a handover action, an event-related decision, a signal quality measurement, and starting/stopping a specific timer) may be configured.

Fig. 33 is a diagram showing an example of a UE location according to option 5-1-2-4. In the example shown in Fig. 33, a handover for a second cell is determined based on multiple reference points (reference point #1), distance thresholds from each reference point (L ₁ and L ₁ ' for reference point 1, and L ₂ for reference point #2), and the UE location (distance l ₁ from reference point #1 and distance l 2 from reference point # ₂ ).

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, requesting a handover to the NW, an event-related measurement, a signal quality measurement, and starting/stopping a specific timer.

In this embodiment, information/conditions regarding an event may be set to the UE from the network, or the event may be specified in advance.

<<Type of origin/reference point>>
The type of origin/reference point 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 reported UE capability information, or may be determined based on a combination of these.

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

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

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

The origin/reference point may also be defined/set as a position calculated using a specific method.

For example, the origin/reference point may be at least one of the following: a position/coordinate of a cell edge/area edge, a position/coordinate 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.

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

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

The origin/reference point may be set/defined commonly for Non-Terrestrial Networks (NTN) and Terrestrial Networks (TN), or may be set/defined separately.

<Notification of the trigger to the network>
The UE may use a specific UL signal to send a notification (handover trigger notification) to the NW about triggering a handover.

The particular UL signal may be, for example, PUCCH/PUSCH/PRACH/SRS/other signal.

For example, the UE may send a handover trigger notification to the NW using a scheduling request (SR). In this case, the UE may use an SR setting/SR resource dedicated to the notification. If an SR setting/SR resource dedicated to the notification is not configured for the UE, the UE may use a normal (not dedicated to the notification) SR setting/SR resource.

For example, the UE may use a MAC CE to send a handover trigger notification to the NW. In this case, if there is an UL grant (e.g., free resources on a PUSCH), the UE may send the MAC CE on the PUSCH, and if not, may send an SR to request an UL grant.

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

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 than the serving cell/area).

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

UE Operation After Handover Trigger
The UE may perform at least one of the following actions after triggering the handover:
- Transmit PRACH to the target cell/area.
- Monitor the PDCCH in the target cell/area.
Stop sending and receiving signals to the source cell/area.
-Perform RRC reconfiguration.

The UE may not transmit a PRACH to the target cell/area in certain cases (i.e., the UE may not perform a random access procedure). The certain cases may be at least one of the following: the UE already holds/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 related to the handover trigger.

<<How to measure location information>>
The UE's location information may be measured/determined based on at least one of the time/phase (e.g., time/phase shift) of the PDCCH/PDSCH/reference signal (e.g., SSB/CSI-RS/TRS) transmitted from the NW, the PUCCH/PUSCH/reference signal (e.g., SRS) transmitted from the UE, and the TA.

The location information of the UE may also 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.

　The UE's location information may also be determined based on (existing) positioning/sensing information.

The UE's location information may be measured by the UE and reported to the NW, or it may be measured by the NW.

The UE location information may be an actual measurement value or a predicted value. An AI/ML model on the UE/NW side may be used to measure/predict the UE location information.

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

According to the fifth embodiment, 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.

<Additional Information>
[Notification of information to UE]
In the above-described embodiment, any information may be notified to the UE (from a network (NW) (e.g., a base station (BS))) (in other words, any information is received 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.

When the above notification is performed by a MAC CE, the MAC CE may be identified by including in the MAC subheader a new Logical Channel ID (LCID) that is not specified in existing standards.

When the notification is made by a 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.

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

[Information notification 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.

If the notification is made by a MAC CE, the MAC CE may be identified by including a new LCID in the MAC subheader that is not specified in existing standards.

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

Furthermore, in the above-mentioned embodiments, notification of any information from the UE may be performed periodically, semi-persistently, or aperiodically.

[Application of each embodiment]
At least one of the above-mentioned embodiments may be applied when a specific condition is met, which may be specified in a standard or may be notified to a UE/BS using higher layer signaling/physical layer signaling.

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

The particular UE capability may indicate support for particular processing/operations/control/information for at least one of the above embodiments.

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

The above-mentioned specific UE capabilities may be capabilities that are applied across all duplexing methods (commonly regardless of the duplexing method), or may be capabilities for each duplexing method (e.g., Time Division Duplex (TDD) and Frequency Division Duplex (FDD)).

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

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

(Additional Note)
With respect to one embodiment of the present disclosure, the following invention is noted.
[Appendix 1-1]
A terminal having 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 handover operation based on the trigger instruction or the notification.
[Appendix 1-2]
The terminal according to claim 1-1, wherein the trigger instruction is transmitted based on location information of the terminal measured by a network or the terminal.
[Appendix 1-3]
The terminal according to Supplementary Note 1-1 or Supplementary Note 1-2, wherein the notification is transmitted to a cell before handover or a cell after handover.
[Appendix 1-4]
The control unit controls 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. A terminal according to any one of Supplementary Note 1-1 to Supplementary Note 1-3.
[Appendix 2-1]
A terminal comprising: a receiving unit that receives a Radio Resource Control (RRC) setting for a cell whose physical range is changed; and a control unit that controls a handover operation between a plurality of the cells based on the RRC setting.
[Appendix 2-2]
The terminal according to Supplementary Note 2-1, wherein one physical cell identifier (PCI) for a cell whose physical range is not changed corresponds to one cell whose physical range is changed.
[Appendix 2-3]
The terminal according to Supplementary Note 2-1 or Supplementary Note 2-2, wherein a plurality of physical cell identifiers (PCIs) for cells whose physical ranges are not changed correspond to one of the cells whose physical ranges are changed.
[Appendix 2-4]
The RRC configuration includes 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. A terminal according to any one of Supplementary Note 2-1 to Supplementary Note 2-3.
[Appendix 3-1]
A terminal comprising: a receiving unit that receives trigger information regarding handover; and a control unit that controls at least one of uplink synchronization and downlink synchronization for a cell whose physical range is changed based on the trigger information.
[Appendix 3-2]
The terminal according to Supplementary Note 3-1, wherein the trigger information is transmitted using Radio Resource Control (RRC) reconfiguration.
[Appendix 3-3]
The terminal according to claim 3-1 or 3-2, wherein the trigger information is transmitted using a specific Medium Access Control (MAC) control element.
[Appendix 3-4]
The terminal according to any one of Supplementary Note 3-1 to Supplementary Note 3-3, wherein the trigger information is transmitted using downlink control information.
[Appendix 4-1]
A terminal having a control unit that determines whether or not to perform an operation related to a handover based on a trigger condition related to the handover for a cell whose physical range is changed, and a transmission unit that transmits a report related to the handover if the handover operation is to be performed.
[Appendix 4-2]
The terminal according to Supplementary Note 4-1, wherein the trigger condition is set using Radio Resource Control (RRC) reconfiguration.
[Appendix 4-3]
The terminal according to claim 4-1 or 4-2, wherein the report on the handover is transmitted using a specific Medium Access Control (MAC) control element or uplink control information.
[Appendix 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.
[Appendix 5-1]
A terminal having: a receiving unit 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 control unit that determines 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 based on the MAC control elements.
[Appendix 5-2]
The MAC control element indicates, in a bitmap format, at least one of the following: 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 described in Supplementary Note 5-1.
[Appendix 5-3]
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. The terminal described in Supplementary Note 5-1 or Supplementary Note 5-2.
[Appendix 5-4]
A terminal as described in any one 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.

(Wireless communication system)
A 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 of these methods.

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

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.

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

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

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 arranged within the macrocell C1 and form a small cell C2 that is narrower than the macrocell C1. A user terminal 20 may be located within at least one of the cells. The arrangement and number of each cell and user terminal 20 are not limited to the embodiment shown in the figure. Hereinafter, when there is no need to distinguish between the base stations 11 and 12, they will be collectively referred to as base station 10.

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

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)). Macro cell C1 may be included in FR1, and small cell C2 may be included in FR2. For example, FR1 may be a frequency band below 6 GHz (sub-6 GHz), and FR2 may be a frequency band above 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.

In addition, the user terminal 20 may communicate using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) in each CC.

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

The base station 10 may be connected to the core network 30 via another base station 10 or directly. 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), etc.

The core network 30 may include network functions (Network Functions (NF)) such as, for example, 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). Note that multiple functions may be provided by one network node. In addition, communication with an external network (e.g., the Internet) may be performed via the DN.

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

In the wireless communication system 1, a wireless access method based on Orthogonal Frequency Division Multiplexing (OFDM) may be used. For example, in at least one of the downlink (DL) and uplink (UL), 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), etc. may be used.

The radio access method may also be called a waveform. Note that in the wireless communication system 1, other radio access methods (e.g., other single-carrier transmission methods, other multi-carrier transmission methods) may be used for the UL and DL radio access methods.

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.

In addition, 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)), etc. may be used as an uplink channel.

User data, upper layer control information, System Information Block (SIB), etc. are transmitted via PDSCH. User data, upper layer control information, etc. may also be transmitted via PUSCH. Furthermore, Master Information Block (MIB) may also be transmitted via PBCH.

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

Note that the DCI for scheduling the PDSCH may be called a DL assignment or DL DCI, and the DCI for scheduling the PUSCH may be called a UL grant or UL DCI. Note that the PDSCH may be interpreted as DL data, and the PUSCH may be interpreted as UL data.

A control resource set (COntrol REsource SET (CORESET)) and a search space may be used to detect the PDCCH. The CORESET corresponds to the resources to search for DCI. The search space corresponds to the search region and search method of PDCCH candidates. One CORESET may be associated with one or multiple search spaces. The UE may monitor the CORESET associated with a search space based on the search space configuration.

A 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 setting," "search space set setting," "CORESET," "CORESET setting," etc. in this disclosure may be read as interchangeable.

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 a scheduling request (SR). The PRACH may transmit a random access preamble for establishing a connection with a cell.

Note that in this disclosure, downlink, uplink, etc. may be expressed without adding "link." Also, various channels may be expressed without adding "Physical" to the beginning.

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.

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 PBCH) may be called an SS/PBCH block, an SS Block (SSB), etc. In addition, the SS, SSB, etc. may also be called a reference signal.

In addition, in the wireless communication system 1, a measurement reference signal (Sounding Reference Signal (SRS)), a demodulation reference signal (DMRS), etc. 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).

(base station)
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 one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140 may be provided.

Note that this example mainly shows the functional blocks of the characteristic parts of this embodiment, and the base station 10 may also be assumed to have other functional blocks necessary for wireless communication. Some of the processing of each part described below may be omitted.

The control unit 110 controls the entire base station 10. The control unit 110 can be configured from a controller, a control circuit, etc., which are described based on a common understanding in the technical field to which this disclosure pertains.

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 of communication channels (setting, release, etc.), status management of the base station 10, management of radio resources, etc.

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 composed of 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 a common understanding in the technical field to which the present disclosure relates.

The transceiver 120 may be configured as an integrated transceiver, or may be composed of a transmitter and a receiver. The transmitter may be composed of a transmission processing unit 1211 and an RF unit 122. The receiver may be composed of a reception processing unit 1212, an RF unit 122, and a measurement unit 123.

The transmitting/receiving antenna 130 can be configured as an antenna described based on common understanding in the technical field to which this disclosure pertains, such as an array antenna.

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.

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

The transceiver 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 and control information obtained from the control unit 110 to generate a bit string to be transmitted.

The transceiver 120 (transmission processor 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.

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.

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.

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, and acquire user data, etc.

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.

The transmission path interface 140 may transmit and receive signals (backhaul signaling) between devices included in the core network 30 (e.g., network nodes providing 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.

Note that the transmitting section and receiving section of the base station 10 in this disclosure may be configured with at least one of the transmitting/receiving section 120, the transmitting/receiving antenna 130, and the transmission path interface 140.

The transceiver unit 120 may transmit Radio Resource Control (RRC) settings for the cell whose physical range is to be changed. The control unit 110 may use the RRC settings to provide instructions regarding handover operations between the multiple cells (0th embodiment).

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

The transceiver unit 120 may transmit settings for trigger conditions related to handover to a cell whose physical range is to be changed. The control unit 110 may control the reception of reports related to the handover transmitted based on the trigger conditions (second embodiment).

The transceiver unit 120 may transmit Medium Access Control (MAC) control elements for activating 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 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 elements to instruct at least one of activating the first cell, activating the group of the first cells, activating the transmission/reception point, activating the synchronization signal, and activating the second cell (third embodiment).

The transceiver unit 120 may transmit a handover trigger instruction based on the terminal's location information, 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).

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

Note that this example mainly shows the functional blocks of the characteristic parts of this embodiment, and the user terminal 20 may also be assumed to have other functional blocks necessary for wireless communication. Some of the processing of each part described below may be omitted.

The control unit 210 controls the entire user terminal 20. The control unit 210 can be configured from a controller, a control circuit, etc., which are described based on a common understanding in the technical field to which this disclosure pertains.

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

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 composed of 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 a common understanding in the technical field to which the present disclosure relates.

The transceiver unit 220 may be configured as an integrated transceiver unit, or may be composed of a transmission unit and a reception unit. The transmission unit may be composed of a transmission processing unit 2211 and an RF unit 222. The reception unit may be composed of a reception processing unit 2212, an RF unit 222, and a measurement unit 223.

The transmitting/receiving antenna 230 can be configured as an antenna described based on common understanding in the technical field to which this disclosure pertains, such as an array antenna.

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.

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

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

The transceiver 220 (transmission processor 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.

Whether or not to apply DFT processing may be based on the settings 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 above-mentioned transmission processing in order to transmit the channel using a DFT-s-OFDM waveform, and when transform precoding is not enabled, it is not necessary to perform DFT processing as the above-mentioned transmission processing.

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.

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.

The transceiver 220 (reception processor 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 to acquire user data, etc.

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.

The measurement unit 223 may derive channel measurements for CSI calculation based on channel measurement resources. The channel measurement resources may be, for example, non-zero power (NZP) CSI-RS resources. The measurement unit 223 may derive interference measurements for CSI calculation based on interference measurement resources. The interference measurement resources may be at least one of NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, etc. CSI-IM may be called CSI-Interference Management (IM) or may be interchangeably read as Zero Power (ZP) CSI-RS. In this disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc. may be read as interchangeable.

In addition, the transmitting unit and receiving unit of the user terminal 20 in this disclosure may be configured by at least one of the transmitting/receiving unit 220 and the transmitting/receiving antenna 230.

The transceiver unit 220 may receive Radio Resource Control (RRC) settings for the cell whose physical range is to be changed. The control unit 210 may control handover operations between the multiple cells based on the RRC settings (0th embodiment).

For one cell whose physical range is changed, one physical cell identifier (PCI) for a cell whose physical range is not changed may correspond (0th embodiment).

For one cell whose physical range is changed, multiple physical cell identifiers (PCIs) relating to cells whose physical range is not changed may correspond (0th embodiment).

The RRC configuration may include 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, an index of a transmission/reception point, and an index of a reference signal (0th embodiment).

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

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

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

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

The control unit 210 may determine whether to perform an operation related to the handover based on a trigger condition related to the handover to 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).

The trigger condition may be set using Radio Resource Control (RRC) reconfiguration (second embodiment).

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

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

The transceiver unit 220 may receive Medium Access Control (MAC) control elements for activating 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 constituting the second cell, a synchronization signal transmitted within the second cell, and the second cell. The control unit 210 may determine at least one of activating the first cell, activating the group of the first cells, activating the transmission/reception point, activating the synchronization signal, and activating the second cell based on the MAC control elements (third embodiment).

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

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).

When the first cell is activated by the MAC control element, the MAC control element may include 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 may include an identifier of the group of the first cell and an identifier of the first cell. When the synchronization signal is activated by the MAC control element, 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).

The transceiver unit 220 may receive a handover trigger instruction based on the terminal's location information, or send a notification that the handover has been triggered. The control unit 210 may control the handover operation based on the trigger instruction or the notification (fifth embodiment).

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

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

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).

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

Here, the functions include, but are not limited to, judgement, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs the transmission function may be called a transmitting unit, a transmitter, and the like. In either case, as mentioned above, there are no particular limitations on the method of realization.

For example, a base station, a user terminal, etc. in one embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. FIG. 37 is a diagram showing an example of the hardware configuration of a base station and a user terminal according to one embodiment. The above-mentioned 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.

In addition, in this disclosure, terms such as apparatus, circuit, device, section, and unit may be interpreted as interchangeable. 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 figures, or may be configured to exclude some of the devices.

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, sequentially, or using other techniques. Furthermore, the processor 1001 may be implemented by one or more chips.

The functions of the base station 10 and the user terminal 20 are realized, for example, by loading specific software (programs) onto hardware such as the processor 1001 and memory 1002, causing the processor 1001 to perform calculations, control communications via the communication device 1004, and control at least one of the reading and writing of data in the memory 1002 and storage 1003.

The processor 1001, for example, operates 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, registers, etc. For example, at least a portion of the above-mentioned control unit 110 (210), transmission/reception unit 120 (220), etc. may be realized by the processor 1001.

The processor 1001 also reads out 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 according to these. The programs used are those that cause a computer to execute at least some of the operations described in the above embodiments. For example, the control unit 110 (210) may be realized by a control program stored in the memory 1002 and running on the processor 1001, and similar implementations may be made for other functional blocks.

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

Storage 1003 is a computer-readable recording medium and may be composed of at least one of a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disk (Compact Disc ROM (CD-ROM)), a digital versatile disk, a Blu-ray disk), 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.

The communication device 1004 is hardware (transmitting/receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, a communication module, etc. 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, for example, Frequency Division Duplex (FDD) and Time Division Duplex (TDD). For example, the above-mentioned transmitting/receiving unit 120 (220), transmitting/receiving antenna 130 (230), etc. may be realized by the communication device 1004. The transmitting/receiving unit 120 (220) may be implemented as a transmitting unit 120a (220a) and a receiving unit 120b (220b) that are physically or logically separated.

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 performs output to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one structure (e.g., a touch panel).

Furthermore, each device such as the processor 1001 and 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.

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 the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

(Modification)
In addition, the terms described in this disclosure and the terms necessary for understanding this 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 read as mutually interchangeable. A signal may also be a message. A reference signal may be abbreviated as RS, and may be called a pilot, a pilot signal, or the like depending on the applied standard. A component carrier (CC) may also be called a cell, a frequency carrier, a carrier frequency, or the like.

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.

Here, the numerology may be a communication parameter that is applied to at least one of the transmission and reception of a signal or channel. The numerology may indicate, for example, at least one of the following: SubCarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame configuration, a specific filtering process performed by the transceiver in the frequency domain, a specific windowing process performed by the transceiver in the time domain, etc.

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

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.

A radio frame, subframe, slot, minislot, and symbol all represent time units when transmitting a signal. A different name may be used for radio frame, subframe, slot, minislot, and symbol. Note that the time units such as frame, subframe, slot, minislot, and symbol in this disclosure may be read as interchangeable.

For example, one subframe may be called a TTI, multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. In other words, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 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.

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

The TTI may be a transmission time unit for a channel-coded 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) in which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

Note that 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 of scheduling. In addition, the number of slots (minislots) that constitute the minimum time unit of scheduling may be controlled.

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

Note that 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 equal to or greater than 1 ms.

A resource block (RB) is a resource allocation unit in the time domain and 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, and may be, for example, 12. The number of subcarriers included in an RB may be determined based on numerology.

Furthermore, an RB may include one or more symbols in the time domain and may be one slot, one minislot, one subframe, or one TTI in length. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

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.

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

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 an index of the RB relative to a common reference point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

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.

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 "cell," "carrier," etc. in this disclosure may be read as "BWP."

Note that the above-mentioned structures of radio frames, subframes, slots, minislots, and symbols 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, as well as the number of symbols in a TTI, the symbol length, and the cyclic prefix (CP) length can be changed in various ways.

In addition, the information, parameters, etc. described in this disclosure may be represented using absolute values, may be represented using relative values from a predetermined value, or may be represented using other corresponding information. For example, a radio resource may be indicated by a predetermined index.

The names used for parameters and the like in this disclosure are not limiting in any respect. Furthermore, the formulas 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 the various names assigned to these various channels and information elements are not limiting in any respect.

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

In addition, 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.

Input/output information, signals, etc. may be stored in a specific location (e.g., memory) or may be managed using a management table. Input/output information, signals, etc. may be overwritten, updated, or added to. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.

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

The physical layer signaling may be called Layer 1/Layer 2 (L1/L2) control information (L1/L2 control signal), L1 control information (L1 control signal), etc. The RRC signaling may be called an RRC message, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc. The MAC signaling may be notified, for example, using a MAC Control Element (CE).

Furthermore, notification of specified information (e.g., notification that "X is the case") is not limited to explicit notification, but may be implicit (e.g., by not notifying the specified information or by notifying other information).

The determination may be based on a value represented by a single bit (0 or 1), a Boolean value represented by true or false, or a comparison of numerical values (e.g., with a predetermined value).

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.

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

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

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.

In the present disclosure, the 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 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. The spatial domain transmission filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.

The above groups 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, etc.

Furthermore, in this disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, codeword (CW), transport block (TB), RS, etc. may be read as interchangeable.

Furthermore, in this 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 interpreted as interchangeable.

Furthermore, in this disclosure, "QCL", "QCL assumptions", "QCL relationship", "QCL type information", "QCL property/properties", "specific QCL type (e.g., Type A, Type D) characteristics", "specific QCL type (e.g., Type A, Type D)", etc. may be read as interchangeable.

In this disclosure, the terms index, identifier (ID), indicator, indication, resource ID, etc. may be interchangeable. In this disclosure, the terms sequence, list, set, group, cluster, subset, etc. may be interchangeable.

Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and the spatial relationship information (TCI state) may be interchangeable. "Spatial relationship information (TCI state)" may be interchangeable as "set of spatial relationship information (TCI state)", "one or more pieces of spatial relationship information", etc. TCI state and TCI may be interchangeable. Spatial relationship information and spatial relationship may be interchangeable.

In this 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.

A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the entire coverage area of the base station can be divided into multiple smaller areas, and each smaller area can also provide communication services by a base station subsystem (e.g., a small base station for indoor use (Remote Radio Head (RRH))). The term "cell" or "sector" refers to a part or the entire coverage area of at least one of the base station and base station subsystems that provide communication services in this coverage.

In this 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.

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

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.

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. In addition, 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.

The moving body in question refers to an object that can move, and the moving speed is arbitrary, and of course includes the case where the moving body is stationary. The moving body in question includes, but is not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, artificial satellites, drones, multicopters, quadcopters, balloons, and objects mounted on these. The moving body in question may also be a moving body that moves autonomously based on an operating command.

The moving object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned moving 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.

FIG. 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, an axle 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.

The drive unit 41 is composed of 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 handlebar), and is configured to steer at least one of the front wheels 46 and the rear wheels 47 based on the operation of the steering wheel operated by the user.

The electronic control unit 49 is composed of a microprocessor 61, memory (ROM, RAM) 62, and a communication port (e.g., 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).

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

The information service unit 59 is composed of various devices, such as a car navigation system, audio system, speakers, displays, televisions, and radios, for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices. The information service unit 59 uses information acquired from external devices via the communication module 60, etc., to provide various information/services (e.g., multimedia information/multimedia services) to the occupants of the vehicle 40.

The information service unit 59 may include input devices (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that accept input from the outside, and may also include output devices (e.g., a display, a speaker, an LED lamp, a touch panel, etc.) that perform output to the outside.

The driving assistance system unit 64 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving load, such as a millimeter wave radar, a Light Detection and Ranging (LiDAR), a camera, a positioning locator (e.g., a Global Navigation Satellite System (GNSS)), map information (e.g., a High Definition (HD) map, an Autonomous Vehicle (AV) map, etc.), a gyro system (e.g., an Inertial Measurement Unit (IMU), an Inertial Navigation System (INS), etc.), an Artificial Intelligence (AI) chip, and an AI processor, and 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 a driving assistance function or an autonomous driving function.

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 between 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 that are provided on the vehicle 40.

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 above-mentioned base station 10 or user terminal 20. The communication module 60 may also be, for example, at least one of the above-mentioned base station 10 and user terminal 20 (it may function as at least one of the base station 10 and user terminal 20).

The communication module 60 may transmit at least one of the signals from the various sensors 50-58 described above 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 input.

The communication module 60 receives various information (traffic information, 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 (or data/information decoded from the PDSCH) received by the communication module 60).

The communication module 60 also stores various information received from external devices in memory 62 that can be used by the microprocessor 61. Based on the information stored in 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 on the vehicle 40.

Furthermore, the base station in the present disclosure may be read as a user terminal. For example, each aspect/embodiment 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), Vehicle-to-Everything (V2X), etc.). 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, the uplink channel, downlink channel, etc. may be read as the sidelink channel.

Similarly, the user terminal in this disclosure may be interpreted as a base station. In this case, the base station 10 may be configured to have the functions of the user terminal 20 described above.

In this disclosure, operations that are described as being performed by a base station may in some cases be performed by its upper node. In a network that includes one or more network nodes having base stations, it is clear that various operations performed for communication with terminals may be performed by the base station, one or more network nodes other than the base station (such as, but not limited to, a Mobility Management Entity (MME) or a Serving-Gateway (S-GW)), or a combination of these.

Each aspect/embodiment described in this disclosure may be used alone, in combination, or switched between depending on the implementation. In addition, the processing procedures, sequences, flow charts, etc. of each aspect/embodiment described in this disclosure may be rearranged as long as there is no inconsistency. For example, the methods described in this disclosure present elements of various steps in an exemplary order, and are not limited to the particular order presented.

Each aspect/embodiment described in this disclosure includes 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)), Future Radio Access (FRA), New-Radio The present invention may be applied to systems that use 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.20, Ultra-Wide Band (UWB), Bluetooth (registered trademark), and other appropriate wireless communication methods, as well as next-generation systems that are expanded, modified, created, or defined based on these. In addition, multiple systems may be combined (for example, a combination of LTE or LTE-A and 5G, etc.).

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."

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

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 in a table, database, or other data structure), ascertaining, etc.

"Determining" may also be considered to mean "determining" receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in a memory), etc.

Furthermore, "judgment (decision)" may be considered to mean "judging (deciding)" resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment (decision)" may be considered to mean "judging (deciding)" some kind of action. In this disclosure, "judgment (decision)" may be read as interchangeably with the actions described above.

Furthermore, in this disclosure, "determine/determining" may be interpreted interchangeably as "assume/assuming," "expect/expecting," "consider/considering," etc. Furthermore, in this disclosure, "does not expect to do..." may be interpreted interchangeably as "assumes not to do...."

In the present disclosure, "expect" may be read as "be expected". For example, "expect(s) ..." ("..." may be expressed, for example, as a that clause, a to infinitive, etc.) may be read as "be expected ...". "does not expect ..." may be read as "be not expected ...". Also, "An apparatus A is not expected ..." may be read as "An apparatus B other than apparatus A does not expect ..." (for example, if apparatus A is a UE, apparatus B may be a base station).

The "maximum transmit power" referred to in this disclosure may mean the maximum value of transmit power, may mean the nominal UE maximum transmit power, or may mean the rated UE maximum transmit power.

As used in this disclosure, the terms "connected" and "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 the elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access."

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, and the like, as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range, light (both visible and invisible) range, and the like, as some non-limiting and non-exhaustive examples.

In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combined" may also be interpreted in the same way as "different."

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." Additionally, the term "or," as used in this disclosure, is not intended to be an exclusive or.

In this disclosure, where articles have been added through translation, such as a, an, and the in English, this disclosure may include that the nouns following these articles are plural.

In this disclosure, terms such as "less than", "less than", "greater than", "more than", "equal to", etc. may be read as interchangeable. In addition, in this disclosure, terms meaning "good", "bad", "big", "small", "high", "low", "fast", "slow", "wide", "narrow", etc. may be read as interchangeable, not limited to positive, comparative and superlative. In addition, in this disclosure, terms meaning "good", "bad", "big", "small", "high", "low", "fast", "slow", "wide", "narrow", etc. may be read as interchangeable, not limited to positive, comparative and superlative, as expressions with "ith" (i is any integer) (for example, "best" may be read as "ith best").

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

In the present disclosure, "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", "B until A" and the like may be read as interchangeable. Note that A, B, etc. here may be replaced with appropriate expressions such as nouns, gerunds, and normal sentences depending on the context. Note that the time difference between A and B may be almost 0 (immediately after or immediately before). Also, a time offset may be applied to the time when A occurs. For example, "A" may be read interchangeably as "before/after the time offset at which A occurs." The time offset (e.g., one or more symbols/slots) may be predefined or may be identified by the UE based on signaled information.

In this disclosure, timing, time, duration, time instance, any time unit (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc. may be interpreted as interchangeable.

　The invention disclosed herein has been described in detail above, but it is clear to those skilled in the art that the invention disclosed herein is not limited to the embodiments described herein.

Claims (6)

A transceiver unit that receives a handover trigger instruction based on location information of a terminal, or transmits a notification that the handover has been triggered;
A control unit that controls the handover operation based on the trigger instruction or the notification. The terminal according to claim 1, wherein the trigger instruction is transmitted based on location information of the terminal measured by a network or the terminal. The terminal according to claim 1, wherein the notification is transmitted to a cell before handover or a cell after handover. The terminal according to claim 1, wherein the control unit controls 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. receiving a handover trigger instruction based on location information of the terminal, or sending a notification that the handover has been triggered;
and controlling the handover operation based on the trigger instruction or the notification. A transceiver unit that transmits a handover trigger instruction based on location information of a terminal or receives a notification that the handover has been triggered;
A control unit that determines an operation of the handover based on the trigger instruction or the notification.

Images