EP4612964A1

EP4612964A1 - Methods and apparatuses for handling of secondary cell group at the execution of a layer 1/layer 2 triggered mobility cell switch

Info

Publication number: EP4612964A1
Application number: EP23805206.2A
Authority: EP
Inventors: Antonino ORSINO; Icaro Leonardo DA SILVA; Stefan Wager; Jens Bergqvist
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2022-11-04
Filing date: 2023-11-01
Publication date: 2025-09-10
Also published as: WO2024096795A1; AU2023372520A1; CN120303980A

Abstract

Embodiments described herein relate to methods and apparatuses for enabling performance of actions in relation to a first secondary cell group at the execution of a Layer 1 (L1)/Layer 2, L2, triggered mobility cell switch. A method performed by a user equipment in communication with a source node in a Master Cell Group, MCG comprises executing a layer 1/layer 2 based inter-cell mobility, LTM, cell switch procedure from the source node to a target node, and after or during execution of the LTM cell switch procedure, performing one or more actions in relation to a first Secondary Cell Group.

Description

METHODS AND APPARATUSES FOR HANDLING OF SECONDARY CELL GROUP AT THE EXECUTION OF A LAYER 1/LAYER 2 TRIGGERED MOBILITY CELL SWITCH TECHNICAL FIELD [1] Embodiments described herein relate to methods and apparatuses for enabling performance of actions in relation to a first secondary cell group at the execution of a Layer 1 (L1)/Layer 2 (L2) triggered mobility cell switch. BACKGROUND [2] L1/L2-triggered mobility [3] In 3GPP Release 18, a work item known as Further NR mobility enhancements has been agreed. This work item includes a technical area entitled L1/L2-based inter-cell mobility. According to the Work Item Description, WID, RP-222332, “Further New Radio (NR) mobility enhancements”, MediaTek, 3GPP TSG RAN Meeting #97-e, Electronic Meeting, September 12-16, 2022, when the user equipment (UE) moves from the coverage area of one cell to another cell, at some point a serving cell change needs to be performed. Currently serving cell change is triggered by Layer 3 (L3) measurements and is done by Radio Resource Control (RRC) signalling triggered Reconfiguration with Synchronization for change of Primary Cell (PCell) and Primary Secondary Cell (PSCell), as well as release/add for Secondary Cells (SCells) when applicable. All cases involve complete L2 (and L1) resets, leading to longer latency, larger overhead and longer interruption time than beam switch mobility. The goal of L1/L2 based inter-cell mobility is to enable a serving cell change via L1/L2 signalling, in order to reduce the latency, overhead and interruption time. [4] In WID RP-222332 the following is included as one objective of the work: [20] In 3GPP, discussions have started on solutions for L1/L2 based inter-cell mobility (sometimes also referred to as LTM, L1/L2-triggered mobility or lower layer-triggered mobility). [21] A basic principle with L1/L2-triggered mobility is that the UE is pre-configured, by the network, with an RRC configuration per LTM candidate target cell, sometimes also known as a LTM candidate target cell configuration. Such a LTM candidate target cell configuration may be an RRCReconfiguration message or one or more information elements (IEs)/ fields/ parameters such as CellGroupConfig. The UE performs measurements on these candidate LTM candidate target cells and transmits corresponding measurement reports to the network. The network then triggers the execution LTM cell switch in the UE by transmitting a lower layer signal (such as a Medium Access Control (MAC) Control Element (CE) or Downlink Control Information (DCI)), to the UE, which then connects to the target cell and switches to a configuration of an LTM candidate target cell. [22] At the 3GPP RAN2#119-e and RAN2#119bis-e meetings, there were multiple agreements made on L1/L2-triggered mobility, and among these are the following: ^ RAN2 to consider preparation of target cell configurations capable of dynamic switching without need for full configuration. ^ R2 assumption: Rel-18 L1/L2 mobility includes both non-carrier aggregation (CA) (PCell only) and CA scenarios (PCell and SCell). This includes the following cases a) the target PCell/target SCell(s) is not a current serving cell (CA CA scenario with PCell change) b) FFS the target PCell is a current SCell c) FFS the target SCell is the current PCell. ^ DC scenarios are FFS (e.g. PSCell mobility may be a low hanging fruit FFS). ^ A L1/L2 inter-cell mobility candidate (target) configuration is received within an RRC message before the L1/L2 dynamic switch is triggered. ^ RAN2 continues the discussion on the RRC models by focusing on Model 1 and Model 2 and stage-3 details. a. Model 1: One RRCReconfiguration message (or FFS RRCReconfiguration IEs) for each candidate target configuration b. Model 2: One CellGroupConfig IE (FFS additional IEs) for each candidate target configuration ^ RAN2 to use “LTM” as term for the L1/L2-triggered mobility. ^ Use the term “cell switch” for the procedure of triggering change of cells via the LTM feature ^{^} Use the term “Subsequent” LTM for the case when cell switch between L1/L2 mobility candidates is done without RRC reconfiguration in between. ^ RAN2 assumes that sequential L1L2 cell change between Candidates without RRC reconfiguration can be supported. ^ RAN2 assumes that candidate cell configuration can only be modified / released by Network (FFS later whether some optimization should be applied e.g. for release). ^ For L1L2 mobility will support that candidate configurations are delta configurations on top of a reference configuration. FFS if the reference configuration is a separate reference configuration or e.g. the current configuration. ^ For L1L2 mobility, Target Pcell/SCell can be current SCell/PCell, i.e., current SCell/PCell can be configured as candidates. ^ RAN2 assumes L1/2 mobility trigger information is conveyed in a MAC CE, FFS if the MAC CE or a DCI is used for the actual triggering. ^ RAN2 assumes the MAC CE for L1/2 mobility trigger contains at least a candidate configuration index. ^ L1L2 based mobility supports the following CA scenarios: PCell change without SCell change PCell change with SCell change ^ Support NR-DC scenario in L1L2 based mobility, at least for the PSCell change without MN involvement case, i.e. intra-SN. [23] At the RAN3#117-e and RAN3#117bis-e meetings, there were multiple agreements made on L1/L2 based inter-cell mobility, and among these are the following: [24] [25] - Both intra- DU and intra-CU inter-DU scenarios are supported for L1/L2 mobility. [26] -RAN3 will aim for a single solution for network signaling design on L1/L2 based inter-cell mobility to support all agreed scenarios. The details of solution are FFS. [27] -The gNB-CU initiates the L1/L2 mobility configuration procedure. [28] -The configuration of candidate target cell(s) for L1/L2 mobility is initiated by the gNB-CU. [29] -WA: RAN3 assumes that the UE sends the L1 measurement report to the gNB-DU and the gNB-DU triggers UE mobility to a target candidate cell. All details are up to RAN1 and RAN2 discussion. [30] -During L1/L2 handover configuration, the gNB-CU sends the suggested candidate cell(s) to the gNB-DU in UE Context Modification Request procedure, FFS in one message or multiple messages. [31] -The gNB-DU may accept the target cells of L1/L2 handover and responds to the gNB-CU with the access control result in UE Context Modification Response message(s). gNB-DU may accept all or part of the target candidate cells. [32] -gNB-DU initiated L1/L2 handover configuration is not allowed. [33] -The UE sends the lower-layer measurement report to the gNB-DU and the gNB-DU triggers UE mobility to a target candidate cell. [34] -WA: The gNB-DU indicates the gNB-CU about the UE successful access to the target cell by Access Success message. [35] -For inter-DU inter-cell mobility, the UE Context Setup procedure is reused for handover configuration. [36] 3GPP Dual Connectivity [37] In 3GPP Rel-12, the Long Term Evolution (LTE) feature Dual Connectivity (DC) was introduced, to enable the UE to be connected in two cell groups, each controlled by an LTE access node, eNBs, labelled as the Master eNB, MeNB and the Secondary eNB, SeNB. The UE still only has one RRC connection with the network. In 3GPP, the Dual Connectivity (DC) solution has since then been evolved and is now also specified for NR as well as between LTE and NR. With introduction of 5G, the term MR-DC (Multi-Radio Dual Connectivity, see also 3GPP TS 37.340) was defined as a generic term for all dual connectivity options which includes at least one NR access node. Using the MR-DC generalized terminology, the UE is connected in a Master Cell Group (MCG), controlled by the Master Node (MN), and in a Secondary Cell Group (SCG) controlled by a Secondary Node (SN). [38] Further, in MR-DC, when dual connectivity is configured for the UE, within each of the two cell groups, MCG and SCG, carrier aggregation may be used as well. In this case, within the Master Cell Group, MCG, controlled by the master node (MN), the UE may use one PCell and one or more SCell(s). And within the Secondary Cell Group, SCG, controlled by the secondary node (SN), the UE may use one Primary SCell (PSCell, also known as the primary SCG cell in NR) and one or more SCell(s). Figure 1 illustrates dual connectivity combined with carrier aggregation in MR-DC. In NR, the primary cell of a master or secondary cell group is sometimes also referred to as the Special Cell (SpCell). Hence, the SpCell in the MCG is the PCell and the SpCell in the SCG is the PSCell. [39] There are different ways to deploy 5G network with or without interworking with LTE (also referred to as E-UTRA) and evolved packet core (EPC). These different ways to deploy 5G are also known as architecture options. In principle, NR and LTE can be deployed without any interworking, denoted by NR stand-alone (SA) operation, also known as architecture option 2, that is gNB in NR can be connected to 5G core network (5GC) and eNB in LTE can be connected to EPC with no interconnection between the two, also known as architecture option 1. [40] On the other hand, the first supported version of NR uses dual connectivity, denoted as EN- DC (E-UTRAN-NR Dual Connectivity), also known as architecture option 3, as depicted in Figure 2. In such a deployment, dual connectivity between NR and LTE is applied, where the UE is connected with both the LTE radio interface (LTE Uu in the figure) to an LTE access node and the NR radio interface (NR Uu in the figure) to an NR access node. Further, in EN- DC, the LTE access node acts as the master node (in this case known as the Master eNB, MeNB), controlling the master cell group, MCG, and the NR access node acts as the secondary node (in this case sometimes also known as the Secondary gNB, SgNB), controlling the secondary cell group, SCG. The SgNB has a user plane connection S1-U to the core network (EPC). The control plane connection S1-C to the core network (EPC) is instead is provided by the MeNB. This is also called as “Non-standalone NR" or, in short, "NSA NR". Notice that in this case the functionality of an NR cell is limited and would be used for connected mode UEs as a booster and/or diversity leg, but an RRC_IDLE UE cannot camp on these NR cells. In EN-DC, there is no connection to the 5G core network (5GC). [41] With the introduction of 5GC, other options may be also valid. As mentioned above, option 2 supports stand-alone NR deployment where gNB is connected to 5GC. Similarly, LTE can also be connected to 5GC using option 5 (also known as eLTE, E-UTRA/5GC, or LTE/5GC and the node can be referred to as an ng-eNB). In these cases, both NR and LTE are seen as part of the NG-RAN (and both the ng-eNB and the gNB can be referred to as NG-RAN nodes). [42] It is worth noting that, there are also other variants of dual connectivity between LTE and NR which have been standardized as part of NG-RAN connected to 5GC. Under the MR-DC umbrella, we have: [43] EN-DC (also known as architecture option 3): LTE is the master node and NR is the secondary node (EPC CN employed, as depicted in Figure 2) [44] NE-DC (also known as architecture option 4): NR is the master node and LTE is the secondary (5GC employed) [45] NGEN-DC (also known as architecture option 7): LTE is the master node and NR is the secondary (5GC employed) [46] NR-DC (variant of architecture option 2): Dual connectivity where both the master node, MN, controlling the MCG, and the secondary node, SN, controlling the SCG, are NR (5GC employed, as depicted in Figure 3). [47] In NR-DC, depicted in Figure 3, the secondary node (NR SN) is a gNB, which provides a NR radio interface NR Uu to the UE, and has a user plane connection NG-U to the 5G core network (5GC). The master node (NR MN) is also a gNB, which provides an NR radio interface NR Uu to the UE and has the control plane connection NG-C as well as a user plane connection NG-U to the 5G core network (5GC). Between the MN and the SN the Xn interface is used. [48] As migration for these options may differ from different operators, it is possible to have deployments with multiple options in parallel in the same network e.g. there could be eNB base station supporting architecture options 3, 5 and 7 in the same network as NR base station supporting architecture options 2 and 4. In combination with dual connectivity solutions between LTE and NR it is also possible to support CA (Carrier Aggregation) in each cell group (i.e. MCG and SCG) and dual connectivity between nodes on same RAT (e.g. NR-NR DC). For the LTE cells, a consequence of these different deployments is the co-existence of LTE cells associated to eNBs connected to EPC, 5GC or both EPC/5GC. [49] As said earlier, DC is standardized for both LTE and E-UTRA -NR DC (EN-DC). [50] LTE DC and EN-DC are designed differently when it comes to which nodes control what. Basically, there are two options: [51] Centralized solution (like LTE-DC), [52] Decentralized solution (like EN-DC). [53] Figure 4 shows an example of a schematic control plane architecture for LTE DC, EN-DC and NR-DC. The main difference here is that in EN-DC and NR-DC, the Secondary Node, SN, has a separate NR RRC entity. This means that the SN can control the UE as well, sometimes using the NR radio interface NR Uu directly to the UE without the knowledge of the MN. However, often the SN may need to coordinate with the Master Node, MN. The UE has an LTE RRC state in EN-DC and an NR RRC state in NR-DC. Further, in LTE-DC and EN-DC, the control plane interface between MN and SN is X2-C. In LTE-DC, the RRC decisions may be received from MN (MN uses the LTE radio interface LTE Uu to the UE). Note however, the SN may still decides the configuration of the SN, since it is only the SN itself that has knowledge of what kind of , for example, resources or capabilities it has. Further, in LTE-DC, the UE has an LTE RRC state. Further, in NR-DC, the control plane interface between MN and SN is Xn-C. [54] Figure 4 illustrates Control Plane architecture for Dual Connectivity in LTE DC, EN-DC and NR-DC [55] For EN-DC and NR-DC, the major changes compared to LTE DC are: [56] - The introduction of split data radio bearer (DRB) from the SN (known as SN terminated split DRB) [57] - The introduction of split signaling radio bearer (SRB) for RRC. [58] - The introduction of a direct SRB from the SN (also referred to as SCG SRB or SRB3) [59] Figure 5 shows, from network perspective, the user plane protocol architecture in MR-DC with EPC (EN-DC). A bearer may be categorized into a bearer type. Each bearer type is characterized by which radio resources that are involved. For an MCG bearer, only MCG radio resources and Radio Link Control (RLC)+MAC layer entities for the MCG are involved. For an SCG bearer, only SCG radio resources and RLC+MAC layer entities for the SCG are involved. For a split bearer, both MCG and SCG radio resources as well as RLC+MAC layer entities for both the MCG and SCG are involved. Further, a bearer may also be categorized into MN terminated bearers and SN terminated bearers depending on which network node where they are terminated. For MN terminated bearers, the Physical Downlink Control Plane (PDCP) layer entity and the user plane connection to the core network is terminated in the MN. For SN terminated bearers, the PDCP layer entity and the user plane connection to the core network is terminated in the SN. [60] The network can configure either E-UTRA PDCP layer or NR PDCP layer for MN terminated MCG bearers while NR PDCP layer is always used for all other bearers. In this case, the network can configure either E-UTRA PDCP or NR PDCP for MN terminated MCG DRBs while NR PDCP is always used for all other DRBs. [61] Figure 5 illustrates network side protocol termination options for MCG, SCG and split DRBs in MR-DC with EPC (EN-DC). [62] Figure 5 shows, from network perspective, the user plane protocol architecture in MR-DC with 5GC (NGEN-DC, NE-DC and NR-DC). In MR-DC with 5GC, NR PDCP is always used for all DRB types. In NGEN-DC, E-UTRA RLC/MAC is used in the MN while NR RLC/MAC is used in the SN. In NE-DC, NR RLC/MAC is used in the MN while E-UTRA RLC/MAC is used in the SN. In NR-DC, NR RLC/MAC is used in both MN and SN. [63] Figure 6 illustrates Network side protocol termination options for MCG, SCG and split DRBs in MR-DC with 5GC (NGEN-DC, NE-DC and NR-DC) [64] EN-DC capability coordination [65] In EN-DC, capability coordination in terms of UE supported Band Combinations (BC) was performed using configuration restriction information in inter node message signalling. _[66] Having selected the BC for the MCG, the MN signals the allowed BCs for the SCG to the SN in ConfigRestrictInfoSCG of CG-ConfigInfo. ConfigRestrictInfoSCG contains a list of BCs and corresponding FeatureSets that the SN can choose from, see ASN.1 snippet from CG- ConfigInfo below. [67] ConfigRestrictInfoSCG ::= SEQUENCE { [68] allowedBC-ListMRDC BandCombinationInfoList OPTIONAL, [69] powerCoordination-FR1 SEQUENCE { [70] p-maxNR-FR1 P-Max OPTIONAL, [71] p-maxEUTRA P-Max OPTIONAL, [72] p-maxUE-FR1 P-Max OPTIONAL [73] } OPTIONAL, [74] servCellIndexRangeSCG SEQUENCE { [75] lowBound ServCellIndex, [76] upBound ServCellIndex [77] } OPTIONAL, -- Cond SN-Addition [78] maxMeasFreqsSCG-NR INTEGER(1..maxMeasFreqsMN) OPTIONAL, [79] maxMeasIdentitiesSCG-NR INTEGER(1..maxMeasIdentitiesMN) OPTIONAL, [80] ... [81] } [82] [83] BandCombinationInfoList ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombinationInfo [84] [85] BandCombinationInfo ::= SEQUENCE { [86] bandCombinationIndex BandCombinationIndex, [87] allowedFeatureSetsList SEQUENCE (SIZE (1..maxFeatureSetsPerBand)) OF FeatureSetEntryIndex [88] } [89] [90] FeatureSetEntryIndex ::= INTEGER (1.. maxFeatureSetsPerBand) [91] In return, once SN has selected the NR bands for the SCG configuration, it can inform the MN of the selected SCG band combination using selectedBandCombinationNR of CG-Config, see ASN.1 snippet below. [92] CG-Config-IEs ::= SEQUENCE { [93] scg-CellGroupConfig OCTET STRING (CONTAINING RRCReconfiguration) OPTIONAL, [94] scg-RB-Config OCTET STRING (CONTAINING RadioBearerConfig) OPTIONAL, [95] configRestrictModReq ConfigRestrictModReqSCG OPTIONAL, [96] drx-InfoSCG DRX-Info OPTIONAL, [97] candidateCellInfoListSN OCTET STRING (CONTAINING MeasResultList2NR) OPTIONAL, [98] measConfigSN MeasConfigSN OPTIONAL, [99] selectedBandCombinationNR BandCombinationInfoSN OPTIONAL, [100] fr-InfoListSCG FR-InfoList OPTIONAL, [101] candidateServingFreqListNR CandidateServingFreqListNR OPTIONAL, [102] nonCriticalExtension SEQUENCE {} OPTIONAL [103] } SUMMARY [104] There currently exist certain challenge(s). At the last RAN2#119-bis-e meeting, the following was agreed regarding the use of L1/L2 triggered mobility (LTM) with Dual Connectivity (DC): Support NR-DC scenario in L1L2 based mobility, at least for the PSCell change without MN involvement case, i.e. intra-SN. [105] What this agreement means is that LTM on the SCG is independent from the LTM on the MCG but the other way may not have the same conclusion. Also, for the SCG, at the moment, only the case of an intra-SN LTM is supported, and the case where the MN is not involved in the process. [106] Nevertheless, no NR-DC scenario is excluded and thus one critical aspect that needs to be addressed is how to handle the SCG for the case when the LTM is executing within the MCG. Generally speaking, the SCG is added upon request from the MCG and the configuration of the SCG is also dependent on certain restrictions that are signalled (over the X2/Xn) interface by the MCG to the SCG. The restrictions are to ensure that the UE capabilities are not exceeded by the MCG and SCG configurations combined, as explained in the background section above. [107] At the moment, the 3GPP assumption is that the SCG is not impacted by LTM on the MCG. However, the problem is that if changes are made to the MCG during LTM cell switch, e.g. SCells are added, then in order to avoid that UE capabilities are exceeded it may be necessary to release the SCG. In fact, is still not clear if upon the execution of an LTM cell switch procedure within the MCG the SCG should be configured right away, configured but kept in deactivated state, configured with an activated state, or not configured at all (meaning this will be configured in a later moment). For example, it may be that due to capability limitations in the UE, the UE may not be able to support the SCG that was configured before the LTM cell switch, if there are changes in the MCG configuration, e.g. during inter- frequency handover or SCells are added. Also, it is not clear if an SCG can be added by the execution of LTM within the MCG. [108] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. [109] In order to address the above challenges, the embodiments described herein present methods for a User Equipment (UE), to handle (e.g. by release, suspend, add, modify, deactivate, activate, resume)at the execution of LTM cell switch procedure, from a source node to a target node for the Master Cell Group (MCG), at least a Secondary Cell Group (SCG). The SCG may be part of the UE configuration prior to the LTM cell change or it can be part of a LTM candidate target configuration. [110] In one method, the UE receives, from a network node, such as the source network node, the target network node or a third network node, an indication to handle (e.g. by release, suspend, add, modify, deactivate, activate, resume) at least one SCG at the execution of a LTM cell switch procedure within the MCG. [111] In methods, this indication is included in the Lower layer signaling indicating to the UE the LTM cell switch procedure at the MCG received from the source network node. In methods, this indication is included in a lower layer signaling received from the target network node. In methods, this indication is included in an RRC message which includes a LTM candidate target cell, wherein the indication is not within the LTM candidate target cell, but it is associated to it (e.g. included in the same IE), so that the UE knows which candidate configuration is to be modified and which ones are not to be modified. In methods, this indication is included to avoid a UE capability conflict in the UE between the MCG and SCG due to changes in the MCG performed during the LTM cell switch. [112] In methods, the UE transmits, to a network node, such as the source network node, the target network node or a third network node, an indication on which SCG that is part of a LTM candidate target cell configuration has been configured during the execution of a LTM cell switch procedure within the MCG. In methods, this indication is included in a lower layer signaling transmitted to the target network node. [113] The embodiments described herein also present methods for a source network node, such as a source gNB/eNB, acting as a Master Node (MN), providing the UE with a Master Cell Group (MCG), to handle (e.g. by release, suspend, add, modify, deactivate, activate, resume)at least a Secondary Cell Group (SCG). The SCG may be part of the UE configuration prior to the LTM cell change or it can be part of a LTM candidate target configuration, at the execution of LTM cell switch procedure within the MCG. The LTM cell switch procedure may be within the source node or from the source node to a target node. [114] In methods, the source network node determines to handle (e.g. by release, suspend, add, modify, deactivate, activate, resume)a SCG, during the execution of a LTM cell switch procedure within the MCG. [115] In methods, the source network node transmits, to the UE, an indication to handle (e.g. by release, suspend, add, modify, deactivate, activate, resume)an SCG that is part of the UE configuration before the execution of the LTM cell switch or is part of a LTM candidate target cell configuration, during the execution of a LTM cell switch procedure within the MCG. In methods, this indication is included in the Lower layer signaling indicating to the UE the LTM cell switch procedure within the MCG. In methods, this indication is already included in the configuration of a LTM candidate target cell configuration for, or release of, an SCG that is sent to the UE before the execution of a LTM cell switch procedure within the MCG. In methods, this indication is included in a Lower layer signaling indicating the configuration or release of a SCG but that is different from the Lower layer signaling indicating to the UE the execution of the LTM cell switch procedure within the MCG. [116] In methods, the source network node transmits, to the third network node, a request on whether to handle (e.g. by release, suspend, add, modify, deactivate, activate, resume) an SCG, during the execution of a LTM cell switch procedure within the MCG. [117] In methods, the source network node transmits, to the target network node, a request on whether to handle (e.g. by release, suspend, add, modify, deactivate, activate, resume) an SCG, during the execution of a LTM cell switch procedure within the MCG. [118] In methods, the source network node receives, from a third network node, an indication to handle (e.g. by release, suspend, add, modify, deactivate, activate, resume) an SCG, during the execution of a LTM cell switch procedure within the MCG. [119] In methods, the source network node receives, from the target network node, an indication to handle (e.g. by release, suspend, add, modify, deactivate, activate, resume) an SCG, during the execution of a LTM cell switch procedure within the MCG. In methods, the source network node receives, from the UE, an indication about which SCG that is part of a LTM candidate target cell configuration have been configured, at the execution of a LTM cell switch procedure within the MCG. [120] The embodiments described herein also present methods for a target network node, such as a target gNB/eNB, acting as a Master Node (MN), providing the UE with a Master Cell Group (MCG) , to handle (e.g. by release, suspend, add, modify, deactivate, activate, resume) the at least a Secondary Cell Group (SCG). The SCG may be part of the UE configuration prior to the LTM cell change or it can be part of a LTM candidate target configuration, at the execution of LTM cell switch procedure within the MCG. The LTM cell switch procedure may be within the source node or from the source node to a target node. [121] In methods, the target network node determines to handle (e.g. by release, suspend, add, modify, deactivate, activate, resume) the SCG, during the execution of a LTM cell switch procedure within the MCG. [122] In methods, the target network node transmits, to the UE, an indication to handle (e.g. by release, suspend, add, modify, deactivate, activate, resume) the SCG, after the execution of a LTM cell switch procedure within the MCG. In methods, this indication is included in the Lower layer signaling indicating to the UE to configure an SCG. [123] In methods, the target network node receives, from a third network node, a request to handle (e.g. by release, suspend, add, modify, deactivate, activate, resume) an SCG, during the execution of a LTM cell switch procedure within the MCG. [124] In methods, the target network node receives, from the source network node, a request to handle (e.g. by release, suspend, add, modify, deactivate, activate, resume) an SCG, during the execution of a LTM cell switch procedure within the MCG. [125] In methods, the target network node transmits, to the third network node, an indication on whether to handle (e.g. by release, suspend, add, modify, deactivate, activate, resume) an SCG, during the execution of a LTM cell switch procedure within the MCG. [126] In methods, the target network node transmits, to the source network node, an indication on whether to handle (e.g. by release, suspend, add, modify, deactivate, activate, resume) an SCG, during the execution of a LTM cell switch procedure within the MCG. [127] In methods, the target network node receives, from the UE, an indication about which SCG that is part of a LTM candidate target cell configuration have been configured, after the execution of a LTM cell switch procedure within the MCG. [128] The embodiments described herein also present methods for a third network node, such as gNB/eNB, acting as a Secondary Node (SN), providing the UE with a Secondary Cell Group (SCG) , to handle (e.g. by release, suspend, add, modify, deactivate, activate, resume) the at least a Secondary Cell Group (SCG). The SCG may be part of the UE configuration prior to the LTM cell change or it can be part of a LTM candidate target configuration, at the execution of LTM cell switch procedure within the MCG. The LTM cell switch procedure may be within the source node or from the source node to a target node. [129] In methods, the third network node determines to handle (e.g. by release, suspend, add, modify, deactivate, activate, resume) an SCG, during the execution of a LTM cell switch procedure within the MCG. [130] In methods, the third network node transmits, to the UE, an indication to handle (e.g. by release, suspend, add, modify, deactivate, activate, resume) an SCG. In methods, this indication is included in a configuration of a LTM candidate target cell. [131] In methods, the third network node transmits, to the source network node, an indication to handle (e.g. by release, suspend, add, modify, deactivate, activate, resume) an SCG. [132] In methods, the third network node transmits, to the target network node, an indication to handle (e.g. by release, suspend, add, modify, deactivate, activate, resume) an SCG. [133] In methods, the third network node receives, from the source network node, a request to handle (e.g. by release, suspend, add, modify, deactivate, activate, resume) the SCG. [134] In methods, the third network node receives, from the target network node, a request to handle (e.g. by release, suspend, add, modify, deactivate, activate, resume) an SCG. [135] In methods, the third network node receives, from the UE, an indication about which SCG that is part of a LTM candidate target cell configuration have been configured, after the execution of a LTM cell switch procedure within the MCG. [136] According to some embodiments there is provided a method performed by a user equipment in communication with a source node in a Master Cell Group, MCG. The method comprises executing a layer 1/layer 2 based inter-cell mobility, LTM, cell switch procedure from the source node to a target node, and after or during execution of the LTM cell switch procedure, performing one or more actions in relation to a first Secondary Cell Group. [137] According to some embodiments there is provided a method performed by a source node providing a user equipment with a Master Cell Group, MCG. The method comprises executing a layer 1/layer 2 based inter-cell mobility, LTM, cell switch procedure for the user equipment from the source node to a target node; and during execution of the LTM cell switch procedure, obtaining one or more actions in relation to a first Secondary Cell Group. [138] According to some embodiments there is provided a method performed by a target node for providing a user equipment with a Master Cell Group, MCG, The method comprises executing a layer 1/layer 2 based inter-cell mobility, LTM, cell switch procedure for the user equipment from a source node to the target node in the MCG, and after or during execution of the LTM cell switch procedure, obtaining one or more actions in relation to a first Secondary Cell Group. [139] According to some embodiments there is provided a method performed by a third network node for providing a first secondary cell group to a user equipment. The method comprises before, during or after execution of a layer 1/layer 2 based inter-cell mobility, LTM, cell switch procedure for the user equipment from a source node to a target node for a Master Cell Group, obtaining one or more actions in relation to the first Secondary Cell Group. [140] According to some embodiments there is provided a user equipment, UE, for communicating with a source node in a Master Cell Group. The UE comprises processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the UE is operable to: execute a layer 1/layer 2 based inter-cell mobility, LTM, cell switch procedure from the source node to a target node, and after or during execution of the LTM cell switch procedure, perform one or more actions in relation to a first Secondary Cell Group. [141] According to some embodiments there is provided a source node for providing a user equipment with a Master Cell Group, MCG. The source node comprises processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the source node is operable to: execute a layer 1/layer 2 based inter-cell mobility, LTM, cell switch procedure for the user equipment from the source node to a target node; and during execution of the LTM cell switch procedure, obtain one or more actions in relation to a first Secondary Cell Group. [142] According to some embodiments there is provided a target node for providing a user equipment with a Master Cell Group, MCG. The target node comprises processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the target node is operable to: execute a layer 1/layer 2 based inter-cell mobility, LTM, cell switch procedure for the user equipment from a source node to the target node in the MCG, and after or during execution of the LTM cell switch procedure, obtain one or more actions in relation to a first Secondary Cell Group. [143] According to some embodiments there is provided a third network node for providing a first secondary cell group to a user equipment. The third network node comprises processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the third network node is operable to: before, during or after execution of a layer 1/layer 2 based inter-cell mobility, LTM, cell switch procedure for the user equipment from a source node to a target node for a Master Cell Group, obtain one or more actions in relation to the first Secondary Cell Group. [144] According to some embodiments there is provided a computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out any of the methods described above. [145] According to some embodiments there is provided a computer-readable medium comprising instructions that, when executed on at least one processor, cause the at least one processor to perform any of the methods described above. [146] According to some embodiments there is provided a computer program product comprising non transitory computer readable media having stored thereon a computer program as described above. [147] Certain embodiments may provide one or more of the following technical advantage(s). The embodiments described herein allow for fast setup and handling of the SCG during an LTM cell switch procedure in a MCG thus improving the overall capacity and throughput of the system. The embodiments described herein also allow for a fast setup of an SCG and the handling of specific uses cases that require low latencies and high data rates. BRIEF DESCRIPTION OF THE DRAWINGS [148] For a better understanding of the embodiments of the present disclosure, and to show how it may be put into effect, reference will now be made, by way of example only, to the accompanying drawings, in which: [149] Fig.1 Illustration of dual connectivity combined with carrier aggregation in MR-DC; [150] Fig, 2 illustrates EN-DC; [151] Fig, 3 illustrates NR-DC; [152] Fig. 4 shows the schematic control plane architecture looks like for LTE DC, EN-DC and NR-DC; [153] Fig, 5 shows, from network perspective, the user plane protocol architecture in MR-DC with EPC (EN-DC); [154] Fig.6 shows, from network perspective, the user plane protocol architecture in MR-DC with 5GC (NGEN-DC, NE-DC and NR-DC); [155] Fig.7 illustrates an example of the overall architecture (with both NG-RAN and 5GC), with NG-RAN split in CU and DU connected via F1 interface [156] Fig.8 is a flow chart illustrating a method in accordance with some embodiments; [157] Fig.9 is a flow chart illustrating a method in accordance with some embodiments; [158] Fig.10 is a flow chart illustrating a method in accordance with some embodiments; [159] Fig.11 is a flow chart illustrating a method in accordance with some embodiments; [160] Fig.12 is an example signalling diagram; [161] Fig.13 is an example signalling diagram; [162] Fig.14 is an example signalling diagram; [163] Fig. 15 shows an example of a communication system in accordance with some embodiments; [164] Fig.16 shows a UE in accordance with some embodiments; [165] Fig.17 shows a network node in accordance with some embodiments; [166] Fig.18 is a block diagram of a host; [167] Fig. 19 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized; and [168] Fig.20 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments. DETAILED DESCRIPTION [169] 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. [170] Figure 7 illustrates an example of an overall network architecture (with both NG-RAN and 5GC), with the NG-RAN split into a central unit (CU) and a distributed unit (DU) connected via F1 interface. In particular Figure 7 illustrates an overall architecture for what the embodiments describe herein disclose as a CU and a DU in a Radio Access Network (RAN). The document uses the following example: a RAN corresponding to a Next-Generation RAN (NG-RAN), which may be referred as the 5G RAN. However, the method is applicable to any RAN such as a Sixth Generation (6G) RAN architecture, which may follow a similar split or a different functional split. [171] The RAN (e.g. NG-RAN) comprises of a set of RAN nodes (e.g. gNBs, 6G gNodeBs) connected to a Core Network (e.g. a 5GC, 6G Core Network) through a RAN/CN interface (e.g. NG interface, S1 interface, 6G NG 1). In the case of NG-RAN, this may comprise one or more ng-eNBs, wherein an ng-eNB may consist of an ng-eNB-CU and one or more ng-eNB- DU(s). A gNB may consist of a gNB-CU and one or more gNB-DU(s). A gNB-CU and a gNB- DU is connected via F1 interface. A gNB-DU may be connected to multiple gNB-CUs by appropriate implementation. [172] NG, Xn and F1 are logical interfaces. And, in case of the NG-RAN, the NG and Xn-C interfaces for a gNB consisting of a gNB-CU and gNB-DUs, terminate in the gNB-CU. For EN-DC, the S1-U and X2-C interfaces for a gNB consisting of a gNB-CU and gNB-DUs, terminate in the gNB-CU. The gNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GC as a gNB.. Thus, when the method refers to the CU the method comprises the action(s) being performed by any entities comprised within the CU e.g. CU-CP, gNB-CU- CP. [173] In some examples, there may be an interface directly between different gNB-DUs. Signalling that is sent from one gNB-DU to another gNB-DU, e.g. from/to a source gNB-DU to/from a target gNB-DU, can then be sent directly between the gNB-DUs without going via the gNB- CU. In cases throughout this disclosure where it is written that there is signalling from one DU (e.g. a gNB-DU) to another DU (e.g. a gNB-DU) via the CU (e.g. a gNB-CU) it will be appreciated that the same signalling may also be transmitted directly from one DU (e.g. a gNB- DU) to the other DU (e.g. a gNB-DU). [174] Herein the term “L1/L2 based inter-cell mobility” as used in the Work Item Description in 3GPP, may be used interchangeably with the terms L1/L2-triggered mobility (LTM), Lower layer mobility (LLM), L1/L2 mobility, L1-mobility, L1 based mobility, L1/L2-centric inter- cell mobility or L1/L2 inter-cell mobility. The basic principle is that the UE receives a lower layer signaling from the network indicating to the UE a change (or switch or activation) of its serving cell (e.g. change of PCell, from a source to a target PCell), wherein a lower layer signaling is a message/ signaling of a lower layer protocol, which may be referred as a L1/L2 inter-cell mobility execution command, or a cell switch command/ message. The change of serving cell (e.g. change of PCell) may also lead to a change in Scell(s) for the same cell group e.g. in case the command triggers the UE to change to another cell group configuration of the same type (e.g. another MCG configuration). [175] A lower layer protocol refers to a lower layer protocol in the air interface protocol stack compared to RRC protocol, e.g. Medium Access Control (MAC) is considered a lower layer protocol as it is “below” RRC in the air interface protocol stack, and in this case a lower layer signaling/ message may correspond to a MAC Control Element (MAC CE). Another example of lower layer protocol is the Layer 1 (or Physical Layer, L1), and in this case a lower layer signaling/ message may correspond to a Downlink Control Information (DCI). Signaling information in a protocol layer lower than RRC reduces the processing time and, consequently, reduces the interruption time during mobility; in addition, it may also increase the mobility robustness as the network may respond to faster changes in the channel conditions. Another relevant aspect in L1/L2 inter-cell mobility is that in multi-beam scenario, a cell can be associated to multiple Synchronization Signal Blocks (SSBs), and during a half-frame, different SSBs may be transmitted in different spatial directions (i.e. using different beams, spanning the coverage area of a cell). Similar reasoning may be applicable to CSI-RS resources, which may also be transmitted in different spatial directions. Hence, in L1/L2 inter- cell mobility, the reception of a lower layer signaling indicates the UE to change from one beam in the serving cell, to another beam in a neighbour cell (which is a configured candidate cell), and by that changing serving cell (cell switch for LTM). [176] The phrase “Lower layer signaling indicating to the UE the LTM cell switch procedure” is a message/signal/indication that is sent by the source network node to the UE to provide the UE with the information required for the LTM cell switch procedure. The signaling being ‘lower layer’ means that the signaling is at a layer of the protocol stack below the RRC layer, for example signaling in L1 and/or L2, such as a Medium Access Control Control Element, MAC CE. The UE starts executing the LTM cell switch procedure upon reception of the Lower layer signaling indicating to the UE the LTM cell switch procedure. This does however not exclude that the UE may start executing the LTM cell switch procedure based on other triggers or events. [177] Embodiments herein refer to configuration of a LTM candidate target cell and that the UE is configured with at least one LTM candidate target cell. This configuration may be an RRC configuration, such as encapsulated in an RRC Reconfiguration message, that the UE receives when being configured with inter-DU L1/L2 inter-cell mobility. The configuration of a LTM candidate target cell comprises the configuration which the UE needs to start to operate accordingly when it performs LTM cell switch procedure to that LTM candidate target cell e.g. upon reception of the Lower layer signaling indicating to the UE the LTM cell switch procedure to that LTM candidate target cell, which becomes the target cell and the current (new) SpCell, or an SCell, or an SCG in a serving frequency. The configuration of a LTM candidate target cell comprises parameters of a serving cell (or multiple serving cells, such as a cell group), comprising one or more of the groups of parameters, such as an RRCReconfiguration message an IE CellGroupConfig or an IE SpCellConfig (or the IE SCellConfig, in the case of a SCG). A configuration of a LTM candidate target cell may in one example comprise one or more of: i) the PCell configuration and one or more SCell configuration(s) of a Master Cell Group (MCG); i) the PSCell configuration and one or more SCell configuration(s) of a Secondary Cell Group (SCG). The terms (LTM) candidate configuration, LTM configuration, (LTM) candidate target cell configuration, (LTM) target candidate (cell) configuration may be used interchangeably when referring to configuration of a LTM candidate target cell. [178] The phrase LTM cell switch procedure refers to the process of a UE changing its cell from a source cell to a target cell, using L1/L2-triggered mobility. In the context of L1/L2 based inter-cell mobility or L1/L2-triggered mobility (LTM), LTM cell switch procedure may also be known as dynamic switch, LTM switch, (LTM) cell switch, (LTM) serving cell change or (LTM) cell change. [179] Herein the term “handling of a Secondary Cell Group (SCG) or Secondary Node (SN)” is used when, in addition to a Master Node (MN) or Master Cell Group (MCG), another node is added and this is referred to as a Secondary Node (SN). This term may also comprise the action of creating (generating) and/or releasing (discarding) and/or changing a state of the configuration of an SN/SCG. In one example, the UE configures an SN/SCG according to what is received in a LTM candidate target cell configuration and changes a “state” of SN/SCG to “activate” or to “deactivated”. Also, generally speaking the term “SN” refers to the whole node hosting both lower layers (e.g., PHY, MAC, RLF) and higher layer (e.g., SDAP, PDCP, RRC). However, for the lower layers also the term “SCG” is used and thus one can say that the “SCG” is a subset of the “SN”. Nevertheless, for simplicity here is assumed that the term “SN” and “SCG” can be used interchangeably without any loss of meaning. [180] Embodiments herein also refer to actions being “at execution of a LTM cell switch procedure (also called cell switch for LTM) within MCG”, however, it will be appreciated that this may encompass any moment upon reception of the lower layer mobility command for cell switch in LTM execution (e.g. MAC CE indicating a target candidate configuration) within the MCG, such as upon the reception, when the UE applies the lower layer command (e.g. as part of the actions in the UE’s MAC entity), or after the UE performs random access to the target cell, that is a cell belonging to the MN, during the LTM cell switch, or before the UE performs random access to the target cell, that is a cell belong to the MN, during the LTM cell switch, or before/ after the UE starts monitoring PDCCH (or control channels in general) in the target cell, that is a cell belonging to the MN, or before the UE transmits a first UL message to the target cell, that is a cell belonging to the MN, upon LTM cell switch. Also, “at execution of a LTM cell switch procedure (also called cell switch for LTM) within MCG” may be utilized to mean that the UE switches from a source cell to a target cell, where both the source cell and target cell belong to the same MN. [181] Embodiments herein refer to “handling an SCG”, which may refer to the UE performing one or more actions at the existing SCG (if it has one already configured) or to the UE performing one or more actions at the SCG that is part of an LTM candidate target cell configuration. Which actions the UE may perform may be comprise, for example, “releasing”, “modify”, “reconfiguring”, “add”, “keep”, “deactivate”, “activate”, “suspend”, “resume” of the SCG. [182] Figure 8 depicts a method in accordance with particular embodiments. The method of Figure 8 may be performed by a UE or wireless device (e.g. the UE 1512 or UE 1600 as described later with reference to Figures 15 and 16 respectively). The method may be performed by a UE in communication with a source node in a Master Cell group. The method begins at step 802 with executing a layer 1/layer 2 based inter-cell mobility, LTM, cell switch procedure from the source node to a target node. In Step 804 the method comprises after or during execution of the LTM cell switch procedure, performing one or more actions in relation to a first Secondary Cell Group. It will be appreciated that the term “executing” herein may be considered equivalent to “performing”. [183] In other words, the method of Figure 8 allows the UE, to handle (e.g. by performing one or more actions of e.g.: release, suspend, add, modify, deactivate, activate, resume the first SCG) at the execution of LTM cell switch procedure within the same Master Cell Group (MCG) at least a first Secondary Cell Group (SCG). The LTM cell switch procedure may be from a source node to a target node. [184] The first SCG may be part of the UE configuration prior to the LTM cell change or it can be part of a LTM candidate target configuration. In other words, the first SCG may comprise part of the UE configuration prior to the LTM cell switch procedure, or the first SCG may comprise part of a LTM candidate target configuration. In some examples the UE may perform actions in relation to both an SCG configured prior to the LTM cell switch procedure, and in relation to an SCG that is part of an LTM candidate target configuration for after the LTM cell switch procedure. [185] The method of Figure 8 may comprise the UE receiving an indication from the source node, the target node or a third network node (where the third network node may be configured to provide the first SCG) of the one or more actions in relation to the first SCG. In other words, the UE may receive an indication from a network node, such as the source network node, target network node, or a third network node to handle at least the first SCG (e.g. by release, suspend, add, modify, deactivate, activate, resume) at the execution of LTM cell switch procedure within the MCG from a source node to a target node. [186] However, in some examples, the UE determines itself at the execution of LTM cell switch procedure within an MCG whether to release, suspend, add, modify, deactivate, activate or resume at least the first SCG. In other words, the method of Figure 8 may comprise the UE determining the one or more actions. [187] The one or more actions of step 804 may comprise one or more of: [188] releasing the first SCG, [189] suspending the first SCG, [190] adding the first SCG, [191] reconfiguring the first SCG, [192] deactivating the first SCG, [193] activating the first SCG, [194] resuming the first SCG, and [195] continuing use of the first SCG. [196] Specifically, some of these actions may be defined as follows: ^ Continuing use of the first SCG. In this action, the SCG that is part of the LTM candidate cell configuration is the same as the existing SCG (which in this example comprises the first SCG) configured at the UE prior to the execution of the LTM cell switch procedure within the MCG. Alternatively, the LTM candidate cell configuration may comprise a field instructing to the UE to continue using the first SCG. In this case, upon the execution of the LTM cell switch procedure within the MCG the UE may simply keep using the first (i.e. the current) SCG without modifying any parameters/fields/structure related to the configuration of the first SCG. ^ Reconfiguring the first SCG. In this example, the UE reconfigures the existing SCG configured at the UE prior art the LTM cell switch procedure (which is in this example, the first SCG) to produce the new SCG for the LTM candidate cell configuration. In other words, the UE may apply parameters/fields/structure related to the configuration of the new SCG on top of the existing first SCG configuration used by the UE prior to the execution of the LTM cell switch within the MCG. In this case, this reconfiguration may be regarded as “full configuration” if the UE changes the existing configuration for the SCG with the new one received within the LTM candidate cell configuration at the execution of the LTM cell switch procedure. Otherwise, this reconfiguration may be regarded as a “delta configuration” if the UE changes only a subset of parameters/fields/structure related with those ones present in the new one received within the LTM candidate cell configuration at the execution of the LTM cell switch procedure. ^ Activating, deactivating, suspending. In this example, the first SCG may comprise either or both of the existing SCG configured at the UE prior to the LTM cell switch procedure or a new SCG forming part of the MTW candidate cell configuration. The first SCG configured by the UE and its state is set to “activated” or “deactivated” or “suspended”. This means that the UE will apply the parameters/fields/structure related to the configuration of the first SCG but will start to use the first SCG for performing transmissions and reception after the execution of the LTM cell switch procedure within the MCG only if the state of this first SCG is changed to “activated”. The state of the SCG may be changed to “activated” by the target network or by the third node (e.g. the SN) after the execution of the LTM cell switch procedure within the MCG. Otherwise, setting the state of the first SCG to “activated” or “deactivated” or “suspended” may be indicated together with the lower layer signaling for the executing of the LTM cell switch procedure within the MCG (either within the same lower layer signaling of in a different one) ^ Releasing the first SCG. The first SCG that is part of the LTM candidate cell configuration is indicated to not be used or to be released by the UE. This means that the UE will ignore the parameters/fields/structure related to the configuration of a first SCG that are received before the execution of a LTM cell switch procedure within an LTM candidate target cell configuration. This also means that, if the UE has an existing SCG configured (and that is using), the UE will simply release the existing SCG and keep only the new MCG after executing the LTM cell switch procedure. The setting of the state of the first SCG to “activated” or “deactivated” or “suspended” may be indicated together with the lower layer signaling for the executing of the LTM cell switch procedure within the MCG (either within the same lower layer signaling of in a different one). [197] In some examples, the state of the SCG (e.g., “activate” or “deactivated”) is based according at least to one of the following signaling options: ^ In one embodiment, the setting of that “state” of the SCG is based on the RRC configuration the UE receives for LTM. For example, the step of receiving the indication of the one or more actions may comprise receiving a Radio Resource Control configuration o In one option, the status is set to “activated” or “deactivated” or “suspended” or “non-valid” or “invalid” or “released”. For example, when a UE with an MCG A is configured with LTM candidate MCG B, and together with MCG B the UE is also configured with SCG A, it is indicated to the UE that in case the UE moves from MCG A to MCG B the status of the SCG A should be set to “activated”. In another example, when a UE with an MCG A and an SCG A is configured with LTM candidate MCG B, and together with MCG B the UE is also configured with SCG B, it is indicated to the UE that in case the UE moves from MCG A to the MCG B the status of the SCG A should be set to “released” and the status of SCG B should be set to “activated”. ^ In one embodiment, the setting of that “state” for a SCG which is within an LTM candidate target cell configuration or part of the UE configuration prior to the LTM cell switch, is based on a lower layer signaling the UE receives to indicate the execution of LTM (LTM cell switch) within an MCG e.g. MAC CE for the LTM cell switch or another MAC CE concatenated with it. It will be appreciated that the one or more actions may comprise one of activating, deactivating, releasing or suspending the first SCG. Thean indication of the one or more actions may be received in a lower layer signalling, wherein the lower layer signally further requests the execution of the LTM cell switch procedure. ^ In one embodiment, the setting of that “state” for a SCG which is within an LTM candidate target cell configuration is based on measurements performed by the UE. For example, the method 8 may comprise determining the one or more actions based on measurements performed by the UE. o In one option, the UE may perform measurement on a SCG that is part of an LTM candidate target cell configuration before receiving a lower layer signaling to indicate the execution of an LTM cell switch procedure within an MCG. In particular, the UE may perform such measurements because configured to do so within the received LTM candidate target cell configuration or may decide to perform such measurements autonomously or may be configured to perform such measurements by the third node. The measurements performed by the UE can be L1 or L3 measurements and this is according to the UE implementation or to the network configuration. o In one option, the UE may perform measurement on a SCG that is part of an LTM candidate target cell configuration and report such measurement to the network before receiving a lower layer signaling to indicate the execution of an LTM cell switch procedure. Once the measurements are performed the UE reports such measurements to the source network node or to the third network node before receiving the lower layer signaling for the execution of the LTM cell switch procedure. ^ In some embodiments, the step of receiving, from the source node, the target node or a third network node, an indication of the one or more actions in relation to the first SCG comprises, receiving the indication of the one or more actions in lower layer signalling. The indication may be comprised in a lower layer signaling received that is different from the lower layer signaling to indicate the execution of an LTM cell switch procedure. However, in some examples, the lower layer signalling that indicates the one or more actions is further requests the execution of the LTM cell switch procedure. ^ In one embodiment, the setting of that “state” for a SCG which is within an LTM candidate target cell configuration is based on an indication received from the third network node. o In one option, the third network node may configure the UE to perform SCG measurements on potential LTM candidate SCG target cells and when those measurements are reported by the UE the third network node forwards such measurement to the source network node. As previously mentioned, that UE may receive two distinctive lower layer signaling indications from the source network node, one to indicate the execution of the LTM cell switch procedure within the MCG, and one to indicate the one or more actions to perform in relation to the first SCG (e.g. to release, suspend, add, modify, deactivate, activate or resume the first a SCG). In one embodiment, the two lower layer signaling indications are sent to the UE in two distinctive messages (e.g., two MAC CEs and MAC PDUs). In one embodiment, the two lower layer signaling indications are sent to the UE within the same message (e.g., two MAC CEs within the same MAC PDU). [198] In some examples, the two distinctive lower layers signaling indications received by the UE are sent one by the source network node, and one by the target network node or the third network node. [199] The UE may not, as a default behavior, at the execution of the LTM cell switch procedure within the MCG, configure any new SCG, regardless of if any SCG is part of the LTM candidate target cell configuration indicated in the lower layer signaling for executing the LTM cell switch procedure. If the UE has an existing SCG prior to executing the LTM switch procedure, this SCG may be released/deleted. In other words, the method of Figure 8 may comprise that UE does not configure a new SCG at the LTM cell switch procedure and the one or more actions comprises releasing the first SCG, wherein the first SCG comprises an existing SCG. [200] The UE may, as a default behavior, at the execution of the LTM cell switch procedure within an MCG, configure the first SCG(s) with a state set to “deactivated/suspended”, regardless of the state of the first SCG indicated within the LTM candidate target cell configuration (e.g. indicated in the lower layer signaling for executing the LTM cell switch procedure). In other words, the method of Figure 8 may further comprise deactivating or suspending the first SCG regardless of a state associated with the first SCG within the LTM candidate target cell configuration for executing the LTM cell switch procedure. [201] The UE may transmit, to a network node, such as the source network node, the target network node or a third network node, an indication about which SCG that are part of a LTM candidate target cell configuration has been configured, after the execution of a LTM cell switch procedure within an MCG. In other words, the method of Figure 8 may comprise transmitting an indication of second SCG that has been configured after execution of the LTW cell switch procedure or will be configured during execution of the LTM procedure. The indication may be transmitted to the target node, the source node or a third node. The second SCG may comprise the first SCG. ^ In one alternative, this indication is included in a lower layer signaling transmitted to the target network node. ^ In one alternative, this indication is included in a lower layer signaling transmitted to the source network node. ^ In one alternative, this indication is included in a lower layer signaling transmitted to the third network node. ^ In one alternative, this indication is included in a RRC signaling transmitted to the target network node or third network node or source network node. [202] As previously described, the one or more actions described above may apply to the existing SCG (if any) configured at the UE before the execution of the LTM cell switch procedure. [203] As previously described the one or more actions described above may apply to the SCG received in an LTM candidate target cell configuration received by the UE before the execution of the LTM cell switch procedure. [204] In some examples, the LTM candidate target cell configuration includes only the MCG, only the SCG, or both an MCG and an SCG. In case the LTM candidate target cell configuration includes only an MCG or only an SCG, this means that upon the execution of a LTM cell switch procedure the UE may need to apply two separate LTM candidate target cell configuration one for the MCG and one for the SCG. [205] In some embodiments, the UE receives an RRC Reconfiguration (e.g. RRCReconfiguration, in MN format, including an MCG configuration) from the network (e.g. from the network node operating as MN) including the configuration for LTM: e.g. the message includes at least one LTM candidate cell configuration, such as an embedded RRCReconfiguration (denoted RRCReconfiguration*) which is to be applied or switched to upon reception of a lower layer command for LTM cell switch. The embedded RRCReconfiguration* for the target candidate configuration includes the configuration for a Master Cell Group (MCG); upon reception of a lower layer command for LTM cell switch for the MCG, indicating the switch of the PCell (or the MCG in general terms), the UE also performs one or more actions on an configuration which may be being: added (in case the UE is not in DC), released (in case the UE is in MR- DC, but shall not be after the cell switch), modified or simply indicated to be kept. Examples of the different use cases are the following: - A) UE is in DC, upon the cell switch for LTM the UE deletes / releases MR-DC (e.g. deletes the configured SCG); - B) UE is in DC, upon the cell switch for LTM the UE remains in MR-DC without a PSCell change i.e. PSCell is kept; - C) UE is in MR-DC, upon the cell switch for LTM the UE remains in MR-DC with a PSCell change; - D) UE is in not MR-DC, upon the cell switch for LTM the UE adds an SCG. [206] In some embodiments, the UE receives an RRC Reconfiguration (e.g. RRCReconfiguration, in MN format, including an MCG configuration) from the network (e.g. from the network node operating as MN) including the configuration for LTM: e.g. the message includes at least one LTM candidate cell configuration, such as an embedded RRCReconfiguration (denoted RRCReconfiguration*) which is to be applied or switched to upon reception of a lower layer command for LTM cell switch. The embedded RRCReconfiguration* for the target candidate configuration includes the configuration for a Master Cell Group (MCG) and the configuration for a Secondary Cell Group (SCG), embedded as an SCG RRC Reconfiguration (which may be denoted as an SN RRCReconfiguration as it is generated by a node operating as Secondary Node – SN, or RRCReconfiguration**); upon reception of a lower layer command for LTM cell switch for the MCG, indicating the switch of the PCell (or the MCG in general terms), the UE applies or switches to the configuration in RRCReconfiguration* and, as part of that either adds and/or modifies and /or releases the SCG. In other words, the reception of the lower layer cell switch for LTM for the MCG leads to one or more actions on an SCG being added, released and/or modified. In some embodiments, the UE receives an RRC Reconfiguration (e.g. RRCReconfiguration, in MN format, including an MCG configuration) from the network (e.g. from the network node operating as MN) including the configuration for LTM: e.g. the message includes at least one LTM candidate cell configuration, such as an instance of the IE CellGroupConfig* (e.g. as defined in TS 38.331) for the MCG which is to be applied or switched to upon reception of a lower layer command for LTM cell switch. The embedded CellGroupConfig* for the target candidate configuration includes the configuration for a MCG and the configuration for a Secondary Cell Group (SCG), embedded as an SCG CellGroupConfig IE (which may be denoted SN CellGroupConfig IE as it is generated by a node operating as SN, or CellGroupConfig**); upon reception of a lower layer command for LTM cell switch for the MCG, indicating the switch of the PCell (or the MCG in general terms), the UE applies or switches to the configuration in CellGroupConfig* and, as part of that either adds and/or modifies and /or releases the SCG. In other words, the reception of the lower layer cell switch for LTM for the MCG leads to one or more actions on an SCG being added, released and/or modified. [207] In some embodiments, the UE receives two messages for LTM in the MCG and LTM in the SCG: - A first RRC Reconfiguration (e.g. RRCReconfiguration, in MN format, including an MCG configuration) from the network (e.g. from the network node operating as MN) including the configuration for LTM for the MCG: e.g. the message includes at least one LTM candidate cell configuration, such as an instance of the IE CellGroupConfig* (e.g. as defined in TS 38.331) for the MCG. - A second RRC Reconfiguration (e.g. RRCReconfiguration, in SN format, including an SCG configuration) from the network (e.g. from the network node operating as SN) including the configuration for LTM for the SCG: e.g. the message includes at least one LTM candidate cell configuration, such as an instance of the IE CellGroupConfig** (e.g. as defined in TS 38.331) for the SCG which is to be applied or switched to upon reception of a lower layer command for LTM cell switch via the SCG MAC entity. - The UE further receives a concatenated MAC PDU including i) a first lower layer command (first e.g. MAC CE) for the MCG cell switch (including at least a first configuration ID for an MCG candidate cell) and ii) a lower layer command (e.g. second MAC CE) for the SCG cell switch (including as second configuration ID for an SCG candidate cell). upon reception of a lower layer command for LTM cell switch for the MCG, indicating the switch of the PCell (or the MCG in general terms), the UE applies or switches to the configuration in CellGroupConfig* and, as part of that either adds and/or modifies and /or releases the SCG. In other words, the reception of the lower layer cell switch for LTM for the MCG leads to one or more actions on an SCG being added, released and/or modified. [208] In a set of embodiments, a UE that is configured with an SCG receives a command to perform an MCG cell switch for LTM where no SCG is configured for the UE after the cell switch to the target MCG cell, e.g. that the SCG is released as part of the LTM cell switch. The UE then stores and/or suspends/deactivates the SCG configuration that it had before the cell switch (when in the source MCG cell) as part of the LTM cell switch. In one alternative, the UE stores and/or suspends/deactivates the SCG configuration based on an indication from the network e.g. in the Lower Layer signalling that corresponds to the LTM cell switch command, in the LTM candidate target configuration for the target MCG cell or in the LTM candidate target configuration for the source MCG cell. [209] When the UE performs a subsequent MCG cell switch for LTM, it then resumes the SCG configuration when in the target MCG cell for that LTM cell switch procedure. In one example, the UE resumes the SCG configuration at an MCG cell switch for LTM to the MCG cell where the UE earlier was configured with the SCG configuration. In one alternative, the UE resumes the SCG configuration based on an indication from the network, e.g. in the Lower Layer signalling that corresponds to the LTM cell switch command, in the LTM candidate target configuration for the target MCG cell or the LTM candidate target configuration for the source MCG cell or in the LTM candidate target configuration for the MCG cell where the UE was configured with the SCG. [210] Figure 9 depicts a method in accordance with particular embodiments. The method of Figure 9 may be performed by a network node (e.g. the network node 1510 or network node 1700 as described later with reference to Figures 15 and 17 respectively). The network node may comprise a source node providing a user equipment with a MCG. The method begins at step 902 with executing a LTM cell switch procedure for the UE from the source node to the target node. In step 904 the method comprises during execution of the LTM cell switch procedure, obtaining one or more actions in relation to a first SCG. [211] In other words, a source network node (also referred to as a source node), such as a source gNB/eNB, belonging to a Master Node (MN), or a Master Cell Group (MCG) may configure, at the UE, at least a Secondary Node (SN), or a Secondary Cell Group (SCG) that is part of a LTM candidate target configuration at the execution of LTM cell switch procedure from a source node or a target node within the MCG. [212] The one or more actions of step 904 may comprise one or more of: [213] releasing the first SCG, [214] suspending the first SCG, [215] adding the first SCG, [216] reconfiguring the first SCG, [217] deactivating the first SCG, [218] activating the first SCG, [219] resuming the first SCG, and [220] continuing use of the first SCG. [221] Specifically, some of these actions may be defined as follows: ^ Continuing use of the first SCG. In this action, the SCG that is part of the LTM candidate cell configuration is the same as the existing SCG (which in this example comprises the first SCG) configured at the UE prior to the execution of the LTM cell switch procedure within the MCG. Alternatively, the LTM candidate cell configuration may comprise a field instructing to the UE to continue using the first SCG. In this case, upon the execution of the LTM cell switch procedure within the MCG the UE may simply keep using the first (i.e. the current) SCG without modifying any parameters/fields/structure related to the configuration of the first SCG. ^ Reconfiguring the first SCG. In this example, the UE reconfigures the existing SCG configured at the UE prior art the LTM cell switch procedure (which is in this example, the first SCG) to produce the new SCG for the LTM candidate cell configuration. In other words, the UE may apply parameters/fields/structure related to the configuration of the new SCG on top of the existing first SCG configuration used by the UE prior to the execution of the LTM cell switch within the MCG. In this case, this reconfiguration may be regarded as “full configuration” if the UE changes the existing configuration for the SCG with the new one received within the LTM candidate cell configuration at the execution of the LTM cell switch procedure. Otherwise, this reconfiguration may be regarded as a “delta configuration” if the UE changes only a subset of parameters/fields/structure related with those ones present in the new one received within the LTM candidate cell configuration at the execution of the LTM cell switch procedure. ^ Activating, deactivating, suspending. In this example, the first SCG may comprise either or both of the existing SCG configured at the UE prior to the LTM cell switch procedure or a new SCG forming part of the MTW candidate cell configuration. The first SCG configured by the UE and its state is set to “activated” or “deactivated” or “suspended”. This means that the UE will apply the parameters/fields/structure related to the configuration of the first SCG but will start to use the first SCG for performing transmissions and reception after the execution of the LTM cell switch procedure within the MCG only if the state of this first SCG is changed to “activated”. The state of the SCG may be changed to “activated” by the target network or by the third node (e.g. the SN) after the execution of the LTM cell switch procedure within the MCG. Otherwise, setting the state of the first SCG to “activated” or “deactivated” or “suspended” may be indicated together with the lower layer signaling for the executing of the LTM cell switch procedure within the MCG (either within the same lower layer signaling of in a different one) ^ Releasing the first SCG. The first SCG that is part of the LTM candidate cell configuration is indicated to not be used or to be released by the UE. This means that the UE will ignore the parameters/fields/structure related to the configuration of a first SCG that are received before the execution of a LTM cell switch procedure within an LTM candidate target cell configuration. This also means that if the UE has an existing SCG configured (and that is using), the UE will simply release the existing SCG and keep only the new MCG after executing the LTM cell switch procedure. [222] The source node of method of Figure 9 may determine to configure at the UE with the first SCG that is part of a LTM candidate target configuration at the execution of LTM cell switch procedure within an MCG from a source network node to a target network node. ^ In one alternative, the source network node determines to configure at the UE the first SCG based on measurements received by the UE before the execution of the LTM cell switch procedure within an MCG. In this example, the step 904 comprises determining the one or more actions. For example, the method of Figure 9 may further comprise determining the one or more actions based on measurements received by the UE before execution of the LTM cell switch procedure. ^ In one alternative, the source network node determines to configure at the UE the first SCG based on an indication received by the target network node or by a third network node. In other words, the step 904 may comprise receiving an indication of the one or more actions from the target node or a third node. [223] The source network node transmits, to the UE, an indication to configure the first SCG that is part of a LTM candidate target cell configuration, at the execution of a LTM cell switch procedure within the MCG. In other words, the method of Figure 9 may further comprise transmitting an indication of the one or more actions to the UE. ^ In one alternative, this indication is included in the Lower layer signaling. ^ The lower layer signally may also indicate to the UE the LTM cell switch procedure within an MCG. In other words, the lower layer signalling may further request the LTM cell switch procedure. ^ In one alternative, this indication is implicit and is included directly within the configuration of LTM candidate target cell, at the execution of a LTM cell switch procedure within an MCG. ^ In one alternative, this indication is included in a lower layer signaling that is different from the lower layer signaling used to indicate to the UE the execution of the LTM cell switch procedure within an MCG. In other words, the lower layer signalling comprising the indication is separate to lower layer signalling that requests the LTM cell switch procedure. [224] It may therefore be appreciated that two distinctive lower layer signaling indications are used from the source network node, one to indicate the execution of the LTM cell switch procedure within an MCG, and one to indicate on whether to configure at least an SCG that is part of a LTM candidate target configuration. ^ In one embodiment, the two lower layers signaling indications are sent to the UE in two distinctive messages (e.g., two MAC CEs and MAC PDUs). ^ In one embodiment, the two lower layers signaling indications are sent to the UE within the same message (e.g., two MAC CEs within the same MAC PDU). [225] In some examples, source network node sends only one of the two lower layers signaling indications and that other one is sent by the target network node or third network node. [226] In some examples step 904 comprises transmitting a request for the one or more actions to a third network node. For example, the source node may transmit, to the third network node, a request to configure at the UE an SCG that is part of a LTM candidate target configuration at the execution of LTM cell switch procedure from a source node or a target node within the MCG. ^ In one alternative, the source network node transmits this request in a message transmitted over the Xn/X2AP interface. One example could be that the source network node sends this request to the third node via the S-NODE MODIFICATION REQUEST message. ^ In one alternative, this request may include one or more SCG configuration(s) that are part of a LTM candidate target cell configuration generated by the third network node and the request is for the third network node to indicate the one to be configured. [227] In some examples, step 904 comprises transmitting a request for the one or more actions to the target node. For example, the source network node may transmit, to the target network node, a request to configure at the UE an SCG that is part of a LTM candidate target configuration at the execution of LTM cell switch procedure from a source node or a target node within the MCG. ^ In one alternative, the source network node transmits this request in a message over the F1AP interface to the Central Unit (CU) to which the source network node is connected, and the CU forwards this request in a message over the F1AP interface to the target network node (since the target network node is also connected to the same CU). ^ In one alternative, the source network node transmits this request to the target network node in a message transmitted over the Xn/X2AP interface. One example could be that the source network node sends this request to the third node via the HANDOVER REQUEST message. [228] In some examples, step 904 comprises receiving an indication of the one or more actions from the third network node. For example, the source node may receive, from the third network node, an indication to configure at the UE the first SCG that is part of a LTM candidate target configuration at the execution of LTM cell switch procedure from the source node to a target node within the MCG. ^ In one alternative, the source network node receives this indication in a message transmitted over the Xn/X2AP interface. One example could be that the source network node receives this indication from the third node via the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message. ^ In one alternative, this indication may include one SCG configuration that is not part of the previously sent LTM candidate target cell configuration generated by the third network node. In this case, this new SCG configuration may be considered as part of the previously sent LTM candidate target cell configuration. [229] In some examples, step 904 comprises receiving an indication of the one or more actions from the target node. For example, the source node may receive, from the target network node, an indication to configure at the UE an SCG that is part of a LTM candidate target configuration at the execution of LTM cell switch procedure from the source node to the target node within an MCG. ^ In one alternative, the source network node receives this indication in a message over the F1AP interface sent by CU to which the source network node is connected, meaning that the target network node has transmitted this indication to the source network node via the CU. ^ In one alternative, the source network node receives this indication from the target network node in a message transmitted over the Xn/X2AP interface. One example could be that the source network node sends this request to the third node via the HANDOVER REQUEST ACKNOWLEDGE message. ^ In one alternative, this indication may include one SCG configuration that is not part of the previously sent LTM candidate target cell configuration generated by the third network node. In this case, this new SCG configuration may be considered as part of the previously sent LTM candidate target cell configuration. [230] In some examples, the method of Figure 9 further comprises: receiving an indication of second SCG that has been configured after execution of the LTM cell switch procedure or will be configured during execution of the LTM procedure. The second SCG may comprise the first SCG. [231] In other words, the source node may receive, from the UE, an indication on which SCG that is part of a LTM candidate target cell configuration has been configured during the execution of a LTM cell switch procedure within an MCG. ^ In one alternative, this indication is included in the Lower layer signaling sent by the UE before executing the LTM cell switch procedure within an MCG. ^ In one alternative, this indication is included in the Lower layer signaling sent by the UE after executing the LTM cell switch procedure within an MCG. ^ In one alternative, this indication is included in an RRC message sent by the UE before executing the LTM cell switch procedure within an MCG. [232] It will be appreciated that the one or more actions according to the method of Figure 9 may be applied to the existing SCG (if any) configured at the UE before the execution of the LTM cell switch procedure. In other words, the first SCG may comprise part of the UE configuration prior to the LTM cell switch procedure. [233] It will also be appreciated that the one or more actions according to the method of Figure 9 may be applied to the SCG included in an LTM candidate target cell configuration transmitted to the UE before the execution of the LTM cell switch procedure. In other words, the first SCG may comprise part of a LTM candidate target configuration. [234] Figure 10 depicts a method in accordance with particular embodiments. The method of Figure 10 may be performed by a network node (e.g. the network node 1510 or network node 1700 as described later with reference to Figures 15 and 17 respectively). The method may be performed by a target node for providing a user equipment with a MCG. The method begins at step 1002 with executing a layer 1/layer 2 based inter-cell mobility, LTM, cell switch procedure for the user equipment from a source node to the target node in the MCG. In step 1004 the method comprises after or during execution of the LTM cell switch procedure, obtaining one or more actions in relation to a first Secondary Cell Group. [235] In other words, a target network node (also referred to herein as a target node), such as a target gNB/eNB, belonging to a Master Node (MN), or a Master Cell Group (MCG) may configure at the UE at least a Secondary Node (SN), or a Secondary Cell Group (SCG) that is part of a LTM candidate target configuration at the execution of LTM cell switch procedure from a source node or a target node within the MCG. [236] The one or more actions of step 1004 may comprise one or more of: [237] releasing the first SCG, [238] suspending the first SCG, [239] adding the first SCG, [240] reconfiguring the first SCG, [241] deactivating the first SCG, [242] activating the first SCG, [243] resuming the first SCG, and [244] continuing use of the first SCG. [245] Specifically, some of these actions may be defined as follows: ^ Continuing use of the first SCG. In this action, the SCG that is part of the LTM candidate cell configuration is the same as the existing SCG (which in this example comprises the first SCG) configured at the UE prior to the execution of the LTM cell switch procedure within the MCG. Alternatively, the LTM candidate cell configuration may comprise a field instructing to the UE to continue using the first SCG. In this case, upon the execution of the LTM cell switch procedure within the MCG the UE may simply keep using the first (i.e. the current) SCG without modifying any parameters/fields/structure related to the configuration of the first SCG. ^ Reconfiguring the first SCG. In this example, the UE reconfigures the existing SCG configured at the UE prior art the LTM cell switch procedure (which is in this example, the first SCG) to produce the new SCG for the LTM candidate cell configuration. In other words, the UE may apply parameters/fields/structure related to the configuration of the new SCG on top of the existing first SCG configuration used by the UE prior to the execution of the LTM cell switch within the MCG. In this case, this reconfiguration may be regarded as “full configuration” if the UE changes the existing configuration for the SCG with the new one received within the LTM candidate cell configuration at the execution of the LTM cell switch procedure. Otherwise, this reconfiguration may be regarded as a “delta configuration” if the UE changes only a subset of parameters/fields/structure related with those ones present in the new one received within the LTM candidate cell configuration at the execution of the LTM cell switch procedure. ^ Activating, deactivating, suspending. In this example, the first SCG may comprise either or both of the existing SCG configured at the UE prior to the LTM cell switch procedure or a new SCG forming part of the MTW candidate cell configuration. The first SCG configured by the UE and its state is set to “activated” or “deactivated” or “suspended”. This means that the UE will apply the parameters/fields/structure related to the configuration of the first SCG but will start to use the first SCG for performing transmissions and reception after the execution of the LTM cell switch procedure within the MCG only if the state of this first SCG is changed to “activated”. The state of the SCG may be changed to “activated” by the target network or by the third node (e.g. the SN) after the execution of the LTM cell switch procedure within the MCG. Otherwise, setting the state of the first SCG to “activated” or “deactivated” or “suspended” may be indicated together with the lower layer signaling for the executing of the LTM cell switch procedure within the MCG (either within the same lower layer signaling of in a different one) ^ Releasing the first SCG. The first SCG that is part of the LTM candidate cell configuration is indicated to not be used or to be released by the UE. This means that the UE will ignore the parameters/fields/structure related to the configuration of a first SCG that are received before the execution of a LTM cell switch procedure within an LTM candidate target cell configuration. This also means that if the UE has an existing SCG configured (and that is using), the UE will simply release the existing SCG and keep only the new MCG after executing the LTM cell switch procedure. [246] The target node of method of Figure 10 may determine to configure at the UE an SCG that is part of a LTM candidate target configuration at the execution of LTM cell switch procedure from a source node or a target node within the MCG. In one alternative, the target network node determines to configure at the UE the first SCG based on measurements received by the UE after the execution of the LTM cell switch procedure within the MCG. In other words, step 1004 comprises determining the one or more actions. For example, the step of determining may comprise determining the one or more actions based on measurements received by the UE after execution of the LTM cell switch procedure. In one alternative, the target network node determines to configure at the UE an SCG based on an indication received from the source network node or from a third network node. In other words, the step 1004 may comprise receiving an indication of the one or more actions from the source node or a third node. [247] The target network node may receive, from a third network node, a request to configure at the UE an SCG that is part of a LTM candidate target configuration. For example, the method of Figure 10 may further comprise receiving a request for the one or more actions from the third network node. a. In one alternative, the target network node receives this request in a message transmitted over the Xn/X2AP interface. One example could be that the source network node sends this request to the third node via the S-NODE MODIFICATION REQUEST or S-NODE CHANGE REQUIRED message. b. In one alternative, this request may include one or more SCG configuration(s) that are part of a LTM candidate target cell configuration generated by the third network node. [248] The target network node may receive, from the source network node, a request to configure at the UE an SCG that is part of a LTM candidate target configuration. For example, the method of Figure 10 may further comprise receiving a request for the one or more actions from the source node. a. In one alternative, the target network node receives this request in a message over the F1AP interface to the Central Unit (CU) to which both the source network node and target network node are connected. This means that the CU has received this indication in a message over the F1AP interface by the source network node. For example, the source network node may send this request to the target network node via the CU. b. In one alternative, the target network node receives this request to the target network node in a message transmitted over the Xn/X2AP interface. One example could be that the source network node sends this request to the third node via the HANDOVER REQUEST message. c. In one alternative, this request may include one or more SCG configuration(s) that are part of a LTM candidate target cell configuration generated by the third network node and the request is for the third network node to indicate the one to be configured. [249] In some examples, the target network node transmits, to a third network node, an indication to configure at the UE an SCG that is part of a LTM candidate target configuration. In other words, the method of Figure 10 may further comprise transmitting an indication of the one or more actions a third network node. a. In one alternative, the target network node receives this request to the target network node in a message transmitted over the Xn/X2AP interface. One example could be that the source network node sends this request to the third node via the S-NODE ADDITION REQUEST, S-NODE MODIFICATION REQUIRED, or S-NODE RELEASE REQUEST message. b. In one alternative, this request may include one or more SCG configuration(s) that are part of a LTM candidate target cell configuration generated by the third network node and the request is for the third network node to indicate the one to be configured. [250] In some examples, the target network node transmits, to a source network node, an indication to configure at the UE an SCG that is part of a LTM candidate target configuration. In other words, the method of Figure 10 may further comprise transmitting an indication of the one or more actions to the source node. a. In one alternative, the target network node transmits this indication in a message over the F1AP interface to the Central Unit (CU) to which both the source network node and target network node are connected. This means that the CU has received this indication in a message over the F1AP interface by the target network node. Basically the target network node sends this indication to the source network node via the CU. b. In one alternative, the target network node transmits this indication in a message over the Xn/X2AP interface. One example could be that the target network node transmit this indication to the source node via the HANDOVER REQUEST ACKNOWLEDGE message. c. In one alternative, this indication may include one SCG configuration that is not part of the previously sent LTM candidate target cell configuration generated by the third network node. In this case, this new SCG configuration should be considered as part of the previously sent LTM candidate target cell configuration. [251] The method of figure 10 may further comprise transmitting an indication of the one or more actions to the UE after execution of the LTM cell switch procedure. In other words, the target network node may transmit, to the UE, an indication to configure at the UE an SCG that is part of a LTM candidate target configuration. a. In one alternative, this indication is included in the Lower layer signaling sent to the UE after the execution of the LTM cell switch procedure within the MCG. b. In one alternative, this indication is included in an RRC message sent to the UE only after the execution of the LTM cell switch procedure within the MCG. [252] The target network node may receive, from the UE, an indication of which SCG that are part of a LTM candidate target cell configuration have been configured during the execution of a LTM cell switch procedure within the MCG. In other words, method of Figure 10 may further comprise receiving an indication of a second SCG that has been configured after execution of the LTM cell switch procedure. The second SCG may comprise the first SCG. a. In one alternative, this indication is included in the Lower layer signaling sent by the UE after executing the LTM cell switch procedure within the MCG. b. In one alternative, this indication is included in an RRC message sent by the UE after executing the LTM cell switch procedure within the MCG. [253] It will be appreciated that the one or more actions above with reference to Figure 10 may be applied to the existing SCG (if any) configured at the UE before the execution of the LTM cell switch procedure. In other words, the first SCG may comprise part of the UE configuration prior to the LTM cell switch procedure. [254] It will be appreciated that the one or more actions above with reference to Figure 10 may be applied to the SCG included in an LTM candidate target cell configuration transmitted to the UE before the execution of the LTM cell switch procedure. In other words, the first SCG may comprise part of a LTM candidate target configuration. [255] Figure 11 depicts a method in accordance with particular embodiments. The method of Figure 11 may be performed by a network node (e.g. the network node 1510 or network node 1700 as described later with reference to Figures 15 and 17 respectively). The method may be performed by a third network node, for example a third node for providing a first Secondary Cell Group (SCG). The method begins at step 1102 with before, during or after execution of a layer 1/layer 2 based inter-cell mobility, LTM, cell switch procedure for the user equipment from a source node to a target node for a Master Cell Group, obtaining one or more actions in relation to the first Secondary Cell Group. [256] In other words, a third network node, such as a third gNB/eNB, belonging to a Secondary Node (SN), or a Secondary Cell Group (SCG) may configure at the UE a Secondary Node (SN), or a Secondary Cell Group (SCG) that is part of a LTM candidate target configuration at the execution of LTM cell switch procedure from a source node or a target node within the MCG. [257] The one or more actions of step 1102 may comprise one or more of: [258] releasing the first SCG, [259] suspending the first SCG, [260] adding the first SCG, [261] reconfiguring the first SCG, [262] deactivating the first SCG, [263] activating the first SCG, [264] resuming the first SCG, and [265] continuing use of the first SCG. [266] Specifically, some of these actions may be defined as follows: [267] Continuing use of the first SCG. In this action, the SCG that is part of the LTM candidate cell configuration is the same as the existing SCG (which in this example comprises the first SCG) configured at the UE prior to the execution of the LTM cell switch procedure within the MCG. Alternatively, the LTM candidate cell configuration may comprise a field instructing to the UE to continue using the first SCG. In this case, upon the execution of the LTM cell switch procedure within the MCG the UE may simply keep using the first (i.e. the current) SCG without modifying any parameters/fields/structure related to the configuration of the first SCG. [268] Reconfiguring the first SCG. In this example, the UE reconfigures the existing SCG configured at the UE prior art the LTM cell switch procedure (which is in this example, the first SCG) to produce the new SCG for the LTM candidate cell configuration. In other words, the UE may apply parameters/fields/structure related to the configuration of the new SCG on top of the existing first SCG configuration used by the UE prior to the execution of the LTM cell switch within the MCG. In this case, this reconfiguration may be regarded as “full configuration” if the UE changes the existing configuration for the SCG with the new one received within the LTM candidate cell configuration at the execution of the LTM cell switch procedure. Otherwise, this reconfiguration may be regarded as a “delta configuration” if the UE changes only a subset of parameters/fields/structure related with those ones present in the new one received within the LTM candidate cell configuration at the execution of the LTM cell switch procedure. [269] Activating, deactivating, suspending. In this example, the first SCG may comprise either or both of the existing SCG configured at the UE prior to the LTM cell switch procedure or a new SCG forming part of the MTW candidate cell configuration. The first SCG configured by the UE and its state is set to “activated” or “deactivated” or “suspended”. This means that the UE will apply the parameters/fields/structure related to the configuration of the first SCG but will start to use the first SCG for performing transmissions and reception after the execution of the LTM cell switch procedure within the MCG only if the state of this first SCG is changed to “activated”. How the state of the SCG is changed to “activated” may be by the target network or by the third node (e.g. the SN) after the execution of the LTM cell switch procedure within the MCG. Otherwise, setting the state of the first SCG to “activated” or “deactivated” or “suspended” may be indicated together with the lower layer signaling for the executing of the LTM cell switch procedure within the MCG (either within the same lower layer signaling of in a different one) [270] Releasing the first SCG. The first SCG that is part of the LTM candidate cell configuration is indicated to not be used or to be released by the UE. This means that the UE will ignore the parameters/fields/structure related to the configuration of a first SCG that are received before the execution of a LTM cell switch procedure within an LTM candidate target cell configuration. This also means that if the UE has an existing SCG configured (and that is using), the UE will simply release the existing SCG and keep only the new MCG after executing the LTM cell switch procedure. [271] The third network node of Figure 11 may determine to configure at the UE an SCG that is part of a LTM candidate target configuration at the execution of LTM cell switch procedure from a source node to a target node within the MCG. ^ In one alternative, the third network node determines to configure at the UE an SCG that is part of a LTM candidate target configuration after the execution of LTM cell switch procedure within the MCG. ^ In some examples, step 1102 may comprise determining the one or more actions. In one alternative, the third network node determines to configure at the UE an SCG based on measurements received by the UE before the execution of the LTM cell switch procedure within the MCG. In one alternative, the third network node determines to configure at the UE an SCG based on measurements received by the UE after the execution of the LTM cell switch procedure within the MCG. In other words, the step of determining may comprise determining the one or more actions based on measurements received by the UE after or after execution of the LTM cell switch procedure. ^ In one alternative, the third network node determines to configure at the UE an SCG based on an indication received by the source network node or by a target network node. [272] The third network node may transmit, to the UE, an indication to configure at the UE an SCG at the execution of LTM cell switch procedure within an MCG. In other words, Figure 11 may further comprise transmitting an indication of the one or more actions to the UE before or after execution of the LTM cell switch procedure. ^ In one alternative, this indication is included in a configuration of a LTM candidate target cell send to the UE before the execution of the LTM cell switch procedure within the MCG. ^ In one alternative, this indication is included in a configuration sent to the UE after the execution of the LTM cell switch procedure within the MCG. ^ In one alternative, this indication is included in a lower layer signaling sent to the UE after the execution of the LTM cell switch procedure within the MCG. ^ this indication is included in a lower layer signaling sent to the UE before the execution of the LTM cell switch procedure within the MCG. [273] The third network node may transmit, to the source network node, an indication to configure at the UE an SCG at the execution of the LTM cell switch procedure. In other words, the method of Figure 11 may comprise transmitting an indication of the one or more actions to the source node. ^ In one alternative, the third network node transmits this indication in a message transmitted over the Xn/X2AP interface. One example could be that the source network node sends this request to the third node via the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message. ^ In one alternative, this request may include one SCG configuration that is not part of the previously sent LTM candidate target cell configuration generated by the third network node. In this case, this new SCG configuration should be considered as part of the previously sent LTM candidate target cell configuration. ^ In one alternative, the third network node transmits this indication upon the reception of the same indication from a target network node. [274] The third network node may receive, from the source network node, a request to configure at the UE an SCG that is part of a LTM candidate target configuration. In other words, step 1104 may comprise receiving a request for the one or more actions to the source node. ^ In one alternative, the third network node receives this request in a message transmitted over the Xn/X2AP interface. One example could be that the source network node sends this request to the third node via the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message. ^ In one alternative, this request may include one SCG configuration that is not part of the previously sent LTM candidate target cell configuration generated by the third network node. In this case, this new SCG configuration should be considered as part of the previously sent LTM candidate target cell configuration. [275] The third network node may receive, from the target network node, an indication to configure at the UE at least a SCG that is part of a LTM candidate target configuration. For example, the step 1104 may comprise receiving an indication of the one or more actions from the target node. ^ In one alternative, the third network node receives this indication in a message transmitted over the Xn/X2AP interface. One example could be that the source network node sends this request to the third node via the S-NODE ADDITION REQUEST ACKNOWLEDGE, S-NODE MODIFICATION REQUIRED ACKNOWLEDGE, or S-NODE RELEASE REQUEST ACKNOWLEDGE message. ^ In one alternative, this indication may include one or more SCG configuration(s) that are part of a LTM candidate target cell configuration generated by the third network node and the request is for the third network node to indicate the one to be configured. [276] It will be appreciated that the one or more actions according to the method of Figure 11 may be applied to the existing SCG (if any) configured at the UE before the execution of the LTM cell switch procedure. [277] It will be appreciated that the one or more actions according to the method of Figure 11 may be applied to the SCG included in an LTM candidate target cell configuration transmitted to the UE before the execution of the LTM cell switch procedure. [278] Figure 12 illustrates an example implementation of the Methods of Figures 8 to 11. [279] In this example steps 1203 and 1204 correspond to the source node obtaining the one or more actions corresponding to step 904. The source node indicates the one or more actions to the UE in step 1206. [280] Figure 13 illustrates an example implementation of the Methods of Figures 8 to 11. [281] In this example, the source node determines the one or more actions, and indicates the one or more actions to the UE in step 1304 (SCG configuration indication). [282] Figure 14 illustrates an example implementation of the Methods of Figures 8 to 11. [283] In this example, the source node obtains in step 1406 (which corresponds to 904) the one or more actions (e.g. SCG configuration) from the third node via the target node. [284] Figure 15 shows an example of a communication system 1500 in accordance with some embodiments. [285] In the example, the communication system 1500 includes a telecommunication network 1502 that includes an access network 1504, such as a radio access network (RAN), and a core network 1506, which includes one or more core network nodes 1508. The access network 1504 includes one or more access network nodes, such as network nodes 1510a and 1510b (one or more of which may be generally referred to as network nodes 1510), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 1510 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1512a, 1512b, 1512c, and 1512d (one or more of which may be generally referred to as UEs 1512) to the core network 1506 over one or more wireless connections. [286] 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 1500 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 1500 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system. [287] The UEs 1512 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 1510 and other communication devices. Similarly, the network nodes 1510 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 1512 and/or with other network nodes or equipment in the telecommunication network 1502 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 1502. [288] In the depicted example, the core network 1506 connects the network nodes 1510 to one or more hosts, such as host 1516. 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 1506 includes one more core network nodes (e.g., core network node 1508) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1508. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF). [289] The host 1516 may be under the ownership or control of a service provider other than an operator or provider of the access network 1504 and/or the telecommunication network 1502, and may be operated by the service provider or on behalf of the service provider. The host 1516 may host a variety of applications to provide one or more services. Examples of such applications include the provision of live and/or pre-recorded audio/video content, data collection services, for example, 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. [290] As a whole, the communication system 1500 of Figure 15 enables connectivity between the 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 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (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. [291] In some examples, the telecommunication network 1502 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1502 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1502. For example, the telecommunications network 1502 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 IoT services to yet further UEs. [292] In some examples, the UEs 1512 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 1504 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1504. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio – Dual Connectivity (EN-DC). [293] In the example illustrated in Figure 15, the hub 1514 communicates with the access network 1504 to facilitate indirect communication between one or more UEs (e.g., UE 1512c and/or 1512d) and network nodes (e.g., network node 1510b). In some examples, the hub 1514 may be a controller, router, a content source and analytics node, or any of the other communication devices described herein regarding UEs. For example, the hub 1514 may be a broadband router enabling access to the core network 1506 for the UEs. As another example, the hub 1514 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 1510, or by executable code, script, process, or other instructions in the hub 1514. As another example, the hub 1514 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 1514 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1514 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1514 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 1514 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy IoT devices. [294] The hub 1514 may have a constant/persistent or intermittent connection to the network node 1510b. The hub 1514 may also allow for a different communication scheme and/or schedule between the hub 1514 and UEs (e.g., UE 1512c and/or 1512d), and between the hub 1514 and the core network 1506. In other examples, the hub 1514 is connected to the core network 1506 and/or one or more UEs via a wired connection. Moreover, the hub 1514 may be configured to connect to an M2M service provider over the access network 1504 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1510 while still connected via the hub 1514 via a wired or wireless connection. In some embodiments, the hub 1514 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 1510b. In other embodiments, the hub 1514 may be a non-dedicated hub – that is, a device which is capable of operating to route communications between the UEs and network node 1510b, but which is additionally capable of operating as a communication start and/or end point for certain data channels. [295] Figure 16 shows a UE 1600 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs. Examples of a UE 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 camera, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. [296] A UE 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, a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE 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, a UE 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). [297] The UE 1600 includes processing circuitry 1602 that is operatively coupled via a bus 1604 to an input/output interface 1606, a power source 1608, a memory 1610, a communication interface 1612, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 16. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc. [298] The processing circuitry 1602 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 1610. The processing circuitry 1602 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 1602 may include multiple central processing units (CPUs). The processing circuitry 1602 may be operable to provide, either alone or in conjunction with other UE 1600 components, such as the memory 1610, UE 1600 functionality. For example, the processing circuitry 1602 may be configured to cause the UE 1602 to perform the methods as described with reference to Figure 8. [299] In the example, the input/output interface 1606 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 the UE 1600. 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. [300] In some embodiments, the power source 1608 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. The power source 1608 may further include power circuitry for delivering power from the power source 1608 itself, and/or an external power source, to the various parts of the UE 1600 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1608. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1608 to make the power suitable for the respective components of the UE 1600 to which power is supplied. [301] The memory 1610 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 1610 includes one or more application programs 1614, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1616. The memory 1610 may store, for use by the UE 1600, any of a variety of various operating systems or combinations of operating systems. [302] The memory 1610 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 1610 may allow the UE 1600 to access instructions, application 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 1610, which may be or comprise a device-readable storage medium. [303] The processing circuitry 1602 may be configured to communicate with an access network or other network using the communication interface 1612. The communication interface 1612 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1622. The communication interface 1612 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 UE or a network node in an access network). Each transceiver may include a transmitter 1618 and/or a receiver 1620 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1618 and receiver 1620 may be coupled to one or more antennas (e.g., antenna 1622) and may share circuit components, software or firmware, or alternatively be implemented separately. [304] In some embodiments, communication functions of the communication interface 1612 may include cellular communication, Wi-Fi communication, 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 in 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. [305] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1612, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The 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). [306] As another example, a UE 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, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or controls a robotic arm performing a medical procedure according to the received input. [307] A UE, when in the form of an Internet of Things (IoT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an IoT device are devices which are or which are 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 head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), 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. A UE in the form of an IoT device comprises circuitry and/or software in dependence on the intended application of the IoT device in addition to other components as described in relation to the UE 1600 shown in Figure 16. [308] As yet another specific example, in an IoT scenario, a UE 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 UE and/or a network node. The UE 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, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE 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. [309] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE 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 UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators. [310] Figure 17 shows a network node 1700 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network. 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)). [311] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units 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). [312] Other examples of network nodes 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). [313] The network node 1700 includes processing circuitry 1702, a memory 1704, a communication interface 1706, and a power source 1708, and/or any other component, or any combination thereof. The network node 1700 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 1700 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1700 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1704 for different RATs) and some components may be reused (e.g., a same antenna 1710 may be shared by different RATs). The network node 1700 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1700, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1700. [314] The processing circuitry 1702 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 network node 1700 components, such as the memory 1704, network node 1700 functionality. For example, the processing circuitry 1702 may be configured to cause the network node to perform the methods as described with reference to Figures 9, 10 or 11. [315] In some embodiments, the processing circuitry 1702 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1702 includes one or more of radio frequency (RF) transceiver circuitry 1712 and baseband processing circuitry 1714. In some embodiments, the radio frequency (RF) transceiver circuitry 1712 and the baseband processing circuitry 1714 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 1712 and baseband processing circuitry 1714 may be on the same chip or set of chips, boards, or units. [316] The memory 1704 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 1702. The memory 1704 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 1702 and utilized by the network node 1700. The memory 1704 may be used to store any calculations made by the processing circuitry 1702 and/or any data received via the communication interface 1706. In some embodiments, the processing circuitry 1702 and memory 1704 is integrated. [317] The communication interface 1706 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 1706 comprises port(s)/terminal(s) 1716 to send and receive data, for example to and from a network over a wired connection. The communication interface 1706 also includes radio front-end circuitry 1718 that may be coupled to, or in certain embodiments a part of, the antenna 1710. Radio front-end circuitry 1718 comprises filters 1720 and amplifiers 1722. The radio front-end circuitry 1718 may be connected to an antenna 1710 and processing circuitry 1702. The radio front-end circuitry may be configured to condition signals communicated between antenna 1710 and processing circuitry 1702. The radio front-end circuitry 1718 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1718 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1720 and/or amplifiers 1722. The radio signal may then be transmitted via the antenna 1710. Similarly, when receiving data, the antenna 1710 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1718. The digital data may be passed to the processing circuitry 1702. In other embodiments, the communication interface may comprise different components and/or different combinations of components. [318] In certain alternative embodiments, the network node 1700 does not include separate radio front-end circuitry 1718, instead, the processing circuitry 1702 includes radio front-end circuitry and is connected to the antenna 1710. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1712 is part of the communication interface 1706. In still other embodiments, the communication interface 1706 includes one or more ports or terminals 1716, the radio front-end circuitry 1718, and the RF transceiver circuitry 1712, as part of a radio unit (not shown), and the communication interface 1706 communicates with the baseband processing circuitry 1714, which is part of a digital unit (not shown). [319] The antenna 1710 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna 1710 may be coupled to the radio front-end circuitry 1718 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna 1710 is separate from the network node 1700 and connectable to the network node 1700 through an interface or port. [320] The antenna 1710, communication interface 1706, and/or the processing circuitry 1702 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 1710, the communication interface 1706, and/or the processing circuitry 1702 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment. [321] The power source 1708 provides power to the various components of network node 1700 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1708 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1700 with power for performing the functionality described herein. For example, the network node 1700 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 1708. As a further example, the power source 1708 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. [322] Embodiments of the network node 1700 may include additional components beyond those shown in Figure 17 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, the network node 1700 may include user interface equipment to allow input of information into the network node 1700 and to allow output of information from the network node 1700. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1700. [323] Figure 18 is a block diagram of a host 1800, which may be an embodiment of the host 1516 of Figure 15, in accordance with various aspects described herein. As used herein, the host 1800 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 1800 may provide one or more services to one or more UEs. [324] The host 1800 includes processing circuitry 1802 that is operatively coupled via a bus 1804 to an input/output interface 1806, a network interface 1808, a power source 1810, and a memory 1812. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 16 and 17, such that the descriptions thereof are generally applicable to the corresponding components of host 1800. [325] The memory 1812 may include one or more computer programs including one or more host application programs 1814 and data 1816, which may include user data, e.g., data generated by a UE for the host 1800 or data generated by the host 1800 for a UE. Embodiments of the host 1800 may utilize only a subset or all of the components shown. The host application programs 1814 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 1814 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 1800 may select and/or indicate a different host for over-the-top services for a UE. The host application programs 1814 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc. [326] Figure 19 is a block diagram illustrating a virtualization environment 1900 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 1900 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. [327] Applications 1902 (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. [328] Hardware 1904 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 1906 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1908a and 1908b (one or more of which may be generally referred to as VMs 1908), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 1906 may present a virtual operating platform that appears like networking hardware to the VMs 1908. [329] The VMs 1908 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1906. Different embodiments of the instance of a virtual appliance 1902 may be implemented on one or more of VMs 1908, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment. [330] In the context of NFV, a VM 1908 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 1908, and that part of hardware 1904 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 VMs 1908 on top of the hardware 1904 and corresponds to the application 1902. [331] Hardware 1904 may be implemented in a standalone network node with generic or specific components. Hardware 1904 may implement some functions via virtualization. Alternatively, hardware 1904 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 1910, which, among others, oversees lifecycle management of applications 1902. In some embodiments, hardware 1904 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 1912 which may alternatively be used for communication between hardware nodes and radio units. [332] Figure 20 shows a communication diagram of a host 2002 communicating via a network node 2004 with a UE 2006 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 1512a of Figure 15 and/or UE 1600 of Figure 16), network node (such as network node 1510a of Figure 15 and/or network node 1700 of Figure 17), and host (such as host 1516 of Figure 15 and/or host 1800 of Figure 18) discussed in the preceding paragraphs will now be described with reference to Figure 20. [333] Like host 1800, embodiments of host 2002 include hardware, such as a communication interface, processing circuitry, and memory. The host 2002 also includes software, which is stored in or accessible by the host 2002 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 2006 connecting via an over-the-top (OTT) connection 2050 extending between the UE 2006 and host 2002. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 2050. [334] The network node 2004 includes hardware enabling it to communicate with the host 2002 and UE 2006. The connection 2060 may be direct or pass through a core network (like core network 1506 of Figure 15) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet. [335] The UE 2006 includes hardware and software, which is stored in or accessible by UE 2006 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 2006 with the support of the host 2002. In the host 2002, an executing host application may communicate with the executing client application via the OTT connection 2050 terminating at the UE 2006 and host 2002. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 2050 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 2050. [336] The OTT connection 2050 may extend via a connection 2060 between the host 2002 and the network node 2004 and via a wireless connection 2070 between the network node 2004 and the UE 2006 to provide the connection between the host 2002 and the UE 2006. The connection 2060 and wireless connection 2070, over which the OTT connection 2050 may be provided, have been drawn abstractly to illustrate the communication between the host 2002 and the UE 2006 via the network node 2004, without explicit reference to any intermediary devices and the precise routing of messages via these devices. [337] As an example of transmitting data via the OTT connection 2050, in step 2008, the host 2002 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 2006. In other embodiments, the user data is associated with a UE 2006 that shares data with the host 2002 without explicit human interaction. In step 2010, the host 2002 initiates a transmission carrying the user data towards the UE 2006. The host 2002 may initiate the transmission responsive to a request transmitted by the UE 2006. The request may be caused by human interaction with the UE 2006 or by operation of the client application executing on the UE 2006. The transmission may pass via the network node 2004, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 2012, the network node 2004 transmits to the UE 2006 the user data that was carried in the transmission that the host 2002 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2014, the UE 2006 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 2006 associated with the host application executed by the host 2002. [338] In some examples, the UE 2006 executes a client application which provides user data to the host 2002. The user data may be provided in reaction or response to the data received from the host 2002. Accordingly, in step 2016, the UE 2006 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE 2006. Regardless of the specific manner in which the user data was provided, the UE 2006 initiates, in step 2018, transmission of the user data towards the host 2002 via the network node 2004. In step 2020, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 2004 receives user data from the UE 2006 and initiates transmission of the received user data towards the host 2002. In step 2022, the host 2002 receives the user data carried in the transmission initiated by the UE 2006. [339] One or more of the various embodiments improve the performance of OTT services provided to the UE 2006 using the OTT connection 2050, in which the wireless connection 2070 forms the last segment. More precisely, the teachings of these embodiments may improve the rate of provision of a SCG and thereby provide benefits such as improved performance. [340] In an example scenario, factory status information may be collected and analyzed by the host 2002. As another example, the host 2002 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 2002 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 2002 may store surveillance video uploaded by a UE. As another example, the host 2002 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 2002 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data. [341] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 2050 between the host 2002 and UE 2006, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 2002 and/or UE 2006. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 2050 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 2050 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 2004. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 2002. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 2050 while monitoring propagation times, errors, etc. [342] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware. [343] 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.

