Network coordination for tat acquisition in ltm

By configuring the UE with a TAT value in the TA acquisition process, the system addresses the challenge of invalid TAT in 3GPP 5G systems, enabling efficient RACH-less cell switch procedures and reducing latency and overhead.

WO2026235590A1PCT designated stage Publication Date: 2026-11-12TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/SE2026/050287
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-07
Filing Date
2026-04-30
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

In wireless communication systems, particularly in 3GPP 5G systems, the UE lacks a clear mechanism to determine whether a Time Alignment Timer (TAT) value is valid, leading to inefficiencies in RACH-less cell switch procedures due to the inability to start the TAT, which is crucial for conditional mobility processes.

Method used

A network node configures the UE with a Timing Advance (TA) acquisition configuration that includes a TAT value, allowing the UE to initiate the TAT before the mobility procedure, ensuring valid TA determination and supporting RACH-less cell switch.

Benefits of technology

This approach enables the UE to determine the validity of the TA value, facilitating RACH-less cell switch procedures, reducing latency, and improving performance while minimizing signaling overhead and energy consumption.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure SE2026050287_12112026_PF_FP_ABST
    Figure SE2026050287_12112026_PF_FP_ABST
Patent Text Reader

Abstract

Systems and methods are disclosed for Time Alignment Timer (TAT) acquisition for mobility. In one embodiment, a method performed by a User Equipment (UE) for conditional mobility comprises receiving, from a first network node, a configuration which comprises a Timing Advance (TA) acquisition configuration, one or more execution conditions, and a TAT value applicable for a candidate target cell for a conditional mobility procedure, wherein the candidate target cell belongs to a second network node. The method further comprises transmitting, to the second network node, a preamble message in the candidate target cell and receiving, from the first network node, a message including TA related information for the candidate target cell of the conditional mobility procedure. The method further comprises starting a TAT according to the TAT value received from the first network node.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] NETWORK COORDINATION FOR TAT ACQUISITION IN LTM

[0002] RELATED APPLICATIONS

[0003] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 801,492, filed May 7, 2025, the disclosure of which is hereby incorporated herein by reference in its entirety.

[0004] TECHNICAL FIELD

[0005] The present disclosure relates to a wireless communications system and, more specifically, to Time Alignment Timer (TAT) acquisition in a Radio Access Network (RAN) of a wireless communication system.

[0006] BACKGROUND

[0007] In a 3rdGeneration Partnership Project (3GPP) 5thGeneration (5G) system, Layer 1 (Ll) / Layer (2)-Triggered Mobility (LTM) is a procedure in which a next generation NodeB (gNB) receives LI measurement report(s) from a User Equipment (UE) and, on the basis of this LI measurement report(s), the gNB changes the UE’s serving cell by a cell switch command signaled via a Medium Access Control (MAC) Control Element (CE). The cell switch command indicates an LTM candidate configuration that the gNB previously prepared and provided to the UE through Radio Resource Control (RRC) signaling. Then, the UE switches to the target configuration according to the cell switch command. While it is not necessary for understanding the present disclosure, for more information, the interested reader is directed to 3GPP Technical Specification (TS) 38.300 (see, e.g., V18.0.0).

[0008] When configured by the network, it is possible to activate Transmission Configuration Indicator (TCI) states of one or multiple cells that are different from the current serving cell. This is sometimes called pre-activation of a candidate TCI state, since this is pre-activating a TCI state of an LTM candidate cell before the UE receives the LTM cell switch command i.e. before the LTM cell switch procedure. For instance, the TCI states of the LTM candidate cells can be activated in advance before any of those cells become the serving cell. This allows the UE to be downlink (DL) synchronized with those cells (or DL pre-sync), thereby facilitating a faster cell switch to one of those cells when cell switch is triggered.

[0009] Cell switch command is conveyed in a MAC CE, which contains the necessary information to perform the LTM cell switch. The overall procedure for LTM is shown in Figure 1.

[0010] As illustrated in Figure 1, the steps of the procedure for LTM are as follows:Step 1. The UE sends a MeasurementReport message to the gNB. The gNB decides to configure LTM and initiates LTM preparation.

[0011] Step 2. The gNB transmits an RRCReconfiguration message to the UE including the LTM candidate configurations.

[0012] Step 3. The UE stores the LTM candidate configurations and transmits an RRCReconfigurationComplete message to the gNB.

[0013] Step 4a. The UE performs DL synchronization with the candidate cell(s) before receiving the cell switch command. This is triggered upon reception by the UE of a “Candidate Cell TCI States Activation / Deactivation MAC CE” for LTM candidate cell(s) configured in CandidateTCL State and CandidateTCI-UL-State. Upon reception, in the UE’s MAC entity, the UE’s MAC entity receives a Candidate Cell TCI States Activation / Deactivation MAC CE on a Serving Cell, the UE indicates to lower layers the information regarding the Candidate Cell TCI States Activation / Deactivation MAC CE. Further details of this procedure can be found in 3GPP TS 38.321 (see, e.g., V18.0.0).

[0014] Step 5. The UE performs LI measurements on the configured candidate cell(s) and transmits LI measurement reports to the gNB. LI measurement should be performed as long as RRC reconfiguration (step 2) is applicable.

[0015] Step 6. The gNB decides to execute cell switch to a target cell and transmits a MAC CE triggering cell switch by including the candidate configuration index of the target cell. The UE switches to the target cell and applies the configuration indicated by candidate configuration index.

[0016] Step 7. The UE performs the random access procedure towards the target cell, if UE does not have valid TA of the target cell as specified in clause 6.1.3.xy of TS 38.321.

[0017] Step 8. The UE completes the LTM cell switch procedure by sending RRCReconfigurationComplete message to target cell. If the UE has performed a RA procedure in step 7 the UE considers that LTM cell switch execution is successfully completed when the random access procedure is successfully completed. For Random Access Channel (RACH)-less LTM, the UE considers that LTM cell switch execution is successfully completed when the UE determines that the network has successfully received its first UL data.

[0018] Conditional LTM (CLTM) is a procedure being specified in 3GPP Release 19. A UE may be configured with CLTM, which means the UE is configured with a CLTM candidate cell configuration (i.e. an RRCReconfiguration for the CLTM candidate cell) and an associated CLTM execution condition which is being monitored. When that CLTM execution condition is fulfilled, the UE executes CLTM i.e. by applying the RRC Reconfiguration associated to the CLTM candidate cell. For such a CLTM cell, the UE may have received a MAC CE from the network(e.g. from the serving cell) including a Timing Advance (TA) value for, before the CLTM execution, as agreed in RAN2 128:

[0019] In RAN2#129-bis meeting, the followings have been agreed related to Time Alignment Timer (TAT) for CLTM:

[0020] • C-LTM TAT for target cell is not stopped upon C-LTM cell switch execution to the target cell if it is running and starts the Primary Timing Advance Group (PTAG) using the remaining time from the C-LTM timer.

[0021] • C-LTM TAT for target cell is not stopped upon C-LTM cell switch execution to the target cell if it is running and starts the PTAG using the remaining time from the C-LTM timer. RAN3 has addressed the following topic, however, the need for future study remains. • Whether needs to indicate from Central Unit (CU) to source Distributed Unit (DU) and candidate DU when the cell is configured with L3 CLTM, separately from LI CLTM.

[0022] SUMMARY

[0023] Systems and methods are disclosed for Time Alignment Timer (TAT) acquisition for mobility. In one embodiment, a method performed by a User Equipment (UE) for conditional mobility comprises receiving, from a first network node, a configuration which comprises a Timing Advance (TA) acquisition configuration, one or more execution conditions, and a TAT value applicable for a candidate target cell for a conditional mobility procedure, wherein the candidate target cell belongs to a second network node. The method further comprises transmitting, to the second network node, a preamble message in the candidate target cell and receiving, from the first network node, a message including TA related information for the candidate target cell of the conditional mobility procedure. The method further comprises starting a TAT according to the TAT value received from the first network node. In this manner, the UE is provided the TAT for the candidate target cell in advance of execution of the conditional mobility procedure.

[0024] In one embodiment, the TAT value is comprised in the TA acquisition configuration. In one embodiment, the TAT value is comprised in the configuration separate from the TA acquisition configuration.

[0025] Corresponding embodiments of a UE are also disclosed. In one embodiment, a UE comprises a communication interface comprising a transmitter and a receiver. The UE further comprises processing circuitry associated with the communication interface, wherein the processing circuitry is configured to cause the UE to receive, from a first network node, aconfiguration which comprises a TA acquisition configuration, one or more execution conditions, and a TAT value, applicable for a candidate target cell for a conditional mobility procedure, wherein the candidate target cell belongs to a second network node. The processing circuitry is further configured to cause the UE to transmit, to the second network node, a preamble message in the candidate target cell and receive, from the first network node, a message including TA related information for the candidate target cell of the conditional mobility procedure. The processing circuitry is further configured to cause the UE to start a TAT according to the TAT value received from the first network node.

[0026] In one embodiment, the TAT value is comprised in the TA acquisition configuration or is comprised in the configuration separate from the TA acquisition configuration.

[0027] In another embodiment, a method performed by a UE for mobility comprises receiving, from a first network node, a mobility configuration for a candidate target cell that belongs to a second network node, wherein the mobility configuration comprises a TA related information applicable to the candidate target cell.

[0028] In one embodiment, the method further comprises receiving, from the first network node, one or more execution conditions for the mobility procedure.

[0029] In one embodiment, the mobility configuration is for a conditional mobility procedure, and the mobility configuration further comprises one or more execution conditions for the conditional mobility procedure.

[0030] In one embodiment, the mobility configuration comprises a TAT value applicable for the candidate target cell.

[0031] In one embodiment, the TA related information comprises a TAT value applicable for the candidate target cell.

[0032] In one embodiment, the method further comprises starting a TAT applicable to the candidate target cell according to the TAT value received from the first network node.

[0033] Corresponding embodiments of a UE are also disclosed. In one embodiment, a UE comprises a communication interface comprising a transmitter and a receiver. The UE further comprises processing circuitry associated with the communication interface, wherein the processing circuitry is configured to cause the UE to receive, from a first network node, a mobility configuration for a candidate target cell that belongs to a second network node, wherein the mobility configuration comprises TA related information applicable to the candidate target cell.

[0034] Embodiments of a method performed by a first network node are also disclosed. In one embodiment, a method performed by a first network node comprises transmitting a first message to a second network node that operates or otherwise handles a candidate target cell for a conditionalmobility procedure for a UE wherein the first message comprises a request to provide TA related information for the candidate target cell and receiving, from the second network node, a second message comprising the TA information for the candidate target cell. The method further comprises transmitting, to the UE, a mobility configuration for the candidate target cell, the mobility configuration comprising the TA related information for the candidate target cell.

[0035] In one embodiment, the TA information received from the second network node or the second message received from the second network node comprises a TAT value applicable to the candidate target cell.

[0036] In one embodiment, the first message further comprises a request to provide one or more execution conditions for the conditional mobility procedure, the second message comprises the one or more execution conditions for the conditional mobility procedure, and the mobility configuration comprises the one or more execution conditions for the conditional mobility procedure.

[0037] In one embodiment, the first network node transmits to the second network node in the first message an indicator to request Layer 1 (LI) or Layer 3 (L3) execution conditions.

[0038] In one embodiment, the first network node transmits to the second network node an explicit indicator to perform a TA acquisition procedure for the candidate target cell.

[0039] In one embodiment, in the mobility configuration or in a separate configuration, the first network node configures the UE with one or more execution conditions for the conditional mobility procedure and a configuration for performing a TA acquisition procedure for the candidate target cell.

[0040] In one embodiment, the request for the TA related information comprises an explicit indication to provide a TAT value to be provided to the UE.

[0041] In one embodiment, the first network node further sends, to the second network node, a separate request for a TAT value applicable to the candidate target cell to be provided to the UE.

[0042] In one embodiment, the first network node further sends, to the second network node, a request to provide a TAT value applicable to the candidate target cell to be provided to the UE, wherein the request to provide the TAT value is independent from the request to provide TA related information or conditional execution.

[0043] In one embodiment, the first network node further sends, to the second network node, a request to provide a TAT value applicable to the candidate target cell to be provided to the UE, wherein the request to provide a TAT value is included within the request to provide one or more execution conditions for the mobility procedure. In one embodiment, the request to provide a TAT value for the UE is only included in case Layer 1 (LI) execution conditions are requested, therequest to provide a TAT value for the UE is only included in case Layer 3 (L3) execution conditions are requested, or the request to provide a TAT value for the UE is included regardless of whether LI or L3 execution conditions are requested.

