Devices, methods, apparatuses, and computer-readable media for mobility robustness optimization
By coordinating the execution conditions for conditional handover and the addition or modification of conditional primary and secondary cells in 5G networks, the problem of radio link failure caused by dense cell deployment is identified and adapted, thus improving mobility robustness and network stability.
Patent Information
- Application Number
- CN202580029539.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2024-04-26
- Filing Date
- 2025-03-03
- Publication Date
- 2026-11-17
AI Technical Summary
In 5G networks, due to radio link failures (RLF) caused by dense cell deployment, existing technologies cannot effectively distinguish and resolve the delay and interference issues in the execution conditions of conditional handover (CHO) and conditional primary/secondary cell addition or alteration (CPAC), leading to difficulties in mobility robustness optimization (MRO).
A Mobility Robustness Optimization (MRO) solution is provided, which identifies which of the CHO and CPAC execution conditions is causing the problem by coordinating between the UE and network nodes, recording and reporting failure information, and adapting the conditions based on the failure report to ensure the coordinated configuration of CHO and CPAC conditions and reduce RLF.
It improves the robustness of CHO and CPAC processes, reduces radio link failures, enhances network mobility and stability, and reduces network signaling overhead by optimizing condition configuration through machine learning models.
Smart Images

Figure CN123125953A_ABST
Abstract
Description
Technical Field
[0001] The various example embodiments described herein relate generally to communication technologies, and more specifically to devices, methods, apparatuses, and computer-readable media for mobility robustness optimization during conditional handover (CHO) processes utilizing candidate secondary cell groups (SCGs). Background Technology
[0002] Some abbreviations that may be found in the instruction manual and / or accompanying drawings are defined here as follows: CHO condition switching CPA Conditions for Primary and Secondary Communities CPAC conditions for adding or changing primary and secondary cells CPC conditions for changes in primary and secondary communities MCG Main Cell Group MN master node MR-DC Multi-Wireless Dual-Connection MRO Mobility Robustness Optimization OAM Operations Management and Maintenance PCell main cell PSCell Primary and Secondary Communities RAN (Radio Access Network) RLF radio link failure RRC Radio Resource Control SCell Auxiliary Community SCG Auxiliary Community Group SN auxiliary node UE User Equipment The large-scale deployment of dense small cells for 5G networks will enhance coverage and capacity, but on the other hand, it will increase the handover probability, potentially leading to radio link failure (RLF). Therefore, mobility robustness optimization (MRO) solutions are being investigated for mobility frameworks including conditional handover (CHO) with (multiple) candidate secondary cell groups (SCGs) to ensure reliable and stable communication during the mobility of mobile users. Summary of the Invention
[0003] The following provides a brief overview of exemplary embodiments to offer a basic understanding of some aspects of the various embodiments. It should be noted that the content of this invention is not intended to identify key features of essential elements or define the scope of the embodiments, and its sole purpose is to introduce some concepts in a simplified form as a prelude to the more detailed description provided below.
[0004] In a first aspect, an example embodiment of an apparatus is provided. The apparatus may include at least one processor and at least one memory. The at least one memory may store instructions that, when executed by the at least one processor, cause the apparatus to at least: receive a configuration message from a first network node by a terminal device, the configuration message including at least one condition for conditional handover and at least one condition for cell addition or modification; evaluate whether the at least one condition for conditional handover and the at least one condition for cell addition or modification are satisfied; detect a connection failure between the terminal device and the first network node before both at least one of the above-mentioned conditions are satisfied; establish a radio connection with a second network node in response to the detected radio link failure; and send a failure report to the second network node indicating that the radio link failure occurred before both at least one of the above-mentioned conditions were satisfied.
[0005] In a second aspect, an example embodiment of an apparatus is provided. The apparatus may include at least one processor and at least one memory. The at least one memory stores instructions that, when executed by the at least one processor, cause the apparatus to at least: establish a radio connection with a terminal device by a second network node; receive a failure report from the terminal device, the failure report indicating a radio link failure with a first network node that occurred when at least one of a condition for conditional handover and at least one condition for cell addition or modification was not met; and perform one of the following: send the failure report to an operations management and maintenance entity; send the failure report to the first network node; or, if the at least one condition for cell addition or modification is determined by the second network node and is not met when the radio link failure occurred, determine adaptation information for the at least one condition for cell addition or modification based on the failure report.
[0006] In a third aspect, an example embodiment of an apparatus is provided. The apparatus may include at least one processor and at least one memory. The at least one memory may store instructions that, when executed by the at least one processor, cause the apparatus to at least: send a configuration message from a first network node to a terminal device, the configuration message including at least one condition for conditional handover and at least one condition for cell addition or modification; receive a failure report from a second network device indicating a radio link failure between the terminal device and the first network node when at least one of the at least one condition for conditional handover and the at least one condition for cell addition or modification is not met; and perform one of the following: send the failure report to an operations management and maintenance entity; or, if the failure report indicates that the at least one condition for conditional handover is not met, determine adaptation information for the at least one condition for conditional handover.
[0007] In a fourth aspect, an example embodiment of an apparatus is provided. The apparatus may include at least one processor and at least one memory. The at least one memory may store instructions that, when executed by the at least one processor, cause the apparatus to at least: receive a failure report from a first network node or a second network node by an operations management and maintenance entity, the failure report indicating a radio link failure between a terminal device and the first network node when at least one of at least one condition for handover and at least one condition for cell addition or modification is not met; determine unmet adaptation information for the at least one condition for handover or the at least one condition for cell addition or modification; and, if the adaptation information is determined for the at least one condition for handover that is not met, send the adaptation information to (i) the first network node, (ii) the second network node, or (iii) the first network node or the second network node from which the failure report is received, if the adaptation information is determined for the at least one condition for cell addition or modification that is not met.
[0008] Example embodiments of methods, apparatuses and computer-readable media are also provided, which generally correspond to the example embodiments described above, and for convenience, repeated descriptions thereof are omitted herein.
[0009] Other features and advantages of exemplary embodiments of this disclosure will also become apparent when read in conjunction with the accompanying drawings, which illustrate the principles of exemplary embodiments of this disclosure by way of example. Attached Figure Description
[0010] Some exemplary embodiments will now be described by way of non-limiting example with reference to the accompanying drawings.
[0011] Figure 1 This is a schematic diagram illustrating an example communication network.
[0012] Figure 2 This is a schematic message flow diagram illustrating an example process.
[0013] Figure 3 This is a schematic message flow diagram illustrating another example process.
[0014] Figure 4 This is a schematic message flow diagram illustrating another example process.
[0015] Figure 5 This is a schematic message flow diagram illustrating another example process.
[0016] Figure 6 This is a schematic message flow diagram illustrating another example process.
[0017] Figure 7 This is a schematic message flow diagram illustrating another example process.
[0018] Figure 8 This is a schematic flowchart illustrating an example method.
[0019] Figure 9 This is a schematic flowchart illustrating another example method.
[0020] Figure 10 This is a schematic flowchart illustrating another example method.
[0021] Figure 11 This is a schematic flowchart illustrating another example method.
[0022] Figure 12 This is a schematic flowchart illustrating another example method.
[0023] Figure 13 This is a schematic flowchart illustrating another example method.
[0024] Figure 14 This is a schematic flowchart illustrating another example method.
[0025] Figure 15 This is a schematic flowchart illustrating another example method.
[0026] Figure 16 This is a schematic block diagram illustrating an exemplary device.
[0027] Figure 17 This is a schematic block diagram illustrating another example device.
[0028] Figure 18 This is a schematic block diagram illustrating another example device.
[0029] Figure 19 This is a schematic block diagram illustrating another example device.
[0030] Figure 20 This is a schematic block diagram illustrating another example device.
[0031] Figure 21 This is a schematic block diagram illustrating another example device.
[0032] Figure 22 This is a schematic block diagram illustrating another example device.
[0033] Figure 23 This is a schematic block diagram illustrating another example device.
[0034] Figure 24A , Figure 24B and Figure 24CThis is a schematic block diagram illustrating an example device.
[0035] In all the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Repeated descriptions of the same elements will be omitted. Detailed Implementation
[0036] In the following description, some exemplary embodiments are described in detail with reference to the accompanying drawings. Specific details are included in the description for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known circuits, technologies, and components are shown in block diagram form to avoid obscuring the described concepts and features.
[0037] In the following description, some exemplary embodiments are described in detail with reference to the accompanying drawings. Specific details are included in the description for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known circuits, technologies, and components are shown in block diagram form to avoid obscuring the described concepts and features.
[0038] Figure 1 A schematic diagram of an example communication network 100 in which some example embodiments of the present disclosure may be implemented is shown. The communication network 100 may be a wireless, mobile, or cellular communication network. Reference Figure 1 The communication network 100 may include two domains: a radio access network (RAN) 120 and a core network (CN) 130. RAN 120 may include multiple base stations (BS) (shown as BS120A and BS120B) to provide network access for multiple user equipment (UE) 110 (only one shown). Each base station 120A, 120B may provide communication coverage for a specific geographical area (also called a cell). It should be understood that the term "cell" may refer to the coverage area of a base station or a subsystem of base stations serving that coverage area, depending on the context in which the term is used.
[0039] Core network 130 may include numerous network functions (NFs) (not shown) to provide a variety of functionalities. For example, it may provide access control to ensure that UEs 110 are authenticated for the services they are using, route telephone calls over the Public Switched Telephone Network (PSTN), connect UEs 110 to data networks (e.g., the Internet), and enable operators to charge for call and data usage. Core network 130 may also control the network by enabling handover when a UE moves from cell coverage provided by a base station to another cell coverage provided by the same or a different base station. In some example embodiments, core network 130 may be deployed in a cloud, such as a public cloud, private cloud, or hybrid cloud.
[0040] UE110 can be configured to operate in dual connectivity (DC) mode. In DC mode, UE110 connects to two base stations, for example, as shown below. Figure 1 The diagram shows a first base station 120A and a second base station 120B. Assume that the first base station 120A acts as the primary node (MN) of UE110, and the second base station 120B acts as the secondary node (SN) of UE110. MN120A has a Radio Resource Control (RRC) connection with UE110 and provides both Control Plane (CP) and User Plane (UP) connections to the core network 130. SN120B provides additional resources to UE110, but it does not provide a CP connection from UE110 to the core network 130. UE110 can simultaneously receive and transmit data from the serving cells of MN120A and SN120B on multiple component carriers. The serving cell of MN120A can be referred to as the Primary Cell Group (MCG), which includes a primary cell (PCell) 121 and one or more optional secondary cells (SCells) 122. PCell 121 is used to initiate the initial access of UE110 to network 100, and it serves as the primary connection point for UE110. UE110 aggregates PCell121 and one or more SCell122 via carrier aggregation (CA). The serving cell of SN120B can be referred to as a secondary cell group (SCG), which includes a primary secondary cell (PSCell) 123 and one or more optional secondary cells (SCells) 124. Similarly, PSCell123 is used to initiate initial access under the SCG, and it aggregates with one or more SCells 124 via carrier aggregation. Dual connectivity and carrier aggregation technologies enable UE110 to combine resources from multiple cells or carriers, thereby achieving higher data rates. In the case of multi-radio dual connectivity (MR-DC), one of MN120A and SN120B can be a 5G New Radio (NR) base station, and the other can be an E-UTRA base station or an NR base station. UE110 can also operate in CA mode without dual connectivity.
[0041] When UE110 moves from one cell to another, a handover procedure can be performed to ensure reliable and stable communication between UE110 and the network. During the Conditional Handover (CHO) process, UE110 can evaluate certain execution conditions and decide to perform the handover when the conditions are met. A CHO with an SN or a CHO with a candidate SCG configuration can be provided to UE110, which may include a CHO configuration for PCell change (also known as an MCG configuration), a Conditional PSCell Addition or Change (CPAC) configuration for PSCell addition or change (also known as an SCG configuration), and associated execution conditions. The CPAC configuration may include, for example, a Conditional PSCell Addition (CPA) configuration and / or a Conditional PSCell Change (CPC) configuration. Upon receiving the configuration, UE110 can begin evaluating the execution conditions of the candidate PCell and PSCell. In some cases, the CHO in MR-DC may be limited to scenarios where the target MN can prepare a single target PSCell (under the control of the SN), and the execution conditions of the candidate PCell and PSCell are not bound to each other. When the associated execution conditions are met, UE110 can independently execute PCell changes or PSCell additions or changes. In other words, CPAC execution conditions will not affect CHO execution, and CHO execution conditions will not affect CPAC execution.
[0042] In some cases, the Choice of Health (CHO) in MR-DC can be extended to scenarios where the target MN can prepare multiple candidate PSCells for the same candidate PCell. This enhances the usefulness of CHOs in MR-DC features where the UE may need to access different candidate PSCells when a CHO needs to be executed. In cases where multiple candidate PSCells are associated with a candidate PCell, the CHO with candidate SCG configurations provided from the network to the UE110 can include multiple CHO and CPAC configurations for the same candidate PCell and different candidate PSCells. That is, each CHO and CPAC configuration contains one CHO / MCG configuration for the same candidate PCell and one CPAC / SCG configuration for different candidate PSCells, along with associated execution conditions. The CHO and CPAC execution conditions associated with a CHO and CPAC configuration are bound together and will be evaluated at the UE110. If one of the CHO and CPAC execution conditions is met but the other is not, the UE110 will continue to evaluate both the CHO and CPAC execution conditions. In other words, UE110 will not perform PCell changes and PSCell additions or changes until both the CHO and CPAC execution conditions are met. Therefore, the CHO and CPAC execution conditions should be set in a way that they will coordinate with each other, i.e., one condition does not necessarily prevent the other, so that it does not prevent the UE from performing a handover unnecessarily.
[0043] When CHO and CPAC execution conditions are independent of each other, the network can adapt the CHO and CPAC execution conditions by examining failure information. For example, if a CHO execution fails due to an incorrect CHO execution condition configuration, the network can learn from the failure information what error occurred in the CHO execution condition and adapt the CHO execution condition to reduce failures. CHO failure information will not indicate the status of CPAC execution conditions because CPAC execution conditions do not affect CHO execution. As another example, if a CPAC execution fails due to an incorrect CPAC execution condition configuration, the network can learn from the failure information what error occurred in the CPAC execution condition and adapt the CPAC execution condition to reduce failures. CPAC failure information will not indicate the status of CHO execution conditions because CHO execution conditions do not affect CPAC execution.
[0044] When a UE is configured with CHO and CPAC execution conditions that are bound to each other, CHO and CPAC execution may be delayed if one of the execution conditions is not properly configured, because, as mentioned above, the UE should only execute CHO and CPAC when both conditions are met. This delay may cause the UE to suffer severe interference from the target PCell of the target MCG or the target PSCell of the target SCG. If CHO and CPAC execution is delayed long enough, the UE will experience radio link failure on either the source primary node link (also known as the MCG link) or the source secondary node link (also known as the SCG link). However, the network cannot identify which of the CHO and CPAC execution conditions is suboptimal, erroneous, or inappropriate, because the UE only executes CHO and CPAC when both execution conditions are met. If one of the CHO and CPAC execution conditions is not properly configured, the entire CHO and CPAC execution will be delayed because the CHO and CPAC configuration cannot be partially executed. Delayed execution due to unmet execution conditions can make the UE vulnerable to interference from the target PCell or PSCell, leading to interruptions and consequently, Radio Link Failure (RLF) on the UE side. Currently, after the UE re-establishes its radio connection with the network, there is no mechanism to identify the cause of the RLF (i.e., whether the RLF was caused by a CHO execution condition or a CPAC execution condition). For example, if an MCGRLF is caused by an inappropriate CPAC execution condition, the RLF report only contains CHO-related information, but the CPAC condition status is unknown. If an SCG failure is caused by an incorrect CHO execution condition, the SCG failure information only contains CPAC-related information, but the CHO condition status is unknown. Therefore, when a CHO and CPAC configuration including combined CHO and CPAC execution conditions is configured, the network cannot resolve the problem because it does not know which of the CHO and CPAC execution conditions caused the problem.
[0045] This disclosure provides example embodiments of a mobility robustness optimization (MRO) solution for combined CHO and CPAC mobility. The MRO solution can identify which of the CHO and CPAC execution conditions caused the mobility robustness problem, i.e., MCG failure or SCG failure, before the CHO and CPAC are successfully executed. In some example embodiments, the UE can record in various reports which execution condition(s) were not met and be directed to a situation-specific problem, allowing the network to know from the UE reports whether the failure was caused by the CHO execution condition, CPAC execution, or neither (e.g., by a coverage hole). The network can then determine adaptation information for the problematic execution condition. Condition adaptation can be implemented centrally (e.g., at an Operations Management and Maintenance (OAM) entity) or distributedly (e.g., at the base station that determined the problematic execution condition). Some example embodiments also propose new triggers for failure reporting within the context of mutually bound CHO and CPAC and define UE behavior when configuring failure reporting.
[0046] Figure 2 Example procedure 200 is shown for adapting combined CHO and CPAC execution conditions in CHO and CPAC configurations.
[0047] like Figure 2 As shown, the source primary node (S-MN) 120A can initiate a conditional handover preparation process for UE 110 by sending a handover (HO) request message to one or more potential / candidate target primary nodes (T-MNs), including T-MN 120C, at point 210. Assume UE 110 is operating in dual connectivity (DC) mode, connected to S-MN 120A and source secondary node (S-MN) 120B. S-MN 120A can determine one or more candidate T-MNs for UE 110 based on measurement reports received from UE 110 and send handover requests to the candidate T-MNs. In some example embodiments, the handover request may indicate the maximum number of conditional reconfigurations that candidate T-MN 120C can prepare for UE 110.
[0048] Upon receiving a handover request, the T-MN120C can decide to prepare a CHO and CPAC configuration for UE110, also known as a CHO with candidate SCG configuration, and send an SN add request at 212 to one or more potential / candidate target secondary nodes (T-SNs), including the T-SN120D. The SN add request may include CHO-related information (e.g., source MN identifier (ID) and UEID in the source MN) in the source MN to indicate that the SN add preparation process is triggered relative to a conditional handover and to enable candidate SNs to identify requests associated with the same UE. The T-MN120C may indicate in the SN add request one or more candidate PSCells recommended by the T-MN120C via recent measurements for the T-SN120D to select and configure candidate SCG cells, and the maximum number of candidate PSCells that the T-SN120D can prepare for UE110.
[0049] At 214, the T-SN120D can respond to the T-MN120C using an SN Add Request Confirmation message. The SN Add Request Confirmation message may include the (multiple) PSCells to be prepared (taking into account the maximum number indicated by the T-MN120C) and a list of additional SCGSCells for each prepared PSCell.
[0050] At 216, T-MN120C can determine CHO and CPAC configurations that include MCG configurations (also known as CHO configurations) and SCG configurations (also known as CPAC configurations) bound to each other. The MCG configuration is determined at T-MN120C and indicates candidate PCells and one or more MCGSCells optionally prepared at T-MN120C. At 214, an SCG configuration is received from T-SN120D, and the SCG configuration indicates candidate PSCells and one or more SCGSCells optionally prepared at T-SN120D. In some example embodiments, T-MN120C can determine multiple CHO and CPAC configurations, each configuration including a pair of MCG / CHO configurations and SCG / CPAC configurations. For example, T-MN120C can prepare multiple candidate PCells for UE110, and for each PCell, multiple PSCells can be prepared at T-SN120D and / or other potential T-SNs.
[0051] The T-MN120C can also determine at 216 at at least one CPAC execution condition (or simply CPAC condition) for each SCG configuration or specifically for a target PSCell within an SCG configuration. In some example embodiments, the T-MN120C can determine a dual-event (e.g., events A3 and A5) execution condition for an SCG configuration, meaning that both events must be satisfied simultaneously to trigger CPAC to the target PSCell.
[0052] Optionally, the T-MN120C can also determine the failure reporting configuration for UE110 at 216, specifying the content and / or triggering criteria of the failure report. In the event that UE110 encounters an MCG or SCG link failure before CHO and CPAC are triggered, a failure report can be sent from UE110, as will be described in detail below. In some example embodiments, the failure reporting configuration can be determined by the S-MN120A, or alternatively predefined at UE110.
[0053] Then, at 218, the T-MN120C can send a handover request confirmation message to the S-MN120A. The handover request confirmation message may contain one or more CHO and CPAC configurations, each configuration including an MCG / CHO configuration, an SCG / CPAC configuration, and CPAC execution conditions for the SCG / CPAC configuration. The confirmation message may also include a failure reporting configuration determined at the T-MN120C. In some example embodiments, the failure reporting configuration may be sent to the S-MN120A via a separate message. It should be understood that the S-MN120A may receive handover request confirmation messages from multiple potential / candidate T-MNs.
[0054] In response to the switch request confirmation message, the S-MN120A can determine at 220 at at least one CHO execution condition (or simply CHO condition) for each MCG / CHO configuration (or precisely the target PCell indicated in the MCG configuration). In some example embodiments, the S-MN120A can determine a dual-event (e.g., events A3 and A5) execution condition for the MCG configuration, meaning that both events must be satisfied simultaneously to trigger a CHO to the target PCell. It should be understood that the CHO execution condition and the corresponding CPAC execution condition are determined in a way that they will coordinate with each other; that is, one condition does not necessarily block the other.
[0055] In some example embodiments, if the T-MN120C does not determine the failure reporting configuration at 216, the S-MN120A can determine the failure reporting configuration at 220. In some other example embodiments, the failure reporting configuration can be predefined at UE110, and neither the T-MN120C nor the S-MN120A needs to determine the failure reporting configuration for UE110. In some other example embodiments, the failure reporting configuration can be partially determined at the T-MN120C and / or the S-MN120A, and the remaining portion can be predefined at UE110.
[0056] At position 222, the S-MN120A can send an RRC reconfiguration message to the UE110 containing one or more CHO and CPAC configurations, and optionally a failure reporting configuration. Each of the one or more CHO and CPAC configurations may include an MCG / CHO configuration, an SCG / CPAC configuration, at least one CHO execution condition, and at least one CPAC execution condition. As described above, the CHO execution conditions(s) and CPAC execution conditions(s) contained in each CHO and CPAC configuration are bound together such that they must all be satisfied to trigger the execution of the CHO and CPAC based on the CHO and CPAC configurations. It is assumed here that the UE110 is not provided and configured with a CHO-only configuration or has a CHO with a candidate SCG configuration including independent CHO and CPAC execution conditions. If UE110 is configured with a CHO-only configuration or a CHO with a candidate SCG configuration including a standalone CHO and CPAC execution conditions, and the CHO execution conditions used for the CHO and CPAC configuration are also used for the CHO-only configuration or the CHO with a candidate SCG configuration, then when the CHO execution conditions are met and the corresponding CPAC execution conditions are not met, UE110 will trigger a PCell change based on the CHO-only configuration or the CHO with a candidate SCG configuration, without waiting for the CPAC execution conditions to be met.
[0057] At 224, UE110 can store the received configuration and respond to S-MN120A using the RRC reconfiguration completion message.
[0058] Upon receiving the CHO and CPAC configurations, UE110 can begin evaluating whether the CHO and CPAC execution conditions are met at point 226. For example, UE110 can evaluate the CHO execution conditions based on measurements of the target / candidate PCell and optionally based on measurements of the source / serving PCell, and evaluate the CPAC execution conditions based on measurements of the target / candidate PSCell and optionally based on measurements of the source / serving PSCell. If UE110 determines that one of the CHO and CPAC execution conditions is met while the other is not, as described above, UE110 will not execute the CHO and CPAC, and the execution of the CHO and CPAC will be delayed due to the unmet conditions.
[0059] At 228, UE110 may experience / detect an interruption of the radio connection with S-MN120A. In response to this interruption, UE110 may start a Radio Link Failure (RLF) timer T310 for the S-MN link. The interruption may be caused by link quality degradation between UE110 and S-MN120A and / or interference from T-MN120C when UE110 moves away from S-MN120A. In some other example embodiments, either the CHO or CPAC execution condition may be satisfied first, and then UE110 may experience an interruption. In other examples, UE110 may experience an interruption first, and then either the CHO or CPAC execution condition may be satisfied. In other words, when an interruption occurs, neither the CHO nor the CPAC execution condition may be satisfied.
[0060] If neither the S-MN link is restored nor the CHO and CPAC execution conditions are met to trigger CHO and CPAC execution before the RLF timer T310 for the S-MN link expires, UE110 may declare an RLF for the S-MN link at 230. In some example embodiments, UE110 may also declare an RLF for the S-MN link for other reasons. Three scenarios for S-MN RLF are listed below: - Scenario 1: When configuring CHO and CPAC, S-MN(MCG)RLF: • Case 1A: When the CHO execution condition is met but the CPAC execution condition is not met, the UE experiences an RLF with the S-MN due to interference from the T-MN; • Case 1B: When the CPAC execution condition is met but the CHO execution condition is not met, the UE experiences RLF with the S-MN due to the low link quality with the S-MN (e.g., reference signal received power, RSRP) (e.g., S-MN coverage hole). • Case 1C: When neither the CHO execution condition nor the CPAC execution condition is met, the UE experiences an RLF with the S-MN due to interference from the T-MN and / or low link quality with the S-MN.
[0061] After declaring an RLF, UE110 can trigger a failure report if the criteria for triggering a failure report are met. As mentioned above, the criteria for triggering a failure report can be received from S-MN120A at 222 or predefined at UE110. In some example embodiments, the criteria for triggering a failure report may include the failure to meet at least one of the CHO execution condition and the CPAC execution condition at the time of the RLF. In some other example embodiments, the criteria for triggering a failure report may include the failure to meet one of the CHO and CPAC execution conditions at the time of the RLF, and the other condition being met. Figure 2 In the example shown, it is assumed that the failure report triggering criteria are met, and UE110 triggers a failure report at 232.
[0062] In some example embodiments, if an execution condition is met according to the relevant measurements, but the trigger time to trigger (TTT) timer for that condition is still running, then UE110 will not trigger CHO and CPAC execution. Therefore, the reference to unmet conditions covers scenarios where the condition is not met and the TTT timer associated with that condition is not running (i.e., the timer value is zero), as well as scenarios where the condition is met according to the measurements but the TTT timer associated with that condition is still running.
[0063] At point 232, UE110 can create a failure report and record relevant failure information in the report. In some example embodiments, UE110 can record in the failure report an identifier (ID) of the CHO and CPAC configurations, which has at least one execution condition that has not yet been met, and a reason why CHO and CPAC execution based on the CHO and CPAC configurations is not triggered. For example, the reason can indicate which of the CHO execution conditions and CPAC execution conditions was not met at the time of RLF, i.e., the problem condition that caused the delay in CHO and CPAC execution and ultimately led to RLF. Alternatively or additionally, the reason can also indicate which of the CHO execution conditions and CPAC execution conditions was met at the time of RLF, from which it can be inferred that the other condition was not met. For example, in case 1A, the reason can indicate that the CHO execution condition was met but the CPAC execution condition was not met; in case 1B, the reason can indicate that the CPAC execution condition was met but the CHO execution condition was not met; in case 1C, the reason can indicate that neither the CHO execution condition nor the CPAC execution condition was met. In some example implementations, if the CHO execution condition and the CPAC execution condition are each configured as a dual-event condition, the UE110 can use four information elements (IEs) to indicate whether the two dual events are satisfied.
[0064] In some example embodiments, UE110 can log information related to failure reports, which can be used to adapt the conditions of the problem in order to eliminate or mitigate RLF. For example, UE110 can log one or more of the following: • Unmet CHO or CPAC execution conditions during RLF, such as unmet event thresholds or offset values. • Information about the target cell (PCell or PSCell) related to the unmet conditions, such as the target cell's Physical Cell Identifier (PCI) and frequency. • The N last measurements of the target cell prior to this RLF, where N is a positive integer. • Information about the source cell (PCell or PSCell) related to the unmet conditions, such as the source cell's PCI and frequency. • The N last measurements of the source cell prior to this RLF, or • Indicates that the TTT timer is running when the CHO or CPAC execution condition is not met.
[0065] It should be understood that the above information is described as an example of failure report content, but failure reports are not limited to such examples in any way. UE110 can generate failure reports based on failure report configurations predefined at UE110 or received from S-MN120A at 222.
[0066] In response to the RLF, UE110 can initiate an RRC connection re-establishment procedure at position 234 and connect to the appropriate cell. Figure 2 In the example shown, it is assumed that UE110 is connected to T-MN120C; however, it should be understood that UE110 can connect to any other suitable cell and base station through the cell reselection process. For example, UE110 can connect to S-MN120A, S-SN120B (in... Figure 1 This can be done at different base stations that the UE110 connects to after the RLF (Regional Support Facility), such as the T-SN120D or any base station that does not participate in the conditional handover process. Therefore, some of the operations of the T-MN120C described below can be performed at different base stations that the UE110 connects to after the RLF.
[0067] At position 236, UE110 may send a failure report to T-MN120C (or any other base station to which UE110 is currently connected), indicating that an RLF occurred before both the CHO execution condition and the CPAC execution condition are met (i.e., when at least one of the CHO execution condition and the CPAC execution condition is not met). In some example embodiments, UE110 may indicate the availability of the failure report to T-MN120C in an RRC completion message (e.g., RRCReconfigurationComplete, RRCReestablishmentComplete, RRCSetupComplete, or RRCResumeComplete message), and then T-MN120C may obtain the failure report through the UE Information Request procedure. In some other example embodiments, after UE110 successfully connects to T-MN120C, T-MN120C may obtain the failure report blindly from UE110, or UE110 may send the failure report directly to T-MN120C. The content of the failure report has been described above, and for simplicity and convenience, a repeated description thereof is omitted here.
[0068] In some example embodiments, the T-MN120C can send the received failure report to the OAM140 at point 238. Before sending the failure report to the OAM140, the T-MN120C can modify the failure report, for example, by adding new information elements and / or removing unnecessary information elements when necessary. In some example embodiments, the T-MN120C can send the failure report to the OAM140 from a transparent container, and the T-MN120C may not be aware of the content of the failure report.
[0069] The OAM140 can collect a number of failure reports related to CHO and CPAC configurations and analyze the statistics of RLFs to determine whether the RLFs are caused by unmet execution conditions or other factors. If the RLFs are caused by unmet execution conditions(s), the OAM140 can determine adaptation information for(s) unmet / problematic execution conditions(s) to eliminate or reduce the RLFs. For example, the OAM140 can decide to adjust parameters (e.g.,(s) event thresholds and / or offset values for(s) problematic execution conditions(s)) so that(s) the execution conditions(s) can be satisfied earlier, for example, before the T310 timer expires, thereby eliminating or reducing the RLFs. The OAM140 can determine adaptation information for(s) unmet / problematic execution conditions(s) based on failure reports (e.g., N last measurements of the target cell and N last measurements of the optional source cell indicated in the failure reports). Adaptation information may include one or more new parameter values for(s) problematic execution conditions(s), or one or more increments of one or more parameters for(s) problematic execution conditions(s). In some example embodiments, the OAM140 can execute a machine learning model or algorithm to determine adaptation information for problematic execution conditions. The machine learning model can receive information elements from failure reports as input and provide adaptation information as output.
[0070] At position 240, the OAM140 can send a failure report to the base station from which it receives the report (e.g., Figure 2 The example shown (T-MN120C) sends adaptation information for unmet execution conditions. OAM140 can indicate to T-MN120C whether the adaptation information is for CHO or CPAC execution conditions.
[0071] If the adaptation information is for CPAC execution conditions determined at T-MN120C, then T-MN120C can adapt the CPAC execution conditions at 242 based on the adaptation information. For example, when T-MN120C receives a new handover request from S-MN120A, T-MN120C can consider the adaptation information to determine the new CPAC execution conditions.
[0072] If the adaptation information is used for the CHO execution condition determined at S-MN120A, T-MN120C can send the adaptation information to S-MN120A at 244. In some example embodiments, OAM140 can directly send the adaptation information for the CHO execution condition to S-MN120A at 246. OAM140 can know which base station determined the problematic execution condition from the CHO and CPAC configuration identifiers indicated in the failure report. If adaptation information is determined for the CHO execution condition, OAM140 can send the adaptation information to S-MN120A at 246. If adaptation information is determined for the CPAC execution condition, OAM140 can send the adaptation information to T-MN120C at 240. This can reduce network signaling overhead.
[0073] At point 248, the S-MN120A can adapt CHO execution conditions based on adaptation information. For example, when the S-MN120A receives a new CHO and CPAC configuration from the T-MN120C, the S-MN120A can consider the adaptation information to determine the new CHO execution conditions.
[0074] In some example embodiments, if the OAM140 sends adaptation information to a base station from which it receives a failure report, but the base station does not participate in the CHO and CPAC processes, the base station can forward the adaptation information to the S-MN120A or T-MN120C. For example, the adaptation information may contain information elements indicating the destination of the adaptation information.
[0075] In procedure 200, UE110 reports a failure to T-MN120C (or any base station UE110 connects to after the RLF), and then T-MN120C sends the failure information to OAM140. In some example embodiments, T-MN120C may send the failure information to S-MN120A. S-MN120A may then send the failure information to OAM140 or otherwise process the failure information. Examples of such procedures are... Figure 3 As shown in the image.
[0076] refer to Figure 3 Process 300 may also include the above regarding Figure 2 Steps 210-236 are described herein, and a repeated description of steps 210-236 is omitted here. After receiving a failure report from UE110 at 236, T-MN120C (or whatever base station UE110 is now connected to) can send a failure report to S-MN120A (i.e., the source master node of UE110 before RLF) at 310. T-MN120C (or whatever base station UE110 is now connected to) can identify S-MN120A based on the identifiers of the CHO and CPAC configuration indicated in the failure report.
[0077] At position 312, the S-MN120A can send the received failure report to the OAM140. Before sending the failure report to the OAM140, the S-MN120A can modify the failure report, for example, by adding new information elements and / or removing unnecessary information elements when necessary.
[0078] The OAM140 can collect a number of failure reports related to CHO and CPAC configurations and analyze RLF statistics to determine whether the RLF is caused by unmet execution conditions or other factors. If the RLF is caused by unmet execution conditions, the OAM140 can determine adaptation information for the unmet / problematic execution conditions to eliminate or reduce the RLF. For example, the OAM140 can decide to adjust the parameters of the problematic execution conditions (e.g., event thresholds and / or offset values) so that the execution conditions can be met earlier, for example, before the T310 timer expires, thereby eliminating or reducing the RLF.
[0079] At point 314, the OAM140 can send adaptation information for the unmet execution conditions to the S-MN120A (i.e., the base station from which it receives the failure report). The OAM140 can indicate to the S-MN120A whether the adaptation information is used for the CHO execution conditions and / or the CPAC execution conditions.
[0080] If the adaptation information is used for the CHO execution conditions determined at S-MN120A, then S-MN120A can adapt the CHO execution conditions at 316 based on the adaptation information. For example, when S-MN120A receives the CHO and CPAC configuration from T-MN120C, S-MN120A can consider the adaptation information to determine the new CHO execution conditions.
[0081] If the adaptation information is used for the CPAC execution condition determined at T-MN120C, S-MN120A can send the adaptation information to T-MN120C at 318. In some example embodiments, OAM140 can send the adaptation information for the CPAC execution condition directly to T-MN120C at 320. OAM140 can know which base station determined the problematic execution condition from the CHO and CPAC configuration identifier indicated in the failure report. If adaptation information is determined for the CHO execution condition, OAM140 can send the adaptation information to S-MN120A at 314. If adaptation information is determined for the CPAC execution condition, OAM140 can send the adaptation information to T-MN120C at 320. This can reduce network signaling overhead.
[0082] At point 322, the T-MN120C can adapt CPAC execution conditions based on adaptation information. For example, when the T-MN120C receives a new handover request from the S-MN120A, the T-MN120C can consider the adaptation information to determine the new CPAC execution conditions.
[0083] In processes 200 and 300 described above, T-MN120C (or any base station to which UE110 is connected after the RLF) sends the failure report received from UE110 to OAM140 or S-MN120A. In some example embodiments, T-MN120C may selectively send a failure report indicating that the CPAC execution conditions are not met to OAM140, and selectively send a failure report indicating that the CHO execution conditions are not met to S-MN120A. S-MN120A may then send a failure report indicating that the CHO execution conditions are not met to OAM140. OAM140 may send adaptation information for the CHO execution conditions to S-MN120A, and adaptation information for the CPAC execution conditions to T-MN120C.
[0084] In processes 200 and 300, execution condition adaptation is performed centrally; that is, OAM140 acts as the entity that collects failure reports to derive statistics and adapts condition parameters. In some other example embodiments, execution condition adaptation can be performed in a distributed manner, i.e., at the base station that determines the execution conditions. Therefore, signaling from / to OAM can be omitted, and the workload can be distributed across multiple network nodes. Examples of such processes are shown in... Figure 4 As shown in the image.
[0085] refer to Figure 4 Process 400 may also include the above regarding Figure 2Steps 210-236 are described herein, and a repeated description of steps 210-236 is omitted here. After receiving a failure report from UE110 at 236, if the failure report indicates that the CPAC execution conditions are not met, T-MN120C can determine adaptation information for the CPAC execution conditions at 410. In some example embodiments, T-MN120C may collect a number of failure reports from multiple UEs and analyze the statistics of the RLF to determine whether the RLF is caused by unmet CPAC execution conditions or by other factors. If the RLF is caused by unmet CPAC execution conditions, T-MN120C can determine adaptation information for the CPAC execution conditions to eliminate or reduce the RLF. For example, T-MN120C may decide to adjust the parameters of the problematic execution conditions (e.g., (multiple) event thresholds and / or offset values) so that the execution conditions can be met earlier, for example, before the T310 timer expires, thereby eliminating or reducing the RLF. The T-MN120C can determine adaptation information for CPAC execution conditions based on failure reports (e.g., N last measurements of the target PSCell indicated in the failure report and, optionally, N last measurements of the source PSCell). In some example embodiments, the T-MN120C can execute machine learning models or algorithms to determine adaptation information for CPAC execution conditions. Adaptation information may include one or more new parameter values for the problematic execution condition, or one or more increments to one or more parameters of the problematic execution condition.
[0086] At 412, the T-MN120C can adapt the CPAC execution conditions based on the determined adaptation information. For example, when the T-MN120C receives a new handover request from the S-MN120A, the T-MN120C can consider the adaptation information to determine the new CPAC execution conditions.
[0087] If a failure report indicates that the CHO execution conditions are not met, the T-MN120C can determine, based on the identifiers of the CHO and CPAC configurations indicated in the failure report, that the unmet CHO execution conditions were determined by the S-MN120A, since the CHO and CPAC configurations were sent from the T-MN120C to the S-MN120A at point 218. Then, at point 414, the T-MN120C can send a failure report to the S-MN120A.
[0088] In response to a failure report indicating that the CHO execution conditions were not met, the S-MN120A can determine adaptation information for the CHO execution conditions at point 416. In some example embodiments, the S-MN120A can collect a certain number of failure reports related to the CHO and CPAC configuration and analyze the statistics of the RLF to determine whether the RLF is caused by unmet CHO execution conditions or by other factors. If the RLF is caused by unmet CHO execution conditions, the S-MN120A can determine adaptation information, such as one or more new parameter values or increments for the CHO execution conditions, to ensure that the CHO execution conditions are met earlier, for example, before the T310 timer expires, thereby eliminating or reducing the RLF. The S-MN120A can determine the adaptation information for the CHO execution conditions based on the failure reports (e.g., the N last measurements of the target PCell and the N last measurements of the optional source PCell indicated in the failure reports).
[0089] At 418, the S-MN120A can adapt the CHO execution conditions based on the determined adaptation information. For example, when the S-MN120A receives a new CHO and CPAC configuration from the T-MN120C, the S-MN120A can consider the adaptation information to determine the new CHO execution conditions.
[0090] In some example embodiments, if UE110 connects and sends a failure report to a base station that is not involved in the CHO and CPAC processes, the base station may send a failure report to T-MN120C if the failure report indicates that the CPAC execution conditions are not met, or to S-MN120A if the failure report indicates that the CHO execution conditions are not met. T-MN120C or S-MN120A can then determine and apply adaptation information for the unmet execution conditions.
[0091] In the example embodiments described above, the UE experiences an RLF (Restricted Level Failure) with the MCG connection before the CHO and CPAC execution trigger (i.e., before both the CHO and CPAC execution conditions are met). In some other example embodiments, the UE110 may experience an RLF with the SCG connection before the CHO and CPAC execution trigger. Figure 5 The example procedure involving SCG failure is shown in the figure.
[0092] refer to Figure 5 Process 500 can also include the above regarding Figure 2Steps 210-226 are described herein, and a repeated description of steps 210-226 is omitted here. At 510, UE110 may experience / detect an interruption of the radio connection with S-SN120B (not shown). As described above, UE110 may experience an S-SN link interruption before or after one of the CHO and CPAC execution conditions is met. In response to this interruption, UE110 may start a Radio Link Failure (RLF) timer T310 for the S-SN link. When UE110 moves away from S-SN120B, the interruption may be caused by degradation of the link quality (e.g., Reference Signal Received Power, RSRP) between UE110 and S-SN120B and / or by interference from T-SN120D. In some example embodiments, UE110 may experience an interruption first and then meet one of the CHO and CPAC execution conditions. In other words, when an interruption occurs, neither the CHO nor the CPAC execution condition is met.
[0093] If neither the S-SN link is restored nor the CHO and CPAC execution conditions are met before the RLF timer T310 for the S-SN link expires, UE110 can declare an SCG failure at 512. In some example embodiments, UE110 can also declare an SCG failure due to other reasons (e.g., changes in network conditions affecting PSCell performance). Three scenarios for SCG failure are listed below: - Scenario 2: SCG(S-SN) fails when configuring CHO and CPAC: • Case 2A: When the CPAC execution conditions are met but the CHO execution conditions are not met, the UE experiences a failure with the S-SN due to interference from the T-SN; • Case 2B: When the CHO execution conditions are met but the CPAC execution conditions are not met, the UE experiences a failure with the S-SN due to low link quality (e.g., reference signal received power, RSRP) with the S-SN (e.g., S-SN coverage hole). • Case 2C: When neither the CHO execution condition nor the CPAC execution condition is met, the UE experiences a failure with the S-SN due to interference from the T-SN and low link quality with the S-SN.
[0094] In response to an SCG failure, UE110 may trigger a failure report if the criteria for triggering a failure report are met. As described above, the criteria for triggering a failure report may be received from S-MN120A at 222 or predefined at UE110. In some example embodiments, the criteria for triggering a failure report may include the failure to meet at least one of the CHO execution condition and the CPAC execution condition when the SCG fails. Figure 5In the example shown, it is assumed that at least one of the CHO and CPAC execution conditions is not met when the SCG fails. Therefore, the failure report triggering criterion is met, and UE110 triggers a failure report at 514.
[0095] At point 514, UE110 can create a failure report and record relevant failure information in the report. In some example embodiments, UE110 can record in the failure report an identifier (ID) of the CHO and CPAC configurations, which has at least one execution condition that has not yet been met, and the reason why CHO and CPAC execution is not triggered based on the CHO and CPAC configurations. For example, the reason may indicate which of the CHO and CPAC execution conditions was not met when SCG failed, i.e., the problematic execution conditions (multiple) caused the delay in CHO and CPAC execution and ultimately led to SCG failure. Alternatively or additionally, the reason may indicate which of the CHO and CPAC execution conditions was met when SCG failed, from which it can be inferred that the other was not met. For example, in case 2A, the reason may indicate that the CPAC execution condition was met but the CHO execution condition was not met; in case 2B, the reason may indicate that the CHO execution condition was met but the CPAC execution condition was not met; and in case 2C, the reason may indicate that neither the CHO nor the CPAC execution condition was met. In some example implementations, if the CHO execution condition and the CPAC execution condition are each configured as a dual-event condition, the UE110 can use four information elements (IEs) to indicate whether the two dual events are satisfied.
[0096] In some example embodiments, UE110 can log information related to failure reports, which can be used to adapt the conditions of the problem in order to eliminate or mitigate SCG failures. For example, UE110 can log one or more of the following: • Unmet CHO or CPAC execution conditions when SCG fails, such as unmet event thresholds or offset values. • Information about the target cell (PCell or PSCell) related to the unmet conditions(s), such as the target cell's Physical Cell Identifier (PCI) and frequency. • The N last measurements of the target cell before the SCG failed, where N is a positive integer. • Information about the source cell (PCell or PSCell) related to unmet conditions (e.g., the source cell's PCI and frequency). • The N last measurements of the source cell before the SCG failed, or • Indicates that the TTT timer is running when the SCG fails, provided that the CHO or CPAC execution condition has not been met.
[0097] It should be understood that the above information is described as an example of failure report content, but failure reports are not limited to such examples in any way. UE110 can generate failure reports based on failure report configurations predefined at UE110 or received from S-MN120A at 222.
[0098] At point 516, UE110 can send a failure report to S-MN120A, indicating that SCG failure occurred before both the CHO execution condition and the CPAC execution condition were met; that is, at least one of the CHO execution condition and the CPAC execution condition was not met when SCG failed. It is worth noting that in the case of SCG failure, UE110 still maintains a radio connection with S-MN120A, therefore, it is not necessary to initiate an RRC connection re-establishment procedure. In some example embodiments, UE110 can first indicate the availability of the failure report to S-MN120A, and then S-MN120A can obtain the failure report through the UE Information Request procedure. In some other example embodiments, UE110 can directly send the failure report to S-MN120A. The content of the failure report has already been described above, and for simplicity and convenience, a repeated description is omitted here.
[0099] In some example embodiments, the S-MN120A can send the received failure report to the OAM140 at point 518. Before sending the failure report to the OAM140, the S-MN120A can modify the failure report, for example, by adding new information elements and / or removing unnecessary information elements when necessary. In some example embodiments, the S-MN120A can send the failure report to the OAM140 from a transparent container, and the S-MN120A may not be aware of the content of the failure report.
[0100] The OAM140 can collect a number of failure reports related to CHO and CPAC configurations and analyze the statistics of SCG failures to determine whether the SCG failures are caused by unmet execution conditions or other factors. If the SCG failures are caused by unmet execution conditions(s), the OAM140 can determine adaptation information for the unmet / problematic execution conditions(s) to eliminate or reduce SCG failures. For example, the OAM140 can decide to adjust parameters, such as event thresholds and / or offset values for the problematic execution conditions(s), so that the execution conditions(s) can be met earlier, for example, before the T310 timer expires, thereby eliminating or reducing SCG failures. The OAM140 can determine adaptation information for the unmet / problematic execution conditions(s) based on failure reports (e.g., N last measurements of the target cell and N last measurements of the optional source cell indicated in the failure reports). Adaptation information may include one or more new parameter values for the problematic execution conditions(s), or one or more increments of one or more parameters for the problematic execution conditions(s). In some example embodiments, the OAM140 can execute a machine learning model or algorithm to determine adaptation information for problematic execution conditions. The machine learning model can receive information elements from failure reports as input and provide adaptation information as output.
[0101] At point 520, OAM140 can send adaptation information to S-MN120A for unmet execution conditions. OAM140 can indicate to S-MN120A whether the adaptation information is used for CHO execution conditions and / or CPAC execution conditions.
[0102] If the adaptation information is used to determine the CHO execution conditions at S-MN120A, then S-MN120A can adapt the CHO execution conditions at 522 based on the adaptation information. For example, when S-MN120A receives a new CHO and CPAC configuration from T-MN120C, S-MN120A can consider the adaptation information to determine the new CHO execution conditions.
[0103] If the adaptation information is used for the CPAC execution condition determined at T-MN120C, S-MN120A can send the adaptation information to T-MN120C at 524. In some example embodiments, OAM140 can directly send the adaptation information for the CPAC execution condition to T-MN120C at 526. OAM140 can know from the failure report which base station determined the problematic execution condition. If the SCG failure is caused by the CHO execution condition, OAM140 can send the adaptation information for the CHO execution condition to S-MN120A at 520. If the SCG failure is caused by the CPAC execution condition, OAM140 can send the adaptation information for the CPAC execution condition to T-MN120C at 526. This can reduce network signaling overhead.
[0104] At point 528, the T-MN120C can adapt CPAC execution conditions based on adaptation information. For example, when the T-MN120C receives a new handover request from the S-MN120A, the T-MN120C can consider the adaptation information to determine the new CPAC execution conditions.
[0105] In procedure 500, UE110 reports SCG failure information to S-MN120A, and S-MN120A forwards the SCG failure information to OAM140. In some example embodiments, S-MN120A may send failure information to T-MN120C. T-MN120C may send failure information to OAM140 or otherwise process the failure information. Examples of such procedures are... Figure 6 As shown in the image.
[0106] refer to Figure 6 Process 600 may also include the above regarding Figure 2 and Figure 5 Steps 210-226 and 510-516 are described herein, and repeated descriptions of steps 210-226 and 510-516 are omitted here. After receiving a failure report from UE110 at 516, if the failure report indicates that the CPAC execution conditions were not met when the SCG failed, S-MN120A may send a failure report to T-MN120C, which determines the CPAC execution conditions, at 610. If the failure report indicates that the CHO execution conditions were not met when the SCG failed, S-MN120A may proceed as described above regarding... Figure 5 Step 518 of the discussion involves sending a failure report to OAM140. If neither the CHO execution condition nor the CPAC execution condition is met, S-MN120A may send the portion of the failure report related to CHO execution to OAM140 and the portion of the failure report related to CPAC execution to T-MN120C.
[0107] In some example embodiments, the T-MN120C may send a failure report to the OAM140 at point 612. Before sending the failure report to the OAM140, the T-MN120C may modify the failure report, for example, by adding new information elements and / or removing unnecessary information elements when necessary. For example, the T-MN120C may add information that will help determine the appropriate CPAC execution conditions to the failure report.
[0108] In some example implementations, if a failure report indicates that the CPAC execution conditions are not met, the S-MN120A can send the failure report directly to the OAM140 at 614. This reduces the overall signaling overhead of the network because the S-MN120A does not need to send the failure report to the T-MN120C.
[0109] The OAM140 can collect a number of failure reports related to CHO and CPAC configurations and analyze the statistics of SCG failures to determine whether the SCG failures are caused by unmet CPAC execution conditions or other factors. If the SCG failures are caused by unmet CPAC execution conditions, the OAM140 can determine adaptation information for the CPAC execution conditions to eliminate or reduce SCG failures. For example, the OAM140 can decide to adjust the parameters of the CPAC execution conditions (e.g., event thresholds and / or offset values) so that the CPAC execution conditions can be met earlier, for example, before the T310 timer expires, thereby eliminating or reducing SCG failures. The OAM140 can determine the adaptation information for the CPAC execution conditions based on failure reports (e.g., N last measurements of the target PSCell indicated in the failure reports and, optionally, N last measurements of the source PSCell). The adaptation information may include one or more new parameter values for the CPAC execution conditions, or one or more increments to one or more parameters of the CPAC execution conditions. In some example embodiments, the OAM140 can execute machine learning models or algorithms to determine adaptation information for CPAC execution conditions.
[0110] At position 616, the OAM140 can send adaptation information for CPAC execution conditions to the T-MN120C.
[0111] At point 618, the T-MN120C can adapt the CPAC execution conditions based on the received adaptation information. For example, when the T-MN120C receives a new handover request from the S-MN120A, the T-MN120C can consider the adaptation information to determine the new CPAC execution conditions.
[0112] In procedures 500 and 600, UE110 reports failure information to S-MN120A, and S-MN120A sends failure information to OAM140 directly or via T-MN120C. OAM140 then determines adaptation information for the unmet execution conditions. In other words, execution condition adaptation is performed centrally. In some other example embodiments, execution condition adaptation can be performed in a distributed manner, i.e., at the base station that determines the execution conditions. Therefore, signaling from / to OAM140 can be omitted, and the workload can be distributed to multiple network nodes. Examples of such procedures are shown in... Figure 7 As shown in the image.
[0113] refer to Figure 7 Process 700 may also include the above regarding Figure 2 and Figure 5 Steps 210-226 and 510-516 are described herein, and repeated descriptions of steps 210-226 and 510-516 are omitted here. After receiving an SCG failure report from UE110 at 516, if the failure report indicates that the CHO execution conditions are not met, S-MN120A can determine adaptation information for the CHO execution conditions at 710. In some example embodiments, S-MN120A may collect a number of failure reports from multiple UEs and analyze the statistics of SCG failures to determine whether the SCG failure is caused by unmet CHO execution conditions or by other factors. If the SCG failure is caused by unmet CHO execution conditions, S-MN120A can determine adaptation information for the CHO execution conditions to eliminate or reduce SCG failures. For example, S-MN120A may decide to adjust parameters, such as multiple event thresholds and / or offset values of the CHO execution conditions, so that the CHO execution conditions can be met earlier, for example, before the T310 timer expires, thereby eliminating or reducing SCG failures. The S-MN120A can determine adaptation information for CHO execution conditions based on failure reports (e.g., N last measurements of the target PCell and N last measurements of the optional source PCells indicated by the failure reports). In some example embodiments, the S-MN120A can execute machine learning models or algorithms to determine adaptation information for CHO execution conditions. Adaptation information may include one or more new parameter values for CHO execution conditions, or one or more increments to one or more parameters for CHO execution conditions.
[0114] At 712, the S-MN120A can adapt the CHO execution conditions based on the determined adaptation information. For example, when the S-MN120A receives a new CHO and CPAC configuration from the T-MN120C, the S-MN120A can consider the adaptation information to determine the new CHO execution conditions.
[0115] If the failure report received from UE110 indicates that the CPAC execution conditions are not met, S-MN120A can determine, based on the CHO and CPAC configuration identifier indicated in the failure report, that the unmet CPAC execution conditions were determined by T-MN120C. S-MN120A can then send a failure report to T-MN120C at 714.
[0116] In response to a failure report indicating that CPAC execution conditions were not met, the T-MN120C can determine adaptation information for the CPAC execution conditions at point 716. In some example embodiments, the T-MN120C can collect a number of failure reports related to the CHO and CPAC configuration and analyze statistics on SCG failures to determine whether the SCG failure was caused by unmet CPAC execution conditions or by other factors. If the SCG failure was caused by unmet CPAC execution conditions, the T-MN120C can determine adaptation information (e.g., one or more new values or increments of one or more parameters of the CPAC execution conditions) to ensure that the CPAC execution conditions are met earlier, for example, before the T310 timer expires, thereby eliminating or reducing SCG failures. The T-MN120C can determine the adaptation information for the CPAC execution conditions based on failure reports (e.g., N last measurements of the target PSCell indicated in the failure report and, optionally, N last measurements of the source PSCell).
[0117] At point 718, the T-MN120C can adapt CPAC execution conditions based on the determined adaptation information. For example, when the T-MN120C receives a new handover request from the S-MN120A, the T-MN120C can consider the adaptation information to determine the new CPAC execution conditions.
[0118] In procedure 200-700, the UE reports failure information indicating which of the CHO and CPAC execution conditions was not met when the MCG or SCG failed. The network can then distinguish whether the failure was caused by either of the two conditions bound to a single CHO and CPAC configuration. Therefore, the network can adapt the relevant conditions of the CHO and CPAC configurations. Condition adaptation can be implemented centrally at the OAM or distributedly at the corresponding RAN node that identifies the problematic execution condition.
[0119] Figure 8An example method 800 is shown for the execution conditions associated with adapting and combining conditional handovers and cell additions or changes in configuration (e.g., the CHO and CPAC configurations discussed above). Method 800 can be implemented at a terminal device (e.g., UE110 mentioned above). It is assumed that the terminal device operates in dual connectivity (DC) mode, connected to a first network node acting as the primary node (e.g., S-MN120A discussed above) and a third network node acting as the secondary node (e.g., S-SN120B discussed above).
[0120] refer to Figure 8 Method 800 may include step 810 of receiving a configuration message from a first network node by a terminal device. This configuration message includes at least one execution condition for conditional handover and at least one execution condition for cell addition or modification. The configuration may indicate candidate PCells and optional one or more MCGSCells prepared at a second network node (e.g., T-MN120C discussed above) for conditional handover operations, and candidate PSCells and optional one or more SCGSCells prepared at a fourth network node (e.g., T-SN120D discussed above) for cell addition or modification operations. The at least one execution condition for conditional handover and the at least one execution condition for cell addition or modification may be bound to each other, meaning that conditional handover and cell addition or modification will not be triggered unless both are satisfied.
[0121] After receiving the configuration message, the terminal device may, at step 820, evaluate whether at least one execution condition for conditional handover and at least one execution condition for cell addition or change are met. For example, when the terminal device moves from the first network node and the third network node toward the second network node and the fourth network node, it may first meet one of the at least one condition for conditional handover and at least one condition for cell addition or change, while the other may not yet be met.
[0122] Method 800 may further include step 830 of detecting a radio link failure between the terminal device and the first network node before both at least one condition for conditional handover and at least one condition for cell addition or change are met. In other words, at the time of radio link failure, at least one of the at least one condition for conditional handover and at least one condition for cell addition or change is not met. For example, when the terminal device moves from the first network node (i.e., S-MN) toward the second network node (i.e., candidate T-MN), the terminal device may experience an S-MN link interruption due to low link quality (e.g., low RSRP) of the first network node and / or interference from the second network node. The terminal device may start a T310 timer for the S-MN interruption. If conditional handover and cell addition or change are not triggered (i.e., at least one of the at least one condition for cell addition or change and at least one condition for conditional handover has not been met) and the T310 timer expires (i.e., the S-MN link has not been restored), the terminal device may declare a radio link failure with the first network node.
[0123] In response to a radio link failure with the first network node (i.e., S-MN), the terminal device may establish a radio connection with the second network node (i.e., the candidate T-MN) at step 840. For example, the terminal device may initiate an RRC connection re-establishment procedure to connect to a suitable cell supported by the second network node.
[0124] After establishing a radio connection with the second network node, the terminal device may perform step 850 of sending a failure report to the second network node, the failure report indicating a radio link failure that occurred before both at least one condition for handover and at least one condition for cell addition or change were met. In some example embodiments, the failure report may include identifiers of the handover and cell addition or change configurations and a reason why the handover and cell addition or change were not triggered based on the configuration. For example, the reason may indicate which of the at least one condition for handover and at least one condition for cell addition or change were not met, which of the at least one condition for handover and at least one condition for cell addition or change were met, or both. Thus, the network can know which condition potentially delayed the execution of the handover and cell addition or change, and therefore caused the radio link failure.
[0125] In some example embodiments, the failure report may also include additional information to adapt to problematic conditions that could potentially cause the radio link to fail. For example, the failure report may also include at least one of the following: • At least one condition for conditional handover or for cell addition or modification that is not met, such as a threshold and offset parameter for the condition. • Information about the target cell related to the unmet conditions, such as the target cell's Physical Cell Identifier (PCI) and frequency. • The N last measurements of the target cell before the radio link failed, where N is a positive integer. • Information about the source cell related to the unmet conditions, such as the source cell's PCI and frequency. • The N last measurements of the source cell before the radio link failed, or • An indication that the unmet trigger time (TTT) timer is running when the radio link fails.
[0126] In some example embodiments, method 800 may further include a step configured by the terminal device to receive a failure report from a first network node before the radio link fails. Figure 8 (Not shown in the image). The failure reporting configuration can specify at least one of the following: • The content of the failure report; or • The criteria used to trigger this failure report.
[0127] The terminal device can then trigger a failure report and record relevant information based on the failure report configuration. In some example embodiments, the criteria for triggering a failure report may include at least one of the following: failure to meet at least one condition for conditional handover and at least one condition for cell addition or change when the radio link fails.
[0128] Figure 9 An example method 900 is shown for the execution conditions associated with adapting and combining conditional handover and cell addition or change configurations (e.g., the CHO and CPAC configurations discussed above). Method 900 can be implemented at a second network node (e.g., any other base station that T-MN120C or UE110 connects to after the radio link with S-MN120A fails), as described above.
[0129] refer to Figure 9 Method 900 may include step 910 of establishing a radio connection between a second network node and a terminal device (e.g., UE110 discussed above), and step 920 of receiving a failure report from the terminal device. The failure report may indicate that a radio link failure has occurred between the terminal device and the first network node when at least one of a condition for conditional handover and at least one condition for cell addition or change is not met at the terminal device. In some example embodiments, the first network node acts as the master node of the terminal device prior to the radio link failure, such as S-MN120A discussed above.
[0130] In some example embodiments, the failure report may include a configuration identifier that includes at least one condition for conditional handover and at least one condition for cell addition or change. For example, the configuration may be a combined conditional handover and conditional PSCell addition or change configuration. The failure report may also include a reason why conditional handover and cell addition or change are not triggered based on the configuration. The reason may indicate which of the at least one condition for conditional handover and at least one condition for cell addition or change was not met, which of the at least one condition for conditional handover and at least one condition for cell addition or change was met, or both. It should be understood that conditional handover and cell addition or change can only be triggered if both conditions are met. Therefore, the network can know from the failure report which condition(s) potentially delayed the execution of conditional handover and cell addition or change, and thus caused radio link failure.
[0131] In some example embodiments, the failure report may also include additional information to accommodate multiple problematic conditions that could potentially cause the radio link to fail. For example, the failure report may also include at least one of the following: • At least one condition for conditional handover or for cell addition or modification that is not met, such as a threshold and offset parameter for the condition. • Information about the target cell related to the unmet conditions, such as the target cell's Physical Cell Identifier (PCI) and frequency. • The N last measurements of the target cell before the radio link failed, where N is a positive integer. • Information about the source cell related to the unmet conditions, such as the source cell's PCI and frequency. • The N last measurements of the source cell before the radio link failed, or • An indication that the unmet trigger time (TTT) timer is running when the radio link fails.
[0132] Upon receiving a failure report, the second network node may send the failure report at step 930 to the Operation Management and Maintenance (OAM) entity (e.g., OAM140 discussed above) or to the first network node (e.g., S-MN120A discussed above). Alternatively or additionally, if the unmet execution condition indicated in the failure report is determined by the second network node—that is, at least one execution condition for cell addition or modification determined at the second network node is unmet—the second network node may determine at 940 the adaptation information for the unmet condition (i.e., at least one condition for cell addition or modification).
[0133] In some example embodiments, if a failure report is sent to an OAM entity, the method may further include the step of receiving adaptation information from the OAM entity for unmet conditions. If the adaptation information is for at least one condition used for condition handover, the second network node may send the adaptation information to a first network node to which the adaptation information can be applied. If the adaptation information is for at least one condition determined at the second network node for cell addition or modification, the second network node may adapt the at least one condition for cell addition or modification based on the adaptation information.
[0134] In some example embodiments, if a failure report is sent to a first network node, the method may further include receiving adaptation information from the first network node for at least one condition determined at a second network node for cell addition or modification. The second network node can then adapt the at least one condition for cell addition or modification based on the adaptation information.
[0135] In some example embodiments, the second network node may determine a failure reporting configuration and send it to the first network node before establishing a radio connection with the terminal device. The failure reporting configuration may specify the content of the failure report and / or the criteria used to trigger the failure report. The first network node may send the failure reporting configuration to the terminal device before a radio link failure occurs.
[0136] Figure 10 An example method 1000 is shown for the execution conditions associated with adapting and combining conditional handovers and cell additions or configuration changes (e.g., the CHO and CPAC configurations discussed above). Method 1000 can be implemented at a first network node (e.g., the S-MN120A described above).
[0137] refer to Figure 10 Method 1000 may include the step of sending a configuration message from a first network node to a terminal device (e.g., UE110 discussed above), the configuration message including at least one condition for conditional handover and at least one condition for cell addition or change, and the step of receiving a failure report from a second network device (e.g., T-MN120C or any other base station that UE110 connects to after a radio link failure with S-MN120A), as described above. It should be understood that conditional handover and cell addition or change can only be triggered if both conditions are met. The failure report may indicate that a radio link failure occurred between the terminal device and the first network node when at least one of the conditions for conditional handover and at least one condition for cell addition or change is not met at the terminal device.
[0138] In some example embodiments, the failure report may include a configuration identifier that includes at least one condition for conditional handover and at least one condition for cell addition or change. For example, the configuration may be a combined conditional handover and conditional PSCell addition or change configuration. The failure report may also include a reason why the conditional handover and cell addition or change are not triggered based on the configuration. The reason may indicate which of the at least one condition for conditional handover and at least one condition for cell addition or change was not met, which of the at least one condition for conditional handover and at least one condition for cell addition or change was met, or both. Therefore, the network can know from the failure report which condition(s) potentially delayed the execution of the conditional handover and cell addition or change, and thus caused the radio link failure.
[0139] In some example embodiments, the failure report may also include additional information to accommodate multiple problematic conditions that could potentially cause the radio link to fail. For example, the failure report may also include at least one of the following: • At least one condition for conditional handover or for cell addition or modification that is not met, such as a threshold and offset parameter for the condition. • Information about the target cell related to the unmet conditions, such as the target cell's Physical Cell Identifier (PCI) and frequency. • The N last measurements of the target cell before the radio link failed, where N is a positive integer. • Information about the source cell related to the unmet conditions, such as the source cell's PCI and frequency. • The N last measurements of the source cell before the radio link failed, or • An indication that the unmet trigger time (TTT) timer is running when the radio link fails.
[0140] Upon receiving a failure report, the first network node may send the failure report to the Operations Management and Maintenance (OAM) entity (e.g., OAM140 discussed above) at step 1030. Alternatively or additionally, if the first network node determines that an unmet execution condition indicated in the failure report is not met—that is, at least one execution condition for condition switching is not met—the first network node may determine adaptation information for the unmet condition (i.e., at least one condition for condition switching) at step 1040.
[0141] In some example embodiments, if a failure report is sent to an OAM entity, the method may further include the step of receiving adaptation information from the OAM entity for unmet conditions. If the adaptation information is for at least one condition used for handover, the first network node may adapt to the at least one condition used for handover based on the adaptation information. If the adaptation information is for at least one condition used for cell addition or modification, the first network node may send the adaptation information to the second network node if the second network node determines the at least one condition for cell addition or modification.
[0142] In some example embodiments, the first network node may send a failure report configuration to the terminal device before a radio link failure occurs between the first network node and the terminal device. If the second network node acts as a candidate target master node for the terminal device before the radio link failure, the failure report configuration may be determined by the first network node or received from the second network node, and it may specify the content of the failure report and / or the criteria used to trigger the failure report.
[0143] Figure 11 An example method 1100 is shown for the execution conditions associated with adapting and combining conditional handovers and cell additions or configuration changes (e.g., the CHO and CPAC configurations discussed above). Method 1100 can be implemented at an Operations Administration and Maintenance (OAM) entity (e.g., OAM140 mentioned above).
[0144] refer to Figure 11 Method 1100 may include step 1110: receiving a failure report from a first network node or a second network node by an OAM entity, the failure report indicating a radio link failure between the terminal device and the first network node when at least one of a condition for conditional handover and at least one condition for cell addition or change is not met. In some example embodiments, the first network node acts as the master node of the terminal device before the radio link failure, and the terminal device connects to the second network node after the radio link failure. In some example embodiments, the second network node is configured as a candidate target master node of the terminal device before the radio link failure. Assuming the terminal device first sends a failure report to the second network node, the second network node may then send the failure report to the OAM entity directly or via the first network node.
[0145] In some example embodiments, the failure report may include a configuration identifier that includes at least one condition for conditional handover and at least one condition for cell addition or change. For example, the configuration may be a combined conditional handover and conditional PSCell addition or change configuration. The failure report may also include a reason why the conditional handover and cell addition or change are not triggered based on the configuration. The reason may indicate which of the at least one condition for conditional handover and at least one condition for cell addition or change was not met, which of the at least one condition for conditional handover and at least one condition for cell addition or change was met, or both. Therefore, the network can know from the failure report which condition(s) potentially delayed the execution of the conditional handover and cell addition or change, and thus caused the radio link failure.
[0146] In some example embodiments, the failure report may also include additional information to accommodate multiple problematic conditions that could potentially cause the radio link to fail. For example, the failure report may also include at least one of the following: • At least one condition for conditional handover or for cell addition or modification that is not met, such as a threshold and offset parameter for the condition. • Information about the target cell related to the unmet conditions, such as the target cell's Physical Cell Identifier (PCI) and frequency. • The N last measurements of the target cell before the radio link failed, where N is a positive integer. • Information about the source cell related to the unmet conditions, such as the source cell's PCI and frequency. • The N last measurements of the source cell before the radio link failed, or • An indication that the unmet trigger time (TTT) timer is running when the radio link fails.
[0147] Upon receiving a failure report, the OAM entity can determine adaptation information for the unmet conditions indicated in the failure report at step 1120, and send the determined adaptation information to the relevant network node at step 1130. In some example embodiments, the OAM entity can send the adaptation information to a first network node if adaptation information is determined for at least one condition used for handover, or to a second network node if adaptation information is determined for at least one condition used for cell addition or modification. In some other example embodiments, the OAM entity can send the adaptation information to the network node from which it received the failure report, regardless of which condition the adaptation information was determined for.
[0148] Figure 12An example method 1200 is shown for the execution conditions associated with adapting and combining conditional handovers and cell additions or changes in configuration (e.g., the CHO and CPAC configurations discussed above). Method 1200 can be implemented at a terminal device (e.g., UE 110 mentioned above). It is assumed that the terminal device operates in dual connectivity (DC) mode, connected to a first network node acting as the primary node (e.g., S-MN120A discussed above) and a third network node acting as the secondary node (e.g., S-SN120B discussed above).
[0149] refer to Figure 12 Method 1200 may include step 1210 of receiving a configuration message from a first network node by a terminal device. This configuration message includes at least one execution condition for conditional handover and at least one execution condition for cell addition or modification. The configuration may indicate candidate PCells and optional one or more MCGSCells prepared at a second network node (e.g., T-MN120C discussed above) for conditional handover operations, and candidate PSCells and optional one or more SCGSCells prepared at a fourth network node (e.g., T-SN120D discussed above) for cell addition or modification operations. The at least one execution condition for conditional handover and the at least one execution condition for cell addition or modification may be bound to each other, meaning that conditional handover and cell addition or modification will not be triggered unless both are satisfied.
[0150] After receiving the configuration message, the terminal device may, at step 1220, evaluate whether at least one execution condition for conditional handover and at least one execution condition for cell addition or change are met. For example, when the terminal device moves from the first network node and the third network node toward the second network node and the fourth network node, it may first meet one of the at least one condition for conditional handover and at least one condition for cell addition or change, while the other may not yet be met.
[0151] Method 1200 may further include step 1230: before both at least one condition for conditional handover and at least one condition for cell addition or change are met, i.e. before the combined conditional handover and cell addition or change are triggered, a connection failure between the terminal device and the third network node is detected. For example, when the terminal device moves from the third network node (i.e., S-SN) to the fourth network node (i.e., candidate T-SN), the terminal device may experience an S-SN link interruption due to low link quality (e.g., low RSRP) of the third network node and / or interference from the fourth network node. The terminal device may start a T310 timer for the S-SN interruption. If the conditional handover and cell addition or change are not triggered (i.e., at least one condition for cell addition or change or at least one condition for conditional handover has not been met) and the T310 timer expires (i.e., the S-SN link has not been restored), the terminal device may declare a connection failure with the third network node, i.e., SCG failure.
[0152] Method 1200 may further include step 1240: sending a failure report to a first network node, the failure report indicating that an SCG failure occurred before both at least one condition for conditional handover and at least one condition for cell addition or change were met. In some example embodiments, the failure report may include identifiers of the conditional handover and cell addition or change configurations and a reason why the conditional handover and configuration-based cell addition or change were not triggered. For example, the reason may indicate which of the at least one condition for conditional handover and at least one condition for cell addition or change were not met, which of the at least one condition for conditional handover and at least one condition for cell addition or change were met, or both. Thus, the network can know which condition(s) potentially delayed the execution of the conditional handover and cell addition or change, and therefore caused the SCG failure.
[0153] In some example embodiments, the failure report may also include additional information to accommodate multiple problem conditions that could cause the SCG to fail. For example, the failure report may also include at least one of the following: • At least one condition for conditional handover or for cell addition or modification that is not met, such as a threshold and offset parameter for the condition. • Information about the target cell related to the unmet conditions, such as the target cell's Physical Cell Identifier (PCI) and frequency. • The N last measurements of the target cell before the radio link failed, where N is a positive integer. • Information about the source cell related to the unmet conditions, such as the source cell's PCI and frequency. • The N last measurements of the source cell before the radio link failed, or • An indication that the unmet trigger time (TTT) timer is running when the radio link fails.
[0154] In some example embodiments, method 1200 may further include the step of receiving a failure report configuration from a first network node by the terminal device before the SCG fails (not shown). The failure report configuration may specify at least one of the following: • The content of the failure report; or • The criteria used to trigger this failure report.
[0155] The terminal device can then trigger a failure report and record relevant information based on the failure report configuration. In some example embodiments, the criteria for triggering a failure report may include at least one of the following: at least one condition for conditional handover and at least one condition for cell addition or modification is not met when the SCG fails.
[0156] Figure 13 An example method 1300 is shown for the execution conditions associated with adapting and combining conditional handovers and cell additions or configuration changes (e.g., the CHO and CPAC configurations discussed above). Method 1300 can be implemented at a second network node (e.g., the T-MN120C mentioned above).
[0157] Reference Figure 13 Method 1300 may include step 1310 of sending at least one condition regarding cell addition or change from a second network node to a first network node. For example, the second network node may determine and send at least one condition for cell addition or change in response to a handover request received from the first network node. The first network node may act as a master node (e.g., S-MN120A discussed above) for a terminal device (e.g., UE110 discussed above) and is intended to hand over the terminal device to the second network node. The second network node may determine a combined conditional handover and cell addition or change configuration for the terminal device, including at least one condition for cell addition or change, and send the configuration to the first network node at step 1310.
[0158] At step 1320, the second network node may receive a failure report from the first network node. The failure report may indicate that an SCG failure occurred between the terminal device and the third network node when at least one of the conditions for conditional handover and at least one of the conditions for cell addition or change was not met at the terminal device. The third network node acts as a secondary node supporting the SCG cell of the terminal device, such as the S-SN120B discussed above.
[0159] In some example embodiments, the failure report may include a configuration identifier that includes at least one condition for conditional handover and at least one condition for cell addition or modification. For example, the configuration may be a combined conditional handover and conditional PSCell addition or modification configuration. The failure report may also include a reason why the conditional handover and cell addition or modification are not triggered based on the configuration. This reason may indicate that at least one condition for cell addition or modification was not met when the SCG failed. Therefore, the second network node can know from the failure report that at least one condition for cell addition or modification may have delayed the execution of conditional handover and cell addition or modification, thus causing the SCG failure.
[0160] In some example embodiments, the failure report may also include additional information to accommodate the problematic conditions(s) that could cause the SCG to fail. For example, the failure report may also include at least one of the following: • At least one condition for conditional handover or for cell addition or modification that is not met, such as a threshold and offset parameter for the condition. • Information about the target cell related to the unmet conditions, such as the target cell's Physical Cell Identifier (PCI) and frequency. • The N last measurements of the target cell before the radio link failed, where N is a positive integer. • Information about the source cell related to the unmet conditions, such as the source cell's PCI and frequency. • The N last measurements of the source cell before the radio link failed, or • An indication that the unmet trigger time (TTT) timer is running when the radio link fails.
[0161] After receiving a failure report, the second network node may send the failure report to the Operation Management and Maintenance (OAM) entity (e.g., OAM140 discussed above) in step 1330, or determine adaptation information for at least one condition for cell addition or modification in step 1340.
[0162] In some example embodiments, if a failure report is sent to the OAM entity in step 1330, the method may further include a step of receiving adaptation information from the OAM entity for at least one condition for cell addition or modification. Figure 13 (Not shown in the image). The second network node can adapt to at least one condition for cell addition or modification based on adaptation information received from the OAM entity, or based on adaptation information determined by the second network node at step 1340.
[0163] In some example embodiments, the second network node may determine and send a failure report configuration to the first network node before receiving the failure report from the first network node. The failure report configuration may specify the content of the failure report and / or the criteria used to trigger the failure report. The first network node may send the failure report configuration to the terminal device before an SCG failure occurs.
[0164] Figure 14 An example method 1400 is shown for the execution conditions associated with adapting and combining conditional handovers and cell additions or configuration changes (e.g., the CHO and CPAC configurations discussed above). Method 1400 can be implemented at a first network node (e.g., the S-MN120A described above).
[0165] refer to Figure 14 Method 1400 may include step 1410 of sending a configuration message from a first network node to a terminal device (e.g., UE 110 discussed above), the configuration message including at least one condition for conditional handover and at least one condition for cell addition or change, and step 1420 of receiving a failure report from the terminal device. In some example embodiments, the at least one condition for conditional handover and the at least one condition for cell addition or change may be bound together, i.e., conditional handover and cell addition or change may be triggered only if both conditions are met. The failure report may indicate that an SCG failure has occurred between the terminal device and the third network node when at least one of the at least one condition for conditional handover and the at least one condition for cell addition or change is not met at the terminal device. The first network node may act as the primary node of the MCG cell supporting the terminal device, and the third network node may act as the secondary node of the SCG cell supporting the terminal device.
[0166] In some example embodiments, the failure report may include a configured identifier that includes at least one condition for conditional handover and at least one condition for cell addition or change. The failure report may also include a reason why conditional handover and cell addition or change are not triggered based on the configuration. The reason may indicate which of the at least one condition for conditional handover and at least one condition for cell addition or change was not met, which of the at least one condition for conditional handover and at least one condition for cell addition or change was met, or both. Therefore, the network can know from the failure report which condition(s) potentially delayed the execution of conditional handover and cell addition or change, and thus caused the SCG to fail.
[0167] In some example embodiments, the failure report may also include additional information to accommodate multiple problem conditions that could cause the SCG to fail. For example, the failure report may also include at least one of the following: • At least one condition for conditional handover or for cell addition or modification that is not met, such as a threshold and offset parameter for the condition. • Information about the target cell related to the unmet conditions, such as the target cell's Physical Cell Identifier (PCI) and frequency. • The N last measurements of the target cell before the radio link failed, where N is a positive integer. • Information about the source cell related to the unmet conditions, such as the source cell's PCI and frequency. • The N last measurements of the source cell before the radio link failed, or • An indication that the unmet trigger time (TTT) timer is running when the radio link fails.
[0168] Upon receiving a failure report, in step 1430, the first network node may send the failure report to an Operations Management and Maintenance (OAM) entity, such as OAM140 discussed above. If the failure report indicates that at least one condition for cell addition or modification is not met, the first network node may send the failure report to a second network node that determines at least one condition for cell addition or modification.
[0169] In some example embodiments, if a failure report indicates that at least one condition for conditional switching is not met, then at step 1440, the first network node may determine adaptation information for the at least one condition for conditional switching. The first network node may then adapt the at least one condition for conditional switching based on the adaptation information.
[0170] In some example embodiments, if a failure report is sent to the OAM entity in step 1430, the method may further include a step of receiving adaptation information from the OAM entity for unmet conditions. Figure 14 (Not shown in the image). If the adaptation information pertains to at least one condition for handover, the first network node can adapt to the at least one condition for handover based on the adaptation information. If the adaptation information pertains to at least one condition for cell addition or modification, the first network node can send the adaptation information to a second network node that can apply the adaptation information.
[0171] In some example embodiments, the first network node may send a failure report configuration to the terminal device before an SCG failure occurs between the third network node and the terminal device. The failure report configuration may be determined by the first network node or received from the second network node, and it may specify the content of the failure report and / or the criteria used to trigger the failure report.
[0172] Figure 15An example method 1500 is shown for the execution conditions associated with adapting and combining conditional handovers and cell additions or configuration changes (e.g., the CHO and CPAC configurations discussed above). Method 1500 can be implemented at an Operations Administration and Maintenance (OAM) entity (e.g., OAM140 mentioned above).
[0173] refer to Figure 15 Method 1500 may include step 1510: when at least one of the conditions for conditional handover and at least one of the conditions for cell addition or change is not met, the OAM entity receives a failure report from a first network node or a second network node indicating that an SCG failure has occurred between the terminal device and the third network node. In some example embodiments, the first network node may act as the primary node of the terminal device (e.g., S-MN120A discussed above), the third network node may act as the secondary node of the terminal device (e.g., S-SN120B discussed above), and the second network node may be configured as a candidate target primary node that determines at least one condition for cell addition or change for the terminal device. Assume that the terminal device experiences an SCG failure with the third network node and sends a failure report to the first network node. The first network node may then send the failure report to the OAM entity directly or via the second network node.
[0174] In some example embodiments, the failure report may include a configuration identifier that includes at least one condition for conditional handover and at least one condition for cell addition or modification. For example, the configuration may be a combined conditional handover and conditional PSCell addition or modification configuration. It should be understood that the combined conditional handover and cell addition or modification can only be triggered if both execution conditions are met. The failure report may also include a reason why the conditional handover and cell addition or modification are not triggered based on the configuration. The reason may indicate which of the at least one condition for conditional handover and at least one condition for cell addition or modification was not met, which of the at least one condition for conditional handover and at least one condition for cell addition or modification was met, or both. Therefore, the OAM entity can know from the failure report which condition potentially delayed the execution of the conditional handover and cell addition or modification, and thus caused the SCG to fail.
[0175] In some example embodiments, the failure report may also include additional information to accommodate problematic conditions that could cause the SCG to fail. For example, the failure report may also include at least one of the following: • At least one condition for conditional handover or for cell addition or modification that is not met, such as a threshold and offset parameter for the condition. • Information about the target cell related to the unmet conditions, such as the target cell's Physical Cell Identifier (PCI) and frequency. • The N last measurements of the target cell before the radio link failed, where N is a positive integer. • Information about the source cell related to the unmet conditions, such as the source cell's PCI and frequency. • The N last measurements of the source cell before the radio link failed, or • An indication that the unmet trigger time (TTT) timer is running when the radio link fails.
[0176] Upon receiving a failure report, the OAM entity can determine adaptation information for the unmet conditions indicated in the failure report at step 1520, and send the determined adaptation information to the relevant network node at step 1530. In some example embodiments, the OAM entity can send the adaptation information to a first network node if adaptation information is determined for at least one condition used for handover, or to a second network node if adaptation information is determined for at least one condition used for cell addition or modification. In some other example embodiments, the OAM entity can send the adaptation information to the network node from which it received the failure report, regardless of which condition the adaptation information was determined for.
[0177] Figure 16 This is a schematic block diagram illustrating an exemplary device 1600. Device 1600 may be implemented to include or form at least a part of a terminal device (such as UE 110 discussed above) to perform at least a part of the operations associated with UE 110. Blocks of device 1600 may be implemented using software, hardware, firmware, or any combination thereof.
[0178] refer to Figure 16 The apparatus 1600 may include: a component 1610 for receiving a configuration message from a first network node, the configuration message including at least one condition for conditional handover and at least one condition for cell addition or modification; a component 1620 for evaluating whether the at least one condition for conditional handover and the at least one condition for cell addition or modification are met; a component 1630 for detecting a radio link failure of the connection between the terminal device and the first network node before both at least one condition is met; a component 1640 for establishing a radio connection with a second network node in response to the detected radio link failure; and a component 1650 for sending a failure report to the second network node, the failure report indicating a radio link failure that occurred before both at least one condition was met.
[0179] In some example embodiments, the apparatus 1600 may further include components (not shown) for receiving failure report configuration from the first network node. The failure report configuration may specify the content of the failure report and / or the criteria used to trigger the failure report.
[0180] Figure 17 This is a schematic block diagram illustrating an exemplary device 1700. Device 1700 can be implemented to include or form at least a portion of a second network node (such as T-MN120C or any other base station that UE110 connects to after the radio link failure described above) to perform at least a portion of the operations associated with the second network node. Blocks of device 1700 can be implemented using software, hardware, firmware, or any combination thereof.
[0181] refer to Figure 17 The device 1700 may include means 1710 for establishing a radio connection with a terminal device, and means 1720 for receiving a failure report from the terminal device. In some example embodiments, the failure report may indicate a radio link failure with a first network node that occurred when at least one of at least one condition for conditional handover and at least one condition for cell addition or change was not met.
[0182] In some example embodiments, the apparatus 1700 may also include a third component 1730 for sending failure reports to an Operations Management and Maintenance (OAM) entity or a first network node.
[0183] In some example embodiments, the apparatus 1700 may further include a fourth component 1740 for determining adaptation information for at least one condition for cell addition or modification based on a failure report if at least one condition for cell addition or modification is determined by a second network node and is not met when a radio link failure occurs.
[0184] In some example embodiments, the apparatus 1700 may further include: components (not shown) for receiving adaptation information from an OAM entity for at least one unmet condition for handover or for at least one condition for cell addition or modification; components (not shown) for sending the adaptation information to a first network node if the adaptation information is for at least one unmet condition for handover; or components (not shown) for adapting the adaptation information to at least one condition for cell addition or modification based on the adaptation information if the adaptation information is for at least one unmet condition for cell addition or modification. In some example embodiments, the apparatus 1700 may further include: a component (not shown) for receiving adaptation information from a first network node for at least one unmet condition for cell addition or modification; and a component (not shown) for adapting to at least one condition for cell addition or modification based on the adaptation information.
[0185] In some example embodiments, the apparatus 1700 may further include components (not shown) for sending a failure report configuration to a first network node before establishing a radio connection with the terminal device. The failure report configuration may specify the content of the failure report and / or the criteria used to trigger the failure report.
[0186] Figure 18 This is a schematic block diagram illustrating an exemplary device 1800. Device 1800 may be implemented to include or form at least a portion of a first network node (such as the S-MN120A discussed above) to perform at least a portion of operations associated with the S-MN120A. Blocks of device 1800 may be implemented using software, hardware, firmware, or any combination thereof.
[0187] refer to Figure 18 The apparatus 1800 may include a component 1810 for sending a configuration message to a terminal device, the configuration message including at least one condition for conditional handover and at least one condition for cell addition or modification, and a component 1820 for receiving a failure report from a second network device. The failure report may indicate a radio link failure between the terminal device and the first network node that occurred when at least one of the conditions for conditional handover and the condition for cell addition or modification was not met.
[0188] In some example embodiments, the apparatus 1800 may further include a component 1830 for sending a failure report to an Operations Management and Maintenance (OAM) entity, or a component 1840 for determining adaptation information for at least one condition of a condition switch if the failure report indicates that at least one condition of a condition switch is not met.
[0189] Figure 19 This is a schematic block diagram illustrating an exemplary device 1900. Device 1900 may be implemented to include or form at least a part of an Operation Management and Maintenance (OAM) entity (such as OAM140 discussed above) to perform at least a part of the operations associated with OAM140. Blocks of device 1900 may be implemented using software, hardware, firmware, or any combination thereof.
[0190] Reference Figure 19The apparatus 1900 may include a component 1910 for receiving a failure report from a first network node or a second network device. The failure report may indicate a radio link failure between the terminal device and the first network node when at least one of at least one condition for conditional handover and at least one condition for cell addition or change is not met.
[0191] In some example embodiments, the apparatus 1900 may further include a component 1920 for determining adaptation information for at least one condition for condition handover or for at least one condition for cell addition or change that is not met.
[0192] In some example embodiments, the apparatus 1900 may further include a component 1930 for sending adaptation information to relevant network nodes. For example, component 1930 may send adaptation information to a first network node if adaptation information is determined for at least one condition for adjusting handover that is not met, send adaptation information to a second network node if adaptation information is determined for at least one condition for adding or changing a cell that is not met, or send adaptation information to a network node from which it receives a failure report, regardless of which condition the adaptation information is determined for.
[0193] Figure 20 This is a schematic block diagram illustrating an exemplary device 2000. Device 2000 may be implemented to include or form at least a part of a terminal device (such as UE 110 discussed above) to perform at least a part of operations associated with UE 110. Blocks of device 2000 may be implemented using software, hardware, firmware, or any combination thereof.
[0194] Reference Figure 20 The apparatus 2000 may include: a component 2010 for receiving from a first network node a configuration message including at least one condition for conditional handover and at least one condition for cell addition or change; a component 2020 for evaluating whether at least one condition for conditional handover and at least one condition for cell addition or change are met; a component 2030 for detecting a connection failure with a third network node before both of the at least two conditions are met; and a component 2040 for sending a failure report to the first network node indicating a connection failure that occurred before both of the at least two conditions were met.
[0195] In some example embodiments, the apparatus 2000 may further include components (not shown) for receiving failure report configuration from a first network node. The failure report configuration may specify the content of the failure report and / or the criteria used to trigger the failure report.
[0196] Figure 21This is a schematic block diagram illustrating an exemplary device 2100. Device 2100 can be implemented to include or form at least a portion of a second network node (such as the T-MN120C discussed above) to perform at least a portion of the operations associated with the T-MN120C. Blocks of device 2100 can be implemented using software, hardware, firmware, or any combination thereof.
[0197] Reference Figure 21 The apparatus 2100 may include: a component 2110 for sending at least one condition for cell addition or modification to a first network node; and a component 2120 for receiving a failure report from the first network node. The failure report may indicate a connection failure that occurred between the terminal device and the third network node when at least one condition for cell addition or modification was not met.
[0198] In some example embodiments, the apparatus 2100 may further include: a component 2130 for sending a failure report to an Operations Management and Maintenance (OAM) entity, or a component 2140 for determining adaptation information for at least one condition for cell addition or modification.
[0199] In some example embodiments, the apparatus 2100 may further include: a component (not shown) for receiving adaptation information from an OAM entity for at least one condition for cell addition or modification; and a component (not shown) for adapting the adaptation information to at least one condition for cell addition or modification.
[0200] In some example embodiments, apparatus 2100 may further include a component (not shown) for sending a failure report configuration to the first network node before component 2120 receives the failure report. For example, the failure report configuration may specify the content of the failure report and / or the criteria used to trigger the failure report.
[0201] Figure 22 This is a schematic block diagram illustrating an exemplary device 2200. Device 2200 can be implemented to include or form at least a portion of a first network node (such as the S-MN120A discussed above) to perform at least a portion of the operations associated with the S-MN120A. Blocks of device 2200 can be implemented using software, hardware, firmware, or any combination thereof.
[0202] refer to Figure 22The apparatus 2200 may include a component 2210 for sending a configuration message to a terminal device, the configuration message including at least one condition for handover and at least one condition for cell addition or modification, and a component 2220 for receiving a failure report from the terminal device. The failure report may indicate a connection failure occurring between the terminal device and a third network node when at least one of the conditions for handover and cell addition or modification is not met.
[0203] In some example embodiments, the apparatus 2200 may further include a component 2230 for sending a failure report to an Operations Management and Maintenance (OAM) entity, or, if at least one condition for cell addition or modification is not met, sending a failure report to a second network node that determines at least one condition for cell addition or modification.
[0204] In some example embodiments, the apparatus 2200 may further include a component 2240 for determining adaptation information for at least one condition for condition switching in the event that at least one condition for condition switching is not met.
[0205] In some example embodiments, the apparatus 2200 may further include: components for receiving adaptation information from an OAM entity for at least one condition for handover or for at least one unmet condition for cell addition or modification; components (not shown) for sending the adaptation information to a second network node if the adaptation information is for at least one condition for cell addition or modification; and components (not shown) for adapting the at least one condition for handover based on the adaptation information if the adaptation information is for at least one condition for handover.
[0206] In some example embodiments, apparatus 2200 may further include components for sending failure report configuration to a terminal device. In example embodiments, the failure report may specify the content of the failure report and / or the criteria used to trigger the failure report. The failure report configuration may be determined by a first network node or received from a second network node.
[0207] Figure 23 This is a schematic block diagram illustrating an exemplary device 2300. Device 2300 may be implemented to include or form at least a part of an Operation Management and Maintenance (OAM) entity (such as OAM140 discussed above) to perform at least a part of the operations associated with OAM140. Blocks of device 2300 may be implemented using software, hardware, firmware, or any combination thereof.
[0208] Reference Figure 23The apparatus 2300 may include a component 2310 for receiving a failure report from a first network node or a second network device. The failure report may indicate a connection failure occurring between the terminal device and the third network node when at least one of at least one condition for conditional handover and at least one condition for cell addition or change is not met.
[0209] The apparatus 2300 may further include: a component 2320 for determining adaptation information for at least one unmet condition for handover or at least one unmet condition for cell addition or modification; and a component 2330 for sending the adaptation information to the relevant network node. For example, component 2330 may send the adaptation information to a first network node if adaptation information is determined for at least one unmet condition for handover, send the adaptation information to a second network node if adaptation information is determined for at least one unmet condition for cell addition or modification, or send failure information to the first network node because a failure report is received from the first network node, regardless of whether at least one condition for handover or at least one condition for cell addition or modification is unmet.
[0210] Figure 24A Example terminal device 2410 is shown. Figure 24B An example radio access network (RAN) device 2420 is shown, and Figure 24C Example Operations Management and Maintenance (OAM) device 2430 is shown.
[0211] refer to Figure 24A Terminal device 2410 may include one or more processors 2411, one or more memories 2412, and one or more transceivers 2413 interconnected via one or more buses 2414. The one or more buses 2414 may be address, data, or control buses and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, optical fibers, optics, or other optical communication devices. Each of the one or more transceivers 2413 may include a receiver and a transmitter connected to one or more antennas 2416. Terminal device 2410 may wirelessly communicate with RAN device 2420 via one or more antennas 2416. The one or more memories 2412 may include instructions 2415 that, when executed by one or more processors 2411, cause terminal device 2410 to perform operations related to UE 110 as described above.
[0212] refer to Figure 24BRAN device 2420 may include one or more processors 2421, one or more memories 2422, one or more transceivers 2423, and one or more network interfaces 2427 interconnected via one or more buses 2424. The one or more buses 2424 may be address, data, or control buses and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, optical fibers, optics, or other optical communication devices. Each of the one or more transceivers 2423 may include a receiver and a transmitter connected to one or more antennas 2426. RAN device 2420 may operate as a master node, slave node, candidate master node, or candidate slave node of terminal device 2410 in dual-connectivity mode, or as a single serving base station of terminal device 2410 in single-connectivity mode. RAN device 2420 may wirelessly communicate with terminal device 2410 via one or more antennas 2426. One or more network interfaces 2427 may provide wired or wireless communication links through which RAN device 2420 may communicate with other network devices, entities, components, or functions. For example, RAN device 2420 can communicate with OAM device 2430 via a wired or wireless connection and with the core network (not shown) via a backhaul connection. One or more memories 2422 may include instructions 2425, which, when executed by one or more processors 2421, can cause RAN device 2420 to perform operations related to any of the base stations 120 as described above.
[0213] refer to Figure 24C The OAM device 2430 may include one or more processors 2431, one or more memories 2432, and one or more network interfaces 2437 interconnected via one or more buses 2434. The one or more buses 2434 may be address, data, or control buses and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, optical fibers, optics, or other optical communication devices. The one or more network interfaces 2437 may provide wired or wireless communication links through which the OAM device 2430 can communicate with other network devices, entities, components, or functions. In some example embodiments, the OAM device 2430 may be connected directly or via a core network (not shown) to the RAN device 2420. The one or more memories 2432 may include instructions 2435, which, when executed by one or more processors 2431, cause the OAM device 2430 to perform operations and processes related to the OAM entity 140 as described above.
[0214] The one or more processors 2411, 2421, and 2431 discussed above can be any suitable type for the local technology network and can include one or more processors from general-purpose processors, dedicated processors, microprocessors, digital signal processors (DSPs), processor-based multi-core processor architectures, and dedicated processors (such as those developed based on field-programmable gate arrays (FPGAs) and application-specific integrated circuits (ASICs). The one or more processors 2411, 2421, and 2431 can be configured to control other elements of the terminal / RAN / core network equipment and cooperate with them to implement the processes discussed above.
[0215] One or more memories 2412, 2422, and 2432 may include at least one storage medium of various forms, such as transient and / or non-transient memory. Transient memory may include, but is not limited to, random access memory (RAM) or cache. Non-transient memory may include, but is not limited to, read-only memory (ROM), hard disk, flash memory, etc. As used herein, the term "non-transient" is a limitation on the medium itself (i.e., tangible, not tactile), rather than a limitation on the persistence of data storage (e.g., RAM and ROM). Furthermore, one or more memories 2412, 2422, and 2432 may include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or apparatuses, or any combination thereof.
[0216] It should be understood that the boxes in the figures can be implemented in various ways, including software, hardware, firmware, or any combination thereof. In some embodiments, one or more boxes may be implemented using software and / or firmware (e.g., machine-executable instructions stored in a storage medium). In addition to or in lieu of machine-executable instructions, some or all of the boxes in the figures may be implemented at least partially by one or more hardware logic components. Examples, but not limited to, illustrative types of hardware logic components that may be used include field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-chip systems (SOCs), complex programmable logic devices (CPLDs), etc. Some example embodiments also provide one or more program instructions that, when executed by one or more processors, cause a device or apparatus to perform the processes described above. The program instructions for performing the processes of the example embodiments can be written in any combination of one or more programming languages. The program instructions can be provided to one or more processors or controllers of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that, when executed by the processor or controller, the program instructions cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program instructions can be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.
[0217] Some example embodiments also provide a computer program product or computer-readable medium in which one or more program instructions are stored. A computer-readable medium can be any tangible medium that can contain or store a program used by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. More specific examples of machine-readable storage media will include electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.
[0218] As used herein, “at least one of the following: a list of two or more elements” and “at least one of the following: a list of two or more elements” and similar wording (where the list of two or more elements is connected by “and” or “or”) means at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.
[0219] Furthermore, although the operations are described in a specific order, this should not be construed as requiring that such operations be performed in the specific order shown or sequentially, or that all the operations shown be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, while the foregoing discussion contains details of several specific embodiments, these details should not be construed as limiting the scope of the invention, but rather as descriptions of features that may be specific to particular embodiments. Certain features described in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.
[0220] Throughout this disclosure, references to "one embodiment," "embodiment," "some embodiments," "other embodiments," etc., indicate that one or more specific features, structures, steps, concepts, and / or characteristics based on the principles of this disclosure may be included in that embodiment. However, such references do not necessarily imply that all embodiments include the specific features, structures, steps, concepts, and / or characteristics, or that an embodiment includes all features, structures, steps, concepts, and / or characteristics. Some embodiments may include one or more such features, structures, steps, concepts, and / or characteristics in various combinations thereof. It should be understood that one or more of the features, structures, steps, concepts, and / or characteristics described with reference to one embodiment may be combined with one or more of the features, structures, steps, concepts, and / or characteristics of any other embodiment provided herein. That is, any features, structures, steps, concepts, and / or characteristics described herein may be mixed and matched to create hybrid embodiments, and such hybrid embodiments are within the scope of this disclosure. Furthermore, references to "one embodiment," "embodiment," "some embodiments," "other embodiments," etc., in various places in the specification do not necessarily refer to the same embodiment, nor are they necessarily separate or alternative embodiments that are mutually exclusive with other embodiments. It should also be understood that the various features, structures, steps, concepts, and / or characteristics of the disclosed embodiments are independent and separate from each other, and may be used or present individually or in various combinations thereof to create alternative embodiments that are considered part of this disclosure. Therefore, this disclosure is not limited to the embodiments specifically described herein, as describing all the many possible combinations and sub-combinations of features, structures, steps, concepts, and / or characteristics would be too cumbersome, and the examples of embodiments disclosed herein are not intended to limit the broader aspects of this disclosure.
[0221] Although the subject matter has been described in language specific to structural features and / or methodological actions, it should be understood that the subject matter defined in the appended claims is not limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as examples of implementing the claims.
Claims
1. An apparatus comprising: At least one processor; as well as At least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the device to at least: The terminal device receives a configuration message from the first network node, the configuration message including at least one condition for conditional handover and at least one condition for cell addition or modification; Evaluate whether at least one condition for the conditional handover and at least one condition for the cell addition or change are met; The radio link for detecting the connection between the terminal device and the first network node fails until at least one of the two conditions is met. In response to the detected radio link failure, a radio connection is established with the second network node; as well as A failure report is sent to the second network node, the failure report indicating that the radio link failure occurred before at least one of the two conditions is met.
2. The apparatus of claim 1, wherein the apparatus is configured to: Receive a failure report configuration from the first network node, the failure report configuration specifying at least one of the following: The content of the failure report; or The criteria used to trigger the failure report.
3. The apparatus of claim 2, wherein the criteria for triggering the failure report include: When the radio link failure is detected, at least one of the at least one condition for the condition switching and at least one condition for the cell addition or change is not met.
4. The apparatus according to any one of claims 1 to 3, wherein the failure report comprises: Including the identifier of the configuration for the at least one condition used for the conditional handover and for the at least one condition used for adding or changing the cell, and The reason why the conditional handover and the addition or change of the cell are not triggered based on the configuration is as follows.
5. The apparatus of claim 4, wherein the reason for not triggering the conditional handover and the cell addition or change indicates at least one of the following: When the radio link failure is detected, which of the at least one condition for the conditional handover and the at least one condition for the cell addition or change is not met? When the radio link failure is detected, which of the at least one condition for the condition switching and the at least one condition for the cell addition or change is satisfied? 6. The apparatus of claim 4 or 5, wherein the failure report further comprises at least one of the following: At least one condition for the conditional handover or at least one condition for the cell addition or change that was not met when the radio link failure was detected. Information about the target cell, which is associated with at least one condition for the conditional handover or for adding or changing the cell that was not met when the radio link failure was detected. For the N final measurements of the target cell, where N is a positive integer, Information about the source cell, which is associated with at least one condition for the conditional handover or for adding or changing the cell that was not met when the radio link failure was detected. For the N last measurements of the source cell, or An indication that, when the radio link failure is detected, a trigger timer for at least one condition for the condition switching or for at least one condition for the cell addition or change is running and has not been met.
7. An apparatus comprising: At least one processor; as well as At least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the device to at least: A radio connection is established between the second network node and the terminal device; The terminal device receives a failure report indicating that a radio link failure with the first network node occurs when at least one of the following conditions is not met: at least one condition for conditional handover and at least one condition for cell addition or change. as well as Perform one of the following: Send the failure report to the operations management and maintenance entity. Send the failure report to the first network node, or If the at least one condition for adding or changing the cell is determined by the second network node and is not met when the radio link failure occurs, adaptation information is determined for the at least one condition for adding or changing the cell based on the failure report.
8. The apparatus of claim 7, wherein the apparatus is configured to: Before establishing the radio connection with the terminal device, a failure report configuration is sent to the first network node, the failure report configuration specifying at least one of the following: The content of the failure report; or The criteria used to trigger the failure report.
9. The apparatus of claim 7 or 8, wherein the failure report comprises: The configured identifier, the configuration including at least one condition for the conditional handover and at least one condition for adding or changing the cell, and The reason why the conditional handover and the addition or change of the cell are not triggered based on the configuration is as follows.
10. The apparatus of claim 9, wherein the reason for not triggering the conditional handover and the cell addition or change indicates at least one of the following: When the radio link failure occurs, which of the at least one condition for the conditional handover and the at least one condition for the cell addition or change is not met? When a radio link failure occurs, which of the at least one condition for the conditional handover and the at least one condition for the cell addition or change is satisfied? 11. The apparatus according to any one of claims 7 to 10, wherein, when the failure report is sent to the operation management and maintenance entity, the apparatus is configured to: Receive from the operation management and maintenance entity adaptation information for at least one unmet condition for the conditional handover or for the cell addition or modification; and In the case where the adaptation information is for at least one condition used for the condition switching that has not been met, Send the adaptation information to the first network node, or In the case where the adaptation information is for at least one condition for adding or changing the cell that has not been met. The adaptation information is used to adapt to at least one condition for adding or changing the cell.
12. The apparatus according to any one of claims 7 to 11, wherein, when the failure report is sent to the first network node, the apparatus is configured to: Receive adaptation information from the first network node for at least one unmet condition for adding or changing the cell; and The adaptation information is used to adapt to at least one condition for adding or changing the cell.
13. An apparatus comprising: At least one processor; as well as At least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the device to at least: The first network node sends a configuration message to the terminal device, the configuration message including at least one condition for conditional handover and at least one condition for cell addition or change; A failure report is received from a second network device, the failure report indicating a radio link failure between the terminal device and the first network node when at least one of the at least one condition for the condition switching and the at least one condition for the cell addition or change is not met; as well as Perform one of the following: Send the failure report to the operations management and maintenance entity, or If the failure report indicates that at least one condition for the condition switching is not met, adaptation information is determined for the at least one condition for the condition switching.
14. The apparatus of claim 13, wherein the apparatus is configured to: Send a failure report configuration to the terminal device, wherein the failure report configuration specifies at least one of the following: The content of the failure report; The criteria used to trigger the failure report The failure report configuration is determined by the first network node or received from the second network node.
15. The apparatus of claim 13 or 14, wherein, in the event of sending the failure report to the operation management and maintenance entity, the apparatus is configured to: Receive from the operation management and maintenance entity adaptation information for at least one unmet condition for the conditional handover or for the cell addition or modification; and In the case where the adaptation information is for at least one condition for adding or changing the cell that has not been met. Send the adaptation information to the second network node, or In the case where the adaptation information is for at least one condition used for the condition switching that has not been met, The adaptation information is used to adapt at least one condition for the condition switching.
16. An apparatus comprising: At least one processor; as well as At least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the device to at least: The operation management and maintenance entity receives a failure report from a first network node or a second network node, the failure report indicating a radio link failure between the terminal device and the first network node when at least one of at least one condition for condition handover and at least one condition for cell addition or change is not met; Adaptation information is determined for at least one condition for the conditional handover that is not met, or for at least one condition for adding or changing the cell. as well as The adaptation information: If the adaptation information is determined for at least one condition used for the condition switching that has not been met, it is sent to the first network node. If the adaptation information is determined in response to at least one unmet condition for adding or changing the cell, it is sent to the second network node, or Send it to the first network node or the second network node from which it receives the failure report.
17. A method comprising: The terminal device receives a configuration message from the first network node, the configuration message including at least one condition for conditional handover and at least one condition for cell addition or modification; Evaluate whether at least one condition for the conditional handover and at least one condition for the cell addition or change are met; The radio link for detecting the connection between the terminal device and the first network node fails until both of at least one of the conditions are met. In response to the detected radio link failure, a radio connection is established with the second network node; as well as A failure report is sent to the second network node, the failure report indicating that the radio link failure occurred before at least one of the two conditions is met.
18. The method of claim 17, further comprising: Receive a failure report configuration from the first network node, the failure report configuration specifying at least one of the following: The content of the failure report; or The criteria used to trigger the failure report.
19. A method comprising: A radio connection is established between the second network node and the terminal device; The terminal device receives a failure report indicating a radio link failure with the first network node that occurred when at least one of at least one condition for condition handover and at least one condition for cell addition or change was not met. as well as Perform one of the following: Send the failure report to the operations management and maintenance entity. Send the failure report to the first network node, or If the at least one condition for adding or changing the cell is determined by the second network node and is not met when the radio link failure occurs, adaptation information for the at least one condition for adding or changing the cell is determined based on the failure report.
20. The method of claim 19, further comprising: Before establishing the radio connection with the terminal device, a failure report configuration is sent to the first network node, the failure report configuration specifying at least one of the following: The content of the failure report; or The criteria used to trigger the failure report.
21. The method according to claim 19 or 20, further comprising: When the failure report is sent to the operations management and maintenance entity. Receive adaptation information from the operation management and maintenance entity for at least one condition for the condition switching that has not been met or for the cell addition or change. as well as If the adaptation information pertains to at least one unmet condition for the conditional handover, the adaptation information is sent to the first network node; or if the adaptation information pertains to at least one unmet condition for the cell addition or modification, the adaptation information is used to adapt to the at least one condition for the cell addition or modification. When the failure report is sent to the first network node Receive adaptation information from the first network node for at least one unmet condition for adding or changing the cell; and The adaptation information is used to adjust at least one condition for adding or changing the cell.
22. A method comprising: The first network node sends a configuration message to the terminal device, the configuration message including at least one condition for conditional handover and at least one condition for cell addition or change; A failure report is received from a second network device, the failure report indicating a radio link failure between the terminal device and the first network node when at least one of the at least one condition for the condition switching and the at least one condition for the cell addition or change is not met; as well as Perform one of the following: Send the failure report to the operations management and maintenance entity, or If the failure report indicates that at least one condition for the condition switching is not met, adaptation information for the at least one condition for the condition switching is determined.
23. A method comprising: The operation management and maintenance entity receives a failure report from a first network node or a second network device, the failure report indicating a radio link failure between the terminal device and the first network node when at least one of at least one condition for condition handover and at least one condition for cell addition or change is not met; For at least one condition for the conditional handover that is not met, or for the cell addition or modification that is not met, adaptation information is determined; as well as The adaptation information: If the adaptation information is determined for at least one condition used for the condition switching that has not been met, it is sent to the first network node. If the adaptation information is determined in response to at least one unmet condition for adding or changing the cell, it is sent to the second network node, or Send it to the first network node or the second network node from which it receives the failure report.
24. An apparatus comprising components for performing the method according to any one of claims 17 to 23.
25. A computer-readable medium comprising instructions that, when executed by a device, cause the device to perform the method according to any one of claims 17 to 23.
