Apparatus and method for handling processing condition switch failure

CN122934400APending Publication Date: 2026-10-16GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611180171.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-11-17
Filing Date
2024-11-13
Publication Date
2026-10-16

AI Technical Summary

Technical Problem

然而,仍未定义LTM完成后触发释放或维持这些条件配置的过程

Benefits of technology

[0005] The purpose of this disclosure is to provide apparatus and methods for managing conditional reconfiguration that can solve the above-mentioned and other problems in the prior art, and/or perform appropriate actions for the removal or maintenance of conditional reconfiguration when mobility-related processes are completed.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122934400A_ABST
    Figure CN122934400A_ABST
Patent Text Reader

Abstract

A method of managing conditional reconfiguration performed by a user equipment (UE) includes performing, by a higher layer of the UE, removal or maintenance of a conditional reconfiguration upon completion of a mobility-related procedure. The completion of the mobility-related procedure can include one or more of: receiving, from a lower layer of the UE, an indication that execution of a lower triggered mobility (LTM) cell handover has successfully completed, successfully completing a RACH procedure toward a target cell during execution of the LTM cell handover, receiving, from the lower layer of the UE during execution of the LTM cell handover, an indication that the RACH procedure toward the target cell has successfully completed, executing an LTM procedure, executing a CPA, CPC, SCPAC, or CHO, or completing one or more of the CPA, CPC, LTM, SCPAC, or CHO procedures.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Case Analysis This application is a divisional application of Chinese patent application No. 202480065461.9, entitled "Apparatus and Method for Handling Failure of Condition Switching", which entered the Chinese national phase of PCT international patent application PCT / CN2024 / 131842 filed on November 13, 2024. Technical Field

[0002] This disclosure relates to the field of communication systems, and more specifically, to apparatus and methods for managing condition reconfiguration. Background Technology

[0003] In wireless communication systems, conditional configurations for cell additions and changes are traditionally released when user equipment (UE) completes the access process toward a target cell. Recent advances such as lower-layer triggered mobility (LTM) and subsequent conditional primary secondary cell addition or change (SCPAC) enable dynamic cell adjustments based on lower-layer measurements and allow conditional reconfiguration without complete reinitialization. However, the procedure for triggering the release or maintenance of these conditional configurations after LTM completion remains undefined.

[0004] Therefore, there is a need for devices and methods for managing condition reconfiguration. Summary of the Invention

[0005] The purpose of this disclosure is to provide apparatus and methods for managing conditional reconfiguration that can solve the above-mentioned and other problems in the prior art, and / or perform appropriate actions for the removal or maintenance of conditional reconfiguration when mobility-related processes are completed.

[0006] In a first aspect of this disclosure, a method for managing conditional reconfiguration performed by a user equipment (UE) includes removing or maintaining the conditional reconfiguration by a higher layer of the UE upon completion of a mobility-related process.

[0007] In a second aspect of this disclosure, the user equipment (UE) includes a higher layer configured to perform removal or maintenance of conditional reconfiguration upon completion of mobility-related procedures.

[0008] In a third aspect of this disclosure, a user equipment (UE) includes a memory, a transceiver, and a processor coupled to the memory and the transceiver. The UE is configured to perform the methods described above.

[0009] In a fourth aspect of this disclosure, a non-transitory machine-readable storage medium stores instructions that, when executed by a computer, cause the computer to perform the methods described above.

[0010] In a fifth aspect of this disclosure, a chip includes a processor for calling and running a computer program stored in a memory to cause a device on which the chip is mounted to perform the methods described above.

[0011] In a sixth aspect of this disclosure, a computer-readable storage medium is provided, wherein a computer program is stored that causes a computer to perform the above-described method.

[0012] In a seventh aspect of this disclosure, a computer program product includes a computer program that causes a computer to perform the methods described above.

[0013] In the eighth aspect of this disclosure, a computer program causes a computer to perform the above-described method. Attached Figure Description

[0014] To more clearly illustrate the embodiments or related technologies of this disclosure, the following drawings, which will be briefly described in the embodiments, will be briefly introduced. Obviously, the drawings are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without being limited thereto.

[0015] Figure 1 This is a block diagram of one or more user equipment (UE) and a communication base station in a communication network system according to embodiments of the present disclosure.

[0016] Figure 2 This is a schematic diagram illustrating the user plane protocol stack according to an embodiment of the present disclosure.

[0017] Figure 3 This is a schematic diagram illustrating a control plane protocol stack according to an embodiment of the present disclosure.

[0018] Figure 4 This is a block diagram of a UE according to an embodiment of the present disclosure.

[0019] Figure 5 This is a block diagram of a UE according to an embodiment of the present disclosure.

[0020] Figure 6 This is a flowchart illustrating a method for reconfiguring management conditions performed by a UE according to an embodiment of the present disclosure.

[0021] Figure 7 This is a block diagram of an example computing device according to embodiments of the present disclosure.

[0022] Figure 8 This is a block diagram of a communication system according to an embodiment of the present disclosure. Detailed Implementation

[0023] The technical features, structural characteristics, objectives, and effects of the embodiments of this disclosure are described in detail below with reference to the accompanying drawings. Specifically, the terminology used in the embodiments of this disclosure is only used to describe the purpose of a particular embodiment and is not intended to limit the disclosure.

[0024] The technical solutions of this disclosure can be applied to various communication systems, such as the Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), General Packet Radio Service (GPRS), Long Term Evolution (LTE), LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), Advanced Long Term Evolution (LTE-A), New Radio (NR), evolution systems of NR, LTE-based access to unlicensed spectrum (LTE-U), NR-based access to unlicensed spectrum (NR-U), Universal Mobile Telecommunications System (UMTS), and global interoperability for microwave access. Access (WiMAX) communication systems, wireless local area networks (WLAN), wireless fidelity (Wi-Fi), future fifth-generation (5G) systems (also known as new radio (NR) systems or other communication systems, etc.)