EMBODIMENTS Group A Embodiments 1. A method performed by a user equipment in communication with a source node in a Master Cell Group, the method comprising: executing a layer 1/layer 2 based inter-cell mobility, LTM, cell switch procedure from the source node to a target node, and after or during execution of the LTM cell switch procedure, performing one or more actions in relation to a first Secondary Cell Group. 2. The method of embodiment 1 wherein the one or more actions comprise one or more of: releasing the first SCG, suspending the first SCG, adding the first SCG, reconfiguring the first SCG, deactivating the first SCG, activating the first SCG, resuming the first SCG, and continuing use of the first SCG. 3. The method of embodiment 1 or 2 further comprising: determining the one or more actions. 4. The method of embodiment 1 or 2 further comprising: receiving an indication from the source node, the target node or a third network node of the one or more actions in relation to the first SCG. 5. The method of any embodiment 4 wherein the method further comprises: receiving the indication of the one or more actions in a Radio Resource Control configuration. 6. The method of any embodiment 4 wherein the method further comprises: receiving the indication of the one or more actions in a lower layer signalling. 7. The method of embodiment 6 wherein the lower layer signally further requests the execution of the LTM cell switch procedure. 8. The method of embodiment 6 or 7 wherein the lower layer signalling is received from the target node. 9. The method of embodiment 6 or 7 wherein the lower layer signalling is received from the source node. 10. The method of embodiment 6 or 7 wherein the lower layer signalling is received from a third network node, wherein the third network node provides the first Secondary Cell Group. 11. The method of any embodiment 3 wherein the method further comprises: determining the one or more actions based on measurements performed by the UE. 12. The method of any previous embodiment wherein the UE does not configure a new SCG at the LTM cell switch procedure and the one or more actions comprises releasing the first SCG, wherein the first SCG comprises an existing SCG. 13. The method of any one of embodiment 1 to 12 wherein one or more actions comprises: deactiviating or suspending the first SCG regardless of a state associated with the first SCG within the LTM candidate target cell configuration for executing the LTM cell switch procedure. 14. The method of any previous embodiment wherein the first SCG comprises part of the UE configuration prior to the LTM cell switch procedure. 15. The method of any one of embodiment 1 to 13 wherein the first SCG comprises part of a LTM candidate target configuration. 16. The method of any previous embodiment further comprising: transmitting an indication of second SCG that has been configured after execution of the LTW cell switch procedure or will be configured during execution of the LTM procedure. 17. The method of embodiment 16 wherein the indication is transmitted to the target node, the source node or a third node. 18. The method of embodiment 16 to 17 wherein the second SCG comprises the first SCG. 19. The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node. Group B Embodiments 20. A method performed by a source node providing a user equipment with a Master Cell Group (MCG) to the method comprising: executing a layer 1/layer 2 based inter-cell mobility, LTM, cell switch procedure for the user equipment from the source node to a target node; and during execution of the LTM cell switch procedure, obtaining one or more actions in relation to a first Secondary Cell Group. 21. The method of embodiment 20 wherein the one or more actions comprise one or more of: releasing the first SCG, suspending the first SCG, adding the first SCG, reconfiguring the first SCG, deactivating the first SCG, activating the first SCG, resuming the first SCG, and continuing use of the first SCG. 22. The method of embodiment 20 or 21 further comprising: transmitting an indication of the one or more actions to the UE. 23. The method of embodiment 22 wherein the indication is transmitted in lower layer signalling. 24. The method of embodiment 23 wherein the lower layer signalling further requests the LTM cell switch procedure. 25. The method of embodiment 23 wherein the lower layer signalling comprising the indication is separate to lower layer signalling that requests the LTM cell switch procedure. 26. The method of embodiment 22 wherein the indication is comprised in a LTM candidate target cell configuration. 27. The method of any one of embodiments 21 to 26 wherein the first SCG comprises part of the UE configuration prior to the LTM cell switch procedure. 28. The method of any one of embodiment 21 to 26 wherein the first SCG comprises part of a LTM candidate target configuration. 29. The method of any one of embodiments 21 to 28 wherein the step of obtaining comprises:: transmitting a request for the one or more actions to a target network node. 30. The method of any one of embodiments 21 to 29 wherein the step of obtaining comprises: receiving an indication of the one or more actions from the target network node. 31. The method of any one of embodiments 21 to 28 wherein the step of obtaining comprises: transmitting a request for the one or more actions to a third network node, wherein the third network node provides the first Secondary Cell Group; and receiving an indication of the one or more actions from a third network node. The method of any one of embodiments 21 to 28 wherein the step of obtaining comprises: receiving an indication of the one or more actions from a third network node. The method of any one of embodiments 21 to 28 further comprising: determining the one or more actions. The method of embodiment 33 wherein the step of determining comprises determining the one or more actions based on measurements received by the UE before execution of the LTM cell switch procedure. The method of any one of embodiments 21 to 34 further comprising: receiving an indication of second SCG that has been configured after execution of the LTM cell switch procedure or will be configured during execution of the LTM procedure. The method of embodiment 35 wherein the second SCG comprises the first SCG. A method performed by a target node for providing a user equipment with a Master Cell Group (MCG) to the method comprising: executing a layer 1/layer 2 based inter-cell mobility, LTM, cell switch procedure for the user equipment from a source node to the target node in the MCG, and after or during execution of the LTM cell switch procedure, obtaining one or more actions in relation to a first Secondary Cell Group. The method of embodiment 37 wherein the one or more actions comprise one or more of: releasing the first SCG, suspending the first SCG, adding the first SCG, reconfiguring the first SCG, deactivating the first SCG, activating the first SCG, resuming the first SCG, and continuing use of the first SCG. 39. The method of embodiment 37 or 38 further comprising: transmitting an indication of the one or more actions to the UE after execution of the LTM cell switch procedure. 40. The method of embodiment 39 wherein the indication is transmitted in lower layer signalling. 41. The method of embodiment 39 wherein the indication is comprised in a an RRC message. 42. The method of embodiment 37 or 38 further comprising: transmitting an indication of the one or more actions to the source node or a third network node. 43. The method of any one of embodiments 37 to 42 wherein the first SCG comprises part of the UE configuration prior to the LTM cell switch procedure. 44. The method of any one of embodiment 37 to 42 wherein the first SCG comprises part of a LTM candidate target configuration. 45. The method of any one of embodiments 37 to 44 wherein the method further comprises: receiving a request for the one or more actions from the source node. 46. The method of any one of embodiments 37 to 45 wherein method further comprises: transmitting an indication of the one or more actions to the source node. 47. The method of any one of embodiments 37 to 44 wherein the method further comprises: receives a request for the one or more actions from a third network node 48. The method of any one of embodiments 37 to 44 wherein the method further comprises: transmitting an indication of the one or more actions from a third network node. 49. The method of any one of embodiments 37 to 44 wherein the step of obtaining comprises: determining the one or more actions. 50. The method of embodiment 49 wherein the step of determining comprises determining the one or more actions based on measurements received by the UE after execution of the LTM cell switch procedure. 51. The method of any one of embodiments 37 to 50 further comprising: receiving an indication of second SCG that has been configured after execution of the LTM cell switch procedure. 52. The method of embodiment 51 wherein the second SCG comprises the first SCG. 53. A method performed by a third network node for providing a first secondary cell group to a user equipment the method comprising: before, during or after execution of a layer 1/layer 2 based inter-cell mobility, LTM, cell switch procedure for the user equipment from a source node to a target node for a Master Cell Group, obtaining one or more actions in relation to the first Secondary Cell Group. 54. The method of embodiment 37 wherein the one or more actions comprise one or more of: releasing the first SCG, suspending the first SCG, adding the first SCG, reconfiguring the first SCG, deactivating the first SCG, activating the first SCG, resuming the first SCG, and continuing use of the first SCG. 55. The method of embodiment 53 or 54 further comprising: transmitting an indication of the one or more actions to the UE before or after execution of the LTM cell switch procedure. 56. The method of embodiment 55 wherein the indication is comprised in a LTM candidate target cell configuration. 57. The method of embodiment 55 wherein the indication is comprised in lower layer signalling transmitted before or after execution of the LTM cell switch procedure. 58. The method of embodiment 53 or 54 further comprising: transmitting an indication of the one or more actions to the source node or the target node. 59. The method of any one of embodiment 53 to 58 wherein the first SCG comprises part of a LTM candidate target configuration. 60. The method of any one of embodiments 53 to 59 wherein the step of obtaining comprises: receiving a request for the one or more actions to the source node. 61. The method of any one of embodiments 53 to 60 wherein the step of obtaining comprises: receiving an indication of the one or more actions from the target node. 62. The method of any one of embodiments 53 to 59 further comprising: determining the one or more actions. 63. The method of embodiment 64 wherein the step of determining comprises determining the one or more actions based on measurements received by the UE after or after execution of the LTM cell switch procedure. 64. The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment. Group C Embodiments 65. A user equipment, the user equipment comprising: processing circuitry configured to cause the user equipment to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry. 66. A network node, the network node comprising: processing circuitry configured to cause the network node to perform any of the steps of any of the Group B embodiments; power supply circuitry configured to supply power to the processing circuitry. 67. A user equipment (UE) for [insert purpose], the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE. 68. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to receive the user data from the host. 69. The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data to the UE from the host. 70. The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application. 71. A method implemented by a host operating in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the UE performs any of the operations of any of the Group A embodiments to receive the user data from the host. 72. The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE. 73. The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application. 74. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to transmit the user data to the host. 75. The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host. 76. The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application. 77. A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs any of the steps of any of the Group A embodiments to transmit the user data to the host. 78. The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE. 79. The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application. 80. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE. 81. The host of the previous embodiment, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host. 82. A method implemented in a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE. 83. The method of the previous embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE. 84. The method of any of the previous 2 embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application. 85. A communication system configured to provide an over-the-top service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE. 86. The communication system of the previous embodiment, further comprising: the network node; and/or the user equipment. 87. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to receive the user data from a user equipment (UE) for the host. 88. The host of the previous embodiment, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application. 89. The host of the any of the previous 2 embodiments, wherein the initiating receipt of the user data comprises requesting the user data. 90. A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, initiating receipt of user data from the UE, the user data originating from a transmission which the network node has received from the UE, wherein the network node performs any of the steps of any of the Group B embodiments to receive the user data from the UE for the host. 91. The method of the previous embodiment, further comprising at the network node, transmitting the received user data to the host.

