Managing near failure events during dual connectivity in a wireless communication system

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. The disclosure relates to a method performed by a User Equipment (UE). The method includes receiving a radio resource control (RRC) reconfiguration message including reconfiguration with sync information for a secondary cell group (SCG), wherein the RRC reconfiguration message does not include secondary node (SN)-initiated primary SCG cell (PScell) change information, initiating execution of a reconfiguration with sync procedure for the SCG, identifying whether a timer T312, associated with a measurement identity of a target PSCell and included in measurement configuration information associated with the SCG, is running at the time of initiating the execution, determining, if the timer T312 is running at the time of initiating the execution, whether a ratio between a value of elapsed time of the timer T312 and a configured value of the timer T312 is greater than a threshold value, and storing successful PSCell change information in a successful PSCell change report based on determining that the ratio is greater than the threshold value.

Description

MANAGING NEAR FAILURE EVENTS DURING DUAL CONNECTIVITY IN A WIRELESS COMMUNICATION SYSTEMThis application is based on and derives the benefit of Indian Provisional Applications 202541002081 filed on 9thJanuary 2025, and 202541005457 filed on 23rdJanuary 2025 the contents of which are incorporated herein by reference. The present disclosure relates generally to the field of wireless communication. More specifically, the present disclosure pertains to systems and methods for managing near-failure events during dual connectivity within a wireless communication network system.5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in “Sub 6GHz” bands such as 3.5GHz, but also in “Above 6GHz” bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.Moreover, there has been ongoing standardization in air interface architecture / protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture / service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.According to an aspect of an exemplary embodiment, there is provided a communication method in a wireless communication system.FIG. 1 is a block diagram that illustrates a User Equipment for managing near-failure events during dual connectivity in a wireless communication network system according to embodiments as disclosed herein.FIG. 2 is a flowchart that illustrates a method for managing near-failure events during dual connectivity in a wireless communication network system according to embodiments as disclosed herein.FIG. 3 is a flow diagram that illustrates a scenario of logging a SuccessPSCell Report (SPR) based on the timer T312 threshold by the UE in the wireless communication networks according to embodiments as disclosed herein.FIG. 4 is a flow diagram that illustrates the UE logging SPR based on the T312 thresholds according to embodiments as disclosed herein.FIG. 5 is a flow diagram that illustrates a Network node configuring the T312 thresholds according to embodiments as disclosed herein.FIG. 6 is a flow diagram that illustrates the UE performing measurements for conditional Layer-1 / Layer-2 Triggered Mobility (LTM) according to embodiments as disclosed herein.FIG. 7 is a flow diagram that illustrates a scenario for determining fulfillment of entry conditions for conditional Layer-1 / Layer-2 Triggered Mobility (LTM) according to embodiments as disclosed herein.FIG. 8 is a flow diagram that illustrates a scenario for determining fulfillment of leaving conditions for conditional Layer-1 / Layer-2 Triggered Mobility (LTM) according to embodiments as disclosed herein.FIG. 9 is a flow diagram that illustrates a scenario for the UE logging a SuccessPSCell Report (SPR) based on T312 thresholds for a Secondary Node (SN) initiated PSCell change according to embodiments as disclosed herein.FIG. 10 is a flow diagram illustrating a scenario for executing the Secondary Cell Group (SCG) Layer-1 / Layer-2 Triggered Mobility (LTM) cell switch according to embodiments as disclosed herein.FIG. 11 is a block diagram of a terminal or user equipment (UE) according to an embodiment of the disclosure.FIG. 12 is a block diagram of a base station (BS) according to an embodiment of the disclosure.FIG. 13 is a block diagram of a network entity according to an embodiment of the disclosure.Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanying drawings.In describing the embodiments, while numerous details are set forth for the purpose of illustration, it is understood that some aspects of the disclosure may be practiced with less than all of these details. Numerous variations and alternatives to the details provided herein are possible and are considered within the scope of the disclosure. In some instances, descriptions related to technical contents well-known in the art may be omitted so as to not obscure an understanding of the disclosure, and such omitted descriptions are understood to be within the scope of the disclosure.For the same reason, in the accompanying drawings, some elements may be exaggerated, omitted, or schematically illustrated. Further, the size of each element does not completely reflect the actual size. In the drawings, identical or corresponding elements are provided with identical reference numerals or different reference numerals.The advantages and features of the disclosure and ways to achieve them will be apparent by making reference to embodiments as described herein in detail in conjunction with the accompanying drawings. However, the disclosure is not limited to the embodiments set forth herein, but may be implemented in various different forms. Other features, aspects, and advantages of the subject matter described herein will become apparent from the disclosure. The following embodiments are merely examples to aid in an understanding of the disclosure and should not be construed to narrow the scope or spirit of the subject matter described herein in any way, but on the contrary, the disclosure covers all modifications, equivalents and alternatives falling within the spirit and scope of the subject matter as defined by the appended claims and equivalents thereof. Throughout the specification, the same or like reference numerals designate the same or like elements. Furthermore, terms which will be described herein are terms defined in consideration of the functions in the disclosure, and may be different according to users, intentions of the operators, or customs. Therefore, the definitions of the terms should be made based on the contents throughout the specification.Herein, it will be understood that each block of flowchart illustrations, and combinations of blocks in the flowchart illustrations, may be performed based on computer program instructions. These computer program instructions may be loaded collectively onto at least one processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which perform through any one of, or in any combination of, the at least one processor of the computer or other programmable data processing apparatus, create means for performing the functions specified in the flowchart block(s). These computer program instructions may also be stored in a non-transitory computer usable or computer-readable memory that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer usable or computer-readable memory produce an article of manufacture including instruction means that perform the function specified in the flowchart block(s). The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable data processing apparatus to produce a computer executed process such that the instructions that perform on the computer or other programmable data processing apparatus provide steps for executing the functions specified in the flowchart block(s).Further, each block may represent a module, segment, or portion of code, which includes one or more executable instructions for executing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order. For example, two blocks(or functions) shown in succession may in fact be performed substantially concurrently or the blocks may sometimes be performed in the reverse order, depending upon the functionality involved.As used in embodiments of the disclosure, a "~unit / module" may refer to a software element or a hardware element, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), which performs a predetermined function. However, the term including the word "~unit / module" does not always have a meaning limited to software or hardware. The "~unit / module" may be constructed either to be stored in an addressable storage medium or to execute one or more processors. Therefore, the "~unit / module" includes, for example, software elements, object-oriented software elements, components such as class elements and task elements, processes, functions, properties, procedures, sub-routines, segments of a program code, drivers, firmware, micro-codes, circuits, data, database, data structures, tables, arrays, and parameters. The components and functions provided by the "~unit / module" may be either combined into a smaller number of components and a "~unit / module," or divided into additional components and a "~unit / module." Moreover, the components and "~units / modules" may be implemented to reproduce one or more central processing units (CPUs) within a device or a security multimedia card. Further, in the embodiments, the "～unit / module" may include one or more processors.The entirety of the one or more computer programs may be stored in a single memory device or the one or more computer programs may be divided with different portions stored in different multiple memory devices.Any of the functions or operations described herein can be processed by one processor or a combination of processors. The one processor or the combination of processors is circuitry performing processing and includes circuitry like an application processor (AP, e.g. a CPU), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, a Bluetooth® chip, a global positioning system (GPS) chip, a near field communication (NFC) chip, connectivity chips, a sensor controller, a touch controller, a finger-print sensor controller, a display driver integrated circuit (IC), an audio CODEC chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, microprocessors, microcontrollers, digital signal processors, FPGA, ASIC, a microprocessor unit (MPU), a system on chip (SoC), an IC, or the like. The one processor or the combination of processors executes instructions that can be stored in a memory, such as the operating system, in order to control the overall operation of the device. Also, the one processor or the combination of processors is also capable of executing other processes and programs resident in the memory, such as processes for the disclosure.It will be appreciated that various embodiments of the disclosure according to the claims and description in the specification can be realized in the form of hardware, software or a combination of hardware and software.Any such software may be stored in non-transitory computer readable storage media. The non-transitory computer readable storage media store one or more computer programs (software modules), the one or more computer programs include computer-executable instructions that, when executed by one or more processors of an electronic device individually or collectively, cause the electronic device to perform a method of the disclosure. Additionally, or alternatively, such software may be a computer program [product] comprising instructions which, when executed by one or more processors of an electronic device individually or collectively, cause the electronic device to perform a method of the disclosure.Any such software may be stored in the form of volatile or non-volatile storage such as, for example, a storage device like read only memory (ROM), whether erasable or rewritable or not, or in the form of memory such as, for example, random access memory (RAM), memory chips, device or integrated circuits or on an optically or magnetically readable medium such as, for example, a compact disk (CD), digital versatile disc (DVD), magnetic disk or magnetic tape or the like. It will be appreciated that the storage devices and storage media are various embodiments of non-transitory machine-readable storage that are suitable for storing a computer program or computer programs comprising instructions that, when executed, implement various embodiments of the disclosure. Accordingly, various embodiments of the present disclosure may provide a program comprising code for implementing apparatus or a method as claimed in any one of the claims of this specification and a non-transitory machine-readable storage storing such a program.Hereinafter, the determination of priority between A and B in the present disclosure may refer to various actions such as selecting the one having a higher priority based on a predefined priority rule and performing an operation corresponding thereto, or omitting or dropping an operation corresponding to the one having a lower priority.Hereinafter, "A or B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.In addition, "at least one of A, B, and C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.In addition, "at least one of A, B, or C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.Furthermore, "A / B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.Furthermore, "A, B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.Furthermore, "A and B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.Furthermore, "if condition A and condition B are satisfied," as described in the present disclosure, may not be limited to a case where both condition A and condition B are satisfied, but may be understood to include a case where either condition A or condition B is individually satisfied, both condition A and condition B are satisfied, or one or more additional conditions are satisfied in combination.Furthermore, throughout this disclosure, ordinal terms such as "first," "second," "third," etc., (and similar qualifiers) are used merely to distinguish between different instances, occurrences, configurations, messages, stages, elements or aspects of elements, operations, or information as described herein. Unless the context clearly dictates otherwise, the use of such ordinal terms does not itself require that the elements, operations, or information distinguished by these terms be structurally different, numerically distinct, or substantively dissimilar. For example, a "first signal" and a "second signal" may refer to instances of the same signal transmitted at different times or containing the same core information despite minor variations, or they may refer to signals with different content or characteristics, depending on the specific context. Similarly, a "first value" and a "second value" may represent the same magnitude but measured or applied in different circumstances, or they may represent different magnitudes. The interpretation should be guided by the specific technical context, function, and relationship described in the relevant portion of the specification and claims.Furthermore, the terms "first ~", "second ~", etc., as described in the present disclosure with respect to various elements (e.g., information, objects, operation, sequences, or the like), should not limit those elements. These terms may only be intended to distinguish one element from another, and may not be intended to indicate a specific order. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element.Furthermore, even if "first ~" and "second ~" are described in the present disclosure, it may be understood that element(s) referred to by "first ~" and "second ~" may be the same or different. For example, in case of element(s) being information, first information and second information may both be same information and, in some cases, are separate and different information.In addition, the terms "if ~" and "in case that ~" as used in the disclosure or claims may be interpreted to include the meanings of "when (or upon) ~," "in response to ~," "based on ~," or "according to ~," and may be used interchangeably with these expressions. In addition, expressions other than those exemplified herein may also be used, as long as they have substantially the same meaning and do not impair the technical features of the present disclosure. If a method step (e.g. transmit a signal) is performed according to the disclosure of the application in connection with one of the above terms (such as "in case that ~" or the like), it may be interpreted to include the meanings (disclosure) of a prior determination that a feature has a specific state "~" (e.g. a bit length is above X), and then perform the method step in response to said determination.For example, the physical layer signaling may be referred to as Layer 1 (L1) signaling and may include downlink control information (DCI). In addition, the higher layer signaling may include a medium access control (MAC) control message, a radio resource control (RRC) signaling message, a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as L3 (layer 3) signaling. It should be noted, however, that the higher layer signaling is not limited to the aforementioned examples.In addition, the term "not perform" as used in the present disclosure or claims may, in context, be understood to mean that the corresponding step is omitted or skipped. Such a term may be replaced with other terms having the same or substantially equivalent meaning.In addition, "transmitting a message including A and B" as described in the present disclosure, may be understood as encompassing both (i) transmitting A and B in a single message, and (ii) transmitting A and B separately via multiple messages (e.g., transmitting a first message including A and a second message including B). This interpretation may also apply to messages that include two or more items (e.g., A, B, C), transmitted either together or separately.In addition, "transmitting a message including A and transmitting a message including B" may also be interpreted as transmitting a message including A and B in a single message.In the embodiments of the present disclosure described herein, terms or components included in the disclosure may be expressed in singular or plural form depending on the specific embodiments presented. However, such singular or plural expressions are selected appropriately for convenience of description, and the present disclosure is not limited to a singular or plural number of components. A component expressed in the plural form may be implemented as a single component, and a component expressed in the singular form may be implemented as multiple components.The drawings or flowcharts described herein illustrate example methods that may be implemented according to the principles of the present disclosure, and various modifications may be made to the methods illustrated in the flowcharts of the present disclosure. For example, although illustrated as a series of steps, various steps in each drawing or flowchart may overlap, occur in parallel, occur in a different order, or be repeated. In other examples, any step may be omitted or replaced with another step.The process of the flowchart may be performed by a device. One or more of the steps of the flowchart can be implemented by one or more processors / computer programs executing instructions to perform the noted functions.The methods and apparatuses proposed in the embodiments of the present disclosure may be disclosed in connection with drawings disclosing flowcharts to illustrate example methods that may be implemented according to the principles of the present disclosure. Such flowcharts may contain different branches and / or sub-branches. It is understood that the principles of the present disclosure do not only contain the combination of all branches / sub-branches disclosed in the embodiment, but the present disclosure also contains at least one isolated branch / isolated sub-branch, in particular to a single branch / single sub-branch.The methods and apparatuses proposed in the embodiments of the present disclosure are not limited to each embodiment individually, but may also be applied in combination of all or some of the embodiments proposed in the disclosure. Therefore, the embodiments of the present disclosure may be modified and applied without significantly departing from the scope of the present disclosure, as would be understood by those skilled in the art.In this case, even if certain wordings are described differently across embodiments, they may be used interchangeably or in substitution or in combination if their underlying concepts are equivalent. For example, for the same or equivalent concept, even if one embodiment uses the expression "A" and another embodiment uses the expression "B", such expressions may be understood interchangeably, in substitution, or in combination.The terms used in the following description to refer to access nodes, network entities, messages, interfaces between network entities, various types of identification information, and the like, are provided merely for the convenience of explanation by way of example. Therefore, the present disclosure is not limited to the terms describedherein, and other terms having equivalent technical meanings may also be used. Such terms may also be interchangeable with terms defined in any 3rd generation partnership project (3GPP) technical specifications (TS) or similar technical specifications, e.g., from the European telecommunications standards institute (ETSI), where appropriate.Hereinafter, a base station (BS) is an entity that allocates resources to terminals, and may be at least one of a gNode B, an eNode B, a Node B, a wireless access unit, a BS controller, or a node on a network.Furthermore, the base station of the present disclosure may include a split architecture comprising a central unit (CU) and a distributed unit (DU). In this structure, the CU is configured to process the higher layers of the control and user planes, while the DU is configured to process lower-layer radio resource functions. The embodiments of the present disclosure may be equally applicable to 5th generation (5G) base station architectures in which such CU and DU functional splits are implemented.A terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, a tablet, a wearable device, an Internet of Things (IoT) device, or any other device / system capable of performing communication functions.In the disclosure, a downlink (DL) refers to a radio link through which a BS transmits a signal to a terminal, and an uplink (UL) refers to a radio link through which a terminal transmits a signal to a BS.Furthermore, hereinafter, 5G mobile communication technologies (e.g., 5G new radio (NR)), 6th generation (6G) mobile communication technologies may be described by way of example, but the embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, newly evolved mobile communication systems developed after 5G and 6G may be included. Furthermore, based on determinations by those skilled in the art, the embodiments of the present disclosure may also be applied to other communication systems (e.g., Wi-Fi systems) through some modifications without significantly departing from the scope of the present disclosureIn the following description, the terms physical channel and signal may be used interchangeably with data or control signal. For example, the term physical downlink shared channel (PDSCH) refers to a physical channel through which data is transmitted, but the term PDSCH may also be used to refer to the data itself. That is, in the present disclosure, the expression "transmit a physical channel" may be interpreted as being equivalent to the expression "transmit data or a signal via a physical channel."Hereinafter, in the context of the present disclosure, higher layer signaling may refer to signaling corresponding to at least one or any combination of the following: master information block (MIB), system information block (SIB) or SIB M (M = 1, 2, ...), RRC, or MAC control element (CE), or a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as Layer 3 (L3) signaling.In addition, L1 signaling may refer to signaling corresponding to at least one or any combination of signaling techniques using the at least one or any combination of the following physical layer channels or signaling: physical downlink control channel (PDCCH), DCI, UE-specific DCI, group-common DCI, common DCI, scheduling DCI (e.g., DCI used for scheduling downlink or uplink data), non-scheduling DCI (e.g., DCI not used for scheduling downlink or uplink data) physical uplink control channel (PUCCH), or uplink control information (UCI). The L1 signaling message may be referred to as a physical layer signaling.Hereinafter, the expression that information is configured by the BS, as used in the present disclosure or claims, may, in context, be understood to mean that the terminal receives the corresponding information from the BS via a physical layer signaling or a higher layer signaling. Such an expression may be replaced with other terms having the same or substantially equivalent meaning.Hereinafter, the operational principle of the present disclosure will be described in detail with reference to the accompanying drawings.In the realm of wireless communication technologies, particularly in the context of 5G New Radio (NR), user equipment (UE) devices frequently traverse different cells, necessitating robust mobility management procedures. Mobility management in 5G NR is critical for maintaining seamless connectivity and service continuity as the UE transitions between cells. This process involves managing the UE's movement and ensuring that the connection remains stable and uninterrupted.Mobility management in 5G NR operates differently depending on the UE's mode. In Radio Resource Control (RRC) IDLE mode, mobility is managed through a procedure called cell reselection. However, in RRC CONNECTED mode, mobility is handled via a more intricate procedure known as handover. Up to NR Release 17, the handover process in RRC CONNECTED mode is network-controlled and requires explicit signaling from a Next Generation NodeB (gNB). The handover process typically involves three main steps: handover preparation, handover execution, and handover completion. During this process, the gNB may instruct the UE to report measurements. Based on these reported measurements or the gNB's own understanding of the network topology, the gNB sends an RRC Reconfiguration message to facilitate the UE's transition from a source cell to a target cell. Upon successful access to the target cell, the UE sends an RRC Reconfiguration Complete message.An alternative method introduced in the 3rd Generation Partnership Project (3GPP) NR Release 16 allows the gNB to configure the UE with execution conditions for triggering handover. Once these conditions are satisfied, the UE autonomously moves to the target cell and sends the RRC Reconfiguration Complete message. Despite the advancements provided by conditional handover, the handover process still relies heavily on Layer 3 (RRC) messages, which can result in significant signaling overhead and latency issues. During handover, the UE may be configured to apply full configuration during a Layer 3 handover, as described in section 5.3.5.11 of Technical Specification (TS) 38.331.In scenarios involving dual connectivity, the UE may perform Primary Secondary Cell Change (PSCellChange) or Conditional PSCellChange, configured by either a Master Node (MN) or a Secondary Node (SN). The PSCellChange process is also referred to as Layer 3 mobility. Specifically, PSCellChange or Conditional PSCellChange is termed Secondary Cell Group (SCG) Layer 3 mobility, while handover and Conditional Handover (CHO) are termed Master Cell Group (MCG) Layer 3 mobility within the context of dual connectivity.To address mobility management challenges, version 18.4.0 of the 3rd Generation Partnership Project (3GPP) specifications, such as TS 38.300, TS 38.331, and TS 38.321, provide relevant technical background. The 3GPP Release 18 is considering Lower Layers (L1 / L2 layers) Triggered Mobility, also known as LTM, to address latency and signaling overhead issues. The goal of LTM is to enable a serving cell change via L1 / L2 signaling to reduce the latency overhead and interruption time associated with Layer 3 mobility procedures. A network (gNB) may configure the UE with multiple candidate cells to allow fast application of configurations for the candidate cells. The network may further send Medium Access Control Control Element (MAC CE) or L1 signaling to dynamically switch the UE from a source cell to one of the configured candidate cells. Additionally, LTM can be triggered based on L1 measurements rather than L3 measurements.In existing mechanisms, the UE performs Layer 3 measurements for Conditional LTM (CLTM) according to specific conditions. The variables referenced are as per TS 38.331 but can be any other variable with similar functionality in other Radio Access Technologies (RATs). The UE performs the Layer 3 measurements when a reportType for an associated reportConfig is condTriggerConfig, a measurement identity (measId) is within a MCG VarMeasConfig, and the measurement identity is indicated in a CLTM-ExecutionConditions Information Element (IE) associated with the MCG. Similarly, the UE performs the Layer 3 measurements when the reportType for the associated reportConfig is condTriggerConfig, the measurement identity is within a SCG VarMeasConfig, and the measurement identity is indicated in a CLTM-ExecutionConditions IE associated with the SCG.For supporting subsequent LTM, the UE may be configured with CLTM execution conditions in the candidate cells. In the current system, the UE uses the CLTM execution conditions in the MCG for performing measurements for MCG CLTM. The UE uses the CLTM execution conditions in both a Primary Cell (PCell) and candidate cells. Similarly, for the SCG, the UE uses the CLTM execution conditions in a Primary Secondary Cell (PSCell) and SCG candidate cells for performing measurements for SCG CLTM. This approach of using CLTM execution conditions in both serving cells and candidate cells leads to the UE performing unnecessary measurements, resulting in battery drain and unnecessary energy consumption.In existing mechanisms, the UE logs a SuccessPSCell Report (SPR, also known as Successful PSCell Addition / Change Report) based on a T312 threshold for MN-initiated PSCellChange and SN-initiated PSCellChange. The UE logs the SPR if a ratio between the elapsed time of a timer T312 and the configured value of the timer T312 exceeds a certain threshold percentage (thresholdPercentageT312-SCG) before executing a last reconfiguration with synchronization for the SCG. The logging is crucial for understanding the state of mobility for the SCG.For SN-initiated PSCellChange, in the existing system, if the timer T312 associated with the measurement identity of the target PSCell was running at the time of initiating an execution of a reconfiguration with synchronization procedure for the SCG, and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312 configured while the UE was connected to a source PSCell before executing the last reconfiguration with synchronization is greater than thresholdPercentageT312-SCG included in a successPSCell-Config if configured by the source PSCell before executing the last reconfiguration with synchronization for the SCG, the UE logs the SPR. In the SPR, the UE logs that the SPR is due to the T312 cause. For MN initiated PSCellChange, in the existing system, if the timer T312 associated with the measurement identity of the target PSCell was running at the time of initiating an execution of a reconfiguration with synchronization procedure for the SCG, and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312 configured while the UE was connected to a source PSCell before executing the last reconfiguration with synchronization is greater than thresholdPercentageT312-SCG included in a successPSCell-Config if configured by the PCell, before executing the last reconfiguration with synchronization for the SCG, the UE logs the SPR. In the SPR, the UE logs that the SPR is due to the T312 cause.However, the UE may be configured with separate measurement objects for a target frequency by both the Master Node and the Secondary Node, leading to distinct measurement identities for the target PSCell. A first measurement identity is configured by the Master Node, and a second measurement identity is configured by the Secondary Node. If the timer T312 associated with the measurement identity configured by the Master Node is considered for determining the SPR, the timer T312 will not give an accurate state of the mobility for the SCG, leading to potential inaccuracies in mobility management and performance optimization.Thus, it is desired to address the above-mentioned disadvantages, issues, or other shortcomings, or at least provide a useful alternative.The principal object of the invention herein is for managing near-failure events during dual connectivity in a wireless communication network system.Yet another object of the invention is to provide a method for accurately logging SuccessPSCell Report (SPR) based on a T312 threshold during Primary Secondary Cell (PSCell) change procedures in dual connectivity scenarios by utilizing the timer T312 associated with a measurement identity of a target PSCell included in a measurement configuration associated with a Secondary Cell Group (SCG).Yet another object of the invention is to provide a method for distinguishing between timer T312 configured by a Master Node (MN) and timer T312 configured by a Secondary Node (SN) when determining SPR logging criteria, thereby ensuring accurate mobility state reporting for the SCG during MN-initiated and SN-initiated PSCell change procedures.Yet another object of the invention is to provide a User Equipment configured to manage near-failure events during dual connectivity by accurately determining and logging SPR when a ratio of an elapsed value of the timer T312 to a configured value of the timer T312 exceeds a threshold value, thereby optimizing Mobility Robustness Optimization (MRO) for the Secondary Cell Group.In an aspect, the objectives are achieved by providing a method for managing near-failure events during dual connectivity in a wireless communication network system. The method includes determining by a User Equipment (UE) whether a Secondary Cell Group (SCG) reconfiguration with synchronization (reconfigurationWithSync) procedure is initiated by the source Primary SCG Cell (PSCell). Further, the method includes determining by the UE that a timer T312 included in a measurement configuration associated with the SCG is running at a time of initiating the reconfigurationWithSync procedure for the SCG. Further, the method includes determining by the UE that a ratio of an elapsed value of the timer T312 to a configured value of the timer T312 exceeds a threshold value for logging a successful PSCell change or addition when the timer T312 is running at the time of initiating the reconfigurationWithSync procedure for the SCG. Further, the method includes logging by the UE successful PSCell change or addition information when the ratio exceeds the threshold value. Further, the method includes determining, by the UE, whether the ratio exceeds a threshold value included in a success PSCell configuration configured by a Primary Cell (PCell) before initiating a last reconfigurationWithSync procedure for the SCG. Further, the applicable timer T312 may be associated to a measurement identity of the target PSCell. Further, the configured value of the timer T312 may be set while the UE is connected to the source PSCell before initiating a last reconfigurationWithSync procedure. Further, the successful PSCell change or addition information may be logged in a variable success PSCell report. Further, the determining, by the UE, that the ratio between the elapsed value of the timer T312 and a configured value of the timer T312 comprises: determining, by the UE, at least one of: whether the ratio exceeds a threshold value included in a success PSCell configuration configured by a Primary Cell (PCell) before initiating a last reconfigurationWithSync procedure for the SCG when the reconfiguration with synchronization (reconfigurationWithSync) procedure is not initiated by the source PSCell, and whether the ratio exceeds a threshold value included in the success PSCell configuration configured by the source PSCell before initiating a last reconfigurationWithSync procedure for the SCG, when reconfigurationWithSync procedure is initiated by the source PSCell, and determining, by the UE, that the ratio exceeds the threshold value. Further, the method includes determining, by the UE, that a timer T312 associated with a measurement object for a target frequency configured by the MN is running, and determining, by the UE, that a timer T312 associated with a measurement object for the target frequency configured by the SN is not running, wherein the UE refrains from logging the successful PSCell change or addition information based on the threshold value when the timer configured by the SN is not running. Further, the method includes setting, by the UE, a T312-cause indicator in a success-PSCell-report to indicate that the logging of the successful PSCell change or addition information is triggered based on determining that a ratio associated with the timer T312 exceeds an applicable threshold value. Further, the method includes reporting, by the UE, the logged successful PSCell change or addition information based on the T312 to the network.In another aspect, the objectives are achieved by providing a user equipment for managing near-failure events during dual connectivity in a wireless communication network system. Further, the UE includes a memory, a processor, and a near-failure event optimisation controller. The near-failure event optimisation controller is coupled to the memory and the processor. The near-failure event optimisation controller determines whether a Secondary Cell Group (SCG) reconfiguration with synchronization (reconfigurationWithSync) procedure is initiated by the source Primary SCG Cell (PSCell). Further, the near-failure event optimisation controller determines that a timer T312 included in a measurement configuration associated with the SCG is running at a time of initiating the reconfigurationWithSync procedure for the SCG. Further, the near-failure event optimisation controller determines that a ratio of an elapsed value of the timer T312 to a configured value of the timer T312 exceeds a threshold value for logging a successful PSCell change or addition when the timer T312 is running at the time of initiating the reconfigurationWithSync procedure for the SCG. Further, the near-failure event optimisation controller logs successful PSCell change or addition information when the ratio exceeds the threshold value.The 3GPP specifications such as TS 38.300, TS 38.331, TS 37.340, and TS 38.321 version 18.4.0 are also considered relevant existing mechanisms. The measurement configuration includes the measurement objects, reporting configurations and measurement identities.In an embodiment, the measurement objects may be list of objects on which the user equipment shall perform the measurements. For intra-frequency and inter-frequency measurements, a measurement object indicates a frequency / time location and subcarrier spacing of reference signals to be measured. Associated with the measurement object, the network may configure a list of cell-specific offsets, a list of exclude-listed cells, and a list of allow-listed cells. The exclude-listed cells are not applicable in event evaluation or measurement reporting. The allow-listed cells are the only cells applicable in event evaluation or measurement reporting.In an embodiment, the reporting configurations may be a list of reporting configurations where there can be one or multiple reporting configurations per measurement object.In an embodiment, the measurement identities may be used for measurement reporting, a list of measurement identities where each measurement identity links one measurement object with one reporting configuration. By configuring multiple measurement identities, the measurement configuration enables linking more than one measurement object to the same reporting configuration, as well as linking more than one reporting configuration to the same measurement object. The measurement identity is also included in a measurement report that triggered the reporting, serving as a reference to the network. For conditional reconfiguration triggering, one measurement identity links to exactly one conditional reconfiguration trigger configuration. Up to 2 measurement identities can be linked to one conditional reconfiguration execution condition in NR.In NR Dual Connectivity (NR-DC), the user equipment may receive two independent measurement configurations (measConfig): a first measurement configuration associated with MCG that is included in an RRCReconfiguration message received via Signaling Radio Bearer 1 (SRB1), and a second measurement configuration associated with SCG that is included in an RRCReconfiguration message received via Signaling Radio Bearer 3 (SRB3) or alternatively included within an RRCReconfiguration message embedded in an RRCReconfiguration message received via SRB1.Further, if a measurement configuration (measConfig) is associated with a cell group, the measurement configuration is considered such that a measurement object or reporting configuration or measurement identity within the measurement configuration is associated with the same cell group.Further, the measurement configurations described above operate within a broader network architecture that enables mobility management across multiple cells and nodes.Further, the 5G NR (New Radio) radio access network, also known as Next Generation Radio Access Network (NG-RAN), comprises a number of NR base stations known as gNB. The gNB can be connected to each other through an Xn interface and are connected to various core network elements including an Access and Mobility Management Function (AMF) and a User Plane Function (UPF). Further, the gNB can be divided into two physical entities named a Centralized Unit (CU) and a Distributed Unit (DU). The Centralized Unit provides support for the higher layers of a protocol stack, such as Service Data Application Protocol (SDAP), Packet Data Convergence Protocol (PDCP), and Radio Resource Control (RRC), while the Distributed Unit provides support for the lower layers of the protocol stack, such as Radio Link Control (RLC), Medium Access Control (MAC), and a Physical layer. Each gNB can have multiple cells serving many user equipment devices. Further, the given complexity of managing multiple gNB, cells, and configuration parameters across such a distributed network architecture, automated optimization techniques become essential.Further, a large number of algorithms and configuration parameters are used in NG-RAN. Identifying the most optimal radio parameters is a very difficult task, and operators often resort to manual techniques like drive tests to identify the optimal parameters. However, such manual parameter tuning is a costly operation since the manual parameter tuning depends on many factors, such as a number of users, a number of neighbors, maximum throughput in a cell, average throughput in the cell, and other factors. Additionally, whenever a neighbor gNB is installed or a new service is introduced, many of the manual operations need to be repeated.To resolve the problem of manual parameter tuning, 3GPP has introduced Self-Organizing Networks (SON) techniques in wireless technologies like NR. SON was first introduced in 3GPP Release 9 in Long Term Evolution (LTE). SON solutions can be divided into three categories: Self-Configuration, Self-Optimization, and Self-Healing. The SON architecture can be a centralized solution, a distributed solution, or a hybrid solution. Mobility Robustness Optimization (MRO) is a SON technique used to optimize various parameters related to mobility. As a key component of SON-based mobility optimization, MRO relies on specific reporting mechanisms to detect and correct mobility-related problems, particularly in dual connectivity scenarios involving PSCell changes / According to 3GPP specifications such as TS 38.300 Version 17.3.0, Mobility Robustness Optimization (MRO) aims at detecting and enabling correction of the following problems- connection failure due to intra-system or inter-system mobility; inter-system unnecessary handover, specifically too early inter-system handover from NR to Evolved Universal Terrestrial Radio Access Network (E-UTRAN) with no radio link failure; and inter-system handover ping-pong.Further, the MRO provides means to distinguish the above problems from NR coverage-related problems and other problems not related to mobility. The user equipment may be configured for reporting information related to successful PSCell Addition and successful PSCell Change. The information related to successful PSCell Addition and successful PSCell Change could be configured to be stored and reported in a report called SuccessPSCell Report (SPR). The configuration for the SuccessPSCell Report may be provided in SuccessPSCell-Config. The SuccessPSCell-Config structure includes several threshold parameters that determine when the user equipment should generate and log SPR information based on timer values during PSCell mobility procedures.SuccessPSCell-Config-r18 ::= SEQUENCE {thresholdPercentageT304-SCG-r18 ENUMERATED {p40, p60, p80, spare5, spare4, spare3, spare2, spare1} OPTIONAL, --Need RthresholdPercentageT310-SCG-r18 ENUMERATED {p40, p60, p80, spare5, spare4, spare3, spare2, spare1} OPTIONAL, --Need RthresholdPercentageT312-SCG-r18 ENUMERATED {p20, p40, p60, p80, spare4, spare3, spare2, spare1} OPTIONAL, --Need R...}The thresholdPercentageT304-SCG field indicates the threshold for the ratio in percentage between the elapsed T304 timer associated with the target PSCell and the configured value of the T304 timer. Value p40 corresponds to 40%, value p60 corresponds to 60%, and so on. This field is set in the otherConfig configured by the target PSCell of the PSCell change or addition.The thresholdPercentageT310-SCG indicates the threshold for the ratio in percentage between the elapsed T310 timer associated with the source PSCell and the configured value of the T310 timer. Value p40 corresponds to 40%, value p60 corresponds to 60%, and so on. This field is set in the otherConfig configured by the source PSCell of the PSCell change or CPC or in the otherConfig configured by the PCell for the PSCell change or CPC. This field is not configured at the time of PSCell change via SRB3.The thresholdPercentageT312-SCG field indicates the threshold for the ratio in percentage between the elapsed T312 timer associated with the measurement identity of the target PSCell and the configured value of the T312 timer. Value p20 corresponds to 20%, value p40 corresponds to 40%, and so on. This field is set in the otherConfig configured by the source PSCell of the PSCell change or CPC or in the otherConfig configured by the PCell for the PSCell change or CPC. This field is not configured in case of sSN initiated PSCell change via SRB3.The following are the actions for the successful PSCell change or addition report determination. The UE shall for the PSCell:The UE shall for the PSCell:1> if the ratio between the value of the elapsed time of the timer T304 and the configured value of the timer T304, included in the last applied RRCReconfiguration message for the SCG including the reconfigurationWithSync, is greater than thresholdPercentageT304-SCG if included in the successPSCell-Config received before executing the last reconfiguration with sync for the SCG; or1> if sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is configured and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync for the SCG, is greater than thresholdPercentageT310-SCG included in the successPSCell-Config if configured by the source PSCell before executing the last reconfiguration with sync for the SCG; or1> if sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is configured and if the T312 associated to the measurement identity of the target PSCell was running at the time of initiating the execution of the reconfiguration with sync procedure for the SCG and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312-SCG included in the successPSCell-Config if configured by the source PSCell before executing the last reconfiguration with sync for the SCG:1> if sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is not configured and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync for the SCG, is greater than thresholdPercentageT310-SCG included in the successPSCell-Config if configured by the PCell before executing the last reconfiguration with sync for the SCG; or1> if sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is not configured and if the T312 associated to the measurement identity of the target PSCell was running at the time of initiating the execution of the reconfiguration with sync procedure for the SCG and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312-SCG included in the successPSCell-Config if configured by the PCell before executing the last reconfiguration with sync for the SCG:2> clear the information included in VarSuccessPSCell-Report, if any;2> store the successful PSCell change or addition information in VarSuccessPSCell-Report and determine the content in VarSuccessPSCell-Report as follows:<various steps of logging SPR>3> if triggering threshold for storing the successful PSCell change or addition information in VarSuccessPSCell-Report based on the thresholdPercentageT312-SCG is met:4> set t312-cause in spr-Cause to true;<various steps of logging SPR>1> release successPSCell-Config configured by the source PSCell if available and thresholdPercentageT304 if configured by the target PSCell.The UE may discard the successful PSCell change or addition information, i.e., release the UE variable VarSuccessPSCell-Report, 48 hours after the last successful PSCell change or addition information is added to the VarSuccessPSCell-Report or upon deregistration from the network as specified in TS 23.502

