Method and apparatus for managing interactions of LTM and CLTM with l3 mobility

By configuring UE and network nodes to manage serving cell security identifiers and perform L3-based measurements, the solution addresses challenges in LTM and CLTM interactions, enhancing mobility management and reducing latency in wireless communication networks.

WO2026240404A1PCT designated stage Publication Date: 2026-11-19SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2026/005887
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-12
Filing Date
2026-05-07
Publication Date
2026-11-19

AI Technical Summary

Technical Problem

Current wireless communication networks face challenges in managing interactions between Low-Layer Triggered Mobility (LTM) and Conditional Low-Layer Triggered Mobility (CLTM) with Layer 3 (L3) mobility, particularly in handling serving cell security identifiers during L3 mobility and performing measurements for CLTM based on L3 conditions.

Method used

The proposed solution involves configuring User Equipment (UE) and network nodes to handle the ltm-ServingCellNoSecurityChangeID during L3 mobility, defining UE actions for LTM candidate cells, and enabling measurements for CLTM based on L3 measurement conditions, using RRC messages for LTM configuration and execution conditions.

Benefits of technology

This approach reduces latency and signaling overhead by allowing efficient LTM and CLTM operations, ensuring seamless mobility management and secure transitions between cells in wireless communication networks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2026005887_19112026_PF_FP_ABST
    Figure KR2026005887_19112026_PF_FP_ABST
Patent Text Reader

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. The disclosure provides a method performed by a user equipment (UE) in a wireless communication system, the method comprises receiving, from a base station, a radio resource control (RRC) message including a layer 1 / layer 2 triggered mobility (LTM) configuration, identifying whether a measurement identifier is indicated based on a LTM execution condition included in the LTM configuration and performing measurement for a conditional LTM (CLTM) based on layer 3 (L3) measurement associated with the measurement identifier, if the measurement identifier is indicated based on the LTM execution condition.
Need to check novelty before this filing date? Find Prior Art

Description

METHOD AND APPARATUS FOR MANAGING INTERACTIONS OF LTM AND CLTM WITH L3 MOBILITY

[0001] Embodiments disclosed herein relate to wireless communication networks, and more particularly to managing interactions of with Lower-Layer (L1 / L2) Triggered Mobility (LTM) and Conditional Lower-Layer (L1 / L2) Triggered Mobility (CLTM) with Layer 3 (L3) mobility in wireless communication networks.

