Mechanisms for CHOs with candidate SCGs

Abstract

Illustrative embodiments of this disclosure relate to a UE, source MN, target MN, source SN, method, processor, and computer storage medium for a mechanism for a CHO with a candidate SCG. In this solution, the UE may receive a first configuration comprising one or more CHO execution conditions for a CHO with a candidate SCG and one or more CPAC execution conditions for a CHO with a candidate SCG. In some examples, the UE may receive a second configuration comprising at least one time threshold, the at least one time threshold used to determine whether to store or report first information relating to a successful CHO procedure with a candidate SCG. In some examples, if at least one trigger condition relating to at least one time threshold is met, the UE may store or report first information relating to a successful CHO procedure with a candidate SCG. Thus, first information relating to a successful CHO procedure with a candidate SCG may be stored or reported by the UE, and in some examples, further MRO may be performed by a network node.

Description

Technical Field

[0001] The present disclosure relates to wireless communication, and more particularly, to a device, method, apparatus, and computer-readable medium for a mechanism for conditional handover (CHO) with a candidate secondary cell group (SCG).

Background Art

[0002] A wireless communication system may include one or more network communication devices, such as a base station, which may sometimes be referred to by terms such as an evolved Node B (eNB), a next-generation Node B (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 sometimes be referred to by terms such as a user equipment (UE) or other suitable terms. The wireless communication system may support wireless communication with one or more user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). Additionally, the wireless communication system may support wireless communication across various wireless access technologies, including third-generation (3G) wireless access technology, fourth-generation (4G) wireless access technology, fifth-generation (5G) wireless access technology, among suitable wireless access technologies beyond 5G (e.g., sixth-generation (6G)).

[0003] To enhance mobility, it has been proposed to specify CHO with candidate SCG(s) procedures. In CHO procedures with candidate SCG(s) (i.e., CHO procedures with at least one candidate SCG, or CHO procedures with one or more candidate SCGs), the UE evaluates whether the CHO execution conditions and CPC / CPA execution conditions are met. If both the CHO execution conditions and CPC / CPA execution conditions are met, the UE executes the CHO and CPAC. To improve mobility robustness, self-organizing network (SON) extensions for CHO with candidate SCGs should be considered. [Overview of the project] [Means for solving the problem]

[0004] This disclosure relates to devices, methods, apparatus, and computer-readable media for mechanisms for CHOs with candidate SCGs.

[0005] In some implementations, a UE is provided. The UE comprises at least one memory and at least one processor coupled to at least one memory, the at least one processor being configured to cause the UE to receive from a first radio access network (RAN) node a first configuration comprising one or more CHO execution conditions for a CHO with a candidate SCG and one or more conditional primary SCG cell (PSCell) add and modify (CPAC) execution conditions for a CHO with a candidate SCG, and to receive from the first RAN node a second configuration comprising at least one time threshold, wherein at least one time threshold is used to determine whether first information relating to a successful CHO procedure with a candidate SCG should be stored or reported, and to store or report first information relating to a successful CHO procedure with a candidate SCG in accordance with the determination that at least one trigger condition relating to at least one time threshold is met.

[0006] In some implementations, a first RAN node is provided. The first RAN node comprises at least one memory and at least one processor coupled to at least one memory, the at least one processor configured to cause the first RAN node to send to the UE a first configuration comprising one or more CHO execution conditions for a CHO with a candidate SCG and one or more CPAC execution conditions for a CHO with a candidate SCG, and a second configuration comprising at least one time threshold, the at least one time threshold used to determine whether to store or report first information relating to a successful CHO procedure with a candidate SCG.

[0007] In some implementations, a target MN is provided. The target MN comprises at least one memory and at least one processor coupled to at least one memory, the at least one processor being configured to cause the target MN to receive first or second information from a UE or a second RAN node, the UE being configured with one or more CHO execution conditions for a CHO with a candidate SCG and one or more CPAC execution conditions for a CHO with a candidate SCG, the second RAN node being a target secondary node (SN) or another RAN node, and to perform mobility robustness optimization (MRO) analysis based on the first or second information.

[0008] In some implementations, a source SN is provided. The source SN comprises at least one memory and at least one processor coupled to the at least one memory, the at least one processor configured to cause the source SN to determine time-related information comprising at least one last configured timer value for T310 or T312, or a fifth time threshold related to the T310 trigger condition for the source PSCell, or a sixth time threshold related to the T312 trigger condition for the source PSCell, and to send the time-related information to the source MN.

[0009] In some implementations, a method is provided that is performed by the UE. The method comprises receiving from a first RAN node a first configuration comprising one or more CHO execution conditions for a CHO with a candidate SCG and one or more CPAC execution conditions for a CHO with a candidate SCG, and receiving from the first RAN node a second configuration comprising at least one time threshold, wherein at least one time threshold is used to determine whether first information relating to a successful CHO procedure with a candidate SCG should be stored or reported, and storing or reporting first information relating to a successful CHO procedure with a candidate SCG according to the determination that at least one trigger condition relating to at least one time threshold is met.

[0010] In some implementations, a method is provided that is executed by a first RAN node. The method comprises sending a first configuration to the UE comprising one or more CHO execution conditions for a CHO with a candidate SCG and one or more CPAC execution conditions for a CHO with a candidate SCG, and sending a second configuration to the UE comprising at least one time threshold, the at least one time threshold being used to determine whether the first information relating to a successful CHO procedure with a candidate SCG should be stored or reported.

[0011] In some implementations, a method is provided that is performed by the target MN. The method comprises receiving first or second information from a UE or a second RAN node, wherein the UE is configured with one or more CHO execution conditions for a CHO with a candidate SCG and one or more CPAC execution conditions for a CHO with a candidate SCG, the second RAN node is a target secondary node (SN) or a further RAN node, and performing a mobility robustness optimization (MRO) analysis based on the first or second information.

[0012] In some implementations, a method is provided that is performed by the source SN. The method comprises determining time-related information comprising one of the following: the last configured timer value for T310 or T312, or a fifth time threshold related to the T310 trigger condition for the source PSCell, or a sixth time threshold related to the T312 trigger condition for the source PSCell; and sending the time-related information to the source MN.

[0013] In some implementations, a processor for wireless communication is provided. The processor comprises at least one controller coupled to at least one memory, the at least one controller configured to cause the processor to receive from a first RAN node a first configuration comprising one or more CHO execution conditions for a CHO with a candidate SCG and one or more CPAC execution conditions for a CHO with a candidate SCG, and to receive from a first RAN node a second configuration comprising at least one time threshold, wherein at least one time threshold is used to determine whether to store or report first information relating to a successful CHO procedure with a candidate SCG, and to store or report first information relating to a successful CHO procedure with a candidate SCG according to the determination that at least one trigger condition related to at least one time threshold is met.

[0014] In some implementations, a processor for wireless communication is provided. The processor comprises at least one controller coupled to at least one memory, the at least one controller configured to cause the processor to send to the UE a first configuration comprising one or more CHO execution conditions for a CHO with a candidate SCG and one or more CPAC execution conditions for a CHO with a candidate SCG, and a second configuration comprising at least one time threshold, the at least one time threshold used to determine whether to store or report the first information relating to a successful CHO procedure with a candidate SCG.

[0015] In some implementations, a processor for wireless communication is provided. The processor comprises at least one controller coupled to at least one memory, the at least one controller configured to cause the processor to receive first or second information from a UE or a second RAN node, wherein the UE is configured with one or more CHO execution conditions for a CHO with a candidate SCG and one or more CPAC execution conditions for a CHO with a candidate SCG, the second RAN node is a target secondary node (SN) or further RAN node, and to perform mobility robustness optimization (MRO) analysis based on the first or second information.

[0016] In some implementations, a processor for wireless communication is provided. The processor comprises at least one controller coupled to at least one memory, the at least one controller configured to cause the processor to determine time-related information comprising at least one last configured timer value for T310 or T312, or one of a fifth time threshold related to a T310 trigger condition for a source PSCell, or a sixth time threshold related to a T312 trigger condition for a source PSCell, and to transmit the time-related information to the source MN.

[0017] Some implementations of the methods and UEs described herein further include determining that at least one trigger condition associated with at least one time threshold is met, based on the determination that the duration between the time when one or more CHO execution conditions for a CHO with a candidate SCG are met and the time when one or more CPAC execution conditions for a CHO with a candidate SCG are met exceeds a seventh time threshold.

[0018] Some implementations of the methods and UEs described herein further include sending first information relating to a successful CHO procedure with a candidate SCG to a second RAN node, the second RAN node being one of the target MN, target SN, or further RAN nodes.

[0019] The methods and some implementations of the UE described herein further include sending instructions relating to the availability of first information to a second RAN node and receiving a request for first information from the second RAN node.

[0020] The methods and some implementations of the UE described herein further include transmitting capability information of the UE indicating that the UE supports a CHO procedure with a candidate SCG, or that the UE has the ability to store or report first information relating to a successful CHO procedure with a candidate SCG.

[0021] Some implementations of the methods and UEs described herein further include receiving a third configuration from a first RAN node having at least one CHO execution condition for a mere CHO (CHO-only), and / or receiving a fourth configuration from the first RAN node having at least one CHO execution condition for a CHO with an SCG.

[0022] Some implementations of the methods and UEs described herein further include performing a simple CHO execution toward a first target PCell that satisfies at least one of the at least one CHO execution conditions for a simple CHO, according to the determination that one or more CHO execution conditions for a CHO with a candidate SCG or one or more CPAC execution conditions for a CHO with a candidate SCG are not met, and at least one of the at least one CHO execution conditions for a simple CHO is met; or performing a CHO with an SCG execution toward a second target PCell that satisfies at least one of the at least one CHO execution conditions for a CHO with an SCG, and a target PSCell associated with the second target PCell, according to the determination that one or more CHO execution conditions for a CHO with a candidate SCG or one or more CPAC execution conditions for a CHO with a candidate SCG are not met, and at least one of the at least one CHO execution conditions for a CHO with an SCG is met.

[0023] The methods and some implementations of the UE described herein further include storing or reporting second information.

[0024] The methods and some implementations of the UE described herein further include transmitting second information to a second RAN node, the second RAN node being one of the target MN, target SN, or further RAN nodes.

[0025] The methods and some implementations of the UE described herein further include storing or reporting first failure information in accordance with the determination that access to a first target PCell for a simple CHO execution or access to a second target PCell for a CHO execution with an SCG fails.

[0026] In some implementations of the methods and UEs described herein, further comprising storing or reporting second failure information according to a determination that access to a target PSCell associated with a second target PCell for execution of a CHO with an SCG fails.

[0027] In some implementations of the methods and the first RAN node described herein, further comprising receiving a first time threshold from a candidate MN.

[0028] In some implementations of the methods and the first RAN node described herein, further comprising receiving an instruction from a candidate MN for determining a fifth and / or a sixth time threshold, and determining the fifth and / or the sixth time threshold based on the instruction.

[0029] In some implementations of the methods and the first RAN node described herein, further comprising transmitting an instruction to a source SN for providing at least one timer value configured last for T310 or T312, receiving at least one timer value configured last for T310 or T312 from the source SN, and determining a fifth and / or a sixth time threshold based on at least one timer value configured last for T310 or T312.

[0030] In some implementations of the methods and the first RAN node described herein, further comprising receiving a fifth and / or a sixth time threshold from a source SN or a candidate MN.

[0031] In some implementations of the methods and the first RAN node described herein, further comprising receiving first information related to a successful CHO procedure with a candidate SCG from a second RAN node, where the second RAN node is one of a target MN, a target SN, or a further RAN node.

[0032] The methods described herein and some implementations of the first RAN node further include sending a third configuration to the UE having at least one CHO execution condition for a mere CHO, and / or sending a fourth configuration to the UE having at least one CHO execution condition for a CHO accompanied by an SCG.

[0033] The methods described herein and some implementations of the first RAN node further include receiving second information from a second RAN node, which is a target MN, a target SN, or one of further RAN nodes.

[0034] The methods described herein and some implementations of the first RAN node further include generating an analysis result indicating at least one of the following: whether at least one parameter of one or more CHO execution conditions for a CHO with a candidate SCG needs to be optimized, or whether at least one parameter of at least one CHO execution condition for a CHO alone needs to be optimized, or whether at least one parameter of at least one CHO execution condition for a CHO with an SCG needs to be optimized, or whether at least one parameter of one or more CPAC execution conditions for a CHO with a candidate SCG needs to be optimized, and transmitting the analysis result to a target MN.

[0035] The methods and some implementations of the target MN described herein further include receiving first failure information from further RAN nodes.

[0036] The methods and some implementations of the target MN described herein further include receiving second failure information from the UE or further RAN nodes.

[0037] The methods and some implementations of the target MN described herein further include generating an analysis result indicating at least one of the following: whether at least one parameter of one or more CHO execution conditions for a CHO with a candidate SCG needs to be optimized, or whether at least one parameter of at least one CHO execution condition for a CHO alone needs to be optimized, or whether at least one parameter of at least one CHO execution condition for a CHO with an SCG needs to be optimized, or whether at least one parameter of one or more CPAC execution conditions for a CHO with a candidate SCG needs to be optimized.

[0038] Some implementations of the methods and source SNs described herein further include receiving instructions from the source MN for determining or providing time-related information.

[0039] In some implementations of the methods and apparatus described herein, at least one time threshold comprises one of the following: a first time threshold related to a T304 trigger condition for a candidate target PCell, a second time threshold related to a T310 trigger condition for a source PCell, or a third time threshold related to a T312 trigger condition for measurement identification of a candidate target PCell.

[0040] In some implementations of the methods and apparatus described herein, at least one time threshold further comprises one of the following: a fourth time threshold related to a T304 trigger condition for a candidate target PSCell, a fifth time threshold related to a T310 trigger condition for a source PSCell, or a sixth time threshold related to a T312 trigger condition for a source PSCell.

[0041] In some implementations of the methods and apparatus described herein, at least one time threshold comprises a seventh time threshold relating to the duration between the time at which one or more CHO execution conditions for a CHO with a candidate SCG are met and the time at which one or more CPAC execution conditions for a CHO with a candidate SCG are met.

[0042] In some implementations of the methods and apparatus described herein, the first information relating to a successful CHO procedure with a candidate SCG comprises a causal value indicating that the first information relating to a successful CHO procedure with a candidate SCG is stored due to the fulfillment of at least one trigger condition, the type of the first satisfied execution condition for the CHO with a candidate SCG, the duration between two satisfied execution conditions for the CHO with a candidate SCG, a type indicating that it is a CHO procedure with a candidate SCG, one or more last received CHO execution conditions for the CHO with a candidate SCG, one or more last received CPAC execution conditions for the CHO with a candidate SCG, recent radio measurement results of at least one adjacent cell, an indication indicating whether at least one adjacent cell belongs to at least one candidate PCell configured for the CHO with a candidate SCG, an indication indicating whether at least one adjacent cell belongs to at least one candidate PSCell configured for the CHO with a candidate SCG, a list of candidate PCells configured for the CHO with a candidate SCG that are not in at least one adjacent cell, or a list of candidate PSCells configured for the CHO with a candidate SCG that are not in at least one adjacent cell.

[0043] In some implementations of the methods and apparatus described herein, the first information is contained in one of the following: a successful handover report (SHR) and a successful PSCell change report (SPR), or a successful handover report with a PSCell change.

[0044] In some implementations of the methods and apparatus described herein, the second information is the type of first satisfied execution condition for a CHO with a candidate SCG, one or more last received CHO execution conditions for a CHO with a candidate SCG, one or more last received CPAC execution conditions for a CHO with a candidate SCG, at least one last received CHO execution condition for a simple CHO, at least one last received CHO execution condition for a CHO with an SCG, recent radio measurement results of at least one adjacent cell, an indication that at least one adjacent cell belongs to at least one candidate PCell configured for a CHO with a candidate SCG, at least one adjacent cell belongs to at least one candidate PCell configured for a simple CHO The system includes one of the following: an instruction indicating whether a cell belongs to a given cell; an instruction indicating whether at least one adjacent cell belongs to at least one candidate PCell configured for a CHO with an SCG; an instruction indicating whether at least one adjacent cell belongs to at least one candidate PSCell configured for a CHO with a candidate SCG; a list of candidate PCells configured for a CHO with a candidate SCG that are not in at least one adjacent cell; a list of candidate PSCells configured for a CHO with a candidate SCG that are not in at least one adjacent cell; a list of candidate PCells configured for a CHO only that are not in at least one adjacent cell; or a list of candidate PCells configured for a CHO with an SCG that are not in at least one adjacent cell.

[0045] In some implementations of the methods and apparatus described herein, the type of first satisfied execution condition for a CHO with a candidate SCG indicates that the first satisfied execution condition for a CHO with a candidate SCG belongs to one or more CHO execution conditions for a CHO with a candidate SCG, and the second information indicates an ID and associated information of a candidate PCell in which the candidate PCell satisfies one of the one or more CHO execution conditions for a CHO with a candidate SCG, and the candidate PSCell does not satisfy one of the one or more CPAC execution conditions for a CHO with a candidate SCG. The system further comprises an ID indicating a candidate PSCell, a time length between a first time and a second time, a time length between a third time and a second time, or a time length between a third time and a first time, wherein the first time is the time when at least one CHO execution condition for a simple CHO is met, or at least one CHO execution condition for a CHO with an SCG is met, the second time is the time when one of the first configuration, third configuration, or fourth configuration is received, and the third time is the time when one or more CHO execution conditions for a CHO with a candidate SCG are met.

[0046] In some implementations of the methods and apparatus described herein, the type of first satisfied execution condition for a CHO with a candidate SCG indicates that the first satisfied execution condition for a CHO with a candidate SCG belongs to one or more CPAC execution conditions for a CHO with a candidate SCG, and the second information is an ID indicating a candidate PCell and associated with a candidate PCell in which the candidate PCell does not satisfy one of the one or more CHO execution conditions for a CHO with a candidate SCG, and the candidate PSCell satisfies one of the one or more CPAC execution conditions for a CHO with a candidate SCG. The system further comprises an ID indicating a candidate PSCell, a time length between a first time and a second time, a time length between a fourth time and a second time, or a time length between a fourth time and a first time, wherein the first time is the time when at least one CHO execution condition for a simple CHO is met, or at least one CHO execution condition for a CHO with an SCG is met, the second time is the time when one of the first, third, or fourth configurations is received, and the fourth time is the time when one or more CPAC execution conditions for a CHO with a candidate SCG are met.

[0047] In some implementations of the methods and apparatus described herein, the first failure information includes the ID of the source PCell, the ID of the first or second target PCell, the type of the first satisfied execution condition for the CHO with candidate SCG, the last received one or more CHO execution conditions for the CHO with candidate SCG, the last received one or more CPAC execution conditions for the CHO with candidate SCG, the last received at least one CHO execution condition for a simple CHO, the last received at least one CHO execution condition for a CHO with SCG, the most recent radio measurement result of at least one adjacent cell, an indication that at least one adjacent cell belongs to at least one candidate PCell configured for a CHO with candidate SCG, and at least one adjacent cell belonging to at least one candidate PCell configured for a simple CHO. The system includes one of the following: an instruction indicating whether a cell belongs to a cell; an instruction indicating whether at least one adjacent cell belongs to at least one candidate PCell configured for a CHO with an SCG; an instruction indicating whether at least one adjacent cell belongs to at least one candidate PSCell configured for a CHO with a candidate SCG; a list of candidate PCells configured for a CHO with a candidate SCG that are not in at least one adjacent cell; a list of candidate PSCells configured for a CHO with a candidate SCG that are not in at least one adjacent cell; a list of candidate PCells configured for a simple CHO that are not in at least one adjacent cell; a list of candidate PCells configured for a CHO with an SCG that are not in at least one adjacent cell; or a failure type; or an instruction indicating that a simple CHO execution or a CHO execution with an SCG will fail.

[0048] In some implementations of the methods and apparatus described herein, the type of first satisfied execution condition for a CHO with a candidate SCG indicates that the first satisfied execution condition for a CHO with a candidate SCG belongs to one or more CHO execution conditions for a CHO with a candidate SCG, the first failure information indicates that a candidate PCell satisfies one of the one or more CHO execution conditions for a CHO with a candidate SCG, and a candidate PSCell does not satisfy one of the one or more CPAC execution conditions for a CHO with a candidate SCG, the ID indicating a candidate PCell and the ID indicating a candidate PSCell associated with the candidate PCell, the time length between the first time and the second time, and the time between the third time and the second time. The configuration further comprises a time length, a time length between the third time and the first time, a time length between the first time and the fifth time, a time length between the second time and the fifth time, or a time length between the third time and the fifth time, wherein the first time is the time when at least one CHO execution condition for a simple CHO is met or at least one CHO execution condition for a CHO with an SCG is met, the second time is the time when one of the first configuration, the third configuration, or the fourth configuration is received, the third time is the time when one or more CHO execution conditions for a CHO with a candidate SCG are met, and the fifth time is the time when a simple CHO execution or an execution of a CHO with an SCG fails.

[0049] In some implementations of the methods and apparatus described herein, the type of first satisfied execution condition for a CHO with a candidate SCG indicates that the first satisfied execution condition for a CHO with a candidate SCG belongs to one or more CPAC execution conditions for a CHO with a candidate SCG, the first failure information indicates that the candidate PCell does not satisfy one of the one or more CHO execution conditions for a CHO with a candidate SCG, and the candidate PSCell satisfies one of the one or more CPAC execution conditions for a CHO with a candidate SCG, the ID indicating the candidate PCell and the ID indicating the candidate PSCell associated with the candidate PCell, the time length between the first time and the second time, and the time between the fourth time and the second time. The configuration further comprises a time length, a time length between the fourth time and the first time, a time length between the first time and the fifth time, a time length between the second time and the fifth time, or a time length between the fourth time and the fifth time, wherein the first time is the time when at least one CHO execution condition for a simple CHO is met or at least one CHO execution condition for a CHO with an SCG is met, the second time is the time when one of the first configuration, the third configuration, or the fourth configuration is received, the fourth time is the time when one or more CPAC execution conditions for a CHO with a candidate SCG are met, and the fifth time is the time when a simple CHO execution or an execution of a CHO with an SCG fails.

