Methods, apparatus and comptuer-readable media relating to timing advance and mobility

By using stored timing advance values for RACH-less mobility during LTM, the UE can perform faster and more efficient cell transitions without random access procedures, addressing the ambiguity in existing 3GPP specifications.

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

Patent Information

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

Smart Images

  • Figure SE2026050299_12112026_PF_FP_ABST
    Figure SE2026050299_12112026_PF_FP_ABST
Patent Text Reader

Abstract

Embodiments described herein related to methods and apparatus related to time advance and mobility. A method performed by a wireless device comprises: obtaining a first timing advance value for communicating with a first LTM candidate cell, the wireless device stores an LTM configuration for the first LTM candidate cell. The method comprises receiving an instruction to initiate an LTM mobility procedure to the first LTM candidate cell. The instruction comprises a timing advance value field set to a null value FFF. The method comprises performing an LTM mobility procedure to the first LTM candidate cell, responsive to the instruction comprises the timing advance value field set to the null value FFF. The LTM mobility procedure comprises using the first timing advance value to communicate with the first LTM candidate cell without performing a random-access procedure.
Need to check novelty before this filing date? Find Prior Art

Description

METHODS, APPARATUS AND COMPTUER-READABLE MEDIA RELATING TO TIMING ADVANCE AND MOBILITYTECHNICAL FIELDEmbodiments described herein relate to methods and apparatus relating to timing advance and mobility procedures.BACKGROUNDTiming Advance

[0001] The Timing Advance (TA) is used by the User Equipment (UE) to synchronize the uplink transmission at the gNodeB (gNB) receiving side. Each UE will apply an individual TA to ensure that all transmissions towards a gNB arrives within the scheduled time window.

[0002] In RRC IDLE, the UE has no TA value since there is no uplink transmission. The reading of System Information is downlink oriented and hence does not require TA.

[0003] In RRC INACTIVE, the UE has no TA value since there is no uplink transmission. There is one exception however, with the addition of Small Data Transmission in Rel-17 and 18, methods for maintaining a TA value has been added.

[0004] In RRC CONNECTED, the UE maintains a TA value. This TA value is sent from the network to the UE in Msg2, based on the preamble in Msgl, see Figure 1.

[0005] During RRC CONNECTED, the UE maintains this TA by continuously monitoring how the downlink signal aligns within the slotted structure and makes small adjustments. If the gNB notices the UE falling out of synchronization, it can send a PDCCH Order to force the UE to send a new PRACH preamble and re-synchronize.

[0006] For the reason of maintaining an acquired TA value there is a number of TA validity timers, e.g. timeAlignmentTimer (3GPP TS 38.321) that is used within the MAC specification. These timers set a time range for when the TA value is considered as valid and are reset during the specification.3GPP TS 38.321 - Chapter 5.2RRC configures the following parameters for the maintenance of UL time alignment:- timeAlignmentTimer (per TAG) which controls how long the MAC entity considers the Serving Cells to the associated TAG to be uplink time aligned for the TAG;- InactivePosSRS-TimeAlignmentTimer which controls how long the MAC entity considers the Positioning SRS transmission in RRC INACTIVE in clause 5.26 to be uplink time aligned;- cg-SDT-TimeAlignmentTimer which controls how long the MAC entity considers the uplink transmission for CG-SDT to be uplink time aligned;- inactivePosSRS-ValidityAreaTAT which controls how long the MAC entity considers Positioning SRStransmission in RRC INACTIVE in clause 5.26 to be uplink time aligned when SRS positioning validity area is configured.3GPP TS 38.321 - Chapter 5.21> when a Timing Advance Command is received in a Random Access Response message for a Serving Cell configured with two TAGs or in a MSGB for an SpCell configured with two TAGs:2> if the Random Access Preamble was not selected by the MAC entity among the contention-based Random Access Preamble:3> apply the Timing Advance Command for the TAG indicated in the received Random Access Response message or MSGB;3> start or restart the timeAlignmentTimer associated with TAG indicated in the received Random Access Response message or MSGB.

[0007] Also, for Rel-18 (non-conditional) LTM, the network can send a cell switch command indicating a TA command as ‘FFF’, meaning that the UE should use a TA value it might have acquired through UE based TA estimation.SUMMARYCurrent situation in 3GPP for Rel-19TA signaling

[0008] So far, agreements have been made in 3GPP to maintain the TA values and keep the corresponding timer running for other candidate cells when executing a conditional cell switch:| RAN2#129bis:• Upon C-LTM execution, UE performs the following for received TA values and TA timers for other candidate cells than the target candidate cell: Maintain the TA value and Keep the early TA timer running.• 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 PT AG using the remaining time from the C-LTM timer.

[0009] It is a possibility that 3 GPP might agree to let the new source cell aware of these TA values in some way, wither by letting the source transfer this to the target, or let the UE send them to the target (new source) during the completion procedure.Early delivery of TA value

[0010] During the work of conditional LTM in Rel-19 it has been agreed that the network can deliver a TA value by a MAC CE to the UE. In Rel-18 for non-conditional LTM this TA value would be delivered in the cell switch command, but for conditional LTM there is no cell switch command since it is decided by the UE.RAN2#128• The Early TA is signalled to the UE from the source cell (i.e. , not from the candidate cell directly to the UE). This agreement will be included in the LS to RAN1 / 3 / 4. • The network can inform the candidate cell’s TA information to UE via new MAC CE,which is the TA value when UE switches to that candidate cell during CLTM.LTM Candidates

[0011] An LTM candidate is present already in Rel-18. For Rel-19 with the introduction of conditional LTM, the running CR which is endorsed treats a conditional LTM configuration like a normal LTM candidate, but with associated execution conditions. This means that a UE can use an LTM candidate with associated execution conditions to execute a cell switch to that cell.Network triggered cell switch

[0012] It has also been agreed that the network can trigger a cell switch to a candidate for which there are also one or more associated execution conditions:RAN2#129bis• Network can send an LTM Cell Switch Command MAC CE indicating a CLTMcandidate configuration (no specification change).

[0013] There currently exist certain challenge(s). Based on the agreements described above, the UE receives a TA value for one or more candidate cells via a dedicated MAC CE.Since the network may send an LTM cell switch command for a candidate cell to a UE which has already received a TA value for that particular candidate cell, it is not clear how the UE should treat the stored TA. For example, If the UE should not consider the stored TA and the LTM cell switch command has no TA included, this means that the UE will be forced to execute a RACH-based LTM cell switch procedure, even if a TA value was available and the LTM cell switch could have been done without the random access procedure.

[0014] Since no behaviour is specified, at the moment it is not clear whether a RACH-less procedure will be executed or not and this may cause the mobility procedure to be slower, with a consequent increase in the connectivity interruption.

[0015] According to a first aspect of the invention, a method performed by a wireless device is provided. The method comprises obtaining a first timing advance value for communicating with a first Layer 1 / Layer 2 Triggered Mobility candidate cell. The wireless device stores an LTM configuration for the first LTM candidate cell. The method comprises receiving, from a first network node, an instruction to initiate an LTM mobility procedure to the first LTM candidate cell. The instruction comprises a timing advance value field set to a null value FFF. The method comprises performing an LTM mobility procedure to the first LTM candidate cell responsive to the instruction comprises the timing advance value field set to the null value FFF. The LTM mobility procedure comprises using the first timing advance value to communicate with the first LTM candidate cell without performing a random-access procedure.

[0016] According to a second aspect of the invention, a method performed by a first network node is provided. The method comprises transmitting, to a wireless device, an instruction to initiate an Layerl / Layer2 Triggered Mobility procedure to a first LTM candidate cell. The instruction comprises a timing advance value filed set to a null value FFF. The wireless device stores a first timing advance value for communicating with the first LTM candidate cell. The wireless device further stores an LTM configuration for the first LTM candidate cell.

[0017] According to a third aspect of the invention, a wireless device is provided. The wireless device comprises processing circuitry configured to cause the wireless device to perform any steps of the method of the first aspect as described herein. The wireless device comprises a power source configured to supply power to the processing circuitry.

[0018] According to a fourth aspect of the invention, a network node is provided. The network node comprises processing circuitry configured to cause the network node to perform any of the operations of any of the steps of the method of the second aspect asdescribed herein. The network node comprises a power source configured to supply power to the processing circuitry.

[0019] According to a fifth aspect of the invention, a wireless device is provided. The wireless device comprises one or more antennas; communication interface connected to the one or more antennas and to processing circuitry; the processing circuitry being configured to cause the wireless device to perform any of the operations of any of the steps of the method of the first aspect as described herein; an input interface connected to the processing circuitry and configured to allow input of information into the wireless device to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the wireless device that has been processed by the processing circuitry; and a power source connected to the processing circuitry and configured to supply power to the wireless device.

[0020] According to a sixth aspect of the invention, a computer program product is provided. The computer program product comprises a non-transitory computer-readable medium having computer-readable embodied therein, the computer-readable code being configured such that, on execution by a suitable computer or processing circuitry, the computer or processing circuitry is caused to perform the method of any of steps of the first aspect and / or any of the second aspect.

[0021] According to a seventh aspect of the invention, a wireless device is provided. The wireless device is configured to perform the method of the first aspect as described herein.

[0022] According to an eighth aspect of the invention, a wireless device is provided. The wireless device comprises processing circuitry and a memory, said memory containing instructions executable by said processing circuitry whereby said wireless device is operative to perform the method of the first aspect as described herein.

[0023] According to a ninth aspect of the invention, a network node is provided. The network node is configured to perform the method of the second aspect as described herein.

[0024] According to a tenth aspect of the invention, a network node is provided. The network node comprises processing circuitry and a memory, said memory containing instructions executable by said processing circuitry whereby said network node is operative to perform the method of the second aspect as described herein.

[0025] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, some embodiments of the disclosure introduce methods to let the UE use a stored TA and perform a RACH-less mobility procedure for a candidate cell, especially in the case when a mobility command is received and a TA for the candidatecell is not included. Embodiments of the disclosure may additionally or alternatively introduce methods that establish a priority between a TA value already stored at the UE (e.g., a TA value with a running TA validity timer) and a TA value sent through a mobility command (e.g., an LTM Cell Switch Command MAC CE).

[0026] Certain embodiments may provide one or more of the following technical advantage(s). For example, the methods and solutions disclosed herein may allow the UE to use a stored TA and perform a RACH-less mobility procedure for a candidate cell, especially in the case when a mobility command is received and a TA for the candidate cell is not included. This means that a RACH-less mobility procedure may be executed with a consequently shorter mobility execution procedure and a shorter connectivity interruption.BRIEF DESCRIPTION OF THE DRAWINGS