[0025] Optionally, the base station mentioned in this application embodiment can provide communication coverage for a specific geographical area and can communicate with user equipment (UE) located within that coverage area. Optionally, the base station can be a base transceiver unit (BTS) in a gNB, GSM, or CDMA system, or a NodeB (NB) in a WCDMA system, or an evolved NodeB (eNB or eNodeB) in an LTE system, or a radio controller in a cloud radio access network (CRAN).

[0026] User equipment (UE) can refer to an access terminal, subscriber unit, subscriber station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user equipment. An access terminal can be a cellular wireless phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication capabilities, computing device, other processing devices coupled to a wireless modem, in-vehicle equipment, wearable device, terminal equipment in future 5G networks, and terminal equipment in future evolved public land mobile networks (PLMNs), etc.

[0027] Optionally, the communication system in this application embodiment can be applied to unlicensed spectrum, wherein unlicensed spectrum can also be regarded as shared spectrum; or the communication system in this application embodiment can also be applied to licensed spectrum, wherein licensed spectrum can also be regarded as non-shared spectrum.

[0028] In traditional systems, when a User Equipment (UE) completes a random access procedure toward a target primary secondary cell (PCell) / PSCell, the conditional primary secondary cell (PSCell) addition (CPA) and conditional PSCell change (CPC) configurations are released. To further enhance mobility, Release 18 introduces lower-layer triggered mobility (LTM) (e.g., layer 1 / layer 2 (L1 / L2) triggered mobility) and subsequent conditional PSCell addition or change (SCPAC). LTM is a process in which a base station, such as a gNB, receives an L1 measurement report from the UE and, based on the L1 measurement report, changes the UE's serving cell (e.g., PCell or PSCell) by issuing a cell handover command signaled via a medium access control (MAC) control element (CE). SCPAC is designed to enable the execution of conditional PSCell addition or modification procedures after a PSCell has been changed, added, or released, without requiring network reconfiguration or reinitialization of CPA / CPC settings. Therefore, the UE can maintain its SCPAC configuration after PCell / PSCell adjustments.

[0029] In some embodiments of this disclosure, the handling of conditional configurations upon completion of LTM execution and the management of LTM configurations during CPA, CPC, or SCPAC execution are specified. This includes details of the UE's behavior at each protocol layer (e.g., the radio resource control (RRC) layer and the MAC layer) and the interactions between these layers.

[0030] In detail, in some embodiments, exemplary implementations describe how conditional configurations are handled upon completion of LTM execution, and the management of LTM configurations during the execution of Conditional PSCell Addition (CPA), Conditional PSCell Change (CPC), and subsequent Conditional PSCell Addition or Change (SCPAC). This example details the behavior of the User Equipment (UE) at various protocol layers such as the Radio Resource Control (RRC) layer and the Media Access Control (MAC) layer, and outlines the inter-layer interactions required to manage these configurations.

[0031] Specifically, upon receiving an indication that LTM execution is complete, the RRC layer performs actions to release or maintain conditional configurations stored in UE variables, such as CPA, CPC, and SCPAC. This may include removing or updating relevant information associated with these configurations (e.g., cell set ID, distributed cell (DU) ID, or timing advance (TA) ID). Similarly, during the execution of CPA, CPC, or SCPAC, the UE's MAC layer signals to the RRC layer to adjust the configuration based on the current mobility state, thereby ensuring that the UE maintains only the necessary configurations and cell set information.

[0032] Furthermore, inter-layer interactions are designed to ensure dynamic configuration adjustments based on conditional procedures and LTM state. For example, upon successful execution of CPA or SCPAC, the RRC layer can selectively release or retain specific configurations, such as conditional handover (CHO), depending on whether LTM is active in the primary or secondary cell group. This inter-layer management minimizes reconfiguration complexity, optimizes UE resource utilization, and ensures a smooth transition across network cells during mobility procedures.

[0033] This exemplary method demonstrates an efficient handling of conditional configurations during the completion of LTM, CPA, CPC, or SCPAC procedures, thereby providing enhanced mobility and network efficiency for UEs in wireless communication systems.

[0034] Figure 1 The illustration shows one or more user equipment (UE) 10 and base station (e.g., next-generation NodeB (gNB) or eNB) 20 communicating in a communication network system 30 (e.g., an NR system) according to embodiments of the present disclosure in some embodiments. The communication network system 30 includes one or more UEs 10 and base station 20. One or more UEs 10 may include a memory 12, a transceiver 13, and a processor 11 coupled to the memory 12 and the transceiver 13. The base station 20 may include a memory 22, a transceiver 23, and a processor 21 coupled to the memory 22 and the transceiver 23. The processor 11 or 21 may be configured to implement the functions, processes, and / or methods proposed herein. A layer of radio interface protocol may be implemented in the processor 11 or 21. The memory 12 or 22 is operatively coupled to the processor 11 or 21 and stores various information to operate the processor 11 or 21. Transceiver 13 or 23 is operably coupled to processor 11 or 21, and transceiver 13 or 23 transmits and / or receives radio signals.

[0035] Processor 11 or 21 may include application-specific integrated circuits (ASICs), other chipsets, logic circuits, and / or data processing devices. Memory 12 or 22 may include read-only memory (ROM), random access memory (RAM), flash memory, memory cards, storage media, and / or other storage devices. Transceiver 13 or 23 may include baseband circuitry for processing radio frequency signals. When embodiments are implemented in software, the techniques described herein can be implemented using modules (e.g., processes, functions, etc.) that perform the functions described herein. Modules may be stored in memory 12 or 22 and executed by processor 11 or 21. Memory 12 or 22 may be implemented within or outside of processor 11 or 21; in the case of external implementation, memory 12 or 22 may be communicatively coupled to processor 11 or 21 via various means known in the art.