[0044] In one embodiment, the first network node provides an indication to the UE to initiate a TA acquisition procedure in the candidate target cell.

[0045] In one embodiment, the first network node transmits to the UE a TAT value for the candidate target cell within the mobility configuration or in a separate message.

[0046] In one embodiment, the first network node transmits to the UE a TAT value for the candidate target cell, wherein the TAT value included within a TA acquisition configuration transmitted to the UE.

[0047] In one embodiment, the first network node receives a TAT value for the candidate target cell from second network node within a container.

[0048] In one embodiment, the first network node receives a TAT value for the candidate target cell from second network node in an explicit way.

[0049] In one embodiment, the first message and the second message are transmitted and received by the first network node using one or more F1AP procedures.

[0050] In one embodiment, the first message and the second message are transmitted and received by the first network node using one or more XnAP procedures.

[0051] Corresponding embodiments of a first network node are also disclosed. In one embodiment, a first network node comprises a communication interface and processing circuitry associated with the communication interface. The processing circuitry is configured to cause the first network node to transmit a first message to a second network node that operates or otherwise handles a candidate target cell for a conditional mobility procedure for a UE wherein the first message comprises a request to provide TA related information for the candidate target cell and receive, from the second network node, a second message comprising the TA information for the candidate target cell. The processing circuitry is further configured to cause the first network node to transmit, to the UE, a mobility configuration for the candidate target cell, the mobility configuration comprising the TA related information for the candidate target cell.

[0052] Embodiments of a method performed by a second network node are also disclosed. In one embodiment, a method performed by a second network node that operates or otherwise controls a candidate target cell for a conditional mobility procedure for a UE comprises receiving, from a first network node, a first message comprising a request to provide TA related information for the candidate target cell and transmitting, to the first network node, a second message comprising the requested TA information.In one embodiment, the TA information transmitted to the first network node in the second message comprises a TAT value applicable to the candidate target cell.

[0053] In one embodiment, the TA information transmitted to the first network node in the second message comprises one or more TA values.

[0054] In one embodiment, the method further comprises determining whether to provide a TAT value for the candidate target cell to the first network node to be forwarded to the UE. In one embodiment, the method further comprises, responsive to determining to provide a TAT value for the candidate target cell to the first network node to be forwarded to the UE, transmitting the TAT value to the first network node. In another embodiment, the method further comprises, responsive to determining to provide a TAT value for the candidate target cell to the first network node to be forwarded to the UE, including the TAT value for the candidate target cell within the TA information transmitted to the first network node in the second message or in the second message transmitted to the first network node.

[0055] In one embodiment, the first message further comprises a request for one or more execution conditions for the mobility procedure, and the second message further comprises the requested one or more execution conditions for the mobility procedure.

[0056] In one embodiment, the first message further comprises a request to provide one or more execution conditions for the mobility procedure that comprises one or both of the following: an indication to provide LI execution conditions and an indication to provide L3 execution conditions.

[0057] In one embodiment, the request to provide the TA related information comprises an explicit request to configure a TAT value within a TA acquisition configuration for the UE.

[0058] In one embodiment, the request to provide the TA related information comprises a request to include a TAT value within the TA related information.

[0059] In one embodiment, the method further comprises determining whether to provide a TAT value for the candidate target cell to the first network node to be forwarded to the UE, wherein the determining comprises implicitly determining that a TAT value is to be provided within a TA acquisition configuration for the UE based on a presence of a request to provide one or more execution conditions for the mobility procedure.

[0060] In one embodiment, the second network node provides the TAT value for the candidate target cell to the first network node within a container.

[0061] In one embodiment, the second network node provides the TAT value for the candidate target cell to the first network node in an explicit way.In one embodiment, the method further comprises determining whether to provide a TAT value for the candidate target cell to the first network node to be forwarded to the UE, wherein the determining comprises implicitly determining that a TAT value is requested based on a presence of a request to provide LI execution conditions for the mobility procedure.

[0062] In one embodiment, the method further comprises determining whether to provide a TAT value for the candidate target cell to the first network node to be forwarded to the UE, wherein the determining comprises implicitly determining that a TAT value is requested based on the presence of the request to provide L3 execution conditions for a mobility procedure.

[0063] In one embodiment, the method further comprises determining whether to provide a TAT value for the candidate target cell to the first network node to be forwarded to the UE, wherein the determining comprises implicitly determining that a TAT value is requested based on receiving an indication that Conditional LTM is being prepared.

[0064] In one embodiment, the method further comprises determining whether to provide a TAT value for the candidate target cell to the first network node to be forwarded to the UE, wherein the determining comprises implicitly determining that a TAT value is requested based on receiving an indication that Conditional LTM is being prepared and one of LI execution conditions or L3 execution conditions are not requested.

[0065] In one embodiment, a TAT value sent from the second network node to the first network node in the second message is provided for the specific UE.

[0066] In one embodiment, a TAT value sent from the second network node to the first network node in the second message is provided for a specific UE and a group of cells.

[0067] In one embodiment, the second network node transmits a TAT value to the first network node in response to receiving a request for the TAT value.

[0068] In one embodiment, the first message is received and the second message is transmitted using one or more F1AP procedures.

[0069] In one embodiment, the first message is received and the second message is transmitted using one or more XnAP procedures.

[0070] Corresponding embodiments of a second network node are also disclosed. In one embodiment, a second network node for operation or control of a candidate target cell for a conditional mobility procedure for a UE the second network node comprises a communication interface and processing circuitry associated with the communication interface. The processing circuitry is configured to cause the second network node to receive, from a first network node, a first message comprising a request to provide TA related information for the candidate target celland transmit, to the first network node, a second message comprising the requested TA information.

[0071] Embodiments of a method performed by a third network node are also disclosed. In one embodiment, a method performed by a third network node comprises transmitting to a first network node that operates or controls a source or serving cell of a UE a message comprising TAT information per cell for one or more cells.

[0072] In one embodiment, the message is transmitted using one or more F1AP procedures. In one embodiment, the one or more cells comprise one or more candidate target cells for a mobility procedure for a UE where the one or more candidate target cells are operated or controlled by a second network node.

[0073] Corresponding embodiments of a third network node are also disclosed. In one embodiment, a third network node comprises a communication interface and processing circuitry associated with the communication interface. The processing circuitry is configured to cause the first network node to transmit to a first network node that operates or controls a source or serving cell of a UE a message comprising TAT information per cell for one or more cells.

[0074] BRIEF DESCRIPTION OF THE DRAWINGS

[0075] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0076] Figure 1 illustrates the Layer 1 (LI) / Layer 2 (L2) Triggered Mobility (LTM) procedure in 3rdGeneration Partnership Project (3GPP) 5thGeneration (5G) New Radio (NR).

[0077] Figure 2 is a flow chart that illustrates a procedure performed by a first network node to determine whether to configure a Time Alignment Timer (TAT) value for a mobility procedure for a User Equipment (UE), in accordance with an embodiment of the present disclosure.

[0078] Figure 3 is a flow chart that illustrates the operation of a second network node to determine whether to configure a TAT value for a conditional mobility procedure to a UE, where the candidate target cell is handled by the second network node, in accordance with an embodiment of the present disclosure.

[0079] Figure 4 is a flow chart that illustrates the operation of a third network node to provide TAT to a candidate target cell of a conditional mobility procedure for a UE, where the candidate target cell is operated by (or otherwise belongs to or is handled by) a second network node, in accordance with an embodiment of the present disclosure.Figure 5 is a flow chart that illustrates the operation of a UE for performing Timing Advance (TA) acquisition for a candidate target cell of a mobility procedure, in accordance with an embodiment of the present disclosure.

[0080] Figure 6 is a flow chart that illustrates the operation of a UE, in accordance with another embodiment of the present disclosure.

[0081] Figure 7 shows an example of a communication system in accordance with some embodiments.

[0082] Figure 8 is another example of a communication system according to some embodiments. Figure 9 shows a wireless device, which may be configured to operate in communication system of Figure 7 or in communication system of Figure 8.

[0083] Figure 10 shows a network node in accordance with some embodiments.

[0084] Figure 11 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.

[0085] DETAILED DESCRIPTION

[0086] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0087] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0088] There currently exist certain challenge(s). Based on the Radio Access Network Working Group 2 (RAN2) discussion in 3rdGeneration Partnership Project (3GPP), a User Equipment (UE) can be configured to support conditional execution using both Layer 1 (LI) measurements (LI execution conditions) and Layer 3 (L3) measurements (L3 execution conditions) for the same candidate cell. Regardless on the execution condition provided (LI or L3), each candidate cell needs to provide a Time Alignment Timer (TAT) value to the UE because, when a Timing Advance (TA) value is received, the UE needs to start a TAT according to the TAT value configured by the candidate cell.

[0089] At the moment, a candidate cell does not understand whether it needs to configure a TAT value, as this is dependent on how the execution conditions are requested / configured on thenetwork node. However, if the TAT value is not provided to the UE, the UE would not be able to start the TAT and thus it would not be able to determine whether a TA value is still valid or not. The outcome will be that UE considers the TA value always as invalid (since the TAT cannot be started) and thus no Random Access Channel (RACH)-less cell switch procedure can be supported.

[0090] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Systems and methods are disclosed herein for managing TA and TAT in mobility procedures, such as conditional handover. A first network node obtains TA information and, optionally, execution conditions from a second network node. The first network node then uses this information to configure the UE with relevant mobility parameters, including TA and TAT. The UE, upon receiving the configuration, transmits a preamble in the candidate target cell, obtains the TA value, and initiates the TAT to ensure proper uplink time alignment.

[0091] Certain embodiments may provide one or more of the following technical advantage(s). Embodiments of the solutions proposed herein allow a candidate cell to understand whether a TAT value should be provided at the UE as part of the early synchronization configuration. This allows the UE to be able to start the TAT and thus determine whether a TA value is still valid or not. If the UE is able to determine whether a TA value is valid or not, the RACH-less cell switch procedure can be supported and thus the latency of the procedure will be reduced. Performance will thereby be improved and signaling overhead and energy will be also reduced.

[0092] The description herein refers to the term “L1 / L2 based inter-cell mobility” as used in the Work Item Description in 3GPP, though it interchangeably uses the terms L1 / L2 mobility, Ll-mobility, LI based mobility, Ll / L2-centric inter-cell mobility, L1 / L2 inter-cell mobility L1 / L2-Triggered Mobility, Lower-layer triggered Mobility, or LTM. The basic principle is that the UE receives a lower layer signaling from the network indicating to the UE a change (or switch or activation) of its serving cell (e.g. change of Primary Cell (PCell), from a source to a target PCell), wherein a lower layer signaling is a message / signaling of a lower layer protocol, which may be referred as a L1 / L2 inter-cell mobility execution command or LTM cell switch command. The change of serving cell (e.g. change of PCell) may also lead to a change in Secondary Cell(s) (SCell(s)) for the same cell group e.g. in case the command triggers the UE to change to another cell group configuration of the same type (e.g. another Master Cell Group (MCG) configuration). Before the UE receives the LTM cell switch command, the UE is configured by the network with one or more LTM candidate cell configurations (e.g. reception of a Radio Resource Control (RRC) Reconfiguration message, with at least one LTM candidate cell configuration) A LTM candidate cell configuration may include parameters in the Information Element (IE) CellGroupConfig per candidate cell and / or an embedded RRC Reconfiguration per LTM candidate cell. In onealternative, the lower layer command may also correspond a light version of an RRC message, such as an RRC message with a limited number of fields or parameters which indicates to the UE to apply a stored RRC configuration associated to an LTM candidate cell.

[0093] The term “LTM cell switch procedure” as used herein refers to the process of a UE switching (or changing) its cell from a source cell to a target cell (which may be called here an LTM candidate cell or a neighbor cell), using Ll / L2-triggered mobility (LTM). In the context of LTM, an LTM cell switch procedure may sometimes also be known as L1 / L2 based inter-cell mobility execution, LTM execution, dynamic switch, LTM switch, (LTM) cell switch, (LTM) serving cell change, or (LTM) cell change. In the context of the present disclosure, switching to the LTM candidate cell configuration comprises the UE considering that an LTM candidate cell becomes its new special cell (SpCell) e.g. PCell in case of LTM being configured for a MCG and / or PSCell in case of LTM being configured for a Secondary Cell Group (SCG); or, changing its SpCell from the current PCell to an LTM candidate cell.