[0027] For a better understanding of the embodiments of the present disclosure, and to show how it may be put into effect, reference will now be made, by way of example only, to the accompanying drawings, in which:

[0028] Figure 1 is a schematic diagram illustrating a procedure for maintaining a TA value at a wireless device;

[0029] Fig. 2 is a flow chart illustrating a method in accordance with some embodiments;

[0030] Fig. 3 is a flow chart illustrating a method in accordance with some embodiments;

[0031] Fig. 4 shows an example of a communication system in accordance with some embodiments;

[0032] Fig. QQ2 shows an example of another communication system in accordance with some embodiments;

[0033] Fig. 5 shows a wireless device in accordance with some embodiments;

[0034] Fig. 6 shows a network node in accordance with some embodiments; and

[0035] Fig. 7 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.DETAILED DESCRIPTION

[0036] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of exampleto convey the scope of the subject matter to those skilled in the art. Additional information may also be found in the document(s) provided in the Appendix.

[0037] The text refers to the term “L1 / L2 based inter-cell mobility” as used in the Work Item Description in 3GPP, though it interchangeably also uses the terms L1 / L2 mobility, Ll-mobility, LI based mobility, Ll / L2-centric inter-cell mobility, L1 / L2 inter-cell mobility Ll / L2-Triggered Mobility, Lower-layer triggered Mobility or LTM. The basic principle is that the UE normally 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 PCell, from a source to a target PCell), wherein a lower layer signaling is a message / signaling of a lower layer protocol, which sometimes 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 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 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 an RRC Reconfiguration message, with at least one LTM candidate cell configuration). An LTM candidate cell configuration may include parameters in the IE CellGroupConfig for an LTM candidate cell and / or an embedded RRC Reconfiguration for an LTM candidate cell.

[0038] The term LTM cell switch procedure 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 neighbour cell), using Ll / L2-triggered mobility (LTM). In the context of L1 / L2-triggered mobility (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 Master Cell Group (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.

[0039] Even if the term switch or change of cells is used, that may comprise a switch or 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).

[0040] An LTM cell switch procedure may be triggered in the UE by reception of a 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.

[0041] The text refers to an LTM candidate cell, which is a cell the UE is configured with when configured with Ll / L2-triggered mobility. That is a cell the UE can move to in an LTM cell switch procedure. Such cells may also be called candidate cell(s), candidates, mobility candidates, non-serving cells, additional cells, target candidate cell, target candidate, etc. A LTM candidate cell is a cell the UE may perform measurements on (e.g. CSI measurements) so that the UE reports these measurements and network may take educated decision on which beam (e.g. 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 or a SCG SCell).

[0042] The text refers to at least one LTM candidate cell configuration and that the UE has received at least one LTM candidate cell configuration. This is also sometimes referred to as a configuration of a LTM candidate cell, which may be an RRC configuration, such as encapsulated in an RRC Reconfiguration message, that the UE receives when being configured with Ll / L2-Triggered Mobility. An LTM candidate cell configuration comprises the configuration which the UE needs to start to operate accordingly when it performs an LTM cell switch procedure to that LTM candidate cell e.g. upon reception of the LTM cell switch command indicating the UE to perform a LTM cell switch procedure to that LTM candidate cell, which becomes the target cell and the current (new) SpCell, or an SCell in a serving frequency. The LTM candidate cell configuration comprises parameters of a serving cell (or multiple serving cells, such as a cell group), comprising one or more of the groups of parameters, such as an RRCReconfiguration message an IE CellGroupConfig or an IE SpCellConfig (or the IE SCellConfig, in the case of a Secondary Cell). An LTM candidate cell configuration may in one example comprise one or more of: i) the PCell configuration and one or more SCell configuration(s) of a Master Cell Group (MCG); i) the PSCell configuration and one or more SCell configuration(s) of a secondary Cell Group (SCG). The terms (LTM) candidate configuration, LTM configuration, (LTM) candidate target cell configuration, (LTM) target candidate (cell) configuration may be used interchangeably when referring to LTM candidate cell configuration. An LTM candidate cell configuration may be associated with an identifier which is used in the signaling when referring to a certain LTM candidate cell configuration, such as when the UE receives the LTM candidate cell configuration and whenthe UE receives an LTM cell switch command indicating the UE to perform an LTM cell switch procedure to that LTM candidate cell. This identifier is sometimes known as the LTM candidate cell configuration identity or LTM candidate configuration index (or similar).

[0043] The actual LTM candidate cell configuration and its exact content and / or structure of this IE and / or embedded message may be called an RRC model for the candidate configuration, or simply RRC model. An LTM candidate cell configuration comprises the configuration which the UE needs to operate accordingly when it performs (executes) L1 / L2 based inter-cell mobility execution to a LTM candidate cell, upon reception of the lower layer signaling (MAC CE) indicating a L1 / L2 based inter-cell mobility to a LTM candidate cell (which becomes the target cell and the current (new) PCell, or an SCell in a serving frequency), or upon reception of the lower layer signaling (MAC CE) indicating a L1 / L2 based inter-cell mobility to a LTM candidate cell configuration indicated with a candidate configuration index (sometimes also denoted candidate configuration ID). The UE may be configured with multiple LTM candidate cell configurations, so a Candidate DU generates and sends to the CU multiple configuration(s). The actual LTM candidate cell configuration the UE receives during the LTM configuration may be a delta signaling to be applied on top of a reference configuration, so that the actual configuration the UE is to use in the candidate cell upon LTM cell switch is the combination of the LTM candidate cell configuration and the reference configuration (e.g. separately signaled by the network to the UE).

[0044] In this disclosure, the term LTM related mobility procedure refers to Lower Layer Triggered Mobility cell switch that might be in the form of:• a network triggered intra-CU or inter-CU LTM Cell switch• a UE controlled conditional LTM Cell switch

[0045] This means that, in the following methods, when the UE performs a mobility procedure to switch from a source cell to a target cell, this mobility procedure can be either triggered by the network (e.g., for the case of LTM) or triggered by the UE itself (e.g., for the case of conditional LTM).

[0046] One focus of the present disclosure is to provide methods for the UE to determine whether it is possible to extend the validity of a TA value received by the network. However, how the TA value is calculated by the network and how the TA value is delivered to the UE is out of scope of this disclosure. One assumption may be that for the TA acquisition and calculation the framework agreed and specified in Rel-18 within the context of LTM (and captured in TS 38.300 V18.0.0) is re-used as baseline.

[0047] The text uses the term “cell” to identify a location (or coverage) on which the UE is located. However, the term “cell” can also be exchanged without any loss of meaning with the terms “radio resources”, “beams”, “TCI state”, or “TRS”. This is just to clarify that this disclosure does not target specifically a scenario where there is a cell, but rather when a UE uses a set of source radio resources and need to switch to a target set of radio resources. In such a case, radio resource can also identify a set of configurations, field, parameters, or ASN.l structures or IES.

[0048] The text further uses the term MCG to identify a first network node that provides a first connectivity link to the UE and SCG to identify e second network node that provides a second connectivity link to the UE. However, the terms “MCG” and “MN” can be exchanged without any loss of meaning as well as the terms “SCG” and “SN”

[0049] The text refers to a mobility procedure, configuration of a mobility procedure or execution of a mobility procedure. In the context of this disclosure, a mobility procedure may be L1 / L2 Triggered Mobility, LTM, inter-CU LTM, inter-SN LTM, L3 handover, PCell handover, conditional handover (CHO), conditional LTM, PSCell change or conditional PSCell Addition or Change (CP AC). The solutions described in the disclosure sometimes uses the inter-SN LTM as the example. However, many of the examples may also be applied for other mobility procedures, for example, LTM, inter-CU LTM, conditional LTM or CHO.

[0050] The text refers to a mobility configuration. When the UE has been configured with a mobility configuration, it may use the mobility configuration during preparation of a mobility procedure, including measurements (such as RSRP measurements on neighbor or serving cells), triggering and transmission of measurement reports, synchronization towards neighbor cells, evaluation of conditions (for conditional mobility, e.g. CHO), and during the execution of a mobility procedure (e.g. execution of an LTM cell switch procedure, execution of an inter-MN LTM cell switch procedure or execution of handover).

[0051] A mobility configuration may include one or multiple of the following type of elements where each element contains a configuration of one aspect of LTM, for example as follows:• LTM candidate cell configuration(s),• inter-CU LTM candidate cell configuration(s),• lower layer information, such as physical layer configuration, MAC layer configuration or RLC layer configuration, Cell Group configuration, serving cell configuration• higher layer information, such as RRC protocol parameters, such as timer values, PDCP layer configuration, radio bearer configuration or measurement configuration• Configuration of measurements for LTM• Configuration for measurement reports for LTM• CSI resource configuration(s) for LTM• CSI report configuration for LTM• Configurations of early synchronization procedures, such aso Configurations for DL pre-sync for LTM, such as configurations for early TCI state activationo Configurations for UL pre-sync for LTM, such as configurations for reception of PDCCH ordered triggered preamble transmission and reception of TA• Configurations for the execution of an LTM cell switch procedure for a given LTM candidate cell configuration or inter-CU LTM candidate cell configuration (e.g., whether to perform random access procedure, whether to perform RLC reestablishment, or MAC reset, or PDCP recovery), a timer value, configured UL grants, dedicated RA preambles.• A configuration which the UE needs to start to operate accordingly when it performs an LTM cell switch procedure to an LTM candidate cell which is controlled by a different base station, e.g. gNB, from the current source base station e.g. serving gNB of the UE.• Information to perform security key refresh, e.g. the RRC IE MasterKeyUpdate or a RRC IE RadioBearerConfig that includes SecurityConfig with S ecurity AlgorithmC onfig.• Indication to perform a full configuration, e.g. the RRC field fullConfig.• Indication to perform L2 re-establishment, such as an indication to perform PDCP re-establishment for one or multiple bearers.• One or more lists of sk-counters values.• One or more conditional execution conditions

[0052] The term “LTM” or “L1 / L2 triggered mobility” include also the case of 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 CLTMcandidate cell), by receiving an LTM candidate cell configuration, as in legacy LTM, and called herein a Conditional LTM candidate cell configuration, and an associated execution condition, denoted as 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 SS-RSRP, derived from SSBs and / or CSI-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 aren't 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 RSRP, reference signal received quality (RSRQ) or signal-to-interference-plus-noise ratio (SINR), time-to-trigger (TTT), and so forth.

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

[0054] The text also discusses the concept of 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, or L1 / L2 inter-cell mobility candidate cell, depending on the context or terminology used in this 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 sourcecell 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 5G Radio Access Technology like NR or a future 6G Radio Access Technology.

