[go: up one dir, main page]

WO2025141793A1 - Terminal, procédé de communication sans fil et station de base - Google Patents

Terminal, procédé de communication sans fil et station de base Download PDF

Info

Publication number
WO2025141793A1
WO2025141793A1 PCT/JP2023/047001 JP2023047001W WO2025141793A1 WO 2025141793 A1 WO2025141793 A1 WO 2025141793A1 JP 2023047001 W JP2023047001 W JP 2023047001W WO 2025141793 A1 WO2025141793 A1 WO 2025141793A1
Authority
WO
WIPO (PCT)
Prior art keywords
cell
handover
mac
area
configuration
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/JP2023/047001
Other languages
English (en)
Japanese (ja)
Inventor
守 奥村
祐輝 松村
聡 永田
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
NTT Docomo Inc
Original Assignee
NTT Docomo Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by NTT Docomo Inc filed Critical NTT Docomo Inc
Priority to PCT/JP2023/047001 priority Critical patent/WO2025141793A1/fr
Publication of WO2025141793A1 publication Critical patent/WO2025141793A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W16/00Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/02Resource partitioning among network components, e.g. reuse partitioning
    • H04W16/10Dynamic resource partitioning
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/08Reselecting an access point
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/20Control channels or signalling for resource management
    • H04W72/23Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/231Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the layers above the physical layer, e.g. RRC or MAC-CE signalling

