Terminal, wireless communication method, and base station

Abstract

A terminal according to one embodiment of the present disclosure includes a reception unit that receives a Radio Resource Control (RRC) setting related to 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. According to one embodiment of the present disclosure, appropriate power control of a network can be performed, and more flexible communication can be performed.

Description

Technical Field

[0001] This disclosure relates to terminals, wireless communication methods, and base stations in next-generation mobile communication systems. Background Technology

[0002] In Universal Mobile Telecommunications System (UMTS) networks, Long Term Evolution (LTE) was standardized with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). Furthermore, LTE-Advanced (3GPP Rel. 10-14) was standardized with the aim of further increasing capacity and improving the height of LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9).

[0003] The development of successor systems to LTE is also underway (e.g., also known as the 5th generation mobile communication system (5G), 5G+ (plus), the 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel.15 and later, etc.).

[0004] Existing technical documents

[0005] Non-patent literature

[0006] Non-patent document 1: 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010 Summary of the Invention

[0007] The problem that the invention aims to solve

[0008] In future wireless communication systems (e.g., Rel.20 and beyond), research is underway on cell-free communication where terminals (user terminals, user equipment (UE)) communicate using units smaller than existing cells.

[0009] However, specific research on cellless communication is insufficient. This lack of research may prevent network (NW) control based on factors such as traffic volume, raising concerns that improvements in communication throughput may be suppressed.

[0010] Therefore, one of the purposes of this disclosure is to provide a terminal, wireless communication method, and base station that enables appropriate power control of the network and more flexible communication.

[0011] Methods for solving problems

[0012] One aspect of this disclosure relates to a terminal comprising: a receiving unit for receiving Radio Resource Control (RRC) settings associated with a cell whose physical range has been altered; and a control unit for controlling handover operations between a plurality of said cells based on said RRC settings.

[0013] Invention Effects

[0014] According to one aspect of this disclosure, appropriate power control of the network can be performed, enabling more flexible communication. Attached Figure Description

[0015] Figure 1A and Figure 1B This is a diagram illustrating an overview of MIMO.

[0016] Figure 2A This is a diagram showing an overview of a cellular system. Figure 2B This is a diagram showing the overview of a cellless system.

[0017] Figures 3A-3C This is a diagram illustrating an example of the outlines of various envisioned cellless structures.

[0018] Figure 4 This is a diagram illustrating an example of the pattern of a PCI component.

[0019] Figures 5A-5E This is a diagram illustrating an example of the structure of the first cell.

[0020] Figure 6This is a diagram illustrating an example of the pattern of the constituent elements (area components) of an area.

[0021] Figure 7A This is a diagram illustrating an example of the structure of the first / second cell involved in option 1.1. Figure 7B This is a diagram illustrating an example of the structure of the first / second cell involved in option 1.2.

[0022] Figure 8A This is a diagram illustrating an example of the structure of the first / second cell involved in option 2 / 4.1. Figure 8B This is a diagram illustrating an example of the structure of the first / second cell involved in option 2 / 4.2.

[0023] Figure 9A This is a diagram illustrating an example of the structure of the first / second cell involved in option 3 / 5.1. Figure 9B This is a diagram illustrating an example of the structure of the first / second cell involved in option 3 / 5.2.

[0024] Figure 10 This is a diagram illustrating an example of structural changes in the second cell.

[0025] Figures 11A-11C This is a diagram illustrating an example of the structure of the second cell involved in option 0.3.

[0026] Figure 12 This is a diagram illustrating an example of a mobility scenario.

[0027] Figures 13A-13C This is a diagram illustrating an example of the setting of the RRC parameters involved in Embodiment 1-1.

[0028] Figure 14 This is a diagram illustrating an example of the MAC CE-based instruction involved in option 1-2-1.

[0029] Figure 15 This is a diagram illustrating an example of the MAC CE-based instruction involved in option 1-2-2.

[0030] Figure 16 This is a diagram illustrating an example of the MAC CE-based instructions involved in options 1-2-3.

[0031] Figure 17 This is a diagram illustrating an example of the MAC CE-based instructions involved in options 1-2-4.

[0032] Figures 18A-18C This is a diagram illustrating an example of the indicator fields involved in options 1-3-1 / 1-3-2 / 1-3-3.

[0033] Figures 19A-19FThis is a diagram illustrating an example of the setting of the RRC parameters involved in option 2-1-2.

[0034] Figure 20A and Figure 20B This is a diagram illustrating an example of the MAC CE-based instruction involved in option 2-2-1.

[0035] Figure 21A and Figure 21B This is a diagram illustrating an example of the MAC CE-based instruction involved in option 2-2-2.

[0036] Figure 22A and Figure 22B This is a diagram illustrating an example of the MAC CE-based instruction involved in option 2-2-3.

[0037] Figure 23A and Figure 23B This is a diagram illustrating an example of the MAC CE-based instruction involved in option 2-2-4.

[0038] Figures 24A-24C This is a diagram illustrating an example of the indicator fields involved in options 2-3-1 / 2-3-2 / 2-3-3.

[0039] Figure 25A and Figure 25B This is a diagram illustrating an example of the MAC CE involved in options 3-1-1 / 3-1-2.

[0040] Figure 26A and Figure 26B This is a diagram illustrating an example of the MAC CE involved in option 3-2-1 / 3-2-2.

[0041] Figure 27 This is a diagram illustrating an example of the process of changing / handing over the second cell according to the fifth embodiment.

[0042] Figure 28 This is a diagram illustrating another example of the process of changing / handing over the second cell according to the fifth embodiment.

[0043] Figure 29 This is a diagram illustrating another example of the process of changing / handing over the second cell according to the fifth embodiment.

[0044] Figure 30 This is a diagram illustrating an example of the location of the UE involved in option 5-1-2-1.

[0045] Figure 31 This is a diagram illustrating an example of the location of the UE involved in option 5-1-2-2.

[0046] Figure 32This is a diagram illustrating an example of the location of the UE involved in option 5-1-2-3.

[0047] Figure 33 This is a diagram illustrating an example of the location of the UE involved in option 5-1-2-4.

[0048] Figure 34 This is a diagram illustrating an example of the schematic structure of a wireless communication system according to one embodiment.

[0049] Figure 35 This is a diagram illustrating an example of the structure of a base station according to one embodiment.

[0050] Figure 36 This is a diagram illustrating an example of the structure of a user terminal according to one embodiment.

[0051] Figure 37 This is a diagram illustrating an example of the hardware structure of a base station and a user terminal according to one embodiment.

[0052] Figure 38 This is a diagram illustrating an example of a vehicle according to one embodiment. Detailed Implementation

[0053] (Cell-free)

[0054] In existing wireless communication systems (e.g., 5G NR), a cellular approach is generally used, where a cell is formed by a single antenna / transmitter / receiver point (TRP). The area formed by this cell is fixed / static.

[0055] Furthermore, in existing wireless communication systems (e.g., Rel. 16 and later), distributed multiple input multiple output (Distributed MIMO, e.g., multi-TRP utilizing multiple TRPs) has been introduced to form communication areas using the coverage of multiple antennas / TRPs. Distributed MIMO enables simultaneous communication using multiple antennas / TRPs as well as communication using only one antenna / TRP.

[0056] By adopting distributed MIMO, a more suitable line-of-sight environment can be built, enabling performance improvements related to MIMO.

[0057] Figure 1A and Figure 1B This is a diagram illustrating an overview of MIMO. Figure 1AThe document describes an example of co-located MIMO. In co-located MIMO, a UE communicates with one antenna / TRP.

[0058] on the other hand, Figure 1B The document describes an example of distributed MIMO. In distributed MIMO, a UE communicates with multiple coordinated antennas / TRPs.

[0059] In future wireless communication systems (e.g., Rel.20 and beyond), the introduction of cellless communication is being studied with the aim of further improving performance and reducing energy consumption by reducing interference between multiple antennas / TRPs, constructing line-of-sight environments to cope with high frequency utilization, improving the overall frequency utilization efficiency of the system, and applying equal and high-quality communication to all users.

[0060] Cellular-free MIMO can also be referred to as cellless massive MIMO (mMIMO) or large-scale distributed MIMO (D-MIMO). Cellular-free MIMO utilizes coherent coordination across multiple access points. It can also incorporate at least one of the following: ultra-dense deployment, scalable cooperation, user-centric clustering, supercarrier aggregation, and analog fronthaul. The user plane for cellless MIMO can also offer more flexible scheduling than existing methods. The control plane for cellless MIMO can also maintain several cell forms to facilitate signaling.

[0061] In cellless environments, unlike traditional cellular systems, multiple antennas / TRPs can form an area (also known as a cell / sub-cell, etc.). That is, this area can also refer to a cell whose location is independent of the antenna / TRP.

[0062] In a cell-free environment, the set of antennas / TRPs used for area formation can be changed according to the needs of the UEs. For example, the set of antennas / TRPs can be changed based on factors other than the coverage area of ​​the antenna / TRP, such as the number of UEs, the number of services, or the purpose of communication (e.g., initial access / data communication / measurement / reporting).

[0063] In other words, in a cell-free environment, the coverage areas of multiple antennas / TRPs can also overlap.

[0064] In a cell-free environment, the direction of transmitting synchronization signals (e.g., also known as synchronization signal block (SSB), synchronization signal / physical broadcast channel (SS / PBCH) block, etc.) can also be controlled in each antenna / TRP.

[0065] Furthermore, in cellless environments, the central unit (CU) / distributed unit (DU) for each antenna can also be virtualized. Alternatively, each antenna can be managed solely by the CU.

[0066] Figure 2A This is a diagram showing an overview of a cellular system. Figure 2A The diagram shows the cell formed by each antenna / TRP, upon which the UE communicates.

[0067] on the other hand, Figure 2B This is a diagram illustrating the overview of a cellless system. Figure 2B In the example shown, the antenna / TRP configuration does not form a fixed / static cell within the cellular system. For example... Figure 2B As shown, in a cell-free system, one or more antennas / TRPs form an area corresponding to the conditions. Therefore, in a cell-free system, each antenna / TRP may not correspond to the same physical cell ID, and the areas between multiple antennas / TRPs may overlap.

[0068] Cellular non-cell functionality can also be achieved by adjusting the set of antennas / TRPs controlled by a central control unit (e.g., CU).

[0069] In cellless systems, a first cell with a fixed physical range, similar to a cell in a 5G NR system (e.g., it can also be called a cell / super cell / macro cell / large cell, etc.), and a second cell whose physical range changes semi-statically / dynamically based on conditions (e.g., it can also be called a sub-cell / region / micro-cell / cell / small cell / second cell within the first cell, etc.).

[0070] For example, to distinguish it from second cells, the first cell can also be called a supercell. When a supercell consists of multiple second cells, the second cells can also have the same definition / operation / coverage as existing cells in the NR. For example, to distinguish it from the first cell, the second cell can also be called a subcell. When a supercell or a cell consists of multiple subcells, the subcells can also have the same definition / operation / coverage as existing cells in the NR.

[0071] The first cell can be a newly defined cell in a future wireless communication system, or it can reuse the cell definition in an existing wireless communication system.

[0072] The structures of the first and second communities can be considered under the following assumptions 1 and 2:

[0073] Scenario 1: The first cell consists of multiple TRPs, each with a single cell ID (Physical Cell ID (PCI)). These multiple TRPs can coordinate their transmission and reception.

[0074] Scenario 2: The first cell consists of multiple TRPs (or sub-cells) with different cell IDs. Multiple TRPs / sub-cells can coordinate their transmission and reception.

