Simultaneous configuration for PCell change and PSCell addition / change

Abstract

Example embodiments of the present disclosure relate to a UE, a MN, a SN, a processor, a method, an apparatus, and a computer readable medium for simultaneous configuration for PCell change and PSCell addition / change. In this technical solution, the UE can be configured with a first configuration related to PCell change and a second configuration related to PSCell addition / change. Furthermore, the UE can perform a first operation if the PCell change is triggered, or the UE can perform a second operation if the PSCell addition / change is triggered. Thus, the UE behavior is defined and thus the mobility of the UE can be guaranteed.

Description

Technical Field

[0001] This disclosure relates to wireless communications, and more specifically to user equipment (UE), primary node (MN), secondary node (SN), methods, apparatus, and computer-readable media for simultaneous configuration of primary cell (PCell) changes and primary / secondary cell (PSCell) additions or changes. Background Technology

[0002] A wireless communication system may include one or more network communication devices (such as base stations), which may also be referred to as eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. Each network communication device (such as a base station) may support wireless communication for one or more user communication devices, which may also be referred to as user equipment (UE), or other suitable terms. The wireless communication system may support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). Furthermore, the wireless communication system may support wireless communication across a variety of wireless access technologies, including third-generation (3G) wireless access technology, fourth-generation (4G) wireless access technology, fifth-generation (5G) wireless access technology, and other suitable wireless access technologies beyond 5G (e.g., sixth-generation (6G)).

[0003] Within the 3GPP (3rd Generation Partnership Project), a work item titled Layer 1 / Layer 2 Triggered Mobility (LTM) for further New Radio (NR) mobility enhancements has been approved to change the serving cell via Layer 1 / Layer 2 (L1 / L2) signaling. LTM is a cell handover procedure triggered by the network based on L1 measurements via a Media Access Control (MAC) control element (CE) to reduce latency, overhead, and downtime. It has been agreed that the UE will not voluntarily release its LTM configuration during network-triggered Layer 3 (L3) handover or PSCell change. However, PCell changes and PSCell additions / changes may occur simultaneously, and their details should be investigated. Summary of the Invention

[0004] This disclosure relates to a UE, MN, SN, method, apparatus, processor, and computer-readable medium for simultaneous configuration of PCell change and PSCell addition / change. According to the proposed technical solution, UE behavior is defined when PCell change and PSCell addition / change occur simultaneously.

[0005] In some implementations, a UE is provided. The UE includes at least one memory; and at least one processor coupled to the at least one memory, and configured such that the UE: receives a first configuration related to a PCell change from a MN; receives a second configuration related to a PSCell addition or PSCell change from a MN or SN; and performs the first operation based on a determination that a PCell change has been triggered; or performs the second operation based on a determination that a PSCell addition or PSCell change has been triggered.

[0006] In some implementations, an MN is provided. The MN includes at least one memory; and at least one processor coupled to the at least one memory and configured such that the MN: sends a first configuration related to a PCell change to a UE, wherein the UE is also configured with a second configuration related to a PSCell addition or PSCell change; and receives a report from the UE indicating that a PCell change or PSCell addition or PSCell change has been performed.

[0007] In some implementations, a SN is provided. The SN includes at least one memory; and at least one processor coupled to the at least one memory and configured such that the SN: sends a second configuration related to a PSCell change to the UE, wherein the UE is also configured with a first configuration related to a PCell change; and receives a report from the UE indicating that a PCell change or a PSCell change has been performed.

[0008] In some implementations, a method is provided to be executed by the UE. The method includes: receiving a first configuration related to a PCell change from the MN; receiving a second configuration related to a PSCell addition or PSCell change from the MN or SN; and performing the first operation based on a determination that a PCell change has been triggered; or performing the second operation based on a determination that a PSCell addition or PSCell change has been triggered.

[0009] In some implementations, a method is provided that is executed by the MN. This method includes: sending a first configuration related to a PCell change to the UE, wherein the UE is also configured with a second configuration related to a PSCell addition or PSCell change; and receiving a report from the UE indicating that a PCell change, PSCell addition, or PSCell change has been executed.

[0010] In some implementations, a method is provided that is executed by the SN. This method includes: sending a second configuration related to a PSCell change to the UE, wherein the UE is also configured with a first configuration related to a PCell change; and receiving a report from the UE indicating that a PCell change or a PSCell change has been executed.

[0011] In some implementations, a processor for wireless communication is provided. The processor includes at least one controller coupled to at least one memory and configured to: receive from a MN a first configuration related to a PCell change; receive from the MN or SN a second configuration related to a PSCell addition or change; and perform the first operation based on a determination that a PCell change has been triggered; or perform the second operation based on a determination that a PSCell addition or change has been triggered.

[0012] In some implementations, a processor for wireless communication is provided. The processor includes at least one controller coupled to at least one memory and configured to: send a first configuration to a UE relating to a PCell change, wherein the UE is also configured with a second configuration relating to a PSCell addition or PSCell change; and receive a report from the UE indicating that a PCell change or PSCell addition or PSCell change has been performed.

[0013] In some implementations, a processor for wireless communication is provided. The processor includes at least one controller coupled to at least one memory and configured to: send a second configuration related to a PSCell change to a UE, wherein the UE is also configured with a first configuration related to a PCell change; and receive a report from the UE indicating that a PCell change or a PSCell change has been performed.

[0014] In the methods described herein and in some implementations of the UE, the method further includes: determining that a PCell change is triggered based on the determination that the execution conditions for a candidate cell for a conditional handover (CHO) procedure are met, wherein the first operation includes one of the following: performing a CHO procedure for a candidate cell; sending a first report to the SN indicating that the execution conditions for the candidate cell for the CHO procedure are met; ignoring secondary cell group (SCG) LTM commands during the CHO procedure; or releasing a second configuration for the LTM procedure for the SCG.

[0015] The method described in this paper and some implementations of the UE also include: sending a second report to the SN based on the determination that the CHO process is complete, the second report indicating that the CHO process is complete.

[0016] The method described herein and some implementations of the UE further include: determining that a PSCell change is triggered based on the determination that an SCG LTM command indicating a candidate cell has been received, and wherein the second operation includes one of the following: performing an LTM procedure for the candidate cell against the SCG; stopping the evaluation of the execution conditions for the CHO procedure; not performing the CHO procedure if the execution conditions for the CHO procedure are met; or suspending the CHO procedure until the LTM procedure against the SCG is completed.

[0017] In the methods described herein and in some implementations of the UE, the method further includes: determining that a PCell change is triggered based on the determination received from the MN according to the LTM cell handover command for the primary cell group (MCG), and wherein the first operation includes one of the following: performing the MCG LTM procedure based on the LTM cell handover command for the MCG; stopping the evaluation of the conditions for PSCell addition or PSCell change; releasing the second configuration for PSCell addition or PSCell change; or performing both the MCG LTM procedure and PSCell addition or PSCell change in response to the conditions for the candidate cell for PSCell addition or PSCell change being met.

[0018] In the methods described in this paper and in some implementations of the UE, the first operation also includes: after the MCG LTM procedure is completed, continuing to evaluate the conditions for subsequent CPC procedures.

[0019] In the methods described herein and in some implementations of the UE, the method further includes: determining that a PSCell addition or PSCell change is triggered based on the determination that the conditions for a candidate cell for PSCell addition or PSCell change are met, and wherein the second operation includes one of the following: performing a PSCell addition or PSCell change for a candidate cell; ignoring an LTM cell handover command for the MCG during the PSCell addition or PSCell change; sending a third report to the MN indicating that the conditions for PSCell addition or PSCell change are met; releasing the first configuration of the MCG LTM procedure; or performing both the MCG LTM procedure and the PSCell addition or PSCell change in response to receiving an LTM cell handover command for the MCG from the MN.

[0020] In the methods described herein and in some implementations of the UE, the second operation further includes sending an indication to the MN that the LTM cell handover command for the MCG is ignored due to the execution of PSCell addition or PSCell change.

[0021] The methods described in this paper and some implementations of MN also include: sending a second configuration related to PSCell addition or PSCell change to the UE.

[0022] The method described in this paper and some implementations of MN also include: releasing the first configuration of the MCG LTM process in response to a third report indicating that the conditions for adding or changing a PSCell have been met.