[0055] In the methods outlined below, the UE may receive an LTM candidate cell configuration for Conditional LTM, typically through an RRC Reconfiguration message, which is stored in the UE and applied upon fulfillment of the associated CLTM execution conditions. An LTM candidate cell configuration comprises the configuration which the UE needs to start to operate accordingly when it performs a Conditional LTM execution to that LTM candidate cell e.g., upon the fulfilment of CLTM execution conditions. A candidate cell configuration may include parameters in the information element (IE) CellGroupConfig per LTM candidate cell and / or an embedded RRC Reconfiguration per candidate cell. An LTM candidate cell configuration may be associated with an identifier which can then be used in the signaling when referring to a certain LTM candidate cell configuration, such as when performing the early UL or DL synchronization with that LTM cell. This identifier is sometimes known as the LTM candidate cell configuration identifier (ID) or LTM candidate configuration index (or similar).

[0056] Additionally or alternatively, a TA value may be obtained for the UE for early UL synchronization. This allows the UE to prevent the transmission of a PRACH (Physical Random-Access Channel) preamble, and consequently, the reception of a corresponding Random-Access Response (RAR) message during the access to that target cell and reduce handover interruption. This acquisition facilitates the UE to execute a RACH-less access to the target cell during the handover procedure. In a RACH-less access, the UE has a valid TA for the selected LTM or CLTM candidate cell. In other words, the time alignment timer (TAT) for the earlier acquired TA value for an LTM candidate cell is still running or not expired yet.

[0057] Figure 2 depicts a method in accordance with particular embodiments. The method may be performed by a wireless device (e.g. UE 412, station QQ212 or wireless device 500 as described later with reference to Figures 4, QQ2 and 5 respectively). The method depicted in Figure 2 involves signalling with one or more network nodes. A corresponding method performed by one such network node is described below with respect to Figure 3. Those skilled in the art will appreciate that aspects of the description in Figure 2 are applicable to the description of the method shown in Figure 3, and vice versa.

[0058] The method begins at step 202, in which the wireless device may receive an LTM configuration for a first LTM candidate cell. The LTM configuration may comprise one or more of: information that enables the wireless device to perform an LTM mobility procedure to the first LTM candidate cell; information that enables the wireless device to communicate with the first LTM candidate cell following execution of the mobility procedure.

[0059] The LTM configuration may additionally comprise or be associated with one or more execution conditions (e.g., based on radio measurements performed on transmissions by a serving cell or network node, and by the LTM candidate cell or a network node serving such a cell). Upon fulfilment of one or more of those execution conditions, the wireless device may execute the LTM mobility procedure to the LTM candidate cell without further instruction from the network. In this case, the LTM configuration may be referred to as a conditional LTM configuration. In the absence of such execution condition(s), the LTM configuration is a “regular” (i.e., non-conditional) LTM configuration.

[0060] In step 204, the wireless device obtains a first timing advance (TA) value for communicating with the first LTM candidate cell, e.g., for use in early synchronization with the first LTM candidate cell.

[0061] The first TA value may be obtained by receiving an indication of the first timing advance value from the network, e.g., from a first network node (such as a serving or source network node). The indication of the first TA value may be received in a separate message, prior to the instruction to initiate the LTM mobility procedure (see step 206 below), such as a Timing Advance Command message. The indication may be received in an existing (e.g., legacy) or new (e.g., newly defined) RRC message, an existing (e.g., legacy) or new (e.g., newly defined) MAC CE; and / or an existing (e.g., legacy) or new (e.g., newly defined) LI signal (e.g., DCI).

[0062] Additionally or alternatively, the wireless device may obtain the first timing advance value by performing measurements on transmissions by the LTM candidate cell to determine the first timing advance value. That is, the wireless device calculates or estimates the first timing advance value itself, e.g., by following the procedures set out in 3GPP TS 38.300 V18.0.0. Note that, in some embodiments, the wireless device may both receive an indication of the first TA value and also calculate the first TA value. That is, the wireless device may obtain two TA values for use in communicating with the LTE candidate cell prior to receiving any instruction to perform an LTM mobility procedure to that LTE candidate cell.

[0063] In step 206, the wireless device receives an instruction to initiate an LTM mobility procedure to the first LTM candidate cell. For example, the instruction may comprise an LTMcell switch command (or other suitable message where a different mobility is contemplated than handover). The instruction may be received in an existing (e.g., legacy) or new (e.g., newly defined) RRC message, an existing (e.g., legacy) or new (e.g., newly defined) MAC CE; and / or an existing (e.g., legacy) or new (e.g., newly defined) LI signal (e.g., DCI). The instruction comprises a timing advance value field set to a null value FFF.

[0064] The mobility procedure may involve mobility from the first network node (e.g., which becomes the source network node) to a second network node serving the LTM candidate cell (e.g., which becomes the target network node). The first network node may therefore be a source gNB-DU, a source gNB-CU, or a source gNB. The second network node may be a target gNB-DU, a target gNB-CU, or a target gNB. The LTM mobility procedure may therefore be intra-CU (inter-DU) mobility or inter-CU mobility.

[0065] In step 208, the wireless device executes or performs an LTM mobility procedure to the first LTM candidate cell. Responsive to a first condition which is the instruction comprising the timing advance value filed being set to null value FFF, the LTM mobility procedure may include using the first TA value (i.e., the TA value obtained in step 204) to communicate with the first LTM candidate cell without performing a random-access procedure (e.g., RACH-less mobility or access).

[0066] The instruction may contain no timing advance value for communicating with the LTM candidate cell. For example, the instruction may comprise no field for indicating the timing advance value (e.g., the field is absent from the message), or the field may comprise a null or other special value indicating that the wireless device is to use the first TA value for RACH-less mobility, e.g., “FFF” (representing hexadecimal digits). Note that, in this latter case, the instruction nonetheless does not contain any indication of a TA value that the wireless device may use for communicating with the LTM candidate cell.

[0067] A second condition, responsive to which the LTM procedure is performed, may be that the obtained first timing advance value is valid when the instruction is received and / or when the LTM mobility procedure is performed. For example, the first TA value may be associated with a validity timer, such as TimingAdvanceTimer (TAT), which is started or restarted (e.g., reset) upon obtaining the first TA value in step 204. The first timing advance value may be determined to be valid if that timer associated with the timing advance value is running (i.e., has not expired) when the instruction is received in step 206 and / or when the LTM mobility procedure is performed in step 208.

[0068] The wireless device may use the first TA value for RACH-less mobility to the LTM candidate cell responsive to fulfilment of both first and second conditions, or responsive tofulfilment of at least the first or second condition, e.g., the first TA value is used for RACH-less mobility to the LTM candidate cell responsive to the instruction containing no indication of a TA value; responsive to the obtained first TA value being valid; or responsive to both the instruction containing no indication of a TA value and the obtained first TA value being valid.

[0069] The wireless device may determine to perform a RACH-less mobility procedure when one or more of the following conditions apply:• The wireless device has already received a TA value before the reception of a mobility command, and the received mobility command does not comprise a TA value.• The wireless device has already calculated a TA value before the reception of a mobility command, and the received mobility command does not comprise a TA value.• The wireless device has a TAT running before the reception of a mobility command, and the received mobility command does not comprise a TA value.• The wireless device has a valid TA before the reception of a mobility command, and the received mobility command does not comprise a TA value • The wireless device has more than a TA value available before the reception of a mobility command, and the received mobility command does not comprise a TA value• The wireless device has already received a TA value before the reception of a mobility command, and the received mobility command comprises a TA value set to a value which indicates that such TA value should be ignored / discarded.• The wireless device has already calculated a TA value before the reception of a mobility command, and the received mobility command comprises a TA value set to a value which indicates that such TA value should be ignored / discarded.• The wireless device has a TAT running before the reception of a mobility command, and the received mobility command comprise a TA value set to a value which indicate that such TA value should be ignored / discarded.• The wireless device has a valid TA before the reception of a mobility command, and the received mobility command comprises a TA value set to a value which indicates that such TA value should be ignored / discarded• The wireless device has more than a TA value available before the reception of a mobility command, and the received mobility command comprises a TA value set to a value which indicates that such TA value should be ignored / discarded.

[0070] Responsive to at least one of the conditions not being fulfilled (or responsive to all conditions not being fulfilled), the wireless device may perform the LTM mobility procedure to the LTM candidate cell differently. For example, responsive to a determination that the instruction comprises an indication of a second timing advance value for communication with the LTE candidate cell, the wireless device may perform an LTM mobility procedure to the LTM candidate cell, including using the second timing advance value to communicate with the LTM candidate cell without performing a random-access procedure. That is, the wireless device uses the TA value indicated in the instruction to execute the LTM mobility procedure, rather than the TA value obtained in step 204. The wireless device may further stop any timer (e.g., TAT) related to the first TA value obtained in step 204, and start anew timer (e.g., TAT) related to the second TA value received within the instruction.

[0071] In general, the wireless device may obtain a plurality of timing advance values for communication with the LTE candidate cell. The plurality of TA values may include two or more of: the first timing advance value, being received from the first network node prior to the instruction to initiate the LTM mobility procedure; a second timing advance value, being received from the first network node in the instruction; and a third timing advance value, being calculated by the wireless device. In such circumstances, the wireless device may select one of the first, second and third timing advance values to communicate with the LTM candidate cell without performing a random-access procedure.

[0072] The timing advance value may be selected according to one or more of the following rules:• The first timing advance value is selected if available;• The second timing advance value is selected if available• The third timing advance value is selected if available;• The timing advance value associated with the greatest remaining timer value is selected;• The timing advance value associated with the greatest timer value (e.g., the greatest initial time value) is selected;• The timing advance value associated with the smallest remaining timer value is selected;• The timing advance value associated with the smallest timer value (e.g., the smallest initial time value) is selected;• The timing advance value is selected based on an indication from the network (e.g., the first network node)

[0073] In other embodiments, if the UE has received a TA value from the first network node within a first message, has calculated a TA value by itself, and has received a TA value also in the mobility command within a second message from the first network node, the UE applies one or more of the following rules to select a TA value to use for the mobility procedure:• The TA value received within the mobility command is selected to be used when performing a mobility procedure without any random access procedure.• The TA value calculated by itself is selected to be used when performing a mobility procedure without any random access procedure.• The TA value received from the first network node within the first message is selected to be used when performing a mobility procedure without any random access procedure• The TA with the largest TAT value is selected to be used when performing a mobility procedure without any random access procedure• The TA with the largest remaining TAT (if running) is selected to be used when performing a mobility procedure without any random access procedure• The TA with the smaller value is selected to be used when performing a mobility procedure without any random access procedure• The TA is selected according to a network indication