[0075] Figure 3A This is a diagram illustrating an example of a schematic representation of a cell-free structure, concept 1. Figure 3A In the example shown, the TRPs contained in the first cell (supercell / cell) have the same PCI (PCI#0). Multiple TRPs can communicate in a coordinated manner for a single UE.

[0076] Figure 3B This is a diagram illustrating an example of a schematic representation of a cell-free structure, concept 2. Figure 3B In the example shown, the TRPs contained in the first cell (supercell / cell) have different PCIs (PCI#0 to #9). Multiple TRPs can communicate in a coordinated manner for a single UE.

[0077] Figure 3C This is another diagram illustrating a schematic of concept 2 for a cell-free structure. Figure 3C In the example shown, PCI is allocated to each TRP contained in the first cell (supercell / cell). Figure 3C In the example shown, with Figure 3B Unlike other examples, the same PCI can correspond to multiple TRPs. Multiple TRPs can communicate in a coordinated manner for a single UE.

[0078] Transmission / reception, which is coordinated with TRP / subcell, can also be based on at least one of the following methods supported in NR.

[0079] • Transmission of a single TRP / subcell accompanying dynamic TRP / subcell handover (single TRP transmission).

[0080] • Joint transmission using multiple TRPs / subcells (multi-TRP joint transmission). This joint transmission can be based on a single DCI or multiple DCIs. It can be either incoherent joint transmission (NCJT) or coherent joint transmission (CJT).

[0081] In order to eliminate cells, under the assumption of ideal backhaul and close coordination, CJT can take precedence over NCJT in joint transmission mode, and joint transmission based on a single DCI can also take precedence over joint transmission based on multiple DCIs.

[0082] (No structures within the community)

[0083] The following is an example of a structure without a community.

[0084] In this disclosure, the physical boundaries of a community are fixed, the community that has not been changed, the first community, the super community, the community, the macro community, the large community, etc. can also be interchanged.

[0085] In this disclosure, the physical range of a cell that changes semi-statically / dynamically based on conditions, the modified cell, the second cell, the cell, the region, the microcell, the small cell, the second cell within the first cell, etc., can also be rewritten to each other.

[0086] In this disclosure, terms such as region, neighborhood, coverage area, and scope can be interchanged.

[0087] The first community can also contain more than one second community.

[0088] A second cell can also be contained within multiple first cells. Different first cells can also share a second cell.

[0089] Different first cells may or may not overlap.

[0090] The UE can also use a second cell included in the first cell to transmit and receive signals. The UE can also receive settings related to the second cell and transmit and receive signals based on those settings.

[0091] A Physical Cell ID (PCI) may also include at least one of the following components:

[0092] • Number of TRPs per PCI.

[0093] • TRP coverage layout.

[0094] • The number of synchronization signals (e.g., SSB, SS / PBCH blocks) for each TRP.

[0095] The structure of the first cell can also be associated with the components of PCI. The first cell can also be constructed based on the components of PCI.

[0096] Figure 4This is a diagram illustrating an example of the layout of a PCI component (PCI module). Figure 4 As shown, a PCI component consists of the number of TRPs for each PCI, the TRP coverage layout, and the number of SSBs for each TRP.

[0097] like Figure 4 As shown, the number of TRPs for each PCI can take one or more values, the TRP coverage layout can be either non-overlapping or overlapping coverage areas for each TRP, and the number of SSBs for each TRP can take one or more values.

[0098] In this disclosure, the mode involved in the PCI component can also be Figure 4 Any one of the modes 1 to 5 shown. Figure 4 The model numbers shown are for a single example and are not limited to this one. Furthermore, PCI components may also contain... Figure 4 Elements other than those shown.

[0099] Figure 5A This is a diagram illustrating an example of the cell structure involved in Mode 1. In Figure 5A In the cell structure shown, each PCI / cell contains one TRP, the TRP coverage areas do not overlap, and each TRP has multiple SSBs. Additionally, in Figure 5A In the cell structure, the coverage area of ​​the TRP can also be consistent with the coverage area of ​​the cell (the first cell) (therefore, in Figure 5A (The coverage area of ​​TRP is not shown in the figure).

[0100] For example, using Figure 5A The cell structure involved in Mode 1, as shown, enables inter-cell multi-TRP operations.

[0101] Figure 5B This is a diagram illustrating an example of the cell structure involved in Mode 2. Figure 5B In the cell structure shown, the PCI / cell contains multiple TRPs, the coverage areas of which do not overlap, and each TRP has one SSB. Additionally, in Figure 5B In the cell structure, the coverage area of ​​the TRP can also be consistent with the coverage area of ​​the SSB (therefore, in Figure 5B (The coverage area of ​​TRP is not shown in the figure).

[0102] For example, using Figure 5B The cell structure involved in Mode 2, as shown, enables inter-cell multi-TRP operations.

[0103] Figure 5C This is a diagram illustrating an example of the cell structure involved in Mode 3. Figure 5CIn the cell structure shown, the PCI / cell contains multiple TRPs, the coverage areas of the TRPs do not overlap, and each TRP has multiple SSBs.

[0104] For example, using Figure 5C The cell structure involved in Mode 3, as shown, enables inter-cell multi-TRP operations.

[0105] Figure 5D This is a diagram illustrating an example of the cell structure involved in Mode 4. Figure 5D In the cell structure shown, the PCI / cell contains multiple TRPs with overlapping coverage areas, and each TRP has one SSB. Additionally, in Figure 5D In the cell structure, the coverage area of ​​the TRP can also be consistent with the coverage area of ​​the SSB (therefore, in Figure 5D (The coverage area of ​​TRP is not shown in the figure).

[0106] For example, using Figure 5D The cell structure involved in Mode 3, as shown, enables multiple TRP operations between cells / within a cell.

[0107] Figure 5E This is a diagram illustrating an example of the cell structure involved in Mode 5. In Figure 5E In the cell structure shown, the PCI / cell contains multiple TRPs with overlapping coverage areas, and each TRP has multiple SSBs.

[0108] For example, using Figure 5D The cell structure involved in Mode 3, as shown, enables multiple TRP operations between / within a cell.

[0109] In addition, the constituent elements of a second cell (e.g., a region) may also include at least one of the following:

[0110] • Number of CUs / DUs in each second cell.

[0111] • The number of PCIs in each second cell.

[0112] • The number of TRPs for each second cell.

[0113] • The number of synchronization signals (e.g., SSB, SS / PBCH blocks) in each second cell.

[0114] The structure of a second cell can also be associated with its constituent elements. A second cell can also be constructed based on its constituent elements.

[0115] Figure 6This is a diagram illustrating an example of a pattern of the constituent elements (regional components) of a region. For example... Figure 6 As shown, the area component consists of the number of CU / DUs in each area, the number of PCIs in each area, the number of TRPs in each area, and the number of synchronization signals in each area.

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

[0117] In this disclosure, the patterns involved in the region components can also be Figure 6 Any one of the patterns A through E shown. Figure 6 The notation for the pattern shown is an example only, and is not limited to this example. Furthermore, region components may also contain... Figure 6 Elements other than those shown.

[0118] For example, the second cell involved in the above patterns A, D and E can also be constructed in any first cell (cell structure).

[0119] The following describes the structures related to the first / second cell in cases of overlapping and non-overlapping cells. It is also possible to specify / define at least one of the structures related to the first / second cell described below.

[0120] The structure of the first / second cell involved in Mode 1

[0121] [Option 1.1]

[0122] Different first cells may not overlap (physically).

[0123] In this option, it can also constitute a second cell involved in at least one of the above modes A, B, D and E.

[0124] Figure 7A This is a diagram illustrating an example of the structure of the first / second cell involved in option 1.1. Figure 7A In the example shown, the two different cells (the first cell) do not overlap.

[0125] exist Figure 7A The examples shown illustrate the second cell (coverage range) involved in Mode A, the second cell (coverage range) involved in Mode B, and the second cell (coverage range) involved in Mode D / E.

[0126] In addition, Figure 7AIn the cell structure, the coverage area of ​​the TRP can also be consistent with the coverage area of ​​the cell (the first cell) (therefore, in Figure 7A (The coverage area of ​​TRP is not shown in the figure).

[0127] In the structure of this option, each second cell may also be able to perform only a single TRP operation.

[0128] Based on the structure of this option, more appropriate power reduction (network energy saving (NES)) can be achieved in the network.

[0129] [Options 1.2]

[0130] Different first cells can also overlap (physically).

[0131] In this option, it can also constitute a second cell involved in at least one of the above modes A, B, D and E.

[0132] Figure 7B This is a diagram illustrating an example of the structure of the first / second cell involved in option 1.2. Figure 7B In the example shown, two different cells (the first cell) overlap.

[0133] exist Figure 7B The examples shown illustrate the second cell (coverage range) involved in Mode A, the second cell (coverage range) involved in Mode B, and the second cell (coverage range) involved in Mode D / E.

[0134] In addition, Figure 7B In the cell structure, the coverage area of ​​the TRP can also be consistent with the coverage area of ​​the cell (the first cell) (therefore, in Figure 7B (The coverage area of ​​TRP is not shown in the figure).

[0135] In the structure of this option, for example, in the second cell involved in mode D / E, it is also possible to operate inter-cell multi-TRP operations.

[0136] Based on the structure of this option, for example, by increasing the coverage within overlapping cells, the uniformity of communication quality can be improved.

[0137] Furthermore, based on the structure of this option, frequency utilization efficiency can be improved, for example, by reducing the coverage area within overlapping cells.

[0138] Furthermore, in the structure of this option, by reusing existing NR specification antennas / TRPs, it is possible to use them by changing the antenna / TRP device to overlap with the coverage area deployed in the existing NR, thereby reducing deployment costs.

[0139] The structure of the first / second cell involved in Mode 2 / Mode 4

[0140] [Option 2 / 4.1]

[0141] Different first cells may not overlap (physically).

[0142] In this option, a second cell may also be constituted as involved in at least one of the above modes A, C, D and E.

[0143] Figure 8A This is a diagram illustrating an example of the structure of the first / second cell involved in option 2 / 4.1. Figure 8A In the example shown, the two different cells (the first cell) do not overlap.

[0144] exist Figure 8A The examples shown illustrate the second cell (coverage range) involved in Mode A, the second cell (coverage range) involved in Mode C, and the second cell (coverage range) involved in Mode D / E.

[0145] In addition, Figure 8A In the cell structure, the coverage area of ​​the TRP can also be consistent with the coverage area of ​​the SSB (therefore, in Figure 8A (The coverage area of ​​TRP is not shown in the figure).

[0146] Furthermore, in the structure of this option, each second cell may only be able to perform a single TRP operation.

[0147] Based on the structure of this option, for example, by increasing the number of TRPs in each first cell, it is possible to improve the consistency of communication quality and frequency utilization efficiency.

[0148] [Option 2 / 4.2]

[0149] Different first cells can also overlap (physically).

[0150] In this option, a second cell may also be constituted as involved in at least one of the above modes A, C, D and E.

[0151] Figure 8B This is a diagram illustrating an example of the structure of the first / second cell involved in option 2 / 4.2. Figure 8BIn the example shown, two different cells (the first cell) overlap.

[0152] exist Figure 8B The examples shown illustrate the second cell (coverage range) involved in Mode A, the second cell (coverage range) involved in Mode C, and the second cell (coverage range) involved in Mode D / E.

[0153] In addition, Figure 8B In the cell structure, the coverage area of ​​the TRP can also be consistent with the coverage area of ​​the SSB (therefore, in Figure 8B (The coverage area of ​​TRP is not shown in the figure).

[0154] In the structure of this option, for example, in the second cell involved in mode D / E, it is also possible to operate inter-cell multi-TRP operations.

[0155] Based on the structure of this option, for example, by increasing the coverage within overlapping cells, the consistency of communication quality can be improved.

[0156] Furthermore, based on the structure of this option, frequency utilization efficiency can be improved, for example, by reducing the coverage area within overlapping cells.

[0157] Furthermore, based on the structure of this option, for example, by increasing the number of TRPs in each first cell, it is possible to improve the consistency of communication quality and frequency utilization efficiency.

[0158] The structure of the first / second cell involved in Mode 3 / Mode 5

[0159] [Option 3 / 5.1]

[0160] Different first cells may not overlap (physically).

[0161] In this option, it can also constitute a second cell involved in at least one of the above modes A, B, C, D and E.

[0162] Figure 9A This is a diagram illustrating an example of the structure of the first / second cell involved in option 3 / 5.1. Figure 9A In the example shown, the two different cells (the first cell) do not overlap.

[0163] exist Figure 9A The examples shown illustrate the second cell (coverage range) involved in Mode A, Mode B, Mode C, and Mode D / E.

[0164] Additionally, the following example is shown: Figure 9A The second cell involved in Mode B shown is only included within the coverage area of ​​antenna / TRP#0. Furthermore, the following example is shown: Figure 11A The second cell involved in Mode C shown corresponds to the overlapping area of ​​the coverage of antenna / TRP#1 and antenna / TRP#2.

[0165] In the structure of this option, single TRP operations can also be performed in each second cell.

[0166] Furthermore, in this configuration, multi-TRP operations within a cell can also be performed in a second cell where the coverage areas of multiple TRPs overlap. This configuration improves frequency utilization efficiency.

[0167] Furthermore, based on the structure of this option, for example, by increasing the number of TRPs in each first cell, it is possible to improve the consistency of communication quality and frequency utilization efficiency.

[0168] [Option 3 / 5.2]

[0169] Different first cells can also overlap (physically).

[0170] In this option, it can also constitute a second cell involved in at least one of the above modes A, B, C, D and E.

[0171] Figure 9B This is a diagram illustrating an example of the structure of the first / second cell involved in option 3 / 5.2. Figure 9B In the example shown, two different cells (the first cell) overlap.

[0172] exist Figure 9B The examples shown illustrate the second cell (coverage range) involved in Mode A, Mode B, Mode C, and Mode D / E.

[0173] Additionally, the following example is shown: Figure 9B The second cell involved in Mode B shown is only included within the coverage area of ​​antenna / TRP#0. Furthermore, the following example is shown: Figure 9B The second cell involved in Mode C shown corresponds to the overlapping area of ​​the coverage of antenna / TRP#1 and antenna / TRP#2.

[0174] In the structure of this option, for example, in the second cell involved in mode D / E, it is also possible to operate inter-cell multi-TRP operations.

[0175] Furthermore, in this option's structure, under the cell structure of Mode 5, it is also possible to operate multiple TRP operations within the cell. This configuration improves frequency utilization efficiency.

[0176] Based on the structure of this option, for example, compared with option 1.2 above, it can improve the consistency of communication quality and frequency utilization efficiency, and compared with option 2 / 4.2 above, it can suppress deployment costs.

[0177] The Flexibility of Second Communities

[0178] Second cells can also be formed / reconstructed based on specific conditions / opportunities. An example of the definition of a second cell will be detailed below.

[0179] The structure of the second community can also be changed / updated based on specific conditions / opportunities.

[0180] The specific condition / opportunity may also be at least one of the following: a condition / opportunity related to the distribution of the UE, a condition / opportunity related to the service, a condition / opportunity related to a specific event, and a condition / opportunity based on specific information (e.g., information related to time, location information related to the UE / TRP, and at least one of information related to period).

[0181] For example, the conditions / opportunities related to the distribution of UEs can also be based on the distribution / number of UEs in the first cell / second cell.

[0182] For example, a service-related condition / opportunity can also be a condition / opportunity based on at least one of the following: traffic volume / communication volume in the first / second cell, traffic volume / communication volume for the TRP, and traffic volume / communication volume for the SSB.

[0183] For example, the specific event associated with the conditions / opportunities of a particular event can be predefined by the specification or depend on the implementation of NW.

[0184] For example, a condition / opportunity based on specific information can also be a condition / opportunity based on at least one of time-related information, information related to a specific timer, location information related to the UE / TRP, and information related to a period (e.g., date / time / week / climate, etc.).

[0185] The second community can also be statically constructed based on that specific condition / opportunity, or unrelated to that specific condition.

[0186] The second cell can also be configured dynamically or semi-statically based on specific conditions / opportunities. This configuration enables power consumption reduction in the NW and provides communication quality that matches the UE's needs.

[0187] Restrictions related to changes / updates of the second cell can also be specified. NW can also, in specific circumstances, determine that changes / updates of the second cell should not be performed.

[0188] Figure 10 This diagram illustrates an example of structural changes in the second cell. Figure 10 The example shown illustrates how the range of the second cell (area) is changed based on the distribution of UEs and the change in time (from time #1 to time #2).

[0189] Definition of a Second Community

[0190] The following is an example of the structure / definition of the second cell.

[0191] Regarding the structure / definition of the second cell, at least one of the following options 0.1 and 0.2 may be appropriately combined with the above description of the second cell without contradiction.

[0192] [Option 0.1]

[0193] The second cell can also consist of a cell (the first cell) / PCI.

[0194] For example, a second cell can also be identified via PCI (just like an existing NR). For example, a second cell can also be constructed using the same PCI as an existing NR.

[0195] This PCI can, for example, be specified in the same way as the PCI specified in the existing NR.

[0196] This option can also correspond to the above assumption 1.

[0197] [[Option 0.1.1]]

[0198] A second cell can also consist of a TRP (Transmission Relationship Program) oriented towards a single cell. In other words, a second cell can also correspond to a single TRP.

[0199] [[[Option 0.1.1.1]]]

[0200] The second cell can also consist of a synchronization signal (e.g., at least one of the SSB and SS / PBCH blocks) directed to a cell. In other words, a second cell can also correspond to a synchronization signal. Such a structure is, for example, equivalent to the second cell involved in mode A of at least one of the above options 1.1, 1.2, 2 / 4.1, 2 / 4.2, 3 / 5.1, and 3 / 5.2.

[0201] [[[Option 0.1.1.2]]]

[0202] A second cell can also consist of multiple synchronization signals (e.g., a portion of a synchronization signal for a cell) directed towards a cell. In other words, a second cell can also correspond to multiple synchronization signals (a portion of a synchronization signal for a cell). Such a structure is, for example, equivalent to the second cell involved in Mode B of at least one of the above options 1.1, 1.2, 3 / 5.1, and 3 / 5.2.

[0203] [[[Option 0.1.1.3]]]

[0204] A second cell can also consist of multiple synchronization signals directed to a single cell (e.g., all synchronization signals directed to a single cell). In other words, a second cell can also correspond to multiple synchronization signals (all synchronization signals directed to a single cell). Such a structure is, for example, equivalent to the second cell described in Mode B of at least one of options 1.1 and 1.2 above.

[0205] [[Option 0.1.2]]

[0206] A second cell can also consist of multiple TRPs (e.g., a portion of a TRP for a given cell) that are directed to a given cell. In other words, a second cell can correspond to multiple TRPs (a portion of a TRP for a given cell).

[0207] [[[Option 0.1.2.1]]]

[0208] A second cell can also consist of multiple synchronization signals (e.g., a portion of the synchronization signals for a cell) directed towards a cell. In other words, a second cell can also correspond to multiple synchronization signals (a portion of the synchronization signals for a cell). Such a structure is, for example, equivalent to the second cell involved in mode C of at least one of the above options 2 / 4.1, 2 / 4.2, 3 / 5.1, and 3 / 5.2.

[0209] [[Option 0.1.3]]

[0210] A second cell can also consist of multiple TRPs (e.g., all TRPs for a cell). In other words, a second cell can also correspond to multiple TRPs (all TRPs for a cell).

[0211] [[[Option 0.1.3.1]]]

[0212] The second cell can also consist of a synchronization signal (e.g., at least one of the SSB and SS / PBCH blocks) directed to a single cell. In other words, a second cell can also correspond to a synchronization signal. Such a structure is, for example, equivalent to the second cell involved in Mode A of at least one of Options 1.1 and 1.2 above.

[0213] [[[Option 0.1.3.2]]]

[0214] A second cell can also consist of multiple synchronization signals (e.g., a portion of the synchronization signals for a cell) directed towards a cell. In other words, a second cell can also correspond to multiple synchronization signals (a portion of the synchronization signals for a cell). Such a structure is, for example, equivalent to the second cell involved in mode B of at least one of options 1.1 and 1.2 above, and the second cell involved in mode C of at least one of options 3 / 5.1 and 3 / 5.2 above.

[0215] [[[Option 0.1.3.3]]]

[0216] A second cell can also consist of multiple synchronization signals directed to a single cell (e.g., all synchronization signals directed to a single cell). In other words, a second cell can also correspond to multiple synchronization signals (all synchronization signals directed to a single cell). Such a structure is, for example, equivalent to the second cell involved in mode B of at least one of options 1.1 and 1.2 above, and the second cell involved in mode C of at least one of options 2 / 4.1, 2 / 4.2, 3 / 5.1, and 3 / 5.2 above.

[0217] [Option 0.2]

[0218] The second cell can also be composed of multiple cells (first cell) / PCIs.

[0219] This PCI can, for example, be specified in the same way as the PCI specified in the existing NR.

[0220] This option can also correspond to the above-mentioned assumption 2.

[0221] [[Option 0.2.1]]

[0222] A second cell can also consist of multiple TRPs. In other words, one second cell can correspond to multiple TRPs.

[0223] This TRP can, for example, be specified in the same way as the TRP specified in the existing NR.

[0224] [[[Option 0.2.1.1]]]

[0225] The second cell can also consist of multiple synchronization signals. In other words, one second cell can correspond to multiple synchronization signals. Such a structure is, for example, equivalent to the second cell involved in mode D / E of at least one of the above options 1.1, 1.2, 2 / 4.1, 2 / 4.2, 3 / 5.1, and 3 / 5.2.

[0226] The above options can also be selected / determined based on the above conditions / opportunities (e.g., conditions / opportunities based on time / number of UEs / services, etc.).

[0227] The changes / updates of the above options can also 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.

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

[0229] The second community can also be identified by a specific ID.

[0230] This specific ID can also have a fixed value.

[0231] Furthermore, this specific ID can also be a virtual ID. In other words, this specific ID is a dynamically changeable ID, and the structure / range / location of the second cell can also be dynamically changed along with the change of this ID.

[0232] It is also possible to notify the UE of common / dedicated settings / parameters in multiple second cells. These settings / parameters can also be notified, for example, using higher-layer (RRC) parameters.

[0233] This setting / parameter can also be a setting / parameter associated with PCI / TRP / SSB, for example.

[0234] The second cell can also be used for a specific purpose / property. In other words, the second cell can also be defined / constituted / identified for a specific purpose / property.

[0235] This specific purpose may also be, for example, at least one of the following: control plane, user plane, paging, measurement, reporting, measurement reporting, beam indication / activation, transmission / reception of a specific channel / signal (e.g., PUCCH / PUSCH / SRS / PDCCH / PDSCH / CSI-RS), initial access, on-demand signaling, and handover triggering signal.

[0236] This specific characteristic may also be, for example, at least one of Doppler offset, Doppler spread, average delay, average spread, band / component carrier, subcarrier spacing, TCI status, spatial relationship, QCL type, timing advance value, downlink transmission timing, and RNTI.

[0237] The number of PCI / TRP / SSBs (e.g., the maximum number) in a second cell can be predetermined by the specification, set / instructed / notified to the UE using higher-layer signaling (RRC / MAC CE) / DCI, determined based on reports of UE capability information, or determined by a combination of at least two of these.

[0238] Second cells can also be configured contiguously (physically / spatially). Alternatively, second cells can be configured discontinuously (physically / spatially) from one another.

[0239] Sharing between second communities

[0240] [Option 0.3.1]

[0241] Synchronization signals (e.g., at least one of the SSB and SS / PBCH blocks) can also be shared among multiple second cells. The UE can also be envisioned as being able to receive the same (shared / common) synchronization signal in different second cells.

[0242] In this case, the information contained in the synchronization signal can also be set to cell-specific information.

[0243] In option 0.3.1, TRP / PCI can also be shared across multiple second sub-intervals.

[0244] In option 0.3.1, in multiple second subintervals, IDs associated with the same synchronization signal (e.g., SSB ID / SSB index / candidate SSB index), IDs associated with the same TRP (e.g., at least one of the ID used to identify the TRP, TRPID, and CORESET pool index), and at least one of the same PCI can also be used.

[0245] Figure 11AThis is a diagram illustrating an example of the area involved in option 0.3.1. Figure 11A The image shows a cell containing TRP#0-TRP#3. Figure 11A In the example shown, regions #1 and #2 are formed within the coverage area of ​​TRP #0. Regions #1 and #2 overlap and have the same SSB coverage area. That is, in this overlapping region, regions #1 and #2 can share the same SSB / TRP / PCI.

[0246] By making a structure like option 0.3.1 possible, the most flexible structure for the second cell can be achieved.

[0247] [Option 0.3.2]

[0248] Synchronization signals may not be shared between multiple second cells. The UE can also be designed to not receive the same (shared / common) synchronization signal in different second cells.

[0249] In this case, the information contained in the synchronization signal can also be set to be cell-specific. Furthermore, in this case, an index associated with the synchronization signal can be used to identify the second cell.

[0250] In option 0.3.2, TRP / PCI can also be shared across multiple second sub-intervals.

[0251] In option 0.3.2, in multiple second sub-intervals, at least one of the IDs associated with the same TRP (e.g., the ID used to identify the TRP, the TRP ID, and at least one of the CORESET pool index) and at least one of the same PCIs can also be used.

[0252] Figure 11B This is a diagram illustrating an example of the area involved in option 0.3.2. In Figure 11B The image shows a cell containing TRP#0-TRP#3. Figure 11B In the example shown, regions #1 and #2 are formed within the coverage area of ​​TRP #1. Since regions #1 and #2 do not overlap, they have different SSB coverage areas. Therefore, regions contained within either region #1 or region #2 do not share the same SSB but can share the same TRP / PCI.

[0253] In a structure like option 0.3.2, the maximum number of second cells within the first cell can also be the number of synchronization signals (SSB / SSB coverage areas). Furthermore, if a second cell spans multiple SSB coverage areas, the maximum number of second cells within the first cell can also be the number of SSBs (SSB groups) it spans.

[0254] [Option 0.3.3]

[0255] In multiple second cells, synchronization signals and TRPs may not be shared. The UE can also be designed to not transmit or receive signals for the same TRP and not receive the same (shared / common) synchronization signals in different second cells.

[0256] In this case, the information contained in the synchronization signal can also be set to be cell-specific. Furthermore, in this case, an index associated with the synchronization signal can be used to identify the second cell. Additionally, in this case, an ID associated with the TRP (used to identify the TRP) can also be used to identify the second cell.

[0257] In option 0.3.3, PCI can also be shared across multiple second sub-intervals.

[0258] In option 0.3.3, the same PCI can also be used in multiple second sub-intervals.

[0259] Figure 11C This is a diagram illustrating an example of the area involved in option 0.3.3. Figure 11C The image shows a cell containing TRP#0-TRP#3. Figure 11C In the example shown, region #1 is formed within the coverage area of ​​TRP #2, and region #2 is formed within the coverage area of ​​TRP #3. Since regions #1 and #2 do not overlap, they have different SSB coverage areas. Therefore, regions contained within region #1 or region #2 do not share the same SSB, do not share the same TRP, but can share the same PCI.

[0260] In a structure like option 0.3.3, the maximum number of second cells within the first cell can also be the number of TRPs. Furthermore, if a second cell spans multiple TRPs, the maximum number of second cells within the first cell can also be the number of TRPs (TRP groups) it spans.

[0261] [Option 0.3.4]

[0262] In multiple second cells, synchronization signals, TRPs, and PCIs may not be shared. The UE can also be designed so that it does not transmit or receive signals for the same cell (first cell / PCI), transmit or receive signals for the same TRP, or receive the same (shared / common) synchronization signals in different second cells.

[0263] In this case, the information contained in the synchronization signal can also be set to be specific to the second cell. Furthermore, the second cell can be identified using an index associated with the synchronization signal. Additionally, the second cell can be identified using an ID associated with the TRP (the ID used to identify the TRP). Furthermore, the second cell can be identified using the PCI.

[0264] In a structure like option 0.3.4, the maximum number of second cells within a first cell can also be one. Furthermore, if a second cell spans multiple first cells, the total maximum number of second cells can also be the number of first cells / PCIs (PCI groups) it spans.

[0265] The above options can also be selected / determined based on the above conditions / opportunities (e.g., conditions / opportunities based on time / number of UEs / services, etc.).

[0266] The changes / updates of the above options can also 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.

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

[0268] The IDs in the above options (e.g., IDs associated with synchronization signals, IDs associated with TRP, and at least one of PCI) can be either global (e.g., common across all NWs) or local (e.g., unique within a subset of NWs) IDs.

[0269] 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 can be predefined by the specification, set / instructed / notified to the UE using higher-layer signaling (RRC / MAC CE) / DCI, determined based on reports of UE capability information, or determined by combining at least two of these.

[0270] (analyze)

[0271] Mobility scenarios in future wireless communication systems (e.g., Rel.20 and beyond) can be considered as follows: Figure 12 Such examples.

[0272] Additionally, in this disclosure, source / serving (e.g., source area / serving) may also refer to the (current) object before the handover (e.g., area). Furthermore, in this disclosure, target (e.g., target area) may also refer to the object at the handover destination (e.g., area).

[0273] exist Figure 12 The document describes the modes (modes FM) involved in mobility scenarios in a cell-free architecture. These mobility scenarios can also 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.

[0274] exist Figure 12 The example shown illustrates the patterns of movement between second cells (here, regions) (i.e., when the source region and the target region are different) or within the second cell (i.e., when the source region and the target region are the same).

[0275] exist Figure 12 In the example shown, mode 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.

[0276] Additionally, in Mode F, it is envisioned that beam management operations using existing systems (as specified up to Rel.18) and operations involving changes to the second cell are used in cases of mobility between second cells (i.e., when the source area and the target area are different).

[0277] exist Figure 12 In the example shown, mode 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.

[0278] Additionally, in Mode G, it is envisioned that beam management operations using existing systems (as defined up to Rel.18) and operations involving changes to the second cell are used in the case of mobility between second cells (i.e., when the source area and the target area are different).

[0279] exist Figure 12In the example shown, mode 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.

[0280] Additionally, in Mode H, for intra-CU handover, the same TRP is shared by different PCIs. Furthermore, Mode H envisions the operation involved in changing the second cell in the case of mobility between second cells (i.e., when the source area and the destination area are different).

[0281] exist Figure 12 In the example shown, Mode 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.

[0282] Additionally, in Mode I, we envision operations involving intra-CU handover and, in cases of mobility between second cells (i.e., when the source and destination areas are different), changes to the second cell.

[0283] exist Figure 12 In the example shown, mode 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.

[0284] Additionally, in Mode J, for intra-CU handover, different CUs share the same TRP / PCI. Furthermore, Mode J envisions the operation involved in changing the second cell in the case of mobility between second cells (i.e., when the source area and destination area are different).

[0285] exist Figure 12 In the example shown, mode 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.

[0286] Additionally, in Mode K, for intra-CU handover, different CUs share the same PCI. Furthermore, Mode K envisions the operations involved in changing the second cell in the case of mobility between second cells (i.e., when the source area and destination area are different).

[0287] exist Figure 12 In the example shown, mode 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.

[0288] Additionally, in Mode L, for intra-CU handover, the same TRP is shared by different CUs / PCIs. Furthermore, in Mode L, the operations involved in changing the second cell are envisioned in the case of mobility between second cells (i.e., when the source area and the destination area are different).

[0289] exist Figure 12 In the example shown, mode 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.

[0290] In addition, in Mode M, it is envisioned that the operation involves handover within the CU and the operation involves changing the second cell in the case of mobility between the second cells (i.e., when the source area and the target area are different).

[0291] In this way, multiple mobility scenarios are envisioned in future wireless communication systems (e.g., Rel.20 and beyond), but research on the operation and settings of the network (NW, e.g., base station) / UE for these scenarios is insufficient.

[0292] Specifically, research on the settings related to the second cell (RRC settings) and the methods involved in the indication / detection of movement between second cells is insufficient.

[0293] Furthermore, within the second cell (e.g., when the PCI is the same / different between TRP / antenna), the existing beam management framework can be used, but when crossing the boundary of the second cell (e.g., even when the PCI is the same / different between TRP / antenna), a handover operation is required.

[0294] Especially in the case of cellless communication, at the boundary between second cells, the signal strength from each TRP / antenna can be considered to be uniform. Therefore, at this boundary, it may be affected by complex interference, making it difficult to judge the handover operation based solely on the signal reception quality.

[0295] For example, in Figure 2A In a cellular system like the one shown, the signal quality from the source cell degrades at the cell edge, thus allowing for precise identification of the target cell. On the other hand, in... Figure 2B In a cellless system like the one shown, since the area is constructed by multiple antennas / TRPs, the communication quality within the area becomes consistent. At the boundary between second cells, the signal strength may change significantly, making it difficult to determine the handover operation.

[0296] As a way to address such issues, the introduction of handover operations based on UE location information is being studied, but this research is not yet sufficient.

[0297] In the absence of sufficient research, there are concerns that the appropriate communication of dynamically / semi-statically changing cells / areas cannot be carried out, which may inhibit the improvement of communication throughput.

[0298] Therefore, the inventors of this invention conceived of a method to solve the above-mentioned problems.

[0299] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The wireless communication methods involved in each embodiment can be applied individually or in combination.

[0300] In this disclosure, "A / B" and "at least one of A and B" may be rewritten as each other. In addition, in this disclosure, "A / B / C" may also mean "at least one of A, B and C".

[0301] In this disclosure, terms such as notification, activation, deactivation, indication (or indication), selection, configuration, update, and determination can be overridden. Similarly, terms such as support, control, ability to control, operation, and ability to operate can also be overridden.

[0302] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-level parameters, fields, Information Elements (IE), settings, etc., can also be modified interchangeably. In this disclosure, Medium Access Control (MAC) elements (MAC ControlElement (CE)), update commands, activation / deactivation commands, etc., can also be modified interchangeably.

[0303] In this disclosure, higher-layer signaling may also be any one or a combination of the following: Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, other messages (e.g., positioning protocol messages (e.g., NR Positioning Protocol A (NRPPa) / LTE Positioning Protocol (LPP) messages, etc. from the core network)).

[0304] In this disclosure, MAC signaling may also use, for example, a MAC Control Element (MACCE) or a MAC Protocol Data Unit (PDU). Broadcast information may also be, for example, a Master Information Block (MIB), a System Information Block (SIB), a Minimum System Information (Remaining Minimum System Information (RMSI)), or Other System Information (OSI).

[0305] In this disclosure, physical layer signaling may also be, for example, downlink control information (DCI) or uplink control information (UCI).

[0306] In this disclosure, synchronization signals, SSB, SS / PBCH blocks, etc., can also be rewritten.

[0307] (Wireless communication method)

[0308] In this disclosure, PCI, target setting ID, candidate cell ID, cell ID, and ID used to identify the cell (first cell) can also be rewritten.

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

[0310] Furthermore, the embodiments of this disclosure are not limited to cellless structures and can be applied to situations where a cellless structure is not used. In other words, the embodiments of this disclosure can also be applied to situations where a cellless structure is not employed.

[0311] <Empirical Implementation>

[0312] In this embodiment, the configuration of the second cell will be explained.

[0313] This implementation method is generally divided into implementation methods 0-1 and 0-2. The UE / NW can apply the following implementation methods 0-1 / 0-2 individually, or in combination.

[0314] In addition, the UE / NW can also switch and apply the mode corresponding to the following implementation 0-1 / 0-2 based on specific settings / parameters / instructions.

[0315] Implementation Method 0-1

[0316] For the second cell, there can also be a corresponding PCI.

[0317] This implementation can also correspond to the above-described concept 1.

[0318] One PCI can also correspond to multiple TRPs / SSBs.

[0319] By setting the structure as in Implementation 0-1, more flexible communication is possible.

[0320] [Options 0-1-1]

[0321] For the UE, a second cell can also be configured.

[0322] This setting can also be implemented using higher-level signaling (e.g., RRC signaling).

[0323] [Options 0-1-2]

[0324] For a UE, multiple second cells can also be configured (e.g., a list / set containing multiple second cells).

[0325] These multiple second cells can also be, for example, multiple second cells corresponding to one PCI.

[0326] This setting can also be implemented using higher-level signaling (e.g., RRC signaling).

[0327] [Options 0-1-3]

[0328] For the UE, a second cell can also be configured using settings associated with the serving cell (e.g., ServingCellConfig).

[0329] For example, the settings associated with the serving cell may also include an ID (e.g., a region ID) for identifying the second cell.

[0330] In implementation 0-1, settings related to the second cell (e.g., CellFree-AreaConfig) can also be notified to the UE.

[0331] The settings related to the second cell may also include at least one of the following:

[0332] • The ID used to identify the second cell.

[0333] • Service cell index.

[0334] PCI.

[0335] • A list of indices related to the TRPs that constitute the second cell.

[0336] • A list of indices of the reference signals (e.g., SSBs) that constitute the second cell.

[0337] In addition, the ID used to identify the second cell can represent a specific value throughout the entire NW, or it can have a specific value within the PCI corresponding to the second cell.

[0338] Additionally, the TRPs constituting the second cell can also be associated with reference signals. For example, the indexes of the reference signals can also be set within the list of indexes associated with the TRPs.

[0339] Implementation Methods 0-2

[0340] A second cell can also correspond to multiple PCIs.

[0341] This implementation can also correspond to the above-described concept 2.

[0342] One PCI can also correspond to multiple TRPs / SSBs.

[0343] By adopting a structure similar to that in implementation 0-2, the number of PCI / SSBs corresponding to one PCI can be reduced.

[0344] [Options 0-2-1]

[0345] For the UE, a second cell can also be configured.

[0346] This setting can also be implemented using higher-level signaling (e.g., RRC signaling).

[0347] [Options 0-2-2]

[0348] For a UE, multiple second cells can also be configured (e.g., a list / set containing multiple second cells).

[0349] This setting can also be implemented using higher-level signaling (e.g., RRC signaling).

[0350] [Options 0-2-3]

[0351] For the UE, a second cell can also be configured using at least one of cell group-related settings (e.g., CellGroupConfig) and RRC reconfiguration (e.g., RRC Reconfiguration).

[0352] For example, at least one of the cell group-related settings and the RRC reset may include an ID (e.g., area ID) for identifying the second cell.

[0353] In implementation 0-2, settings related to the second cell (e.g., CellFree-AreaConfig) can also be notified to the UE.

[0354] The settings related to the second cell may also include at least one of the following:

[0355] • The ID used to identify the second cell.

[0356] • Service cell index.

[0357] PCI.

[0358] • A list of indices related to the TRPs that constitute the second cell.

[0359] • A list of indices of the reference signals (e.g., SSBs) that constitute the second cell.

[0360] In addition, the ID used to identify the second cell can represent a specific value throughout the entire NW, or it can have a specific value within the PCI corresponding to the second cell.

[0361] Additionally, the PCI corresponding to the second cell and the TRP constituting the second cell can also be associated. For example, an index related to the TRP can be set within the list of PCIs corresponding to the second cell.

[0362] Furthermore, the TRPs constituting the second cell can also be associated with reference signals. For example, the indexes of the reference signals can also be set within the list of indexes associated with the TRPs.

[0363] According to the above zeroth implementation method, the settings involved in the second cell can be appropriately specified.

[0364] <First Implementation>

[0365] The first implementation involves the movement / handover of the UE between second cells.

[0366] The UE can also use higher-layer signaling (RRC signaling / MAC CE) / DCI received from the NW (base station) to be set / indicated / triggered for changes / handovers related to the second cell.

[0367] Implementation Method 1-1

[0368] The UE can also use specific RRC parameters to be set / indicated / triggered for changes / handovers related to the second cell.

[0369] This specific RRC parameter can also be, for example, an RRC reset (e.g., RRC Reconfiguration).

[0370] [Option 1-1-1]

[0371] For example, if the specific RRC parameters include settings related to the second cell (e.g., CellFree-AreaConfig), the UE can also determine that a change / handover related to the second cell is to be performed.

[0372] Alternatively, this option can also be applied to options 0-1-1 / 0-2-1 mentioned above.

[0373] For example, if the specific RRC parameters do not include settings related to the second cell (e.g., CellFree-AreaConfig), the UE can also determine that it will not perform a change / handover related to the second cell. In this case, the UE can also determine that it will perform a change / handover related to the (existing) first cell.

[0374] [Options 1-1-2]

[0375] For example, the specific RRC parameter may also include an ID used to identify the second cell.

[0376] For example, if the specific RRC parameter includes an ID used to identify the second cell, the UE can also determine whether to perform a change / handover related to the second cell based on that ID (following that ID).

[0377] Alternatively, this option can also be applied to options 0-2-3 above.

[0378] For example, the UE can also determine to perform a change / handover related to the second cell if the current ID of the second cell (e.g., the service area ID) is different from the ID of the second cell contained in the specific RRC parameter.

[0379] In addition, the UE can also receive RRC parameters indicating whether to perform a change / handover related to the second cell. The UE can also determine whether to perform a change / handover related to the second cell based on these RRC parameters.

[0380] For example, if the RRC parameter represents a first value (e.g., 0 (or 1), or false), the UE can also determine that it will not perform a change / handover related to the second cell. Furthermore, if the RRC parameter represents a second value (e.g., 1 (or 0), or true), the UE can also determine that it will perform a change / handover related to the second cell.

[0381] The RRC parameter can also be included in that specific RRC parameter along with the ID used to identify the second cell.

[0382] In this option, for example, if the UE determines that it will not perform a change / handover related to the second cell, the UE may also determine that it will perform a change / handover related to the (existing) first cell.

[0383] [Options 1-1-3]

[0384] For example, the specific RRC parameter may also include at least one of the cell group-related settings (e.g., CellGroupConfig) and the serving cell-related settings (e.g., ServingCellConfig).

[0385] Settings related to cell groups (e.g., CellGroupConfig) and settings related to serving cells (e.g., ServingCellConfig) can also be used for the modified second cell.

[0386] An ID for identifying the second cell may also be included in at least one of the cell group-related settings (e.g., CellGroupConfig) and the serving cell-related settings (e.g., ServingCellConfig).

[0387] For example, if the specific RRC parameter includes an ID used to identify the second cell, the UE can also determine whether to perform a change / handover related to the second cell based on that ID (following that ID).

[0388] Alternatively, this option can also be applied to options 0-1-3 / 0-2-3 mentioned above.

[0389] For example, the UE can also determine to perform a change / handover related to the second cell if the current ID of the second cell (e.g., the service area ID) is different from the ID of the second cell contained in the specific RRC parameter.

[0390] In addition, the UE can also receive RRC parameters indicating whether to perform a change / handover related to the second cell. The UE can also determine whether to perform a change / handover related to the second cell based on these RRC parameters.

[0391] For example, if the RRC parameter represents a first value (e.g., 0 (or 1), or false), the UE can also determine that it will not perform a change / handover related to the second cell. Furthermore, if the RRC parameter represents a second value (e.g., 1 (or 0), or true), the UE can also determine that it will perform a change / handover related to the second cell.

[0392] The RRC parameter can also be included in that specific RRC parameter along with the ID used to identify the second cell.

[0393] In this option, for example, if the UE determines that it will not perform a change / handover related to the second cell, the UE may also determine that it will perform a change / handover related to the (existing) first cell.

[0394] Figures 13A-13C This is a diagram illustrating an example of the setting of the RRC parameters involved in Embodiment 1-1.

[0395] Figure 13A In the RRC reconfiguration, settings related to the second cell (CellFree-AreaConfig), the ID of the second cell (Area ID), and parameters indicating whether to perform changes / handovers related to the second cell (Area switch indicator).

[0396] exist Figure 13A In the above options 1-1-1, the RRC resetting includes settings related to the second cell (CellFree-AreaConfig), and in the above options 1-1-1, the RRC resetting includes the ID of the second cell (Area ID) and parameters indicating whether to perform changes / handovers related to the second cell (area switch indicator).

[0397] Figure 13B This example shows a CellGroupConfig configuration used for changing a second cell (area) during RRC reconfiguration. The CellGroupConfig configuration includes a CellGroup ID, the ID of the second cell (Area ID), and a parameter indicating whether a change / handover related to the second cell is being performed (area switch indicator).

[0398] exist Figure 13BIn the above options 1-1-3, the RRC reset includes cell group settings (CellGroupConfig). Corresponding to the above options 1-1-3, the cell group settings include the ID of the second cell (Area ID) and parameters indicating whether to perform changes / handovers related to the second cell (areaswitch indicator).

[0399] Figure 13C An example is shown where the ServingCellConfig of the second cell (area) is included in the RRC reconfiguration. The ServingCellConfig includes the ID of the second cell (Area ID) and a parameter indicating whether a change / handover related to the second cell is to be performed (area switch indicator).

[0400] exist Figure 13C In the above options 1-1-3, the RRC reconfiguration includes the Serving Cell Configuration. Corresponding to the above options 1-1-3, the Serving Cell Configuration includes the ID of the second cell (Area ID) and a parameter indicating whether to perform changes / handovers related to the second cell (areaswitch indicator).

[0401] According to the above implementation method 1-1, changes / handovers related to the second cell can be appropriately triggered by utilizing the RRC-based settings.

[0402] Implementation Methods 1-2

[0403] The UE can also use a specific MAC CE to be set / indicated / triggered for changes / handovers related to the second cell.

[0404] The MAC CE can be, for example, a new MAC CE (specified after Rel.20) or an extension of the MAC CE for L1L2-triggered mobility (LTM) specified in Rel.18.

[0405] [Option 1-2-1]

[0406] The MAC CE may also include fields related to the ID used to identify the second cell.

[0407] The UE can also determine whether to make a change / handover related to the second cell based on this field (following this field).

[0408] In addition to the ID of the destination setting (the setting for switching destinations), this field can also be included in the MAC CE.

[0409] Alternatively, this option can also be applied to options 0-1-2 / 0-2-2 mentioned above.

[0410] The ID of the second cell that can be indicated by the MAC CE can be the ID of multiple (e.g., all) second cells that are pre-set using RRC signaling, or the ID of at least one second cell that is pre-received by other MAC CEs (e.g., MAC CE for activating TCI status).

[0411] Figure 14 This is a diagram illustrating an example of the MAC CE-based instruction involved in option 1-2-1. Figure 14 The document describes a MAC CE derived by extending the MAC CE used in LTM.

[0412] Figure 14 The MAC CE shown includes at least a Target Config ID field and a Region ID field. Additionally, Figure 14 The example shown illustrates a scenario where three region candidates are set for the UE, and illustrates an example where the region ID field is 2 bits. The region ID field can also be determined based on the number of region candidates set for the UE.

[0413] UE can also be based on Figure 14 The value of the Region ID field in the MAC CE, as shown, determines whether to perform a region change. For example, if the field represents "00", the UE determines that no region change will be performed; if the field represents "01", "10", and "11", the UE determines that a region change will be performed to "Region #1", "Region #2", and "Region #3", respectively.

[0414] Furthermore, the field names, number of bits, and field positions in the diagrams involved in the MAC CE in this disclosure are only examples and are not limited to these examples.

[0415] In this option, for example, if the UE determines that it will not perform a change / handover related to the second cell, the UE may also determine that it will perform a change / handover related to the (existing) first cell.

[0416] [Options 1-2-2]

[0417] The MAC CE may also include a target setting ID and a field indicating whether a change / handover related to the second cell is being performed.

[0418] For example, if the field represents a first value (e.g., 0 (or 1)), the UE can also determine that it will not perform a change / handover related to the second cell. Furthermore, if the field represents a second value (e.g., 1 (or 0)), the UE can also determine that it will perform a change / handover related to the second cell based on the target setting ID.

[0419] The target settings identified by the target setting ID can also include an ID used to identify the second cell. The UE can also perform changes / handovers related to the second cell based on the ID used to identify the second cell.

[0420] Figure 15 This is a diagram illustrating an example of the MAC CE-based instruction involved in option 1-2-2. Figure 15 The document describes a MAC CE derived by extending the MAC CE used in LTM.

[0421] Figure 15 The MAC CE shown includes at least a Target Configuration ID field and a flag field indicating whether a change / handover related to the second cell is being performed.

[0422] UE can also be based on Figure 15 The value of the flag field included in the MAC CE, as shown, determines whether to perform a region change. For example, if the field represents "0", the UE determines that no region change will be performed, and if the field represents "1", the UE determines that a region change will be performed to the region corresponding to the target setting ID.

[0423] In this option, for example, if the UE determines that it will not perform a change / handover related to the second cell, the UE may also determine that it will perform a change / handover related to the (existing) first cell.

[0424] [Options 1-2-3]

[0425] The MAC CE can also contain a target setting ID.

[0426] The UE can also determine whether to perform changes / handovers related to the second cell based on the target settings identified by the target ID.

[0427] This option can also be used in combination with the operations of options 1-1-1 / 1-1-2 / 1-1-3 above.

[0428] Figure 16 This is a diagram illustrating an example of the MAC CE-based instructions involved in options 1-2-3. Figure 16 The document describes a MAC CE derived by extending the MAC CE used in LTM.

[0429] Figure 16 The MAC CE shown at least includes a Target Configuration ID field (Target Configuration ID). Additionally, as... Figure 16 As shown, the target setting ID can also be associated with the ID of the RRC parameter involved in the LTM candidate (e.g., LTM candidate ID). The RRC parameter involved in the LTM candidate may also include the LTM candidate ID, a parameter indicating whether a change / handover related to the second cell is performed (e.g., area change indicator), and the ID of the second cell (area ID).

[0430] UE can also be based on Figure 16 The value of the target setting ID contained in the MAC CE shown is used to determine whether to perform a region change, based on the setting of the LTM candidate associated with that target setting ID.

[0431] In this option, for example, if the UE determines that it will not perform a change / handover related to the second cell, the UE may also determine that it will perform a change / handover related to the (existing) first cell.

[0432] [Options 1-2-4]

[0433] The MAC CE can also contain a target setting ID.

[0434] In addition, the UE can also use this MAC CE to be notified of at least one of the following: TCI status (joint / UL / DL TCI status) ID, timing advance (TA) value, random access (Contention Free Random Access (CFRA)) resource / SSB index / random access preamble index.

[0435] If the ID of the second cell associated with at least one of the following—ID, TA value, random access (Contention Free Random Access (CFRA)) resources, SSB index, and random access preamble index—is different from the ID of the current second cell (serving area), the UE can also determine that a change / handover related to the second cell is to be performed.

[0436] The target setting ID can also be associated with the handover / LTM candidate. The handover / LTM candidate may also contain at least one of the following: RRC settings related to TCI status (joint / UL / DL TCI status), RRC settings related to TA value, and RRC settings related to random access (CFRA) resources. At least one of the following: RRC settings related to TCI status (joint / UL / DL TCI status), RRC settings related to TA value, and RRC settings related to random access (CFRA) resources may also contain the ID of the second cell.

[0437] In addition, the UE can also receive RRC parameters indicating whether to perform a change / handover related to the second cell. The UE can also determine whether to perform a change / handover related to the second cell based on these RRC parameters.

[0438] For example, if the RRC parameter represents a first value (e.g., 0 (or 1), or false), the UE can also determine that it will not perform a change / handover related to the second cell. Furthermore, if the RRC parameter represents a second value (e.g., 1 (or 0), or true), the UE can also determine that it will perform a change / handover related to the second cell.

[0439] The RRC parameters indicating whether to perform changes / handovers related to the second cell can be included in the RRC parameters related to the handover / LTM candidate / candidate TCI status, or associated with any parameter included in the RRC parameters related to the handover / LTM candidate / candidate TCI status.

[0440] Figure 17 This is a diagram illustrating an example of the MAC CE-based instructions involved in options 1-2-4. Figure 17 The document describes a MAC CE derived by extending the MAC CE used in LTM.

[0441] Figure 17 The MAC CE shown includes at least a Target Config ID field and a TCI state ID field / UL TCI state ID field. The Target Config ID can also be associated with an ID that identifies the RRC parameter involved in the LTM candidate (e.g., LTM candidate ID).

[0442] In addition, such as Figure 17As shown, the RRC parameters related to the candidate TCI status / candidate UL TCI status may also include the TCI status ID, parameters indicating whether a change / handover related to the second cell is being performed (e.g., area change indicator), and the ID of the second cell (area ID). RRC parameters related to the candidate TCI status / candidate UL TCI status may also be included in the RRC parameters related to the LTM candidate. For example, the KTM candidate may include parameters related to a list of TCI statuses, and parameters related to the TCI status ID represented by that list of TCI statuses may also refer to the RRC parameters related to the candidate TCI status / candidate UL TCI status.

[0443] UE can also be based on Figure 17 The MAC CE, as shown, contains the value of the target setting ID and the indicated TCI status ID. It then determines whether to perform a region change based on the TCI status within the setting of the LTM candidate associated with that target setting ID.

[0444] For example, the UE determines the TCI / UL TCI status indicated by the TCI status list within the LTM candidate settings associated with the target setting ID indicated by the MAC CE, and determines whether to perform an area change based on the RRC parameters associated with the candidate TCI / UL TCI status containing the ID of that TCI / UL TCI status. The RRC parameters associated with the candidate TCI / UL TCI status may also include the ID of the TCI / UL TCI status, parameters indicating whether to perform a change / handover related to the second cell (e.g., an area change indicator), and the ID of the second cell (area ID).

[0445] In this option, for example, if the UE determines that it will not perform a change / handover related to the second cell, the UE may also determine that it will perform a change / handover related to the (existing) first cell.

[0446] According to the above implementation methods 1-2, changes / handovers related to the second cell can be appropriately triggered by utilizing RRC-based settings and MAC CE-based instructions.

[0447] Implementation Methods 1-3

[0448] The UE can also be set / indicated / triggered for changes / handovers related to the second cell by using at least one of a specific MAC CE and a specific DCI.

[0449] The MAC CE can be, for example, a new MAC CE (specified after Rel.20), a MAC CE that is an extension of the MAC CE specified in Rel.18, or a MAC CE specified before Rel.18.

[0450] The UE can also use at least one of the specific MAC CE and the specific DCI to activate / deactivate the TCI state. The UE can also use at least one of the specific MAC CE and the specific DCI to be indicated the TCI state.

[0451] [Option 1-3-1]

[0452] A specific MAC CE / DCI may also include a field for identifying the ID of the second cell.

[0453] The UE can also make changes / handovers related to the second cell based on the value of the ID field.

[0454] The ID of the second cell that can be indicated by the MAC CE can be the ID of multiple (e.g., all) second cells that are pre-set using RRC signaling, or the ID of at least one second cell that is pre-received by other MAC CEs (e.g., MAC CE for activating TCI status).

[0455] The UE can also determine that it uses the indicated TCI state after the change of the second cell.

[0456] Figure 18A This is a diagram illustrating an example of the indication field involved in option 1-3-1. The UE can also be based on... Figure 18A The UE determines whether to perform a region change by using the value of an indicator field contained in a specific MAC CE / DCI, as shown. For example, if the field represents "00", the UE determines that no region change will be performed; if the field represents "01", "10", and "11", the UE determines that a region change will be performed to "Region #1", "Region #2", and "Region #3", respectively.

[0457] In this option, for example, if the UE determines that it will not perform a change / handover related to the second cell, the UE may also determine that it will perform a change / handover related to the (existing) first cell.

[0458] [Options 1-3-2]

[0459] A specific MAC CE / DCI may also include a field indicating whether a change / handover related to the second cell is being performed.

[0460] For example, if the field represents a first value (e.g., 0 (or 1)), the UE may also determine that it will not perform a change / handover related to the second cell. Furthermore, if the field represents a second value (e.g., 1 (or 0)), the UE may also determine that it will perform a change / handover related to the second cell.

[0461] The indicated TCI state can also be associated with a second cell. The UE can also 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 a change / handover related to the second cell should be performed.

[0462] Figure 18B This is a diagram illustrating an example of the indication fields involved in option 1-3-2. The UE can also be based on... Figure 18B The value of the indication field contained in the specific MAC CE / DCI, as shown, determines whether to perform a region change. For example, if the field represents "0", the UE determines that no region change will be performed, and if the field represents "1", the UE determines that a region change will be performed to the region associated with the indicated TCI state.

[0463] In this option, for example, if the UE determines that it will not perform a change / handover related to the second cell, the UE may also determine that it will perform a change / handover related to the (existing) first cell.

[0464] [Options 1-3-3]

[0465] The UE can also determine whether to perform a change / handover related to the second cell based on the TCI status indicated by using that specific MAC CE / DCI.

[0466] For example, the UE may also determine to perform a change / handover related 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).

[0467] The RRC parameters related to the TCI status used by the serving cell / area can also include the ID of the second cell.

[0468] In addition, the UE can also receive RRC parameters indicating whether to perform a change / handover related to the second cell. The UE can also determine whether to perform a change / handover related to the second cell based on these RRC parameters.

[0469] For example, if the RRC parameter represents a first value (e.g., 0 (or 1), or false), the UE can also determine that it will not perform a change / handover related to the second cell. Furthermore, if the RRC parameter represents a second value (e.g., 1 (or 0), or true), the UE can also determine that it will perform a change / handover related to the second cell.

[0470] The RRC parameters indicating whether to perform changes / handovers related to the second cell can be included in the RRC parameters related to the TCI status, or associated with any parameter included in the RRC parameters related to the TCI status.

[0471] Figure 18C This is a diagram illustrating an example of the indicator fields involved in option 1-3-3. The UE can also be based on... Figure 18C The value of the indicator field contained in the specific MAC CE / DCI, as shown, determines whether a region change should be performed.

[0472] For example, if the field indicates "00", the UE can refer to the RRC parameter corresponding to TCI status ID#0 and determine whether to perform a region change to the corresponding region based on the region change indicator and region ID contained in the RRC parameter.

[0473] In this option, for example, if the UE determines that it will not perform a change / handover related to the second cell, the UE may also determine that it will perform a change / handover related to the (existing) first cell.

[0474] According to the above implementation methods 1-3, changes / handovers related to the second cell can be appropriately triggered using MAC CE / DCI-based indications.

[0475] According to the first implementation method described above, changes / handovers related to the second cell can be appropriately performed based on notifications from the NW.

[0476] <Second Implementation>

[0477] The second implementation involves the movement / handover of the UE between two cells.

[0478] The UE can also determine whether to perform changes / handovers related to the second cell based on specific conditions.

[0479] Implementation Method 2-1

[0480] The UE can also use specific RRC parameters to set specific conditions.

[0481] This specific RRC parameter can also be, for example, an RRC reset (e.g., RRC Reconfiguration).

[0482] The UE can also use this specific RRC parameter to set events related to the triggering of changes / handovers associated with the second cell. The UE can also determine whether to perform changes / handovers related to the second cell based on the set events.

[0483] In addition, the UE can also determine whether to perform a change / handover related to the second cell based on events related to the triggering of changes / handovers related to the second cell as specified in the pre-defined specifications.

[0484] The event can be a common event for multiple (e.g., all) UEs / second cells. Alternatively, the event can be a specific event for each UE / second cell.

[0485] [Option 2-1-1]

[0486] For example, if the event related to the triggering of a change / handover associated with the second cell is met, and the specific RRC parameter contains a setting related to the second cell (e.g., CellFree-AreaConfig), the UE can also determine that a change / handover associated with the second cell is to be performed.

[0487] Alternatively, this option can also be applied to options 0-1-1 / 0-2-1 mentioned above.

[0488] For example, if the specific RRC parameters do not include settings related to the second cell (e.g., CellFree-AreaConfig), the UE can also determine that it will not perform a change / handover related to the second cell. In this case, the UE can also determine that it will perform a change / handover related to the (existing) first cell.

[0489] [Option 2-1-2]

[0490] For example, the specific RRC parameter, or any parameter contained in the specific RRC parameter, may also contain an ID used to identify the second cell.

[0491] Any parameter included in this particular RRC parameter may be, for example, at least one of the following: a parameter related to conditional reconfiguration (e.g., ConditionalReconfiguration), a measurement setting (e.g., MeasConfig), a CSI report setting (e.g., CSI report Config), and a CSI resource setting (e.g., CSI resource Config).

[0492] For example, if the event related to the triggering of a change / handover associated with the second cell is met, and the specific RRC parameter contains an ID for identifying the second cell, the UE can also determine, based on that ID (following that ID), that a change / handover associated with the second cell should be performed.

[0493] Alternatively, this option can also be applied to options 0-2-3 above.

[0494] For example, the UE can also determine to perform a change / handover related to the second cell if the current ID of the second cell (e.g., the service area ID) is different from the ID of the second cell contained in the specific RRC parameter.

[0495] In addition, the UE can also receive RRC parameters indicating whether to perform a change / handover related to the second cell. The UE can also determine whether to perform a change / handover related to the second cell based on these RRC parameters.

[0496] For example, if the RRC parameter represents a first value (e.g., 0 (or 1), or false), the UE can also determine that it will not perform a change / handover related to the second cell. Furthermore, if the RRC parameter represents a second value (e.g., 1 (or 0), or true), the UE can also determine that it will perform a change / handover related to the second cell.

[0497] The RRC parameter can also be included in that specific RRC parameter along with the ID used to identify the second cell.

[0498] In this option, for example, if the UE determines that it will not perform a change / handover related to the second cell, the UE may also determine that it will perform a change / handover related to the (existing) first cell.

[0499] Figures 19A-19F This is a diagram illustrating an example of the setting of the RRC parameters involved in option 2-1-2.

[0500] exist Figure 19A In the example shown, the Conditional Reconfiguration includes the ID of the second cell (Area ID) and a parameter indicating whether to perform changes / handovers related to the second cell (area switch indicator).

[0501] exist Figure 19BIn the example shown, the conditional reconfiguration list (CondReconfigToAddModList) contains the ID of the second cell (Area ID) and a parameter indicating whether to perform changes / handovers related to the second cell (area switch indicator).

[0502] exist Figure 19C In the example shown, the parameters related to the execution conditions of the conditional reconfiguration in the conditional reconfiguration list (CondReconfigToAddModList) include the ID of the second cell (Area ID) and a parameter indicating whether to perform changes / handovers related to the second cell (areaswitch indicator).

[0503] exist Figure 19D In the example shown, the measurement settings (MeasConfig) include the ID of the second cell (Area ID) and a parameter indicating whether to perform changes / handovers related to the second cell (areaswitch indicator).

[0504] exist Figure 19E In the example shown, the parameters of the measurement objects (MeasObjectNR) contained in the list of measurement objects (MeasObjectToAddModList) in the measurement settings (MeasConfig) include the ID of the second cell (Area ID) and a parameter indicating whether to perform changes / handovers related to the second cell (area switch indicator).

[0505] exist Figure 19F In the example shown, the list of measurement IDs (MeasIDToAddModList) in the measurement settings (MeasConfig) includes the ID of the second cell (Area ID) and a parameter indicating whether to perform changes / handovers related to the second cell (area switch indicator).

[0506] [Options 2-1-3]

[0507] For example, the specific RRC parameter or any parameter contained in the specific RRC parameter may include at least one of the cell group-related settings (e.g., CellGroupConfig) and the serving cell-related settings (e.g., ServingCellConfig).

[0508] Any parameter included in this specific RRC parameter can also be a parameter related to conditional reconfiguration associated with the target cell / region (e.g., Conditional Reconfiguration).

[0509] This specific RRC parameter can also be included in conditional RRC reconfiguration (e.g., CondRRCReconfig).

[0510] Settings related to cell groups (e.g., CellGroupConfig) and settings related to serving cells (e.g., ServingCellConfig) can also be used for the modified second cell.

[0511] An ID for identifying the second cell may also be included in at least one of the cell group-related settings (e.g., CellGroupConfig) and the serving cell-related settings (e.g., ServingCellConfig).

[0512] For example, if the event related to the triggering of a change / handover associated with the second cell is met, and the specific RRC parameter contains an ID for identifying the second cell, the UE can also determine, based on that ID (following that ID), that a change / handover associated with the second cell should be performed.

[0513] Alternatively, this option can also be applied to options 0-1-3 / 0-2-3 mentioned above.

[0514] For example, the UE can also determine to perform a change / handover related to the second cell if the current ID of the second cell (e.g., the service area ID) is different from the ID of the second cell contained in the specific RRC parameter.

[0515] In addition, the UE can also receive RRC parameters indicating whether to perform a change / handover related to the second cell. The UE can also determine whether to perform a change / handover related to the second cell based on these RRC parameters.

[0516] For example, if the RRC parameter represents a first value (e.g., 0 (or 1), or false), the UE can also determine that it will not perform a change / handover related to the second cell. Furthermore, if the RRC parameter represents a second value (e.g., 1 (or 0), or true), the UE can also determine that it will perform a change / handover related to the second cell.

[0517] The RRC parameter can also be included in that specific RRC parameter along with the ID used to identify the second cell.

[0518] In this option, for example, if the UE determines that it will not perform a change / handover related to the second cell, the UE may also determine that it will perform a change / handover related to the (existing) first cell.

[0519] In addition, the settings / parameters involved in RRC in this embodiment can also be set in at least one of the settings / parameters involved in the measurement report triggered by L1 UE, the settings / parameters involved in the conditional LTM (Rel.19), the settings / parameters involved in the measurement report triggered by L3 UE, and the settings / parameters involved in the conditional switching (Rel.16).

[0520] According to the above implementation method 2-1, it is possible to appropriately determine changes / handovers related to the second cell by utilizing the RRC-based settings.

[0521] Implementation Method 2-2

[0522] The UE can also use a specific MAC CE to report at least one of the following: changes / handover related to the second cell, and beam reports.

[0523] The MAC CE can be, for example, a new MAC CE (as specified after Rel.20), a MAC CE that extends the MAC CE for beam reporting triggered by L1 / L3 UEs, or a MAC CE that extends the MAC CE used for LTM in (Rel.19).

[0524] [Option 2-2-1]

[0525] The MAC CE may also include fields related to the ID used to identify the second cell.

[0526] The UE can also use this field to report changes / handovers related to the second cell corresponding to the field value.

[0527] Alternatively, this option can also be applied to options 0-1-2 / 0-2-2 mentioned above.

[0528] The ID of the second cell that can be reported by the MAC CE can be the ID of multiple (e.g., all) second cells that are pre-set using RRC signaling, or the ID of at least one second cell indicated by other MAC CEs received in advance (e.g., MAC CE for TCI status activation).

[0529] Figure 20A This is a diagram illustrating an example of the MAC CE-based instruction involved in option 2-2-1. Figure 20A The document describes a MAC CE derived by extending the MAC CE used in LTM.

[0530] Figure 20A The MAC CE shown contains at least the Target Config ID field and the Area ID field.

[0531] UE can also be used Figure 20A The value of the Region ID field in the MAC CE, as shown, indicates a region change for the region corresponding to that field.

[0532] Figure 20B This is a diagram illustrating other examples of MAC CE-based instructions related to option 2-2-1. Figure 20B The document describes a MAC CE derived by extending the MAC CE used for beam reporting.

[0533] Figure 20B The MAC CE shown contains at least a Area ID field.

[0534] UE can also be used Figure 20B The value of the Region ID field in the MAC CE, as shown, indicates a region change for the region corresponding to that field.

[0535] In this option, for example, it is also possible that if the UE determines that no change / handover related to the second cell should be performed, the UE reports that a change / handover related to the (existing) first cell should be performed.

[0536] [Option 2-2-2]

[0537] The MAC CE may also include a field indicating whether a change / handover related to the second cell is being performed.

[0538] For example, if the field represents a first value (e.g., 0 (or 1)), it could also mean that the UE does not perform a change / handover related to the second cell. Conversely, if the field represents a second value (e.g., 1 (or 0)), it could also mean that the UE performs a change / handover related to the second cell.

[0539] The UE can also report at least one of the target cell / area settings (target settings) and the target reference signal (RS) settings. The UE can also perform changes / handovers related to a second cell for a second cell included in at least one of the reported target cell / area settings and target reference signal settings.

[0540] Figure 21A This is a diagram illustrating an example of the MAC CE-based instruction involved in option 2-2-2. Figure 21A The document describes a MAC CE derived by extending the MAC CE used in LTM.

[0541] Figure 21A The MAC CE shown includes at least a Target Configuration ID field and a flag field indicating whether a change / handover related to the second cell is being performed.

[0542] UE can also be used Figure 21A The MAC CE, as shown, contains the value of the flag field and the value of the target setting ID, and reports whether to perform a region change for the region corresponding to that target setting ID.

[0543] Figure 21B This is a diagram illustrating other examples of MAC CE-based instructions related to option 2-2-2. Figure 21B The document describes a MAC CE derived by extending the MAC CE used for beam reporting.

[0544] Figure 21B The MAC CE shown contains a field (flag) indicating whether a change / handover is being performed that is at least related to the second cell.

[0545] UE can also be used Figure 21B The value of the region ID field contained in the MAC CE, as shown, indicates whether a region change is being performed for the region corresponding to the RS ID (e.g., the RS ID corresponding to the best reception quality) reference signal contained in the MAC CE.

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

[0547] [Option 2-2-3]

[0548] The MAC CE can also contain a target setting ID.

[0549] The UE can also report whether a change / handover related to the second cell has been performed based on the target setting identified by the target ID and at least one of the PCI.

[0550] For example, the UE can also report whether a change / handover related to the second cell has been performed based on the ID of the second cell associated with the target setting / PCI.

[0551] This option can also be used in combination with the above options 2-1-1 / 2-1-2 / 2-1-3.

[0552] Figure 22A This is a diagram illustrating an example of the MAC CE-based instruction involved in option 2-2-3. Figure 22A The document describes a MAC CE derived by extending the MAC CE used in LTM.

[0553] Figure 22A The MAC CE shown contains at least a Target Configuration ID field (Target Configuration ID).

[0554] UE can also be used Figure 22A The MAC CE, as shown, contains the target setting ID value and the region ID associated with that target setting ID, and reports whether a region change has been performed.

[0555] Figure 22B This is a diagram illustrating other examples of MAC CE-based instructions related to option 2-2-3. Figure 22B The document describes a MAC CE derived by extending the MAC CE used for beam reporting.

[0556] Figure 22B The MAC CE shown contains at least a PCI field (PCI).

[0557] UE can also be used Figure 22B The value of the PCI field (e.g., PCI1) included in the MAC CE, as shown, indicates whether a region change has been made for the region associated with that PCI.

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

[0559] [Option 2-2-4]

[0560] The MAC CE can also contain a target setting ID.

[0561] In addition, the UE can also use this MAC CE to report at least one of the following: TCI status (joint / UL / DL TCI status) ID, timing advance (TA) value, random access (CFRA) resource / SSB index / random access preamble index, RS index, and PCI.

[0562] The target setting ID in the report can also be associated with LTM candidates.

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

[0564] In addition, the ID of the second cell can also be included in the CSI report settings / CSI resource settings associated with the reported PCI / RS index.

[0565] If the ID of the second cell associated with at least one of the following TCI states (joint / UL / DL TCI states), such as ID, TA value, random access (CFRA) resource / SSB index / random access preamble index, RS index, and PCI, is different from the ID of the current second cell (service area), the NW can also determine that the UE is performing a change / handover related to the second cell.

[0566] In addition, the UE can also send RRC parameters indicating whether to perform a change / handover related to the second cell. The NW can also determine whether the UE should perform a change / handover related to the second cell based on these RRC parameters.

[0567] For example, if the RRC parameter represents a first value (e.g., 0 (or 1), or false), the NW can also determine that the UE is not performing a change / handover related to the second cell. Furthermore, if the RRC parameter represents a second value (e.g., 1 (or 0), or true), the NW can also determine that the UE is performing a change / handover related to the second cell.

[0568] Figure 23A This is a diagram illustrating an example of the MAC CE-based instruction involved in option 2-2-4. Figure 23A The document describes a MAC CE derived by extending the MAC CE used in LTM.

[0569] Figure 23A The MAC CE shown includes at least a Target Config ID field and a TCI state ID field / UL TCI state ID field. The Target Config ID can also be associated with an ID that identifies the RRC parameter involved in the LTM candidate (e.g., LTM candidate ID).

[0570] UE can also be used Figure 23A The MAC CE, as shown, contains the target setting ID and TCI status ID, and reports whether to perform a region change for the region corresponding to that target setting ID / TCI status ID.

[0571] Figure 23B This is a diagram illustrating other examples of MAC CE-based instructions related to option 2-2-4. Figure 23B The document describes a MAC CE derived by extending the MAC CE used for beam reporting.

[0572] Figure 23B The MAC CE shown contains at least an RS ID field (RS ID).

[0573] UE can also be used Figure 23B The value of the RS ID field (e.g., RS ID1) included in the MAC CE, as shown, indicates whether a region change has been performed.

[0574] In this option, for example, if the UE determines that it will not perform a change / handover related to the second cell, the UE may also determine that it will perform a change / handover related to the (existing) first cell.

[0575] Additionally, in at least one of the options 2-2-1 to 2-2-4 above, if CSIs of multiple PCIs are reported, the UE may also report a region change using a specific PCI / RS ID.

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

[0577] Additionally, in at least one of the options 2-2-1 to 2-2-4 above, if multiple PCI CSIs are reported, the UE may also use a bit (e.g., 1 bit) representing the PCI / RS ID for which the area change is being performed to report which area.

[0578] According to the above implementation method 2-2, MAC CE can be used to appropriately report changes / handovers related to the second cell.

[0579] Implementation Methods 2-3

[0580] The UE may also use a specific UCI to report at least one of the following: changes / handover related to the second cell, and beam reports.

[0581] [Option 2-3-1]

[0582] A specific UCI may also include a field for identifying the ID of the second cell.

[0583] The UE can also use this ID field to report changes / handovers related to the second cell corresponding to the field value.

[0584] The ID of the second cell that can be reported through the UCI can be the ID of multiple (e.g., all) second cells that are pre-set using RRC signaling, or the ID of at least one second cell indicated by other MAC CEs received in advance (e.g., MAC CEs for activating TCI status).

[0585] Figure 24A This is a diagram illustrating an example of the indicator field involved in option 2-3-1. The UE can also use... Figure 24A The value of the indicator field included in the specific UCI, as shown, indicates whether a region change is to be performed. For example, if the field represents "00", the UE reports no region change; if the field represents "01", "10", and "11", the UE reports a region change to "Region #1", "Region #2", and "Region #3", respectively.

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

[0587] [Option 2-3-2]

[0588] A specific UCI may also include a field indicating whether a change / handover related to the second cell is being performed.

[0589] For example, if the field represents a first value (e.g., 0 (or 1)), it could also mean that no change / handover related to the second cell will be performed. Conversely, if the field represents a second value (e.g., 1 (or 0)), it could also mean that a change / handover related to the second cell will be performed.

[0590] The UE can also report the cell ID (PCI) / RS ID to the NW. The RRC parameters associated with the cell ID (PCI) / RS ID can also be associated with the ID of the second cell.

[0591] NW can also determine the second cell for which the UE should change / handover is based on the ID of the second cell associated with the reported cell ID / RS ID.

[0592] Alternatively, the UE may use at least one of the methods described in option 2-3-1 above to report the changed ID of the second cell.

[0593] Figure 24B This is a diagram illustrating an example of the indicator field involved in option 2-3-2. The UE can also use... Figure 24B The value of the indication field included in the specific UCI, as shown, indicates whether a region change has been performed. For example, a value of "0" in the field could mean that the UE does not perform a region change, while a value of "1" could mean that the UE performs a region change to the corresponding region.

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

[0595] [Options 2-3-3]

[0596] The UE can also use a specific UCI to report the PCI / RS ID.

[0597] The PCI / RS ID reported using a specific UCI can also be associated with the ID of the second cell.

[0598] The UE can also use a specific UCI to report the PCI / RS ID and report changes / handovers related to the second cell associated with that PCI / RS ID.

[0599] For example, CSI report settings / CSI resource settings associated with the reported PCI / RS ID can also include / are associated with the ID of the second cell.

[0600] For example, NW can also determine that the UE is performing a change / handover related to the second cell if the reported ID of the second cell is different from the current ID of the second cell (service area ID).

[0601] In addition, the UE can also send RRC parameters indicating whether a change / handover related to the second cell is being performed. The UE can also use these RRC parameters to report whether a change / handover related to the second cell is being performed.

[0602] For example, if the RRC parameter represents a first value (e.g., 0 (or 1), or false), it may mean that the UE does not perform a change / handover related to the second cell. Conversely, if the RRC parameter represents a second value (e.g., 1 (or 0), or true), it may mean that the UE performs a change / handover related to the second cell.

[0603] Figure 24C This is a diagram illustrating an example of the indicator fields involved in option 2-3-3. The UE can also use... Figure 24C The values ​​of the indicator fields included in the specific UCI, as shown, indicate whether a regional change has been made.

[0604] For example, if the field indicates "00", the UE can also report a region change to the region corresponding to PCI#0 / RS ID#0 (region #3 in this case).

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

[0606] According to the above implementation methods 2-3, changes / handovers related to the second cell can be appropriately reported using UCI-based instructions.

[0607] According to the second implementation method described above, changes / handovers related to the second cell can be appropriately performed based on the UE's report.

[0608] In addition, the UE / NW can also switch and apply modes corresponding to the first and second embodiments described above based on specific settings / parameters / instructions.

[0609] <Third Implementation Method>

[0610] The third implementation relates to a MAC CE for setting / activating / deactivating a second cell.

[0611] This implementation method is generally divided into implementation methods 3-1 and 3-2. The UE / NW can apply the following implementation methods 0-1 / 0-2 individually, or in combination.

[0612] In addition, the UE / NW can also switch and apply the mode corresponding to the following implementation methods 3-1 / 3-2 based on specific settings / parameters / instructions.

[0613] Implementation Method 3-1

[0614] The second cell can also consist of a cell (first cell) group, a cell (first cell), a TRP, and an SSB.

[0615] Cell groups / cells / TRPs / SSBs that constitute a second cell can also be activated / deactivated via MAC CE.

[0616] [Option 3-1-1]

[0617] The UE can also be indicated in bitmap form to indicate the activated / deactivated cell group / cell / TRP / SSB.

[0618] The UE can also activate / deactivate the corresponding cell group / cell / TRP / SSB based on the indicated bits.

[0619] Alternatively, if the UE determines that the corresponding cell group / cell / TRP / SSB is deactivated when the bit representation in the MAC CE is the first value (e.g., 0 (or 1)), and determines that the corresponding cell group / cell / TRP / SSB is activated when the bit representation in the MAC CE is the second value (e.g., 1 (or 0)).

[0620] The number of bits / octets used in MAC CE can also be determined based on the number of cell groups / cells / TRPs / SSBs that can be set for the UE, which is based on at least one of the RRC signaling settings and the reported UE capability information.

[0621] Figure 25A This is a diagram illustrating an example of the MAC CE involved in option 3-1-1. Figure 25A The example shown illustrates a scenario where the UE is configured with 8 SSBs. The UE can also use... Figure 25A The fields (bitmaps) of the MAC CE shown are used to activate / deactivate the SSBs that constitute the region.

[0622] in addition, Figure 25A The number of SSBs shown is just one example. The number of SSBs can be the number specified in the existing specifications (e.g., 64), or a number greater than the number specified in the existing specifications (e.g., 128, 256), or the number can be determined per second cell.

[0623] [Option 3-1-2]

[0624] The UE can also be explicitly indicated with more than one cell group ID / cell ID / TRP ID / SSB ID.

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

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

[0627] The UE can also assume that the SSB corresponding to the deactivated SSB ID was not sent.

[0628] The number of bits used in MAC CE can also be determined based on the number of cell groups / cells / TRPs / SSBs that can be set for the UE. This number of cell groups / cells / TRPs / SSBs that can be set for the UE is based on at least one of the following: RRC signaling settings, reported UE capability information, and values ​​specified in advance in the specification.

[0629] The number of octets used in MAC CE can also be determined based on the number of cell groups / cells / TRPs / SSBs that can be activated, which is based on at least one of the following: RRC signaling settings, reported UE capability information, and values ​​specified in the specification.

[0630] Figure 25B This is a diagram illustrating an example of the MAC CE involved in option 3-1-2. Figure 25B The example shown illustrates the scenario where N SSBs are activated for the UE. The UE can also use... Figure 25B The MAC CE field shown is used to activate / deactivate the SSB of the constitutive region.

[0631] Additionally, MAC CE in options 3-1-1 / 3-1-2 above can also be rewritten as DCI.

[0632] When using MAC CE / DCI to activate / deactivate a cell, the MAC CE / DCI may also contain the cell group ID (or a bitmap associated with the cell group).

[0633] When using MAC CE / DCI to activate / deactivate TRP, the MAC CE / DCI can also contain PCI / cell group ID (or a bitmap associated with the cell / cell group).

[0634] When using MAC CE / DCI to activate / deactivate SSB, the MAC CE / DCI may also contain TRP / PCI / cell group ID (or a bitmap related to TRP / cell / cell group).

[0635] Implementation Method 3-2

[0636] The UE can also receive MAC CEs to activate / deactivate the second cell.

[0637] [Option 3-2-1]

[0638] The UE can also use a bitmap format to indicate the second cell to be activated / deactivated.

[0639] The UE can also activate / deactivate the corresponding cell group / cell / TRP / SSB based on the indicated bits.

[0640] Alternatively, if the UE determines that the corresponding second cell is deactivated when the bit representation in the MAC CE is the first value (e.g., 0 (or 1)), and determines that the corresponding second cell is activated when the bit representation in the MAC CE is the second value (e.g., 1 (or 0)).

[0641] The number of bits / octets used in MAC CE can also be determined based on the number of second cells that can be set for the UE, which is based on at least one of the RRC signaling settings and the reported UE capability information.

[0642] Figure 26A This is a diagram illustrating an example of the MAC CE involved in option 3-2-1. Figure 26A The example shown illustrates a scenario where eight zones are configured for the UE. The UE can also use... Figure 26A The MAC CE field (bitmap) shown is used to activate / deactivate the region structure.

[0643] in addition, Figure 26A The number of second cells (areas) shown is only one example. The number of second cells included in a MAC CE can also be determined for each first cell.

[0644] [Option 3-2-2]

[0645] The UE can also be explicitly indicated with the ID of more than one second cell.

[0646] The UE can also activate the corresponding second cell for the indicated second cell ID (included in the MAC CE).

[0647] The UE can also activate the corresponding second cell for a second cell ID that is not indicated (not included in the MAC CE).

[0648] The number of bits used in MAC CE can also be determined based on the number of second cells that can be set for the UE, which is based on at least one of the following: RRC signaling settings, reported UE capability information, and values ​​specified in advance in the specification.

[0649] The number of octets used in MAC CE can also be determined based on the number of second cells that can be activated, which is based on at least one of the following: RRC signaling settings, reported UE capability information, and values ​​specified in advance in the specification.

[0650] Figure 26B This is a diagram illustrating an example of the MAC CE involved in option 3-2-2. Figure 26B The example shown illustrates the scenario where N second cells (areas) are activated for the UE. The UE can also use... Figure 26B The MAC CE field shown indicates the region activation / deactivation.

[0651] Additionally, MAC CE in options 3-2-1 / 3-2-2 above can also be rewritten as DCI.

[0652] According to the third implementation method described above, the second cell can be properly set up / activated / deactivated using MAC CE (or DCI).

[0653] <Fourth Implementation>

[0654] The fourth implementation relates to the operation of a UE moving within a second inter-cell space.

[0655] In this embodiment, the above-mentioned Figure 12 This section explains the operations involved in changing the UE's second cell in each mode (Mode FM) of the mobility scenario.

[0656] The UE can also perform at least one of the following operations in each mode (Mode FM):

[0657] • Change the RRC settings for the second cell where the destination has changed.

[0658] • Beam switching (e.g., TCI status ID / RS index).

[0659] The UE can also receive RRC resets during RRC setting changes. Additionally, the UE can apply RRC settings for the destination that it has previously saved / acquired.

[0660] The RRC settings for a changed destination can have the same structure as the previous RRC settings, or they can consist of information that differs from the previous RRC settings.

[0661] The UE can switch to a beam indicated by the NW during beam switching, or the UE can select / determine the target beam for switching and report the selected / determined beam to the NW.

[0662] In Mode F, the UE may also choose not to perform DL / UL synchronization with the target area (e.g., random access procedure). The UE may be envisioned using the same TA as the serving area, or it may use the indicated TA / TAG.

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

[0664] In Mode H, the UE may also choose not to perform DL / UL synchronization with the target area (e.g., random access procedure / UE-based TA measurement, etc.). The UE may be envisioned using the same TA as the serving area, or it may use the indicated TA / TAG.

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

[0666] In Mode J, the UE may or may not perform DL / UL synchronization with the target area (e.g., random access procedure / UE-based TA measurement, etc.). The UE may be envisioned using the same TA as the serving area, or it may use the indicated TA / TAG.

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

[0668] In Mode L, the UE may or may not perform DL / UL synchronization with the target area (e.g., random access procedure / UE-based TA measurement, etc.). The UE may be envisioned using the same TA as the serving area, or it may use the indicated TA / TAG.

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

[0670] As mentioned above, the UE operation for each mode can also be specified in advance in the specification.

[0671] In addition, the UE can also use RRC signaling / MAC CE / DCI in various modes to be set / indicated / notified whether to perform DL / UL synchronization with the target area (e.g., random access procedure / UE-based TA measurement, etc.).

[0672] For example, the UE can also use specific parameters / fields / bits to determine whether to perform DL / UL synchronization with the target area (e.g., random access procedure / UE-based TA measurement, etc.).

[0673] For example, if the specific parameter / field / bit represents a first value (e.g., 0 (or 1), or false), the UE may also determine that it will not perform DL / UL synchronization with the target area (e.g., random access procedure / UE-based TA measurement, etc.). Furthermore, if the specific parameter / field / bit represents a second value (e.g., 1 (or 0), or true), the UE may also determine that it will perform DL / UL synchronization with the target area (e.g., random access procedure / UE-based TA measurement, etc.).

[0674] In addition, for example, the UE can also determine whether to perform DL / UL synchronization with the target area (e.g., random access procedure / UE-based TA measurement, etc.) based on whether RRC signaling / MAC CE / DCI is used to receive the TA value of the target area.

[0675] In addition, for example, it may be possible to determine whether to perform DL / UL synchronization with the target area in each mode (e.g., random access procedure / UE-based TA measurement, etc.) based on the reported UE capability information.

[0676] When the frequency / subcarrier spacing is different in the second cell, the UE can also assume that the offset value of the TA set by RRC signaling has been changed.

[0677] Furthermore, in this embodiment, UE operation accompanying the movement of the UE between the second cells is described, but this embodiment can also be applied to UE operation accompanying the movement of the UE within the second cell.

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

[0679] <Fifth Implementation>

[0680] The fifth implementation involves a change / handover operation of a second cell based on the UE's location information.

[0681] The UE can also be triggered by the NW (e.g., the base station of the source cell / area) to change / handover to a second cell. In this case, the first implementation method described above can be applied.

[0682] The change / handover can also be triggered by at least one of the following: an RRC reset message and a MAC CE of a cell handover command.

[0683] For example, the NW (e.g., the base station of the source cell / area) can also measure / obtain the UE's location information and, based on this location information, trigger a change / handover of the second cell for the UE (see reference). Figure 27 ).

[0684] The UE can also perform DL / UL synchronization operations to the target cell / region and make the initial UL transmission after the second cell change / handover is triggered.

[0685] Furthermore, for example, the UE can also measure / obtain its own location information and, under certain conditions, request a change / handover to a second cell and report at least one of the following: Figure 28 ).

[0686] The UE can also perform DL / UL synchronization operations to the target cell / region and make the initial UL transmission after the second cell change / handover is triggered.

[0687] Furthermore, the UE can also determine to perform a second cell change / handover without explicit instruction from the NW. In this case, the second implementation method described above can be applied.

[0688] For example, the UE can also measure / obtain its own location information and, under certain conditions, determine whether to perform a change / handover to a second cell. Then, the UE can also send a change / handover notification to the NW (e.g., the base station of the source cell / area) to initiate a change / handover to a second cell (handover trigger notification) (see reference). Figure 29 ).

[0689] The UE can also perform DL / UL synchronization operations to the target cell / region and perform the initial UL transmission after triggering the change / handover of the second cell.

[0690] in addition, Figures 27-29 The timeline shown for the switching operation is just one example, and is not limited to these examples. For example, Figures 27-29 At least two of the operations shown can also be interchanged. For example, the DL / UL synchronization operation performed by the UE and the handover trigger / handover trigger notification transmission and reception operation can also be interchanged.

[0691] The following explains the operations based on specific location information.

[0692] UE / NW can also use location information based on reference points to perform changes / handovers to a second cell.

[0693] When is the switch triggered?

[0694] [Option 5-1-1]

[0695] The NW can also trigger handover using specific signals based on the UE's location information reported by the UE or measured by the NW.

[0696] This specific signal could also be, for example, RRC signaling / MAC CE / DCI.

[0697] [Option 5-1-1-1]

[0698] The UE can also be triggered to switch using a signal that contains explicit information.

[0699] The explicit information could be, for example, the cell / area ID / TCI status ID / BWP ID used to identify the target cell / area.

[0700] [Options 5-1-1-2]

[0701] The UE can also be triggered to switch using signals that contain implicit information.

[0702] The implicit information may be, for example, a predefined / set TCI status ID / RS ID, a TCI status ID / RS ID associated with a cell / area different from the serving cell / area, or information related to the random access channel of a cell / area different from the serving cell / area.

[0703] In addition, the UE can also receive signals containing this explicit / implicit information from the target cell / source cell / target area / serving area / other area.

[0704] This other area could also be an area that sends only specific signals (e.g., at least one of a switching-related signal and a control signal).

[0705] [Option 5-1-2]

[0706] The UE can also use its own location information and a set / specified reference point to measure the distance between the UE and the reference point.

[0707] Then, the UE can also trigger a handover based on specific conditions (for example, under certain conditions).

[0708] The reference point can also be represented based on the coordinates of the origin.

[0709] Furthermore, in this disclosure, the reference point / origin / UE position can be represented by a Cartesian coordinate system or a polar coordinate system. Additionally, in this disclosure, the reference point / origin / UE position can be represented by a global coordinate system (GCS) or a local coordinate system (LCS). Information related to the conversion from GCS to LCS can also be set / indicated for the UE.

[0710] The coordinates of the reference point / origin and at least one of the specific conditions can be specified in advance in the specification, and can be set / instructed / notified to the UE using RRC signaling / MAC CE / DCI. It can be determined based on UE capability information or through a combination of these.

[0711] The coordinates of the reference point / origin and at least one of the specific conditions can be set / indicated / determined by the UE specifically, or can be set / indicated / determined by multiple UEs commonly.

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

[0713] The maximum number of coordinates of the reference point / origin and at least one of the specific conditions that can be set can be determined based on UE capability information or set using RRC signaling.

[0714] In this disclosure, specific conditions may also include at least one of conditions related to the UE's location information and conditions related to the UE's velocity / acceleration / measurement results (e.g., L1 / L3-RSRP / SINR). At least one of these conditions may be based on measured values ​​or predicted values. The predicted values ​​may also be calculated using an AI (Artificial Intelligence) / ML (Machine Learning) model on the UE / NW side.

[0715] The following describes the UE's location information and specific conditions. The UE's location information and specific conditions involved in the handover operation can also be determined by following at least one of the following options 5-1-2-1 to 5-1-2-4.

[0716] [Option 5-1-2-1]

[0717] You can also set a specific condition (e.g., a threshold / size relationship related to distance / coordinates) and a reference point.

[0718] For example, it could also be that, under a specific condition of distance (a positive value, such as the square of the distance), the handover is triggered when the distance between the reference point and the UE is greater than or less than a threshold.

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

[0720] Furthermore, in this case, the distance condition between the reference point and the UE can also be set for any one of the axes in the Cartesian coordinate system (x-axis, y-axis, z-axis).

[0721] For example, it could also be that, under specific conditions (positive or negative values), the handover is triggered when the UE's position coordinates are greater than or less than a specific coordinate.

[0722] In this case, the handover can also be triggered when the UE's position coordinates are all greater than or less than the components (x component, y component, z component) of a specific coordinate.

[0723] In addition, in this case, the handover can also be triggered when the UE's position coordinates are greater than or less than any of the components (x component, y component, z component) of a specific coordinate.

[0724] Furthermore, in this case, for the values ​​of each component of a specific coordinate, either positive or negative can be set.

[0725] When all coordinates are represented in a rectangular coordinate system, let the coordinates of the reference point #n (n can also be a natural number) be (x...). n y n , z n Given that the coordinates of the UE are (x', y', z'), the distance l from the reference point #n to the UE is... n It can also be done through {(x)} n -x') 2 + (y n -y') 2 + (z) n -z') 2} 1 / 2 To represent it. It can also be expressed as l. n With respect to the conditions L for each reference point #n n (and L) n The comparison is used to determine whether to switch.

[0726] Figure 30This is a diagram illustrating an example of the location of the UE involved in option 5-1-2-1. Figure 30 In the example shown, the handover associated with the second cell is determined based on a reference point (reference point #1), a threshold distance (L1) from the reference point, and the UE's location (distance l1 from the reference point).

[0727] [Option 5-1-2-2]

[0728] You can also set a specific condition (e.g., a threshold / size relationship related to distance / coordinates) and multiple reference points.

[0729] For the conditions of each reference point, option 5-1-2-1 can also be applied.

[0730] For each reference point, different UE operations (e.g., handover operations, judgments related to events, signal quality measurements, and at least one of the start / stop of a specific timer) can also be set to trigger.

[0731] Figure 31 This is a diagram illustrating an example of the location of the UE involved in option 5-1-2-2. Figure 31 In the example shown, the handover associated with the second cell is determined based on multiple reference points (reference point #1 and #2), a threshold distance from each reference point (L1 and L2, where L1=L2), and the UE's location (distance l1 from reference point #1 and distance l2 from reference point #2).

[0732] [Options 5-1-2-3]

[0733] You can also set multiple specific conditions (e.g., thresholds / size relationships related to distance / coordinates) and a reference point.

[0734] For each condition, option 5-1-2-1 can also be applied.

[0735] For each condition, different UE operations (e.g., handover operations, judgments related to events, signal quality measurements, and at least one of the start / stop of a specific timer) can be set to trigger.

[0736] Figure 32 This is a diagram illustrating an example of the location of the UE involved in option 5-1-2-3. Figure 32 In the example shown, the handover associated with the second cell is determined based on a reference point (reference point #1), a threshold distance from that reference point (L1 and L1'), and the UE's location (distance l1 from reference point #1).

[0737] [Options 5-1-2-4]

[0738] You can also set multiple specific conditions (e.g., thresholds / size relationships related to distance / coordinates) and multiple reference points.

[0739] For each condition at each reference point, option 5-1-2-1 can also be applied.

[0740] For each condition at each reference point, different UE operations (e.g., handover operations, judgments related to events, signal quality measurements, and at least one of the start / stop of a specific timer) can be set to trigger.

[0741] Figure 33 This is a diagram illustrating an example of the location of the UE involved in option 5-1-2-4. Figure 33 In the example shown, the handover associated with the second cell is determined based on multiple reference points (reference point #1), a threshold distance from each reference point (L1 and L1' for reference point 1, and L2 for reference point #2), and the UE's location (distance l1 from reference point #1 and distance l2 from reference point #2).

[0742] In addition, in this disclosure, the object / operation triggered by the UE, or the object / operation triggered by the UE, can also be at least one of the following: handover operation, requesting handover to NW, event-related measurement, signal quality measurement, and start / stop of a specific timer.

[0743] In addition, in this embodiment, the NW can set information / conditions related to the event to the UE, or the event can be specified in advance in the specification.

[0744] Types of Origin / Reference Points

[0745] The type of origin / reference point can be specified in advance in the specification, or it can be set / instructed / notified to the UE using RRC signaling / MAC CE / DCI, or it can be determined based on the reported UE capability information, or it can be determined based on a combination of these.

[0746] The origin / reference point can also be defined / set as the position of a physical object.

[0747] For example, the origin / reference point can also be the location / coordinates of a specific base station / TRP / UE.

[0748] For example, multiple candidate origins / reference points can be pre-defined / specified. In this case, which origin / reference point among the multiple candidates is used can be set / indicated / notified via RRC signaling / MAC CE / DCI, which can be pre-specified in the specification, determined based on the reported UE capability information, or determined by a combination of these.

[0749] In addition, the origin / reference point can also be specified / set as a position calculated using a specific method.

[0750] For example, the origin / reference point can also be the location / coordinates of the cell end / area end, the location / coordinates of a specific base station / TRP / UE at a specific distance, or at least one of the centroids / centers of the coordinates of multiple base stations / TRPs / UEs.

[0751] For example, multiple candidate origins / reference points / specific distances can be pre-defined / specified. In this case, which origin / reference point / specific distance among the multiple candidates is used can be set / indicated / notified using RRC signaling / MAC CE / DCI, or it can be pre-specified in the specification, or it can be determined based on the reported UE capability information, or it can be determined by a combination of these.

[0752] Furthermore, the origin / reference point can be specified / set to any location. In this case, the origin / reference point can be determined by the UE or based on coordinates (e.g., longitude / latitude / altitude) used in other services.

[0753] In addition, the origin / reference point can be set / specified both for non-terrestrial networks (NTN) and terrestrial networks (TN), or it can be set / specified separately.

[0754] Notification to NW regarding the triggering

[0755] The UE can also use a specific UL signal to send a notification to the NW for triggering the handover (handover trigger notification).

[0756] This specific UL signal could also be, for example, PUCCH / PUSCH / PRACH / SRS / other signals.

[0757] For example, the UE sends a handover trigger notification to the NW using a scheduling request (SR). In this case, the UE can also utilize the SR settings / SR resources dedicated to this notification. If no SR settings / SR resources are set for the UE for this notification, the UE can also utilize the normal (not notification-specific) SR settings / SR resources.

[0758] For example, the UE can also use a MAC CE to send a handover trigger notification to the NW. In this case, if UL permission exists (e.g., idle resources on the PUSCH), the UE can also send the MAC CE in that PUSCH; otherwise, it can send an SR to request UL permission.

[0759] For example, the UE can also use UCI to send a handover trigger notification to the NW. In this case, the UE can also use resources allocated in periodic / aperiodic / semi-persistent CSI reports. To differentiate / identify from existing CSI reports, bits can be set to identify the purpose of the CSI, or more than one specific bit can be used for the handover trigger notification.

[0760] The UE can send the 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).

[0761] The handover trigger notification may also include at least one of the following: information / number for identifying the conditions involved in the trigger, information / number for identifying the content of the trigger, information / number for the target cell / area, TCI status ID, TA, TAG ID, signal measurement quality (L1 / L3-RSRP / SINR), and the index of the reference signal corresponding to the measurement quality.

[0762] UE Operations After Switching Triggered

[0763] The UE may also perform at least one of the following operations after the handover is triggered:

[0764] • Send PRACH to the target cell / area.

[0765] • Monitor the PDCCH in the target cell / area.

[0766] • Stop transmitting and receiving signals for the source cell / area.

[0767] • Reset RRC.

[0768] Under certain circumstances, the UE may also choose not to send a PRACH to the target cell / area (i.e., the UE may also choose not to perform a random access procedure). Such specific circumstances may include at least one of the following: the UE has already held / acquired 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.

[0769] Methods for measuring location information

[0770] Alternatively, the location information of the UE can be measured / determined based on at least one of the time / phase (e.g., time / phase offset) 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 TA.

[0771] Alternatively, the UE's location information can be measured / determined based on information obtainable from specific services (e.g., Mobility as a Service (MaaS) / Global Positioning System (GPS)) / nodes (e.g., Location Management Function (LMF)) at higher levels (e.g., the UE's movement path, the UE's dwell time / time at a specific location).

[0772] In addition, the UE's location information can also be determined based on information involved in (existing) positioning / sensing.

[0773] The UE's location information can be measured by the UE and reported to the NW, or it can be measured by the NW.

[0774] The UE's location information can be either measured or predicted. AI / ML models on the UE / NW side can also be used in the measurement / prediction of the UE's location information.

[0775] In addition, in this embodiment, location information, connection target base station information (e.g., PCI), information estimated on the NW side based on L1 / L3 reports, information related to continuous paths predicted on the UE side, and time information of the UE's location can also be rewritten.

[0776] According to the fifth implementation method above, by changing / handing over the second cell based on the UE's location information, the change / handover of the second cell can be performed appropriately even if the quality changes drastically or complexly at the boundary of the second cell.

[0777] <Supplement>

[0778] [Information notification to UE]

[0779] The notification of any information from the network (NW) (e.g., base station (BS)) to the UE in the above-described embodiments (in other words, the reception of any information from the BS in the UE) can also be performed using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PDCCH, PDSCH, reference signals), or combinations thereof.

[0780] In the case where the above notification is made via MAC CE, the MAC CE can also be identified by including a new Logical Channel ID (LCID) in the MAC subheader that is not specified in the existing standard.

[0781] When the above notification is made through a DCI, the notification can also be made through specific fields of the DCI, the Radio Network Temporary Identifier (RNTI) used in the scrambling of the Cyclic Redundancy Check (CRC) bits assigned to the DCI, the format of the DCI, etc.

[0782] Furthermore, the notification of any information to the UE in the above embodiments can also be carried out periodically, semi-persistently, or non-periodically.

[0783] [Notification from UE]

[0784] The notification of any information from the UE (to the NW) in the above embodiments (in other words, the transmission / reporting of any information from the UE to the BS) can also be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MACCE), specific signals / channels (e.g., PUCCH, PUSCH, PRACH, reference signals), or combinations thereof.

[0785] In the case where the above notification is made via MAC CE, the MAC CE can also be identified by including a new LCID in the MAC sub-header that is not specified in the existing standard.

[0786] In cases where the above notification is sent via UCI, the above notification may also be sent using PUCCH or PUSCH.

[0787] Furthermore, the notification of any information from the UE in the above embodiments can also be carried out periodically, semi-persistently, or non-periodically.

[0788] [Regarding the application of each implementation method]

[0789] At least one of the above embodiments can also be applied under certain conditions. These specific conditions can be specified in the standard or notified to the UE / BS using higher-layer signaling / physical layer signaling.

[0790] At least one of the above embodiments may also be applied only to UEs that have reported a specific UE capability or support that specific UE capability.

[0791] This specific UE capability can also represent support for at least one of the above-described implementations for specific processing / operation / control / information.

[0792] Furthermore, the aforementioned specific UE capabilities can be capabilities applied across the entire frequency range (commonly independent of frequency), capabilities for each frequency (e.g., one or a combination of cells, bands, band combinations, BWPs, component carriers, etc.), capabilities for each frequency range (e.g., Frequency Range 1 (FR1)), FR2, FR3, FR4, FR5, FR2-1, FR2-2), capabilities for each subcarrier spacing (SCS) or capabilities for each feature set (FS) or each feature set per component carrier (FSPC).

[0793] Furthermore, the aforementioned specific UE capabilities can be either capabilities that apply to all duplex modes (commonly regardless of the duplex mode) or capabilities that apply to each duplex mode (e.g., Time Division Duplex (TDD) and Frequency Division Duplex (FDD)).

[0794] Furthermore, at least one of the above-described embodiments can also be applied when the UE is set / activated / triggered by specific information associated with the above-described embodiments (or performs the operations of the above-described embodiments) via higher-layer signaling / physical layer signaling. For example, this specific information may be information indicating activation of cellless operation, arbitrary RRC parameters for a specific version (e.g., Rel.20 and later), etc.

[0795] The UE may also apply operations such as Rel.15-19 if it does not support at least one of the specific UE capabilities mentioned above, or if the specific information mentioned above is not set.

[0796] (Postscript)

[0797] With respect to one embodiment of this disclosure, the following invention is noted.

[0798] [Postscript 1-1]

[0799] A terminal includes: a transmitting and receiving unit for receiving a trigger indication for switching based on the terminal's location information, or for sending a notification that the switching has been triggered; and a control unit for controlling the switching operation based on the trigger indication or the notification.

[0800] [Notes 1-2]

[0801] As described in 1-1 above, the trigger indication is sent based on the location information of the terminal measured by the network or the terminal itself.

[0802] [Notes 1-3]

[0803] The terminal as described in Appendix 1-1 or Appendix 1-2, wherein the notification is sent to the cell before or after the handover.

[0804] [Notes 1-4]

[0805] As in any one of Appendix 1-1 to Appendix 1-3, the control unit controls the switching operation based on the terminal's location information based on one or more reference points and one or more conditions corresponding to the reference points.

[0806] [Postscript 2-1]

[0807] A terminal includes: a receiving unit for receiving Radio Resource Control (RRC) settings related to a cell whose physical range has been changed; and a control unit for controlling handover operations between a plurality of cells based on the RRC settings.

[0808] [Postscript 2-2]

[0809] As described in Appendix 2-1, in a terminal, a Physical Cell Identifier (PCI) associated with a cell whose physical extent has not been changed corresponds to a cell whose physical extent has been changed.

[0810] [Notes 2-3]

[0811] As described in Appendix 2-1 or Appendix 2-2, in a terminal, multiple Physical Cell Identifiers (PCIs) associated with a cell whose physical extent has not been changed correspond to a cell whose physical extent has been changed.

[0812] [Appendix 2-4]

[0813] As described in any one of Appendix 2-1 to Appendix 2-3, the terminal wherein the RRC setting includes at least one of the following: an identifier of the cell whose physical range has been changed, an identifier of the cell whose physical range has not been changed, an identifier of the serving cell, an index of the transmitting / receiving point, and an index of the reference signal.

[0814] [Postscript 3-1]

[0815] A terminal includes: a receiving unit for receiving trigger information related to handover; and a control unit for controlling at least one of uplink synchronization and downlink synchronization for a cell whose physical range has been changed, based on the trigger information.

[0816] [Postscript 3-2]

[0817] As described in Appendix 3-1, the triggering information is transmitted using Radio Resource Control (RRC) resetting.

[0818] [Postscript 3-3]

[0819] As described in Appendix 3-1 or Appendix 3-2, the terminal wherein the triggering information is sent using a specific Medium Access Control (MAC) element.

[0820] [Notes 3-4]

[0821] The terminal as described in any one of Appendix 3-1 to Appendix 3-3, wherein the triggering information is transmitted using downlink control information.

[0822] [Postscript 4-1]

[0823] A terminal includes: a control unit that determines whether to perform an operation related to the handover based on triggering conditions related to handover for a cell whose physical range has been changed; and a sending unit that, if the handover operation is performed, sends a report related to the handover.

[0824] [Postscript 4-2]

[0825] As described in Appendix 4-1, the triggering conditions are set using Radio Resource Control (RRC) resetting.

[0826] [Appendix 4-3]

[0827] As described in Appendix 4-1 or Appendix 4-2, the terminal in which the report related to the handover is sent using a specific Medium Access Control (MAC) element or uplink control information.

[0828] [Postscript 4-4]

[0829] The terminal as described in any one of Appendix 4-1 to Appendix 4-3, wherein the operation related to the handover is at least one of uplink synchronization and downlink synchronization for the cell.

[0830] [Postscript 5-1]

[0831] A terminal includes: a receiving unit that receives a Medium Access Control (MAC) element for activating at least one of the following: a first cell whose physical range has not been changed, a group of the first cells, a transmit / receive point constituting the second cell, a synchronization signal transmitted within the second cell, and the second cell; and a control unit that, based on the MAC control element, determines at least one of the activation of the first cell, the activation of the group of the first cells, the activation of the transmit / receive point, the activation of the synchronization signal, and the activation of the second cell.

[0832] [Postscript 5-2]

[0833] As described in Appendix 5-1, the terminal wherein the MAC control element, in bitmap form, indicates at least one of the following: activation of the first cell, activation of the group of the first cell, activation of the transmit / receive point, activation of the synchronization signal, and activation of the second cell.

[0834] [Postscript 5-3]

[0835] As described in Appendix 5-1 or Appendix 5-2, the terminal wherein the MAC control element includes at least one of the identifier of the first cell, the identifier of the group of the first cell, the identifier of the transmit / receive point, the index of the synchronization signal, and the identifier of the second cell.

[0836] [Postscript 5-4]

[0837] As in any one of Appendix 5-1 to Appendix 5-3, in the case where the first cell is activated by the MAC control element, the MAC control element includes an identifier of the group of the first cell; in the case where the transmit / receive 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; in the case where 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 transmit / receive point.

[0838] (Wireless communication system)

[0839] The structure of a wireless communication system according to one embodiment of this disclosure will now be described. In this wireless communication system, communication is performed using any one or a combination of the wireless communication methods according to the above embodiments of this disclosure.

[0840] Figure 34 This is a diagram illustrating an example of the schematic structure of a wireless communication system according to one embodiment. The wireless communication system 1 (also referred to simply as System 1) may also be a system that uses Long Term Evolution (LTE) or 5th generation mobile communication system New Radio (5GNR) as standardized by the Third Generation Partnership Project (3GPP).

[0841] Furthermore, the wireless communication system 1 can also support dual connectivity between multiple radio access technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC can also 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.

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

[0843] Wireless communication system 1 can also support dual connectivity between multiple base stations within the same RAT (e.g., MN and SN are dual connectivity between NR base stations (gNB) (NR-NR Dual Connectivity (NN-DC))).

[0844] The wireless communication system 1 may also include a base station 11 forming a macro cell C1 with a relatively wide coverage area, and a base station 12 (12a-12c) configured within the macro cell C1 and forming a small cell C2 narrower than the macro cell C1. The user terminal 20 may also be located within at least one cell. The configuration and number of each cell and the user terminal 20 are not limited to the arrangement shown in the figure. Hereinafter, without distinguishing between base stations 11 and 12, they will be collectively referred to as base station 10.

[0845] User terminal 20 may also connect to at least one of multiple base stations 10. User terminal 20 may also utilize at least one of carrier aggregation (CA) using multiple component carriers (CC) and dual connectivity (DC).

[0846] Each CC can also be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). Macro cell C1 can also be included in FR1, and small cell C2 can also be included in FR2. For example, FR1 can also be a frequency band below 6 GHz (sub-6 GHz), and FR2 can also be a frequency band above 24 GHz (above-24 GHz). In addition, the frequency bands, definitions, etc. of FR1 and FR2 are not limited to these; for example, FR1 can also correspond to a frequency band higher than FR2.

[0847] In addition, in each CC, the user terminal 20 may also use at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) for communication.

[0848] Multiple base stations 10 can also be connected via wired (e.g., fiber optic, X2 interface, etc. based on Common Public Radio Interface (CPRI)) or wireless (e.g., NR communication). For example, when NR communication between base stations 11 and 12 is used as a backhaul, base station 11, which is equivalent to a host station, can also be referred to as an Integrated Access Backhaul (IAB) donor, and base station 12, which is equivalent to a relay station, can also be referred to as an IAB node.

[0849] Base station 10 may also be connected to core network 30 via other base stations 10 or directly. Core network 30 may include, for example, at least one of Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), etc.

[0850] The core network 30 may also include, for example, user plane functions (UPF), access and mobility management functions (AMF), session management functions (SMF), unified data management (UDM), application functions (AF), data network (DN), location management functions (LMF), and network functions (NF) such as operation, administration and maintenance (OAM). Alternatively, multiple functions can be provided through a single network node. Furthermore, communication with external networks (e.g., the Internet) can also be achieved via the DN.

[0851] User terminal 20 can also be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.

[0852] In wireless communication system 1, wireless access methods based on Orthogonal Frequency Division Multiplexing (OFDM) can also be used. For example, in at least one of the downlink (DL) and uplink (UL) links, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), and Single Carrier Frequency Division Multiple Access (SC-FDMA) can also be used.

[0853] The wireless access method can also be referred to as a waveform. In addition, in the wireless communication system 1, other wireless access methods (e.g., other single-carrier transmission methods, other multi-carrier transmission methods) can also be used in the wireless access methods of UL and DL.

[0854] As a downlink channel, the wireless communication system 1 can also use downlink shared channels (Physical Downlink Shared Channel (PDSCH)), broadcast channels (Physical Broadcast Channel (PBCH)), downlink control channels (Physical Downlink Control Channel (PDCCH)) and so on, which are shared among the user terminals 20.

[0855] In addition, as uplink channels, the wireless communication system 1 may also use uplink shared channels (Physical Uplink Shared Channel (PUSCH)), uplink control channels (Physical Uplink Control Channel (PUCCH)), random access channels (Physical Random Access Channel (PRACH)) and so on, which are shared by each user terminal 20.

[0856] User data, high-level control information, and System Information Blocks (SIBs) are transmitted via the PDSCH. User data and high-level control information can also be transmitted via the PUSCH. In addition, Master Information Blocks (MIBs) can also be transmitted via the PBCH.

[0857] Lower-layer control information can also be transmitted via PDCCH. This lower-layer control information may include, for example, downlink control information (DCI), which includes scheduling information for at least one of PDSCH and PUSCH.

[0858] Additionally, the DCI that schedules PDSCH can also be called DL allocation, DL DCI, etc., and the DCI that schedules PUSCH can also be called UL authorization, UL DCI, etc. Furthermore, PDSCH can be rewritten as DL data, and PUSCH can be rewritten as UL data.

[0859] In PDCCH detection, a Control Resource Set (CORESET) and a search space can also be utilized. A CORESET corresponds to the resources used to search for DCIs. The search space corresponds to the search area and search method for PDCCH candidates. A CORESET can also be associated with one or more search spaces. The UE can also monitor CORESETs associated with a specific search space based on search space settings.

[0860] A search space can also correspond to a PDCCH candidate corresponding to one or more aggregation levels. One or more search spaces can also be referred to as a search space set. In addition, the terms "search space", "search space set", "search space setting", "search space set setting", "CORESET", and "CORESET setting" in this disclosure can be rewritten interchangeably.

[0861] The PUCCH can also transmit uplink control information (uplink control information (UCI)) that includes at least one of the following: Channel State Information (CSI), delivery confirmation information (e.g., also known as Hybrid Automatic Repeat Request ACK Knowledge (HARQ-ACK), ACK / NACK, etc.), and Scheduling Request (SR). The PRACH can also transmit random access preambles used for establishing connections with the cell.

[0862] In addition, in this disclosure, downlink, uplink, etc., may be described without the word "link". Furthermore, various channels may be described without the word "physical".

[0863] In wireless communication system 1, synchronization signals (SS) and downlink reference signals (DL-RS) can also be transmitted. In wireless communication system 1, DL-RS can also transmit cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), positioning reference signals (PRS), and phase tracking reference signals (PTRS).

[0864] Synchronization signals can be, for example, at least one of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS). A signal block containing SS (PSS, SSS) and PBCH (and DMRS for PBCH) can also be called an SS / PBCH block, SS block (SSB), etc. In addition, SS, SSB, etc. can also be called reference signals.

[0865] Furthermore, in wireless communication system 1, the uplink reference signal (UL-RS) can also transmit measurement reference signals (sounding reference signals (SRS)) and demodulation reference signals (DMRS). Additionally, DMRS can also be referred to as user terminal-specific reference signals (UE-specific reference signals).

[0866] (Base station)

[0867] Figure 35This diagram illustrates an example of the structure of a base station according to one embodiment. The base station 10 includes a control unit 110, a transmit / receive unit 120, a transmit / receive antenna 130, and a transmission path interface (transmission line interface) 140. Alternatively, the control unit 110, the transmit / receive unit 120, the transmit / receive antenna 130, and the transmission path interface 140 may each be provided in more than one manner.

[0868] Furthermore, while this example primarily illustrates the functional blocks of the characteristic portions of this embodiment, it can also be envisioned that the base station 10 also possesses other functional blocks required for wireless communication. Some of the processing of each unit described below may also be omitted.

[0869] The control unit 110 performs overall control of the base station 10. The control unit 110 can be composed of a controller, control circuit, etc., which are described based on common knowledge in the art to which this disclosure pertains.

[0870] The control unit 110 can also control signal generation and scheduling (e.g., resource allocation, mapping). The control unit 110 can also control transmission, reception, and measurement using the transmit / receive unit 120, transmit / receive antenna 130, and transmission path interface 140. The control unit 110 can also generate data, control information, sequences, etc., to be transmitted as signals and forward them to the transmit / receive unit 120. The control unit 110 can also perform call processing (setting, releasing, etc.) of the communication channel, status management of the base station 10, and management of wireless resources.

[0871] The transmitting / receiving unit 120 may also include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may also include a transmitting processing unit 1211 and a receiving processing unit 1212. The transmitting / receiving unit 120 may be composed of transmitters / receivers, RF circuits, baseband circuits, filters, phase shifters, measurement circuits, transmitting / receiving circuits, etc., as described based on common knowledge in the art to which this disclosure pertains.

[0872] The transmitting and receiving unit 120 can be configured as a single integrated transmitting and receiving unit, or it can be composed of a transmitting unit and a receiving unit. The transmitting unit can also be composed of a transmitting processing unit 1211 and an RF unit 122. The receiving unit can also be composed of a receiving processing unit 1212, an RF unit 122, and a measurement unit 123.

[0873] The transmitting and receiving antenna 130 can be constructed from an antenna, such as an array antenna, as described based on common knowledge in the art to which this disclosure pertains.

[0874] The transmitting / receiving unit 120 can also transmit the aforementioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 120 can also receive the aforementioned uplink channel, uplink reference signal, etc.

[0875] The transmitting and receiving unit 120 may also use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc., to form at least one of the transmitting beam and the receiving beam.

[0876] The transmitting and receiving unit 120 (transmitting processing unit 1211) may, for example, perform processing at the Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer (e.g., RLC retransmission control), and Medium Access Control (MAC) layer (e.g., HARQ retransmission control) on the data and control information obtained from the control unit 110, and generate a bit string to be transmitted.

[0877] The transmitting and receiving unit 120 (transmitting processing unit 1211) can also perform transmission processing such as channel coding (which may also include error correction coding), modulation, mapping, filter processing (filtering processing), Discrete Fourier Transform (DFT) processing (as needed), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output the baseband signal.

[0878] The transmitting and receiving unit 120 (RF unit 122) can also perform modulation, filtering, amplification, etc. on the baseband signal to the wireless frequency band, and transmit the wireless frequency band signal through the transmitting and receiving antenna 130.

[0879] On the other hand, the transmitting and receiving unit 120 (RF unit 122) can also amplify, filter, and demodulate the signals of the wireless frequency band received through the transmitting and receiving antenna 130 into the baseband signal.

[0880] The transmitting and receiving unit 120 (receiving and processing unit 1212) can also perform receiving and processing on the acquired baseband signal, including analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, to acquire user data.

[0881] The transmitting / receiving unit 120 (measurement unit 123) can also perform measurements related to the received signal. For example, the measurement unit 123 can also perform radio resource management (RRM) measurements, channel state information (CSI) measurements, etc., based on the received signal. The measurement unit 123 can also 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 can also be output to the control unit 110.

[0882] The transmission path interface 140 can also transmit and receive signals (backhaul signaling) between the device included in the core network 30 (e.g., the network node providing the NF), other base stations 10, etc., and can also acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

[0883] In addition, the transmitting unit and receiving unit of the base station 10 in this disclosure may also be composed of at least one of a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission path interface 140.

[0884] The transmitting / receiving unit 120 can also transmit Radio Resource Control (RRC) settings related to cells whose physical range has been changed. The control unit 110 can also use the RRC settings to give instructions related to handover operations between the multiple cells (Embodiment 0).

[0885] The transmitting / receiving unit 120 can also transmit trigger information related to handover. The control unit 110 can also use the trigger information to instruct at least one of uplink synchronization and downlink synchronization for a cell whose physical range has been changed (first / fourth embodiment).

[0886] The transmitting / receiving unit 120 can also transmit settings for trigger conditions related to handover of cells with changed physical ranges. The control unit 110 can also control the reception of handover-related reports transmitted based on the trigger conditions (second embodiment).

[0887] The transmit / receive unit 120 may also transmit a Medium Access Control (MAC) element for activating at least one of the following for a second cell whose physical range has been changed: a first cell whose physical range has not been changed, a group of the first cells, a transmit / receive point constituting the second cell, a synchronization signal transmitted within the second cell, and the second cell. The control unit 110 may also use the MAC control element to indicate at least one of the following: activation of the first cell, activation of the group of the first cells, activation of the transmit / receive point, activation of the synchronization signal, and activation of the second cell (third embodiment).

[0888] The sending and receiving unit 120 can also send a trigger indication for switching based on the terminal's location information, or receive a notification that the switching has been triggered. The control unit 110 can also determine the switching operation based on the trigger indication or the notification (fifth embodiment).

[0889] (User terminal)

[0890] Figure 36 This diagram illustrates an example of the structure of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Alternatively, more than one of each of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may be included.

[0891] Furthermore, while this example primarily illustrates the functional blocks of the characteristic portions of this embodiment, it is also conceivable that the user terminal 20 may also have other functional blocks required for wireless communication. Some of the processing of each unit described below may also be omitted.

[0892] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., which are described based on common knowledge in the technical field to which this disclosure pertains.

[0893] The control unit 210 can also control signal generation, mapping, etc. The control unit 210 can also control transmission, reception, measurement, etc., using the transmission / reception unit 220 and the transmission / reception antenna 230. The control unit 210 can also generate data, control information, sequences, etc., to be transmitted as signals and forward them to the transmission / reception unit 220.

[0894] The transmitting / receiving unit 220 may also include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may also include a transmitting processing unit 2211 and a receiving processing unit 2212. The transmitting / receiving unit 220 may be composed of transmitters / receivers, RF circuits, baseband circuits, filters, phase shifters, measurement circuits, transmitting / receiving circuits, etc., as described based on common knowledge in the art to which this disclosure pertains.

[0895] The transmitting and receiving unit 220 can be configured as a single integrated transmitting and receiving unit, or it can be composed of a transmitting unit and a receiving unit. The transmitting unit can also be composed of a transmitting processing unit 2211 and an RF unit 222. The receiving unit can also be composed of a receiving processing unit 2212, an RF unit 222, and a measurement unit 223.

[0896] The transmitting and receiving antenna 230 can be constructed from an antenna, such as an array antenna, as described based on common knowledge in the art to which this disclosure pertains.

[0897] The transmitting / receiving unit 220 can also receive the downlink channel, synchronization signal, downlink reference signal, etc., mentioned above. The transmitting / receiving unit 220 can also transmit the uplink channel, uplink reference signal, etc., mentioned above.

[0898] The transmitting and receiving unit 220 may also use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc., to form at least one of the transmitting beam and the receiving beam.

[0899] The transmitting and receiving unit 220 (transmitting processing unit 2211) may, for example, perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control) on the data and control information obtained from the control unit 210, and generate the bit string to be transmitted.