[0094] Even if the term “change of cell” is used, that may comprise a change of a whole cell group configuration, which includes a change in the SpCell (e.g. change of PCell or change of PSCell) and a change in SCells of the cell group (e.g. addition, modification and / or release of one or more SCells).

[0095] An LTM cell switch procedure may be triggered in the UE by reception of an LTM cell switch command or alternatively triggered by some other event such as a condition, e.g., a triggering condition used for conditional configuration such as conditional handover, being fulfilled, as a result of recovery from radio link failure or handover failure.

[0096] As used herein, the term “LTM candidate cell” refers to a cell the UE is configured with when configured with L1 / L2 -triggered mobility. That is a cell the UE can move to in an LTM cell switch procedure, upon reception of an LTM cell switch command. These cells may also be called candidate cell(s), candidates, mobility candidates, non-serving cells, additional cells, candidate target cell, candidate target, etc. An LTM candidate cell is a cell on which the UE performs measurements (e.g. Channel State Information (CSI) measurements) so that the UE reports these measurements and the network may make an educated decision on which beam (e.g. Transmission Configuration Indication (TCI) state) and / or cell the UE is to be switched to. An LTM candidate cell may be a candidate to be a target PCell or PSCell, or an SCell of a cell group (e.g. MCG SCell).

[0097] The description herein refers to Conditional LTM (CLTM), which can be viewed as a form of conditional reconfiguration. In CLTM, the UE is configured with at least one LTM candidate cell (denoted as a CLTM candidate cell) by receiving an LTM candidate cell configuration (as inlegacy LTM) which is referred to herein a Conditional LTM candidate cell configuration, and an associated execution condition referred to herein as an CLTM execution condition. The evaluation of CLTM execution condition associated to a CLTM candidate cell is performed by the assessment of lower layer measurements, such as Layer 1 Reference Signal Received Power (Ll-RSRP) and / or Synchronization Signal (SS) Reference Signal Received Power (SS-RSRP), derived from Synchronization Signal Blocks (SSBs) and / or Channel State Information Reference Signals (CSL RSs) of either the source cell and / or an LTM candidate cell. Lower layer measurements, in this context, are measurements reported to support lower layer procedures like beam management, candidate cell TCI state activation / deactivation, early timing advance (TA) acquisition, and link adaptation, and they are not filtered based on Layer 3 (L3) parameters, though there may or may not be some filtering of these measurements based on the other lower layer parameters. The reception of CLTM execution condition may also involve receiving an indication of the condition and / or configuring it with parameters such as event identifier(s), offset(s), threshold(s), reference signal (RS) type, trigger quantity such as Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ) or Signal-to-Interference-plus-Noise Ratio (SINR), Time-To-Trigger (TTT), and so forth.

[0098] In the context of CLTM, the UE relies on evaluating one or two condition(s), referred to as CLTM execution condition(s), LTM execution condition(s), or triggering condition(s), or a combination thereof. And, when the condition(s) for a CLTM candidate cell is fulfilled, the UE performs a cell switch, which may be seen as a kind of LTM execution which is not triggered by the reception of an LTM cell switch command; this may also be considered as a kind of LTM cell switch, or LTM cell switch execution, or Conditional LTM cell switch, or Conditional LTM execution, or CLTM execution, or simply cell switch. According to the methods outlined in the present disclosure, upon satisfaction of the execution condition(s), the UE initiates an LTM cell switch. The term LTM cell switch refers to the process of a UE changing its cell from a source cell to a target cell, using L1 / L2 triggered mobility (LTM). In the context of Conditional LTM execution, the text may refer to the serving cell before the LTM cell switch as source cell, old source cell, or previous source cell.

[0099] The description herein uses the term “conditional LTM” or “conditional LTM candidate configuration” which is used to identify a configuration for which the UE is provided with certain criteria which the UE needs to evaluate by itself. Upon the fulfilling of these one or more criteria the UE executes autonomously a conditional LTM cell switch procedure and applies the provided conditional LTM candidate configuration without the network indicating to do so. The text also uses the term “normal LTM” or “normal LTM candidate configuration” which is used to identifyan LTM candidate configuration which the UE applies only upon an indication from the network to trigger an LTM cell switch execution.

[0100] The description also refers to an LTM candidate cell within the framework of Conditional LTM. The candidate cell may be referred to as a CLTM candidate cell, CLTM cell, simply candidate cell, candidate target cell, simply target cell, LTM candidate cell, LTM cell, L1 / L2 intercell mobility candidate cell, depending on the context or terminology used in the present disclosure. Essentially, it denotes a cell to which the UE is directed or switches to in the event of executing a conditional L1 / L2 inter-cell mobility procedure after meeting the associated execution condition(s) and may also be termed as new source cell or next source cell after the LTM cell switch. These cells may also be termed as candidate cells, mobility candidates, non-serving cells, additional cells, candidate target cell, simply target cell or deactivated cells. An LTM candidate cell might also pertain to a candidate cell in a 5thGeneration (5G) Radio Access Technology like New Radio (NR) or a future 6thGeneration (6G) Radio Access Technology.

[0101] For simplicity, the description may use the term “network” to generally refer to a network entity or network node from which the UE receives one or more configurations and / or parameters, such as LTM candidate(s), and CLTM candidate(s).

[0102] Figure 2 is a flow chart that illustrates a procedure performed by a first network node to determine whether to configure a TAT value for a mobility procedure for a UE, in accordance with an embodiment of the present disclosure. The first network node may be, for example, a source or serving Radio Access Network (RAN) node such as a source or serving base station (e.g., a source or serving gNB), a source or serving Distributed Unit (DU) in a base station (e.g., gNB) having a split Central Unit (CU) and DU architecture, a source or serving CU, or a source or serving Master Node (MN), or a source or serving Secondary Node (SN). The procedure of Figure 2 includes the following steps or actions:

[0103] • Step 200: The first network node transmits, to a second network node, a message including a request to provide Timing Advance (TA) related information and optionally a request to provide one or more execution conditions for a mobility procedure. For example, the TA related information includes TA related information for a mobility procedure to a cell (referred to here a candidate target cell) for a mobility procedure for a UE. Likewise, the one or more execution conditions include one or more execution conditions for the mobility procedure to the candidate target cell. The TA related information includes, for example, a TAT value and / or a TA value for the candidate target cell. Note that the second network node may be, for example, a target or candidate RAN node such as a target or candidatebase station (e.g., a target or candidate gNB), a target or candidate DU, a target or candidate CU, a target MN, or a target SN.

[0104] • Step 202: The first network node receives (e.g., in response to the message / request(s) of Step 200), from the second network node, a message including the requested TA related information for the candidate target cell and optionally the requested one or more execution conditions for the mobility procedure.

[0105] • Step 204: The first network node transmits, to the UE, a mobility configuration for the candidate target cell that belongs to the second network node, where the mobility configuration includes the received TA related information and optionally the one or more the execution conditions.

[0106] In one example embodiment, the first network node is a CU of a base station (e.g., a gNB-CU of a certain gNB) and the second network node is a DU of the same base station (e.g., a gNB-DU of the same gNB). The source or serving cell for the UE is served by a different DU of the same base station. In this case, the first network node may transmit the mobility configuration to the UE in Step 204 by transmitting the mobility configuration to the DU of the source or serving cell of the UE, where this DU then transmits the mobility configuration to the UE.

[0107] The first network node may send to the second network node (e.g., in Step 200) an indicator, for example, to request LI and / or L3 execution conditions. For example, this indicator may indicate that the first network node is requesting one or more LI execution conditions, that the first network node is requesting one or more L3 execution conditions, or that the first network node is requesting both LI and L3 execution conditions. In addition or alternatively, the first network node may send to the second network node (e.g., in Step 200 or in a separate step) an explicit indicator to perform a TA acquisition procedure for the candidate target cell.

[0108] In one embodiment, the first network node configures the UE with execution conditions and a configuration for performing the TA acquisition procedure for the candidate target cell. This may be done via the mobility configuration of Step 204, via a separate configuration for the TA acquisition procedure (in which the execution condition(s) are included), or via a combination of the mobility configuration (e.g., including the execution conditions) and a separate configuration for the TA acquisition procedure.

[0109] In one embodiment, the request for the TA related information in Step 200 includes an explicit indication (i.e., a request) to provide a TAT value to be provided to the UE.

[0110] In one embodiment, the request to provide a TAT value for the UE is independent of the request to provide TA related information or conditional execution. This means that, in one embodiment, the request to provide a TAT value for the UE is a standalone request.In one embodiment, the request to provide a TAT value for the UE is included within the request to provide execution conditions for a mobility procedure. More specifically:

[0111] • In one example, the request to provide a TAT value for the UE is only included in case LI execution conditions are requested.

[0112] • In another example, the request to provide a TAT value for the UE is only included in case L3 execution conditions are requested.

[0113] • In another example, the request to provide a TAT value for the UE is included regardless of whether LI or L3 execution conditions are requested.

[0114] In one embodiment, the first network node provides an indication to the UE to initiate the TA acquisition procedure in the candidate target cell. This indication to initiate the TA acquisition procedure may be included in or together with the mobility configuration of Step 204 or may be separate from the mobility configuration of Step 204.

[0115] In one embodiment, the first network node transmits to the UE the received TAT value received from the second network node (e.g., in the mobility configuration of Step 204, e.g., as part of the TA related information or in a separate message).

[0116] In one embodiment, the TAT value is part of a TA acquisition configuration transmitted to the UE.

[0117] In one embodiment, the first network node receives the TAT value from second network node (e.g., as part of the requested TA related information of Step 204) within a container (e.g., as an OCTET STRING).

[0118] In one embodiment, the TAT value is received by the first network node from second network node (e.g., as part of the requested TA related information of Step 204) in an explicit way (e g., as an ENUMERATED or as an INTEGER value).

[0119] In one embodiment, the procedure between the first network node and the second network node (e.g., steps 200 and 202) uses one or more F1AP procedures, e.g., UE Context Setup Request, and / or UE Context Modification Request, and / or a new F1AP procedure. For example, the message of Step 200 may be a UE Context Setup Request or a UE Context Modification Request, and the message of Step 202 may be a UE Context Setup Response or a UE Context Modification Response.

[0120] In one embodiment, the procedure between the first network node and the second network node (e.g., in Steps 200 and 202) uses one or more XnAP procedures, e.g., Handover Request, and / or LTM Configuration Update, and / or a new XnAP procedure.

[0121] Figure 3 is a flow chart that illustrates the operation of a second network node to determine whether to configure a TAT value for a conditional mobility procedure to a UE, where thecandidate target cell is handled by the second network node, in accordance with an embodiment of the present disclosure. The second network node may be, for example, a target or candidate RAN node such as a target or candidate base station (e.g., a target or candidate gNB), a target or candidate DU, a target or candidate CU, a target MN, or a target SN. The procedure of Figure 3 includes the following steps or actions:

[0122] • Step 300: The second network node receives, from the first network node, a request to provide TA related information, e.g., TA values, TAT, etc. (e.g., for a candidate target cell operated by or otherwise belonging to the second network node) and optionally a request to provide one or more execution conditions for a mobility procedure. This corresponds to Step 200 of Figure 2, but from the perspective of the second network node.

[0123] • Step 302 (Optional): The second network node determines whether to provide (e.g., as part of the requested TA related information) a TAT value to the first network node to be forwarded to the UE.

[0124] • Step 304: The second network node transmits, to the first network node, a message including the requested TA related information (which may include a TAT value) and optionally one or more execution conditions for a mobility procedure.

[0125] In one embodiment, the request to provide one or more execution conditions can be a request which includes one or more of the following:

[0126] • An indication to provide LI execution conditions,

[0127] • An indication to provide L3 execution conditions.

[0128] In one embodiment, the request received in Step 300 to provide the TA related information further includes an explicit request to configure a TAT value within the TA related information (e.g., within a TA acquisition configuration) for the UE. The determination made in Step 302 may, for example, be based on whether this explicit indication is received.

[0129] In one embodiment, the second network node determines (e.g., in Step 302) implicitly that a TAT value should be provided within the requested TA related information (e.g., within a TA acquisition configuration) based on the presence of the request to provide one or more execution conditions for a mobility procedure.

[0130] • In one example, if the second network node receives the request to provide execution conditions, this means that the second network node always includes a TAT value within the TA acquisition procedure (or within a TA acquisition configuration for the UE or within the TA related information).