[0050] In some implementations of the methods and apparatus described herein, the second failure information includes the ID of the source PSCell, the ID of the target PSCell associated with the second target PCell, the type of the first satisfied execution condition for the CHO with candidate SCG, one or more last received CHO execution conditions for the CHO with candidate SCG, one or more last received CPAC execution conditions for the CHO with candidate SCG, at least one last received CHO execution condition for the CHO with SCG, recent radio measurement results of at least one adjacent cell, an indication that at least one adjacent cell belongs to at least one candidate PCell configured for the CHO with candidate SCG, and C with SCG The system includes one of the following: an instruction indicating whether at least one adjacent cell belongs to at least one candidate PCell configured for HO; an instruction indicating whether at least one adjacent cell belongs to at least one candidate PSCell configured for CHO with candidate SCG; a list of candidate PCells configured for CHO with candidate SCG that are not in at least one adjacent cell; a list of candidate PSCells configured for CHO with candidate SCG that are not in at least one adjacent cell; a list of candidate PCells configured for CHO with SCG that are not in at least one adjacent cell; or a failure type; or an instruction indicating that a simple CHO execution or a CHO execution with SCG will fail.

[0051] In some implementations of the methods and apparatus described herein, the type of first satisfied execution condition for a CHO with a candidate SCG indicates that the first satisfied execution condition for a CHO with a candidate SCG belongs to one or more CHO execution conditions for a CHO with a candidate SCG, and the second failure information indicates that a candidate PCell satisfies one of the one or more CHO execution conditions for a CHO with a candidate SCG, and a candidate PSCell does not satisfy one of the one or more CPAC execution conditions for a CHO with a candidate SCG, the ID of the candidate PCell and the ID of the candidate PSCell associated with the candidate PCell, and between the first time and the second time. The configuration further comprises a time length, a time length between the third time and the second time, a time length between the third time and the first time, a time length between the first time and the sixth time, a time length between the second time and the sixth time, or one of the time lengths between the third time and the sixth time, wherein the first time is the time when at least one CHO execution condition for a CHO with an SCG is met, the second time is the time when a first configuration or a fourth configuration is received, the third time is the time when one or more CHO execution conditions for a CHO with a candidate SCG are met, and the sixth time is the time when access to a target PSCell associated with a second target PCell fails.

[0052] In some implementations of the methods and apparatus described herein, the type of first satisfied execution condition for a CHO with a candidate SCG indicates that the first satisfied execution condition for a CHO with a candidate SCG belongs to one or more CPAC execution conditions for a CHO with a candidate SCG, and the second failure information indicates that the candidate PCell does not satisfy one of the one or more CHO execution conditions for a CHO with a candidate SCG, and the candidate PSCell satisfies one of the one or more CPAC execution conditions for a CHO with a candidate SCG, the ID of the candidate PCell and the ID of the candidate PSCell associated with the candidate PCell, and between the first time and the second time. The configuration further comprises a time length, a time length between the fourth time and the second time, a time length between the fourth time and the first time, a time length between the first time and the sixth time, a time length between the second time and the sixth time, or one of the time lengths between the fourth time and the sixth time, wherein the first time is the time when at least one CHO execution condition for a CHO with an SCG is met, the second time is the time when the first configuration or the fourth configuration is received, the fourth time is the time when one or more CPAC execution conditions for a CHO with a candidate SCG are met, and the sixth time is the time when access to the target PSCell associated with the second target PCell fails. [Brief explanation of the drawing]

[0053] [Figure 1] This figure shows an example of a wireless communication system in which several embodiments of the present disclosure may be implemented. [Figure 2] This is a schematic diagram of an exemplary communication network in which some embodiments of the present disclosure may be implemented. [Figure 3] This diagram illustrates an exemplary process for a CHO with a candidate SCG. [Figure 4] This is a signaling chart illustrating a communication process according to some exemplary embodiments of the present disclosure. [Figure 5] This is a signaling chart illustrating a communication process according to some exemplary embodiments of the present disclosure. [Figure 6A] These are some exemplary timing schematic diagrams according to some exemplary embodiments of the present disclosure. [Figure 6B] These are some exemplary timing schematic diagrams according to some exemplary embodiments of the present disclosure. [Figure 6C] These are some exemplary timing schematic diagrams according to some exemplary embodiments of the present disclosure. [Figure 6D] These are some exemplary timing schematic diagrams according to some exemplary embodiments of the present disclosure. [Figure 7] This figure shows an example of a device suitable for carrying out the embodiments of the present disclosure. [Figure 8] This figure shows an example of a processor suitable for implementing some embodiments of the present disclosure. [Figure 9] This is a flowchart illustrating an exemplary method implemented in a UE according to the aspects of this disclosure. [Figure 10] This is a flowchart of an exemplary method implemented in the source MN according to the aspects of this disclosure. [Figure 11] This is a flowchart of an exemplary method implemented in the target MN according to the aspects of this disclosure. [Figure 12] This is a flowchart of exemplary methods implemented in a source SN according to some embodiments of the present disclosure. [Modes for carrying out the invention]

[0054] Throughout the drawing, the same or similar reference numerals represent the same or similar elements.

[0055] The principles of this disclosure will now be described with reference to several embodiments. These embodiments are described for illustrative purposes only, without implying any limitation on the scope of this disclosure, and should be understood as being helpful to those skilled in the art in understanding and implementing this disclosure. The disclosure described herein may be implemented in various other ways than those described below. In the following description and claims, unless otherwise specified, all technical and scientific terms used herein have the same meaning as those generally understood by those skilled in the art to which this disclosure belongs.

[0056] References in this disclosure such as “one embodiment,” “an exemplary embodiment,” “one embodiment,” and “several embodiments” indicate that the embodiments described may include certain features, structures, or characteristics, but not all embodiments are required to include those features, structures, or characteristics. Furthermore, such phrases do not necessarily refer to the same embodiments. Moreover, when certain features, structures, or characteristics are described in relation to one embodiment, it is assumed that the operation of such features, structures, or characteristics in relation to other embodiments, whether explicitly described or not, is within the knowledge of those skilled in the art.

[0057] Terms such as “first” and “second” may be used herein to describe various elements, but it should be understood that these elements should not be limited by these terms. These terms are used merely to distinguish one element from another. For example, without departing from the scope of the embodiment, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. The term “and / or” as used herein includes any and all combinations of one or more of the enumerated terms. In some examples, values, procedures, or devices may be referred to as “best,” “lowest,” “highest,” “minimum,” “largest,” etc. It should be understood that such descriptions are intended to indicate that a choice may be made among many functional alternatives used, and that such a choice does not need to be better, smaller, larger, or otherwise preferable than other choices.

[0058] The terms used herein are for the sole purpose of describing specific embodiments and are not intended to limit embodiments. When used herein, the singular forms “a,” “an,” and “the” are also intended to include the plural forms unless the context clearly indicates otherwise. When the terms “comprises,” “comprising,” “has,” “having,” “includes,” and / or “including” are used herein, they specify the existence of the described features, elements, components, etc., but do not exclude the existence or addition of one or more other features, elements, components, and / or combinations thereof. For example, the term “includes” and its variations should be read as an open term meaning “including but not limited to.” The term “based on” should be read as “at least partially based on.” The terms “one embodiment” and “one embodiment” should be read as “at least one embodiment.” The term “another embodiment” should be read as “at least one other embodiment.” The use of expressions such as "A and / or B" can mean either "A only," "B only," or "both A and B." Other explicit and implicit definitions may include the following:

[0059] Figure 1 shows an example of a wireless communication system 100 in which several embodiments of the present disclosure may be implemented. The wireless communication system 100 may include one or more network entities 102 (also called network equipment (NEs)), one or more UEs 104, a core network 106, and a packet data network 108. The wireless communication system 100 may support various radio 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 LTE Advanced (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 radio access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support radio access technologies beyond 5G. Additionally, the wireless communication system 100 may support technologies such as time-division multiple access (TDMA), frequency-division multiple access (FDMA), or code-division multiple access (CDMA).

[0060] One or more network entities 102 may be distributed across a geographical area to form a wireless communication system 100. One or more of the network entities 102 described herein may be, or include, or be referred to as, a network node, base station, network element, radio access network (RAN), transceiver base station, access point, node B, e-node B (eNB), next-generation node B (gNB), or other preferred terms. The network entities 102 and UE 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, the network entities 102 and UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) via a Uu interface.

[0061] A network entity 102 may provide a geographic coverage area 112 to which it can support services (e.g., voice, video, packet data, messages, broadcasts, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, the network entity 102 and the UEs 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messages, broadcasts, etc.) according to one or more radio access technologies. In some implementations, the network entity 102 may be mobile, for example, a satellite related to a non-terrestrial network. In some implementations, different geographic coverage areas 112 related to the same or different radio access technologies may overlap, but different geographic coverage areas 112 may be associated with different network entities 102. The information and signals described herein may 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 may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0062] One or more UEs 104 may be distributed across the entire geographical area of ​​the wireless communication system 100. The UEs 104 may include, or be referred to as, mobile devices, wireless devices, remote devices, remote units, handheld devices, or subscriber devices, or several other preferred terms. In some implementations, the UEs 104 may be referred to as units, stations, terminals, or clients, among other examples. Additionally or alternatively, the UEs 104 may be referred to as Internet of Things (IoT) devices, Internet of Everything (IoE) devices, or machine-type communications (MTC) devices, among other examples. In some implementations, the UEs 104 may be fixed within the wireless communication system 100. In some other implementations, the UEs 104 may be mobile within the wireless communication system 100.

[0063] One or more UE104 may be devices of different forms or with different capabilities. Some examples of UE104 are shown in Figure 1. As shown in Figure 1, UE104 may be capable of communicating with various types of devices, such as network entities 102, other UE104, or network equipment (e.g., core network 106, packet data network 108, relay devices, integrated access and backhaul (IAB) nodes, or other network equipment). Additionally or alternatively, UE104 may support communication with other network entities 102 or UE104 that can act as relays in the wireless communication system 100.

[0064] UE104 may also support direct wireless communication with other UE104s via communication link 114. For example, UE104 may support direct wireless communication with another UE104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V), vehicle-to-everything (V2X), or cellular V2X deployments, communication link 114 may be referred to as a side link (SL). For example, UE104 may support direct wireless communication with another UE104 via the PC5 interface.

[0065] A network entity 102 may support communication with the core network 106, another network entity 102, or both. For example, a network entity 102 may interface with the core network 106 through one or more backhaul links 116 (e.g., via S1, N2, N3, or another network interface). Network entities 102 may communicate with each other through the 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 the core network 106). In some implementations, one or more network entities 102 may include sub-components such as access network entities, the access network entities may be examples of access node controllers (ANCs). The ANC may communicate with one or more UEs 104 through one or more other access network transmitting entities, which may be called radioheads, smart radioheads, or transmit / receive points (TRPs).

[0066] In some implementations, the network entity 102 may consist of a disassembled architecture, which can be configured to utilize a physically or logically distributed protocol stack among two or more network entities 102, such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, the network entity 102 may include one or more of the following: a central unit (CU), a distributed unit (DU), a radio unit (RU), a RAN intelligent controller (RIC) (e.g., a Near-RT RIC or a Non-RT RIC), a service management and organization (SMO) system, or any combination thereof.

[0067] RUs are sometimes called radio heads, smart radio heads, remote radio heads (RRHs), remote radio units (RRUs), or transmit / receive points (TRPs). One or more components of network entity 102 in a disassembled RAN architecture may be located together, or one or more components of network entity 102 may be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 in a disassembled RAN architecture may be implemented as virtual units (e.g., virtual CUs (VCUs), virtual DUs (VDUs), virtual RUs (VRUs)).

[0068] The functional division between CUs, DUs, and RUs may be flexible and support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof) are performed in the CU, DU, or RU. For example, a functional division of the protocol stack may be adopted between the CU and DU such that the CU may support one or more layers of the protocol stack and the DU may support one or more different layers of the protocol stack. In some implementations, the CU may host higher-level protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). A CU may be connected to one or more DUs or RUs, each of which may host lower-level protocol layers 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) functionality, each of which may be at least partially controlled by the CU.

[0069] As an addition or alternative, a functional partition of the protocol stack may be adopted between the DU and RU such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack. The DU may support one or more different cells (for example, through one or more RUs). In some implementations, the functional partition between the CU and the DU or between the DU and the RU may be within the protocol layer (for example, some functions for the protocol layer may be performed by one of the CU, DU, or RU, and other functions for the protocol layer may be performed by one of the different CU, DU, or RU).

[0070] A CU may be functionally further divided into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU may be connected to one or more DUs via midhaul communication links (e.g., F1, F1-C, F1-U), and a DU may 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 may be implemented according to the interlayer interfaces (e.g., channels) of the protocol stacks supported by each network entity 102 communicating via such communication links.

[0071] The core network 106 may support user authentication, access permission, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an advanced packet core (EPC) or 5G core (5GC) that 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 to 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 layer (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.), for one or more UEs 104 served by one or more network entities 102 associated with the core network 106.

[0072] The core network 106 may communicate with the packet data network 108 via one or more backhaul links 116 (for example, via S1, N2, N3, or another network interface). The packet data network 108 may include an application server 118. In some implementations, one or more UEs 104 may communicate with the application server 118. The UEs 104 may establish a session with the core network 106 via a network entity 102 (for example, a protocol data unit (PDU) session). The core network 106 may use the established session (for example, an established PDU session) to route traffic (for example, control information, data, etc.) between the UEs 104 and the application server 118. The PDU session may be an example of a logical connection between the UEs 104 and the core network 106 (for example, one or more network functions of the core network 106).

[0073] In the wireless communication system 100, the network entities 102 and UE104 may use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, the network entities 102 and UE104 may support different resource structures. For example, the network entities 102 and UE104 may support different frame structures. In some implementations, such as in 4G, the network entities 102 and UE104 may support a single frame structure. In some other implementations, such as in 5G, and also among suitable radio access technologies, the network entities 102 and UE104 may support various frame structures (i.e., multiple frame structures). The network entities 102 and UE104 may support various frame structures based on one or more numerologies.

[0074] One or more numerologies may be supported in the wireless communication system 100, and the numerologies may include subcarrier intervals and cyclic prefixes. A first numerology (e.g., μ=0) may be associated with a first subcarrier interval (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., μ=0) associated with the first subcarrier interval (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., μ=1) may be associated with a second subcarrier interval (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., μ=2) may be associated with a third subcarrier interval (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., μ=3) may be associated with a fourth subcarrier interval (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., μ=4) may be associated with a fifth subcarrier interval (e.g., 240 kHz) and a normal cyclic prefix.