[0036] In some embodiments, the processor 11 is configured to perform the removal or maintenance of conditional reconfiguration upon completion of a mobility-related process. This addresses the aforementioned and other issues in the prior art, and / or performs appropriate behavior for the removal or maintenance of conditional reconfiguration upon completion of a mobility-related process.

[0037] In some embodiments, processor 21 is configured to send a command to UE 10 to remove or maintain conditional reconfiguration upon completion of mobility-related procedures. In some embodiments, transceiver 23 is configured to send an instruction to UE 10 to adjust conditional reconfiguration based on completion of mobility-related procedures. This can resolve the above-mentioned and other problems in the prior art, and / or perform appropriate actions to remove or maintain conditional reconfiguration upon completion of mobility-related procedures.

[0038] Figure 2 An example user plane protocol stack according to an embodiment of this disclosure is shown. Figure 2In some embodiments, the Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), and Media Access Control (MAC) sublayers, as well as the Physical (PHY) layer (also referred to as Layer 1 or Layer 1 (L1)), can terminate in the user plane protocol stack within the UE 10 and at the network-side base station 40 (such as a gNB). In the example, the PHY layer provides transport services to higher layers (e.g., MAC, RRC, etc.). In the example, the services and functions of the MAC sublayer may include mapping between logical channels and transport channels, multiplexing MAC Service Data Units (SDUs) belonging to one or different logical channels to / from a Transport Block (TB) delivered to / from the PHY layer, demultiplexing the SDU from the TB, scheduling information reporting, error correction via Hybrid Automatic Repeat Request (HARQ) (e.g., one HARQ entity per carrier in the case of carrier aggregation (CA), priority processing among UEs by means of dynamic scheduling, priority processing among logical channels of a UE by means of logical channel priority ordering, and / or padding. A MAC entity can support one or more parameter sets and / or transmission timings. In the example, mapping constraints in logical channel prioritization control which parameter sets and / or transmission timings a logical channel can use. In the example, the RLC sublayer can support Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM) transmission modes. RLC configuration can be per logical channel, independent of parameter sets and / or Transmission Time Interval (TTI) durations. In the example, Automatic Repeat Request (ARQ) can operate on any of the parameter sets and / or TTI durations configured for a logical channel. In the example, services and functions of the PDCP layer for the user plane can include sequence numbering, header compression and decompression, delivery of user data, reordering and duplicate detection, PDCP PDU routing (e.g., in the case of split bearers), PDCP SDU retransmission, encryption, decryption and integrity protection, PDCP SDU dropping, PDCP reconstruction and data recovery for RLC AM, and / or PDCP PDU duplication. In the example, SDAP services and functions can include mapping between QoS flows and data radio bearers. In the example, SDAP services and functions may include mapping Quality of Service Indicators (QFIs) in downlink (DL) and uplink (UL) packets. In the example, SDAP protocol entities can be configured for a single PDU session.

[0039] Figure 3 An example control plane protocol stack according to an embodiment of this disclosure is shown. Figure 3In some embodiments, the PDCP, RLC, and MAC layers, as well as the PHY layer, can be terminated and perform the aforementioned services and functions in the control plane protocol stack, both by the UE 10 and the base station 40 (such as the gNB) on the network side. In the example, Radio Resource Control (RRC) is used to control radio resources between the UE and the base station (such as the gNB). In the example, RRC can be terminated in both the UE and the gNB on the network side. In the example, the services and functions of RRC may include broadcasting system information related to the Access Layer (AS) and Non-Access Layer (NAS), paging initiated by the 5G Core Network (5GC) or Radio Access Network (RAN), establishing, maintaining, and releasing RRC connections between the UE and the RAN, security functions including key management, establishing, configuring, maintaining, and releasing Signaling Radio Bearers (SRBs) and Data Radio Bearers (DRBs), mobility functions, QoS management functions, UE measurement reporting and control of reports, detection and recovery of radio link failures, and / or NAS message transmission from the Non-Access Layer (NAS) to the UE / from the UE to the NAS. In the example, the NAS control protocol can be terminated in the UE and the AMF on the network side, and can perform functions such as authentication, mobility management between the Access and Mobility Management Function (AMF) for 3GPP access and non-3GPP access and the UE, and session management between the SMF for 3GPP access and non-3GPP access and the UE.

[0040] When a specific application is executed in the UE and that application requires data communication services, the application layer responsible for executing that application provides application-related information, namely application group / category / priority information / ID, to the NAS layer. In this case, the application-related information can be pre-configured / defined in the UE. Alternatively, application-related information can be received from the network and provided to the application layer from the AS (RRC) layer, and when the application layer starts data communication services, it requests information from the AS (RRC) layer to receive that information.

[0041] In some embodiments, the higher layers of UE 10 are configured to remove or maintain conditional reconfigurations upon completion of mobility-related procedures. The higher layer may be the Radio Resource Control (RRC) layer. This addresses the aforementioned and other issues in the prior art, and / or ensures appropriate behavior is performed on the removal or maintenance of conditional reconfigurations upon completion of mobility-related procedures.

[0042] In some embodiments, base station 40 is configured to send a command to UE 10 to remove or maintain conditional reconfiguration upon completion of a mobility-related process. In some embodiments, base station 40 is configured to send an indication to UE to adjust conditional reconfiguration based on completion of the mobility-related process. This can resolve the above-mentioned and other problems in the prior art, and / or perform appropriate actions for the removal or maintenance of conditional reconfiguration upon completion of the mobility-related process.

[0043] Figure 4 An example of a UE 200 according to an embodiment of this application is shown. The UE 200 is configured to implement some embodiments of this disclosure. Some embodiments of this disclosure can be implemented in the UE 200 using any appropriately configured hardware and / or software. The UE 200 includes a higher layer 201 configured to perform the removal or maintenance of conditional reconfiguration upon completion of mobility-related processes. This can resolve the above-mentioned and other problems in the prior art, and / or perform appropriate behavior for the removal or maintenance of conditional reconfiguration upon completion of mobility-related processes.