[0131] • In one example, if the second network node does not receive any request to provide execution conditions, this means that the second network node does not include a TATvalue within the TA acquisition procedure (or within a TA acquisition configuration for the UE or within the TA related information).

[0132] In one embodiment, the TAT value is sent to the first network node (e.g., in Step 304, e.g., as part of the TA related information) within a container (e.g., as an OCTET STRING).

[0133] In one embodiment, the TAT value is sent to the first network node (e.g., in Step 304, e.g., as part of the TA related information) in an explicit way (e.g., as an ENUMERATED or as an INTEGER value).

[0134] In one embodiment, the second network node determines implicitly that a TAT value is requested (e.g., in Step 302) based on the presence of the request (e.g., in Step 300) to provide LI execution conditions for a mobility procedure.

[0135] In one embodiment, the second network node determines (e.g., in Step 302) implicitly that a TAT value is requested based on the presence of the request (e.g., in Step 300) to provide L3 execution conditions for a mobility procedure.

[0136] In one embodiment, the second network node determines (e.g., in Step 302) implicitly that a TAT value is requested based on receiving an indication that Conditional LTM is being prepared.

[0137] In one embodiment, the second network node determines (e.g., in Step 302) implicitly that a TAT value is requested based on receiving an indication that Conditional LTM is being prepared and one of LI execution conditions or L3 execution conditions are not requested.

[0138] In one embodiment, the TAT value (e.g., within the TA acquisition configuration or within the requested TA related information or within a TA acquisition configuration included in the requested TA related information) is provided for a specific UE.

[0139] In one embodiment, the TAT value (e.g., within the TA acquisition configuration or within the requested TA related information or within a TA acquisition configuration included in the requested TA related information) is provided for a specific UE and a group of cells.

[0140] In one embodiment, the TAT value is transmitted to the first network node after receiving a request for it (e.g., in the message of Step 300).

[0141] In one embodiment, the procedure between the first network node and the second network node (e.g., in Steps 300 and 304) uses one or more F1AP procedures, e.g., UE Context Setup Request and Response, and / or UE Context Modification Request and Response, and / or a new F1AP procedure.

[0142] In one embodiment, the procedure between the first network node and the second network node (e.g., in Steps 300 and 304) uses one or more XnAP procedures, e.g., Handover Request Acknowledge, and / or LTM Configuration Update Acknowledge, and / or a new XnAP procedure.Figure 4 is a flow chart that illustrates the operation of a third network node to provide TAT to a candidate target cell of a conditional mobility procedure for a UE, where the candidate target cell is operated by (or otherwise belongs to or is handled by) a second network node, in accordance with an embodiment of the present disclosure. The third network node may be a RAN node such as, e.g., a base station (e.g., gNB), a CU (e.g., a gNB-CU), a source MN, or a source SN. The procedure of Figure 4 includes the following step or action.

[0143] • Step 400: The third network node transmits, to a first network node, a message including Time Alignment Timer information per cell.

[0144] In one embodiment, the procedure between the third network node and the first network node uses one or more F1AP procedures, e.g., CU-DU TA Information Transfer, and / or a new Class 2 F1AP procedure.

[0145] Figure 5 is a flow chart that illustrates the operation of a UE for performing Timing Advance (TA) acquisition for a candidate target cell of a mobility procedure, in accordance with an embodiment of the present disclosure. As illustrated, the procedure of Figure 5 includes the following actions or steps:

[0146] • Step 500: The UE receives, from a first network node, a configuration which comprises a TA acquisition configuration, one or more execution conditions, and a TAT value (which can also be included within the TA acquisition configuration). This information is for or otherwise applicable to a candidate target cell of the conditional mobility procedure, where the candidate target cell is operated by (or otherwise belonging to) a second network node.

[0147] • Step 502: The UE transmits, to the second network node, a preamble message in the candidate target cell.

[0148] • Step 504: The UE receives, from the first network node, a message including TA related information for the candidate target cell of the conditional mobility procedure.

[0149] • Step 506: The UE starts a TAT (e.g., for the candidate target cell) according to the TAT value received from the first network node.

[0150] Figure 6 is a flow chart that illustrates the operation of a UE, in accordance with another embodiment of the present disclosure. As illustrated, the procedure of Figure 6 includes the following actions or steps:

[0151] • Step 600: The UE receives, from a first network node, a mobility configuration for a candidate target cell for a conditional mobility procedure where the candidate target cell is operated by (or otherwise belongs to) a second network node. The mobility configuration information includes TA related information (e.g., a TAT value applicable for the candidate target cell) and optionally one or more execution conditions for the mobility procedure.• Step 602 (Optional): The UE transmits, to the second network node, a preamble message in the candidate target cell.

[0152] • Step 604: The UE starts a TAT (e.g., for the candidate target cell) according to the TAT value received from the first network node.

[0153] Now, additional embodiments will be described that relate to synchronizing candidate cells on TAT value.

[0154] In one embodiment, one of the first network node (such as a source gNB or a serving gNB or a source DU or a serving DU, or a source CU, or a serving CU, or a source MN, or a source SN) or the third network node (such as a gNB, or a gNB-CU, or a source MN, or a source SN), after receiving from a given second network node (such as a target gNB or a candidate gNB, or a target DU or a candidate DU, or a target gNB-CU, or a candidate gNB-CU, or a target MN, or a target SN) the Timing Advance Time for cells of the second network node, sends the received time alignment timer (TAT) to one or more other second network nodes.

[0155] - In one example, the source gNB (first network node) receives from a given candidate gNB (one second network node), the TAT value for at least one candidate cell of the second network node, and then it sends the received TAT value to one or more other candidate gNBs (i.e. “other” second network nodes). For instance, gNBl is the source gNB, gNB2, gNB3 and gNB4 are candidate (or second) network nodes. The gNBl receives the TAT value for a cell of gNB2, and then it sends that TAT value to gNB3 and gNB4.

[0156] - In another example the source MN (first network node) receives from a given candidate MN (one second network node), the TAT value for at least one candidate cell of the second network node, and then it sends the received TAT value to one or more other candidate MNs (i.e. “other” second network nodes). For instance, gNBl is the source MN, gNB2, gNB3 and gNB4 are candidate (or second) network nodes. The gNBl receives the TAT value for a cell of gNB2, and then it sends that TAT value to gNB3 and gNB4.

[0157] - In another example the source CU (first network node) receives from a given candidate DU (one second network node), the TAT value for at least one candidate cell of the second network node, and then it sends the received TAT value to one or more other candidate DUs controlled by the source CU (i.e. “other” second network nodes). For instance, gNB- CU1 is the source CU, gNB-DUl, gNB-DU2, gNB-DU3 are candidate (or second) network nodes. The gNB-CUl receives the TAT value for a cell of gNB-DUl, and then it sends that TAT value to gNB-DU2 and gNB-DU3.

[0158] In a related embodiment, the sending of the received TAT value from first network node (or from the third network node) to other second network node(s) is done at CLTM execution, i.e.,as soon as the first network node (or the third network node) becomes aware that the UE has access the target cell, for example via one or more of the following procedures: XnAP Cell Switch Notification, F1AP CU-DU Cell Switch Notification, F1AP DU-CU Cell Switch Notification, F1AP UE Context Modification (gNB-CU initiated), F1AP UE Context Modification Required (gNB-DU initiated), F1AP Access Success, XnAP M-NG-RAN node initiated S-NG-RAN node Modification Preparation, XnAP S-NG-RAN node initiated S-NG-RAN node Modification.

[0159] In another related embodiment, the sending of the received TAT value from first network node (or from the third network node) to other second network node(s) is done at CLTM preparation, i.e., as soon as the first network node (or the third network node) receives the TAT value, for example via one or more of the following procedures: XnAP LTM Configuration Update, F1AP UE Context Modification (gNB-CU initiated), F1AP UE Context Modification Required (gNB-DU initiated).

[0160] Below an implementation of an example embodiment of the present disclosure is presented as additions 3GPP TS 38.473, vl8.5.0 (2025-03), Fl application protocol (F1AP), where the additions are emphasized by bold, italicized, and underlined text.

[0161] 9.2.2.1 UE CONTEXT SETUP REQUEST

[0162] This message is sent by the gNB-CU to request the setup of a UE context.

[0163] Direction: gNB-CU gNB-DU.

[0164] lE / Group Name Presenc Range IE type and Semantics Criticalit Assigne e reference description y d Criticalit y Message Type M 9.3.1.1 YES reject gNB-CU UE F1AP ID M 9.3.1.4 YES reject gNB-DU UE F1AP ID O 9.3.1.5 YES ignore SpCell ID M NR CGI Special Cell as YES reject 9.3.1.12 defined in TS

[0165] 38.321

[0016] , For

[0166] handover case,

[0167] this IE is

[0168] considered as

[0169] target cell.

[0170] ServCelllndex M INTEGER YES reject (0..31 ,...)

[0171] SpCell UL Configured O Cell UL YES ignore Configured

[0172] 9.3.1.33

[0173] CU to DU RRC M 9.3.1.25 YES reject Information

[0174] Candidate SpCell 0..1 YES ignore List

[0175] >Candidate SpCell 1 .. EACH ignore Item lEs <maxnoo

[0176] fCandidat

[0177]

[0178] eSpCellslE / Group Name Presenc Range IE type and Semantics Criticalit Assigne e reference description y d Criticalit y

[0179] »Candidate M NR CGI Special Cell as - SpCell ID 9.3.1.12 defined in TS

[0180] 38.321

[0016]

[0181] DRX Cycle O 9.3.1.24 YES ignore Resource O OCTET Includes the YES ignore Coordination Transfer STRING MeNB Resource

[0182] Container Coordination

[0183] Information IE as

[0184] defined in

[0185] subclause

[0186] 9.2.116 of TS

[0187] 36.423 [9] for

[0188] EN-DC case or

[0189] MR-DC

[0190] Resource

[0191] Coordination

[0192] Information IE as

[0193] defined in TS

[0194] 38.423

[0028] for

[0195] NGEN-DC and

[0196] NE-DC cases.

[0197] SCell To Be Setup 0..1 YES ignore List

[0198] >SCell to Be Setup 1.. EACH ignore Item lEs <maxnoo

[0199] fSCells>

[0200] »SCell ID M NR CGI SCell Identifier in - 9.3.1.12 gNB

[0201] »SCelllndex M INTEGER - (1..31, ...)

[0202] »SCell UL O Cell UL - Configured Configured

[0203] 9.3.1.33

[0204] »servingCellMO O INTEGER YES ignore (1..64, ...)

[0205] Skip unchanged

[0206] LTM 0..1 YES reject Informationsetup

[0207] >LTM Indicator M ENUMERATE - D (true, ...)

[0208] >Reference O 9.3.1.292 - Configuration

[0209] >CSI Resource O 9.3.1.330 - Configuration

[0210] LTM Configuration ID O 9.3.1.294 YES reject Mapping List

[0211] Early Sync 0..1 YES ignore

[0212]

[0213] Information RequestlE / Group Name Presenc Range IE type and Semantics Criticalit Assigne e reference description y d Criticalit y >Request for RACH M ENUMERATE - Configuration D (true, ...)

[0214] >LTM gNB-DUs 1 This IE contains YES reject List the IDs of the

[0215] source gNB-DU

[0216] and candidate

[0217] gNB-DU(s).

[0218] »LTM gNB-DUs 1..<

[0219] Item lEs maxnoof

[0220] LTMgNB

[0221] DUs>

[0222] »>LTM gNB-DU M gNB-DU ID - ID 9.3.1.9

[0223] >Request for ENUMER

[0224] CLTM information ATED

[0225] [LI

[0226] CLTM,

[0227] L3

[0228] CLTM...)

[0229] Path Addition O 9.3.1.296 YES reject Information

[0230] NR A2X Services O 9.3.1.323 YES ignore Authorized

[0231] LTE A2X Services O 9.3.1.324 YES ignore Authorized

[0232] NR UE Sidelink O NR UE This IE applies YES ignore Aggregate Maximum Sidelink only if the UE is

[0233] Bit Rate for A2X Aggregate authorized for

[0234] Maximum Bit NR A2X

[0235] Rate services.

[0236] 9.3.1.119

[0237] LTE UE Sidelink O LTE UE This IE applies YES ignore Aggregate Maximum Sidelink only if the UE is

[0238] Bit Rate for A2X Aggregate authorized for

[0239] Maximum Bit LTE A2X

[0240] Rate services.

[0241] 9.3.1.118

[0242] DL LBT Failure O ENUMERATE YES ignore Information Request D (inquiry, ...)