[0023] The method described herein and some implementations of MN also include: sending an LTM cell handover command for the MCG to the UE; and receiving an indication from the UE that the LTM cell handover command for the MCG is ignored due to the execution of PSCell addition or PSCell change.

[0024] The methods described in this paper and some implementations of the SN also include: receiving a second report from the UE indicating that the CHO procedure is complete.

[0025] In some implementations of the methods, UE, MN, and SN described in this paper, PCell change is a CHO procedure, and PSCell change is an LTM procedure for SCG.

[0026] In some implementations of the methods, UE, MN, and SN described herein, the first report indicates the duration of the CHO process.

[0027] In some implementations of the methods, UEs, MNs, and SNs described in this paper, PCell change is a Primary Cell Group (MCG) LTM procedure, PSCell addition is a Conditional PSCell Addition (CPA) procedure, and PSCell change is one of the following: a Conditional PSCell Change (CPC) procedure or a subsequent CPC procedure. Attached Figure Description

[0028] Figure 1 The illustration shows an example of a wireless communication system in which some embodiments of the present disclosure may be implemented;

[0029] Figure 2A The diagram illustrates the overall process for LTM;

[0030] Figure 2B The illustration shows a schematic diagram of an example communication network in which some embodiments of the present disclosure may be implemented;

[0031] Figure 3 The diagram illustrates a signaling process according to some example embodiments of the present disclosure;

[0032] Figure 4The diagram illustrates a signaling process according to some example embodiments of the present disclosure;

[0033] Figure 5 The diagram illustrates a signaling process according to some example embodiments of the present disclosure;

[0034] Figure 6A The illustration shows a schematic diagram of an example communication network in which some embodiments of the present disclosure may be implemented;

[0035] Figure 6B The diagram illustrates a signaling process according to some example embodiments of the present disclosure;

[0036] Figure 7 Examples of devices suitable for implementing embodiments of the present disclosure are illustrated;

[0037] Figure 8 Examples of processors suitable for implementing some embodiments of the present disclosure are illustrated;

[0038] Figure 9 The diagram illustrates a flowchart of an example method implemented at the UE according to various aspects of this disclosure;

[0039] Figure 10 The diagram illustrates a flowchart of an example method implemented at MN according to various aspects of this disclosure; and

[0040] Figure 11 The diagram illustrates a flowchart of an example method implemented at SN according to various aspects of this disclosure.

[0041] Throughout the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0042] The principles of this disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not constitute any limitation on the scope of this disclosure. The disclosure described herein can be implemented in various ways other than those described below. In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0043] References to "an embodiment," "example embodiment," "embodiment," "some embodiments," etc., in this disclosure indicate that the described embodiments(s) may include a particular feature, structure, or characteristic, but not every embodiment must include that particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same(s) embodiments(s). Moreover, when a particular feature, structure, or characteristic is described in connection with an embodiment, it should be understood that incorporating other embodiments (whether explicitly described or not) to affect such a feature, structure, or characteristic is within the knowledge of those skilled in the art.

[0044] It should be understood that although the terms “first” and “second” may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may also be referred to as a second element without departing from the scope of the embodiments, and similarly, a second element may also be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms. In some examples, values, processes, or apparatus are referred to as “best,” “lowest,” “highest,” “minimum,” “maximum,” etc. It should be understood that such descriptions are intended to indicate that a variety of functional alternatives may be chosen, and that such a choice is not necessarily better, smaller, higher, or otherwise preferred than other choices.

[0045] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the embodiments. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” used herein also include the plural forms. Furthermore, it should be understood that the terms “comprising,” “including,” “having,” “containing,” and / or “comprise”, when used herein, specify the presence of the stated features, elements, components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. For example, the term “comprising” and its variations should be understood as open terms meaning “including, but not limited to.” The term “based on” should be understood as “at least partially based on.” The terms “one embodiment” and “embodiment” should be understood as “at least one embodiment.” The term “another embodiment” should be understood as “at least one other embodiment.” The use of expressions such as “A and / or B” can mean “A only” or “B only” or “both A and B.” Other explicit and implicit definitions may be included below.

[0046] Figure 1The illustration shows an example of a wireless communication system 100 in which some embodiments of the present disclosure may be implemented. The wireless communication system 100 may include one or more network entities 102 (also referred to as network devices (NEs)), one or more UEs 104, a core network (CN) 106, and a packet data network 108. The wireless communication system 100 may support a variety of wireless access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as a Long Term Evolution (LTE) network or an Advanced LTE (LTE-A) network. In some other implementations, the wireless communication system 100 may be a 5G network, such as a New Radio (NR) network. In other implementations, the wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable wireless access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support wireless access technologies beyond 5G. In addition, the wireless communication system 100 can support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0047] One or more network entities 102 may be distributed throughout a geographic area to form a wireless communication system 100. One or more of the network entities 102 described herein may be, include, or may be referred to as network nodes, base stations, network elements, radio access networks (RANs), base transceiver stations, access points, NodeBs, eNodeBs (eNBs), next-generation NodeBs (gNBs), or other suitable terms. Network entities 102 and UE 104 may communicate via communication link 110, which may be a wireless or wired connection. For example, network entities 102 and UE 104 may perform wireless communication (e.g., receive signaling, send signaling) via a Uu interface.

[0048] Network entity 102 can provide a geographic coverage area 112, and network entity 102 can support services (e.g., voice, video, packet data, messaging, broadcasting, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, network entity 102 and UE 104 can support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) according to one or more radio access technologies. In some implementations, network entity 102 can be mobile, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies can overlap, but different geographic coverage areas 112 can be associated with different network entities 102. The information and signals described herein can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0049] One or more UEs 104 may be distributed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or be referred to as a mobile device, wireless device, remote device, remote unit, handheld device, subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, etc. Alternatively or additionally, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine-Type Communication (MTC) device, etc. In some implementations, UE 104 may be stationary within the wireless communication system 100. In some other implementations, UE 104 may be mobile within the wireless communication system 100.

[0050] One or more UEs 104 can be devices of different forms or with different capabilities. Figure 1 The diagram illustrates some examples of UE 104. UE 104 is capable of communicating with various types of devices, such as network entity 102, other UEs 104, or network devices (e.g., CN 106, packet data network 108, relay equipment, integrated access and backhaul (IAB) node, or another network device). Figure 1 As shown. Alternatively or concurrently, UE 104 may support communication with other network entities 102 or UE 104 that may be used as relays in wireless communication system 100.

[0051] UE 104 can also support direct wireless communication with other UE 104s via communication link 114. For example, UE 104 can support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular V2X deployments, communication link 114 may be referred to as a sidelink (SL). For example, UE 104 can support direct wireless communication with another UE 104 via a PC5 interface.

[0052] Network entity 102 may support communication with CN 106 or with another network entity 102, or both. For example, network entity 102 may interface with CN 106 via one or more backhaul links 116 (e.g., via S1, N2, N3, or another network interface). Network entities 102 may communicate with each other via backhaul links 116 (e.g., via X2, Xn, or another network interface). In some implementations, network entities 102 may communicate directly with each other (e.g., between network entities 102). In some other implementations, network entities 102 may communicate with each other or indirectly (e.g., via CN 106). In some implementations, one or more network entities 102 may include sub-components, such as access network entities, which may be examples of access node controllers (ANCs). The ANC may communicate with one or more UEs 104 via one or more other access network transport entities (which may be referred to as radio headends, smart radio headends, or transmit-receive points (TRPs)).

[0053] In some implementations, network entity 102 can be configured with a decomposed architecture that can utilize protocol stacks physically or logically distributed across two or more network entities 102, such as an Integrated Access Backhaul (IAB) network, Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or Virtualized RAN (vRAN) (e.g., Cloud RAN (C-RAN)). For example, network entity 102 may include one or more of the following: Central Unit (CU), Distributed Unit (DU), Radio Unit (RU), RAN Intelligent Controller (RIC) (e.g., Near Real-Time RIC, Non-Real-Time RIC), Service Management and Orchestration (SMO) system, or any combination thereof.

[0054] An RU can also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit-receive point (TRP). In a decomposed RAN architecture, one or more components of network entity 102 can be co-located, or one or more components of network entity 102 can be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 in a decomposed RAN architecture can be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0055] The functional decomposition between CU, DU, and RU can be flexible and can support different functions based on the functions performed at the CU, DU, or RU (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof). For example, a protocol stack functional decomposition can be used between the CU and DU, allowing the CU to support one or more layers of the protocol stack and the DU to support one or more different layers of the protocol stack. In some implementations, the CU can host upper-layer protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU can connect to one or more DUs or RUs, and one or more DUs or RUs can host lower-layer protocol layer functions and signaling, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Media Access Control (MAC) layer), and each can be at least partially controlled by the CU.