[0044] Figure 5 An example of a UE 300 according to an embodiment of the present disclosure is shown. The UE 300 is configured to implement some embodiments of the present disclosure. Some embodiments of the present disclosure can be implemented in the UE 300 using any suitably configured hardware and / or software. The UE 300 may include a memory 301, a transceiver 302, and a processor 303 coupled to the memory 301 and the transceiver 302. The processor 303 may be configured to implement the functions, processes, and / or methods described herein. A layer of a radio interface protocol may be implemented in the processor 303. The memory 301 is operatively coupled to the processor 303 and stores various information to operate the processor 303. The transceiver 302 is operatively coupled to the processor 303 and transmits and / or receives radio signals. The processor 303 may include an application-specific integrated circuit (ASIC), other chipsets, logic circuits, and / or data processing devices. The memory 301 may include read-only memory (ROM), random access memory (RAM), flash memory, memory cards, storage media, and / or other storage devices. Transceiver 302 may include baseband circuitry for processing radio frequency signals. When embodiments are implemented in software, the techniques described herein can be implemented using modules (e.g., processes, functions, etc.) that perform the functions described herein. Modules may be stored in memory 301 and executed by processor 303. Memory 301 may be implemented within or outside of processor 303; in the case of external implementation, memory 301 may be communicatively coupled to processor 303 via various means known in the art.

[0045] In some embodiments, the higher layers of the UE are configured to remove or maintain conditional reconfigurations upon completion of mobility-related processes. This addresses the aforementioned and other issues in the prior art, and / or ensures appropriate behavior is performed on the removal or maintenance of conditional reconfigurations upon completion of mobility-related processes.

[0046] In some embodiments, completing a mobility-related process includes one or more of the following: receiving from the UE's lower layer an indication that the execution of a lower-layer triggered mobility (LTM) cell handover has been successfully completed; successfully completing a random access channel (RACH) procedure toward a target cell during the execution of an LTM cell handover; receiving from the UE's lower layer an indication that the RACH procedure toward a target cell has been successfully completed during the execution of an LTM cell handover; executing an LTM procedure; executing a conditional primary / secondary cell (PSCell) addition or modification (CPA / CPC), a subsequent conditional PSCell addition or modification (SCPAC), or a conditional handover (CHO); or completing one or more of the CPA, CPC, LTM, SCPAC, or CHO procedures.

[0047] In some embodiments, the removal or maintenance operation of conditional reconfiguration performed by the Radio Resource Control (RRC) layer of the User Equipment (UE) includes one or more of the following: removing the CPA / CPC configuration from the UE variable if a CPA / CPC configuration exists in the UE variable; removing the SCPAC configuration from the UE variable if an SCPAC configuration exists in the UE variable; removing the LTM configuration from the UE variable if an LTM configuration exists in the UE variable; maintaining the SCPAC configuration in the UE variable if an SCPAC configuration exists in the UE variable; maintaining the LTM configuration in the UE variable if an LTM configuration exists in the UE variable; removing the SCPAC-related cell set information from the UE variable if an SCPAC-related cell set information exists in the UE variable; removing the LTM-related cell set information from the UE variable if an LTM-related cell set information exists in the UE variable; maintaining the SCPAC-related cell set information in the UE variable if an SCPAC-related cell set information exists in the UE variable; maintaining the LTM-related cell set information in the UE variable if an LTM-related cell set information exists in the UE variable; or maintaining or releasing the CHO configuration in the UE variable if a CHO configuration exists in the UE variable.

[0048] In some embodiments, SCPAC-related cell set information includes a Secure Cell Set Identifier (ID). In some embodiments, LTM-related cell set information includes a Distributed Unit (DU) information ID for resetting the Layer 2 (L2) protocol stack and a UE-based TA information ID for determining whether to perform UE-based Timing Advance (TA). In some embodiments, the UE is configured to trigger an LTM cell handover on a Primary Cell Group (MCG) or Secondary Cell Group (SCG). In some embodiments, the lower layer of the UE is configured to determine that the execution of the LTM cell handover will be successfully completed under one or more of the following conditions, and send an indication to the higher layer of the UE that the execution of the LTM cell handover has been successfully completed: receiving uplink (UL) permission for the new transmission in the same Hybrid Automatic Repeat Request (HARQ) procedure for the initial UL transmission to the target cell, receiving downlink (DL) allocation after the initial UL transmission to the target cell, or successfully completing the RACH procedure toward the target cell.

[0049] In some embodiments, the lower layer of the UE is configured to indicate to the higher layer of the UE that the LTM cell handover has been successfully completed or that the RACH procedure toward the target cell has been successfully completed during the LTM cell handover. In some embodiments, conditional reconfiguration includes one or more of the following: CPA, CPC, SCPAC, or CHO, with CHO configuration for a secondary cell group (SCG) or candidate SCG.

[0050] Figure 6 This is an example of a method 400 for managing conditional reconfiguration performed by a UE according to embodiments of the present disclosure. The method 400 for managing conditional reconfiguration performed by a UE is configured to implement some embodiments of the present disclosure. Some embodiments of the present disclosure can be implemented in the method 400 for managing conditional reconfiguration performed by a UE using any appropriately configured hardware and / or software. In some embodiments, the method 400 for managing conditional reconfiguration performed by a UE includes: operation 402, whereby a higher layer of the UE performs the removal or maintenance of the conditional reconfiguration upon completion of a mobility-related process. This can address the above-mentioned and other problems in the prior art, and / or perform appropriate actions for the removal or maintenance of the conditional reconfiguration upon completion of a mobility-related process.

[0051] In some embodiments, completing a mobility-related process includes one or more of the following: receiving from the UE's lower layer an indication that the execution of a lower layer triggered mobility (LTM) cell handover has been successfully completed; successfully completing a random access channel (RACH) procedure toward a target cell during the execution of an LTM cell handover; receiving from the UE's lower layer an indication that the RACH procedure toward a target cell has been successfully completed during the execution of an LTM cell handover; executing an LTM procedure; executing a conditional primary / secondary cell (PSCell) addition or modification (CPA / CPC), a subsequent conditional PSCell addition or modification (SCPAC), or a conditional handover (CHO); or completing one or more of the CPA, CPC, LTM, SCPAC, or CHO procedures.