REFERENCES ^1. RP-222332, 3GPP work item description: Further NR mobility enhancements, MediaTek, 3GPP TSG RAN Meeting #97-e, Electronic Meeting, September 12-16, 2022 2. 3GPP TS 38.300 v17.1.0, NR and NG-RAN Overall Description; Stage 2 3. 3GPP TS 38.331, v17.1.0, RRC protocol specification 4. 3GPP TS 38.321, v17.1.0, MAC protocol specification

ABBREVIATIONS At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s). 5GC or 5GCN 5G core network ACK Acknowledgement AGC Automatic Gain Control AMF Access and Mobility management Function AP Application Protocol ARQ Automatic Repeat Request BFD Beam Failure Monitoring BFR Beam Failure Recovery BSR Buffer Status Report BWP Bandwidth Part C-RNTI Cell Radio Network Temporary Identifier CA Carrier Aggregation CE Control Element CGI Cell Global Identity CHO Conditional Handover CN Core Network CPA Conditional PSCell Addition CPC Conditional PSCell Change CP Control Plane CQI Channel Quality Indicator C-RNTI Cell Radio Network Temporary Identifier CSI Channel State Information CU Central Unit DC Dual Connectivity DCI Downlink Control Information DL Downlink DRB Data Radio Bearer DU Distributed Unit eNB (EUTRAN) base station E-RAB EUTRAN Radio Access Bearer E-UTRA Evolved Universal Terrestrial Radio Access E-UTRAN Evolved Universal Terrestrial Radio Access Network FDD Frequency Division Duplex gNB NR base station GTP-U GPRS Tunneling Protocol – User Plane HARQ Hybrid ARQ IE Information Element IP Internet Protocol LTE Long Term Evolution MCGMaster Cell Group MACMedium Access Control MAC CE MAC Control Element MeNB Master eNB MgNB Master gNB MN Master Node MR-DC Multi-Radio Dual Connectivity NACK Negative Acknowledgement NAS Non Access Stratum NG-RAN Next Generation Radio Access Network Ng-eNB Next Generation Evolved Node B NR New Radio PDCP Packet Data Convergence Protocol PCellPrimary Cell PCI Physical Cell Identity PDCCH Physical Downlink Control Channel PHR Power headroom report PSCell Primary SCG (in LTE) or Primary SCG Cell (in NR) PUCCH Physical Uplink Control Channel PUSCH Phyical Uplink Shared Channel RACH Random Access Channel RAT Radio Access Technology RB Radio Bearer RLC Radio Link Control RLF Radio Link Failure RRC Radio Resource Control SCellSCG SCG SCG Group SCTP Stream Control Transmission Protocol SeNB Secondary eNB SgNB Secondary gNB SINRSignal to Interference plus Noise Ratio SN Secondary Node SR Scheduling Request SRB Signaling Radio Bearer SSB Synchronization Signal Block S-SN Source Secondary Node SUL Supplementary uplink SpCell Special Cell, the primary cell of a master or SCG group TAT Time Alignment Timer TCI Transmission Configuration Indication TDD Time Division Duplex TEIDTunnel Endpoint IDentifier TNL Transport Network Layer T-SNTarget Secondary Node UCI Uplink Control Information UDP User Datagram Protocol UPF User Plane Function UE User Equipment UL Uplink UL-SCH Uplink Shared Channel UP User Plane URLLC Ultra Reliable Low Latency Communication X2 Interface between base stations 1x RTT CDMA20001x Radio Transmission Technology 3GPP 3rd Generation Partnership Project 5G 5th Generation 6G 6th Generation ABS Almost Blank Subframe ARQ Automatic Repeat Request AWGN Additive White Gaussian Noise BCCH Broadcast Control Channel BCH Broadcast Channel CA Carrier Aggregation CC Carrier Component CCCH SDU Common Control Channel SDU CDMA Code Division Multiplexing Access CGI Cell Global Identifier CIR Channel Impulse Response CP Cyclic Prefix CPICH Common Pilot Channel CPICH Ec/No CPICH Received energy per chip divided by the power density in the band CQI Channel Quality information C-RNTI Cell RNTI CSI Channel State Information DCCH Dedicated Control Channel DL Downlink DM Demodulation DMRS Demodulation Reference Signal DRX Discontinuous Reception DTX Discontinuous Transmission DTCH Dedicated Traffic Channel DUT Device Under Test E-CID Enhanced Cell-ID (positioning method) eMBMS evolved Multimedia Broadcast Multicast Services E-SMLC Evolved-Serving Mobile Location Centre ECGI Evolved CGI eNB E-UTRAN NodeB ePDCCH Enhanced Physical Downlink Control Channel E-SMLC Evolved Serving Mobile Location Center E-UTRA Evolved UTRA E-UTRAN Evolved UTRAN FDD Frequency Division Duplex FFS For Further Study gNB Base station in NR GNSS Global Navigation Satellite System HARQ Hybrid Automatic Repeat Request HO Handover HSPA High Speed Packet Access HRPD High Rate Packet Data LOS Line of Sight LPP LTE Positioning Protocol LTE Long-Term Evolution MAC Medium Access Control MAC Message Authentication Code MBSFN Multimedia Broadcast multicast service Single Frequency Network MBSFN ABS MBSFN Almost Blank Subframe MDT Minimization of Drive Tests MIB Master Information Block MME Mobility Management Entity MSC Mobile Switching Center NPDCCH Narrowband Physical Downlink Control Channel NR New Radio OCNG OFDMA Channel Noise Generator OFDM Orthogonal Frequency Division Multiplexing OFDMA Orthogonal Frequency Division Multiple Access OSS Operations Support System OTDOA Observed Time Difference of Arrival O&M Operation and Maintenance PBCH Physical Broadcast Channel P-CCPCH Primary Common Control Physical Channel PCell Primary Cell PCFICH Physical Control Format Indicator Channel PDCCH Physical Downlink Control Channel PDCP Packet Data Convergence Protocol PDP Profile Delay Profile PDSCH Physical Downlink Shared Channel PGW Packet Gateway PHICH Physical Hybrid-ARQ Indicator Channel PLMN Public Land Mobile Network PMI Precoder Matrix Indicator PRACH Physical Random Access Channel PRS Positioning Reference Signal PSS Primary Synchronization Signal PUCCH Physical Uplink Control Channel PUSCH Physical Uplink Shared Channel RACH Random Access Channel QAM Quadrature Amplitude Modulation RAN Radio Access Network RAT Radio Access Technology RLC Radio Link Control RLM Radio Link Management RNC Radio Network Controller RNTI Radio Network Temporary Identifier RRC Radio Resource Control RRM Radio Resource Management RS Reference Signal RSCP Received Signal Code Power RSRP Reference Symbol Received Power OR Reference Signal Received Power RSRQ Reference Signal Received Quality OR Reference Symbol Received Quality RSSI Received Signal Strength Indicator RSTD Reference Signal Time Difference SCH Synchronization Channel SCell Secondary Cell SDAP Service Data Adaptation Protocol SDU Service Data Unit SFN System Frame Number SGW Serving Gateway SI System Information SIB System Information Block SNR Signal to Noise Ratio SON Self Optimized Network SS Synchronization Signal SSS Secondary Synchronization Signal TDD Time Division Duplex TDOA Time Difference of Arrival TOA Time of Arrival TSS Tertiary Synchronization Signal TTI Transmission Time Interval UE User Equipment UL Uplink USIM Universal Subscriber Identity Module UTDOA Uplink Time Difference of Arrival WCDMA Wide CDMA WLAN Wide Local Area Network