[0002] Fifth generation (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 6 gigahertz (GHz)” bands such as 3.5GHz, but also in “above 6GHz” bands referred to as millimeter wave (mmWave) including 28GHz and 39GHz. In addition, implementing sixth generation (6G) mobile communication technologies (referred to as Beyond 5G systems) in terahertz (THz) 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 is being considered.

[0003] 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 multi input multi output (MIMO) for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave. In addition, 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 bandwidth part (BWP), new channel coding methods such as a low density parity check (LDPC) code for large amounts of data transmission and a polar code for highly reliable transmission of control information, layer two (L2) pre-processing, and network slicing for providing a dedicated network specialized to a specific service are also being used to support services and to satisfy performance requirements.

[0004] 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 vehicle-to-everything (V2X) technologies 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, new radio unlicensed (NR-U) technologies aimed at system operations conforming to various regulation-related requirements in unlicensed bands, new radio (NR) user equipment (UE) power saving technologies, non-terrestrial network (NTN) technologies, which are UE-satellite direct communication technologies for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning technologies.

[0005] 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, integrated access and backhaul (IAB) 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 dual active protocol stack (DAPS) handover, and two-step random access for simplifying random access procedures (for example, 2-step random access channel (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.

[0006] As 5G mobile communication systems are commercialized, connected devices will be connected to communication networks, and it is 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 augmented reality (AR), virtual reality (VR), and mixed reality (MR). 5G performance improvement and complexity reduction may be accomplished by utilizing artificial intelligence (AI) and machine learning (ML), AI service support, metaverse service support, and drone communication.

[0007] Furthermore, such development of 5G mobile communication systems will serve as a basis for developing new waveforms for providing coverage in THz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as full dimensional multiple input multiple output (FD-MIMO), array and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of THz band signals, high-dimensional space multiplexing technology using orbital angular momentum (OAM), reconfigurable intelligent surface (RIS) technology, 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 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.

[0008] The principal object of embodiments herein is to disclose methods and systems for managing interactions of Low-Layer Triggered Mobility (LTM) and Conditional Low-Layer Triggered Mobility (CLTM) with Layer 3 (L3) mobility in wireless communication networks.

[0009] Another object of embodiments herein is to disclose methods and systems for enabling the UE and the network node to handle the ltm-ServingCellNoSecurityChangeID within VarLTM-ServingCellNoSecurityChangeID, when it is performing L3 mobility.

[0010] Another object of embodiments herein is to define the UE actions when the UE is performing L3 mobility and the PCell or PSCell after successful execution of L3 mobility, is an LTM candidate cell and the LTM candidate configuration includes the execution conditions for Conditional LTM.

[0011] Another object of embodiments herein is to disclose methods and systems for enabling the UE to perform measurement for CLTM with L3 measurement conditions.

[0012] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating at least one embodiment and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit thereof, and the embodiments herein include all such modifications.

[0013] According to the disclosure a method performed by a user equipment (UE) in a wireless communication system is provided. The method comprises receiving, from a base station, a radio resource control (RRC) message including a layer 1 / layer 2 triggered mobility (LTM) configuration; identifying whether a measurement identifier is indicated based on a LTM execution condition included in the LTM configuration; and performing measurement for a conditional LTM (CLTM) based on layer 3 (L3) measurement associated with the measurement identifier, if the measurement identifier is indicated based on the LTM execution condition.

[0014] Also according to the disclosure a method performed by a base station in a wireless communication system is provided. The method comprises transmitting, to a user equipment (UE), a radio resource control (RRC) message including a layer 1 / layer 2 triggered mobility (LTM) configuration; and performing measurement for a conditional LTM (CLTM) based on layer 3 (L3) measurement associated with a measurement identifier, if the measurement identifier is indicated based on an LTM execution condition included in the LTM configuration.

[0015] Also according to the disclosure a user equipment (UE) in a wireless communication system is provided. The UE comprises a transceiver and at least one processor coupled with the transceiver and configured to receive, from a base station, a radio resource control (RRC) message including a layer 1 / layer 2 triggered mobility (LTM) configuration; to identify whether a measurement identifier is indicated based on a LTM execution condition included in the LTM configuration; and to perform measurement for a conditional LTM (CLTM) based on layer 3 (L3) measurement associated with the measurement identifier, if the measurement identifier is indicated based on the LTM execution condition.

[0016] Also according to the disclosure a base station in a wireless communication system is provided. The base station comprises a transceiver; and at least one processor coupled with the transceiver and configured to transmit, to a user equipment (UE), a radio resource control (RRC) message including a layer 1 / layer 2 triggered mobility (LTM) configuration; and to perform measurement for a conditional LTM (CLTM) based on layer 3 (L3) measurement associated with a measurement identifier, if the measurement identifier is indicated based on an LTM execution condition included in the LTM configuration.

[0017] According to various embodiments of the disclosure, if a UE is configured with LTM execution conditions and a measurement identifier is indicated in the configured LTM execution conditions for a serving cell, the UE performs measurements for CLTM based on L3 measurements. Accordingly, CLTM operation can be performed based on L3 measurements under the configured conditions.

[0018] In addition, according to various embodiments of the disclosure provide alternatives for handling a serving cell security identifier during Layer 3 mobility: (i) including the serving cell security identifier in an RRCReconfiguration message, or (ii) releasing all LTM candidate configurations that require the serving cell security identifier. Through these alternatives, the handling of the serving cell security identifier during Layer 3 mobility can be managed in accordance with the configuration.

[0019] Embodiments herein are illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the following illustratory drawings. Embodiments herein are illustrated by way of examples in the accompanying drawings, and in which:

[0020] FIG. 1 depicts a communication network, according to embodiments as disclosed herein;

[0021] FIG. 2 is a block diagram of a terminal or user equipment (UE), according to embodiments as disclosed herein;

[0022] FIG. 3 is a flowchart depicting the process of managing mobility, according to embodiments as disclosed herein;

[0023] FIG. 4 is a block diagram of a network node, according to embodiments as disclosed herein;

[0024] FIG. 5 is a flowchart depicting the process for handling the serving cell security identifier during L3 mobility, according to embodiments as disclosed herein;

[0025] FIG. 6 is a flowchart depicting the process for handling the serving cell security identifier during L3 mobility, according to embodiments as disclosed herein;

[0026] FIGs 7A and 7B depict a process for enabling L3 mobility and LTM configuration for controlling security key change / PDCP reestablishment, according to embodiments as disclosed herein;

[0027] FIG. 8 depicts the L3 mobility and conditional LTM procedure, according to embodiments as disclosed herein; and

[0028] FIG. 9 depicts the process of performing measurement for conditional LTM, according to embodiments as disclosed herein.

[0029] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.

[0030] For the purposes of interpreting this specification, the definitions (as defined herein) will apply and whenever appropriate the terms used in singular will also include the plural and vice versa. It is to be understood that the terminology used herein is for the purposes of describing particular embodiments only and is not intended to be limiting. The terms “comprising”, “having” and “including” are to be construed as open-ended terms unless otherwise noted.

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

[0032] Embodiments herein may be described and illustrated in terms of blocks which carry out a described function or functions. These blocks, which may be referred to herein as managers, units, modules, hardware components or the like, are physically implemented by analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by a firmware. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like. The circuits constituting a block may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block. Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the disclosure. Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the disclosure.

[0033] It should be noted that elements in the drawings are illustrated for the purposes of this description and ease of understanding and may not have necessarily been drawn to scale. For example, the flowcharts / sequence diagrams illustrate the method in terms of the steps required for understanding of aspects of the embodiments as disclosed herein. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Furthermore, in terms of the system, one or more components / modules which comprise the system may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

[0034] The accompanying drawings are used to help easily understand various technical features and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the present disclosure should be construed to extend to any modifications, equivalents, and substitutes in addition to those which are particularly set out in the accompanying drawings and the corresponding description. Usage of words such as first, second, third etc., to describe components / elements / steps is for the purposes of this description and should not be construed as sequential ordering / placement / occurrence unless specified otherwise.

[0035] Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanying drawings.

[0036] In describing the embodiments, descriptions related to technical contents well-known in the art and not associated directly with the disclosure will be omitted. Such an omission of unnecessary descriptions is intended to prevent obscuring of the main idea of the disclosure and more clearly transfer the main idea.

[0037] 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.

[0038] The advantages and features of the disclosure and ways to achieve them will be apparent by making reference to embodiments as described below in detail in conjunction with the accompanying drawings. However, the disclosure is not limited to the embodiments set forth below, but may be implemented in various different forms. The following embodiments are provided only to completely disclose the disclosure and inform those skilled in the art of the scope of the disclosure, and the disclosure is defined only by the scope of the appended claims. Throughout the specification, the same or like reference numerals designate the same or like elements. Furthermore, in describing the disclosure, a detailed description of known functions or constitution incorporated herein will be omitted in the case that it is determined that the description may make the subject matter of the disclosure unnecessarily unclear. The terms which will be described below 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.

[0039] Herein, it will be understood that each block of the 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 individually or 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).

[0040] 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.

[0041] 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 / module” 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.

[0042] 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.

[0043] 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.

[0044] 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.

[0045] 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.

[0046] 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.

[0047] 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.

[0048] 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.

[0049] 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.

[0050] 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.

[0051] 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.

[0052] 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.

[0053] 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.

[0054] 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.

[0055] 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.

[0056] 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.

[0057] 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 the same information, and, in some cases, are separate and different information.

[0058] 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.

[0059] 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.

[0060] 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.

[0061] 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.

[0062] In the specific embodiments of the present disclosure described below, 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.

[0063] The drawings or flowcharts described below 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.

[0064] 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.

[0065] 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.

[0066] 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.

[0067] 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.

[0068] 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 described below, 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 ETSI, where appropriate.

[0069] Hereinafter, a base station (BS) is an entity that allocates resources to terminals, and may be at least one of a gNodeB, an eNodeB, a Node B, a wireless access unit, a BS controller, or a node on a network.

[0070] 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 5G base station architectures in which such CU and DU functional splits are implemented.

[0071] A 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 communication functions.

[0072] 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.

[0073] Furthermore, hereinafter, 5th generation (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 disclosure

[0074] In 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."

[0075] 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, ...), radio resource control (RRC), or medium access control (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.

[0076] In addition, Layer 1 (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), downlink control information (DCI), user equipment (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.

[0077] For example, the physical layer signaling (i.e., L1 signaling) 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 signaling. It should be noted, however, that the higher layer signaling is not limited to the aforementioned examples.

[0078] 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.

[0079] Hereinafter, the operational principle of the present disclosure will be described in detail with reference to the accompanying drawings.

[0080] In wireless technologies (for example, Fifth Generation (5G) New Radio (NR), Sixth Generation (6G), and so on), devices (hereinafter referred to as User Equipments (UEs)) can move across different cells. Mobility is performed using a procedure called cell reselection in RRC_IDLE mode. Till NR R17, mobility is performed using a procedure called handover in RRC_CONNECTED mode. Network controlled mobility applies to UEs in RRC_CONNECTED. It requires explicit Radio Resource Control (RRC) signalling to be triggered by the gNodeB (gNB) in NR. Handover in NR usually comprises of handover preparation, handover execution and handover completion. The gNB may configure the UE to report measurements and based on the reported measurements or based on its own understanding of the network topology, the gNB will send a RRC Reconfiguration message to handover the UE to another cell called target cell from the source cell. The UE accesses the target cell and sends RRC Reconfiguration complete message. In an alternative way introduced in 3gpp NR release 16, the gNB may configure the UE with the execution conditions for triggering handover and once the execution conditions are satisfied, the UE may move to target cell and sends the RRC Reconfiguration complete. 3GPP also introduced a new handover called Dual Active Protocol Stack (DAPS) Handover in release 16. The handover, and conditional handover (CHO) can be referred to as layer 3 (L3) mobility. In case of dual connectivity, the UE may perform PSCellChange or Conditional PSCellChange mainly through L3 signalling. In the context of dual connectivity, PSCellChange or Conditional PSCellChange can be referred to also as L3 mobility; i.e., Handover, Conditional Handover, PSCellChange, Conditional PSCellChange etc. refers to L3 mobility. PSCellChange or Conditional PSCellChange can also be referred to herein as SCG layer 3 mobility and the handover and CHO as MCG layer 3 mobility in the context of dual connectivity. Conditional handover, and conditional PSCell change can be also referred to as conditional mobility.

[0081] In all these methods, the UE performs handover by sending layer 3 (RRC) messages which causes considerable signalling overhead and latency issues. 3gpp release 18 introduced Lower layers (L1 / L2 layers) Triggered Mobility, also known as LTM. As per 3gpp, the goal of LTM is to enable a serving cell change via L1 / L2 signalling, to reduce the latency, overhead and interruption time. The Network (i.e., the gNB) may configure the UE with multiple candidate cells to allow fast application of configurations for candidate cells. The network may further send a Medium Access Control (MAC) Control Element (CE) or L1 signalling to dynamically switch the UE from a source cell to one of the configured candidate cells. Further, LTM can be triggered based on L1 measurements or L3 measurements.

[0082] The gNB provides reference configuration, L1 measurement configuration and candidate cell configuration for LTM.

[0083] While Rel-18 of 3gpp supported LTM within the same gNB CU, Rel-19 is planning to introduce Inter-CU LTM. For a UE in dual connectivity, both a Master Node (MN) and a Secondary Node (SN) can provide the LTM configuration including LTM candidate cells, LTM reference configuration, and so on.

[0084] Conditional L1 / L2 Triggered Mobility (CLTM) is an LTM cell switch procedure that is executed only when execution condition(s) are met. CLTM cell switch is executed by the UE when L1-based or L3-based LTM cell switch execution conditions are met.

[0085] An example procedure for CLTM according to prior arts is as follows:

[0086] 1. The UE sends a MeasurementReport message to the network node such as gNB or 6G base station. The network node decides to configure CLTM and initiates CLTM preparation.

[0087] 2. The source network node can request the candidate cells to provide conditional execution configurations, and the candidate cells provide the conditional configuration including their own execution conditions, to be used in subsequent CLTM.

[0088] 3. The source network node sends an RRC Reconfiguration message to the UE and this includes the CLTM configurations of candidate cells as well as the execution condition for the CLTM.

[0089] 4. The UE stores the CLTM candidate configurations and transmits an RRCReconfigurationComplete message to the network node. The UE starts evaluating the execution conditions based on the provided configuration.

[0090] 5 / 6. The source network node (such as the source gNB) can trigger early synchronization (for example, based on the L1 or L3 measurement reports from the UE, if configured) to the UE. In addition, the source network node can provide the TA value for each of the candidate cells the UE has performed UL synchronization with.

[0091] 7. The CLTM execution condition is satisfied at the UE and on the satisfied candidate LTM cell, the UE performs the CLTM switch by applying the configuration of the satisfied LTM candidate cell. If the UE has valid TA as part of the UL early synchronization from step 6, the UE skips RACH. Otherwise, RACH is performed as part of the CLTM switch.

[0092] 8. The UE completes the CLTM cell switch procedure by sending RRC ReconfigurationComplete message to the switched LTM cell. The UE does not release any valid TA value(s) of LTM candidate cells with CLTM configuration

[0093] Steps 5-8 can be performed multiple times for subsequent CLTM cell switch executions using the CLTM candidate configuration(s) provided in step 2.

[0094] Currently, the below structures can be used for defining LTM and conditional LTM.

[0095] -- ASN1START-- TAG-LTM-CANDIDATE-STARTLTM-Candidate-r18 ::= SEQUENCE {ltm-CandidateId-r18 LTM-CandidateId-r18,ltm-CandidatePCI-r18 PhysCellId OPTIONAL, -- Need Mltm-SSB-Config-r18 LTM-SSB-Config-r18 OPTIONAL, -- Need Mltm-CandidateConfig-r18 OCTET STRING (CONTAINING RRCReconfiguration) OPTIONAL, -- Need Mltm-ConfigComplete-r18 ENUMERATED {true} OPTIONAL, -- Need Rltm-EarlyUL-SyncConfig-r18 OCTET STRING (CONTAINING EarlyUL-SyncConfig-r18) OPTIONAL, -- Need Rltm-EarlyUL-SyncConfigSUL-r18 OCTET STRING (CONTAINING EarlyUL-SyncConfig-r18) OPTIONAL, -- Need Rltm-TCI-Info-r18 LTM-TCI-Info-r18 OPTIONAL, -- Need Mltm-NoResetID-r18 INTEGER (1..maxNrofLTM-Configs-plus1-r18) OPTIONAL, -- Need Mltm-UE-MeasuredTA-ID-r18 INTEGER (1..maxNrofLTM-Configs-plus1-r18) OPTIONAL, -- Need M...,[[ltm-NoSecurityChangeID-r19 INTEGER (1..maxNrofLTM-Configs-plus1-r18) OPTIONAL, -- Need Mcltm-ExecutionConditions-r19 SetupRelease {CLTM-ExecutionConditions-r19} OPTIONAL -- Need M]]}LTM-SSB-Config-r18 ::= SEQUENCE {ssb-Frequency-r18 ARFCN-ValueNR,subcarrierSpacing-r18 SubcarrierSpacing,ssb-Periodicity-r18 ENUMERATED {ms5, ms10, ms20, ms40, ms80, ms160, spare2, spare1} OPTIONAL, -- Need Rssb-PositionsInBurst-r18 CHOICE {shortBitmap BIT STRING (SIZE (4)),mediumBitmap BIT STRING (SIZE (8)),longBitmap BIT STRING (SIZE (64))} OPTIONAL, -- Need Rss-PBCH-BlockPower-r18 INTEGER (-60..50) OPTIONAL, -- Need R...}CLTM-ExecutionConditions-r19 ::= SEQUENCE (SIZE (1..maxNrofLTM-Configs-r18)) OF ExecutionConditions-r19ExecutionConditions-r19 ::= SEQUENCE {ltm-CandidateId-r19 LTM-CandidateId-r18,executionCondition-r19 CHOICE {l1-Conditions-r19 LTM-CSI-ReportConfigId-r18,l3-Conditions-r19 SEQUENCE (SIZE (1..2)) OF MeasId} OPTIONAL, -- Need R...}

[0096] For CLTM based on Layer 3 measurements, as shown above, the execution condition, l3-condition is a sequence of measurement identifiers.

[0097] LTM-Candidate field descriptions:

[0098] ltm-CandidateConfig: This field includes an RRCReconfiguration message used to configure an LTM candidate configuration.

[0099] ltm-CandidatePCI: This field identifies the PCI of the SpCell of the LTM candidate configuration contained in ltm-CandidateConfig.

[0100] ltm-EarlyUL-SyncConfig, ltm-EarlyUL-SyncConfigSUL: A configuration used to perform the early UL synchronization procedure over an UL or SUL carrier.

[0101] ltm-NoResetID: If the network configures this field for one LTM candidate configuration, the network configures also for all LTM candidate configurations within ltm-CandidateToAddModList in LTM-Config and ensures that the UE has stored a value for ltm-ServingCellNoResetID within VarLTM-ServingCellNoResetID.

[0102] ltm-NoSeurityChangeID: If the network configures this field for one LTM candidate configuration, the network configures also for all LTM candidate configurations within ltm-CandidateToAddModList in LTM-Config and ensures that the UE has stored a value for ltm-ServingCellNoSecurityChangeID within VarLTM-ServingCellNoSecurityChangeID.

[0103] ltm-UE-MeasuredTA-ID: If the network configures this field for one LTM candidate configuration, the network configures also for all LTM candidate configurations within ltm-CandidateToAddModList in LTM-Config and ensures that the UE has stored a value for ltm-ServingCellUE-MeasuredTA-ID within VarLTM-ServingCellUE-MeasuredTA-ID. This field is absent if tag2 is present for this LTM candidate configuration.

[0104] A cell can be considered as a CLTM candidate cell if its LTM candidate configuration includes conditional LTM execution conditions (such as CLTM-ExecutionConditions).

[0105] LTM-Config:The IE LTM-Config is used to provide LTM configurations.LTM-Config information element:-- ASN1START-- TAG-LTM-CONFIG-STARTLTM-Config-r18 ::= SEQUENCE {ltm-ReferenceConfiguration-r18 SetupRelease {ReferenceConfiguration-r18} OPTIONAL, -- Need Mltm-CandidateToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofLTM-Configs-r18)) OF LTM-CandidateId-r18 OPTIONAL, -- Need Nltm-CandidateToAddModList-r18 SEQUENCE (SIZE (1..maxNrofLTM-Configs-r18)) OF LTM-Candidate-r18 OPTIONAL, -- Need Nltm-ServingCellNoResetID-r18 INTEGER (1..maxNrofLTM-Configs-plus1-r18) OPTIONAL, -- Need Nltm-CSI-ResourceConfigToAddModList-r18 SEQUENCE (SIZE (1..maxNrofLTM-CSI-ResourceConfigurations-r18)) OF LTM-CSI-ResourceConfig-r18OPTIONAL, -- Need Nltm-CSI-ResourceConfigToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofLTM-CSI-ResourceConfigurations-r18)) OF LTM-CSI-ResourceConfigId-r18OPTIONAL, -- Need NattemptLTM-Switch-r18 ENUMERATED {true} OPTIONAL, -- Cond LTM-MCGltm-ServingCellUE-MeasuredTA-ID-r18 INTEGER (1..maxNrofLTM-Configs-plus1-r18) OPTIONAL, -- Need N...,[[ltm-ServingCellNoSecurityChangeID-r19 INTEGER (1..maxNrofLTM-Configs-plus1-r18) OPTIONAL, -- Need Nltm-SK-Counters-r19 SetupRelease {SK-CounterList-r19} OPTIONAL, -- Need Mcltm-ServingCellExecutionConditions-r19 SetupRelease {CLTM-ExecutionConditions-r19} OPTIONAL -- Need M]]}cltm-ServingCellExecutionConditions includes the execution conditions for CLTM for the serving cell (PCell or PSCell) and can also refer to any information element which provides an equivalent functionality in any RAT.ltm-SK-Counters includes the Sk-Counter values to be used for SCG LTM mobility and in our embodiments can refer to any information element with the equivalent functionality in any RAT.SK-CounterList-r19 ::= SEQUENCE {sk-CounterList-r19 SEQUENCE (SIZE (1..maxSK-Counter-r18)) OF SK-Counter}LTM-ConfigSCG-r19 ::= SEQUENCE {ltm-ConfigurationSCG-r19 OCTET STRING (CONTAINING LTM-Config-r18) OPTIONAL, -- Need R}-- TAG-LTM-CONFIG-STOP-- ASN1STOPLTM-ConfigNRDC:The IE LTM-ConfigNRDC is used to provide LTM configurations in NR-DC.LTM-ConfigNRDC information element:-- ASN1START-- TAG-LTM-CONFIGNRDC-STARTLTM-ConfigNRDC-r19 ::= SEQUENCE {ltm-ConfigurationSCG-r19 SetupRelease {LTM-Config-r18} OPTIONAL -- Need Rltm-SK-CounterConfigToAddModList-r19 SEQUENCE (SIZE (1..maxSecurityCellSet-r18)) OF SK-CounterConfig-r18 OPTIONAL, -- Need Nltm-SK-CounterConfigToReleaseList-r19 SEQUENCE (SIZE (1..maxSecurityCellSet-r18)) OF SecurityCellSetId-r18 OPTIONAL, -- Need N...}-- TAG-LTM-CONFIGNRDC-STOP-- ASN1STOP

