Information for conditional layer1 / layer 2 triggered mobility execution
By logging and reporting reasons for RACH-based or failed RACH-less CLTM cell switch executions, the network can optimize CLTM procedures, enhancing the success rate and reducing interruption times.
Patent Information
- Application Number
- PCT/SE2026/050283
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-08
- Filing Date
- 2026-04-28
- Publication Date
- 2026-11-12
AI Technical Summary
The existing network lacks information on why a UE performs RACH-based access during Conditional Layer 1/Layer 2 Triggered Mobility (CLTM), leading to potential RACH-less access failures and increased interruption times due to invalid Timing Advance (TA) values or lack of uplink resources.
A wireless device logs and reports information to the network about the reasons for RACH-based or failed RACH-less CLTM cell switch executions, including TA validity and resource availability, enabling the network to optimize CLTM procedures and reduce interruption times.
The network can improve the success rate of RACH-less CLTM cell switch executions by receiving UE-reported information, thereby decreasing interruption times and optimizing resource allocation.
Smart Images

Figure SE2026050283_12112026_PF_FP_ABST
Abstract
Description
[0001] Information for Conditional Layerl / Layer 2 Triggered Mobility execution
[0002] TECHNICAL FIELD
[0003] This disclosure relates to Conditional Layer 1 / Layer 2 Triggered Mobility (CLTM), and in particular to information for Random Access Channel (RACH)-based CLTM, or RACH-less 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 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] Both RACH-less and RACH-based access is supported for Conditional LTM (CLTM) cell switch execution. In order to perform a RACH-less access the UE needs to have a valid TA value for the candidate (target) cell and an uplink resource to perform the first uplink transmission to the candidate (target) cell in a RACH-less manner.
[0022] For conditional LTM, the UE can have a Timing Advance (TA) value through a network triggered UL synchronization procedure, by sending a Physical RACH (PRACH) preamble to the candidate cell, or through a UE autonomous UL pre-synchronization. For the network-triggered UL synchronization procedure there is, however, a difference compared to Rel-18 LTM in how the determined TA value is sent to the UE. In Rel-18 LTM it is sent in the LTM Cell Switch Command MAC CE that triggers the LTM cell switch. If the TA is included there the UE will then use it for a RACH-less access to the candidate (target) cell. For conditional LTM there is, however, no LTM Cell Switch Command MAC CE sent to the UE to trigger the cell switch to the candidate cell. This is instead triggered by fulfilment of the associated execution conditions in the UE.
[0023] It has therefore been agreed that the determined TA value is sent to the UE by the source / serving node when the TA value has been determined for the candidate cell and, if applicable, sent from the candidate node to the source / serving node. The TA value is then kept in the UE, which then keeps track of its validity using a timer (a kind of time alignment timer). At the time of CLTM cell switch execution, the UE then checks if it has (earlier) received a TA value for the candidate (target) cell towards which the cell switch is to be executed and whether that TA value is still valid. If not, i.e. if the UE does not have a valid TA value, the UE needs to perform a RACH-based access to the candidate (target) cell at the LTM cell switch.
[0024] As an option, if configured by the network, the UE can use a UE autonomous UL presynchronization procedure to acquire a valid TA value.Self Organising Networks (SON) reports for (Rel-18) L1 / L2 Triggered Mobility (CLTM)
[0025] 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).
[0026] 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):
[0027] > If available, log the L1 measurements for serving cell, target cell and other LTM candidate cells in RLF report, upon RLF or mobility failure.
[0028] > Log the LTM cell ID upon performing recovery an LTM candidate cell, details TBD e.g. which field.
[0029] > Extend lastHO-Type in RLF-Report to indicate the LTM cell switch as last executed mobility procedure.
[0030] > 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.
[0031] > 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.
[0032] > We will not define and log timeSinceLTM-Reconfig (like timeSinceCHO-Reconfig) within RLF-report and SHR in LTM failure and near failure cases.
[0033] > We will not log interruption time in SON reports (e.g. SHR) for LTM.
[0034] > 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, TBD if explicit / implicit.
[0035] 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:
[0036] > 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.
[0037] > 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.
[0038] > For LTM-related RA reports, the UE sets the cellld to the CGI if available, otherwisesets it based on Itm-CandidatePCI and ssb-Frequency in corresponding LTM- Candidate.
[0039] > At RLF and reconfiguration with sync failure:
[0040] 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).
[0041] 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.
[0042] > 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.
[0043] SUMMARY
[0044] There currently exist certain challenge(s). One limitation with the existing or published technology is that the network does not receive from 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).
[0045] One such aspect concerns that in order for a UE to execute a RACH-less access at a conditional LTM cell switch execution, it needs to have e.g.:
[0046] • a valid Timing Advance (TA) value for the target cell (to be used for the first uplink transmission in the target cell at the cell switch execution); and
[0047] • allocated uplink (UL) resources to use in the target cell (and / or for the beam that is to be used in the target cell at the CLTM cell switch execution) for the RACH-less access, such as Physical Uplink Shared Channel (PUSCH) resources, e.g. preconfigured UL grants, or Scheduling Request (SR) resources.
[0048] The UL resources to be used for a RACH-less access are provided to the UE prior to the actual CLTM cell switch execution, e.g. as part of the CLTM candidate cell configuration. These resources can be preconfigured UL grants, e.g. as so-called Configured Grants using the cg-LTM-Configuration field, and the UE may then be configured with such UL grants only for a subset of the beams of the CLTM candidate cell. To configure UL grants for candidate cell(s) can sometimes be costly for the network considering that those resources are not used by the UE until the corresponding CLTM cell switch executions take place. This is triggered by fulfilment of the associated execution conditions, and it is not known by the network when this will happen (ifat all). The resources can then typically not be used for any other purpose, which means that they are often “wasted” resources. A network may then decide to only (pre-)configure such UL grants for a candidate CLTM cell in a subset of the beams in the cell.
[0049] At the CLTM cell switch execution there may be different aspects that the UE needs to take into account when deciding which beam to select / use for the first transmission in the candidate (target) cell. As an example, the signal strength and / or quality of the different beams would typically need to be taken into account. Depending on the beam that the UE then determines to use at the actual CLTM cell switch execution, the UE might then execute the CLTM cell switch execution towards a beam for which the UE has a resource for RACH-less uplink transmission or towards a beam for which the UE does not have a resource for RACH-less uplink transmission. In the latter case the UE would then need to instead perform a RACH-based access towards the candidate (target) cell as part of the CLTM cell switch execution, even if the UE has a valid TA value for the candidate (target) cell.
[0050] If the UE is not able to execute a RACH-less CLTM cell switch execution (and instead executes a RACH-based CLTM cell switch execution), it would be very useful for the network node, e.g. the candidate (target)) gNB-DU, candidate (target)) gNB-CU, source gNB-DU, or source gNB-CU, to get information about the reason why. Otherwise, it may not be able to determine how it can avoid the issues that are preventing the use of a RACH-less execution, and thus leads to a longer interruption time at the CLTM cell switch execution.
[0051] Since the source / serving network node (e.g. the Serving-DU (S-DU)), which triggers the early UL synchronization procedure (i.e. the TA acquisition for the CLTM candidate cell(s)), is not in control of when the corresponding CLTM cell switch procedure actually takes place, there is a risk that the UE does not have a valid TA value for the candidate (target) cell at the time of the CLTM cell switch execution. This could be due to, e.g.:
[0052] - the CLTM cell switch execution is triggered before the UE has got any TA value for the corresponding candidate (target) cell. For example, this could be due to the source / serving node not yet initiating the early UL synchronization (TA acquisition) procedure when the CLTM cell switch execution is triggered, or due to the early UL synchronization procedure being initiated but the UE has not yet received the TA value from the network (e.g. from the source / serving node);
[0053] - the UE has received a corresponding TA value for the candidate (target) cell, but it is no longer valid at the time of the CLTM cell switch execution, e.g. due to the associated timer (e.g. a time alignment timer) having expired;
[0054] - the UE autonomously determines the TA value for the candidate (target) cell, but it is no longer valid at the time of the CLTM cell switch execution.The lack of a valid TA value for the candidate (target) cell at the time of the CLTM cell switch execution could thus be due to the serving / source network node (e.g. S-Dll) initiating the early UL synchronization (TA acquisition) procedure too late (including the step to provide the TA value to the UE), or initiating it too early and / or without any re-acquisition of the TA value in time. Without any information about this from the UEs that needed to execute a RACH-based CLTM cell switch execution, it will however be difficult for the network to overcome these issues.
[0055] Another problem (or risk) can be that although the UE managed to initiate a RACH-less CLTM cell switch execution, the conditions the UE checked to determine whether RACH-less CLTM cell switch was possible were about to not be satisfied. As of now, the network is not provided with information to reduce this risk.
[0056] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. In particular, this disclosure provides methods for a UE (or more generally a wireless device) to log and / or report to the network (e.g. based on a network configuration) information about why it has executed RACH-based access at execution of a conditional LTM (CLTM) cell switch execution. Based on this information that is logged by the UE and reported to the network, the network can make changes to its configuration and / or handling of the CLTM procedures in order to avoid, or try to avoid, the reasons that led to a RACH-based access instead of a RACH-less access.
[0057] This disclosure also includes methods for a UE to log and / or report to the network information about a failed RACH-less CLTM cell switch execution, e.g. the reason why it failed and information about available valid Timing Advance (TA) value(s) for the target cell and / or for other CLTM candidate cells. Based on this information that is logged by the UE and reported to the network, the network can make changes to its configuration and / or handling of the CLTM procedures in order to avoid, or try to avoid, the reasons that led to the failure of the RACH-less access.
[0058] Certain embodiments may provide one or more of the following technical advantage(s). With the proposed solution(s), the network can perform one or more optimisations due to information received from UEs in relation to Conditional LTM (CLTM), such as to enable that RACH-less accesses can be utilised more often at execution of a CLTM cell switch. This will typically decrease the interruption times at those future CLTM cell switch executions compared to using a RACH-based access.
[0059] The network can also determine the reasons why RACH-less CLTM cell switch executions fail and utilise this to improve the performance (e.g. success rate) of the CLTM cell switch executions.According to a first aspect, there is provided a method performed by a wireless device. The method comprises: sending, to a Radio Access Network, RAN, node in a communication network, information relating to a Conditional L1 / L2 triggered mobility, CLTM, procedure that was attempted or performed by the wireless device. The information is one or more of: a reason for performing a Random Access-, RA-, based CLTM procedure, and information relating to a success or failure of a RA-less CLTM procedure.
[0060] According to a second aspect, there is provided a method performed by a radio access network, RAN, node in a communication network. The method comprises one or more of: (i) sending, to a wireless device, a configuration for information to be logged and / or reported relating to a Conditional L1 / L2 triggered mobility, CLTM, procedure to be attempted or performed by the wireless device; (ii) sending, to the wireless device, a request for information relating to the CLTM procedure attempted or performed by the wireless device; and (iii) receiving, from the wireless device, information relating to the CLTM procedure that was attempted or performed by the wireless device. The information is one or more of: a reason for performing a Random Access-, RA-, based CLTM procedure; and information relating to a success or failure of a RA-less CLTM procedure.
[0061] 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.
[0062] 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.
[0063] 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.
[0064] 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.
[0065] 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.
[0066] BRIEF DESCRIPTION OF THE DRAWINGSSome of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings, in which:
[0067] Fig. 1 is a signalling diagram illustrating the LTM signalling procedure;
[0068] Fig. 2 is a signalling diagram illustrating signalling according to embodiments of the disclosure;
[0069] Fig. 3 is a flow chart illustrating a method performed by a wireless device in accordance with some embodiments;
[0070] Fig. 4 is a flow chart illustrating a method performed by a RAN node in accordance with some embodiments;
[0071] Fig. 5 shows an example of a communication system in accordance with some embodiments;
[0072] Fig. 6 shows a wireless device in accordance with some embodiments;
[0073] Fig. 7 shows a radio access network (RAN) node in accordance with some embodiments; and
[0074] Fig. 8 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.
[0075] DETAILED DESCRIPTION
[0076] 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.
[0077] The terms “UE”, “User Equipment” and “wireless device” are used interchangeably herein. 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), 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.
[0078] 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, a RAN Area Function (RANAF) ID, an O-gNB ID, an O-DU ID, an O-CU ID, an O-CU-CP ID, an O-CU-UP-ID, a 6G node ID or similar.
[0079] 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.
[0080] This disclosure relates to “CLTM cell switch procedures”, which are also interchangeablyreferred to herein as “CLTM procedures” and “CLTM cell switch execution”. A “RACH-less CLTM cell switch procedure” or “RACH-less CLTM” or “RACH-less Conditional LTM” or “RACH-less Conditional Cell Switch” is a CLTM cell switch procedure in which the UE does not need to perform random access (RA) at the CLTM cell switch execution 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” and a “RA-less CLTM procedure”. . A “RACH-based CLTM cell switch procedure” is a CLTM cell switch procedure in which the UE does need to perform random access (RA) at the CLTM cell switch execution 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”.
[0081] This disclosure discusses UL resources in a “candidate target cell” (or “target cell” or “candidate cell”) for a CLTM cell switch execution. Such UL resources can include, but are not limited to, PUSCH resources that are used for a RACH-less access.
[0082] According to some methods, a UE logs and / or reports information in relation to RACH-based CLTM cell switch execution or RACH-less CLTM cell switch execution. This disclosure details various information and types of information that the UE can log and / or report in different scenarios, for example in case a RACH-based CLTM cell switch execution is executed, and / or in case a RACH-less CLTM cell switch is attempted or fails.
[0083] Exemplary signalling according to embodiments of this disclosure is shown in Fig. 2. Fig.
[0084] 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 RACH-based and / or RACH-less CLTM cell switch execution according to any of the embodiments in this disclosure. Signal 211 may also configure the UE 201 to send the information relating to RACH-based and / or RACH-less CLTM cell switch execution to the RAN node 202, or, alternatively the RAN node 202 can send a separate (optional) signal 212 that requests the UE to send the information to the RAN node 202.
[0085] The UE201 sends information relating to RACH-based and / or RACH-less CLTM cell switch execution according to any of the embodiments in this disclosure to the RAN node 202, as shown by signal 213.
[0086] The information that a UE can log and / or report in relation to RACH-based CLTM cell switch execution and / or RACH-less CLTM cell switch execution can collectively be regarded as “information related to RACH-based and / or RACH-less CLTM cell switch execution”. For instance, according to the information a UE can log and report described in the embodiments below, information related to RACH-based and / or RACH-less CLTM cell switch execution cancomprise:
[0087] for execution of a RACH-based CLTM cell switch, one or more of:
[0088] the reason why a UE has executed a RACH-based CLTM cell switch procedure; an indication that RACH-based CLTM cell switch execution was performed due to the TA value being too old / the TA value being invalid);
[0089] an indication that RACH-based CLTM cell switch execution was performed due to lack of available UL resource for the target beam and / or cell;
[0090] an indication of the percentage of the value of a Time Alignment Timer (TAT) that has / had elapsed when the UE initiated RACH-based CLTM cell switch execution;
[0091] an indication of whether the percentage of the value of a Time Alignment Timer (TAT) that has / had elapsed when the UE initiated RACH-based CLTM cell switch execution exceeded or equalled a threshold;
[0092] an indication of an amount of time remaining for a TAT for a RA-less CLTM procedure;
[0093] an indication of whether an amount of time remaining for a TAT for a RA-less CLTM procedure equals or is less than a threshold;
[0094] a list of CLTM candidate identifier(s) for which the TA value is still valid; an indication that RACH-based CLTM was attempted because the beam selected for the CLTM cell switch was not among the beams for which the PUSCH resources were configured; and / or
[0095] an indication that the UE executed / attempted RACH-based cell switch execution (CLTM or normal LTM) due to a RACH-less CLTM cell switch execution having failed;
[0096] for failure of a RACH-less CLTM cell switch, one or more of:
[0097] RACH-less CLTM cell switch execution fails due to a timer timeout (e.g. T304 timeout);
[0098] information about the remaining validity of the TA value for the candidate (target) cell when the CLTM cell switch execution was attempted / initiated;
[0099] a percentage of a time alignment timer that has or had elapsed when the wireless device attempted or performed the RA-less CLTM procedure;
[0100] an indication that a percentage of a time alignment timer that has or had elapsed when the wireless device attempted or performed the RA-less CLTM procedure equals or exceeds a threshold;an indication of an amount of time remaining for a time alignment timer for the RA-less CLTM procedure;
[0101] an indication of whether an amount of time remaining for a time alignment timer for the RA-less CLTM procedure equals or is less than a threshold; and / or if the validity of the TA value was extended.
[0102] Reason for RACH-based CLTM cell switch execution and / or for failure of RACH-less CLTM cell switch execution
[0103] The execution of a conditional LTM cell switch procedure is triggered by the fulfilment of execution conditions, which are associated to the CLTM candidate cell, and thus evaluated by the UE. The CLTM cell switch execution can either be performed as “RACH-less” or “RACH-based”, where RACH-less execution can achieve a shorter interruption for the cell switch.
[0104] A RACH-less CLTM cell switch can only be performed by the UE if it has a valid Timing Advance (TA) value for the target cell of the cell switch procedure, and if the UE has resources for performing a RACH-less procedure (e.g. the UE has pre-configured uplink PUSCH resources, so-called Configured Grants, or Scheduling Request, SR, resources available for the target cell).
[0105] The PUSCH resources, such as the Configured Grant resources, may only be valid in a subset of the beams of a CLTM candidate cell (e.g. the target cell of the CLTM cell switch execution). If the UE performs the CLTM cell switch procedure towards a beam for which the UE does not have any PUSCH resources available, it may therefore not be able to perform a RACH-less procedure, and instead the UE needs to perform a RACH-based cell switch execution, even if the UE has a valid TA value for the target cell. In some cases, the PUSCH resources for the target cell and / or target beam(s) may have a limited validity in time. If PUSCH resources are not available for the UE for the target beam at the time of execution of the CLTM cell switch, then the UE would need to execute a RACH-based cell switch execution.
[0106] Likewise, if the UE does not have a valid TA value for the target cell at the time of the CLTM cell switch execution, the UE has to perform a RACH-based cell switch execution, even if the UE has been configured with (and thus has available) PUSCH resources for the beam that is used for the cell switch execution.
[0107] As noted in this disclosure, in order for the network to (better) enable RACH-less execution for CLTM cell switch procedures, enabling a shorter interruption time, it is useful for the network to receive, from a UE, information about the reason why the UE has performed a RACH-based execution (and thus not a RACH-less one).
[0108] In some embodiments, which can be combined with other embodiments described herein, in relation to a successful, nearly failed or failed CLTM cell switch execution, the UE thereforelogs and reports in a UE report information about the reason why it has executed a RACH-based CLTM cell switch procedure. The information can include one or more of the following indications:
[0109] • an indication that RACH-based CLTM cell switch execution was performed due to the TA value being too old, i.e. that no RACH-less execution was performed due to the TA value for the target cell that the UE had was too old (invalid). In one example, the UE has received (from the network) a TA value for the target cell, but it has become too old (invalid) at the point in time of the CLTM cell switch execution (i.e. when the associated execution conditions were fulfilled). This can correspond to a validity timer (e.g. a TimeAlignmentTimer (TAT)) having expired for the target cell.
[0110] o The UE may also log and report information about how long ago the TA value, that the UE had for the candidate (target) cell, expired (became too old).
[0111] • an indication of the percentage of the value of TimeAlignmentTimer (TAT) elapsed when the UE initiated RACH-based CLTM cell switch execution. This can help the network to know that RACH-less CLTM cell switch was still possible from the point of view of the UE having a valid TA value, but some other reasons led to the RACH-based CLTM cell switch (e.g. the UE did not have any PUSCH resources available).
[0112] • an indication of an amount of time left from the time duration expressed by the TAT value used by the UE. If the network (e.g. the source DU) knows or can deduce the TAT value at the UE, this can help the network to know that RACH-less CLTM cell switch was still possible from the point of view of the UE having a valid TA value, but some other reasons led to the RACH-based CLTM cell switch (e.g. the UE did not have PUSCH resources available).
[0113] • corresponding indication(s) that RACH-based CLTM was attempted due to the TA value being too old / expired / invalid (but where the execution, in some alternatives, failed).
[0114] • information about CLTM candidate cells for which the TA value is still valid. In this case the indication can be a list of CLTM candidate identifier(s) such that the TA value(s) for such candidate(s) is(are) still valid. Here “still valid” means that the time alignment timer of such TA value(s) is(are) still running or did not expire.
[0115] • an indication that RACH-based CLTM cell switch execution was performed due to lack of available UL resource(s) for the target beam and / or cell (for RACH-less execution) at the time when the CLTM cell switch execution was performed, e.g. that no RACH-less execution was performed due to the UE not having any PUSCH resource, e.g. Configured Grant, and / or SR available for the target beam and / or cell. In some examples, the UE has a valid TA value for the target cell at the point in time of the CLTM cell switch execution.
[0116] o The UE may have resources for uplink transmission (for a RACH-less execution)to the target beam of the candidate (target) cell but it cannot use the UL resources due to another condition. The UE may then log and report information about this, including, for example, the reason why the UE could not use the corresponding resource to perform the RACH-less execution. Such condition could be, for example, that the UE can only perform RACH-less access to a beam where the candidate (target) cell / node is prepared to receive it. In some cases, the network node may not be able to receive the uplink transmission from all the directions (corresponding to different beams used by the UE). For example, the UE may only be allowed to perform RACH-less access if the beam to use at the CLTM cell switch execution is one for which the UE has been indicated to perform a TCI state activation (e.g. for an early downlink synchronization). The UE may only be allowed to perform RACH-less access if the beam to use at the CLTM cell switch execution is the same as that used by the UE (or indicated by the network to use) for transmission of the PRACH preamble to the candidate (target) cell during early uplink synchronization.
[0117] • corresponding indication(s) that RACH-based CLTM was attempted due to lack of PUSCH resources, e.g. Configured Grant, or SR (but where the execution of the RACH-based CLTM procedure, in some cases, failed).
[0118] • an indication that RACH-based CLTM was attempted because the beam selected for the CLTM cell switch was not among the beams for which the PUSCH resources were configured.
[0119] • an indication(s) that the UE has not (yet) received (or estimated) any TA value for the target cell at the point in time of the attempted or successful CLTM cell switch execution. This may correspond to the early UL synchronization being initiated, by the network (e.g. the source node) too close in time to the fulfilment of the execution conditions.
[0120] o The UE may also log and report information about whether an early UL synchronization (TA acquisition) procedure has been initiated towards the candidate (target) cell, but not completed. This can include, for example, an indication that the UE has received an indication from the source / serving cell / node to perform the procedure (e.g. to transmit a PRACH preamble to the candidate target cell) but has not yet received the corresponding TA value from the network (e.g. from the source / serving cell / node). The information can also include indication(s) whether the UE has transmitted the corresponding PRACH preamble to the candidate (target) cell.
[0121] o The UE may also or alternatively log and report information to the network that theUE has transmitted an indication / information to the source / serving cell / node that an early UL synchronization (TA acquisition) procedure should be initiated. This can consist of a specific event, e.g. based on a measurement report event configured by the network.
[0122] o The UE may also or alternatively log that it has successfully estimated the TA value, but this (e.g. the validity of that estimated TA value) has expired before the CLTM cell switch procedure has been triggered.
[0123] o The UE may also or alternatively log how many times it attempted (e.g. if so configured by the network) to estimate the TA value.
[0124] • an indication(s) that the UE has neither a valid TA value nor a valid PUSCH resource for the target cell and / or beam at the time of the CLTM cell switch execution.
[0125] Reporting when RACH-based CLTM cell switch procedure performed - As noted above, the UE may be configured to log and / or report information if it has performed a RACH-based CLTM cell switch execution. The UE may be configured to log and / or report information if it has performed a RACH-based CLTM cell switch execution, even if it has some information or resources available for performing a RACH-less execution, e.g. if the UE has a valid TA value for the target cell, or that it has PUSCH resources available for the target beam and / or cell (for RACH-less execution).
[0126] The report sent by the UE to the network may be a Successful Handover Report (SHR). The configuration for SHR (e.g. in SuccessHO-Config) may include an indication that the UE shall generate a SHR in case of a RACH-based CLTM cell switch execution, possibly related to the UE having a valid TA value for the target cell or a valid PUSCH resource for the target beam and / or cell at the time of cell switch execution. The SHR-Cause value (included in the corresponding SuccessHO-Report reported by the UE) may include a value that is used to indicate that the UE has executed a RACH-based CLTM cell switch procedure.
[0127] Reporting when RACH-less CLTM cell switch procedure fails - As noted above, a UE may attempt to execute a RACH-less CLTM cell switch procedure, but the procedure fails, in which case the UE logs and reports, e.g. in a UE report, information about the failed RACH-less CLTM cell switch procedure. The information logged and reported by the UE can include one or more of the following indications:
[0128] • the reason that the procedure failed, e.g. a timer expired, T304 timeout;
[0129] • an indication of the number of times that the UE has attempted an uplink transmission in the candidate (target) cell and / or the types of transmissions (e.g. whether it was using configured UL grants, PUSCH resources, or Scheduling Request transmissions);• information about the time since the TA value for the candidate (target) cell was received, information about the time since the corresponding PRACH preamble was transmitted to the candidate (target) cell, and / or information about the remaining validity of the TA value for the candidate (target) cell when the CLTM cell switch execution was attempted / initiated;
[0130] • information (e.g. in the form of a percentage) about the remaining validity of the TA value for the candidate (target) cell relative to the Time Alignment Timer associated with the TA value when the CLTM cell switch execution was attempted and / or initiated;
[0131] • a percentage of a TAT that has or had elapsed when the wireless device attempted or performed the RACH-less CLTM procedure;
[0132] • an indication that a percentage of a TAT that has or had elapsed when the wireless device attempted or performed the RACH-less CLTM procedure equals or exceeds a threshold;
[0133] • an indication of an amount of time remaining for a TAT for the RACH-less CLTM procedure;
[0134] • an indication of whether an amount of time remaining for a TAT for the RA-less CLTM procedure equals or is less than a threshold;
[0135] • information relating to whether the validity of the TA value was extended by, but not limited to, any of:
[0136] o methods involving comparing the Reference Signal Received Power (RSRP) of the candidate at the time of receiving the TA value and the time of using the TA value;
[0137] o using UE based TA estimation procedures; and
[0138] o as instructed by the network, e.g. by issuing a new Physical Downlink Control Channel (PDCCH) Order or any other methods.
[0139] • information about which CLTM candidate cells the TA value is still valid for. In this case the indication can be a list of CLTM candidate identifier(s) such that the TA value(s) for such candidate(s) is(are) still valid. Here “still valid” can mean that the time alignment timer of such TA value(s) is(are) still running or did not expire; and
[0140] • information about which beams had UL resources configured.
[0141] Reporting when RACH-based CLTM cell switch procedure performed after failure of RACH-less CLTM cell switch procedure - As noted above, the UE may log and report, e.g. in a UE report, information / an indication that the UE has executed / attempted a RACH-based cell switch execution (CLTM or normal LTM) as a result of a RACH-less CLTM cell switch execution having failed.The UE may include information about the target cell for the RACH-based cell switch execution, for example information about the target cell for the RACH-based cell switch execution relative to the target cell for the failed RACH-less cell switch execution. For example, the information may indicate that the RACH-based cell switch execution was performed to the same cell as the target for the RACH-less CLTM cell switch execution (that failed). Alternatively, the information may indicate that the RACH-based cell switch execution was performed to a different cell than the target for the failed RACH-less CLTM cell switch execution.
[0142] In some embodiments, the RACH-based cell switch procedure is a recovery procedure to a cell that is performed after a cell selection while timer T311 has been performed, where the UE applies a CLTM (or LTM) candidate cell configuration for the cell that was then selected.
[0143] The UE may also or alternatively include some information related to a (possible) TA acquisition procedure and / or CLTM cell switch execution procedure, such as:
[0144] • the radio conditions at the time the PRACH preamble was sent to the candidate (target) cell for the TA acquisition;
[0145] • the time that the PRACH preamble was sent to the candidate (target) cell for the TA acquisition;
[0146] • the beam (e.g. SSB or TCI state) that was used for the TA acquisition;
[0147] • the time between the PRACH preamble being sent to the candidate (target) cell for the TA acquisition and the CLTM cell switch execution to the candidate (target) cell; and
[0148] • information regarding whether the TA acquisition was performed towards a different cell, e.g. another candidate cell, and where the TA value for the candidate target cell was based on that procedure to another cell.
[0149] In the above embodiments where the UE reports after failure of a RACH-less CLTM cell switch procedure, the UE may have attempted to execute the RACH-less CLTM cell switch execution due to a radio link failure in the serving cell. In these embodiments, when the procedure fails the UE then logs and reports, e.g. in a UE report, information about the failed RACH-less CLTM cell switch execution. The information may include one or more of the following indications:
[0150] • information about the radio link failure in the serving cell;
[0151] • the reason for the failed procedure;
[0152] • an indication about the number of times that the UE has attempted an uplink transmission in the candidate (target) cell and / or the types of transmissions (e.g. whether it was using configured UL grants, PUSCH resources, or Scheduling Request transmissions);
[0153] • information about the time since the TA value for the candidate (target) cell was received, since the corresponding PRACH preamble was transmitted to the candidate (target) celland / or about the remaining validity of the TA value for the candidate (target) cell when the CLTM cell switch execution was attempted / initiated.
[0154] In the above embodiments where the UE attempts to execute a RACH-less CLTM cell switch execution and the procedure fails, the UE can log and report, e.g. in a UE report, information about other TA values that it maintained for other cells. The information may include one or more of the following indications:
[0155] • the number of TA values maintained for other candidate cells;
[0156] • the cells the TA values are associated with;
[0157] • the remaining validity of the TA values; and
[0158] • if the TA values are associated with any Timing Advance Group (TAG) ID.
[0159] In some alternatives to the above embodiments, the UE can log and / or report to the network information about TAG IDs for one or more of the different candidate cells. This may include information that one or more candidate cells, including, e.g., the target cell of the CLTM cell switch execution, have the same TAG ID and / or use the same TA value, for example due to the cells being co-located. The information can include that the UE performed a TA acquisition and / or estimation towards a different candidate cell than the target cell of the CLTM cell switch execution. In some examples, the UE may include information that it used a TA value for the target cell of a CLTM cell switch execution based on a TA value that it had for a serving cell before the CLTM cell switch execution, e.g. a serving cell with the same TAG ID as the target cell.
[0160] Reason for almost failed RACH-less CLTM cell switch execution
[0161] In some embodiments of the techniques described herein, which can be combined with any one or more of the other embodiments in this disclosure, a UE can perform a CLTM cell switch execution that is successful, but that is considered to be “nearly failed”. In this case the UE can log and report, e.g. in a UE report, information indicating that the RACH-less CLTM cell switch procedure almost failed, and / or information indicating reason(s) why the RACH-less CLTM cell switch procedure almost failed. The information may include one or more of the following indications:
[0162] • an indication of the percentage of the TimeAlignmentTimer (TAT) that had elapsed when the UE initiated RACH-less CLTM cell switch execution. This can help the network to know that RACH-less CLTM cell switch was still possible from the point of view of the UE having a valid TA value, but it may be appropriate to tweak or change the TAT value (e.g. increase the TAT value, i.e. lengthen the TAT).
[0163] • an indication of an amount of time left from the time duration expressed by the TAT valueused by the UE. This information can support the network node (e.g. the candidate DU) that set the TAT value know that RACH-less CLTM cell switch was still possible from the point of view of the UE having a valid TA value, but it may be appropriate to tweak the TAT value a bit (e.g. make it a bit longer). If this information is made available at the source (serving) DU, the serving DU can forward the information to the other network node (e.g. the candidate DU) setting the TAT value.
[0164] Successful RACH-less CLTM cell switch execution
[0165] In some embodiments of the techniques described herein, which can be combined with any one or more of the other embodiments in this disclosure, the UE can attempt and successfully execute a RACH-less CLTM cell switch procedure, and the UE logs and reports, e.g. in a UE report, information about the successful RACH-less CLTM cell switch procedure. The information may include one or more of the following indications:
[0166] • information about which CLTM candidate cells the TA value is still valid for. The indication can be a list of CLTM candidate identifier(s) such that the TA value(s) for such candidate(s) is(are) still valid. Here “still valid” means that the time alignment timer of such TA value(s) is(are) still running or did not expire.
[0167] • information about which beams had UL resources configured;
[0168] • information about for which CLTM candidate cells the TA value is not valid. The indication can be a list of CLTM candidate identifiers such that the TA value(s) for such candidate(s) is(are) not valid. Here “not valid” means that the time alignment timer of such TA value(s) expired, or it was not acquired, or it was not estimated by the UE.
[0169] • information about which beams did not have UL resources configured;
[0170] • information about the percentage of remaining validity of the TA value for the candidate cell used as target for CLTM cell switch execution relative to the Time Alignment Timer associated with the TA value when the CLTM cell switch execution was attempted and / or initiated;
[0171] • information about the percentage of remaining validity of the TA value for a candidate cell not used as target for CLTM cell switch execution relative to the Time Alignment Timer associated with the TA value when the CLTM cell switch execution was attempted and / or initiated.
[0172] In some embodiments, the RACH-less CLTM cell switch execution can be attempted as a recovery after a failed LTM cell switch execution (towards the same cell used for LTM cell switch, or towards a different cell).Extension of the methods to dual connectivity
[0173] 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) wherein the UE is in dual connectivity scenarios.
[0174] In any of the earlier embodiments and scenarios, the UE may only log information related to successful / failed RACH-based or RACH-less CLTM cell switch procedure associated with the MCG cells (i.e. the information related to the CLTM candidate cells configured by the Master Node (MN)).
[0175] Alternatively, in any of the earlier embodiments and scenarios, the UE may only log information related to successful / failed RACH-based or RACH-less CLTM cell switch procedure associated with the SCG cells (i.e. the information related to the CLTM candidate cells configured by the Secondary Node (SN)).
[0176] In another alternative, in any of the earlier embodiments and scenarios, the UE may log information related to successful / failed RACH-based or RACH-less CLTM cell switch procedure associated with both the MCG cells and the SCG cells.
[0177] The UE may implicitly or explicitly indicate which CLTM candidate cells and / or information related to RACH-based or RACH-less CLTM cell switch execution are configured by the MN (or are associated with the MCG) and which CLTM candidate cells and / or the information related to RACH-based or RACH-less CLTM cell switch execution are configured by the SN (or are associated with the SCG).
[0178] Network embodiments
[0179] 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, 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.
[0180] Thus, a RAN node according to the techniques described herein can be configured or operable to receive the information sent by the UE relating to a RACH-based CLTM cell switch procedure or a RACH-less CLTM cell switch procedure according to any of the above embodiments.
[0181] The RAN node can configure a UE to log and / or report information related to RACH-based or RACH-less CLTM cell switch execution. The RAN node can configure the UE to log and / orreport any of the types of information described in the above embodiments. In alternative embodiments, a UE can be pre-configured or pre-programmed to log and / or report information related to RACH-based or RACH-less CLTM cell switch execution.
[0182] The RAN node can send a request to a UE for the UE to send UE reports comprising information related to RACH-based or RACH-less CLTM cell switch execution.
[0183] The RAN node (e.g. a gNB-CU) can send some or all of the information (or information derived therefrom) received from a UE relating to RACH-based or RACH-less CLTM cell switch execution to another RAN node (e.g. a gNB-DU). An example of when this can happen is when the RAN node that received the UE report(s) is not the RAN node responsible for (or is not the RAN node solely responsible for) optimising CLTM, e.g. to reduce / avoid failures in RACH-less CLTM cell execution, or to increase the chance of triggering RACH-less CLTM cell execution, and with that decrease the interruption time in servicing the UE), and other RAN node is, at least in part, responsible for CLTM optimisation.
[0184] The network (e.g. a RAN node, or other node in a communication network) may instruct / configure the UE to include the CLTM candidate cells and / or information related to RACH-based or RACH-less CLTM cell switch execution in one or more SON reports.
[0185] The RAN node may configure a UE with a threshold parameter indicating a percentage of the TAT value. On receiving this parameter, the UE is configured to report (in a UE report, e.g. a Successful Handover Report) an indication of whether, at the time the UE initiated a RACH-based Conditional LTM cell switch execution, the percentage of elapsed TAT value was higher than (or higher than or equal to) the threshold.
[0186] The RAN node may configure a UE with a threshold parameter indicating a percentage of the TAT value. On receiving this parameter, the UE is configured to report (in a UE report, e.g. a RA report) an indication of whether, at the time the UE initiated a RACH-less Conditional LTM cell switch execution, the percentage of elapsed TAT value was higher than (or higher than or equal to) the threshold.
[0187] The RAN node may configure a UE with a threshold parameter indicating an amount of time remaining for a TAT value. On receiving this parameter, the UE is configured to report (in a UE report, e.g. a Successful Handover Report) an indication of whether, at the time the UE initiated a RACH-based or RACH-less Conditional LTM cell switch execution, the amount of time remaining for the TAT value was lower than (or lower than or equal to) the threshold.
[0188] The RAN node may configure a UE to report (in a UE report, e.g. a RA report) an indication of the time when, and / or since, the UE initiated one of a RACH-less Conditional LTM cell switch execution, and / or a RACH-based Conditional LTM cell switch execution.
[0189] The RAN node may configure a UE to report (in a UE report, e.g. a RA report) an indicationof the time elapsed since the UE initiated one of a RACH attempt or an RRC Reestablishment following any of:
[0190] • a failure in a RACH-less Conditional LTM cell switch execution;
[0191] • a failure in a RACH-based Conditional LTM cell switch execution; or
[0192] • a failed fast recovery that followed a failed RACH-less Conditional LTM cell switch execution.
[0193] A network node (e.g. a core network node or a RAN node) may, upon receiving a UE report(s) comprising information related to RACH-based or RACH-less CLTM cell switch execution, determine that it can perform (or is responsible for) optimisation for CLTM and perform one or more corresponding actions. Non-limiting examples of actions that can be performed include:
[0194] • modifying (e.g. reducing) the Timing Advance Timer value to reduce the risk of the TA value being too old or invalid, and increase the use of RACH-less CLTM cell switch execution; and
[0195] • modifying the allocation of uplink resources in the target cell to increase the chance of using RACH-less CLTM cell switch.
[0196] 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.
[0197] In step 302, which is optional, the wireless device can receive a configuration from a RAN node in the communication network. That configuration indicates information to be logged and / or reported to the communication network relating to a CLTM procedure that is to be attempted or performed by the wireless device. In alternative embodiments, the wireless device can be preconfigured with such a configuration, rather than receiving it 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.
[0198] The wireless device can attempt of perform a CLTM procedure and in step 304, which is optional, the wireless device can log information relating to the CLTM procedure. The logging of this information can be according to a configuration, for example a configuration received according to step 302, or a configuration that the wireless device was pre-configured with.
[0199] In step 306, the wireless device sends information to a RAN node relating to a CLTM procedure that was attempted or performed by the wireless device. The information sent to the RAN node can be a reason for performing a RA-based CLTM procedure, and / or the informationcan relate to a success or failure of a RA-less CLTM procedure. Step 306 is similar or corresponding to signal 213 in Fig. 2.
[0200] 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).
[0201] 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.
[0202] The information may be sent in step 306 in response to a request from the communication network for the wireless device to send information relating to a CLTM procedure. Alternatively, the information can be sent in step 306 in response to the wireless device attempting or performing the CLTM procedure.
[0203] Step 306 can be performed in any of the following situations. For example, the wireless device may have has attempted a RA-less CLTM procedure that succeeded. As another example, the wireless device may have attempted a RA-less CLTM procedure that failed. As another example, the wireless device may have attempted a RA-less CLTM procedure that failed, and then attempted or performed a RA-based CLTM procedure. In another example, the wireless device may have attempted or performed a RA-based CLTM procedure.
[0204] 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.
[0205] Fig. 4 shows three steps, steps 402, 404 and 406. The RAN node may perform any one or more of these steps.
[0206] 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 to be attempted or performed by the wireless device. 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 value relating to a timing value (e.g. a TA value) and / or a time alignment timer.
[0207] 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 attempted or performed by the wireless device.
[0208] In step 406, which, as noted, is optional, the RAN node receives, from the wireless device, information relating to the CLTM procedure that was attempted or performed by the wireless device. The information can be received in any of: a SON report; a SHR; an RLF report; a RA report; or a SPR.
[0209] In any of steps 402, 404 and 406, the information can be a reason for performing a RA-based CLTM procedure, and / or information relating to a success or failure of a RA-less CLTMprocedure.
[0210] 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.
[0211] Although not shown in Fig. 4, the method performed by the RAN node may further comprise the RAN node sending 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.
[0212] Although not shown in Fig. 4, the method performed by the RAN node may further comprise performing optimisation and / or modification of CLTM procedures based on the information received in step 406.
[0213] As noted above, the information sent to the RAN node in step 306 and / or received by the RAN node in step 406, can be a reason for performing a RA-based CLTM procedure. The reason for performing the RA-based CLTM procedure can be any one or more of the following reasons. The reason for performing the RA-based CLTM procedure can be that an attempt to perform a RA-less CLTM procedure failed. The reason for performing the RA-based CLTM procedure can be that an attempt to perform a RA-less CLTM procedure would have failed. The reason for performing the RA-based CLTM procedure can be that a timing value (e.g. a TA value) used for the RA-less CLTM procedure is not available, not configured, too old, expired, and / or invalid. The reason for performing the RA-based CLTM procedure can be that insufficient or no resources (e.g. uplink resources) are available for a target beam or target cell for the RA-less CLTM procedure. The reason for performing the RA-based CLTM procedure can be that insufficient or no resources (e.g. uplink resources) are configured for a target beam or target cell for the RA-less CLTM procedure. The reason for performing the RA-based CLTM procedure can be that a beam or cell selected for the RA-less CLTM procedure was not a beam or cell for which resources are configured. The reason for performing the RA-based CLTM procedure can be related to a percentage of a time alignment timer that has or had elapsed when the wireless device attempted or performed the RA-based CLTM procedure. The reason for performing the RA-based CLTM procedure can be that a percentage of a time alignment timer that has or had elapsed when the wireless device attempted or performed the RA-based CLTM procedure equals or exceeds a threshold. The reason for performing the RA-based CLTM procedure can relate to (or be an indication of) an amount of time remaining for a time alignment timer for the RA-less CLTM procedure. The reason for performing the RA-based CLTM procedure can be that an amount of time remaining for a time alignment timer for the RA-less CLTM procedure equals or is less than a threshold. The reason for performing the RA-based CLTM procedure can be that RLF caused the wireless device to attempt, or to perform, the CLTM procedure.For any of the above reasons for performing the RA-based CLTM procedure, the information sent to the RAN node in step 306 and / or received by the RAN node in step 406, can further comprise one or more of the following. The information can comprise a list of candidate cells and / or candidate beams for which a timing value (e.g. a TA value) used for a RA-less CLTM procedure is still valid. The information can comprise information about a target cell or target beam for a failed RA-less CLTM procedure. The information can comprise information about whether a target cell or target beam for the RA-based CLTM procedure is the same as or different to a target cell or target beam for a failed RA-less CLTM procedure. The information can comprise information about a TAG for one or more candidate cells and / or candidate beams. The information can comprise information relating to an acquisition procedure for a timing value (e.g. a TA value).
[0214] As noted above, the information sent to the RAN node in step 306, and / or received by the RAN node in step 406, can relate to a success or failure of a RA-less CLTM procedure. The information relating to a success or failure of a RA-less CLTM procedure can be an indication and / or reason that the RA-less CLTM procedure succeeded. Alternatively, the information relating to a success or failure of a RA-less CLTM procedure can be an indication and / or reason that the RA-less CLTM procedure nearly failed. Alternatively, the information relating to a success or failure of a RA-less CLTM procedure can be an indication and / or reason that the RA-less CLTM procedure failed.
[0215] The information relating to success or failure of the RA-less CLTM procedure sent in step 306, and / or received by the RAN node in step 406, can be any one or more of the following types of information. The information relating to success or failure of the RA-less CLTM procedure can be an indication that the RA-less CLTM procedure failed due to a timer timeout. The information relating to success or failure of the RA-less CLTM procedure can be an indication of a number of times that the wireless device has attempted transmissions to a candidate cell or candidate beam for the RA-less CLTM procedure. The information relating to success or failure of the RA-less CLTM procedure can be information for a time elapsed since a timing value (e.g. a TA value) used for the RA-less CLTM procedure was received by the wireless device. The information relating to success or failure of the RA-less CLTM procedure can be information for a remaining validity of a timing value (e.g. a TA value) used for the RA-less CLTM procedure when the RA-less CLTM procedure was attempted or performed. The information relating to success or failure of the RA-less CLTM procedure can be information for a remaining validity of a timing value (e.g. a TA value) relative to a time alignment timer used for the RA-less CLTM procedure when the RA-less CLTM procedure was attempted or performed. The information relating to success or failure of the RA-less CLTM procedure can be information for a remaining validity of a timing value(e.g. a TA value) relative to a time alignment timer used for a candidate cell or candidate beam for the RA-less CLTM procedure. The information relating to success or failure of the RA-less CLTM procedure can be a percentage of a time alignment timer that has or had elapsed when the wireless device attempted or performed the RA-less CLTM procedure. The information relating to success or failure of the RA-less CLTM procedure can be an indication that a percentage of a time alignment timer that has or had elapsed when the wireless device attempted or performed the RA-less CLTM procedure equals or exceeds a threshold. The information relating to success or failure of the RA-less CLTM procedure can be an indication of an amount of time remaining for a time alignment timer for the RA-less CLTM procedure. The information relating to success or failure of the RA-less CLTM procedure can be an indication of whether an amount of time remaining for a time alignment timer for the RA-less CLTM procedure equals or is less than a threshold. The information relating to success or failure of the RA-less CLTM procedure can be an indication of whether a validity of a timing value was extended. The information relating to success or failure of the RA-less CLTM procedure can be information about which beam(s) or cell(s) had resources configured for the RA-less CLTM procedure. The information relating to success or failure of the RA-less CLTM procedure can be information about which beam(s) or cell(s) did not have resources configured for the RA-less CLTM procedure. The information relating to success or failure of the RA-less CLTM procedure can be information about a target cell or target beam for a failed RA-less CLTM procedure. The information relating to success or failure of the RA-less CLTM procedure can be information about a TAG for one or more candidate cells and / or candidate beams. The information relating to success or failure of the RA-less CLTM procedure can be information relating to an acquisition procedure for a timing value (e.g. a TA value). The information relating to success or failure of the RA-less CLTM procedure can be an indication that RLF caused the wireless device to attempt, or to perform, the CLTM procedure. The information relating to success or failure of the RA-less CLTM procedure can be an indication that the RA-less CLTM procedure was attempted or performed after a failed LTM procedure. The information relating to success or failure of the RA-less CLTM procedure can be a list of candidate cells and / or candidate beams for which a timing value (e.g. a TA value) used for a RA-less CLTM procedure is still valid. The information relating to success or failure of the RA-less CLTM procedure can be a list of candidate cells and / or candidate beams for which a timing value (e.g. a TA value) used for a RA-less CLTM procedure is not valid.
[0216] 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 acore 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.
[0217] 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 and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the 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.
[0218] 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.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)).
[0219] 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 include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.
[0220] 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 5122, 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.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 (ALISF), 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).
[0221] 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.
[0222] 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 beconfigured 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.
[0223] 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.
[0224] In some examples, the telecommunication network 502 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 502 may support 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.
[0225] 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).
[0226] 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 receivedfrom 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.
[0227] 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 / or one 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.
[0228] 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 wirelessdevice, 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.
[0229] 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).
[0230] 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.
[0231] 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 UE 600 to perform the methods as described herein.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.
[0232] 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.
[0233] 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.
[0234] 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 dynamicrandom access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (IIICC) including one or more subscriber identity modules (SIMs), such as a IISIM and / or ISIM, other memory, or any combination thereof. The IIICC may for example be an embedded IIICC (elllCC), integrated IIICC (illlCC) or a removable IIICC 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.
[0235] 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 remote transceivers of another device capable of wireless communication (e.g., another wireless device or a network node in an access network). Each transceiver may include a transmitter 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.
[0236] 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.
[0237] 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 becommunicated 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).
[0238] 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.
[0239] 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.
[0240] 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.
[0241] 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.
[0242] 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 may be 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., 0-Rll, 0-Dll, O-CU).
[0243] 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 (Dlls)) (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).
[0244] 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).
[0245] 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.
[0246] 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.
[0247] 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 as described herein.
[0248] 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.
[0249] 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.
[0250] 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.
[0251] In certain alternative embodiments, RAN node 700 may be capable of wireless communication but does not include separate radio front-end circuitry 718, instead, theprocessing 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).
[0252] 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.
[0253] 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 signals may 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.
[0254] 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.
[0255] 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 node700. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the RAN node 700.
[0256] 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 environment 800 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.
[0257] 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.
[0258] 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.
[0259] 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, physicalswitches, and physical storage, which can be located in data centers, and customer premise equipment.
[0260] 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.
[0261] 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 some embodiments, 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.
[0262] 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 communicationinterface 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.
[0263] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.
[0264] 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 that was attempted or performed by the wireless device, wherein the information is one or more of:a reason for performing a Random Access-, RA-, based CLTM procedure, and information relating to a success or failure of a RA-less CLTM procedure.
2. The method of claim 1 , wherein one of:the wireless device has attempted a RA-less CLTM procedure that succeeded;the wireless device has attempted a RA-less CLTM procedure that failed;the wireless device has attempted a RA-less CLTM procedure that failed and then attempted or performed a RA-based CLTM procedure; orthe wireless device has attempted or performed a RA-based CLTM procedure.
3. The method of claim 1 or 2, wherein the reason for performing the RA-based CLTM procedure is one or more of:an attempt to perform a RA-less CLTM procedure failed;an attempt to perform a RA-less CLTM procedure would have failed;a timing value used for the RA-less CLTM procedure is any of: not available, not configured, too old, expired, or invalid;insufficient or no resources are available for a target beam or target cell for the RA-less CLTM procedure;insufficient or no resources are configured for a target beam or target cell for the RA-less CLTM procedure;a beam or cell selected for the RA-less CLTM procedure was not a beam or cell for which resources are configured;a percentage of a time alignment timer that has or had elapsed when the wireless device attempted or performed the RA-based CLTM procedure;a percentage of a time alignment timer that has or had elapsed when the wireless device attempted or performed the RA-based CLTM procedure equals or exceeds a threshold;an indication of an amount of time remaining for a time alignment timer for the RA-less CLTM procedure;an indication of an amount of time remaining for a time alignment timer for the RA-less CLTM procedure equals or is less than a threshold; andan indication that Radio Link Failure, RLF, caused the wireless device to attempt, or to perform, the CLTM procedure.
4. The method of claim 3, wherein the information relating to the CLTM procedure further comprises one or more of:a list of candidate cells and / or candidate beams for which a timing value used for a RA-less CLTM procedure is still valid;information about a target cell or target beam for a failed RA-less CLTM procedure; information about whether a target cell or target beam for the RA-based CLTM procedure is the same as or different to a target cell or target beam for a failed RA-less CLTM procedure;information about a Timing Advance Group, TAG, for one or more candidate cells and / or candidate beams; andinformation relating to an acquisition procedure for a timing value.
5. The method of any of claims 1-4, wherein the information relating to success or failure of the RA-less CLTM procedure is one of:an indication that the RA-less CLTM procedure succeeded;an indication that the RA-less CLTM procedure nearly failed; andan indication that the RA-less CLTM procedure failed.
6. The method of any of claims 1-5, wherein the information relating to success or failure of the RA-less CLTM procedure is one of:a reason that the RA-less CLTM procedure succeeded;a reason that the RA-less CLTM procedure nearly failed; anda reason that the RA-less CLTM procedure failed.
7. The method of any of claims 1-6, wherein the information relating to success or failure of the RA-less CLTM procedure comprises any one or more of:an indication that the RA-less CLTM procedure failed due to a timer timeout;an indication of a number of times that the wireless device has attempted transmissions to a candidate cell or candidate beam for the RA-less CLTM procedure;information for a time elapsed since a timing value used for the RA-less CLTM procedure was received by the wireless device;information for a remaining validity of a timing value used for the RA-less CLTM procedure when the RA-less CLTM procedure was attempted or performed;information for a remaining validity of a timing value relative to a time alignment timer used for the RA-less CLTM procedure when the RA-less CLTM procedure was attempted or performed;information for a remaining validity of a timing value relative to a time alignment timer used for a candidate cell or candidate beam for the RA-less CLTM procedure;a percentage of a time alignment timer that has or had elapsed when the wireless device attempted or performed the RA-less CLTM procedure;an indication that a percentage of a time alignment timer that has or had elapsed when the wireless device attempted or performed the RA-less CLTM procedure equals or exceeds a threshold;an indication of an amount of time remaining for a time alignment timer for the RA-less CLTM procedure;an indication of whether an amount of time remaining for a time alignment timer for the RA-less CLTM procedure equals or is less than a threshold;an indication of whether a validity of a timing value was extended;information about which beam(s) or cell(s) had resources configured for the RA-less CLTM procedure;information about which beam(s) or cell(s) did not have resources configured for the RA-less CLTM procedure;information about a target cell or target beam for a failed RA-less CLTM procedure; information about a Timing Advance Group, TAG, for one or more candidate cells and / or candidate beams;information relating to an acquisition procedure for a timing value;an indication that Radio Link Failure, RLF, caused the wireless device to attempt, or to perform, the CLTM procedure;an indication that the RA-less CLTM procedure was attempted or performed after a failed L1 / L2 triggered mobility, LTM, procedure;a list of candidate cells and / or candidate beams for which a timing value used for a RA-less CLTM procedure is still valid; anda list of candidate cells and / or candidate beams for which a timing value used for a RA-less CLTM procedure is not valid.
8. The method of any of claims 1-7, wherein the method further comprises logging (304) the information relating to the CLTM procedure.
9. The method of claim 8, wherein the wireless device logs the information according to a configuration.
10. The method of claim 9, wherein the configuration is received from the communication network.
11. The method of any of claims 1-10, wherein the sending (306) of the information, and / or the information to be sent, is according to a configuration.
12. The method of claim 11, wherein the configuration is received from the communication network.
13. The method of any of claims 1-12, wherein the information is sent in response to a request from the communication network for the wireless device to send information relating to a CLTM procedure.
14. The method of any of claims 1-12, wherein the information is sent in response to the CLTM procedure being attempted or performed.
15. The method of any of claims 1-14, wherein the information is sent in any of: a SelfOrganising Network, SON, report; a Successful Handover Report, SHR; a Radio Link Failure, RLF, report; a Random Access, RA, report; or a Successful Primary Secondary Cell, PSCell, Change Report, SPR.
16. The method of any of claims 1-15, wherein the information relates to a CLTM procedure for any of: a Master Cell Group, MCG; a Secondary Cell Group, SCG; a MCG and a SCG.
17. A method performed by a radio access network, RAN, node in a communication network, the method comprising one or more of:(i) 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 to be attempted or performed by the wireless device;(ii) sending (404), to the wireless device, a request for information relating to the CLTM procedure attempted or performed by the wireless device; and(iii) receiving (406), from the wireless device, information relating to the CLTM procedure that was attempted or performed by the wireless device;wherein the information is one or more of: a reason for performing a Random Access-, RA-, based CLTM procedure; and information relating to a success or failure of a RA-less CLTM procedure.
18. The method of claim 17, wherein the reason for performing the RA-based CLTM procedure is one or more of:an attempt to perform a RA-less CLTM procedure failed;an attempt to perform a RA-less CLTM procedure would have failed;a timing value used for the RA-less CLTM procedure is any of: not available, not configured, too old, expired, or invalid;insufficient or no resources are available for a target beam or target cell for the RA-less CLTM procedure;insufficient or no resources are configured for a target beam or target cell for the RA-less CLTM procedure;a beam or cell selected for the RA-less CLTM procedure was not a beam or cell for which resources are configured;a percentage of a time alignment timer that has or had elapsed when the wireless device attempted or performed the RA-based CLTM procedure;a percentage of a time alignment timer that has or had elapsed when the wireless device attempted or performed the RA-based CLTM procedure equals or exceeds a threshold;an indication of an amount of time remaining for a time alignment timer for the RA-less CLTM procedure;an indication of an amount of time remaining for a time alignment timer for the RA-less CLTM procedure equals or is less than a threshold; andan indication that Radio Link Failure, RLF, caused the wireless device to attempt, or to perform, the CLTM procedure.
19. The method of claim 18, wherein the information relating to the CLTM procedure further comprises one or more of:a list of candidate cells and / or candidate beams for which a timing value used for a RA-less CLTM procedure is still valid;information about a target cell or target beam for a failed RA-less CLTM procedure;information about whether a target cell or target beam for the RA-based CLTM procedure is the same as or different to a target cell or target beam for a failed RA-less CLTM procedure;information about a Timing Advance Group, TAG, for one or more candidate cells and / or candidate beams; andinformation relating to an acquisition procedure for a timing value.
20. The method of any of claims 17-19, wherein the information relating to success or failure of the RA-less CLTM procedure is one of:an indication that the RA-less CLTM procedure succeeded;an indication that the RA-less CLTM procedure nearly failed; andan indication that the RA-less CLTM procedure failed.
21. The method of any of claims 17-20, wherein the information relating to success or failure of the RA-less CLTM procedure is one of:a reason that the RA-less CLTM procedure succeeded;a reason that the RA-less CLTM procedure nearly failed; anda reason that the RA-less CLTM procedure failed.
22. The method of any of claims 17-21 , wherein the information relating to success or failure of the RA-less CLTM procedure comprises any one or more of:an indication that the RA-less CLTM procedure failed due to a timer timeout;an indication of a number of times that the wireless device has attempted transmissions to a candidate cell or candidate beam for the RA-less CLTM procedure;information for a time elapsed since a timing value used for the RA-less CLTM procedure was received by the wireless device;information for a remaining validity of a timing value used for the RA-less CLTM procedure when the RA-less CLTM procedure was attempted or performed;information for a remaining validity of a timing value relative to a time alignment timer used for the RA-less CLTM procedure when the RA-less CLTM procedure was attempted or performed;information for a remaining validity of a timing value relative to a time alignment timer used for a candidate cell or candidate beam for the RA-less CLTM procedure;a percentage of a time alignment timer that has or had elapsed when the wireless device attempted or performed the RA-less CLTM procedure;an indication that a percentage of a time alignment timer that has or had elapsed when the wireless device attempted or performed the RA-less CLTM procedure equals or exceeds a threshold;an indication of an amount of time remaining for a time alignment timer for the RA-less CLTM procedure;an indication of whether an amount of time remaining for a time alignment timer for the RA-less CLTM procedure equals or is less than a threshold;an indication of whether a validity of a timing value was extended;information about which beam(s) or cell(s) had resources configured for the RA-less CLTM procedure;information about which beam(s) or cell(s) did not have resources configured for the RA-less CLTM procedure;information about a target cell or target beam for a failed RA-less CLTM procedure; information about a Timing Advance Group, TAG, for one or more candidate cells and / or candidate beams;information relating to an acquisition procedure for a timing value;an indication that Radio Link Failure, RLF, caused the wireless device to attempt, or to perform, the CLTM procedure;an indication that the RA-less CLTM procedure was attempted or performed after a failed L1 / L2 triggered mobility, LTM, procedure;a list of candidate cells and / or candidate beams for which a timing value used for a RA-less CLTM procedure is still valid; anda list of candidate cells and / or candidate beams for which a timing value used for a RA-less CLTM procedure is not valid.
23. The method of any of claims 17-22, wherein the information is sent in any of: a SelfOrganising Network, SON, report; a Successful Handover Report, SHR; a Radio Link Failure, RLF, report; a Random Access, RA, report; or a Successful Primary Secondary Cell, PSCell, Change Report, SPR.
24. The method of any of claims 17-23, wherein the information relates to a CLTM procedure for any of: a Master Cell Group, MCG; a Secondary Cell Group, SCG; a MCG and a SCG.
25. The method of any of claims 17-24, 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.
26. The method of any of claims 17-25, wherein the configuration for information indicates any of:one or more types of information to be logged and / or reported relating to the CLTM procedure; anda threshold value relating to a timing value and / or a time alignment timer.
27. The method of any of claims 17-26, wherein the method further comprises:perform optimisation and / or modification of CLTM procedures based on the received information.
28. 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-27.
29. A wireless device configured to perform the method of any of claims 1-16.
30. 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-16.
31. A radio access network, RAN, node, configured to perform the method of any of claims 17-27.
32. 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 17-27.