[0075] The time intervals of resources (e.g., communication resources) may be organized according to frames (also called wireless frames). Each frame may have a duration, for example, 10 milliseconds (ms). In some implementations, each frame may contain multiple subframes. For example, each frame may contain 10 subframes, each subframe may have a duration, for example, 1 ms. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0076] As an addition or alternative, the time intervals of resources (e.g., communication resources) may be organized according to slots. For example, a subframe may contain a certain number (e.g., a quantity) of slots. The number of slots in each subframe may also depend on one or more numerologies supported in the wireless communication system 100. For example, the first, second, third, fourth, and fifth numerologies (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with the respective subcarrier intervals of 15kHz, 30kHz, 60kHz, 120kHz, and 240kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and sixteen slots per subframe, respectively. Each slot may contain a certain number (e.g., a quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., a quantity) of slots for a subframe may depend on the numerology. For a normal cyclic prefix, a slot may contain 14 symbols. For an extended cyclic prefix (applicable, for example, to a 60 kHz subcarrier interval), a slot may contain 12 symbols. The relationships between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for normal and extended cyclic prefixes may depend on the numerology. It should be understood that a reference to a first numerology (e.g., μ=0) associated with a first subcarrier interval (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0077] In the wireless communication system 100, the electromagnetic (EM) spectrum may be divided into various classes, frequency bands, frequency channels, etc., based on frequency or wavelength. For example, the wireless communication system 100 may support one or more operating frequency bands, such as frequency range designations FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4 (52.6 GHz to 114.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), and FR5 (114.25 GHz to 300 GHz). In some implementations, network entities 102 and UE 104 may perform wireless communication over one or more of these operating frequency bands. In some implementations, FR1 may also be used by network entities 102 and UE 104 in equipment or devices for cellular communication traffic (e.g., control information, data). In some implementations, FR2 may be used by network entities 102 and UE104, among other equipment or devices for short-range, high-data-rate capabilities.

[0078] FR1 may be associated with one or more numerologies (for example, at least three). For example, FR1 may be associated with a first numerology including a 15 kHz subcarrier interval (e.g., μ=0), a second numerology including a 30 kHz subcarrier interval (e.g., μ=1), and a third numerology including a 60 kHz subcarrier interval (e.g., μ=2). FR2 may be associated with one or more numerologies (for example, at least two). For example, FR2 may be associated with a third numerology including a 60 kHz subcarrier interval (e.g., μ=2), and a fourth numerology including a 120 kHz subcarrier interval (e.g., μ=3).

[0079] A CHO is defined as a handover executed by a UE when one or more handover execution conditions are met. When a UE receives a CHO configuration, it begins evaluating the execution conditions, and when the handover is executed, it stops evaluating the execution conditions. The following principles may apply to a CHO: A CHO configuration includes a CHO candidate target cell configuration, generated by a candidate target gNB, and execution conditions generated by a source gNB. An execution condition may consist of one or two trigger conditions (e.g., CHO events A3 / A4 / A5, i.e., CondEvent A3 / A4 / A5). An execution condition may be called a CHO execution condition. One CHO execution condition may be configured for a single candidate target cell. Only a single RS type is supported, and up to two different trigger quantities (e.g., RSRP and RSRQ, RSRP and SINR, etc.) may be configured simultaneously for the evaluation of a CHO execution condition for a single candidate target cell. When one or more CHO execution conditions are met, the UE may select a candidate target cell that satisfies those CHO execution conditions as the target cell and perform a CHO execution toward or against the target cell, such as synchronization with and / or access to the target cell. While the CHO is being executed, i.e., from the time the UE begins synchronizing with the target cell, the UE does not monitor the source cell.

[0080] CPAC may refer to a conditional PSCell addition (CPA) or conditional PSCell change (CPC) procedure in any MR-DC case, including NR-NR DC, EN DC, NGEN-DC, and NE-DC.

[0081] CPA: An MN can initiate a CPA procedure by sending an SN Addition Request to several candidate target SNs. In the SN Addition Request message, the MN may provide a list of cells that can be used as PSCells, e.g., cells 1, 2, 3, ... 10. A candidate target SN selects several cells from the list of cells provided by the MN that should be prepared as candidate PSCells, e.g., cells 1, 2, 3, ... 5. The candidate target SN then returns an SN Addition Request Recognition Response, which includes an RRC Reconfiguration message that provides the UE with an SN RRC reconfiguration to be used when performing the CPA and accessing the corresponding target SN. The MN generates an MN RRC Reconfiguration message, which includes an RRC Conditional Reconfiguration component consisting of the CPA execution conditions (generated by the MN) and the SN RRC Reconfiguration message (generated by the candidate target SN). For example, the CPA execution conditions may consist of one or two trigger conditions (e.g., CHO event B1 / A4, i.e., CondEvent B1 / A4). One CPA execution condition may be configured for one candidate PSCell. The MN sends the generated MN RRC reconfiguration message to the UE. Upon receiving the CPA-related RRC reconfiguration message, the UE begins to evaluate whether the CPA execution conditions are met (for example, whether the measured radio link quality of a candidate target SN is better than the threshold). If the CPA execution conditions are met, the UE can select the candidate PSCell that satisfies those conditions as the target PSCell and perform a CPA execution toward or against the target PSCell. For example, the UE begins to access the corresponding target PSCell or target SN.

[0082] Inter-SN CPC: Inter-SN CPC can be initiated by either the MN or the source SN. The source SN may initiate an Inter-SN CPC by sending an SN change request message to the MN containing information related to the Inter-SN CPC. Upon receiving an SN change request message that triggers an Inter-SN CPC, or once the MN initiates an Inter-SN CPC, the MN sends an SN Addition Request to several candidate target SNs. Candidate target SNs may respond with an SN Addition Request Recognition Response, which includes an RRC Reconfiguration message providing the UE with an SN RRC reconfiguration to be used when executing the CPC and accessing the corresponding target SN. An MN RRC Reconfiguration message is sent to the UE, which includes an RRC conditional reconfiguration consisting of the CPC execution conditions and the SN RRC reconfiguration message. For example, the CPC execution conditions may consist of one or two trigger conditions (e.g., CHO events B1 / A3 / A4 / A5, i.e., CondEvent B1 / A3 / A4 / A5). One CPC execution condition may be configured for one candidate PSCell. Upon receiving a CPC-related RRC reconfiguration message, the UE begins evaluating whether the CPC execution conditions are met (for example, whether the measured radio link quality of a candidate target SN is better than a threshold). If the CPC execution conditions are met, the UE can select the candidate PSCell that satisfies those conditions as the target PSCell and perform a CPC execution toward or against the target PSCell. For example, the UE may begin accessing the corresponding target SN.

[0083] One objective of mobility extensions is to specify a CHO procedure with a candidate SCG (i.e., a CHO procedure with a CPAC, or a CHO with a (candidate) target MCG and candidate SCG for a CPC / CPA). The UE evaluates whether the CHO execution conditions and CPC / CPA execution conditions are met, and if both conditions are met, the UE executes the CHO execution and CPAC execution. To improve mobility robustness, self-organized network (SON) extensions for CHOs with candidate SCGs should be considered.

[0084] Embodiments of this disclosure provide a solution for a CHO with a candidate SCG. In this solution, the UE may receive a first configuration comprising one or more CHO execution conditions and one or more CPAC execution conditions for the CHO with a candidate SCG. In some examples, the UE may receive a second configuration comprising at least one time threshold, the at least one time threshold used to determine whether to store or report first information relating to a successful CHO procedure with a candidate SCG. In some examples, the UE may store or report first information relating to a successful CHO procedure with a candidate SCG if at least one trigger condition relating to at least one time threshold is met. The principles and implementations of this disclosure are described in detail below with reference to the drawings.

[0085] Figure 2 shows a schematic diagram of an exemplary communication network 200 in which several embodiments of the present disclosure may be implemented. As shown in Figure 2, the communication network 200 may include RAN node 210, RAN node 220, RAN node 215, RAN node 225, and UE 230.

[0086] In scenarios where a handover may be triggered or performed, RAN node 210 may be referred to as source master node (MN) 210, RAN node 220 as source secondary node (SN) 220, RAN node 215 as candidate target MN215, and RAN node 225 as candidate target SN225. If candidate target PCell provided by candidate target MN215 is selected as target PCell, then candidate target MN215 is understood to be target MN(T-MN) 215, and if candidate target PSCell provided by candidate target SN225 is selected as target PSCell, then candidate target SN225 is understood to be target SN(T-SN) 225.

[0087] Several scenarios may be considered for a CHO procedure involving a candidate SCG. In this disclosure, the term “CHO involving a candidate SCG” may also be referred to as a CHO involving a candidate SCG, a CHO involving one or more candidate SCGs, a CHO involving at least one candidate SCG, a CHO involving multiple candidate SCGs, a CHO involving a CPAC, a CHO involving a (candidate) target MCG and a candidate target SCG for CPC / CPA, a CHO including a (candidate) target MCG and a candidate target SCG configuration, and this disclosure is not limited to these embodiments. For example, in some exemplary embodiments described below, the term “CHO involving a candidate SCG” is used for ease of explanation.

[0088] In some examples, the scenario may be a CHO with CPA, i.e., a CHO from a single connectivity to an MRDC connectivity, for example, a CHO from source PCell1 with candidate target SN to candidate target PCell2. Referring to Figure 2, UE230 may initially be in PCell1 provided by source MN(S-MN)210, later perform a CHO execution to PCell2 provided by T-MN215 where its CHO execution conditions are met, and similarly perform a CPA execution to T-SN225 which may provide a target PSCell where its CPA execution conditions are met.

[0089] In some examples, the scenario may be a CHO with an in-SN CPC, i.e., a CHO from source PCell1 with SCG1 in SN1 to candidate target PCell2 with candidate target SCG in the same SN1. For example, UE230 may initially be in PCell1 provided by source MN(S-MN)210 and PSCell1 provided by source SN(S-SN)220, then perform a CHO execution to PCell2 provided by T-MN215 where its CHO execution conditions are met, and similarly perform a CPC execution to target PSCell provided by source SN220 where its CPC execution conditions are met.

[0090] In some examples, the scenario may be a CHO with inter-SN CPC, i.e., a CHO from source PCell1 with SN1 (e.g., S-SN) (e.g., managed by S-MN) to candidate target PCell2 with a candidate target SN other than SN1 (e.g., T-SN) (e.g., managed by T-MN). Referring to Figure 2, UE230 may initially be among PCell1 provided by source MN(S-MN)210 and PSCell1 provided by source SN(S-SN)220, later perform a CHO execution to PCell2 provided by T-MN215 where its CHO execution conditions are met, and similarly perform a CPC execution to target PSCell provided by target SN(T-SN)225, which is related to T-SN225 that may provide PSCell2, where its CPC execution conditions are met.

[0091] It should be understood that the number of devices, their connectivity, and types shown in Figure 2 are for illustrative purposes only and do not imply any limitation. The environment may include any number of suitable devices adapted to carry out embodiments of the present disclosure. For example, it may further include one or more other candidate target MNs and one or more other candidate target SNs.

[0092] Figure 3 shows an exemplary successful process 300 of a CHO with a candidate SCG. A CHO configuration that references or includes a CPC / CPA configuration may be supported within a CHO procedure with a candidate SCG. In a CHO procedure with a candidate SCG, one or more candidate PCells and one or more candidate PSCells can be configured for the UE, and one or more CHO execution conditions and one or more CPAC execution conditions for a CHO with a candidate SCG can also be configured for the UE, with one candidate PCell associated with a CHO execution condition for a CHO with a candidate SCG and one candidate PSCell associated with a CPAC execution condition for a CHO with a candidate SCG. CHO execution condition evaluation and CPC / CPA execution condition evaluation can be performed in parallel / concurrently by the UE. For example, in step 9 in Figure 3, the UE simultaneously starts evaluating one or more CHO execution conditions and one or more CPA / CPC execution conditions (for example, upon receiving the configuration for the CHO procedure with a candidate SCG).

[0093] CHO execution conditions (for candidate PCells) and CPA / CPC execution conditions (for candidate PSCells) are provided based on the source MeasConfig. For CHO execution conditions, source MN210 determines one or more CHO execution conditions (e.g., CondEvent B1 / A3 / A5) for one or more candidate PCells based on the source MCG MeasConfig. For CPA / CPC execution conditions, candidate MN215 determines the parameters (e.g., CondEvent B1 / A3 / A4 / A5 thresholds) for one or more candidate PSCells. Candidate MN215 informs source MN210 about the prepared candidate PSCells and the associated CPA / CPC execution condition parameters (e.g., CondEvent B1 / A3 / A4 / A5 thresholds). Based on the information received from candidate MN215, source MN210 generates the corresponding CPAC execution conditions.

[0094] In the case of a CHO with a candidate SCG for CPA / CPC, the RRCReconfiguration message within a single CHO container includes one MCG configuration and one SCG configuration (i.e., similar to the signaling structure for a Rel-17 CHO configuration with an SCG). The execution conditions associated with a single CHO container include trigger conditions associated with both CHO execution conditions and CPA / CPC execution conditions, i.e., both candidate PCells and candidate PSCells. In other words, within a CHO procedure with a candidate SCG, at least one MCG configuration for at least one candidate PCell, at least one SCG configuration for at least one candidate PSCell, at least one CHO execution condition for at least one candidate PCell for a CHO with a candidate SCG, and at least one CPAC execution condition for at least one candidate PSCell for a CHO with a candidate SCG may be configured for the UE.

[0095] If there are multiple candidate PSCells associated with one candidate PCell, the NW can provide multiple CHO configurations for the same candidate PCell, i.e., each CHO configuration includes one MCG configuration (for the same candidate PCell) and one SCG configuration (for each candidate PSCell within the candidate PSCell).

[0096] If one CPA / CPC execution condition is met but a CHO execution condition is not, the UE230 continues to evaluate both the CHO and CPA / CPC execution conditions. The UE will not execute the CPC / CPA unless the CHO execution condition is met.

[0097] In the case of a CHO procedure with a candidate SCG, CHO execution and CPAC execution may be performed when both the CHO execution conditions and CPAC execution conditions are met. In a CHO procedure with a candidate SCG, in order to handle cases where the CHO execution conditions for a CHO with a candidate SCG or the CPAC execution conditions for a CHO with a candidate SCG are not met, in addition to the configuration for a CHO with a candidate SCG (i.e., the configuration for a CHO with a candidate SCG includes at least one MCG configuration for at least one candidate PCell, at least one SCG configuration for at least one candidate PSCell, at least one CHO execution condition for at least one candidate PCell for a CHO with a candidate SCG, and at least one CPAC execution condition for at least one candidate PSCell for a CHO with a candidate SCG), a configuration for a simple CHO and / or a configuration for a Rel-17 CHO with an SCG may be configured for the UE. For example, a configuration for a simple CHO includes at least one MCG configuration for at least one candidate PCell (the candidate PCell for a simple CHO may be the same as or different from the candidate PCell for a CHO with a candidate SCG), and at least one CHO execution condition for at least one candidate PCell for a simple CHO. For example, a configuration for a Rel-17 CHO with an SCG includes at least one MCG configuration for at least one candidate PCell (the candidate PCell for a Rel-17 CHO with an SCG may be the same as or different from the candidate PCell for a CHO with a candidate SCG), at least one CHO execution condition for at least one candidate PCell for a CHO with an SCG, and at least one SCG configuration for at least one target PSCell (one target PSCell is configured for each candidate PCell for a CHO with an SCG).When one CHO execution condition is met for a CHO with a candidate SCG but the CPC execution condition for the CHO with a candidate SCG is not met, or when one CPAC execution condition is met for a CHO with a candidate SCG but the CHO execution condition for the CHO with a candidate SCG is not met, if there is an available simple CHO configuration or Rel-17 CHO configuration with an SCG that satisfies the CHO execution condition for it, for example, if there is a candidate PCell that satisfies the CHO execution condition for a simple CHO, or if there is a candidate PCell that satisfies the CHO execution condition for a Rel-17 CHO with an SCG, the UE will either perform a simple CHO execution (for example, a UE handover or access to a candidate PCell that satisfies the CHO execution condition for a simple CHO) or a Rel-17 CHO execution (for example, a Rel-17 CHO with an SCG) The UE performs a handover or access to a candidate PCell for which the execution conditions of the CHO are met, and the UE also performs a PSCell addition or modification, or access to a target PSCell associated with the candidate PCell. Therefore, the network can handle such situations by providing an appropriate configuration.

[0098] Further reference is made to Figure 4, which shows a signaling chart illustrating a communication process 400 according to some exemplary embodiments of the present disclosure. Process 400 may involve sources MN210 and UE230.

[0099] In process 400, source MN210 sends a first configuration to UE230 at 410. In some implementations, the first configuration, which may be called the configuration for a CHO with a candidate SCG as described above, is used for a CHO with a candidate SCG. The first configuration may include one or more CHO execution conditions for the CHO with a candidate SCG, and one or more CPAC execution conditions for the CHO with a candidate SCG.

[0100] In some exemplary embodiments, for each candidate (target) PCell, the source MN210 may configure a corresponding CHO execution condition for a CHO with a candidate SCG, which may consist of one or two trigger conditions such as CondEvent A3 / A4 / A5. In some exemplary embodiments, for each candidate (target) PSCell, the corresponding candidate target MN may provide the source MN210 with parameters for a CPAC execution condition, which then generates one or more CPAC execution conditions for a CHO with a candidate SCG and sends them to the UE230 in the first configuration.

[0101] In some examples, the first configuration may represent a first candidate (target) PCell and an associated first candidate (target) PSCell, where the first candidate (target) PCell may relate to a first CHO execution condition and the first candidate (target) PSCell may relate to a first CPAC execution condition. In some examples, the first configuration may represent a second candidate (target) PCell and an associated second candidate (target) PSCell, where the second candidate (target) PCell may relate to a second CHO execution condition and the second candidate (target) PSCell may relate to a second CPAC execution condition. It should be understood that the number of candidate (target) PCells represented by the first configuration is not limited in this disclosure.

[0102] In process 400, source MN210 sends a second configuration to UE230 at 420, where the second configuration includes at least one time threshold. At least one time threshold may be used to determine whether at least one trigger condition is met for storing or reporting a successful CHO procedure with a candidate SCG. Otherwise, at least one time threshold may be used to determine whether first information related to a successful CHO procedure with a candidate SCG should be stored or reported.

[0103] In some implementations, the source MN210 sends the first and second configurations to the UE230 separately, either via the same message or different messages.

[0104] In some implementations, the second configuration may include at least one of the first, second, third, fourth, fifth, sixth, or seventh time thresholds, which are described in detail below. For example, the second configuration may include at least one of the first, second, or third time thresholds, and may further include at least one of the fourth, fifth, or sixth thresholds. For example, the second configuration may include a seventh time threshold, which may be represented as Tth.

[0105] In some exemplary embodiments, upon receiving a first configuration, the UE230 may evaluate whether one or more CHO execution conditions for a CHO with a candidate SCG are met, and may evaluate whether one or more CPAC execution conditions for a CHO with a candidate SCG are met.

[0106] In some implementations, it is assumed that UE230 determines that the CHO execution conditions for a CHO with a candidate SCG and the associated CPAC execution conditions for a CHO with a candidate SCG are met, for example, that the first candidate (target) PCell satisfies its associated CHO execution conditions for a CHO with a candidate SCG, and that the first candidate (target) PSCell satisfies its associated CPAC execution conditions for a CHO with a candidate SCG, where the first candidate (target) PCell is related to the first candidate (target) PSCell. The UE may then hand over to or access the first candidate (target) PCell (sometimes called the target PCell), and the UE may perform a PSCell addition or modification, or access to the first candidate (target) PSCell (sometimes called the target PSCell).

[0107] From several perspectives, a CHO procedure with a candidate SCG is successful, i.e., a successful CHO procedure with a candidate SCG, such as a successful UE handover or access to a first candidate (target) PCell (sometimes called a target PCell), and the UE may successfully perform a PSCell addition or modification, or access to the first candidate (target) PSCell (sometimes called a target PSCell). However, it could also be a nearly failed successful CHO procedure with a candidate SCG.

[0108] In some implementations, after receiving the second configuration, the UE230 may determine whether a trigger condition is met (i.e., satisfied). In some examples, the trigger condition is for a successful report of a CHO with a candidate SCG, and it should be understood that the following explanation will use the term "trigger condition" for brevity. In some examples, the trigger condition is related to at least one time threshold, i.e., at least one time-related threshold.

[0109] In some implementations, the trigger condition may be used by the UE230 to determine whether to log or store first information relating to a nearly failed successful CHO procedure with a candidate SCG.

[0110] In some implementations, the trigger condition may be a new trigger condition. In some examples, the new trigger condition is introduced for a successful report to a CHO with a candidate SCG. In some examples, the trigger condition may be related to a seventh time threshold (or time-related threshold), i.e., Tth.

[0111] In some examples, the fulfillment of a trigger condition may mean that the duration between the time when one or more CHO execution conditions for a CHO with a candidate SCG are fulfilled and the time when one or more CPAC execution conditions for a CHO with a candidate SCG are fulfilled is equal to or greater than a time threshold Tth. For example, the duration between two fulfilled execution conditions is equal to or greater than a time threshold Tth. For example, that duration may be the time elapsed from the time when a CHO execution condition for a CHO with a candidate SCG is fulfilled until a CPAC execution condition for a CHO with a candidate SCG is fulfilled, or the time elapsed from the time when a CPAC execution condition for a CHO with a candidate SCG is fulfilled until a CHO execution condition for a CHO with a candidate SCG is fulfilled.

[0112] In some exemplary embodiments, the second configuration from source MN210 may be included in a message, which may be an RRC reconfiguration message. In some examples, the first and second configurations may be in the same message (such as an RRC reconfiguration message) or in different messages.

[0113] In some embodiments, the new trigger condition (or seventh time threshold) may be determined by source MN210. In some examples, source MN210 may generate or determine the new trigger condition (or seventh time threshold) on its own.

[0114] In some other embodiments, the new trigger condition (or seventh time threshold) may be determined by the candidate target MN215. In some examples, source MN210 may inform candidate target MN215 of one or more prepared candidate (target) PCells and the parameters of the associated CHO execution conditions for one or more candidate (target) PCells, for example, thresholds for TTT or CondEvent A3 / A4 / A5. In some examples, candidate target MN215 may generate or determine the new trigger condition (or seventh time threshold) based on one or more prepared candidate (target) PCells and the parameters of the associated CHO execution conditions for one or more candidate (target) PCells. In some examples, candidate target MN215 may send the new trigger condition (or seventh time threshold) to source MN210, which may then send the new trigger condition (or seventh time threshold) to UE230 (for example, via an RRC reconfiguration message).

[0115] It should be understood that several further exemplary embodiments may apply, for example, that new trigger conditions may be predefined, preconfigured, or pre-stored in UE230. In some examples, UE230 may acquire new trigger conditions (or a seventh time threshold) stored in UE230. In some examples, the second configuration may be omitted, and the time threshold may be pre-stored in UE230.

[0116] It is assumed that within process 400, UE230 determines that a new trigger condition is met. In addition, UE230 logs or stores first information in 430, where first information relates to a successful CHO procedure with a candidate SCG.

[0117] In some exemplary embodiments, a CHO procedure with a candidate SCG may be successfully executed, for example, UE230 may successfully access the target PCell and target PSCell. In some examples, if a new trigger condition is met, for example, if the duration between two met execution conditions is equal to or exceeds a time threshold Tth, UE230 may log or store the first information.

[0118] In some exemplary embodiments, no new trigger conditions (or a seventh time threshold) are sent to or configured for the UE230, or no new trigger conditions are predefined, preconfigured, or pre-stored in the UE230, for example, when one or more CHO execution conditions for a CHO with a candidate SCG and one or more CPAC execution conditions for a CHO with a candidate SCG are met, or when a CHO procedure with a candidate SCG is successfully executed, the UE230 may log or store the first information, and then, for example, when a CHO procedure with a candidate SCG is successfully executed, the UE230 may report the first information, for example, the UE230 may report the first information to a target MN or target SN.

[0119] In some exemplary embodiments, UE230 may generate and / or store both SHR and SPR. In some examples, existing UE variables (e.g., VarSuccessHO-Report) may be reused to log / store some of the first pieces of information relating to a successful CHO execution. In some examples, existing UE variables (e.g., VarSuccessPSCellChange-Report) may be reused to log / store some of the first pieces of information relating to a successful CPAC execution.

[0120] In some exemplary embodiments, UE230 may generate a new report for a nearly failed successful CHO procedure with a candidate SCG. In some other examples, a new UE variable (e.g., VarSuccessHOwithPSCellChange-Report) may be used to log / store first information relating to a successful CHO procedure with a candidate SCG.

[0121] In some other implementations, the trigger conditions may be similar to one or more existing trigger conditions. In some implementations, T304, T310, and T312 may be configured as trigger conditions for successful reporting for a CHO procedure with a candidate SCG. One or more time-related thresholds may be defined in relation to T304, T310, and T312, each of which may be a percentage value.

[0122] In some exemplary embodiments, the trigger condition may include a T304 trigger condition for a candidate target PCell related to a first time threshold. In some examples, the T304 trigger condition related to a candidate target PCell can be used to trigger a CHO report with a candidate SCG (e.g., a new defined report such as a SHR, or a successful HO report with a PSCell change, or a report with another name used to convey the first information), and the T304 trigger threshold (or first time threshold) may be generated / determined by the candidate target MN215. For example, the candidate target MN215 may determine the first time threshold and send the first time threshold to the source MN210. For example, the source MN210 may configure the first time threshold for UE230. In some examples, the same first time threshold may be configured for different candidate target PCells. In some examples, the candidate target MN215 may configure different first time thresholds for different candidate target PCells.

[0123] In some exemplary embodiments, the trigger condition may include a T310 trigger condition for a source PCell related to a second time threshold. In some examples, the T310 trigger condition related to the source PCell may be used to trigger a CHO report with a candidate SCG (e.g., a new defined report such as an SHR, or a successful HO report with a PSCell change, or a report with another name used to convey the first information), and the T310 trigger threshold (or second time threshold) may be generated / determined by the source MN210. For example, the source MN210 may determine the second time threshold and configure the second time threshold for the UE230. In some examples, the same second time threshold may be configured for different candidate target PCells. In some examples, the source MN210 may configure different second time thresholds for different candidate target PCells.

[0124] In some exemplary embodiments, the trigger condition may include a T312 trigger condition for measurement identification of a candidate target PCell, related to a third time threshold. In some examples, the T312 trigger condition related to measurement identification of a candidate target PCell may be used to trigger a CHO report with a candidate SCG (e.g., a new defined report such as a SHR, or a successful HO report with a PSCell change, or a report with another name used to convey the first information), and the T312 trigger threshold (or third time threshold) may be generated / determined by source MN210. For example, source MN210 may determine the third time threshold and configure the third time threshold for UE230. In some examples, the same third time threshold may be configured for different candidate target PCells. In some examples, source MN210 may configure different third time thresholds for different candidate target PCells.

[0125] In some exemplary embodiments, the trigger condition may include a T304 trigger condition for a candidate target PSCell related to a fourth time threshold. In some examples, the T304 trigger condition related to a candidate target PSCell may be used to trigger a CHO report with a candidate SCG (e.g., a new defined report such as an SPR, or a successful HO report with a PSCell change, or a report with another name used to convey the first information), and the T304 trigger threshold (or fourth time threshold) may be generated / determined by the candidate target SN225. For example, the candidate target SN225 may determine the fourth time threshold and send the fourth time threshold to the candidate target MN215, for example, the fourth time threshold may be included in an SN Add-on Request Recognition Response message or an SgNB Add-on Request Recognition Response message from the candidate target SN225 to the candidate target MN215. For example, candidate target MN215 may transfer a fourth time threshold to source MN210, which may be included in the handover request recognition response from candidate target MN215 to source MN210. For example, source MN210 may configure a fourth time threshold for UE230.

[0126] In some exemplary embodiments, the trigger condition may include a T310 trigger condition for a source PSCell related to a fifth time threshold. In some examples, the T310 trigger condition related to a source PSCell may be used to trigger a CHO report with a candidate SCG (e.g., a new defined report such as an SPR, or a successful HO report with a PSCell change, or a report with another name used to convey the first information), and the T310 trigger threshold (or fifth time threshold) may be generated / determined by any one of source MN210, source SN220, or candidate target MN215.

[0127] In some exemplary embodiments, the trigger condition may include a T312 trigger condition for a source PSCell related to a sixth time threshold. In some examples, the T312 trigger condition related to a source PSCell may be used to trigger a CHO report with a candidate SCG (e.g., a new defined report such as an SPR, or a successful HO report with a PSCell change, or a report with another name used to convey the first information), and the T312 trigger threshold (or sixth time threshold) may be generated / determined by any one of source MN210, source SN220, or candidate target MN215.

[0128] In some embodiments, source MN210 may generate or determine fifth / sixth time thresholds related to the T310 / T312 trigger conditions for source PSCell, which may be used to trigger a CHO report with a candidate SCG (e.g., a newly defined report such as an SPR, or a successful HO report with a PSCell change, or a report with another name used to convey the first information).

[0129] In some examples, source MN210 may be informed to generate / determine a fifth / sixth time threshold. For example, candidate target MN215 may send an instruction to source MN210 to explicitly command it to generate / determine a fifth / sixth time threshold, for example, that instruction may be included in a handover request recognition response message from candidate target MN215 to source MN210. In another example, candidate target MN215 may implicitly instruct source MN210 to generate / determine a fifth / sixth time threshold, for example, a handover request recognition response message from candidate target MN215 to source MN210 may include parameters for one or more execution conditions for the candidate target PSCell (e.g., thresholds for TTT or CondEvent B1 / A4) that implicitly indicates to source MN210 to generate / determine a fifth / sixth time threshold for a T310 / T312 trigger condition related to source PSCell, which is used to trigger a CHO report with candidate SCG (e.g., a newly defined report such as SPR, or a successful HO report with a PSCell change, or a report with another name used to convey the first information).

[0130] In some examples, source MN210 may generate or determine the fifth / sixth time threshold on its own. For example, source MN210 may generate or determine the fifth / sixth time threshold without requiring any input from another entity (such as source SN220).

[0131] In some examples, source MN210 may generate or determine a fifth / sixth time threshold based on input from source SN220, where the input may include at least one configured T310 / T312 timer value. For example, source MN210 may inform source SN220 to provide at least one configured T310 / T312 timer value, for example, via an SN release request, SgNB release request, Xn-U address instruction, or a newly introduced message, and source SN220 may accordingly send at least one configured T310 / T312 timer value to source MN210. In another example, source MN210 may always be informed of at least one configured T310 / T312 timer value by a join mechanism, for example, by including an instruction to join to the last configured T310 / T312 timer value in an SN add request message or SgNB add request message, and then source SN220 sends at least one configured T310 / T312 timer value configured by source SN220 to source MN210 when the T310 / T312 timer value changes.

[0132] In some other embodiments, source SN220 may generate or determine a fifth / sixth time threshold for a T310 / T312 trigger condition associated with source PSCell, which is used to trigger a CHO report with a candidate SCG (e.g., a newly defined report such as an SPR, or a successful HO report with a PSCell change, or a report with another name used to convey the first information).

[0133] In some examples, source SN220 may generate / determine the fifth / sixth time thresholds independently or autonomously, and source SN220 may send the fifth / sixth time thresholds to source MN210, for example, via an SN release request recognition response message or an SgNB release request recognition response message.

[0134] In some examples, source MN210 may send an instruction to source SN220, where the instruction may indicate to source SN220 to generate / determine a fifth / sixth time threshold. For example, the instruction from source MN210 to source SN220 may be contained in one of the following: an SN release request, a SgNB release request, an Xn-U address instruction, or a newly introduced message. Accordingly, source SN220 may generate / determine a fifth / sixth time threshold based on the instruction from source MN210, and source SN220 may send the fifth / sixth time threshold to source MN210, for example, via an SN release request recognition response message or a SgNB release request recognition response message. In another example, source MN210 may always be informed of at least one configured T310 / T312 timer value by a join mechanism, for example, by including an instruction to join to the last configured T310 / T312 timer value in an SN add request message or SgNB add request message, and then source SN220 sends at least one configured T310 / T312 timer value configured by source SN220 to source MN210 when the T310 / T312 timer value changes.

[0135] In some examples, source SN220 may be indicated or configured to provide source MN210 with the most recent fifth / sixth time thresholds. For example, instructions for joining the most recent fifth / sixth time thresholds may be included in an SN addition request message to source SN220. For example, source SN220 may send the most recent fifth / sixth time thresholds to source MN210, for example, when updating the fifth / sixth time thresholds. For example, source MN210 may always be aware of the most recent fifth / sixth time thresholds for T310 / T312 trigger conditions associated with source PSCell, which are used to trigger CHO reports with candidate SCGs (e.g., SPRs, or new defined reports such as successful HO reports with PSCell changes or reports with other names used to convey first information).

[0136] In some other embodiments, candidate target MN215 may generate or determine a fifth / sixth time threshold for a T310 / T312 trigger condition related to the source PSCell, which is used to trigger a CHO report with candidate SCG (e.g., a newly defined report such as an SPR, or a successful HO report with a PSCell change, or a report with another name used to convey the first information).

[0137] In some examples, candidate target MN215 may generate or determine the fifth / sixth time threshold independently, and may send the fifth / sixth time threshold to source MN210, for example, via a handover request recognition response message. For example, candidate target MN215 may generate or determine the fifth / sixth time threshold without requiring any input from another entity (such as source SN220).

[0138] In some examples, candidate target MN215 may generate or determine a fifth / sixth time threshold based on input from source SN220, where the input may include at least one configured T310 / T312 timer value, and candidate target MN215 may send the fifth / sixth time threshold to source MN210, for example, via a handover request recognition response message. For example, source SN220 or candidate target SN225 may send at least one configured T310 / T312 timer value to candidate target MN215. For example, source SN220 or candidate target SN225 may send at least one configured T310 / T312 timer value to source MN210, and source MN210 may forward at least one configured T310 / T312 timer value to candidate target MN215.

[0139] In some examples, candidate target MN215 may be indicated or configured to provide the most recent fifth / sixth time threshold to source MN210. For example, instructions for joining the most recent fifth / sixth time threshold may be included in the handover request message to candidate target MN215. For example, candidate target MN215 may send the most recent fifth / sixth time threshold to source MN210, for example, when the fifth / sixth time threshold is updated. For example, source MN210 may always be informed of the most recent fifth / sixth time threshold for T310 / T312 trigger conditions associated with source PSCell, which are used to trigger CHO reports with candidate SCG (e.g., SPR, or a newly defined report such as a successful HO report with a PSCell change or a report with another name used to convey the first information).

[0140] It can be understood that a solution configuring T304, T310, or T312 as a trigger condition for successful reporting for a CHO procedure with the aforementioned candidate SCG may also be used as a solution configuring T304, T310, or T312 as a trigger condition for SHR for a legacy handover procedure or CHO procedure, or as a solution configuring T304, T310, or T312 as a trigger condition for SPR for a legacy PSCell add or modify procedure or CPA / CPC procedure. For example, a solution configuring a T304 trigger condition related to a candidate target PSCell, or a T310 trigger condition related to a source PSCell, or a T312 trigger condition related to a source PSCell, as a trigger condition for successful reporting for a CHO procedure with the aforementioned candidate SCG may also be used as a solution configuring a trigger condition for SPR for a legacy PSCell add or modify procedure or CPA / CPC procedure.

[0141] In some exemplary embodiments, the UE230 may determine (log or store) the first information. In some examples, some of the first information may relate to a successful CHO execution and may be included in the SHR, and some of the first information may relate to a successful CPAC execution and may be included in the SPR. In some examples, the first information may be included in a newly defined report, such as a successful handover report with PSCell changes or a report having another name used to include the first information. In some other examples, the first information may be included in a separate report, and this disclosure is not limited to this embodiment.

[0142] In some embodiments, trigger conditions may be met to trigger a successful handover report with an SHR or PSCell change, and trigger conditions may be met to trigger a successful handover report with an SPR or PSCell change.

[0143] In some examples, the trigger condition for triggering a successful handover report with an SHR or PSCell change may be met if the ratio between the elapsed time value of elapsed timer T304 for the (candidate) target PCell and the configured value of timer T304 (i.e., which may be included in the last RRCReconfiguration message applied to the CHO procedure with candidate SCG) is greater than a first time threshold. In some examples, the trigger condition for triggering a successful handover report with an SHR or PSCell change may be met if the ratio between the elapsed time value of timer T310 for the source PCell and the configured value of timer T310 configured for the source PCell (while the UE230 was connected to the source PCell before the last HO execution or CHO procedure with candidate SCG was executed) is greater than a second time threshold. In some examples, the trigger conditions for triggering a successful handover report with an SHR or PSCell change may include the fact that, at the time of initiating the last HO run or CHO procedure with a candidate SCG, Time 312 related to the measurement identification of the (candidate) target PCell is still running, and the ratio between the elapsed time value of Timer T312 and the configured value of Timer T312 is greater than a third time threshold.

[0144] In some examples, the trigger condition for triggering a successful handover report with an SPR or PSCell change may be met if the ratio between the elapsed time value of elapsed timer T304 for the (candidate) target PSCell and the configured value of timer T304 (i.e., which may be included in the last RRCReconfiguration message applied to the CHO procedure with candidate SCG) is greater than a fourth time threshold. In some examples, the trigger condition for triggering a successful handover report with an SPR or PSCell change may be met if the ratio between the elapsed time value of timer T310 for the source PSCell and the configured value of timer T310 configured for the source PSCell (while UE230 was connected to the source PSCell before the last CPAC run or CHO procedure with candidate SCG was executed) is greater than a fifth time threshold. In some examples, the trigger conditions for triggering a successful handover report with an SPR or PSCell change may include the ratio between the elapsed time value of Timer T312 for the source PSCell and the configured value of Timer T312 configured for the source PSCell (while UE230 was connected to the source PSCell before the last CPAC run or CHO procedure with candidate SCG was executed) being greater than a sixth time threshold.

[0145] In some implementations, the first information may be included in an SHR and SPR, or a report having a different name used to include the first information, such as a successful handover report with PSCell changes. In some exemplary embodiments, the UE230 may generate an SHR and SPR. In some exemplary embodiments, the UE may generate a successful handover report with PSCell changes, or a report having a different name used to include the first information. In some implementations, the first information may be included in an RRC message (for example, an RRC (connection) reconfiguration complete message sent by the UE to the target MN).

[0146] In some examples, the first information may include a new causal value for a successful report. For example, the new causal value may indicate that the first information related to a successful CHO with a candidate SCG is stored due to the fulfillment of at least one trigger condition related to at least one time threshold. For example, the new causal value may indicate that the duration between two satisfied execution conditions for a CHO with a candidate SCG exceeds the time threshold Tth.

[0147] In some examples, the first information may include the type of the first satisfied execution condition for the CHO with the candidate SCG. For example, the type may indicate that the first satisfied execution condition is a CHO execution condition for the CHO with the candidate SCG. For example, the type may indicate that the first satisfied execution condition is a CPAC execution condition for the CHO with the candidate SCG.

[0148] In some examples, the first piece of information may include the duration between two satisfied execution conditions for a CHO with a candidate SCG. For example, the duration may be the time elapsed from the time the CHO execution condition for the CHO with a candidate SCG was satisfied and the time the CPAC execution condition for the CHO with a candidate SCG was satisfied, i.e., the time elapsed from the time the CHO execution condition for the CHO with a candidate SCG was satisfied until the CPAC execution condition for the CHO with a candidate SCG was satisfied. For example, the duration may be the time elapsed from the time the CPAC execution condition for the CHO with a candidate SCG was satisfied and the time the CHO execution condition for the CHO with a candidate SCG was satisfied, i.e., the time elapsed from the time the CPAC execution condition for the CHO with a candidate SCG was satisfied until the CHO execution condition for the CHO with a candidate SCG was satisfied.

[0149] In some examples, the first piece of information may include a new type for lastHO-Type or a new type for lastPSCellchange-Type, for example, chowithcandidateSCG. For example, the type may indicate that the first piece of information is for a CHO with a candidate SCG.

[0150] In some examples, the first information may include the last received CHO execution condition for the CHO associated with the candidate SCG, e.g., a threshold for TTT or CondEvent A3 / A4 / A5. In some examples, the first information may include the last received CPAC execution condition for the CHO associated with the candidate SCG, e.g., a threshold for TTT or CondEvent B1 / A4.

[0151] In some examples, the first information may include recent wireless measurement results from at least one adjacent cell. For example, at least one adjacent cell may include at least one adjacent PCell and / or at least one adjacent PSCell.

[0152] In some examples, the first information may include an indication of whether the measured adjacent cell included in the measurement result is a candidate target PCell for a CHO with a candidate SCG, for example, the first information may include an indication relating to the measured adjacent cell included in the measurement result being a candidate target PCell for a CHO with a candidate SCG. In some examples, the first information may include an indication of whether the measured adjacent cell included in the measurement result is a candidate target PSCell for a CHO with a candidate SCG, for example, the first information may include an indication relating to the measured adjacent cell included in the measurement result being a candidate target PSCell for a CHO with a candidate SCG.

[0153] In some examples, the first information may include a list of candidate target PCells last configured for CHOs with candidate SCGs that are not included in the measurement results (for example, one cell in the list of candidate target PCells may be represented by PLMN+CGI or PCI+ARFCN). In some examples, the first information may include a list of candidate target PSCells last configured for CHOs with candidate SCGs that are not included in the measurement results (for example, one cell in the list of candidate target PSCells may be represented by PLMN+CGI or PCI+ARFCN).

[0154] As an addition or alternative, UE230 may further transmit the first information to a receiving node, for example, target MN215, target SN225, or a further RAN node that is the UE230's serving RAN node (such as a base station not shown in Figure 2).

[0155] In some exemplary embodiments, the SHR and SPR may be reused for a successful CHO procedure with a candidate SCG to store or report the first information. In some embodiments, the UE230 may send the SHR and SPR to a receiving node (target MN215, target SN, or a further RAN node which is the serving RAN node of the UE230).

[0156] In some examples, UE230 may send instructions to a receiving node (target MN215, target SN, or another RAN node that is the serving RAN node of UE230) indicating that both SHR and SPR are available for a CHO procedure with a candidate SCG. For example, instructions relating to the availability of both SHR and SPR sent to the receiving node may be included in an RRC message, such as an RRC (connection) reconfiguration complete message.

[0157] In some examples, UE230 may send a first instruction to the receiving node indicating that an SHR is available for a CHO procedure with a candidate SCG, and a second instruction to the receiving node indicating that an SPR is available for a CHO procedure with a candidate SCG. For example, UE230 may send instructions relating to the availability of an SHR for a CHO procedure with a candidate SCG in one RRC message (e.g., an RRC reconfiguration complete message), and similarly, UE may send another instruction relating to the availability of an SPR for a CHO procedure with a candidate SCG in the same RRC message.

[0158] In some examples, both the SHR and SPR can be requested by the receiving node from the UE via a single request message, and after the UE receives the request message, both the SHR and SPR can be responded to by the UE from the receiving node via a single RRC message. For example, the receiving node may send a request to the UE230 for the SHR and SPR, which may be a UE information request message, which may be an RRC message. In some examples, the UE230 may send the SHR and SPR to the receiving node based on the request from the receiving node, which may be included in the same message, a UE information response message, which may be an RRC message.

[0159] In some other exemplary embodiments, a new report (such as a successful handover report with PSCell changes, or a report with another name used to include the first information) may be used for a successful CHO procedure with a candidate SCG to store or report the first information.

[0160] In some examples, UE230 may send instructions to a receiving node (target MN215, target SN, or another RAN node that is the serving RAN node of UE230) indicating that first information relating to a nearly failed successful CHO with a candidate SCG is available, or that a successful handover report with a PSCell change for a CHO procedure with a candidate SCG is available. That is, UE230 may send instructions to a receiving node relating to the availability of first information, or the availability of a successful handover report with a PSCell change, or the availability of information relating to a nearly failed successful CHO procedure with a candidate SCG. For example, instructions to a receiving node may be included in an RRC message, such as an RRC (connection) reconfiguration complete message.

[0161] In some examples, the receiving node may send an instruction (or request) to the UE230 for a successful handover report with the first information or PSCell change. For example, the receiving node may send an RRC message (e.g., a UE information request message) to the UE to request a successful handover report with the first information or PSCell change, and the instruction to request a successful handover report with the first information or PSCell change may be included in the RRC message. In some examples, the UE230 may send a successful handover report with the first information or a PSCell change (including the first information) to the receiving node based on the instruction (or request) from the receiving node. For example, the successful handover report with the first information or PSCell change may be sent via a UE information response message, which may be an RRC message.

[0162] On the other side of the communication, the receiving node (target MN215, target SN, or another RAN node which is the serving RAN node of UE230) may receive SHR and SPR, or a report from UE230 which has a name used to include a successful handover report with a PSCell change or other information. In some exemplary embodiments, the receiving node may forward the SHR and SPR, or the report which has a name used to include a successful handover report with a PSCell change or other information, to source MN210. In some exemplary embodiments, if the receiving node is not target MN215, the receiving node may forward the SHR and SPR, or the report which has a name used to include a successful handover report with a PSCell change or other information, to target MN215.

[0163] In some implementations, source MN210 may perform further MRO analysis based on the first information, or reports with other names used to include the first information, such as SHR and SPR, or successful handover reports with PSCell changes.

[0164] In some exemplary embodiments, the SHR and SPR may be sent to the source MN210, which should identify first information contained within the SHR and SPR for correct MRO analysis and optimization. In some embodiments, the source MN210 needs to identify that the SHR and SPR are for the same UE in the same CHO procedure with the candidate SCG. In some examples, the receiving node may send instructions to the source MN210 relating to the SHR and SPR being for the same UE in the same CHO procedure with the candidate SCG (for example, based on instructions from the UE relating to both the SHR and SPR being available for the CHO with the candidate SCG, or based on the same new causal value in both the SHR and SPR). The receiving node may forward both the SHR and SPR to the source MN210 simultaneously via the same X2 / Xn message, implicitly indicating to the source MN210 that the SHR and SPR are for the same UE in the same CHO procedure with the candidate SCG. In some examples, a common IE for identification may be included in both the SHR and SPR, for example, the common IE may be source PCell C-RNTI, source PSCell C-RNTI, target PCell C-RNTI, or target PSCell C-RNTI, or the common IE may be an instruction relating to the fact that the SHR and SPR are for the same UE in the same CHO procedure with a candidate SCG.

[0165] In some examples, source MN210 may analyze whether the parameters of the CHO execution conditions for the candidate target PCell need to be optimized. In some examples, source MN210 may analyze whether the parameters of the CPAC execution conditions for the candidate target PSCell need to be optimized. In some exemplary embodiments, source MN210 may generate (or determine) an analysis result. In some examples, source MN210 may send the analysis result to target MN215. For example, the analysis result may indicate that the parameters of the CPAC execution conditions for the candidate target PSCell need to be optimized. For example, the analysis result may indicate that the parameters of the CHO execution conditions for the candidate target PCell need to be optimized. In some examples, target MN215 may further optimize the parameters of the CPAC execution conditions for the candidate target PSCell accordingly.

[0166] In some implementations, source MN210 may send a report to target MN215 containing first information, or a report with other names used to include a successful handover report with SHR and SPR, or PSCell changes, or first information. In some examples, target MN215 may perform further MRO analysis based on the first information, or a report with other names used to include a successful handover report with SHR and SPR, or PSCell changes, or first information. In some examples, target MN215 may analyze whether the parameters of the CHO execution conditions for a candidate target PCell need to be optimized. In some examples, target MN215 may analyze whether the parameters of the CPAC execution conditions for a candidate target PSCell need to be optimized. In some exemplary embodiments, target MN215 may generate (or determine) an analysis result. In some examples, target MN215 may send the analysis result to source MN210. For example, the analysis result may indicate that the parameters of the CHO execution conditions for a candidate target PCell need to be optimized. For example, the analysis results may indicate that the parameters of the CPAC execution conditions for the candidate target PSCell need to be optimized. In some examples, source MN210 may further optimize the parameters of the CPAC execution conditions for the candidate target PSCell accordingly.

[0167] As an addition or alternative, UE230 may transmit capability information to the network, for example, UE230 may transmit capability information to source MN210 or source SN220. For example, capability information may be transmitted to source MN210, and source MN210 may further transmit (e.g., forward) the capability information to source SN220 or candidate target MN215 or candidate target SN225. In some examples, capability information may indicate that UE230 supports a CHO procedure with a candidate SCG. In some examples, capability information may indicate that the UE has the ability to store or report a report (or first information) related to a successful CHO with a candidate SCG.

[0168] For example, a discretionary UE capability may be introduced with signaling for storing or reporting reports (or first information) related to a successful CHO with a candidate SCG. For example, even if the UE supports a CHO mechanism with a candidate SCG, storing or reporting reports, or first information, or information related to a successful CHO procedure with a candidate SCG is discretionary, and this capability is explicitly signaled to the network by the UE, i.e., a discretionary UE capability is introduced with signaling for storing or reporting reports, or first information, or information related to a successful CHO procedure with a candidate SCG, for example, by including a discretionary UE capability instruction for storing or reporting reports, or first information, or information related to a successful CHO procedure with a candidate SCG, for example, in a UE capability information message.

[0169] In some cases, capability information may be omitted. For example, UE230 does not need to explicitly transmit its capability to support a CHO procedure with a candidate SCG, or to store or report a report (or first information) related to a successful CHO with a candidate SCG. For example, an optional UE capability may be introduced that does not involve signaling to store or report a successful report (or first information) related to a successful CHO with a candidate SCG, and storing or reporting a successful report (or first information) related to a successful CHO with a candidate SCG is optional and not signaled by an explicit capability bit.

[0170] According to some exemplary embodiments relating to Figure 4, a second configuration including at least one time threshold may be provided to the UE230, and the UE230 may store the first information in cases where a trigger condition associated with at least one time threshold is met. In some examples, the meeting of the trigger condition may indicate that a nearly successful CHO of a fault with a candidate SCG has been performed, and in some examples the source MN and target MN may perform further MRO in search of a better configuration in the future.

[0171] It should be understood that process 400 relates to a successful (almost failed) CHO procedure with a candidate SCG. In some other implementations, the CHO procedure with a candidate SCG may fail, or a failure may occur within the CHO procedure with a candidate SCG, for example, UE230 may fail to hand over or access the target PCell, or an RLF may occur immediately after UE230 successfully hands over or accesses the target PCell, or UE230 may fail to perform a PSCell addition, PSCell modification, or access to a target PSCell, or an SCG failure or RLF may occur immediately after UE230 successfully performs a PSCell addition, PSCell modification, or access to a target PSCell. When the CHO procedure with a candidate SCG fails, or a failure occurs within the CHO procedure with a candidate SCG, UE230 may generate a failure report, which may be further sent to further RAN nodes that are the serving RAN nodes of UE230. In some exemplary embodiments, the failure report may include, if any, the type of the first satisfied execution condition for the CHO with candidate SCG (for example, the type may indicate that the first satisfied execution condition is a CHO execution condition for the CHO with candidate SCG, or the type may indicate that the first satisfied execution condition is a CPAC execution condition for the CHO with candidate SCG), and, if any, the duration between the two satisfied execution conditions for the CHO with candidate SCG (for example, the duration may be the time elapsed from the time the CHO execution condition for the CHO with candidate SCG was satisfied to the time the CPAC execution condition for the CHO with candidate SCG was satisfied).Otherwise, the duration may be the time elapsed from the time the CPAC execution condition for the CHO with candidate SCG was met and the time the CHO execution condition for the CHO with candidate SCG was met, i.e., the time elapsed from the time the CPAC execution condition for the CHO with candidate SCG was met until the CHO execution condition for the CHO with candidate SCG was met), a new type for lastHO-Type or a new type for lastPSCellchange-Type, for example, chowithcandidateSCG (for example, its type may indicate that a failure occurred in the CHO procedure with candidate SCG), one or more last received CHO execution conditions for the CHO with candidate SCG, one or more last received CPAC execution conditions for the CHO with candidate SCG, recent radio measurement results of at least one adjacent cell, at least one of the at least one candidate PCell configured for the CHO with candidate SCG The report may include one or more of the following: an instruction indicating whether an adjacent cell belongs to a candidate PCell (for example, an instruction indicating that at least one adjacent cell belongs to at least one candidate PCell configured for a CHO with a candidate SCG); an instruction indicating whether at least one adjacent cell belongs to at least one candidate PSCell configured for a CHO with a candidate SCG (for example, an instruction indicating that at least one adjacent cell belongs to at least one candidate PSCell configured for a CHO with a candidate SCG); a list of candidate PCells configured for a CHO with a candidate SCG that are not in at least one adjacent cell (for example, one cell in the list of candidate PCells may be represented by PLMN+CGI or PCI+ARFCN); or a list of candidate PSCells configured for a CHO with a candidate SCG that are not in at least one adjacent cell (for example, one cell in the list of candidate PSCells may be represented by PLMN+CGI or PCI+ARFCN). In some exemplary embodiments, the failure report may be an RLF report. In some exemplary embodiments, failure reports may be sent by the UE230 to a further RAN node, which is the serving RAN node of the UE230.In some exemplary embodiments, failure reports may be transmitted to source MN210 (e.g., from a further RAN node) and / or failure reports may be transmitted to target MN215 (e.g., from a further RAN node), and source MN210 or target MN215 may perform MRO analysis or optimization, for example, source MN210 or target MN215 may analyze whether the parameters of the CPAC execution conditions for CHO with candidate SCG and / or the parameters of the CHO execution conditions for CHO with candidate SCG need to be optimized, and then source MN210 or target MN215 may perform the corresponding optimizations based on the analysis.