[0043] .In the present invention, the thresholdPercentageT312-SCG is generally referred to as T312 threshold. The T312 threshold can be associated with either the MCG or the SCG. If the T312 threshold is configured by PCell, it is associated with the MCG. If the T312 threshold is configured by the PSCell, it is associated with the SCG. The successPSCell-Config is also referred to as SPR configuration.For the purpose of the present invention, 3GPP TS 38.331 version 18.4.0 is considered as existing mechanism. Further, under the existing mechanisms defined in these specifications, the user equipment follows specific procedures for logging SPR based on T312 thresholds during MN-initiated and SN-initiated PSCell changes. The UE identifies whether a PSCellChange is MN initiated or SN initiated based on the presence of a flag which informs that the PSCellChange is SN initiated.In the existing mechanism, the user equipment logs the SPR based on the T312 threshold for MN-initiated PSCellChange. If the timer T312 associated to the measurement identity of the target PSCell was running at the time of initiating the execution of the reconfiguration with synchronization procedure for the SCG and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the user equipment was connected to the source PSCell before executing the last reconfiguration with synchronization, is greater than thresholdPercentageT312-SCG included in the successPSCell-Config if configured by the PCell before executing the last reconfiguration with synchronization for the SCG, the user equipment logs the SPR. In the SPR, the user equipment logs that the SPR is due to T312 cause.The user equipment may be configured with separate measurement objects for the target frequency by the MN and the SN. Hence, there can be separate measurement identities corresponding to the target PSCell, one measurement identity configured by the MN and one measurement identity configured by the SN. If the timer T312 associated with the measurement identity configured by the MN is considered for determining the SPR, the timer T312 will not give an accurate state of the mobility for the SCG.Further, with the evolution of traditional Layer 3 mobility mechanisms and SPR logging procedures, the 3GPP has also introduced Lower Layer Triggered Mobility (LTM) as an alternative approach to reduce latency and signaling overhead associated with conventional handover procedures.In another existing system, the 3GPP proposes to perform LTM without reset of lower layers like MAC to avoid data loss and to reduce the additional delay of data recovery wherever the avoidance is possible. The gNB may provide LTMCandidateConfiguration, where the gNB configures LTM candidate cells through one RRCReconfiguration message for a candidate target cell or through one CellGroupConfig for each candidate target cell or through any similar RRC structure or Information Element (IE) containing similar fields. For example, a new IE LTM-CandidateConfig can be defined as an Abstract Syntax Notation One (ASN.1) sequence containing CellGroupConfig and some other information elements in the RRCReconfiguration. The gNB may further release or modify the candidate configurations. A user equipment may store the LTM configuration of other candidate cells even after moving to a candidate cell through LTM.Further, to avoid transmitting a large message over air interface, the gNB can provide the LTMCandidateConfiguration as delta configuration instead of full configuration. The gNB can indicate the user equipment to use a source cell configuration as a reference for the delta configuration or provide a reference configuration explicitly.Further, the gNB also may provide the user equipment with configuration for performing LTM measurements for different candidate frequencies and candidate cells and reporting based on the performed LTM measurements. The gNB provides reference configuration, L1 measurement configuration, and candidate cell configuration for LTM.Further, the LTM mechanisms have evolved significantly across 3GPP releases to support increasingly complex mobility scenarios, particularly with the introduction of inter-CU mobility capabilities.Further, while Release-18 of 3GPP supported LTM within the same gNB CU, Release-19 is planning to introduce Inter-CU LTM. For SN LTM, both intra-SN LTM and inter-SN LTM can be configured simultaneously. For Inter-CU SCG LTM configuration, the SN generates SCG part configuration, and the MN includes the SCG part configuration into an MN RRC configuration message. For inter-CU SCG LTM, an LTM cell switch command MAC CE is sent by a source SN. Upon execution of inter-SN SCG LTM, the user equipment sends an MN RRCReconfigurationComplete message to the MN, which includes an SN RRCReconfigurationComplete message.Further, the Network implementation avoids the simultaneous execution for both MCG and SCG LTM. In Release 19, inter-CU MCG LTM with intra-SN PSCell change is supported.Further, with respect to dual connectivity, the following scenarios can coexist: Inter-MN LTM and intra-SN LTM; and Inter-SN LTM and intra-MN LTM.Further, in such dual connectivity scenarios, the coordination between the Master Node and Secondary Node for LTM configuration becomes critical for proper mobility management.For a user equipment in dual connectivity, both the MN and the SN can provide the LTM configuration including LTM candidate cells and LTM reference configuration. The MN and the SN may also provide the LTM measurement configurations to the user equipment. The SN sends an Inter-Node RRC message CG-Config to the MN to inform about the configurations the SN has used and to request about the configuration the SN can use. The MN sends an Inter-Node RRC message CG-ConfigInfo to the SN to inform about the configurations the SN is allowed to use, as well as other information.1> if the RRCReconfiguration message includes the ltm-ConfigSCG:2> if the ltm-ConfigSCG is set to setup:3> perform the LTM configuration procedure as specified in5.3.5.18.1;2> else:3> perform the LTM configuration release procedure as specifiedin clause 5.3.5.18.7;According to prior art, the network configures the user equipment with one or more LTM candidate configurations within an LTM-Config IE.In NR-DC, the user equipment may receive two independent ltm-Config:- an ltm-Config associated with the MCG that is included within an RRCReconfiguration message received via SRB1; and- an ltm-Config associated with the SCG that is included within an RRCReconfiguration message either received via SRB3, or, alternatively, embedded in an RRCReconfiguration message received via SRB1.Further, each LTM configuration includes multiple fields that define the specific parameters and conditions for candidate cell mobility.Further, in case the UE receives two independent ltm-Config:- the UE maintains two independentltm-Config;- the UE maintains two independentVarLTM-ServingCellNoResetID, one associated with eachltm-Config;- the UE maintains two independentVarLTM-ServingCellUE-MeasuredTA-ID, one associated with eachltm-Config;- the UE independently performs all the procedures in clause 5.3.5.18 for eachltm-Configand the associatedVarLTM-ServingCellNoResetIDandVarLTM-ServingCellUE-MeasuredTA-IDunless explicitly stated otherwise.Further, the UE shall perform the following actions based on the received LTM-Config IE:1> if the received LTM-Config includes ltm-ServingCellNoResetID:2> if the current VarLTM-ServingCellNoResetID includes an ltm-ServingCellNoResetID:3> replace the ltm-ServingCellNoResetID value within VarLTM-ServingCellNoResetID with the received ltm-ServingCellNoResetID;2> else:3> store the received ltm-ServingCellNoResetID in VarLTM-ServingCellNoResetID;1> if the received LTM-Config includes ltm-ServingCellUE-MeasuredTA-ID:2> if the current VarLTM-ServingCellUE-MeasuredTA-ID includes an ltm-ServingCellUE-MeasuredTA-ID:3> replace the ltm-ServingCellUE-MeasuredTA-ID value within VarLTM-ServingCellUE-MeasuredTA-ID with the received ltm-ServingCellUE-MeasuredTA-ID;2> else:3> store the received ltm-ServingCellUE-MeasuredTA-ID in VarLTM-ServingCellUE-MeasuredTA-ID;1> if the received LTM-Config includes ltm-ServingCellNoSecurityChangeID:2> if the current VarLTM-SecurityChange includes an ltm-ServingCellNoSecurityChangeID:3> replace the ltm-ServingCellNoSecurityChangeID value within VarLTM-SecurityChange with the received ltm-ServingCellNoSecurityChangeID;2> else:3> store the received ltm-ServingCellNoSecurityChangeID in VarLTM-SecurityChange;1> if the received LTM-Config includes ltm-SK-Counters:2> if the current VarLTM-SecurityChange includes an ltm-SK-Counters:3> replace the ltm-SK-Counters value within VarLTM-SecurityChange with the received ltm-SK-Counters;2> else:3> store the received ltm-SK-Counters in VarLTM-SecurityChange;1> if the received LTM-Config includes the ltm-CandidateToReleaseList:2> perform the LTM candidate configuration release as specified in 5.3.5.18.2;1> if the received LTM-Config includes the ltm-CandidateToAddModList:2> perform the LTM candidate configuration addition or modification as specified in 5.3.5.18.3;1> reconfigure the UE according to all other fields of the received LTM-Config IE;1> if the received LTM-Config includes the field cltm-ServingCellExecutionConditions:2> stop the LTM conditions evaluation (based on L1 and / or L3 measurements), if any, for all the LTM candidate configurations associated with the cell group for which the LTM-Config is received:2> if the field l3-Conditions is included within cltm-ServingCellExecutionConditions:3> perform the LTM cell switch conditions evaluation based on L3 measurements as specified in 5.3.5.18.x according to the received cltm-ServingCellExecutionConditions;2> else if the field l1-Conditions is included within cltm-ServingCellExecutionConditions:3> inform lower layers to initiate the LTM cell switch conditions evaluation based on L1 measurements according to the received field cltm-ServingCellExecutionConditions.Further, the conditional LTM execution based on L3 measurements is provided as follows. LTM cell switch conditions evaluation based on L3 measurements is described. The user equipment shall:1> if the CLTM-ExecutionConditions IE is part of an RRCReconfiguration message received via SRB1, but not within mrdc-SecondaryCellGroup or ltm-ConfigSCG:2> for each entry within the CLTM-ExecutionConditions IE associated with the MCG which has the field l3-Conditions configured:3> for each measID indicated in the field l3-Conditions which has a corresponding measID in the VarMeasConfig associated with the MCG measConfig:4> if the condEventId related to this measID is associated with condEventA3 or condEventA5, and if the entry condition(s) applicable for this event is fulfilled for the ltm-CandidatePCI related to the ltm-CandidateId for all measurements after layer 3 filtering taken during the corresponding timeToTrigger defined for this event:5> consider the event associated to this measId to be fulfilled for the ltm-CandidateId associated to the measId;4> if the condEventId related to this measID is associated with condEventA3 or condEventA5, and if the leaving condition(s) applicable for this event is fulfilled for the ltm-CandidatePCI related to the ltm-CandidateId for all measurements after layer 3 filtering taken during the corresponding timeToTrigger defined for this event:5> consider the event associated to this measId to be not fulfilled for the ltm-CandidateId associated to the measId;1> else if the CLTM-ExecutionConditions IE is part of an RRCReconfiguration message received via SRB1 (within mrdc-SecondaryCellGroup or ltm-ConfigSCG) or within an RRCReconfiguration message received via SRB3:2> for each entry within the CLTM-ExecutionConditions IE associated with the SCG which has the field l3-Conditions configured:3> for each measID indicated in the field l3-Conditions which has a corresponding measID in the VarMeasConfig associated with the SCG measConfig:4> if the condEventId related to this measID is associated with condEventA3 or condEventA5, and if the entry condition(s) applicable for this event is fulfilled for the ltm-CandidatePCI related to the ltm-CandidateId for all measurements after layer 3 filtering taken during the corresponding timeToTrigger defined for this event:5> consider the event associated to this measId to be fulfilled for the ltm-CandidateId associated to the measId;4> if the condEventId related to this measID is associated with condEventA3 or condEventA5, and if the leaving condition(s) applicable for this event is fulfilled for the ltm-CandidatePCI related to the ltm-CandidateId for all measurements after layer 3 filtering taken during the corresponding timeToTrigger defined for this event:5> consider the event associated to this measId to be not fulfilled for the ltm-CandidateId associated to the measId;1> if event(s) associated to all measId(s) for a ltm-CandidateId within the CLTM-ExecutionConditions IE are fulfilled:2> perform the LTM cell switch procedure for the LTM candidate configuration associated to the ltm-CandidateId according to the actions specified in 5.3.5.18.6.In the existing mechanisms below structure may be used for defining conditional LTM.In one embodiment, the ltm-CandidateConfig field includes an RRCReconfiguration message used to configure an LTM candidate configuration. The ltm-CandidatePCI field identifies the PCI of the SpCell of the LTM candidate configuration contained in ltm-CandidateConfig.In another embodiment, the ltm-EarlyUL-SyncConfig and ltm-EarlyUL-SyncConfigSUL fields provide a configuration used to perform the early UL synchronization procedure over an UL or SUL carrier. If the network configures the ltm-NoResetID field for one LTM candidate configuration, the network configures the ltm-NoResetID field also for all LTM candidate configurations within ltm-CandidateToAddModList in LTM-Config and ensures that the user equipment has stored a value for ltm-ServingCellNoResetID within VarLTM-ServingCellNoResetID.In an embodiment, if the network configures the ltm-NoSecurityChangeID field for one LTM candidate configuration, the network configures the ltm-NoSecurityChangeID field also for all LTM candidate configurations within ltm-CandidateToAddModList in LTM-Config and ensures that the user equipment has stored a value for ltm-ServingCellNoSecurityChangeID within VarLTM-ServingCellNoSecurityChangeID. If the network configures the ltm-UE-MeasuredTA-ID field for one LTM candidate configuration, the network configures the ltm-UE-MeasuredTA-ID field also for all LTM candidate configurations within ltm-CandidateToAddModList in LTM-Config and ensures that the user equipment has stored a value for ltm-ServingCellUE-MeasuredTA-ID within VarLTM-ServingCellUE-MeasuredTA-ID. The ltm-UE-MeasuredTA-ID field is absent if tag2 is present for the LTM candidate configuration.Further, the IE LTM-Config is used to provide LTM configurations.Further, the UE performs measurements based on the measurement configuration from the network. For conditional LTM, UE performs layer 3 measurements as below, description is according to TS 38.331:1> for each measId included in the measIdList within VarMeasConfig:2> if the reportType for the associated reportConfig is condTriggerConfig, the measId is within the MCG VarMeasConfig and is indicated in a CLTM-ExecutionConditions IE associated with the MCG; or2> if the reportType for the associated reportConfig is condTriggerConfig, the measId is within the SCG VarMeasConfig and is indicated in a CLTM-ExecutionConditions IE associated with the SCG:3> if a measurement gap configuration is setup, or3> if the UE does not require measurement gaps to perform the concerned measurements:4> if s-MeasureConfig is not configured, or4> if s-MeasureConfig is set to ssb-RSRP and the NR SpCell RSRP based on SS / PBCH block, after layer 3 filtering, is lower than ssb-RSRP, or4> if s-MeasureConfig is set to csi-RSRP and the NR SpCell RSRP based on CSI-RS, after layer 3 filtering, is lower than csi-RSRP:5> if the measObject is associated to NR and the rsType is set to csi-rs:6> if reportQuantityRS-Indexes and maxNrofRS-IndexesToReport for the associated reportConfig are configured:7> derive layer 3 filtered beam measurements only based on CSI-RS for each measurement quantity indicated in reportQuantityRS-Indexes, as described in 5.5.3.3a;6> derive cell measurement results based on CSI-RS for the trigger quantity and each measurement quantity indicated in reportQuantityCell using parameters from the associated measObject, as described in 5.5.3.3;5> if the measObject is associated to NR and the rsType is set to ssb:6> if reportQuantityRS-Indexes and maxNrofRS-IndexesToReport for the associated reportConfig are configured:7> derive layer 3 beam measurements only based on SS / PBCH block for each measurement quantity indicated in reportQuantityRS-Indexes, as described in 5.5.3.3a;6> derive cell measurement results based on SS / PBCH block for the trigger quantity and each measurement quantity indicated in reportQuantityCell using parameters from the associated measObject, as described in 5.5.3.3;5> if the measObject is associated to E-UTRA:6> perform the corresponding measurements associated to neighbouring cells on the frequencies indicated in the concerned measObject, as described in 5.5.3.2;5> if the measObject is associated to UTRA-FDD:6> perform the corresponding measurements associated to neighbouring cells on the frequencies indicated in the concerned measObject, as described in 5.5.3.2;5> if the measObject is associated to L2 U2N Relay UE:6> perform the corresponding measurements associated to candidate Relay UEs on the frequencies indicated in the concerned measObject, as described in 5.5.3.4;4> if the measRSSI-ReportConfig is configured in the associated reportConfig:5> perform the RSSI and channel occupancy measurements on the frequency configured by rmtc-Frequency in the associated measObject;NOTE 0: The network avoids configuring UEs supporting only CHO and / or Rel-16 CPC with measurements not referred to by any execution condition.2> if the reportType for the associated reportConfig is set to reportSFTD and the numberOfReportsSent as defined within the VarMeasReportList for this measId is less than one:3> if the reportSFTD-Meas is set to true:4> if the measObject is associated to E-UTRA:5> perform SFTD measurements between the PCell and the E-UTRA PSCell;5> if the reportRSRP is set to true;6> perform RSRP measurements for the E-UTRA PSCell;4> else if the measObject is associated to NR:5> perform SFTD measurements between the PCell and the NR PSCell;5> if the reportRSRP is set to true;6> perform RSRP measurements for the NR PSCell based on SSB;3> else if the reportSFTD-NeighMeas is included:4> if the measObject is associated to NR:5> if the drx-SFTD-NeighMeas is included:6> perform SFTD measurements between the PCell and the NR neighbouring cell(s) detected based on parameters in the associated measObject using available idle periods;5> else:6> perform SFTD measurements between the PCell and the NR neighbouring cell(s) detected based on parameters in the associated measObject;5> if the reportRSRP is set to true:6> perform RSRP measurements based on SSB for the NR neighbouring cell(s) detected based on parameters in the associated measObject;2> if the reportType for the associated reportConfig is cli-Periodical or cli-EventTriggered:3> perform the corresponding measurements associated to CLI measurement resources indicated in the concerned measObjectCLI;2> perform the evaluation of reporting criteria as specified in 5.5.4, except if reportConfig is condTriggerConfig.However, the existing measurement procedures for Conditional LTM result in significant inefficiencies that negatively impact user equipment battery consumption and overall system performance.In the existing mechanisms, the user equipment performs Layer 3 measurements for Conditional LTM (CLTM) according to specific conditions. The variables are as per TS 38.331, but can be any other variable with similar functionality in other Radio Access Technologies (RATs).In a first condition, if the reportType for the associated reportConfig is condTriggerConfig, the measId is within the MCG VarMeasConfig and is indicated in a CLTM-ExecutionConditions IE associated with the MCG.In a second condition, if the reportType for the associated reportConfig is condTriggerConfig, the measId is within the SCG VarMeasConfig and is indicated in a CLTM-ExecutionConditions IE associated with the SCG.For supporting subsequent LTM, the user equipment may be configured with CLTM execution conditions in the candidate cells. In the current system, the user equipment uses the CLTM execution conditions in the MCG for performing measurements for MCG CLTM. The user equipment uses the CLTM execution conditions in both the PCell and candidate cells. Similarly, for the SCG, the user equipment uses the CLTM execution conditions in the PSCell and SCG candidate cells for performing measurements for SCG CLTM. The approach of using CLTM execution conditions in both serving cells and candidate cells leads to the user equipment performing unnecessary measurements, leading to battery drain and unnecessary energy consumption.To overcome the drawbacks of the existing system, there is a need for an improved method for logging SuccessPSCell Report based on the T312 threshold that accurately reflects the mobility state for the SCG.The present invention discloses a mechanism that considers the timer T312 associated with the measurement identity configured by the appropriate cell group when determining whether to log the SPR for MN-initiated PSCellChange and SN-initiated PSCellChange. The present invention discloses a method that ensures the user equipment logs the SPR based on the timer T312 configured in the measurement configuration associated with the SCG rather than the MCG when performing MN-initiated PSCellChange and SN initiated PSCellChange, thereby providing accurate mobility state information for the SCG and enabling proper Mobility Robustness Optimization.Further, the present invention discloses a method that ensures the user equipment logs the SPR based on the timer T312 configured in the measurement configuration associated with the SCG and the T312 threshold configured by the appropriate node when performing SN-initiated PSCellChange, thereby avoiding inaccurate SPR logging that could result from using the timer T312 associated with the incorrect cell group. The present invention discloses an optimized method for Layer 3 measurements for Conditional LTM to reduce unnecessary measurements in serving cells, thereby minimizing battery drain and energy consumption while maintaining effective mobility management for subsequent LTM operations.The present invention discloses a method that distinguishes between measurement configurations provided by the Master Node and the Secondary Node when determining SPR logging criteria, thereby ensuring that the appropriate timer T312 and T312 threshold values are used based on whether the PSCellChange is MN-initiated or SN-initiated.FIG. 1 is a block diagram that illustrates a User Equipment (101) for managing near-failure events during dual connectivity in a wireless communication network system, according to embodiments as disclosed herein.Examples of the UE (101) include, but are not limited to, Consumer Electronics (such as Mobile Phones and Smartphones), Tablets, Wearable Devices, Television, Computing Devices (such as Laptops, Notebooks, Desktops, Workstations, etc.), IoT Devices, Automotive Systems (such as connected cars, Autonomous Vehicles, Vehicle-to-Everything (V2X) communication devices, etc.), Enterprise Devices such as robotics, Specialized Equipment (such as Medical Devices, Public Safety Devices, etc.), and Media Devices (such as Gaming Consoles, Streaming Devices, etc.).Examples of the wireless communication network system include, but are not limited to, Cellular Networks (such as 2G, 3G, 4G, 5G, Beyond 5G (B5G) / 6G, or advanced cellular networks), Local Area Networks (LANs) (such as Wi-Fi, Li-Fi, etc.), Personal Area Networks (PANs) (such as Bluetooth, Zigbee, Z-Wave, etc.), Wide Area Networks (WANs) (such as Satellite Communication Networks, Long Range Wide Area Network, Narrowband IoT, Low-bandwidth communication for IoT, etc.), Metropolitan Area Networks (MANs), Machine-to-Machine (M2M), Ad Hoc and Mesh Networks, Emerging and Advanced Networks. Examples of the UE can include, but are not limited to, Consumer Electronics (such as Mobile Phones and Smartphones), Tablets, Wearable Devices, Computing Devices (such as Laptops, Notebooks, Desktops, Workstations, etc.), IoT Devices, Automotive Systems (such as connected cars, Autonomous Vehicles, Vehicle-to-Everything(V2X) communication devices, etc.), Enterprise Devices such as robotics, Specialized Equipment (such as Medical Devices, Public Safety Devices, etc.), Media Devices (such as Gaming Consoles, Streaming Devices, etc.).The UE (101) includes the processor (102), the memory (104), an I / O interface (104) and a near-failure event optimisation controller (105). The processor (102) of the UE (101) communicates with the memory (104), the I / O interface (104) and the near-failure event optimisation controller (105). The processor (102) is configured to execute instructions stored in the memory (104) and to perform various processes. The processor (102) can include one or a plurality of processors, can be a general-purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an Artificial intelligence (AI) dedicated processor such as a neural processing unit (NPU).Further, the memory (104) of the UE (101) includes storage locations to be addressable through the processor (102). The memory (104) is not limited to a volatile memory and / or a non-volatile memory. Further, the memory (104) can include one or more computer-readable storage media. The memory (104) can include non-volatile storage elements. For example, non-volatile storage elements can include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. The memory (104) includes storage for Radio Resource Control (RRC) reconfiguration messages related to PSCell change, LTM configuration information including ltm-Config and ltm-ConfigSCG, T312 thresholds configured by a Master Cell Group (MCG) and a Secondary Cell Group (SCG), T312 timer values associated with measurement objects for target frequencies of the MCG and the SCG, SuccessPSCell Report (SPR) logging information, and parameters used for determining SPR logging based on the T312 threshold for MN initiated PSCellChange and SN initiated PSCellChange.The I / O interface (103) transmits the information between the memory (104) and external peripheral devices. The peripheral devices are the input-output devices associated with the UE (101). The I / O interface (103) receives several information from the UE (101).The near-failure event optimisation controller (105) is coupled to the memory (104) and the processor (103). This coupling allows for efficient data transfer and communication between the components, ensuring that the near-failure event optimisation controller (105) can access and process T312-related PSCell change data in real time. The near-failure event optimisation controller (105) is an innovative integrated circuit that is implemented in the user equipment (UE) (101). In an embodiment, the structure of such innovative integrated circuit includes a multi-core architecture that enables dynamic management of T312-based near-failure evaluation during PSCell change operations in a wireless communication system. Each core is optimized for specific tasks, such as determining PSCell change type based on RRC reconfiguration messages, identifying whether the PSCell change is MN initiated or SN initiated, checking whether the T312 associated with the measurement object corresponding to the SCG is running at the initiation of the PSCell change, and evaluating whether an elapsed-to-configured T312 ratio exceeds a T312 threshold configured by the MCG or the SCG for logging a SuccessPSCell Report (SPR). The innovative integrated circuit manages selective consideration of T312 values from measurement objects associated with the target frequency of the MCG and the SCG to ensure correct SPR logging based on the SCG-associated T312 timer. The innovative integrated circuit for managing T312-based optimisation is composed of a combination of analog and digital components designed to optimize evaluation accuracy and timing precision of the PSCell change mechanism. The analog components include a high-precision clock and timing reference circuit to ensure accurate T312 timing measurement, while the digital components include a microcontroller unit (MCU) and a digital signal processor (DSP) that work in tandem to dynamically process T312 thresholds, T312 timer values, and RRC reconfiguration parameters during the T312-based optimisation procedure.Further, the near-failure event optimisation controller (105) determines whether a Secondary Cell Group (SCG) reconfiguration with synchronization (reconfigurationWithSync) procedure is initiated by the source Primary SCG Cell (PSCell). Further, the near-failure event optimisation controller (105) determines that an timer T312 included in a measurement configuration associated with the SCG, is running at a time of initiating the reconfigurationWithSync procedure for the SCG. Further, the near-failure event optimisation controller (105) determines that a ratio of an elapsed value of the timer T312 to a configured value of the timer T312 exceeds a threshold value for logging a successful PSCell change or addition, when the timer T312 is running at the time of initiating the reconfigurationWithSync procedure for the SCG. Further, the near-failure event optimisation controller (105) logs successful PSCell change or addition information, when the ratio exceeds the threshold value.Further, the near-failure event optimisation controller (105) determines whether the ratio exceeds a threshold value included in a success PSCell configuration configured by a Primary Cell (PCell) before initiating a last reconfigurationWithSync procedure for the SCG.Further, the near-failure event optimisation controller (105) determines that the applicable timer T312 is associated with a measurement identity of the target PSCell.Further, the near-failure event optimisation controller (105) determines that the configured value of the timer T312 is set while the UE (101) is connected to the source PSCell before initiating a last reconfigurationWithSync procedure.Further, the near-failure event optimisation controller (105) determines that the successful PSCell change or addition information is logged in a variable successPSCell-Report.Further, the near-failure event optimisation controller (105) determines that the ratio between the elapsed value of the timer T312 and a configured value of the timer T312 inludes determining whether the ratio exceeds a threshold value included in a success PSCell configuration configured by a Primary Cell (PCell) before initiating a last reconfigurationWithSync procedure for the SCG when the reconfigurationWithSync procedure is not initiated by the source PSCell. Further, the near-failure event optimisation controller (105) determines whether the ratio exceeds a threshold value included in the success PSCell configuration configured by the source PSCell before initiating a last reconfigurationWithSync procedure for the SCG when the reconfigurationWithSync procedure is initiated by the source PSCell, and determining that the ratio exceeds the threshold value.Further, the near-failure event optimisation controller (105) determines that a timer T312 associated with a measurement object for a target frequency provided by the MN is running, and determines that a timer T312 associated with a measurement object for the target frequency provided by the SN is not running. The UE (101) refrains from logging the successful PSCell change or addition information based on the threshold value when the timer provided by the SN is not running.Further, the near-failure event optimisation controller (105) sets a T312-cause indicator in a Success-PSCell-Report to indicate that the logging of the successful PSCell change or addition information is triggered based on determining that a ratio associated with the timer T312 exceeds an applicable threshold value.Further, the near-failure event optimisation controller (105) reports the logged successful PSCell change or addition information based on the T312 to the network.FIG. 2 is a flowchart that illustrates a method for managing near-failure events during dual connectivity in a wireless communication network system, according to embodiments as disclosed herein.At step 201, the method includes determining whether the SCG reconfiguration with synchronization (reconfigurationWithSync) procedure is initiated by the source Primary SCG Cell (PSCell).At step 202, the method includes determining that the timer T312 included in the measurement configuration associated with the SCG is running at the time of initiating the reconfigurationWithSync procedure for the SCG.At step 203, the method includes determining that the ratio of the elapsed value of the timer T312 to the value of the timer T312 exceeds a threshold for logging a successful PSCell change or addition information when the timer T312 is running at the time of initiating the reconfigurationWithSync procedure for the SCG.At step 204, the method includes logging the successful PSCell change or addition information when the ratio exceeds the threshold.FIG. 3 is a flow diagram that illustrates a scenario of logging a SuccessPSCell Report (SPR) based on the timer T312 threshold by the UE (101) in the wireless communication networks according to embodiments as disclosed herein.At step 301, the UE (101) completes a successful PSCell change procedure. The successful PSCell change procedure may be initiated by the Master Node (MN) or the Secondary Node (SN) in a dual connectivity scenario.At step 302, the UE (101) determines whether specific conditions for logging the SPR based on the T312 threshold are satisfied. The UE (101) evaluates whether sn-InitiatedPSCellChange associated to a last applied RRCReconfiguration with reconfigurationWithSync for the SCG is not configured. Further, the UE (101) determines whether the timer T312 associated to a measurement identity of a target PSCell included in a measurement configuration (measConfig) associated with the SCG may be running at a time of initiating an execution of a reconfiguration with synchronization procedure for the SCG. Additionally, the UE (101) evaluates whether the ratio between a value of an elapsed time of the timer T312 and the configured value of the timer T312, configured while the user equipment was connected to a source PSCell before executing a last reconfiguration with synchronization, is greater than thresholdPercentageT312-SCG included in a successPSCell-Config if configured by the Primary Cell (PCell) before executing the last reconfiguration with synchronization for the SCG.At step 303, when all conditions evaluated at step 302 are satisfied (YES branch), the UE (101) logs the SPR and sets a t312-cause field in an spr-Cause parameter to true in the SPR. The logging of the SPR indicates that the SPR is triggered due to the T312 threshold condition being met during the PSCell change procedure.At step 304, when all conditions evaluated at step 302 are not satisfied (No branch), the UE (101) does not log the SPR based on the T312 threshold. Further, the UE (101) does not set the t312-cause field in the spr-Cause parameter to true in the SPR. The user equipment may proceed with normal operation without logging SPR information related to the T312 threshold condition.In an embodiment, when the UE (101) is executing MN-initiated PSCellChange, if the UE (101) is configured with a T312 threshold by MN and if the T312 associated with the measurement object associated with the SCG corresponding to the PSCell is running at the time of initiating the MN-initiated PSCellChange, and the ratio of the elapsed value of T312 and the configured value of T312 is greater than the T312 threshold configured by the MN, the UE (101) logs SPR information and also logs that the SPR is caused due to T312 cause. In the embodiment, the UE (101) determines whether to log SPR for MN-initiated PSCellChange based on the T312 threshold configured by the PCell and the T312 configured in the measurement object associated with SCG for the target frequency.In an embodiment, when the T312 configured in the Measurement object associated with MCG for the target frequency is running and the T312 configured in the Measurement object associated with the SCG for the target frequency is not running, the UE (101) does not log SPR based on theT312 thresholdIn an embodiment, according to TS 38.331, The UE (101) shall for the PSCell:5.7.10.7 Actions for the successful PSCell change or addition report determinationThe UE shall for the PSCell:1> if the ratio between the value of the elapsed time of the timer T304 and the configured value of the timer T304, included in the last applied RRCReconfiguration message for the SCG including the reconfigurationWithSync, is greater than thresholdPercentageT304-SCG if included in the successPSCell-Config received before executing the last reconfiguration with sync for the SCG; or1> if sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is configured and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync for the SCG, is greater than thresholdPercentageT310-SCG included in the successPSCell-Config if configured by the source PSCell before executing the last reconfiguration with sync for the SCG; or1> if sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is configured and if the T312 associated to the measurement identity of the target PSCell was running at the time of initiating the execution of the reconfiguration with sync procedure for the SCG and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312-SCG included in the successPSCell-Config if configured by the source PSCell before executing the last reconfiguration with sync for the SCG:1> if sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is not configured and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync for the SCG, is greater than thresholdPercentageT310-SCG included in the successPSCell-Config if configured by the PCell before executing the last reconfiguration with sync for the SCG; or1> if sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is not configured and if the T312 associated to the measurement identity of the target PSCell included in a measConfig associated with the SCG was running at the time of initiating the execution of the reconfiguration with sync procedure for the SCG and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312-SCG included in the successPSCell-Config if configured by the PCell before executing the last reconfiguration with sync for the SCG:2> clear the information included in VarSuccessPSCell-Report, if any;2> store the successful PSCell change or addition information in VarSuccessPSCell-Report and determine the content in VarSuccessPSCell-Report as follows:<various steps of logging SPR>3> if triggering threshold for storing the successful PSCell change or addition information in VarSuccessPSCell-Report based on the thresholdPercentageT312-SCG is met:4> set t312-cause in spr-Cause to true;<various steps of logging SPR>1> release successPSCell-Config configured by the source PSCell if available and thresholdPercentageT304 if configured by the target PSCellIn an embodiment, when a gNB retrieves the SPR, the gNB forwards the SPR to the MN which was the source MN for the PSCellChange or PSCellAddition. The MN sends the SPR to the SN for optimising the T312 thresholds. The SN identifies the measurement object, whose T312 was running and the SN optimises the T312 value of the precise measurement object along with other parameters such as various offsets, thresholds and time to trigger used for mobility, according to the embodiment. In the manner, the embodiment allows for the optimization of T312 for the precise measurement object in the SCG which has caused a near failure. The embodiment allows for the precise optimization of T312.FIG. 4 is a flow diagram that illustrates the UE (101) logging SPR based on the T312 thresholds, according to embodiments as disclosed herein.At step 401, a Successful PSCell Change occurs.At step 402, the UE (101) determines whether sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is not configured and whether theT312 associated to any measurement identity in a measConfig associated with the SCG was running at the time of initiating the execution of the reconfiguration with sync procedure for the SCG and whether the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE (101) was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312-SCG included in the successPSCell-Config configured by the PCell before executing the last reconfiguration with sync for the SCG.At step 403, when the determination (at step 402) is YES, the UE (101) logs SPR and sets the t312-cause in spr-Cause to true in SPR.At step 404, when the determination (at step 402) is NO, the UE (101) does not log SPR based on the T312 threshold and the UE (101) does not set the t312-cause in spr-Cause to true in SPR.