[0900] The transmitting and receiving unit 220 (transmitting processing unit 2211) can also perform channel coding (which may include error correction coding), modulation, mapping, filter processing, DFT processing (as needed), IFFT processing, precoding, digital-to-analog conversion and other transmission processing on the bit string to be transmitted, and output the baseband signal.

[0901] Furthermore, whether or not to apply DFT processing can be based on the settings of transform precoding. For a certain channel (e.g., PUSCH), if transform precoding is enabled, the transmit / receive unit 220 (transmit processing unit 2211) can perform DFT processing as described above in order to transmit the channel using the DFT-s-OFDM waveform. If not, the transmit / receive unit 220 (transmit processing unit 2211) can perform the above transmission processing without performing DFT processing.

[0902] The transmitting and receiving unit 220 (RF unit 222) can also perform modulation, filtering, amplification, etc. on the baseband signal to the wireless frequency band, and transmit the wireless frequency band signal through the transmitting and receiving antenna 230.

[0903] On the other hand, the transmitting and receiving unit 220 (RF unit 222) can also amplify, filter, demodulate, etc., the signals of the wireless frequency band received by the transmitting and receiving antenna 230.

[0904] The transmitting and receiving unit 220 (receiving and processing unit 2212) can also perform receiving and processing on the acquired baseband signal, such as analog-to-digital conversion, FFT processing, IDFT processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, to acquire user data.

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

