Enhancements of reporting for conditional layer 1 / layer 2 triggered mobility
By logging and reporting CLTM-related information, UEs assist networks in optimizing CLTM procedures, addressing suboptimal mobility issues and improving execution reliability.
Patent Information
- Application Number
- PCT/SE2026/050297
- 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
AI Technical Summary
The network lacks information from UEs to optimize Conditional Layer 1/Layer 2 Triggered Mobility (CLTM), particularly in scenarios involving intra-CU CLTM, inter-CU CLTM, or Dual Connectivity (DC), leading to suboptimal mobility decisions.
UEs are instructed to log and report information related to CLTM procedures, which can be included in existing UE reports like RA, RLF, or SHR, enabling the network to adjust execution conditions, modify measurement-based triggers, and optimize CLTM configurations.
Enables the network to anticipate and improve CLTM execution by adjusting conditions, reducing the likelihood of failures and enhancing mobility performance.
Smart Images

Figure SE2026050297_12112026_PF_FP_ABST
Abstract
Description
[0001] Enhancements of reporting for Conditional Layer 1 / Layer 2 Triggered Mobility
[0002] TECHNICAL FIELD
[0003] This disclosure relates to Conditional Layer 1 / Layer 2 Triggered Mobility (CLTM), and in particular to reporting for CLTM.
[0004] BACKGROUND
[0005] Layer 1 (L1) / Layer2 (L2) Triggered Mobility (LTM) in 3GPP Release 18
[0006] LTM is introduced as a lower-layer mobility procedure in Release 18 (Rel-18), enabling a network node to receive measurement reports from a User Eguipment (UE) via L1 signalling. These L1 -measurement reports are used by the network for mobility-related decisions, such as executing an LTM cell switch to a target cell by sending an LTM Cell Switch Command Medium Access Control (MAC) Control Element (MAC CE) command. Fig. 1 is a signalling diagram illustrating an exemplary LTM process between a UE and a Radio Access Network (RAN) node in the form of a gNB. The LTM process of Fig. 1 is as follows:
[0007] • The UE (that is in RRC_CONNECTED) sends L3-measurement report(s) to the gNB for one or more cells (as shown by signal 1 in Fig.1). Based on these reports, the gNB identifies and configures one or more cells as LTM candidate cells, initiating the LTM preparation phase (step 1a in Fig. 1).
[0008] • The gNB sends a Radio Resource Control (RRC) Reconfiguration message to the UE with the configuration details for the LTM candidate cells (the RRC Reconfiguration message is signal 2 in Fig.1 ).
[0009] • The UE stores the received LTM candidate configurations and acknowledges with an RRC Reconfiguration Complete message (signal 3 in Fig.1 ).
[0010] • DL Pre-Synchronization (also known as “early DL synchronization”): As shown in step 4a of Fig. 1, the UE may perform early downlink (DL) synchronization with LTM candidate cells upon receiving a “Candidate Cell transmission configuration indicator (TCI) States Activation / Deactivation MAC CE”, reducing the mobility interruption by avoiding Synchronisation Signal Block (SSB)-based synchronization after the cell switch.
[0011] • UL Pre-Synchronization (also known as “early UL synchronization”): As shown in step 4b of Fig. 1, if the UE receives a physical downlink control channel (PDCCH) order for early timing advance (TA) acquisition, it may also perform Uplink (UL) pre-synchronization with the candidate cells, further reducing the mobility delay. If configured by the network to do so, the UE may also, or instead, perform the UL pre-synchronization by autonomouslydetermining a timing advance for a candidate cell by comparing the time of reception of reference signals in the candidate cell with the time of reception signals in the serving cell. The UE autonomous UL pre-synchronization mechanism requires that the candidate cell and the serving cell are synchronized.
[0012] • The UE performs L1 measurements on the configured LTM candidate cells and reports them to the source node (the L1 measurement report is signal 5 in Fig.1 ).
[0013] • In step 5a of Fig. 1, the source node decides the target cell (out of the configured and prepared LTM candidate cells) for the switch and sends an LTM Cell Switch Command MAC CE (signal 6 in Fig. 1) containing the configuration index of the selected LTM cell. The UE switches to the target cell and applies the indicated configuration of the LTM candidate cell, as shown by step 6a of Fig. 1.
[0014] • If the UE lacks a valid TA value for the target cell, it performs a random-access procedure (as shown by step 7 in Fig. 1). If a valid TA was acquired earlier during early UL synchronization, this procedure is skipped and the UE performs a so-called Random Access Channel (RACH)-less LTM cell switch. Moreover, if the target cell Transmission Configuration Indication (TCI) state indicated in the LTM cell switch MAC CE differs from the pre-synchronized TCI state, additional synchronization may be required.
[0015] • The UE completes the LTM cell switch by sending an RRC Reconfiguration Complete message to the target cell. The completion of the LTM cell switch is shown by step 8 in Fig. 1. For cases involving random access, successful completion of the random access procedure confirms the switch. For RACH-less LTM, the switch is deemed successful once the network acknowledges the UE’s first UL data transmission.
[0016] Conditional L1 / L2 Triggered Mobility (CLTM) in 3GPP Release 19
[0017] As of Release 19 (Rel-19), support for Conditional LTM (CLTM) is introduced for intraCentral Unit (CU) mobility, and a UE can be configured with one or more CLTM candidate cells controlled by one or more gNB-Distributed Units (DUs). This is also referred to as intra-CU CLTM. The triggering of intra-CU CLTM can be based on Layer 1 (L1) or Layer 3 (L3) measurements and the CondEventA3 and CondEventA5 conditions specified in Third Generation Partnership Project (3GPP) TS 38.331 v18.5.1 are baseline for the conditional LTM execution.
[0018] If L1 measurements are used to trigger CLTM, the L1 execution condition of a candidate cell is associated to only one triggering event. If L3 measurements are used to trigger CLTM, a L3 execution condition may consist of one or two triggering condition(s). If there are two triggering conditions associated with the same candidate cell, the UE shall consider the execution condition is fulfilled only when both triggering conditions are met. Only a single Reference Signal (RS) typeis supported and at most two different trigger quantities can be configured simultaneously for the evaluation of execution condition of a single candidate cell.
[0019] If a UE is configured with multiple CLTM candidate cells, the UE may receive from the network an CLTM configuration according to which, the CLTM execution to some candidate cells is based on fulfilment of L1 based execution conditions and the CLTM execution towards other candidate cells is based on fulfilment of L3 based execution conditions.
[0020] In case of intra-CU Conditional LTM, within a gNB it is the gNB-CU that decides to configure CLTM, and it also determines which type of CLTM to initiate, i.e. whether Layer 1 (L1) event-triggered CLTM, or Layer 3 (L3) event-triggered CLTM. In case of L1 measurements-based CLTM, it is the gNB-DU that generates the L1 execution condition, while in the case of L3 measurements-based CLTM, it is the gNB-CU that generates the L3 execution conditions.
[0021] Self Organising Networks (SON) reports for (Rel-18) L1 / L2 Triggered Mobility (CLTM)
[0022] In 3GPP Rel-19 there is also normative work to introduce support for UE logging and reporting information for the (Rel-18) intra-CU LTM in Self Organising Networks (SON) reports (e.g. in Radio Link Failure (RLF) reports).
[0023] As part of that work, the 3GPP RAN2 Working Group has reached the following agreements in relation to the logging of information related to non-conditional intra-CU LTM in SON reports (e.g. in RLF reports):
[0024] > If available, log the L1 measurements for serving cell, target cell and other LTM candidate cells in RLF report, upon RLF or mobility failure.
[0025] > Log the LTM cell ID upon performing recovery an LTM candidate cell, details TBD e.g. which field.
[0026] > Extend lastHO-Type in RLF-Report to indicate the LTM cell switch as last executed mobility procedure.
[0027] > RAN2 include the specific access type in the RLF report, i.e. whether it is RA-based or RA-less cell switch. FFS details, e.g. if explicit or implicitly signalled.
[0028] > Log L3 measurements for serving cell, target cell and other LTM candidate cells in RLF report, upon RLF or mobility failure. RAN2 assumes this is already possible with existing spec.
[0029] > We will not define and log timeSinceLTM-Reconfig (like timeSinceCHO-Reconfig) within RLF-report and SHR in LTM failure and near failure cases.
[0030] > We will not log interruption time in SON reports (e.g. SHR) for LTM.
[0031] > We aim to log some info to deduce the ItmCandidate (similar like choCandidate) in SHR to indicate whether a neighbour cell is an LTM candidate cell or not, TBDif explicit / implicit.
[0032] Additional agreements reached in RAN2#129-bis and related to potential content reported (or not reported) by a UE in SON reports for LTM are listed below:
[0033] > We will not add support for including the unnecessary LTM configuration, e.g. LTM candidate cell(s) unused, in SON reports, for both failure and near failure cases. > Do not specify support for reporting difference between the TA value received from the LTM cell switch command and TA value measured by the UE.
[0034] > Do not specify support for reporting of elapsed time between UE obtains the target cell TA and UE receives the cell switch command, or an indication to indicate whether the UE obtains TA before UE receives LTM cell switch command.
[0035] > For LTM-related RA reports, the UE sets the cellld to the CGI if available, otherwise sets it based on Itm-CandidatePCI and ssb-Frequency in corresponding LTM- Candidate.
[0036] > At RLF and reconfiguration with sync failure:
[0037] o If RLF: If the selected candidate cell has the same Rel-19 ID as source (no security key change), the UE performs fast RLF recovery (same as in Rel-18).
[0038] o if reconfiguration failure (inter-CU LTM): If the selected candidate cell has the same Rel-19 ID as target, the UE performs fast failure recovery. FFS if fast failure recovery with different Rel-19 IDs is allowed.
[0039] > Same as Rel-18: When the C-LTM execution is triggered, if the TA of the target cell acquired by early RACH is valid, UE applies the TA acquired by early RACH, otherwise if UE has successfully measured the TA of the target cell, UE applies the measured TA.
[0040] SUMMARY
[0041] There currently exist certain challenge(s). One limitation with the existing or published technology is that the network does not receive from the UE, information that can be used to perform specific optimisation for Conditional LTM (CLTM), whether the CLTM relates to intra-CU CLTM, or inter-CU CLTM, or if it relates to CLTM in the case of Dual Connectivity (DC).
[0042] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. In particular, this disclosure provides that a UE (or more generally a wireless device) can be instructed (by the network or by specification) to log and / or report to the network information related to Conditional Layer1 / Layer2 Triggered Mobility (CLTM). The information canbe included in a new type of UE report, or be included in an existing UE report, for example a Random Access (RA) report, a Radio Link Failure (RLF) report, a Successful Handover Report (SHR), etc. The logging and / or reporting can apply to various scenarios, such as: intra-CU LTM, inter-CU LTM, intra-CU CLTM for Master Cell Group (MCG), intra-CU CLTM for Secondary Cell Group (SCG).
[0043] The disclosure also provides that the network (e.g. a Radio Access Network (RAN) node) can use the received information to optimise CLTM, for example any one or more of: modifying L1 or L3 measurement-based execution conditions, avoiding the use of some cells as candidate cells for CLTM, using some cells as CLTM candidate cells, and / or using some cells as LTM candidate cells and not as CLTM candidate cells.
[0044] Certain embodiments may provide one or more of the following technical advantage(s). With the proposed solution(s), the network can perform a number of optimisations due to information received from UEs in relation to Conditional LTM (CLTM). An example can be the network node (e.g. the source DU, the target DU, or the source CU) that generates the execution conditions adjusting the execution conditions, e.g., anticipating the CLTM cell switch execution (the network may anticipate the fulfilment of the execution conditions and modify the execution conditions so that the UE may initiate CLTM a bit earlier). Another example is the network node (e.g. the source CU) that determines whether to use execution conditions based on L1 measurements or L3 measurements deciding to change from using execution conditions based on L1 measurements to execution conditions based on L3 measurements. Another example is the network deciding to use non-conditional LTM instead of CLTM, or vice versa.
[0045] According to a first aspect, there is provided a method performed by a wireless device. The method comprises sending, to a RAN node in a communication network, information relating to a CLTM procedure towards a first CLTM candidate cell (i.e., the CLTM procedure is towards the first CLTM candidate cell). The CLTM procedure may be: a CLTM procedure that was attempted or performed by the wireless device towards the first CLTM candidate cell; and / or a CLTM procedure that the wireless device is configured to attempt or perform towards the first CLTM candidate cell (e.g., in accordance with a CLTM candidate cell configuration).
[0046] According to a second aspect, there is provided a method performed by a RAN node in a communication network. The method comprises one or more of: sending, to a wireless device, a configuration for information to be logged and / or reported relating to a CLTM procedure towards a first CLTM candidate cell; sending, to the wireless device, a request for information relating to the CLTM procedure towards the first CLTM candidate cell; and receiving, from a wireless device, information relating to the CLTM procedure towards the first CLTM candidate cell.According to a third aspect, there is provided a computer program product comprising a computer readable medium having computer readable code embodied therein, the computer readable code being configured such that, on execution by a suitable computer or processor, the computer or processor is caused to perform the method according to the first aspect, the second aspect, or any embodiments thereof.
[0047] According to a fourth aspect, there is provided a wireless device configured to perform the method according to the first aspect, or any embodiments thereof.
[0048] According to a fifth aspect, there is provided a wireless device comprising a processor and a memory, said memory containing instructions executable by said processor whereby said wireless device is operative to perform the method according to the first aspect, or any embodiments thereof.
[0049] According to a sixth aspect, there is provided a radio access network (RAN) node, configured to perform the method according to the second aspect, or any embodiments thereof.
[0050] According to a seventh aspect, there is provided a radio access network (RAN) node comprising a processor and a memory, said memory containing instructions executable by said processor whereby said RAN node is operative to perform the method according to the second aspect, or any embodiments thereof.
[0051] Brief Description of the Drawings
[0052] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings, in which:
[0053] Fig. 1 is a signalling diagram illustrating the LTM signalling procedure;
[0054] Fig. 2 is a signalling diagram illustrating signalling according to embodiments of the disclosure;
[0055] Fig. 3 is a flow chart illustrating a method performed by a wireless device in accordance with some embodiments;
[0056] Fig. 4 is a flow chart illustrating a method performed by a RAN node in accordance with some embodiments;
[0057] Fig. 5 shows an example of a communication system in accordance with some embodiments;
[0058] Fig. 6 shows a wireless device in accordance with some embodiments;
[0059] Fig. 7 shows a radio access network (RAN) node in accordance with some embodiments; and
[0060] Fig. 8 is a block diagram illustrating a virtualization environment in which functionsimplemented by some embodiments may be virtualized.
[0061] DETAILED DESCRIPTION
[0062] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.
[0063] The terms “network node” and “RAN node” are used interchangeably herein, and can refer to any of, for example, a gNB, a gNB-DU, a gNB-CU, a gNB-CU-Control Plane (gNB-CU-CP), a gNB-CU-User Plane (gNB-CU-UP), a 6thGeneration (6G) radio access network node, a node in an Open-RAN (O-RAN)-based RAN node, an O-gNB, an O-DU, an O-CU, an O-CU-CP.
[0064] Non limiting examples of a “network node ID” or “RAN node ID” can be: a Global gNB ID, a gNB ID, a gNB-DU ID, a gNB-CU ID, O-gNB ID, an O-DU ID, an O-CU ID, an O-CU-CP ID, an O-CU-UP-ID, a Radio Network Area Function (RANAF) ID, a 6G node ID or similar.
[0065] The terms “UE report” and “wireless device report” are used interchangeably herein, and non-limiting examples of “UE report” or “wireless device report” can be an existing SON report, such as a Radio Link Failure (RLF) report, a Successful Handover Report (SHR), a Random Access (RA) report, a Successful PSCell (Primary Secondary Cell) Change Report (SPR), or a new UE report.
[0066] This disclosure relates to “CLTM cell switch procedures”, which are also interchangeably referred to herein as “CLTM procedures” and “CLTM cell switch execution”. A “RACH-less CLTM cell switch procedure” is a CLTM cell switch procedure in which the UE does not need to perform random access (RA) in order to start using the new cell. A “RACH-less CLTM cell switch procedure” is also referred to interchangeably herein as a “RA-less CLTM cell switch procedure”, a “RACH-less CLTM procedure”, a “RA-less CLTM procedure”, “RACH-less CLTM”, “RACH-less Conditional LTM”, or “RACH-less Conditional Cell Switch”. A “RACH-based CLTM cell switch procedure” is a CLTM cell switch procedure in which the UE does need to perform random access (RA) in order to start using the new cell. A “RACH-based CLTM cell switch procedure” is also referred to interchangeably herein as a “RA-based CLTM cell switch procedure”, a “RACH-based CLTM procedure” and a “RA-based CLTM procedure”.
[0067] A “RACH-less LTM cell switch procedure” refers to a LTM cell switch procedure in which the UE does not need to perform RA at the LTM cell switch execution in order to start using the new cell. “LTM” as used herein, when not preceded by “Conditional”, or “C”, refers to a LTM that is not a CLTM, i.e. the LTM is a “non-conditional” LTM.
[0068] A “CLTM candidate cell configuration” for a given cell may include a set of one or moreexecution conditions for triggering a CLTM procedure towards the given cell. A “CLTM candidate cell configuration” is also referred to interchangeably herein as “CLTM configuration” and “CLTM candidate configuration”. A “LTM candidate cell configuration” is also referred to interchangeably herein as “LTM configuration” and “LTM candidate configuration”.
[0069] The techniques described herein are applicable to a variety of different scenarios, including, but not limited to: intra-CU CLTM, inter-CU CLTM, intra-CU LTM for MCG when a UE is in dual connectivity (DC), intra-CU LTM for SCG when UE is in dual connectivity.
[0070] One of the concepts referenced in this disclosure is a “near failure” in CLTM cell switch execution. A “near failure” in CLTM cell switch execution (or a “nearly failed” CLTM cell switch, or a “nearly failed” CLTM cell switch execution) is a CLTM cell switch execution that was successful but had a non-negligible (or quite high) likelihood that it would fail. The risk of a CLTM cell switch execution failing can be expressed in various forms, for example as a percentage of an elapsed time alignment timer (TAT). As an example, a UE can determine that a RACH-less CLTM cell switch is possible because the UE has a valid TA value for a CLTM candidate cell A, and initiate a RACH-less CLTM cell switch towards cell A, which is successful. However, at the time when the CLTM cell switch was triggered, the amount of TAT value that has already elapsed was more than a certain threshold, e.g., expressed as a percentage (e.g., more than 80%) of the total TAT value. Although the TA value was still valid, the threshold can be used by the network to assess whether the TA value was almost outdated. The network can use an indication of the amount of elapsed TAT value compared to the total TAT value to evaluate the risk of the CLTM cell switch execution failing (i.e., whether it “nearly failed”). This threshold value for the TAT value (used to determine whether a CLTM cell switch execution nearly failed) is an example of what is referred to herein as a “nearly failed criterion”.
[0071] The techniques described herein provides benefits for at least the following scenarios.
[0072] Case 1: UE configured with more CLTM candidate cells - A UE can be configured with more (multiple) CLTM candidate cells. If CLTM cell switches towards a certain CLTM candidate cell fail quite often when performed as RACH-less CLTM, and the network acquires this knowledge due to UE reports, the network can attempt some optimisation to improve the situation. For example, the source DU can determine to trigger more frequent early uplink synchronization to acquire a fresher / newer TA value for the concerned CLTM candidate cell to ensure that the TA value is not outdated when the UE triggers CLTM. Another optimisation that the network can do is to avoid RACH-less CLTM towards the concerned CLTM candidate cell, i.e., early TA acquisition for the UE towards that cell is not triggered, and allow the UE to initiate RACH-less CLTM. Yet another optimisation that can be attempted by the network is to trigger RACH-lessLTM towards the concerned cell, i.e., avoiding Conditional LTM, when the network (e.g. the source DU or the source CU) determines that the TAT value is still valid and / or within a certain percentage of the total TAT value. Another optimisation the network can attempt in case of near CLTM failures is to modify the execution conditions (L1 or L3) associated with the cell when used as a CLTM candidate, for example, to anticipate the fulfilment of the execution conditions and allow the UE to initiate CLTM a bit earlier.
[0073] Case 2: UE configured with (at least) one CLTM candidate cell and one LTM candidate cell - A UE can be configured with one or more CLTM candidate cells and one or more non-conditional LTM candidate cells. If CLTM cell switch executions towards a certain CLTM candidate cell fail quite often, and the network acquires this knowledge due to UE reports, the network can attempt some optimisation to improve the situation. For example, the source DU can determine to trigger more frequent early uplink synchronisation to acquire a fresher / newer TA value for the concerned CLTM candidate cell to ensure that the TA value is not outdated when the UE triggers CLTM. Another optimisation that the network can perform is to avoid CLTM executions towards the concerned cell if the TA value is almost outdated, and instead trigger RACH-less or RACH-based LTM towards the concerned cell. Another optimisation the network can attempt in case of near CLTM failure is to modify the execution conditions associated with cell when used as a CLTM candidate, for example, to anticipate the fulfilment of the execution conditions, and allow the UE to initiate CLTM earlier.
[0074] Case 3: UE configured with (at least) one CLTM candidate cell with execution conditions based on L1 measurements, and one CLTM candidate cell with execution conditions based on L3 measurements - A UE can be configured with one or more CLTM candidate cells with associated execution conditions prepared by the source gNB-CU and based on L3 measurements, and one or more CLTM candidate cells with associated execution conditions prepared by the source gNB-DU and based on L1 measurements. If CLTM cell switch executions towards a certain CLTM candidate cell fail (or nearly fail) quite often, and the execution conditions are based on L1 measurements, the CU can determine to change the execution conditions associated with the candidate cell to be based on L3 measurements instead. Or, vice versa, if CLTM cell switch executions towards a certain CLTM candidate cell fail (or nearly fail) quite often, and the execution conditions are based on L3 measurements, the CU can determine to change the execution conditions associated with the candidate cell to be based on L1 measurements instead.
[0075] As noted above, this disclosure provides that a UE (or more generally a wireless device)can be instructed (by the network or by specification) to log and / or report to the network information related to Conditional Layer1 / Layer2 Triggered Mobility (CLTM). The information can be included in a new type of UE report, or be included in an existing UE report, for example a RA report, a RLF report, a SHR, etc. The logging and / or reporting can apply to various scenarios, such as: intra-CU LTM, inter-CU LTM, intra-CU CLTM for Master Cell Group (MCG), intra-CU CLTM for Secondary Cell Group (SCG).
[0076] Exemplary signalling according to embodiments of this disclosure is shown in Fig. 2. Fig.
[0077] 2 shows signalling between a UE 201 and a RAN node 202. Signal 211, which is optional, is sent by the RAN node 202 to the UE 201 to configure the UE 201 to log information relating to a CLTM procedure towards a first CLTM candidate cell. Signal 211, or the configuration sent using signal 211, can be according to any of the embodiments in this disclosure. Signal 211 may also configure the UE 201 to send (report) the information relating to the CLTM procedure to the RAN node 202 (and / or to another RAN node). The RAN node 202 can also or instead send a separate (optional) signal 212 that requests the UE to send the information to the RAN node 202 (and / or to another RAN node). Signal 212, or the configuration sent using signal 212, can be according to any of the embodiments in this disclosure.
[0078] Fig. 2 shows signal 212 being sent to the UE 201 by the same RAN node 202 as signal 211. However, in other examples, signal 212 may be sent to the UE 202 by a different RAN node to the RAN node that sends signal 211 to the UE 202. Signal 211 and signal 212 may be sent in any order or at the same time.
[0079] As shown by signal 213, the UE 201 sends information to the RAN node 202 relating to a CLTM procedure towards a first CLTM candidate cell (also referred to herein as “CLTM related information”). The information sent in signal 213 can be according to any of the embodiments in this disclosure.
[0080] UE embodiments
[0081] The following embodiments are applicable to a UE (or more generally a wireless device), and can be used individually, or in any combination.
[0082] A UE may receive a configuration from a network node (or may be instructed by / configured according to a specification) to log and / or report in a UE report:
[0083] CLTM related information in relation to a failed CLTM cell switch execution.
[0084] CLTM related information in relation to a failed CLTM cell switch execution followed by a successful recovery. In one example of successful recovery: after a failed CLTM cell switch execution, the UE attempts a fast recovery (e.g. the UE performs a successful CLTM cell switch execution to the same CLTM candidate cell or to another CLTMcandidate cell) and the fast recovery succeeds. In another example of successful recovery: after a failed CLTM cell switch execution, the UE attempts a RRC Reestablishment to a cell, which can be the same cell towards which the CLTM cell switch execution failed, or a RRC Reestablishment to a LTM candidate cell, or to a cell which is neither a CLTM candidate cell nor a LTM candidate cell, and the RRC Reestablishment succeeds.
[0085] CLTM related information in relation to a failed CLTM cell switch execution followed by a failure in recovery. The failure in recovery may be a failure in fast recovery where the UE, for example, after a failed CLTM cell switch execution, UE attempts CLTM cell switch execution to the same CLTM candidate cell or to another CLTM candidate cell, and the fast recovery fails. In another example of failure in recovery, after a failed CLTM cell switch execution the UE attempts an RRC Reestablishment to a cell, which can be the same cell towards which the CLTM cell switch execution failed, or a LTM candidate cell, or a cell which is neither a CLTM candidate cell nor a LTM candidate cell, and the RRC Reestablishment fails.
[0086] CLTM related information in relation to a failed CLTM cell switch execution followed by a radio link failure.
[0087] CLTM related information in relation to a near failure in CLTM cell switch execution. CLTM related information in relation to a successful CLTM cell switch execution.
[0088] In some cases, which can be combined with any of the embodiments described herein, the UE can log and / or report in a UE report:
[0089] information for a RACH-less CLTM procedure, and / or
[0090] information for a RACH-based CLTM procedure.
[0091] A UE may log and / or report in a UE report CLTM related information if the failed, nearly failed or successful cell switch execution was triggered by fulfilment of one or more execution conditions, e.g. L1 execution conditions and / or L3 execution conditions associated with the CLTM candidate cell configuration that is executed.
[0092] In relation to a successful (or to a nearly failed) CLTM cell switch execution, the UE may log and / or report in a UE report:
[0093] information about measurements (e.g. measurement results) for evaluation of L1 execution conditions associated with one or more other CLTM candidate cells that the UE is configured with. Optionally, the UE can log and / or report (in a UE report) information about L1 measurements for one or more other CLTM cells when the execution conditions that were fulfilled and triggered the CLTM cell switch execution were based on L3 measurements.information about measurements (e.g. measurement results) for evaluation of L3 execution conditions associated with one or more other CLTM candidate cells that the UE is configured with. Optionally, the UE may log and / or report (in a UE report) information about L3 measurements for one or more other CLTM cells when the execution conditions that were fulfilled and triggered the CLTM cell switch execution were based on L1 measurements.
[0094] In relation to a failed CLTM cell switch execution, the UE may log and / or report in a UE report:
[0095] information about measurements (e.g. measurement results) for evaluation of L1 execution conditions associated with one or more other CLTM candidate cells that the UE is configured with. Optionally, the UE may log and / or report (in a UE report) information about L1 measurements for one or more other CLTM cells when the execution conditions that were fulfilled and triggered the CLTM cell switch execution were based on L3 measurements. Based on this received information, the network may be able to determine if the failed CLTM cell switch execution could have been avoided by, e.g., setting different L1 execution conditions for other CLTM candidate cells, or by configuring the same type of execution conditions (L3 or L1) for the candidate cell where the CLTM cell switch execution failed and for that / those other cell(s).
[0096] information about measurements (e.g. measurement results) for evaluation of L3 execution conditions associated with one or more other CLTM candidate cells that the UE is configured with. Optionally, the UE may log and / or report (in a UE report) information about L3 measurements for one or more other CLTM cells when the execution conditions that were fulfilled and triggered the CLTM cell switch execution were based on L1 measurements. Based on this received information, the network may be able to determine if the failed CLTM cell switch execution could have been avoided by e.g. setting different L3 execution conditions for other CLTM candidate cells, or by configuring the same type of execution conditions (L3 or L1) for the candidate cell where the CLTM cell switch execution failed and for that / those other cell(s).
[0097] As an alternative to the above embodiments, in relation to a successful, nearly failed or failed CLTM cell switch execution, the UE may log and / or report in a UE report information about measurements (e.g. measurement results) performed for one or more other LTM candidate cells, which are not CLTM candidates. This can be, e.g., L1 measurement results and / or L3 measurement results.
[0098] In relation to a failed (or to a nearly failed, or to a successful) CLTM cell switch execution, the UE may log and / or report in a UE report:one or more identities of CLTM candidate cells for which no Layer 1 measurement is available, or for which Layer 1 measurements were available but L1 execution conditions were not fulfilled. In either case, optionally the UE may log and / or report the identity of the CLTM candidate cell only if the corresponding CLTM cell switch execution condition(s) was(were) based on Layer 1 measurements. In a further option, the UE may also log and / or report Layer 3 measurements.
[0099] one or more identities of CLTM candidate cells for which no Layer 3 measurement is available, or for which Layer 3 measurements were available but L3 execution conditions were not fulfilled. In either case, optionally, the UE may log and / or report the identity of the CLTM candidate cell only if the corresponding CLTM cell switch execution condition(s) was(were) based on Layer 3 measurements. In a further option, the UE may also log and / or report Layer 1 measurements.
[0100] In relation to a successful (or to a nearly failed) CLTM cell switch execution, the UE may log and / or report in a UE report:
[0101] one or more identities of a L1 measurement configuration and / or L1 measurement reporting used to execute a CLTM cell switch.
[0102] one or more identities of a L3 measurement configuration and / or L3 measurement reporting used to execute a CLTM cell switch.
[0103] In relation to a successful (or to a nearly failed) CLTM cell switch execution, in addition to information described in other embodiments, the UE may log and / or report information related to failure occurring after the successful (or nearly failed) CLTM cell switch execution, such as the time elapsed from the last successful (or nearly failed) CLTM cell switch execution until radio link failure.
[0104] In relation to a failed CLTM cell switch execution, in addition to information described in other embodiments, the UE may log and / or report information related to recovery actions occurring after the failed CLTM cell switch execution, such as the time elapsed from the last failed CLTM cell switch execution until beam failure recovery, or the time elapsed from the last failed CLTM cell switch execution until a successful failure recovery, or the time elapsed from the last failed CLTM cell switch execution until a failed failure recovery, or the time elapsed from the last failed CLTM cell switch execution until radio link failure, or the time elapsed from the last failed CLTM cell switch execution until an RRC Reestablishment attempt, or the time elapsed from the last failed CLTM cell switch execution until a successful RRC Reestablishment.
[0105] In relation to a failed CLTM cell switch execution followed by a successful recovery (e.g. a successful fast recovery or a successful RRC Reestablishment), the UE may log and / or report in a UE report:one or more identities of CLTM candidate cells for which no Layer 1 measurement is available, or for which Layer 1 measurements were available but L1 execution conditions were not fulfilled. In either case, optionally the UE can log and / or report the identity of the CLTM candidate cell only if the corresponding CLTM cell switch execution condition(s) was(were) based on Layer 1 measurements. In a further option, the UE may also log and / or report Layer 3 measurements.
[0106] one or more identities of CLTM candidate cells for which no Layer 3 measurement is available, or for which Layer 3 measurements were available but L3 execution conditions were not fulfilled. In either case, optionally the UE may log and / or report the identity of the CLTM candidate cell only if the corresponding CLTM cell switch execution condition(s) was(were) based on Layer 3 measurements. In another option, the UE may also log and / or report Layer 1 measurements.
[0107] In relation to a failed CLTM cell switch execution followed by a failed recovery (e.g. a failed fast recovery, a failed RRC Reestablishment, or a Radio Link Failure (in the case of Layer 1 measurements)), the UE may log and / or report in a UE report:
[0108] one or more identities of CLTM candidate cells for which no Layer 1 measurement is available. Optionally, the UE may log and / or report the identity of the CLTM candidate cell only if the corresponding CLTM cell switch execution condition(s) was(were) based on Layer 1 measurements.
[0109] one or more identities of CLTM candidate cells for which no Layer 3 measurement is available. Optionally, the UE can log and / or report the identity of the CLTM candidate cell only if the corresponding CLTM cell switch execution condition(s) was(were) based on Layer 3 measurements.
[0110] In some embodiments, which can be combined with other embodiments described herein, the UE may log and / or report any one or more of:
[0111] CLTM related information in case of failed CLTM cell switch execution (e.g., if a Radio Link Failure occurs, the lastHO-Type in the RLF Report is extended to indicate that the last executed mobility procedure was a Conditional LTM cell switch).
[0112] CLTM related information in case of successful CLTM cell switch execution followed by a Radio Link Failure shortly after.
[0113] CLTM related information in case of near failure in CLTM cell switch execution followed by a Radio Link Failure shortly after.
[0114] CLTM related information in case of a radio link failure (RLF) being detected by the UE while being configured with one or more CLTM candidate configurations. In one example, the UE logs information about the associated execution conditions for the oneor more CLTM candidate cells, which are being evaluated by the UE when the RLF was detected. The UE may also or alternatively log information about the corresponding L1 and / or L3 measurement results for those evaluations. This can also include information about e.g. whether the TimeToTrigger (TTT) timer has been started for the associated event(s) and / or information about the beam that is considered the strongest, e.g. the beam that has triggered the start of the TTT.
[0115] CLTM related information in case of failed CLTM cell switch execution followed by a subsequent attempted or subsequent successful CLTM cell switch execution towards a CLTM candidate cell that is not the same cell towards which the first CLTM cell switch execution failed.
[0116] CLTM related information in case of failed LTM cell switch execution followed by a subsequent attempted or subsequent successful CLTM cell switch execution towards a CLTM candidate cell that is not the same cell towards which the first LTM cell switch execution failed.
[0117] CLTM related information in case of failed LTM cell switch execution towards a first cell followed by a subsequent attempted or subsequent successful CLTM cell switch execution towards the same cell (which is both an LTM candidate cell and a CLTM candidate cell).
[0118] CLTM related information in case of failed CLTM cell switch execution followed by a subsequent re-establishment attempt or successful re-establishment towards a CLTM candidate cell that is not the same cell towards which the first CLTM cell switch execution failed.
[0119] CLTM related information in case of failed CLTM cell switch execution followed by a subsequent attempted recovery procedure or subsequent successful recovery procedure using a CLTM candidate cell configuration. In one example this may correspond to the UE applying the configuration for the CLTM candidate cell (within the corresponding LTM-Candidate) following a cell selection while timer T311 was running. In one example, the recovery procedure may only be started by the UE if the network has configured the UE to do so.
[0120] CLTM related information in case of failed LTM cell switch execution followed by a subsequent attempted recovery procedure or subsequent successful recovery procedure using a CLTM candidate cell configuration. In one example this can correspond to the UE applying the configuration for the CLTM candidate cell (within the corresponding LTM-Candidate) following a cell selection while timer T311 was running. In one example, the recovery procedure may only be started by the UE if the networkhas configured the UE to do so.
[0121] In some embodiments, which can be combined with other embodiments described herein, the UE may log and / or report:
[0122] CLTM related information in case of failed CLTM cell switch execution followed by a subsequent re-establishment attempt or subsequent successful re-establishment towards a cell that is not a CLTM candidate cell and is an LTM candidate cell.
[0123] CLTM related information in case of failed CLTM cell switch execution followed by a subsequent re-establishment attempt or subsequent successful re-establishment towards a cell that is not a CLTM candidate cell and is NOT an LTM candidate cell. CLTM related information in case of failed CLTM cell switch execution followed by a subsequent attempted recovery procedure or subsequent successful recovery procedure using an LTM candidate cell configuration. In one example this can correspond to the UE applying the configuration for the LTM candidate cell (within the corresponding LTM-Candidate) following a cell selection while timer T311 was running. In one example, the recovery procedure may only be started by the UE if the network has configured the UE to do so, e.g. the recovery procedure is only started if attemptLTM-Switch is configured within the Itm-Config that the UE is configured with. In one example, the UE may have an LTM candidate configuration, but no CLTM candidate configuration, for the cell that was selected while T311 was running.
[0124] CLTM related information in case of failed CLTM cell switch execution followed by a subsequent attempted recovery procedure or subsequent successful recovery procedure using a conditional handover configuration. In one example this can correspond to the UE applying condRRCReconfig in the CondReconfigToAddMod entity for the selected cell following a cell selection while timer T311 was running. In one example, the recovery procedure may only be started by the UE if the network has configured the UE to do so, e.g. that the recovery procedure is only started if attemptCondReconfig is configured within the ConditionalReconfiguration that the UE is configured with. In one example, the UE may have a conditional handover (CHO) configuration, but no LTM candidate configuration or conditional LTM candidate configuration, for the cell that was selected while T311 was running. In another example, the UE may have a conditional handover configuration and also an LTM candidate configuration or CLTM candidate configuration, for the cell that was selected while T311 was running.
[0125] The CLTM related information in the different embodiments described herein can include one or more or combination of:- an indication related to a CLTM cell switch execution, indicating that the last executed mobility procedure was a CLTM cell switch.
[0126] ■ By acquiring this indication in case of CLTM cell switch execution failures, together with the cell towards which the mobility fails, the network can decide to change the execution conditions for the candidate cells or, for instance, decide to use the same candidate cell not in conjunction with execution condition (i.e. to have such cell as a CLTM candidate cell), but rather as an LTM candidate cell.
[0127] - an indication on whether CLTM cell switch was initiated based on execution condition(s) based on Layer 1 measurements.
[0128] ■ By acquiring this indication in case of CLTM cell switch execution failures, the network node (e.g., the gNB-DU) can decide to change the L1 based execution conditions or to change from L1 to L3 based execution conditions.
[0129] - an indication on whether CLTM cell switch was initiated based on execution condition(s) based on Layer 3 measurements.
[0130] - an indication, indicating that UE initiated a mobility action (e.g., a CHO) towards a CLTM candidate cell in alternative to (or as a fallback of) a CLTM cell switch, optionally also including the execution condition(s).
[0131] - an indication, indicating that UE initiated a CLTM cell switch towards a CLTM candidate cell in alternative to (or as a fallback of) a LTM cell switch. Optionally a cause for initiating the CLTM cell switch can be indicated, e.g., the LTM cell switch has failed, no TA value was available, or no TA value was acquired.
[0132] - radio measurements related to a CLTM cell switch execution, the radio measurements being Layer 3 or Layer 1 measurements (e.g., the latest measured Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR)) preceding the trigger of the CLTM cell switch execution. The L3 or L1 measurements can be for the current serving cell (or source cell of the cell switch procedure), and / or for the CLTM candidate cell towards which the UE has initiated CLTM cell switch execution, and / or for CLTM candidate cells other than the CLTM candidate cell towards which the UE has initiated CLTM cell switch, and / or for cells which are not CLTM candidate cells. The L1 measurements can be for one or more beams (e.g. SSB or Channel State Information-Reference Signal (CSI-RS)) of the CLTM candidate cell(s) and / or of the serving cell (or source cell of the cell switch procedure). The L3 measurements can also include measurements for one or more beams of the CLTM candidate cell(s) and / or of the serving cell (or source cell of the cell switch procedure).- the TA value for the cell for which CLTM cell switch execution was triggered.
[0133] - an age of the TA value when the CLTM cell switch execution was initiated (for TA value autonomously acquired or for TA value received from the network).
[0134] - an indication that CLTM was initiated towards the same beam used to acquire the TA value for Early UL sync for CLTM.
[0135] - an indication that CLTM was initiated to a different beam compared to the one used to acquire the TA value for Early UL sync for CLTM.
[0136] - an indication of the beam used for CLTM cell switch execution.
[0137] - an indication of the beam used for Early TA acquisition for CLTM.
[0138] - an indication that the CLTM was initiated towards a beam which is an activated beam (i.e., activated TCI state).
[0139] - an indication of one or more activated TCI states.
[0140] - an indication that RACH based CLTM was done via contention free random access (CFRA).
[0141] - an indication that RACH based CLTM was done via contention based random access (CBRA).
[0142] - an indication that RACH based CLTM was done via 2-step Contention Free Random Access (2-step CFRA).
[0143] - an indication that RACH based CLTM was done via 2-step Contention Based Random Access (2-step CBRA).
[0144] - an indication that the (pre-)activated beam used for the CLTM cell switch execution is among the beams for which a configured grant can be used.
[0145] - an indication whether the TA value was estimated autonomously by the UE or received by the network.
[0146] Extension of the methods to dual connectivity
[0147] The techniques described herein can be applied to dual connectivity (DC) scenarios. In particular, the UE can be configured with a conditional LTM for the Master Cell Group (MCG) and / or Secondary Cell Group (SCG) when the UE is in dual connectivity scenarios.
[0148] In any of the earlier embodiments and scenarios, the UE may only log CLTM related information associated with the MCG cells (i.e. the information related to the CLTM candidate cells configured by the Master Node (MN)).
[0149] Alternatively, in any of the earlier embodiments and scenarios, the UE may only log CLTM related information associated with the SCG cells (i.e. the information related to the CLTM candidate cells configured by the Secondary Node (SN)).In another alternative, in any of the earlier embodiments and scenarios, the UE may log CLTM related information associated with both the MCG cells and the SCG cells.
[0150] The UE may implicitly or explicitly indicate which CLTM candidate cells and / or CLTM related information are configured by the MN (or are associated with the MCG), and which CLTM candidate cells and / or the CLTM related information are configured by the SN (or are associated with the SCG).
[0151] The network may instruct or configure the UE to include the CLTM candidate cells and / or CLTM related information in one or more SON reports.
[0152] Network embodiments
[0153] While the above embodiments primarily relate to the operations and functionality of a UE, it will be appreciated that the techniques described herein also relate to the network, and in particular to a Radio Access Network (RAN) node, such as a gNB, a 6G-equivalent of a gNB, a base station, a gNB-CU, a gNB-DU, a source gNB-CU, a source gNB-DU, a target gNB-CU, a target gNB-DU, a source gNB, a target gNB, a source MN, a target MN, a source SN, a target SN, a candidate gNB-DU, a candidate gNB-CU, a candidate gNB, a candidate MN, ora candidate SN.
[0154] Thus, a first RAN node according to the techniques described herein can be configured or operable to receive the information sent by the UE relating to a CLTM procedure towards a first CLTM candidate cell.
[0155] The first RAN node can configure a UE to log and / or report CLTM related information. The first RAN node can configure the UE to log and / or report any of the types of CLTM related information described in the above embodiments. In alternative embodiments, a UE can be preconfigured or pre-programmed to log and / or report CLTM related information.
[0156] The first RAN node can send a request to a UE for the UE to send UE reports comprising CLTM related information.
[0157] The first RAN node, upon or after receiving UE reports comprising CLTM related information from the UE, can determine that it can perform (or is responsible for) optimisation for CLTM, and take corresponding actions. Non-limiting examples of actions can include: initiating the preparation (or reconfiguration) of CLTM with different execution conditions compared to before (e.g. based on Layer 1 measurements instead of Layer 3 measurements, or vice versa); consider certain cell(s) previously not used as CLTM candidate cell(s) as CLTM candidate cell(s); refrain from using certain cell(s) as CLTM candidate cell(s); use certain cell(s) as LTM candidate cell(s) and not as CLTM candidate cell(s); use certain cell(s) as LTM candidate cell(s) as well as CLTM candidate cell(s).The first RAN node can send to another network node (e.g. a core network node or a second RAN node) part or all of the CLTM related information comprised in the report received from the UE. In addition or alternatively, the first RAN node can send information derived from the CLTM related information to the other network node. An example of when the first RAN node can send this information to another node is when the first RAN node (that received the UE report) is not responsible for, or is not the only RAN node responsible for, optimising CLTM performance (e.g., reduce / avoid CLTM cell execution failures), and the other RAN node is, at least in part, responsible for CLTM optimisation. The first RAN node that received the CLTM related information from the UE can, in addition or alternatively to sending part or all of the CLTM related information (or information derived therefrom) to another RAN node, send to the other RAN node additional information indicating a type (or category, or class) for a CLTM cell switch execution, as explained further below.
[0158] Each of the first and second RAN nodes can be one of: a source gNB-CU, a source gNB-DU, a target gNB-CU, target gNB-DU, source gNB, target gNB, source MN, target MN, source SN, target SN, candidate gNB-DU, candidate gNB-CU, candidate gNB, candidate MN, candidate SN.
[0159] A first RAN node (e.g. source CU, source MN, source SN, etc.) or second RAN node (e.g. source DU) can send configuration parameters related to near-failure in CLTM cell switch execution to a UE, instructing the UE to log and / or report CLTM related information in case of near-failure in a CLTM cell switch execution. For example, the RAN node can provide conditions to the UE which, upon fulfilment, trigger the UE to log a SON report (e.g. a Successful Handover Report) containing CLTM related information (since the criteria used / configured by the network to determine that a CLTM cell switch execution is a near-failure are satisfied).
[0160] CLTM cell switch execution classification and associated signalling
[0161] A RAN node (e.g., the source CU, or the source DU, or the source MN, or the source SN), based on received CLTM related information comprised in UE report(s), can perform an initial analysis for CLTM and determine a type (or a category, or a class) for a certain CLTM cell switch execution. Non-limiting examples of type / category / class can include:
[0162] “too early CLTM” (or “CLTM too early”, or similar)
[0163] “too early intra-CU CLTM” (or “intra-CU CLTM too early”, or similar)
[0164] “too early inter-CU CLTM” (or “inter-CU CLTM too early”, or similar)
[0165] “too late CLTM” (or “CLTM too late”, or similar)
[0166] “too late intra-CU CLTM” (or “intra-CU CLTM too late”, or similar)
[0167] “too late inter-CU CLTM” (or “inter-CU CLTM too late”, or similar)“CLTM to wrong cell” (or “CLTM to wrong cell”, or similar)
[0168] “intra-CU CLTM to wrong cell” (or “intra-CU CLTM to wrong cell”, or similar) “inter-CU CLTM to wrong cell” (or “inter-CU CLTM to wrong cell”, or similar) “ping-pong CLTM” (or “CLTM ping-pong”, or similar)
[0169] “ping-pong intra-CU CLTM” (or “intra-CU CLTM ping-pong”, or similar)
[0170] “ping-pong inter-CU CLTM” (or “inter-CU CLTM ping-pong”, or similar)
[0171] A first RAN node (e.g. the source CU, or a first gNB) can send to a second RAN node (e.g. the source DU or a second gNB) the derived category (or type, or class) for a certain CLTM cell switch execution. One case in which this is beneficial is when the second RAN node can use this information for Mobility Robustness Optimisation (MRO) for Conditional LTM. For example, if a source DU receives information from a source CU that many CLTM cell switch execution are classified as “too late CLTM”, it can try to allow the UE to anticipate the CLTM triggering by configuring higher values of RSRP related thresholds used in Layer 1 measurement-based execution conditions. In some examples, the first RAN node is the source CU and the second RAN node is the source DU. In other examples, the first RAN node is the source DU and the second RAN node is the source CU. In other examples, the first RAN node is the source gNB and the second RAN node is one of the gNBs controlling a candidate CLTM cell (or vice versa). In other examples, the first RAN node is the source MN and the second RAN node is a target MN (or vice versa). In yet other examples, the first RAN node is the source SN and the second RAN node is a target SN (or vice versa).
[0172] An exemplary implementation of the techniques described herein in the 3GPP standards (e.g., 3GPP TS 38.473 v18.5.0 (F1AP) and / or 3GPP TS 38.423 v18.5.0 (XnAP)) is provided below, with new additions or changes to the standard indicated in bold italics underline.
[0173] In one exemplary implementation, the F1AP ACCESS AND MOBILITY INDICATION message in 3GPP TS 38.473 v18.5.0 is extended to signal a too early CLTM cell switch execution or a CLTM cell switch execution to wrong cell. This can be used, for instance, to enable the source gNB-CU to indicate to the source gNB-DU that a certain CLTM cell switch was performed too early or to a wrong cell.
[0174] ************************************************************************************************************* 9.2.10.1 ACCESS AND MOBILITY INDICATION
[0175] This message is sent by gNB-CU to gNB-DU to provide access and mobility information to the gNB-DU.
[0176] Direction: gNB-CU gNB-DU.
[0177]
[0178] *************************************************************************************************************
[0179] In another exemplary implementation, the XnAP HANDOVER REPORT message in 3GPP TS 38.423 v18.5.0 is extended to signal a too early CLTM cell switch execution or a CLTM cell switch execution to wrong cell.
[0180] 9.1.3.17 HANDOVER REPORT
[0181] This message is sent by NG-RAN node₁ to NG-RAN node2to report a handover failure event, or other critical mobility problem.
[0182] Direction: NG-RAN node1
[0183]
[0184]
[0185]
[0186] * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
[0187] Fig. 3 is a flow chart of a method performed by a wireless device in accordance with particular embodiments. Embodiments of the method may be performed by a wireless device such as UE 512 or wireless device 600 as described later with reference to Figs. 5 and 6 respectively.
[0188] In step 302, which is optional, the wireless device can receive a configuration that indicates information to be logged and / or reported to the communication network relating to a CLTM procedure towards a first CLTM candidate cell. The configuration can be received from a RAN node in the communication network. In alternative embodiments, the wireless device can be preconfigured with such a configuration, rather than receiving it, e.g. from the communication network, or from a RAN node in the communication network. Step 302 is similar or corresponding to signal 211 in Fig. 2.
[0189] In step 304, which is optional, the wireless device can receive a request for information relating to the CLTM procedure towards the first CLTM candidate cell. The request can be received from a RAN node in the communication network. The request can be received from the same RAN node that the configuration is received from in step 302, or the request can be received from a different RAN node to the RAN node that the configuration is received from in step 302. Step 304 is similar or corresponding to signal 212 in Fig. 2.
[0190] In step 306, the wireless device sends information to a RAN node relating to the CLTM procedure towards the first CLTM candidate cell. Step 306 is similar or corresponding to signal 213 in Fig. 2.
[0191] The information can be sent in any of: a SON report; a SHR; an RLF report; a RA report; or a Successful PSCell Change Report (SPR).
[0192] The CLTM procedure attempted or performed by the wireless device may relate to a CLTM procedure for any of an MCG; an SCG; or an MCG and an SCG.
[0193] Fig. 4 is a flowchart of a method performed by a RAN node in accordance with particular embodiments. Embodiments of the method may be performed by network node 510 or 700 as described later with reference to Figs. 5 and 7 respectively) as follows.
[0194] Fig. 4 shows three steps, steps 402, 404 and 406. The RAN node may perform any one or more of these steps.
[0195] In step 402, which, as noted, is optional, the RAN node sends, to a wireless device, a configuration for information to be logged and / or reported relating to a CLTM procedure towards a first CLTM candidate cell. The configuration for information can indicate one or more types of information to be logged and / or reported relating to the CLTM procedure; and / or a threshold valuerelating to a timing value (e.g. a TA value) and / or a time alignment timer.
[0196] In step 404, which, as noted, is optional, the RAN node sends, to the wireless device, a request for information relating to the CLTM procedure towards the first CLTM candidate cell.
[0197] In step 406, which, as noted, is optional, the RAN node receives, from the wireless device, information relating to the CLTM procedure towards the first CLTM candidate cell. The information can be received in any of: a SON report; a SHR; an RLF report; a RA report; or a SPR.
[0198] Although not shown in Fig. 4, the RAN node can send the information received in step 406, part of the information received in step 406, or information derived from the information received in step 406 to another node in the communication network. Information derived from the received information can be a classification for an outcome of the CLTM procedure.
[0199] The configuration sent in step 402 and / or the request sent in step 404 can indicate one or more types of information to be logged and / or reported relating to the CLTM procedure. The configuration sent in step 402 and / or the request sent in step 404 can also or alternatively indicate one or more scenarios in which information is to be logged and / or reported relating to the CLTM procedure.
[0200] Although not shown in Fig. 4, the RAN node can further perform optimisation and / or modification of CLTM procedures based on the received information. Optimisation and / or modification of CLTM procedures can comprise modifying a CLTM candidate cell configuration for the first CLTM candidate cell. Optimisation and / or modification of CLTM procedures can also or alternatively comprise modifying execution conditions comprised in the CLTM candidate cell configuration for the first CLTM candidate cell.
[0201] The following features can be applied to the method of Fig. 3 and / or the method of Fig. 4. The CLTM procedure may have been attempted or performed by the wireless device towards the first CLTM candidate cell. Alternatively or in addition, the CLTM procedure may be a CLTM procedure that the wireless device is configured to attempt or perform towards the first CLTM candidate cell.
[0202] The CLTM procedure may be one or more of the following. The CLTM procedure may be a CLTM procedure that failed. The CLTM procedure may be a CLTM procedure that succeeded. The CLTM procedure may be a CLTM procedure that satisfies a nearly failed criterion. The CLTM procedure may be a RACH-less CLTM procedure. The CLTM procedure may be a RACH-based CLTM procedure. The CLTM procedure may be a CLTM procedure triggered by fulfilment of one or more execution conditions. The one or more execution conditions can be based on one or both of a L1 measurement of the first CLTM candidate cell and a L3 measurement of the first CLTM candidate cell. The CLTM procedure may be a CLTM procedure that failed and wasfollowed by a recovery procedure that succeeded. The CLTM procedure may be a CLTM procedure that failed and was followed by a recovery procedure that failed. The CLTM procedure may be a CLTM procedure that succeeded and was followed by a radio link failure within a first time interval after the CLTM procedure. The CLTM procedure may be a CLTM procedure that satisfied a nearly failed criterion and was followed by a radio link failure within a second time interval after the CLTM procedure. In this latter case, a CLTM procedure that satisfies a nearly failed criterion may be a CLTM procedure having, when the CLTM procedure was performed, a time alignment timer value that is above a nearly failed threshold value.
[0203] The first CLTM candidate cell may be one or more of the following. The first CLTM candidate cell may be a CLTM candidate cell for which, when the CLTM procedure was attempted or performed, there were no Layer 1 measurements available. The first CLTM candidate cell may be a CLTM candidate cell for which, when the CLTM procedure was attempted or performed, there were no Layer 3 measurements available. The first CLTM candidate cell may be a CLTM candidate cell for which, when the CLTM procedure was attempted or performed, one or more Layer 1 measurements were available and one or more execution conditions based on the one or more Layer 1 measurements were not fulfilled. The first CLTM candidate cell may be a CLTM candidate cell for which, when the CLTM procedure was attempted or performed, one or more Layer 3 measurements were available and one or more execution conditions based on the one or more Layer 3 measurements were not fulfilled.
[0204] The information sent in step 306 (or received in step 406) may comprise one or more of the following information types. The information may comprise an indication that the CLTM procedure failed. The information may comprise an indication that the CLTM procedure succeeded. The information may comprise an identity of the first CLTM candidate cell. The information may comprise an identity of a CLTM candidate cell configuration for which the CLTM procedure failed. The information may comprise an identity of a LTM candidate cell configuration for which an LTM procedure failed. The information may comprise an identity of one or more CLTM candidate cells other than the first CLTM candidate cell. The information may comprise an identity of one or more LTM candidate cells other than the first CLTM candidate cell. The information may comprise a Layer 1 measurement result for the first CLTM candidate cell. The information may comprise a Layer 3 measurement result for the first CLTM candidate cell. The information may comprise a Layer 1 measurement result for one or more CLTM candidate cells other than the first CLTM candidate cell. The information may comprise a Layer 3 measurement result for one or more CLTM candidate cells other than the first CLTM candidate cell. The information may comprise a Layer 1 measurement configuration for the first CLTM candidate cell. The information may comprise a Layer 3 measurement configuration for the first CLTM candidate cell. The informationmay comprise information related to a radio link failure after the CLTM procedure was performed. The information may comprise information related to a recovery procedure attempted or performed after the CLTM procedure failed. The information may comprise an indication that the CLTM procedure is the most recent mobility procedure attempted or performed by the wireless device. The information may comprise information about an execution condition for attempting or performing the CLTM procedure (in accordance with a CLTM candidate cell configuration for the first CLTM candidate cell). The information may comprise a value of a time alignment timer when the CLTM procedure was performed by the wireless device.
[0205] In the above information types, the one or more other CLTM candidate cells (or one or more candidate cells other than the first CLTM candidate cell) can be one or more of the following. The one or more other CLTM candidate cells may be CLTM candidate cell(s) for which, when the CLTM procedure was performed, no Layer 1 measurement was available. The one or more other CLTM candidate cells may be CLTM candidate cell(s) for which, when the CLTM procedure was performed, no Layer 3 measurement was available. The one or more other CLTM candidate cells may be CLTM candidate cell(s) for which, when the CLTM procedure was performed, a Layer 3 measurement was available and an execution condition based on the Layer 3 measurement was not fulfilled. The one or more other CLTM candidate cells may be CLTM candidate cell(s) for which, when the CLTM procedure was performed, a Layer 1 measurement was available and an execution condition based on the Layer 1 measurement was not fulfilled.
[0206] The information related to the recovery procedure may comprise an indication of time elapsed between attempting the CLTM procedure and attempting or performing the recovery procedure. Information related to a radio link failure after the CLTM procedure was performed may comprise an indication of time elapsed between performing the CLTM procedure and the radio link failure (between the wireless device and the first CLTM candidate cell).
[0207] The CLTM procedure may have been attempted or performed by the wireless device after a LTM procedure towards a first LTM candidate cell for the wireless device failed. In this case, the first LTM candidate cell may be the same as the first CLTM candidate cell. The CLTM procedure may have been attempted or performed by the wireless device after a CLTM procedure towards another CLTM candidate cell failed. The CLTM procedure may have been attempted or performed by the wireless device after a CLTM procedure towards another CLTM candidate cell succeeded.
[0208] The CLTM procedure may have been attempted or performed by the wireless device before a re-establishment procedure was attempted or performed towards the first CLTM candidate cell or another CLTM candidate cell. The CLTM procedure may have been attempted or performed by the wireless device before a re-establishment procedure was attempted or performed towardsa second a LTM candidate cell for the wireless device. The CLTM procedure may have been attempted or performed by the wireless device before a recovery procedure was attempted or performed using a CLTM candidate cell configuration. The CLTM procedure may have been attempted or performed by the wireless device before a recovery procedure was attempted or performed using a LTM candidate cell configuration. The CLTM procedure may have been attempted or performed by the wireless device before a recovery procedure was attempted or performed using a conditional handover configuration.
[0209] The information may be sent in step 306 after detecting a radio link failure (between the wireless device and a current cell of the wireless device). In this case, the information can comprise any one or more of the following. The information can be related to an execution condition for performing the CLTM procedure towards the first CLTM candidate cell based on an evaluation of the execution condition when the radio link failure was detected. The information can be an L1 measurement result for the first CLTM candidate cell when the radio link failure was detected. The information can be an L3 measurement result for the first CLTM candidate cell when the radio link failure was detected. The information can be information related to a time to trigger timer for the CLTM procedure. The information can be an identity of a CLTM candidate cell configuration corresponding to the first CLTM candidate cell. The information can be an identity of a LTM candidate cell configuration corresponding to the first CLTM candidate cell. The information can be an identifier for the first CLTM candidate cell.
[0210] Fig. 5 shows an example of a communication system 500 in accordance with some embodiments. In the example, the communication system 500 includes a telecommunication network 502 that includes an access network 504, such as a radio access network (RAN), and a core network 506, which includes one or more core network nodes 508. The access network 504 includes one or more access network nodes or base stations of various types, such as access network nodes 510a and 510b (one or more of which are also referred to as “RAN network nodes 510” or “RAN nodes 510” herein), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (AP). Some embodiments of the access network 504 may include more than one access network technology. The network nodes 510 of access network 504 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 512A, 512B, 512C, and 512D (one or more of which may be generally referred to as UEs 512) to the core network 506 over one or more wireless connections.
[0211] Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied andintegrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 502 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 502 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 nodes to implement one or more functionalities of any node in the telecommunication network 502, including one or more access network nodes 510 and / or core network nodes 508.
[0212] 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 (RIC) (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 A1, F1, W1, E1, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access 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 (SMO) Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies.
[0213] The network nodes 510 facilitate direct or indirect connection of wireless devices / UEs 512, such as by connecting UEs 512a, 512b, 512c, and 512d (one or more of which may be generally referred to as UEs 512) to the core network 506 over one or more wireless connections. The access network nodes 510 may be, for example, access points (APs) (e.g. radio access points), base stations (BSs) (e.g. radio base stations, Node Bs, evolved Node Bs (eNBs) and New Radio (NR) NodeBs (gNBs)).
[0214] 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 500 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 500 may includeand / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.
[0215] The wireless devices / UEs 512 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 510 and other communication devices. Similarly, the access network nodes 510 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 512 and / or with other network nodes or equipment in the telecommunication network 502 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 502. More specifically, UEs 512 may send messages, data, and / or other signals to network nodes 508, 510 or other elements of the telecommunications network 502 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 508, 510 may send messages, data, and other signals to UEs 512, other network nodes 508, 510, and other devices in telecommunications network 502 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 512 by transmitting the message to an access network node 510 that will then transmit the message to the intended UE 512. Similarly, a core network node 108 may receive a particular message from a UE 512 by receiving the message from an access network node 510 that itself received the message from the UE 512.
[0216] In the depicted example, the core network 506 connects elements of the access network 504 (e.g. one or more of the access network nodes 510) to one or more host computing systems, such as host 516. 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 506 includes one more core network nodes (e.g. core network node 508) of various types that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the wireless devices / UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 508. Example core network nodes include 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 Deconcealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).The host 516 may be under the ownership or control of a service provider other than an operator or provider of the access network 504 and / or the telecommunication network 502. The host 516 may be operated by the service provider or on behalf of the service provider. The host 516 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
[0217] As a whole, the communication system 500 of Fig. 5 enables connectivity between the wireless devices / UEs, network nodes, and hosts. In that sense, the communication system 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 2ndGeneration (2G), 3rdGeneration (3G), 4thGeneration (4G), 5thGeneration (5G) standards, or any applicable future generation standard (e.g. 6thGeneration (6G)); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC), ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 500 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 500 supporting different standards, protocols, or rule sets.
[0218] As one example, in certain embodiments, access network 504 may contain some access network nodes 510 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 510 support (or the same access network nodes 510 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 502 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.
[0219] In some examples, the telecommunication network 502 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 502 maysupport network slicing to provide different logical networks to different devices that are connected to the telecommunication network 502. For example, the telecommunications network 502 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.
[0220] In some examples, the UEs 512 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 504 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 504. Additionally, a UE may be configured for operating in single- or multi-Radio Access Technology (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-UTRA (UMTS Terrestrial Radio Access) Network) New Radio - Dual Connectivity (EN-DC).
[0221] In the example, the hub 514 communicates with the access network 504 to facilitate indirect communication between one or more UEs (e.g., UE 512c and / or 512d) and network nodes (e.g., network node 510b). In some examples, the hub 514 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 514 may be a broadband router enabling access to the core network 506 for the UEs. As another example, the hub 514 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 510, or by executable code, script, process, or other instructions in the hub 514. As another example, the hub 514 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 514 may be a content source. For example, for a UE that is a VR device, display, loudspeaker, or other media delivery device, the hub 514 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 514 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 514 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy Internet of Things (loT) devices.
[0222] The hub 514 may have a constant / persistent or intermittent connection to the network node 510b. The hub 514 may also allow for a different communication scheme and / or schedule between the hub 514 and UEs (e.g., UE 512c and / or 512d), and between the hub 514 and the core network 506. In other examples, the hub 514 is connected to the core network 506 and / orone or more UEs via a wired connection. Moreover, the hub 514 may be configured to connect to a machine-to-machine (M2M) service provider over the access network 504 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 510 while still connected via the hub 514 via a wired or wireless connection. In some embodiments, the hub 514 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 510b. In other embodiments, the hub 514 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 510b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.
[0223] Fig. 6 shows a wireless device 600, which may be configured to operate in communication system 500 of Fig. 5. The wireless device 600 may be alternatively referred to as a UE 600, like a UE 512 within the context of communication system 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 customerpremise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, and wireless terminal. Other examples include any type of UE identified by the 3rdGeneration 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.
[0224] A wireless device 600 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 600 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 600 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 600 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).In particular embodiments, wireless device 600 includes processing circuitry 602 that is operatively coupled via a bus 604 to an input / output interface 606, a power source 608, a memory 610, a communication interface 612, and / or any other component, or any combination thereof. Certain embodiments of wireless device 600 may include all or a subset of the components shown in Fig. 6. The level of integration between the components may vary from one embodiment of wireless device 600 to another. In general, in a particular embodiment of wireless device 600, processing circuitry 602, input / output interface 606, power source 608, memory 610, and communication interface 612 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 600. Further, certain embodiments of wireless devices 600 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
[0225] The processing circuitry 602 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 610. The processing circuitry 602 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 602 may include multiple central processing units (CPUs). The processing circuitry 602 may be configured to cause the wireless device 600 to perform the methods described herein.
[0226] In the example, the input / output interface 606 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 600. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.In some embodiments, the power source 608 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 608 may further include power circuitry for delivering power from the power source 608 itself, and / or an external power source, to the various parts of wireless device 600 via input circuitry or an interface such as an electrical power cable. Power source 608 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 600 to which power is supplied.
[0227] The memory 610 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 610 includes one or more programs 614, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 616. The memory 610 may store, for use by wireless device 600, any of a variety of various operating systems or combinations of operating systems.
[0228] The memory 610 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 (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card’. The memory 610 may allow wireless device 600 to access instructions, programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 610, which may be or comprise a device-readable storage medium.
[0229] The processing circuitry 602 may be configured to communicate with an access network or other network via or using the communication interface 612. The communication interface 612 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 622. The communication interface 612 may include one or more transceivers used to communicate, such as by communicating with one or more remotetransceivers 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 618 and / or a receiver 620 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 618 and receiver 620 may be coupled to one or more antennas (e.g., antenna 622) and may share circuit components, software or firmware, or alternatively be implemented separately.
[0230] In the illustrated embodiment, communication functions of the communication interface 612 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMAX, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
[0231] In particular embodiments, wireless device 600 may provide an output of data captured via a sensor, through its communication interface 612, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 600 can be communicated through a wireless connection to a network node via another wireless device 600. 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).
[0232] As another example, wireless device 600 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 600 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.
[0233] Wireless device 600, 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 600 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 600 shown in Fig. 6.
[0234] As yet another specific example, in an loT scenario, wireless device 600 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 600 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 600 may implement the 3GPP NB-loT standard. In other scenarios, wireless device 600 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.
[0235] In practice, any number of wireless devices 600 may be used together with respect to a single use case. For example, a first wireless device 600 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 600 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 600 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 600 can also include more than one of the functionalities described above. For example, wireless device 600 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
[0236] Fig. 7 shows an access node or RAN node 700 in accordance with some embodiments. As used herein, RAN 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, RAN node 700 maybe configured to operate in communication system 500 of Fig. 5, like RAN nodes 508. 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).
[0237] RAN nodes 700 may be categorised 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. RAN node 700 may be a relay node or a relay donor node controlling a relay. RAN nodes 700 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units (CUs), distributed units (DUs)) (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).
[0238] Other examples of RAN nodes 700 include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O& M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).
[0239] In particular embodiments, RAN node 700 includes a processing circuitry 702, a memory 704, a communication interface 706, and a power source 708. In general, in a particular embodiment of RAN node 700, processing circuitry 702, memory 704, communication interface 706, and power source 708 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of RAN node 700.
[0240] The RAN node 700 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 RAN node 700 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several 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 RAN node 700 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 704 or portions of memory 704 for different RATs)and some components may be reused (e.g., a same antenna 710 may be shared by different RATs). The RAN node 700 may also include multiple sets of the various illustrated components for different wireless technologies integrated into RAN node 700, 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 RAN node 700.
[0241] The processing circuitry 702 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 704, to provide RAN node 700 functionality. The processing circuitry 702 may be configured to cause the RAN node 700 to perform the methods described herein.
[0242] In some embodiments, the processing circuitry 702 includes a system on a chip (SOC). In some embodiments, the processing circuitry 702 includes one or more of radio frequency (RF) transceiver circuitry 712 and baseband processing circuitry 714. In some embodiments, the RF transceiver circuitry 712 and the baseband processing circuitry 714 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 712 and baseband processing circuitry 714 may be on the same chip or set of chips, boards, or units.
[0243] The memory 704 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 702. The memory 704 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 702 and utilized by the RAN node 700. The memory 704 may be used to store any calculations made by the processing circuitry 702 and / or any data received via the communication interface 706. In some embodiments, the processing circuitry 702 and memory 704 is integrated.The communication interface 706 is used in wired or wireless communication of signalling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 706 comprises port(s) / terminal(s) 716 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, RAN node 700 may be capable of wireless communication and communication interface 706 may also include radio front-end circuitry 718 that may be coupled to, or in certain embodiments a part of, an antenna 710. Particular embodiments of radio front-end circuitry 718 include filter(s) 720 and amplifier(s) 722. The radio front-end circuitry 718 may be connected to an antenna 710 and processing circuitry 702. The radio front-end circuitry may be configured to condition signals communicated between antenna 710 and processing circuitry 702. The radio front-end circuitry 718 may receive digital data that is to be sent out to other RAN nodes or UEs via a wireless connection. The radio front-end circuitry 718 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 720 and / or amplifiers 722. The radio signal(s) may then be transmitted via the antenna 710. Similarly, when receiving data, the antenna 710 may collect radio signals which are then converted into digital data by the radio front-end circuitry 718. The digital data may be passed to the processing circuitry 702. In other embodiments, the communication interface may comprise different components and / or different combinations of components.
[0244] In certain alternative embodiments, RAN node 700 may be capable of wireless communication but does not include separate radio front-end circuitry 718, instead, the processing circuitry 702 includes radio front-end circuitry and is connected to the antenna 710. Similarly, in some embodiments, all or some of the RF transceiver circuitry 712 is part of the communication interface 706. In still other embodiments, the communication interface 706 includes one or more ports or terminals 716, the radio front-end circuitry 718, and the RF transceiver circuitry 712, as part of a radio unit (not shown), and the communication interface 706 communicates with the baseband processing circuitry 714, which is part of a digital unit (not shown).
[0245] The antenna 710 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 710 may be coupled to the radio front-end circuitry 718 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 710 is separate from the network node 700 and connectable to the RAN node 700 through one or more interfaces or ports.
[0246] The antenna 710, communication interface 706, and / or the processing circuitry 702 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the RAN node 700. Any information, data and / or signalsmay be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 710, the communication interface 706, and / or the processing circuitry 702 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the RAN node 700. Any information, data and / or signals may be transmitted to a UE, another RAN node and / or any other network equipment.
[0247] The power source 708 provides power to the various components of RAN node 700 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 708 may further comprise, or be coupled to, power management circuitry to supply the components of the RAN node 700 with power for performing the functionality described herein. For example, the RAN node 700 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 708. As a further example, the power source 708 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.
[0248] Embodiments of the RAN node 700 may include additional components beyond those shown in Fig. 7 for providing certain aspects of the RAN 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 RAN node 700 may include user interface equipment to allow input of information into the RAN node 700 and to allow output of information from the RAN node 700. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the RAN node 700.
[0249] Fig. 8 is a block diagram illustrating a virtualization environment 800 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 800 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 environment800 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.
[0250] Applications 802 (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.
[0251] Hardware 804 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 806 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 808A and VM 808B (which may be collectively referred to as VMs 808), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 806 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 808.
[0252] The VMs 808 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 806. Different embodiments of the instance of a virtual appliance 802 may be implemented on one or more of VMs 808, 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.
[0253] In the context of NFV, each of the VMs 808 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 808, and that part of hardware 804 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 808 on top of the hardware 804 and corresponds to an application 802.
[0254] Hardware 804 may be implemented in a standalone network node with generic or specific components. Hardware 804 may implement some functions via virtualization. Alternatively, hardware 804 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 810, which, among others, oversees lifecycle management of applications 802. In someembodiments, hardware 804 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 signalling can be provided with the use of a control system 812 which may alternatively be used for communication between hardware nodes and radio units.
[0255] Although the computing devices described herein (e.g., wireless devices, UEs, RAN nodes, core network nodes) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software 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.
[0256] 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 circuitryalone 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.
[0257] The foregoing merely illustrates the principles of the disclosure. Various modifications and alterations to the described embodiments will be apparent to those skilled in the art in view of the teachings herein. It will thus be appreciated that those skilled in the art will be able to devise numerous systems, arrangements, and procedures that, although not explicitly shown or described herein, embody the principles of the disclosure and can be thus within the scope of the disclosure. Various exemplary embodiments can be used together with one another, as well as interchangeably therewith, as should be understood by those having ordinary skill in the art.
Claims
CLAIMS1. A method performed by a wireless device, the method comprising:sending (306), to a radio access network, RAN, node in a communication network, information relating to a Conditional L1 / L2 triggered mobility, CLTM, procedure towards a first CLTM candidate cell.
2. The method of claim 1, wherein the CLTM procedure is:a CLTM procedure that was attempted or performed by the wireless device towards the first CLTM candidate cell; and / ora CLTM procedure that the wireless device is configured to attempt or perform towards the first CLTM candidate cell.
3. The method of any preceding claim, wherein the CLTM procedure is one or more of:a CLTM procedure that failed;a CLTM procedure that succeeded;a CLTM procedure that satisfies a nearly failed criterion;a RACH-less CLTM procedure;a RACH-based CLTM procedure;a CLTM procedure triggered by fulfilment of one or more execution conditions;a CLTM procedure that failed and was followed by a recovery procedure that succeeded; a CLTM procedure that failed and was followed by a recovery procedure that failed; a CLTM procedure that succeeded and was followed by a radio link failure within a first time interval after the CLTM procedure;a CLTM procedure that satisfied a nearly failed criterion and was followed by a radio link failure within a second time interval after the CLTM procedure.
4. The method of claim 3, wherein a CLTM procedure that satisfies a nearly failed criterion comprises a CLTM procedure having, when the CLTM procedure was performed, a time alignment timer value that is above a nearly failed threshold value.
5. The method of claim 3 or 4, wherein the one or more execution conditions are based on one or both of: a Layer 1 measurement of the first CLTM candidate cell; and a Layer 3 measurement of the first CLTM candidate cell.
6. The method of any preceding claim, wherein the first CLTM candidate cell is one or more of:a CLTM candidate cell for which, when the CLTM procedure was attempted or performed, there were no Layer 1 measurements available;a CLTM candidate cell for which, when the CLTM procedure was attempted or performed, there were no Layer 3 measurements available;a CLTM candidate cell for which, when the CLTM procedure was attempted or performed, one or more Layer 1 measurements were available and one or more execution conditions based on the one or more Layer 1 measurements were not fulfilled;a CLTM candidate cell for which, when the CLTM procedure was attempted or performed, one or more Layer 3 measurements were available and one or more execution conditions based on the one or more Layer 3 measurements were not fulfilled.
7. The method of any preceding claim, wherein the information comprises one or more of: an indication that the CLTM procedure failed;an indication that the CLTM procedure succeeded;an identity of the first CLTM candidate cell;an identity of a CLTM candidate cell configuration for which the CLTM procedure failed; an identity of a LTM candidate cell configuration for which an LTM procedure failed; an identity of one or more CLTM candidate cells other than the first CLTM candidate cell; an identity of one or more LTM candidate cells other than the first CLTM candidate cell; a Layer 1 measurement result for the first CLTM candidate cell;a Layer 3 measurement result for the first CLTM candidate cell;a Layer 1 measurement result for one or more CLTM candidate cells other than the first CLTM candidate cell;a Layer 3 measurement result for one or more CLTM candidate cells other than the first CLTM candidate cell;a Layer 1 measurement configuration for the first CLTM candidate cell;a Layer 3 measurement configuration for the first CLTM candidate cell;information related to a radio link failure after the CLTM procedure was performed; information related to a recovery procedure attempted or performed after the CLTM procedure failed;an indication that the CLTM procedure is the most recent mobility procedure attempted or performed by the wireless device;information about an execution condition for attempting or performing the CLTM procedure (in accordance with a CLTM candidate cell configuration for the first CLTM candidate cell); and a value of a time alignment timer when the CLTM procedure was performed by the wireless device.
8. The method of claim 7, wherein the one or more other CLTM candidate cells are one or more of:CLTM candidate cell(s) for which, when the CLTM procedure was performed, no Layer 1 measurement was available;CLTM candidate cell(s) for which, when the CLTM procedure was performed, no Layer 3 measurement was available;CLTM candidate cell(s) for which, when the CLTM procedure was performed, a Layer 3 measurement was available and an execution condition based on the Layer 3 measurement was not fulfilled; andCLTM candidate cell(s) for which, when the CLTM procedure was performed, a Layer 1 measurement was available and an execution condition based on the Layer 1 measurement was not fulfilled.
9. The method of claim 7 or 8, wherein the information related to the recovery procedure comprises an indication of time elapsed between attempting the CLTM procedure and attempting or performing the recovery procedure.
10. The method of any one of claims 7-9, wherein the information related to a radio link failure after the CLTM procedure was performed comprises an indication of time elapsed between performing the CLTM procedure and the radio link failure (between the wireless device and the first CLTM candidate cell).
11. The method of any preceding claim, wherein the CLTM procedure was attempted or performed by the wireless device after one or more of:a L1 / L2 triggered mobility, LTM, procedure towards a first LTM candidate cell for the wireless device failed;a CLTM procedure towards another CLTM candidate cell failed; anda CLTM procedure towards another CLTM candidate cell succeeded.
12. The method of claim 11, wherein the first LTM candidate cell is the same as the first CLTM candidate cell.
13. The method of any preceding claim, wherein the CLTM procedure was attempted or performed by the wireless device before one or more of:a re-establishment procedure was attempted or performed towards the first CLTM candidate cell or another CLTM candidate cell;a re-establishment procedure was attempted or performed towards a second a L1 / L2 triggered mobility, LTM, candidate cell for the wireless device;a recovery procedure was attempted or performed using a CLTM candidate cell configuration;a recovery procedure was attempted or performed using a L1 / L2 triggered mobility, LTM, candidate cell configuration; anda recovery procedure was attempted or performed using a conditional handover configuration.
14. The method of any preceding claim, wherein the information is sent after detecting a radio link failure (between the wireless device and a current cell of the wireless device).
15. The method of claim 14, wherein the information comprises one or more of:information related to an execution condition for performing the CLTM procedure towards the first CLTM candidate cell based on an evaluation of the execution condition when the radio link failure was detected;an L1 measurement result for the first CLTM candidate cell when the radio link failure was detected;an L3 measurement result for the first CLTM candidate cell when the radio link failure was detected;information related to a time to trigger timer for the CLTM procedure;an identity of a CLTM candidate cell configuration corresponding to the first CLTM candidate cell;an identity of a LTM candidate cell configuration corresponding to the first CLTM candidate cell; andan identifier for the first CLTM candidate cell.
16. The method of any preceding claim, wherein the information is comprised in one or more of: a Self-Organizing Network, SON, report; a Random Access report; a Radio Link Failure report; a Successful Handover report; and a Successful Primary Secondary Cell Report.
17. The method of any preceding claim, wherein the information relates to a CLTM procedure for any one of: a Master Cell Group, MCG; a Secondary Cell Group, SCG; an MCG associated with a SCG; and a MCG and a SCG.
18. The method of any preceding claim, wherein the method further comprises, prior to sending the information, receiving (302; 304) one or both of:a configuration for information to be logged and / or reported relating to the CLTM procedure towards the first CLTM candidate cell; anda request for information relating to the CLTM procedure towards the first CLTM candidate cell.
19. The method of claim 18, wherein one or both of the configuration for information and the request for information are received from the RAN node.
20. The method of claim 18, wherein one of the configuration for information and the request for information is received from the RAN node and the other one of the configuration for information and the request for information is received from a different RAN node.
21. A method performed by a radio access network, RAN, node in a communication network, the method comprising one or more of:sending (402), to a wireless device, a configuration for information to be logged and / or reported relating to a Conditional L1 / L2 triggered mobility, CLTM, procedure towards a first CLTM candidate cell;sending (404), to the wireless device, a request for information relating to the CLTM procedure towards the first CLTM candidate cell; andreceiving (406), from a wireless device, information relating to the CLTM procedure towards the first CLTM candidate cell.
22. The method of claim 21, wherein the CLTM procedure is:a CLTM procedure that was attempted or performed by the wireless device towards the first CLTM candidate cell; and / ora CLTM procedure that the wireless device is configured to attempt or perform towards the first CLTM candidate cell.
23. The method of claim 21 or 22, wherein the CLTM procedure is one or more of:a CLTM procedure that failed;a CLTM procedure that succeeded;a CLTM procedure that satisfies a nearly failed criterion;a RACH-less CLTM procedure;a RACH-based CLTM procedure;a CLTM procedure triggered by fulfilment of one or more execution conditions;a CLTM procedure that failed and was followed by a recovery procedure that succeeded; a CLTM procedure that failed and was followed by a recovery procedure that failed; a CLTM procedure that succeeded and was followed by a radio link failure within a first time interval after the CLTM procedure;a CLTM procedure that satisfied a nearly failed criterion and was followed by a radio link failure within a second time interval after the CLTM procedure.
24. The method of claim 23, wherein a CLTM procedure that satisfies a nearly failed criterion comprises a CLTM procedure having, when the CLTM procedure was performed, a time alignment timer value that is above a nearly failed threshold value.
25. The method of claim 23 or 24, wherein the one or more execution conditions are based on one or both of: a Layer 1 measurement of the first CLTM candidate cell; and a Layer 3 measurement of the first CLTM candidate cell.
26. The method of any one of claims 21-25, wherein the first CLTM candidate cell is one or more of:a CLTM candidate cell for which, when the CLTM procedure was attempted or performed, there were no Layer 1 measurements available;a CLTM candidate cell for which, when the CLTM procedure was attempted or performed, there were no Layer 3 measurements available;a CLTM candidate cell for which, when the CLTM procedure was attempted or performed, one or more Layer 1 measurements were available and one or more execution conditions based on the one or more Layer 1 measurements were not fulfilled;a CLTM candidate cell for which, when the CLTM procedure was attempted or performed,one or more Layer 3 measurements were available and one or more execution conditions based on the one or more Layer 3 measurements were not fulfilled.
27. The method of any one of claims 21-26, wherein the information comprises one or more of:an indication that the CLTM procedure failed;an indication that the CLTM procedure succeeded;an identity of the first CLTM candidate cell;an identity of a CLTM candidate cell configuration for which the CLTM procedure failed; an identity of a LTM candidate cell configuration for which an LTM procedure failed; an identity of one or more CLTM candidate cells other than the first CLTM candidate cell; an identity of one or more LTM candidate cells other than the first CLTM candidate cell; a Layer 1 measurement result for the first CLTM candidate cell;a Layer 3 measurement result for the first CLTM candidate cell;a Layer 1 measurement result for one or more CLTM candidate cells other than the first CLTM candidate cell;a Layer 3 measurement result for one or more CLTM candidate cells other than the first CLTM candidate cell;a Layer 1 measurement configuration for the first CLTM candidate cell;a Layer 3 measurement configuration for the first CLTM candidate cell;information related to a radio link failure after the CLTM procedure was performed; information related to a recovery procedure attempted or performed after the CLTM procedure failed;an indication that the CLTM procedure is the most recent mobility procedure attempted or performed by the wireless device;information about an execution condition for attempting or performing the CLTM procedure (in accordance with a CLTM candidate cell configuration for the first CLTM candidate cell); and a value of a time alignment timer when the CLTM procedure was performed by the wireless device.
28. The method of claim 27, wherein the one or more other CLTM candidate cells are one or more of:CLTM candidate cell(s) for which, when the CLTM procedure was performed, no Layer 1 measurement was available;CLTM candidate cell(s) for which, when the CLTM procedure was performed, no Layer 3 measurement was available;CLTM candidate cell(s) for which, when the CLTM procedure was performed, a Layer 3 measurement was available and an execution condition based on the Layer 3 measurement was not fulfilled; andCLTM candidate cell(s) for which, when the CLTM procedure was performed, a Layer 1 measurement was available and an execution condition based on the Layer 1 measurement was not fulfilled.
29. The method of claim 27 or 28, wherein the information related to a recovery procedure comprises an indication of time elapsed between attempting the CLTM procedure and attempting or performing the recovery procedure.
30. The method of any one of claims 27-29, wherein the information related to a radio link failure after the CLTM procedure was performed comprises an indication of time elapsed between performing the CLTM procedure and the radio link failure (between the wireless device and the first CLTM candidate cell).
31. The method of any one of claims 21-30, wherein the CLTM procedure was attempted or performed by the wireless device after one or more of:a L1 / L2 triggered mobility, LTM, procedure towards a first LTM candidate cell for the wireless device failed;a CLTM procedure towards another CLTM candidate cell failed; anda CLTM procedure towards another CLTM candidate cell succeeded.
32. The method of claim 31, wherein the first LTM candidate cell is the same as the first CLTM candidate cell.
33. The method of any one of claims 21-32, wherein the CLTM procedure was attempted or performed by the wireless device before one or more of:a re-establishment procedure was attempted or performed towards the first CLTM candidate cell or another CLTM candidate cell;a re-establishment procedure was attempted or performed towards a second a L1 / L2 triggered mobility, LTM, candidate cell for the wireless device;a recovery procedure was attempted or performed using a CLTM candidate cell configuration;a recovery procedure was attempted or performed using a L1 / L2 triggered mobility, LTM,candidate cell configuration; anda recovery procedure was attempted or performed using a conditional handover configuration.
34. The method of any one of claims 21-33, wherein the information is received after detection of a radio link failure (between the wireless device and a current cell of the wireless device).
35. The method of claim 34, wherein the information comprises one or more of:information related to an execution condition for performing the CLTM procedure towards the first CLTM candidate cell based on an evaluation of the execution condition when the radio link failure was detected;an L1 measurement result for the first CLTM candidate cell when the radio link failure was detected;an L3 measurement result for the first CLTM candidate cell when the radio link failure was detected;information related to a time to trigger timer for the CLTM procedure;an identity of a CLTM candidate cell configuration corresponding to the first CLTM candidate cell;an identity of a LTM candidate cell configuration corresponding to the first CLTM candidate cell; andan identifier for the first CLTM candidate cell.
36. The method of any one of claims 21-35, wherein the information is comprised in one or more of: a Self-Organizing Network, SON, report; a Random Access report; a Radio Link Failure report; a Successful Handover report; and a Successful Primary Secondary Cell Report.
37. The method of any one of claims 21-36, wherein the information relates to a CLTM procedure for any one of: a Master Cell Group, MCG; a Secondary Cell Group, SCG; an MCG associated with a SCG; and a MCG and a SCG.
38. The method of any one of claims 21-37, wherein the method further comprises:sending the received information, part of the received information, or information derived from the received information to another node in the communication network.
39. The method of claim 38, wherein the information derived from the received information comprises a classification for an outcome of the CLTM procedure.
40. The method of any one of claims 21-39, wherein the configuration for information and / or the request for information indicate one or both of:one or more types of information to be logged and / or reported relating to the CLTM procedure; andone or more scenarios in which information is to be logged and / or reported relating to the CLTM procedure.
41. The method of any one of claims 21-40, wherein the method further comprises:performing optimisation and / or modification of CLTM procedures based on the received information.
42. The method of claim 41, wherein optimisation and / or modification of CLTM procedures comprises one or both of:modifying a CLTM candidate cell configuration for the first CLTM candidate cell; and modifying execution conditions comprised in the CLTM candidate cell configuration for the first CLTM candidate cell.
43. A computer program product comprising a computer readable medium having computer readable code embodied therein, the computer readable code being configured such that, on execution by a suitable computer or processor, the computer or processor is caused to perform the method of any of claims 1-42.
44. A wireless device configured to perform the method of any of claims 1-20.
45. A wireless device comprising a processor and a memory, said memory containing instructions executable by said processor whereby said wireless device is operative to perform the method of any of claims 1-20.
46. A radio access network, RAN, node, configured to perform the method of any of claims 21-42.
47. A radio access network, RAN, node comprising a processor and a memory, said memory containing instructions executable by said processor whereby said RAN node is operative to perform the method of any of claims 21-42.