[0243] Ranging and Sidelink O 9.3.1.331 This IE applies YES ignore Positioning Service only if the UE is

[0244] Information authorized for

[0245] NR V2X services

[0246] and / or 5G ProSe

[0247] services.

[0248] Non-lnteger DRX O 9.3.1.344 YES ignore

[0249]

[0250] Cycle

[0251] 9.2.2.2 UE CONTEXT SETUP RESPONSE

[0252] This message is sent by the gNB-DU to confirm the setup of a UE context.

[0253] Direction: gNB-DU gNB-CU.

[0254] lE / Group Name Presen Range IE type and Semantics Criticali Assign

[0255] ce reference description ty ed Criticali ty Message Type M 9.3.1.1 YES reject gNB-CU UE F1AP M 9.3.1.4 YES reject

[0256]

[0257] IDlE / Group Name Presen Range IE type and Semantics Criticali Assign ce reference description ty ed Criticali ty gNB-DU UE F1AP M 9.3.1.5 YES reject ID DU To CU RRC M 9.3.1.26 YES reject Information

[0258] C-RNTI O 9.3.1.32 C-RNTI YES ignore allocated at the

[0259] gNB-DU

[0260] Skip unchanged

[0261] Early Sync 0..1 YES ignore Information

[0262] >TCI States M OCTET Includes the

[0263] Configurations STRING LTM-TCI-Info

[0264] List IE, as defined

[0265] in TS 38.331

[0266] [8].

[0267] >Early UL Sync O 9.3.1.328 - Configuration

[0268] >Early UL Sync O Early UL This IE applies

[0269] Configuration for Sync for SUL carrier.

[0270] SUL Configuratio

[0271] n

[0272] 9.3.1.328

[0273] >CLTM 0..1

[0274] Information

[0275] »Timinq Refer to the

[0276] Alignment TimeAlignme

[0277] Timer ntTimer

[0278] IE as

[0279] specified in

[0280] TS 38.331.

[0281] »TA value INTEGER Indicates the

[0282] (0..4095) TA value as

[0283] defined in TS

[0284] 38.213 [311

[0285] LTM Configuration 0..1 YES ignore >SSB Information M 9.3.1.202 Includes the

[0286] SSB

[0287] Information for

[0288] the requested

[0289] target cell.

[0290] >Reference O OCTET Includes the

[0291] Configuration STRING CellGroupConfi

[0292] Information g IE, as

[0293] defined in TS

[0294] 38.331 [8],

[0295] >Complete O ENUMERAT

[0296] Candidate ED

[0297] Configuration (complete, ...

[0298] Indicator )

[0299] >LTM CFRA O OCTET Includes the

[0300] Resource STRING RACH- Configuration ConfigDedicate

[0301] d IE, as

[0302] defined in TS

[0303]

[0304] 38.331 [8],lE / Group Name Presen Range IE type and Semantics Criticali Assign ce reference description ty ed

[0305] Criticali

[0306] ty

[0307] >LTM CFRA O OCTET Includes the

[0308] Resource STRING RACH- Configuration for ConfigDedicate

[0309] SUL d IE, as

[0310] defined in TS

[0311] 38.331 [8],

[0312] This IE applies

[0313] for SUL carrier.

[0314] S-CPAC 0..1 YES ignore Configuration

[0315] >Reference O OCTET Includes the

[0316] Configuration STRING CellGroupConfi

[0317] Information g IE, as

[0318] defined in TS

[0319] 38.331 [8],

[0320] >Complete o ENUMERAT

[0321] Candidate ED

[0322] Configuration (complete, ...

[0323]

[0324] Indicator ) _

[0325] In another example implementation is described below as additions to 3GPP TS 38.473, V18.5.0 (2025-03), Fl application protocol (F1AP), where the additions are emphasized by bold, italicized, and underlined text. In this example, the TAT value is requested explicitly from the gNB-CU to a source DU in a UE CONTEXT MODIFICATION REQUEST Fl AP message and / or to a candidate DU in a UE CONTEXT SETUP REQUEST F1AP message (e.g., when the CU determines that LTM is initiated). The TAT value is returned from the source DU in a UE CONTEXT MODIFICATION RESPONSE Fl AP message and / or from the candidate DU in a UE CONTEXT SETUP RESPONSE Fl AP message.

[0326] 9.2.2.1 UE CONTEXT SETUP REQUEST

[0327] This message is sent by the gNB-CU to request the setup of a UE context.

[0328] Direction: gNB-CU gNB-DU.

[0329] lE / Group Name Presence Range IE type and Semantics Criticality Assigned reference description Criticality Message Type M 9.3.1.1 YES reject gNB-CU UE F1AP ID M 9.3.1.4 YES reject gNB-DU UE F1AP ID O 9.3.1.5 YES ignore (skip)

[0330]

[0331] LTM Informationsetup 0..1 YES rejectlE / Group Name Presence Range IE type and Semantics Criticality Assigned reference description Criticality >LTM Indicator M ENUMERATED - (true, ...)

[0332] >Reference O 9.3.1.292 - Configuration

[0333] >CSI Resource O 9.3.1.330 - Configuration

[0334] >Time Alignment O ENUMERATED 2

[0335] Timer Request (true, ...)

[0336] LTM Configuration ID o 9.3.1.294 YES reject

[0337]

[0338] Mapping List

[0339] 9.2.2.2 UE CONTEXT SETUP RESPONSE

[0340] This message is sent by the gNB-DU to confirm the setup of a UE context.

[0341] Direction: gNB-DU gNB-CU.

[0342] lE / Group Name Presence Range IE type and Semantics Criticality Assigned reference description Criticality Message Type M 9.3.1.1 YES reject gNB-CU UE F1AP ID M 9.3.1.4 YES reject gNB-DU UE F1AP ID M 9.3.1.5 YES reject (skip)

[0343] Early Sync 0..1 YES ignore Information

[0344] >TCI States M OCTET Includes the LTM- Configurations List STRING TCI-Infb

[0345] IE, as defined in

[0346] TS 38.331 [8],

[0347] >Early UL Sync O 9.3.1.328 - Configuration

[0348] >Early UL Sync O Early UL Sync This IE applies for - Configuration for SUL Configuration SUL carrier.

[0349] 9.3.1.328

[0350] >Time Aiqnment O ENUMERATED

[0351] Timer (ms500,

[0352] ms750,

[0353] ms1280,

[0354] ms1920,

[0355] ms2560,

[0356] ms5120,

[0357] ms10240,

[0358] infinity, ■■■)

[0359] LTM Configuration 0..1 YES Ignore

[0360]

[0361] (skip)

[0362] 9.2.2.7 UE CONTEXT MODIFICATION REQUEST

[0363] This message is sent by the gNB-CU to provide UE Context information changes to the gNB-DU. Direction: gNB-CU gNB-DU

[0364] lE / Group Name Presence Range IE type and Semantics Criticality Assigned reference description Criticality Message Type M 9.3.1.1 YES reject gNB-CU UE F1AP ID M 9.3.1.4 YES reject gNB-DU UE F1AP ID M 9.3.1.5 YES reject (skip)

[0365] LTM Information 0..1 YES reject Modify

[0366]

[0367] >LTM Indicator M ENUMERATED -lE / Group Name Presence Range IE type and Semantics Criticality Assigned reference description Criticality (true, ...)

[0368] >Reference O 9.3.1.292 - Configuration

[0369] >CSI Resource O 9.3.1.330 - Configuration

[0370] >Time Alignment O ENUMERATED 2

[0371] Timer Request (true, ...)

[0372] LTM CFRA Resource 0..1 YES Ignore Config List

[0373]

[0374] (skip)

[0375] 9.2.2.8 UE CONTEXT MODIFICATION RESPONSE

[0376] This message is sent by the gNB-DU to confirm the modification of a UE context.

[0377] Direction: gNB-DU gNB-CU.

[0378] lE / Group Name Presence Range IE type and Semantics Criticality Assigned reference description Criticality Message Type M 9.3.1.1 YES reject gNB-CU UE F1AP ID M 9.3.1.4 YES reject gNB-DU UE F1AP ID M 9.3.1.5 YES reject (skip)

[0379] Early Sync 0..1 YES ignore Information

[0380] >TCI States M OCTET Includes the LTM- Configurations List STRING TCI-Infb

[0381] IE, as defined in

[0382] TS 38.331 [8],

[0383] >Early UL Sync O 9.3.1.328 - Configuration

[0384] >Early UL Sync O Early UL Sync This IE applies for - Configuration for SUL Configuration SUL carrier.

[0385] 9.3.1.328

[0386] >Time Aiqnment O ENUMERATED

[0387] Timer (ms500,

[0388] ms750,

[0389] ms1280,

[0390] ms1920,

[0391] ms2560,

[0392] ms5120,

[0393] ms10240,

[0394] infinity, ■■■)

[0395] LTM Configuration 0..1 YES ignore

[0396]

[0397] (skip)

[0398] Figure 7 shows an example of a communication system 700 in accordance with some embodiments. The UE described in the embodiments above is, for example, one of the UEs 712 of Figure 7. The first, second, and third network nodes may be, for example, different network nodes 710 of Figure 7 or may be different components (e.g., CU, DU(s)) of one of the network nodes 710 of Figure 7.In the example, the communication system 700 includes a telecommunications network 702 that includes an access network 704, such as a radio access network (RAN), and a core network 706, which includes one or more core network nodes 708. The access network 704 includes one or more access network nodes or base stations of various types, access network nodes 710A and 710B are depicted (which may be collectively referred to as network nodes 710), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 704 may include more than one access network technology. The network nodes 710 of access network 704 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 712A, 712B, 712C, and 712D (one or more of which may be generally referred to as UEs 712) to the core network 706 over one or more wireless connections.

[0399] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 702 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 702 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node in the telecommunications network 702, including one or more access network nodes 710 and / or core network nodes 708.

[0400] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platformorchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the 0-RAN Alliance or comparable technologies.

[0401] The network nodes 710 facilitate direct or indirect connection of one or more UEs 712 to the core network 706 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 700 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 700 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0402] The UEs 712 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 710 and other communication devices. Similarly, the network nodes 708, 710 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 702) with the UEs 712 and / or with other network nodes or equipment in the telecommunications network 702 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 702. More specifically, UEs 712 may send messages, data, and / or other signals to network nodes 708, 710 or other elements of the telecommunications network 702 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 708, 710 may send messages, data, and other signals to UEs 712, other network nodes 708, 710, and other devices in telecommunications network 702 directly or indirectly. As one specific example, a core network node 708 may transmit a particular message to a UE 712 by transmitting the message to an access network node 710 that will then transmit the message to the intended UE 712. Similarly, a core network node 708 may receive a particular message from a UE 712 by receiving the message from an access network node 710 that itself received the message from the UE 712.

[0403] In the depicted example, the core network 706 connects elements of the access network 704 (e.g., one or more of the network nodes 710) to one or more host computing systems, such ashost 716. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 706 includes one or more core network nodes (e.g., core network node 708) of various types, one or more of which may be generally referred to as network nodes 708. Network nodes 708 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 708. Example core network nodes provide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0404] The host 716 may be under the ownership or control of a service provider other than an operator or provider of the access network 704 and / or the telecommunications network 702. The host 716 may be operated by the service provider or on behalf of the service provider. The host 716 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0405] As a whole, the communication system 700 of Figure 7 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 700 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 700 may be configured to support multiple different standards, protocols, or other rule sets, with individual componentssupporting all of the relevant rule sets or with different components or sub-systems within the communication system 700 supporting different standards, protocols, or rule sets.

