Configuration information storage control

Abstract

An apparatus having means to receive at least one L1 / L2 triggered mobility, LTM, candidate cell configuration, pre-process the at least one LTM candidate cell configuration, and store the pre-processe

Description

TECHNOLOGICAL FIELD Examples of the disclosure relate to configuration information storage control. Some relate to L1 / L2 triggered mobility, LTM, candidate cell configuration information storage control. BACKGROUND A wireless network comprises a plurality of network nodes including terminal nodes and access nodes. Communication between the terminal nodes and access nodes is wireless. A terminal node, such as a user equipment, UE, can receive configuration information, for example LTM candidate cell configurations. In some circumstances, it may be desirable to improve or enhance how a terminal node stores received and processed configuration information. BRIEF SUMMARY According to various, but not necessarily all, examples there is provided an apparatus comprising means for: receiving at least one L1 / L2 triggered mobility, LTM, candidate cell configuration; pre-processing the at least one LTM candidate cell configuration; and storing the pre-processed at least one LTM candidate cell configuration in at least one memory until at least one condition is satisfied. In some examples, the means are configured to: determine whether the at least one condition has been satisfied; and in response to determining that the at least one condition has been satisfied, stop storing at least one of the pre-processed at least one LTM candidate cell configuration. In some examples, the at least one LTM candidate cell configurations as at least one LTM candidate cell radio resource control, RRC, configuration. In some examples, stopping storing comprises at least one of the following: releasing the memory used to store the pre-processed at least one LTM candidate cell configuration for re-use, removing a stored reference to the memory used to store the pre-processed at least one LTM candidate cell configuration, or deleting the pre-processed at least one LTM candidate cell configuration. In some examples, the means are configured to pre-process the at least one LTM candidate cell configurations based, at least in part, on at least one trigger event. In some examples, the at least one trigger event comprises at least one of the following: receiving the at least one LTM candidate cell configuration, receiving TCI state activation, or receiving physical downlink control channel, PDCCH, order. In some examples, the at least one condition comprises at least one of the following: expiry of a pre-processing timer, transmission configuration indicator, TCI, state deactivation, early estimated timing advance, TA, becomes invalid, or cell becomes undetectable. In some examples, the means are configured to determine a pre-processing timer duration and to start the pre-processing timer based, at least in part, on at least one trigger event for pre-processing at least one LTM candidate cell configuration. In some examples, determining a pre-processing timer duration comprises at least one of the following: retrieving the pre-processing timer duration from at least one memory, or receiving the pre-processing timer duration from an access node. In some examples, determining the pre-processing timer duration comprises determining the pre-processing timer duration based, at least in part, on the type of trigger event that starts the pre-processing timer. In some examples, determining a pre-processing timer duration comprises retrieving the pre-processing timer duration from at least one memory, and the means are configured to transmit an indication of the determined pre-processing timer duration towards at least one access node. In some examples, the pre-processing timer duration is determined based, at least in part, on the duration of at least one different timer. In some examples, the means are configured to extend the duration of the preprocessing timer based, at least in part, on at least one trigger event for preprocessing at least one LTM candidate cell configurations. In some examples, the means are configured to stop the pre-processing timer based, at least in part, on fulfilment of at least one end condition. In some examples, the at least one end condition comprises at least one of the following: transmission configuration indicator, TCI, state deactivation, early estimated timing advance, TA, becomes invalid, or cell becomes undetectable. In some examples, the means are configured to continue to store at least one of the pre-processed at least one LTM candidate cell configurations after cell switch to at least one candidate cell associated with one of the at least one LTM candidate cell configurations. In some examples, the at least one LTM candidate cell configuration comprises a plurality of LTM candidate cell configurations, and the means are configured to stop storing the pre-processed LTM candidate cell configuration associated with a cell to which a cell switch is performed, and to continue storing at least one pre-processed LTM candidate cell configuration associated with at least one cell to which cell switch was not performed. According to various, but not necessarily all, embodiments there is provided a method comprising: receiving at least one L1 / L2 triggered mobility, LTM, candidate cell configuration; pre-processing the at least one LTM candidate cell configuration; and storing the pre-processed at least one LTM candidate cell configuration in at least one memory until at least one condition is satisfied. In some examples, the method compriser: determining whether the at least one condition has been satisfied; and in response to determining that the at least one condition has been satisfied, stopping storing at least one of the pre-processed at least one LTM candidate cell configuration. In some examples, the at least one LTM candidate cell configurations is at least one LTM candidate cell radio resource control, RRC, configuration. In some examples, stopping storing comprises at least one of the following: releasing the memory used to store the pre-processed at least one LTM candidate cell configuration for re-use, removing a stored reference to the memory used to store the pre-processed at least one LTM candidate cell configuration, or deleting the pre-processed at least one LTM candidate cell configuration. In some examples, the method comprises pre-processing the at least one LTM candidate cell configurations based, at least in part, on at least one trigger event. In some examples, the at least one trigger event comprises at least one of the following: receiving the at least one LTM candidate cell configuration, receiving TCI state activation, or receiving physical downlink control channel, PDCCH, order. According to various, but not necessarily all, embodiments there is provided a computer program comprising instructions which, when executed by an apparatus, cause the apparatus at least to perform: receiving at least one L1 / L2 triggered mobility, LTM, candidate cell configuration; pre-processing the at least one LTM candidate cell configuration; storing the pre-processed at least one LTM candidate cell configuration in at least one memory until at least one condition is satisfied. In some examples, the computer program comprises instructions which, when executed by an apparatus, cause the apparatus at least to perform: determining whether the at least one condition has been satisfied; and in response to determining that the at least one condition has been satisfied, stopping storing at least one of the pre-processed at least one LTM candidate cell configuration. is provided... According to various, but not necessarily all, embodiments there is provided an apparatus comprising at least one processor; and at least one memory including computer program code; the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to perform at least a part of one or more methods described herein. According to various, but not necessarily all, embodiments there is provided an apparatus comprising means for performing at least part of one or more methods described herein. The description of a function and / or action should additionally be considered to also disclose any means suitable for performing that function and / or action. Functions and / or actions described herein can be performed in any suitable way using any suitable method. According to various, but not necessarily all, embodiments there is provided examples as claimed in the appended claims. While the above examples of the disclosure and optional features are described separately, it is to be understood that their provision in all possible combinations and permutations is contained within the disclosure. It is to be understood that various examples of the disclosure can comprise any or all the features described in respect of other examples of the disclosure, and vice versa. Also, it is to be appreciated that any one or more or all the features, in any combination, may be implemented by / comprised in / performable by an apparatus, a method, and / or computer program instructions as desired, and as appropriate. The description of a function should additionally be considered to also disclose any means suitable for performing that function BRIEF DESCRIPTION Some examples will now be described with reference to the accompanying drawings in which: FIG. 1 shows an example of the subject matter described herein; FIG. 2 shows another example of the subject matter described herein; FIG. 3A shows another example of the subject matter described herein; FIG. 3B shows another example of the subject matter described herein; FIG. 4 shows another example of the subject matter described herein; FIG. 5 shows another example of the subject matter described herein; FIG. 6A shows another example of the subject matter described herein; and FIG. 6B shows another example of the subject matter described herein. The figures are not necessarily to scale. Certain features and views of the figures can be shown schematically or exaggerated in scale in the interest of clarity and conciseness. For example, the dimensions of some elements in the figures can be exaggerated relative to other elements to aid explication. Similar reference numerals are used in the figures to designate similar features. For clarity, all reference numerals are not necessarily displayed in all figures. DETAILED DESCRIPTION FIG 1 illustrates an example of a network 100 comprising a plurality of network nodes including terminal nodes 110, access nodes 120 and one or more core nodes 129. The terminal nodes 110 and access nodes 120 communicate with each other. The one or more core nodes 129 communicate with the access nodes 120. The network 100 is in this example a radio telecommunications network, in which at least some of the terminal nodes 110 and access nodes 120 communicate with each other using transmission / reception of radio waves / signals. The one or more core nodes 129 may, in some examples, communicate with each other. The one or more access nodes 120 may, in some examples, communicate with each other. The network 100 may be a cellular network comprising a plurality of cells 122 each served by an access node 120. In this example, the interface between the terminal nodes 110 and an access node 120 defining a cell 122 is a wireless interface 124. The access node 120 is a cellular radio transceiver. The terminal nodes 110 are cellular radio transceivers. In the example illustrated the cellular network 100 is a third generation Partnership Project (3GPP) network in which the terminal nodes 110 are user equipment (UE), see, for example, FIG. 2, and the access nodes 120 are base stations. In examples the network 100 is an Evolved Universal Terrestrial Radio Access network (E-UTRAN). The E-UTRAN consists of E-UTRAN NodeBs (eNBs) 120, providing the E-UTRA user plane and control plane (RRC) protocol terminations towards the UE. The eNBs 120 are interconnected with each other by means of an X2 interface 126. The eNBs are also connected by means of the S1 interface 128 to the Mobility Management Entity (MME) 129. In other examples the network 100 is a Next Generation (or New Radio, NR) Radio Access network (NG-RAN). The NG-RAN consists of gNodeBs (gNBs) 120, providing the user plane and control plane (RRC) protocol terminations towards the UE 110. The gNBs 120 are interconnected with each other by means of an Xn interface 126. The gNBs are also connected by means of the N2 interface 128 to the Access and Mobility management Function (AMF). In some examples, the access nodes 120 can comprise at least one wireless edge computing server. A user equipment (UE) can comprise a mobile equipment. Where reference is made to user equipment that reference includes and encompasses, wherever possible, a reference to mobile equipment. The network 100 can comprise a combination of E-UTRAN and NG-RAN. The network 100 can comprise a 6th generation radio access network, 6GRAN. A terminal node 110, such as a UE 164, can be configured to perform layer 1, L1, / layer 2, L2, triggered mobility (LTM). In examples, a terminal node 110 can be provided with at least one LTM candidate cell configuration and can be caused to pre-process the at least one LTM candidate cell configuration to, for example, reduce processing time during cell switch. For example, a terminal node 110 can be triggered to pre-process the at least one LTM candidate cell configuration by at least one predetermined event, which can be considered at least one trigger event. In examples, the terminal node 110 stores the pre-processed at least one LTM candidate cell configuration in at least one memory, for example a fast memory to enable efficient cell switch. In examples, the terminal node 110 is configured to store the pre-processed at least one LTM candidate cell configuration until at least one condition is satisfied to, for example, prevent the terminal node 110 from storing the pre-processed configurations for a long time when they are not needed. For example, the terminal node 110 can discard the pre-processed at least one LTM candidate cell configuration after expiry of a timer. Examples of the disclosure relate to at least one of the following: apparatuses, methods, or computer programs for controlling storage of LTM candidate cell configuration information. Examples of the disclosure relate to at least one of the following: apparatuses, methods, or computer programs for controlling storage of pre-processed LTM candidate cell configuration information based, at least in part, on fulfilment of at least one condition. FIG. 2 illustrates an example of signaling between entities. FIG. 2 also illustrates an example of a method 200. FIG. 2 illustrates methods performed by a system comprising interaction between different system entities. FIG. 2 also illustrates a collection of separate methods performed separately by the different system entities. One or more of the features discussed in relation to FIG. 2 can be found in one or more of the other FIGs. In the example of FIG. 2, a plurality of apparatuses transmit and / or receive one or more signals and / or messages across and / or via and / or using a network. In examples, any suitable form of communication in any suitable network can be used. For example, at least a portion of the network 100 of FIG. 1 can be used. In the example of FIG. 2, a terminal node 110 and a transmission / reception point transmit and / or receive one or more signals and / or one or more messages. In the example of FIG. 2 the terminal node 110 is a UE 164, and the transmission / reception point is an access node 120, such as a gNodeB (gNB) 166. However, in examples, the transmission / reception point can comprise any suitable node or nodes in a network, such as the network of FIG. 1. In examples, the terminal node 110 is in a connected mode or state, for example a radio connected mode such as radio resource control, RRC, CONNECTED. Accordingly, in examples, at least part of method 200 is performed while the terminal node 110 is in a connected mode. In some examples, method 200 is performed while the terminal node 110 is in connected mode. In examples, transmissions between entities illustrated in FIG. 2 can proceed via any number of intervening entities, including no intervening entities. Although a single terminal node 110 is illustrated in the example of FIG. 2, in examples any suitable number of terminal nodes 110 can be included. Similarly, any suitable number of transmission / reception points, such as access nodes 120, can be used. As used herein, a description of a function / action should also be considered to disclose at least one of the following: enabling, causing, or controlling that function / action. For example, description of transmitting information should also be considered to disclose at least one of the following: enabling transmission of information, causing transmission of information, or controlling transmission of information. For example, a description of an apparatus, such as an access node 120, transmitting information should also be considered to disclose at least one controller of the apparatus performing at least one of the following: enabling the apparatus to transmit the information, causing the apparatus to transmit the information, or controlling the apparatus to transmit the information. In examples, at least part of method 200 can be considered a method of controlling storage of configuration information. In examples, at least part of method 200 can be considered a method of controlling storage of at least one pre-processed LTM candidate cell configuration. In examples, at least part of method 200 can be considered a method of controlling use of terminal node resources. In the illustrated examples, the location of the blocks indicates the entity or entities performing the function(s) / action(s). For example, block 202 is performed by the access node 120 (transmitting) and the terminal node 110 (receiving). For example, block 204 is performed by the terminal node 110. As used herein, the term ‘block’ is intended to refer to an action or actions indicated in a FIG. For example, the term ‘block’ can refer to the action of transmitting / receiving indicated by reference numeral 202 in FIG. 2, and can also refer to the action of determining indicated by reference numeral 208 and so on. At block 202, method 200 comprises, from the point of view of the access node 120, transmitting at least one LTM candidate cell configuration 168. As FIG. 2 illustrates one or more functions / actions of transmitting, FIG. 2 also illustrates the corresponding receiving and causing / enabling / controlling function(s) / action(s). For example, from the point of view of the terminal node 110, at block 202, method 200 comprises receiving at least one LTM candidate cell configuration 168. The at least one LTM candidate cell configuration 168 can be any suitable LTM candidate cell configuration 168. For example, the at least one LTM candidate cell configuration 168 can be any suitable LTM candidate cell configuration 168 to configure the terminal node 110 for LTM towards at least one candidate cell. In some examples, the at least one LTM candidate cell configuration 168 is at least one LTM candidate cell RRC configuration. Any suitable number of LTM candidate cell configurations 168 can be received. In examples, any number up to and including a maximum number of LTM candidate cell configurations 168 that the terminal node 110 is capable of supporting can be received. The terminal node 110 can inform the access node 120 of the maximum number of LTM candidate cell configurations 168 that the terminal node 110 is capable of supporting in, for example, capability information. The at least one LTM candidate cell configuration 168 can be transmitted using any suitable message or messages. In some examples, the at least one LTM candidate cell configuration 168 is transmitted with at least one ASN.1 formatted message, such as RRC Reconfiguration message. At block 204, method 200 comprises pre-processing the at least one LTM candidate cell configuration 168. In examples, pre-processing at least one LTM candidate cell configuration 168 means that the terminal node 110 processes the at least one LTM candidate cell configurations prior to a cell switch command being received. For example, in the example of FIG. 2, the terminal node 110 processes (pre-processes) the at least one LTM candidate cell configuration 168 before a cell switch command 182 is received from the access node 120. In examples, pre-processing the at least one LTM candidate cell configuration 168 comprises processing the at least one LTM candidate cell configuration 168 so that it is ready for use during cell switch. In examples, pre-processing the at least one LTM candidate cell configuration 168 comprises performing Abstract Syntax Notation One (ASN.1) decoding and validity / compliance check for the at least one LTM candidate cell configuration 168. In examples, block 204 comprises pre-processing a subset of the received at least one LTM candidate cell configurations 168. For example, a plurality of LTM candidate cell configurations 168 can be received at block 204 and at least one, but not all, of the plurality of received LTM candidate cell configurations 168 can be pre-processed at block 204. In some examples, method 200 comprises pre-processing the least one LTM candidate cell configuration 168 based, at least in part, on at least one trigger event 174. The at least one trigger event 174 can comprise any suitable event or events. For example, the at least one trigger event 174 can comprise at least one of receiving or transmitting information. For example, the at least one trigger event 174 can comprise any suitable event or events involved in LTM. In some examples, the at least one trigger event 174 comprises at least one of the following: receiving the least one LTM candidate cell configuration 168, receiving transmission configuration indicator (TCI) state activation, or receiving physical downlink control channel (PDCCH) order. At block 206, method 200 comprises storing the pre-processed at least one LTM candidate cell configuration 168 in at least one memory 134 until at least one condition 172 is satisfied. Consequently, FIG. 2 illustrates a method 200 comprising: receiving at least one LTM candidate cell configuration 168; pre-processing the at least one LTM candidate cell configuration 168; and storing the pre-processed at least one LTM candidate cell configuration 172 in at least one memory 134 until at least one condition 172 is satisfied. As discussed above, in examples, the terminal node 110 in FIG. 2 is in a radio connected mode, such as RRC CONNECTED mode. Accordingly, in some examples, block 206 comprises storing the pre-processed at least one LTM candidate cell configuration 168 in at least one memory 134 until at least one condition 172 is satisfied while the terminal node is in a radio connected mode, such as RRC CONNECTED mode. In some examples, block 206 comprises storing the pre-processed at least one LTM candidate cell configuration 168 in at least one memory 134 until at least one condition 172 is satisfied while the terminal node 110 is in a radio connected mode, such as RRC CONNECTED mode, and remains in a radio connected mode. That is, in examples, the terminal node 110 remains in a radio connected mode after the at least one condition 172 is satisfied. Accordingly, in examples, the at least one condition 172 is not related to the terminal node 110 changing to or being in an idle or disconnected mode, such as RRC IDLE or RRC DISCONNECTED mode, or the terminal node 172 being powered off. In examples, the at least one memory 134 is any suitable memory. In some examples, the at least one memory 134 is at least one memory close to the processor(s) of the terminal node 110. The at least one memory 134 can be a fast memory / at least one memory that is accessible in a fast manner. For example, the at least one memory 134 can be an L1 cache memory. Accordingly, in examples, storing the pre-processed at least one LTM candidate cell configuration 168 in the at least one memory represents a significant use of resources for the terminal node 110. The at least one condition 172 can comprise any suitable condition(s). For example, the at least one condition 172 can be associated with at least one pre-processing timer 176. Additionally, or alternatively, the at least one condition 172 can be associated with LTM, for example, at least one state associated with LTM, at least one action associated with LTM and so on. In examples, the at least one condition 172 can be associated with a subset of the at least one LTM candidate cell configurations 168. For example, a plurality of LTM candidate cell configurations 168 can be received at block 202 and the at least one condition 172 can be associated with at least one, but not all, of the plurality of LTM candidate cell configurations 168. In some examples, the at least one condition 172 is cell specific. Accordingly, in examples, satisfying of at least one condition 172 affects at least one, but not necessarily all, of the pre-processed at least one LTM candidate cell configurations 172. At block 208, method 200 comprises determining whether the at least one condition 172 has been satisfied. In some examples, the at least one condition 172 comprises at least one of the following: expiry of a pre-processing timer 176, TCI state deactivation, early estimated timing advance (TA) becomes invalid, or cell becomes undetectable. Cell becomes undetectable can be considered cell associated with at least one pre-processed LTM candidate cell configuration 172 becomes undetectable. Accordingly, in examples, method 200 comprises at least one of the following: determining whether a pre-processing timer 176 has expired, determining whether early estimated TA has become invalid, or determining whether a cell has become undetectable. In examples, the pre-processing timer 176 can have any suitable duration 178. Accordingly, in examples, method 200 comprises starting a pre-processing timer 176 having any suitable duration 178. In examples, the terminal node 110 starts and controls the pre-processing timer 176. Accordingly, in examples, actions associated with the pre-processing timer 176 are performed by the terminal node 110. In some examples, starting the pre-processing timer 176 is based, at least in part, on the trigger event 174 based, at least in part, on which the pre-processing the at least one LTM candidate cell configuration 168 occurred. For example, the pre-processing timer 176 can be started when the trigger event happens, or the pre-processing timer 176 can be started after a delay following the trigger event 174 occurring. For example, when the trigger event 174 comprises receiving the at least one LTM candidate cell configuration 168, the pre-processing timer 176 can be started after the at least one LTM candidate cell configuration 168 has been processed (pre-processed) and therefore the pre-processing timer 176 can be started after a processing delay. See, for example, FIGs 3A and 3B. In examples, a pre-processing timer 176 can be referred to as a storage timer. In some examples, method 200 comprises determining a pre-processing timer duration 178 and starting the pre-processing timer 176 based, at least in part, on at least one trigger event for pre-processing at least one LTM candidate cell configuration 168. In examples, determining a pre-processing timer duration 178 comprises at least one of the following: retrieving the pre-processing timer duration 178 from at least one memory 134, or receiving the pre-processing timer duration 178 from an access node 120. For example the pre-processing timer duration 178 can be received in ASN.1 formatted configurations such as RRC message or RRCReconfiguration message, or in UE capability message such as UECapabilitylnformation. For example, the pre-processing timer duration 178 can be pre-determined, for example defined in at least one technical specification, and can be stored in at least one memory of the device during manufacture, for example. The timer duration may be indicated in capability information transmitted towards the access node 120. For example, the pre-processing timer duration 178 can be configured at the terminal node 110 by an access node 120 using, for example, at least one configuration message. In some examples, the pre-processing timer duration 178 can have a pre-determined default value which can be changed by an access node 120 using, for example, at least one configuration message. In examples, determining the pre-processing timer duration 178 comprises determining the pre-processing timer duration 178 based, at least in part, on the type of trigger event 174 that starts the pre-processing timer 176. For example, the pre-processing timer duration 178 can have a duration of X milliseconds if the trigger event 174 is type A, and can have a duration of Y milliseconds if the trigger event 174 is type B and so on. For example, the pre-processing timer duration 178 can have a first duration if the trigger event 174 comprises receiving the at least one LTM candidate cell configuration 168 and can have a second, different duration if the trigger event 174 comprises receiving TCI state activation and so on. In some examples, determining a pre-processing timer duration 178 comprises retrieving the pre-processing timer duration 178 from at least one memory 134, and transmitting an indication of the determined pre-processing timer duration 178 towards at least one access node 120. Accordingly, in examples, the terminal node 110 can inform the access node 120 of the pre-processing timer duration 178. For example, the terminal node 110 can transmit capability information towards an access node 120 to inform the access node 120 of the pre-processing timer duration 178. In some examples, the terminal node 110 selects a pre-processing timer duration 178 from a plurality of pre-defined pre-processing timer durations 178 and transmits an indication of the selected pre-processing timer duration 178 towards an access node 120. In examples, the duration of the pre-processing timer 178 is determined based, at least in part, on the duration of at least one different timer. For example, if there is another timer running for example for TCI state remaining active, early estimated TA to remain valid, or LTM candidate cell configuration to remain applicable, the preprocessing timer duration 178 can be linked to the at least one different timer and can, for example, expire when the at least one different timer expires. In some examples, method 200 comprises extending the duration of the preprocessing timer 176 based, at least in part, on at least one trigger event 174 for preprocessing at least one LTM candidate cell configuration 168. The terminal node 110 can, in examples, extend the duration of the pre-processing timer 176 based, at least in part, on at least one trigger event 174 for pre-processing at least one LTM candidate cell configuration 168 occurring. For example, a pre-processing timer 176 can be started in response to receiving a LTM TCI state activation and can be extended in response to receiving PDCCH order. See, for example, FIG. 5. By way of example, reference is made to the example of FIG. 3A. FIG. 3A shows an example of a timeline with time increasing from left to right. FIG. 3A is an example of the use of a pre-processing timer 176. In the example of FIG. 3A, a trigger event 174 takes place. In the illustrated example the trigger event 174 is receiving at least one LTM candidate cell configuration 168. In FIG. 3A, a processing delay 186 is implemented to allow pre-processing of the at least one LTM candidate cell configuration 168 and then a pre-processing timer 176 is started 184. In the illustrated example, the pre-processing timer 176 applies to all of the at least one LTM candidate cell configuration 168. However, in some examples the preprocessing timer 176 applies to a subset of the at least one LTM candidate cell configuration 168. In examples, a plurality of pre-processing timers 176 can be used in relation to different subsets of the at least one LTM candidate cell configuration 168. In the example of FIG. 3A, the pre-processing timer 176 has a duration 178A, and in the absence of any further trigger events 174, the pre-processing timer expires at 188A. However, in examples, a second trigger event 174 occurs after the pre-processing timer 176 has been started. In the example of FIG. 3A the second trigger event 174 is receiving of TCI state activation. In such examples, the duration of the pre-processing timer 176 is extended in response to the second trigger event 174 and therefore the pre-processing timer 176 does not expire at 188A. In the illustrated example, the pre-processing timer 176 is restarted in response to the second trigger event 174, and therefore has duration 178B from that point in time. In such examples the pre-processing timer 176 expires at 188B. Returning to the discussion of the example of FIG. 2, in some examples method 200 comprises stopping the pre-processing timer 176 based, at least in part, on fulfilment of at least one end condition 180. Accordingly, in examples, the terminal node 110 can stop the pre-processing timer 176 before the duration 178 has expired based, at least in part, on fulfilment of at least one end condition 180. The at least one end condition 180 can comprise any suitable condition or conditions. For example, the at least one end condition 180 can be based, at least in part, on receiving or transmitting at least on signal, the at least one end condition 180 can be associated with LTM, for example, at least one state associated with LTM, at least one action associated with LTM and so on. In some examples, the at least one end condition 180 comprises at least one of the following: TCI state deactivation, early estimate TA becomes invalid, or cell becomes undetectable. By way of example, reference is made to the example of FIG. 3B. FIG. 3B is similar to the example of FIG. 3A. However, in the example of FIG. 3B an end condition 180 is fulfilled prior to the full duration 178 of the pre-processing timer 176 expiring. In the illustrated example, the pre-processing timer 176 therefore expires at 188A, rather than 188B due to the occurrence of the end condition 180. If the preprocessing timer 176 has been stopped, for example due to an end condition 180, it can be considered that the pre-processing timer 176 has expired. Returning to the discussion of the example of FIG. 2, at block 210 method 200 comprises in response to determining that the at least one condition 172 has been satisfied, stopping storing at least one of the pre-processed at least one LTM candidate cell configuration 168. Consequently, FIG. 2 illustrates a method 200 comprising determining whether the at least one condition 172 has been satisfied and in response to determining that the at least one condition 172 has been satisfied, stopping storing at least one of the pre-processed at least one LTM candidate cell configuration 168. In examples, the pre-processed LTM candidate cell configuration(s) 168 associated with the at least one condition 172 are no longer stored. For example, if the at least one condition is TCI state deactivation, it is the pre-processed LTM candidate cell configuration 168 associated with the TCI state deactivation that is no longer stored. Similarly, if the at least one condition 172 is expiry of a pre-processing timer 176 it is the pre-processed LTM candidate cell configuration(s) 168 associated with the expired pre-processing timer 176 that are no longer stored, which can be all of the pre-processed LTM candidate cell configurations or a subset of the pre-processed LTM candidate cell configurations 168 for example. In examples, stopping storing the at least one of the pre-processed at least one LTM candidate cell configuration means that the memory used to store the at least one of the pre-processed at least one LTM candidate cell configuration is again available for use. In some examples, stopping storing comprises at least one of the following: releasing the memory used to store the pre-processed at least one LTM candidate cell configuration 168, removing a stored reference to the memory used to store the pre-processed at least one LTM candidate cell configuration 168, or deleting the pre-processed at least one LTM candidate cell configuration 168. In examples, the access node 120 can transmit a cell switch command 182 towards the terminal node 120 to cause the terminal node 110 to perform cell switch. If the cell switch command 182 is received while the pre-processed LTM candidate cell configuration 168 for the target cell involved in the cell switch is still stored at the terminal node 110, for example while a pre-processing timer 176 is still running, the terminal node 110 is not allowed time for processing of the target cell configuration during cell switch. However, If the cell switch command 182 is received while the pre-processed LTM candidate cell configuration 168 for the target cell involved in the cell switch is not still stored at the terminal node 110, for example after a pre-processing timer 176 has expired, the terminal node 110 is allowed time for processing of the target cell configuration during cell switch. With reference to the example of FIG. 2, the cell switch command 182 can, for example, be received at block 212A which, in the illustrated example, is while the at least one pre-processed LTM candidate cell configuration 168 is still stored and therefore in this example the terminal node 110 is not allowed time for processing of the target cell configuration during cell switch. However, the cell switch command 182 can, for example, be received at block 212B which, in the illustrated example, is after the at least one condition 172 is satisfied and the at least one pre-processed LTM candidate cell configuration 168 is no longer stored. Therefore, in this example, the terminal node 110 is allowed time for processing of the target cell configuration during cell switch. In some examples, method 200 comprises continuing to store at least one of the pre-processed at least one LTM candidate cell configurations 168 after cell switch to at least one candidate cell associated with one of the at least one LTM candidate cell configurations 168. This allows, for example, for other pre-processed LTM candidate cell configurations to be useable if, for example, a subsequent cell switch is made. In some examples, the terminal node 110 can continue to store the pre-processed candidate cell configuration 168 associated with the cell to which the cell switch has been performed. In some examples, the at least one LTM candidate cell configuration 168 comprises a plurality of LTM candidate cell configurations 168, and the method 200 comprises stopping storing the pre-processed LTM candidate cell configuration 168 associated with a cell to which a cell switch is performed, and continuing storing at least one pre-processed LTM candidate cell configuration 168 associated with at least one cell to which cell switch was not performed. Examples of the disclosure are advantageous and / or provide technical benefits. For example, examples of the disclosure provide for a terminal node, such as a UE, to not have to unnecessarily store candidate cell configurations when it / they are not needed. For example, examples of the disclosure enable efficient use of UE resources, such as memory. For example, examples of the disclosure enable efficient use of UE resources, such as memory enabling UE to have reduced power consumption. For example, examples of the disclosure allow the network to configure LTM candidate cells and, for example, activate TCI states a long time before the cell switch is needed. The network can know what kind of cell switch delay to expect depending, for example, on whether the pre-processing timer is still running or not. For example, examples of the disclosure introduce a maximum time the UE is required to store a pre-processed candidate cell configuration before cell switch. FIG. 4 illustrates and example of a method 400. Method 400 can be performed by any suitable apparatus comprising any suitable means for performing method 400, for example an apparatus as described in relation to FIG. 6A and / or 6B. In examples, method 400 can be performed by a terminal node 110, such as a UE 164, or by at least one control device configured to control the functioning thereof. At block 402, method 400 comprises receiving at least one LTM candidate cell configuration 168. At block 404, method 400 comprises pre-processing the at least one LTM candidate cell configuration 168. At block 406, method 400 comprises storing the pre-processed at least one LTM candidate cell configuration 172 in at least one memory 134 until at least one condition 172 is satisfied. Consequently, FIG. 4 illustrates a method 400 comprising: receiving at least one LTM candidate cell configuration 168; pre-processing the at least one LTM candidate cell configuration 168; and storing the pre-processed at least one LTM candidate cell configuration 172 in at least one memory 134 until at least one condition 172 is satisfied. FIG. 5 illustrates an example of signaling between entities. FIG. 5 also illustrates a method 500. FIG. 5 is similar to the example of FIG. 2, however in the example of FIG. 5 a source transmission / reception point 190 and two target transmission / reception points 192A, 192B are illustrated. In FIG. 5 an example of how the pre-processing timer 176 is used in the LTM procedure is shown. For purposes of clarity, only the significant parts of the procedure are included in the example of FIG. 5. In the example of FIG. 5, the pre-processing timer 176 starts after the UE has completed the pre-processing based on any predefined trigger 174, in the example of FIG. 5 either based on LTM candidate cell configuration, TCI state activation or PDCCH order. In the example of FIG. 5, after timer expiration 188, it is restarted if a new trigger happens. If cell switch happens while the timer is running, the UE is not given time during cell switch to process the candidate cell configuration (T_LTM_RRC-processing = 0). If cell switch happens when the timer has expired, UE is allowed time to process the candidate cell configuration during cell switch (T_LTM_RRC-processing >0, for example 10 ms). In block 1 of FIG. 5, UE 164 indicates to the network that it supports pre-processing capability of maxLTMCandidateConfig candidate cell configurations and the maximum number of serving cells and cells to be pre-processed is maxServingAndCandidateCells. In block 2 of FIG. 5, network sends LTM candidate cell configuration 168 with configuration of cells tTRP1 and tTRP2. In the first example of FIG. 5, LTM candidate cell configuration triggers pre-processing of one or more cells in the LTM candidate cell configuration (tTRP1, tTRP2 or both depending on the configuration). In FIG. 5, after the delay 186 it takes to pre-process the configuration(s), preprocessing timer 176 starts running. If the timer 176 expires before another preprocessing trigger 174 or cell switch command 182, the UE 164 is allowed to discard the stored pre-processed candidate cell configuration(s) 168. In the first example of FIG. 5, the timer 176 expires before there is a cell switch command 182. In block 3 of FIG. 5, network sends TCI state activation for tTRP1. Because, in this example, the timer 176 has expired, the UE 164 will pre-process tTRP1 candidate cell configuration triggered by TCI state activation for this cell, and after the processing delay, the timer is restarted for tTRP1. In block 4, network sends PDCCH order for tTRP1. Because the pre-processing timer 176 is still running based on TCI state activation, PDCCH order restarts the timer after UE has processed tTRP1 configuration. The UE 164 continues to store the pre-processed candidate cell configuration fortTRPI. Cell switch: Option 1: In block 5 of FIG. 5, network sends cell switch command 182 with tTRP1 as the target cell to the UE 164. Because the pre-processing timer is still running, the UE is not allowed time to process tTRP1 candidate cell configuration during cell switch, and UE completes RACH-less or RACH-based cell switch with T_LTM_RRC-processing = 0 in block 6. Option 2: In block 7 of FIG. 5, network sends cell switch command with tTRP1 as the target cell to the UE. Because in this option the pre-processing timer 176 has expired, the UE 164 is allowed time to process tTRP1 candidate cell configuration during cell switch, and UE completes RACH-less or RACH-based cell switch with T_LTM_RRC-processing = 10 ms in block 8. In examples, when the UE is triggered to pre-process a LTM candidate cell configuration before LTM cell switch based on any predefined condition or configuration, the UE is only required to store the pre-processed configuration for a predefined time duration. In other words, in examples, after the UE has pre-processed a candidate cell configuration based on any predefined trigger, the UE starts a pre-processing timer that defines how long to store the pre-processed configuration. In examples, if cell switch does not happen before the pre-processing timer expires, the UE is allowed to discard (not continue to store) the pre-processed configuration when the pre-processing timer expires. In examples, if the UE receives another trigger to pre-process the configuration of the same cell, the timer is re-started. In some examples the timer may be related also to some condition other than cell switch, where the timer expires if a predefined condition is fulfilled, for example: TCI state becomes deactivated (through MAC-CE or some other condition) TA estimated before cell switch becomes invalid Cell becomes undetectable In some examples, the timer may only be related to one or more of the listed conditions and not have a predefined value or have value infinite. In examples, when the UE receives cell switch command, If the timer is running, the UE is not allowed time for processing of the target cell configuration during cell switch, If the timer is not running, the UE is allowed time for processing of the target cell configuration during cell switch. In some examples, the pre-processing timer may continue to run even after cell switch either for any cell for which the timer is still running, or it may only continue to run only for other cells than the one to which cell switch is performed. In examples, the value for the timer may be predefined in the standard or signaled to the UE by the network. In the latter case the timer value may be for example configured in the LTM candidate cell configuration, and there may be different options for the timer duration. In examples, the timer may also be UE dependent and defined as a capability, where the options are: To implement the timer value in the existing fast ASN.1 decoding and validity check capability as a new component, or To add an additional capability to define how long the UE is able to store the decoded candidate cell configurations. In both cases, the capability may allow a set of values of which the UE may select what to report to the network, for example: preprocessingTimer = {160 ms, 1280 ms, 100 s, 300 s, infinite}, where infinite means that the UE does not have any limitation for how long it will store the pre-procesed configuration(s). In examples, the value for the timer may be defined independently or it may be tied to some other condition. For example, if there is another timer running for example for TCI state remaining active, early estimated TA to remain valid, or LTM candidate cell configuration to remain applicable, the pre-processing timer may follow this other timer and expire while the other timer expires. Example: TCI state remains active only for Y ms after TCI state activation. If TCI state activation triggers pre-processing, pre-processing timer expires after Y ms and the UE is allowed to discard the pre-processed configuration. In some examples, the timer may expire at the event of: TCI state deactivation Early estimated TA to become invalid Cell becoming undetected or the timer may not have a predefined value and the UE is just allowed to discard the pre-processed configuration when some of those conditions become fulfilled. In some examples, the timer will not expire at cell switch but continues to run after cell switch. This option is beneficial, for example, for the case when subsequent LTM cell switch is considered. The timer may continue to run after cell switch for all cells for which the timer is still running (target cell and others), or the timer may only continue to run for the cells that are not the target cell of the cell switch. For example, UE is triggered to pre-process and store cell 1 configuration. While the timer is running for cell 1, network sends cell switch command to cell 2. UE performs cell switch to cell 2 while it continues to store cell 1 configuration. If cell switch to cell 1 happens while the timer is still running after the cell switch to cell 2, the UE is not allowed time for processing cell 1 configuration during the cell switch. In examples, the timer may be used associated to any of the pre-processing triggers used as examples herein, or it may apply under any other trigger. The timer may also apply for all applicable triggers or only for some of the triggers. Different values for the timer may also be defined depending on which trigger is used. Below is an example how the timer may be captured in a technical specification, for example in the RAN4 specification (TS 38.133): Tltm-RRC-processing is the time for ASN.l decoding and validity / compliance check for the RRC configuration of tire LTM target cell indicated in the LTM cell switch coimnand. • TLTM-RRC-processing = 0. if tire UE supports [earlyDecodingAndValidityCheck] capability, and at least one of the following conditions is met within X ms before reception of the cell switch command: - UE has received LTM candidate cell configuration and the number of candidate cells in the LTM candidate cell configuration does not exceed [number of candidate cells for early ASN.l decoding and validity) check}, - UE has received LTM candidate cell TCI state activation command for the target cell at least Tharq + 13 ms before the LTM cell switch command, and the number of candidate cells with TCI state(s) in LTM candidate cell active TCI state list does not exceed [number of candidate cells for early ASN. 1 decoding and validity check], - UE lias received PDCCH order for early RACK for the target cell. [FFS further conditions] - [FFS: SCell is not part of the cell switch.] Otherwise TLTM-RRC-processmg = 10 ms. If the timer value is signalled to the UE by the network, it can be included in LTM candidate cell configuration, in which case the requirement impact may be for example: Tltm RRC-processing is the time for ASN.l decoding and validity / compliance check for the RRC configuration of the LTM target cell indicated in the LTM cell switch command. • TLTM-RRC-processing = 0, if the UE supports [earlyDecodingAndValidityCheck] capability’, and at least one of the following conditions is met: - UE has received LTM candidate cell configuration and the number of candidate cells in the LTM candidate cell configuration does not exceed [number of candidate cells for early ASN. 1 decoding and validity check], - UE is configured with fastRRCProcessingTimer for the cell indicated in the LTM cell switch command and the timer is running: - Alternative 1: at the time of receiving the MA C CE cell switch command - Alternative 2: at the lime of receiving M AC CE cell switch command + decoding time of the MAC CE (MAC CE + 3 ms) - UE has received LTM candidate cell TCI state activation command for the target cell at least Tharq + 13 ms before the LTM cell switch command, and the number of candidate cells with TCI state(s) in LTM candidate cell active TCI state list does not exceed [number of candidate cells for early ASN. 1 decoding and validity check], - UE has received PDCCH order for early RACH for the target cell. [FES'further conditions] - [FFS: SCell is not part of the cell switch.] Otherwise TLTM~RRc>prOceSsmg = 10 ms. FIG. 6A illustrates an example of a block diagram of an apparatus 130. The apparatus 130 may be a controller of an apparatus or device such as a terminal node 110, for example a UE 170, or an access node 120. The apparatus 130 may be considered a controller or controller device. Implementation of a controller 130 may be as controller circuitry. The controller 130 may be implemented in hardware alone, have certain aspects in software including firmware alone or can be a combination of hardware and software (including firmware). As illustrated in Fig 6A the controller 130 may be implemented using instructions that enable hardware functionality, for example, by using executable instructions 136 in a general-purpose or special-purpose processor 132 that may be stored on a machine readable storage medium (disk, memory etc.) to be executed by such a processor 132. The processor 132 is configured to read from and write to the memory 134. The processor 132 may also comprise an output interface via which data and / or commands are output by the processor 132 and an input interface via which data and / or commands are input to the processor 132. The memory 134 stores instructions, program, or code 136 that controls the operation of the apparatus 130 when loaded into the processor 132. The computer program instructions, program or code 136, provide the logic and routines that enables the apparatus 130 to perform the methods illustrated in the accompanying FIGs. The processor 132 by reading the memory 134 is configured to load and execute the instructions, program, or code 136. The apparatus 130 comprises: at least one processor 132; and at least one memory 134 storing instructions that, when executed by the at least one processor 132, cause the apparatus at least to: receiving at least one LTM candidate cell configuration 168; pre-processing the at least one LTM candidate cell configuration 168; and storing the pre-processed at least one LTM candidate cell configuration 172 in at least one memory 134 until at least one condition 172 is satisfied. As illustrated in Fig 6A, the instructions, program, or code 136 may arrive at the apparatus 130 via any suitable delivery mechanism 162. The delivery mechanism 162 may be, for example, a machine readable medium, a computer-readable medium, a non-transitory computer-readable storage medium, a computer program product, a memory device, a record medium such as a Compact Disc Read-Only Memory (CD-ROM) or a Digital Versatile Disc (DVD) or a solid-state memory, an article of manufacture that comprises or tangibly embodies the computer program 136. The delivery mechanism may be a signal configured to reliably transfer the computer program 136. The apparatus 130 may propagate or transmit the computer program 136 as a computer data signal. The term “non-transitory” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal ) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM). Computer program instructions for causing an apparatus to perform at least the following or for performing at least the following: receiving at least one LTM candidate cell configuration 168; pre-processing the at least one LTM candidate cell configuration 168; and storing the pre-processed at least one LTM candidate cell configuration 172 in at least one memory 134 until at least one condition 172 is satisfied. The computer program instructions may be comprised in a computer program, a non-transitory computer readable medium, a computer program product, a machine readable medium. In some but not necessarily all examples, the computer program instructions may be distributed over more than one computer program. Although the memory [REF2] is illustrated as a single component / circuitry it may be implemented as one or more separate components / circuitry some or all of which may be integrated / removable and / or may provide permanent / semi-permanent / dynamic / cached storage. In examples the memory 134 comprises a random-access memory 158 and a read only memory 160. In examples the computer program 136 can be stored in the read only memory 158. See, for example, Fig. 6B. Although the processor 132 is illustrated as a single component / circuitry it may be implemented as one or more separate components / circuitry some or all of which may be integrated / removable. The processor 132 may be a single core or multi-core processor. References to ‘computer-readable storage medium’, ‘computer program product’, ‘tangibly embodied computer program’ etc. or a ‘controller’, ‘computer’, ‘processor1 etc. should be understood to encompass not only computers having different architectures such as single / multi- processor architectures and sequential (Von Neumann) / parallel architectures but also specialized circuits such as field-programmable gate arrays (FPGA), application specific circuits (ASIC), signal processing devices and other processing circuitry. References to computer program, instructions, code etc. should be understood to encompass software for a programmable processor or firmware such as, for example, the programmable content of a hardware device whether instructions for a processor, or configuration settings for a fixed-function device, gate array or programmable logic device etc. As used in this application, the term ‘circuitry’ may refer to one or more or all the following: (a) hardware-only circuitry implementations (such as implementations in only analog and / or digital circuitry) and (b) combinations of hardware circuits and software, such as (as applicable): i. a combination of analog and / or digital hardware circuit(s) with software / firmware and ii. any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory or memories that work together to cause an apparatus, such as a mobile phone or server, to perform various functions and (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (for example, firmware) for operation, but the software may not be present when it is not needed for operation. This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the claim element, a baseband integrated circuit for a mobile device or a similar integrated circuit in a server, a cellular network device, or other computing or network device. The blocks illustrated in the accompanying Figs may represent steps in a method and / or sections of code in the computer program [REF3]. The illustration of a particular order to the blocks does not necessarily imply that there is a required or preferred order for the blocks and the order and arrangement of the block may be varied. Furthermore, it may be possible for some blocks to be omitted. Where a structural feature has been described, it may be replaced by means for performing one or more of the functions of the structural feature whether that function or those functions are explicitly or implicitly described. In examples, an apparatus can comprise means for performing one or more methods, or at least part of one or more methods, as disclosed herein. In examples, an apparatus can be configured to perform one or more methods, or at least a part of one or more methods, as disclosed herein. The above-described examples find application as enabling components of: automotive systems; telecommunication systems; electronic systems including consumer electronic products; distributed computing systems; media systems for generating or rendering media content including audio, visual and audio visual content and mixed, mediated, virtual and / or augmented reality; personal systems including personal health systems or personal fitness systems; navigation systems; user interfaces also known as human machine interfaces; networks including cellular, non-cellular, and optical networks; ad-hoc networks; the internet; the internet of things; virtualized networks; and related software and services. The apparatus can be provided in an electronic device, for example, a mobile terminal, according to an example of the present disclosure. It should be understood, however, that a mobile terminal is merely illustrative of an electronic device that would benefit from examples of implementations of the present disclosure and, therefore, should not be taken to limit the scope of the present disclosure to the same. While in certain implementation examples, the apparatus can be provided in a mobile terminal, other types of electronic devices, such as, but not limited to: mobile communication devices, hand portable electronic devices, wearable computing devices, portable digital assistants (PDAs), pagers, mobile computers, desktop computers, televisions, gaming devices, laptop computers, cameras, video recorders, GPS devices and other types of electronic systems, can readily employ examples of the present disclosure. Furthermore, devices can readily employ examples of the present disclosure regardless of their intent to provide mobility. The term ‘comprise’ is used in this document with an inclusive not an exclusive meaning. That is any reference to X comprising Y indicates that X may comprise only one Y or may comprise more than one Y. If it is intended to use ‘comprise’ with an exclusive meaning then it will be made clear in the context by referring to ‘comprising only one...’ or by using ‘consisting.’ In this description, the wording ‘connect’, ‘couple’ and ‘communication’ and their derivatives mean operationally connected / coupled / in communication. It should be appreciated that any number or combination of intervening components can exist (including no intervening components), i.e., to provide direct or indirect connection / coupling / communication. Any such intervening components can include hardware and / or software components. As used herein, the term "determine / determining" (and grammatical variants thereof) can include, not least: calculating, computing, processing, deriving, measuring, 35 investigating, identifying, looking up (for example, looking up in a table, a database, or another data structure), ascertaining and the like. Also, "determining" can include receiving (for example, receiving information), accessing (for example, accessing data in a memory), obtaining and the like. Also," determine / determining" can include resolving, selecting, choosing, establishing, and the like. In this description, reference has been made to various examples. The description of features or functions in relation to an example indicates that those features or functions are present in that example. The use of the term ‘example’ or ‘for example’ or ‘can’ or ‘may’ in the text denotes, whether explicitly stated or not, that such features or functions are present in at least the described example, whether described as an example or not, and that they can be, but are not necessarily, present in some of or all other examples. Thus ‘example’, ‘for example’, ‘can’, or ‘may’ refers to a particular instance in a class of examples. A property of the instance can be a property of only that instance or a property of the class or a property of a sub-class of the class that includes some but not all the instances in the class. It is therefore implicitly disclosed that a feature described with reference to one example but not with reference to another example, can where possible be used in that other example as part of a working combination but does not necessarily have to be used in that other example. As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or” mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements. Although examples have been described in the preceding paragraphs with reference to various examples, it should be appreciated that modifications to the examples given can be made without departing from the scope of the claims. Features described in the preceding description may be used in combinations other than the combinations explicitly described above. Although functions have been described with reference to certain features, those functions may be performable by other features whether described or not. The description of a feature, such as an apparatus or a component of an apparatus, configured to perform a function, or for performing a function, should additionally be considered to also disclose a method of performing that function. For example, description of an apparatus configured to perform one or more actions, or for performing one or more actions, should additionally be considered to disclose a method of performing those one or more actions with or without the apparatus. Although features have been described with reference to certain examples, those features may also be present in other examples whether described or not. The term ‘a’, ‘an’ or ‘the’ is used in this document with an inclusive not an exclusive meaning. That is any reference to X comprising a / an / the Y indicates that X may comprise only one Y or may comprise more than one Y unless the context clearly indicates the contrary. If it is intended to use ‘a’, ‘an’ or ‘the’ with an exclusive meaning then it will be made clear in the context. In some circumstances the use of ‘at least one’ or ‘one or more’ may be used to emphasis an inclusive meaning but the absence of these terms should not be taken to infer any exclusive meaning. The presence of a feature (or combination of features) in a claim is a reference to that feature or (combination of features) itself and to features that achieve substantially the same technical effect (equivalent features). The equivalent features include, for example, features that are variants and achieve substantially the same result in substantially the same way. The equivalent features include, for example, features that perform substantially the same function, in substantially the same way to achieve substantially the same result. In this description, reference has been made to various examples using adjectives or adjectival phrases to describe characteristics of the examples. Such a description of a characteristic in relation to an example indicates that the characteristic is present in some examples exactly as described and is present in other examples substantially as described. The above description describes some examples of the present disclosure however those of ordinary skill in the art will be aware of possible alternative structures and method features which offer equivalent functionality to the specific examples of such structures and features described herein above and which for the sake of brevity and clarity have been omitted from the above description. Nonetheless, the above description should be read as implicitly including reference to such alternative structures and method features which provide equivalent functionality unless such alternative structures or method features are explicitly excluded in the above description of the examples of the present disclosure. Whilst endeavoring in the foregoing specification to draw attention to those features believed to be of importance the Applicant may seek protection via the claims in respect of any patentable feature or combination of features hereinbefore referred to and / or shown in the drawings whether or not emphasis has been placed thereon. l / we claim:

Claims

1. An apparatus comprising means for:receiving at least one L1 / L2 triggered mobility, LTM, candidate cell configuration;pre-processing the at least one LTM candidate cell configuration; and storing the pre-processed at least one LTM candidate cell configuration in at least one memory until at least one condition is satisfied.

2. An apparatus as claimed in claim 1, wherein the means are configured to: determine whether the at least one condition has been satisfied; and in response to determining that the at least one condition has been satisfied, stop storing at least one of the pre-processed at least one LTM candidate cell configuration.

3. An apparatus as claimed in claim 1 or 2, wherein the at least one LTM candidate cell configurations as at least one LTM candidate cell radio resource control, RRC, configuration.

4. An apparatus as claimed in claim 2, or 3 wherein stopping storing comprises at least one of the following: releasing the memory used to store the pre-processed at least one LTM candidate cell configuration for re-use, removing a stored reference to the memory used to store the pre-processed at least one LTM candidate cell configuration, or deleting the pre-processed at least one LTM candidate cell configuration.

5. An apparatus as claimed in any preceding claim, wherein the means are configured to pre-process the at least one LTM candidate cell configurations based, at least in part, on at least one trigger event.

6. An apparatus as claimed in claim 5, wherein the at least one trigger event comprises at least one of the following:receiving the at least one LTM candidate cell configuration,receiving TCI state activation, orreceiving physical downlink control channel, PDCCH, order.

7. An apparatus as claimed in any preceding claim, wherein the at least one condition comprises at least one of the following:expiry of a pre-processing timer,transmission configuration indicator, TCI, state deactivation, early estimated timing advance, TA, becomes invalid, or cell becomes undetectable.

8. An apparatus as claimed in claim 7, wherein the means are configured to determine a pre-processing timer duration and to start the pre-processing timer based, at least in part, on at least one trigger event for pre-processing at least one LTM candidate cell configuration.

9. An apparatus as claimed in claim 8, wherein determining a pre-processing timer duration comprises at least one of the following:retrieving the pre-processing timer duration from at least one memory, or receiving the pre-processing timer duration from an access node.

10. An apparatus as claimed in claim 8 or 9, wherein determining the preprocessing timer duration comprises determining the pre-processing timer duration based, at least in part, on the type of trigger event that starts the pre-processing timer.

11. An apparatus as claimed in claim 8, 9, or 10, wherein determining a preprocessing timer duration comprises retrieving the pre-processing timer duration from at least one memory, and the means are configured to transmit an indication of the determined pre-processing timer duration towards at least one access node.

12. An apparatus as claimed in any of claims 8 to 11, wherein the pre-processing timer duration is determined based, at least in part, on the duration of at least one different timer.

13. An apparatus as claimed in any of claims 8 to 12, wherein the means are configured to extend the duration of the pre-processing timer based, at least in part, on at least one trigger event for pre-processing at least one LTM candidate cell configurations.

14. An apparatus as claimed in any of claims 8 to 13, wherein the means are configured to stop the pre-processing timer based, at least in part, on fulfilment of at least one end condition.

15. An apparatus as claimed in claim 14, wherein the at least one end condition comprises at least one of the following:transmission configuration indicator, TCI, state deactivation, early estimated timing advance, TA, becomes invalid, or cell becomes undetectable.

16. An apparatus as claimed in any preceding claim, wherein the means are configured to continue to store at least one of the pre-processed at least one LTM candidate cell configurations after cell switch to at least one candidate cell associated with one of the at least one LTM candidate cell configurations.

17. An apparatus as claimed in any preceding claim, wherein the at least one LTM candidate cell configuration comprises a plurality of LTM candidate cell configurations, and the means are configured to stop storing the pre-processed LTM candidate cell configuration associated with a cell to which a cell switch is performed, and to continue storing at least one pre-processed LTM candidate cell configuration associated with at least one cell to which cell switch was not performed.

18. A method comprising:receiving at least one L1 / L2 triggered mobility, LTM, candidate cell configuration;pre-processing the at least one LTM candidate cell configuration; and storing the pre-processed at least one LTM candidate cell configuration in at least one memory until at least one condition is satisfied.

19. A method as claimed in claim 18, comprising:determining whether the at least one condition has been satisfied; and in response to determining that the at least one condition has been satisfied, stopping storing at least one of the pre-processed at least one LTM candidate cell configuration.

20. A method as claimed in claim 18 or 19, wherein the at least one LTM candidate cell configurations is at least one LTM candidate cell radio resource control, RRC, configuration.

21. A method as claimed in claim 18, 19, or 20 wherein stopping storing comprises at least one of the following: releasing the memory used to store the pre-processed at least one LTM candidate cell configuration for re-use, removing a stored reference to the memory used to store the pre-processed at least one LTM candidate cell configuration, or deleting the pre-processed at least one LTM candidate cell configuration.

22. A method as claimed in any of claims 18 to 22, comprising pre-processing the at least one LTM candidate cell configurations based, at least in part, on at least one trigger event.

23. A method as claimed in claim 22, wherein the at least one trigger event comprises at least one of the following:receiving the at least one LTM candidate cell configuration, receiving TCI state activation, orreceiving physical downlink control channel, PDCCH, order.

24. A computer program comprising instructions which, when executed by an apparatus, cause the apparatus at least to perform:receiving at least one L1 / L2 triggered mobility, LTM, candidate cell configuration;pre-processing the at least one LTM candidate cell configuration;storing the pre-processed at least one LTM candidate cell configuration in at least one memory until at least one condition is satisfied.

25. A computer program as claimed in claim 24 comprising instructions which, when executed by an apparatus, cause the apparatus at least to perform: determining whether the at least one condition has been satisfied; and5 in response to determining that the at least one condition has been satisfied,stopping storing at least one of the pre-processed at least one LTM candidate cell configuration.10

Images