[0106] LTM-ConfigNRDC field descriptions:

[0107] ltm-ConfigurationSCG: The network does not configure this field in an RRCReconfiguration message within an LTM-Config IE and ConditionalReconfiguration IE.

[0108] The UE may store the ltm-ServingCellNoSecurityChangeID in the UE variable (for example, VarLTM-ServingCellNoSecurityChangeID).

[0109] As referred to herein, ltm-NoSecurityChangeID also refers to any equivalent information element of the candidate cell which is used to decide whether UE performs PDCP reestablishment or security updates in any RAT.

[0110] As referred to herein, ltm-ServingCellNoSecurityChangeID also refers to any equivalent information element of the serving cell which is used to decide whether the UE performs PDCP reestablishment or security updates in any RAT.

[0111] VarLTM-ServingCellNoSecurityChange:

[0112] The IE VarLTM-ServingCellNoSecurityChange is used to store the ID associated with the serving cell based on which the UE determines whether a security change is needed or not upon an LTM cell switch procedure and the list of sk-counter value that can be used when a security key change is performed at the SCG.

[0113] VarLTM-ServingCellNoSecurityChangeID UE variable:

[0114] -- ASN1START-- TAG-VARLTM-SEVINGCELLNOSECURITYCHANGE-STARTVarLTM-ServingCellNoSecurityChangeID-r19 ::= SEQUENCE {ltm-ServingCellNoSecurityChangeID-r19 INTEGER (1..maxNrofLTM-Configs-plus1-r18) OPTIONAL,ltm-SK-Counters-r19 SEQUENCE (SIZE (1..maxSecurityCellSet-r18)) OF SK-CounterConfigLTM-r19 OPTIONAL}-- TAG-VARLTM-SEVINGCELLNOSECURITYCHANGE-STOP-- ASN1STOP