[0052] In some embodiments, the removal or maintenance operation of conditional reconfiguration performed by the RRC layer of the UE includes one or more of the following: removing the CPA / CPC configuration from the UE variable if a CPA / CPC configuration exists in the UE variable; removing the SCPAC configuration from the UE variable if an SCPAC configuration exists in the UE variable; removing the LTM configuration from the UE variable if an LTM configuration exists in the UE variable; maintaining the SCPAC configuration in the UE variable if an SCPAC configuration exists in the UE variable; maintaining the LTM configuration in the UE variable if an LTM configuration exists in the UE variable; removing the SCPAC-related cell set information from the UE variable if an SCPAC-related cell set information exists in the UE variable; removing the LTM-related cell set information from the UE variable if an LTM-related cell set information exists in the UE variable; maintaining the SCPAC-related cell set information in the UE variable if an SCPAC-related cell set information exists in the UE variable; maintaining the LTM-related cell set information in the UE variable if an LTM-related cell set information exists in the UE variable; or maintaining or releasing the CHO configuration in the UE variable if a CHO configuration exists in the UE variable.

[0053] In some embodiments, SCPAC-related cell set information includes a secure cell set identifier (ID). In some embodiments, LTM-related cell set information includes a distributed unit (DU) information ID for resetting the Layer 2 (L2) protocol stack and a UE-based TA information ID for determining whether to perform UE-based timing advance (TA). In some embodiments, the method further includes the UE triggering an LTM cell handover on a primary cell group (MCG) or secondary cell group (SCG). In some embodiments, the method further includes the lower layer of the UE determining that the execution of the LTM cell handover will be successfully completed and sending an indication to the higher layer of the UE that the execution of the LTM cell handover has been successfully completed under one or more of the following conditions: receiving uplink (UL) permission for the new transmission in the same Hybrid Automatic Repeat Request (HARQ) procedure for the initial UL transmission to the target cell, receiving downlink (DL) allocation after the initial UL transmission to the target cell, or successfully completing a RACH procedure toward the target cell.

[0054] In some embodiments, the method further includes: instructing a lower layer of the user equipment to its higher layer that the execution of an LTM cell handover has been successfully completed or that a RACH procedure toward the target cell has been successfully completed during the execution of the LTM cell handover. In some embodiments, conditional reconfiguration includes one or more of the following: CPA, CPC, SCPAC, or CHO, with a CHO configuration for a secondary cell group (SCG) or candidate SCG.

[0055] Example technical solution: The Radio Resource Control (RRC) layer of the user equipment receives, 1) an indication from the UE's lower layer (e.g., Media Access Control (MAC)) that the LTM cell handover execution has been successfully completed; or 2) a Random Access Channel (RACH) procedure toward the target channel has been successfully completed during the LTM cell handover execution; or 3) an indication from the lower layer (e.g., the MAC layer) that a RACH procedure toward the target cell has been successfully completed for the LTM cell handover execution; or 4) the execution of LTM; or 5) the execution of CPA, CPC, or SCPAC; or 6) the completion of CPA, CPC, LTM, SCPAC, or CHO, and performs the following operations: a) removing the CPA / CPC configuration from the UE variable if it exists in the UE variable; b) removing the SCPAC configuration from the UE variable if it exists in the UE variable; c) removing the LTM configuration from the UE variable if it exists in the UE variable; d) maintaining the SCPAC configuration in the UE variable if it exists in the UE variable; e) f) If LTM configuration exists in the UE variable, maintain the LTM configuration in the UE variable; f) If SCPAC-related cell set information (e.g., secure cell set ID) exists in the UE variable, remove the SCPAC-related cell set information from the UE variable; g) If LTM-related cell set information (e.g., distributed unit (DU) information ID used to reset the L2 protocol stack, UE-based TA information ID used to determine whether UE-based timing advance (TA) can be executed) exists in the UE variable, remove the LTM-related cell set information from the UE variable; h) If SCPAC-related cell set information (e.g., secure cell set ID) exists in the UE variable, maintain the SCPAC-related cell set information in the UE variable; i) If LTM-related cell set information (e.g., DU information ID used to reset the L2 protocol stack, UE-based TA information ID used to determine whether UE-based TA can be executed) exists in the UE variable, maintain the LTM-related cell set information in the UE variable; j) If CHO configuration exists in the UE variable, maintain or release the CHO configuration in the UE variable.

[0056] For example, if CPA / CPC or SCPAC is configured, the CHO configuration is released after the SCG LTM is completed. Similarly, the CHO configuration is released after the Primary Cell Group (MCG) LTM is completed.

[0057] LTM cell handover can be triggered on the primary cell group (MCG) or the secondary cell group (SCG).

[0058] The MAC layer considers the LTM cell handover process to be successfully completed and indicates this to higher layers (e.g., RRC) under the following conditions: a) receiving uplink (UL) permission for the new transmission on the same Hybrid Automatic Repeat Request (HARQ) procedure used for the initial UL transmission to the target cell; b) receiving downlink (DL) allocation after the initial UL transmission to the target cell; c) successfully completing the RACH procedure toward the target cell.

[0059] The MAC layer indicates to higher layers that the LTM cell handover execution has been successfully completed or that the RACH process toward the target cell has been successfully completed for the LTM cell handover execution.

[0060] The Radio Resource Control (RRC) layer manages the removal or maintenance of conditional reconfigurations in response to specific indicators from lower layers. This includes signaling that an LTM cell handover or a RACH procedure to a target cell has been successfully completed during LTM execution. The covered conditional reconfigurations include Conditional PSCell Addition (CPA), Conditional PSCell Change (CPC), Subsequent Conditional PSCell Addition or Change (SCPAC), and Conditional Handover (CHO), as well as CHO configurations with a Secondary Cell Group (SCG) or Candidate SCG.