[0406] As one example, in certain embodiments, access network 704 may contain some access network nodes 710 that support 3 GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 710 support (or the same access network nodes 710 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 702 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result, may include an access network 704 and / or a core network 706 that supports multiple different standard generations or may include multiple access networks 704 and / or multiple core networks 706 with individual networks 704, 706 supporting different standard generations.

[0407] Telecommunications network 702 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 702. For example, the telecommunications network 702 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0408] In some examples, one or more of the UEs 712 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 704 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 704. Additionally, a UE may be configured for operating in single- or multi -RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0409] In the example, the hub 714 communicates with the access network 704 to facilitate indirect communication between one or more UEs (e.g., UE 712C and / or 712D) and network nodes (e.g., network node 710B). In some examples, the hub 714 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 714 may be a broadband router enabling access to the core network 706 for the UEs. As another example, the hub 714 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 710, or by executable code, script, process, or other instructions in the hub 714.As another example, the hub 714 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 714 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 714 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 714 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 714 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0410] The hub 714 may have a constant / persistent or intermittent connection to the network node 710B. The hub 714 may also allow for a different communication scheme and / or schedule between the hub 714 and UEs (e.g., UE 712C and / or 712D), and between the hub 714 and the core network 706. In other examples, the hub 714 is connected to the core network 706 and / or one or more UEs via a wired connection. Moreover, the hub 714 may be configured to connect to an M2M service provider over the access network 704 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 710 while still connected via the hub 714 via a wired or wireless connection. In some embodiments, the hub 714 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 710B. In other embodiments, the hub 714 may be a nondedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 710B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0411] Figure 8 is another example of a communication system 800 according to some embodiments. As used herein, the communication system 800 includes multiple access points (APs) 810 (with four exemplary APs 810A, 810B, 810C, and 810D being depicted) and multiple wireless devices, referred to in the context of communication system 800 as stations (STAs) 812 (referred to individually as STA 812A, STA 812B, STA 812C, STA 812D, and STA 812E). STA 812Ais served by AP 810Ain a first basic service set (BSS) 820A. STA 812B and STA 812C are served by AP 810B in a second BSS, BSS 820B. STA 812D is served by AP 810C in a third BSS, BSS 820C. STA 812E is served by AP 810D in a fourth BSS, BSS 820D. Stations 812 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 812 could, for example,correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0412] Each of STAs 812 may connect through a radio link to one of APs 810. For example, depending on location or channel conditions experienced by a given STA 812, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.

[0413] Each AP 810 may provide data connectivity to STAs 812 connected to a particular AP 810. As illustrated, APs 810 may be connected to a data network 830. In this way, APs 810 may also provide data connectivity between STAs 812 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA 812 and its serving AP 810 may be used for providing various kinds of services to STA 812, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 812 and / or on a device linked to STA 812. By way of example, Figure 8 illustrates an application service platform 832 provided in data network 830. The application(s) executed on STA 812 and / or on one or more other devices linked to STA 812 may use the radio link for data communication with one or more other STA 812 and / or the application service platform 832, thereby enabling utilization of the corresponding service(s) at STA 812.

[0414] Figure 9 shows a wireless device 900, which may be configured to operate in communication system 700 of Figure 7 or in communication system 800 of Figure 8. The wireless device 900 may be alternatively referred to as a UE 900, like a UE 712 within the context of communication system 700, or as a station (STA) 900 or as a non-access-point station (non-AP STA) 900, like a STA 812 within the context of the communication system 800, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicleembedded / integrated wireless device, and wireless terminal. Other examples include any type of UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0415] A wireless device 900 may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, wireless device 900 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 900 may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, wireless device 900 may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0416] In particular embodiments, wireless device 900 includes processing circuitry 902 that is operatively coupled via a bus 904 to an input / output interface 906, a power source 908, a memory 910, a communication interface 912, and / or any other component, or any combination thereof. Certain embodiments of wireless device 900 may include all or a subset of the components shown in Figure 9. The level of integration between the components may vary from one embodiment of wireless device 900 to another. In general, in a particular embodiment of wireless device 900, processing circuitry 902, input / output interface 906, power source 908, memory 910, and communication interface 912 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 900. Further, certain embodiments of wireless devices 900 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0417] The processing circuitry 902 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 910. The processing circuitry 902 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 902 may include multiple central processing units (CPUs).In the example, the input / output interface 906 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into wireless device 900. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0418] In some embodiments, the power source 908 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used to supply power to circuitry or to charge an associated battery. The power source 908 may further include power circuitry for delivering power from the power source 908 itself, and / or an external power source, to the various parts of wireless device 900 via input circuitry or an interface such as an electrical power cable. Power source 908 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 900 to which power is supplied.

[0419] The memory 910 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 910 includes one or more programs 914, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 916. The memory 910 may store, for use by wireless device 900, any of a variety of various operating systems or combinations of operating systems.

[0420] The memory 910 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamicrandom access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 910 may allow wireless device 900 to access instructions, programs, and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 910, which may be or comprise a device-readable storage medium.

[0421] The processing circuitry 902 may be configured to communicate with an access network or other network via or using the communication interface 912. The communication interface 912 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 922. The communication interface 912 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another wireless device or a network node in an access network). Each transceiver may include a transmitter 918 and / or a receiver 920 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 918 and receiver 920 may be coupled to one or more antennas (e.g., antenna 922) and may share circuit components, software, or firmware, or alternatively be implemented separately.

[0422] In the illustrated embodiment, communication functions of the communication interface 912 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0423] In particular embodiments, wireless device 900 may provide an output of data captured via a sensor, through its communication interface 912, via a wireless connection to a network node,and / or in any appropriate manner. Data captured by sensors of a wireless device 900 can be communicated through a wireless connection to a network node via another wireless device 900. In particular embodiments, such output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected, an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0424] As another example, wireless device 900 comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, wireless device 900 may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0425] Wireless device 900, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. In particular embodiments, wireless device 900 represents an loT device that comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the example embodiment of wireless device 900 shown in Figure 9.

[0426] As yet another specific example, in an loT scenario, wireless device 900 may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another wireless device and / or a network node. Wireless device 900 may in this case be an M2M device, which may in a 3 GPP context be referred to as an MTC device. As one particular example, wireless device 900 may implement the 3GPP NB-IoT standard. In other scenarios, wireless device 900 may represent a vehicle, such as a car, abus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0427] In practice, any number of wireless devices 900 may be used together with respect to a single use case. For example, a first wireless device 900 might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second wireless device 900 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 900 may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second wireless device 900 can also include more than one of the functionalities described above. For example, wireless device 900 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0428] Figure 10 shows a network node 1000 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunications network. In accordance with respective embodiments, network node 1000 may be configured to operate in communication system 700 of Figure 7, like network nodes 708 or 710, or in communication system 800 of Figure 8, like an AP 810 or a station 812. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), 0-RAN nodes or components of an 0-RAN node (e.g., 0-RU, 0-DU, O-CU).

[0429] Network nodes 1000 may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Network node 1000 may be a relay node or a relay donor node controlling a relay. Network nodes 1000 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an 0-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0430] Other examples of network nodes 1000 include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities(MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0431] In particular embodiments, network node 1000 includes a processing circuitry 1002, a memory 1004, a communication interface 1006, and a power source 1008. In general, in a particular embodiment of network node 1000, processing circuitry 1002, memory 1004, communication interface 1006, and power source 1008 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 1000.

[0432] The network node 1000 may be composed of multiple distinct network entities (e.g., a NodeB entity and an RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 1000 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1000 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 1004 or portions of memory 1004 for different RATs) and some components may be reused (e.g., a same antenna 1010 may be shared by different RATs). The network node 1000 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1000, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1000.

[0433] The processing circuitry 1002 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other components, such as the memory 1004, to provide network node 1000 functionality.

[0434] In some embodiments, the processing circuitry 1002 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1002 includes one or more of radio frequency (RF) transceiver circuitry 1012 and baseband processing circuitry 1014. In some embodiments, the RFtransceiver circuitry 1012 and the baseband processing circuitry 1014 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1012 and baseband processing circuitry 1014 may be on the same chip or set of chips, boards, or units.

[0435] The memory 1004 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 1002. The memory 1004 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 1002 and utilized by the network node 1000. The memory 1004 may be used to store any calculations made by the processing circuitry 1002 and / or any data received via the communication interface 1006. In some embodiments, the processing circuitry 1002 and memory 1004 is integrated.

[0436] The communication interface 1006 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 1006 comprises port(s) / terminal(s) 1016 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 1000 may be capable of wireless communication and communication interface 1006 may also include radio front-end circuitry 1018 that may be coupled to, or in certain embodiments a part of, an antenna 1010. Particular embodiments of radio front-end circuitry 1018 include filter(s) 1020 and amplifier(s) 1022. The radio front-end circuitry 1018 may be connected to an antenna 1010 and processing circuitry 1002. The radio front-end circuitry may be configured to condition signals communicated between antenna 1010 and processing circuitry 1002. The radio front-end circuitry 1018 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1018 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 1020 and / or amplifiers 1022. The radio signal(s) may then be transmitted via the antenna 1010. Similarly, when receiving data, the antenna 1010 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1018. The digital data may be passed tothe processing circuitry 1002. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0437] In certain alternative embodiments, network node 1000 may be capable of wireless communication but does not include separate radio front-end circuitry 1018, instead, the processing circuitry 1002 includes radio front-end circuitry and is connected to the antenna 1010. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1012 is part of the communication interface 1006. In still other embodiments, the communication interface 1006 includes one or more ports or terminals 1016, the radio front-end circuitry 1018, and the RF transceiver circuitry 1012, as part of a radio unit (not shown), and the communication interface 1006 communicates with the baseband processing circuitry 1014, which is part of a digital unit (not shown).

[0438] The antenna 1010 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 1010 may be coupled to the radio front-end circuitry 1018 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 1010 is separate from the network node 1000 and connectable to the network node 1000 through one or more interfaces or ports.

[0439] The antenna 1010, communication interface 1006, and / or the processing circuitry 1002 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node 1000. Any information, data, and / or signals may be received from a UE, another network node, and / or any other network equipment. Similarly, the antenna 1010, the communication interface 1006, and / or the processing circuitry 1002 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 1000. Any information, data and / or signals may be transmitted to a UE, another network node, and / or any other network equipment.

[0440] The power source 1008 provides power to the various components of network node 1000 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1008 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1000 with power for performing the functionality described herein. For example, the network node 1000 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1008. As a further example, the power source 1008 may comprise a source of power in the form of a battery or battery pack which is connected to, orintegrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0441] Embodiments of the network node 1000 may include additional components beyond those shown in Figure 10 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1000 may include user interface equipment to allow input of information into the network node 1000 and to allow output of information from the network node 1000. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1000.

[0442] Figure 11 is a block diagram illustrating a virtualization environment 1100 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1100 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 1100 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

[0443] Applications 1102 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 1100 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0444] Hardware 1104 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1106 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 1108 A and VM 1108B (which may be collectively referred to as VMs 1108), and / or perform any of the functions,features and / or benefits described in relation with some embodiments described herein. The virtualization layer 1106 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 1108.

[0445] The VMs 1108 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 1106. Different embodiments of the instance of a virtual appliance 1102 may be implemented on one or more of VMs 1108, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0446] In the context of NFV, each of the VMs 1108 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1108, and that part of hardware 1104 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more of the VMs 1108 on top of the hardware 1104 and corresponds to an application 1102.

[0447] Hardware 1104 may be implemented in a standalone network node with generic or specific components. Hardware 1104 may implement some functions via virtualization. Alternatively, hardware 1104 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1110, which, among others, oversees lifecycle management of applications 1102. In some embodiments, hardware 1104 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 1112 which may alternatively be used for communication between hardware nodes and radio units.

[0448] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software neededto perform the tasks, features, functions, and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0449] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0450] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

[0451] Some exemplary embodiments of the present disclosure are as follows:

[0452] Group A Embodiments

[0453] Embodiment 1: A method performed by a User Equipment, UE, for performing Timing Advance, TA, acquisition for a candidate target cell of a (e.g., conditional) mobility procedure, themethod comprising any one or more of the following: receiving (500), from a first network node, a configuration which comprises a TA acquisition configuration, one or more execution conditions, and a Time Alignment Timer, TAT, value (which can also be included within the TA acquisition configuration), applicable for a candidate target cell for a mobility procedure, wherein the candidate target cell belongs to (e.g., is operated by) a second network node; transmitting (502), to the second network node, a preamble message in the candidate target cell; receiving (504), from the first network node, a message including TA related information for the candidate target cell of the conditional mobility procedure; and starting (506) a TAT according to the TAT value received from the first network node.

[0454] Embodiment 2: The method of embodiment 1, wherein the TAT value is additionally or alternatively included in the TA acquisition configuration.

[0455] Embodiment 3: A method performed by a User Equipment, UE, for performing Timing Advance, TA, acquisition for a candidate target cell of a (e.g., conditional) mobility procedure, the method comprising: receiving (600), from a first network node, a mobility configuration for a candidate target cell that belongs to (e.g., is operated by) a second network node, wherein the mobility configuration comprises TA related information applicable to the candidate target cell.

[0456] Embodiment 4: The method of embodiment 3, further comprising receiving (600), from the first network node (e.g., as part of the mobility configuration), one or more execution conditions for the mobility procedure.

