Methods and apparatus for handling radio link failures (RLF) in wireless communication networks

By successfully configuring PSCell in the wireless communication network and using SRB3 for threshold optimization, the handover delay and signaling overhead issues in RLF and dual-connectivity scenarios were resolved, achieving efficient RLF recovery and self-optimization, and improving network mobility performance.

CN123077192APending Publication Date: 2026-11-10SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202580026248.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2024-04-29
Filing Date
2025-03-31
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

Existing technologies cannot effectively handle radio link failures (RLF) in wireless communication networks, especially in dual-connectivity scenarios. They cannot optimize T310 and T312 thresholds during handover and conditional handover, resulting in signaling overhead and latency issues, and inconsistencies between UE and network successful handover reports.

Method used

By configuring successful PSCell configuration in the user equipment (UE), it determines whether to retain or release relevant parameters during RLF, utilizes Signaling Radio Bearer 3 (SRB3) for threshold configuration and successful handover reporting, supports low-level mobility (LTM) handover, and optimizes T310 and T312 thresholds to reduce latency and signaling overhead.

Benefits of technology

It achieves efficient handover and self-optimization under RLF conditions, reduces signaling overhead and latency, ensures consistency in successful handover reports between the UE and the network, and improves the mobility performance of the wireless communication network.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123077192A_ABST
    Figure CN123077192A_ABST
Patent Text Reader

Abstract

This disclosure relates to 5G or 6G communication systems for supporting higher data transmission rates. The embodiments disclosed herein relate to wireless communication networks, and there is a need for efficient and effective methods and systems for handling radio link failure (RLF) recovery in wireless communication networks.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments disclosed herein relate to wireless communication networks, and more specifically to methods and systems for handling radio link failure (RLF) recovery in wireless communication networks. Background Technology

[0002] 5G mobile communication technology defines a wide frequency band, enabling high transmission rates and new services. It can be implemented not only in "sub-6GHz" bands such as 3.5GHz, but also in "above 6GHz" bands, including 28GHz and 39GHz, known as mmWave. Furthermore, 6G mobile communication technology (referred to as "super 5G systems") is being considered in terahertz bands (e.g., the 95GHz to 3THz band) to achieve transmission rates fifty times faster than 5G and ultra-low latency one-tenth that of 5G.

[0003] At the outset of 5G mobile communication technology development, standardization was underway regarding beamforming and massive MIMO to support services and meet performance requirements associated with enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC). This standardization aimed to mitigate radio wave path loss in millimeter waves and increase radio wave transmission distance, support parameter sets for dynamic operation (e.g., operating multiple subcarrier spacings) to efficiently utilize millimeter wave resources and time slot formats, initial access technologies to support multi-beam transmission and broadband, the definition and operation of BWP (bandwidth portion), new channel coding methods such as LDPC (low-density parity-check) codes for large-volume data transmission and polar codes for highly reliable transmission of control information, L2 preprocessing, and network slicing for providing dedicated networks for specific services.

[0004] Currently, given the services that 5G mobile communication technology needs to support, discussions are underway regarding improvements and performance enhancements to the initial 5G mobile communication technology. Physical layer standardization already exists for technologies such as V2X (Vehicle-to-Everything), NR-U (New Radio Unlicensed), NR UE Power Saving, Non-Terrestrial Network (NTN), and positioning. V2X is used to assist autonomous vehicles in making driving decisions and enhancing user convenience based on vehicle location and status information transmitted by the vehicle. NR-U aims to comply with system operations related to various regulations in unlicensed frequency bands. NR UE Power Saving and Non-Terrestrial Network (NTN) are UE-satellite direct communication used to provide coverage in areas where communication with terrestrial networks is impossible.

[0005] In addition, standardization is underway for air interface architectures / protocols such as those for supporting new services through interoperability and convergence with other industries in the Industrial Internet of Things (IIoT); for providing nodes for network service area extension by supporting wireless backhaul and access links in an integrated manner; mobility enhancements including conditional handover and DAPS (Dual Active Stack) handover; and for two-step random access (2-step RACH for NR) to simplify the random access process. Standardization is also underway for 5G baseline architectures (e.g., service-based architectures or service-based interfaces) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and for system architectures / services for Mobile Edge Computing (MEC) based on UE location reception services.

[0006] With the commercialization of 5G mobile communication systems, the already exponentially growing number of connected devices will be connected to communication networks, thus necessitating enhanced functionality and performance of 5G mobile communication systems, as well as integrated operation of connected devices. To this end, new research has been arranged related to: extended reality (XR) for efficient support of AR, VR, MR, etc.; 5G performance improvements and complexity reductions through the utilization of artificial intelligence (AI) and machine learning (ML); AI service support; metaverse service support; and drone communications.

[0007] Furthermore, this development of 5G mobile communication systems will serve as the foundation for not only developing new waveforms and multi-antenna transmission technologies (such as full-dimensional MIMO (FD-MIMO), array antennas, and large antennas) for providing terahertz band coverage for 6G mobile communication technologies, metamaterial-based lenses and antennas for improving terahertz band signal coverage, high-dimensional spatial multiplexing technologies using OAM (orbital angular momentum), and RIS (reconfigurable smart surfaces), but also for improving the frequency efficiency of 6G mobile communication technologies and full-duplex technologies for improving system networks, AI-based communication technologies for system optimization by leveraging satellites and AI (artificial intelligence) from the design stage and internalizing end-to-end AI support capabilities, and next-generation distributed computing technologies for providing services with complexity exceeding the operational limits of UEs by utilizing ultra-high-performance communication and computing resources.

[0008] Fifth-generation (5G), or new radio (NR) mobile communications, is gaining increasing momentum recently amid global technological activity surrounding a wide range of candidate technologies from industry and academia. Candidate enablers for 5G / NR mobile communications include massive MIMO technology, from traditional cellular bands to higher frequencies, to provide beamforming gain and support increased capacity; new waveforms (e.g., new radio access technologies (RAT)) to flexibly adapt to a variety of services / applications with varying needs; new multiple access schemes to support massive connectivity, and more.

[0009] In wireless technologies like 5G New Radio (NR), devices can move between different cells. Mobility is performed using a process called cell reselection in RRC_IDLE mode. Prior to NR Release 17, mobility in RRC_CONNECTED mode was managed by a process called handover. Network-controlled mobility applies to user equipment (UE) in RRC_CONNECTED mode and requires explicit Radio Resource Control (RRC) signaling triggered by the gNB (or gNodeB) in NR. Handover in NR consists of three steps: handover preparation, handover execution, and handover completion. The gNB can configure the UE to report measurements, and based on the reported measurements or based on the network topology, the gNB will send an RRC reconfiguration message to hand over the UE from the source cell to another cell, called the target cell. The UE accesses the target cell and sends an RRC reconfiguration completion message.

[0010] An alternative approach was introduced in 3GPP NR Release 16, where the gNB can configure the execution conditions for triggering handover for the UE. Once the execution conditions are met, the UE can move to the target cell and send an RRC reconfiguration completion message. 3GPP introduced a new handover method called DAPS handover in Release 16. In all these methods, the UE performs the handover by sending a Layer 3 (RRC) message, resulting in considerable signaling overhead and latency issues. We can refer to handover and conditional handover (CHO) as Layer 3 mobility. During handover, the UE can be configured to apply a full configuration during L3 handover, and if configured, the UE applies the full configuration as described in Clause 5.3.5.11 of TS 38.331 in the case of dual connectivity. This patent application refers to handover and conditional handover (CHO) as Layer 3 mobility. 3GPP Release 18 also introduced lower-layer (L1 / L2) triggered mobility, also known as LTM.

[0011] NG-RAN supports Multiple Radio Dual Connectivity (MR-DC) operation, whereby user equipment (UE) in RRC_CONNECTED mode is configured to utilize radio resources provided by two different schedulers located in two different NG-RAN nodes via a non-ideal backhaul connection. One node provides NR access, while the other provides either Evolved UMTS Terrestrial Radio Access (E-UTRA) or NR access. One node acts as the primary node (MN), and the other acts as the secondary node (SN). The MN and SN are connected via a network interface, and at least the MN is connected to the core network.

[0012] NG-RAN supports NG-RAN E-UTRA-NR dual connectivity (NGEN-DC), where the UE connects to an ng-eNB (an E-UTRA base station capable of connecting to the 5G core) acting as the MN and a gNB (a 5G base station) acting as the SN. NG-RAN also supports NR-E-UTRA dual connectivity (NE-DC), where the UE connects to a gNB acting as the MN and an ng-eNB acting as the SN. The MN can move the SCG (Secondary Cell Group) to different states, such as deactivated or activated. When carrier aggregation is supported, the secondary cell can also move between deactivated and activated states. When a radio link failure occurs in the SCG, the UE sends an RRC message SCGFailureInformation.

[0013] Primary SCG cell (PSCell) change can occur due to mobility and may or may not involve secondary node change (SN change). The secondary node change process can be initiated by the MN or SN and is used to transfer the UE context from the source SN to the target SN, while updating the SCG configuration in the UE.

[0014] Conditional PSCell Change (CPC) is defined as a PSCell change performed by the UE when specific execution conditions are met. The UE can be configured with execution conditions and, when they are met, executes an RRC message (e.g., RRC reconfiguration) for one or more candidate cells. The UE begins evaluating the execution conditions upon receiving the CPC configuration and stops evaluating once a PSCell change is triggered. Intra-SN CPCs without MN participation and inter-SN CPCs initiated by the MN or SN are supported. The MN adds a PSCell during the PSCell addition process. A PSCell addition process that is performed only when the PSCell addition conditions are met is called Conditional PSCell Addition (CPA).

[0015] The UE can perform either PSCellChange or Conditional PSCellChange. In the context of dual connectivity, PSCellChange or Conditional PSCellChange can also be referred to as Layer 3 mobility. That is, handover, conditional handover, PSCell change, and conditional PSCell change all refer to L3 mobility. In the context of dual connectivity, PSCellChange or Conditional PSCellChange can be referred to as SCG Layer 3 mobility, and handover and CHO can be referred to as MCG Layer 3 mobility. The UE can be configured to have the network device apply conditional configuration using a flag after a radio link failure. In NR, the network configures the attemptCondReconfig flag for the UE. If this flag is configured, the UE will perform conditional reconfiguration after selecting a cell following a radio link failure if the selected cell is the target candidate cell and it is the first cell selection after the failure.

[0016] The 3GPP Release 18 is considering lower-layer (L1 / L2) triggered mobility (LTM), referred to as LTM, to address issues related to latency, signaling overhead, and other factors associated with Layer 3 mobility. According to 3GPP, LTM is used to implement serving cell changes via L1 / L2 signaling to reduce latency, overhead, and downtime. The network (gNB) can configure multiple candidate cells for the UE to allow for rapid application of candidate cell configurations. The network can also send Media Access Control-Control Element (MAC CE) or L1 signaling to dynamically switch the UE from the source cell to one of the configured candidate cells. Furthermore, LTM can be triggered based on L1 measurements instead of L3 measurements.

[0017] 3GPP proposed implementing LTM without resetting lower layers such as MAC to avoid data loss and minimize additional latency in data recovery.

[0018] The gNB CU can provide LTM CandidateConfiguration, which configures LTM candidate cells via an RRCReconfiguration message for the candidate target cell. The gNB can further release or modify candidate configurations. Even after moving to a candidate cell via LTM, the UE can store the LTM configurations of other candidate cells. The gNB CU can provide the UE with configurations for performing LTM measurements on different candidate frequencies and candidate cells and reporting based on the performed LTM measurements. The gNB can further release or modify candidate configurations. Even after moving to a candidate cell via LTM, the UE can store the LTM configurations of other candidate cells. The gNB can also provide the UE with configurations for performing LTM measurements on different candidate frequencies and candidate cells and reporting based on the performed LTM measurements. 3GPP supports subsequent LTM, meaning that after an LTM candidate cell becomes a source cell due to LTM, the UE can store the LTM candidate configuration and continue reporting LTM measurements (i.e., L1 measurements for LTM), and the new serving cell can send an LTM cell handover command to the UE, and the UE performs LTM; this type of LTM is called subsequent LTM. The UE can be configured to have the network device apply an LTM candidate configuration using a flag after a radio link failure. In NR, the network configures the attemptLTM-Switch flag for the UE. If this flag is configured, the UE will perform an LTM cell handover after selecting a cell following the radio link failure, provided that the selected cell is the target candidate cell and it is the first cell selection after the failure.

[0019] The UE performs L1 measurements on the source cell and candidate cells to report the L1 measurements to the gNBDU of the source cell via a CSI report. The gNBDU may send a MAC CE requesting the UE to hand over to another cell that is an LTM candidate cell (e.g., LTM MACCE or cell handover MAC CE). The UE may perform random access during LTM cell handover, or the cell handover may be RACH-free. The CellSwitch may be protected by a timer (called T3xx).

[0020] The gNB can request the UE to perform random access on candidate cells before cell handover, allowing the network to calculate timing advance before the handover and notify the UE via a random access response or within a MAC CE sent for cell handover. The gNB can configure the UE to perform random access on one or more LTM candidate cells to receive timing advance (TA) before cell handover (referred to as early TA, early synchronization TA, or TA for early synchronization). Random access performed on LTM candidate cells for timing advance reception is called random access for early TA. The gNB sends a Physical Downlink Control Channel (PDCCH) command to initiate a Random Access Channel (RACH) for TA measurement on candidate cells. The UE receives the PDCCH command from the serving cell. Upon receiving the PDCCH command, the UE initiates a RACH for TA measurement on one or more candidate cells. The UE sends a RACH preamble to the candidate cells and receives the timing advance (TA) value from the candidate cells. The TA for the candidate cells can also be received from the source cell. Typically, the TA is received in the random access response, but it can also be received via a MAC CE. If the source DU instructs the UE to retransmit the RACH used for early TA, the UE retransmits the RACH. The gNB can also send a PDCCH command to retransmit the RACH used for TA measurements (also known as the RACH used for early synchronization).

[0021] In conventional methods, the UE's MAC reset and configuration processing when attemptCondReconfig or attemptLTM-Switch is configured are not disclosed. Therefore, the UE's processing using successPSCell-Config (i.e., the configuration used by the UE to report successful PSCell changes or additions to the network) when attemptCondReconfig or attemptLTM-Switch is configured is not disclosed. As a result, the UE and network will be out of sync regarding successPSCell-Config. The UE's ability to report RACH commands regarding PDCCH is not disclosed.

[0022] Furthermore, the 5G NR (New Radio) radio access network, also known as NG-RAN (Next Generation Radio Network), comprises multiple NR base stations (i.e., gNBs). gNBs can connect to each other via the Xn interface and will connect to various core network elements such as AMF (Access and Mobility Management Functions), UPF (User Plane Functions), etc. Additionally, gNBs can be divided into two physical entities: CU (Centralized Unit) and DU (Distributed Unit). The CU provides support for higher layers of the protocol stack, such as SDAP (Session Data Application Protocol), PDCP (Packet Data Convergence Protocol), and RRC (Radio Resource Control). The DU provides support for lower layers of the protocol stack, such as RLC (Radio Link Control), MAC (Media Access Control), and the physical layer. Each gNB can have multiple cells serving many UEs (User Equipment). NG-RAN uses a large number of algorithms and configuration parameters. In particular, identifying optimal radio parameters is a very difficult task, and operators are accustomed to resorting to manual techniques (such as drive testing) to identify optimal parameters. However, this manual parameter tuning is an expensive operation because it depends on many factors, such as the number of users, the number of neighboring cells, the maximum throughput in the cell, and the average throughput in the cell. Furthermore, many of these manual operations need to be repeated whenever a neighboring gNB is installed or a new service is introduced.

[0023] To address this issue, 3GPP has introduced Self-Organizing Network (SON) technology into wireless technologies such as NR. SON was first introduced in 3GPP Release 9 for LTE. SON solutions can be categorized into three types: self-configuration, self-optimization, and self-healing. SON architectures can be centralized, distributed, or hybrid solutions. Mobility Robustness Optimization (MRO) is a SON technique used to optimize various mobility-related parameters.

[0024] According to 3GPP specifications such as TS 38.300 V17.3.0, mobility robustness optimization aims to detect and correct the following issues:

[0025] - Connection failure due to mobility within or between systems;

[0026] - Unnecessary inter-system HO (premature inter-system HO from NR to E-UTRAN, no radio link failure).

[0027] -Inter-system HO Ping Pong.

[0028] Mobility Robustness Optimization (MRO) provides a way to distinguish the above-mentioned problems from NR coverage-related problems and other problems unrelated to mobility.

[0029] One of the functions of Mobility Robustness Optimization (MRO) is to detect suboptimal successful handover events. The purpose of MRO is to identify underlying conditions during successful normal handovers, successful DAPS handovers, or successful conditional handovers. For successful handover analysis, the UE supports successful handover reporting (if received) based on its network configuration (e.g., via the IE successHO-Config defined in the 3GPP technical specification TS 38.331 in NR) and makes the Successful Handover Report (SHR) available to the network. Upon retrieving a successful handover report, the receiving node can analyze whether its mobility configuration needs adjustment. Similarly, for dual connectivity, the UE can be configured to report successful PSCell Change or Addition Information (SPR), as described in 3GPP specifications such as TS 38.331.

[0030] The network configures the UE to report successful handover. In the NR, the gNB configures the UE to report successful handover via OtherConfig in RRCReconfiguration. OtherConfig-v1700 ::=

[0031] SEQUENCE {

[0032] successHO-Config-r17 SetupRelease {SuccessHO-Config-r17} OPTIONAL, --Need M

[0033] <only relevant parameter shown>

[0034] }

[0035] The gNB can also configure the UE to perform a successful handover report between RATs via the MobilityFromNRCommand as shown below:

[0036] MobilityFromNRCommand-v1800-IEs ::= SEQUENCE {

[0037] successHO-Config-r18 SetupRelease {SuccessHO-Config-r17} OPTIONAL,

[0038] nonCriticalExtension SEQUENCE {} OPTIONAL

[0039] }

[0040] SuccessHO-Config (the configuration used by the UE to report successful handover information to the network) includes some thresholds and may also include some conditions that the UE evaluates during handover. Based on this evaluation, the UE records a successful handover report.

[0041] In NR, SuccessHO-Config is defined as follows:

[0042] SuccessHO-Config-r17 ::= SEQUENCE {

[0043] thresholdPercentageT304-r17 ENUMERATED {p40, p60, p80, spare5,spare4, spare3, spare2, spare1} OPTIONAL, --Need R

[0044] thresholdPercentageT310-r17 ENUMERATED {p40, p60, p80, spare5,spare4, spare3, spare2, spare1} OPTIONAL, --Need R

[0045] thresholdPercentageT312-r17 ENUMERATED {p20, p40, p60, p80, spare4,spare3, spare2, spare1} OPTIONAL, --Need R

[0046] sourceDAPS-FailureReporting-r17 ENUMERATED {true} OPTIONAL, --Need R ...

[0048] }

[0049] Based on the provided threshold, there are different conditions when the UE records SHR.

[0050] If the network configures the UE with ThresholdPercentageT310, and the ratio between the elapsed time of timer T310 and its configured value is greater than ThresholdPercentageT310, then the UE records an SHR (Short-Term Response Time). If the network configures the UE with ThresholdPercentageT312, and the ratio between the elapsed time of timer T312 and its configured value is greater than ThresholdPercentageT312, then the UE records an SHR. If the network configures the UE with ThresholdPercentageT304, and the ratio between the elapsed time of timer T304 and its configured value is greater than ThresholdPercentageT304, then the UE records an SHR.

[0051] The UE reports the recorded SHR to the network based on a request from the network.

[0052] For SCG mobility optimization, the network can use successPSCell configuration (SuccessPSCell-Config) to configure the UE to record and report SPR.

[0053] SuccessPSCell-Config-r18 ::= SEQUENCE {

[0054] thresholdPercentageT304-SCG-r18 ENUMERATED {p40, p60, p80, spare5,spare4, spare3, spare2, spare1} OPTIONAL, --Need R

[0055] thresholdPercentageT310-SCG-r18 ENUMERATED {p40, p60, p80, spare5,spare4, spare3, spare2, spare1} OPTIONAL, --Need R

[0056] thresholdPercentageT312-SCG-r18 ENUMERATED {p20, p40, p60, p80,spare4, spare3, spare2, spare1} OPTIONAL, --Need R ...

[0058] }

[0059] Based on the provided threshold, there are different conditions when the UE records SPR.

[0060] If the network configures the UE using ThresholdPercentageT310-SCG, and the ratio between the elapsed time of timer T310 and its configured value is greater than ThresholdPercentageT310-SCG, then the UE records an SPR. If the network configures the UE using ThresholdPercentageT312-SCG, and the ratio between the elapsed time of timer T312 and its configured value is greater than ThresholdPercentageT312-SCG, then the UE records an SPR. If the network configures the UE using ThresholdPercentageT304, and the ratio between the elapsed time of timer T304 and its configured value is greater than ThresholdPercentageT304-SCG, then the UE records an SPR.

[0061] The UE reports the recorded SPR to the network based on a request from the network.

[0062] According to the NR specification TS 38.331, the parameters are defined as follows:

[0063]

[0064] In NR R18, the evaluation of a successful switch involves the steps in TS 38.331V18.0.0 5.3.5.9 and 5.4.3.3.

[0065] In NR, a successful switchover assessment is performed based on the following:

[0066] 1> Configure the content of the RRCReconfigurationComplete message as follows:

[0067] 2> If RRCReconfiguration includes reconfigurationWithSync in MCG's spCellConfig:

[0068] 3> If the UE is configured with successHO-Config when connecting to the source PCell; and

[0069] 3> If the applied RRCReconfiguration is not due to conditional reconfiguration performed during cell selection at the timer T311 runtime, as defined in 5.3.7.3:

[0070] 4> After successfully completing the random access procedure triggered by reconfigurationWithSync in spCellConfig for MCG, perform the actions determined by the successful handover report as specified in Clause 5.7.10.6;

[0071] 5.4.3.4 Successfully completed mobility transfer from NR

[0072] 1> If the UE is configured with successHO-Config and targetRAT-Type is set to eutra when connecting to the source PCell:

[0073] 2> Perform the actions specified in the successful switchover report as defined in Clause 5.7.10.6.

[0074] If the conditions for a successful handover configuration are met, the UE records a Successful Handover Report (SHR). In NR, the SHR is defined in TS38.331.

[0075] The UE indicates the availability of the SHR in the RRC completion message. In NR, the message can be RRCSetupComplete, RRCResumeComplete, or RRCReconfigurationComplete. Additionally, the UE can receive requests to send an SHR and report the SHR to the network.

[0076] In NR, the request for SHR is sent in the UEInformationRequest message, and the UE sends the SHR to the gNB via the UEInformationResponse message, as described in NR TS 38.331.

[0077] The current successful switchover configuration method does not allow configuring the T310 and T312 thresholds in the successful switchover configuration (e.g., SuccessHO-Config in NR) during switchover. Similarly, for successful PSCellChange, when PSCellChange is sent directly by the SN without MN interaction, the T310 and T312 thresholds cannot be configured in the successful PSCell configuration (e.g., successPSCell-Config in NR) during PSCellChange.

[0078] 3GPP versions V18.0.0 of TS 38.331, TS 38.321, TS 38.300, and TS 38.304 can be considered relevant background. 3GPP specifications such as TS38.300, TS38.331, and TS 38.321 v18.0.0 can also be considered relevant background.

[0079] Therefore, there is a need in the art for solutions that overcome the aforementioned drawbacks. Summary of the Invention

[0080] Technical issues

[0081] The primary objective of the embodiments herein is to disclose methods and systems for handling radio link failures (RLF) in wireless communication networks.

[0082] Another objective of the embodiments described herein is to discover methods and systems for configuring at least one threshold parameter in a wireless communication network.

[0083] Another objective of the embodiments described herein is to provide self-optimization for mobility in dual connectivity of user equipment (UE) in a wireless communication network.

[0084] Another objective of the embodiments herein is to provide T310 and T312 thresholds for optimization during handover in dual connectivity in a wireless communication network.

[0085] Another objective of the embodiments described herein is to provide a UE that maintains its SPR configuration when both attemptCondReconfig and attemptLTM-Switch are configured.

[0086] Another objective of the embodiments described herein is to provide a way for the UE to release the above configuration when recovery fails according to attemptCondReconfig and attemptLTM-Switch.

[0087] Another objective of the embodiments herein is to provide a method for processing SPR configuration during RRCReestablishment when the UE is configured for CHO-based recovery or LTM-based recovery.

[0088] Another objective of the embodiments described herein is to allow network entities to configure SPR configurations on SRB3.

[0089] Another objective of this embodiment is to provide a network entity that, when sending an RRCReconfiguration including ReconfigurationWithSync via SRB3, configures the UE using the T310-SCG threshold (ThresholdPercentageT310-SCG-r18) and T312-SCG threshold (ThresholdPercentageT312-SCG-r18) from the source PSCell before sending a PSCellChange ReconfigurationSync to the UE.

[0090] With the development of communication systems, there is a need for methods and systems to handle radio link failures.

[0091] The technical topics pursued in this disclosure may not be limited to those described above, and other technical topics not mentioned will be clearly understood by those skilled in the art from the following description.

[0092] Technical solutions

[0093] An embodiment discloses a method for handling radio link failure (RLF) in a wireless communication network. The method includes: during an RRC reconstruction procedure, a user equipment (UE) determining whether at least one parameter associated with at least one of conditional reconfiguration and a mobility handover attempt is configured. The method includes the UE performing one of the following: if it is determined that at least one parameter associated with at least one of conditional reconfiguration and a mobility handover attempt is configured, retaining a successPSCell configuration configured by the primary / secondary cell group (PSCell); and if it is determined that at least one parameter associated with at least one of conditional reconfiguration and a mobility handover attempt is not configured, releasing the successPSCell configuration configured by the PSCell.

[0094] The embodiments disclose a method for handling radio link failure (RLF) in a wireless communication network. The method includes determining, during the initiation of an RRC reconstruction procedure, whether at least one parameter associated with at least one of conditional reconfiguration and a mobility handover attempt is configured. The method includes the UE performing one of the following: retaining the successPSCell configuration configured by the primary / secondary cell group (PSCell) when it is determined that at least one parameter associated with at least one of the conditional reconfiguration and mobility handover attempts is configured; and releasing the successPSCell configuration configured by the PSCell when it is determined that at least one parameter associated with at least one of the conditional reconfiguration and mobility handover attempts is not configured.

[0095] The embodiments disclose a method for configuring at least one threshold parameter in a wireless communication network. The method includes configuring a UE (User Equipment) to report at least one of a successful PSCell change and additional information to the network using a successPSCell-Config message from a source primary / secondary cell (PSCell). The method also includes configuring the UE to perform the PSCell change via signaling radio bearer 3 (SRB3) in an RRC reconfiguration message.

[0096] An embodiment discloses a user equipment including: a processor; a memory; and a radio link failure (RLF) controller coupled to the processor and the memory. The RLF controller is configured to: upon initiating an RRC reconstruction procedure, determine whether at least one parameter related to at least one of conditional reconfiguration and a mobility handover attempt is configured. If it is determined that at least one parameter related to at least one of conditional reconfiguration and a mobility handover attempt is configured, the RLF controller performs one of the following: retains the successPSCell configuration configured by the primary / secondary cell group (PSCell). If it is determined that at least one parameter related to at least one of conditional reconfiguration and a mobility handover attempt is not configured, the RLF controller releases the successPSCell configuration configured by the PSCell.

[0097] An embodiment discloses a network entity including: a processor; a memory; and a threshold configuration controller coupled to the processor and the memory. The threshold configuration controller configures the UE to report at least one of a successful PSCell change and additional information to the network using a successPSCell-Config from the source primary / secondary cell (PSCell). The threshold configuration controller configures the UE to perform a PSCell change via signaling radio bearer 3 (SRB3) in an RRC reconfiguration message.

[0098] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and accompanying drawings. However, it should be understood that while the following description indicates at least one embodiment and its many specific details, it is given by way of illustration rather than limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from them, and the embodiments herein encompass all such modifications.

[0099] Beneficial effects

[0100] This disclosure provides an effective and efficient method for handling radio link failures. The beneficial effects obtainable from this disclosure are not limited to those described above, and other effects not mentioned will be clearly understood by those skilled in the art from the following description. Attached Figure Description

[0101] Embodiments of the present invention are illustrated in the accompanying drawings, in which the same reference numerals denote corresponding parts in the various drawings. The embodiments of the present invention will be better understood through the following description with reference to the accompanying drawings. Embodiments of the present invention are illustrated by way of example in the accompanying drawings, wherein:

[0102] Figure 1This is an example diagram illustrating a scenario for handling radio link failure (RLF) and configuring at least one threshold parameter in a wireless communication network according to embodiments disclosed herein;

[0103] Figure 2 This is an example flowchart for determining a Successful Switchover Report (SHR) according to embodiments disclosed herein;

[0104] Figure 3 This is an example flowchart for determining an SHR using at least one threshold parameter, according to embodiments disclosed herein;

[0105] Figure 4 This is an example flowchart for determining SPR using at least one threshold parameter, according to embodiments disclosed herein;

[0106] Figure 5 This is an example diagram depicting a UE performing a UE capability report for an SHR according to an embodiment disclosed herein;

[0107] Figure 6 This is an example diagram depicting the interaction between a source gNB and a target gNB for performing a handover operation in an SHR configuration according to embodiments disclosed herein;

[0108] Figure 7 This is an example flowchart illustrating a scenario with a successPSCell-Config of attempted conditional reconfiguration / LTM according to embodiments disclosed herein;

[0109] Figure 8 This is an example flowchart illustrating a scenario in which cell selection is performed at runtime in T311 with successPSCell-Config according to an embodiment disclosed herein;

[0110] Figure 9 This is an example flowchart illustrating a scenario in which cell selection is performed while the T311 is running an attempt at conditional reconfiguration / LTM, according to an embodiment disclosed herein;

[0111] Figure 10 This is an example sequence diagram illustrating a scenario of UE capability reporting for RACH for PDCCH commands according to embodiments disclosed herein;

[0112] Figure 11 Various hardware components of a UE for handling radio link failure (RLF) in a wireless communication network are shown according to embodiments disclosed herein;

[0113] Figure 12 Various hardware components for configuring at least one threshold parameter in a wireless communication network are shown according to embodiments disclosed herein.

[0114] Figure 13 This is a flowchart depicting a method for processing RLF in a wireless communication network according to embodiments disclosed herein; and

[0115] Figure 14 This is a flowchart depicting a method for configuring at least one threshold parameter in a wireless communication network according to embodiments disclosed herein. Detailed Implementation

[0116] The embodiments described herein, along with their various features and advantageous details, are explained more fully with reference to the non-limiting embodiments illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques have been omitted to avoid unnecessarily obscuring the embodiments herein. The examples used herein are intended only to facilitate understanding of how the embodiments described herein can be practiced and to further enable those skilled in the art to practice the embodiments described herein. Therefore, these examples should not be construed as limiting the scope of the embodiments described herein.

[0117] For the purposes of interpreting this specification, definitions (as defined herein) will apply, and terms used in the singular will include the plural where appropriate, and vice versa. It should be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not restrictive. Unless otherwise stated, the terms “comprising,” “having,” and “including” should be interpreted as open-ended terms.

[0118] The words / phrases “exemplary,” “example,” “illustration,” “in instance,” “like,” “etc,” “e.g.,” “i.e.,” are used herein only to mean “used as an example, instance, or illustration.” Any embodiment or implementation of the subject matter described herein using the words / phrases “exemplary,” “example,” “illustration,” “in instance,” “like,” “etc,” “e.g.,” “i.e.,” is not necessarily to be construed as preferred or advantageous over other embodiments.

[0119] Embodiments herein can be described and illustrated based on blocks that perform one or more of the described functions. These blocks (which may be referred to herein as managers, units, modules, hardware components, etc.) are physically implemented by analog and / or digital circuitry (such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuitry, passive electronic components, active electronic components, optical components, hardwired circuitry, etc.) and may optionally be driven by firmware. The circuitry may be embodied, for example, in one or more semiconductor chips or on a substrate support such as a printed circuit board. The circuitry constituting a block may be implemented by dedicated hardware, by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware (for performing certain functions of the block) and a processor (for performing other functions of the block). Each block of an embodiment may be physically divided into two or more interacting and discrete blocks without departing from the scope of this disclosure. Similarly, the blocks of an embodiment may be physically combined into more complex blocks without departing from the scope of this disclosure.