[0115] As referred to herein, VarLTM-ServingCellNoSecurityChangeID also refers to any equivalent variable which stores ltm-ServingCellNoSecurityChangeID or equivalent variable.

[0116] The UE performs various operations based on received value of ltm-NoSecurityChangeID and the value of ltm-ServingCellNoSecurityChangeID from the UE variable. If ltm-ServingCellNoSecurityChangeID and ltm-ServingCellNoSecurityChangeID (for example, in the UE variable such as VarLTM-ServingCellNoSecurityChangeID) are different, the UE performs PDCP reestablishment for the Data Radio Bearers (DRB) and / or Signalling Radio Bearers (SRB) and the reestablishment of corresponding RLC entities, security key change and applies new ciphering and integrity for DRBs / SRBs.

[0117] In the prior art, the UE actions based on ltm-ServingCellNoSecurityChangeID are explained as below:

[0118] 5.3.5.18.6 LTM cell switch execution:Upon the indication by lower layers that an 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, or upon the fulfilment of LTM cell switch execution conditions, the UE shall:1> if the fieldltm-NoSecurityChangeIDis configured for theLTM-CandidateIE inltm-Configorltm-ConfigNRDCindicated by lower layers and if the UE does not have any value stored ofltm-ServingCellNoSecurityChangeIDwithinVarLTM-ServingCellNoSecurityChangeID; or1> if the value of fieldltm-NoSecurityChangeIDcontained within theLTM-CandidateIE inltm-Configorltm-ConfigNRDCindicated by lower layers or for the selected cell in accordance with 5.3.7.3 is not equal to the value ofltm-ServingCellNoSecurityChangeIDwithinVarLTM-ServingCellNoSecurityChangeID:2> if the LTM cell switch is triggered on the MCG:3> update the master security key by performing the AS security key update procedure as specified in 5.3.5.7;3> if theLTM-CandidateIE indicated by lower layers does not include anmrdc-SecondaryCellGroupConfigset torelease:4> consider the firstsk-Countervalue in theltm-SK-Counterswithin theVarLTM-ServingCellNoSecurityChangeIDaccording to the fieldltm-NoSecurityChangeIDas the selectedsk-Countervalue, and perform security key update procedure as specified in 5.3.5.7;4> remove the selectedsk-Countervalue from theltm-SK-Counterswithin theVarLTM-ServingCellNoSecurityChangeID;2> else if the LTM cell switch is triggered on the SCG:3> consider the firstsk-Countervalue in theltm-SK-Counterswithin theVarLTM-ServingCellNoSecurityChangeIDaccording to the fieldltm-NoSecurityChangeIDas the selectedsk-Countervalue, and update the secondary key by performing security key update procedure as specified in 5.3.5.7;3> remove the selectedsk-Countervalue from theltm-SK-Counterswithin theVarLTM-ServingCellNoSecurityChangeID;2> at the end of the procedure, for eachdrb-Identityvalue that is part of the current UE configuration:3> if the PDCP entity of this DRB is not configured withcipheringDisabled:4> configure the PDCP entity with the ciphering algorithm and KUPenckey associated with the master key (KgNB) or secondary key (S-KgNB), as indicated inkeyToUse, i.e. the ciphering configuration shall be applied to all subsequent PDCP PDUs received and sent by the UE;3> if the PDCP entity of this DRB is configured withintegrityProtection:4> configure the PDCP entity with the integrity protection algorithms according tosecurityConfigand apply the KUPintkey associated with the master key (KeNB / KgNB) or the secondary key (S-KgNB) as indicated inkeyToUse;3> ifdrb-ContinueROHCis included inpdcp-Config:4> indicate to lower layer thatdrb-ContinueROHCis configured;3> ifdrb-ContinueEHC-DLis included inpdcp-Config:4> indicate to lower layer thatdrb-ContinueEHC-DLis configured;3> ifdrb-ContinueEHC-ULis included inpdcp-Config:4> indicate to lower layer thatdrb-ContinueEHC-ULis configured;3> ifdrb-ContinueUDCis included inpdcp-Config:4> indicate to lower layer thatdrb-ContinueUDCis configured;3> re-establish the PDCP entity of this DRB as specified in TS 38.323 [5], clause 5.1.2;3> re-establish the corresponding RLC entity as specified in TS 38.322 [4];2> at the end of the procedure, for eachsrb-Identityvalue that is part of the current UE configuration:3> configure the PDCP entity to apply the integrity protection algorithm and KRRCintkey associated with the master key (KgNB) or the secondary key (S-KgNB), as indicated inkeyToUse, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;3> configure the PDCP entity to apply the ciphering algorithm and KRRCenckey associated with the master key (KgNB) or the secondary key (S-KgNB) as indicated inkeyToUse, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;3> re-establish the PDCP entity of this SRB as specified in TS 38.323 [5];3> re-establish the corresponding RLC entity as specified in TS 38.322The UE performs measurements if the UE is configured with LTM execution conditions and the measurement identifier is indicated in the configured LTM execution conditions. These measurements can be used for evaluation of conditional LTM.2> if thereportTypefor the associatedreportConfigiscondTriggerConfig,themeasIdis within the MCGVarMeasConfigand is indicated in anLTM-ExecutionConditionIE:

[0119] <perform measurements>

[0120] In the prior arts, the UE performs measurements for all the measurement identifiers configured in any of the LTM execution condition; i.e., including the LTM execution condition of any of the candidate cells. Performing measurements for the execution condition of all candidate cells can result in an increase in the battery consumption of the UEs.

[0121] Consider v18.5.1 of 3gpp specifications such as TS38.300, TS38.331, TS 38.321,TS 37.340 also as relevant background.

[0122] In the background TS 38.331, VarMeasConfig, conditional triggering configuration (condTriggerConfig) and the report configuration including report type (reportType) is defined as follows:

[0123] - VarMeasConfigThe UE variable VarMeasConfig includes the accumulated configuration of the measurements to be performed by the UE, covering intra-frequency, inter-frequency and inter-RAT mobility related measurements.VarMeasConfig UE variable-- ASN1START-- TAG-VARMEASCONFIG-STARTVarMeasConfig ::= SEQUENCE {-- Measurement identitiesmeasIdList MeasIdToAddModList OPTIONAL,-- Measurement objectsmeasObjectList MeasObjectToAddModList OPTIONAL,-- Reporting configurationsreportConfigList ReportConfigToAddModList OPTIONAL,-- Other parametersquantityConfig QuantityConfig OPTIONAL,s-MeasureConfig CHOICE {ssb-RSRP RSRP-Range,csi-RSRP RSRP-Range} OPTIONAL}-- TAG-VARMEASCONFIG-STOP-- ASN1STOPCondTriggerConfig-r16 ::= SEQUENCE {condEventId CHOICE {condEventA3 SEQUENCE {a3-Offset MeasTriggerQuantityOffset,hysteresis Hysteresis,timeToTrigger TimeToTrigger},condEventA5 SEQUENCE {a5-Threshold1 MeasTriggerQuantity,a5-Threshold2 MeasTriggerQuantity,hysteresis Hysteresis,timeToTrigger TimeToTrigger},...,condEventA4-r17 SEQUENCE {a4-Threshold-r17 MeasTriggerQuantity,hysteresis-r17 Hysteresis,timeToTrigger-r17 TimeToTrigger},condEventD1-r17 SEQUENCE {distanceThreshFromReference1-r17 INTEGER(0.. 65525),distanceThreshFromReference2-r17 INTEGER(0.. 65525),referenceLocation1-r17 ReferenceLocation-r17,referenceLocation2-r17 ReferenceLocation-r17,hysteresisLocation-r17 HysteresisLocation-r17,timeToTrigger-r17 TimeToTrigger},condEventT1-r17 SEQUENCE {t1-Threshold-r17 INTEGER (0..549755813887),duration-r17 INTEGER (1..6000)},condEventD2-r18 SEQUENCE {distanceThreshFromReference1-r18 INTEGER(0.. 65535),distanceThreshFromReference2-r18 INTEGER(0.. 65535),hysteresisLocation-r18 HysteresisLocation-r17,timeToTrigger-r18 TimeToTrigger}},rsType-r16 NR-RS-Type,...,[[nesEvent-r18 ENUMERATED {true} OPTIONAL -- Need R]]}ReportConfigNR ::= SEQUENCE {reportType CHOICE {periodical PeriodicalReportConfig,eventTriggered EventTriggerConfig,...,reportCGI ReportCGI,reportSFTD ReportSFTD-NR,condTriggerConfig-r16 CondTriggerConfig-r16,cli-Periodical-r16 CLI-PeriodicalReportConfig-r16,cli-EventTriggered-r16 CLI-EventTriggerConfig-r16,rxTxPeriodical-r17 RxTxPeriodical-r17,reportOnScellActivation-r18 ReportOnScellActivation-r18}}