[0906] Additionally, the measurement unit 223 can also derive channel measurements for CSI calculation based on channel measurement resources. Channel measurement resources can be, for example, non-zero power (NZP) CSI-RS resources. Furthermore, the measurement unit 223 can also derive interference measurements for CSI calculation based on interference measurement resources. Interference measurement resources can be at least one of NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, etc. Additionally, CSI-IM can also be referred to as CSI-Interference Management (IM), and can be interchanged with zero power (ZP) CSI-RS. Furthermore, in this disclosure, CSI-RS, NZPCSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc., can also be interchanged.

[0907] Alternatively, the transmitting and receiving units of the user terminal 20 in this disclosure may also be composed of at least one transmitting / receiving unit 220 and transmitting / receiving antenna 230.

[0908] The transmitting / receiving unit 220 can also receive Radio Resource Control (RRC) settings related to cells whose physical range has been changed. The control unit 210 can also control handover operations between multiple cells based on the RRC settings (Embodiment 0).

[0909] Alternatively, a Physical Cell Identifier (PCI) associated with a cell whose physical extent has not been changed may correspond to a cell whose physical extent has been changed (Implementation 0).

[0910] Alternatively, multiple Physical Cell Identifiers (PCIs) associated with a cell whose physical extent has not been changed may correspond to a cell whose physical extent has been changed (Implementation 0).