[0001] In an embodiment, when the UE (101) is executing MN initiated PSCellChange, when the UE (101) is configured with the T312 threshold by MN and when the T312 associated with any measurement object associated with the SCG is running at the time of initiating the MN initiated PSCellChange and the ratio of the elapsed value of T312 and the configured value of T312 is greater than the T312 threshold configured by the MN, the UE (101) logs SPR information and also logs that the SPR is caused due to T312 cause. In the embodiment, the UE (101) determines whether to log SPR for MN initiated PSCellChange based on T312 threshold configured by the PCell and the T312 configured in any Measurement object associated with SCG.In an embodiment, when the T312 configured in any Measurement object associated with MCG is running and the T312 configured in any Measurement object associated with SCG is not running, the UE (101) does not log SPR based on T312 threshold. This embodiment extends the logging of SPR to additional scenarios considering all the neighbor frequencies. This allows the optimization of scenarios where there are multiple neighbor cells, for which the UE (101) may trigger sending of the measurement report. However, this also has a disadvantage as it may trigger the optimization for the frequency which is not the most suitable target frequency as the UE has not finally moved to a target cell in that frequency.In an embodiment, according to TS 38.331, the UE (101) shall for the PSCell:5.7.10.7 Actions for the successful PSCell change or addition report determinationThe UE shall for the PSCell:1> if the ratio between the value of the elapsed time of the timer T304 and the configured value of the timer T304, included in the last applied RRCReconfiguration message for the SCG including the reconfigurationWithSync, is greater than thresholdPercentageT304-SCG if included in the successPSCell-Config received before executing the last reconfiguration with sync for the SCG; or1> if sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is configured and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync for the SCG, is greater than thresholdPercentageT310-SCG included in the successPSCell-Config if configured by the source PSCell before executing the last reconfiguration with sync for the SCG; or1> if sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is configured and if the T312 associated to the measurement identity of the target PSCell was running at the time of initiating the execution of the reconfiguration with sync procedure for the SCG and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312-SCG included in the successPSCell-Config if configured by the source PSCell before executing the last reconfiguration with sync for the SCG:1> if sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is not configured and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync for the SCG, is greater than thresholdPercentageT310-SCG included in the successPSCell-Config if configured by the PCell before executing the last reconfiguration with sync for the SCG; or1> if sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is not configured and if the T312 associated to any measurement identity in a measConfig associated with the SCG was running at the time of initiating the execution of the reconfiguration with sync procedure for the SCG and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312-SCG included in the successPSCell-Config if configured by the PCell before executing the last reconfiguration with sync for the SCG:2> clear the information included in VarSuccessPSCell-Report, if any;2> store the successful PSCell change or addition information in VarSuccessPSCell-Report and determine the content in VarSuccessPSCell-Report as follows:<various steps of logging SPR>3> if triggering threshold for storing the successful PSCell change or addition information in VarSuccessPSCell-Report based on the thresholdPercentageT312-SCG is met:4> set t312-cause in spr-Cause to true;<various steps of logging SPR>1> release successPSCell-Config configured by the source PSCell if available and thresholdPercentageT304 if configured by the target PSCellIn an embodiment, when the gNB retrieves the SPR, the gNB forwards the SPR to the MN which may be the source MN for the PSCellChange or PSCellAddition. The MN sends the SPR to the SN for optimising the T312 thresholds. The SN identifies that T312 may be running while MN initiated PSCell Change was running and the SN optimises the T312 value of all the measurement objects along with other parameters such as various offsets, thresholds and time to trigger used for mobility, according to the embodiment. In the manner, the embodiment allows for the optimization of T312 for all measurement objects in the SCG which has caused a near failure. The embodiment allows for a wider optimization.FIG. 5 is a flow diagram that illustrates Network node configuring the T312 thresholds, according to embodiments as disclosed herein.At step 501, a decision to configure SPR occursAt step 502, the network node determines whether the Network node is operating as SN for the UE (101) or whether the Network node is operating as MN for the UE (101) and whether the Network node is including sn-Initiated PSCellChange in the RRCReconfiguration message.At step 503, when the determination a(t step 502) is YES, the Network node includes the T312 threshold in the SPR configuration.At step 504, when the determination (at step 502) is NO, the network node does not include the T312 threshold in the SPR configuration.In an embodiment, network node such as the gNB avoids including T312 threshold for determining SPR for MN initiated PSCellChange.In an embodiment, the network node configures the T312 threshold in the successPSCell-Config when the successPSCell-Config is configured by the PSCell, and the network node does not include T312 threshold in the successPSCell-Config when the successPSCell-Config is configured by the PCell. While configuring SPR configuration, the network node determines whether the network node is operating as master node or secondary node and the network node includes T312 threshold in the SPR configuration when the network node is operating as a secondary node.In an embodiment, while including SPR configuration, network node operating as master node, the network node includes T312 threshold in the SPR configuration when the network node is including the SPR configuration configured by the PSCell, and the network node may not include T312 threshold in the SPR configuration when the network node is including the SPR configuration configured by the PCell.In an embodiment, while including SPR configuration, the gNB operating as master node, the gNB includes the T312 threshold in the SPR configuration only when the gNB includes sn-initiatedPSCellChange in other configuration such as OtherConfig information element in NR TS 38.331.Further, the network based embodiments provide a simpler solution compared to the UE (101) based methods. The network based embodiments reduce the actions required for the determination of SPR based on the T312 thresholds to the SPR configuration configured by the PCell avoiding the detailed interaction between MN and SN and decision making involved in determining SPR thresholds at the MN, the network based embodiments reduce the overall scope of optimization in SN.In an embodiment, according to TS 38.331, thresholdPercentageT312-SCG field indicates the threshold for the ratio in percentage between the elapsed T312 timer associated to the measurement identity of the target PSCell and the configured value of the T312 timer. Value p20 corresponds to 20%, value p40 corresponds to 40% and so on. The thresholdPercentageT312-SCG field is set in the otherConfig configured by the source PSCell of the PSCell change or CPC, or in the otherConfig configured by the PCell for the PSCell change or CPC to provide the successful PSCell change or addition information configured by the PSCell. The thresholdPercentageT312-SCG field is not configured at the time of PSCell change via SRB3.In an embodiment, according to TS 38.331, thresholdPercentageT312-SCG field indicates the threshold for the ratio in percentage between the elapsed T312 timer associated to the measurement identity of the target PSCell and the configured value of the T312 timer. Value p20 corresponds to 20%, value p40 corresponds to 40% and so on. The thresholdPercentageT312-SCG field is set in the otherConfig configured by the source PSCell of the PSCell change or CPC. The thresholdPercentageT312-SCG field is not configured at the time of PSCell change via SRB3.In an embodiment, according to TS 38.331, thresholdPercentageT312-SCG field indicates the threshold for the ratio in percentage between the elapsed T312 timer associated to the measurement identity of the target PSCell and the configured value of the T312 timer. The value p20 corresponds to 20%, value p40 corresponds to 40% and so on. The thresholdPercentageT312-SCG field is set in the SPR configuration configured by the source PSCell of the PSCell change or CPC. The thresholdPercentageT312-SCG field is not configured at the time of PSCell change via SRB3.FIG. 6 is a flow diagram that illustrates the UE (101) performing measurements for conditional LTM, according to embodiments as disclosed herein.At step 601, the UE (101) receives measurement configuration and LTM configuration including the Layer3 execution conditions for the conditional LTM.At step 602, the UE (101) performs measurements for the conditional LTM for the measurement identifier when the report type for the associated report configuration is conditional trigger configuration and when the measurement identifier is within the MCG VarMeasConfig and when the measurement identifier is indicated in a conditional LTM execution condition associated with the PCell. This restricts the MCG measurements to the most necessary ones, thereby saving UE (101) power,processing etc.At step 603, the UE (101) performs measurements for the conditional LTM for the measurement identifier when the report type for the associated report configuration is conditional trigger configuration and when the measurement identifier is within the SCG VarMeasConfig and when the measurement identifier is indicated in a conditional LTM execution condition associated with the PSCell. This restricts the SCG measurements to the most necessary ones, thereby saving UE (101) power,processing etc.In an embodiment, the UE (101) performs measurements for conditional Layer-1 / Layer-2 Triggered Mobility (LTM) the MCG for the measurement identifier when the report configuration associated with the measurement identifier is configured for the MCG and when the measurement identifier is indicated in the conditional LTM configuration associated with the PCell. This restricts the MCG measurements to the most necessary ones, thereby saving UE power,processing etc.In an embodiment, the UE (101) performs measurements for conditional LTM for the SCG for the measurement identifier when a report configuration associated with the measurement identifier is configured for the SCG and when the measurement identifier is indicated in the conditional LTM configuration associated with the PSCell. This restricts the SCG measurements to the most necessary ones, thereby saving the UE (101) power,processing etc.In an embodiment, according to TS 38.3311> for each measId included in the measIdList within VarMeasConfig:2> if the reportType for the associated reportConfig is condTriggerConfig, the measId is within the MCG VarMeasConfig and is indicated in a CLTM-ExecutionConditions IE associated with the PCell; or2> if the reportType for the associated reportConfig is condTriggerConfig, the measId is within the SCG VarMeasConfig and is indicated in a CLTM-ExecutionConditions IE associated with the PSCell:3> if a measurement gap configuration is setup, or3> if the UE does not require measurement gaps to perform the concerned measurements:4> if s-MeasureConfig is not configured, or4> if s-MeasureConfig is set to ssb-RSRP and the NR SpCell RSRP based on SS / PBCH block, after layer 3 filtering, is lower than ssb-RSRP, or4> if s-MeasureConfig is set to csi-RSRP and the NR SpCell RSRP based on CSI-RS, after layer 3 filtering, is lower than csi-RSRP:5> if the measObject is associated to NR and the rsType is set to csi-rs:6> if reportQuantityRS-Indexes and maxNrofRS-IndexesToReport for the associated reportConfig are configured:7> derive layer 3 filtered beam measurements only based on CSI-RS for each measurement quantity indicated in reportQuantityRS-Indexes, as described in 5.5.3.3a;6> derive cell measurement results based on CSI-RS for the trigger quantity and each measurement quantity indicated in reportQuantityCell using parameters from the associated measObject, as described in 5.5.3.3;5> if the measObject is associated to NR and the rsType is set to ssb:6> if reportQuantityRS-Indexes and maxNrofRS-IndexesToReport for the associated reportConfig are configured:7> derive layer 3 beam measurements only based on SS / PBCH block for each measurement quantity indicated in reportQuantityRS-Indexes, as described in 5.5.3.3a;6> derive cell measurement results based on SS / PBCH block for the trigger quantity and each measurement quantity indicated in reportQuantityCell using parameters from the associated measObject, as described in 5.5.3.3;5> if the measObject is associated to E-UTRA:6> perform the corresponding measurements associated to neighbouring cells on the frequencies indicated in the concerned measObject, as described in 5.5.3.2;5> if the measObject is associated to UTRA-FDD:6> perform the corresponding measurements associated to neighbouring cells on the frequencies indicated in the concerned measObject, as described in 5.5.3.2;5> if the measObject is associated to L2 U2N Relay UE:6> perform the corresponding measurements associated to candidate Relay UEs on the frequencies indicated in the concerned measObject, as described in 5.5.3.4;4> if the measRSSI-ReportConfig is configured in the associated reportConfig:5> perform the RSSI and channel occupancy measurements on the frequency configured by rmtc-Frequency in the associated measObject;NOTE 0: The network avoids configuring UEs supporting only CHO and / or Rel-16 CPC with measurements not referred to by any execution condition.In an embodiment, the UE (101) checks whether the measurement identifier related to Layer 3 conditions for conditional LTM is fulfilled for a neighbour cell and whether a Physical Cell Identity (PCI) and a frequency of the neighbour cell are the same as a PCI and a frequency of the LTM candidate cell, and upon the PCI and the frequency being the same, the UE (101) considers that the Layer 3 conditions are fulfilled for the LTM candidate cell.In an embodiment, a Radio Access Network (RAN) node such as a gNodeB (gNB) informs the UE (101) whether conditional LTM is applicable for a LTM candidate. The UE (101) receives the LTM candidate configuration for the LTM candidate, and in the LTM candidate configuration, an information element is provided for informing the UE (101) whether conditional LTM is applicable for the LTM candidate. In an embodiment, the information element is a flag or an enumerated value. Upon the information element being present in the LTM candidate configuration, conditional LTM is applicable for the LTM candidate and the UE (101) performs measurements for the conditional LTM and evaluations for the conditional LTM for the LTM candidate cell. In an embodiment, upon the information element being set to a specific value, conditional LTM is applicable for the LTM candidate and the UE (101) performs measurements for the conditional LTM and evaluations for the conditional LTM for the LTM candidate cell.In an embodiment, a presence of conditional LTM execution conditions, including cltm-ExecutionConditions, is used for determining whether conditional LTM is applicable for the LTM candidate and the UE (101) performs measurements for the conditional LTM and evaluations for the conditional LTM for the LTM candidate cell. Upon the conditional LTM execution conditions being present in the LTM candidate configuration of the LTM candidate, the UE (101) considers that conditional LTM is applicable for the LTM candidate and the UE (101) performs measurements for the conditional LTM and evaluations for the conditional LTM for the LTM candidate cell.Further, the UE (101) uses LTM conditions associated with a Primary Cell (PCell) for determining whether conditional LTM is applicable for the LTM candidate and for performing measurements for the conditional LTM and evaluations for the conditional LTM for the LTM candidate cell.FIG. 7 is a flow diagram that illustrates a scenario for determining fulfilment of entry conditions for conditional Layer-1 / Layer-2 Triggered Mobility (LTM), according to embodiments as disclosed herein.At step 701, the UE (101) receives the LTM configuration including the Layer 3 execution conditions for conditional LTM. The LTM configuration includes execution-related information for determining applicability of conditional LTM.At step 702, the UE (101) performs measurements in accordance with the LTM configuration. The measurements include Layer 3 filtered measurement results for cells associated with the LTM candidate identifier.At step 703, the UE (101) determines that one or more entry conditions applicable for an event are fulfilled when the PCI and a frequency associated with the LTM candidate identifier satisfy the entry condition or the entry conditions for all measurements, after Layer 3 filtering, taken during a corresponding timeToTrigger duration.At step 704, the UE (101) considers the entry condition or the entry conditions applicable for the event as fulfilled upon the determination in step 703 satisfied.In an embodiment, the UE (101) checks whether the measurement identifier related to Layer 3 conditional LTM and entry conditions for conditional LTM are fulfilled for a neighbour cell and whether the PCI and the frequency of the neighbour cell are the same as a PCI and a frequency of the LTM candidate cell, and upon the PCI and the frequency being the same, the UE (101) considers that the entry conditions are fulfilled for the LTM candidate cell.FIG. 8 is a flow diagram that illustrates a scenario for determining fulfilment of leaving conditions for conditional Layer-1 / Layer-2 Triggered Mobility (LTM), according to embodiments as disclosed here.At step 801, the UE (101) receives the LTM configuration including the Layer 3 execution conditions for conditional LTM.At step 802, the UE (101) performs measurements in accordance with the LTM configuration.At step 803, the UE (101) determines that one or more leaving conditions applicable for an event are fulfilled for the PCI and the frequency associated with the LTM candidate identifier for all measurements, after Layer 3 filtering, taken during a corresponding timeToTrigger duration.At step 804, the UE (101) considers the leaving conditions applicable for the event as fulfilled.In an embodiment, the UE (101) checks whether the measurement identifier related to Layer 3 conditional LTM and leaving conditions for conditional LTM are fulfilled for a neighbour cell and whether the PCI and the frequency of the neighbour cell are the same as the PCI and the frequency of the LTM candidate cell, and upon the PCI and the frequency being the same, the UE (101) considers that the leaving conditions are fulfilled for the LTM candidate cell.In an embodiment, in New Radio (NR), the frequency is represented as an NR-ARFCN.In an embodiment, the UE (101) checks whether the measurement identifier related to Layer 3 conditions for conditional LTM is fulfilled for the neighbour cell and whether a PCI and the NR-ARFCN of the neighbour cell are the same as the PCI and the frequency of the LTM candidate cell, and upon the PCI and the NR-ARFCN being the same, the UE (101) considers that the conditions are fulfilled for the LTM candidate cell.In an embodiment, the UE (101) checks whether the measurement identifier related to Layer 3 conditional LTM and entry conditions for conditional LTM are fulfilled for a neighbour cell and whether the PCI and an NR-ARFCN of the neighbour cell are the same as the PCI and the frequency of the LTM candidate cell, and upon the PCI and the NR-ARFCN being the same, the UE (101) considers that the entry conditions are fulfilled for the LTM candidate cell.In an embodiment, the UE (101) checks whether the measurement identifier related to Layer 3 conditional LTM and leaving conditions for conditional LTM are fulfilled for the neighbour cell and whether the PCI and an NR-ARFCN of the neighbour cell are the same as the PCI and the frequency of the LTM candidate cell, and upon the PCI and the NR-ARFCN being the same, the UE (101) considers that the leaving conditions are fulfilled for the LTM candidate cell.In an embodiment according to TS 38.331, the following are the LTM cell switch conditions evaluation based on L3 measurements. The UE shall:1> if the CLTM-ExecutionConditions IE is part of an RRCReconfiguration message received via SRB1, but not within mrdc-SecondaryCellGroup or ltm-ConfigSCG:2> for each entry within the CLTM-ExecutionConditions IE associated with the MCG which has the field l3-Conditions configured:3> for each measID indicated in the field l3-Conditions which has a corresponding measID in the VarMeasConfig associated with the MCG measConfig:4> if the condEventId related to this measID is associated with condEventA3 or condEventA5, and if the entry condition(s) applicable for this event is fulfilled for the ltm-CandidatePCI and NR-ARFCN related to the ltm-CandidateId for all measurements after layer 3 filtering taken during the corresponding timeToTrigger defined for this event:5> consider the event associated to this measId to be fulfilled for the ltm-CandidateId associated to the measId;4> if the condEventId related to this measID is associated with condEventA3 or condEventA5, and if the leaving condition(s) applicable for this event is fulfilled for the ltm-CandidatePCI and NR-ARFCN related to the ltm-CandidateId for all measurements after layer 3 filtering taken during the corresponding timeToTrigger defined for this event:5> consider the event associated to this measId to be not fulfilled for the ltm-CandidateId associated to the measId;1> else if the CLTM-ExecutionConditions IE is part of an RRCReconfiguration message received via SRB1 (within mrdc-SecondaryCellGroup or ltm-ConfigSCG) or within an RRCReconfiguration message received via SRB3:2> for each entry within the CLTM-ExecutionConditions IE associated with the SCG which has the field l3-Conditions configured:3> for each measID indicated in the field l3-Conditions which has a corresponding measID in the VarMeasConfig associated with the SCG measConfig:4> if the condEventId related to this measID is associated with condEventA3 or condEventA5, and if the entry condition(s) applicable for this event is fulfilled for the ltm-CandidatePCI and NR-ARFCN related to the ltm-CandidateId for all measurements after layer 3 filtering taken during the corresponding timeToTrigger defined for this event:5> consider the event associated to this measId to be fulfilled for the ltm-CandidateId associated to the measId;4> if the condEventId related to this measID is associated with condEventA3 or condEventA5, and if the leaving condition(s) applicable for this event is fulfilled for the ltm-CandidatePCI and NR-ARFCN related to the ltm-CandidateId for all measurements after layer 3 filtering taken during the corresponding timeToTrigger defined for this event:5> consider the event associated to this measId to be not fulfilled for the ltm-CandidateId associated to the measId;1> if event(s) associated to all measId(s) for a ltm-CandidateId within the CLTM-ExecutionConditions IE are fulfilled:2> perform the LTM cell switch procedure for the LTM candidate configuration associated to the ltm-CandidateId according to the actions specified in 5.3.5.18.6.In NR, the frequency may be represented as a NR-Absolute Radio Frequency Channel Number (NR-ARFCN) and a subcarrier spacing (SCS).In an embodiment, the UE (101) checks whether the measurement identifier related to Layer 3 conditions for conditional LTM is fulfilled for a neighbour cell and whether a Physical Cell Identity (PCI), a NR-ARFCN, and a SCS, when available, of the neighbour cell are the same as the PCI and the frequency of a LTM candidate cell, and upon the PCI, the NR-ARFCN, and the SCS being the same, the UE (101) considers that the conditions are fulfilled for the LTM candidate cell.In an embodiment, the UE (101) checks whether the measurement identifier related to Layer 3 conditional LTM and entry conditions for conditional LTM are fulfilled for a neighbour cell and whether the PCI, the NR-ARFCN, and the SCS, when available, of the neighbour cell are the same as the PCI and the frequency of the LTM candidate cell, and upon the PCI, the NR-ARFCN, and the SCS being the same, the UE (101) considers that the entry conditions are fulfilled for the LTM candidate cell.In an embodiment, the UE (101) checks whether the measurement identifier related to Layer 3 conditional LTM and leaving conditions for conditional LTM are fulfilled for a neighbour cell and whether the PCI, the NR-ARFCN, and the SCS, when available, of the neighbour cell are the same as the PCI and the frequency of the LTM candidate cell, and upon the PCI, the NR-ARFCN, and the SCS being the same, the UE (101) considers that the leaving conditions are fulfilled for the LTM candidate cell.In an embodiment according to TS 38.331, the following are the LTM cell switch conditions evaluation based on L3 measurements.The UE shall:1> if the CLTM-ExecutionConditions IE is part of an RRCReconfiguration message received via SRB1, but not within mrdc-SecondaryCellGroup or ltm-ConfigSCG:2> for each entry within the CLTM-ExecutionConditions IE associated with the MCG which has the field l3-Conditions configured:3> for each measID indicated in the field l3-Conditions which has a corresponding measID in the VarMeasConfig associated with the MCG measConfig:4> if the condEventId related to this measID is associated with condEventA3 or condEventA5, and if the entry condition(s) applicable for this event is fulfilled for the ltm-CandidatePCI and NR-ARFCN and SCS related to the ltm-CandidateId for all measurements after layer 3 filtering taken during the corresponding timeToTrigger defined for this event:5> consider the event associated to this measId to be fulfilled for the ltm-CandidateId associated to the measId;4> if the condEventId related to this measID is associated with condEventA3 or condEventA5, and if the leaving condition(s) applicable for this event is fulfilled for the ltm-CandidatePCI and NR-ARFCN and SCS related to the ltm-CandidateId for all measurements after layer 3 filtering taken during the corresponding timeToTrigger defined for this event:5> consider the event associated to this measId to be not fulfilled for the ltm-CandidateId associated to the measId;1> else if the CLTM-ExecutionConditions IE is part of an RRCReconfiguration message received via SRB1 (within mrdc-SecondaryCellGroup or ltm-ConfigSCG) or within an RRCReconfiguration message received via SRB3:2> for each entry within the CLTM-ExecutionConditions IE associated with the SCG which has the field l3-Conditions configured:3> for each measID indicated in the field l3-Conditions which has a corresponding measID in the VarMeasConfig associated with the SCG measConfig:4> if the condEventId related to this measID is associated with condEventA3 or condEventA5, and if the entry condition(s) applicable for this event is fulfilled for the ltm-CandidatePCI and NR-ARFCN and SCS related to the ltm-CandidateId for all measurements after layer 3 filtering taken during the corresponding timeToTrigger defined for this event:5> consider the event associated to this measId to be fulfilled for the ltm-CandidateId associated to the measId;4> if the condEventId related to this measID is associated with condEventA3 or condEventA5, and if the leaving condition(s) applicable for this event is fulfilled for the ltm-CandidatePCI and NR-ARFCN and SCS related to the ltm-CandidateId for all measurements after layer 3 filtering taken during the corresponding timeToTrigger defined for this event:5> consider the event associated to this measId to be not fulfilled for the ltm-CandidateId associated to the measId;1> if event(s) associated to all measId(s) for a ltm-CandidateId within the CLTM-ExecutionConditions IE are fulfilled:2> perform the LTM cell switch procedure for the LTM candidate configuration associated to the ltm-CandidateId according to the actions specified in 5.3.5.18.6.FIG. 9 is a flow diagram that illustrates a scenario for the UE (101) logging a SuccessPSCell Report (SPR) based on T312 thresholds for a Secondary Node (SN) initiated PSCell change, according to embodiments as disclosed herein.At step 901, the UE (101) detects the successful PSCell change associated with a SN-initiated PSCell change procedure.At step 902, the UE (101) determines whether the SN-initiated PSCell change associated with a last applied RRC reconfiguration including a reconfiguration-with-sync for the Secondary Cell Group (SCG) is configured, whether a timer T312 associated with any measurement identity in a measurement configuration associated with the SCG was running at initiation of the execution of the reconfiguration-with-sync procedure for the SCG, and whether a ratio between an elapsed time of the timer T312 and a configured value of the timer T312, configured while the UE (101) was connected to a source PSCell before executing the last reconfiguration-with-sync, is greater than a thresholdPercentageT312-SCG included in a successPSCell-Config configured by the PSCell before executing the last reconfiguration-with-sync for the SCG.At step 903, upon the ratio being greater than the thresholdPercentageT312-SCG, the UE (101) logs the SuccessPSCell Report (SPR) and sets a T312-related cause in an SPR cause field to true in the SPR.At step 904, upon the ratio not being greater than the thresholdPercentageT312-SCG, the UE (101) does not log the SuccessPSCell Report (SPR) based on a T312 threshold and does not set the T312-related cause in the SPR cause field to true.In an embodiment, during execution of theSN initiated PSCell change procedure, the UE (101) is configured with the T312 threshold by an SN. When the timer T312 associated with the measurement object corresponding to the PSCell associated with an SCG is running at initiation of the SN initiated PSCell change procedure, and when the ratio between an elapsed value of the timer T312 and a configured value of the timer T312 is greater than the T312 threshold configured by the SN, the UE (101) logs SPR information and logs that the SPR is caused due to the T312 cause.In this embodiment, the UE (101) determines whether to log SPR for the SN initiated PSCell change based on the T312 threshold configured by the PSCell and based on the timer T312 configured in a measurement object associated with the SCG for a target frequency. When the timer T312 configured in the measurement object for the target frequency associated with an MCG is running and the timer T312 configured in the measurement object for the target frequency associated with the SCG is not running, the UE (101) does not log SPR based on the T312 threshold.In an embodiment, the following are the actions for the successful PSCell change or addition report determination. The UE (101) shall for the PSCell:1> if the ratio between the value of the elapsed time of the timer T304 and the configured value of the timer T304, included in the last applied RRCReconfiguration message for the SCG including the reconfigurationWithSync, is greater than thresholdPercentageT304-SCG if included in the successPSCell-Config received before executing the last reconfiguration with sync for the SCG; or1> if sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is configured and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync for the SCG, is greater than thresholdPercentageT310-SCG included in the successPSCell-Config if configured by the source PSCell before executing the last reconfiguration with sync for the SCG; or1> if sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is configured and if the T312 associated to the measurement identity of the target PSCell included in a measConfig associated with the SCG was running at the time of initiating the execution of the reconfiguration with sync procedure for the SCG and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312-SCG included in the successPSCell-Config if configured by the source PSCell before executing the last reconfiguration with sync for the SCG:1> if sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is not configured and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync for the SCG, is greater than thresholdPercentageT310-SCG included in the successPSCell-Config if configured by the PCell before executing the last reconfiguration with sync for the SCG; or1> if sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is not configured and if the T312 associated to the measurement identity of the target PSCell included in a measConfig associated with the SCG was running at the time of initiating the execution of the reconfiguration with sync procedure for the SCG and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312-SCG included in the successPSCell-Config if configured by the PCell before executing the last reconfiguration with sync for the SCG:2> clear the information included in VarSuccessPSCell-Report, if any;2> store the successful PSCell change or addition information in VarSuccessPSCell-Report and determine the content in VarSuccessPSCell-Report as follows:<various steps of logging SPR>3> if triggering threshold for storing the successful PSCell change or addition information in VarSuccessPSCell-Report based on the thresholdPercentageT312-SCG is met:4> set t312-cause in spr-Cause to true;<various steps of logging SPR>1> release successPSCell-Config configured by the source PSCell if available and thresholdPercentageT304 if configured by the target PSCellIn an embodiment, the UE (101) and a Radio Access Network (RAN) node associate LTM configuration information received in ltm-ConfigSCG with an MCG. In an embodiment, the UE (101) maintains LTM configuration information received in ltm-Config and ltm-ConfigSCG within an RRCReconfiguration message received via SRB1 independently from ltm-Config included within an RRCReconfiguration message received via SRB3 or, alternatively, embedded within an RRCReconfiguration message received via SRB1.In an embodiment, the UE (101) maintains two independent VarLTM-ServingCellNoResetID and two independent VarLTM-ServingCellUE-MeasuredTA-ID, and executes LTM-related procedures independently for LTM configuration information received in ltm-Config and ltm-ConfigSCG within an RRCReconfiguration message received via SRB1 and for ltm-Config included within an RRCReconfiguration message received via SRB3 or, alternatively, embedded within an RRCReconfiguration message received via SRB1.In an embodiment, the network configures the UE with one or more LTM candidate configurations within the LTM-Config IE.In NR-DC, the UE may receive two independent ltm-Config:- an ltm-Config associated with the MCG that is included in ltm-Config or ltm-ConfigSCG within an RRCReconfiguration message received via SRB1; and- an ltm-Config associated with the SCG that is included within an RRCReconfiguration message either received via SRB3, or, alternatively, embedded in an RRCReconfiguration message received via SRB1.In case the UE receives two independent ltm-Config:- the UE maintains two independent ltm-Config;- the UE maintains two independent VarLTM-ServingCellNoResetID, one associated with each ltm-Config;- the UE maintains two independent VarLTM-ServingCellUE-MeasuredTA-ID, one associated with each ltm-Config;- the UE independently performs all the procedures in clause 5.3.5.18 for each ltm-Config and the associated VarLTM-ServingCellNoResetID and VarLTM-ServingCellUE-MeasuredTA-ID unless explicitly stated otherwise.In an embodiment, in NR, while performing LTM cell switch triggered on SCG, the UE, releases / clears current dedicated configurations associated with MCG if the applied LTM configuration (ltm-configSCG) is included within an RRCReconfiguration message received via SRB1.FIG. 10 is a flow diagram illustrating a scenario for executing the Secondary Cell Group (SCG) Layer-1 / Layer-2 Triggered Mobility (LTM) cell switch, according to embodiments as disclosed herein.At step 1001, dual connectivity is established by the UE (101), enabling operation with both the MCG and the SCG.At step 1002, the UE (101) receives LTM configuration information within ltm-ConfigSCG for the SCG, the configuration being delivered in an RRCReconfiguration message.At step 1003, an SCG LTM cell switch is executed based on the LTM configuration information received for the SCG.At step 1004, in response to executing the SCG LTM cell switch, the UE releases or clears dedicated configuration information associated with the MCG, except for predefined specific configurations. The UE applies default values for timers T310, N310, and N311 associated with the SCG, and applies default values for timers T310, N310, T311, and N311 associated with the MCG. The UE further applies a default Medium Access Control (MAC) Cell Group configuration for both the MCG and SCG as specified in Section 9.2.2.In an embodiment, when an ltm-Config (ltm-ConfigSCG) related to the LTM cell switch is included within an RRCReconfiguration message received via SRB1, and when the LTM cell switch is triggered on the SCG, the UE (101) applies the default MAC Cell Group configuration for the MCG and the SCG, such as specified in Section 9.2.2 of TS 38.331 for NR.The steps are as follows, at step 1, the UE (101) is configured for dual connectivity and has a PSCell. At step 2, the UE(101) receives LTM configuration for SCG LTM, where the LTM configuration is received in MN format, i.e., the LTM configuration (ltm-ConfigSCG) is associated with the MCG or is received within an RRCReconfiguration message received via SRB1 in NR. The order of step 1 and step 2 is interchangeable. Atstep S3, the UE (101) performs an LTM cell switch triggered on the SCG. At step S4, the UE (101) applies the default MAC Cell Group configuration for the MCG and the SCG while performing the LTM cell switch.In an embodiment, in NR, when the ltm-Config (ltm-ConfigSCG) related to the LTM cell switch is included within an RRCReconfiguration message received via SRB1, and when the LTM cell switch is triggered on the SCG, the UE applies the default values for timers T310 and T311 and constants N310 and N311 associated with the MCG, and applies the default values for timer T310 and constants N310 and N311 associated with the SCG.Further, the steps are as follows, at step 1, the UE (101) is configured for dual connectivity and has the PSCell. At step 2, the UE (101) receives LTM configuration for SCG LTM (ltm-ConfigSCG). The LTM configuration is received in MN format, i.e., the LTM configuration is associated with the MCG or is received within an RRCReconfiguration message received via SRB1 in NR. The order of step 1 and step 2 is interchangeable.At step 3, the UE (101) performs the LTM cell switch triggered on the SCG. At step 4, the UE (101) applies the default values for timers T310 and T311 and constants N310 and N311 associated with the MCG, and applies the default values for timer T310 and constants N310 and N311 associated with the SCG upon performing the LTM cell switch.In an embodiment, upon the indication by lower layers that the LTM cell switch procedure is triggered, or upon performing LTM cell switch following cell selection performed while timer T311 was running, as specified in 5.3.7.3, the UE (101) shall:1> if the LTM cell switch is triggered on the MCG:<different steps for LTM cell switch triggered on MCG >1> else, if the LTM cell switch is triggered on the SCG:2> release / clear all current dedicated and common radio configurations which have been received either via SRB1 within mrdc-SecondaryCellGroup, or via SRB3 except for the following:- the radio bearer configuration (configured via RadioBearerConfig IE)- the logicalChannelIdentity and logicalChannelIdentityExt of RLC bearers configured in RLC-BearerConfig and the associated RLC entities, their state variables, buffers, and timers, except for triggering the associated RLC entities to reset the variable RETX_COUNT its initial value, as specified in TS 38.322 [4];- the bh-LogicalChannelIdentity of BH RLC channels configured in BH-RLC-ChannelConfig and the associated RLC entities, their state variables, buffers, and timers, except for triggering the associated RLC entities to reset the variable RETX_COUNT its initial value, as specified in TS 38.322 [4];- the UE variables VarLTM-ServingCellNoResetID and VarLTM-ServingCellUE-MeasuredTA-ID;- the ltm-Config;- the AS security configurations associated with the secondary key;2> use the default values specified in 9.2.3 for timers T310 and constants N310, N311 associated with SCG.2> if the LTM configuration is received in ltm-ConfigSCG3> release / clear all current dedicated and common radio configurations which have neither been received via SRB1 within mrdc-SecondaryCellGroup, nor via SRB3 except for the following:- the radio bearer configuration (configured via RadioBearerConfig)- the logicalChannelIdentity and logicalChannelIdentityExt of RLC bearers configured in RLC-BearerConfig and the associated RLC entities, their state variables, buffers, and timers, except for triggering the associated RLC entities to reset the variable RETX_COUNT its initial value, as specified in TS 38.322 [4];- the bh-LogicalChannelIdentity of BH RLC channels configured in BH-RLC-ChannelConfig and the associated RLC entities, their state variables, buffers, and timers, except for triggering the associated RLC entities to reset the variable RETX_COUNT its initial value, as specified in TS 38.322 [4];- the UE variables VarLTM-ServingCellNoResetID and VarLTM-ServingCellUE-MeasuredTA-ID;- the ltm-Config;- the MCG C-RNTI;- the AS security configurations associated with the master key;- the logged measurement configuration;- the ServingCellConfigCommon of the PCell.Embodiments of the invention provide a technical advantage by ensuring that logging of the SuccessPSCell Report (SPR) for the PSCell change is performed based on the T312 timer associated with a Secondary Cell Group (SCG), rather than any T312 timer associated with the MCG. This eliminates incorrect SPR logging in scenarios where the T312 timer running on the MCG does not reflect the failure risk on the SCG. By evaluating the elapsed value of the T312 timer configured for the SCG together with the T312 threshold configured by the MCG, the UE (101) is able to accurately detect near-failure conditions for SCG-based mobility, resulting in improved reliability of dual-connectivity mobility reporting and preventing false near-failure reports. This enables more accurate mobility robustness optimization, reduces unnecessary mobility-related signalling, and improves network diagnostics and performance for dual-connectivity systems.Embodiments of the invention further provide a technical advantage by enabling the UE (101) to distinguish between measurement configurations originating from the MCG and the SCG and to base SPR logging exclusively on the T312 timer that reflects the behaviour of the target PSCell within the SCG. This prevents the UE (101) from relying on T312 values associated with the MCG, which may be unrelated to the PSCell change condition. As a result, the UE (101) performs selective and context-accurate failure-risk assessment for SCG mobility events. This selective evaluation enhances the precision of near-failure detection, minimizes false positives associated with MCG-based measurement objects, and increases the fidelity of MDT and SON analytics by ensuring that only mobility events relevant to SCG are logged. This improves overall system robustness and enables more efficient network optimization for multi-cell dual-connectivity environments. Further combining the T312 value associated with the SCG with the threshold from MCG or SCG based on the node that initiates the PSCellChange avoids the network implementation complexity of exchanging the threshold values, while keeping the robustness of near failure detection of PSCellChange intact.Embodiments of the present invention provide a method for managing near-failure events during dual connectivity in a wireless communication network system. The method includes determining, by a User Equipment (UE) (101), whether a Secondary Cell Group (SCG) reconfiguration with synchronization (reconfigurationWithSync) procedure is initiated by the source Primary SCG Cell (PSCell) or PCell. Further, the method includes determining timer T312 included in a measurement configuration of associated with the SCG. Further, the method includes determining, by the UE (101), that a ratio of an elapsed value of the timer T312 to a configured value of the timer T312 exceeds a threshold value for logging a successful PSCell change or addition, when the timer T312 is running at the time of initiating the reconfigurationWithSync procedure for the SCG and the threshold is configured by PSCell when the PSCellChange is SN initiated and the threshold is configured by PCell when the PSCellChange is not SN initiated. i.e. the UE uses T312 value from SCG and T312 threshold from MCG for SPR determination for MN initiated PSCellChange and both T312 and T312 thresholds from SCG for SPR determination for SN initiated PSCellChange. Further, the method includes logging successful PSCell change or addition information, when the ratio exceeds the threshold value.In an exemplary embodiment, the UE (101) may operate in a multi-connectivity configuration such as E-UTRA-NR Dual Connectivity (EN-DC), NR-NR Dual Connectivity (NR-DC), or NR-E-UTRA Dual Connectivity (NE-DC), where the UE (101) maintains simultaneous connections with the MN providing the MCG and the SN providing a Secondary Cell Group (SCG). When the UE (101) is connected to the source Primary SCG Cell (PSCell) and experiences deteriorating radio link quality, timer T312 begins running as part of the measurement configuration associated with the SCG. During this near-failure condition, the source PSCell initiates an SCG reconfiguration with synchronization (reconfigurationWithSync) procedure to transition the UE (101) to the target PSCell. The near-failure event optimization controller (105) determines that timer T312 is running at the time of initiating the reconfigurationWithSync procedure and calculates the ratio of the elapsed value of timer T312 to its configured value (e.g., 800ms elapsed out of 1000ms configured equals 0.8 or 80%).The near-failure event optimisation controller (105) compares the calculated ratio against a threshold value (e.g., 50%, 70%, or 80%) that is configured by the network in a success PSCell configuration, which may be provided by either the PCell of the MCG or the source PSCell depending on which entity initiated the reconfiguration. If the ratio exceeds the threshold value, indicating that the PSCell change occurred under significant radio link quality degradation conditions, the near-failure event optimisation controller (105) logs the successful PSCell change or addition information into a variable success PSCell report stored in memory (104) and sets the T312-cause indicator to identify this as a near-failure event. In multi-connectivity scenarios where multiple timer T312 instances may be running simultaneously (one configured by the MN and another by the SN), the near-failure event optimisation controller (105) identifies the applicable timer T312 based on the measurement identity of the target PSCell frequency. The logged information is subsequently reported to the network via processor (102), enabling operators to distinguish near-failure mobility events from routine handovers and optimize multi-connectivity parameters across different Radio Access Technologies and frequency bands.FIG. 11 is a block diagram of a terminal or user equipment (UE) 1100 according to an embodiment of the disclosure.The terminal is an electronic device capable of wireless communication and having various form factors, examples of the terminal may include a UE, a mobile station (MS), a cellular phone, a smartphone, a computer, a tablet, a wearable device, an Internet of Things (IoT) device, or any other device / system capable of performing wireless communication with a base station (BS) and / or another terminal through a wireless channel.Referring to FIG. 11, the UE 1100 may include at least one transceiver (hereinafter, referred to as simply "transceiver") 1101, at least one processor (hereinafter, referred to as simply "processor") 1102, and at least one memory (hereinafter, referred to as simply "memory") 1103. According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the transceiver 1101, the processor 1102, and the memory 1103 of the UE 1100 may operate. However, components of the UE 1100 are not limited to the example components illustrated in FIG. 11. In another embodiment, the UE 1100 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in some embodiments, any combination of the transceiver 1101, the processor 1102, or the memory 1103 may be integrated in the form of one component.The transceiver 1101 may be a communication circuit or communication circuitry that enables the UE 1100 to perform wireless communication with a node or an entity of a network. For example, the transceiver 1101 may enable the UE 1100 to transmit or receive a signal to or from a BS through cellular communication, or to transmit or receive a signal to or from another UE through cellular communication. For example, the transceiver 1101 may support at least one of various cellular communication technologies including 3rd generation (3G), 4th generation (4G), long term evolution (LTE), 5th generation (5G) NR, 6th generation (6G), and various cellular wireless communication technologies supported by the transceiver (1101) may include all subsequent generations of evolved wireless communications.According to an embodiment, the UE 1100 may include a plurality of transceivers. For example, in the case of supporting evolved-universal terrestrial radio access-new radio (E-UTRA-NR) dual connectivity (EN-DC), the UE 1100 may include a first transceiver supporting the 4G LTE wireless communication and a second transceiver supporting the 5G NR wireless communication. According to another embodiment, in the case of supporting NR-dual connectivity (NR-DC), the UE 1100 may include a plurality of transceivers supporting the 5G NR wireless communication. According to still another embodiment, in the case of supporting near field wireless communication, the UE 1100 may separately include a transceiver supporting at least one standard in the group of wireless communication protocol standards as defined in the protocol standards for Bluetooth®, wireless local area network (WLAN) network (including institute of electrical and electronics engineers (IEEE) 802.11-2016 standard or its amendments, e.g., 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be, without being limited thereto).According to an embodiment, the transceiver 1101 may include various circuit structures used to transmit or receive signals to or from a BS through a wireless channel. The signals may include control information and data. For example, the transceiver 1101 may include a radio frequency (RF) transmitter for up-converting and amplifying the frequency of a transmitted signal and an RF receiver for low-noise-amplifying a received signal and down-converting the frequency thereof. The transceiver 1101 may output a signal received through a wireless channel to the processor 1102 and may transmit, through a wireless channel, a signal output from the processor 1102.The processor 1102 may control general operations of the UE 1100 according to embodiments of the disclosure. The processor 1102 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processing operations. The processor 1102 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 1103, individually, collectively or in any combination thereof. Further, the processor 1102 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme.The processor 1102 may be electrically, operatively, and / or communicatively coupled to the transceiver 1101 to control the transceiver 1101.The processor 1102 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. For example, the processor 1102 may include a communication processor (CP) configured to control communication operations and an application processor (AP) configured to control execution of an upper layer (for example, an application layer). In a specific embodiment, at least a part of the processor 1102 may be included in one chip (or IC) and the other part of the processor 1102 may be included in another chip (or IC). Otherwise, at least one processor may be included in another component, for example, the transceiver 1101 or the memory 1103.The processor 1102 may perform or control or cause an operation of the UE 1100 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 1102 may control operations of the UE 1100 for processing a downlink signal received from a BS or generating and transmitting an uplink signal to a BS. To this end, the processor 1102 may execute a computer program, codes, or instructions stored in the memory 1103, so as to control other components of the UE 1100 to enable execution of various operations.The memory 1103 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 1103 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.The memory 1103 may be electrically, operatively, and / or communicatively coupled to the processor 1102 and may be accessed by the processor 1102.The memory 1103 may store a computer program, codes, or instructions executable by the processor 1102. According to an embodiment, a computer program, codes, or instructions executable by the processor 1102 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 1103, the processor 1102 may perform various functions according to an embodiment of the disclosure.According to an embodiment of the disclosure, operations of the UE 1100 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 1103 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.According to an embodiment, the UE 1100 corresponds to the UE 101 of FIG. 1.FIG. 12 is a block diagram of a base station (BS) 1200 according to an embodiment of the disclosure.The BS 1200 may perform wireless communication with at least one user equipment (UE) located within the area of the BS 1200 through a wireless channel. The BS 1200 may perform communication with a node or an entity of a network through wired or wireless communication.Referring to FIG. 12, the BS 1200 may include at least one transceiver (hereinafter, referred to as simply "transceiver") 1201, at least one processor (hereinafter, referred to as simply "processor") 1202, and at least one memory (hereinafter, referred to as simply "memory") 1203. According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the transceiver 1201, the processor 1202, and the memory 1203 of the BS 1200 may operate. However, components of the BS 1200 are not limited to the example components illustrated in FIG. 12. In another embodiment, the BS 1200 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in some embodiments, any combination of the transceiver 1201, the processor 1202, or the memory 1203 may be integrated in the form of one component.The transceiver 1201 may be a communication circuit or communication circuitry that enables the BS 1200 to perform wireless communication with a node or an entity of a network. For example, the transceiver 1201 may enable the BS 1200 to transmit or receive a signal to or from the UE X00 through cellular communication, or to transmit or receive a signal to or from another network entity through wireless communication. For example, the transceiver 1201 may support various cellular communication technologies including 3rd generation (3G), 4th generation (4G), long term evolution (LTE), 5th generation (5G) NR, 6th generation (6G), and various cellular wireless communication technologies supported by the transceiver (1201) may include all subsequent generations of evolved wireless communications.. According to an embodiment, the transceiver 1201 may include various circuit structures used to transmit or receive signals to or from a UE through a wireless channel. The signals may include control information and data. For example, the transceiver 1201 may include a radio frequency (RF) transmitter for up-converting and amplifying the frequency of a transmitted signal and an RF receiver for low-noise-amplifying a received signal and down-converting the frequency thereof. The transceiver 1201 may output a signal received through a wireless channel to the processor 1202 and may transmit, through a wireless channel, a signal output from the processor 1202.Meanwhile, according to an embodiment of the present disclosure, the BS 1200 may perform communication with a node or an entity of a network through wired or wireless communication. For example, the BS 1200 may perform wired or wireless communication with an adjacent BS, or a node or an entity of a core network through a backhaul network. Although not illustrated in FIG. 12, when the BS 1200 performs wired communication, the BS 1200 may further include a separate network interface for wired communication in addition to the transceiver 1201. The network interface may be referred to as network interface circuitry or communication interface circuitry.The processor 1202 may control general operations of the BS 1200 according to embodiments of the disclosure. The processor 1202 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processing operations. The processor 1202 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 1203, individually, collectively or in any combination thereof. Further, the processor 1202 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme.The processor 1202 may be electrically, operatively, and / or communicatively coupled to the transceiver 1201 to control the transceiver 1201.The processor 1202 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. In a specific embodiment, at least a part of the processor 1202 may be included in one chip (or IC) and the other part of the processor 1202 may be included in another chip (or IC). Otherwise, at least one processor may be included in another component, for example, the transceiver 1201 or the memory 1203.The processor 1202 may perform or control or cause an operation of the BS 1200 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 1202 may control operations of the BS 1200 for generating and transmitting a downlink signal to a UE or processing an uplink signal received from a UE. Otherwise, the BS 1200 may transmit or receive a signal to or from a neighboring BS, transfer a signal received from a UE to an upper node of the network, or transmit a signal transferred from an upper node of the network to a UE. To this end, the processor 1202 may execute a computer program, codes, or instructions stored in the memory 1203, so as to control other components of the BS 1200 to enable execution of various operations.The memory 1203 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 1203 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.The memory 1203 may be electrically, operatively, and / or communicatively coupled to the processor 1202 and may be accessed by the processor 1202.The memory 1203 may store a computer program, codes, or instructions executable by the processor 1202. According to an embodiment, a computer program, codes, or instructions executable by the processor 1202 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 1203, the processor 1202 may perform various functions according to an embodiment of the disclosure.According to an embodiment of the disclosure, operations of the BS 1200 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 1203 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.The UE or the base station may perform various communication procedures related to the control plane or the user plane by cooperating with one or more network entities based on wireless communication. For example, the UE may communicate with a network entity (for example, an Access and Mobility Management Function (AMF), a Session Management Function (SMF), rtc.) via the base station, or the base station may perform at least one communication procedure by directly transmitting and receiving signals to / from, or relaying signals between, the network entities.The structure of the above-described network entity will be described in more detail with reference to the drawings.FIG. 13 is a block diagram of a network entity 1300 according to an embodiment of the disclosure.The network entity 1300 may include an entity (apparatus, device, or server, etc.) that performs one or more network functions (NFs) or a part of a network function constituting a core network (e.g., a 5th generation (5G) core (5GC)) in a communication system. In this case, multiple NFs may be implemented within a single network entity, or a single NF may be distributed and implemented across a plurality of network entities. In addition, when an NF is implemented within the network entity, the NF may be implemented in the form of software, and in such a case, a program for operating the NF may be stored in memory of the network entity 1300.A single NF may be implemented by one or more instances, which may be deployed on the same network entity or distributed across multiple network entities to operate. The instance may be a software unit that logically executes a specific network function, and may be implemented in a form that is decoupled from physical hardware resources. Further, one or more NFs may be implemented in the form of one network slice to operate to satisfy specifications required by a particular service.The NF may include at least one of an access and mobility management function (AMF), a session management function (SMF), a local session management function (L-SMF), a user plane function (UPF), a local user plane function (L-UPF), a policy control function (PCF), a unified data management (UDM), a unified data repository (UDR), a network exposure function (NEF), a network repository function (NRF), an application function (AF), a network slice selection function (NSSF), a network data analytics function (NWDAF), a network slice admission control function (NSACF), an authentication server function (AUSF), or a data network (DN), etc.Referring to FIG. 13, the network entity 1300 may include at least one network interface 1301, at least one processor 1302 (hereinafter, "processor"), and at least one memory 1303 (hereinafter, "memory"). As described above, a NF may be implemented in the form of a physical device such as the network entity 1300, or may be virtualized and executed in the form of an instance. When implemented as an instance, the NF need not necessarily include physical components as illustrated in FIG. 13. In such a case, the instance may be logically represented as comprising one or more logical functional elements.According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the network interface 1301, the processor 1302, and the memory 1303 of the network entity 1300 may operate. However, components of the network entity 1300 are not limited to the example components illustrated in FIG. 13. In another embodiment, the network entity 1300 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in an embodiment, the network interface 1301, the processor 1302, or the memory 1303 may be integrated in the form of one component.The network interface 1301 is a collective term for a transmitter part of the network entity 1300 and a receiver part of the network entity 1300, and may be a communication circuit for transmitting or receiving a signal to or from a user equipment (UE), a base station (BS), or another network entity. Here, the communication circuit may include both a communication circuit for wireless communication and a communication circuit for a wired communication. For example, the network interface 1301 may include a circuit, logic, hardware, etc., configured to exchange a control plane message or a user plane message with a UE, a BS, or other core network entities through wireless communication or wired communication. The network interface 1301 may operate using various protocols (e.g., non-access stratum (NAS) protocol). The network interface 1301 may also be referred to, for convenience of description or depending on implementation, as communication circuitry, network interface circuitry, or a communication interface circuitry.The processor 1302 may control general operations of the network entity 1300 according to embodiments of the disclosure. The processor 1302 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processing operations. The processor 1302 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 1303, individually, collectively or in any combination thereof. Further, the processor 1302 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme. Further, it should be noted that, according to another embodiment, in a case where NF is implemented in the form of an instance, the network function may be not necessarily configured by physical hardware.According to an embodiment, the processor 1302 may be electrically, operatively, and / or communicatively coupled to the network interface 1301 to control the network interface 1301.The processor 1302 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. In a specific embodiment, at least a part of the processor 1302 may be included in one chip (or IC) and the other part of the processor 1302 may be included in another chip (or IC). Otherwise, at least one processor may be included in another component, for example, the network interface 1301 or the memory 1303.The processor 1302 may perform or control or cause an operation of the network entity 1300 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 1302 may control operations of the network entity 1300 for exchanging a control plane message or a user plane message with a UE, a BS, or other core network entities through wireless or wired communication, using various protocols (e.g., NAS protocol). To this end, the processor 1302 may execute a computer program, codes, or instructions stored in the memory 1303, so as to control other components of the network entity 1300 to enable execution of various operations.The memory 1303 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 1303 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.The memory 1303 may be electrically, operatively, and / or communicatively coupled to the processor 1302 and may be accessed by the processor 1302.The memory 1303 may store a computer program, codes, or instructions executable by the processor 1302. According to an embodiment, a computer program, codes, or instructions executable by the processor 1302 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 1303, the processor 1302 may perform various functions according to an embodiment of the disclosure.According to an embodiment of the disclosure, operations of the network entity 1300 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 1303 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.Meanwhile, although specific embodiments of the present disclosure have been described in detail, various modifications may be made without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims and equivalents thereof.