[0457] Embodiment 5: The method of any of embodiments 3 to 4, wherein the mobility configuration comprises a Time Alignment Timer, TAT, value applicable for the candidate target cell.

[0458] Embodiment 6: The method of any of embodiments 3 to 4, wherein the TA related information comprises a Time Alignment Timer, TAT, value applicable for the candidate target cell.

[0459] Embodiment 7: The method of embodiment 5 or 6, further comprising starting (604) a TAT (e.g., applicable to the candidate target cell) according to the TAT value received from the first network node.

[0460] Embodiment 8: The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node.

[0461] Group B EmbodimentsEmbodiment 9: A method performed by a first network node for (e.g., configuring a TAT value for a mobility procedure for a UE), the method comprising any one or more of the following: transmitting (200) a first message to a second network node that operates or otherwise handles a candidate target cell for a mobility procedure for a User Equipment, UE, wherein the first message comprises a request to provide Timing Advance, TA, related information for the candidate target cell; receiving (202), from the second network node, a second message comprising the TA information for the candidate target cell; transmitting (204), to the UE, a mobility configuration for the candidate target cell, the mobility configuration comprising the TA related information for the candidate target cell.

[0462] Embodiment 10: The method of embodiment 9, wherein the TA information received from the second network node or the second message received from the second network node comprises a Time Alignment Timer, TAT, value applicable to the candidate target cell.

[0463] Embodiment 11: The method of embodiment 9 or 10, wherein the first message further comprises a request to provide one or more execution conditions for the mobility procedure, the second message comprises the one or more execution conditions for the mobility procedure, and the mobility configuration comprises the one or more execution conditions for the mobility procedure.

[0464] Embodiment 12: The method of any of embodiments 9 to 11, wherein the first network node transmits to the second network node (e.g., in the first message) an indicator to request LI or L3 execution conditions.

[0465] Embodiment 13: The method of any of embodiments 9 to 12, wherein the first network node transmits to the second network node (e.g., in the first message) an explicit indicator to perform a TA acquisition procedure for the candidate target cell.

[0466] Embodiment 14: The method of any of embodiments 9 to 13, wherein (e.g., in the mobility configurations or in a separate configuration s)) the first network node configures the UE with one or more execution conditions for the mobility procedure and a configuration for performing a TA acquisition procedure for the candidate target cell.

[0467] Embodiment 15: The method of any of embodiments 9 to 14, wherein the request for the TA related information includes an explicit indication to provide a TAT value to be provided to the UE.

[0468] Embodiment 16: The method of any of embodiments 9 to 14, wherein the first network node further sends, to the second network node, a separate (e.g., standalone or separate from the request for the TA related information and if present any request to provide one or more executionconditions for the mobility procedure) request a TAT value applicable to the candidate target cell to be provided to the UE.

[0469] Embodiment 17: The method of any of embodiments 9 to 14, wherein the first network node further sends, to the second network node, a request to provide a TAT value applicable to the candidate target cell to be provided to the UE, wherein the request to provide the TAT value is independent to the request to provide TA related information or conditional execution.

[0470] Embodiment 18: The method of any of embodiments 9 to 14, wherein the first network node further sends, to the second network node, a request to provide a TAT value applicable to the candidate target cell to be provided to the UE, wherein the request to provide a TAT value is included within the request to provide one or more execution conditions for the mobility procedure.

[0471] Embodiment 19: The method of embodiment 18, wherein: the request to provide a TAT value for the UE is only included in case LI execution conditions are requested, or the request to provide a TAT value for the UE is only included in case L3 execution conditions are requested, or the request to provide a TAT value for the UE is included regardless of whether LI or L3 execution conditions are requested.

[0472] Embodiment 20: The method of any of embodiments 9 to 19, wherein the first network node provides an indication to the UE to initiate a TA acquisition procedure in the candidate target cell.

[0473] Embodiment 21: The method of any of embodiments 9 to 20, wherein the first network node transmits to the UE a TAT value for the candidate target cell within the mobility configuration or in a separate message.

[0474] Embodiment 22: The method of any of embodiments 9 to 20, wherein the first network node transmits to the UE a TAT value for the candidate target cell, wherein the TAT value included within a TA acquisition configuration transmitted to the UE.

[0475] Embodiment 23: The method of any of embodiments 9 to 22, wherein the first network node receives the TAT value for the candidate target cell from second network node within a container (e.g., as an OCTET STRING).

[0476] Embodiment 24: The method of any of embodiments 9 to 22, wherein the first network node receives the TAT value for the candidate target cell from second network node in an explicit way (e g., as an ENUMERATED or as an INTEGER value).

[0477] Embodiment 25: The method of any of embodiments 9 to 24, wherein the first message and the second message are transmitted and received by the first network node using one or more F1AP procedures, e.g., UE Context Setup Request and Response, and / or UE Context Modification Request and Response, and / or a new F1AP procedure.Embodiment 26: The method of any of embodiments 9 to 24, wherein the first message and the second message are transmitted and received by the first network node using one or more XnAP procedures, e.g., Handover Request, and / or LTM Configuration Update, and / or a new XnAP procedure.

[0478] Embodiment 27: A method performed by a second network node that handles (e.g., operates or otherwise controls) a candidate target cell for a mobility procedure for a User Equipment, UE, (e.g., for determining whether to configure a TAT value for the mobility procedure for the UE), the method comprising any one or more of the following: receiving (300), from a first network node, a first message comprising a request to provide Timing Advance, TA, related information for the candidate target cell; transmitting (304), to the first network node, a second message comprising the requested TA information.

[0479] Embodiment 28: The method of embodiment 27, wherein the TA information transmitted to the first network node in the second message comprises a Time Alignment Timer, TAT, value applicable to the candidate target cell.

[0480] Embodiment 29: The method of embodiment 27 or 28, wherein the TA information comprises one or more TA values.

[0481] Embodiment 30: The method of embodiment 27, further comprising determining (302) whether to provide a Time Alignment Timer, TAT, value for the candidate target cell to the first network node to be forwarded to the UE.

[0482] Embodiment 31: The method of embodiment 30, further comprising, responsive to determining to provide a TAT value for the candidate target cell to the first network node to be forwarded to the UE, transmitting the TAT value to the first network node.

[0483] Embodiment 32: The method of embodiment 30, further comprising, responsive to determining to provide a TAT value for the candidate target cell to the first network node to be forwarded to the UE, including the TAT value for the candidate target cell within the TA information transmitted to the first network node in the second message or in the second message transmitted to the first network node.

[0484] Embodiment 33: The method of any of embodiments 27 to 32, wherein the first message further comprises a request for one or more execution conditions for the mobility procedure, and the second message further comprises the requested one or more execution conditions for the mobility procedure.

[0485] Embodiment 34: The method of any of embodiments 27 to 33, wherein the first message further comprises a request to provide one or more execution conditions for the mobility procedurethat comprises one or both of the following: an indication to provide LI execution conditions, and an indication to provide L3 execution conditions.

[0486] Embodiment 35: The method of any of embodiments 27 to 34, wherein the request to provide the TA related information comprises an explicit request to configure a TAT value within a TA acquisition configuration for the UE.

[0487] Embodiment 36: The method of any of embodiments 27 to 34, wherein the request to provide the TA related information comprises a request (explicit or implicit) to include a TAT value within the TA related information.

[0488] Embodiment 37: The method of any of embodiments 27 to 36, further comprising determining (302) whether to provide a Time Alignment Timer, TAT, value for the candidate target cell to the first network node to be forwarded to the UE, wherein said determining comprises implicitly determining that a TAT value is to be provided within a TA acquisition configuration for the LTE based on a presence of a request to provide one or more execution conditions for the mobility procedure.

[0489] Embodiment 38: The method of any of embodiments 27 to 37, wherein the second network node provides the TAT value for the candidate target cell to the first network node within a container (e.g., as an OCTET STRING).

[0490] Embodiment 39: The method of any of embodiments 27 to 37, wherein the second network node provides the TAT value for the candidate target cell to the first network node in an explicit way (e g., as an ENUMERATED or as an INTEGER value).

[0491] Embodiment 40: The method of any of embodiments 27 to 36, further comprising determining (302) whether to provide a Time Alignment Timer, TAT, value for the candidate target cell to the first network node to be forwarded to the UE, wherein said determining comprises implicitly determining that a TAT value is requested based on a presence of a request to provide LI execution conditions for the mobility procedure.

[0492] Embodiment 41: The method of any of embodiments 27 to 36, further comprising determining (302) whether to provide a Time Alignment Timer, TAT, value for the candidate target cell to the first network node to be forwarded to the UE, wherein said determining comprises implicitly determining that a TAT value is requested based on the presence of the request to provide L3 execution conditions for a mobility procedure.

[0493] Embodiment 42: The method of any of embodiments 27 to 36, further comprising determining (302) whether to provide a Time Alignment Timer, TAT, value for the candidate target cell to the first network node to be forwarded to the UE, wherein said determining comprisesimplicitly determining that a TAT value is requested based on receiving an indication that Conditional LTM is being prepared.

[0494] Embodiment 43: The method of any of embodiments 27 to 36, further comprising determining (302) whether to provide a Time Alignment Timer, TAT, value for the candidate target cell to the first network node to be forwarded to the UE, wherein said determining comprises implicitly determining that a TAT value is requested based on receiving an indication that Conditional LTM is being prepared and one of LI execution conditions or L3 execution conditions are not requested.

[0495] Embodiment 44: The method of any of embodiments 27 to 43, wherein the TAT value sent from the second network node to the first network node (e.g., in the second message) (e.g., within a TA acquisition configuration) is provided for the specific UE.

[0496] Embodiment 45: The method of any of embodiments 27 to 43, wherein the TAT value sent from the second network node to the first network node (e.g., in the second message) (e.g., within a TA acquisition configuration) is provided for the specific UE and a group of cells.

[0497] Embodiment 46: The method of any of embodiments 27 to 45, wherein the second network node transmits the TAT value to the first network node in response to receiving a request for the TAT value.

[0498] Embodiment 47: The method of any of embodiments 27 to 46, wherein the first message is received and the second message is transmitted using one or more F1AP procedures, e.g., UE Context Setup Request and Response, and / or UE Context Modification Request and Response, and / or a new F1AP procedure.

[0499] Embodiment 48: The method of any of embodiments 27 to 46, wherein the first message is received and the second message is transmitted using one or more XnAP procedures, e.g., Handover Request Acknowledge, and / or LTM Configuration Update Acknowledge, and / or a new XnAP procedure.

[0500] Embodiment 49: A method performed by a third network node, the method comprising: transmitting (400), to a first network node (e.g., that operates or controls a source or serving cell of a User Equipment, UE), a message comprising Time Alignment Timer, TAT, information per cell for one or more cells (e.g., one or more candidate target cells for a mobility procedure, where the one or more candidate target cells are operated or controlled by a second network node).

[0501] Embodiment 50: The method of embodiment 49, wherein the message is transmitted using one or more Fl AP procedures, e.g., CU-DU TA Information Transfer, and / or a new Class 2 F1AP procedure.Embodiment 51: The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.

[0502] Group C Embodiments

[0503] Embodiment 52: A User Equipment, UE, comprising: processing circuitry configured to perform any of the operations of any of the Group A embodiments; and a power source configured to supply power to the processing circuitry.

[0504] Embodiment 53: A network node comprising: processing circuitry configured to perform any of the operations of any of the Group B embodiments; a power source circuitry configured to supply power to the processing circuitry.

[0505] Embodiment 54: A User Equipment, UE, comprising: one or more antennas; communication interface connected to the one or more antennas and to processing circuitry; the processing circuitry being configured to perform any of the operations of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a power source connected to the processing circuitry and configured to supply power to the UE.

Claims

CLAIMS1. A method performed by a User Equipment, UE, for conditional mobility, the method comprising:receiving (500), from a first network node, a configuration which comprises a Timing Advance, TA, acquisition configuration, one or more execution conditions, and a Time Alignment Timer, TAT, value, applicable for a candidate target cell for a conditional mobility procedure, wherein the candidate target cell belongs to a second network node;transmitting (502), to the second network node, a preamble message in the candidate target cell;receiving (504), from the first network node, a message including TA related information for the candidate target cell of the conditional mobility procedure; andstarting (506) a TAT according to the TAT value received from the first network node.

2. The method of claim 1, wherein the TAT value is comprised in the TA acquisition configuration.

3. The method of claim 1, wherein the TAT value is comprised in the configuration separate from the TA acquisition configuration.