[0172] Further reference is made to Figure 5, which shows a signaling chart illustrating a communication process 500 according to some exemplary embodiments of the present disclosure. Process 500 may involve a source MN210, a UE230, and a target MN215.

[0173] In process 500, source MN210 sends a first configuration to UE230 in 510, which may be called a configuration for a CHO with a candidate SCG, as described above. The first configuration may include one or more CHO execution conditions for a CHO with a candidate SCG, and one or more CPAC execution conditions for a CHO with a candidate SCG.

[0174] In some exemplary embodiments, for each candidate target PCell, source MN210 may configure a corresponding CHO execution condition for a CHO with a candidate SCG, which may consist of one or two trigger conditions such as CondEvent A3 / A4 / A5. In some exemplary embodiments, for each candidate target PSCell, the corresponding candidate target MN may provide source MN210 with parameters for a CPAC execution condition, which source MN210 then generates one or more CPAC execution conditions for a CHO with a candidate SCG and sends them to UE230 in the first configuration.

[0175] In some examples, the first configuration may represent a first candidate target PCell and an associated first candidate target PSCell, where the first candidate target PCell may relate to a first CHO execution condition and the first candidate target PSCell may relate to a first CPAC execution condition. In some examples, the first configuration may represent a second candidate target PCell and an associated second candidate target PSCell, where the second candidate target PCell may relate to a second CHO execution condition and the second candidate target PSCell may relate to a second CPAC execution condition. It should be understood that the number of candidate target PCells represented by the first configuration is not limited in this disclosure.