[0056] Alternatively, a functional split of the protocol stack can be employed between the DU and RU, allowing the DU to support one or more layers of the protocol stack and the RU to support one or more different layers of the protocol stack. The DU can support one or more different cells (e.g., via one or more RUs). In some implementations, the functional split between the CU and DU or between the DU and RU can be within a protocol layer (e.g., some functions of the protocol layer can be performed by one of the CU, DU, or RU, while other functions of the protocol layer can be performed by another of the CU, DU, or RU).

[0057] The CU can be further functionally divided into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU can be connected to one or more DUs via midhaul communication links (e.g., F1, F1-C, F1-U), and the DUs can be connected to one or more RUs via fronthaul communication links (e.g., open fronthaul (FH) interfaces). In some implementations, the midhaul or fronthaul communication links can be implemented based on interfaces (e.g., channels) between layers of a protocol stack supported by the corresponding network entity 102 communicating via such communication links.

[0058] CN 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. CN 106 can be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., Mobility Management Entity (MME), Access and Mobility Management Function (AMF)) and user plane entities that route packets or interconnect with external networks (e.g., Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)). In some implementations, the control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.) for one or more UEs 104 served by one or more network entities 102 associated with CN 106.

[0059] CN 106 can communicate with packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N3, or another network interface). Packet data network 108 may include application server 118. In some implementations, one or more UEs 104 can communicate with application server 118. UE 104 can establish a session (e.g., Protocol Data Unit (PDU) session, etc.) with CN 106 via network entity 102. CN 106 can use the established session (e.g., an established PDU session) to route traffic (e.g., control information, data, etc.) between UE 104 and application server 118. A PDU session can be an example of a logical connection between UE 104 and CN 106 (e.g., one or more network functions of CN 106).

[0060] In the wireless communication system 100, network entity 102 and UE 104 can use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, network entity 102 and UE 104 can support different resource structures. For example, network entity 102 and UE 104 can support different frame structures. In some implementations, such as in 4G, network entity 102 and UE 104 can support a single frame structure. In some other implementations, such as in 5G and other suitable wireless access technologies, network entity 102 and UE 104 can support various frame structures (i.e., multiple frame structures). Network entity 102 and UE 104 can support various frame structures based on one or more sets of parameters.