[0124] Hence, there is a need in the art for solutions which will overcome the above mentioned drawback(s), among others.

[0125] The embodiments herein achieve methods and systems for managing interactions of Low-Layer Triggered Mobility (LTM) and Conditional Low-Layer Triggered Mobility (CLTM) with Layer 3 (L3) mobility in wireless communication networks. Referring now to the drawings, and more particularly to FIGS. 1 through 9, where similar reference characters denote corresponding features consistently throughout the figures, there are shown embodiments.

[0126] Embodiments herein disclose methods and systems for managing interactions of Low-Layer Triggered Mobility (LTM) and Conditional Low-Layer Triggered Mobility (CLTM) with Layer 3 (L3) mobility in wireless communication networks. Embodiments herein disclose methods and systems for enabling the UE and the network node to handle the ltm-ServingCellNoSecurityChangeID (i.e., an identifier related to the serving cell which indicates whether to change the security related parameter) within VarLTM-ServingCellNoSecurityChangeID (i.e., a UE variable which stores the above parameter), when it is performing L3 mobility. Embodiments herein define the UE actions when the UE is performing L3 mobility and the PCell or PSCell after successful execution of L3 mobility, is an LTM candidate cell and the LTM candidate configuration includes the execution conditions for Conditional LTM. Embodiments herein disclose methods and systems for enabling the UE to perform measurement for CLTM with L3 measurement conditions.

[0127] FIG. 1 depicts a communication network. The communication network as depicted comprises at least one network node 102 connected to at least one UE 101. Consider that the UE 101 is undergoing L3 mobility, from cell1 to cell 2. An example of the network node 102 can be a gNB.

[0128] In an embodiment herein, consider that the UE 101 is performing L3 mobility from Cell1 to Cell2, wherein Cell2 is an LTM candidate cell and the LTM candidate configuration of Cell2 contains ltm-NoSecurityChangeID. The UE 101 can store the received ltm-NoSecurityChangeID within the LTM candidate configuration of Cell2 in the ltm-ServingCellNoSecurityChangeID within VarLTM-ServingCellNoSecurityChangeID; i.e., the UE 101 does not execute the RRCReconfiguration from LTM candidate configuration of Cell2 during L3 mobility, but the UE 101 can store the ltm-NoSecurityChangeID from the LTM candidate configuration of Cell2, in the ltm-ServingCellNoSecurityChangeID within VarLTM-ServingCellNoSecurityChangeID.

[0129] In an embodiment herein, consider that the UE 101 is performing L3 mobility from Cell1 to Cell2, wherein Cell2 is an LTM candidate cell and the LTM candidate configuration of Cell2 contains ltm-NoSecurityChangeID. The UE 101 can store the ltm-NoSecurityChangeID received within the LTM candidate configuration of Cell2 in the ltm-ServingCellNoSecurityChangeID within VarLTM-ServingCellNoSecurityChangeID, if the value of ltm-NoSecurityChangeID in LTM candidate configuration of Cell2 is different from the ltm-ServingCellNoSecurityChangeID stored in VarLTM-ServingCellNoSecurityChangeID; i.e., the UE 101 does not execute the RRCReconfiguration from LTM candidate configuration of Cell2, however the UE 101 can store the ltm-NoSecurityChangeID from the LTM candidate configuration of Cell2, in the ltm-ServingCellNoSecurityChangeID within VarLTM-ServingCellNoSecurityChangeID, if the value of ltm-NoSecurityChangeID in LTM candidate configuration of Cell2 is different from the ltm-ServingCellNoSecurityChangeID stored in VarLTM-ServingCellNoSecurityChangeID.

[0130] In an embodiment herein, consider that the UE 101 is performing L3 mobility from Cell1 to Cell2, wherein Cell2 is an LTM candidate cell. If the LTM candidate configuration of Cell2 does not contain ltm-NoSecurityChangeID, the UE 101 can remove the ltm-ServingCellNoSecurityChangeID stored in VarLTM-ServingCellNoSecurityChangeID.

[0131] In an embodiment herein, consider that the UE 101 is performing L3 mobility from Cell1 to Cell2, wherein Cell2 is an LTM candidate cell. If the LTM candidate configuration of Cell2 does not contain ltm-NoSecurityChangeID and the ltm-ServingCellNoSecurityChangeID is not received in the RRC Reconfiguration triggering LTM mobility, the UE 101 can remove the ltm-ServingCellNoSecurityChangeID stored in VarLTM-ServingCellNoSecurityChangeID.

[0132] In an embodiment herein, consider that the UE 101 is performing L3 handover from Cell1 to Cell2, wherein the Cell2 is not an LTM candidate cell. The UE 101 can remove the ltm-ServingCellNoSecurityChangeID stored in VarLTM-ServingCellNoSecurityChangeID.

[0133] In an embodiment herein, consider that the UE 101 is performing LTM cell switch from Cell1 to Cell2. If the LTM candidate configuration of Cell2 does not contain ltm-NoSecurityChangeID, the UE 101 can remove the ltm-ServingCellNoSecurityChangeID stored inVarLTM-ServingCellNoSecurityChangeID.

[0134] Embodiments herein help the UE 101 to perform LTM cell switch from Cell2 to any other LTM candidate cell, including inter-CU LTM candidate cells by ensuring that it has the updated configuration in the UE variable in VarLTM-ServingCellNoSecurityChangeID even after performing L3 mobility.

[0135] In an embodiment herein, the network node 102 can send a RRC message (for example, a RRCReconfiguration message) to perform L3 mobility of the UE 101 from Cell1 to Cell2. The LTM is configured at the UE 101 including LTM in which the UE 101 updates the security configuration (i.e., Inter-CU LTM), includes ltm-ServingCellNoSecurityChangeID in the LTM configuration, within the RRC message (for example, a RRCReconfiguration message including ReconfigurationWithSync in NR), which triggers L3 mobility. In other words, the network node 102 can modify the LTM configuration while performing L3 mobility and provide a new value of ltm-ServingCellNoSecurityChangeID in the LTM configuration, within Cell2’s RRC Reconfiguration message (for example, a RRCReconfiguration message including ReconfigurationWithSync in NR), that triggers L3 mobility.

[0136] In an embodiment herein, the network node 102 can send a RRC message (for example, a RRCReconfiguration message) to perform mobility of the UE 101 from Cell1 to Cell2 using L3 mobility. If Cell1 and Cell2 belong to two different Centralized Units (CU), the LTM is configured at the UE 101, including the LTM in which the UE 101 updates the security configuration (i.e., Inter-CU LTM), includes ltm-ServingCellNoSecurityChangeID in the LTM configuration, within the RRC message triggered to perform L3 mobility. In other words, the network node 102 can modify the LTM configuration while performing L3 mobility and provide a new value of ltm-ServingCellNoSecurityChangeID in the LTM configuration, within Cell2’s RRC Reconfiguration message (such as RRCReconfiguration including ReconfigurationWithSync in NR), that triggers L3 mobility if the Cell and Cell2 belongs to two different CUs.

[0137] In an embodiment herein, if Cell1 and Cell2 are configured as LTM candidate cells, the network node 102 can move the UE 101 from Cell1 to Cell2 using LTM and avoid moving through L3 mobility. In an embodiment herein, the network node 102 can send a RRC message (for example, a RRCReconfiguration message) to perform mobility of the UE 101 from Cell1 to Cell2 using L3 mobility and the LTM is configured at the UE 101, wherein the UE 101 can release the LTM configuration or the LTM candidate configuration of Cell1 or Cell2.

[0138] In an embodiment herein, the UE 101 can perform L3 mobility from Cell1 to Cell2, wherein Cell2 is an LTM candidate cell and the LTM candidate configuration of Cell2 includes the execution conditions for Conditional LTM. The UE 101 can perform the LTM cell switch conditions evaluation according to the execution conditions configured in the LTM candidate cell configuration of Cell2. In an embodiment herein, on the L3 mobility being completed, the UE 101 can evaluate LTM cell switch conditions. In an embodiment herein, the UE 101 can evaluate the LTM cell switch condition based on L3 conditions or L1 conditions. If the LTM cell switch condition is evaluated based on L3 conditions, the RRC of the UE 101 can evaluate LTM cell switch conditions. If the LTM cell switch condition is evaluated based on L1 conditions, the RRC of the UE 101 can inform the lower layers (for example, a UE MAC layer) to evaluate the LTM cell switch conditions.