[0061] The Radio Resource Control (RRC) layer in the User Equipment (UE) manages conditional configurations during mobility-related processes, including lower-layer triggered LTM cell handovers, Random Access Channel (RACH) procedures, and conditional handovers. This management involves selectively removing or maintaining configurations and associated cell information, such as CPA / CPC, SCPAC, and LTM data. The Media Access Control (MAC) layer supports these processes by indicating successful LTM or RACH completion to higher layers under specific conditions, including uplink and downlink reception or successful RACH procedure. These interactions ensure efficient handling of mobility events and dynamically adjust UE configurations for performance optimization across cell groups.

[0062] In some embodiments of the proposed solution, a method is implemented in the User Equipment (UE) to effectively manage conditional configurations upon completion of LTM execution. When the LTM process is complete, the RRC layer within the UE evaluates existing conditional configurations, such as Conditional PSCell Addition (CPA), Conditional PSCell Change (CPC), and subsequent Conditional PSCell Addition or Change (SCPAC). The RRC layer then determines, based on predefined conditions and the current network environment, whether each configuration can be removed or maintained.

[0063] For example, upon receiving an indication from the Media Access Control (MAC) layer that a handover of an LTM cell has been successfully completed via signaling, the RRC layer can remove outdated CPA / CPC configurations while retaining the SCPAC configuration associated with the currently serving cell. This process also involves managing relevant cell information, such as the Security Cell Set ID and Distributed Unit (DU) information identifiers used to reset the Layer 2 protocol stack.

[0064] In scenarios involving Conditional Handover (CHO), this solution enables the UE to release or maintain its CHO configuration based on the LTM completion status in the Primary Cell Group (MCG) or Secondary Cell Group (SCG). This selective removal or maintenance of the configuration minimizes reconfiguration overhead, optimizes resource utilization, and ensures the UE is ready for seamless mobility in subsequent network scenarios. This example demonstrates how the proposed solution enables the UE to effectively adapt its conditional configuration, thereby providing improved performance and network efficiency.

[0065] Some implementations offer the following commercial benefits: 1. Solving the above and other problems in the prior art. 2. Performing appropriate actions for the removal or maintenance of condition reconfiguration during mobility-related processes. 3. Maintaining service continuity. 4. Providing good communication performance. 5. Providing high reliability. Some embodiments of this disclosure can be used in many applications. Some embodiments of this disclosure are provided by chipset suppliers, video system development suppliers, automobile manufacturers including cars, trains, trucks, buses, bicycles, motorcycles, helmets, etc., drone (unmanned aerial vehicle) manufacturers, smartphone manufacturers, communication equipment for public safety purposes, such as gaming, conference / seminar, and AR / VR / MR device manufacturers for educational purposes. Some embodiments of this disclosure are combinations of "technologies / processes" that can be adopted in video standards to create the final product. Some embodiments of this disclosure propose technical mechanisms. At least one proposed solution, method, system, and apparatus of some embodiments of this disclosure can be used with current and / or new / future standards regarding communication systems (such as UEs, base stations, and / or communication systems). Compatible products follow at least one proposed solution, method, system, and apparatus of some embodiments of this disclosure. The proposed solutions, methods, systems, and apparatuses are widely used in UEs, base stations, and / or communication systems. Implementations of at least one of the proposed solutions, methods, systems, and apparatuses using some embodiments of this disclosure are considered to allow for at least one modification of wireless communication methods and apparatuses for standardization.

[0066] Figure 7 This is an example of a computing device 1100 according to embodiments of the present disclosure. Any suitable computing device can be used to perform the operations described herein. For example, Figure 7 It demonstrates that this can be achieved using any suitably configured hardware and / or software. Figures 1 to 6 Examples of computing devices 1100 in some embodiments are provided. In some embodiments, computing device 1100 may include processor 1112 communicatively coupled to memory 1114 and executing computer-executable program code and / or accessing information stored in memory 1114. Processor 1112 may include a microprocessor, application-specific integrated circuit (“ASIC”), state machine, or other processing device. Processor 1112 may include any one of a plurality of processing devices, including one. Such a processor may include or be able to communicate with a computer-readable medium storing instructions that, when executed by processor 1112, cause the processor to perform the operations described herein.

[0067] Memory 1114 may include any suitable non-transitory computer-readable medium. Computer-readable media may include any electronic, optical, magnetic, or other storage device capable of providing computer-readable instructions or other program code to a processor. Non-limiting examples of computer-readable media include disks, memory chips, read-only memory (ROM), random access memory (RAM), application-specific integrated circuits (ASICs), configured processors, optical storage devices, magnetic tape or other magnetic storage devices, or any other medium from which instructions can be read by a computer processor. Instructions may include processor-specific instructions generated by a compiler and / or interpreter from code written in any suitable computer programming language, including, for example, C, C++, C#, Visual Basic, Java, Python, Perl, JavaScript, and ActionScript.

[0068] The computing device 1100 may also include a bus 1116. The bus 1116 may communicatively couple one or more components of the computing device 1100. The computing device 1100 may also include multiple external or internal devices, such as input or output devices. For example, the computing device 1100 is shown having an input / output (“I / O”) interface 1118 that can receive input from one or more input devices 1120 or provide output to one or more output devices 1122. One or more input devices 1120 and one or more output devices 1122 may be communicatively coupled to the I / O interface 1118. The communicative coupling may be implemented via any suitable means (e.g., via a connection to a printed circuit board, via a cable, via wireless communication, etc.). Non-limiting examples of the input device 1120 include a touchscreen (e.g., one or more cameras for imaging a touch area or a pressure sensor for detecting pressure changes caused by a touch), a mouse, a keyboard, or any other device that can be used to generate input events in response to physical actions of a user of the computing device. Non-limiting examples of output device 1122 include liquid crystal display (LCD) screens, external monitors, speakers, or any other device that can be used to display or otherwise present output generated by a computing device.