[0120] It should be noted that the elements in the accompanying drawings are shown for the purposes of this specification and ease of understanding, and may not necessarily be drawn to scale. For example, flowcharts / sequence diagrams illustrate the method according to the steps required to understand the aspects of the embodiments disclosed herein. Furthermore, in terms of the construction of the apparatus, one or more components of the apparatus may have been represented by conventional symbols in the drawings, and the drawings may only show specific details relevant to understanding the embodiments, so as not to obscure the drawings from details readily understood by those skilled in the art from the description herein. Similarly, in terms of the system, one or more components / modules constituting the system may have been represented by conventional symbols in the drawings, and the drawings may only show specific details relevant to understanding the embodiments, so as not to obscure the drawings from details readily understood by those skilled in the art from the description herein.

[0121] The accompanying drawings are provided to aid in the easy understanding of the various technical features, and it should be understood that the embodiments presented herein are not limited to the drawings. Therefore, except for those specifically set forth in the drawings and corresponding descriptions, this disclosure should be construed as extending to any modifications, equivalents, and substitutions. The use of terms such as first, second, third, etc., to describe components / elements / steps is for the purposes of this specification and, unless otherwise stated, should not be construed as indicating a sequential order / placement / occurrence.

[0122] The embodiments herein disclose methods and systems for handling radio link failures (RLF) in wireless communication networks.

[0123] The proposed method allows a user equipment (UE) to determine whether at least one parameter related to at least one of the conditional reconfiguration and mobility handover attempts is configured when initiating a radio resource control (RRC) re-establishment process.

[0124] At least one parameter associated with at least one of the conditional reconfiguration and mobility handover attempts includes attemptCondReconfig and attemptLTM-Switch, which are configured by the primary and secondary cell (PSCell) for processing successPSCell.

[0125] This document discloses methods and systems for performing mobility-based RLF recovery. This disclosure provides methods for a UE to reset Media Access Control (MAC) and process configuration when attemptCondReconfig or attemptLTM-Switch is configured. Furthermore, this disclosure provides methods for a UE to process successPSCell-Config when attemptCondReconfig or attemptLTM-Switch is configured. This disclosure provides methods for a UE to report the RACH capability of PDCCH commands.

[0126] This document discloses a method and system for configuring at least one threshold parameter in a wireless communication network by configuring a UE to report at least one of a successful PSCell change and additional information to the network using a successful PSCell configuration from a source primary SCG (secondary cell group). The additional information includes processing the successful PSCell change and the added information.

[0127] The proposed method discloses at least one threshold parameter including ThresholdPercentageT310-SCG-r18 (T310-SCG) and ThresholdPercentageT312-SCG-r18 (T312-SCG).

[0128] LTM is the process by which the gNB receives an L1 measurement report from the UE, and based on this, the gNB changes the UE's serving cell via a cell handover command signaled via the MAC CE. The cell handover command indicates the LTM candidate cell configuration previously prepared by the gNB and provided to the UE via RRC signaling. The UE then hands over to the target cell according to the cell handover command. As described, the LTM procedure can be used to reduce mobility latency.

[0129] The network can request the UE to perform early TA acquisition for a candidate cell before cell handover. Early TA acquisition is triggered by a PDCCH command [or by UE-based TA measurement].

[0130] The network indicates in the cell handover command whether the UE should access the target cell using the RA procedure without providing a TA value or using a PUSCH transmission with the indicated TA value. For LTM without RACH, the UE listens to the PDCCH during LTM cell handover for dynamic scheduling from the target cell, or the UE selects the authorization timing of the configuration associated with the beam indicated in the cell handover command.

[0131] The following principles apply to LTM:

[0132] - The UE does not update its security key in LTM.

[0133] - Supports subsequent LTM.

[0134] LTM supports both intra-gNB-DU and inter-gNB-DU mobility within and between gNB-CUs. LTM also supports inter-frequency mobility, including mobility to cells on frequencies other than the current serving cell. The following scenarios are supported:

[0135] - PCell changes in non-CA scenarios

[0136] - PCell changes in CA scenarios

[0137] - In dual-connection scenarios, at least for PSCell changes without MN involvement, i.e., PSCell changes within SN.

[0138] The supervisory timer can be used to detect the failure of the LTM cell handover process. If the LTM supervisory timer expires, the LTM process fails, and the UE initiates the RRC connection reconstruction process.

[0139] When the UE has already stored the LTM candidate cell configuration, the UE can also execute any L3 handover command sent by the network. The network avoids any problems caused by conflicts between LTM execution and L3 handover execution, such as avoiding sending LTM cell handover commands and L3 handover commands simultaneously.

[0140] Cell handover commands are transmitted in the MAC CE, which contains the necessary information to perform LTM cell handover.

[0141] After declaring RLF, UE:

[0142] - In the case of CHO, for RLF in the source cell:

[0143] - Select a suitable cell, and if the selected cell is a CHO candidate, and if the network is configured for the UE to attempt CHO after RLF, then the UE attempts CHO once; otherwise, it attempts to re-establish the cell.

[0144] - If no suitable cell is found within a certain period of time after the RLF is declared, then enter RRC_IDLE.

[0145] - In the case of MCG LTM, for RLF in the source cell:

[0146] - Select a suitable cell, and if the selected cell is an LTM candidate cell, and if the network is configured for the UE to attempt LTM after RLF, then the UE attempts one RACH-based LTM execution; otherwise, a reconstruction is performed.

[0147] Similarly, when the initial CHO execution attempt fails or the HO fails, the UE performs cell selection. If the selected cell is a CHO candidate, and if the network configuration allows the UE to attempt CHO after a handover / CHO failure, the UE attempts CHO execution once; otherwise, a rebuild is performed. In the current specification, even when the UE attempts CHO execution, the UE releases the SPR configuration from the PCell and PSCell.

[0148] When an LTM execution attempt triggered by the LTM cell handover command MAC CE fails or a HO fails, the UE performs cell selection. If the selected cell is an LTM candidate cell, and if the network is configured for the UE to attempt LTM after a handover / LTM execution failure, the UE attempts a RACH-based LTM execution; otherwise, a rebuild is performed. In the current specification, even when the UE attempts an LTM execution, the UE releases the SPR configuration from the PCell and PSCell.

[0149] The various steps for recovery based on CHO or LTM are specified in TS 38.331 as follows.

[0150] 5.3.7 RRC Connection Reconstruction

[0151] 5.3.7.2 Initiate

[0152] The UE initiates this procedure when one of the conditions specified in TS 38.331 5.3.7.2 is met:

[0153] When initiating this process, the UE should:

[0154] 1> Stop timer T310 (if running);

[0155] 1> Stop timer T312 (if it is running);

[0156] 1> Stop timer T304 (if running);

[0157] 1> Start timer T311;

[0158] 1> Stop timer T316 (if running);

[0159] 1> If the UE is not configured with attemptCondReconfig; and

[0160] 1> If the UE is not configured with attemptLTM-Switch:

[0161] 2> Reset MAC address;

[0162] 2> Release spCellConfig (if configured);

[0163] 2> Suspend all RBs except SRB0 and broadcast MRB, the BH RLC channel for IAB-MT, and the Uu trunk RLC channel for L2U2N trunk UEs;

[0164] 2> Release the MCG SCell (if configured);

[0165] 2> If MR-DC is configured:

[0166] 3> Perform MR-DC release as specified in Clause 5.3.5.10;

[0167] 2> Perform the LTM configuration release procedure for MCG and SCG as specified in Clause 5.3.5.18.7;

[0168] 2> Release delayBudgetReportingConfig (if configured) and stop timer T342 (if running);

[0169] 2> Release overheatingAssistanceConfig (if configured) and stop timer T345 (if running);

[0170] 2> Release idc-AssistanceConfig (if configured);

[0171] 2> Release btNameList (if configured);

[0172] 2> Release wlanNameList (if configured);

[0173] 2> Release sensorNameList (if configured);

[0174] 2> Release drx-PreferenceConfig for MCG (if configured) and stop timer T346a associated with MCG (if running);

[0175] 2> Release the maxBW-PreferenceConfig of the MCG (if configured) and stop the timer T346b associated with the MCG (if running);

[0176] 2> Release MCG's maxCC-PreferenceConfig (if configured) and stop the timer T346c associated with MCG (if running);

[0177] 2> Release the maxMIMO-LayerPreferenceConfig of the MCG (if configured) and stop the timer T346d associated with the MCG (if running);

[0178] 2> Release the minSchedulingOffsetPreferenceConfig of the MCG (if configured), and stop the timer T346e associated with the MCG (if running);

[0179] 2> Release the rlm-RelaxationReportingConfig of the MCG (if configured) and stop the timer T346j associated with the MCG (if running);

[0180] 2> Release the bfd-RelaxationReportingConfig of the MCG (if configured) and stop the timer T346k associated with the MCG (if running);

[0181] 2> Release releasePreferenceConfig (if configured), stop timer T346f (if running);

[0182] 2> Release onDemandSIB-Request (if configured) and stop timer T350 (if running);

[0183] 2> Release referenceTimePreferenceReporting (if configured);

[0184] 2> Release sl-AssistanceConfigNR (if configured);

[0185] 2> Release obtainCommonLocation (if configured);

[0186] 2> Release musim-GapAssistanceConfig (if configured) and stop timer T346h (if running);

[0187] 2> Release musim-GapPriorityAssistanceConfig (if configured);

[0188] 2> Release musim-LeaveAssistanceConfig (if configured);

[0189] 2> Release musim-CapabilityRestrictionConfig (if configured) and stop timer T346n (if running);

[0190] 2> Release ul-GapFR2-PreferenceConfig (if configured);

[0191] 2> Release scg-DeactivationPreferenceConfig (if configured) and stop timer T346i (if running);

[0192] 2> Release propDelayDiffReportConfig (if configured);

[0193] 2> Release rrm-MeasRelaxationReportingConfig (if configured);

[0194] 2> Release maxBW-PreferenceConfigFR2-2 (if configured);

[0195] 2> Release maxMIMO-LayerPreferenceConfigFR2-2 (if configured);

[0196] 2> Release minSchedulingOffsetPreferenceConfigExt (if configured);

[0197] 2> multiRx-PreferenceReportingConfigFR2 (if configured), and stop timer T346m (if running);

[0198] 2> Release aerial-FlightPathAvailabilityConfig (if configured);

[0199] 2> Release ul-TrafficInfoReportingConfig (if configured) and stop all instances of timer T346l (if running);

[0200] 1> Release successHO-Config (if configured);

[0201] 1> Release successPSCell-Config configured by PCell (if configured);

[0202] 5.3.7.3 Actions after cell selection during T311 runtime

[0203] When selecting a suitable NR cell, the UE should:

[0204] 1> Ensure that the basic system information as specified in Clause 5.2.2.2 is valid and up-to-date;

[0205] 1> Stop timer T311;

[0206] 1> If T390 is running:

[0207] 2> Stop timer T390 for all access categories;

[0208] 2> Perform the actions specified in 5.3.14.4;

[0209] 1> Stop the relay (re)selection process (if in progress);

[0210] 1> If cell selection is triggered by detecting a radio link failure of the MCG, a reconfiguration failure of the MCG with synchronization, or mobility failure from an NR failure, and

[0211] 1> If attemptCondReconfig is configured; and

[0212] 1> If the selected cell is not configured with CondEventT1, or if the selected cell is configured with CondEventT1 but the leave conditions have not yet been met; and

[0213] 1> If the selected cell is one of the candidate cells in the masterCellGroup included in MCGVarConditionalReconfig for its reconfigurationWithSync, and condExecutionCondPSCell is not configured for the corresponding condReconfigId in MCGVarConditionalReconfig, then:

[0214] 2> If the UE supports RLF reporting for conditional handover, set choCellId in VarRLF-Report to the global cell identifier (if available), otherwise set to the physical cell identifier and carrier frequency of the selected cell;

[0215] 2> Apply the stored condRRCReconfig associated with the selected cell and perform the actions specified in 5.3.5.3;

[0216] Note 1: In the event of a failed handover without key changes, how to avoid key stream reuse in the case of CHO-based recovery is left to the network implementation.

[0217] 1> If cell selection is triggered by detecting a radio link failure of the MCG or a synchronized reconfiguration failure of the MCG for an LTM cell handover procedure, the LTM cell handover procedure is triggered upon instruction from a lower layer as specified in Clause 5.3.5.18.6; and

[0218] 1> If attemptLTM-Switch is configured; and

[0219] 1> If the selected cell is one of the LTM candidate cells in the LTM-Candidate IE within the ltm-Config associated with the MCG, then:

[0220] 2> Perform the LTM cell handover procedure for the selected LTM candidate cell according to the actions specified in 5.3.5.18.6;

[0221] Note 2: When both attemptCondReconfig and attemptLTM-Switch are configured, which process to execute depends on the UE implementation.

[0222] 1> Otherwise

[0223] 2> If the UE is configured with attemptCondReconfig; or

[0224] 2> If the UE is configured with attemptLTM-Switch:

[0225] 3> Reset MAC address;

[0226] 3> Release spCellConfig (if configured);

[0227] 3> Release the MCG SCell (if configured);

[0228] 3> Release delayBudgetReportingConfig (if configured) and stop timer T342 (if running);

[0229] 3> Release overheatingAssistanceConfig (if configured) and stop timer T345 (if running);

[0230] 3> If MR-DC is configured:

[0231] 4> Perform MR-DC release as specified in Clause 5.3.5.10;

[0232] 3> Release idc-AssistanceConfig (if configured);

[0233] 3> Release btNameList (if configured);

[0234] 3> Release wlanNameList (if configured);

[0235] 3> Release sensorNameList (if configured);

[0236] 3> Release drx-PreferenceConfig for MCG (if configured) and stop timer T346a associated with MCG (if running);

[0237] 3> Release the maxBW-PreferenceConfig of the MCG (if configured) and stop the timer T346b associated with the MCG (if running);

[0238] 3> Release MCG's maxCC-PreferenceConfig (if configured) and stop the timer T346c associated with MCG (if running);

[0239] 3> Release the maxMIMO-LayerPreferenceConfig of the MCG (if configured) and stop the timer T346d associated with the MCG (if running);

[0240] 3> Release the minSchedulingOffsetPreferenceConfig of the MCG (if configured) and stop the timer T346e associated with the MCG (if running);

[0241] 3> Release the rlm-RelaxationReportingConfig of the MCG (if configured) and stop the timer T346j associated with the MCG (if running);

[0242] 3> Release the bfd-RelaxationReportingConfig of the MCG (if configured) and stop the timer T346k associated with the MCG (if running);

[0243] 3> Release releasePreferenceConfig (if configured) and stop timer T346f (if running);

[0244] 3> Release onDemandSIB-Request (if configured) and stop timer T350 (if running);

[0245] 3> Release referenceTimePreferenceReporting (if configured);

[0246] 3> Release sl-AssistanceConfigNR (if configured);

[0247] 3> Release obtainCommonLocation (if configured);

[0248] 3> Release scg-DeactivationPreferenceConfig (if configured) and stop timer T346i (if running);

[0249] 3> Release musim-GapAssistanceConfig (if configured), and if it is running, stop timer T346h;

[0250] 3> Release musim-GapPriorityAssistanceConfig (if configured);

[0251] 3> Release musim-LeaveAssistanceConfig (if configured);

[0252] 3> Release musim-CapabilityRestrictionConfig (if configured) and stop timer T346n (if running);

[0253] 3> Release propDelayDiffReportConfig (if configured);

[0254] 3> Release ul-GapFR2-PreferenceConfig (if configured);

[0255] 3> Release rrm-MeasRelaxationReportingConfig (if configured);

[0256] 3> Release maxBW-PreferenceConfigFR2-2 (if configured);

[0257] 3> Release maxMIMO-LayerPreferenceConfigFR2-2 (if configured);

[0258] 3> Release minSchedulingOffsetPreferenceConfigExt (if configured);