Definitions

  • This disclosure relates to terminals, wireless communication methods, and base stations in next-generation mobile communication systems.
  • LTE Long Term Evolution
  • UMTS Universal Mobile Telecommunications System
  • Non-Patent Document 1 LTE-Advanced (3GPP Rel. 10-14) was specified for the purpose of achieving higher capacity and greater sophistication over LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9).
  • LTE 5th generation mobile communication system
  • 5G+ 5th generation mobile communication system
  • 6G 6th generation mobile communication system
  • NR New Radio
  • one of the objectives of this disclosure is to provide a terminal, a wireless communication method, and a base station that can perform suitable power control for a network and can perform more flexible communications.
  • a terminal has a receiving unit that receives Radio Resource Control (RRC) settings for a cell whose physical range is to be changed, and a control unit that controls handover operations between the cells based on the RRC settings.
  • RRC Radio Resource Control
  • FIGS. 1A and 1B are diagrams showing an overview of MIMO.
  • 2A is a diagram showing an overview of a cellular system
  • FIG 2B is a diagram showing an overview of a cell-free system.
  • 3A to 3C are diagrams showing an example of an outline of each assumed cell-free configuration.
  • FIG. 4 is a diagram showing an example of a pattern of one PCI component.
  • 5A to 5E are diagrams showing an example of the configuration of the first cell.
  • FIG. 6 is a diagram showing an example of a pattern of components (area components) of one area.
  • Fig. 7A is a diagram showing an example of a configuration of a first/second cell according to option 1.1.
  • FIG. 7B is a diagram showing an example of a configuration of a first/second cell according to option 1.2.
  • Fig. 8A is a diagram showing an example of a configuration of a first/second cell according to option 2/4.1
  • Fig. 8B is a diagram showing an example of a configuration of a first/second cell according to option 2/4.2
  • Fig. 9A is a diagram showing an example of a configuration of a first/second cell according to option 3/5.1
  • Fig. 9B is a diagram showing an example of a configuration of a first/second cell according to option 3/5.2
  • FIG. 10 is a diagram showing an example of a change in the configuration of the second cell.
  • 11A to 11C are diagrams showing an example of the configuration of a second cell according to option 0.3.
  • FIGS. 12 illustrates an example of a mobility scenario.
  • 13A to 13C are diagrams showing an example of RRC parameter settings relating to embodiment 1-1.
  • Figure 14 is a diagram showing an example of an instruction by a MAC CE relating to option 1-2-1.
  • Figure 15 is a diagram showing an example of an instruction by a MAC CE relating to option 1-2-2.
  • Figure 16 shows an example of an instruction by a MAC CE relating to option 1-2-3.
  • Figure 17 is a diagram showing an example of an instruction by a MAC CE relating to option 1-2-4.
  • 18A-18C are diagrams showing an example of an instruction field relating to options 1-3-1/1-3-2/1-3-3.
  • 19A to 19F are diagrams showing an example of RRC parameter settings relating to Option 2-1-2.
  • Figures 20A and 20B are diagrams showing an example of an instruction by a MAC CE relating to option 2-2-1.
  • Figures 21A and 21B are figures showing an example of an instruction by a MAC CE relating to option 2-2-2.
  • Figures 22A and 22B are figures showing an example of an instruction by a MAC CE relating to option 2-2-3.
  • Figures 23A and 23B are figures showing an example of an instruction by a MAC CE relating to option 2-2-4.
  • 24A to 24C are diagrams showing an example of an instruction field relating to options 2-3-1/2-3-2/2-3-3.
  • Figures 25A and 25B are diagrams showing an example of a MAC CE relating to options 3-1-1/3-1-2.
  • FIGS 26A and 26B are diagrams showing an example of a MAC CE relating to options 3-2-1/3-2-2.
  • FIG. 27 is a diagram showing an example of a second cell change/handover procedure according to the fifth embodiment.
  • FIG. 28 is a diagram showing another example of the procedure of the second cell change/handover according to the fifth embodiment.
  • FIG. 29 is a diagram showing another example of the procedure of the second cell change/handover according to the fifth embodiment.
  • FIG. 30 is a diagram showing an example of the location of a UE according to option 5-1-2-1.
  • FIG. 31 is a diagram showing an example of the location of a UE according to option 5-1-2-2.
  • FIG. 32 is a diagram showing an example of the location of a UE according to option 5-1-2-3.
  • FIG. 33 is a diagram showing an example of the location of a UE according to option 5-1-2-4.
  • FIG. 34 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment.
  • FIG. 35 is a diagram illustrating an example of the configuration of a base station according to an embodiment.
  • FIG. 36 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment.
  • FIG. 37 is a diagram showing an example of the hardware configuration of a base station and a user terminal according to an embodiment.
  • FIG. 38 is a diagram illustrating an example of a vehicle according to an embodiment.
  • a cellular system In existing wireless communication systems (e.g., 5G NR), a cellular system has been adopted in which one cell is formed by one antenna/transmitting/receiving point (TRP) in principle. The area formed by the cell is fixed/static.
  • TRP antenna/transmitting/receiving point
  • distributed multi-input multi-output e.g., distributed MIMO, e.g., multi-TRP using multiple TRPs
  • distributed MIMO allows simultaneous communication using multiple antennas/TRPs, as well as communication using one antenna/TRP.
  • Figures 1A and 1B are diagrams showing an overview of MIMO.
  • Figure 1A shows an example of Co-located MIMO.
  • Co-located MIMO one UE communicates with one antenna/TRP.
  • Figure 1B shows an example of distributed MIMO.
  • distributed MIMO one UE communicates with multiple antennas/TRPs that are linked together.
  • Self-free may be referred to as cell-free massive MIMO (mMIMO) or large-scale distributed MIMO (D-MIMO).
  • mMIMO massive MIMO
  • D-MIMO large-scale distributed MIMO
  • Self-free uses coherent cooperation of multiple access points.
  • Self-free may include at least one of ultra-dense deployment, scalable cooperation, user-centric clustering, super carrier aggregation, and analog fronthaul.
  • the user plane for cell-free may provide more flexible scheduling than existing scheduling.
  • the control plane for cell-free may maintain some form of cells to facilitate signaling.
  • one area (which may be called a cell/sub-cell, etc.) may be formed by multiple antennas/TRPs.
  • the area may refer to a cell that is not dependent on the position of the antenna/TRP.
  • the coverage between multiple antennas/TRPs may overlap.
  • a synchronization signal (which may be called, for example, a synchronization signal block (SSB), a synchronization signal/physical broadcast channel (SS/PBCH) block, etc.) is transmitted may be controlled for each antenna/TRP.
  • SSB synchronization signal block
  • SS/PBCH synchronization signal/physical broadcast channel
  • the central unit (CU)/distributed unit (DU) may be virtualized for each antenna.
  • each antenna may be managed by the CU alone.
  • Figure 2A is a diagram showing an overview of a cellular system.
  • Figure 2A shows the cells formed by each antenna/TRP, and the UE communicates based on these cells.
  • FIG. 2B is a diagram showing an overview of a cell-free system.
  • the installed antennas/TRPs do not form fixed/static cells in a cellular system.
  • one or more antennas/TRPs form an area according to conditions. Therefore, in a cell-free system, each antenna/TRP does not have to correspond to the same physical cell ID, and the areas between multiple antennas/TRPs may overlap.
  • Selfie may be achieved, for example, by adjusting a set of antennas/TRPs controlled by a central control unit (e.g., CU).
  • a central control unit e.g., CU
  • a first cell (which may be called, for example, a cell/super cell/macro cell/large cell, etc.) with a fixed physical range like a cell in a 5G NR system
  • a second cell (which may be called, for example, a sub cell/area/micro cell/cell/small cell/second cell within the first cell, etc.) with a quasi-static/dynamic physical range that varies based on conditions may be formed.
  • the first cell may be a cell that is newly defined in a future wireless communication system, or the definition of a cell in an existing wireless communication system may be reused.
  • FIG. 3C is a diagram showing another example of the outline of the cell-free configuration assumption 2.
  • a PCI is assigned to each TRP included in the first cell (super cell/cell).
  • the same PCI may correspond to multiple TRPs. Multiple TRPs can communicate in a coordinated manner with one UE.
  • Transmission/reception with TRP/subcell coordination may be based on at least one of the following schemes supported in NR: - Single TRP/subcell transmission with dynamic TRP/subcell switching (single-TRP transmission). Joint transmission using multiple TRPs/subcells (multi-TRP joint transmission), which may be based on a single DCI or multiple DCIs, and which may be non-coherent joint transmission (NCJT) or coherent joint transmission (CJT).
  • NCI non-coherent joint transmission
  • CJT coherent joint transmission
  • CJT may be prioritized over NCJT, and single DCI-based joint transmission may be prioritized over multi-DCI-based joint transmission.
  • a cell with a fixed physical range a cell that does not change, a first cell, a super cell, a cell, a macro cell, a large cell, etc. may be interpreted as interchangeable.
  • a cell whose physical range changes quasi-statically/dynamically based on conditions a cell that changes, a second cell, a cell, an area, a microcell, a small cell, a second cell within a first cell, etc. may be interpreted as interchangeable.
  • area, cell, coverage, range, etc. may be interpreted as interchangeable.
  • the first cell may include one or more second cells.
  • a single second cell may be included in multiple first cells. Different first cells may share a single second cell.
  • the different first cells may or may not overlap.
  • the UE may transmit and receive signals using a second cell included in the first cell.
  • the UE may receive a configuration related to the second cell and transmit and receive signals based on the configuration.
  • a Physical Cell ID (PCI) Component may include at least one of the following: - Number of TRPs per PCI. -TRP coverage layout. - Number of synchronization signals (e.g. SSB, SS/PBCH blocks) per TRP.
  • Figure 4 shows an example of a pattern of a single PCI component.
  • a PCI component is composed of the number of TRPs per PCI, the TRP coverage layout, and the number of SSBs per TRP.
  • the number of TRPs per PCI can take one or multiple values
  • the TRP coverage layout can be either non-overlapping or overlapping in TRP coverage
  • the number of SSBs per TRP can take one or multiple values.
  • FIG. 5A is a diagram showing an example of a cell configuration relating to pattern 1.
  • the number of TRPs included in the PCI/cell is one, the TRP coverage does not overlap, and the number of SSBs per TRP is multiple. Note that in the cell configuration in FIG. 5A, the coverage of the TRP may match the coverage of the cell (first cell) (therefore, the coverage of the TRP is not shown in FIG. 5A).
  • Figure 5B is a diagram showing an example of a cell configuration relating to pattern 2.
  • the number of TRPs included in the PCI/cell is multiple, the TRP coverage does not overlap, and the number of SSBs per TRP is one. Note that in the cell configuration in Figure 5B, the coverage of the TRP may match the coverage of the SSB (so the coverage of the TRP is not shown in Figure 5B).
  • a second cell relating to at least one of the above patterns A, B, D, and E may be configured.
  • the coverage of the TRP may match the coverage of the cell (first cell) (so the coverage of the TRP is not shown in FIG. 7B).
  • inter-cell multi-TRP operation may be possible in the second cell related to pattern D/E.
  • This optional configuration can, for example, increase the coverage within overlapping cells, improving the uniformity of communication quality.
  • this optional configuration can improve frequency utilization efficiency, for example, by reducing the coverage in overlapping cells.
  • existing NR-specification antennas/TRPs can be reused, allowing operation by modifying the antenna/TRP equipment so that it overlaps with the coverage deployed with existing NR, reducing station installation costs.
  • the different first cells may not (physically) overlap.
  • a second cell relating to at least one of the above patterns A, C, D, and E may be configured.
  • FIG. 8A is a diagram showing an example of the configuration of the first and second cells related to option 2/4.1. In the example shown in FIG. 8A, the two different cells (first cells) do not overlap.
  • a second cell (second cell coverage) related to pattern A a second cell (second cell coverage) related to pattern C, and a second cell (second cell coverage) related to pattern D/E are shown.
  • the coverage of the TRP may match the coverage of the SSB (so the coverage of the TRP is not shown in Figure 8A).
  • the different first cells may (physically) overlap.
  • FIG. 8B is a diagram showing an example of the configuration of the first and second cells related to option 2/4.2. In the example shown in FIG. 8B, two different cells (first cells) overlap.
  • a second cell (second cell coverage) related to pattern A a second cell (second cell coverage) related to pattern C, and a second cell (second cell coverage) related to pattern D/E are shown.
  • the coverage of the TRP may match the coverage of the SSB (so the coverage of the TRP is not shown in Figure 8B).
  • This optional configuration can, for example, increase the coverage within overlapping cells, improving the uniformity of communication quality.
  • the different first cells may not (physically) overlap.
  • a second cell may be configured that corresponds to at least one of the above patterns A, B, C, D, and E.
  • single TRP operation may be possible in each second cell.
  • intra-cell multi-TRP operation may be possible in a second cell where the coverage of multiple TRPs overlap.
  • the different first cells may (physically) overlap.
  • a second cell may be configured that corresponds to at least one of the above patterns A, B, C, D, and E.
  • FIG. 9B is a diagram showing an example of the configuration of the first and second cells related to option 3/5.2. In the example shown in FIG. 9B, two different cells (first cells) overlap.
  • a second cell (second cell coverage) related to pattern A a second cell (second cell coverage) related to pattern B, a second cell (second cell coverage) related to pattern C, and a second cell (second cell coverage) related to pattern D/E are shown.
  • the second cell of pattern B shown in FIG. 9B is an example that is included only in the coverage of antenna/TRP#0. Also, the second cell of pattern C shown in FIG. 9B is an example that falls in the overlapping area between the coverage of antenna/TRP#1 and the coverage of antenna/TRP#2.
  • inter-cell multi-TRP operation may be possible in the second cell relating to pattern D/E.
  • the configuration of this option can improve the uniformity of communication quality and frequency utilization efficiency compared to the above-mentioned option 1.2, and can reduce station placement costs compared to the above-mentioned option 2/4.2.
  • the second cell may be configured/reconfigured based on certain conditions/triggers, an example of a definition of the second cell is described in detail below.
  • the configuration of the second cell may be changed/updated based on specific conditions/triggers.
  • the specific condition/trigger may be, for example, at least one of a condition/trigger related to UE distribution, a condition/trigger related to traffic, a condition/trigger related to a specific event, and a condition/trigger based on specific information (for example, at least one of information related to time, location information related to UE/TRP, and information related to season).
  • condition/trigger regarding the distribution of UEs may be a condition/trigger based on the distribution/number of UEs in the first cell/second cell.
  • condition/trigger based on specific information may be a condition/trigger based on at least one of information related to time, information related to a specific timer, location information related to the UE/TRP, and information related to the time of year (e.g., date/time/day of the week/weather, etc.).
  • the second cell may be configured based on the particular condition/trigger, or statically, regardless of the particular condition.
  • Restrictions on changing/updating the second cell may be specified.
  • the NW may decide not to change/update the second cell in certain cases.
  • At least one of options 0.1 and 0.2 below may be appropriately and consistently combined with the above description of the second cell.
  • the second cell may be constituted by one cell (the first cell)/PCI.
  • the second cell may be identified by a PCI (similar to the existing NR).
  • the second cell may be configured with a PCI similar to the existing NR.
  • a second cell may be configured with one TRP for one cell, in other words, one second cell may correspond to one TRP.
  • the second cell may be configured with one synchronization signal (e.g., SSB and/or SS/PBCH block) for one cell.
  • one second cell may correspond to one synchronization signal.
  • Such a configuration corresponds, for example, to the second cell according to Pattern A in at least one of Options 1.1, 1.2, 2/4.1, 2/4.2, 3/5.1 and 3/5.2.
  • the second cell may be configured by multiple synchronization signals (e.g., parts of the synchronization signal) for one cell.
  • one second cell may correspond to multiple synchronization signals (parts of the synchronization signal for one cell).
  • Such a configuration corresponds, for example, to the second cell according to Pattern B in at least one of Options 1.1, 1.2, 3/5.1, and 3/5.2 above.
  • the second cell may be configured with multiple synchronization signals for one cell (e.g., all synchronization signals for one cell).
  • one second cell may correspond to multiple synchronization signals (all synchronization signals for one cell).
  • Such a configuration corresponds, for example, to the second cell according to Pattern B in at least one of Options 1.1 and 1.2 above.
  • the second cell may be configured by multiple TRPs for one cell (e.g., a portion of the TRP for one cell).
  • one second cell may correspond to multiple TRPs (a portion of the TRP for one cell).
  • the second cell may be configured with multiple synchronization signals (e.g., parts of the synchronization signal) for one cell.
  • one second cell may correspond to multiple synchronization signals (parts of the synchronization signal for one cell).
  • Such a configuration corresponds, for example, to the second cell according to Pattern C in at least one of Options 2/4.1, 2/4.2, 3/5.1, and 3/5.2.
  • a second cell may be configured by multiple TRPs for one cell (e.g., all TRPs for one cell). In other words, one second cell may correspond to multiple TRPs (all TRPs for one cell).
  • the second cell may be configured with one synchronization signal (e.g., SSB and/or SS/PBCH block) for one cell.
  • one second cell may correspond to one synchronization signal.
  • Such a configuration corresponds, for example, to the second cell according to Pattern A in at least one of Options 1.1 and 1.2 above.
  • the second cell may be configured by multiple synchronization signals (e.g., parts of a synchronization signal) for one cell.
  • one second cell may correspond to multiple synchronization signals (parts of a synchronization signal for one cell).
  • Such a configuration corresponds, for example, to the second cell according to the pattern B in at least one of the above options 1.1 and 1.2, and to the second cell according to the pattern C in at least one of the above options 3/5.1 and 3/5.2.
  • the second cell may be configured with multiple synchronization signals for one cell (e.g., all synchronization signals for one cell).
  • one second cell may correspond to multiple synchronization signals (all synchronization signals for one cell).
  • Such a configuration corresponds, for example, to the second cell according to the pattern B in at least one of the above options 1.1 and 1.2, and the second cell according to the pattern C in at least one of the above options 2/4.1, 2/4.2, 3/5.1, and 3/5.2.
  • the PCI may be defined, for example, in the same way as the PCI defined in the existing NR.
  • This option may address scenario 2 above.
  • the second cell may be configured by multiple TRPs, in other words, one second cell may correspond to multiple TRPs.
  • the TRP may be defined, for example, in the same way as the TRP defined in an existing NR.
  • Changes/updates to each of the above options may be set/instructed/notified to the UE based on at least one of system information (e.g., SIB/MIB), higher layer signaling (RRC parameters/MAC CE), and DCI.
  • system information e.g., SIB/MIB
  • RRC parameters/MAC CE higher layer signaling
  • DCI DCI
  • the second cell may be identified by a specific ID.
  • the particular ID may have a fixed value.
  • the information contained in the synchronization signal may be configurable as information specific to the second cell.
  • the TRP/PCI may be shared among multiple second cells.
  • FIG. 11A is a diagram showing an example of an area related to option 0.3.1.
  • FIG. 11A shows one cell including TRP#0-TRP#3.
  • area #1 and area #2 are formed within the coverage of TRP#0.
  • the area where area #1 and area #2 overlap has the same SSB coverage.
  • area #1 and area #2 can share the same SSB/TRP/PCI.
  • the synchronization signal may not be shared among the second cells.
  • the UE may assume that it does not receive the same (shared/common) synchronization signal in different second cells.
  • the information contained in the synchronization signal may be configurable as information specific to the second cell.
  • the second cell may be identified using an index related to the synchronization signal.
  • the TRP/PCI may be shared among multiple second cells.
  • At least one of an ID for the same TRP (e.g., an ID for identifying the TRP, a TRP ID, and/or a CORESET pool index) and the same PCI may be used between multiple second cells.
  • FIG. 11B is a diagram showing an example of an area related to Option 0.3.2.
  • FIG. 11B shows one cell including TRP#0-TRP#3.
  • Area#1 and Area#2 are formed within the coverage of TRP#1. Area#1 and Area#2 do not overlap with each other, so Area#1 and Area#2 have different SSB coverage. Therefore, areas included in Area#1 or Area#2 do not share the same SSB, but can share the same TRP/PCI.
  • the maximum number of second cells in a first cell may be the number of synchronization signals (SSB/SSB coverage). Also, if the second cell spans multiple SSB coverages, the maximum number of second cells in a first cell may be the number of SSBs (SSB groups) spanned.
  • the synchronization signal and the TRP may not be shared among the second cells.
  • the UE may assume that it does not transmit and receive signals for the same TRP and does not receive the same (shared/common) synchronization signal in different second cells.
  • the information included in the synchronization signal may be configurable as information specific to the second cell.
  • the second cell may be identified using an index related to the synchronization signal.
  • the second cell may be identified using an ID related to the TRP (ID for identifying the TRP).
  • the PCI may be shared among multiple second cells.
  • the same PCI may be used between multiple second cells.
  • FIG. 11C is a diagram showing an example of an area related to option 0.3.3.
  • FIG. 11C shows one cell including TRP#0-TRP#3.
  • area #1 is formed within the coverage of TRP#2
  • area #2 is formed within the coverage of TRP#3.
  • Area #1 and area #2 do not overlap with each other, so area #1 and area #2 have different SSB coverage. Therefore, areas included in area #1 or area #2 do not share the same SSB, do not share the same TRP, and can share the same PCI.
  • the maximum number of second cells in a first cell may be the number of TRPs. Also, if the second cell spans multiple TRPs, the maximum number of second cells in a first cell may be the number of spanned TRPs (TRP groups).
  • the synchronization signal, TRP and PCI may not be shared among the second cells.
  • the UE may assume that the UE does not transmit/receive signals to/from the same cell (first cell/PCI), the same TRP, or receive the same (shared/common) synchronization signal among the different second cells.
  • the information included in the synchronization signal may be configurable as information specific to the second cell.
  • the second cell may be identified using an index related to the synchronization signal.
  • the second cell may be identified using an ID related to the TRP (ID for identifying the TRP).
  • the second cell may be identified using a PCI.
  • the maximum number of second cells in a first cell may be one. Also, if a second cell spans multiple first cells, the total maximum number of second cells may be the number of spanned first cells/PCI (PCI group).
  • Changes/updates to each of the above options may be set/instructed/notified to the UE based on at least one of system information (e.g., SIB/MIB), higher layer signaling (RRC parameters/MAC CE), and DCI.
  • system information e.g., SIB/MIB
  • RRC parameters/MAC CE higher layer signaling
  • DCI DCI
  • the above options may be changed/updated based on the above conditions/triggers (e.g., timers/events) or based on the implementation of the NW/UE.
  • the IDs in each of the above options may be global IDs (e.g., common to all networks) or local IDs (e.g., unique to a portion of networks).
  • the number (e.g., maximum number) of multiple second cells using at least one of the same synchronization signal ID, the same TRP ID, and the same PCI may be predefined in the specifications, may be set/instructed/notified to the UE using higher layer signaling (RRC/MAC CE)/DCI, may be determined based on a report of UE capability information, or may be determined by a combination of at least two of these.
  • RRC/MAC CE higher layer signaling
  • source/serving e.g., source area/serving
  • target e.g., target area
  • target e.g., area of the handover destination.
  • FIG. 12 shows patterns (patterns F-M) related to mobility scenarios in a cell-free configuration.
  • the mobility scenario may be determined based on whether the target CU is the same as the source CU, whether the target PCI is the same as the source PCI, and whether the target TRP is the same as the source TRP.
  • FIG. 12 shows a pattern for moving between second cells (here, areas) (i.e., when the source area and target area are different) or within a second cell (i.e., when the source area and target area are the same).
  • pattern F is a mobility scenario where the target CU is the same as the source CU, the target PCI is the same as the source PCI, and the target TRP is the same as the source TRP.
  • Pattern F it is assumed that the beam management operations of the existing system (defined by Rel. 18) and operations related to changing the second cell in the case of mobility between second cells (i.e., when the source area and target area are different) will be used.
  • pattern G is a mobility scenario where the target CU is the same as the source CU, the target PCI is the same as the source PCI, and the target TRP is different from the source TRP.
  • pattern G it is assumed that the beam management operations of the existing system (defined by Rel. 18) and operations related to changing the second cell in the case of mobility between second cells (i.e., when the source area and target area are different) will be used.
  • pattern H is a mobility scenario where the target CU is the same as the source CU, the target PCI is different from the source PCI, and the target TRP is the same as the source TRP.
  • pattern H the handover is intra-CU, and the same TRP is shared by different PCIs. Also, in pattern H, it is assumed that an operation related to changing the second cell is used in the case of mobility between second cells (i.e., when the source area and target area are different).
  • pattern I is a mobility scenario where the target CU is the same as the source CU, the target PCI is different from the source PCI, and the target TRP is different from the source TRP.
  • pattern I it is assumed that an intra-CU handover operation and an operation related to changing the second cell in the case of mobility between second cells (i.e., when the source area and target area are different) are used.
  • pattern J is a mobility scenario where the target CU is different from the source CU, the target PCI is the same as the source PCI, and the target TRP is the same as the source TRP.
  • pattern J handover is performed within a CU, and the same TRP/PCI is shared by different CUs. Also, in pattern J, it is assumed that operations related to changing the second cell are used in the case of mobility between second cells (i.e., when the source area and target area are different).
  • pattern K is a mobility scenario where the target CU is different from the source CU, the target PCI is the same as the source PCI, and the target TRP is different from the source TRP.
  • pattern K handover is performed within a CU, and the same PCI is shared by different CUs. Also, in pattern K, it is assumed that an operation related to changing the second cell is used in the case of mobility between second cells (i.e., when the source area and target area are different).
  • pattern L handover is performed within a CU, and the same TRP is shared by different CUs/PCIs. Also, in pattern L, it is assumed that operations related to changing the second cell are used in the case of mobility between second cells (i.e., when the source area and target area are different).
  • pattern M it is assumed that an intra-CU handover operation and an operation related to changing the second cell in the case of mobility between second cells (i.e., when the source area and target area are different) are used.
  • NW e.g., base station
  • the higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, other messages (e.g., messages from the core network such as positioning protocols (e.g., NR Positioning Protocol A (NRPPa)/LTE Positioning Protocol (LPP)) messages), or a combination of these.
  • RRC Radio Resource Control
  • MAC Medium Access Control
  • LPP LTE Positioning Protocol
  • the MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc.
  • the broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.
  • MIB Master Information Block
  • SIB System Information Block
  • RMSI Remaining Minimum System Information
  • OSI System Information
  • the physical layer signaling may be, for example, Downlink Control Information (DCI), Uplink Control Information (UCI), etc.
  • DCI Downlink Control Information
  • UCI Uplink Control Information
  • synchronization signal SSB, SS/PBCH block, etc. may be interpreted as interchangeable.
  • each embodiment of the present disclosure can be applied without being limited to a cell-free configuration. In other words, each embodiment of the present disclosure can be applied even in cases where a cell-free configuration is not adopted.
  • This embodiment is broadly divided into embodiments 0-1 and 0-2.
  • the UE/NW may apply the following embodiments 0-1/0-2 alone or in combination.
  • This embodiment may correspond to Assumption 1 above.
  • a second cell may be configured for the UE.
  • This configuration may be performed, for example, using higher layer signaling (e.g., RRC signaling).
  • higher layer signaling e.g., RRC signaling
  • the configuration for the second cell may include at least one of the following information: An ID for identifying the second cell. -Serving cell index. ⁇ PCI. - (A list of) indices for the TRPs that constitute the second cell. (A list of) indices of reference signals (eg, SSBs) that constitute the second cell.
  • the PCI corresponding to the second cell may be associated with the TRP constituting the second cell.
  • an index (list) relating to the TRP may be set in the PCI (list) corresponding to the second cell.
  • the TRP constituting the second cell may be associated with the reference signal.
  • a list of indexes for the reference signal may be set in a list of indexes for the TRP.
  • the settings related to the second cell can be appropriately defined.
  • the first embodiment relates to the movement/handover of the UE between the second cells.
  • the UE may configure/instruct/trigger a change/handover to the second cell using higher layer signaling (RRC signaling/MAC CE)/DCI received from the NW (base station).
  • RRC signaling/MAC CE higher layer signaling
  • the particular RRC parameter may be, for example, an RRC reconfiguration.
  • the UE may determine to perform a change/handover to the second cell based on (in accordance with) the ID.
  • the UE may determine to perform a change/handover to the second cell if the current ID of the second cell (e.g., serving area ID) is different from the ID of the second cell included in the specific RRC parameter.
  • the current ID of the second cell e.g., serving area ID
  • the UE may determine not to perform a change/handover to the second cell. Also, for example, if the RRC parameter indicates a second value (e.g., 1 (or 0) or true), the UE may determine to perform a change/handover to the second cell.
  • a first value e.g., 0 (or 1) or false
  • the UE may determine not to perform a change/handover to the second cell.
  • a second value e.g., 1 (or 0) or true
  • the UE may determine to perform a change/handover to the second cell.
  • the RRC parameters may be included in the specific RRC parameters along with an ID for identifying the second cell.
  • the configuration related to the cell group e.g., CellGroupConfig
  • the configuration related to the serving cell e.g., ServingCellConfig
  • the UE may determine to perform a change/handover to the second cell based on (in accordance with) the ID.
  • This option may also be applied, for example, to options 0-1-3/0-2-3 above.
  • the UE may also receive an RRC parameter indicating whether or not to perform a change/handover to the second cell.
  • the UE may determine whether or not to perform a change/handover to the second cell based on the RRC parameter.
  • the RRC reconfiguration includes a configuration for the second cell (CellFree-AreaConfig) in response to the above option 1-1-1, and the RRC reconfiguration includes the ID of the second cell (Area ID) and a parameter (area switch indicator) indicating whether or not to perform a change/handover for the second cell in response to the above option 1-1-1.
  • the RRC reconfiguration includes a cell group configuration (CellGroupConfig) corresponding to the above option 1-1-3, and the cell group configuration includes the ID (Area ID) of the second cell and a parameter (area switch indicator) indicating whether or not to perform a change/handover related to the second cell corresponding to the above option 1-1-3.
  • CellGroupConfig CellGroupConfig
  • the cell group configuration includes the ID (Area ID) of the second cell and a parameter (area switch indicator) indicating whether or not to perform a change/handover related to the second cell corresponding to the above option 1-1-3.
  • FIG. 13C shows an example in which the RRC reconfiguration includes the serving cell configuration (ServingCellConfig) of the second cell (area).
  • the serving cell configuration (ServingCellConfig) includes the ID of the second cell (Area ID) and a parameter (area switch indicator) indicating whether or not to perform a change/handover regarding the second cell.
  • the UE may configure/instruct/trigger a change/handover to the second cell using a specific MAC CE.
  • the MAC CE may be, for example, a new MAC CE (defined in Rel. 20 or later), or an extended MAC CE for L1L2-triggered mobility (LTM) defined in Rel. 18.
  • LTM L1L2-triggered mobility
  • This field may be included in the MAC CE in addition to or instead of the ID of the target configuration (handover destination configuration).
  • This option may also be applied, for example, to options 0-1-2/0-2-2 above.
  • Figure 14 shows an example of an instruction by a MAC CE related to option 1-2-1.
  • a MAC CE that is an extension of the MAC CE for LTM is described.
  • the MAC CE shown in FIG. 14 includes at least a target configuration ID field (Target Config ID) and an area ID field (Area ID). Note that the example shown in FIG. 14 shows a case where three area candidates are set for the UE, and an example where the area ID field is two bits is shown. The area ID field may be determined based on the number of area candidates set for the UE.
  • the UE may determine whether to change areas based on the value of the area ID field included in the MAC CE as shown in FIG. 14. For example, if the field indicates "00", the UE may determine not to change areas, and if the field indicates "01", “10", or "11", the UE may determine to change areas to "Area #1", “Area #2”, or "Area #3", respectively.
  • field names, bit numbers, and field positions are merely examples and are not limited to the examples shown.
  • the UE may determine to perform a change/handover to the (existing) first cell.
  • the UE may determine not to perform a change/handover to the second cell. Also, for example, if the field indicates a second value (e.g., 1 (or 0)), the UE may determine to perform a change/handover to the second cell based on the target configuration ID.
  • a first value e.g., 0 (or 1)
  • the UE may determine not to perform a change/handover to the second cell.
  • a second value e.g., 1 (or 0)
  • the UE may determine to perform a change/handover to the second cell based on the target configuration ID.
  • the UE may determine whether to perform an area change based on the value of a flag field included in a MAC CE as shown in FIG. 15. For example, if the field indicates "0", the UE may determine not to perform an area change, and if the field indicates "1", the UE may determine to perform an area change to the area corresponding to the target setting ID.
  • Figure 16 shows an example of an instruction by a MAC CE related to option 1-2-3.
  • a MAC CE that is an extension of the MAC CE for LTM is described.
  • the MAC CE may include a target setting ID.
  • the target configuration ID may be associated with a handover/LTM candidate.
  • the handover/LTM candidate may include at least one of an RRC configuration for a TCI state (joint/UL/DL TCI state), an RRC configuration for a TA value, and an RRC configuration for a random access (CFRA) resource.
  • At least one of an RRC configuration for a TCI state (joint/UL/DL TCI state), an RRC configuration for a TA value, and an RRC configuration for a random access (CFRA) resource may include an ID of the second cell.
  • the UE may also receive an RRC parameter indicating whether or not to perform a change/handover to the second cell.
  • the UE may determine whether or not to perform a change/handover to the second cell based on the RRC parameter.
  • the UE may determine not to perform a change/handover to the second cell. Also, for example, if the RRC parameter indicates a second value (e.g., 1 (or 0) or true), the UE may determine to perform a change/handover to the second cell.
  • a first value e.g., 0 (or 1) or false
  • the UE may determine not to perform a change/handover to the second cell.
  • a second value e.g., 1 (or 0) or true
  • the UE may determine to perform a change/handover to the second cell.
  • the RRC parameters indicating whether or not to perform a change/handover to the second cell may be included in the RRC parameters related to the handover/LTM candidate/candidate TCI state, or may be associated with any parameter included in the RRC parameters related to the handover/LTM candidate/candidate TCI state.
  • Figure 17 shows an example of an instruction by a MAC CE related to option 1-2-4.
  • a MAC CE that is an extension of the MAC CE for LTM is described.
  • the MAC CE shown in FIG. 17 includes at least a target configuration ID field (Target Config ID) and a TCI state ID field (TCI state ID)/UL TCI state ID field (UL TCI state ID).
  • the target configuration ID may be associated with an ID (e.g., an LTM candidate ID) that identifies RRC parameters related to the LTM candidate.
  • the RRC parameters related to the candidate TCI state/candidate UL TCI state may include a TCI state ID, a parameter indicating whether or not to perform a change/handover to the second cell (e.g., an area change indicator), and the ID of the second cell (area ID).
  • the RRC parameters related to the candidate TCI state/candidate UL TCI state may be included in the RRC parameters related to the LTM candidates.
  • a parameter related to a list of TCI states may be included in the KTM candidates, and the parameters related to the TCI state IDs indicated in the list of TCI states may refer to the RRC parameters related to the candidate TCI state/candidate UL TCI state.
  • the UE may determine whether to change areas according to the TCI state in the LTM candidate configuration associated with the target configuration ID based on the value of the target configuration ID included in the MAC CE as shown in FIG. 17 and the indicated TCI state ID.
  • the UE determines the TCI state/UL TCI state indicated by the TCI state list in the LTM candidate configuration associated with the target configuration ID indicated by the MAC CE, and determines whether to perform an area change based on the RRC parameters for the candidate TCI state/candidate UL TCI state including the ID of the TCI state/UL TCI state.
  • the RRC parameters for the candidate TCI state/candidate UL TCI state may include the ID of the TCI state/UL TCI state, a parameter indicating whether to perform a change/handover to the second cell (e.g., an area change indicator), and the ID of the second cell (area ID).
  • the UE may determine to perform a change/handover to the (existing) first cell.
  • the UE may configure/indicate/trigger a change/handover to the second cell using a specific MAC CE and/or a specific DCI.
  • the MAC CE may be, for example, a new MAC CE (defined in Rel. 20 or later), a MAC CE that is an extension of the MAC CE defined in Rel. 18, or a MAC CE defined up to Rel. 18.
  • the UE may activate/deactivate the TCI state using at least one of the specific MAC CE and the specific DCI.
  • the UE may be instructed on the TCI state using at least one of the specific MAC CE and the specific DCI.
  • the UE may make a change/handover to the second cell based on the value of the ID field.
  • the ID of the second cell that can be indicated by the MAC CE may be the IDs of multiple (e.g., all) second cells that are set in advance using RRC signaling, or may be the ID of at least one second cell that is indicated by another MAC CE (e.g., a MAC CE for activation of the TCI state) that is received in advance.
  • the UE may determine to perform a change/handover to the (existing) first cell.
  • a specific MAC CE/DCI may include a field indicating whether or not a change/handover to the second cell is to be performed.
  • the UE may determine not to perform a change/handover to the second cell. Also, for example, if the field indicates a second value (e.g., 1 (or 0)), the UE may determine to perform a change/handover to the second cell.
  • a first value e.g., 0 (or 1)
  • the UE may determine not to perform a change/handover to the second cell.
  • a second value e.g., 1 (or 0)
  • the UE may determine to perform a change/handover to the second cell.
  • the indicated TCI state may be associated with a second cell.
  • the UE may determine whether to perform a change/handover to the second cell associated with the indicated TCI state based on the indicated TCI state and a field indicating whether to perform a change/handover to the second cell.
  • Figure 18B is a diagram showing an example of an indication field related to option 1-3-2.
  • the UE may determine whether to perform an area change based on the value of the indication field included in a specific MAC CE/DCI as shown in Figure 18B. For example, if the field indicates "0", the UE may determine not to perform an area change, and if the field indicates "1", the UE may determine to perform an area change to an area related to the indicated TCI state.
  • the UE may decide whether or not to perform a change/handover to the second cell based on the TCI status indicated using that particular MAC CE/DCI.
  • the RRC parameters related to the TCI state for the serving cell/area may include the ID of the second cell.
  • the UE may also receive an RRC parameter indicating whether or not to perform a change/handover to the second cell.
  • the UE may determine whether or not to perform a change/handover to the second cell based on the RRC parameter.
  • the UE may determine not to perform a change/handover to the second cell. Also, for example, if the RRC parameter indicates a second value (e.g., 1 (or 0) or true), the UE may determine to perform a change/handover to the second cell.
  • a first value e.g., 0 (or 1) or false
  • the UE may determine not to perform a change/handover to the second cell.
  • a second value e.g., 1 (or 0) or true
  • the UE may determine to perform a change/handover to the second cell.
  • the RRC parameters indicating whether or not to perform a change/handover to the second cell may be included in the RRC parameters related to the TCI state, or may be associated with any parameter included in the RRC parameters related to the TCI state.
  • FIG. 18C is a diagram showing an example of an indication field related to option 1-3-3.
  • the UE may determine whether to change areas based on the value of an indication field included in a specific MAC CE/DCI, as shown in FIG. 18C.
  • the UE may refer to the RRC parameters corresponding to TCI state ID #0 and determine whether or not to perform an area change to the corresponding area based on the area change indicator and area ID contained in the RRC parameters.
  • the UE may determine to perform a change/handover to the (existing) first cell.
  • the second embodiment relates to the movement/handover of the UE between the second cells.
  • the UE may decide whether or not to perform a change/handover to the second cell based on certain conditions.
  • the UE may be configured with the specific conditions using specific RRC parameters.
  • the particular RRC parameter may be, for example, an RRC reconfiguration.
  • the UE may use the specific RRC parameters to configure an event for triggering a change/handover to the second cell.
  • the UE may determine whether or not to perform a change/handover to the second cell based on the configured event.
  • the UE may also determine whether to perform a change/handover to the second cell based on an event that triggers a change/handover to the second cell, which is predefined in the specifications.
  • the event may be, for example, a common event for multiple (e.g., all) UEs/second cells. Also, the event may be, for example, a specific event for each UE/second cell.
  • the UE may also receive an RRC parameter indicating whether or not to perform a change/handover to the second cell.
  • the UE may determine whether or not to perform a change/handover to the second cell based on the RRC parameter.
  • the RRC parameters may be included in the specific RRC parameters along with an ID for identifying the second cell.
  • conditional reconfiguration list includes the ID of the second cell (Area ID) and a parameter (area switch indicator) indicating whether or not to perform a change/handover regarding the second cell.
  • the parameter (condExecutionCond) related to the execution condition of the conditional reconfiguration in the list of conditional reconfiguration includes the ID of the second cell (Area ID) and a parameter (area switch indicator) indicating whether or not to perform a change/handover related to the second cell.
  • the measurement configuration includes the ID of the second cell (Area ID) and a parameter (area switch indicator) indicating whether or not to perform a change/handover regarding the second cell.
  • the parameter (MeasObjectNR) of the measurement object included in the list of measurement objects (MeasObjectToAddModList) in the measurement configuration (MeasConfig) includes the ID (Area ID) of the second cell and a parameter (area switch indicator) indicating whether or not to perform a change/handover regarding the second cell.
  • the list of measurement IDs (MeasIDToAddModList) in the measurement configuration (MeasConfig) includes the ID of the second cell (Area ID) and a parameter (area switch indicator) indicating whether or not to perform a change/handover regarding the second cell.
  • Any parameter included in the specific RRC parameters may be a parameter related to conditional reconfiguration for the target cell/area (e.g., ConditionalReconfiguration).
  • the configuration related to the cell group e.g., CellGroupConfig
  • the configuration related to the serving cell e.g., ServingCellConfig
  • At least one of the configuration related to the cell group (e.g., CellGroupConfig) and the configuration related to the serving cell (e.g., ServingCellConfig) may include an ID for identifying the second cell.
  • This option may also be applied, for example, to options 0-1-3/0-2-3 above.
  • the RRC parameters may be included in the specific RRC parameters along with an ID for identifying the second cell.
  • the UE may determine to perform a change/handover to the (existing) first cell.
  • the settings/parameters related to RRC in this embodiment may be set in at least one of the settings/parameters related to L1 UE triggered measurement reporting, (Rel. 19) settings/parameters related to conditional LTM, settings/parameters related to L3 UE triggered measurement reporting, and (Rel. 16) settings/parameters related to conditional handover.
  • the UE may use a specific MAC CE to perform at least one of change/handover reporting and beam reporting regarding the second cell.
  • the MAC CE may be, for example, a new MAC CE (specified in Rel. 20 or later), a MAC CE that is an extension of the MAC CE in the L1/L3 UE triggered beam report, or a MAC CE that is an extension of the MAC CE for LTM (Rel. 19).
  • the MAC CE may include a field related to an ID for identifying the second cell.
  • the UE may use this field to report to the second cell corresponding to the field value that it will perform a change/handover to the second cell.
  • This option may also be applied, for example, to options 0-1-2/0-2-2 above.
  • the IDs of the second cells that can be reported by the MAC CE may be IDs of multiple (e.g., all) second cells that are pre-configured using RRC signaling, or may be IDs of at least one second cell that is indicated by another MAC CE (e.g., a MAC CE for activation of the TCI state) that is received in advance.
  • FIG. 20A is a diagram showing an example of an instruction by a MAC CE related to option 2-2-1.
  • FIG. 20A shows a MAC CE that is an extension of the MAC CE for LTM.
  • the MAC CE shown in FIG. 20A includes at least a target configuration ID field (Target Config ID) and an area ID field (Area ID).
  • the UE may use the value of the area ID field included in the MAC CE as shown in FIG. 20A to report that an area change will be made to the area corresponding to that field.
  • Figure 20B is a diagram showing another example of an instruction by a MAC CE relating to option 2-2-1.
  • Figure 20B shows a MAC CE that is an extension of the MAC CE for beam reporting.
  • the MAC CE shown in FIG. 20B includes at least an area ID field (Area ID).
  • the UE may use the value of the area ID field included in the MAC CE as shown in FIG. 20B to report that an area change will be made to the area corresponding to the field.
  • the UE may report that it will perform a change/handover to the (existing) first cell.
  • the MAC CE may include a field indicating whether or not to perform a change/handover to the second cell.
  • the field indicates a first value (e.g., 0 (or 1)), it may mean that the UE does not perform a change/handover to the second cell. Also, for example, when the field indicates a second value (e.g., 1 (or 0)), it may mean that the UE performs a change/handover to the second cell.
  • a first value e.g., 0 (or 1)
  • a second value e.g., 1 (or 0
  • the UE may report at least one of a target cell/area configuration (target configuration) and a target reference signal (RS) configuration.
  • the UE may perform a change/handover to a second cell included in at least one of the reported target cell/area configuration and the target reference signal configuration.
  • FIG. 21A is a diagram showing an example of an instruction by a MAC CE related to option 2-2-2.
  • FIG. 21A shows a MAC CE that is an extension of the MAC CE for LTM.
  • the MAC CE shown in FIG. 21A includes at least a target configuration ID field (Target Config ID) and a field (flag) indicating whether or not to perform a change/handover to the second cell.
  • Target Config ID target configuration ID field
  • Flag field indicating whether or not to perform a change/handover to the second cell.
  • the UE may use the value of the flag field included in the MAC CE as shown in FIG. 21A and the value of the target setting ID to report whether to perform an area change to the area corresponding to the target setting ID.
  • Figure 21B is a diagram showing another example of an instruction by a MAC CE relating to option 2-2-2.
  • Figure 21B shows a MAC CE that is an extension of the MAC CE for beam reporting.
  • the MAC CE shown in FIG. 21B includes a field (flag) indicating whether or not to perform a change/handover to at least the second cell.
  • the UE may use the value of the area ID field included in the MAC CE as shown in FIG. 21B to report whether or not to perform an area change for the area corresponding to the RS ID (e.g., the RS ID corresponding to the best reception quality) reference signal included in the MAC CE.
  • the RS ID e.g., the RS ID corresponding to the best reception quality
  • the UE may report that it will perform a change/handover to the (existing) first cell.
  • the MAC CE may include a target setting ID.
  • the UE may also use the MAC CE to report at least one of the following: TCI state (joint/UL/DL TCI state) ID, Timing Advance (TA) value, Random Access (CFRA) resource/SSB index/Random Access Preamble index, RS index, and PCI.
  • TCI state joint/UL/DL TCI state
  • TA Timing Advance
  • CFRA Random Access
  • the reported target setting ID may be associated with the LTM candidate.
  • the ID of the second cell may be included in at least one of the settings of the TCI state (joint/UL/DL TCI state) ID, TA value, and random access (CFRA) resource/SSB index/random access preamble index associated with the LTM candidate (included in the LTM candidate).
  • TCI state join/UL/DL TCI state
  • TA value TA value
  • CFRA random access
  • the ID of the second cell may also be included in the CSI reporting configuration/CSI resource configuration associated with the reported PCI/RS index.
  • the NW may determine that the UE will perform a change/handover to the second cell.
  • the UE may also transmit an RRC parameter indicating whether or not to perform a change/handover to the second cell.
  • the NW may determine whether or not the UE will perform a change/handover to the second cell based on the RRC parameter.
  • FIG. 23A is a diagram showing an example of an instruction by a MAC CE relating to option 2-2-4.
  • FIG. 23A shows a MAC CE that is an extension of the MAC CE for LTM.
  • the MAC CE shown in FIG. 23A includes at least a target configuration ID field (Target Config ID) and a TCI state ID field (TCI state ID)/UL TCI state ID field (UL TCI state ID).
  • the target configuration ID may be associated with an ID (e.g., an LTM candidate ID) that identifies RRC parameters related to the LTM candidate.
  • the UE may use the value of the target configuration ID and the TCI state ID included in the MAC CE as shown in FIG. 23A to report whether to perform an area change to the area corresponding to the target configuration ID/TCI state ID.
  • the MAC CE shown in FIG. 23B includes at least an RS ID field (RS ID).
  • the UE may determine to perform a change/handover to the (existing) first cell.
  • the MAC CE can be used to appropriately report changes/handovers related to the second cell.
  • the specific UCI may include an ID field for identifying the second cell.
  • the UE may use the ID field to report to the second cell corresponding to the field value that it will perform a change/handover to the second cell.
  • the IDs of the second cells that can be reported by the UCI may be IDs of multiple (e.g., all) second cells that are pre-configured using RRC signaling, or may be IDs of at least one second cell that is indicated by another MAC CE (e.g., a MAC CE for activation of the TCI state) that is received in advance.
  • another MAC CE e.g., a MAC CE for activation of the TCI state
  • FIG. 24A is a diagram showing an example of an instruction field related to option 2-3-1.
  • the UE may report whether to perform an area change using the value of the instruction field included in a specific UCI as shown in FIG. 24A. For example, if the field indicates "00", the UE may report that the area change will not be performed, and if the field indicates "01", “10", or "11", the UE may report that the area change will be performed to "Area #1", "Area #2", or "Area #3", respectively.
  • the UE may report that it will perform a change/handover to the (existing) first cell.
  • the particular UCI may include a field indicating whether or not a change/handover to the second cell is to be performed.
  • the field when the field indicates a first value (e.g., 0 (or 1)), it may mean that no change/handover is performed regarding the second cell. Also, for example, when the field indicates a second value (e.g., 1 (or 0)), it may mean that a change/handover is performed regarding the second cell.
  • a first value e.g., 0 (or 1)
  • a second value e.g., 1 (or 0
  • the UE may report the cell ID (PCI)/RS ID to the NW.
  • the ID of the second cell may be associated with the RRC parameters associated with the cell ID (PCI)/RS ID.
  • the NW may determine the second cell to which the UE should change/handover based on the ID of the second cell associated with the reported cell ID/RS ID.
  • the UE may report the ID of the second cell to be changed using at least one of the methods described in Option 2-3-1 above.
  • FIG. 24B is a diagram showing an example of an indication field related to option 2-3-2.
  • the UE may report whether to perform an area change using the value of an indication field included in a specific UCI as shown in FIG. 24B. For example, when the field indicates "0", it may mean that the UE will not perform an area change, and when the field indicates "1", it may mean that the UE will perform an area change to the corresponding area.
  • the UE may report that it will perform a change/handover to the (existing) first cell.
  • the UE may report the PCI/RS ID using a specific UCI.
  • the PCI/RS ID reported using a particular UCI may be associated with the ID of the second cell.
  • the UE may report a PCI/RS ID using a specific UCI and report a change/handover to a second cell associated with that PCI/RS ID.
  • the ID of the second cell may be included/associated with the CSI reporting configuration/CSI resource configuration associated with the reported PCI/RS ID.
  • the NW may determine that the UE will perform a change/handover to the second cell if the reported ID of the second cell is different from the current ID (serving area ID) of the second cell.
  • the UE may also transmit an RRC parameter indicating whether or not to perform a change/handover to the second cell.
  • the UE may use the RRC parameter to report whether or not to perform a change/handover to the second cell.
  • the RRC parameter when the RRC parameter indicates a first value (e.g., 0 (or 1) or false), it may mean that the UE does not perform a change/handover to the second cell. Also, for example, when the RRC parameter indicates a second value (e.g., 1 (or 0) or true), it may mean that the UE performs a change/handover to the second cell.
  • a first value e.g., 0 (or 1) or false
  • a second value e.g., 1 (or 0) or true
  • FIG. 24C is a diagram showing an example of an indication field related to option 2-3-3.
  • the UE may report whether to perform an area change using the value of an indication field included in a specific UCI, as shown in FIG. 24C.
  • the UE may report that it will change areas to the area corresponding to PCI#0/RS ID#0 (area#3 in this case).
  • the UE may report that it will perform a change/handover to the (existing) first cell.
  • the change/handover regarding the second cell can be appropriately reported using the instruction from the UCI.
  • the UE/NW may switch between the modes corresponding to the first and second embodiments based on specific settings/parameters/instructions.
  • Third Embodiment A third embodiment relates to a MAC CE for configuring/activating/deactivating a second cell.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Un terminal, selon un aspect de la présente divulgation, comprend : une unité de réception qui reçoit un réglage de commande de ressources radio (RRC) associé à une cellule dont la plage physique doit être modifiée ; et une unité de commande qui commande une opération de transfert entre une pluralité des cellules sur la base du réglage RRC. Selon un aspect de la présente divulgation, une commande de puissance appropriée d'un réseau peut être effectuée et une communication plus flexible peut être effectuée.
PCT/JP2023/047001 2023-12-27 2023-12-27 Terminal, procédé de communication sans fil et station de base Pending WO2025141793A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2023/047001 WO2025141793A1 (fr) 2023-12-27 2023-12-27 Terminal, procédé de communication sans fil et station de base

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2023/047001 WO2025141793A1 (fr) 2023-12-27 2023-12-27 Terminal, procédé de communication sans fil et station de base

Publications (1)

Publication Number Publication Date
WO2025141793A1 true WO2025141793A1 (fr) 2025-07-03

Family

ID=96217082

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2023/047001 Pending WO2025141793A1 (fr) 2023-12-27 2023-12-27 Terminal, procédé de communication sans fil et station de base

Country Status (1)

Country Link
WO (1) WO2025141793A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017119077A1 (fr) * 2016-01-06 2017-07-13 富士通株式会社 Appareil de communications, appareil de station de base, système de communications mobiles, procédé de communications, et appareil de station mobile
JP2023151034A (ja) * 2022-03-31 2023-10-16 Kddi株式会社 第1制御装置、信号処理装置、方法及びプログラム

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017119077A1 (fr) * 2016-01-06 2017-07-13 富士通株式会社 Appareil de communications, appareil de station de base, système de communications mobiles, procédé de communications, et appareil de station mobile
JP2023151034A (ja) * 2022-03-31 2023-10-16 Kddi株式会社 第1制御装置、信号処理装置、方法及びプログラム

Similar Documents

Publication Publication Date Title
WO2023073929A1 (fr) Terminal, procédé de communication sans fil, et station de base
WO2023073930A1 (fr) Terminal, procédé de communication radio et station de base
WO2023152905A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2023053460A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2023053291A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2025141793A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2025141792A1 (fr) Équipement utilisateur, procédé de communication sans fil et station de base
WO2025141794A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2025141795A1 (fr) Terminal, procédé de communication sans fil, et station de base
WO2025141796A1 (fr) Terminal, procédé de communication sans fil, et station de base
JP7785158B2 (ja) 端末、無線通信方法及び基地局
JP7716493B2 (ja) 端末、無線通信方法、基地局及びシステム
JP7716492B2 (ja) 端末、無線通信方法、基地局及びシステム
WO2025158524A1 (fr) Terminal, procédé de communication sans fil, et station de base
WO2025158525A1 (fr) Terminal, procédé de communication sans fil, et station de base
WO2025158656A1 (fr) Terminal, procédé de communication sans fil, et station de base
WO2025158655A1 (fr) Terminal, procédé de communication sans fil, et station de base
WO2025158528A1 (fr) Terminal, procédé de communication sans fil, et station de base
WO2025203651A1 (fr) Terminal, procédé de communication sans fil, et station de base
WO2025203652A1 (fr) Terminal, procédé de communication sans fil, et station de base
WO2025150122A1 (fr) Terminal, procédé de communication sans fil, et station de base
WO2025150123A1 (fr) Terminal, procédé de communication sans fil et station de base
JP2025155611A (ja) 端末、無線通信方法及び基地局
JP2025149820A (ja) 基地局、無線通信方法及び無線通信システム
JP2025156074A (ja) 端末、無線通信方法及び基地局

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23963142

Country of ref document: EP

Kind code of ref document: A1