[0074] Those skilled in the art will appreciate that the messages received from the network in the method described above may be transmitted by the same or different network nodes. In one embodiment, where step 204 comprises the wireless device receiving the first TA value from the network, the first TA value may be transmitted by the same network node that transmits the instruction in step 206 (referred to herein as the first network node). The first network node may be a serving network node for the wireless device, and may be the source network node (or may serve the source cell) for the LTM mobility procedure. The LTM configuration may also be transmitted by the first network node; however, the wireless device may maintain its LTM configurations following a mobility procedure. Accordingly, the wireless device may receive the LTM configuration in step 202 from a different network node than the node which then transmits the instruction in step 206 (e.g., in circumstances where the wireless device has performed mobility between steps 202 and 206).

[0075] Figure 3 depicts a method in accordance with particular embodiments. The method 3 may be performed by a first network node (e.g. network node 410, access point QQ210 or network node 600 as described later with reference to Figures 4, QQ2 and 6 respectively). The method depicted in Figure 3 involves signalling with a wireless device. A corresponding method performed by such a wireless device is described above with respect to Figure 2. Thoseskilled in the art will appreciate that aspects of the description in Figure 3 are applicable to the description of the method shown in Figure 2, and vice versa.

[0076] The method begins at step 302, in which the first network node may transmit, to a wireless device, an LTM configuration for a first LTM candidate cell. The LTM configuration may comprise one or more of: information that enables the wireless device to perform an LTM mobility procedure to the first LTM candidate cell; information that enables the wireless device to communicate with the first LTM candidate cell following execution of the mobility procedure.

[0077] The LTM configuration may additionally comprise or be associated with one or more execution conditions (e.g., based on radio measurements performed on transmissions by a serving cell or network node, and by the LTM candidate cell or a network node serving such a cell). Upon fulfilment of one or more of those execution conditions, the wireless device may execute the LTM mobility procedure to the LTM candidate cell without further instruction from the network. In this case, the LTM configuration may be referred to as a conditional LTM configuration. In the absence of such execution condition(s), the LTM configuration is a “regular” (i.e., non-conditional) LTM configuration.

[0078] In step 304, optionally, the first network node transmits an indication of a first timing advance (TA) value for communicating with the first LTM candidate cell, e.g., for use in early synchronization with the first LTM candidate cell. The wireless device may therefore obtain the first TA value by receiving an indication of the first timing advance value from the first network node. The indication of the first TA value may be transmitted in a separate message, prior to the instruction to initiate the LTM mobility procedure (see step 306 below), such as a Timing Advance Command message. The indication may be transmitted in an existing (e.g., legacy) or new (e.g., newly defined) RRC message, an existing (e.g., legacy) or new (e.g., newly defined) MAC CE; and / or an existing (e.g., legacy) or new (e.g., newly defined) LI signal (e.g., DCI).

[0079] Additionally or alternatively, however, the wireless device may obtain the first timing advance value by performing measurements on transmissions by the LTM candidate cell to determine the first timing advance value. That is, the wireless device calculates or estimates the first timing advance value itself, e.g., by following the procedures set out in 3GPP TS 38.300 vl 8.0.0. Note that, in some embodiments, the wireless device may both receive an indication of the first TA value and also calculate the first TA value. That is, the wireless device may obtain two TA values for use in communicating with the LTE candidate cell prior to receiving any instruction to perform an LTM mobility procedure to that LTE candidate cell.

[0080] In step 306, the first network node transmits, to the wireless device, an instruction to initiate an LTM mobility procedure to the first LTM candidate cell. For example, the instruction may comprise an LTM cell switch command (or other suitable message where a different mobility is contemplated than handover). The instruction may be transmitted in an existing (e.g., legacy) or new (e.g., newly defined) RRC message, an existing (e.g., legacy) or new (e.g., newly defined) MAC CE; and / or an existing (e.g., legacy) or new (e.g., newly defined) LI signal (e.g., DCI). The instruction comprises a timing advance value field set to a null value FFF.

[0081] The mobility procedure may involve mobility from the first network node (e.g., which becomes the source network node) to a second network node serving the LTM candidate cell (e.g., which becomes the target network node). The first network node may therefore be a source gNB-DU, a source gNB-CU, or a source gNB. The second network node may be a target gNB-DU, a target gNB-CU, or a target gNB. The LTM mobility procedure may therefore be intra-CU (inter-DU) mobility or inter-CU mobility.

[0082] Responsive to a determination that the wireless device is to perform the LTM mobility procedure using the first timing advance value to communicate with the LTM candidate cell without performing a random-access procedure, step 306 may comprise adapting the instruction to contain no timing advance value for communicating with the LTM candidate cell. For example, the instruction may comprise no field for indicating the timing advance value (e.g., the field is absent from the message), or the field may comprise a null or other special value indicating that the wireless device is to use the first TA value for RACH-less mobility, e.g., “FFF” (representing hexadecimal digits). Note that, in this latter case, the instruction nonetheless does not contain any indication of a TA value that the wireless device may use for communicating with the LTM candidate cell.

[0083] Responsive to a determination that the wireless device is to perform the LTM mobility procedure using a second timing advance value to communicate with the LTM candidate cell without performing a random-access procedure, step 306 may comprise adapting the instruction to contain an indication of the second timing advance value.

[0084] As noted above, those skilled in the art will appreciate that the messages transmitted in the method described above may be transmitted by the same or different network nodes. Accordingly, the method shown in Figure 3 is only one embodiment in which the same network node transmits all the messages in steps 302, 304 and 306. In one embodiment, the first TA value may be transmitted in step 304 by the same network node that transmits the instruction in step 306 (referred to herein as the first network node). The first network nodemay be a serving network node for the wireless device, and may be the source network node (or may serve the source cell) for the LTM mobility procedure. The LTM configuration may also be transmitted by the first network node, as shown in step 302; however, the wireless device may maintain its LTM configurations following a mobility procedure. Accordingly, the wireless device may receive the LTM configuration from a different network node than the node which then transmits the instruction in step 306 (e.g., in circumstances where the wireless device has performed mobility between receiving the LTM configuration and 206).

[0085] Figure 4 shows an example of a communication system 400 in accordance with some embodiments.

[0086] In the example, the communication system 400 includes a telecommunications network 402 that includes an access network 404, such as a radio access network (RAN), and a core network 406, which includes one or more core network nodes 408. The access network 404 includes one or more access network nodes or base stations of various types, access network nodes 410A and 410B are depicted (which may be collectively referred to as network nodes 410), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 404 may include more than one access network technology. The network nodes 410 of access network 404 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 412A, 412B, 412C, and 412D (one or more of which may be generally referred to as UEs 412) to the core network 406 over one or more wireless connections.

[0087] 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 402 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 402 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 402, including one or more access network nodes 410 and / or core network nodes 408.

[0088] 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 platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the 0-RAN Alliance or comparable technologies.

[0089] The network nodes 410 facilitate direct or indirect connection of one or more UEs 412 to the core network 406 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 400 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 400 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0090] The UEs 412 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 410 and other communication devices. Similarly, the network nodes 408, 410 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 402) with the UEs 412 and / or with other network nodes or equipment in the telecommunications network 402 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 402. More specifically, UEs 412 may sendmessages, data, and / or other signals to network nodes 408, 410 or other elements of the telecommunications network 402 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 408, 410 may send messages, data, and other signals to UEs 4122, other network nodes 408, 410, and other devices in telecommunications network 402 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 412 by transmitting the message to an access network node 410 that will then transmit the message to the intended UE 412. Similarly, a core network node 108 may receive a particular message from a UE 412 by receiving the message from an access network node 410 that itself received the message from the UE 412.

[0091] In the depicted example, the core network 406 connects elements of the access network 404 (e.g., one or more of the network nodes 410) to one or more host computing systems, such as host 416. 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 406 includes one or more core network nodes (e.g., core network node 408) of various types, one or more of which may be generally referred to as network nodes 408. Network nodes 408 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 408. 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).

[0092] The host 416 may be under the ownership or control of a service provider other than an operator or provider of the access network 404 and / or the telecommunications network 402. The host 416 may be operated by the service provider or on behalf of the service provider. The host 416 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 ofUEs, 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.

[0093] As a whole, the communication system 400 of Figure 4 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 400 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 400 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 400 supporting different standards, protocols, or rule sets.

[0094] As one example, in certain embodiments, access network 404 may contain some access network nodes 410 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 410 support (or the same access network nodes 410 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 402 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 104 and / or a core network 106 that supports multiple different standard generations or may include multiple access networks 104 and / or multiple core networks 106 with individual networks 104, 106 supporting different standard generations.

[0095] Telecommunications network 402 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 402. For example, the telecommunications network 402 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.

[0096] In some examples, one or more of the UEs 412 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 404 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 404. 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).

[0097] In the example, the hub 414 communicates with the access network 404 to facilitate indirect communication between one or more UEs (e.g., UE 412C and / or 412D) and network nodes (e.g., network node 410B). In some examples, the hub 414 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 414 may be a broadband router enabling access to the core network 406 for the UEs. As another example, the hub 414 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 410, or by executable code, script, process, or other instructions in the hub 414.

[0098] As another example, the hub 414 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 414 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 414 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 414 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 414 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0099] The hub 414 may have a constant / persistent or intermittent connection to the network node 410B. The hub 414 may also allow for a different communication scheme and / or schedule between the hub 414 and UEs (e.g., UE 412C and / or 412D), and between the hub 414 and the core network 406. In other examples, the hub 414 is connected to the core network 406 and / or one or more UEs via a wired connection. Moreover, the hub 414 may be configured to connect to an M2M service provider over the access network 404 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the networknodes 410 while still connected via the hub 414 via a wired or wireless connection. In some embodiments, the hub 414 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 41 OB. In other embodiments, the hub 414 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 41 OB, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0100] Figure 5 shows a wireless device 500, which may be configured to operate in communication system 400 of Figure 4. The wireless device 500 may be alternatively referred to as a UE 500, like a UE 412 within the context of communication system 400, or as a station (STA) 500 or as a non-access-point station (non-AP STA) 500, 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 vehicle embedded / 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-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0101] A wireless device 500 may support device-to-device (D2D) communication, for example by implementing a 3GPP 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 500 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 500 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 500 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).

[0102] In particular embodiments, wireless device 500 includes processing circuitry 502 that is operatively coupled via a bus 504 to an input / output interface 506, a power source 508,a memory 510, a communication interface 512, and / or any other component, or any combination thereof. Certain embodiments of wireless device 500 may include all or a subset of the components shown in Figure 5. The level of integration between the components may vary from one embodiment of wireless device 500 to another. In general, in a particular embodiment of wireless device 500, processing circuitry 502, input / output interface 506, power source 508, memory 510, and communication interface 512 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 500. Further, certain embodiments of wireless devices 500 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0103] The processing circuitry 502 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 510. The processing circuitry 502 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 502 may include multiple central processing units (CPUs). The processing circuitry 502 may be configured to cause the wireless device 500 to perform the methods as described with reference to Figure 2.