4. A User Equipment, UE, (712; 900) for conditional mobility, the UE (712; 900) comprising:a communication interface (912) comprising a transmitter (918) and a receiver (920); and processing circuitry (902) associated with the communication interface (912), the processing circuitry (912) configured to cause the UE (712; 900) to:receive (500), from a first network node, a configuration which comprises a Timing Advance, TA, acquisition configuration, one or more execution conditions, and a Time Alignment Timer, TAT, value, applicable for a candidate target cell for a conditional mobility procedure, wherein the candidate target cell belongs to a second network node;transmit (502), to the second network node, a preamble message in the candidate target cell;receive (504), from the first network node, a message including TA related information for the candidate target cell of the conditional mobility procedure; andstart (506) a TAT according to the TAT value received from the first network node.

5. The UE (712; 900) of claim 4, wherein the TAT value is comprised in the TA acquisitionconfiguration or is comprised in the configuration separate from the TA acquisition configuration.

6. A method performed by a User Equipment, UE, for mobility, the method comprising:receiving (600), from a first network node, a mobility configuration for a candidate target cell that belongs to a second network node, wherein the mobility configuration comprises a Timing Advance, TA, related information applicable to the candidate target cell.

7. The method of claim 6, further comprising receiving (600), from the first network node, one or more execution conditions for the mobility procedure.

8. The method of claim 6, wherein the mobility configuration is for a conditional mobility procedure, and the mobility configuration further comprises one or more execution conditions for the conditional mobility procedure.

9. The method of any of claims 6 to 8, wherein the mobility configuration comprises a Time Alignment Timer, TAT, value applicable for the candidate target cell.

10. The method of any of claims 6 to 8, wherein the TA related information comprises a Time Alignment Timer, TAT, value applicable for the candidate target cell.

11. The method of claim 9 or 10, further comprising starting (604) a TAT applicable to the candidate target cell according to the TAT value received from the first network node.

12. A User Equipment, UE, (712; 900) for mobility, the UE (712; 900) comprising:a communication interface (912) comprising a transmitter (918) and a receiver (920); and processing circuitry (902) associated with the communication interface (912), the processing circuitry (912) configured to cause the UE (712; 900) to receive (600), from a first network node, a mobility configuration for a candidate target cell that belongs to a second network node, wherein the mobility configuration comprises Timing Advance, TA, related information applicable to the candidate target cell.

13. The UE (712; 900) of claim 12, wherein the processing circuitry (9092) is further configured to cause the UE (712; 900) to perform the method of any of claims 7 to 11.

14. A method performed by a first network node, the method comprising:transmitting (200) a first message to a second network node that operates or otherwise handles a candidate target cell for a conditional mobility procedure for a User Equipment, UE, wherein the first message comprises a request to provide Timing Advance, TA, related information for the candidate target cell;receiving (202), from the second network node, a second message comprising the TA information for the candidate target cell;transmitting (204), to the UE, a mobility configuration for the candidate target cell, the mobility configuration comprising the TA related information for the candidate target cell.

15. The method of claim 14, wherein the TA information received from the second network node or the second message received from the second network node comprises a Time Alignment Timer, TAT, value applicable to the candidate target cell.

16. The method of claim 14 or 15, wherein the first message further comprises a request to provide one or more execution conditions for the conditional mobility procedure, the second message comprises the one or more execution conditions for the conditional mobility procedure, and the mobility configuration comprises the one or more execution conditions for the conditional mobility procedure.

17. The method of any of claims 14 to 16, wherein the first network node transmits to the second network node in the first message an indicator to request Layer 1, LI, or Layer 3, L3, execution conditions.

18. The method of any of claims 14 to 17, wherein the first network node transmits to the second network node an explicit indicator to perform a TA acquisition procedure for the candidate target cell.

19. The method of any of claims 14 to 18, wherein, in the mobility configuration or in a separate configuration, the first network node configures the UE with one or more execution conditions for the conditional mobility procedure and a configuration for performing a TA acquisition procedure for the candidate target cell.

20. The method of any of claims 14 to 19, wherein the request for the TA related informationcomprises an explicit indication to provide a time alignment timer, TAT, value to be provided to the UE.

21. The method of any of claims 14 to 19, wherein the first network node further sends, to the second network node, a separate request for a time alignment timer, TAT, value applicable to the candidate target cell to be provided to the UE.

22. The method of any of claims 14 to 19, wherein the first network node further sends, to the second network node, a request to provide a time alignment timer, TAT, value applicable to the candidate target cell to be provided to the UE, wherein the request to provide the TAT value is independent from the request to provide TA related information or conditional execution.

23. The method of any of claims 14 to 19, wherein the first network node further sends, to the second network node, a request to provide a time alignment timer, TAT, value applicable to the candidate target cell to be provided to the UE, wherein the request to provide a TAT value is included within the request to provide one or more execution conditions for the mobility procedure.

24. The method of claim 23, wherein:the request to provide a TAT value for the UE is only included in case Layer 1, LI, execution conditions are requested, orthe request to provide a TAT value for the UE is only included in case Layer 3, L3, execution conditions are requested, orthe request to provide a TAT value for the UE is included regardless of whether LI or L3 execution conditions are requested.

25. The method of any of claims 14 to 24, wherein the first network node provides an indication to the UE to initiate a TA acquisition procedure in the candidate target cell.

26. The method of any of claims 14 to 25, wherein the first network node transmits to the UE a time alignment timer, TAT, value for the candidate target cell within the mobility configuration or in a separate message.

27. The method of any of claims 14 to 25, wherein the first network node transmits to the UE a time alignment timer, TAT, value for the candidate target cell, wherein the TAT value includedwithin a TA acquisition configuration transmitted to the UE.

28. The method of any of claims 14 to 27, wherein the first network node receives a time alignment timer, TAT, value for the candidate target cell from second network node within a container.

29. The method of any of claims 14 to 27, wherein the first network node receives a time alignment timer, TAT, value for the candidate target cell from second network node in an explicit way.

30. The method of any of claims 14 to 29, wherein the first message and the second message are transmitted and received by the first network node using one or more F1AP procedures.

31. The method of any of claims 14 to 29, wherein the first message and the second message are transmitted and received by the first network node using one or more XnAP procedures.

32. A first network node (710; 1000), comprising:a communication interface (1006); andprocessing circuitry (1002) associated with the communication interface (1006), the processing circuitry (1002) configured to cause the first network node (710; 1000) to:transmit (200) a first message to a second network node that operates or otherwise handles a candidate target cell for a conditional mobility procedure for a User Equipment, UE, wherein the first message comprises a request to provide Timing Advance, TA, related information for the candidate target cell;receive (202), from the second network node, a second message comprising the TA information for the candidate target cell;transmit (204), to the UE, a mobility configuration for the candidate target cell, the mobility configuration comprising the TA related information for the candidate target cell.

33. The first network node (710; 1000) of claim 32, wherein the processing circuitry (1002) is further configured to cause the first network node (710; 1000) to perform the method of any of claims 15 to 31.

34. A method performed by a second network node that operates or otherwise controls acandidate target cell for a conditional mobility procedure for a User Equipment, UE, the method comprising:receiving (300), from a first network node, a first message comprising a request to provide Timing Advance, TA, related information for the candidate target cell; and transmitting (304), to the first network node, a second message comprising the requested TA information.

35. The method of claim 34, wherein the TA information transmitted to the first network node in the second message comprises a Time Alignment Timer, TAT, value applicable to the candidate target cell.

36. The method of claim 34 or 35, wherein the TA information transmitted to the first network node in the second message comprises one or more TA values.

37. The method of claim 34, further comprising determining (302) whether to provide a Time Alignment Timer, TAT, value for the candidate target cell to the first network node to be forwarded to the UE.

38. The method of claim 37, further comprising, responsive to determining to provide a TAT value for the candidate target cell to the first network node to be forwarded to the UE, transmitting the TAT value to the first network node.

39. The method of claim 37, further comprising, responsive to determining to provide a TAT value for the candidate target cell to the first network node to be forwarded to the UE, including the TAT value for the candidate target cell within the TA information transmitted to the first network node in the second message or in the second message transmitted to the first network node.

40. The method of any of claims 34 to 39, wherein the first message further comprises a request for one or more execution conditions for the mobility procedure, and the second message further comprises the requested one or more execution conditions for the mobility procedure.

41. The method of any of claims 34 to 40, wherein the first message further comprises a request to provide one or more execution conditions for the mobility procedure that comprises one or bothof the following:an indication to provide LI execution conditions,an indication to provide L3 execution conditions.

42. The method of any of claims 34 to 41, wherein the request to provide the TA related information comprises an explicit request to configure a TAT value within a TA acquisition configuration for the UE.

43. The method of any of claims 34 to 41, wherein the request to provide the TA related information comprises a request to include a TAT value within the TA related information.

44. The method of any of claims 34 to 43, further comprising determining (302) whether to provide a Time Alignment Timer, TAT, value for the candidate target cell to the first network node to be forwarded to the UE, wherein the determining comprises implicitly determining that a TAT value is to be provided within a TA acquisition configuration for the UE based on a presence of a request to provide one or more execution conditions for the mobility procedure.

45. The method of any of claims 34 to 44, wherein the second network node provides the TAT value for the candidate target cell to the first network node within a container.

46. The method of any of claims 34 to 44, wherein the second network node provides the TAT value for the candidate target cell to the first network node in an explicit way.

47. The method of any of claims 34 to 43, further comprising determining (302) whether to provide a Time Alignment Timer, TAT, value for the candidate target cell to the first network node to be forwarded to the UE, wherein the determining comprises implicitly determining that a TAT value is requested based on a presence of a request to provide LI execution conditions for the mobility procedure.

48. The method of any of claims 34 to 43, further comprising determining (302) whether to provide a Time Alignment Timer, TAT, value for the candidate target cell to the first network node to be forwarded to the UE, wherein the determining comprises implicitly determining that a TAT value is requested based on the presence of the request to provide L3 execution conditions for a mobility procedure.

49. The method of any of claims 34 to 43, further comprising determining (302) whether to provide a Time Alignment Timer, TAT, value for the candidate target cell to the first network node to be forwarded to the UE, wherein the determining comprises implicitly determining that a TAT value is requested based on receiving an indication that Conditional LTM is being prepared.

50. The method of any of claims 34 to 43, further comprising determining (302) whether to provide a Time Alignment Timer, TAT, value for the candidate target cell to the first network node to be forwarded to the UE, wherein the determining comprises implicitly determining that a TAT value is requested based on receiving an indication that Conditional LTM is being prepared and one of LI execution conditions or L3 execution conditions are not requested.

51. The method of any of claims 34 to 50, wherein a TAT value sent from the second network node to the first network node in the second message is provided for the specific UE.

52. The method of any of claims 34 to 50, wherein a TAT value sent from the second network node to the first network node in the second message is provided for a specific UE and a group of cells.

53. The method of any of claims 34 to 52, wherein the second network node transmits a TAT value to the first network node in response to receiving a request for the TAT value.

54. The method of any of claims 34 to 53, wherein the first message is received and the second message is transmitted using one or more F1AP procedures.

55. The method of any of claims 34 to 53, wherein the first message is received and the second message is transmitted using one or more XnAP procedures.

56. A second network node (710; 1000) for operation or control of a candidate target cell for a conditional mobility procedure for a User Equipment, UE, the second network node comprising:a communication interface (1006); andprocessing circuitry (1002) associated with the communication interface (1006), the processing circuitry (1002) configured to cause the second network node (710; 1000) to:receive (300), from a first network node, a first message comprising a request to provide Timing Advance, TA, related information for the candidate target cell; andtransmit (304), to the first network node, a second message comprising the requested TA information.

57. A method performed by a third network node, the method comprising:transmitting (400) to a first network node that operates or controls a source or serving cell of a User Equipment, UE, a message comprising Time Alignment Timer, TAT, information per cell for one or more cells.

58. The method of claim 57, wherein the message is transmitted using one or more F1AP procedures.

59. The method of claim 57 or 58, wherein the one or more cells comprise one or more candidate target cells for a mobility procedure for a User Equipment, UE, where the one or more candidate target cells are operated or controlled by a second network node.

60. A third network node (1000), comprising:a communication interface (1006); andprocessing circuitry (1002) associated with the communication interface (1006), the processing circuitry (1002) configured to cause the first network node (1000) to transmit (400) to a first network node that operates or controls a source or serving cell of a User Equipment, UE, a message comprising Time Alignment Timer, TAT, information per cell for one or more cells.