Claims

CLAIMS 1. A method performed by a user equipment in communication with a source node in a Master Cell Group, MCG, the method comprising: executing (802) a layer 1/layer 2 based inter-cell mobility, LTM, cell switch procedure from the source node to a target node, and after or during execution of the LTM cell switch procedure, performing (804) one or more actions in relation to a first Secondary Cell Group.

2. The method of claim 1 or 2, further comprising: performing the step of executing the LTM cell switch procedure responsive to receiving lower layer signalling requesting the execution of the LTM cell switch procedure.

3. The method of claim 1 or 2, wherein the one or more actions comprise one or more of: releasing the first SCG, suspending the first SCG, adding the first SCG, reconfiguring the first SCG, deactivating the first SCG, activating the first SCG, resuming the first SCG, and continuing use of the first SCG.

4. The method of any one of claims 1 to 3, further comprising: receiving an indication from the source node, the target node or a third network node of the one or more actions in relation to the first SCG.

5. The method of any claim 4 wherein the method further comprises: receiving the indication of the one or more actions in a Radio Resource Control configuration.

6. The method of any claim 4 wherein the method further comprises: receiving the indication of the one or more actions in a lower layer signalling.

7. The method of claim 6 or 7 wherein the lower layer signalling is received from the target node, to source node or a third network node, wherein the third network node provides the first Secondary Cell Group.