[0061] One or more parameter sets may be supported in the wireless communication system 100, and the parameter sets may include subcarrier spacing and cyclic prefix (CP). A first parameter set (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a regular cyclic prefix. In some implementations, the first parameter set (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one time slot per subframe. A second parameter set (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a regular cyclic prefix. A third parameter set (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a regular cyclic prefix or an extended cyclic prefix. A fourth parameter set (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a regular cyclic prefix. A fifth parameter set (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a regular cyclic prefix.

[0062] The time intervals of resources (e.g., communication resources) can be organized according to frames (also known as radio frames). Each frame can have a duration, for example, 10 milliseconds (ms). ms The duration of a frame. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, such as 1... ms The duration of a frame. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0063] Alternatively or concurrently, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more parameter sets supported in the wireless communication system 100. For example, a first parameter set, a second parameter set, a third parameter set, a fourth parameter set, and a fifth parameter set (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize one time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe, respectively. Each time slot may include a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of time slots in a subframe may depend on the parameter set. For a regular cyclic prefix, a time slot may include 14 symbols. For an extended cyclic prefix (e.g., for a 60 kHz subcarrier spacing), a time slot can include 12 symbols. The relationship between the number of symbols per time slot, the number of time slots per subframe, and the number of time slots per frame for both regular and extended cyclic prefixes can depend on the parameter set. It should be understood that references to the first parameter set (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) can be used interchangeably between subframes and time slots.

[0064] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc., based on frequency or wavelength. For example, the wireless communication system 100 can support one or more operating frequency bands, such as frequency range identifiers FR1 (410MHz-7.125GHz), FR2 (24.25GHz-52.6GHz), FR3 (7.125GHz-24.25GHz), FR4 (52.6GHz-114.25GHz), FR4a or FR4-1 (52.6GHz-71GHz), and FR5 (114.25GHz-300GHz). In some implementations, network entity 102 and UE 104 can perform wireless communication on one or more operating frequency bands. In some implementations, FR1 can be used by network entity 102 and UE 104, along with other equipment or devices, for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by network entity 102 and UE 104, along with other equipment or devices, for short-range, high data rate capabilities.

[0065] FR1 can be associated with one or more parameter sets (e.g., at least three parameter sets). For example, FR1 can be associated with: a first parameter set (e.g., μ=0) comprising a subcarrier spacing of 15 kHz; a second parameter set (e.g., μ=1) comprising a subcarrier spacing of 30 kHz; and a third parameter set (e.g., μ=2) comprising a subcarrier spacing of 60 kHz. FR2 can be associated with one or more parameter sets (e.g., at least two parameter sets). For example, FR2 can be associated with: a third parameter set (e.g., μ=2) comprising a subcarrier spacing of 60 kHz; and a fourth parameter set (e.g., μ=3) comprising a subcarrier spacing of 120 kHz.

[0066] LTM is a procedure in which the gNB receives multiple L1 measurement reports from the UE and, based on these reports, changes the UE's serving cell via a cell handover command signaled via the MAC CE. The cell handover command indicates a previously prepared LTM candidate cell configuration provided to the UE via RRC signaling. The UE then hands over to the target cell according to the cell handover command. The LTM procedure can be used to reduce mobility latency.

[0067] Cell handover commands are transmitted in the MAC CE, which contains the information necessary to perform an LTM cell handover, including at least a candidate configuration index. Cell-specific configurations, radio bearer configurations, and measurement configurations can be part of the LTM candidate cell configuration. Figure 2A The diagram illustrates the overall process for LTM.

[0068] exist Figure 2A In step 1, the UE sends a message to the gNB. Measurement Report The gNB decides to configure LTM and initiates preparation of (multiple) candidate cells. In step 2, the gNB sends a message to the UE. RRCReconfiguration The message, RRCReconfiguration The message includes LTM candidate cell configurations for one or more candidate cells. In step 3, the UE stores the LTM candidate cell configurations and sends them to the gNB. RRCReconfigurationComplete information.

[0069] At step 4a, the UE can perform DL synchronization with (multiple) candidate cells before receiving the cell handover command. It should be understood that, at least based on the Synchronization Signal Block (SSB), DL synchronization with (multiple) candidate cells before the cell handover command is supported.

[0070] At step 4b, if requested by the network, the UE performs Early Time Advance (TA) acquisition with (multiple) candidate cells before receiving the cell handover command. This is done via CFRA triggered by the PDCCH command from the source cell, after which the UE sends a preamble to the indicated candidate cell. To minimize data interruption to the source cell due to CFRA with (multiple) candidate cells, the UE does not receive RAR for TA value acquisition, and the TA value of the candidate cell is indicated in the cell handover command. The UE does not maintain a TA timer for the candidate cells, but relies on the network implementation to ensure TA validity.

[0071] In step 5, the UE performs L1 measurements on the configured candidate cells(s) and sends an L1 measurement report to the gNB. L1 measurements should be performed whenever RRC reconfiguration is applied in step 2.

[0072] In step 6, the gNB determines to perform a cell handover to the target cell and sends a MAC CE to trigger the handover, including a candidate configuration index for the target cell. The UE hands over to the target cell and applies the configuration indicated by the candidate configuration index.

[0073] In step 7, if the UE does not have a valid TA for the target cell, the UE performs a random access procedure for the target cell.

[0074] In step 8, the UE completes the LTM cell handover process by sending an RRC reconfiguration complete message to the target cell. If the UE has already performed the RA procedure in step 7, the UE considers the LTM execution to be successfully completed when the random access procedure is successfully completed. For LTM without a random access channel (RACH), the UE considers the LTM execution to be successfully completed when it determines that the network has successfully received its first UL data. The UE determines the successful reception of its first UL data by receiving the PDCCH of its C-RNTI addressed in the target cell, which schedules new transmissions after the first UL data.

[0075] Figure 2A The procedures described on the air interface apply to both intra-DU LTM and inter-DU LTM. In this disclosure, the overall LTM procedures on the F1-C and Xn interfaces will be repeated.

[0076] L3 switching may occur during the configuration, evaluation, or use of LTM. However, it is not discussed whether LTM can be configured simultaneously with condition-based switching. If coexistence is allowed, PCell changes and PSCell changes may occur concurrently, and further investigation is warranted for details.

[0077] This disclosure provides a communication technical solution. In this solution, the UE can receive a first configuration related to PCell change and a second configuration related to PSCell addition or change. When a PCell change or PSCell addition / change is triggered, the UE can also perform corresponding operations. Therefore, simultaneous configuration for PCell change and PSCell addition / change is supported, and UE behavior is defined. Thus, communication at the UE can be guaranteed. The principles and implementation of this disclosure will now be described in detail with reference to the accompanying drawings.

[0078] Figure 2B The illustration shows a schematic diagram of an example communication network 200 in which some embodiments of the present disclosure may be implemented. For example... Figure 2B As shown, the communication network 200 may include MN 210, SN 220, SN 230, and UE 240, which can communicate with each other. (Reference) Figure 1 Each of MN 210, SN 220, and SN 230 can be a network entity 102, and UE 240 can be a UE 104.

[0079] It should be understood that Figure 2B The number of devices given is for illustrative purposes and does not imply any limitation on this disclosure. For example, during inter-SN mobility, there may be multiple SNs for UE 240. For example, UE 240 may be configured with carrier aggregation (CA) or dual connectivity (DC).

[0080] In this disclosure, PCell refers to the primary cell of the primary cell group (MCG), and PSCell refers to the primary cell of the secondary cell group (SCG).

[0081] Figure 3 The illustration shows a signaling diagram illustrating a communication process 300 according to some example embodiments of the present disclosure. For example... Figure 2B As shown, procedure 300 may involve MN 210, SN 220, and UE 240. It should be understood that procedure 300 can be applied to other communication scenarios, which will not be described in detail hereafter.

[0082] UE 240 accesses both MN 210 and SN 220 via a DC, meaning UE 240 accesses the network via a DC that includes both MCG and SCG. UE 240 can send measurement reports to MN 210 and SN 220 respectively. For example, the measurement reports can indicate cell measurements of neighboring cells and the serving cell.

[0083] In procedure 300, MN 210 sends a first configuration related to the PCell change to UE 240 at 310. In some implementations, the first configuration may include CHO configurations related to multiple candidate cells. In some implementations, UE 240 may begin evaluating (multiple) CHO conditions after receiving the CHO configuration.

[0084] In procedure 300, at point 320, SN 220 sends a second configuration related to the PSCell change to UE 240. In some implementations, the second configuration may include an LTM configuration for the SCG (SCG-LTM configuration).

[0085] In some example embodiments, in the case of SN-initiated SCG LTM without MN participation, if the signaling radio bearer (SRB) between SN 220 and UE 240 has been configured, SN 220 can directly send the LTM configuration for SCG to UE 240. For example, if SRB3 is configured, SRB3 can be used for transmission between SN 220 and UE 240.

[0086] In some examples, if the SRB between SN 220 and UE 240 is not configured, SN 220 can send the LTM configuration for SCG to UE 240 via MN 210. For example, SN 220 sends the LTM configuration for SCG to MN 210, and MN 210 forwards the LTM configuration for SCG to UE 240.

[0087] In some examples, an RRC configuration message can be sent to UE 240, and the RRC configuration message includes LTM configuration for the SCG. For example, the RRC configuration message may include information elements (IEs) carrying the LTM configuration for the SCG, such as... LTM- Config .

[0088] In some examples, the LTM configuration for SCG may also include another configuration, such as RACH resources for early TA acquisition.

[0089] Based on the first configuration related to the PCell change and the second configuration related to the PSCell change, a PCell change can be triggered and a PSCell change can be triggered. If the PCell change is triggered first, operation 330 can be executed. If the PSCell change is triggered first, operation 340 can be executed.

[0090] UE 240 can determine at point 331 that the execution conditions of the candidate cell configured for CHO are met; that is, if the execution conditions of the candidate cell configured for CHO are met, the PCell change is triggered. Furthermore, UE 240 performs the CHO procedure to the candidate cell at point 332. For example, the candidate cell is a candidate PCell.

[0091] In some implementations, UE 240 may send a first report to SN 220 at 333, for example, via an RRC message or via MAC CE. In some examples, the first report may indicate that a PCell change has been triggered. In some examples, the first report may indicate that the execution conditions for the candidate cell configured for CHO have been met. In some examples, the first report may indicate that a CHO procedure to the candidate cell is in progress. In some examples, the first report may indicate that SCGLTM is not allowed.

[0092] In some examples, the first report may also indicate the duration of the CHO procedure. For example, when the CHO procedure begins, a timer (such as T304) may be started at UE 240, and the duration may be the length of the timer. For example, the first report may include the value of the timer used to indicate the duration.

[0093] In some examples, based on the receipt of the first report, SN 220 can stop triggering SCG LTM at 334, that is, SN 220 will not send SCG LTM commands (i.e., LTM commands for SCG) for the duration.

[0094] In some examples, when the CHO procedure is completed, UE 240 may also send a second report to SN 220. For example, the second report may be sent via an RRC message or via a MAC CE. For example, the second report may indicate that the CHO procedure is complete. For example, the second report may indicate that SCG LTM is enabled. Therefore, upon receiving the second report, SN 220 may trigger SCG LTM if necessary.

[0095] In some implementations, UE 240 may receive the SCG LTM command from SN 220 at 335 during the CHO procedure, and UE 240 may ignore the SCG LTM command at 336. In some examples, when UE 240 receives the SCG LTM command while UE 240 is performing the CHO procedure, UE 240 will not perform the LTM procedure for SCG (which may also be referred to as the SCG LTM procedure). In some examples, the SCG LTM procedure may be performed based on the SCG LTM command after the CHO procedure is completed.

[0096] In some implementations, UE 240 may receive an SCG LTM command from SN 220 at 337 during the CHO procedure, and UE 240 may perform a reconstruction procedure. That is, when UE 240 receives an SCG LTM command while the CHO procedure is in progress, UE 240 performs a reconstruction procedure at 338.

[0097] In some implementations, UE 240 can release the LTM configuration for SCG at 339. In some examples, UE 240 can release the LTM configuration for SCG when the CHO procedure is triggered / started, or when the CHO procedure completes.

[0098] In operation 340, SN 220 sends an SCG LTM command to UE 240 at 341, while UE 240 is still evaluating the execution conditions(s) configured for CHO. In some implementations, the SCG LTM command from SN 220 may include an index of the candidate cell, such as indicating a candidate PSCell. Furthermore, at 342, UE 240 performs an SCG LTM procedure towards the candidate cell based on the SCG LTM command.

[0099] In some implementations, UE 240 may stop evaluating the execution conditions for the CHO procedure at point 343. In some examples, the evaluation of the conditions will be stopped when the SCG LTM command is received. In some examples, UE 240 may continue evaluating the execution conditions for the CHO procedure after the SCG LTM procedure has completed. For example, after UE 240 completes the SCG LTM procedure, the evaluation of the execution conditions may begin, restart, or resume.

[0100] In some implementations, UE 240 can perform the reconstruction procedure at 344, for example, when the execution conditions for the CHO procedure are met while UE 240 is performing the SCG LTM procedure.

[0101] In some implementations, if the execution conditions for the CHO procedure are met while UE 240 is performing the SCG LTM procedure, UE 240 will not execute the CHO procedure at point 345. For example, UE 240 may continue to evaluate the execution conditions but will not execute the CHO procedure.

[0102] In some implementations, UE 240 may pause the CHO procedure at point 346 until the SCG LTM procedure is complete. In some examples, when UE 240 executes the SCG LTM procedure, UE 240 may determine that the execution conditions for the CHO procedure are met, and UE 240 may continue executing the SCG LTM procedure but pause the CHO procedure. In some examples, the CHO procedure may begin after the SCG LTM procedure is complete.

[0103] In some implementations, the DU of SN 220 can provide cell handover notification to the CU of SN 220, and furthermore, the CU of SN 220 can send a notification to MN 210 at point 347. For example, this notification can be sent to the CU of MN 210 via the Xn interface.

[0104] According to the reference Figure 3 In this embodiment, when both the CHO configuration and the SCG LTM configuration are configured for UE 240, the behavior is defined, and therefore, the mobility of UE 240 can be guaranteed. It should be understood that if both the CHO configuration and the SCG LTM configuration are not allowed to be configured, then one of the CHO configuration and the SCG LTM configuration can be released.

[0105] Figure 4 The illustration shows a signaling diagram illustrating a communication process 400 according to some example embodiments of the present disclosure. For example... Figure 2B As shown, process 400 may involve MN 210 and UE 240. It should be understood that process 400 can be applied to other communication scenarios, which will not be described in detail hereafter.

[0106] UE 240 accesses the network via MCG. UE 240 can send measurement reports to MN 210. For example, the measurement report can indicate cell measurements of neighboring cells and the serving cell.

[0107] In procedure 400, MN 210 sends a first configuration related to the PCell change to UE 240 at 410. In some implementations, the first configuration may include an LTM configuration for the MCG (MCG LTM configuration).

[0108] In procedure 400, MN 210 sends a second configuration related to PSCell addition to UE 240 at 420. In some implementations, the second configuration may include CPA configuration for at least one candidate cell. In some implementations, UE 240 may begin evaluating one or more conditions for the candidate cells for CPA after receiving the CPA configuration.

[0109] Based on the first configuration related to PCell change and the second configuration related to PSCell addition, PCell change can be triggered and PSCell addition can be triggered. If PCell change is triggered first, operation 430 can be executed. If PSCell addition is triggered first, operation 440 can be executed.

[0110] In operation 430, MN 210 sends an LTM cell handover command for MCG to UE 240 at 431, while UE 240 is still evaluating the conditions(s) for CPA. In some implementations, the LTM cell handover command for MCG may also be referred to as the MCG LTM cell handover command or the MCG LTM command. Furthermore, at 432, UE 240 performs the MCG LTM procedure (which may also be referred to as the MCG LTM procedure) based on the LTM cell handover command for MCG.

[0111] In some implementations, UE 240 can stop evaluating the conditions for CPA at 433. In some examples, the evaluation of conditions will be stopped when an MCG LTM cell handover command is received, or when an MCG LTM procedure is being performed.

[0112] In some implementations, UE 240 can release the CPA configuration at 434. In some examples, the UE can release the CPA configuration when the MCG LTM cell handover command is received, or when the MCG LTM procedure is being executed, or when the MCG LTM procedure is completed.

[0113] In some implementations, simultaneous PCell change and PSCell addition are allowed. If the conditions for CPA are met while UE 240 is performing the MCG LTM procedure, then UE 240 can execute both the MCG LTM procedure and the CPA procedure in parallel at 435.

[0114] In operation 440, UE 240 can determine at 441 that the conditions for CPA are met; that is, if the conditions for CPA are met, PSCell addition is triggered. Furthermore, UE 240 performs the CPA procedure at 442. For example, the conditions for the candidate PSCell are met, and the CPA procedure for the candidate cell is performed.

[0115] In some implementations, UE 240 may receive an LTM cell handover command for MCG from MN 210 at 443 during the CPA procedure, and UE 240 may ignore the LTM cell handover command for MCG at 444. In some examples, UE 240 may send an indication to MN 210, which may indicate that UE 240 ignores the LTM cell handover command for MCG from MN 210 due to the execution of CPA.

[0116] In some implementations, UE 240 may receive an LTM cell handover command for MCG from MN 210 at 445 during the CPA procedure, and UE 240 may determine at 446, based on the LTM cell handover command for MCG from MN 210, to stop CPA and execute the MCG LTM procedure.

[0117] In some implementations, UE 240 may send a third report to MN 210 at point 447. In some examples, the third report may indicate that a PSCell add-on (i.e., CPA) has been triggered. In some examples, the third report may indicate that the conditions for CPA have been met. In some examples, the third report may indicate that the MCG LTM configuration should be released. In some examples, based on the receipt of the third report, MN 210 may release the MCG LTM configuration at point 448. In some examples, UE 240 may release the first configuration of the MCG LTM after the CPA procedure.

[0118] In some implementations, simultaneous PCell change and PSCell addition are allowed. If an LTM cell handover command for MCG is received from MN 210 while UE 240 is performing the CPA procedure, UE 240 can perform both the MCG LTM procedure and the CPA procedure in parallel at 449.

[0119] According to the reference Figure 4 In this embodiment, when both the MCG LTM configuration and the CPA configuration are configured for UE 240, the behavior is defined, and therefore, the mobility of UE 240 can be guaranteed. It should be understood that if both the MCG LTM configuration and the CPA configuration are not allowed to be configured, then one of the MCG LTM configuration and the CPA configuration can be released.

[0120] Figure 5 The illustration shows a signaling diagram illustrating a communication process 500 according to some example embodiments of the present disclosure. For example... Figure 2B As shown, procedure 500 may involve MN 210, SN 220, and UE 240. It should be understood that procedure 500 can be applied to other communication scenarios, which will not be described in detail hereafter.

[0121] UE 240 accesses both MN 210 and SN 220 via a DC, meaning UE 240 accesses the network via a DC that includes both MCG and SCG. UE 240 can send measurement reports to at least MN 210. For example, the measurement reports can indicate cell measurements of neighboring cells and the serving cell.

[0122] In procedure 500, MN 210 sends a first configuration related to the PCell change to UE 240 at 510. In some implementations, the first configuration may include an LTM configuration for the MCG (MCG LTM configuration).

[0123] In procedure 500, MN 210 or SN 220 sends a second configuration related to the PSCell change to UE 240 at 520. In some implementations, the second configuration may include: a CPC configuration for at least one candidate cell, or a subsequent CPC (SCPC) configuration for at least one candidate cell. In some implementations, UE 240 may begin evaluating one or more conditions for the candidate cells for CPC or SCPC after receiving the CPC / SCPC configuration.

[0124] In some examples, for CPC / SCPC procedures initiated by the MN or inter-SN CPC / SCPC procedures initiated by the SN, the MN210 may send a second configuration related to the PSCell change. In some examples, for intra-SN CPC / SCPC procedures initiated by the SN, the SN 220 may send a second configuration related to the PSCell change.

[0125] Based on the first configuration related to the PCell change and the second configuration related to the PSCell change, a PCell change can be triggered and a PSCell change can be triggered. If the PCell change is triggered first, operation 530 can be executed. If the PSCell change is triggered first, operation 540 can be executed.

[0126] In operation 530, MN 210 sends an LTM cell handover command for MCG to UE 240 at 531, while UE 240 is still evaluating the conditions(s) for CPC / SCPC. In some implementations, the LTM cell handover command for MCG may also be referred to as an MCG LTM cell handover command or an MCG LTM command. Furthermore, at 532, UE 240 performs the MCG LTM procedure based on the LTM cell handover command for MCG.

[0127] In some implementations, UE 240 may stop evaluating conditions for CPC / SCPC at point 533. In some examples, condition evaluation will be stopped when an MCG LTM cell handover command is received, or when the MCG LTM procedure is being executed. In some examples, UE 240 may continue evaluating conditions for SCPC after the MCG LTM procedure is completed.

[0128] In some implementations, UE 240 can release the CPC / SCPC configuration at 534. In some examples, the UE can release the CPC / SCPC configuration when an MCG LTM cell handover command is received, when an MCG LTM procedure is being executed, or when an MCG LTM procedure is completed.

[0129] In some implementations, simultaneous changes to PCell and PSCell are allowed. If the conditions for CPC / SCPC are met when UE 240 executes the MCG LTM procedure, UE 240 can execute both the MCG LTM procedure and the CPC / SCPC procedure in parallel at 535.

[0130] In operation 540, UE 240 can determine at 541 that the conditions for CPC / SCPC are met; that is, if the conditions for CPC / SCPC are met, the PSCell change is triggered. Furthermore, UE 240 executes the CPC / SCPC procedure at 542. For example, the conditions for the candidate PSCell are met, and the CPC / SCPC procedure for the candidate cell is executed.

[0131] For example, for intra-SN CPC / SCPC procedures, a candidate cell could belong to SN 220. For example, for inter-SN CPC / SCPC procedures, a candidate cell could belong to another SN, such as SN 230.

[0132] In some implementations, UE 240 may receive an LTM cell handover command for MCG from MN 210 at 543 during the CPC / SCPC procedure, and UE 240 may ignore the LTM cell handover command for MCG at 544. In some examples, UE 240 may send an indication to MN 210, wherein the indication may indicate that UE 240 ignores the LTM cell handover command for MCG from MN 210 due to the execution of CPC / SCPC.

[0133] In some implementations, UE 240 may receive an LTM cell handover command for MCG from MN 210 at 545 during the CPC / SCPC procedure, and UE 240 may determine to stop CPC / SCPC and execute the MCG LTM procedure at 546 based on the LTM cell handover command for MCG from MN 210.

[0134] In some implementations, UE 240 may send a third report to MN 210 at point 547, for example, via an RRC message or via a MAC CE. In some examples, the third report may indicate that a PSCell change (i.e., CPC / SCPC) has been triggered. In some examples, the third report may indicate that the conditions for CPC / SCPC have been met. In some examples, the third report may indicate that the MCG LTM configuration should be released. In some examples, based on the receipt of the third report, MN 210 may determine at point 548 whether to release the MCG LTM configuration or retain it.

[0135] In some implementations, simultaneous PCell and PSCell changes are allowed. If an LTM cell handover command for MCG is received from MN 210 while UE 240 is performing the CPC / SCPC procedure, UE 240 can perform both the MCG LTM procedure and the CPC / SCPC procedure in parallel at 549.

[0136] According to the reference Figure 5 In this embodiment, when both the MCG LTM configuration and the CPC / SCPC configuration are configured for UE 240, the behavior is defined, and therefore, the mobility of UE 240 can be guaranteed. It should be understood that if both the MCG LTM configuration and the CPC / SCPC configuration are not allowed to be configured, then one of the MCG LTM configuration and the CPC / SCPC configuration can be released.

[0137] Figure 6A The illustration shows a schematic diagram of an example communication network 600 in which some embodiments of the present disclosure may be implemented. For example... Figure 6A As shown, the communication network 600 may include CU 610, DU 620, and UE 640. UE 640 is connected to DU 620, which is controlled by CU 610. Due to the mobility of UE 640, it can switch to DU 625, which is controlled by CU 615. (Reference) Figure 1 Each of CU610, CU615, DU620, and DU625 can be part of a network entity 102, and UE640 can be a UE 104.

[0138] In network 600, CU 610 can be the source CU (or source gNB) of UE 640, DU 620 can be the source DU of UE 640, and CU 615 and DU 625 are the target CU and target DU of UE 640, respectively.

[0139] It should be understood that Figure 6A The number of devices given is for illustrative purposes and does not represent any limitation on this disclosure. For example, one or more DUs may be connected to CU 610 / 615. For example, UE 640 may be configured with carrier aggregation (CA) or dual connectivity (DC).

[0140] Figure 6B The illustration shows a signaling diagram illustrating a communication process 650 according to some example embodiments of the present disclosure. For example... Figure 6A As shown, procedure 650 may involve UE 640, source DU 620, source CU 610, target CU 615, and target DU 625. It should be understood that procedure 650 can be applied to other communication scenarios, which will not be described in detail hereafter.

[0141] UE 640 can access the network via a DC including both MCG and SCG, or only via MCG. When the UE accesses both MN and SN via DC, UE 640 can send measurement reports to both MN and SN separately. For example, the measurement report can indicate cell measurements of neighboring cells and the serving cell.

[0142] In procedure 650, UE 640 receives CHO configuration and MCG LTM configuration from the serving gNB (such as source CU 610) at 601. In some implementations, the CHO configuration is associated with one or more candidate cells, and UE 640 begins evaluating CHO candidate cells after receiving the CHO configuration. In some implementations, the MCG LTM configuration is associated with one or more candidate cells.

[0143] In some example embodiments, UE 640 can receive an RRC configuration message that includes LTM configuration, for example... LTM-Config IE. LTM configuration may also include configurations for UE 640 to perform early TA acquisition, such as RACH resources.

[0144] When configured by the network, the TCI state of one or more cells different from the currently serving cell can be activated. For example, the TCI state of LTM candidate cells can be activated in advance before any of these cells becomes the serving cell. This allows the UE 640 to perform DL synchronization with these cells, thereby facilitating a faster handover to one of these cells when a handover is triggered. In this way, the UE 640 stores the activated TCI states for some LTM candidate cells.

[0145] When configured by the network, a UL TA acquisition process can be initiated for one or more cells different from the current serving cell. For example, the network (e.g., source CU 610 or source DU 620) can request UE 640 to perform early TA acquisition for candidate cells before cell handover. Early TA acquisition is triggered by a PDCCH command. The candidate gNB-DU (such as DU 625) to which the candidate cell belongs calculates the TA value and sends it to source DU 620 via target CU 615 and source CU 610. When LTM cell handover is triggered, the serving cell / DU 620 sends the TA value to UE 640 in the LTM cell handover command MAC CE. In this way, source DU 620 stores early TA values ​​for some LTM candidate cells.

[0146] In procedure 650, UE 640 performs a CHO procedure to a candidate cell at 602. Specifically, UE 640 is triggered to perform a CHO to a candidate cell after the execution conditions associated with a CHO candidate cell are met.

[0147] In some implementations, if a radio link failure (RLF) occurs, UE 640 can be triggered to initiate cell selection for reconstruction purposes. Figure 6B (Not shown in the image). In some examples, if an LTM candidate cell or a CHO candidate cell is selected, the UE 640 can perform the LTM procedure or the CHO procedure instead of performing a reconstruction.

[0148] In some implementations, after UE 640 is triggered to perform a CHO procedure to a candidate cell, or after UE 640 successfully performs a CHO procedure to a candidate cell, UE 640 may continue to store the active TCI state for some candidate cells. In some examples, UE 640 may also store RACH resource and CSI resource configurations used for early TA acquisition.

[0149] In some implementations, after UE 640 is triggered to perform a CHO procedure to a candidate cell, or after UE 640 successfully performs a CHO procedure to a candidate cell, UE 640 may release the active TCI state for some candidate cells.

[0150] In procedure 650, target DU 625 sends an access success message to target CU 615 at 611. In some implementations, the access success message at 611 may be sent along with the target cell ID after a successful CHO procedure, LTM-based recovery, or CHO-based recovery.

[0151] In procedure 650, target CU 615 sends a handover success message to source CU 610 at 612. In some implementations, after receiving the access success message, target CU 615 sends an Xn message to source CU 610, including the target cell ID and some indications; for example, the Xn message could be a handover success message. In some examples, the handover success message can be used to notify UE 640 that it has successfully accessed the target cell.

[0152] In some examples, a switchover success message may include one or more of the following: a request for TCI status activation, a request for RACH resources for early TA acquisition, a request for CSI resource configuration, or a request for an early TA value stored in the source DU 620.

[0153] In process 650, source CU 610 sends a request to source DU 620 at 613. In some implementations, source CU 610 may send the request to source DU 620 after receiving an Xn message (including one or more requests) from target CU 615. In some examples, the request at 613 may include one or more requests included in the Xn message from target CU 615. In some examples, the request at 613 may include one or more of the following: a request for TCI state activation, a request for RACH resources for early TA acquisition, a request for CSI resource configuration, or a request for an early TA value stored in source DU 620.

[0154] In procedure 650, source DU 620 sends a response to source CU 610 at 614. In some implementations, the response at 614 may include: an active TCI state for some candidate cells and / or an early TA value for some candidate cells.

[0155] In process 650, source CU 610 sends another Xn message to target CU 615 at 616, and target CU 615 further sends another message to target DU 625 at 617. In some examples, each of the Xn message at 616 and the message at 617 may include an active TCI state for some candidate cells and / or an early TA value for some candidate cells. In other words, the active TCI state for some candidate cells and / or the early TA value for some candidate cells can be forwarded from source DU 620 to target DU 625 by source CU 610 and target CU 615.

[0156] In some other example implementations, such as Figure 6B As shown, UE 640 can send a report to target DU 625 at 618, and the report can include an indication that the active TCI status for some candidate cells and / or the early TA value for some candidate cells is available at UE 640.

[0157] In some examples, if target DU 625 requires the active TCI status and / or early TA values ​​for some candidate cells, target DU 625 may send another request to UE 640 in response to receiving a report. Furthermore, UE 640 may send another message to target DU 625, which may include the active TCI status and / or early TA values ​​for some candidate cells.

[0158] In some other examples, if the target DU 625 does not need them, the target DU 625 may send a removal instruction to the UE 640, and in addition, the UE 640 may remove (or delete, release) the active TCI state for some candidate cells and / or the early TA value for some candidate cells based on the removal instruction.

[0159] It should be understood that in some cases, step 618 may be omitted. In some other cases, if step 618 is performed, the access success message at 611, the handover success message at 612, and the request for TCI state activation in the request at 613 may be removed, and therefore, the response at 614, the Xn message at 616, and the message at 617 with activated TCI state for some candidate cells may be removed.

[0160] According to the reference Figures 6A to 6B Some embodiments provide a technical solution for transferring the activated TCI state and / or early TA after CHO (or CHO-based recovery or LTM-based recovery).

[0161] Figure 7 An example of a device 700 suitable for implementing embodiments of the present disclosure is illustrated. Device 700 may be an example of a UE or BS as described herein. Device 700 may support wireless communication with a UE, MN, SN, CU, DU, or any combination thereof. Device 700 may include components for bidirectional communication, including components for transmitting and receiving communications (such as processor 702, memory 704, transceiver 706, and optional I / O controller 708). These components may communicate electronically or be otherwise coupled (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0162] Processor 702, memory 704, transceiver 706, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of the present disclosure described herein. For example, processor 702, memory 704, transceiver 706, or various combinations thereof, or components thereof, may support methods for performing one or more of the operations described herein.

[0163] In some implementations, processor 702, memory 704, transceiver 706, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise supporting components for performing the functions described in this disclosure. In some implementations, processor 702 and memory 704 coupled to processor 702 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in memory 704 by processor 702).

[0164] For example, according to the examples disclosed herein, processor 702 may support wireless communication at device 700. Processor 702 may be configured to operate to support components used for the operations described above.

[0165] Processor 702 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, processor 702 may be configured to use a memory controller to operate a memory array. In some other implementations, the memory controller may be integrated into processor 702. Processor 702 may be configured to execute computer-readable instructions stored in memory (e.g., memory 704) to cause device 700 to perform various functions of this disclosure.

[0166] Memory 704 may include random access memory (RAM) and read-only memory (ROM). Memory 704 may store computer-readable, computer-executable code, including instructions that, when executed by processor 702, cause device 700 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code may not be directly executed by processor 702, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, memory 704 may include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0167] I / O controller 708 can manage the input and output signals of device 700. I / O controller 708 can also manage peripheral devices not integrated into device 700. In some implementations, I / O controller 708 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 708 can utilize an operating system such as iOS®, Android®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or other known operating systems. In some implementations, I / O controller 708 can be implemented as part of a processor, such as processor 702. In some implementations, a user can interact with device 700 via I / O controller 708 or via hardware components controlled by I / O controller 708.

[0168] In some implementations, device 700 may include a single antenna 710. However, in other implementations, device 700 may have more than one antenna 710 (i.e., multiple antennas), including multiple antenna panels or antenna arrays, which may be able to transmit or receive multiple wireless transmissions concurrently. Transceiver 706 may communicate bidirectionally via one or more antennas 710, wired or wireless links, as described herein. For example, transceiver 706 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 706 may also include a modem for modulating packets, providing modulated packets to one or more antennas 710 for transmission, and demodulating packets received from one or more antennas 710. Transceiver 706 may include one or more transmit chains, one or more receive chains, or combinations thereof.

[0169] The transmission chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. At least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmission chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmission chain may also include one or more antennas 710 for transmitting the amplified signal over the air or wireless medium.

[0170] The receiver chain can be configured to receive signals (e.g., control information, data, packets) via a wireless medium. For example, the receiver chain may include one or more antennas 710 for receiving signals over the air or via a wireless medium. The receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain may include at least one demodulator configured to demodulate the received signal and acquire the transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0171] Figure 8 An example of a processor 800 suitable for implementing some embodiments of the present disclosure is illustrated. Processor 800 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 800 may include a controller 802 configured to perform various operations according to the examples described herein. Processor 800 may optionally include at least one memory 804, such as an L1 / L2 / L3 cache. Additionally or alternatively, processor 800 may optionally include one or more arithmetic logic units (ALUs) 806. One or more of these components may be electronically communicated or otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0172] Processor 800 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, send, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to the processor chipset (e.g., processor 800) or included in the processor chipset), or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase-change memory (PCM), etc.).