Claims

1.A method performed by a user equipment (UE), the method comprising:receiving a radio resource control (RRC) reconfiguration message including reconfiguration with sync information for a secondary cell group (SCG), wherein the RRC reconfiguration message does not include secondary node (SN)-initiated primary SCG cell (PScell) change information;initiating execution of a reconfiguration with sync procedure for the SCG;identifying whether a timer T312, associated with a measurement identity of a target PSCell and included in measurement configuration information associated with the SCG, is running at the time of initiating the execution;determining, if the timer T312 is running at the time of initiating the execution, whether a ratio between a value of elapsed time of the timer T312 and a configured value of the timer T312 is greater than a threshold value; andstoring successful PSCell change information in a successful PSCell change report based on determining that the ratio is greater than the threshold value.2.The method of claim 1,wherein the configured value of the timer T312 is configured by a source PSCell before the execution of the reconfiguration with sync procedure for the SCG.3.The method of claim 1,wherein the threshold value is configured by a primary cell (PCell).4.The method of claim 3,wherein the threshold value corresponds to a threshold percentage value of the timer T312 for the SCG included in success PSCell configuration information configured by the PCell.5.The method of claim 4, further comprising:receiving the success PSCell configuration information before the execution of the reconfiguration with sync procedure for the SCG.6.The method of claim 1,clearing any information included in the successful PSCell change report before storing the successful PSCell change information in the successful PSCell change report.7.A user equipment (UE) comprising:at least one transceiver;at least one processor communicatively coupled to the at least one transceiver; andat least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the UE to:receive a radio resource control (RRC) reconfiguration message including reconfiguration with sync information for a secondary cell group (SCG), wherein the RRC reconfiguration message does not include secondary node (SN)-initiated primary SCG cell (PScell) change information,initiate execution of a reconfiguration with sync procedure for the SCG,identify whether a timer T312, associated with a measurement identity of a target PSCell and included in measurement configuration information associated with the SCG, is running at the time of initiating the execution,determine, if the timer T312 is running at the time of initiating the execution, whether a ratio between a value of elapsed time of the timer T312 and a configured value of the timer T312 is greater than a threshold value, andstore successful PSCell change information in a successful PSCell change report based on determining that the ratio is greater than the threshold value.8.The UE of claim 7,wherein the configured value of the timer T312 is configured by a source PSCell before the execution of the reconfiguration with sync procedure for the SCG.9.The UE of claim 7,wherein the threshold value is configured by a primary cell (PCell).10.The UE of claim 9,wherein the threshold value corresponds to a threshold percentage value of the timer T312 for the SCG included in success PSCell configuration information configured by the PCell.11.The UE of claim 10, wherein the instructions, when executed by the at least one processor, further cause the UE to:receive the success PSCell configuration information before the execution of the reconfiguration with sync procedure for the SCG.12.The UE of claim 7,clearing any information included in the successful PSCell change report before storing the successful PSCell change information in the successful PSCell change report.

Images