8. The method of any previous claim wherein the one or more actions comprises releasing the first SCG, wherein the first SCG comprises an existing SCG and the after LTM cell switch the UE is only configured with an MCG without an SCG.

9. The method of any previous claim wherein the first SCG comprises part of the UE configuration prior to the LTM cell switch procedure, or part of a LTM candidate target configuration.

10. The method of any previous claim further comprising: transmitting an indication of second SCG that has been configured after execution of the LTM cell switch procedure or will be configured during execution of the LTM procedure.

11. The method of claim 10 wherein the indication is transmitted to the target node, the source node or a third node.

12. A method performed by a source node providing a user equipment with a Master Cell Group, MCG, the method comprising: executing (902) a layer 1/layer 2 based inter-cell mobility, LTM, cell switch procedure for the user equipment from the source node to a target node; and during execution of the LTM cell switch procedure, obtaining (904) one or more actions in relation to a first Secondary Cell Group.

13. The method of claim 12 further comprising: transmitting lower layer signalling to the UE requesting the execution of the LTM cell switch procedure.

14. The method of claim 12 or 13, wherein the one or more actions comprise one or more of: releasing the first SCG, suspending the first SCG, adding the first SCG, reconfiguring the first SCG, deactivating the first SCG, activating the first SCG, resuming the first SCG, and continuing use of the first SCG.