[0139] In an embodiment herein, the network node 102 can configure the UE 101 to perform L3 mobility from Cell1 to Cell2, wherein Cell2 is an LTM candidate cell and the LTM candidate configuration of Cell2 includes the execution conditions for Conditional LTM. The network node 102 can modify the execution conditions for Conditional LTM in the LTM candidate configuration of Cell2 in the RRC Reconfiguration message (for example, a RRCReconfiguration message includes a ReconfigurationWithSync) send to trigger L3 mobility. In an embodiment herein, the network node 102 can also provide the measurement configuration to the UE 101. The measurement configuration can include measurement object configuration, report configuration and measurement identifier configuration corresponding to the execution conditions configured as before. The UE 101 can apply the received modified configuration.

[0140] In an embodiment herein, for configuring the UE 101 for performing L3 mobility from Cell1 to Cell2, the network node 102 can modify the serving cell execution conditions for Conditional LTM in the LTM configuration in the RRC Reconfiguration message (for example, a RRCReconfiguration message including ReconfigurationWithSync), send to trigger L3 mobility. In an embodiment herein, the network node 102 can also provide the measurement configuration to the UE 101. The measurement configuration can include a measurement object configuration, a report configuration and a measurement identifier configuration corresponding to the execution conditions configured as before. The UE 101 can apply the received configuration and use the same for executing CLTM from Cell2.

[0141] In an embodiment herein, upon performing L3 mobility, the UE 101 can release the received cltm-ServingCellExecutionConditions (or equivalent variable in any Radio Access Technology (RAT)).

[0142] In an embodiment herein, upon configuring the UE 101 for L3 mobility, the network node 102 can release the cltm-ServingCellExecutionConditions (or equivalent variable in any RAT).

[0143] In an embodiment herein, upon executing LTM cell switch, the UE 101 can release the received cltm-ServingCellExecutionConditions (or equivalent variable in any RAT).

[0144] In an alternative embodiment herein, the network node 102 can release the CLTM configuration, wherein the network node 102 has send a RRC message (for example, a RRCReconfiguration message) to perform mobility of the UE 101 from Cell1 to Cell2 using L3 mobility and the LTM is configured at the UE 101.

[0145] In an embodiment herein, according to TS 38.331,

[0146] 5.3.5.5.2 Reconfiguration with syncThe UE shall perform the following actions to execute a reconfiguration with sync.1> ifsl-PathSwitchConfigis included:1> else (sl-PathSwitchConfigis not included):2> if this procedure is performed due to an LTM cell switch execution:3> start synchronising to the DL of the indicated LTM candidate cell, if no DL synchronization for the indicated LTM candidate cell has been already acquired;2> else:3> if the target SpCell is different from current SpCell:3> stop the LTM conditions evaluation (based on L1 and / or L3 measurements), if any, for all the LTM candidate configurations;3> if LTM conditions evaluation was done based on L1 measurements:4> inform lower layers to stop the LTM cell switch conditions evaluation for all LTM candidate configurations;4> if the target SpCell is a LTM candidate cell5> ifltm-ExecutionConditionis configured within theLTM-CandidateIE for the selected LTM candidate configuration:6> if the fieldl3-Conditionsis included withinltm-ExecutionCondition:7> perform the LTM cell switch conditions evaluation based on L3 measurements as specified in 5.3.5.18.x according to the receivedltm-ExecutionConditiononce this procedure is completed;5> else if the fieldl1-Conditionsis included withinltm-ExecutionCondition:6> inform lower layers to initiate the LTM cell switch conditions evaluation based on L1 measurements according to the received field cltm-ExecutionConditions once this procedure is completed.3> start synchronising to the DL of the target SpCell;4> If the target Spcell is a LTM candidate cell:5> if the value of fieldltm-NoSecurityChangeIDcontained within theLTM-CandidateIE inltm-Configorltm-ConfigNRDCfor the target Spcell is not equal to the value ofltm-ServingCellNoSecurityChangeIDwithinVarLTM-ServingCellNoSecurityChangeID:6> replace the value ofltm-ServingCellNoSecurityChangeIDinVarLTM-ServingCellNoSecurityChangeIDwith the value ofltm-NoSecurityChangeIDin theLTM-Candidateinltm-Configorltm-ConfigNRDCfor the target SpCell;2> apply the specified BCCH configuration defined in 9.1.1.1 for the target SpCell;2> acquire theMIBof the target SpCell, which is scheduled as specified in TS 38.213

[0147] In an embodiment herein, if the UE 101 is configured with LTM execution conditions and the measurement identifier is indicated in the configured LTM execution conditions in the LTM candidate configuration of the serving cell (PCell or PSCell), the UE 101 can perform measurements. The measurements performed by the UE 101 can be used for evaluation of conditional LTM. In NR, if the measurement identifier as the LTM execution condition is present in LTM-Candidate configuration of serving cell (PCell or PSCell) as described in the below section, the UE 101 performs Layer 3 measurements.

[0148] LTM-Candidate-r18 ::= SEQUENCE {<only relevant IEs included>ltm-CandidateId-r18 LTM-CandidateId-r18,cltm-ExecutionConditions-r19 SetupRelease {CLTM-ExecutionConditions-r19} OPTIONAL -- Need M}

[0149] Further, the UE 101 performs CLTM evaluation based on the performed measurements according to the below section.

[0150] 6> if the fieldl3-Conditionsis included withinltm-ExecutionCondition:7> perform the LTM cell switch conditions evaluation based on L3 measurements as specified in 5.3.5.18.x according to the receivedltm-ExecutionConditiononce this procedure is completed;

[0151] Based on embodiments as disclosed herein, the UE 101 performs layer 3 measurements for the measurement identifier configured as execution conditions for conditional LTM, if the execution conditions are present in serving cell execution conditions (i.e. within ltm-config) for the serving cell or the candidate configurations of the serving cell. This allows to restrict measurements to the most essential scenarios for CLTM, thereby reducing the battery consumption.

[0152] In an embodiment herein, according to TS 38.331,

[0153] 5.5.3 Performing measurements5.5.3.1GeneralThe UE shall:1> for eachmeasIdincluded in themeasIdListwithinVarMeasConfig:2> if thereportTypefor the associatedreportConfigiscondTriggerConfig,themeasIdis within the MCGVarMeasConfigand is indicated in anLTM-ExecutionConditionIE in the LTM candidate configuration of the PCell or PSCell:3> various steps and conditions for performing L3 measurements

[0154] In all the embodiments herein, on the network node 102 configuring the UE 101 with a configuration, the UE 101 can apply the received configuration.

[0155] In an embodiment herein, if the UE 101 is configured with LTM execution conditions and the measurement identifier is indicated in the configured LTM execution conditions in the LTM configuration of the serving cell (PCell or PSCell) which has received the LTM configuration (either LTM configuration is added or modified), the UE 101 can perform measurements. The measurements performed by the UE 101 can be used for evaluation of conditional LTM.

[0156] In NR, if the measurement identifier as the LTM execution condition is present in LTM configuration of serving cell (PCell or PSCell) as described in the below section in cltm-ServingCellExecutionConditons, the UE 101 performs Layer 3 measurements.

[0157] LTM-Config-r18 ::= SEQUENCE {[[cltm-ServingCellExecutionConditions-r19 SetupRelease {CLTM-ExecutionConditions-r19} OPTIONAL -- Need M]]

[0158] The performed measurements are used for evaluation of CLTM.As explained earlier, cltm-ServingCellExecutionConditions includes the execution conditions for CLTM for the serving cell (PCell or PSCell) and the measurements according to the embodiment is used for evaluation of execution conditions.

[0159] In an embodiment herein, upon performing PCell L3 mobility, the UE 101 can release all the ltm-SK-Counters or equivalent variable in any other RAT.

[0160] In an embodiment herein, upon performing PCell L3 mobility, the network node 102 can configure the UE 101 to release the ltm-SK-Counters or equivalent variable in any other RAT. The network node 102 can send an ltm-SK-CounterConfigToReleaseList or equivalent to the UE 101, to release all the ltm-SK-Counter values. The network node 102 can send an LTM-NoSecurityChangeId or equivalent of all the SCG LTM candidate cells to the UE 101, for which ltm-SK-Counter values are configured.

[0161] FIG. 2 is a block diagram of a terminal or user equipment (UE). 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.

[0162] Referring to FIG. 2, the UE 101 may include at least one transceiver (hereinafter, referred to as simply “transceiver”) 201, at least one processor (hereinafter, referred to as simply “processor”) 202, and at least one memory (hereinafter, referred to as simply “memory”) 203. According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the transceiver 201, the processor 202, and the memory 203 of the UE 101 may operate. However, components of the UE 101 are not limited to the example components illustrated in FIG. 2. In another embodiment, the UE 101 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 201, the processor 202, or the memory 203 may be integrated in the form of one component.

[0163] The transceiver 201 may be a communication circuit or communication circuitry that enables the UE 101 to perform wireless communication with a node or an entity of a network. For example, the transceiver 201 may enable the UE 101 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 201 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 201 may include all subsequent generations of evolved wireless communications.

[0164] According to an embodiment, the transceiver 201 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 201 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 201 may output a signal received through a wireless channel to the processor 202 and may transmit, through a wireless channel, a signal output from the processor 202.

[0165] According to an embodiment, the UE 101 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 101 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 101 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 101 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).