[0069] Computing device 1100 can configure processor 1112 to perform the above-mentioned... Figures 1 to 6 The program code describes one or more operations in some embodiments. The program code may reside in memory 1114 or any suitable computer-readable medium and may be executed by processor 1112 or any other suitable processor.

[0070] The computing device 1100 may also include at least one network interface device 1124. The network interface device 1124 may include any device or group of devices adapted to establish wired or wireless data connections to one or more data networks 1128. Non-limiting examples of the network interface device 1124 include Ethernet network adapters, modems, etc. The computing device 1100 may transmit messages as electronic or optical signals via the network interface device 1124.

[0071] Figure 8 This is a block diagram of an example communication system 1200 according to embodiments of the present disclosure. The embodiments described herein can be implemented in the communication system 1200 using any appropriately configured hardware and / or software. Figure 8 A communication system 1200 is shown, which includes at least radio frequency (RF) circuitry 1210, baseband circuitry 1220, application circuitry 1230, memory / storage device 1240, display 1250, camera 1260, sensor 1270, and input / output (I / O) interface 1280, all of which are coupled to each other as shown.

[0072] Application circuitry 1230 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor may include any combination of general-purpose processors and special-purpose processors (such as graphics processors, application processors). The processor may be coupled to a memory / storage device and configured to execute instructions stored in the memory / storage device to enable various applications and / or operating systems running on the system. Communication system 1200 may configure application circuitry 1230 to perform the above-described... Figures 1 to 6 The program code describes one or more operations in some embodiments of the operation. The program code may reside in application circuit 1230 or any suitable computer-readable medium and may be executed by application circuit 1230 or any other suitable processor.

[0073] The baseband circuit 1220 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor may include a baseband processor. The baseband circuitry can handle various radio control functions that enable communication with one or more radio networks via RF circuitry. Radio control functions may include, but are not limited to, signal modulation, encoding, decoding, and radio frequency shifting. In some embodiments, the baseband circuitry can provide communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry may support communication with the Evolved Universal Terrestrial Radio Access Network (EUTRAN) and / or other Wireless Metropolitan Area Networks (WMAN), Wireless Local Area Networks (WLAN), and Wireless Personal Area Networks (WPAN). Embodiments of the baseband circuitry configured to support radio communication with more than one radio protocol may be referred to as a multi-mode baseband circuitry.

[0074] In various embodiments, baseband circuit 1220 may include circuitry for operating with signals not strictly considered to be at baseband frequencies. For example, in some embodiments, the baseband circuitry may include circuitry for operating with signals having an intermediate frequency (IF), which is between the baseband frequency and the radio frequency (RF). RF circuit 1210 may use modulated electromagnetic radiation through a non-solid-state medium to achieve communication with a wireless network. In various embodiments, RF circuitry may include switches, filters, amplifiers, etc., to facilitate communication with a wireless network. In various embodiments, RF circuitry 1210 may include circuitry for operating with signals not strictly considered to be at the radio frequency (RF). For example, in some embodiments, RF circuitry may include circuitry for operating with signals having an intermediate frequency (IF), which is between the baseband frequency and the RF frequency.

[0075] In various embodiments, the above regarding Figures 1 to 6The transmitter circuitry, control circuitry, or receiver circuitry discussed in some embodiments may be wholly or partially embodied in one or more of the RF circuitry, baseband circuitry, and / or application circuitry. As used herein, “circuit” can refer to, or is part of, an application-specific integrated circuit (ASIC), electronic circuitry, a processor (shared, dedicated, or grouped) and / or memory (shared, dedicated, or grouped), combinational logic circuitry, and / or other suitable hardware components that provide the described functionality. In some embodiments, electronic device circuitry may be implemented in one or more software or firmware modules, or the functionality associated with the circuitry may be implemented by one or more software or firmware modules. In some embodiments, some or all of the components of the baseband circuitry, application circuitry, and / or memory / storage device may be implemented together on a system-on-a-chip (SOC). Memory / storage device 1240 may be used to load and store, for example, data and / or instructions for the system. Memory / storage device for one embodiment may include any combination of suitable volatile memory (such as dynamic random access memory (DRAM)) and / or non-volatile memory (such as flash memory).

[0076] In various embodiments, I / O interface 1280 may include one or more user interfaces designed to enable a user to interact with the system and / or peripheral component interfaces designed to enable peripheral components to interact with the system. User interfaces may include, but are not limited to, a physical keyboard or keypad, touchpad, speaker, microphone, etc. Peripheral component interfaces may include, but are not limited to, non-volatile memory ports, universal serial bus (USB) ports, audio jacks, and power interfaces. In various embodiments, sensor 1270 may include one or more sensing devices to determine environmental conditions and / or location information related to the system. In some embodiments, sensors may include, but are not limited to, gyroscope sensors, accelerometers, proximity sensors, ambient light sensors, and positioning units. Positioning units may also be part of or interact with baseband and / or RF circuitry to communicate with components of a positioning network (e.g., Global Positioning System (GPS) satellites).

[0077] In various embodiments, display 1250 may include a display, such as a liquid crystal display (LCD) and a touchscreen display. In various embodiments, communication system 1200 may be a mobile computing device, such as, but not limited to, a laptop, tablet, netbook, ultrabook, smartphone, AR / VR glasses, etc. In various embodiments, the system may have more or fewer components and / or different architectures. Where appropriate, the methods described herein may be implemented as a computer program. The computer program may be stored on a storage medium (e.g., a non-transitory storage medium).