[0911] The RRC setting may also include at least one of the following: the identifier of the cell whose physical range has been changed, the identifier of the cell whose physical range has not been changed, the identifier of the serving cell, the index of the transmitting and receiving point, and the index of the reference signal (Embodiment 0).

[0912] The transmitting and receiving unit 220 can also receive trigger information related to handover. The control unit 210 can also control at least one of uplink synchronization and downlink synchronization for cells whose physical range has been changed (first / fourth embodiment) based on the trigger information.

[0913] The triggering information can also be sent using Radio Resource Control (RRC) (first implementation).

[0914] The triggering information can also be sent using a specific Medium Access Control (MAC) element (first implementation).

[0915] The triggering information can also be sent using downlink control information (first implementation).

[0916] The control unit 210 may also determine whether to perform a handover-related operation based on triggering conditions related to handover for cells whose physical range has been changed. If the handover operation is performed, the transmitting / receiving unit 220 may also send a handover-related report (second embodiment).

[0917] The triggering conditions can also be reset using Radio Resource Control (RRC) (second implementation).

[0918] The handover-related reports may also be sent using specific Media Access Control (MAC) elements or uplink control information (second implementation).

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

[0920] The transmit / receive unit 220 may also receive a Medium Access Control (MAC) element for activating at least one of the following for a second cell whose physical range has been changed: a first cell whose physical range has not been changed, a group of the first cells, a transmit / receive point constituting the second cell, a synchronization signal transmitted within the second cell, and the second cell. The control unit 210 may also determine, based on the MAC control element, at least one of the following: activation of the first cell, activation of the group of the first cells, activation of the transmit / receive point, activation of the synchronization signal, and activation of the second cell (third embodiment).