15. The method of any one of claims 12 to 14, further comprising: transmitting an indication of the one or more actions to the UE.

16. The method of claim 15, wherein the indication is transmitted in lower layer signalling, or comprised in a LTM candidate target cell configuration.

17. The method of any one of claims 12 to 14, wherein the first SCG comprises part of the UE configuration prior to the LTM cell switch procedure, or the first SCG comprises part of a LTM candidate target configuration.

18. The method of any one of claims 12 to 17, wherein the step of obtaining comprises: transmitting a request for the one or more actions to a target network node; and receiving an indication of the one or more actions from the target network node.

19. The method of any one of claims 12 to 17, wherein the step of obtaining comprises: transmitting a request for the one or more actions to a third network node, wherein the third network node provides the first Secondary Cell Group; and receiving an indication of the one or more actions from a third network node.

20. The method of any one of claims 12 to 19, further comprising: receiving an indication of second SCG that has been configured after execution of the LTM cell switch procedure or will be configured during execution of the LTM procedure.

21. A method performed by a target node for providing a user equipment with a Master Cell Group, MCG, the method comprising: executing (1002) a layer 1/layer 2 based inter-cell mobility, LTM, cell switch procedure for the user equipment from a source node to the target node in the MCG, and after or during execution of the LTM cell switch procedure, obtaining (1004) one or more actions in relation to a first Secondary Cell Group.