[0078] Those skilled in the art will understand that each unit, algorithm, and operation described and disclosed in the embodiments of this disclosure is implemented using electronic hardware or a combination of computer software and electronic hardware. Whether a function operates in hardware or software depends on the application conditions and the design requirements of the technical solution. Those skilled in the art can implement the function for each specific application in different ways, and such implementation should not exceed the scope of this disclosure. Those skilled in the art will understand that since the working processes of the above-described systems, devices, and units are substantially the same, they can refer to the working processes of the systems, devices, and units in the above embodiments. For ease of description and simplification, these working processes will not be described in detail again.

[0079] It should be understood that the systems, apparatuses, and methods disclosed in the embodiments of this disclosure can be implemented in other ways. The above embodiments are merely exemplary. The division of units is based solely on logical function, while other divisions exist in the implementation. Multiple units or components can be combined or integrated into another system. It is also possible to omit or skip some features. On the other hand, the mutual coupling, direct coupling, or communication coupling shown or discussed operates indirectly or communicatively through some ports, devices, or units in an electrical, mechanical, or other type of manner.

[0080] The units used for illustration may or may not be physically separate. The units used for display may or may not be physical units, i.e., located in one location or distributed across multiple network units. Some or all of the units may be used depending on the purpose of the embodiment. Furthermore, each functional unit in each embodiment may be integrated into a processing unit, or physically independent, or integrated into a processing unit having two or more units.

[0081] If a software functional unit is implemented and used and sold as a product, it can be stored in a readable storage medium in a computer. Based on this understanding, the technical solutions proposed in this disclosure can be implemented substantially or partially in the form of a software product. Alternatively, a portion of the technical solution that is beneficial to conventional technology can be implemented in the form of a software product. The software product in the computer is stored in a storage medium and includes multiple commands for a computing device (such as a personal computer, server, or network device) to perform all or part of the operations disclosed in the embodiments of this disclosure. The storage medium includes a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a floppy disk, or other types of media capable of storing program code.

[0082] While this disclosure has been described in conjunction with what are considered to be the most practical and preferred embodiments, it should be understood that this disclosure is not limited to the disclosed embodiments, but is intended to cover various arrangements made without departing from the broadest interpretation of the appended claims.

Claims

1. A method for managing conditional reconfiguration performed by a user equipment (UE), comprising: The removal or maintenance of conditional reconfiguration is performed by the higher layers of the UE when completing mobility-related procedures.

2. The method according to claim 1, wherein, The mobility-related process includes one or more of the following: The UE receives an indication from its lower layer that the lower-layer triggered LTM cell handover has been successfully completed. The Random Access Channel (RACH) procedure toward the target cell was successfully completed during the LTM cell handover. During the execution of the LTM cell handover, the UE receives an indication from its lower layer that the RACH process toward the target cell has been successfully completed; Execute the LTM process; Execution conditions: adding or changing CPA / CPC in the primary / secondary cell PSCell; subsequent conditions: adding or changing SCPAC in the PSCell; or conditional switchover CHO; or Complete one or more of the following processes: CPA, CPC, LTM, SCPAC, or CHO.

3. The method according to claim 1 or 2, wherein, The removal or maintenance of the conditional reconfiguration performed by the RRC layer of the UE includes one or more of the following: If the CPA / CPC configuration is conditionally added to or changed in the primary and secondary cell PSCells within the UE variables, the CPA / CPC configuration is removed from the UE variables. If there are subsequent conditions in the UE variable that add or change the SCPAC configuration, the SCPAC configuration will be removed from the UE variable. If there is a lower-layer triggered mobility LTM configuration in the UE variable, remove the LTM configuration from the UE variable; If the SCPAC configuration exists within the UE variable, maintain the SCPAC configuration within the UE variable; If the LTM configuration exists in the UE variable, maintain the LTM configuration in the UE variable; If the SCPAC-related cell set information is present in the UE variable, remove the SCPAC-related cell set information from the UE variable. If the LTM-related cell set information exists in the UE variable, remove the LTM-related cell set information from the UE variable. If the SCPAC-related cell set information is present in the UE variable, the SCPAC-related cell set information in the UE variable shall be maintained. If the LTM-related cell set information is present in the UE variable, the LTM-related cell set information in the UE variable shall be maintained. or If a conditional switch of the CHO configuration occurs within the UE variable, the CHO configuration within the UE variable may be maintained or released.

4. The method according to claim 3, wherein, The SCPAC-related cell set information includes the Secure Cell Set Identifier (SCI).

5. The method according to claim 3, wherein, The LTM-related cell set information includes a Distributed Unit (DU) information ID used to reset the Layer 2 (L2) protocol stack and a UE-based TA information ID used to determine whether to execute the UE-based timed advance TA.

6. The method according to claim 2, further comprising: The lower layer of the UE determines that the LTM cell handover will be successfully completed under one or more of the following conditions, and sends an indication to the higher layer of the UE that the LTM cell handover has been successfully completed: An uplink UL permission for the new transmission is received during the same Hybrid Automatic Repeat Request (HARQ) procedure used for the initial UL transmission to the target cell. A downlink DL allocation is received after the initial UL transmission to the target cell; or The RACH process toward the target cell was successfully completed.

7. The method according to claim 2, further comprising: The lower layer of the UE indicates to the higher layer of the UE that the LTM cell handover has been successfully completed or that the RACH procedure toward the target cell has been successfully completed during the LTM cell handover.

8. The method according to claim 1, wherein, The conditional reconfiguration includes one or more of the following: adding CPA to the primary and secondary cell PSCell, changing CPC in the conditional PSCell, adding or changing SCPAC or conditional handover CHO in the subsequent conditional PSCell, and configuring CHO with secondary cell group SCG or candidate SCG.

9. A user equipment (UE), comprising: Memory, which stores instructions; transceiver; and A processor, which is coupled to the memory and the transceiver; The processor is configured to execute the instructions to cause the UE to perform the method according to any one of claims 1 to 8.

10. A chip, comprising: The processor is configured to invoke and run a computer program stored in memory to cause a device on which the chip is mounted to perform the method according to any one of claims 1 to 8.