[0166] The processor 202 may control general operations of the UE 101 according to embodiments of the disclosure. The processor 202 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processing operations. The processor 202 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 203, individually, collectively or in any combination thereof. Further, the processor 202 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.

[0167] The processor 202 may be electrically, operatively, and / or communicatively coupled to the transceiver 201 to control the transceiver 201.

[0168] The processor 202 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 202 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 202 may be included in one chip and the other part of the processor 202 may be included in another chip. Otherwise, at least one processor may be included in another component, for example, the transceiver 201 or the memory 203.

[0169] The processor 202 may perform or control or cause an operation of the UE 101 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 202 may control operations of the UE 101 for processing a downlink signal received from a BS or generating and transmitting an uplink signal to a BS. To this end, the processor 202 may execute a computer program, codes, or instructions stored in the memory 203, so as to control other components of the UE 101 to enable execution of various operations.

[0170] The memory 203 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 203 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.

[0171] The memory 203 may be electrically, operatively, and / or communicatively coupled to the processor 202 and may be accessed by the processor 202.

[0172] The memory 203 may store a computer program, codes, or instructions executable by the processor 202. According to an embodiment, a computer program, codes, or instructions executable by the processor 202 may be either stored in a single memory device or separated and stored in a distributed manner in two or more memory devices. By executing the instructions stored in the memory 203, the processor 202 may perform various functions according to an embodiment of the disclosure.

[0173] According to an embodiment of the disclosure, operations of the UE 101 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 203 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.

[0174] The UE 101 can perform the measurements for CLTM based on L3 measurements, if the UE 101 is configured with LTM execution conditions and the measurement identifier is indicated in the configured LTM execution conditions in the LTM candidate configuration for the serving cell (PCell or PSCell).

[0175] Consider that the UE 101 is performing L3 mobility from Cell1 to Cell2. The serving cell can be one of a Primary Cell (PCell), and a Primary Secondary Cell (PSCell). The processor 202 can check if the UE 101 is configured with LTM execution conditions and a measurement identifier is indicated in the configured LTM execution conditions in an LTM candidate configuration for a serving cell. If the UE 101 is configured with LTM execution conditions and a measurement identifier is indicated in the configured LTM execution conditions in an LTM candidate configuration for a serving cell, the processor 202 can perform measurements for CLTM based on L3 measurements. If the reportType for an associated reportConfig is condTriggerConfig, the measId is within an MCG VarMeasConfig and is indicated in an LTM-ExecutionCondition IE in an LTM candidate configuration of the PCell or PSCell, for each measId included in a measIdList within VarMeasConfig, the processor 202 can perform measurements for CLTM based on L3 measurements.

[0176] FIG. 3 is a flowchart depicting the process of managing mobility. In step 301, consider that the UE 101 is performing L3 mobility from Cell1 to Cell2. The serving cell can be one of a Primary Cell (PCell), and a Primary Secondary Cell (PSCell). In step 302, the UE 101 checks if it has been configured with LTM execution conditions and a measurement identifier is indicated in the configured LTM execution conditions in an LTM candidate configuration or LTM configuration for the serving cell. If the UE 101 is configured with LTM execution conditions and a measurement identifier is indicated in the configured LTM execution conditions in an LTM candidate configuration for a serving cell, in step 303, the UE 101 performs measurements for CLTM based on L3 measurements. If the reportType for an associated reportConfig is condTriggerConfig, the measId is within an MCG VarMeasConfig and is indicated in an LTM-ExecutionCondition IE in an LTM candidate configuration or LTM configuration of the PCell or PSCell, for each measId included in a measIdList within VarMeasConfig, the processor 202 can perform measurements for CLTM based on L3 measurements. The various actions in method 300 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 3 may be omitted.

[0177] FIG. 4 is a block diagram of a network node 102. The network node 102 may perform wireless communication with at least one terminal located within the area of the network node 102 through a wireless channel. The network node 102 may perform communication with a node or an entity of a network through wired or wireless communication.

[0178] Referring to FIG. 4, the network node 102 may include at least one transceiver (hereinafter, referred to as simply “transceiver”) 401, at least one processor (hereinafter, referred to as simply “processor”) 402, and at least one memory (hereinafter, referred to as simply “memory”) 403. According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the transceiver 401, the processor 402, and the memory 403 of the network node 102 may operate. However, components of the network node 102 are not limited to the exemplary components illustrated in FIG. 4. In another embodiment, the network node 102 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 401, the processor 402, or the memory 403 may be integrated in the form of one component.

[0179] The transceiver 401 may be a communication circuit or communication circuitry that enables the network node 102 to perform wireless communication with a node or an entity of a network. For example, the transceiver 401 may enable the network node 102 to transmit or receive a signal to or from the UE 101 through cellular communication, or to transmit or receive a signal to or from another network entity through wireless communication. For example, the transceiver 401 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 401 may include all subsequent generations of evolved wireless communications. According to an embodiment, the transceiver 401 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 401 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 401 may output a signal received through a wireless channel to the processor 402 and may transmit, through a wireless channel, a signal output from the processor 402.

[0180] Meanwhile, according to an embodiment of the present disclosure, the network node 102 may perform communication with a node or an entity of a network through wired or wireless communication. For example, the network node 102 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. 4, when the network node 102 performs wired communication, the network node 102 may further include a separate network interface for wired communication in addition to the transceiver 401. The network interface may be referred to as network interface circuitry or communication interface circuitry.

[0181] The processor 402 may control general operations of the network node 102 according to embodiments of the disclosure. The processor 402 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processing. The processor 402 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 403, individually, collectively or in any combination thereof. Further, the processor 402 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.

[0182] The processor 402 may be electrically, operatively, and / or communicatively coupled to the transceiver 401 to control the transceiver 401.

[0183] The processor 402 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 402 may be included in one chip and the other part of the processor 402 may be included in another chip. Otherwise, at least one processor may be included in another component, for example, the transceiver 401 or the memory 403.

[0184] The processor 402 may perform or control or cause an operation of the network node 102 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 402 may control operations of the network node 102 for generating and transmitting a downlink signal to a UE or processing an uplink signal received from a UE. Otherwise, the network node 102 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 402 may execute a computer program, codes, or instructions stored in the memory 403, so as to control other components of the network node 102 to enable execution of various operations.

[0185] The memory 403 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 403 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.

[0186] The memory 403 may be electrically, operatively, and / or communicatively coupled to the processor 402 and may be accessed by the processor 402.

[0187] The memory 403 may store a computer program, codes, or instructions executable by the processor 402. According to an embodiment, a computer program, codes, or instructions executable by the processor 402 may be either stored in a single memory device or separated and stored in a distributed manner in two or more memory devices. By executing the instructions stored in the memory 403, the processor 402 may perform various functions according to an embodiment of the disclosure.

[0188] According to an embodiment of the disclosure, operations of the network node 102 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 403 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.

[0189] The processor 402 can handle the security identifier of the UE 101 during L3 mobility. In an embodiment herein, the processor 402 can include the serving cell security identifier in a RRCReconfiguration message to the UE 101, when the UE 101 is performing L3 mobility. The RRCReconfiguration message can include ReconfigurationWithSync in a NR that triggers L3 mobility. In an embodiment herein, the processor 402 can release all LTM candidates for the UE 101, wherein the LTM candidate configuration includes the security identifier.

[0190] FIG. 5 is a flowchart depicting the process for handling the serving cell security identifier during L3 mobility. The network node 102 can handle the security identifier of the UE 101 during L3 mobility. In step 501, the UE 101 is performing L3 mobility. In step 502, the network node 102 includes the serving cell security identifier in a RRCReconfiguration message to the UE 101. The RRCReconfiguration message includes ReconfigurationWithSync in a NR that triggers L3 mobility. In an embodiment herein, the processor 402 can release all LTM candidates for the UE 101, wherein the LTM candidate configuration includes the security identifier. The various actions in method 500 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 5 may be omitted.

[0191] FIG. 6 is a flowchart depicting the process for handling the serving cell security identifier during L3 mobility. The network node 102 can handle the security identifier of the UE 101 during L3 mobility. In step 601, the UE 101 is performing L3 mobility. In step 602, the network node 102 releases all LTM candidates for the UE 101, wherein the LTM candidate configuration includes the security identifier. The various actions in method 600 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 6 may be omitted.