[0176] In process 500, source MN210 sends a third configuration to UE230 at 520. The third configuration may include at least one CHO execution condition for a mere CHO, for example, a third configuration sometimes referred to as a configuration for a mere CHO as described above. For example, the third configuration, i.e., a configuration for a mere CHO, includes at least one MCG configuration for at least one candidate target PCell (the candidate target PCell for a mere CHO may be the same as or different from the candidate target PCell for a CHO with a candidate SCG), and at least one CHO execution condition for at least one candidate target PCell for a mere CHO. In some exemplary embodiments, the third configuration may indicate that at least one candidate target PCell for a mere CHO is configured, and for each candidate target PCell within the at least one candidate target PCell for a mere CHO, a corresponding CHO execution condition for a mere CHO is configured.

[0177] In process 500, source MN210 sends a fourth configuration to UE230 at 530. The fourth configuration may include at least one CHO execution condition for legacy R17 CHO with SCG, for example, the fourth configuration may be called a configuration for CHO with SCG as described above. For example, the fourth configuration, i.e., a configuration for CHO with SCG, includes at least one MCG configuration for at least one candidate target PCell (the candidate target PCell for CHO with SCG may be the same as or different from the candidate target PCell for CHO with SCG), at least one CHO execution condition for at least one candidate target PCell for CHO with SCG, and at least one SCG configuration for at least one target PSCell (one associated target PSCell is configured for each candidate target PCell for CHO with SCG). In some exemplary embodiments, the fourth configuration may indicate that at least one candidate target PCell for a CHO with SCG is configured, and for each candidate target PCell within the at least one candidate target PCell for a CHO with SCG, a corresponding CHO execution condition for the CHO with SCG is configured.

[0178] It should be understood that in some cases, one of operations 520 and 530 may be omitted. For example, there may be a first and third configuration configured for UE230 without the fourth configuration. In another example, there may be a first and fourth configuration configured for UE230 without the third configuration.

[0179] It should be understood that in some cases operations 520 and 530 may be performed. For example, the first configuration, the third configuration, and the fourth configuration may be configured for UE230 within the same single RRC message, or within two RRC messages, or within three RRC messages.

[0180] In some exemplary embodiments, UE230 may evaluate one or more CHO execution conditions for a CHO with a candidate SCG, and one or more CPAC execution conditions for a CHO with a candidate SCG. In some exemplary embodiments, UE230 may also evaluate at least one CHO execution condition for a CHO without a SCG. In some exemplary embodiments, UE230 may also evaluate at least one CHO execution condition for a CHO with an SCG.

[0181] In some embodiments, the CHO execution conditions for a CHO with a candidate SCG may be met, but the associated CPAC execution conditions for the CHO with a candidate SCG may not be met, or the CPAC execution conditions for a CHO with a candidate SCG may be met, but the associated CHO execution conditions for the CHO with a candidate SCG may not be met, and in addition, the CHO execution conditions for a simple CHO may be met, in which case a simple CHO execution may be performed. For example, UE230 may perform a simple CHO execution on a first target PCell that satisfies the CHO execution conditions for a simple CHO.

[0182] In some other embodiments, the CHO execution conditions for a CHO with a candidate SCG may be met, but the associated CPAC execution conditions for the CHO with a candidate SCG may not be met, or the CPAC execution conditions for a CHO with a candidate SCG may be met, but the associated CHO execution conditions for the CHO with a candidate SCG may not be met, and in addition, the CHO execution conditions for a legacy R17 CHO with an SCG may be met, in which case a legacy R17 CHO execution with an SCG may be performed. For example, UE230 may perform a legacy R17 CHO execution with an SCG, for example, UE access to a second target PCell and its associated target PSCell, where the second target PCell satisfies the CHO execution conditions for a CHO with an SCG, for example, the UE performs a UE handover or access to the second target PCell, and the UE also performs a PSCell addition or modification or access to a target PSCell associated with the second target PCell.

[0183] In process 500, UE230 performs access to the first target PCell, or the second target PCell and its associated target PSCell, at 540.

[0184] In process 500, UE230 stores second information at 550. The second information may relate to a successful legacy R17 CHO with a successful CHO or SCG, but to a CHO with a candidate SCG that cannot be executed or fails even if executed.

[0185] In some exemplary embodiments, the second information may include some information relating to a CHO with a candidate SCG, and some information relating to a legacy CHO with a mere CHO or SCG. In some exemplary embodiments, the UE receives one or more trigger conditions for storing or reporting the second information, or information relating to a successful legacy CHO with a successful mere CHO or SCG, and if at least one of the one or more trigger conditions for storing or reporting the second information, or information relating to a successful legacy CHO with a successful mere CHO or SCG, is met, the UE may store or report the second information, or information relating to a successful legacy CHO with a successful mere CHO or SCG. In some examples, even if the UE does not receive one or more trigger conditions for storing or reporting the second information, or information relating to a successful legacy CHO with a successful mere CHO or SCG, the UE may store or report the second information, or information relating to a successful legacy CHO with a successful mere CHO or SCG, when the legacy CHO with a mere CHO or SCG is successful.

[0186] In some implementations, the second piece of information may include, if any, the type of the first satisfied execution condition for the CHO with a candidate SCG. For example, the type may indicate that the first satisfied execution condition is a CHO execution condition for the CHO with a candidate SCG. For example, the type may indicate that the first satisfied execution condition is a CPAC execution condition for the CHO with a candidate SCG. For example, the type may be omitted, which indicates that neither the CPAC execution condition for the CHO with a candidate SCG nor the CHO execution condition for the CHO with a candidate SCG is satisfied.

[0187] In some examples, the second piece of information may include a new type for lastHO-Type or a new type for lastPSCellchange-Type, such as cho-only or chowithSCG. For example, the type may indicate that the second piece of information is for legacy R17 CHO with just CHO or SCG.

[0188] In some examples, the second piece of information may include the last received CHO execution condition for the CHO associated with the candidate SCG, e.g., a threshold for TTT or CondEvent A3 / A4 / A5. In some examples, the second piece of information may include the last received CPAC execution condition for the CHO associated with the candidate SCG, e.g., a threshold for TTT or CondEvent B1 / A4.

[0189] In some examples, the second piece of information may include, if any, the last received CHO execution condition for a simple CHO, e.g., a threshold for TTT or CondEvent A3 / A4 / A5. In some examples, the second piece of information may include, if any, the last received CHO execution condition for a legacy CHO with an SCG, e.g., a threshold for TTT or CondEvent A3 / A4 / A5.

[0190] In some examples, the second piece of information may include recent wireless measurement results from at least one adjacent cell. For example, at least one adjacent cell may include at least one adjacent PCell and / or at least one adjacent PSCell.

[0191] In some examples, the second information may include an indication of whether the measured adjacent cell included in the measurement results is a candidate target PCell for a CHO with a candidate SCG, for example, the second information may include an indication relating to the measured adjacent cell included in the measurement results being a candidate target PCell for a CHO with a candidate SCG. In some examples, the second information may include an indication of whether the measured adjacent cell included in the measurement results is a candidate target PSCell for a CHO with a candidate SCG, for example, the second information may include an indication relating to the measured adjacent cell included in the measurement results being a candidate target PSCell for a CHO with a candidate SCG.

[0192] In some examples, the second information may include an indication of whether the measured adjacent cell included in the measurement results is a candidate target PCell for a mere CHO, for example, the second information may include an indication relating to the measured adjacent cell included in the measurement results being a candidate target PCell for a mere CHO. In some examples, the second information may include an indication of whether the measured adjacent cell included in the measurement results is a candidate target PCell for a legacy CHO with an SCG, for example, the second information may include an indication relating to the measured adjacent cell included in the measurement results being a candidate target PCell for a legacy CHO with an SCG.

[0193] In some examples, the second piece of information may include, for example, a list of candidate target PCells last configured for a CHO with a candidate SCG that are not included in the measurement results (for example, one cell in the list of candidate target PCells may be represented by PLMN+CGI or PCI+ARFCN).

[0194] In some examples, the second piece of information may include, for example, a list of candidate target PSCells last configured for a CHO with a candidate SCG that are not included in the measurement results (for example, one cell in the list of candidate target PSCells may be represented by PLMN+CGI or PCI+ARFCN).

[0195] In some examples, the second piece of information may include a list of candidate target PCells that were last configured simply for the CHO and are not included in the measurement results (for example, one cell in the list of candidate target PCells may be represented by PLMN+CGI or PCI+ARFCN).

[0196] In some examples, the second piece of information may include, for example, a list of candidate target PCells last configured for legacy CHOs with SCG that are not included in the measurement results (for example, one cell in the list of candidate target PCells may be represented by PLMN+CGI or PCI+ARFCN).

[0197] In some cases, the type of the first satisfied execution condition for a CHO with a candidate SCG indicates that the first satisfied execution condition for a CHO with a candidate SCG belongs to one or more CHO execution conditions for a CHO with a candidate SCG, in other words, if the first satisfied execution condition for a CHO with a candidate SCG is a CHO execution condition for a CHO with a candidate SCG, the second information may further include one or more of the following: an ID indicating a candidate PCell and an ID indicating a candidate PSCell associated with the candidate PCell, the time length between the first time and the second time, the time length between the third time and the second time, or the time length between the third time and the first time. For example, it may include the ID of a candidate PCell that satisfies its associated CHO execution condition for a CHO with a candidate SCG. For example, it may include the ID of an associated candidate PSCell that does not satisfy its associated CPAC execution condition for a CHO with a candidate SCG. For example, the first time is the time when at least one CHO execution condition for a simple CHO is met, or at least one CHO execution condition for a CHO with an SCG is met. For example, the second time is the time when one of the first, third, or fourth configurations is received. For example, the third time is the time when one or more CHO execution conditions for a CHO with a candidate SCG are met.

[0198] For example, if the type of first execution condition satisfied for a CHO with a candidate SCG is a CHO execution condition for a CHO with a candidate SCG (i.e., the CHO execution condition for a CHO with a candidate SCG is satisfied, but the CPAC execution condition for a CHO with a candidate SCG is not satisfied), then the second information is: ■The candidate target PCell ID (e.g., PLMN+CGI or PCI+ARFCN) or associated CondReconfigId may include at least one of the following: the CHO execution conditions for a CHO with a candidate SCG are met, but the associated CPAC execution conditions for a CHO with a candidate SCG are not met. ■For example, to indicate the time elapsed between the start of the last CHO execution toward the target PCell for a legacy CHO with a simple CHO or SCG (or the fulfillment of the CHO execution condition for a legacy CHO with a simple CHO or SCG, or the execution of a simple CHO execution or an execution for a legacy CHO with an SCG) and the reception of a recent conditional reconfiguration (for a CHO with a simple CHO and candidate SCG, or for a legacy CHO with an SCG and a candidate SCG), an existing IE, such as TimeSinceCHO-Reconfig for a legacy CHO with a simple CHO or SCG, may be reused. ■A new IE may be added to indicate the time elapsed between the fulfillment of the CHO execution conditions for a CHO with a candidate SCG and the receipt of a recent conditional reconstruction (for a simple CHO and a CHO with a candidate SCG, or for a legacy CHO with an SCG and a CHO with a candidate SCG, or for a simple CHO, a legacy CHO with an SCG, and a CHO with a candidate SCG), or ■ New IEs may be added to indicate the time elapsed between the fulfillment of the CHO execution conditions for a CHO with a candidate SCG and the start of the last CHO execution toward the target PCell for a simple CHO or legacy CHO with an SCG, or the time elapsed between the fulfillment of the CHO execution conditions for a CHO with a candidate SCG and the fulfillment of the CHO execution conditions for a simple CHO or legacy CHO with an SCG, or the time elapsed between the fulfillment of the CHO execution conditions for a CHO with a candidate SCG and the execution of a simple CHO or execution toward a legacy CHO with an SCG.

[0199] Referring to Figure 6A, which shows an exemplary timing schematic diagram 610, it is assumed that t0 represents the time of reception of the most recent conditional configuration, which is the most recent of the times for reception of the first configuration, the time for reception of the third configuration, and the time for reception of the fourth configuration. It is assumed that t1 represents the time when the CHO execution condition is met for the CHO with a candidate SCG. It is assumed that t2 represents the time when the CHO execution condition is met for a simple CHO or a legacy CHO with an SCG. As shown in Figure 6A, T1 may represent the time length between t0 and t1, T2 may represent the time length between t1 and t2, and T3 may represent the time length between t0 and t2.

[0200] For example, the second piece of information may include one or more of T1, T2, or T3. For example, IE TimeSinceCHO-Reconfig may be reused to represent T3. For example, a new IE may be used to represent T1. For example, another new IE may be used to represent T2.

[0201] In some cases, the type of the first satisfied execution condition for a CHO with a candidate SCG indicates that the first satisfied execution condition for a CHO with a candidate SCG belongs to one or more CPAC execution conditions for a CHO with a candidate SCG, in other words, if the first satisfied execution condition for a CHO with a candidate SCG is a CPAC execution condition for a CHO with a candidate SCG, the second information may further include one or more of the following: an ID indicating a candidate PCell and an ID indicating a candidate PSCell associated with the candidate PCell, the time length between the first time and the second time, the time length between the fourth time and the second time, or the time length between the fourth time and the first time. For example, it may include the ID of a candidate PCell that does not satisfy its associated CHO execution condition for a CHO with a candidate SCG. For example, it may include the ID of a candidate PSCell that satisfies its associated CPAC execution condition for a CHO with a candidate SCG (associated with a candidate PCell that does not satisfy its associated CHO execution condition for a CHO with a candidate SCG). For example, the first time is the time when at least one CHO execution condition for a CHO alone is met, or at least one CHO execution condition for a CHO with an SCG is met. For example, the second time is the time when one of the first, third, or fourth configurations is received. For example, the fourth time is the time when one or more CPAC execution conditions for a CHO with a candidate SCG are met.

[0202] For example, if the type of first execution condition that is satisfied for a CHO with a candidate SCG is the CPAC execution condition for a CHO with a candidate SCG (i.e., the CHO execution condition for a CHO with a candidate SCG is not satisfied, but the CPAC execution condition for a CHO with a candidate SCG is satisfied), then the second information is: ■The candidate target PCell ID (e.g., PLMN+CGI or PCI+ARFCN) or associated CondReconfigId may include at least one of the following: a candidate target PSCell ID (e.g., PLMN+CGI or PCI+ARFCN) or associated CondReconfigId for a CHO with a candidate SCG, where the CHO execution conditions for that CHO are not met, but the associated CPAC execution conditions for the CHO with the candidate SCG are met. ■For example, to indicate the time elapsed between the start of the last CHO execution toward the target PCell for a legacy CHO with a simple CHO or SCG (or the fulfillment of the CHO execution condition for a legacy CHO with a simple CHO or SCG, or the execution of a simple CHO execution or an execution for a legacy CHO with an SCG) and the reception of a recent conditional reconfiguration (for a CHO with a simple CHO and candidate SCG, or for a legacy CHO with an SCG and a candidate SCG), an existing IE TimeSinceCHO-Reconfig for a legacy CHO with a simple CHO or SCG may be reused. ■A new IE may be added to indicate the time elapsed between the CPAC execution conditions for a CHO with a candidate SCG being met and the receipt of a recent conditional reconfiguration (for simple CHOs and CHOs with a candidate SCG, or for legacy CHOs with an SCG and CHOs with a candidate SCG), or ■ New IEs may be added to indicate the time elapsed between the fulfillment of the CPAC execution conditions for a CHO with a candidate SCG and the start of the last CHO execution toward the target PCell for a simple CHO or legacy CHO with an SCG, or the time elapsed between the fulfillment of the CPAC execution conditions for a CHO with a candidate SCG and the fulfillment of the CHO execution conditions for a simple CHO or legacy CHO with an SCG, or the time elapsed between the fulfillment of the CPAC execution conditions for a CHO with a candidate SCG and the execution of a simple CHO execution or execution toward a legacy CHO with an SCG.

[0203] Referring to Figure 6B, which shows an exemplary timing schematic diagram 620, it is assumed that t0 represents the time of reception of the most recent conditional configuration, which is the most recent of the times for reception of the first configuration, the time for reception of the third configuration, and the time for reception of the fourth configuration. It is assumed that t11 ​​represents the time when the CPAC execution condition for the CHO with candidate SCG is met. It is assumed that t2 represents the time when the CHO execution condition for a simple CHO or a legacy CHO with SCG is met. As shown in Figure 6B, T11 may represent the time length between t0 and t11, T12 may represent the time length between t11 and t2, and T3 may represent the time length between t0 and t2.

[0204] For example, the second piece of information may include one or more of T11, T12, or T3. For example, IE TimeSinceCHO-Reconfig may be reused to represent T3. For example, a new IE may be used to represent T11. For example, another new IE may be used to represent T12.

[0205] As an addition or alternative, UE230 may further transmit the second information to a receiving node, for example, target MN215, target SN225, or another RAN node that is the UE230's serving RAN node (such as a base station not shown in Figure 2).

[0206] In some exemplary embodiments, the SHR or SPR may be reused for transmitting a second piece of information, or the SHR or SPR may be reused for storing or reporting the second piece of information. In some embodiments, the UE230 may transmit the SHR to a receiving node (target MN215, target SN225, or further RAN node), where the SHR contains the second piece of information. In some examples, the SHR may be triggered or stored by the UE230, or reported to the receiving node.

[0207] In some examples, the SHR may be forwarded from the receiving node to the target MN215. In some examples, the target MN215 may perform MRO based on the SHR. In some examples, the target MN215 may analyze whether the parameters of the CPAC execution conditions for the CHO with the candidate SCG need to be optimized. In some examples, the target MN215 may show the source MN210 the results of its analysis on whether the parameters of the CPAC execution conditions for the CHO with the candidate SCG need to be optimized (for example, the target MN215 may inform the source MN210 that the parameters of the CPAC execution conditions for the CHO with the candidate SCG need to be optimized).