[0104] In the example, the input / output interface 506 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 500. 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 typeof 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.

[0105] In some embodiments, the power source 508 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 508 may further include power circuitry for delivering power from the power source 508 itself, and / or an external power source, to the various parts of wireless device 500 via input circuitry or an interface such as an electrical power cable. Power source 508 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 500 to which power is supplied.

[0106] The memory 510 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 510 includes one or more programs 514, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 516. The memory 510 may store, for use by wireless device 500, any of a variety of various operating systems or combinations of operating systems.

[0107] The memory 510 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 dynamic random 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 510 may allow wireless device 500 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 acommunication system may be tangibly embodied as or in the memory 510, which may be or comprise a device-readable storage medium.

[0108] The processing circuitry 502 may be configured to communicate with an access network or other network via or using the communication interface 512. The communication interface 512 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 522. The communication interface 512 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 518 and / or a receiver 520 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 518 and receiver 520 may be coupled to one or more antennas (e.g., antenna 522) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0109] In the illustrated embodiment, communication functions of the communication interface 512 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 / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0110] In particular embodiments, wireless device 500 may provide an output of data captured via a sensor, through its communication interface 512, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 500 can be communicated through a wireless connection to a network node via another wireless device 500. 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).

[0111] As another example, wireless device 500 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 500 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.

[0112] Wireless device 500, 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 500 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 500 shown in Figure 5.

[0113] As yet another specific example, in an loT scenario, wireless device 500 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 500 may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, wireless device 500 may implement the 3GPP NB-IoT standard. In other scenarios, wireless device 500 may represent a vehicle, such as a car, a bus, 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.

[0114] In practice, any number of wireless devices 500 may be used together with respect to a single use case. For example, a first wireless device 500 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 500 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 500 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 500 can also include more than one of the functionalities described above. For example, wireless device 500 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0115] Figure 6 shows a network node 600 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 600 may be configured to operate in communication system 400 of Figure 4, like network nodes 408 or 410. 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)), O-RAN nodes or components of an O-RAN node (e g., O-RU, O-DU, O-CU).

[0116] Network nodes 600 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 600 may be a relay node or a relay donor node controlling a relay. Network nodes 600 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 O-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).

[0117] Other examples of network nodes 600 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 SupportSystem (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).

[0118] In particular embodiments, network node 600 includes a processing circuitry 602, a memory 604, a communication interface 606, and a power source 608. In general, in a particular embodiment of network node 600, processing circuitry 602, memory 604, communication interface 606, and power source 608 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 600.

[0119] The network node 600 may be composed of multiple distinct network entities (e.g. , a NodeB entity and a 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 600 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 600 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 604 or portions of memory 604 for different RATs) and some components may be reused (e.g., a same antenna 610 may be shared by different RATs). The network node 600 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 600, 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 600.

[0120] The processing circuitry 602 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 604, to provide network node 600 functionality. For example, the processing circuitry 602 may be configured to cause the network node 600 to perform the methods as described with reference to Figure 3.

[0121] In some embodiments, the processing circuitry 602 includes a system on a chip (SOC). In some embodiments, the processing circuitry 602 includes one or more of radiofrequency (RF) transceiver circuitry 612 and baseband processing circuitry 614. In some embodiments, the RF transceiver circuitry 612 and the baseband processing circuitry 614 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 612 and baseband processing circuitry 614 may be on the same chip or set of chips, boards, or units.

[0122] The memory 604 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 computerexecutable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 602. The memory 604 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 602 and utilized by the network node 600. The memory 604 may be used to store any calculations made by the processing circuitry 602 and / or any data received via the communication interface 606. In some embodiments, the processing circuitry 602 and memory 604 is integrated.

[0123] The communication interface 606 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 606 comprises port(s) / terminal(s) 616 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 500 may be capable of wireless communication and communication interface 606 may also include radio front-end circuitry 618 that may be coupled to, or in certain embodiments a part of, an antenna 610. Particular embodiments of radio front-end circuitry 618 include filter(s) 620 and amplifier(s) 622. The radio front-end circuitry 618 may be connected to an antenna 610 and processing circuitry 602. The radio frontend circuitry may be configured to condition signals communicated between antenna 610 and processing circuitry 602. The radio front-end circuitry 618 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 618 may convert the digital data into a radio signal (s) having the appropriate channel and bandwidth parameters using a combination of filters 620 and / or amplifiers 622. The radio signal(s) may then be transmitted via the antenna 610. Similarly, when receiving data, theantenna 610 may collect radio signals which are then converted into digital data by the radio front-end circuitry 618. The digital data may be passed to the processing circuitry 602. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0124] In certain alternative embodiments, network node 600 may be capable of wireless communication but does not include separate radio front-end circuitry 618, instead, the processing circuitry 602 includes radio front-end circuitry and is connected to the antenna 610. Similarly, in some embodiments, all or some of the RF transceiver circuitry 612 is part of the communication interface 606. In still other embodiments, the communication interface 606 includes one or more ports or terminals 616, the radio front-end circuitry 618, and the RF transceiver circuitry 612, as part of a radio unit (not shown), and the communication interface 606 communicates with the baseband processing circuitry 614, which is part of a digital unit (not shown).

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

[0126] The antenna 610, communication interface 606, and / or the processing circuitry 602 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 600. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 610, the communication interface 606, and / or the processing circuitry 602 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 600. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0127] The power source 608 provides power to the various components of network node 600 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 608 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 600 with power for performing the functionality described herein. For example, the network node 600 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 suppliespower to power circuitry of the power source 608. As a further example, the power source 608 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0128] Embodiments of the network node 600 may include additional components beyond those shown in Figure 6 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 600 may include user interface equipment to allow input of information into the network node 600 and to allow output of information from the network node 600. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 600.

[0129] Figure 7 is a block diagram illustrating a virtualization environment 700 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 700 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 700 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.

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