[0173] Controller 802 can be configured to manage and coordinate various operations of processor 800 (e.g., signaling, receiving, acquiring, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 800 to support various operations according to the examples described herein. For example, controller 802 can operate as a control unit of processor 800 to generate control signals for managing the operation of various components of processor 800. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating the timing of operations.

[0174] Controller 802 can be configured to fetch (e.g., fetch, retrieve, receive) instructions from memory 804 and determine subsequent instructions(s) to be executed, enabling processor 800 to support various operations according to the examples described herein. Controller 802 can be configured to track the memory addresses of instructions associated with memory 804. Controller 802 can be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 802 can be configured to interpret instructions and determine control signals to be output to other components of processor 800, enabling processor 800 to support various operations according to the examples described herein. Additionally or alternatively, controller 802 can be configured to manage data flow within processor 800. Controller 802 can be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 800.

[0175] Memory 804 may include one or more caches (e.g., memory or other memory, such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc., local to or included in processor 800). In some implementations, memory 804 may reside within or on the processor chipset (e.g., local to processor 800). In some other implementations, memory 804 may reside outside the processor chipset (e.g., remote from processor 800).

[0176] Memory 804 may store computer-readable, computer-executable code, including instructions that, when executed by processor 800, cause processor 800 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. Controller 802 and / or processor 800 may be configured to execute computer-readable instructions stored in memory 804 to cause processor 800 to perform various functions. For example, processor 800 and / or controller 802 may be coupled to or connected to memory 804, and processor 800, controller 802, and memory 804 may be configured to perform the various functions described herein. In some examples, processor 800 may include multiple processors, and memory 804 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, and these processors and memories may be configured individually or collectively to perform the various functions described herein.

[0177] One or more ALU 806s can be configured to support a variety of operations as described in the examples herein. In some implementations, one or more ALU 806s may reside within or on a processor chipset (e.g., processor 800). In some other implementations, one or more ALU 806s may reside outside the processor chipset (e.g., processor 800). One or more ALU 806s can perform one or more calculations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 806s can receive input operands and an opcode that determines the operation to be performed. One or more ALU 806s are configured with a variety of logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Alternatively or additionally, one or more ALU 806s may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALU 806s to handle conditional operations, comparisons, and bitwise operations.

[0178] Based on the examples disclosed herein, processor 800 may support wireless communication. Processor 800 may be configured or operable to support components used in some embodiments of this disclosure.

[0179] Figure 9 A flowchart illustrating a method 900 performed by a UE according to various aspects of this disclosure is shown. Operation of method 900 may be implemented by the device or its components described herein. For example, operation of method 900 may be performed by… Figure 2B The UE 240 in the system executes the function. In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described function. Alternatively or alternatively, the device can use dedicated hardware to perform aspects of the described function.

[0180] At 910, the method may include: receiving a first configuration related to the PCell change from the MN. The operation of 910 can be performed according to the examples described herein. In some implementations, aspects of the operation of 910 may be derived from references... Figure 2B The aforementioned UE 240 is executed.

[0181] At 920, the method may include receiving a second configuration related to PSCell addition or PSCell modification from MN or SN. The operation of 920 can be performed according to the examples described herein. In some implementations, aspects of the operation of 920 may be derived from references... Figure 2B The aforementioned UE 240 is executed.

[0182] At 930, the method may include: performing a first operation based on the determination that the PCell change was triggered. The operation at 930 can be performed according to the examples described herein. In some implementations, aspects of the operation at 930 may be derived from references. Figure 2B The aforementioned UE 240 is executed.

[0183] At 940, the method may include: performing a second operation based on a determination triggered by a PSCell addition or PSCell change. The operation at 940 can be performed according to the examples described herein. In some implementations, aspects of the operation at 940 may be derived from references. Figure 2B The aforementioned UE 240 is executed.

[0184] Figure 10 A flowchart illustrating a method 1000 performed by an MN according to various aspects of this disclosure is shown. Operation of method 1000 may be implemented by the device or its components described herein. For example, operation of method 1000 may be performed by… Figure 2BThe MN210 in the device executes the function. In some implementations, the device can execute an instruction set to control the functional elements of the device to perform the described function. Alternatively or alternatively, the device can use dedicated hardware to perform aspects of the described function.

[0185] At point 1010, the method may include: sending a first configuration related to a PCell change to the UE, wherein the UE is also configured with a second configuration related to a PSCell addition or change. The operation of 1010 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1010 may be derived from references. Figure 2B The MN 210 is executed.

[0186] At point 1020, the method may include: receiving a report from the UE indicating that a PCell change or PSCell addition or PSCell change has been performed. The operation at point 1020 can be performed according to the examples described herein. In some implementations, aspects of the operation at point 1020 may be derived from references. Figure 2B The MN 210 is executed.

[0187] Figure 11 A flowchart illustrating method 1100 performed by an SN according to various aspects of this disclosure is shown. Operation of method 1100 may be implemented by the device or its components described herein. For example, operation of method 1100 may be performed by… Figure 2B The SN220 in the device executes the function. In some implementations, the device can execute an instruction set to control the functional elements of the device to perform the described function. Alternatively or alternatively, the device can use dedicated hardware to perform aspects of the described function.

[0188] At 1110, the method may include: sending a second configuration related to the PSCell change to the UE, wherein the UE is also configured with a first configuration related to the PCell change. The operation at 1110 can be performed according to the examples described herein. In some implementations, aspects of the operation at 1110 may be derived from references... Figure 2B The aforementioned SN 220 is executed.

[0189] At 1120, the method may include: receiving a report from the UE indicating that a PCell change or PSCell change has been performed. The operation at 1120 can be performed according to the examples described herein. In some implementations, aspects of the operation at 1120 may be derived from references. Figure 2B The aforementioned SN 220 is executed.

[0190] It should be noted that the methods described in this paper describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are also possible. Furthermore, aspects from two or more methods can be combined.

[0191] The various illustrative blocks and components described herein can be implemented or executed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware component or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0192] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwired, or any combination thereof. Features implementing the functions can also be physically located in various locations, including being distributed such that portions of the functions are implemented at different physical locations.