22. The method of claim 21 wherein the one or more actions comprise one or more of: releasing the first SCG, suspending the first SCG, adding the first SCG, reconfiguring the first SCG, deactivating the first SCG, activating the first SCG, resuming the first SCG, and continuing use of the first SCG.

23. The method of claim 21 or 22, further comprising: transmitting an indication of the one or more actions to the UE after execution of the LTM cell switch procedure.

24. The method of claim 23, wherein the indication is transmitted in lower layer signalling, or comprised in a an RRC message.

25. The method of claim 21 or 22, further comprising: transmitting an indication of the one or more actions to the source node or a third network node.

26. The method of any one of claims 21 to 25, wherein the first SCG comprises part of the UE configuration prior to the LTM cell switch procedure, or part of a LTM candidate target configuration.

27. The method of any one of claims 21 to 26, wherein the method further comprises: receiving a request for the one or more actions from the source node, or a third network node.

28. The method of any one of claims 21 to 27, wherein method further comprises: transmitting an indication of the one or more actions to the source node, or a third network node.

29. The method of any one of claims 21 to 28, further comprising: receiving an indication of second SCG that has been configured after execution of the LTM cell switch procedure.

30. A method performed by a third network node for providing a first secondary cell group to a user equipment the method comprising: before, during or after execution of a layer 1/layer 2 based inter-cell mobility, LTM, cell switch procedure for the user equipment from a source node to a target node for a Master Cell Group, obtaining (1102) one or more actions in relation to the first Secondary Cell Group.