[0921] The MAC control element may also be in bitmap form to indicate at least one of the following: activation of the first cell, activation of the group of the first cell, activation of the transmit / receive point, activation of the synchronization signal, and activation of the second cell (third embodiment).

[0922] The MAC control element may also include at least one of the following: the identifier of the first cell, the identifier of the group of the first cell, the identifier of the transmit / receive point, the index of the synchronization signal, and the identifier of the second cell (third embodiment).

[0923] When the first cell is activated by the MAC control element, the MAC control element may also include an identifier for the group of the first cell. When the transmit / receive point is activated by the MAC control element, the MAC control element may also include an identifier for the group of the first cell and an identifier for the first cell. When the synchronization signal is activated by the MAC control element, the MAC control element may also include an identifier for the group of the first cell, an identifier for the first cell, and an identifier for the transmit / receive point (third embodiment).

[0924] The transmitting and receiving unit 220 can also receive a trigger indication for switching based on the terminal's location information, or send a notification that the switching has been triggered. The control unit 210 can also control the switching operation based on the trigger indication or the notification (fifth embodiment).

[0925] The trigger indication may also be sent based on the location information of the terminal measured by the network or the terminal (fifth embodiment).

[0926] The notification can also be sent to the cell before the handover or the cell after the handover (fifth implementation).