[0208] In some examples, the SHR may be forwarded from the receiving node to the source MN210. In some examples, the source MN210 may perform MRO based on the SHR. In some examples, the source MN210 may analyze whether the parameters of the CPAC execution conditions for CHOs with candidate SCGs need to be optimized. In some examples, the source MN210 may show the target MN215 the results of its analysis on whether the parameters of the CPAC execution conditions for CHOs with candidate SCGs need to be optimized (for example, the source MN210 may inform the target MN215 that the parameters of the CPAC execution conditions for CHOs with candidate SCGs need to be optimized). In some examples, the source MN210 may analyze whether the parameters of the CHO execution conditions for a simple CHO need to be optimized, or whether the parameters of the CHO execution conditions for a legacy CHO with an SCG need to be optimized, or whether the parameters of the CHO execution conditions for a CHO with a candidate SCG need to be optimized. In some examples, source MN210 may provide target MN215 with analysis results regarding whether the parameters of the CHO execution conditions need to be optimized for a simple CHO, or for a legacy CHO with an SCG, or for a CHO with a candidate SCG (for example, source MN210 may inform target MN215 that the parameters of the CHO execution conditions need to be optimized for a CHO with a candidate SCG).

[0209] In some other exemplary embodiments, if an SHR is not triggered / stored / reported within UE230, UE230 may report second information to the receiving node, for example, in an RRC reconfiguration complete message. In some examples, the receiving node may be the target MN215.

[0210] In some examples, target MN215 may analyze whether the parameters of the CPAC execution conditions for CHOs with candidate SCGs need to be optimized. In some examples, target MN215 may provide source MN210 with the results of its analysis on whether the parameters of the CPAC execution conditions for CHOs with candidate SCGs need to be optimized (for example, target MN215 may inform source MN210 that the parameters of the CPAC execution conditions for CHOs with candidate SCGs need to be optimized).

[0211] In some examples, target MN215 may analyze whether the parameters of the CHO execution conditions need to be optimized for a legacy CHO with a simple CHO or SCG, or for a CHO with a candidate SCG. In some examples, target MN215 may show source MN210 the results of its analysis on whether the parameters of the CHO execution conditions need to be optimized for a legacy CHO with a simple CHO or SCG, or for a CHO with a candidate SCG (for example, target MN215 may inform source MN210 that the parameters of the CHO execution conditions need to be optimized for a CHO with a candidate SCG).

[0212] In some examples, the second piece of information may be forwarded by the target MN215 to the source MN210. In some examples, the source MN210 may analyze whether the parameters of the CHO execution conditions need to be optimized for a legacy CHO with a simple CHO or an SCG, or for a CHO with a candidate SCG. In some examples, the source MN210 may analyze whether the parameters of the CPAC execution conditions need to be optimized for a CHO with a candidate SCG.

[0213] As described above, when a CHO with a candidate SCG cannot be triggered but the execution conditions for a simple CHO are met, the UE may execute the simple CHO, for example, accessing a first target PCell that satisfies the execution conditions for the simple CHO. However, in some cases, a failure may occur within the simple CHO, i.e., the execution of the simple CHO may fail, or an RLF may occur immediately after a successful execution of the simple CHO. For example, synchronization with the first target PCell or random access to the first target PCell may fail. For example, UE230 may fail to hand over or access the first target PCell, or an RLF may occur immediately after UE230 successfully hand over or accesses the first target PCell.

[0214] Similarly, as described above, when a CHO with a candidate SCG cannot be triggered but the CHO execution conditions for a legacy CHO with an SCG are met, the execution of the legacy CHO with an SCG, for example, access to a second target PCell and its associated target PSCell, may be performed by the UE, where the second target PCell satisfies the CHO execution conditions for the legacy CHO with an SCG. However, in some examples, a failure may occur within the legacy CHO with an SCG, i.e., the execution of the legacy CHO with an SCG may fail, or an RLF may occur immediately after a successful execution of the legacy CHO with an SCG. For example, synchronization with the second target PCell or random access to the second target PCell may fail. For example, UE230 may fail to hand over or access the second target PCell, or an RLF may occur immediately after UE230 successfully hand over or accesses the second target PCell.

[0215] In some implementations, the UE230 may store (or log) a first failure information. For example, the first failure information may relate to a failure occurring in a simple CHO or in a legacy CHO with an SCG, and for example, the first failure information may relate to a failure when accessing a first target PCell or a second target PCell. In some implementations, the first failure information may be further transmitted to a further RAN node, which is the serving RAN node of the UE230. In some implementations, the first failure information may be included in the RLF report. In some exemplary embodiments, first failure information may be transmitted to source MN210 and / or failure report may be transmitted to target MN215, and source MN210 or target MN215 may perform MRO analysis or optimization, for example, source MN210 or target MN215 may analyze whether the parameters of the CPAC execution conditions for CHO with candidate SCG need to be optimized and / or whether the parameters of the CHO execution conditions for CHO with candidate SCG need to be optimized, and then source MN210 or target MN215 may perform the corresponding optimization based on the analysis.

[0216] In some implementations, the first failure information may include some information relating to a CHO with a candidate SCG, and some information relating to a legacy CHO with just a CHO or an SCG.

[0217] In some examples, the first failure information may include the source PCell ID (i.e., the source PCell ID) (for example, the ID may be represented by PLMN+CGI or PCI+ARFCN). For example, the source PCell may be provided by source MN210.

[0218] In some examples, the first failure information may include the ID of the target PCell (i.e., the target PCell ID) (for example, the ID may be represented by PLMN+CGI or PCI+ARFCN). For example, the target PCell may be the first target PCell or the second target PCell described above.

[0219] In some examples, the first failure information may include, if any, the type of the first satisfied execution condition for the CHO with the candidate SCG. For example, the type may indicate that the first satisfied execution condition is a CHO execution condition for the CHO with the candidate SCG. For example, the type may indicate that the first satisfied execution condition is a CPAC execution condition for the CHO with the candidate SCG. For example, the type may be omitted, which indicates that neither the CPAC execution condition for the CHO with the candidate SCG nor the CHO execution condition for the CHO with the candidate SCG is satisfied.

[0220] In some cases, the type of the first satisfied execution condition for a CHO with a candidate SCG indicates that the first satisfied execution condition for a CHO with a candidate SCG belongs to one or more CHO execution conditions for a CHO with a candidate SCG, in other words, if the first satisfied execution condition for a CHO with a candidate SCG is a CHO execution condition for a CHO with a candidate SCG, the first failure information may further include one or more of the following: an ID indicating a candidate PCell and an ID indicating a candidate PSCell associated with the candidate PCell, the time length between the first time and the second time, the time length between the third time and the second time, the time length between the third time and the first time, the time length between the first time and the fifth time, the time length between the second time and the fifth time, or the time length between the third time and the fifth time. For example, it may include the ID of a candidate PCell that satisfies its associated CHO execution condition for a CHO with a candidate SCG. For example, it may include the ID of an associated candidate PSCell that does not satisfy its associated CPAC execution condition for a CHO with a candidate SCG. For example, the first time is the time when at least one CHO execution condition for a simple CHO is met, or at least one CHO execution condition for a CHO with an SCG is met. For example, the second time is the time when one of the first, third, or fourth configurations is received. For example, the third time is the time when one or more CHO execution conditions for a CHO with a candidate SCG are met. For example, the fifth time is the time when a simple CHO execution fails, or an execution of a CHO with an SCG fails, or an RLF occurs immediately after a successful simple CHO execution, or an RLF occurs immediately after a successful execution of a CHO with an SCG.

[0221] For example, if the type of first execution condition met for a CHO with a candidate SCG is a CHO execution condition for a CHO with a candidate SCG (i.e., the CHO execution condition for a CHO with a candidate SCG is met, but the CPAC execution condition for a CHO with a candidate SCG is not met), then the first failure information is: ■The candidate target PCell ID (e.g., PLMN+CGI or PCI+ARFCN) or associated CondReconfigId may include at least one of the following: the CHO execution conditions for a CHO with a candidate SCG are met, but the associated CPAC execution conditions for a CHO with a candidate SCG are not met. ■For example, to indicate the time elapsed between the start of the last CHO execution toward the target PCell for a legacy CHO with a simple CHO or SCG (or the fulfillment of the CHO execution condition for a legacy CHO with a simple CHO or SCG, or the execution of a simple CHO execution or an execution for a legacy CHO with an SCG) and the reception of a recent conditional reconfiguration (for a CHO with a simple CHO and a candidate SCG, or for a legacy CHO with an SCG and a candidate SCG, or for a CHO with a simple CHO, a legacy CHO with an SCG, and a candidate SCG), an existing IE, such as TimeSinceCHO-Reconfig for a legacy CHO with a simple CHO or SCG, may be reused. ■Existing IEs, for example, timeConnFailure for legacy CHOs with simple CHOs or SCGs, may be reused to indicate the time elapsed from the start of the last CHO execution toward the target PCell for a legacy CHO with simple CHOs or SCGs (or from the fulfillment of the CHO execution conditions for a legacy CHO with simple CHOs or SCGs, or from the execution of a simple CHO execution or an execution for a legacy CHO with SCGs) to a connection failure (i.e., a failure occurs in a simple CHO or a failure occurs in a legacy CHO with SCGs). ■A new IE may be added to indicate the time elapsed between the fulfillment of the CHO execution conditions for a CHO with a candidate SCG and the receipt of a recent conditional reconstruction (for a simple CHO and a CHO with a candidate SCG, or for a legacy CHO with an SCG and a CHO with a candidate SCG, or for a simple CHO, a legacy CHO with an SCG, and a CHO with a candidate SCG). ■Alternatively, to indicate the time elapsed between the fulfillment of the CHO execution conditions for a CHO with a candidate SCG and the start of the last CHO execution toward the target PCell for a simple CHO or legacy CHO with an SCG, or the time elapsed between the fulfillment of the CHO execution conditions for a CHO with a candidate SCG and the fulfillment of the CHO execution conditions for a simple CHO or legacy CHO with an SCG, or the time elapsed between the fulfillment of the CHO execution conditions for a CHO with a candidate SCG and the execution of a simple CHO or legacy CHO with an SCG, a new IE may be added, or ■A new IE may be added to indicate the time elapsed between the fulfillment of the CHO execution conditions for a CHO with a candidate SCG and a connection failure (i.e., a failure occurring in a simple CHO or a failure occurring in a legacy CHO with an SCG).

[0222] In some cases, the type of the first satisfied execution condition for a CHO with a candidate SCG indicates that the first satisfied execution condition for a CHO with a candidate SCG belongs to one or more CPAC execution conditions for a CHO with a candidate SCG, in other words, if the first satisfied execution condition for a CHO with a candidate SCG is a CPAC execution condition for a CHO with a candidate SCG, the first failure information may further include one or more of the following: an ID indicating a candidate PCell and an ID indicating a candidate PSCell associated with the candidate PCell, the time length between the first time and the second time, the time length between the fourth time and the second time, the time length between the fourth time and the first time, the time length between the first time and the fifth time, the time length between the second time and the fifth time, or the time length between the fourth time and the fifth time. For example, it may include the ID of a candidate PCell that does not satisfy its associated CHO execution condition for a CHO with a candidate SCG. For example, it may include the ID of a candidate PSCell that satisfies the associated CPAC execution conditions for a CHO with a candidate SCG (relating to a candidate PCell that does not satisfy the associated CHO execution conditions for a CHO with a candidate SCG). For example, the first time is the time when at least one CHO execution condition for a simple CHO is met, or at least one CHO execution condition for a CHO with an SCG is met. For example, the second time is the time when one of the first, third, or fourth configurations is received. For example, the fourth time is the time when one or more CPAC execution conditions for a CHO with a candidate SCG are met. For example, the fifth time is the time when a simple CHO execution fails, or an execution of a CHO with an SCG fails, or an RLF occurs immediately after a successful simple CHO execution, or an RLF occurs immediately after a successful execution of a CHO with an SCG.

[0223] For example, if the type of first execution condition met for a CHO with a candidate SCG is the CPAC execution condition for a CHO with a candidate SCG (i.e., the CHO execution condition for a CHO with a candidate SCG is not met, but the CPAC execution condition for a CHO with a candidate SCG is met), then the first failure information is: ■The ID of a candidate target PCell (e.g., PLMN+CGI or PCI+ARFCN) or its associated CondReconfigId may include at least one of the following: the ID of a candidate target PSCell (e.g., PLMN+CGI or PCI+ARFCN) or its associated CondReconfigId, and / or the ID of a candidate target PSCell (e.g., PLMN+CGI or PCI+ARFCN) or its associated CondReconfigId for a CHO with a candidate SCG, for which the CHO execution conditions are not met, but the CPAC execution conditions for a CHO with a candidate SCG are met. ■For example, to indicate the time elapsed between the start of the last CHO execution toward the target PCell for a legacy CHO with a simple CHO or SCG (or the fulfillment of the CHO execution condition for a legacy CHO with a simple CHO or SCG, or the execution of a simple CHO execution or an execution for a legacy CHO with an SCG) and the reception of a recent conditional reconfiguration (for a CHO with a simple CHO and a candidate SCG, or for a legacy CHO with an SCG and a candidate SCG, or for a CHO with a simple CHO, a legacy CHO with an SCG, and a candidate SCG), an existing IE, TimeSinceCHO-Reconfig for a legacy CHO with a simple CHO or SCG, may be reused. ■Existing IEs, for example, timeConnFailure for legacy CHOs with simple CHOs or SCGs, may be reused to indicate the time elapsed from the start of the last CHO execution toward the target PCell for a legacy CHO with simple CHOs or SCGs (or from the fulfillment of the CHO execution conditions for a legacy CHO with simple CHOs or SCGs, or from the execution of a simple CHO execution or an execution for a legacy CHO with SCGs) to a connection failure (i.e., a failure occurs in a simple CHO or a failure occurs in a legacy CHO with SCGs). ■A new IE may be added to indicate the time elapsed between the CPAC execution conditions being met for a CHO with a candidate SCG and the receipt of a recent conditional reconfiguration (for a simple CHO and a CHO with a candidate SCG, or for a legacy CHO with an SCG and a CHO with a candidate SCG, or for a simple CHO, a legacy CHO with an SCG, and a CHO with a candidate SCG). ■To indicate the time elapsed between the fulfillment of the CPAC execution conditions for a CHO with a candidate SCG and the start of the last CHO execution toward the target PCell for a simple CHO or legacy CHO with an SCG, or the time elapsed between the fulfillment of the CPAC execution conditions for a CHO with a candidate SCG and the fulfillment of the CHO execution conditions for a simple CHO or legacy CHO with an SCG, or the time elapsed between the fulfillment of the CPAC execution conditions for a CHO with a candidate SCG and the execution of a simple CHO execution or execution for a legacy CHO with an SCG, a new IE may be added, or ■A new IE may be added to indicate the time elapsed between the CPAC execution conditions being met for a CHO with a candidate SCG and a connection failure (i.e., a failure occurring in a simple CHO or a failure occurring in a legacy CHO with an SCG).

[0224] In some examples, the first failure information may include the last received CHO execution condition for the CHO with the candidate SCG, e.g., a threshold for TTT or CondEvent A3 / A4 / A5. In some examples, the first failure information may include the last received CPAC execution condition for the CHO with the candidate SCG, e.g., a threshold for TTT or CondEvent B1 / A4.

[0225] In some examples, the first failure information may include, if any, the last received CHO execution condition for a simple CHO, e.g., a threshold for TTT or CondEvent A3 / A4 / A5. In some examples, the first failure information may include, if any, the last received CHO execution condition for a legacy CHO with an SCG, e.g., a threshold for TTT or CondEvent A3 / A4 / A5.

[0226] In some examples, the first fault information may include recent wireless measurement results from at least one adjacent cell. For example, at least one adjacent cell may include at least one adjacent PCell and / or at least one adjacent PSCell.

[0227] In some examples, the first fault information may include an indication of whether the measured adjacent cell included in the measurement result is a candidate target PCell for a CHO with a candidate SCG, for example, the first fault information may include an indication relating to the measured adjacent cell included in the measurement result being a candidate target PCell for a CHO with a candidate SCG. In some examples, the first fault information may include an indication of whether the measured adjacent cell included in the measurement result is a candidate target PSCell for a CHO with a candidate SCG, for example, the first fault information may include an indication relating to the measured adjacent cell included in the measurement result being a candidate target PSCell for a CHO with a candidate SCG.

[0228] In some examples, the first fault information may include an indication of whether the measured adjacent cell included in the measurement result is a candidate target PCell for a mere CHO, for example, the first fault information may include an indication relating to the measured adjacent cell included in the measurement result being a candidate target PCell for a mere CHO. In some examples, the first fault information may include an indication of whether the measured adjacent cell included in the measurement result is a candidate target PCell for a legacy CHO with an SCG, for example, the first fault information may include an indication relating to the measured adjacent cell included in the measurement result being a candidate target PCell for a legacy CHO with an SCG.

[0229] In some examples, the first failure information may include, for example, a list of the last configured candidate target PCells for the CHO with a candidate SCG that are not included in the measurement results (for example, one cell in the list of candidate target PCells may be represented by PLMN+CGI or PCI+ARFCN).

[0230] In some examples, the first failure information may include, for example, a list of the last configured candidate target PSCells for the CHO with a candidate SCG that are not included in the measurement results (for example, one cell in the list of candidate target PSCells may be represented by PLMN+CGI or PCI+ARFCN).

[0231] In some examples, the first failure information may include a list of the last configured candidate target PCells for CHO that are not included in the measurement results (for example, one cell in the list of candidate target PCells may be represented by PLMN+CGI or PCI+ARFCN).

[0232] In some examples, the first failure information may include, for example, a list of the last configured candidate target PCells for legacy CHOs with SCG that are not included in the measurement results (for example, one cell in the list of candidate target PCells may be represented by PLMN+CGI or PCI+ARFCN).

[0233] In some examples, the first failure information may include an indication of the failure type, or an indication that a simple CHO execution or a CHO execution with an SCG will fail. For example, in cases where both a simple CHO and a CHO with a candidate SCG are configured, or both a legacy CHO with an SCG and a CHO with a candidate SCG are configured, or where a simple CHO, a legacy CHO with an SCG, and a CHO with a candidate SCG are configured (especially when neither the CHO execution condition for a CHO with a candidate SCG nor the CPAC execution condition for a CHO with a candidate SCG is met), the first failure information may include an indication relating to the failure of a simple CHO or a legacy CHO with an SCG. For example, a new type for lastHO-Type may be introduced and may be included in the first failure information, for example, cho-onlyinchowithcandidateSCG or chowithSCGinchowithcandidateSCG. For example, a new 1-bit flag may be used as the indication.

[0234] As an addition or alternative, the UE230 may further transmit the first fault information to a receiving node, for example, a further RAN node serving the UE230 (such as a base station not shown in Figure 2). In some examples, the first fault information may be included in the RLF report.

[0235] Similarly, as described above, when a CHO with a candidate SCG cannot be triggered but the CHO execution conditions for a legacy CHO with an SCG are met, the legacy CHO with an SCG may be executed, for example, access to a second target PCell and its associated target PSCell, where the second target PCell satisfies the CHO execution conditions for the legacy CHO with an SCG. However, in some cases, a failure may occur within the legacy CHO with an SCG, i.e., the addition or modification of the PSCell to the target PSCell may fail, or an SCG failure may occur immediately after a successful execution of the legacy CHO with an SCG (for example, after a successful PSCell addition or modification).

[0236] In some implementations, the UE230 may store (or log) a second failure information. For example, the second failure information may relate to a failure occurring in a legacy CHO with an SCG, or, for example, to a failure when accessing a target PSCell related to a second target PCell. In some implementations, the second failure information may be further transmitted to a target MN, or to a further RAN node that is the serving RAN node of the UE230. In some implementations, the second failure information may be included in an RLF report or an SCG failure information message. In some exemplary embodiments, second failure information may be transmitted to source MN210 and / or a failure report may be transmitted to source SN and / or the failure report may be transmitted to target SN, source MN, or source SN, or target MN or target SN may perform MRO analysis or optimization, for example, source MN210 or source SN or target MN or target SN may analyze whether the parameters of the CPAC execution conditions for CHO with candidate SCG need to be optimized and / or whether the parameters of the CHO execution conditions for CHO with candidate SCG need to be optimized, and then source MN or source SN or target MN or target SN may perform the corresponding optimization based on the analysis.

[0237] In some implementations, the second failure information may include some information related to the CHO with the candidate SCG, and some information related to the legacy CHO with the SCG.

[0238] In some examples, the second failure information may include the source PSCell ID (i.e., the source PSCell ID) (for example, the ID may be represented by PLMN+CGI or PCI+ARFCN). For example, the source PSCell may be provided by source SN220.

[0239] In some examples, the second failure information may include the ID of the target PSCell (i.e., the target PSCell ID) (for example, the ID may be represented by PLMN+CGI or PCI+ARFCN). For example, the target PSCell may be the target PSCell related to the second target PCell described above.

[0240] In some examples, the second failure information may include, if any, the type of the first satisfied execution condition for the CHO with the candidate SCG. For example, the type may indicate that the first satisfied execution condition is a CHO execution condition for the CHO with the candidate SCG. For example, the type may indicate that the first satisfied execution condition is a CPAC execution condition for the CHO with the candidate SCG. For example, the type may be omitted, which indicates that neither the CPAC execution condition for the CHO with the candidate SCG nor the CHO execution condition for the CHO with the candidate SCG is satisfied.