31. The method of claim 30 wherein the one or more actions comprise one or more of: releasing the first SCG, suspending the first SCG, adding the first SCG, reconfiguring the first SCG, deactivating the first SCG, activating the first SCG, resuming the first SCG, and continuing use of the first SCG.

32. The method of claim 30 or 31, further comprising: transmitting an indication of the one or more actions to the UE before or after execution of the LTM cell switch procedure.

33. The method of claim 32, wherein the indication is comprised in a LTM candidate target cell configuration, or in lower layer signalling.

34. The method of claim 30 or 31, further comprising: transmitting an indication of the one or more actions to the source node or the target node.

35. The method of any one of claim 30 to 34, wherein the first SCG comprises part of a LTM candidate target configuration.

36. The method of any one of claims 30 to35, wherein the step of obtaining comprises: receiving a request for the one or more actions to the source node.

37. The method of any one of claims 30 to 36, wherein the step of obtaining comprises: receiving an indication of the one or more actions from the target node.

38. A user equipment, UE, for communicating with a source node in a Master Cell Group, the UE comprising processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the UE is operable to: execute (802) a layer 1/layer 2 based inter-cell mobility, LTM, cell switch procedure from the source node to a target node, and after or during execution of the LTM cell switch procedure, perform (804) one or more actions in relation to a first Secondary Cell Group.

39. The UE as claimed in claim 38 wherein the memory contains further instructions executable by the processing circuitry whereby the UE is operable to perform the method as claimed in any one of claims 2 to 11.

40. A source node for providing a user equipment with a Master Cell Group, MCG, the source node comprising processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the source node is operable to: execute (902) a layer 1/layer 2 based inter-cell mobility, LTM, cell switch procedure for the user equipment from the source node to a target node; and during execution of the LTM cell switch procedure, obtain (904) one or more actions in relation to a first Secondary Cell Group.

41. The source node as claimed in claim 40 wherein the memory contains instructions executable by the processing circuitry whereby the source node is operable to perform the method as claimed in any one of claims 13 to 20.

42. A target node for providing a user equipment with a Master Cell Group, MCG, the target node comprising processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the target node is operable to: execute (1002) a layer 1/layer 2 based inter-cell mobility, LTM, cell switch procedure for the user equipment from a source node to the target node in the MCG, and after or during execution of the LTM cell switch procedure, obtain (1004) one or more actions in relation to a first Secondary Cell Group.

43. The target node as claimed in claim 42 wherein the memory contains further instructions executable by the processing circuitry whereby the target node is operable to perform the method as claimed in any one of claims 22 to 29.

44. A third network node for providing a first secondary cell group to a user equipment, the third network node comprising processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the third network node is operable to: before, during or after execution of a layer 1/layer 2 based inter-cell mobility, LTM, cell switch procedure for the user equipment from a source node to a target node for a Master Cell Group, obtain (1102) one or more actions in relation to the first Secondary Cell Group.

45. The third network node as claimed in claim 44 wherein the memory contains further instructions executable by the processing circuitry whereby the third network node is operable to perform the method as claimed in any one of claims 31 to 37.

46. A computer program, comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out a method according to any of claims 1 to 37.

47. A computer-readable medium comprising instructions that, when executed on at least one processor, cause the at least one processor to perform the method according to any of claims 1 to 37.

48. A computer program product comprising non transitory computer readable media having stored thereon a computer program according to claim 46.