[0927] The control unit 210 can also control the switching operation based on the location information of the terminal based on one or more reference points and one or more conditions corresponding to the reference points (fifth embodiment).

[0928] (Hardware structure)

[0929] Furthermore, the block diagrams used in the description of the above embodiments illustrate functional units. These functional blocks (structural units) are implemented through any combination of at least one of hardware and software. Moreover, the implementation method of each functional block is not particularly limited. That is, each functional block can be implemented using a single device that is physically or logically combined, or it can be implemented by directly or indirectly (e.g., using wired, wireless, etc.) connecting two or more physically or logically separate devices. A functional block can also be implemented by combining the aforementioned single device or multiple devices with software.

[0930] Here, the functions include judgment, decision, determination, calculation, calculation, processing, export, investigation, search, confirmation, receiving, sending, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, regard as, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning, but are not limited to these. For example, a functional block (structural unit) that implements the sending function can also be called a transmitting unit, transmitter, etc. Each of these, as described above, is not particularly limited in its implementation method.

[0931] For example, in one embodiment of this disclosure, the base station, user terminal, etc., can also function as a computer for processing the wireless communication method of this disclosure. Figure 37 This is a diagram illustrating an example of the hardware structure of a base station and a user terminal according to one embodiment. The base station 10 and the user terminal 20 described above can also be physically configured as a computer device including a processor 1001, a memory 1002, a storage device 1003, a communication device 1004, an input device 1005, an output device 1006, and a bus 1007, etc.

[0932] Furthermore, in this disclosure, terms such as apparatus, circuit, device, section, and unit can be interchanged. The hardware structure of base station 10 and user terminal 20 can be configured to include one or more of the apparatuses shown in the figures, or it can be configured not to include any of the apparatuses.

[0933] For example, only one processor 1001 is shown, but there can be multiple processors. Furthermore, processing can be performed by one processor, or simultaneously, sequentially, or by two or more processors using other methods. Additionally, processor 1001 can be implemented using more than one chip.

[0934] Regarding the functions in base station 10 and user terminal 20, for example, by reading specific software (programs) into hardware such as processor 1001 and memory 1002, so that processor 1001 performs calculations and controls communication via communication device 1004, or by controlling at least one of reading and writing data in memory 1002 and storage device 1003.

[0935] The processor 1001 enables the operating system to operate and control the computer as a whole. The processor 1001 may also be a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic devices, registers, etc. For example, at least a portion of the control unit 110 (210), the transmit / receive unit 120 (220), etc., described above may also be implemented by the processor 1001.

[0936] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and performs various processes accordingly. As a program, a program that causes the computer to perform at least a portion of the operations described in the above embodiments can be used. For example, the control unit 110 (210) can also be implemented by a control program stored in the memory 1002 and operated in the processor 1001; similar implementations can be made for other functional blocks.

[0937] The memory 1002 may also be a computer-readable recording medium, such as being composed of at least one of a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), or other suitable storage media. The memory 1002 may also be referred to as a register, cache, main memory (main storage device), etc. The memory 1002 is capable of storing executable programs (program code), software modules, etc., for implementing the wireless communication method according to an embodiment of this disclosure.

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

[0939] The communication device 1004 is hardware (transmitting and receiving device) used for communication between computers via at least one of a wired network and a wireless network. It is also referred to as a network device, network controller, network interface card (NIC), communication module, etc. To implement at least one of, for example, Frequency Division Duplex (FDD) and Time Division Duplex (TDD), the communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. For example, the aforementioned transmit / receive unit 120 (220) and transmit / receive antenna 130 (230) may also be implemented by the communication device 1004. The transmit / receive unit 120 (220) may also be implemented by physically or logically separating the transmit unit 120a (220a) and the receive unit 120b (220b).

[0940] Input device 1005 is an input device that receives input from external sources (e.g., keyboard, mouse, microphone, switch, button, sensor, etc.). Output device 1006 is an output device that performs output to external sources (e.g., display, speaker, light-emitting diode (LED) lamp, etc.). Alternatively, input device 1005 and output device 1006 can also be an integrated structure (e.g., a touch panel).

[0941] Furthermore, the processor 1001, memory 1002, and other devices are connected via a bus 1007 for communicating information. The bus 1007 can be configured as a single bus or as different buses between the devices.

[0942] Furthermore, the base station 10 and the user terminal 20 can also 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 can also use this hardware to implement part or all of the functional blocks. For example, the processor 1001 can also be implemented using at least one of these hardware components.

[0943] (Modified example)

[0944] Furthermore, the terms described in this disclosure, as well as those necessary for understanding this disclosure, may be replaced with terms that have the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) may be interchanged. Additionally, a signal may also be a message. A reference signal can also be abbreviated as RS, and may be referred to as pilot, pilot signal, etc., depending on the applied standard. Furthermore, a component carrier (CC) may also be referred to as cell, frequency carrier, carrier frequency, etc.

[0945] A radio frame can also be composed of one or more periods (frames) in the time domain. Each of these periods (frames) that constitute a radio frame can also be called a subframe. Furthermore, a subframe can also be composed of one or more time slots in the time domain. A subframe can also be a fixed time length (e.g., 1 ms) independent of the parameter set (numerology).

[0946] Here, the parameter set can also be communication parameters applied in at least one of the transmission and reception of a signal or channel. For example, the parameter set can also represent 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 structure, specific filtering processing performed by the transmitter and receiver in the frequency domain, and specific windowing processing performed by the transmitter and receiver in the time domain.

[0947] In the time domain, a time slot can also be composed of one or more symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.). In addition, a time slot can also be a time unit based on a set of parameters.

[0948] A time slot can also contain multiple mini-time slots. Each mini-time slot can also consist of one or more symbols in the time domain. Furthermore, a mini-time slot can also be called a sub-time slot. A mini-time slot can also consist of fewer symbols than a time slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-time slot can also be called PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using mini-time slots can also be called PDSCH (PUSCH) mapping type B.

[0949] Radio frames, subframes, time slots, mini-time slots, and symbols all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-time slots, and symbols can also use their respective other names. Furthermore, the time units such as frames, subframes, time slots, mini-time slots, and symbols in this disclosure can be interchanged.

[0950] For example, a subframe can also be called a TTI, multiple consecutive subframes can also be called a TTI, and a time slot or a mini-time slot can also be called a TTI. That is, at least one of a subframe and a TTI can be a subframe in existing LTE (1ms), a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. In addition, the unit representing TTI may not be called a subframe, but rather a time slot, mini-time slot, etc.