[0241] In some cases, the type of the first satisfied execution condition for a CHO with a candidate SCG indicates that the first satisfied execution condition for a CHO with a candidate SCG belongs to one or more CHO execution conditions for a CHO with a candidate SCG, in other words, if the first satisfied execution condition for a CHO with a candidate SCG is a CHO execution condition for a CHO with a candidate SCG, the second failure information may further include one or more of the following: an ID indicating a candidate PCell and an ID indicating a candidate PSCell associated with the candidate PCell, the time length between the first time and the second time, the time length between the third time and the second time, the time length between the third time and the first time, the time length between the first time and the sixth time, the time length between the second time and the sixth time, or the time length between the third time and the sixth time. For example, it may include the ID of a candidate PCell that satisfies its associated CHO execution condition for a CHO with a candidate SCG. For example, it may include the ID of an associated candidate PSCell that does not satisfy its associated CPAC execution condition for a CHO with a candidate SCG. For example, the first time is the time when at least one CHO execution condition for a CHO alone is met, or at least one CHO execution condition for a CHO with an SCG is met. For example, the second time is the time when one of the first, third, or fourth configurations is received. For example, the third time is the time when one or more CHO execution conditions for a CHO with a candidate SCG are met. For example, the sixth time is the time when an SCG failure occurs, i.e., access to the target PSCell associated with the second target PCell fails, or when an SCG failure occurs immediately after successful access to the target PSCell (e.g., successful PSCell addition or modification to the target PSCell).

[0242] For example, if the type of first execution condition met for a CHO with a candidate SCG is a CHO execution condition for a CHO with a candidate SCG (i.e., the CHO execution condition for a CHO with a candidate SCG is met, but the CPAC execution condition for a CHO with a candidate SCG is not met), then the second failure information is: ■ The ID of the candidate target PCell (e.g., PLMN+CGI or PCI+ARFCN) or the associated CondReconfigId, and / or the CHO execution conditions for the CHO with the candidate SCG are met, but the associated CPAC execution conditions for the CHO with the candidate SCG are not met, the ID of the candidate target PSCell (e.g., PLMN+CGI or PCI+ARFCN) or the associated CondReconfigId, ■Time elapsed between the receipt of the most recent conditional reconfiguration and the SCG failure (for legacy CHOs with SCG and candidate SCGs, or for simple CHOs, legacy CHOs with SCGs, and candidate SCGs) (e.g., reuse existing IE, e.g., timeSCGFailure, to indicate time information), ■ The time elapsed between the fulfillment of the CHO execution conditions for a CHO with a candidate SCG and the receipt of the most recent conditional reconstruction (for legacy CHOs with SCGs and CHOs with candidate SCGs, or for simple CHOs, legacy CHOs with SCGs, and CHOs with candidate SCGs), ■The time elapsed between the fulfillment of the CHO execution conditions for a CHO with a candidate SCG and the fulfillment of the CHO execution conditions for a CHO with an SCG. ■The time elapsed between the fulfillment of the CHO execution conditions for CHOs accompanied by SCG and the SCG failure. ■The time elapsed between the fulfillment of the CHO execution conditions for a CHO with SCG and the receipt of the most recent conditional reconstruction (for legacy CHOs with SCG and CHOs with candidate SCGs, or for simple CHOs, legacy CHOs with SCGs, and CHOs with candidate SCGs), or ■This may include at least one of the time elapsed between the fulfillment of the CHO execution conditions for a CHO with a candidate SCG and the SCG failure.

[0243] Referring to Figure 6C, which shows an exemplary timing schematic diagram 630, it is assumed that t0 represents the time of reception of the most recent conditional configuration, which is the most recent of the time for reception of the first configuration and the time for reception of the fourth configuration. It is assumed that t1 represents the time when the CHO execution conditions for the CHO with candidate SCG are met. It is assumed that t2 represents the time when the CHO execution conditions for the legacy CHO with SCG are met. It is assumed that t3 represents the time when an SCG failure occurs in the legacy CHO with SCG, i.e., access to the target PSCell related to the second target PCell fails, or when an SCG failure occurs immediately after successful access to the target PSCell (e.g., successful PSCell addition or modification to the target PSCell).

[0244] As shown in Figure 6C, Ta may represent the time length between t0 and t1, Tb may represent the time length between t1 and t2, and Tc may represent the time length between t2 and t3. For example, the second failure information may include one or more of Ta, Tb, Tc, Ta+Tb, Tb+Tc, or Ta+Tb+Tc. For example, the IE TimeSinceSCGFailure may be reused to represent Ta+Tb+Tc. For example, a new IE may be used to represent each of Ta, Tb, Tc, Ta+Tb, or Tb+Tc.

[0245] In some cases, the type of the first satisfied execution condition for a CHO with a candidate SCG indicates that the first satisfied execution condition for a CHO with a candidate SCG belongs to one or more CPAC execution conditions for a CHO with a candidate SCG, in other words, if the first satisfied execution condition for a CHO with a candidate SCG is a CPAC execution condition for a CHO with a candidate SCG, the second failure information may further include one or more of the following: an ID indicating a candidate PCell and an ID indicating a candidate PSCell associated with the candidate PCell, the time length between the first time and the second time, the time length between the fourth time and the second time, the time length between the fourth time and the first time, the time length between the first time and the sixth time, the time length between the second time and the sixth time, or the time length between the fourth time and the sixth time. For example, it may include the ID of a candidate PCell that does not satisfy its associated CHO execution condition for a CHO with a candidate SCG. For example, it may include the ID of a candidate PSCell that satisfies the associated CPAC execution conditions for a CHO with a candidate SCG (and is associated with a candidate PCell that does not satisfy the associated CHO execution conditions for a CHO with a candidate SCG). For example, the first time is the time when at least one CHO execution condition for a simple CHO is met, or at least one CHO execution condition for a CHO with an SCG is met. For example, the second time is the time when one of the first, third, or fourth configurations is received. For example, the fourth time is the time when one or more CPAC execution conditions for a CHO with a candidate SCG are met. For example, the sixth time is the time when an SCG failure occurs, i.e., access to a target PSCell associated with a second target PCell fails, or when an SCG failure occurs immediately after successful access to a target PSCell (e.g., successful PSCell addition or modification to a target PSCell).

[0246] For example, if the type of first execution condition met for a CHO with a candidate SCG is the CPAC execution condition for a CHO with a candidate SCG (i.e., the CHO execution condition for a CHO with a candidate SCG is not met, but the CPAC execution condition for a CHO with a candidate SCG is met), then the second failure information is: ■ The ID of the candidate target PCell (e.g., PLMN+CGI or PCI+ARFCN) or the associated CondReconfigId, and / or the ID of the candidate target PSCell (e.g., PLMN+CGI or PCI+ARFCN) or the associated CondReconfigId, for a CHO with a candidate SCG where the CHO execution conditions are not met, but the CPAC execution conditions for a CHO with a candidate SCG are met, ■Time elapsed between the receipt of the most recent conditional reconfiguration and the SCG failure (for legacy CHOs with SCG and candidate SCGs, or for simple CHOs, legacy CHOs with SCGs, and candidate SCGs) (e.g., reuse existing IE, e.g., timeSCGFailure, to indicate time information), ■ The time elapsed between the fulfillment of the CPAC execution conditions for a CHO with a candidate SCG and the receipt of the most recent conditional reconfiguration (for legacy CHOs with SCGs and CHOs with candidate SCGs, or for CHOs with only SCGs, legacy CHOs with SCGs, and CHOs with candidate SCGs), ■The time elapsed between the fulfillment of the CPAC execution conditions for a CHO with a candidate SCG and the fulfillment of the CHO execution conditions for a CHO with an SCG. ■The time elapsed between the fulfillment of the CHO execution conditions for CHOs accompanied by SCG and the SCG failure. ■The time elapsed between the fulfillment of the CHO execution conditions for a CHO with SCG and the receipt of the most recent conditional reconstruction (for legacy CHOs with SCG and CHOs with candidate SCGs, or for simple CHOs, legacy CHOs with SCGs, and CHOs with candidate SCGs), or ■This may include at least one of the following time periods: the time elapsed between the fulfillment of the CPAC execution conditions for a CHO with a candidate SCG and the SCG failure.

[0247] Referring to Figure 6D, which shows an exemplary timing schematic diagram 640, it is assumed that t0 represents the time of reception of the most recent conditional configuration, which is the most recent of the time for reception of the first configuration and the time for reception of the fourth configuration. It is assumed that t11 ​​represents the time when the CPAC execution condition for the CHO with candidate SCG is met. It is assumed that t2 represents the time when the CHO execution condition for the legacy CHO with SCG is met. It is assumed that t3 represents the time when an SCG failure occurs in the legacy CHO with SCG, i.e., access to the target PSCell related to the second target PCell fails, or when an SCG failure occurs immediately after successful access to the target PSCell (e.g., successful PSCell addition or modification to the target PSCell).

[0248] As shown in Figure 6D, Ta1 may represent the time length between t0 and t11, Tb1 may represent the time length between t11 and t2, and Tc may represent the time length between t2 and t3. For example, the second failure information may include one or more of Ta1, Tb1, Tc, Ta1+Tb1, Tb1+Tc, or Ta1+Tb1+Tc. For example, the IE TimeSinceSCGFailure may be reused to represent Ta1+Tb1+Tc. For example, a new IE may be used to represent each of Ta1, Tb1, Tc, Ta1+Tb1, or Tb1+Tc.

[0249] In some examples, the second failure information may include the last received CHO execution condition for the CHO with the candidate SCG, e.g., a threshold for TTT or CondEvent A3 / A4 / A5. In some examples, the second failure information may include the last received CPAC execution condition for the CHO with the candidate SCG, e.g., a threshold for TTT or CondEvent B1 / A4.

[0250] In some examples, the second failure information may include, if any, the last received CHO execution condition for a legacy CHO with SCG, such as TTT or thresholds for CondEvent A3 / A4 / A5.

[0251] In some examples, the second fault information may include recent wireless measurement results from at least one adjacent cell. For example, at least one adjacent cell may include at least one adjacent PCell and / or at least one adjacent PSCell.

[0252] In some examples, the second fault information may include an indication of whether the measured adjacent cell included in the measurement results is a candidate target PCell for a CHO with a candidate SCG, for example, the second fault information may include an indication relating to the measured adjacent cell included in the measurement results being a candidate target PCell for a CHO with a candidate SCG. In some examples, the second fault information may include an indication of whether the measured adjacent cell included in the measurement results is a candidate target PSCell for a CHO with a candidate SCG, for example, the second fault information may include an indication relating to the measured adjacent cell included in the measurement results being a candidate target PSCell for a CHO with a candidate SCG.

[0253] In some examples, the second fault information may include an indication of whether the measured adjacent cell included in the measurement results is a candidate target PCell for a legacy CHO with SCG, for example, the second fault information may include an indication relating to the fact that the measured adjacent cell included in the measurement results is a candidate target PCell for a legacy CHO with SCG.

[0254] In some examples, the second failure information may include, for example, a list of the last configured candidate target PCells for the CHO with a candidate SCG that are not included in the measurement results (for example, one cell in the list of candidate target PCells may be represented by PLMN+CGI or PCI+ARFCN).

[0255] In some examples, the second failure information may include, for example, a list of the last configured candidate target PSCells for the CHO with a candidate SCG that are not included in the measurement results (for example, one cell in the list of candidate target PSCells may be represented by PLMN+CGI or PCI+ARFCN).

[0256] In some examples, the second failure information may include, for example, a list of the last configured candidate target PCells for legacy CHOs with SCG that are not included in the measurement results (for example, one cell in the list of candidate target PCells may be represented by PLMN+CGI or PCI+ARFCN).

[0257] In some examples, the second failure information may include an indication of the failure type, or that the execution of a CHO with an SCG has failed, or that an SCG failure has occurred within a CHO with an SCG. For example, in cases where both a legacy CHO with an SCG and a CHO with a candidate SCG are configured, or where a simple CHO, a legacy CHO with an SCG, and a CHO with a candidate SCG are configured (especially when neither the CHO execution conditions for a CHO with a candidate SCG nor the CPAC execution conditions for a CHO with a candidate SCG are met), the second failure information may include an indication relating to the failure of the legacy CHO with an SCG or that an SCG failure has occurred within a CHO with an SCG. For example, a new type may be introduced and included in the second failure information, for example, synchReconfigFailureinchowithSCGandchowithcandidateSCG. For example, a new 1-bit flag may be used as the indication.

[0258] As an addition or alternative, UE230 may further transmit second fault information to a receiving node, such as target MN215, or to any further RAN node serving UE230 (such as a base station not shown in Figure 2). In some examples, the second fault information may be included in an RLF report or SCG fault information message.

[0259] In some implementations, further MRO may be performed by, for example, the target MN215 or source MN210, which may refer to those described above, and this will not be repeated in this specification for the sake of brevity.

[0260] According to some exemplary embodiments of Figure 5, in cases where a CHO with a candidate SCG is not triggered, a simple CHO execution or a legacy CHO execution with an SCG may be performed.

[0261] It should be understood that the exemplary embodiments described above are for illustrative purposes only and without limitation, and that, for example, some of the information above may be combined, some may be omitted, and some may be modified, and that this disclosure does not limit these embodiments.

[0262] Figure 7 shows an example of a device 700 suitable for carrying out embodiments of the present disclosure. Device 700 may be an example of a source MN210, a source SN220, a target MN215, a target SN, or a UE230, as described herein. Device 700 may support wireless communication with a source MN210, a source SN220, a target MN215, a target SN, a UE230, or any combination thereof. Device 700 may include components for bidirectional communication, including components for transmitting and receiving communications, such as a processor 702, a memory 704, a transceiver 706, and optionally an I / O controller 708. These components may communicate electronically via one or more interfaces (e.g., buses), or may be coupled (e.g., operably, communicatively, functionally, electronically, electrically).

[0263] The processor 702, memory 704, transceiver 706, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the present disclosure as described herein. For example, the processor 702, memory 704, transceiver 706, or various combinations thereof or components thereof may support a method for performing one or more of the operations described herein.

[0264] In some implementations, the processor 702, memory 704, transceiver 706, or various combinations or components thereof, may be implemented in hardware (for example, in a communication management circuit configuration). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof that constitutes, or otherwise supports, means for performing the functions described herein. In some implementations, the processor 702 and the memory 704 coupled to the processor 702 may be configured to perform one or more of the functions described herein (for example, having the processor 702 execute instructions stored in memory 704).

[0265] For example, the processor 702 may support wireless communication in the device 700 in accordance with examples such as those disclosed herein. The processor 702 may be operable to support means for receiving from a first RAN node a first configuration comprising one or more CHO execution conditions for a CHO with a candidate SCG and one or more CPAC execution conditions for a CHO with a candidate SCG; means for receiving from the first RAN node a second configuration comprising at least one time threshold, wherein at least one time threshold is used to determine whether to store or report first information relating to a successful CHO procedure with a candidate SCG; and means for storing or reporting first information relating to a successful CHO procedure with a candidate SCG in accordance with the determination that at least one trigger condition relating to at least one time threshold is met. The processor 702 may be operable to support means for sending to the UE a first configuration comprising one or more CHO execution conditions for a CHO with a candidate SCG and one or more CPAC execution conditions for a CHO with a candidate SCG, and means for sending to the UE a second configuration comprising at least one time threshold, the at least one time threshold being used to determine whether first information relating to a successful CHO procedure with a candidate SCG should be stored or reported. The processor 702 may be operable to support means for receiving first or second information from the UE or a second RAN node, wherein the UE is configured with one or more CHO execution conditions for a CHO with a candidate SCG and one or more CPAC execution conditions for a CHO with a candidate SCG, and the second RAN node is a target SN or further RAN node, and means for performing MRO analysis based on the first or second information.The processor 702 may be operable to support means for determining time-related information comprising at least one last configured timer value for T310 or T312, or one of a fifth time threshold related to a T310 trigger condition for a source PSCell, or a sixth time threshold related to a T312 trigger condition for a source PSCell, and means for transmitting the time-related information to a source MN.

[0266] The 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, the processor 702 may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into the processor 702. The processor 702 may be configured to execute computer-readable instructions stored in memory (e.g., memory 704) to cause the device 700 to perform various functions of this disclosure.

[0267] Memory 704 may include random access memory (RAM) and read-only memory (ROM). Memory 704 may store computer-readable computer-executable code, which, when executed by processor 702, causes device 700 to perform various functions described herein. The code may be stored in a non-temporary computer-readable medium, such as system memory or another type of memory. In some implementations, the code does not have to be directly executable by processor 702, but may cause the computer to perform the functions described herein (for example, when compiled and executed). In some implementations, memory 704 may include a basic I / O system (BIOS) that can control basic hardware or software operations, such as interactions with peripheral components or peripheral devices.

[0268] The I / O controller 708 may manage input and output signals for device 700. The I / O controller 708 may also manage peripherals not integrated into device 700. In some implementations, the I / O controller 708 may represent physical connections or ports to external peripherals. In some implementations, the I / O controller 708 may utilize an operating system such as iOS®, ANDROID®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In some implementations, the I / O controller 708 may be implemented as part of a processor, such as processor 702. In some implementations, a user may interact with device 700 via the I / O controller 708 or via hardware components controlled by the I / O controller 708.

[0269] In some implementations, device 700 may include a single antenna 710. However, in some other implementations, device 700 may have two or more antennas 710 (i.e., multiple antennas), including multiple antenna panels or antenna arrays that may be capable of transmitting or receiving multiple wireless transmissions in parallel. Transceiver 706 may communicate bidirectionally via one or more antennas 710, a wired link, or a wireless link, as described herein. For example, transceiver 706 may represent a wireless transceiver and communicate bidirectionally with another wireless transceiver. Transceiver 706 may also include a modem for modulating packets and providing modulated packets to one or more antennas 710 for transmission, and for demodulating packets received from one or more antennas 710. Transceiver 706 may include one or more transmit chains, one or more receive chains, or a combination thereof.

[0270] The transmit chain may be configured to generate and transmit signals (e.g., control information, data, packets). The transmit chain may include at least one modulator for modulating data over a carrier signal to prepare the signal for transmission over a wireless medium. The 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 transmit chain may also include at least one power amplifier configured to amplify the signal to be modulated to an appropriate power level suitable for transmission over a wireless medium. The transmit chain may also include one or more antennas 710 for transmitting the amplified signal into the air or into the wireless medium.

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

[0272] Figure 8 shows an example of a processor 800 suitable for carrying out some embodiments of the present disclosure. The processor 800 may be an example of a processor configured to perform various operations as illustrated herein. The processor 800 may include a controller 802 configured to perform various operations as illustrated herein. The processor 800 may optionally include at least one memory 804, such as an L1 / L2 / L3 cache. In addition or alternatively, the processor 800 may optionally include one or more arithmetic logic units (ALUs) 806. One or more of these components may communicate electronically via one or more interfaces (e.g., buses), or may be coupled (e.g., operably, communicatively, functionally, electronically, electrically).

[0273] The processor 800 may be a processor chipset and may include a protocol stack (e.g., a software stack) that is executed by the processor chipset to perform various operations such as those described herein (e.g., receiving, acquiring, retrieving, transmitting, outputting, transferring, storing, determining, identifying, accessing, writing, reading). The processor chipset may include one or more cores, one or more caches (e.g., memory local to or contained within the processor chipset (e.g., processor 800), 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), and others).

[0274] The controller 802 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, fetching, transmitting, outputting, transferring, storing, determining, identifying, accessing, writing, reading) of the processor 800 in order to support the processor 800 to perform various operations according to examples as described herein. For example, the controller 802 may operate as a control unit of the processor 800 to generate control signals for managing the operations of various components of the processor 800. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating the timing of operations.

[0275] The controller 802 may be configured to fetch (e.g., obtain, fetch, receive) instructions from the memory 804 and determine subsequent instructions to be executed in order to support the processor 800 to perform various operations according to examples as described herein. The controller 802 may be configured to track the memory addresses of instructions related to the memory 804. The controller 802 may be configured to decode instructions to determine the operations to be performed and the operands involved. For example, the controller 802 may be configured to interpret instructions and determine control signals to be output to other components of the processor 800 in order to support the processor 800 to perform various operations according to examples as described herein. Additionally or alternatively, the controller 802 may be configured to manage the data flow within the processor 800. The controller 802 may be configured to control the transfer of data between registers, an arithmetic logic unit (ALU), and other functional units of the processor 800.

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

[0277] When executed by processor 800, memory 804 may store computer-readable computer-executable code that includes instructions to 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 the computer-readable instructions stored in memory 804 to cause processor 800 to perform the various functions. For example, processor 800 and / or controller 802 may be coupled 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, which may be individually or collectively configured to perform the various functions herein.

[0278] One or more ALU806s may be configured to support various operations, such as those described herein. In some implementations, one or more ALU806s may reside in or on a processor chipset (e.g., processor 800). In some other implementations, one or more ALU806s may reside outside the processor chipset (e.g., processor 800). One or more ALU806s may perform one or more calculations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU806s may receive input operands and operation codes that determine the operation to be performed. One or more ALU806s may be configured with various logic and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. As an addition or alternative, one or more ALU806s may support logical operations such as AND, OR, exclusive OR (XOR), inverted OR (NOR), and inverted AND (NAND), enabling one or more ALU806s to handle conditional operations, comparisons, and bitwise operations.

[0279] The processor 800 may support wireless communication as illustrated in this specification. The processor 800 may be configured to support, or operable to support, means for operation as described in some embodiments of this disclosure.

[0280] Figure 9 shows a flowchart of Method 900 performed by a UE according to an aspect of this disclosure. The operation of Method 900 may be performed by a device or its components as described herein. For example, the operation of Method 900 may be performed by a UE 230 as described in Figure 2. In some implementations, the device may execute a set of instructions for controlling the device's functional elements to perform the functions described. In addition or alternatively, the device may use dedicated hardware to perform aspects of the functions described.

[0281] In 910, the method may include receiving from a first RAN node a first configuration comprising one or more CHO execution conditions for a CHO with a candidate SCG and one or more CPAC execution conditions for a CHO with a candidate SCG. The operation of 910 may be performed according to examples such as those described herein. In some implementations, the operation of 910 may be performed by a UE230 as described with reference to Figure 2.

[0282] In 920, the method may include receiving a second configuration from a first RAN node, which has at least one time threshold, used to determine whether first information relating to a successful CHO procedure with a candidate SCG should be stored or reported. The operation of 920 may be performed according to examples such as those described herein. In some implementations, the operation of 920 may be performed by a UE230 as described with reference to Figure 2.