[0193] Computer-readable media include both non-transitory computer storage media and communication media, with communication media including any medium that facilitates the transfer of a computer program from one place to another. Non-transitory storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer. For example, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, optical disc (CD) ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures and can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

[0194] As used herein, including in the claims, the article “a” preceding an element is a non-limiting article and should be understood to mean “at least one” or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein, including in the claims, the word “or” used in a list of items (e.g., a list of items beginning with phrases such as “at least one of…” or “one or more of…” or “one or both of…”) indicates an inclusive list, such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase “based on” should not be construed as a reference to a closed set of conditions. For example, an example step described as “based on condition A” may be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as the phrase “at least partially based on.” Furthermore, as used herein, including in the claims, a “set” may include one or more elements.

[0195] The description provided herein is intended to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE), comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the UE: Receive the first configuration related to the changes in the primary cell (PCell) from the master node (MN); Receive a second configuration related to the addition or change of primary / secondary cells (PSCell) from the MN or secondary node (SN); as well as Based on the determination that the PCell change is triggered, perform the first operation; or Based on the determination that the addition or change of the PSCell is triggered, the second operation is performed.

2. The UE according to claim 1, wherein the PCell change is a conditional handover (CHO) procedure, and the PSCell change is a Layer 1 or Layer 2 triggered mobility (LTM) procedure for the secondary cell group (SCG).