[0951] Here, TTI refers, for example, to the smallest unit of time for scheduling in wireless communication. For instance, in an LTE system, the base station schedules radio resources (frequency bandwidth, transmit power, etc., available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0952] TTI can also be a unit of time for transmitting channel-coded data packets (transmission blocks), code blocks, codewords, etc., and can also be a unit of processing such as scheduling and link adaptation. In addition, when a TTI is given, the actual time interval (e.g., the number of symbols) mapped to transmission blocks, code blocks, codewords, etc. can be shorter than the TTI.

[0953] Additionally, where a time slot or a mini-time slot is referred to as a TTI, more than one TTI (i.e., more than one time slot or more than one mini-time slot) can also serve as the minimum time unit for scheduling. Furthermore, the number of time slots (mini-time slots) constituting the minimum time unit of the schedule can also be controlled.

[0954] A TTI with a duration of 1ms can also be referred to as a normal TTI (TTI in 3GPPRel.8-12), a standard TTI, a long TTI, a normal subframe, a standard subframe, a long subframe, a time slot, etc. A TTI shorter than a normal TTI can also be referred to as a shortened TTI, a short TTI, a partial TTI (partial or fractional TTI), a shortened subframe, a short subframe, a mini time slot, a sub-time slot, a time slot, etc.

[0955] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) can also be rewritten as a TTI with a duration of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) can also be rewritten as a TTI with a duration of less than a long TTI but more than 1 ms.

[0956] A resource block (RB) is a unit of resource allocation in both the time and frequency domains. In the frequency domain, it can also contain one or more consecutive subcarriers. The number of subcarriers in an RB can be the same regardless of the parameter set, for example, it can be 12. The number of subcarriers in an RB can also be determined based on the parameter set.

[0957] Furthermore, an RB can contain one or more symbols in the time domain, and can also be a time slot, a mini-time slot, a subframe, or the length of a TTI. A TTI, a subframe, etc., can also be composed of one or more resource blocks.

[0958] In addition, one or more RBs can also be referred to as Physical Resource Blocks (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

[0959] In addition, a resource block can also consist of one or more resource elements (REs). For example, an RE can also be a radio resource area consisting of a subcarrier and a symbol.

[0960] The Bandwidth Part (BWP) (also referred to as partial bandwidth, etc.) can also represent a subset of consecutive common resource blocks (RBs) used for a certain parameter set in a certain carrier. Here, common RBs can also be determined by the index of RBs based on the common reference point of the carrier. PRBs can also be defined in a BWP and appended with numbers within that BWP.

[0961] A BWP can also include a UL BWP (the BWP used by UL) and a DL BWP (the BWP used by DL). For a UE, one or more BWPs can also be set within a single carrier.

[0962] At least one of the configured BWPs can be active, and the UE may not intend to transmit or receive specific signals / channels outside of the active BWPs. Additionally, terms such as "cell" and "carrier" in this disclosure may be replaced with "BWP".

[0963] Furthermore, the structures described above, such as radio frames, subframes, time slots, mini-time slots, and symbols, are merely illustrative. For example, the number of subframes contained in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-time slots contained within a time slot, the number of symbols and RBs contained in a time slot or mini-time slot, the number of subcarriers contained in an RB, and the number of symbols in a TTI, symbol length, and cyclic prefix (CP) length can be varied in many ways.

[0964] Furthermore, the information, parameters, etc., described in this disclosure can be represented by absolute values, relative values ​​with respect to a specific value, or other corresponding information. For example, wireless resources can also be indicated by a specific index.

[0965] In this disclosure, the names used for parameters, etc., are not limiting names in any respect. Furthermore, the mathematical expressions, etc., using these parameters may differ from those explicitly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name; therefore, the various names assigned to these various channels and information elements are not limiting names in any respect.

[0966] The information, signals, etc., described in this disclosure can also be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc., which may be mentioned throughout the above description, can also be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination thereof.

[0967] Furthermore, information, signals, etc., can be output in at least one of the following directions: from higher level (upper layer) to lower level (lower layer), and from lower layer to higher level. Information, signals, etc., can also be input and output via multiple network nodes.

[0968] Input and output information, signals, etc., can be stored in a specific location (e.g., memory) or managed using a management table. Input and output information, signals, etc., can be overwritten, updated, or appended. Output information, signals, etc., can also be deleted. Input information, signals, etc., can also be sent to other devices.

[0969] The notification of information is not limited to the methods / implementations described in this disclosure, and may also be carried out by other methods. For example, the notification of information in this disclosure may also be implemented by physical layer signaling (e.g., downlink control information (DCI), uplink control information (UCI), etc.), 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 combinations thereof.

[0970] In addition, physical layer signaling can also be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. Furthermore, RRC signaling can also be referred to as RRC messages, such as RRC connection setup messages, RRC connection reconfiguration messages, etc. Additionally, MAC signaling can also be notified using, for example, the MAC control element (CE).

[0971] Furthermore, notification of specific information (e.g., a notification of “is X”) is not limited to explicit notification, but can also be implicit (e.g., by not providing that specific information, or by providing other information).

[0972] The determination can be made by a value represented by a single bit (0 or 1), by a true or false value (boolean), or by a comparison of values ​​(e.g., by comparison with a specific value).

[0973] Whether software is called software, firmware, middleware, microcode, hardware description language, or any other name, it should be broadly interpreted to refer to instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc.

[0974] Furthermore, software, instructions, and information can also be sent and received via a transmission medium. For example, when software is sent from a website, server, or other remote source using at least one of wired technologies (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL) etc.) and wireless technologies (infrared, microwave, etc.), at least one of these wired and wireless technologies is included within the definition of a transmission medium.

[0975] The terms “system” and “network” as used in this disclosure are interchangeable. “Network” may also mean devices included in a network (e.g., base stations).

[0976] In this disclosure, the terms “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”, “beamwidth”, “beam angle”, “antenna”, “antenna element”, “panel”, “UE panel”, “transmitting entity”, and “receiving entity” are used interchangeably.

[0977] Furthermore, in this disclosure, the antenna port can also be rewritten with an antenna port used for any signal / channel (e.g., a DeModulation Reference Signal (DMRS) port). In this disclosure, resources can also be rewritten with resources used for any signal / channel (e.g., reference signal resources, SRS resources, etc.). Additionally, resources can also include time / frequency / code / space / power resources. Moreover, the spatial domain transmission filter can also include at least one of a spatial domain transmission filter and a spatial domain reception filter.

[0978] The aforementioned groups may include, for example, at least one of the following: spatial relation group, code division multiplexing (CDM) group, reference signal (RS) group, control resource set (CORESET) group, PUCCH group, antenna port group (e.g., DMRS port group), layer group, resource group, beam group, antenna group, panel group, etc.

[0979] Furthermore, in this disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, Codeword (CW), Transport Block (TB), RS, etc., can also be rewritten to each other.

[0980] Furthermore, in this disclosure, the TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, and joint TCI state can also be rewritten to each other.

[0981] Furthermore, in this disclosure, terms such as "QCL", "QCL concept", "QCL relationship", "QCL type information", "QCL property (QCLproperty / properties)", "specific QCL type (e.g., type A, type D) property", and "specific QCL type (e.g., type A, type D)" can be rewritten interchangeably.

[0982] In this disclosure, indexes, identifiers (IDs), indicators, indications, resource IDs, etc., can be interchanged. Sequences, lists, sets, groups, clusters, subsets, etc., can also be interchanged.

[0983] Furthermore, the spatial relationship information Identifier (ID) (TCI state ID) and spatial relationship information (TCI state) can be interchanged. "Spatial relationship information (TCI state)" can also be interchanged with "a set of spatial relationship information (TCI states)," "one or more spatial relationship information," etc. TCI state and TCI can also be interchanged. Spatial relationship information and spatial relationships can also be interchanged.

[0984] In this disclosure, the terms "Base Station (BS)", "Wireless Base Station", "Fixed Station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "Access Point", "Transmission Point (TP)", "Reception Point (RP)", "Transmission / Reception Point (TRP)", "Panel", "Cell", "Sector", "Cell Group", "Carrier", and "Component Carrier" are used interchangeably. There are also instances where the terms macro cell, small cell, femtocell, and picocell are used to refer to a base station.

[0985] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, its overall coverage area can be divided into several smaller areas, each of which can also provide communication services through a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). Terms such as "cell" or "sector" refer to a portion or all of the coverage area of ​​at least one of the base station and base station subsystem providing communication services within that coverage area.

[0986] In this disclosure, the act of a base station sending information to a terminal can also be rewritten in relation to the act of the base station instructing the terminal to perform control / operation based on that information.

[0987] In this disclosure, the terms “Mobile Station (MS)”, “user terminal”, “user equipment (UE)”, and “terminal” are used interchangeably.

[0988] There are also instances where mobile stations are referred to as subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, handsets, user agents, mobile clients, clients, or several other appropriate terms.

[0989] At least one of the base station and the mobile station can also be referred to as a transmitting device, a receiving device, a wireless communication device, etc. Additionally, at least one of the base station and the mobile station can also be a device mounted on a moving object, the moving object itself, etc.

[0990] The term "mobile body" refers to a movable object whose speed is arbitrary, including when the object is stationary. Examples of such mobile bodies include vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships (ships and other watercraft), airplanes, rockets, artificial satellites, drones, multicopters, quadcopters, hot air balloons, and objects carried on them, but are not limited to these. Furthermore, the mobile body can also be a mobile body that moves autonomously based on operational commands.

[0991] The mobile entity can be a means of transportation (e.g., a vehicle, an airplane, etc.), a mobile entity moving in an unmanned manner (e.g., a drone, an autonomous vehicle, etc.), or a robot (humanized or unmanned). Additionally, at least one of the base station and the mobile station also includes a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station can also be an Internet of Things (IoT) device such as a sensor.

[0992] Figure 38 This diagram illustrates an example of a vehicle according to one embodiment. The vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, an electronic control unit 49, various sensors (including a current sensor 50, a speed sensor 51, a 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.

[0993] The drive unit 41 is comprised of at least one of an engine, a motor, or a combination of an engine and a motor. The steering unit 42 is configured to include at least a steering wheel (also called a steering handle) that steers at least one of the front wheels 46 and the rear wheels 47 based on operation of the steering wheel by the user.

[0994] The electronic control unit 49 consists of a microprocessor 61, a memory (ROM, RAM) 62, and a communication port (e.g., an input / output (IO) port) 63). Signals from various sensors 50-58 present in the vehicle are input to the electronic control unit 49. The electronic control unit 49 can also be referred to as an electronic control unit (ECU).

[0995] The signals from various sensors 50-58 include the following: current signal from current sensor 50 sensing the current of the motor; rotational speed signal of the front wheel 46 / rear wheel 47 obtained by speed sensor 51; air pressure signal of the front wheel 46 / rear wheel 47 obtained by air pressure sensor 52; vehicle speed signal obtained by vehicle speed sensor 53; acceleration signal obtained by acceleration sensor 54; accelerator pedal 43 depress amount signal obtained by accelerator pedal sensor 55; brake pedal 44 depress amount signal obtained by brake pedal sensor 56; shift lever 45 operation signal obtained by shift lever sensor 57; and detection signal obtained by object detection sensor 58 for detecting obstacles, vehicles, pedestrians, etc.

[0996] The information service unit 59 comprises various devices such as a navigation system, audio system, speakers, display, television, and radio, used to provide (output) 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 obtained 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.

[0997] The information service unit 59 may include input devices (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) that accept input from the outside, and output devices (e.g., display, speaker, LED light, touch panel, etc.) that implement output to the outside.

[0998] The driver assistance system unit 64 comprises various devices used to provide functions for preventing accidents or reducing the driver's workload, such as millimeter-wave radar, light detection and ranging (LiDAR), cameras, positioning detectors (e.g., Global Navigation Satellite System (GNSS), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyroscope systems (e.g., Inertial Measurement Unit (IMU), Inertial Navigation System (INS)), artificial intelligence (AI) chips, and AI processors, and one or more ECUs that control these devices. Furthermore, the driver assistance system unit 64 sends and receives various information via communication module 60 to realize driver assistance functions or autonomous driving functions.

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

[1000] The communication module 60 can be controlled by the microprocessor 61 of the electronic control unit 49 and is a communication device capable of communicating with external devices. For example, it can transmit and receive various types of information with external devices via wireless communication. The communication module 60 can be located both inside and outside the electronic control unit 49. The external device can be, for example, the aforementioned base station 10, user terminal 20, etc. Furthermore, the communication module 60 can be, for example, at least one of the aforementioned base station 10 and user terminal 20 (or it can function as at least one of the base station 10 and user terminal 20).

[1001] The communication module 60 can also wirelessly transmit at least one of the signals input to the electronic control unit 49 from the various sensors 50-58 described above, the information obtained based on these signals, and the information based on input from an external (user) source obtained via the information service unit 59 to an external device. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc., can also be referred to as input units that receive input. For example, the PUSCH transmitted via the communication module 60 can also contain information based on the aforementioned inputs.

[1002] The communication module 60 receives various information (traffic information, signal information, workshop information, etc.) sent from external devices and displays it on the vehicle's information service unit 59. The information service unit 59 can also be referred to as an output unit that outputs information (for example, outputs information to devices such as displays and speakers based on the PDSCH received by the communication module 60 (or the data / information decoded from the PDSCH).

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

[1004] Furthermore, the base station in this disclosure can also be rewritten as a user terminal. For example, various methods / implementations of this disclosure can be applied to structures where communication between the base station and the user terminal is replaced by communication between multiple user terminals (e.g., also referred to as device-to-device (D2D) or vehicle-to-everything (V2X)). In this case, it can also be configured such that the user terminal 20 has the functions of the base station 10 described above. In addition, terms such as "uplink" and "downlink" can be rewritten as terms corresponding to inter-terminal communication (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can also be rewritten as sidelink channel.

[1005] Similarly, the user terminal in this disclosure can also be rewritten as a base station. In this case, it can also be configured such that the base station 10 has the functions of the user terminal 20 described above.

[1006] In this disclosure, operations are assumed to be performed by the base station, and sometimes, depending on the circumstances, by its upper node. In a network containing one or more network nodes having a base station, the various operations performed for communication with a terminal can obviously be performed by the base station, one or more network nodes other than the base station (e.g., considering a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc., but not limited to these), or combinations thereof.

[1007] The various methods / implementations described in this disclosure can be used individually or in combination, and can be switched as needed during execution. Furthermore, the processing procedures, timing sequences, flowcharts, etc., of the various methods / implementations described in this disclosure can be rearranged as long as they do not contradict each other. For example, for the method described in this disclosure, the illustrated order is used to indicate various steps, but the order in which they are indicated is not limited.

[1008] The various methods / implementations described in this disclosure can also be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG, where x is, for example, an integer or a decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Futuregeneration Radio Access (FX), Global System for Mobile Communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE This includes 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-Wideband (UWB)), Bluetooth (registered trademark), systems utilizing other suitable wireless communication methods, and next-generation systems derived from, modified, generated, or specified based on these methods. Furthermore, multiple systems can be combined (e.g., LTE or LTE-A, combinations with 5G, etc.) for application.

[1009] As used in this disclosure, the term "based on" does not mean "based on only" unless otherwise specified. In other words, the term "based on" means both "based on only" and "based on at least".

[1010] Any reference to an element using the designations "first," "second," etc., as used in this disclosure does not comprehensively limit the quantity or order of these elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, reference to the first and second elements does not imply that only two elements may be used, or that the first element must take precedence over the second element in some form.

[1011] The term "determining" as used in this disclosure can encompass a wide variety of operations. For example, "determining" can also refer to judging, calculating, computing, processing, deriving, investigating, looking up (search, inquiry) (e.g., searching in a table, database or other data structure), and ascertaining.

[1012] In addition, "judgment (decision)" can also refer to receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, accessing (e.g., accessing data in memory), etc., as situations where "judgment (decision)" is performed.

[1013] Furthermore, "judgment (decision)" can also refer to situations where resolving, selecting, choosing, establishing, or comparing are considered as making a "judgment (decision)". That is, "judgment (decision)" can also refer to certain operations as making a "judgment (decision)". In this disclosure, "judgment (decision)" can also be rewritten in relation to the operations described above.

[1014] Furthermore, in this disclosure, "determine / determining" can also be interchanged with "assume / assuming," "expect / expecting," "consider / considering," etc. Additionally, in this disclosure, "not assuming to proceed..." can also be interchanged with "assuming not to proceed..."

[1015] In this disclosure, "expect" can also be interchanged with "be expected." For example, "expect(s)..." (where "..." can also be expressed using a that clause, to infinitive, etc.) can also be interchanged with "be expected...". "Does not expect..." can also be interchanged with "be not expected...". Furthermore, "An apparatus A is not expected..." can also be interchanged with "Apparatus B other than apparatus A does not expect..." (for example, if apparatus A is a UE, apparatus B can also be a base station).

[1016] The term "maximum transmit power" as used in this disclosure may refer to the maximum value of the transmit power, the nominal maximum transmit power (the nominal UE maximum transmit power), or the rated maximum transmit power (the rated UE maximum transmit power).

[1017] As used in this disclosure, the terms “connected,” “coupled,” or all variations thereof, refer to all direct or indirect connections or combinations between two or more elements, and can include cases where there is one or more intermediate elements between two mutually “connected” or “coupled” elements. The connections or combinations between elements can be physical, logical, or a combination thereof. For example, “connection” can also be rewritten as “access.”

[1018] In this disclosure, when two elements are connected, it is possible to consider using more than one wire, cable, printed electrical connection, etc. to be "connected" or "combined" with each other, and as several non-limiting and non-exclusive examples, to use electromagnetic energy with wavelengths having wireless frequency domain, microwave region, light (both visible and invisible) region to be "connected" or "combined" with each other.

[1019] In this disclosure, the term "A is different from B" can also mean "A and B are different from each other." Additionally, the term can also mean "A and B are each different from C." Terms such as "separate" and "combined" can also be interpreted in the same way as "different."

[1020] When the terms "include," "including," and variations thereof are used in this disclosure, these terms, like the term "comprising," mean inclusive. Furthermore, the term "or" as used in this disclosure does not mean XOR.

[1021] In this disclosure, for example, in cases where articles are added through translation, such as a, an, and the in English, the disclosure may also include cases where the noun following these articles is in a plural form.

[1022] In this disclosure, words such as "below," "less than," "above," "more than," and "equal to" can be interchanged. Furthermore, in this disclosure, words meaning "good," "bad," "large," "small," "high," "low," "early," "slow," "wide," and "narrow," etc., are not limited to the positive, comparative, and superlative degrees, and can be interchanged. Additionally, in this disclosure, words meaning "good," "bad," "large," "small," "high," "low," "early," "slow," "wide," and "narrow," etc., as expressions with "i" appended (i being any integer), are not limited to the positive, comparative, and superlative degrees, and can be interchanged (for example, "highest" can also be interchanged with "i-th highest").

[1023] In this disclosure, "of", "for", "regarding", "related to", "associated with", etc., can also be rewritten interchangeably.

[1024] In this disclosure, phrases such as "when A, B", "if A, then B", "B upon A", "B in response to A", "based on A", "B during / while A", "before A", "at the same time as / on A", "after A", "since A", and "until A" can be rewritten interchangeably. Furthermore, A and B can be replaced with nouns, gerunds, or ordinary sentences, depending on the context. Additionally, the time difference between A and B can be approximately 0 (immediately following or immediately preceding). Moreover, a time offset can be applied to the time A occurs. For example, "A" can be rewritten interchangeably with "before / after the time offset of A". This time offset (e.g., more than one symbol / slot) can be predetermined or determined by the UE based on the information it is notified of.

[1025] In this disclosure, timing, moment, time, time instance, arbitrary time unit (e.g., time slot, sub-time slot, symbol, subframe), period, opportunity, resource, etc., can also be overridden.

[1026] The inventions involved in this disclosure have been described in detail above. However, it will be apparent to those skilled in the art that the inventions involved in this disclosure are not limited to the embodiments described herein.

Claims

1. A terminal, comprising: The receiving unit receives Radio Resource Control (RRC) settings related to the cell whose physical range has been changed; and The control unit, based on the RRC settings, controls the handover operations between multiple cells.

2. The terminal according to claim 1, wherein, A Physical Cell Identifier (PCI) associated with a cell whose physical extent has not been changed corresponds to a cell whose physical extent has been changed.

3. The terminal according to claim 1, wherein, Multiple Physical Cell Identifiers (PCIs) associated with a cell whose physical extent has not been changed correspond to a cell whose physical extent has been changed.

4. The terminal according to claim 1, wherein, The RRC settings include at least one of the following: the identifier of the cell whose physical range has been changed, the identifier of the cell whose physical range has not been changed, the identifier of the serving cell, the index of the transmitting and receiving point, and the index of the reference signal.

5. A wireless communication method for a terminal, comprising: The steps for receiving Radio Resource Control (RRC) settings related to a cell whose physical range has been changed; and Based on the RRC settings, the steps for controlling handover operations between multiple cells are described.

6. A base station, comprising: The transmitting unit transmits Radio Resource Control (RRC) settings related to cells whose physical range has been changed; and The control unit, using the RRC settings, gives instructions related to handover operations between the multiple cells.

Images