[0131] Hardware 704 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 706(also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 708 A and VM 708B (which may be collectively referred to as VMs 708), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 706 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 708.

[0132] The VMs 708 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 706. Different embodiments of the instance of a virtual appliance 702 may be implemented on one or more of VMs 708, 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.

[0133] In the context of NFV, each of the VMs 708 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 708, and that part of hardware 704 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 708 on top of the hardware 704 and corresponds to an application 702.

[0134] Hardware 704 may be implemented in a standalone network node with generic or specific components. Hardware 704 may implement some functions via virtualization. Alternatively, hardware 704 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 710, which, among others, oversees lifecycle management of applications 702. In some embodiments, hardware 704 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 712 which may alternatively be used for communication between hardware nodes and radio units.

[0135] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments maycomprise 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 needed to 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.

[0136] 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.EMBODIMENTSGroup A Embodiments1. A method performed by a wireless device, the method comprising:obtaining a first timing advance value for communicating with a first LTM candidate cell, wherein the wireless device stores an LTM configuration for the first LTM candidate cell;receiving, from a first network node, an instruction to initiate an LTM mobility procedure to the first LTM candidate cell; andperforming an LTM mobility procedure to the first LTM candidate cell, wherein, responsive to the fulfillment of one or more conditions, the LTM mobility procedure comprises using the first timing advance value to communicate with the first LTM candidate cell without performing a random-access procedure.2. The method of embodiment 1, wherein the one or more conditions comprise a first condition that the instruction contains no timing advance value for communicating with the LTM candidate cell.3. The method of embodiment 2, wherein a field for indicating the timing advance value is absent from the instruction.4. The method of embodiment 2, wherein the instruction comprises a null value for the timing advance value.5. The method of embodiment 4, wherein the null value is FFF.6. The method of any one of the preceding embodiments, wherein the one or more conditions comprise a second condition that the obtained timing advance value is valid when the instruction is received and / or when the LTM mobility procedure is performed.7. The method of embodiment 6, wherein the obtained timing advance value is valid if a timer associated with the timing advance value is running when the instruction is received and / or when the LTM mobility procedure is performed.8. The method of embodiment 7, wherein the timer is initiated upon obtaining the timing advance value.9. The method of any one of the preceding embodiments, wherein obtaining the first timing advance value comprises receiving the first timing advance value from the first network node.10. The method of embodiment 9, wherein the first timing advance value is received in a separate message, prior to the instruction to initiate the LTM mobility procedure.11. The method of embodiment 10, wherein the separate message is a Timing Advance Command message.12. The method of any one of embodiments 1 to 8, wherein obtaining the first timing advance value comprises performing measurements on transmissions by the LTM candidate cell to determine the first timing advance value.13. The method of any one of the preceding embodiments, wherein the first timing advance value is for early synchronization with the LTM candidate cell.14. The method of any one of the preceding embodiments, further comprising:responsive to a determination that the instruction comprises an indication of a second timing advance value for communication with the LTE candidate cell, performing an LTM mobility procedure to the LTM candidate cell, wherein the LTM mobility procedure comprises using the second timing advance value to communicate with the LTM candidate cell without performing a random-access procedure.15. The method of any one of the preceding embodiments, wherein the wireless device obtains a plurality of timing advance values for communication with the LTE candidate cell, including two or more of: the first timing advance value, being received from the first network node prior to the instruction to initiate the LTM mobility procedure; a second timing advance value, being received from the first network node in the instruction; and a third timing advance value, being calculated by the wireless device.16. The method of embodiment 15, wherein the LTM mobility procedure comprises using a selected one of the first, second and third timing advance values to communicate with the LTM candidate cell without performing a random-access procedure.17. The method of embodiment 16, wherein the timing advance value is selected accordingto one or more of the following rules:• The first timing advance value is selected if available;• The second timing advance value is selected if available• The third timing advance value is selected if available;• The timing advance value associated with the greatest remaining timer value is selected;• The timing advance value associated with the greatest timer value (e.g., the greatest initial time value) is selected;• The timing advance value associated with the smallest remaining timer value is selected;• The timing advance value associated with the smallest timer value (e.g., the smallest initial time value) is selected;• The timing advance value is selected based on an indication from the network (e.g., the first network node)18. The method of any one of the preceding embodiments, wherein the first network node is a source node for the LTE mobility procedure.19. The method of any one of the preceding embodiments, wherein the LTM configuration is a conditional LTM configuration for the first LTM candidate cell, and wherein the conditional LTM configuration comprises or is associated with one or more execution conditions for executing an LTM mobility procedure to the first LTM candidate cell.20. The method of any of the previous embodiments, further comprising:providing user data; andforwarding the user data to a host via the transmission to the network node.AL A method at a User Equipment (UE), which is configured with at least a mobility configuration by a first network node, comprising:• Receiving a first message from a first network node which includes a TA value for a second network node• Receiving a second message from a first network node which include a mobility command to initiate a mobility procedure to a second network node and which mobility command does not include a TA value• Determining to perform a mobility procedure without a random access procedure • Performing a mobility procedure towards the second network node without performing a random access procedure.A2. The method in Al, wherein the mobility command received within the second messagedoes not include any TA value e.g., the field for providing the TA value is absent within the mobility command.A3. The method in Al, wherein the mobility command received within the second message includes the TA value with a special value to indicate to the UE that it should not consider the TA value.A4. The method in Al, wherein the UE determines to perform a RACH-less mobility procedure when one or more of the following conditions happen:• The UE has already received a TA value before the reception of a mobility command, and the received mobility command does not comprise a TA value.• The UE has already calculated a TA value before the reception of a mobility command, and the received mobility command does not comprise a TA value.• The UE has a TAT running before the reception of a mobility command, and the received mobility command does not comprise a TA value.• The UE has a valid TA before the reception of a mobility command, and the received mobility command does not comprise a TA value• The UE has more than a TA value available before the reception of a mobility command, and the received mobility command does not comprise a TA value• The UE has already received a TA value before the reception of a mobility command, and the received mobility command comprises a TA value set to a value which indicates that such TA value should be ignored / discarded.• The UE has already calculated a TA value before the reception of a mobility command, and the received mobility command comprises a TA value set to a value which indicates that such TA value should be ignored / discarded.• The UE has a TAT running before the reception of a mobility command, and the received mobility command comprise a TA value set to a value which indicate that such TA value should be ignored / discarded.• The UE has a valid TA before the reception of a mobility command, and the received mobility command comprises a TA value set to a value which indicates that such TA value should be ignored / discarded• The UE has more than a TA value available before the reception of a mobility command, and the received mobility command comprises a TA value set to a value which indicates that such TA value should be ignored / discarded.A5. The method in any one of Al, A3 and A4, wherein the value of the TA to indicate to the UE that such TA value should be ignored / discarded is “FFF”.A6. The method in Al, wherein the UE instead of receiving a TA value in a first message from the first network node, calculates the TA value by itself.A7. The method in Al, wherein if the UE has received a TA value from the first networknode within a first message, has calculated a TA value by itself, and has received a TA value also in the mobility command within a second message from the first network node, the UE applies one or more of the following rules to select a TA value to use for the mobility procedure:• The TA value received within the mobility command is selected to be used when performing a mobility procedure without any random access procedure.• The TA value calculated by itself is selected to be used when performing a mobility procedure without any random access procedure.• The TA value received from the first network node within the first message is selected to be used when performing a mobility procedure without any random access procedure• The TA with the largest TAT value is selected to be used when performing a mobility procedure without any random access procedure• The TA with the largest remaining TAT (if running) is selected to be used when performing a mobility procedure without any random access procedure• The TA with the smaller value is selected to be used when performing a mobility procedure without any random access procedure• The TA is selected according to a network indicationA8. The method in any one of Al to A7, wherein the UE, when performing a mobility procedure, stop the TAT related to the TA value received within the first message from the first network node, and start a new TAT related to the TA value received within the mobility command.A9. The method in any one of Al to A8, wherein the first network node is a source gNB-DU, a source gNB-CU, or a source gNB.A10. The method in any one of Al to A9, wherein the second network node is a target gNB-DU, a target gNB-CU, or a target gNB.All. The method in any one of Al to A10, wherein the first and second message are received according to one or more of the following signaling options:• An existing (e.g., legacy) or new (e.g., newly defined) RRC message• An existing (e.g., legacy) or new (e.g., newly defined) MAC CE• An existing (e.g., legacy) or new (e.g., newly defined) LI signalling (e.g., DCI)Group B Embodiments21. A method performed by a first network node, the method comprising:transmitting, to a wireless device, an instruction to initiate an LTM mobility procedureto a first LTM candidate cell, wherein the wireless device stores a first timing advance value for communicating with the first LTM candidate cell, wherein the wireless device further stores an LTM configuration for the first LTM candidate cell.22. The method of embodiment 21, wherein, responsive to a determination that the wireless device is to perform the LTM mobility procedure using the first timing advance value to communicate with the LTM candidate cell without performing a random-access procedure, the instruction is adapted to contain no timing advance value for communicating with the LTM candidate cell.23. The method of embodiment 22, wherein a field for indicating the timing advance value is absent from the instruction.24. The method of embodiment 22, wherein the instruction comprises a null value for the timing advance value.25. The method of embodiment 24, wherein the null value is FFF.26. The method of any one of embodiments 21 to 25, wherein, responsive to a determination that the wireless device is to perform the LTM mobility procedure using a second timing advance value to communicate with the LTM candidate cell without performing a randomaccess procedure, the instruction is adapted to contain an indication of the second timing advance value.27. The method of any one of embodiments 21 to 26, further comprising:transmitting the first timing advance value to the wireless device.28. The method of embodiment 27, wherein the first timing advance value is transmitted in a separate message, prior to the instruction to initiate the LTM mobility procedure.29. The method of embodiment 28, wherein the separate message is a Timing Advance Command message.30. The method of any one of embodiments 21 to 29, wherein the first network node is asource node for the LTE mobility procedure.31. The method of any one of embodiments 21 to 30, wherein the LTM configuration is a conditional LTM configuration for the first LTM candidate cell, and wherein the conditional LTM configuration comprises or is associated with one or more execution conditions for executing an LTM mobility procedure to the first LTM candidate cell.32. The method of any of the previous embodiments, further comprising:obtaining user data; andforwarding the user data to a host or a user equipment.BL Methods at a first network node e.g., a source gNB-DU, a source gNB-CU, or a source gNB which has configured a UE with at least a mobility configuration, comprising:• Transmitting a first message to the UE which includes a TA value for a second network node• Transmitting a second message to the UE which includes a mobility command to initiate a mobility procedure to a second network node and which mobility command does not include a TA valueB2. The method in Bl, wherein the mobility command transmitted within the second message does not include any TA value e.g., the field for providing the TA value is absent within the mobility command.B3. The method in Bl, wherein the mobility command transmitted within the second message includes the TA value with a special value to indicate to the UE that it should not consider the TA value.B4. The method in B3, wherein the special value is “FFF”.B5. The method in any one of Bl to B4, wherein the first and second message are received according to one or more of the following signaling options:• An existing (e.g., legacy) or new (e.g., newly defined) RRC message• An existing (e.g., legacy) or new (e.g., newly defined) MAC CE• An existing (e.g., legacy) or new (e.g., newly defined) LI signalling (e.g., DCI)C Embodiments33. A wireless device (412, QQ212, 500) comprising:processing circuitry (502) configured to cause the wireless device to perform any of the operations of any of the Group A embodiments; anda power source (508) configured to supply power to the processing circuitry (502).34. A network node (410, QQ210, 600) comprising:processing circuitry (602) configured to cause the network node to perform any of the operations of any of the Group B embodiments;a power source (608) configured to supply power to the processing circuitry (602).35. A wireless device comprising:one or more antennas;communication interface connected to the one or more antennas and to processing circuitry;the processing circuitry being configured to cause the wireless device 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 wireless device to be processed by the processing circuitry;an output interface connected to the processing circuitry and configured to output information from the wireless device that has been processed by the processing circuitry; and a power source connected to the processing circuitry and configured to supply power to the wireless device.36. A computer program product comprising a non-transitory computer-readable medium having computer-readable code embodied therein, the computer-readable code being configured such that, on execution by a suitable computer or processing circuitry, the computer or processing circuitry is caused to perform the method of any of the Group A embodiments and the Group B embodiments.37. A wireless device (412, QQ212, 500) configured to perform the method of any of the Group A embodiments.38. A wireless device (412, QQ212, 500) comprising processing circuitry (502) and a memory (510), said memory containing instructions executable by said processing circuitrywhereby said wireless device is operative to perform the method of any of the Group A embodiments.39. A network node (410, QQ210, 600), configured to perform the method of any of the Group B embodiments.40. A network node (410, QQ210, 600) comprising processing circuitry (602) and a memory (604), said memory containing instructions executable by said processing circuitry whereby said network node is operative to perform the method of any of the Group B embodiments.APPENDIXINTRODUCTION DISCUSSIONConfigured Grant ActivationThe discussion so far in RAN2 has concluded that a configured grant in the target cell enables the UE to make a RACH-less conditional cell switch. Since a configured grant configuration needs to be included within each LTM candidate configuration, this represent a very big burden for the network as a lot of resources needs to be reserved in advance (at the time of the conditional LTM preparation) and the network would not know for how long, since the LTM cell switch procedure in this case is triggered by the UE itself. For this reason, a large number of resources might be occupied just for the case of configuring an LTM candidate, and this is especially true when the decision to execute the cell switch is under UE control as for conditional LTM. The consequence of this is that the network may not be able to configure many LTM candidate configurations, thus not exploiting fully the benefits of LTM.Observation 1 Reserving network resource in advance for a LTM candidate configuration is not efficient from a resource usage and efficiency perspective. Observation 2 Due to the scarcity of available resources, network may be able to configure only few LTM candidate configurations.According to this, it would be beneficial from a resource usage (and efficiency) perspective if a configured grant could be allocated during the LTM configuration procedure but activated just in time for the cell switch execution.This means that the network can indeed configure a CG within an LTM candidate configuration, but this CG will not be used by the UE unless the network explicitly indicates the UE that can use it. If the network does not indicate that the UE can use that CG during an LTM cell switch procedure, this means that the LTM cell switch procedure will be RACH-based, even if a valid TA is available. This may sounds not efficient, but the benefit of this solution is that the same CG may be configured for more than one LTM candidate configuration and the network may decide to “activate” such CG only for the most promising LTM candidate configuration (network can figures out e.g., based on the UE’s measurements). How the activation of this CG is done, it can be further discussed. Thus, we propose:Proposal 1 The network can activate or deactivate a CG which is part of an (conditional) LTM candidate configuration.TA values after CLTM cell switch executionPrevious agreements in RAN2 have concluded what should happen for TA values and associated timers that the UE might have for other candidate cells when a cell switch is executed by the UE to a target cell:RAN2#129bis agreement:Upon C-LTM execution, UE performs the following for received TA values and TA timers for other candidate cells than the target candidate cell: Maintain the TA value and Keep the early TA timer running.This means that the UE will keep the TA values and timers for other candidates than the target cell. However, it is not clear for what purpose these will be kept by the UE. For what is currently agreed the only use case would be if the UE executes another conditional cell switch to one of the cells for which it has a TA value with a timer still running.Observation 3 The use for a TA value to another candidate cell after a cell switch execution is limited since the network does not know of this TA value.From a network perspective, if the new serving cell (i.e. , the target cell to which the UE is switching to) does not know which TA value are kept by the UE and what is the status of their TAT, the agreement taken in RAN2 would not be very useful. In fact, if such information is not known, the new serving cell should assume that no TA values are available at the UE and thus the early UL synchronization procedure should be done from scratch for all the LTM candidate cells.Observation 4 If the new serving cell does now know which TA values are kept at the UE, the new serving cell will assume that no TA are available at the UE and the early UL synchronization procedure needs to be re-triggered (or done from scratch). According to this, it would be good if network can inform the new serving cell about which TA values and TAT for other LTM candidate cells the UE has kept. The benefit would be that the new serving cell would not need to re-triggere the early UL synchronization procedure again, unless if e.g., a TAT is going to expire soon or is expired. This will save resources and signalling.Observation 5 If the new serving cell knows which TA values and TAT for other LTM candidate cells the UE has kept, the early UL synchronization procedure does not need to be re-triggered again, and this saves network resources and signaling. Therefore, we propose:Proposal 2 The UE informs the new serving cell, within the RRCReconfigurationComplete message, which TA values and TAT for other LTM candidate cells the UE has kept.L2 reset coordinationDuring non-conditional LTM cell switch the target DU will be aware of what the source cell is through the Cell Switch Notification message, and therefore the target DU can understand if the Itm-noResetID differs and thus if a L2 reset has been performed at the UE side.For the conditional case however, there are no message to the DU serving the target cell since the execution is initiated by the UE. Since the source cell can be not only a certain cell, but one out of a number of candidates (and the candidate configuration does not depend on which the source cell is), the target DU needs to know if a L2 reset has been performed at the UE side to act accordingly.Observation 6 When the UE has executed CLTM, the target DU needs to be aware if the UE has performed L2 reset or not.To handle this issue, we see three possible options:1) Good Bye message; The UE tells the source DU which candidate cell it intends to switch to, before it executes the cell switch so the source DU can inform the target with the relevant information.2) Hello message; The UE tells the target in the first available grant what the reset ID is, or potentially if it has reset its MAC buffer or not, to let the target DU know the appropriate action.3) CU synchronization; The CU will know the configuration of all UEs and which have conditional configuration. It can continuously send this information to the DUs to let them know which is the current source cell for each UE. When a DU receives an incoming cell switch it will inform the CU so the CU can send an updated list to all DUs.Option 1) above has already been discussed in RAN2 and there is no support to introduce it, mainly because the robustness aspects will be affected if the message doesn’t get through to the source. For this reason we don’t think it is a good option.Option 2) would rely on either a new MAC CE with highest priority in the LCP procedure alternatively an indication in the UCI to let the target DU know if the buffer has been reset or not. It seems feasible but comes with some specification impact.Option 3) sounds like a stable option since the CU will have information about current state of all candidate configurations. This falls within the RAN3 domain so we think it would be best to consult them with evaluating the feasibility for these options as RAN2s preferred choice.Observation 7 Letting the CU informing the DUs pro-actively would mean the target DU has information about if a L2 reset has been performed or not.Proposal 3 For CLTM, the CU shall update the DU(s) of other LTM candidates about the current serving cell for a UE at every LTM cell switch to allow the DU for the LTM candidate to understand whether an L2 reset needs to be done or not. Send an LS to RAN3 to inform them.LTM cell switch MAC CE for a CLTM candidateIn the previous RAN2 meeting we made the following agreement:RAN2#129bis agreement:Network can send an LTM Cell Switch Command MAC CE indicating a CLTM candidate configuration (no specification change).However, a case not discussed yet is what should happen if the UE receives the cell switch command and already has a valid TA (i.e., because was delivered previously). In Rel-18 LTM, the network can signal the value ‘FFF’ as the Timing Advance Command which indicates that no TA value is available from the network. However, if value “FFF” is included in the LTM cell switch MAC CE and the UE has a valid TA, it would be reasonable to allow the UE to still perform a RACH-less LTM cell switch procedure. This is also in line with the behavior we have in Rel-18 for the case on when the UE is configured with UE-based TA measurements.Observation 8 If value “FFF” is included in the LTM cell switch MAC CE and the UE has a valid TA, it would be reasonable to allow the UE to still perform a RACH-less LTM cell switch procedure. This is also in line with the behavior we have in Rel-18 for the case on when the UE is configured with UE-based TA measurements. Therefore, we propose:Proposal 4 If the network sends a LTM cell switch MAC CE with value “FFF” for the TA value, and the UE has a valid TA (either because previously send by the network or because or UE-based TA), the UE performs a RACH-less LTM cell switch procedure.Open issues in MAC running CRSelection of valid CG-resources MAC-9Editor ’s NOTE: FES in case UE considers RACH-less CLTM is ongoing, i.e., UE has valid TA for CLTM target cell, how UE selects the valid CG resource for L3 based CLTM.This issue could be easily solved if the UE just uses the CG resource that it has for the specific candidate configuration for which the L3 execution conditions is configured.Proposal 5 The UE selects the CG resources that are configured in the LTM candidate for which the particular execution conditions was fulfilled.Beam selection for L3 execution conditions MAC-10Editor ’s NOTE: FES how to determine the selected beam in case the CLTM is triggered by L3 event.Since we have already agreed to leave up to UE implementation for LI, (if more than one beam fulfills the execution condition) then for L3 which would for many cases reflect asimilar selection procedure, the UE should follow the same principle.Proposal 6 Which beam to select in case CLTM is triggered by L3 events is up to UE implementation.RACH-less when no CG resources available MAC-11In case UE considers RACH-less CLTM is ongoing, i.e., UE has valid TA for LTM target cell, while UE couldn ’t obtain valid CG resource, whether UE will fall back to RACH-based LTM?What should be considered as a valid CG resource or not should perhaps be considered as if the periodicity indicates that the next CG occasion is far away in time. In other similar use of configured grants (e.g. SDT) there is a possibility for the network to configure an “acceptable” waiting time that denotes how far away in time the CG occasion can be, otherwise the UE will revert to a random access based procedure.However, for the SDT case, this behavior was introduced when the periodicities were of an extended format, far exceeding normal configured grants periodicities. For this reason it doesn’t seem necessary to introduce similar behavior for the CG in mobility. Instead, together with Error! Reference source not found, it could be assumed that the configured periodicity is kept short enough to always be used. An alternative would be to allow the use of RACH-based, but this would be followed by discussions on how long time in the future it would be acceptable to wait, so it is considered as not necessary.In the case that there are no valid CG occasion (not including that it falls to far in the future due to the periodicity of the CG), then the UE should make a RACH-based cell switch.Proposal 7 It is up to network to configure CG resources so that they are available and valid for the UE. If there is no valid CG occasion then the UE shall fall back to RACH-based LTM.Network based cell switch during CLTM TA timer runningEditor ’s NOTE: FES for the case when CLTM candidate TAT timer is running, an (Enhanced) LTM Cell switch Command MAC CE is received.Since it has been agreed that the network can initiate a network triggered cell switch even for LTM configurations which includes execution conditions, it does not seem to be any certain differences for if the candidate TAT is running for that cell fir which the UE is receiving a cell switch command for. The only issue could be if the network has filled in a TA value (other than ‘FFF’) in the TA command field of the MAC CE.It would be a simple solution to update the specifications so that a TA value from the network always takes precedence over any TA value the UE might already have.Proposal 8 If the UE receives a cell switch command for a candidate configuration where it has a TAT running to the candidate cell, then any TA command in the MAC CE takes precedence over any TA value the UE might have stored already.CONCLUSIONIn the previous sections we made the following observations:Observation 1 ... Reserving network resource in advance for a LTM candidate configuration is not efficient from a resource usage and efficiency perspective.Observation 2 Due to the scarcity of available resources, network may be able to configure only few LTM candidate configurations.Observation 3 The use for a TA value to another candidate cell after a cell switch execution is limited since the network does not know of this TA value.Observation 4 If the new serving cell does now know which TA values are kept at the UE, the new serving cell will assume that no TA are available at the UE and the early UL synchronization procedure needs to be re-triggered (or done from scratch).Observation 5 If the new serving cell knows which TA values and TAT for other LTM candidate cells the UE has kept, the early UL synchronization procedure does not need to be re-triggered again, and this saves network resources and signaling.Observation 6...When the UE has executed CLTM, the target DU needs to be aware if the UE has performed L2 reset or not.Observation 7..Letting the CU informing the DUs pro-actively would mean the target DU has information about if a L2 reset has been performed or not.Observation 8... If value “FFF” is included in the LTM cell switch MAC CE and the UE has a valid TA, it would be reasonable to allow the UE to still perform a RACH-less LTM cell switch procedure. This is also in line with the behavior we have in Rel-18 for the case on when the UE is configured with UE-based TA measurements.Based on the discussion in the previous sections we propose the following:Proposal 1 The network can activate or deactivate a CG which is part of an (conditional) LTM candidate configuration.Proposal 2 The UE informs the new serving cell, within the RRCReconfigurationComplete message, which TA values and TAT for other LTM candidate cells the UE has kept.Proposal 3 For CLTM, the CU shall update the DU(s) of other LTM candidates about the current serving cell for a UE at every LTM cell switch to allow the DU for the LTM candidate to understand whether an L2 reset needs to be done or not. Send an LS to RAN3 toinform them.Proposal 4 If the network sends a LTM cell switch MAC CE with value “FFF” for the TA value, and the UE has a valid TA (either because previously send by the network or because or UE-based TA), the UE performs a RACH-less LTM cell switch procedure.Proposal 5 The UE selects the CG resources that are configured in the LTM candidate for which the particular execution conditions was fulfilled.Proposal 6 Which beam to select in case CLTM is triggered by L3 events is up to UE implementation.Proposal 7 It is up to network to configure CG resources so that they are available and valid for the UE. If there is no valid CG occasion then the UE shall fall back to RACH-based LTM. Proposal 8 If the UE receives a cell switch command for a candidate configuration where it has a TAT running to the candidate cell, then any TA command in the MAC CE takes precedence over any TA value the UE might have stored already.ABBREVIATIONSAt least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).3GPP 3rd Generation Partnership Project5G 5th Generation6G 6th GenerationABS Almost Blank SubframeARQ Automatic Repeat RequestAWGN Additive White Gaussian NoiseBCCH Broadcast Control ChannelBCH Broadcast ChannelCA Carrier AggregationCC Carrier ComponentCCCH SDU Common Control Channel SDUCDMA Code Division Multiplex AccessCGI Cell Global IdentityCIR Channel Impulse ResponseCP Cyclic PrefixCPICH Common Pilot ChannelCQI Channel Quality InformationC-RNTI Cell RNTICSI Channel State InformationDCCH Dedicated Control ChannelDL DownlinkDM DemodulationDMRS Demodulation Reference SignalDRX Discontinuous ReceptionDTX Discontinuous TransmissionDTCH Dedicated Traffic ChannelDUT Device Under TestE-CID Enhanced Cell-ID (positioning method)Ec / No Received energy per chip divided by the power density in the band eMBMS Evolved Multimedia Broadcast Multicast ServicesECGI Evolved CGIeNB E-UTRAN NodeBePDCCH Enhanced Physical Downlink Control ChannelE-SMLC Evolved Serving Mobile Location CenterE-UTRAN Evolved Universal Terrestrial Radio Access NetworkFDD Frequency Division DuplexFFS For Further StudygNB Base station in NRGNSS Global Navigation Satellite SystemHARQ Hybrid Automatic Repeat RequestHO HandoverHSPA High Speed Packet AccessHRPD High Rate Packet DataLOS Line of SightLPP LTE Positioning ProtocolLTE Long-Term EvolutionLTM Layer 1 (LI) / Layer 2 (L2) Triggered MobilityMAC Medium Access ControlMAC Message Authentication CodeMBSFN Multimedia Broadcast Multicast Service Single Frequency Network MBSFN ABS MBSFN Almost Blank SubframeMDT Minimization of Drive TestsMIB Master Information BlockMME Mobility Management EntityMSC Mobile Switching CenterNPDCCH Narrowband Physical Downlink Control ChannelNR New RadioOCNG OFDMA Channel Noise GeneratorOFDM Orthogonal Frequency Division MultiplexingOFDMA Orthogonal Frequency Division Multiple AccessOSS Operations Support SystemOTDOA Observed Time Difference of ArrivalO&M Operation and MaintenancePBCH Physical Broadcast ChannelP-CCPCH Primary Common Control Physical ChannelPCell Primary CellPCFICH Physical Control Format Indicator ChannelPDCCH Physical Downlink Control ChannelPDCP Packet Data Convergence ProtocolPDP Power Delay ProfilePDSCH Physical Downlink Shared ChannelPGW Packet GatewayPHICH Physical Hybrid-ARQ Indicator ChannelPLMN Public Land Mobile NetworkPMI Precoding Matrix IndicatorPRACH Physical Random Access ChannelPRS Positioning Reference SignalPSS Primary Synchronization SignalPUCCH Physical Uplink Control ChannelPUSCH Physical Uplink Shared ChannelRACH Random Access ChannelRAR Random Access ResponseQAM Quadrature Amplitude ModulationRAN Radio Access NetworkRAT Radio Access TechnologyRFC Radio Link ControlRLM Radio Link MonitoringRNC Radio Network ControllerRNTI Radio Network Temporary IdentifierRRC Radio Resource ControlRRM Radio Resource ManagementRS Reference SignalRSCP Received Signal Code PowerRSRP Reference Symbol Received Power ORReference Signal Received PowerRSRQ Reference Signal Received Quality OR Reference Symbol Received QualityRS SI Received Signal Strength IndicatorRSTD Reference Signal Time DifferenceSCH Synchronization ChannelSCell Secondary CellSDAP Service Data Adaptation ProtocolSDU Service Data UnitSFN System Frame NumberSGW Serving GatewaySI System InformationSIB System Information BlockSNR Signal to Noise RatioSON Self-Organizing Networkss Synchronization Signalsss Secondary Synchronization SignalTDD Time Division DuplexTDOA Time Difference of ArrivalTOA Time of ArrivalTSS Tertiary Synchronization SignalTTI Transmission Time IntervalUE User EquipmentUL UplinkUMTS Universal Mobile Telecommunications System USIM Universal Subscriber Identity Module UTDOA Uplink Time Difference of Arrival WCDMA Wideband CDMAWLAN Wireless Local Area Network

Claims

CLAIMSGroup A Embodiments1. A method performed by a wireless device, the method comprising:obtaining a first timing advance value for communicating with a first Layer 1 / Layer 2 Triggered Mobility candidate cell, wherein the wireless device stores an LTM configuration for the first LTM candidate cell;receiving, from a first network node, an instruction to initiate an LTM mobility procedure to the first LTM candidate cell, wherein the instruction comprises a timing advance value field set to a null value FFF; andperforming an LTM mobility procedure to the first LTM candidate cell, wherein, responsive to the instruction comprises the timing advance value field set to the null value FFF, the LTM mobility procedure comprises using the first timing advance value to communicate with the first LTM candidate cell without performing a random-access procedure.

2. The method of claim 1, wherein the performing of the LTM procedure is responsive to a second condition that the first obtained timing advance value is valid when the instruction is received and / or when the LTM mobility procedure is performed.

3. The method of claim 2, wherein the obtained first timing advance value is valid if a timer associated with the timing advance value is running when the instruction is received and / or when the LTM mobility procedure is performed.

4. The method of claim 3, wherein the timer is initiated upon obtaining the timing advance value.

5. The method of any one of the preceding claims, wherein obtaining the first timing advance value comprises receiving the first timing advance value from the first network node.

6. The method of claim 9, wherein the first timing advance value is received in a separate message, prior to the instruction to initiate the LTM mobility procedure.

7. The method of claim 10, wherein the separate message is a Timing Advance Command message.

8. The method of any one of claims 1 to 4, wherein obtaining the first timing advance value comprises performing measurements on transmissions by the LTM candidate cell to determine the first timing advance value.

9. The method of any one of the preceding claims, wherein the first timing advance value is for early synchronization with the LTM candidate cell.

10. The method of any one of the preceding claims, further comprising:responsive to a determination that the instruction comprises an indication of a second timing advance value for communication with the LTE candidate cell, performing an LTM mobility procedure to the LTM candidate cell, wherein the LTM mobility procedure comprises using the second timing advance value to communicate with the LTM candidate cell without performing a random-access procedure.

11. The method of any one of the preceding claims, wherein the wireless device obtains a plurality of timing advance values for communication with the LTE candidate cell, including two or more of: the first timing advance value, being received from the first network node prior to the instruction to initiate the LTM mobility procedure; a second timing advance value, being received from the first network node in the instruction; and a third timing advance value, being calculated by the wireless device.

12. The method of claim 11 , wherein the LTM mobility procedure comprises using a selected one of the first, second and third timing advance values to communicate with the LTM candidate cell without performing a random-access procedure.

13. The method of claim 12, wherein the timing advance value is selected according to one or more of the following rules:• The first timing advance value is selected if available;• The second timing advance value is selected if available• The third timing advance value is selected if available;• The timing advance value associated with the greatest remaining timer value is selected;• The timing advance value associated with the greatest timer value (e.g., the greatest initial time value) is selected;• The timing advance value associated with the smallest remaining timer value is selected;• The timing advance value associated with the smallest timer value (e.g., the smallest initial time value) is selected;• The timing advance value is selected based on an indication from the network (e.g., the first network node)14. The method of any one of the preceding claims, wherein the first network node is a source node for the LTE mobility procedure.

15. The method of any one of the preceding claims, wherein the LTM configuration is a conditional LTM configuration for the first LTM candidate cell, and wherein the conditional LTM configuration comprises or is associated with one or more execution conditions for executing an LTM mobility procedure to the first LTM candidate cell.

16. A method performed by a first network node, the method comprising:transmitting, to a wireless device, an instruction to initiate an Layerl / Layer2 Triggered Mobility procedure to a first LTM candidate cell,wherein the instruction comprises a timing advance value field set to a null value FFF, wherein the wireless device stores a first timing advance value for communicating with the first LTM candidate cell,wherein the wireless device further stores an LTM configuration for the first LTM candidate cell.

17. The method of claim 16, wherein, responsive to a determination that the wireless device is to perform the LTM mobility procedure using the first timing advance value to communicate with the LTM candidate cell without performing a random-access procedure, the instruction is adapted to contain no timing advance value for communicating with the LTM candidate cell.

18. The method of any one of claims 16 to 17, wherein, responsive to a determination that the wireless device is to perform the LTM mobility procedure using a second timing advance value to communicate with the LTM candidate cell without performing a random-access procedure, the instruction is adapted to contain an indication of the second timing advance value.

19. The method of any one of claims 16 to 18, further comprising:transmitting the first timing advance value to the wireless device.

20. The method of claim 19, wherein the first timing advance value is transmitted in a separate message, prior to the instruction to initiate the LTM mobility procedure.

21. The method of claim 20, wherein the separate message is a Timing Advance Command message.

22. The method of any one of claims 16 to 21, wherein the first network node is a source node for the LTE mobility procedure.

23. The method of any one of claims 16 to 23, wherein the LTM configuration is a conditional LTM configuration for the first LTM candidate cell, and wherein the conditional LTM configuration comprises or is associated with one or more execution conditions for executing an LTM mobility procedure to the first LTM candidate cell.

24. A wireless device (412, QQ212, 500) comprising:processing circuitry (502) configured to cause the wireless device to perform any of claims 1 to 15; anda power source (508) configured to supply power to the processing circuitry (502).

25. A network node (410, QQ210, 600) comprising:processing circuitry (602) configured to cause the network node to perform any of the operations of any of claims 16 to 23;a power source (608) configured to supply power to the processing circuitry (602).

26. A wireless device comprising:one or more antennas;communication interface connected to the one or more antennas and to processing circuitry;the processing circuitry being configured to cause the wireless device to perform any of the operations of any of claims 1 to 15;an input interface connected to the processing circuitry and configured to allow inputof information into the wireless device to be processed by the processing circuitry;an output interface connected to the processing circuitry and configured to output information from the wireless device that has been processed by the processing circuitry; and a power source connected to the processing circuitry and configured to supply power to the wireless device.

27. A computer program product comprising a non-transitory computer-readable medium having computer-readable code embodied therein, the computer-readable code being configured such that, on execution by a suitable computer or processing circuitry, the computer or processing circuitry is caused to perform the method of any of claims 1 to 15 and / or any of claims 16 to 23.

28. A wireless device (412, QQ212, 500) configured to perform the method of any of claims 1 to 15.

29. A wireless device (412, QQ212, 500) comprising processing circuitry (502) and a memory (510), said memory containing instructions executable by said processing circuitry whereby said wireless device is operative to perform the method of any of claims 1 to 15.

30. A network node (410, QQ210, 600), configured to perform the method of any of claims 16 to 23.

31. A network node (410, QQ210, 600) comprising processing circuitry (602) and a memory (604), said memory containing instructions executable by said processing circuitry whereby said network node is operative to perform the method of any of claims 16 to 23.