3. The UE of claim 2, wherein the at least one processor is further configured to cause the UE to: Based on the determination that the execution conditions for the candidate cells used in the CHO process are met, it is determined that the PCell change is triggered. And the first operation described therein includes one of the following: Perform the CHO procedure for the candidate cell; A first report is sent to the SN, the first report indicating that the execution conditions for the candidate cell used in the CHO process have been met; The SCG LTM command is ignored during the CHO process; or Release the second configuration of the LTM process for SCG.

4. The UE of claim 3, wherein the first report indicates the duration of the CHO process.

5. The UE according to claim 3, wherein the first operation further comprises: Based on the determination that the CHO process is completed, a second report is sent to the SN, the second report indicating that the CHO process is complete.

6. The UE of claim 2, wherein the at least one processor is further configured to cause the UE to: Based on the determination that the SCG LTM command indicating the candidate cell has been received, it is determined that the PSCell change has been triggered. And the second operation described therein includes one of the following: Perform the LTM procedure for the SCG to the candidate cell; Stop evaluating the execution conditions used for the CHO process; If the execution conditions for the CHO procedure are met, the CHO procedure is not executed. or Pause the CHO process until the LTM process for SCG is completed.

7. The UE according to claim 1, wherein the PCell change is a Primary Cell Group (MCG) LTM procedure, the PSCell addition is a Conditional PSCell Addition (CPA) procedure, and the PSCell change is a Conditional PSCell Change (CPC) procedure or a subsequent CPC procedure.