[0259] 3> Release aerial-FlightPathAvailabilityConfig (if configured);

[0260] 3> Release ul-TrafficInfoReportingConfig (if configured) and stop all instances of timer T346l (if running);

[0261] 3> Suspend all RB and BH RLC channels used for IAB-MT, except for SRB0 and broadcast MRB;

[0262] 2> Remove all entries (if any) from MCG VarConditionalReconfig;

[0263] 2> Perform the LTM configuration release procedure for MCG and SCG as specified in Clause 5.3.5.18.7;

[0264] The UE notifies LTM of several capabilities. One of these capabilities is whether the UE might cause an interruption in the DL slot on the serving cell due to the RACH transmission of the PDCCH command. The following are definitions of these capabilities in known prior art related to the RACH transmission of the PDCCH command.

[0265]

[0266]

[0267] Now refer to the attached diagram, for more specific details. Figures 1 to 14 The figures, in which similar reference numerals are consistently used to denote corresponding features throughout, illustrate at least one embodiment.

[0268] Figure 1This is an example diagram illustrating a scenario for handling radio link failure (RLF) and configuring at least one threshold parameter in a wireless communication network 100.

[0269] like Figure 1 As shown, embodiments of this document disclose the handling of radio link failure (RLF) recovery and mobility handover in a wireless communication network 100. UE 1102 is configured to determine whether certain parameters related to conditional reconfiguration or mobility handover attempts are set when initiating an RRC reconstruction procedure. Based on this determination, UE 1102 retains or releases the successPSCell configuration associated with the primary / secondary cell group (PSCell).

[0270] Parameters related to conditional reconfiguration or mobility handover attempts may include, but are not limited to, `attemptCondReconfig` and `attemptLTM-Switch`. These parameters help UE 1102 decide whether to retain or release the `successPSCell` configuration. If recovery based on conditional handover (CHO) or recovery based on lower-layer triggered mobility (LTM) fails and at least one parameter is configured, UE 1102 releases the `successPSCell` configuration. This ensures that UE 1102 does not persist with PSCell configurations that are no longer feasible, thus allowing it to switch to a more suitable cell.

[0271] In another embodiment, UE 1102 determines, while the timer is active, that it cannot apply LTM-based candidate configurations or conditional reconfigurations when performing cell selection. If parameters related to conditional reconfiguration and mobility handover attempts are configured, UE 1102 releases the successPSCell configuration after completing cell selection, while the timer remains active.

[0272] In another embodiment, at least one threshold parameter is configured in the wireless communication network 100. Network entity 1202 is responsible for configuring UE 1102 to report successful PSCell changes and additional information to network entity 1202. The additional information processes the successful PSCell change and added information. The report contains the successPSCell-Config from the source PSCell, allowing the network to monitor mobility performance and optimize handover management. The network entity then configures UE 1102 via an RRC reconfiguration message to perform the PSCell change using Signaling Radio Bearer 3 (SRB3). SRB3 is used to process control signaling related to secondary cell group (SCG) transitions, ensuring a smooth transition of UE 1102 between PSCells.

[0273] In another embodiment disclosed herein, the configured threshold parameters include T310-SCG and T312-SCG to identify problems in the SCG mobility configuration. Timers T310 and T312 are associated with radio link failures. When UE 1102 identifies certain problems on the radio link, UE 1102 starts timer T310. When UE 1102 identifies certain problems on the radio link and UE 1102 has measurements to report for certain measurement identifiers, UE 1102 starts T312. The T310-SCG threshold indicates a threshold representing the percentage ratio between the elapsed T310 timer associated with the measurement identifier of the target PSCell and the configured value of the T310 timer. The T312-SCG threshold indicates a threshold representing the percentage ratio between the elapsed T312 timer associated with the measurement identifier of the target PSCell and the configured value of the T312 timer. The T310 and T312 thresholds can be used in the SHR configuration. The T310-SCG and T312-SCG thresholds can be used in the SPR configuration. These thresholds help UE 1102 manage connectivity and optimize failure recovery mechanisms. Handling RLF failures concerns processing successPSCell-Config during RLF, and the threshold parameters are part of successPSCell-Config.

[0274] In this embodiment, UE 1102 receives threshold parameters T310 and T312 from the target cell for SHR determination. UE 1102 receives useAllSCGConfig from the target in the SHR configuration, which aids in mobility processing decisions. UE 1102 applies the configured T310 and T312 thresholds from the target cell, thereby allowing the determination of successful handover. Therefore, ensuring that UE 1102 applies the correct parameters for mobility management prevents unnecessary failures during network transitions.

[0275] In another embodiment disclosed herein, network entity 1202 may configure UE 1102 to report successful PSCell changes along with additional information. Network entity 1202 then configures UE 1102 via an RRC reconfiguration message to perform the PSCell change using Signaling Radio Bearer 3 (SRB3). SRB3 is responsible for handling control plane signaling specific to secondary cell group (SCG) transitions, ensuring smooth and efficient mobility between cells. UE 1102 may use this configuration to record information related to successful PSCellChanges.

[0276] As disclosed in another embodiment herein, an SHR is determined by UE 1102 using at least one threshold parameter. UE 1102 receives source threshold parameters ThresholdPercentageT310-r18 and ThresholdPercentageT312-r18 from the target cell to define the SHR record. Network entity 1202 configures these threshold parameters, which include ThresholdPercentageT310-r18 and ThresholdPercentageT312-r18. ThresholdPercentageT310 indicates a threshold representing the percentage ratio between the elapsed T310 timer associated with the measurement identifier of the target PSCell and the configured value of the T310 timer. ThresholdPercentageT312 indicates a threshold representing the percentage ratio between the elapsed T312 timer associated with the measurement identifier of the target PSCell and the configured value of the T312 timer. UE 1102 applies the configured thresholds and reports the SHR.

[0277] As in another embodiment disclosed herein, the secondary primary reconfiguration (SPR) using threshold parameters is performed by UE 1102. UE 1102 receives sourceThresholdPercentageT310-SCG-r18 and ThresholdPercentageT312-SCG-r18 from the target PSCell, thereby ensuring the correct parameters are applied. UE 1102 applies the thresholds used for SPR determination, thereby allowing the determination of the appropriate configuration for PSCell changes.

[0278] As in another embodiment disclosed herein, UE 1102 performs an SHR capability reporting procedure. UE 1102 receives a capability query request from gNB 500 and initiates a process of reporting SHR-related capabilities. UE 1102 provides capability information, including its ability to apply T310 and T312 thresholds received from the target cell for SHR determination. The reported capabilities specifically relate to Radio Link Failure Recovery, Mobility Management, and Successful Handover Reporting (SHR), thereby ensuring that gNB 500 is aware of UE 1102's reporting capabilities for managing near-failure mobility transitions.

[0279] As in another embodiment disclosed herein, a handover operation in the SHR configuration is performed between the source gNB 500A and the target gNB 500B. The target gNB 500B sends a HandoverRequest message to the source gNB 500A. This message contains HandoverPreparationInformation, including T310 and T312 thresholds, ensuring that the handover is performed using the correct failure detection parameters. The source gNB 500A processes the request and provides a HandoverRequest acknowledgment, confirming that the handover operation can continue. The interaction between the source and target gNBs ensures that the handover is seamless, and the UE 1102 receives the correct threshold parameters for mobility and failure handling.

[0280] In the embodiments described herein, the network entity configures UE 1102 using the SHR T310 threshold (ThresholdPercentageT310-r17 as defined in TS 38.331) and the SHR T312 threshold (ThresholdPercentageT312-r17 as defined in TS 38.331) from the source cell before sending the handover ReconfigurationSync to UE 1102.

[0281] In the embodiments described herein, the source cell may include a T310 / T312 threshold in its RRCReconfiguration, which contains a ReconfigurationSync generated by the cell itself for a handover targeting the target cell. In the embodiments described herein, the source cell may include an SHR T310 / T312 threshold in its RRCReconfiguration message, which is sent before an RRCReconfiguration including a ReconfigurationWithSync for handover to the target cell is sent.

[0282] In the embodiments described herein, network node / entity 1202 configures UE 1102 to determine whether it can use the T310 threshold (ThresholdPercentageT310-r17) and T312 threshold (ThresholdPercentageT312-r17) of SHR in the target cell (e.g., C2) configuration instead of the T310 and T312 thresholds of SHR in the source cell (e.g., C1) configuration to determine a successful handover report from source cell C1 to target cell (e.g., C2). UE 1102 uses the T310 and T312 thresholds for SHR in the target cell configuration based on this configuration. If the target cell configuration is unavailable, UE 1102 uses the T310 and T312 thresholds for SHR in the source cell configuration. In the embodiments described herein, this configuration applies to all parameters from the source cell, which are used by default to determine a successful handover report.

[0283] In the embodiments described herein, network node / network entity 1202 configures UE 1102 to use the T310 threshold (ThresholdPercentageT310-r17) and the T312 threshold (ThresholdPercentageT312-r17) for SHR in the target cell (e.g., C2) configuration to determine a successful handover report from source cell C1 to target cell C2. UE 1102 uses the T310 and T312 thresholds for SHR in the target cell configuration based on this configuration. If this configuration is unavailable, UE 1102 uses the T310 and T312 thresholds for SHR in the source cell configuration. In the embodiments described herein, this configuration applies to all parameters from the source cell, which are used by default to determine a successful handover report.

[0284] In the embodiments described herein, network node / network entity 1202 indicates to UE 1102 the T310 threshold (ThresholdPercentageT310-r17) and T312 threshold (ThresholdPercentageT312-r17) of the SHR in the target cell C2 configuration, or the T310 threshold and T312 threshold of the SHR in the source cell C2 configuration, for determining a successful handover report from source cell C1 to target cell C2. UE 1102 uses the configuration indicated by the network node.

[0285] In an alternative embodiment of this document, network node / network entity 1202 configures UE 1102 to use the T310 SHR threshold (ThresholdPercentageT310-r17) and / or the T312 SHR threshold (ThresholdPercentageT312-r17) and / or the T304 SHR threshold (ThresholdPercentageT304-r17) in the source PScell ​​(e.g., C1) configuration (or PCell configuration) to determine a successful handover report from the source cell (e.g., C1) to the target cell (e.g., C2). If configured, UE 1102 uses the T310 SHR threshold and / or the T312 SHR threshold and / or the T304 SHR threshold in the source cell (e.g., C1) configuration. If not configured, UE 1102 uses the T310 SHR threshold and / or the T312 SHR threshold and / or the T304 SHR threshold in the target cell (e.g., C2) configuration. UE 1102 records SHR based on the T310 SHR threshold and / or the T312 SHR threshold. In the embodiments described herein, this configuration applies to all parameters from the target cell, which are used by default to determine successful handover reports.

[0286] In the embodiments described herein, the configuration used by network entity 1202 to notify UE 1102 of the T310 threshold (ThresholdPercentageT310-r17) and T312 threshold (ThresholdPercentageT310-r17) for SHR configured by the target cell (as described in the embodiments above) is an information element (IE), such as a flag or enumeration. If the information element is included (or if the flag is true), UE 1102 considers the T310 threshold and the T312 threshold for SHR (as configured by the target cell). In the embodiments described herein, this IE may be sent when sending the configuration for handover or when sending the configuration for determining a successful handover report.

[0287] Consider the scenario where UE 1102 moves from source cell C1 to target cell C2. UE 1102 receives the T310 threshold (ThresholdPercentageT310-r17) and the T312 threshold (ThresholdPercentageT312-r17) for the SHR from source cell C1. UE 1102 also receives the T310 and T312 thresholds for the SHR from target cell C2. In the current system, UE 1102 uses the T310 and T312 thresholds for the SHR from source cell C1 to determine the SHR.

[0288] According to the embodiments disclosed herein, communication network 100 can instruct UE 1102 which T310 SHR threshold or T312 SHR threshold to use. Network 100 can instruct UE 1102 to use a threshold from a target cell, and UE 1102 uses the T310 SHR threshold and T312 SHR threshold received from target cell C2 to determine the SHR during handover from source cell C1 to target cell C2. If there is no specific instruction from the network to use a threshold from the target cell, UE 1102 uses the T310 SHR threshold and T312 SHR threshold received from source cell C1.

[0289] In the embodiments herein, according to TS 38.331,

[0290] SuccessHO-Config-r17 ::= SEQUENCE {

[0291] thresholdPercentageT304-r17 ENUMERATED {p40, p60, p80, spare5,spare4, spare3, spare2, spare1} OPTIONAL, --Need R

[0292] thresholdPercentageT310-r17 ENUMERATED {p40, p60, p80, spare5,spare4, spare3, spare2, spare1} OPTIONAL, --Need R

[0293] thresholdPercentageT312-r17 ENUMERATED {p20, p40, p60, p80, spare4,spare3, spare2, spare1} OPTIONAL, --Need R

[0294] sourceDAPS-FailureReporting-r17 ENUMERATED {true} OPTIONAL, --Need R [

[0296] uset310T312Threshold-FromTarget-r18 ENUMERATED {true} OPTIONAL, --Need R ] ...

[0299] }

[0300] useT310T312Threshold-FromTarget-r18: If this field is included in target_cell_SuccessHO-Config, then UE 1102 uses ThresholdPercentageT310-r17 and ThresholdPercentageT31-r17 configured by the target cell (instead of the values ​​in the source cell configuration) during SHR determination.

[0301] 5.3.5.9 Other Configurations

[0302] 1> If the received otherConfig includes SuccessHO-Config (and SuccessHO-Config is set):

[0303] 2> If include useT310T312Threshold-FromTarget-r17

[0304] 3> Consider ThresholdPercentageT310-r17 and ThresholdPercentageT310-r17 (if included) in the target cell configuration, as configured by the source PSCell.

[0305] Alternatively,

[0306] 5.3.5.9 Other Configurations

[0307] 1> If the otherConfig received from the target PSCell includes SuccessHO-Config (and SuccessHO-Config is set):

[0308] 2> If include useT310T312Threshold-FromTarget-r18

[0309] 3> Consider ThresholdPercentageT304-r17 and ThresholdPercentageT312-r17 in the target cell configuration, if they are included as configured by the source PSCell.

[0310] In the embodiments described herein, if useT310T312Threshold-FromTarget-r18, then UE 1102 uses ThresholdPercentageT310-r17 and ThresholdPercentageT312-r17 from the target cell to determine the SPR. UE 1102 may not use any ThresholdPercentageT310-r17 and ThresholdPercentageT312-r17 from the source cell for the PSCellChange from the current source to the target.

[0311] In the embodiments described herein, useT310T312Threshold-FromTarget-r18 is only included by the target cell.

[0312] In the embodiments described herein, the target cell includes a T310 threshold for the SHR from the source cell (determined by the source cell) and a T312 threshold for the SHR from the source cell (determined by the source cell) in the SuccessHO-Config.

[0313] In the embodiments described herein, the target cell includes a T310 threshold and a T312 threshold for the SHR from the source cell in its SuccessHO-Config, separate from the T310 and T312 thresholds for the SHR from the target cell. The T310 and T312 thresholds for the SHR from the source cell included in the target cell's SuccessHO-Config can be used to determine the SHR from the source cell to the target cell, while the T310 and T312 thresholds for the SHR from the target cell included in the target cell's SuccessHO-Config are used to determine the SHR from the target cell to another cell (i.e., when the target becomes the source).

[0314] In the embodiments herein, according to TS 38.331,

[0315] SuccessHO-Config-r17 ::= SEQUENCE {

[0316] thresholdPercentageT304-r17 ENUMERATED {p40, p60, p80, spare5,spare4, spare3, spare2, spare1} OPTIONAL, --Need R

[0317] thresholdPercentageT310-r17 ENUMERATED {p40, p60, p80, spare5,spare4, spare3, spare2, spare1} OPTIONAL, --Need R

[0318] thresholdPercentageT312-r17 ENUMERATED {p20, p40, p60, p80, spare4,spare3, spare2, spare1} OPTIONAL, --Need R

[0319] sourceDAPS-FailureReporting-r17 ENUMERATED {true} OPTIONAL, --Need R [

[0321] sourceThresholdPercentageT310-r18 ENUMERATED {p40, p60, p80, spare5,spare4, spare3, spare2, spare1} OPTIONAL, --Need R

[0322] sourceThresholdPercentageT312-r18 ENUMERATED {p20, p40, p60, p80,spare4, spare3, spare2, spare1} OPTIONAL, --Need R ] ...

[0325] }