[0192] FIGs. 7A and 7B depict a process for enabling L3 mobility and LTM configuration for controlling security key change / PDCP reestablishment. Consider that the UE 101 is in Cell1, has LTM configuration, and is performing L3 mobility to Cell2 (step 701). In step 702, the UE 101 checks if Cell2 is an LTM candidate cell.

[0193] If Cell2 is an LTM candidate cell, in step 703, the UE 101 checks if the RRCReconfiguration applied at L3 mobility modifies LTM configuration and the LTM configuration includes ltm-ServingCellNoSecurityChangeID. If the RRCReconfiguration applied at L3 mobility modifies LTM configuration and the LTM configuration includes ltm-ServingCellNoSecurityChangeID, in step 704, the UE 101 stores ltm-ServingCellNoSecurityChangeID from modified LTM configuration in ltm-ServingCellNoSecurityChangeID within VarLTM-ServingCellNoSecurityChangeID. If the RRCReconfiguration applied at L3 mobility has not modified LTM configuration and / or the LTM configuration does not include ltm-ServingCellNoSecurityChangeID, in step 705, the UE 101 removes ltm-ServingCellNoSecurityChangeID in VarLTM-ServingCellNoSecurityChangeID (if present).

[0194] If Cell2 is not an LTM candidate cell, in step 706, the UE 101 checks if the Cell2 LTM candidate configuration includes ltm-NoSecurityChangeID. If the Cell2 LTM candidate configuration includes ltm-NoSecurityChangeID, in step 707, the UE 101 stores ltm-NoSecurityChangeID from cell2 LTM candidate configuration in the ltm-ServingCellNoSecurityChangeID in the VarLTM-ServingCellNoSecurityChangeID. If the Cell2 LTM candidate configuration does not include ltm-NoSecurityChangeID, in step 708, the UE 101 removes ltm-ServingCellNoSecurityChangeID in VarLTM-ServingCellNoSecurityChangeID (if present). The various actions in method 700 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 7 may be omitted.

[0195] FIG. 8 depicts the L3 mobility and conditional LTM procedure. Consider that the UE 101 is in Cell1, has LTM configuration, and is performing L3 mobility to Cell2 (step 801). In step 802, the UE 101 checks if the Cell2 LTM candidate cell and the LTM candidate configuration include the execution conditions for Conditional LTM. If the Cell2 LTM candidate cell and the LTM candidate configuration include the execution conditions for Conditional LTM, in step 803, the UE 101 evaluates the LTM cell switch conditions according to the execution conditions configured in the LTM candidate cell configuration of Cell2. The various actions in method 800 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 8 may be omitted.

[0196] FIG. 9 depicts the process of performing measurement for conditional LTM. In step 901, the UE 101 identifies the measurement identifiers within the measurement configuration and is indicated in an LTM execution condition of Pcell or PSCell and the report type is conditional trigger config. In step 902, the UE 101 performs the measurements for the measurement identifier. The various actions in method 900 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 9 may be omitted.

[0197] Embodiments herein reduce the signalling overhead of providing as the configuration can be stored and applied.

[0198] 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.

[0199] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the network elements. The elements include blocks which can be at least one of a hardware device, or a combination of hardware device and software module.

[0200] The embodiments disclosed herein describe methods and systems for managing interactions of Low-Layer Triggered Mobility (LTM) and Conditional Low-Layer Triggered Mobility (CLTM) with Layer 3 (L3) mobility in wireless communication networks. Therefore, it is understood that the scope of the protection is extended to such a program and in addition to a computer readable means having a message therein, such computer readable storage means contain program code means for implementation of one or more steps of the method, when the program runs on a server or mobile device or any suitable programmable device. The method is implemented in at least one embodiment through or together with a software program written in e.g., Very high speed integrated circuit Hardware Description Language (VHDL) another programming language, or implemented by one or more VHDL or several software modules being executed on at least one hardware device. The hardware device can be any kind of portable device that can be programmed. The device may also include means which could be e.g., hardware means like e.g., an ASIC, or a combination of hardware and software means, e.g., an ASIC and an FPGA, or at least one microprocessor and at least one memory with software modules located therein. The method embodiments described herein could be implemented partly in hardware and partly in software. Alternatively, the invention may be implemented on different hardware devices, e.g., using a plurality of CPUs.

[0201] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and / or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of embodiments and examples, those skilled in the art will recognize that the embodiments and examples disclosed herein can be practised with modification within the scope of the embodiments as described herein.

Claims

1.A method performed by a user equipment (UE) in a wireless communication system, the method comprising:receiving, from a base station, a radio resource control (RRC) message including a layer 1 / layer 2 triggered mobility (LTM) configuration;identifying whether a measurement identifier is indicated based on a LTM execution condition included in the LTM configuration; andperforming measurement for a conditional LTM (CLTM) based on layer 3 (L3) measurement associated with the measurement identifier, if the measurement identifier is indicated based on the LTM execution condition.2.The method of claim 1,wherein the measurement for the CLTM is performed if a report type for an associated reportConfig is condTriggerCoinfig and the measurement identifier is within a master cell group (MCG) VarMeasConfig, and the measurement identifier is indicated based on the LTM execution condition.3.The method of claim 1, further comprising:receiving, from the base station, an RRC reconfiguration message triggering an L3 mobility to a cell for which the LTM configuration is configured,wherein the RRC reconfiguration message including a ltm-ServingCellNoSecurityChangeID to update security configuration for the LTM configuration.4.The method of claim 1, further comprising:receiving, from the base station, an RRC reconfiguration message triggering an L3 mobility to a cell for which the LTM configuration is configured; andreleasing the LTM configuration or an LTM candidate configuration of the cell.5.A method performed by a base station in a wireless communication system, the method comprising:transmitting, to a user equipment (UE), a radio resource control (RRC) message including a layer 1 / layer 2 triggered mobility (LTM) configuration; andperforming measurement for a conditional LTM (CLTM) based on layer 3 (L3) measurement associated with a measurement identifier, if the measurement identifier is indicated based on an LTM execution condition included in the LTM configuration.6.The method of claim 5,wherein the measurement for the CLTM is performed if a report type for an associated reportConfig is condTriggerCoinfig and the measurement identifier is within a master cell group (MCG) VarMeasConfig, and the measurement identifier is indicated based on the LTM execution condition.7.The method of claim 5, further comprising:transmitting, to the UE, an RRC reconfiguration message triggering an L3 mobility to a cell for which the LTM configuration is configured,wherein the RRC reconfiguration message including a ltm-ServingCellNoSecurityChangeID to update security configuration for the LTM configuration.8.The method of claim 5, further comprising:transmitting, to the UE, an RRC reconfiguration message triggering an L3 mobility to a cell for which the LTM configuration is configured; andreleasing the LTM configuration or an LTM candidate configuration of the cell.9.A user equipment (UE) in a wireless communication system, the UE comprising:a transceiver; andat least one processor coupled with the transceiver and configured to:receive, from a base station, a radio resource control (RRC) message including a layer 1 / layer 2 triggered mobility (LTM) configuration;identify whether a measurement identifier is indicated based on a LTM execution condition included in the LTM configuration; andperform measurement for a conditional LTM (CLTM) based on layer 3 (L3) measurement associated with the measurement identifier, if the measurement identifier is indicated based on the LTM execution condition.10.The UE of claim 9,wherein the measurement for the CLTM is performed if a report type for an associated reportConfig is condTriggerCoinfig and the measurement identifier is within a master cell group (MCG) VarMeasConfig, and the measurement identifier is indicated based on the LTM execution condition.11.The UE of claim 9,wherein the at least one processor is further configured to receive, from the base station, an RRC reconfiguration message triggering an L3 mobility to a cell for which the LTM configuration is configured, andwherein the RRC reconfiguration message including a ltm-ServingCellNoSecurityChangeID to update security configuration for the LTM configuration.12.The UE of claim 9,wherein the at least one processor is further configured to:receive, from the base station, an RRC reconfiguration message triggering an L3 mobility to a cell for which the LTM configuration is configured; andrelease the LTM configuration or an LTM candidate configuration of the cell.13.A base station in a wireless communication system, the base station comprising:a transceiver; andat least one processor coupled with the transceiver and configured to:transmit, to a user equipment (UE), a radio resource control (RRC) message including a layer 1 / layer 2 triggered mobility (LTM) configuration; andperform measurement for a conditional LTM (CLTM) based on layer 3 (L3) measurement associated with a measurement identifier, if the measurement identifier is indicated based on an LTM execution condition included in the LTM configuration.14.The base station of claim 13,wherein the measurement for the CLTM is performed if a report type for an associated reportConfig is condTriggerCoinfig and the measurement identifier is within a master cell group (MCG) VarMeasConfig, and the measurement identifier is indicated based on the LTM execution condition.15.The base station of claim 13, further comprising:wherein the at least one processor is further configured to transmit, to the UE, an RRC reconfiguration message triggering an L3 mobility to a cell for which the LTM configuration is configured,wherein the RRC reconfiguration message including a ltm-ServingCellNoSecurityChangeID to update security configuration for the LTM configuration or the LTM configuration or an LTM candidate configuration of the cell is released.