8. The UE of claim 7, wherein the at least one processor is further configured to cause the UE to: Based on the determination that the LTM cell handover command for the MCG is received from the MN, it is determined that the PCell change has been triggered. And the first operation described therein includes one of the following: Based on the LTM cell handover command for the MCG, the MCG LTM process is executed; Stop evaluating the conditions for adding or changing the PSCell; Release the second configuration added to or changed by the PSCell; or In response to the conditions for the candidate cell for the PSCell addition or PSCell change being met, both the MCGLTM procedure and the PSCell addition or PSCell change are performed.

9. The UE according to claim 8, wherein the first operation further comprises: After the MCG LTM process is completed, the conditions for the subsequent CPC process are evaluated.

10. The UE of claim 7, wherein the at least one processor is further configured such that the UE: Based on the determination that the conditions for the candidate cells used for the PSCell addition or PSCell change are met, it is determined that the PSCell addition or PSCell change is triggered. And the second operation described therein includes one of the following: Perform the addition or modification of the PSCell for the candidate cell; During the PSCell addition or PSCell change, LTM cell handover commands for MCG are ignored; A third report is sent to the MN, the third report indicating that the conditions for adding or changing the PSCell have been met; Release the first configuration of the MCG LTM process; or In response to receiving an LTM cell handover command for the MCG from the MN, both the MCG LTM procedure and the PSCell addition or PSCell modification are performed.

11. The UE of claim 10, wherein the second operation further comprises: Send an indication to the MN that the LTM cell handover command for the MCG is ignored due to the execution of the PSCell addition or PSCell change.

12. A master node (MN) comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the MN: Sending a first configuration related to a change in the primary cell (PCell) to the user equipment (UE), wherein the UE is also configured with a second configuration related to the addition or change of the primary / secondary cell (PSCell); and The UE receives a report indicating that the PCell has been changed or the PSCell has been added or the PSCell change has been performed.

13. The MN of claim 12, wherein the at least one processor is further configured such that the MN: Send the second configuration related to the addition or change of the PSCell to the UE.

14. The MN of claim 12, wherein the PCell change is a conditional handover (CHO) procedure, and the PSCell change is a Layer 1 or Layer 2 triggered mobility (LTM) procedure for the secondary cell group (SCG).

15. The MN of claim 12, wherein the PCell change is a primary cell group (MCG) LTM process, the PSCell addition is a conditional PSCell addition (CPA) process, and the PSCell change is one of the following: a conditional PSCell change (CPC) process, or a subsequent CPC process.

16. The MN of claim 15, wherein the report includes a third report indicating that the conditions for adding or changing the PSCell are met.

17. The MN of claim 16, wherein the at least one processor is further configured such that the MN: Release the first configuration of the MCG LTM process.

18. The MN of claim 15, wherein the at least one processor is further configured such that the MN: Send an LTM cell handover command for the MCG to the UE; and The UE receives an indication that the LTM cell handover command for the MCG is ignored due to the execution of the PSCell addition or PSCell change.

19. An auxiliary node (SN), comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the SN: Send a second configuration related to a change in primary / secondary cell (PSCell) to the user equipment (UE), wherein the UE is also configured with a first configuration related to a change in primary cell (PCell); and The UE receives a report indicating that a PCell change or a PSCell change has been performed.

20. The SN of claim 19, wherein the PCell change is a conditional handover (CHO) procedure, and the PSCell change is a Layer 1 or Layer 2 triggered mobility (LTM) procedure for the secondary cell group (SCG).

Images