[0326] sourceThresholdPercentageT310-r18: This field is included in the SuccessHO-Config configured by the target cell. If this field is configured, UE 1102 uses it during the successful handover report determination (instead of ThresholdPercentageT310-r17 included in the source cell's OtherConfig).

[0327] UE 1102 uses sourceThresholdPercentageT310-r18 from OtherConfig of the target PSCell as if it were receiving ThresholdPercentageT310-r17 from OtherConfig of the source cell.

[0328] sourceThresholdPercentageT312-r18: This field is included in the SuccessHO-Config configured by the target cell. If this field is configured, UE 1102 uses it during the successful handover report determination (instead of ThresholdPercentageT312-r17 included in the source cell's OtherConfig).

[0329] UE 1102 uses sourceThresholdPercentageT312-r18 from OtherConfig of the target PSCell as if it were receiving ThresholdPercentageT312-r17 from OtherConfig of the source cell.

[0330] 5.3.5.9 Other Configurations

[0331] 1> If the received otherConfig includes SuccessHO-Config (and SuccessHO-Config is set):

[0332] 2> If sourceThresholdPercentageT310-r18 is included

[0333] 3> Treat sourceThresholdPercentageT310-r18 as ThresholdPercentageT310-r17 configured by the source cell.

[0334] 2> If sourceThresholdPercentageT312-r18 is included

[0335] 3> Treat sourceThresholdPercentageT312-r18 as ThresholdPercentageT312-r17 configured by the source cell.

[0336] Alternatively,

[0337] 5.3.5.9 Other Configurations

[0338] 1> If the otherConfig received from the target PSCell includes SuccessHO-Config (and SuccessHO-Config is set):

[0339] 2> If sourceThresholdPercentageT310-r18 is included

[0340] 3> Treat sourceThresholdPercentageT310-r18 as ThresholdPercentageT310-r17 configured by the source cell.

[0341] 2> If sourceThresholdPercentageT312-r18 is included

[0342] 3> Treat sourceThresholdPercentageT312-r18 as ThresholdPercentageT312-r17 configured by the source cell.

[0343] In the embodiments described herein, the source cell notifies the target cell to include the T310 threshold and T312 threshold of the SHR determined by the source cell in the OtherConfig configured by the target cell. This information can be sent from the source cell to the target cell in a HandoverPreparationInformation message.

[0344] In the embodiments described herein, the source cell notifies the target cell of the T310 threshold and the T312 threshold for SHR determined by the source cell for the target cell. This information can be sent from the source cell to the target cell in a HandoverPreparationInformation message. The target cell includes the T310 threshold and the T312 threshold for SHR received from the source cell in an RRCReconfiguration message, which includes ReconfigurationWithSync, and is sent to UE 1102 to perform a handover from the source cell to the target cell. In the embodiments described herein, the target cell includes the T310 threshold and the T312 threshold for SHR received from the source cell as sourceThresholdPercentageT310-r18 and sourceThresholdPercentageT312-r18 (or variables with similar functionality). In the embodiments described herein, the target cell includes the T310 threshold and the T312 threshold of the SHR received from the source cell, as ThresholdPercentageT310-r17 and ThresholdPercentageT312-r17, and also includes useT310T312Threshold-FromTarget-r18 (or a variable with similar functionality).

[0345] In the example specification from TS 38.331,

[0346] -- ASN1START

[0347] -- TAG-HANDOVER-PREPARATION-INFORMATION-START

[0348] HandoverPreparationInformation ::= SEQUENCE {

[0349] criticalExtensions CHOICE {

[0350] c1 CHOICE{

[0351] handoverPreparationInformation HandoverPreparationInformation-IEs,

[0352] spare3 NULL, spare2 NULL, spare1 NULL

[0353] },

[0354] criticalExtensionsFuture SEQUENCE {}

[0355] }

[0356] }

[0357] HandoverPreparationInformation-IEs ::= SEQUENCE {

[0358] ue-CapabilityRAT-List UE-CapabilityRAT-ContainerList,

[0359] sourceConfig AS-Config OPTIONAL, -- Cond HO

[0360] rrm-Config RRM-Config OPTIONAL,

[0361] as-Context AS-Context OPTIONAL,

[0362] nonCriticalExtension SEQUENCE {} OPTIONAL

[0363] }

[0364] AS-Context ::= SEQUENCE {

[0365] <only relevant IEs shown> [[

[0367] needForGapNCSG-InfoNR-r17 NeedForGapNCSG-InfoNR-r17 OPTIONAL,

[0368] needForGapNCSG-InfoEUTRA-r17 NeedForGapNCSG-InfoEUTRA-r17 OPTIONAL,

[0369] mbsInterestIndication-r17 OCTET STRING (CONTAININGMBSInterestIndication-r17) OPTIONAL

[0370] ]], [[

[0372] thresholdPercentageT310-r18 ENUMERATED {p40, p60, p80, spare5,spare4, spare3, spare2, spare1} OPTIONAL,

[0373] thresholdPercentageT312-r18 ENUMERATED {p20, p40, p60, p80, spare4,spare3, spare2, spare1} OPTIONAL, ]]

[0375] }

[0376] -- TAG-HANDOVER-PREPARATION-INFORMATION-STOP

[0377] -- ASN1STOP

[0378] ThresholdPercentageT310-r18 and ThresholdPercentageT312-r18 are the T310 and T312 thresholds of the SHR determined by the source cell.

[0379] In the embodiments described herein, the target PSCell includes, in its SuccessPSCell-Config, a T310-SCG threshold and a T312-SCG threshold for the SPR from the source PSCell, separate from the T310-SCG threshold and T312-SCG threshold for the SPR from the target PSCell. The T310-SCG threshold and T312-SCG threshold for the SPR from the source PSCell included in the target PSCell's SuccessPSCell-Config are used to determine the SPR from the source PSCell to the target PSCell, while the T310-SCG threshold and T312-SCG threshold for the SPR from the target PSCell included in the target PSCell's SuccessPSCell-Config are used to determine the SPR of a PSCellChange from the target PSCell to another PSCell, where the target PSCell becomes the source PSCell.

[0380] In the embodiments herein, according to TS 38.331,

[0381] SuccessPSCell-Config-r18 ::= SEQUENCE {

[0382] thresholdPercentageT304-SCG-r18 ENUMERATED {p40, p60, p80, spare5,spare4, spare3, spare2, spare1} OPTIONAL, --Need R

[0383] thresholdPercentageT310-SCG-r18 ENUMERATED {p40, p60, p80, spare5,spare4, spare3, spare2, spare1} OPTIONAL, --Need R

[0384] thresholdPercentageT312-SCG-r18 ENUMERATED {p20, p40, p60, p80,spare4, spare3, spare2, spare1} OPTIONAL, --Need R

[0385] sourceThresholdPercentageT310-SCG-r18 ENUMERATED {p40, p60, p80,spare5, spare4, spare3, spare2, spare1} OPTIONAL, --Need R

[0386] sourceThresholdPercentageT312-SCG-r18 ENUMERATED {p20, p40, p60, p80,spare4, spare3, spare2, spare1} OPTIONAL, --Need R ...

[0388] }

[0389] sourceThresholdPercentageT310-SCG-r18: This field is included in the SuccessPSCell-Config configured by the target PSCell. If this field is configured, UE 1102 uses it when determining successful PSCell add or change information (instead of ThresholdPercentageT310-SCG-r18 included in the source PSCell OtherConfig).

[0390] UE 1102 uses sourceThresholdPercentageT310-SCG-r18 from OtherConfig of the target PSCell as if it were received from OtherConfig of the source PSCell.

[0391] sourceThresholdPercentageT312-SCG-r18: This field is included in the SuccessPSCell-Config configured by the target PSCell. If this field is configured, UE 1102 uses it when determining successful PSCell add or change information (instead of ThresholdPercentageT312-SCG-r18 included in the source PSCell OtherConfig).

[0392] The sourceThresholdPercentageT312-SCG-r18 is received from the target PSCell's OtherConfig as if it were received from the source PSCell's OtherConfig.

[0393] 5.3.5.9 Other Configurations

[0394] 1> If the received otherConfig includes SuccessPSCell-Config (and SuccessPSCell-Config is set):

[0395] 2> If sourceThresholdPercentageT310-SCG-r18 is included

[0396] 3> Treat sourceThresholdPercentageT310-SCG-r18 as ThresholdPercentageT310-SCG-r18 configured by the source cell.

[0397] 2> If sourceThresholdPercentageT312-SCG-r18 is included

[0398] 3> Treat sourceThresholdPercentageT312-SCG-r18 as ThresholdPercentageT312-SCG-r18 configured by the source cell.

[0399] Alternatively,

[0400] 5.3.5.9 Other Configurations

[0401] 1> If the otherConfig received from the target PSCell includes SuccessPSCell-Config (and SuccessPSCell-Config is set):

[0402] 2> If sourceThresholdPercentageT310-SCG-r18 is included

[0403] 3> Treat sourceThresholdPercentageT310-SCG-r18 as ThresholdPercentageT310-SCG-r18 configured by the source cell.

[0404] 2> If sourceThresholdPercentageT312-SCG-r18 is included

[0405] 3> Treat sourceThresholdPercentageT312-SCG-r18 as ThresholdPercentageT312-SCG-r18 configured by the source cell.

[0406] In the embodiments described herein, UE 1102 notifies the network whether it can use the T310 and T312 thresholds for SHR in the target cell's configuration (i.e., SuccessHO-Config). In Nr, this can be notified as a single bit of per-UE capability in the UECapabilityInformation RRC message. The network uses this information to configure sourceThresholdPercentageT310-r18, sourceThresholdPercentageT312-r18, or useT310T312Threshold-FromTarget-r18 in the target cell's SuccessHO-Config.

[0407] In the embodiments described herein, UE 1102 notifies the network whether it can use the T310 and T312 thresholds for SHR in the target cell's configuration (i.e., SuccessHO-Config); that is, UE 1102 notifies whether it can process the fields sourceThresholdPercentageT310-r18, sourceThresholdPercentageT312-r18, or useT310T312Threshold-FromTarget-r18 in the SHR configuration according to the above embodiments of the present invention. In NR, this can be notified as a single bit per UE capability in the UECapabilityInformation RRC message. The network uses this information to configure sourceThresholdPercentageT310-r18, sourceThresholdPercentageT312-r18, or useT310T312Threshold-FromTarget-r18 in the target cell's SuccessHO-Config.

[0408] In the embodiments described herein, UE 1102 notifies the network whether it can use the T310-SCG and T312-SCG thresholds for SPR in the configuration of the target PSCell (i.e., SuccessPSCell-Config). This can be notified as a single bit of per-UE capability in the UECapabilityInformation RRC message. The network uses this information to configure sourceThresholdPercentageT310-SCG-r18 or sourceThresholdPercentageT312-SCG-r18 or useT310T312Threshold-FromTarget-r18 in the SuccessHO-Config of the target cell.

[0409] In the embodiments described herein, when an RRCReconfiguration including ReconfigurationWithSync is sent via SRB3, the network node configures UE 1102 using the T310-SCG threshold (ThresholdPercentageT310-SCG-r18) and T312-SCG threshold (ThresholdPercentageT312-SCG-r18) from the source PSCell before sending the PSCellChange ReconfigurationSync to UE 1102. The source PSCell may include the T310 / T312 thresholds in the RRCReconfiguration, which contains the ReconfigurationSync generated by itself for the PSCellChange in which it is the target. When an RRCReconfiguration message including ReconfigurationWithSync for PSCellChange is sent via SRB3, the source PSCell may include the T310 / T312 threshold in the RRCReconfiguration message sent before sending the RRCReconfiguration message including ReconfigurationWithSync.

[0410] In the embodiments described herein, SuccessHO-Config is included as a setting whenever the source cell includes it. In the embodiments described herein, SuccessHO-Config is included as a setting whenever the target cell includes it.

[0411] In the embodiments described herein, SuccessPSCell-Config is included as a setting whenever the source PSCell includes it. Similarly, in the embodiments described herein, SuccessPSCell-Config is included as a setting whenever the target PSCell includes it.

[0412] In the embodiments described herein, it is included as a setting whenever PCell includes SuccessPSCell-Config.

[0413] Figure 2 This is an example flowchart for determining a Successful Handover Report (SHR). As shown in flowchart 200, in step 202, UE 1102 can receive threshold parameters T310 and T312 for the SHR from the target cell. In step 204, UE 1102 can receive useAllSCGConfig from the target in the SHR configuration. In step 206, UE 1102 can apply the T310 and T312 thresholds of the threshold parameters SHR from the target cell to determine the SHR.

[0414] As shown in flowchart 200, the process begins with network entity 1202 configuring UE 1102 to report a successful PSCell change along with additional information. UE 1102 is responsible for detecting when a PSCell transition occurs and sending a corresponding report to the network, thereby allowing network entity 1202 to effectively monitor mobility transitions.

[0415] Once UE 1102 reports a PSCell change, network entity 1102 continues to configure UE 1102 to perform the PSCell change via signaling radio bearer 3 (SRB3) in the RRC reconfiguration message. SRB3 is used to manage control plane signaling specifically for secondary cell group (SCG) configuration. This ensures that UE 1102 applies the new mobility configuration while maintaining connection stability.

[0416] The next phase involves setting threshold parameters to regulate network transitions. UE 1102 is configured to process T310-SCG and T312-SCG thresholds, which affect UE 1102's response to RLF and mobility events. T310-SCG (ThresholdPercentageT310-SCG-r18) defines the timer expiration for detecting radio link failures on secondary cell groups (SCGs), while T312-SCG (ThresholdPercentageT312-SCG-r18) determines the delay before UE 1102 declares a failure or attempts to rebuild.

[0417] Figure 3This is an example flowchart for determining the SHR using at least one threshold parameter. (See flowchart 300.) Figure 3 As shown, in step 302, UE 1102 can be configured to receive sourceThresholdPercentageT310-r18 and sourceThresholdPercentageT312-r18 from the target cell.

[0418] Network entity 1202 configures at least one threshold parameter, which may include, but is not limited to, T310-SCG (ThresholdPercentageT310-SCG-r18) and T312-SCG (ThresholdPercentageT312-SCG-r18). The T310-SCG parameter defines the timer expiration threshold for detecting radio link failures on secondary cell groups (SCGs). The T312-SCG parameter defines the delay before declaring a failure or initiating a reconstruction process.

[0419] Threshold parameters help UE 1102 determine when to retry PSCell reconfiguration, declare a link failure, or handover to an alternative cell. In step 304, UE 1102 can apply the configured thresholds and adjust connectivity. Once UE 1102 receives the new configuration, it applies the T310-SCG and T312-SCG thresholds to adjust its response to potential radio link failures. Therefore, if the T310-SCG timer expires, UE 1102 initiates an RLF recovery procedure. If the T312-SCG threshold is reached, UE 1102 declares a failure and can initiate a rebuild or handover procedure.

[0420] Figure 4 This is an example flowchart for determining the SPR using at least one threshold parameter. In step 402 of flowchart 400, UE 1102 can receive sourceThresholdPercentageT310-SCG-r18 and sourceThresholdPercentageT312-SCG-r18 from the target PSCell. In step 404, UE 1102 can apply the T310-SCG and T312-SCG thresholds of the SPR from the target PSCell to perform SPR determination.

[0421] Figure 5 This is an example diagram depicting UE 1102 performing a UE 1102 capability report for SHR. (Example...) Figure 5As depicted, in step 1, UE 1102 receives a capability request from gNB 500. In step 2, UE 1102 can provide capability information including the ability to apply T310 and T312 thresholds received from the target cell for SHR determination. Specifically, this relates to radio link failure recovery, mobility management, and secondary handover recovery (SHR).

[0422] Figure 6 This is an example diagram depicting the interaction between the source gNB and the target gNB used to perform a handover operation in an SHR configuration. For example... Figure 6 As shown, the source gNB 500A and the target gNB 500B interact to perform a handover. In step 1, the target gNB 500B may send a HandoverRequest including HandoverPreparationInformation, which contains T310 and T312 thresholds for SHR configuration. In step 2, the source gNB 500A, upon receiving the request, may provide a HandoverRequest acknowledgment to perform the handover operation.

[0423] Figure 7 This is an example flowchart illustrating a scenario with a successPSCell-Config that attempts conditional reconfiguration / LTM. For example... Figure 7 As shown, flowchart 700 depicts UE 1102 and network entity 1202 handling radio link failure (RLF) and mobility transition. This step begins at 702 to determine the RLF. In step 704, UE 1102 determines whether parameters related to conditional reconfiguration and mobility handover attempts are configured. These parameters include `attemptCondReconfig` and `attemptLTM-Switch`, which affect whether UE 1102 retains or releases the `successPSCell` configuration. In step 706, if the parameters related to conditional reconfiguration and mobility handover attempts are configured, UE 1102 retains the `successPSCell` configuration as part of the rebuild process. In step 708, if the parameters are not configured, UE 1102 releases the `successPSCell` configuration configured by PSCell.

[0424] Figure 8 This is an example flowchart illustrating a scenario where cell selection is performed during T311 runtime with successPSCell-Config. (Example...) Figure 8As shown, flowchart 800 begins with cell selection, while timer T311 is running. In step 802, UE 1002 determines whether parameters associated with conditional reconfiguration and mobility handover, such as attemptCondReconfig or attemptLTM-Switch, are configured. In step 804, if UE 1002 determines that the parameters are configured, it can release successPSCell-Config configured by PSCell.

[0425] Flowchart 800 considers the scenario where UE 1102 cannot apply LTM-based candidate configurations or conditional reconfigurations during cell selection when the timer is active. In this case, UE 1102 releases the PSCell configuration after completing cell selection. Threshold parameters T310 and T312 are used for optimized mobility.

[0426] Figure 9 This is an example flowchart illustrating a scenario where cell selection is performed during T311 in an attempt to perform conditional reconfiguration / LTM runtime. As shown in flowchart 900, in step 902, cell selection is performed when timer T311 is activated. In step 904, it is checked whether UE 1102 has applied the stored condRRCReconfig associated with the selected cell and has not yet performed an LTM cell handover procedure for the selected LTM candidate cell. In step 304, if it is determined that UE 1102 has not yet performed an LTM cell handover for the selected LTM candidate cell, it can proceed to step 906. In step 906, if attemptCondReconfig or attemptLTM-Switch is configured, it can proceed to step 908. In step 908, UE 1102 resets the MAC, releases successPSCell-Config, and performs other UE 1102-related operations.

[0427] Figure 10 This is an example sequence diagram illustrating a scenario of UE 1102 capability reporting for RACH in response to PDCCH commands. (Example...) Figure 4 The sequence diagram shown illustrates the interaction between UE 1102 and next-generation Node B / base station (gNB) 500 for processing PDCCH command RACH (Physical Downlink Control Channel Command Random Access Channel) configuration and scheduling within the wireless communication network.

[0428] In step 1, starting with UE 1102, a capability query request originates from gNB 500. UE 1102 can configure the cell group to handle interruptions during the PDCCH command RACH. UE 1102 configures itself to recognize and respond to PDCCH commands that trigger the random access procedure, which is essential for establishing and maintaining a connection with gNB 500.

[0429] In step 2, the UE 1102, which has configuration capabilities, can interact with the gNB 500 to handle the scheduling and allocation of cell group authorizations. The gNB 500 processes the configuration received from the UE 1102 and ensures that resources are allocated efficiently based on the current network conditions and the UE's capabilities.

[0430] Therefore, ensuring that UE 1102 and gNB 500 remain synchronized allows for smooth RACH-based access procedures, network access, mobility, and radio link recovery. This interaction facilitates dynamic resource allocation and ensures that UE 1102 can successfully perform access procedures while minimizing latency and interruptions.

[0431] Figure 11 Various hardware components for a UE 1102 used to handle radio link failures (RLF) in a wireless communication network 100 are illustrated. In an embodiment, the UE 1102 includes a processor 1104, a memory 1106, a communicator 1108, and a radio link failure (RLF) controller 1110. The processor 1104 is coupled to the communicator 1108, the memory 1106, and the RLF controller 1110.

[0432] RLF controller 1110 can determine whether at least one parameter related to conditional reconfiguration or mobility handover attempt is configured when initiating RRC reconstruction. If the parameter is detected, RLF controller 1110 instructs UE 1102 to retain the successPSCell configuration, thereby allowing UE 1102 to continue operating using the previously assigned primary and secondary cells (PSCells).

[0433] If the RLF controller 1110 determines that there is neither a configuration condition reconfiguration nor a configuration mobility handover attempt, it instructs UE 1102 to release the successPSCell configuration. This enables the UE 1102 to reset and select a new cell for rebuilding, thus preventing UE 1102 from relying on an outdated or ineffective PSCell configuration.

[0434] Therefore, the RLF controller 1110 operates by first evaluating whether at least one parameter related to a conditional reconfiguration or mobility handover attempt exists when initiating the RRC rebuild process. If the parameter is configured, the controller indicates that the UE 1102 is undergoing a planned reconfiguration or mobility handover, which retains the existing PSCell configuration.

[0435] When the RLF controller 1110 determines that a conditional reconfiguration or mobility handover attempt has been configured, it instructs UE 1102 to retain the successPSCell configuration. UE 1102 continues to use the previously assigned PSCell. By retaining the PSCell configuration, UE 1102 avoids unnecessary interruptions and can quickly resume communication with the network.

[0436] If the RLF controller 1110 determines that there is neither a configuration condition reconfiguration nor a configuration mobility handover attempt, it decides to release the successPSCell configuration. Therefore, UE 1102 is allowed to discard the previous PSCell.

[0437] The interaction between the RLF controller 1110, processor 1104, and memory 1106 ensures efficient handling of radio link failure recovery.

[0438] The embodiments described herein focus on handling primary and secondary cell (PSCell) configurations during radio link failure (RLF) recovery in wireless communication networks. This involves determining parameters related to conditional reconfiguration and mobility handover attempts to determine whether to retain or release the successPSCell configuration based on various network conditions.

[0439] Parameters such as attemptCondReconfig and attemptLTM-Switch are used to manage PSCell conversions. These parameters indicate whether a conditional reconfiguration or mobility switch attempt has been triggered.

[0440] This embodiment includes a scenario where UE 1102 may need to release the successPSCell configuration. If recovery based on Conditional Handover (CHO) or recovery based on Lower Layer Triggered Mobility (LTM) fails, and if conditional reconfiguration and / or mobility handover attempts have been configured, UE 1102 releases the successPSCell configuration. This ensures that UE 1102 does not continue to use the no longer viable PSCell, allowing it to transition to a more stable network connection.

[0441] In another embodiment, when UE 1102 determines that an LTM-based candidate configuration or conditional reconfiguration cannot be applied during cell selection, UE 1102 releases the successPSCell configuration if the timer is active and configured with the necessary parameters related to conditional reconfiguration and mobility handover attempts. This step prevents UE 1102 from maintaining an invalid PSCell setting and allows it to establish a new, more suitable connection in the network.

[0442] This embodiment ensures that UE 1102 dynamically assesses mobility and recovery conditions regarding PSCell configuration retention or release based on real-time network conditions. By combining CHO-based and LTM-based recovery mechanisms, mobility transitions are optimized, network stability is enhanced, and the efficiency of the RRC reconstruction process in the wireless communication system is improved.

[0443] As used herein, UE 1102 can be an electronic device / user equipment used by a user to connect to, interact with, and / or control the operation of multiple other devices using a 3GPP network. Examples of UE 1102 may include, but are not limited to, smartphones, mobile phones, video phones, computers, tablet PCs, laptops, wearable devices, televisions, personal digital assistants (PDAs), IoT devices, or any other device that can use a 3GPP network or a non-3GPP network.

[0444] The RLF controller 1110 is implemented by analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, etc., and may optionally be driven by firmware.

[0445] Processor 1104 may include one or more processors. The one or more processors may be general-purpose processors (such as central processing unit (CPU), application processor (AP), etc.), pure graphics processing units (such as graphics processing unit (GPU), vision processing unit (VPU)) and / or AI-specific processors (such as neural processing unit (NPU)). Processor 1104 may include multiple cores and is configured to execute instructions stored in memory 1106.

[0446] Furthermore, processor 1104 is configured to execute instructions stored in memory 1106 and perform various processes. Communicator 1108 is configured for internal communication between internal hardware components and for communication with external devices via one or more networks. Memory 1106 also stores instructions to be executed by processor 1104. Memory 1106 may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard disks, optical disks, floppy disks, flash memory, or electrically programmable memory (EPROM) or electrically erasable programmable memory (EEPROM). Additionally, in some examples, memory 1106 may be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or propagating signal. However, the term "non-transitory" should not be construed as meaning that memory 1106 is immovable. In some instances, a non-transitory storage medium may store data that can change over time (e.g., in random access memory (RAM) or cache memory).

[0447] Figure 12 Various hardware components for configuring at least one threshold parameter in a network entity 1202 in a wireless communication network 100 are illustrated. The network entity may include, but is not limited to, next-generation node B (gNB), evolved Node B (eNB), target gNB, source gNB, primary cell, secondary cell, primary node (MN), secondary node (SN), etc. In an embodiment, network entity 1202 includes a processor 1204, a memory 1206, a communicator 1208, and a threshold configuration controller 1210.

[0448] The threshold configuration controller 1210 includes a processor 1204, which is responsible for executing commands related to network entity 1202 for configuring threshold parameters.

[0449] The threshold configuration controller 1210 can report successful PSCell changes and additional information to the network using the successPSCell-Config from the source primary / secondary cell (PSCell). The report includes the successPSCell-Config from the source PSCell, which helps the network track handover. The threshold configuration controller 1210 uses an RRC reconfiguration message via Signaling Radio Bearer 3 (SRB3) to configure UE 1102 to perform PSCell changes. SRB3 is a dedicated signaling bearer that allows control plane communication between UE 1102 and the network, thereby ensuring a smooth PSCell transition.

[0450] The threshold configuration controller 1210 of network entity 1202 configures UE 1102 to apply threshold parameters T310-SCG and T312-SCG. The T310-SCG threshold determines the expiration of a timer used to detect radio link failure in a secondary cell group (SCG), while the T312-SCG threshold defines the delay before a failure is declared or a reconstruction attempt is made.

[0451] Network entity 1202 (which may be, but is not limited to, gNB 500 (next-generation node B), source gNB 500A, target gNB 500B, or another control unit) interacts with UE 1102 to send configuration updates, process PSCell reports, and listen for network transitions.

[0452] The threshold configuration controller 1210 is implemented by analog and / or digital circuits (such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, etc.) and may optionally be driven by firmware.

[0453] Processor 1204 may include one or more processors. The one or more processors may be general-purpose processors (such as central processing unit (CPU), application processor (AP), etc.), pure graphics processing units (such as graphics processing unit (GPU), visual processing unit (VPU)), and / or AI-specific processors (such as neural processing unit (NPU)). Processor 1204 may include multiple cores and is configured to execute instructions stored in memory 1206.

[0454] Furthermore, processor 1204 is configured to execute instructions stored in memory 1206 and perform various processes. Communicator 1208 is configured for internal communication between internal hardware components and for communication with external devices via one or more networks. Memory 1206 also stores instructions to be executed by processor 1204. Memory 1206 may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard disks, optical disks, floppy disks, flash memory, or electrically programmable memory (EPROM) or electrically erasable programmable memory (EEPROM). Additionally, in some examples, memory 1206 may be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or propagating signal. However, the term "non-transitory" should not be construed as meaning that memory 1206 is non-removable. In some instances, a non-transitory storage medium may store data that can change over time (e.g., in random access memory (RAM) or cache memory).

[0455] In this embodiment, UE 1102 records a successful PSCell change or add report (successPSCell-Config) for PSCell mobility initiated against the MN based on a successful PSCell change or add report configuration, and uses this information for PSCell mobility initiated by the SN based on the configuration from the PSCell. When UE 1102 recovers from RLF based on conditional reconfiguration or LTM configuration, the source PSCell and UE 1102 need to be synchronized relative to successPSCell-Config. Similarly, when a recovery attempt fails and a new PSCell is configured, the new PSCell and UE 1102 need to be synchronized relative to successPSCell-Config.

[0456] Network entities need to be able to use SRB3 to configure successPSCell-Config for UE 1102 in order to avoid unnecessary signaling between MN and SN and between MN and UE 1102.

[0457] In the embodiment, after selecting a suitable NR cell during T311 operation, UE 1102 checks whether it has applied the stored conditional reconfiguration (condRRCReconfig) associated with the selected cell and has not yet performed an LTM cell handover procedure for the selected LTM candidate cell (e.g., as per Clause 5.3.7.3). If so, UE 1102 further checks whether UE 1102 is configured to apply the stored conditional reconfiguration (condRRCReconfig) associated with the selected cell or the stored LTM candidate cell associated with the selected cell. If so, UE 1102 resets the MAC, releases a set of configurations, and suspends all RB and BH RLC channels of IAB-MT except for SRB0 and broadcast MRB.

[0458] In an embodiment, this may be represented as follows in TS 38.331.

[0459] 5.3.7.3 Actions after cell selection during T311 runtime

[0460] When selecting a suitable NR cell, the UE should:

[0461] 1> Ensure that the basic system information as specified in Clause 5.2.2.2 is valid and up-to-date;

[0462] 1> Stop timer T311;

[0463] 1> If T390 is running:

[0464] 2> Stop timer T390 for all access categories;

[0465] 2> Perform the actions specified in 5.3.14.4;

[0466] 1> Stop the relay (re)selection process (if in progress);

[0467] 1> If cell selection is triggered by detecting a radio link failure of the MCG, a reconfiguration failure of the MCG with synchronization, or mobility failure from an NR failure, and

[0468] 1> If attemptCondReconfig is configured; and

[0469] 1> If the selected cell is not configured with CondEventT1, or if the selected cell is configured with CondEventT1 but the leave conditions have not yet been met; and

[0470] 1> If the selected cell is one of the candidate cells in the masterCellGroup included in MCGVarConditionalReconfig for its reconfigurationWithSync, and condExecutionCondPSCell is not configured for the corresponding condReconfigId in MCGVarConditionalReconfig, then:

[0471] 2> If the UE supports RLF reporting for conditional handover, set choCellId in VarRLF-Report to the global cell identifier (if available), otherwise set to the physical cell identifier and carrier frequency of the selected cell;

[0472] 2> Apply the stored condRRCReconfig associated with the selected cell and perform the actions specified in 5.3.5.3;

[0473] Note 1: In the event of a failed handover without key changes, how to avoid key stream reuse in the case of CHO-based recovery is left to the network implementation.

[0474] 1> If cell selection is triggered by detecting a radio link failure of the MCG or a synchronized reconfiguration failure of the MCG for an LTM cell handover procedure, the LTM cell handover procedure is triggered upon instruction from a lower layer as specified in Clause 5.3.5.18.6; and

[0475] 1> If attemptLTM-Switch is configured; and

[0476] 1> If the selected cell is one of the LTM candidate cells in the LTM-CandidateIE within the ltm-Config associated with the MCG, then:

[0477] 2> Perform the LTM cell handover procedure for the selected LTM candidate cell according to the actions specified in 5.3.5.18.6;

[0478] Note 2: When both attemptCondReconfig and attemptLTM-Switch are configured, which process to execute depends on the UE implementation.

[0479] 1> If the UE has not yet applied the stored condRRCReconfig associated with the selected cell, and has not yet performed an LTM cell handover procedure for the selected LTM candidate cell, as described above:

[0480] 2> If the UE is configured with attemptCondReconfig; or

[0481] 2> If the UE is configured with attemptLTM-Switch:

[0482] 3> Reset MAC address;

[0483] 3> Release spCellConfig (if configured);

[0484] 3> Release the MCG SCell (if configured);

[0485] 3> Release delayBudgetReportingConfig (if configured) and stop timer T342 (if running);

[0486] 3> Release overheatingAssistanceConfig (if configured) and stop timer T345 (if running);

[0487] 3> If MR-DC is configured:

[0488] 4> Perform MR-DC release as specified in Clause 5.3.5.10;

[0489] 3> Release idc-AssistanceConfig (if configured);

[0490] 3> Release btNameList (if configured);

[0491] 3> Release wlanNameList (if configured);

[0492] 3> Release sensorNameList (if configured);

[0493] 3> Release drx-PreferenceConfig for MCG (if configured) and stop timer T346a associated with MCG (if running);

[0494] 3> Release the maxBW-PreferenceConfig of the MCG (if configured) and stop the timer T346b associated with the MCG (if running);

[0495] 3> Release MCG's maxCC-PreferenceConfig (if configured) and stop the timer T346c associated with MCG (if running);

[0496] 3> Release the maxMIMO-LayerPreferenceConfig of the MCG (if configured) and stop the timer T346d associated with the MCG (if running);

[0497] 3> Release the minSchedulingOffsetPreferenceConfig of the MCG (if configured) and stop the timer T346e associated with the MCG (if running);

[0498] 3> Release the rlm-RelaxationReportingConfig of the MCG (if configured) and stop the timer T346j associated with the MCG (if running);

[0499] 3> Release the bfd-RelaxationReportingConfig of the MCG (if configured) and stop the timer T346k associated with the MCG (if running);

[0500] 3> Release releasePreferenceConfig (if configured) and stop timer T346f (if running);

[0501] 3> Release onDemandSIB-Request (if configured) and stop timer T350 (if running);

[0502] 3> Release referenceTimePreferenceReporting (if configured);

[0503] 3> Release sl-AssistanceConfigNR (if configured);

[0504] 3> Release obtainCommonLocation (if configured);

[0505] 3> Release scg-DeactivationPreferenceConfig (if configured) and stop timer T346i (if running);

[0506] 3> Release musim-GapAssistanceConfig (if configured), and if it is running, stop timer T346h;

[0507] 3> Release musim-GapPriorityAssistanceConfig (if configured);

[0508] 3> Release musim-LeaveAssistanceConfig (if configured);

[0509] 3> Release musim-CapabilityRestrictionConfig (if configured) and stop timer T346n (if running);

[0510] 3> Release propDelayDiffReportConfig (if configured);

[0511] 3> Release ul-GapFR2-PreferenceConfig (if configured);

[0512] 3> Release rrm-MeasRelaxationReportingConfig (if configured);

[0513] 3> Release maxBW-PreferenceConfigFR2-2 (if configured);

[0514] 3> Release maxMIMO-LayerPreferenceConfigFR2-2 (if configured);

[0515] 3> Release minSchedulingOffsetPreferenceConfigExt (if configured);

[0516] 3> Release aerial-FlightPathAvailabilityConfig (if configured);

[0517] 3> Release ul-TrafficInfoReportingConfig (if configured) and stop all instances of timer T346l (if running);

[0518] 3> Suspend all RB and BH RLC channels used for IAB-MT, except for SRB0 and broadcast MRB;

[0519] 2> Remove all entries (if any) from MCG VarConditionalReconfig;

[0520] 2> Perform the LTM configuration release procedure for MCG and SCG as specified in Clause 5.3.5.18.7;

[0521] In an embodiment,

[0522] 5.3.7 RRC Connection Reconstruction

[0523] 5.3.7.2 Initiate

[0524] The UE initiates this procedure when one of the conditions specified in TS 38.331 5.3.7.2 is met:

[0525] When initiating this process, the UE should:

[0526] 1> Stop timer T310 (if running);

[0527] 1> Stop timer T312 (if it is running);

[0528] 1> Stop timer T304 (if running);

[0529] 1> Start timer T311;

[0530] 1> Stop timer T316 (if running);

[0531] 1> If the UE is not configured with attemptCondReconfig; and

[0532] 1> If the UE is not configured with attemptLTM-Switch, and cell selection is triggered by detecting a radio link failure of the MCG or a synchronized reconfiguration failure of the MCG for the LTM cell handover process, the LTM cell handover process is triggered upon indication from the lower layer:

[0533] 2> Reset MAC address;

[0534] 2> Release spCellConfig (if configured);

[0535] 2> Suspend all RBs except SRB0 and broadcast MRB, the BH RLC channel for IAB-MT, and the Uu trunk RLC channel for L2U2N trunk UEs;

[0536] 2> Release the MCG SCell (if configured);

[0537] 2> If MR-DC is configured:

[0538] 3> Perform MR-DC release as specified in Clause 5.3.5.10;

[0539] 2> Perform the LTM configuration release procedure for MCG and SCG as specified in Clause 5.3.5.18.7;

[0540] 2> Release the set

[0541] 1> Release successHO-Config (if configured);

[0542] 1> Release successPSCell-Config configured by PCell (if configured);

[0543] 5.3.7.3 Actions after cell selection during T311 runtime

[0544] When selecting a suitable NR cell, the UE should:

[0545] 1> Ensure that the basic system information as specified in Clause 5.2.2.2 is valid and up-to-date;

[0546] 1> Stop timer T311;

[0547] 1> If T390 is running:

[0548] 2> Stop timer T390 for all access categories;

[0549] 2> Perform the actions specified in 5.3.14.4;

[0550] 1> Stop the relay (re)selection process (if in progress);

[0551] 1> If cell selection is triggered by detecting a radio link failure of the MCG, a reconfiguration failure of the MCG with synchronization, or mobility failure from an NR failure, and

[0552] 1> If attemptCondReconfig is configured; and

[0553] 1> If the selected cell is not configured with CondEventT1, or if the selected cell is configured with CondEventT1 but the leave conditions have not yet been met; and

[0554] 1> If the selected cell is one of the candidate cells in the masterCellGroup included in MCGVarConditionalReconfig for its reconfigurationWithSync, and condExecutionCondPSCell is not configured for the corresponding condReconfigId in MCGVarConditionalReconfig, then:

[0555] 2> If the UE supports RLF reporting for conditional handover, set choCellId in VarRLF-Report to the global cell identifier (if available), otherwise set to the physical cell identifier and carrier frequency of the selected cell;

[0556] 2> Apply the stored condRRCReconfig associated with the selected cell and perform the actions specified in 5.3.5.3;

[0557] Note 1: In the event of a failed handover without key changes, how to avoid key stream reuse in the case of CHO-based recovery is left to the network implementation.

[0558] 1> If cell selection is triggered by detecting a radio link failure of the MCG or a synchronized reconfiguration failure of the MCG for an LTM cell handover procedure, the LTM cell handover procedure is triggered upon instruction from a lower layer as specified in Clause 5.3.5.18.6; and

[0559] 1> If attemptLTM-Switch is configured; and

[0560] 1> If the selected cell is one of the LTM candidate cells in the LTM-CandidateIE within the ltm-Config associated with the MCG, then:

[0561] 2> Perform the LTM cell handover procedure for the selected LTM candidate cell according to the actions specified in 5.3.5.18.6;

[0562] Note 2: When both attemptCondReconfig and attemptLTM-Switch are configured, which process to execute depends on the UE implementation.

[0563] 1> If the UE has not yet applied the stored condRRCReconfig associated with the selected cell, and has not yet performed an LTM cell handover procedure for the selected LTM candidate cell, as described above:

[0564] 2> If the UE is configured with attemptCondReconfig; or

[0565] 2> If the UE is configured with attemptLTM-Switch, and cell selection is triggered by detecting a radio link failure of the MCG or a synchronized reconfiguration failure of the MCG for the LTM cell handover process, the LTM cell handover process is triggered upon indication from the lower layer:

[0566] 3> Reset MAC address;

[0567] 2> Release the set

[0568] 2> Remove all entries (if any) from MCG VarConditionalReconfig;

[0569] 2> Perform the LTM configuration release procedure for MCG and SCG as specified in Clause 5.3.5.18.7;

[0570] In this embodiment, UE 1102 informs the network of its ability to cause an interruption in the DL slot on the serving cell due to RACH transmission of PDCCH commands for the same cell group.

[0571]

[0572] For example, if UE 1102, which has been notified to the network that it can avoid interruption of the DL slot on the serving cell due to RACH transmission of PDCCH commands for the same cell group, receives RACH transmission of PDCCH commands for the MCG, it may cause an interruption of the serving cell on the SCG, but not an interruption on the MCG. Similarly, if UE 1102, which has been notified to the network that it can avoid interruption of the DL slot on the serving cell due to RACH transmission of PDCCH commands for the same cell group, receives RACH transmission of PDCCH commands for the SCG, it may cause an interruption of the serving cell on the MCG, but not an interruption on the SCG.

[0573]

[0574] UE 1102 reports an interruption length due to RF retuning of the RACH of the PDCCH command, where the resources of the RACH of the PDCCH command are not fully contained in the UL BWP of the active serving cell in the same cell group configured by the UE. If UE 1102 receives a PDCCH command on an MCG LTM candidate cell, UE 1102 will create an interruption of the specified length due to RF retuning of the RACH of the PDCCH command, where the resources are not fully contained in any ULBWP of the active serving cell in the MCG configured by the UE. During this interval, MN will not schedule UE 1102 for UL transmissions or schedule any DL transmissions. SN may schedule UE 1102 for UL transmissions or schedule any DL transmissions during this interval.

[0575] Similarly, if UE 1102 receives a PDCCH command on an SCG LTM candidate cell, UE 1102 will create a specified-length interruption due to RF realignment of the RACH of the PDCCH command, where resources are not fully contained in any UL BWP of the UE's configured SCG active serving cell. During this interval, SN will not schedule UE 1102 for UL transmissions or any DL transmissions. MN may schedule UE 1102 for UL transmissions or any DL transmissions during this interval.

[0576] In this embodiment, if UE 1102 is configured with attemptCondReconfig (or any variable with equivalent functionality) or attemptLTM-Switch (or any variable with equivalent functionality) when initiating an RRC re-establishment procedure (or equivalent procedure), then UE 1102 retains successPSCell-Config configured by PSCell (if configured). If neither attemptCondReconfig nor attemptLTM-Switch is configured, then UE 1102 releases successPSCell-Config configured by PSCell when initiating an RRC connection re-establishment.

[0577] In an embodiment, if UE 1102 cannot apply LTM candidate configuration or conditional reconfiguration during cell selection when running at T311, and if at least one of attemptCondReconfig and attemptLTM-Switch is configured, then UE 1102 releases successPSCell-Config configured by PSCell after cell selection when running at T311.

[0578] In this embodiment, if UE 1102 supports RLF reporting for LTM, the choCellId in VarRLF-Report is set to the global cell identifier (if available), otherwise it is set to the physical cell identifier and carrier frequency of the selected cell.

[0579] 5.3.7 RRC Connection Reconstruction

[0580] 5.3.7.2 Initiate

[0581] The UE initiates this procedure when one of the conditions specified in TS 38.331 5.3.7.2 is met:

[0582] When initiating this process, the UE should:

[0583] 1> Stop timer T310 (if running);

[0584] 1> Stop timer T312 (if it is running);

[0585] 1> Stop timer T304 (if running);

[0586] 1> Start timer T311;

[0587] 1> Stop timer T316 (if running);

[0588] 1> If the UE is not configured with attemptCondReconfig; and

[0589] 1> If the UE is not configured with attemptLTM-Switch:

[0590] 2> Reset MAC address;

[0591] 2> Release spCellConfig (if configured);

[0592] 2> Suspend all RBs except SRB0 and broadcast MRB, the BH RLC channel for IAB-MT, and the Uu trunk RLC channel for L2U2N trunk UEs;

[0593] 2> Release the MCG SCell (if configured);

[0594] 2> If MR-DC is configured:

[0595] 3> Perform MR-DC release as specified in Clause 5.3.5.10;

[0596] 2> Perform the LTM configuration release procedure for MCG and SCG as specified in Clause 5.3.5.18.7;

[0597] 2> Release delayBudgetReportingConfig (if configured) and stop timer T342 (if running);

[0598] 2> Release overheatingAssistanceConfig (if configured) and stop timer T345 (if running);

[0599] 2> Release idc-AssistanceConfig (if configured);

[0600] 2> Release btNameList (if configured);

[0601] 2> Release wlanNameList (if configured);

[0602] 2> Release sensorNameList (if configured);

[0603] 2> Release drx-PreferenceConfig for MCG (if configured) and stop timer T346a associated with MCG (if running);

[0604] 2> Release the maxBW-PreferenceConfig of the MCG (if configured) and stop the timer T346b associated with the MCG (if running);

[0605] 2> Release MCG's maxCC-PreferenceConfig (if configured) and stop the timer T346c associated with MCG (if running);

[0606] 2> Release the maxMIMO-LayerPreferenceConfig of the MCG (if configured) and stop the timer T346d associated with the MCG (if running);

[0607] 2> Release the minSchedulingOffsetPreferenceConfig of the MCG (if configured), and stop the timer T346e associated with the MCG (if running);

[0608] 2> Release the rlm-RelaxationReportingConfig of the MCG (if configured) and stop the timer T346j associated with the MCG (if running);

[0609] 2> Release the bfd-RelaxationReportingConfig of the MCG (if configured) and stop the timer T346k associated with the MCG (if running);

[0610] 2> Release releasePreferenceConfig (if configured), stop timer T346f (if running);

[0611] 2> Release onDemandSIB-Request (if configured) and stop timer T350 (if running);

[0612] 2> Release referenceTimePreferenceReporting (if configured);

[0613] 2> Release sl-AssistanceConfigNR (if configured);

[0614] 2> Release obtainCommonLocation (if configured);

[0615] 2> Release musim-GapAssistanceConfig (if configured), and stop timer T346h if it is running;

[0616] 2> Release musim-GapPriorityAssistanceConfig (if configured);

[0617] 2> Release musim-LeaveAssistanceConfig (if configured);

[0618] 2> Release musim-CapabilityRestrictionConfig (if configured) and stop timer T346n (if running);

[0619] 2> Release ul-GapFR2-PreferenceConfig (if configured);

[0620] 2> Release scg-DeactivationPreferenceConfig (if configured) and stop timer T346i (if running);

[0621] 2> Release propDelayDiffReportConfig (if configured);

[0622] 2> Release rrm-MeasRelaxationReportingConfig (if configured);

[0623] 2> Release maxBW-PreferenceConfigFR2-2 (if configured);

[0624] 2> Release maxMIMO-LayerPreferenceConfigFR2-2 (if configured);

[0625] 2> Release minSchedulingOffsetPreferenceConfigExt (if configured);

[0626] 2> multiRx-PreferenceReportingConfigFR2 (if configured), and stop timer T346m (if running);

[0627] 2> Release aerial-FlightPathAvailabilityConfig (if configured);

[0628] 2> Release ul-TrafficInfoReportingConfig (if configured) and stop all instances of timer T346l (if running);

[0629] 2> Release successPSCell-Config configured by PSCell (if configured);

[0630] 1> Release successHO-Config (if configured);

[0631] 1> Release successPSCell-Config configured by PCell (if configured);

[0632] 1> If any DAPS bearers are configured:

[0633] 2> Reset the source MAC address and release the source MAC configuration;

[0634] 2> For each DAPS bearer:

[0635] 3> Release one or more RLC entities and the associated logical channel of the source SpCell as specified in Clause 5.1.3 of TS 38.322[4];

[0636] 3> Reconfigure the PDCP entity to release DAPS, as specified in TS 38.323[5];

[0637] 2> For each SRB:

[0638] 3> Release the PDCP entity of the source SpCell;

[0639] 3> Release the RLC entity and the associated logical channel of the source SpCell as specified in Clause 5.1.3 of TS 38.322[4];

[0640] 2> Release the physical channel configuration of the source SpCell;

[0641] 2> Discard the keys used in the source SpCell (KgNB key, KRRCenc key, KRRCint key, KUPint key, and KUPenc key), if any;

[0642] 1> Release sl-L2RelayUE-Config (if configured);

[0643] 1> Release sl-L2RemoteUE-Config (if configured);

[0644] 1> If an SRAP entity is configured, release the SRAP entity;

[0645] 1> If configured, release ncr-FwdConfig;

[0646] 1> If the UE is NCR-MT:

[0647] 2> Instruct NCR-Fwd to stop forwarding;

[0648] 1> If SL indirect path is configured:

[0649] 2> Release the cell identifier and relay UE ID configured in sl-IndirectPathAddChange;

[0650] 2> Instructs the upper layer to release the PC5 unicast link of the SL indirect path;

[0651] 1> If N3C indirect path is configured:

[0652] 2> Release n3c-IndirectPathAddChange;

[0653] 2> Consider not using non-3GPP connections;

[0654] 1> If the UE acts as an N3C relay UE, then:

[0655] 2> Release n3c-IndirectPathConfigRelay;

[0656] 2> Consider not using non-3GPP connections;

[0657] 1> If the UE acts as an L2 U2N remote UE and is not configured with an MP via an L2 U2N relay UE, then:

[0658] 2> If it is determined that the PC5-RRC connection with the U2N relay UE should be released:

[0659] 3> Instruct the upper layer to trigger the release of the PC5 unicast link;

[0660] 3> Perform cell selection according to the cell selection procedure specified in TS 38.304

[20] , or perform cell selection according to the relay selection specified in Clause 5.8.15.3, or both;

[0661] 2> Otherwise (i.e., maintain the PC5 RRC connection):

[0662] 3> Treat the connected L2 U2N relay UE as appropriate and perform the actions specified in Clause 5.3.7.3a;

[0663] Note 1: Whether to release or maintain the current PC5 unicast link depends on the remote UE implementation.

[0664] 1> Otherwise:

[0665] 2> If the UE is capable of L2 U2N remote UE:

[0666] 3> Perform cell selection as specified in TS 38.304

[20] , or relay selection as specified in Clause 5.8.15.3, or both;

[0667] 2> Otherwise:

[0668] 3> Perform cell selection according to the cell selection procedure specified in TS 38.304

[20] .

[0669] Note 2: For L2 U2N remote UEs, if both a suitable cell and a suitable relay are available, the UE can choose either one based on its implementation.

[0670] 5.3.7.3 Actions after cell selection during T311 runtime

[0671] When selecting a suitable NR cell, the UE should:

[0672] 1> Ensure that the basic system information as specified in Clause 5.2.2.2 is valid and up-to-date;

[0673] 1> Stop timer T311;

[0674] 1> If T390 is running:

[0675] 2> Stop timer T390 for all access categories;

[0676] 2> Perform the actions specified in 5.3.14.4;

[0677] 1> Stop the relay (re)selection process (if in progress);

[0678] 1> If cell selection is triggered by detecting a radio link failure of the MCG, a reconfiguration failure of the MCG with synchronization, or mobility failure from an NR failure, and

[0679] 1> If attemptCondReconfig is configured; and

[0680] 1> If the selected cell is not configured with CondEventT1, or if the selected cell is configured with CondEventT1 but the leave conditions have not yet been met; and

[0681] 1> If the selected cell is one of the candidate cells in the masterCellGroup included in MCGVarConditionalReconfig for its reconfigurationWithSync, and condExecutionCondPSCell is not configured for the corresponding condReconfigId in MCGVarConditionalReconfig, then:

[0682] 2> If the UE supports RLF reporting for conditional handover, set choCellId in VarRLF-Report to the global cell identifier (if available), otherwise set to the physical cell identifier and carrier frequency of the selected cell;

[0683] 2> Apply the stored condRRCReconfig associated with the selected cell and perform the actions specified in 5.3.5.3;

[0684] Note 1: In the event of a failed handover without key changes, how to avoid key stream reuse in the case of CHO-based recovery is left to the network implementation.

[0685] 1> If cell selection is triggered by detecting a radio link failure of the MCG or a synchronized reconfiguration failure of the MCG for an LTM cell handover procedure, the LTM cell handover procedure is triggered upon instruction from a lower layer as specified in Clause 5.3.5.18.6; and

[0686] 1> If attemptLTM-Switch is configured; and

[0687] 1> If the selected cell is one of the LTM candidate cells in the LTM-CandidateIE within the ltm-Config associated with the MCG, then:

[0688] 2> If the UE supports RLF reporting for LTM, set choCellId in VarRLF-Report to the global cell identifier (if available), otherwise set to the physical cell identifier and carrier frequency of the selected cell;

[0689] 2> Perform the LTM cell handover procedure for the selected LTM candidate cell according to the actions specified in 5.3.5.18.6;

[0690] Note 2: When both attemptCondReconfig and attemptLTM-Switch are configured, which process to execute depends on the UE implementation.

[0691] 1> If the UE has not yet applied the stored condRRCReconfig associated with the selected cell, and has not yet performed an LTM cell handover procedure for the selected LTM candidate cell, as described above:

[0692] 2> If the UE is configured with attemptCondReconfig; or

[0693] 2> If the UE is configured with attemptLTM-Switch:

[0694] 3> Reset MAC address;

[0695] 3> Release spCellConfig (if configured);

[0696] 3> Release the MCG SCell (if configured);

[0697] 3> Release delayBudgetReportingConfig (if configured) and stop timer T342 (if running);

[0698] 3> Release overheatingAssistanceConfig (if configured) and stop timer T345 (if running);

[0699] 3> If MR-DC is configured:

[0700] 4> Perform MR-DC release as specified in Clause 5.3.5.10;

[0701] 3> Release idc-AssistanceConfig (if configured);

[0702] 3> Release btNameList (if configured);

[0703] 3> Release wlanNameList (if configured);

[0704] 3> Release sensorNameList (if configured);

[0705] 3> Release drx-PreferenceConfig for MCG (if configured) and stop timer T346a associated with MCG (if running);

[0706] 3> Release the maxBW-PreferenceConfig of the MCG (if configured) and stop the timer T346b associated with the MCG (if running);

[0707] 3> Release MCG's maxCC-PreferenceConfig (if configured) and stop the timer T346c associated with MCG (if running);

[0708] 3> Release the maxMIMO-LayerPreferenceConfig of the MCG (if configured) and stop the timer T346d associated with the MCG (if running);

[0709] 3> Release the minSchedulingOffsetPreferenceConfig of the MCG (if configured) and stop the timer T346e associated with the MCG (if running);

[0710] 3> Release the rlm-RelaxationReportingConfig of the MCG (if configured) and stop the timer T346j associated with the MCG (if running);

[0711] 3> Release the bfd-RelaxationReportingConfig of the MCG (if configured) and stop the timer T346k associated with the MCG (if running);

[0712] 3> Release releasePreferenceConfig (if configured) and stop timer T346f (if running);

[0713] 3> Release onDemandSIB-Request (if configured) and stop timer T350 (if running);

[0714] 3> Release referenceTimePreferenceReporting (if configured);

[0715] 3> Release sl-AssistanceConfigNR (if configured);

[0716] 3> Release obtainCommonLocation (if configured);

[0717] 3> Release scg-DeactivationPreferenceConfig (if configured) and stop timer T346i (if running);

[0718] 3> Release musim-GapAssistanceConfig (if configured), and if it is running, stop timer T346h;

[0719] 3> Release musim-GapPriorityAssistanceConfig (if configured);

[0720] 3> Release musim-LeaveAssistanceConfig (if configured);

[0721] 3> Release musim-CapabilityRestrictionConfig (if configured) and stop timer T346n (if running);

[0722] 3> Release propDelayDiffReportConfig (if configured);

[0723] 3> Release ul-GapFR2-PreferenceConfig (if configured);

[0724] 3> Release rrm-MeasRelaxationReportingConfig (if configured);

[0725] 3> Release maxBW-PreferenceConfigFR2-2 (if configured);

[0726] 3> Release maxMIMO-LayerPreferenceConfigFR2-2 (if configured);

[0727] 3> Release minSchedulingOffsetPreferenceConfigExt (if configured);

[0728] 3> Release aerial-FlightPathAvailabilityConfig (if configured);

[0729] 3> Release ul-TrafficInfoReportingConfig (if configured) and stop all instances of timer T346l (if running);

[0730] 3> Suspend all RB and BH RLC channels used for IAB-MT, except for SRB0 and broadcast MRB;

[0731] 3> Release successPSCell-Config configured by PSCell (if configured);

[0732] 2> Remove all entries (if any) from MCG VarConditionalReconfig;

[0733] 2> Perform the LTM configuration release procedure for MCG and SCG as specified in Clause 5.3.5.18.7.

[0734] Figure 13 This is a flowchart S1300 depicting a method for processing RLF in a wireless communication network 100. (Example) Figure 13As shown, in step S1302, UE 1102 may determine whether at least one parameter related to at least one of the conditional reconfiguration and mobility handover attempts is configured when initiating the RRC reconstruction procedure. In step S1304, UE 1102: if it is determined that at least one parameter related to at least one of the conditional reconfiguration and mobility handover attempts is configured, retains the successPSCell configuration configured by the primary / secondary cell group (PSCell). In step S1306, UE 1102 may release the successPSCell configuration configured by the PSCell if it is determined that at least one parameter related to at least one of the conditional reconfiguration and mobility handover attempts is not configured.

[0735] Figure 14 This is a flowchart S1400 depicting a method for configuring at least one threshold parameter in a wireless communication network 100. For example... Figure 14 As shown, in step S1402, network entity 1202 may configure UE 1102 to report at least one of the following to the network using successPSCell-Config from the source primary and secondary cell (PSCell): successful PSCell change and addition information.

[0736] In step S1404, network entity 1202 may configure UE 1102 to perform PSCell change via signaling radio bearer 3 (SRB3) in the RRC reconfiguration message.

[0737] The various actions, behaviors, blocks, steps, etc. in the flowcharts / diagrams (200, 300, 400, 700, 800, 900, S1300-S1400) can be executed in the order they are presented, in different orders, or simultaneously. Furthermore, in some embodiments, without departing from the scope of the invention, some actions, behaviors, blocks, steps, etc., can be omitted, added, modified, skipped, etc.

[0738] The embodiments disclosed herein can be implemented by at least one software program that runs on at least one hardware device and performs network management functions to control network elements. Elements include blocks that may be at least one of a hardware device or a combination of a hardware device and a software module.

[0739] Therefore, it should be understood that the scope of protection extends to programs containing program code means for implementing one or more steps of the method, in addition to computer-readable means containing messages, when the program is run on a server or mobile device or any suitable programmable device. In at least one embodiment, the method is implemented by or with a software program written in another programming language, such as Very High Speed ​​Integrated Circuit Hardware Description Language (VHDL), or by one or more VHDL or several software modules executed on at least one hardware device. The hardware device can be any kind of portable device that can be programmed. The device may also include means that can be, for example, a hardware device (e.g., an ASIC) or a combination of hardware and software devices (e.g., ASIC and FPGA), or at least one microprocessor and at least one memory having software modules located therein. The method embodiments described herein can be implemented partly in hardware and partly in software. Alternatively, the invention can be implemented on different hardware devices, for example, using multiple CPUs.

[0740] The description of the specific embodiments above will fully reveal the general nature of the embodiments herein. Others can readily modify and / or adapt these specific embodiments for various applications by applying existing knowledge without departing from the general concepts. Therefore, such modifications and adaptations should and are intended to be understood as equivalents of the disclosed embodiments. It should be understood that the wording or terminology used herein is for descriptive purposes and not for limitation. Therefore, although embodiments herein have been described with reference to examples and examples, those skilled in the art will recognize that the embodiments and examples disclosed herein can be practiced with modifications within the scope of the embodiments described herein.

Claims

1. A method executed by a terminal in a wireless communication system, the method comprising: Receive messages from the base station; The identification message includes at least one of a first piece of information about conditional reconfiguration or a second piece of information about Layer 1 (L1) / Layer 2 (L2) triggered mobility (LTM); and If the message includes at least one of the first or second information, release a third information regarding the successful change or addition of a PSCell, in addition to a fourth information regarding the successful change or addition of a Primary / Secondary Cell Group (SCG) cell (PSCell). The third piece of information is configured by the main cell PCell, and The fourth piece of information is configured by PSCell.

2. The method according to claim 1, further comprising: If the message does not include at least one of the first or second information, release the third and fourth information.

3. The method according to claim 1, further comprising: If the selected cell is not one of the LTM candidate cells, release the third and fourth information. The identification includes, when initiating a Radio Resource Control (RRC) re-establishment process or during cell selection, the identification message including at least one of a first message or a second message.

4. The method according to claim 1, further comprising: Receive from the base station at least one of the following: fifth information regarding a threshold associated with timer T310 or sixth information regarding a threshold associated with timer T312. In this case, at least one of the fifth or sixth messages is not configured in a time manner that is changed via the PSCell of Signaling Radio Bearer 3 (SRB3).

5. A method performed by a base station in a wireless communication system, the method comprising: Generate a message that includes at least one of a first message about conditional reconfiguration or a second message about mobility (LTM) triggered by layer 1 (L1) / layer 2 (L2); as well as Send a message to the terminal. In cases where the message includes at least one of the first or second information, in addition to the fourth information regarding a successful Primary / Secondary Cell Group (SCG) cell (PSCell) change or addition, the third information regarding a successful PSCell change or addition is released by the terminal. The third piece of information is configured by the main cell PCell, and The fourth piece of information is configured by PSCell.

6. The method according to claim 5, in, If the message does not include at least one of the first or second information, the third and fourth information are released by the terminal. In cases where the selected cell is not one of the LTM candidate cells, the third and fourth information are released by the terminal, and In this process, at least one of the first or second information is configured when initiating a Radio Resource Control (RRC) re-establishment procedure or during cell selection.

7. The method according to claim 5, further comprising: Send to the terminal at least one of the following: fifth information regarding a threshold associated with timer T310 or sixth information regarding a threshold associated with timer T312. In this case, at least one of the fifth or sixth messages is not configured in a time manner that is changed via the PSCell of Signaling Radio Bearer 3 (SRB3).

8. A terminal in a wireless communication system, the terminal comprising: transceiver; as well as At least one processor, coupled to the transceiver, is configured to: Receive messages from the base station. The identification message includes at least one of a first piece of information about conditional reconfiguration or a second piece of information about mobility (LTM) triggered by Layer 1 (L1) / Layer 2 (L2), and If the message includes at least one of the first or second information, release a third information regarding the successful change or addition of a PSCell, in addition to a fourth information regarding the successful change or addition of a Primary / Secondary Cell Group (SCG) cell (PSCell). The third piece of information is configured by the main cell PCell, and The fourth piece of information is configured by PSCell.

9. The terminal according to claim 8, wherein, At least one processor is also configured to: If the message does not include at least one of the first or second information, release the third and fourth information.

10. The terminal according to claim 8, wherein, At least one processor is also configured to: If the selected cell is not one of the LTM candidate cells, release the third and fourth information. The identification includes, when initiating a Radio Resource Control (RRC) re-establishment process or during cell selection, the identification message including at least one of a first message or a second message.

11. The terminal according to claim 8, wherein, At least one processor is also configured to: Receive from the base station at least one of the following: fifth information regarding a threshold associated with timer T310 or sixth information regarding a threshold associated with timer T312. In this case, at least one of the fifth or sixth messages is not configured in a time manner that is changed via the PSCell of Signaling Radio Bearer 3 (SRB3).

12. A base station in a wireless communication system, the base station comprising: transceiver; as well as At least one processor, coupled to the transceiver, is configured to: Generate a message including at least one of a first message about conditional reconfiguration or a second message about mobility (LTM) triggered by Layer 1 (L1) / Layer 2 (L2), and Send a message to the terminal. In cases where the message includes at least one of the first or second information, in addition to the fourth information regarding a successful Primary / Secondary Cell Group (SCG) cell (PSCell) change or addition, the third information regarding a successful PSCell change or addition is released by the terminal. The third piece of information is configured by the main cell PCell, and The fourth piece of information is configured by PSCell.

13. The base station according to claim 12, in, If the message does not include at least one of the first or second information, the third and fourth information are released by the terminal.

14. The base station according to claim 12, in, If the selected cell is not one of the LTM candidate cells, the third and fourth information are released by the terminal, and In this process, at least one of the first or second information is configured when initiating a Radio Resource Control (RRC) re-establishment procedure or during cell selection.

15. The base station according to claim 12, wherein, At least one processor is also configured to: Send to the terminal at least one of the following: fifth information regarding a threshold associated with timer T310 or sixth information regarding a threshold associated with timer T312. In this case, at least one of the fifth or sixth messages is not configured in a time manner that is changed via the PSCell of Signaling Radio Bearer 3 (SRB3).