[0283] In 930, the method may include storing or reporting first information relating to a successful CHO procedure with a candidate SCG if at least one trigger condition related to at least one time threshold is met. The operation of 930 may be performed according to examples such as those described herein. In some implementations, the operation of 930 may be performed by UE230 as described with reference to Figure 2.

[0284] Figure 10 shows a flowchart of Method 1000 performed by a source MN according to an aspect of this disclosure. The operation of Method 1000 may be performed by a device or its components as described herein. For example, the operation of Method 1000 may be performed by a source MN210 as described in Figure 2. In some implementations, the device may execute a set of instructions for controlling the device's functional elements to perform the functions described. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the functions described.

[0285] In 1010, the method may include sending a first configuration to the UE comprising one or more CHO execution conditions for a CHO with a candidate SCG and one or more CPAC execution conditions for a CHO with a candidate SCG. The operation of 1010 may be performed according to examples such as those described herein. In some implementations, the operation of 1010 may be performed by a source MN210 as described with reference to Figure 2.

[0286] In 1020, the method may include sending a second configuration to the UE having at least one time threshold, the at least one time threshold used to determine whether to store or report first information relating to a successful CHO procedure with a candidate SCG. The operation of 1020 may be performed according to examples such as those described herein. In some implementations, the operation of 1020 may be performed by a source MN210 as described with reference to Figure 2.

[0287] Figure 11 shows a flowchart of Method 1100 performed by a target MN according to an aspect of this disclosure. The operation of Method 1100 may be performed by a device or its components as described herein. For example, the operation of Method 1100 may be performed by target MN215 in Figure 2. In some implementations, the device may execute a set of instructions for controlling the functional elements of the device to perform the function described. In addition or alternatively, the device may use dedicated hardware to perform aspects of the function described.

[0288] In 1110, the method may include receiving first or second information from a UE or a second RAN node, the UE being configured with one or more CHO execution conditions for a CHO with a candidate SCG and one or more CPAC execution conditions for a CHO with a candidate SCG, and the second RAN node being a target SN or a further RAN node. The operation of 1110 may be performed according to examples such as those described herein. In some implementations, the operation of 1110 may be performed by a target MN215 as described with reference to Figure 2.

[0289] In 1120, the method may include performing an MRO analysis based on the first or second piece of information. The operation of 1120 may be performed according to examples such as those described herein. In some implementations, the operation of 1120 may be performed by a target MN215 as described with reference to Figure 2.

[0290] Figure 12 shows a flowchart of Method 1200 performed by a source SN according to an aspect of this disclosure. The operation of Method 1200 may be performed by a device or its components as described herein. For example, the operation of Method 1200 may be performed by source SN220 in Figure 2. In some implementations, the device may execute a set of instructions for controlling the functional elements of the device to perform the function described. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the function described.

[0291] In 1210, the method may include determining time-related information comprising at least one last configured timer value for T310 or T312, or a fifth time threshold related to the T310 trigger condition for the source PSCell, or a sixth time threshold related to the T312 trigger condition for the source PSCell. The operation of 1210 may be performed according to examples such as those described herein. In some implementations, the operation of 1210 may be performed by a source SN220 as described with reference to Figure 2.

[0292] In 1220, the method may include sending time-related information to the source MN. The operation of 1220 may be performed according to examples such as those described herein. In some implementations, the operation of 1220 may be performed by the source SN220 as described with reference to Figure 2.

[0293] It should be noted that the methods described herein represent possible implementations, and that the operations and steps may be rearranged or modified in other ways, and that other implementations are possible. Furthermore, two or more embodiments of the methods may be combined.

[0294] The various exemplary blocks and components described in this disclosure may be implemented or executed using general-purpose processors, DSPs, ASICs, CPUs, FPGAs, or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, 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 working with a DSP core, or any other such configuration).

[0295] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted through one or more instructions or codes on a computer-readable medium. Other examples and implementations are within the scope of this disclosure and the accompanying claims. For example, due to the nature of the software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features implementing the functions may also be physically located in various locations, including being distributed so that parts of the functions are implemented in different physical locations.

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

[0297] As used herein, including in the claims, the article "a" before an element is unrestricted and is understood to refer to "at least one" of those elements or "one or more" of those elements. The terms "a", "at least one", "one or more", and "at least one of one or more" may be interchangeable. As used herein, including in the claims, "or" as used in a listing of items (e.g., a listing of items followed by phrases such as "at least one of ~" or "one or more of ~" or "one or both of ~") indicates an inclusive listing such that, for example, a listing 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). Also, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an exemplary step represented as "based on condition A" may be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" shall be construed in the same manner as the phrase "at least partially based on". Further, as used herein, including in the claims, a "set" may include one or more elements.

[0298] The description herein is provided to enable one of ordinary skill in the art to make and use the present disclosure. Various modifications to the present disclosure will be apparent to those of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, and the broadest scope consistent with the principles and novel features disclosed herein should be given.

Description of Reference Numerals

[0299] 100 Wireless communication system 102 Network entity 104 UE 106 Core network 108 Packet Data Network 110 Communication Link 112 Geographic Coverage Areas 114 Communication Link 116 Backhaul Link 118 Application Server 200 Communication Networks 210 RAN nodes, Source Master Node (MN) 215 RAN nodes, candidate target MN 220 RAN nodes, source secondary nodes (SN) 225 RAN nodes, candidate target SN 230 UE 700 devices 702 Processor 704 memory 706 Transceiver 708 I / O Controller 710 Antenna 800 processors 802 Controller 804 memory 806 Arithmetic Logic Unit (ALU)

Claims

1. User equipment (UE), At least one memory, The system comprises at least one processor coupled to the at least one memory, and the at least one processor provides the UE, Receiving from a first radio access network (RAN) node a first configuration comprising one or more CHO execution conditions for a conditional handover (CHO) with a candidate secondary cell group (SCG) and one or more conditional primary SCG cell (PSCell) addition and modification (CPAC) execution conditions for a CHO with a candidate SCG, Receiving a second configuration from the first RAN node, comprising at least one time threshold, wherein the at least one time threshold is used to determine whether to store or report first information relating to a successful CHO procedure with a candidate SCG, In accordance with the determination that at least one trigger condition related to the at least one time threshold is met, the first information relating to the successful CHO procedure with the candidate SCG is stored or reported. User equipment (UE) configured to perform a specific action.

2. The aforementioned at least one time threshold is A seventh time threshold is provided, relating to the duration between the time at which one or more CHO execution conditions for a CHO with a candidate SCG are met and the time at which one or more CPAC execution conditions for a CHO with a candidate SCG are met. The UE according to claim 1.

3. The aforementioned at least one processor provides the UE, The UE according to claim 2, further configured to determine that the at least one trigger condition associated with the at least one time threshold is met, upon determination that the duration between the time the one or more CHO execution conditions for the CHO with candidate SCG are met and the time the one or more CPAC execution conditions for the CHO with candidate SCG are met exceeds the seventh time threshold.

4. The first information relating to the successful CHO procedure with candidate SCG is, A cause value indicating that the first information relating to the successful CHO procedure with candidate SCG is stored as a result of satisfying the at least one trigger condition, The first type of execution condition that is satisfied for the CHO with candidate SCG, The duration between the two satisfied execution conditions for the CHO with the candidate SCG, A type indicating that it is a CHO procedure with a candidate SCG, The last received one or more CHO execution conditions for the CHO associated with the candidate SCG, The last received 1 or more CPAC execution conditions for the CHO associated with the candidate SCG, Recent wireless measurement results from at least one adjacent cell, An indication of whether the at least one adjacent cell belongs to the at least one candidate PCell configured for the CHO with the candidate SCG, An indication of whether the at least one adjacent cell belongs to the at least one candidate PSCell configured for the CHO with the candidate SCG, A list of candidate PCells configured for the CHO, which are not located in the at least one adjacent cell, or List of candidate PSCells configured for the CHO with candidate SCG, which are not located in the at least one adjacent cell. The UE according to claim 1, comprising one of the following.

5. The aforementioned at least one processor provides the UE, The system is further configured to transmit the first information relating to the successful CHO procedure with candidate SCGs to a second RAN node, the second RAN node being one of the target master node (MN), target secondary node (SN), or further RAN nodes. The UE according to claim 1.

6. The aforementioned at least one processor provides the UE, An instruction related to the availability of the first information is sent to the second RAN node. The second RAN node receives a request for the first information. The UE according to claim 5, further configured as follows.

7. The aforementioned at least one processor provides the UE, A third configuration having at least one CHO execution condition for a simple CHO is received from the first RAN node, and / or A fourth configuration, comprising at least one CHO execution condition for a CHO with SCG, is received from the first RAN node. The UE according to claim 1, further configured as follows.

8. The aforementioned at least one processor provides the UE, In accordance with the determination that one or more of the above CHO execution conditions for a CHO with a candidate SCG or one or more of the above CPAC execution conditions for a CHO with a candidate SCG are not met, and at least one of the above at least one CHO execution condition for a simple CHO is met, a simple CHO execution is performed toward a first target PCell that satisfies at least one of the above at least one CHO execution condition for a simple CHO, or In accordance with the determination that one or more of the aforementioned CHO execution conditions for a CHO with a candidate SCG or one or more of the aforementioned CPAC execution conditions for a CHO with a candidate SCG are not met, and at least one of the aforementioned at least one CHO execution condition for a CHO with an SCG is met, the execution of the CHO with an SCG is performed toward a second target PCell that satisfies at least one of the aforementioned at least one CHO execution condition for a CHO with an SCG, and a target PSCell associated with the second target PCell. The UE according to claim 7, further configured as follows.

9. The aforementioned at least one processor provides the UE, The first type of execution condition that is satisfied for the CHO with candidate SCG, The last received one or more CHO execution conditions for the CHO associated with the candidate SCG, The last received 1 or more CPAC execution conditions for the CHO associated with the candidate SCG, The last received CHO execution condition for the aforementioned simple CHO, The last received CHO execution condition for the CHO accompanied by SCG, Recent wireless measurement results from at least one adjacent cell, An indication of whether the at least one adjacent cell belongs to the at least one candidate PCell configured for the CHO with the candidate SCG, An indication of whether the at least one adjacent cell belongs to the at least one candidate PCell configured for the mere CHO, An indication of whether the at least one adjacent cell belongs to the at least one candidate PCell configured for the CHO with SCG, An indication of whether the at least one adjacent cell belongs to the at least one candidate PSCell configured for the CHO with the candidate SCG, A list of candidate PCells configured for the CHO, which are not located in at least one adjacent cell, and which include a candidate SCG. A list of candidate PSCells configured for the CHO, which are not located in the at least one adjacent cell, that include a candidate SCG. A list of candidate PCells configured for the mere CHO that are not located within the aforementioned at least one adjacent cell, or List of candidate PCells configured for the CHO with SCG, which are not located in the aforementioned at least one adjacent cell. Store a second piece of information that includes one of the following: The second piece of information described above is sent to the second RAN node. The UE according to claim 8, further configured such that the second RAN node is one of the target MN, target SN, or further RAN nodes.

10. The type of the first satisfied execution condition for the CHO with the candidate SCG indicates that the first satisfied execution condition for the CHO with the candidate SCG belongs to the one or more CHO execution conditions for the CHO with the candidate SCG, and the second information is An ID indicating a candidate PCell that satisfies one of the one or more CHO execution conditions for a CHO with a candidate SCG, and a ID indicating a candidate PSCell associated with the candidate PCell, The length of time between the first time and the second time, The length of time between the third time and the second time, or The time length between the third time and the first time It also has one of the following features: The first time is the time during which the at least one CHO execution condition for a CHO alone is met, or the at least one CHO execution condition for a CHO accompanied by an SCG is met. The second time is the time during which one of the first configuration, the third configuration, or the fourth configuration is received. The third time is the time during which one or more of the above-mentioned CHO execution conditions are met for a CHO associated with a candidate SCG. The UE according to claim 9.

11. The type of the first satisfied execution condition for the CHO with the candidate SCG indicates that the first satisfied execution condition for the CHO with the candidate SCG belongs to the one or more CPAC execution conditions for the CHO with the candidate SCG, and the second information is An ID indicating a candidate PCell and an ID indicating a candidate PSCell associated with a candidate PCell, wherein the candidate PCell does not satisfy one of the one or more CHO execution conditions for a CHO with a candidate SCG, and the candidate PSCell satisfies one of the one or more CPAC execution conditions for a CHO with a candidate SCG. The length of time between the first time and the second time, The length of time between the fourth time and the second time, or The time length between the fourth time and the first time It also has one of the following features: The first time is the time during which the at least one CHO execution condition for a CHO alone is met, or the at least one CHO execution condition for a CHO accompanied by an SCG is met. The second time is the time during which one of the first configuration, the third configuration, or the fourth configuration is received. The fourth time is the time during which one or more of the CPAC execution conditions for the CHO associated with the candidate SCG are met. The UE according to claim 9.

12. The aforementioned at least one processor provides the UE, The system is further configured to store first failure information in accordance with the determination that access to the first target PCell by a simple CHO execution or access to the second target PCell by a CHO execution with SCG fails, wherein the first failure information is: Source PCell ID, The ID of the first target PCell or the second target PCell, The first type of execution condition that is satisfied for the CHO with candidate SCG, The last received one or more CHO execution conditions for the CHO associated with the candidate SCG, The last received 1 or more CPAC execution conditions for the CHO associated with the candidate SCG, The last received CHO execution condition for the aforementioned simple CHO, The last received CHO execution condition for the CHO accompanied by SCG, Recent wireless measurement results from at least one adjacent cell, An indication of whether the at least one adjacent cell belongs to the at least one candidate PCell configured for the CHO with the candidate SCG, An indication of whether the at least one adjacent cell belongs to the at least one candidate PCell configured for the mere CHO, An indication of whether the at least one adjacent cell belongs to the at least one candidate PCell configured for the CHO with SCG, An indication of whether the at least one adjacent cell belongs to the at least one candidate PSCell configured for the CHO with the candidate SCG, A list of candidate PCells configured for the CHO, which are not located in at least one adjacent cell, and which include a candidate SCG. A list of candidate PSCells configured for the CHO, which are not located in the at least one adjacent cell, that include a candidate SCG. A list of candidate PCells configured for the mere CHO, which are not located within the aforementioned at least one adjacent cell, A list of candidate PCells configured for the CHO with SCG, which are not located in the aforementioned at least one adjacent cell, or Failure type, or an indication that the execution of a CHO with a simple CHO or an SCG fails. The UE according to claim 8, comprising one of the following.

13. The type of the first satisfied execution condition for the CHO with the candidate SCG indicates that the first satisfied execution condition for the CHO with the candidate SCG belongs to the one or more CHO execution conditions for the CHO with the candidate SCG, and the first failure information is An ID indicating a candidate PCell that satisfies one of the one or more CHO execution conditions for a CHO with a candidate SCG, and a ID indicating a candidate PSCell associated with the candidate PCell, The length of time between the first time and the second time, The time length between the third time and the second time, The time length between the third time and the first time, The time length between the first time and the fifth time, The time length between the second time and the fifth time, or The time length between the third time and the fifth time It also has one of the following features: The first time is the time during which the at least one CHO execution condition for a CHO alone is met, or the at least one CHO execution condition for a CHO accompanied by an SCG is met. The second time is the time during which one of the first configuration, the third configuration, or the fourth configuration is received. The third time is the time during which one or more of the above-mentioned CHO execution conditions are met for a CHO associated with a candidate SCG. The fifth time is the time at which the execution of the CHO alone or the execution of the CHO with SCG fails. The UE according to claim 12.

14. The type of the first satisfied execution condition for the CHO with the candidate SCG indicates that the first satisfied execution condition for the CHO with the candidate SCG belongs to the one or more CPAC execution conditions for the CHO with the candidate SCG, and the first failure information is An ID indicating a candidate PCell and an ID indicating a candidate PSCell associated with a candidate PCell, wherein the candidate PCell does not satisfy one of the one or more CHO execution conditions for a CHO with a candidate SCG, and the candidate PSCell satisfies one of the one or more CPAC execution conditions for a CHO with a candidate SCG. The length of time between the first time and the second time, The time length between the fourth time and the second time, The time length between the fourth time and the first time, The time length between the first time and the fifth time, The time length between the second time and the fifth time, or The time length between the fourth time and the fifth time It also has one of the following features: The first time is the time during which the at least one CHO execution condition for a CHO alone is met, or the at least one CHO execution condition for a CHO accompanied by an SCG is met. The second time is the time during which one of the first configuration, the third configuration, or the fourth configuration is received. The fourth time is the time during which one or more of the CPAC execution conditions for the CHO with the candidate SCG are met. The fifth time is the time at which the execution of the CHO alone or the execution of the CHO with SCG fails. The UE according to claim 12.

15. The aforementioned at least one processor provides the UE, The CHO with SCG is further configured to store second failure information in accordance with the decision that access to the target PSCell related to the second target PCell of the execution of the CHO with SCG fails, and the second failure information is Source PSCell ID, The ID of the target PSCell related to the second target PCell, The first type of execution condition that is satisfied for the CHO with candidate SCG, The last received one or more CHO execution conditions for the CHO associated with the candidate SCG, The last received 1 or more CPAC execution conditions for the CHO associated with the candidate SCG, The last received CHO execution condition for the CHO accompanied by SCG, Recent wireless measurement results from at least one adjacent cell, An indication of whether the at least one adjacent cell belongs to the at least one candidate PCell configured for the CHO with the candidate SCG, An indication of whether the at least one adjacent cell belongs to the at least one candidate PCell configured for the CHO with SCG, An indication of whether the at least one adjacent cell belongs to the at least one candidate PSCell configured for the CHO with the candidate SCG, A list of candidate PCells configured for the CHO, which are not located in at least one adjacent cell, and which include a candidate SCG. A list of candidate PSCells configured for the CHO, which are not located in the at least one adjacent cell, that include a candidate SCG. A list of candidate PCells configured for the CHO with SCG, which are not located in the aforementioned at least one adjacent cell, or Failure type, or an indication that the execution of a CHO with a simple CHO or an SCG fails. It has one of the following: The UE according to claim 8.

16. The type of the first satisfied execution condition for the CHO with the candidate SCG indicates that the first satisfied execution condition for the CHO with the candidate SCG belongs to the one or more CHO execution conditions for the CHO with the candidate SCG, and the second failure information is An ID indicating a candidate PCell and an ID of a candidate PSCell associated with a candidate PCell, wherein the candidate PCell satisfies one of the one or more CHO execution conditions for a CHO with a candidate SCG, and the candidate PSCell does not satisfy one of the one or more CPAC execution conditions for a CHO with a candidate SCG. The length of time between the first time and the second time, The time length between the third time and the second time, The time length between the third time and the first time, The time length between the first time and the sixth time, The time length between the second time and the sixth time, or The time length between the third time and the sixth time It also has one of the following features: The first time is the time during which at least one of the conditions for executing a CHO with an SCG is met. The second time is the time during which the first configuration or the fourth configuration is received. The third time is the time during which one or more of the above-mentioned CHO execution conditions are met for a CHO associated with a candidate SCG. The sixth time is the time during which the access to the target PSCell related to the second target PCell fails. The UE according to claim 15.

17. The type of the first satisfied execution condition for the CHO with the candidate SCG indicates that the first satisfied execution condition for the CHO with the candidate SCG belongs to the one or more CPAC execution conditions for the CHO with the candidate SCG, and the second failure information is An ID indicating a candidate PCell and an ID of a candidate PSCell associated with a candidate PCell, wherein the candidate PCell does not satisfy one of the one or more CHO execution conditions for a CHO with a candidate SCG, and the candidate PSCell satisfies one of the one or more CPAC execution conditions for a CHO with a candidate SCG. The length of time between the first time and the second time, The time length between the fourth time and the second time, The time length between the fourth time and the first time, The time length between the first time and the sixth time, The time length between the second time and the sixth time, or The time length between the fourth time and the sixth time It also has one of the following features: The first time is the time during which at least one of the conditions for executing a CHO with an SCG is met. The second time is the time during which the first configuration or the fourth configuration is received. The fourth time is the time during which one or more of the CPAC execution conditions for the CHO with the candidate SCG are met. The sixth time is the time during which the access to the target PSCell related to the second target PCell fails. The UE according to claim 15.

18. A first radio access network (RAN) node, At least one memory, The system comprises at least one processor coupled to the at least one memory, and the at least one processor is connected to the first RAN node. A first configuration comprising one or more CHO execution conditions for a conditional handover (CHO) with a candidate secondary cell group (SCG) and one or more conditional primary SCG cell (PSCell) addition and modification (CPAC) execution conditions for a CHO with a candidate SCG is transmitted to the user equipment (UE), A second configuration having at least one time threshold is sent to the UE. A first radio access network (RAN) node is configured such that the at least one time threshold is used to determine whether to store or report first information relating to a successful CHO procedure with a candidate SCG.

19. The target master node (MN) is At least one memory, The system comprises at least one processor coupled to the at least one memory, and the at least one processor provides the target MN, Receiving first or second information from a user device (UE) or a second radio access network (RAN) node, wherein the UE is configured with one or more CHO execution conditions for a conditional handover (CHO) with a candidate secondary cell group (SCG) and one or more conditional primary SCG cell (PSCell) addition and modification (CPAC) execution conditions for a CHO with a candidate SCG, and the second RAN node is a target secondary node (SN) or another RAN node. Performing Mobility Robustness Optimization (MRO) analysis based on the first or second information and A target master node (MN) configured to perform this action.

20. Source secondary node (SN), At least one memory, The system comprises at least one processor coupled to the at least one memory, and the at least one processor provides the source SN, The last configured timer value for T310 or T312, or A fifth time threshold related to the T310 trigger condition for the source PSCell, or The sixth time threshold related to the T312 trigger condition for the source PSCell. Determine time-related information that includes one of the following: The aforementioned time-related information is sent to the source master node (MN). A source secondary node (SN) configured in this way.

Images