Methods, apparatus and computer-readable media related to dual-connectivity in wireless networks

Abstract

A method is performed by a first network node The first network node is a master node or a serving node configured for a user equipment (UE). The method comprises receiving, from one or more second network nodes, first information comprising at least one UE-associated metric for dual connectivity and / or at least one non-UE associated metric for dual connectivity. The one or more second network nodes comprise at least one secondary node configured for the UE and / or at least one candidate secondary node for the UE. The at least one UE-associated metric for dual connectivity relates to a single UE served by the first network node. The at least one non-UE associated metric for dual connectivity is not specific to a single UE, and comprises a measurement and / or a prediction associated with a plurality of user equipments and / or at least one network entity.

Description

METHODS, APPARATUS AND COMPUTER-READABLE MEDIA RELATED TO DUAL-CONNECTIVITY IN WIRELESS NETWORKSTECHNICAL FIELD

[0001] Embodiments of the present disclosure relate to wireless networks, and particularly to methods, apparatus and computer-readable media relating to dual -connectivity in wireless networks.BACKGROUND

[0001] The current 5G Radio Access Network (RAN) (Next Generation (NG) RAN (NG- RAN)) architecture is depicted and described in the 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 38.401 vl8.0.0 as follows.

[0002] Figure 1 illustrates the NG-RAN architecture. The NG-RAN 100 comprises a set of gNBs 101, 102 connected to the 5G Core (5GC) 103 through the NG interface.

[0003] As specified in TS 38.300, the NG-RAN 100 could also comprise a set of ng-eNBs, an ng-eNB may comprises an ng-eNB- Central Unit (CU) and one or more ng-eNB- Distributed Unit(s) (DU(s)). An ng-eNB-CU and an ng-eNB-DU are connected via W1 interface. The general principle described here also applies to ng-eNB and W1 interface, if not explicitly specified otherwise.

[0004] A gNB 101, 102 can support Frequency Division Duplex (FDD) mode, Time Division Duplex (TDD) mode or dual mode operation.

[0005] The gNBs 101, 102 can be interconnected through the Xn interface.

[0006] A gNB 102 may comprise a gNB-CU 104 and one or more gNB-DU(s) 105. A gNB- CU 104 and a gNB-DU 105 is connected via Fl interface.

[0007] One gNB-DU 105 is connected to only one gNB-CU 104.

[0008] NG, Xn, and Fl are logical interfaces.

[0009] For NG-RAN 100, the NG and Xn-C interfaces for a gNB 102 comprising a gNB-CU 104 and gNB-DUs 105, terminate in the gNB-CU 104. For Evolved Universal Terrestrial RAN (E-UTRAN) New Radio (NR) Dual Connectivity (DC) (EN-DC), the Sl-U and X2-C interfaces for a gNB 102 comprising a gNB-CU 104 and gNB-DUs 105, terminate in the gNB- CU 104. The gNB-CU 104 and connected gNB-DUs 105 are only visible to other gNBs 101 and the 5GC 103 as a gNB 102.

[0010] The overall architecture for separation of gNB-CU- Control Plane (CP) and gNB-CU-User Plane (UP) is depicted in Figure 2. A gNB 200 may comprise a gNB-CU-CP 201, multiple gNB-CU-UPs 202 and multiple gNB-DUs 203. The gNB-CU-CP 201 is connected to the gNB-DU 203 through the Fl-C interface. The gNB-CU-UP 202 is connected to the gNB- DU 203 through the Fl-U interface. The gNB-CU-UP 202 is connected to the gNB-CU-CP 201 through the El interface. One gNB-DU 203 is connected to only one gNB-CU-CP 201. One gNB-CU-UP 202 is connected to only one gNB-CU-CP 201.

[0011] The architecture shown in Figure 2 is what 3 GPP has defined for 5G. Other standardization groups, such as the Open RAN (0-RAN) Alliance, have further extended the architecture above and have for example split the gNB-DU into two further nodes connected by a fronthaul interface. The lower node of the split gNB-DU would contain the Physical (PHY) protocol and the Radio Frequency (RF) parts, the upper node of the split gNB-DU would host the Radio Link Control (RLC) and Medium Access Control (MAC). In 0-RAN, the upper node is called Open-DU (0-DU), while the lower node is called Open-RU (O-RU).Multi-Radio Dual Connectivity (MR-DC)

[0012] MR-DC is a generalization of the Intra-E-UTRA DC described in TS 36.300 v.18.0.0, where a multiple Receiving (Rx) / Transmitting (Tx) capable User Equipment (UE) may be configured to utilise resources provided by two different nodes connected via non-ideal backhaul, one providing NR access and the other one providing either E-UTRA or NR access. One node acts as the Master Node (MN) and the other as the Secondary Node (SN). The MN and SN are connected via a network interface and at least the MN is connected to the core network. The MR-DC network architecture for the NR-DC case is shown in Figure 3, in which an MN 301 is connected to an SN 302 via the Xn-C interface, and the MN 301 is connected to an Access and Mobility Management Function (AMF) 303 via the NG-C interface.Release 19 (Rel-19) 3GPP discussions on the support for Artificial intelligence (Al) and / or Machine Learning (ML) (AIML) in RAN for NR-DC

[0013] Qualcomm in their contribution RP -233022 suggest the study and specification of signaling enhancements for Release 18 (Rel-18) AI / ML based mobility optimization use case for AI / ML based on Primary Secondary Cell (SCell) (PSCell) mobility (e.g. predicting PSCells), AI / ML based on Conditional Handover (CHO) (e.g., predicting CHO candidate / target cells), AI / ML based on Layer 1 (Ll) / Layer 2 (L2) Triggered Mobility (LTM) (e.g., predicting LTM candidate / target cell(s) and beam(s)), for both split and non-split gNB architectures as potential Release 19 study items.

[0014] Xiaomi in their contribution RP-233554 suggest that the following Rel-18 leftovers can be further considered in Rel-19: Mobility optimization for NR-DC, UE Trajectory prediction, Continuous Minimization of Drive Tests (MDT), coordination with SA2 / SA5 may be needed.

[0015] ZTE in their contribution RP-233622 propose that while traffic steering in NR-DC scenarios is covered in Technical Report (TR) 37.817, NR-DC scenarios have been given lower priority in Rel-18. The suggested focus is to investigate AI / ML-based solutions for optimizing mobility in NR-DC scenarios. Some essential parts can be transferring the predicted / measured UE trajectory and UE performance feedback between MN and SN nodes.

[0016] Huawei in their contribution RP -233677 mention that it is proposed to specify the inference-based NR-DC case in Rel-19.SUMMARY

[0017] There currently exist certain challenge(s). The published technology so far has not specified any signaling support for inference-based use-cases with NR-DC, in the context of core NR-DC procedures which determine addition, change, or removal of one or more cells to the UE.

[0018] Using measurement-based or heuristic-based algorithms to handle NR-DC procedures may be slow, or take longer to converge, in addition to possibly taking more resources in terms of signaling or control plane resources.

[0019] With the presence of multiple candidate nodes which could be used as secondary nodes to a UE, finding the optimal node / cell to connect to at all times may require a lot of measurements and signaling.

[0020] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Embodiments of the present disclosure relate to the exchange of UE- associated and non-UE-associated metrics between network nodes in the context of dual connectivity. The network nodes are the nodes that either are serving the UE currently, e.g., the source node or the MN, or nodes that are candidates to serve the UE, e.g., a candidate SN, or nodes that are already configured as part of the Secondary Cell Group (SCG) to the UE. The use-cases emerging from the exchange of the following different categories of metrics is explored in the present disclosure: quantifiers of existing performance, i.e., measured metrics, predictions, i.e., values derived based on AI / ML functions using existing measurements as one of the inputs, andother indications that may either be associated to a single UE or may indicate metrics related to a gNB that may either be current or candidate MN or SN.

[0021] The exchanged values facilitate NR-DC related operations, such as secondary node addition / change, MN change, etc. The present disclosure discusses the different use-cases of exchanging such metrics, in addition to configuration and reporting parameters for such metrics.

[0022] In a first aspect of the disclosure, there is provided a method performed by a first network node. The first network node is a master node or a serving node configured for a UE. The method comprises receiving, from one or more second network nodes, first information comprising at least one UE-associated metric for dual connectivity and / or at least one non-UE associated metric for dual connectivity. The one or more second network nodes comprise at least one secondary node configured for the UE and / or at least one candidate secondary node for the UE. The at least one UE-associated metric for dual connectivity relates to a single UE served by the first network node. The at least one non-UE associated metric for dual connectivity is not specific to a single UE, and comprises a measurement and / or a prediction associated with a plurality of UEs and / or at least one network entity.

[0023] In a second aspect of the disclosure, there is provided a method performed by a second network node. The second network node comprises a secondary node configured for a UE and / or a candidate secondary node for the UE. The method comprises sending, to a first network node, first information comprising at least one UE associated metric for dual connectivity and / or at least one non-UE associated metric for dual connectivity. The first network node is a master node or a serving node configured for the UE. The at least one UE- associated metric for dual connectivity relates to a single UE served by the first network node. The at least one non-UE associated metric for dual connectivity is not specific to a single UE, and comprises a measurement and / or a prediction associated with a plurality of UEs and / or at least one network entity.

[0024] In a third aspect of the disclosure, there is provided a first network node. The first network node comprises processing circuitry configured to cause the first network node to receive, from one or more second network nodes, first information comprising at least one UE associated metric for dual connectivity and / or at least one non-UE associated metric for dual connectivity. The first network node is a master node or a serving node configured for a UE. The one or more second network nodes comprise at least one secondary node configured for the UE and / or at least one candidate secondary node for the UE. The at least one UE-associatedmetric for dual connectivity relates to a single UE served by the first network node. The at least one non-UE associated metric for dual connectivity is not specific to a single UE, and comprises a measurement and / or a prediction associated with a plurality of UEs and / or at least one network entity.

[0025] In a fourth aspect of the disclosure, there is provided a first network node adapted to perform the method according to any embodiment of the first aspect.

[0026] In a fifth aspect of the disclosure, there is provided a computer program product comprising code which, when executed by processing circuitry of a first network node, causes the first network node to perform the method of any embodiment of the first aspect.

[0027] In a sixth aspect of the disclosure, there is provided a second network node. The second network node comprises processing circuitry configured to cause the second network node to send, to a first network node, first information comprising at least one UE associated metric for dual connectivity and / or at least one non-UE associated metric for dual connectivity. The first network node is a master node or a serving node configured for a UE. The second network node comprises a secondary node configured for the UE, and / or a candidate secondary node for the UE. The at least one UE-associated metric for dual connectivity relates to a single UE served by the first network node. The at least one non-UE associated metric for dual connectivity is not specific to a single UE, and comprises a measurement and / or a prediction associated with a plurality of UEs and / or at least one network entity.

[0028] In a seventh aspect of the disclosure, there is provided a second network node adapted to perform the method according to any embodiment of the second aspect.

[0029] In an eighth aspect of the disclosure, there is provided a computer program product comprising code which, when executed by processing circuitry of a second network node, causes the second network node to perform the method of any embodiment of the second aspect.

[0030] Certain embodiments may provide one or more of the following technical advantage(s).The embodiments may facilitate exchange of information (either measurements or predictions) that makes it feasible to observe or extrapolate a resulting change in the performance observed by a UE when a change in the Master Cell Group (MCG) or SCG configuration shall be performed.- By exchanging UE-associated and non-UE-associated metrics, both cell / node-level and UE-level impacts on the expected performance can be analyzed.Trial-and-error or blind configuration-based approaches which may lead a significant number of NR-DC operations that result in no improvement, or even a performance degradation at the UE can be avoided.BRIEF DESCRIPTION OF THE DRAWINGS

[0002] 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:

[0003] Fig. l is a schematic diagram illustrating NG-RAN architecture;

[0004] Fig. 2 is a schematic diagram illustrating an overall architecture for the separation of gNB-CU-CP and gNB-CU-UP;

[0005] Fig. 3 is a schematic diagram illustrating MR-DC network architecture for NR-DC;

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

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

[0008] Fig. 6 shows a signalling flow according to embodiments of the disclosure in a scenario where a UE is in dual connectivity with an MN and an SN;

[0009] Fig. 7 shows a signalling flow according to embodiments of the disclosure in a scenario where a UE becomes configured with dual connectivity;

[0010] Fig. 8 shows a signalling flow according to embodiments of the disclosure in a scenario where a first network node (MN) identifies multiple candidate SNs;

[0011] Figs. 9 and 10 show signalling flows according to embodiments of the disclosure in which UE-associated metrics for dual connectivity are requested;

[0012] Figs. 11 to 15 show signalling flows according to embodiments of the disclosure in which UE-associated metrics for dual connectivity are reported;

[0013] Figs. 16 and 17 show signalling flows according to embodiments of the disclosure in which non-UE associated information enables a serving network node to deduce a network node to select as SN;

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

[0015] Fig. 19 shows a UE in accordance with some embodiments;

[0016] Figs. 20a and b show network nodes in accordance with some embodiments; and

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

[0018] 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.

[0031] In the description of embodiments below, NR is used as an example radio access technology and the gNB / gNB-CU is the logical function in the RAN making use of an AIML inference function. However, the case where the AIML inference function is deployed at a gNB-DU (instead of a gNB-CU) is also possible and should be regarded as covered by the embodiments of the present disclosure. Moreover, embodiments of the present disclosure can apply as well to other radio access technologies, such as 4G and 6G and the logical entities hosting the AI / ML algorithms deriving the predictions described can comprise any of such radio access technology nodes.

[0032] Embodiments of the present disclosure are described for NR-DC, but they can apply also to other forms of MR-DC, e.g., to EN-DC.

[0033] In embodiments of the present disclosure, the first network node is often exemplified as a MN for a UE in dual connectivity (or, if the UE is initially in single connectivity, the network node that will become the MN, or can potentially become the MN), and the second network node is the SN. Note, however, that for the scenarios where a UE is already in dual connectivity, the role of the first network node can be either the MN or the SN. Accordingly, the role of the second network node will be respectively the SN or the MN. In some cases, more “second network nodes” are involved, e.g., when the MN sends request to collect information from a plurality of candidate network nodes.

[0019] Figure 4 depicts a method in accordance with particular embodiments. The method of Figure 4 may be performed by a first network node (e.g. the network node 1810 or network node 2000 as described later with reference to Figures 18 and 20 respectively). The method involves interactions with one or more second network nodes. The first and / or second network nodes may comprise radio access network nodes. In one example, the first network node is a master node configured for a UE and the one or more second network nodes comprise at least one secondary node and / or at least one candidate secondary node for the UE (e.g., within the context of a UE configured with dual connectivity, or for the purposes of configuring the UE with dual connectivity). In another example, the first network node is a secondary node or a candidate secondary configured for a UE and the one or more second network nodes compriseat least one master node for the UE, and / or a candidate secondary network node for the UE. In a further example, the first node is a serving node (e.g., for a UE not in dual connectivity), and the one or more second network nodes comprise at least one candidate secondary network node for the UE. Figure 5 below depicts a complementary method performed by a second network node.

[0020] The method begins at step 402, in which the first network node sends, to one or more second network nodes, a first message comprising a request for the one or more second network nodes to report first information comprising one or more UE-associated metrics for dual connectivity and / or one or more non-UE-associated metrics for dual connectivity (e.g., NR-DC, and / or dual connectivity according to any other wireless standard). Further detail regarding the transmission of a request to the one or more second network nodes is set out below in the section entitled “Reporting dual connectivity related metrics upon request”. It will be noted that step 402 is optional, and the second network node(s) may send first information as defined herein without any need for a request (or an explicit request). Further detail regarding such embodiments is set out below in the section entitled “Reporting dual connectivity related metrics without a preceding request, or in case of implicit request”.

[0021] In this context, the at least one UE-associated metric for dual connectivity may be associated with at least one UE served by the first network node and / or the one or more second network nodes. In one particular example, the at least one UE-associated metric for dual connectivity may relate to a single UE served by the first network node and / or the one or more second network nodes. For example, the at least one UE-associated metric for dual connectivity may comprise any one or more of the following: one or more metrics of a network node associated with a UE; one or more UE metrics; one or metrics related to a UE trajectory; and one or more predicted RAN delay components. Further detail may be found below in the section entitled “UE associated metrics for dual connectivity”.

[0022] The at least one non-UE associated metric for dual connectivity may comprise a measurement and / or a prediction associated with a plurality of user equipments and / or at least one network entity, such as a network entity involved in a dual connectivity operation for at least one UE, a network entity previously involved in a dual connectivity operation for at least one UE, or a network entity that is a candidate for being involved in a dual connectivity operation for at least one UE. The at least one non-UE associated metric for dual connectivity may relate to one or more of the following: a network node; an entity served and / or controlled by a network node; an entity served and / or controlled by a network function; a function served and / or controlled by a network node; a function served and / or controlled by a network function;and a set of UEs sharing at least one common characteristic. The at least one non-UE associated metric for dual connectivity may comprise one or more of the following: one or more network node related metrics; one or more resource related metrics; one or more energy related metrics; one or more metrics relating to a group of UEs; and one or more predicted RAN delay components. Further detail may be found below in the section entitled “Non-UE associated metrics for dual connectivity”.

[0023] In some embodiments, the first information may further comprise one or more of the following: an MCG recovery failure cause; an SCG failure cause; a PSCell identifier; and a time elapsed between an MCG failure and an SCG failure.

[0024] UE / Non-UE associated metrics for dual connectivity may comprise: metrics collected / predicted when Dual-Connectivity is already in use (in this case they can be used to judge how the NR-DC performs, or how it will perform, and whether a change in UE configuration is required / appropriate); and / or metrics collected / predicted when DualConnectivity is NOT yet in use (in which case they can be used to judge whether a change from single connectivity to NR-DC is required / appropriate). UE / Non-UE associated metrics for dual connectivity can be collected from one or more of: nodes (MN or SN) already involved in NR-DC for a UE; nodes (e.g. neighbor of an SN, or neighbor of the MN) which are currently not involved in NR-DC; and / or (in case of UE in single connectivity) nodes neighboring the node currently serving the UE (the future MN).

[0025] Any of the at least one UE-associated metric and / or the at least one non-UE associated metric may additionally be defined for single connectivity; that is, metrics associated with single-connectivity for the UE may be re-purposed for dual connectivity.

[0026] Step 402 may further comprise the first network node sending or transmitting additional information to the one or more second network nodes. The additional information may be included in the first message, or sent in one or more additional messages. For example, the additional information may comprise one or more parameters relating to or characterizing a UE for which the one or more UE-associated metrics for dual connectivity are requested. In another example, the additional information may comprise one or more target values (e.g., time-varying parameters) for the one or more UE-associated metrics for dual connectivity and / or the one or more non-UE associated metrics for dual connectivity. The additional information may comprise one or more of: weights and / or priorities for the one or more UE- associated metrics for dual connectivity; and / or weights and / or priorities for the one or more non-UE associated metrics for dual connectivity.

[0027] The first message (or a different message) may additionally configure one or more conditions upon which the one or more second network nodes are to report the first information, and / or collect the first information. For example, the one or more second network nodes may be configured to report the first information responsive to: the at least one UE-associated metric and / or the at least one non-UE associated metric reaching a specific value; or the at least one UE-associated metric and / or the at least one non-UE associated metric being within a value range. In a further example, the first message may comprise one or more configuration parameters for: configuring the second network node for the reporting of the first information; and / or configuring the second network node for collecting the at least one UE-associated metric and / or the at least one non-UE associated metric. Further detail is set out below in the sections entitled “Configuration parameters for requesting metrics for dual connectivity” and “Configuration parameters for collecting and reporting metrics for dual connectivity”.

[0028] In step 404, the first network node receives, from one or more second network nodes, first information comprising at least one UE associated metric for dual connectivity and / or at least one non-UE associated metric for dual connectivity. The first network node may receive the first information from a second network node: whilst a UE operating in single connectivity is being reconfigured to operate in dual connectivity with the first network node and the second network node; whilst a UE is operating in dual connectivity with the first network node and the second network node; whilst a UE operating in dual connectivity with the first network node and the second network node is being reconfigured to operate in single connectivity; or whilst a dual connectivity operation of a UE operating in dual connectivity with the first network node and the second network node is modified by changing a secondary node and / or a master node of the UE.

[0029] In step 406, the first network node determines, based at least in part on the first information, one or more actions relating to dual connectivity or handover for a UE. For example, the one or more actions may comprise at least one of the following: an initiation of a secondary node addition for a UE; an initiation of a secondary node change for a UE; an initiation of a secondary node modification for a UE; an initiation of a secondary node release for a UE; an initiation of a handover procedure for a UE; and a type of bearer to be configured for a UE.

[0030] The first information may be provided as an input for one or more machine learning models or functions deployed at the first network node, or in a third network node (e.g., a core network node, or a server connected to the network). The machine learning models or functions may be utilized to determine the one or more actions set out above or for a different purpose(e.g., to derive predictions of the one or more UE-associated metrics and / or the one or more non-UE associated metrics). Thus, the first information may be used as at least one of: an input for training, validating, testing, and / or retraining the machine learning model or function; an input for triggering a retraining of the machine learning model or function; and an input and / or feedback for the machine learning model or function.

[0031] In further embodiments, the method may additionally comprise the first network node indicating to the one or more second network nodes one or more of: that the one or more second network nodes are to pause or terminate the reporting of the one or more UE-associated metrics for dual connectivity and / or the one or more non-UE associated metrics for dual connectivity; that the one or more second network nodes are to continue the reporting of the one or more UE-associated metrics for dual connectivity and / or the one or more non-UE associated metrics for dual connectivity; and that the one or more second network nodes are to initiate and / or resume the reporting of the one or more UE-associated metrics for dual connectivity and / or the one or more non-UE associated metrics for dual connectivity.

[0032] Figure 5 depicts a method in accordance with particular embodiments. The method of Figure 5 may be performed by a second network node (e.g. the network node 1810 or network node 2000 as described later with reference to Figures 18 and 20 respectively). The method involves interactions with a first network node. The first and / or second network nodes may comprise radio access network nodes. In one example, the first network node is a master node configured for a UE and the one or more second network nodes comprise at least one secondary node and / or at least one candidate secondary node for the UE (e.g., within the context of a UE configured with dual connectivity, or for the purposes of configuring the UE with dual connectivity). In another example, the first network node is a secondary node or a candidate secondary configured for a UE and the one or more second network nodes comprise at least one master node for the UE, and / or a candidate secondary network node for the UE. In a further example, the first node is a serving node (e.g., for a UE not in dual connectivity), and the one or more second network nodes comprise at least one candidate secondary network node for the UE. Figure 4 above depicts a complementary method performed by a first network node.

[0033] The method begins at step 502, in which the second network node receives, from the first network node, a first message comprising a request for the one or more second network nodes to report first information comprising one or more UE-associated metrics for dual connectivity and / or one or more non-UE-associated metrics for dual connectivity (e.g., NR- DC, and / or dual connectivity according to any other wireless standard). Further detailregarding the reception of a request from the first network node is set out below in the section entitled “Reporting dual connectivity related metrics upon request”. It will be noted that step 502 is optional, and the second network node(s) may send first information as defined herein without any need for a request (or an explicit request). Further detail regarding such embodiments is set out below in the section entitled “Reporting dual connectivity related metrics without a preceding request, or in case of implicit request”.

[0034] In this context, the at least one UE-associated metric for dual connectivity may be associated with at least one UE served by the first network node and / or the one or more second network nodes. In one particular example, the at least one UE-associated metric for dual connectivity may relate to a single UE served by the first network node and / or the one or more second network nodes. For example, the at least one UE-associated metric for dual connectivity may comprise any one or more of the following: one or more metrics of a network node associated with a UE; one or more UE metrics; one or metrics related to a UE trajectory; and one or more predicted RAN delay components. Further detail may be found below in the section entitled “UE associated metrics for dual connectivity”.

[0035] The at least one non-UE associated metric for dual connectivity may comprise a measurement and / or a prediction associated with a plurality of user equipments and / or at least one network entity, such as a network entity involved in a dual connectivity operation for at least one UE, a network entity previously involved in a dual connectivity operation for at least one UE, or a network entity that is a candidate for being involved in a dual connectivity operation for at least one UE. The at least one non-UE associated metric for dual connectivity may relate to one or more of the following: a network node; an entity served and / or controlled by a network node; an entity served and / or controlled by a network function; a function served and / or controlled by a network node; a function served and / or controlled by a network function; and a set of UEs sharing at least one common characteristic. The at least one non-UE associated metric for dual connectivity may comprise one or more of the following: one or more network node related metrics; one or more resource related metrics; one or more energy related metrics; one or more metrics relating to a group of UEs; and one or more predicted RAN delay components. Further detail may be found below in the section entitled “Non-UE associated metrics for dual connectivity”.

[0036] In some embodiments, the first information may further comprise one or more of the following: an MCG recovery failure cause; an SCG failure cause; a PSCell identifier; and a time elapsed between an MCG failure and an SCG failure.

[0037] UE / Non-UE associated metrics for dual connectivity may comprise: metrics collected / predicted when Dual-Connectivity is already in use (in this case they can be used to judge how the NR-DC performs, or how it will perform, and whether a change in UE configuration is required / appropriate); and / or metrics collected / predicted when DualConnectivity is NOT yet in use (in which case they can be used to judge whether a change from single connectivity to NR-DC is required / appropriate). UE / Non-UE associated metrics for dual connectivity can be collected from one or more of: nodes (MN or SN) already involved in NR-DC for a UE; nodes (e.g. neighbor of an SN, or neighbor of the MN) which are currently not involved in NR-DC; and / or (in case of UE in single connectivity) nodes neighboring the node currently serving the UE (the future MN).

[0038] Any of the at least one UE-associated metric and / or the at least one non-UE associated metric may additionally be defined for single connectivity; that is, metrics associated with single-connectivity for the UE may be re-purposed for dual connectivity.

[0039] Step 502 may further comprise the second network node receiving additional information from the first network node. The additional information may be included in the first message, or in one or more additional messages. For example, the additional information may comprise one or more parameters relating to or characterizing a UE for which the one or more UE-associated metrics for dual connectivity are requested. In another example, the additional information may comprise one or more target values (e.g., tie-varying parameters) for the one or more UE-associated metrics for dual connectivity and / or the one or more non- UE associated metrics for dual connectivity. The additional information may comprise one or more of: weights and / or priorities for the one or more UE-associated metrics for dual connectivity; and / or weights and / or priorities for the one or more non-UE associated metrics for dual connectivity.

[0040] The first message (or a different message) may additionally configure one or more conditions upon which the one or more second network nodes are to report the first information, and / or collect the first information. For example, the one or more second network nodes may be configured to report the first information responsive to: the at least one UE-associated metric and / or the at least one non-UE associated metric reaching a specific value; or the at least one UE-associated metric and / or the at least one non-UE associated metric being within a value range. In a further example, the first message may comprise one or more configuration parameters for: configuring the second network node for the reporting of the first information; and / or configuring the second network node for collecting the at least one UE-associated metric and / or the at least one non-UE associated metric. Further detail is set out below in the sectionsentitled “Configuration parameters for requesting metrics for dual connectivity” and “Configuration parameters for collecting and reporting metrics for dual connectivity”.

[0041] In step 504, the second network node transmits, to the first network node, first information comprising at least one UE associated metric for dual connectivity and / or at least one non-UE associated metric for dual connectivity. The first information may be transmitted: whilst a UE operating in single connectivity is being reconfigured to operate in dual connectivity with the first network node and the second network node; whilst a UE is operating in dual connectivity with the first network node and the second network node; whilst a UE operating in dual connectivity with the first network node and the second network node is being reconfigured to operate in single connectivity; or whilst a dual connectivity operation of a UE operating in dual connectivity with the first network node and the second network node is modified by changing a secondary node and / or a master node of the UE.

[0042] In further embodiments, the method may additionally comprise the second network node receiving an indication from the first network node one or more of that the second network node is to pause or terminate the reporting of the one or more UE-associated metrics for dual connectivity and / or the one or more non-UE associated metrics for dual connectivity; that the second network node is to continue the reporting of the one or more UE-associated metrics for dual connectivity and / or the one or more non-UE associated metrics for dual connectivity; and / or that the second network node is to initiate and / or resume the reporting of the one or more UE-associated metrics for dual connectivity and / or the one or more non-UE associated metrics for dual connectivity.Reporting dual connectivity related metrics upon request

[0034] In a first aspect, the first network node sends a request to a second network node for obtaining UE associated metrics for dual connectivity from the second network node. For instance, the MN requests to another network node, performance measurements (or predictions of these) concerning the UE (measurements or predictions as collected by the other network node). Note, here, that measurements and / or predictions can be requested in various circumstances, for example:- the second network node is already the SN for the UE. A set of measurements is requested to support the MN as feedback related to the addition of the SN, i.e., to evaluate whether the decision to add the SN in question was appropriate.- the second network node is already the SN for the UE. A set of predictions is requestedto support the MN in determining how the UE performances will evolve over a certain time interval while the UE is served by the SN, or which performances are expected for the UE in the SN, at / from a specific point in time in the future.- the second network node is currently not serving the UE, and it is a potential candidate node for SN Addition. A set of measurements and / or predictions is requested to support the first network node to assess when it is opportune to add the potential node as SN for the UE, e.g. if the performance the second network node is able to provide is sufficiently good.- the second network node is currently not serving the UE, and it is one of the candidate network nodes for SN Change. A set of measurements and / or predictions is requested to support the first network node to select the second network node as target SN node for an SN Change.- the first network node requests measurements and / or predictions to a number of second network nodes to identify / optimize the list of potential candidate network nodes to be used as candidates for Conditional SN Addition and / or Conditional SN Change.The second network node is already the SN for the UE. A set of measurements and / or predictions are requested so that the MN can decide if it needs to make configuration changes of the SCG within the same SN, including addition, modification or release of the user plane resource configuration. Also, the MN can use the requested measurement / predictions to decide if it needs to activate or deactivate the SCG.The first network node is already the SN for the UE. The first network node requests to the second network node, which is the MN for the UE, a set of measurements and / or predictions so that the SN can decide whether to perform configuration changes of the SCG, e.g. to trigger the modification / release of the user plane resource configuration, to trigger the release of SCG resources (e.g., release SCG lower layer resources but keep SN), and to trigger PSCell changes (e.g. when a new security key is required or when the MN needs to perform Packet Data Convergence Protocol (PDCP) data recovery). The SN can also use the requested measurements / predictions to decide whether to request the MN to provide more Data Radio Bearer (DRB) Identifiers (IDs) to be used for SN terminated bearers or to return DRB IDs used for SN terminated bearers that are not needed any longer. The SN can also use the requested measurements / predictions to decide whether to activate or deactivate the SCG.The first network node is already the SN for the UE. The first network node requests to the second network node, which is the MN for the UE, a set of measurements and / orpredictions so that the SN can decide whether to configure, modify or release intra-SN Conditional PSCell Change (CPC) or intra-SN subsequent Conditional PSCell Addition or PSCell Change (CPAC) configuration. The SN can also use the requested measurements / predictions to decide whether to configure, modify or release intra-SN SCG LTM configuration.The second network node is already the SN for the UE. A set of measurements and / or predictions are requested to support the MN to decide whether to keep or release the SN.A third network node is currently not serving the UE, and it is one of the candidate network nodes for SN Change. A set of measurements and / or predictions is requested from a second network node and / or from the third network node, that may or may not be serving as the SN for the UE to support the first network node to select the third network node as target SN node for an SN Change.

[0035] Details for UE associated metrics for dual connectivity are described below in the section entitled “Reporting dual connectivity related metrics without a preceding request, or in case of implicit request”. The request can comprise configuration parameters identifying the UE associated metrics for dual connectivity, as detailed in the section below entitled “Configuration parameters for requesting metrics for dual connectivity” and / or configuration parameters for collecting and / or reporting the requested information, as detailed in the section below entitled “Configuration parameters for collecting and reporting metrics for dual”.

[0036] In one variant of this first aspect, instead of requesting UE associated metrics for dual connectivity, the first network node sends a request for obtaining non-UE associated metrics for dual connectivity (see details on these metrics in the section below entitled “UE associated metrics for dual connectivity”).

[0037] In a variant of this first aspect, the first network node sends a request for obtaining both UE associated metrics for dual connectivity and non-UE associated metrics for dual connectivity.

[0038] In one option of the first aspect, the first network node includes, in the message comprising the request or in a separate message, parameters characterizing the UE for which UE associated metrics for dual connectivity are being requested. For example, the first network node sends to the second network node Quality of Service (QoS) flow related parameters associated to the bearer used by the UE.

[0039] In a further option of the first aspect, which can be combined with the preceding one,the first network node includes in the message comprising the request (or in a separate message), desired targets for UE associated metrics for dual connectivity (for example, a desired level of throughput increase for the UE if the network node is added for the UE, a level of throughput that the network node should sustain if used as SN for the UE, an extra capacity that the SN can provide, e.g., in terms of bandwidth, or Physical Resource Blocks (PRBs), to the UE). Targets can be expressed as “minimum” values, or “maximum” values, or “allowed” values, or “increase / decrease relative to a reference”. Reference values can optionally be sent together with the target. How these targets can be considered by the node receiving the request in multiple is described in the information request message. Examples are provided below:The targets are considered to indicate metrics ranges or thresholds. If the node receiving the request determines that the requested metrics are within, above or below such limits, the node shall report the metrics to the first node.The targets are considered by the second node as desired values or value ranges for the requested metrics. The node receiving the request shall act in a way that the requested metrics are within, at, above or below the indicated thresholds or ranges. If such conditions are fulfilled, the second node shall report an indication of such fulfilment to the first node.

[0040] In a further option of the above aspect the targets can be communicated as a timevarying parameter, i.e., the expected UE performance as a function of time.

[0041] In a further option of the first aspect, which can be combined with the preceding ones, the first network node includes in the message comprising the request (or in a separate message), desired targets associated to non-UE associated metrics for dual connectivity (for example, an Energy Cost at the second network node in case the second network node is added as SN for the UE or the Energy Source that will be used at the second network node in case the second network node is added as the SN for the UE, in addition to or independently sending an indication if the energy source will change if a UE with a certain desired performance uses the node as an SN). Targets can be expressed as “minimum” values, or “maximum” values, or “allowed” values, or “increase / decrease relative to a reference” or as a “time-series” of values indicating the change in the target parameters over time. Reference values can optionally be sent together with the target.

[0042] In one variant of the first aspect, the first network node sends a message comprising the request for UE associated metrics for dual connectivity and / or non-UE associated metrics for dual connectivity, to a set of second network nodes, and expects that each one of the second network nodes provide the requested piece of information. According to the options detailedabove, the first network node, in the same message (or in separate messages), can send to each second network node of the set of second network nodes, parameters characterizing the UE and / or desired targets for UE associated metrics for dual connectivity and / or non-UE associated metrics for dual connectivity.- For instance, the first network node is currently the only network node serving the UE (i.e., the UE is in single connectivity), and it sends to a set of candidate SNs a request to obtain (from each candidate SN), predicted UE associated metrics for the UE (e.g., predicted UE throughput in Downlink (DL)).In another example, the first network node sends a message to each network node in a set of second network nodes, containing a request to obtain predicted non-UE associated metrics, associated with the second network node receiving the request, or with a function / entity of the second network node receiving the request. o For example, the first network node (to become MN) requests to each one among the set of candidate SNs on how many carrier frequencies, and / or what aggregated bandwidth, and / or how many Multiple-Input Multiple-Output (MIMO) layers the candidate SN predicts it will be able to provide to the UE

[0043] In another variant complementary to the above, the request for UE associated metrics for dual connectivity and / or non-UE associated metrics for dual connectivity contain also weights / priorities for each of the requested metrics. The request can also contain an indication for the metrics that should be mandatorily provided.

[0044] In another variant the request indicates that the metrics should be sent when specific values are reached (event-based reporting) or whenever a certain metric is within a certain value range.

[0045] According to this first aspect, the second network node sends the requested piece of information according to one or more configuration parameters comprised in the request, and, if reporting configuration parameters are also comprised in the request, the reporting proceeds (or terminates) according to the reporting configuration parameters.In one option, before sending the requested piece of information, the second network node sends a response indicating that the request is (fully) successful.In another option, before sending a portion of the requested piece of information, the second network node sends a response indicating that the request is partially successful, and optionally an indication of the parts that were successful and those that failed, and one or more failure causes associated with the failed parts of the request.In another option, the second network node does not provide the requested information,and instead it sends a response indicating that the request failed and optionally one or more associated failure causes.In another option, the second network node may not send a response, either before sending or together with a requested piece of information, that indicates success, partial failure, or failure. The second network node may respond a failure message or with one or more piece of information that was requested for, while the lack of a certain information in the response may implicitly indicate failure.

[0046] The first network node receiving UE associated metrics for dual connectivity and / or non-UE associated metrics for dual connectivity can use the received information: as input for training, validation, testing, or retraining an AIML model deployed at the first network node (or deployed at a third network node) as input for triggering a retraining of an AIML model deployed at the first network node (or deployed at a third network node) as input / feedback for an AIML inference function deployed at the first network node (or deployed at a third network node)

[0047] The first network node determines, based at least in part on the received UE associated metrics for dual connectivity (and / or non-UE associated metrics for dual connectivity) at least one of the following actions:If the UE is in single connectivity towards the first network node, the first network node triggers the addition of the second network node as SN for the UEIf the UE is in single connectivity towards the first network node, the first network node triggers the addition of one of the candidate second network node in the set of second network nodes, as SN for the UEIf the UE is in dual connectivity towards the first network node and the second network node, the first network node triggers an SN ChangeIf the UE is in dual connectivity towards the first network node and the second network node, the first network node initiates an SN ModificationIf the UE is in dual connectivity towards the first network node and the second network node, the first network node initiates the release of the SNIf the UE is in dual connectivity towards the first network node and the second network node, the first network node initiates configuration and execution of CHO with SN or CHO with candidate SCG(s).If the UE is in dual connectivity towards the first network node and the second network node, the first network node initiates inter-MN handover while the UE context at theSN is kept or moved to another SNIf the UE is in dual connectivity towards the first network node and the second network node, the first network node initiates an SN triggered SN change. In this option the first network node is the SN.If the UE is in dual connectivity towards the first network node and the second network node, the first network node initiates an SN triggered SN release. In this option the first network node is the SN.

[0048] The first network node, regardless of a UE being either in single or in dual connectivity together with the second node, may request from nodes that are configured as SN, or are identified as candidate secondary network nodes, information about either UE or non- UE associated metrics for dual connectivity, where the UE associated demand or requirement or expected performance for a UE in this case may not be directly associated with a UE that is connected to the first network node, but is a value or set of values that is requested by the first network node to understand the available capacity at a candidate secondary network node even though there is no real demand from one or a particular group of UEs corresponding to the communicated UE associated demand at the current point in time.

[0049] The UE associated information described in this section may be collected, upon request of a first network node towards a second network node, for one or more UE that is served by the first network node and by the second network node, or by a UE that is served by the second network node but not necessarily served by the first network node. For example, if the first network node request information from a node that is a potential SN, such node may not be serving any UE served also by the first network node. In this case the second node reports UE associated metrics for UEs served by itself, where such UEs may be in locations and coverage conditions similar to those of a UE for which the second node is added as an SN.

[0050] The measurements described in this section may include metrics collected from UEs. In such case, the node(s) receiving a request to collect such measurements shall signal to the corresponding UEs measurements configurations describing the measurement objects the UE shall measure and report to the node that needs to report the requested measurements.

[0051] In one option of this first aspect, the collection of the requested piece of information is implicitly stopped / terminated. The termination / stop can be implicit with the execution of an action by the first network node or the second network node. For instance, if the SN initiates an SN Release, the reporting is implicitly terminated. Another example is for the case of Conditional SN Addition. The MN has initiated a request towards a set of candidate SN, and receives the reporting from each of them. When one of the candidate SN is eventually selectedby the UE, the MN sends an S-NODE RELEASE REQLEST to all the other candidate SN, and this message can be used as an implicit indication for the remaining candidate SN to stop the reporting. Another implicit stop can be due to a procedure initiated by the second network node (or one or the second network node(s)). For example, the SN sends to the MN an NG- RAN NODE CONFIGURATION UPDATE message, indicating that at least one of the object (e.g., a cell in the SN) for which the reporting is ongoing has changed. The reception of this message (or part of its content) can be used as an implicit indication for the MN that no further reporting can be expected from the SN, or that no further reporting can be expected for the concerned object(s).

[0052] In another option of this first aspect, the collection of the requested piece of information is explicitly stopped / terminated. For example, if predicted UE performance are used by the first network node to determine which one of a second network node and a third network node is the best candidate for SN Addition (or for SN Change), once the SN Addition is triggered towards one of the two (say, for instance, towards the second network node), the first network node sends towards the third network node (but it can do the same also towards the second network node) a request to stop sending UE associated metrics for dual connectivity and / or non-UE associated metrics for dual connectivity.

[0053] According to another option of this main aspect, a previously issued request for UE associated metrics for dual connectivity and / or non-UE associated metrics for dual connectivity is modified. This means that one of the following updates is made:The list of metrics is updated by adding or removing one or more metrics, or changing the targets for one or more metricsThe list of objects (e.g., cells or beams, or node) for which metrics are requested is updated by adding or removing one or more objectsA combination of the above

[0054] In another option of this first aspect, if the first network node determines an action based at least in part on the piece of information received as per its request, the collection of the information is NOT stopped / terminated, but rather it continues. For instance, the UE is already in dual connectivity with a first network node in the role of the MN and a third network node in the role of the SN. The MN has requested two candidate SNs (first candidate SN, second candidate SN) to provide predicted UE performance on the basis of which the MN determines to trigger an SN Change, where the third network node (current SN) is the source SN, and the first candidate SN is the target SN. The MN does NOT send a (further) request towards the second candidate SN, to stop the reporting from the second candidate SN, and suchreporting continues. This is to ensure that, if in the future, the second candidate SN becomes better than the first candidate SN just added, the MN can perform a subsequent SN Change towards the second candidate SN.

[0055] According to variants of the first aspect (some of which already mentioned above, and here repeated for simplicity), a request to initiate or to resume the reporting of UE associated metrics for dual connectivity and / or non-UE associated metrics for dual connectivity can be issued in various ways:- When a UE is in single connectivity, and the request initiated by the future MN- When a UE is in dual connectivity, and the request can be initiated by the MN or by the SNAs part of a procedure that prepares the reconfiguration of a UE from single connectivity to dual connectivity (e.g., the request can be included in the S-NODE ADDITION REQUEST message used for SN Addition, or for Conditional SN Addition)As part of a procedure that confirms the addition of a node in dual connectivity operation for a UE (e.g., the request can be included in a S-NODE RECONFIGURATION COMPLETE message)- When a UE is in dual connectivity, and the request is initiated by the SN when a Fast MCG Recovery succeeds.- When a UE is in dual connectivity, the MN initiates an SN Change, and the MN sends the request to the source SN- When a UE is in dual connectivity, the MN initiates an SN Change, and the MN sends the request to the target SN- When a UE is in dual connectivity, the SN initiates an SN Change, the SN forwards to the target SN (via the MN) a request previously received by the MN, based on which the target SN can start reporting to the MN o the source SN can optionally send / transfer to the target SN (via the MN) one or more of: configuration parameters for requesting metrics and for collecting / reporting metrics, which the source SN has previously received from the MN; UE associated metrics for dual connectivity (measurements and / or predictions) which the MN has previously requested to the SN; non-UE associated metrics for dual connectivity (measurements and / or predictions) which the MN has previously requested to the SN- When a UE is in dual connectivity, the SN initiates an SN Change, and the SN sendsthe request to the MN- When a UE is in dual connectivity, the MN initiates an inter-MN handover with / without SN change, and the target MN sends the request to the source SN (or the target SN) o In case of inter-MN handover, the source MN can optionally forward to the target MN, configuration parameters for requesting metrics and for collecting / reporting metrics, comprised in a previous request issued (or just prepared) by the source MN towards the source SN. o In case of inter-MN handover, the source MN can optionally forward to the target MN, one or more UE associated metrics for dual connectivity (measurements and / or predictions) and / or non-UE associated metrics which the source MN has previously requested to the SN.- When a UE is in dual connectivity and the SN (or the MN) informs the MN (or the SN) that the SN (or the MN) is capable to provide the requested information- When a UE is in dual connectivity and the request can be initiated by the MN or by the SN as SN modification procedure

[0056] According to other variants of the first aspect (some of which already mentioned above, and here repeated for simplicity), a request to stop or pause the reporting of UE associated metrics for dual connectivity and / or non-UE associated metrics for dual connectivity can be issued:- When a UE is in dual connectivity and the MN determines to release the SN- When a UE is in dual connectivity and the SN determines to be released- When a UE is in dual connectivity and the MN sends an SCG Failure Information Report to the SN- When a UE is in dual connectivity and the SN (or the MN) informs the MN (or the SN) that it is no longer capable to provide the requested information- When a UE reaches dual connectivity and the MN determines that it does not need to monitor any longer- When a UE is in single connectivity and the node serving the UE determines dual connectivity need not be setup for the UE in question.

[0057] According to variants of the first aspect, the reporting of UE associated metrics for dual connectivity and / or non-UE associated metrics for dual connectivity can be issued in various ways:In a message comprised in the same procedure also comprising the request o For example, the request is comprised in an S-NODE ADDITION REQUESTXnAP message, and the report is provided in the corresponding S-NODE ADDITION REQUEST ACKNOWLEDGE XnAP message, or in the corresponding S-NODE ADDITION REQUEST FAILURE XnAP message o In another example, the request is comprised in an S-NODE MODIFICATIONREQUEST XnAP message, and the report is provided in the corresponding S- NODE MODIFICATION REQUEST ACKNOWLEDGE XnAP message, or in the corresponding S-NODE MODIFICATION REQUEST FAILURE XnAP messageIn a message comprised in a procedure that differs from the one carrying the request o For example, the request is comprised in a DATA COLLECTION REQUEST XnAP message, and the report is provided in an associated DATA COLLECTION UPDATE XnAP message.

[0058] According to a variant of the first aspect, the request for UE associated metrics for dual connectivity and / or non-UE associated metrics for dual connectivity is first prepared, with a handshake between a first network node and one or more second network nodes (e.g., reusing existing Information Elements (IES) - or introducing new IES - of the existing Data Collection Reporting Initiation Xn procedure), and later activated. The first network node (or the second network node) activates the request by inserting one (or more) of the Information Elements included in one of the messages used during the handshake stage in another message used for the activation. The presence of the Information Element can be used as a method to indicate that the request is activated.- For example: the MN sends to a set of candidate SN an S-NODE ADDITION REQUEST XnAP message, containing configuration parameters related to the request of UE associated metrics and / or non-UE associated metrics. The message from MN to SN comprises a piece of information (e.g., a Data Collection ID) that will be later used for activating the request. At this stage the candidate SN does not provide the requested metrics, but it acknowledges (or fail, or partially fail) the request. Alternatively, the candidate SN can provide to the MN a part of the requested information. When one of the candidate SN is eventually selected, the MN activates the request (or in the alternative, the reporting of the remaining information is activated), by inserting in the S-NODE RECONFIGURATION COMPLETE XnAP message, the same piece of information (e.g., the Data Collection ID) also comprised in the message carrying the request.

[0059] The information that a first node may request as per the embodiments in this sectionmay be used by an AI / ML function / algorithm to infer one or more of the following:Actions and signalling procedures needed to optimally configure a UE. For example, to add an SN, change an SN, remove an SN, change an MN, modifying an existing NR- DC configuration. In this case the nodes impacted by such configuration changes will need to be signalled with instructions on how to implement the desired configurations and the UE impacted by such configuration changes will have to be reconfigured accordingly.- Derive predictions of metrics that may be used to take actions similar to those described above.

[0060] For this reason, the information received by a first node in accordance with the embodiments described above can be used by an AI / ML algorithm as input data or information from which inputs are derived, as feedback data or reward information or information from which rewards are derived, as training data or information from which training data are derived. This information may also be the output of AI / ML algorithms located at the second node.Reporting dual connectivity related metrics without a preceding request, or in case of implicit request

[0061] In a second aspect of the present disclosure, the first network node requests information to the second network node in a similar way, for similar reasons, in similar conditions and to achieve similar purposes as in the first aspect. However, the second network node sends one or more UE associated metrics for dual connectivity to the first network node and / or one or more non-UE associated metrics for dual connectivity, and there is no preceding request for it, or the request to obtain this piece of information is implicit, or it is specified in a procedural text of the standard.

[0062] In one option of this second aspect, the UE is being reconfigured from single connectivity to dual connectivity with a first network node and a second network node, and one of the network nodes sends to the other, one or more UE associated metrics for dual connectivity and / or non-UE associated metrics for dual connectivity in an existing message (or a new message).- For instance, during a SN Addition preparation, the MN sends to the SN a predicted UE Trajectory for the UE as part of the S-NODE ADDITION REQUEST

[0063] In another option of this second aspect, the UE is in dual connectivity with a first network node and a second network node, and one of the network nodes sends to the other, one or more UE associated metrics for dual connectivity and / or non-UE associated metrics for dualconnectivity in an existing message (or a new message).- For instance, the SN sends measured UE performance within a SECONDARY RAT USAGE REPORT message.

[0064] In another option of this second aspect, a UE is in dual connectivity with a first network node and a second network node, the UE is being reconfigured to single connectivity, and one of the network nodes sends to the other, one or more UE associated metrics for dual connectivity and / or non-UE associated metrics for dual connectivity in an existing message (or a new message).- For instance, the SN sends to the MN measured UE performance within a S-NODE MODIFICATION REQUIRED message, or in an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message.

[0065] In another option of this second aspect, a UE is in dual connectivity with a first network node and a second network node, and the dual connectivity operation is being modified by changing the SN, or the MN, and one of the network nodes sends to the other, one or more UE associated metrics for dual connectivity and / or non-UE associated metrics for dual connectivity in an existing message (or a new message).- For instance, the SN sends to the MN measured UE performance within a S-NODE MODIFICATION REQUIRED message, or in an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message.

[0066] In another option of the second aspect, where a UE may be in dual connectivity with a first network node and a second network node, where there is a change in the load situation of the SN or the MN, and / or where a particular node may not be able to deliver a set of preagreed characteristics (either as part of a prior exchange of UE and non-UE associated metrics for dual connectivity), and / or an inability of a node to fulfill the QoS settings of the associated bearers, and / or an inability to fulfill other higher-level (e.g., application-level QoS / Quality of Experience (QoE)) parameters that may have been possible to deliver before, one of the network nodes sends to the other, one or more UE associated metrics for dual connectivity and / or non-UE associated metrics for dual connectivity in an existing message (or a new message).

[0067] The above situation may manifest together with or independently of radio-related events, such as entering coverage of a different network node leading to poor QoS / QoE on the current node or a change in load on the network node leading to traffic being prioritized. In this option of the second aspect, either the MN or the SN sends to the other, one or more UE associated metrics for dual connectivity and / or non-UE associated metrics for dual connectivityin an existing message (or a new message).UE associated metrics for dual connectivity

[0068] UE associated metrics for dual connectivity refers for a certain object, indicating the granularity at which they are requested / collected / provided. For example, a UE, a node, a cell, a Synchronization Signal Block (SSB) beam, a service type, a communication service, a Secondary Cell Group, a Master Cell Group, a set of cells, etc.

[0069] Measured and predicted UE associated metrics for dual connectivity (e.g., UE performance or UE trajectory) can be used by a network node, or by an AIML model for different purposes such as: as feedback for an AIML model, for (re)training, as input for determining an action related to dual connectivity for a UE (e.g., to trigger an SN Addition, or an SN Change, an SN Removal, to update an existing SCG configuration, etc) as input to determine whether to Conditional HO with SN as input for MN to determine the type of bearers that need to be configured. Also based on that the MN can decide which SN to choose. Maybe prefer the SN with no split bearers for instance as input for the receiving node to decide whether the performance gain achieved by configuring NR-DC for a UE outweighs the cost of such configuration e.g. in terms of resources used, signalling load, etc.

[0070] UE associated metrics for dual connectivity can be:- Network node related metrics associated to a UE o candidate target cells for Conditional PSCell Change (determined or predicted) o Measurements taken by the UE for each candidate PSCell■ This information is provided for different times of a conditional PSCell procedure. For example, the information is collected as soon as a conditional PSCell change is prepared and it comprises measurements taken by the UE at the time of conditional PSCell change configuration; the information can be provided also at the time of conditional PSCell change execution, where the UE provides measurements of cells that the UE can detect when the PSCell change takes place.■ This information enables the node receiving it to deduce patterns in thecandidate PSCell measurements and to derive predictions on which of such candidate PSCells will be the selected PSCell based on the patterns identified from the cell measurements. list of SCells (or number of SCells), determined or predicted List of configured SCells for the UE and UE measurements of each SCell■ This enables the receiving node to take into account the configured SCells and how they are measured by the UE when selecting a target PSCell or when changing a PSCell or when deactivating a PSCell. The node receiving this information can predict whether, by taking any action such as SN addition, change, removal, there can be impacts on how carrier aggregation will work, namely how SCell resources can be aggregated. amount of aggregated resources for the UE (e.g., total PRBs, PRBs in Uplink (UL) / DL, MIMO configurations (e.g. 2x2, 4x4), bands combinations and feature set for the UE■ These statistics enable the node that receives them to understand the configuration the UE is currently using and how that would potentially change in case of e.g. SN addition / modification / removal. The receiving node can therefore foresee if by taking any NR-DC configuration action the overall configuration used by the UE so far will change and whether this can impact the performance with which the UE is served. data volume delivered to / received from the UE (measured or predicted)■ This enables the receiving node to understand the overall amount of traffic the UE is sending and receiving. The receiving node of this information is able to deduce whether it is beneficial, given such amount of UL and DL data volumes, to change the NR-DC configuration for the UE Measurements taken by the UE for each cell used in a NR-DC configuration This information enables the node receiving it to deduce the radio quality of each MCG or SCG and to correlate such radio quality with other statistics such as throughput. The combination of such information enables to derive patterns on how radio signals strength for each cell participating in NR-DC is related to performance related statistics. With this predictions can be made concerning how performance for a UE is going to change given radio measurements of cellsused in NR-DC.- UE related metrics o measured Throughput (e.g., Average, Maximum), separately in UL / DL or total.■ This metric can be provided in a number of ways such as:• Per DRB, where it is possible to deduce the throughput of different types of bearers in NR-DC such as SN terminated SCG bearers, MN terminated SCG bearers, MN terminated MCG bearers, SN terminated MCG bearers.• Per slice throughput, namely the UL / DL throughput for all services of a given network slice■ With this information it is possible to deduce how well a bearer is served by the node part of the NR-DC configuration. This enables to derive patterns about how throughput changes in dependence to other metrics and about how to derive which NR-DC configuration change to take in order to maximise throughput■ This metric can also be used as feedback information to judge how well predictions on this metrics were made or how other actions such as NR- DC reconfigurations affected the metric o predicted Throughput (e.g., Average, Maximum), separately in UL / DL or total.■ This metric can be provided in a number of ways such as:• Per DRB, where it is possible to deduce the predicted throughput of different types of bearers in NR-DC such as SN terminated SCG bearers, MN terminated SCG bearers, MN terminated MCG bearers, SN terminated MCG bearers.• Per slice predicted throughput, namely the UL / DL throughput for all services of a given network slice■ With this information it is possible to deduce how well a bearer is foreseen to be served by the node part of the NR-DC configuration. This enables the node receiving the metric to deduce whether future NR-DC configurations changes are needed. For example, if the predicted throughout for one or more SCG bearers is not sufficiently high, an SN change action may be planned and executed o measured Packet Loss (e.g., Average, Maximum), separately in UL / DL or total.■ This metric can be provided in a number of ways such as:• Per DRB, where it is possible to deduce the packet loss of different types of bearers in NR-DC such as SN terminated SCG bearers, MN terminated SCG bearers, MN terminated MCG bearers, SN terminated MCG bearers.• Per slice packet loss, namely the UL / DL packet loss for all services of a given network slice■ This metric enables to evaluate the current packet loss performance for the UE, for each node taking part in the NR-DC configuration and for each bearer. The metric enables to deduce patterns on how such performance varies together with other metrics.■ This metric can also be used as feedback information to judge how well predictions on this metrics were made or how other actions such as NR- DC reconfigurations affected the metric predicted Packet Loss (e.g., Average, Maximum), separately in UL / DL or total.■ This metric can be provided in a number of ways such as:• Per DRB, where it is possible to deduce the predicted packet loss of different types of bearers in NR-DC such as SN terminated SCG bearers, MN terminated SCG bearers, MN terminated MCG bearers, SN terminated MCG bearers.• Per slice predicted packet loss, namely the UL / DL packet loss for all services of a given network slice■ With this information it is possible to deduce how well a bearer is foreseen to be served by the node part of the NR-DC configuration. This enables the node receiving the metric to deduce whether future NR-DC configurations changes are needed. For example, if the predicted packet loss for one or more SCG bearers is not sufficiently low, an SN change action may be planned and executed measured Packet Delay (e.g., Average, Maximum), separately in UL / DL or total.■ This metric can be provided in a number of ways such as:• Per DRB, where it is possible to deduce the packet delay of different types of bearers in NR-DC such as SN terminated SCGbearers, MN terminated SCG bearers, MN terminated MCG bearers, SN terminated MCG bearers.• Per slice packet delay, namely the UL / DL packet delay for all services of a given network slice■ This metric enables to evaluate the current packet delay performance for the UE, for each node taking part in the NR-DC configuration and for each bearer. The metric enables to deduce patterns on how such performance varies together with other metrics.■ It is worth noting that packet delay needs to be coordinated between the SCG and the MCG. Namely, this metric cannot be very different between the two transmission legs. Therefore knowledge of this metric, in conjunction with other metrics, enables to determine patterns that may lead to a divergence between packet delays in the MCG and in the SCG■ This metric can also be used as feedback information to judge how well predictions on this metrics were made or how other actions such as NR- DC reconfigurations affected the metric predicted Packet Delay (e.g., Average, Maximum), separately in UL / DL or total.■ This metric can be provided in a number of ways such as:• Per DRB, where it is possible to deduce the predicted packet delay of different types of bearers in NR-DC such as SN terminated SCG bearers, MN terminated SCG bearers, MN terminated MCG bearers, SN terminated MCG bearers.• Per slice predicted packet delay, namely the UL / DL predicted packet delay for all services of a given network slice■ With this information it is possible to deduce how well a bearer is foreseen to be served by the node part of the NR-DC configuration. This enables the node receiving the metric to deduce whether future NR-DC configurations changes are needed. For example, if the predicted packet loss for one or more SCG bearers is not sufficiently low, an SN change action may be planned and executed measured RAN Visible QoE metrics■ This metric can be provided in a number of ways such as:• Per service type (e.g., Multimedia Telephony Service for Internet Protocol (IP) Multimedia Subsystem (IMS) (MTSI), Dynamic Adaptive Streaming over Hypertext Transfer Protocol (HTTP) (DASH) -streaming, Virtual Reality (VR), extended Reality (XR)), the communication service type (Unicast, Multicast, Broadcast)• Per DRB, where it is possible to deduce the RAN visible QoE of different types of bearers in NR-DC such as SN terminated SCG bearers, MN terminated SCG bearers, MN terminated MCG bearers, SN terminated MCG bearers.• Per slice RAN visible QoE, namely the RAN visible QoE for all services of a given network slice■ This metric enables to evaluate the current RAN visible QoE performance for the UE, for each node taking part in the NR-DC configuration. The metric enables to deduce patterns on how such performance varies together with other metrics.■ This metric can also be used as feedback information to judge how well predictions on this metrics were made or how other actions such as NR- DC reconfigurations affected the metric icted RAN Visible QoE metrics■ This metric can be provided in a number of ways such as:• Per service type (e.g., MTSI, DASH-streaming, VR, XR), the communication service type (Unicast, Multicast, Broadcast)• Per DRB, where it is possible to deduce the predicted RAN visible QoE of different types of bearers in NR-DC such as SN terminated SCG bearers, MN terminated SCG bearers, MN terminated MCG bearers, SN terminated MCG bearers.• Per slice predicted RAN visible QoE, namely the RAN visible QoE for all services of a given network slice■ With this information it is possible to deduce how well a bearer is foreseen to be served by the node part of the NR-DC configuration. This enables the node receiving the metric to deduce whether future NR-DC configurations changes are needed. For example, if the predicted RANvisible QoE for one or more SCG bearers is not sufficiently high, an SN change action may be planned and executed o UE trajectory■ measured cells, measured time of stay in cell,■ This metric enables to evaluate the UE trajectory currently followed by the UE. The metric enables to deduce patterns on how the UE is moving and therefor it enables predictions of where the UE will be in the future. The latter enables predictions on future NR-DC configurations, such as predictions on future SCGs to add or remove.■ This metric can also be used as feedback information to judge how well predictions on this metrics were made or how other actions such as NR- DC reconfigurations affected the metric o Predicted cells, predicted time of stay in cell,■ This metric enables to predict the UE trajectory followed by the UE. The metric enables to deduce where the UE will be in the future. The latter enables predictions on future NR-DC configurations, such as predictions on future SCGs to add or remove.■ In one embodiment this metric can comprise a chronological list of predicted MCG cells the UE will be connected to. In another embodiment the metric may comprise a chronological list of SCG cells the UE will connect to.- Measured RAN delay components■ This metric comprises one or more components of the packet delay experienced by packets over one or more data channel for a given UE. Such components can comprise one or more of the following:• DL delay in over-the-air interface• DL delay internal to the gNB-DU for handling packets• DL delay on Fl-U, namely the delay experienced by packets over the Fl-U in DL direction• DL delay in CU-UP, namely the internal delay to the gNB-CU experienced for packet processing• UL PDCP packet average delay, namely the internal delay to the UE in handling packet transmission in UL• UL delay in over-the-air interface• UL delay internal to the gNB-DU for handling packets• UL delay on Fl-U, namely the delay experienced by packets over the Fl-U in DL direction• UL delay in CU-UP, namely the internal delay to the gNB-CU experienced for packet processing■ This metric can be provided in a number of ways such as:• Per DRB, where it is possible to deduce the RAN delay components of different types of bearers in NR-DC such as SN terminated SCG bearers, MN terminated SCG bearers, MN terminated MCG bearers, SN terminated MCG bearers.• Per slice RAN delay components, namely the RAN delay components for all services of a given network slice■ This metric enables to evaluate current delays for traffic handled via an MN or an SN. This information is of vital importance because the overall delay of split bearers configured via NR-DC depends on the maximum delay experienced over the MCG or SCG. Hence by knowing that, e.g. the delay for an MN terminated SCG bearer is exceeding a certain value, it may be decided that such better would better be served by the MN, i.e. the bearer should be reconfigured to be an MN terminated MCG bearer.■ This metric can also be used as feedback information to judge how well predictions on this metrics were made or how other actions such as NR- DC reconfigurations affected the metric- Predicted RAN delay components■ This metric comprises predictions of the components of the packet delay experienced by packets over one or more data channel for a given UE. Such components can comprise one or more of the following:• Predicted DL delay in over-the-air interface• Predicted DL delay internal to the gNB-DU for handling packets• Predicted DL delay on Fl-U, namely the delay experienced by packets over the Fl-U in DL direction• Predicted DL delay in CU-UP, namely the internal delay to the gNB-CU experienced for packet processing• Predicted UL PDCP packet average delay, namely the internal delay to the UE in handling packet transmission in UL• Predicted UL delay in over-the-air interface• Predicted UL delay internal to the gNB-DU for handling packets• Predicted UL delay on Fl-U, namely the delay experienced by packets over the Fl-U in DL direction• Predicted UL delay in CU-UP, namely the internal delay to the gNB-CU experienced for packet processing■ This metric can be provided in a number of ways such as:• Per DRB, where it is possible to predict the RAN delay components of different types of bearers in NR-DC such as SN terminated SCG bearers, MN terminated SCG bearers, MN terminated MCG bearers, SN terminated MCG bearers.• Per slice RAN delay components, namely the predicted RAN delay components for all services of a given network slice

[0071] In order to also facilitate Mobility Robustness Optimization (MRO) predictions for the NR-DC case additional information can be included, such as:- MCG recovery failure cause e.g., T316 expiry or SCG deactivatedSCG failure cause while MCG recovery was ongoing, e.g. random access problems in the SCG,- PSCell ID- time elapsed between MCG failure and the SCG failure (in case of SCG failure)

[0072] As mentioned already in the first aspect description, the UE associated information described in this section may be collected, upon request of a first network node towards a second network node, for one or more UE that is served by the first network node and by the second network node, or by a UE that is served by the second network node but not necessarily served by the first network node. As mentioned already in the first aspect description, the UE associated information described in this section may be collected, upon request of a first network node towards a second network node, for one or more UE that is served by the first network node and by the second network node, or by a UE that is served by the second network node but not necessarily served by the first network node. For example, if the first network node requests information from a node that is a potential SN, such node may not be serving any UE served also by the first network node. In this case the second node reports UEassociated metrics for UEs served by itself, where such UEs may be in locations and coverage conditions similar to those of a UE for which the second node is added as an SN.

[0073] The measurements described in this section may include metrics collected from UEs. In such case, the node(s) receiving a request to collect such measurements shall signal to the corresponding UEs measurements configurations describing the measurement objects the UE shall measure and report to the node that needs to report the requested measurements.Non-UE associated metrics for dual connectivity

[0074] In general, a non-UE associated metric for dual connectivity comprises a measurement and / or a prediction that does not pertain to a certain UE, and is associated with a network entity which is / was involved in dual connectivity operation for at least one UE, or that can potentially be involved in dual connectivity operation for at least one UE.

[0075] In one option, non-UE associated metrics for dual connectivity pertains to an object that is a network node, e.g., a gNB. For example: an Energy Cost, a number of potential cell carrier that can be comprised in an SCG, the Energy Source currently in use at a network node, and cost of changing to a different Energy Source.

[0076] In another option, non-UE associated metrics for dual connectivity pertains to an object or a function that is controlled / served by a network node or controlled / served by a network function. Examples of objects or functions can be: a cell, an SSB beam, a carrier frequency, a RAT. An example of metric can be an average cell throughput, or an Energy Cost associated with a cell.

[0077] In another option, non-UE associated metrics for dual connectivity pertains to a set of UEs sharing common characteristics. Non-limiting examples for a set of UEs can be:- the UEs which, during a certain time interval during which the metrics are collected (or for which the metrics are reported), are configured in dual connectivity with a specific first network node and a second network node, and for which the first network node is one of the Master Node or the Secondary Node- the UEs which, during a certain time interval during which the metrics are collected (or for which the metrics are reported), are configured in dual connectivity with a specific first network node and a second network node, and for which the first network node is the Master Node- the UEs which, during a certain time interval during which the metrics are collected (or for which the metrics are reported), are configured in dual connectivity with a specific first network node and a second network node, and for which the first network node isthe Secondary Node- the UEs which, during a certain time interval during which the metrics are collected (or for which the metrics are reported), are configured in dual connectivity with a specific first network node and a second network node, and for which the first network node is the Master Node (or the Secondary Node) and the second network node is the Secondary Node (or the Master Node) a group of UEs in dual connectivity and configured to report certain RAN Visible QoE (RVQoE) metrics,

[0078] Non-UE associated metrics for dual connectivity can be:- Network node related metrics o preferred or predicted candidate target cells for Conditional PSCell Change■ This information is provided by a node that, given a number of inputs, is able to predict or state its preferences on the best PSCell, served by itself, that should be selected for UEs o preferred or predicted cell for subsequent PSCell Change, where the subsequent change may be bound by a time value o predicted average number of SCells in SCG (and associated available bandwidth over the radio interface) such that a requirement on throughput, latency, bandwidth can be satisfied. The number of SCells that could potentially be aggregated (and even so if combined with the available bandwidth) can be used as a simple indication to indicate potentially reachable levels of performance, such as throughput and latency. o measured or predicted average throughput (in total, or in UL, or in DL)■ This is a metric describing the current overall throughput or the predicted overall throughput. The metric helps understanding how the sending node is performing from the throughput point of view. The information may be used in selecting MNs or SNs that are providing or a foreseen to provide a good performance throughput wise. o Measured average delay per interface■ This information enables the receiving node to determine what are the delays experienced on average over the interfaces terminating at the sending node. As an example, one of such delays could be the Fl-U delay, which should be contained in order to ensure good split bearers performance. A too high measured delay may make the NR-DCconfiguration impractical and not beneficial, hence requiring a NR-DC reconfiguration. o Predicted average delay per interface■ This information enables the receiving node to know what are the predicted delays experienced on average over the interfaces terminating at the sending node. As an example, one of such delays could be the Fill delay, which should be contained in order to ensure good split bearers performance. A too high predicted delay may make future NR-DC configurations impractical and not beneficial, hence requiring a NR-DC reconfiguration.- Resource related metrics at different granularities (per network node, per cell, per-SSB, per network slice, per gNB-DU) o measured or predicted amount of PRBs (in total, or in UL, or in DL) o measured or predicted Transport Network Layer (TNL) Capacity (Offered, Available) o measured or predicted composite available capacity (total, or UL, or DL) o measured or predicted Number of Active UEs o measured or predicted Radio Resource Control (RRC) connections o These metrics enable the receiving node to judge how much capacity and resources neighbour nodes have or will have. This helps taking decisions on e.g. SN or MN selection for current and future NR-DC configurations- Energy related metrics at different granularities (per network node, per gNB, per gNB- CU, per gNB-DU, per gNB-CU-UP, per Energy Consumer Group, per cell, per-SSB, per network slice) o measured or predicted Energy Cost o measured or predicted Energy Saving IndexThese metrics enable the receiving node to judge the energy status of neighbour nodes at present and in the future. This helps taking decisions on e.g. SN or MN selection for current and future NR-DC configurations- Per-group of UE related metrics, e.g.: a number of UEs in dual connectivity for which a network node is the SN, a number of UEs in dual connectivity for which a network node is either the MN or the SNConfiguration parameters for requesting metrics for dual connectivity

[0079] Configuration parameters for requesting metrics for dual connectivity can comprise: Identified s) of the request (e.g., a Data Collection ID)Identified s) of one or more UE for which the request is doneIdentified s) of one or more group of UEs for which the request is doneIdentified s) or objects for which metrics are requested and / or collected o For example: cells / SSB beams, RAN node, a gNB-DU, a gNB-CU-UPConfiguration parameters for collecting and reporting metrics for dual connectivity

[0080] Configuration parameters for collecting and reporting metrics for dual connectivity can comprise:Identifier(s) of the reporting, which can match the identifier(s) of a corresponding request (e.g., a Data Collection ID)Identified s) of one or more UE for which the reporting is doneIdentified s) of one or more group of UEs for which the reporting is done- Reporting periodicity for reporting of UE associated metrics for dual connectivity- Reporting periodicity for reporting of non-UE associated metrics for dual connectivity- Reporting interval (or reporting duration) for reporting of UE associated metrics for dual connectivity- Reporting interval (or reporting duration) for reporting of non-UE associated metrics for dual connectivity- Reporting amount for reporting of UE associated metrics for dual connectivity- Reporting amount for reporting of non-UE associated metrics for dual connectivity Collection interval (or collection duration) for collecting UE associated metrics for dual connectivityCollection interval (or collection duration) for collecting non-UE associated metrics for dual connectivity- Events upon fulfillment of which the collecting UE associated metrics for dual connectivity is terminated or initiated or re-initiated- Events upon fulfillment of which the collecting non-UE associated metrics for dual connectivity is terminated or initiated or re-initiatedIndication to terminate collection and / or reporting of UE associated metrics for dual connectivity upon SN release (MN initiated or SN initiated)Indication to terminate collection and / or reporting of UE associated metrics for dualconnectivity upon SN Change (MN initiated or SN initiated)- weights / priorities for the requested metricsExamples of flow charts

[0081] The following flow charts set out signalling flows in which the embodiments of the disclosure set out above (e.g., with respect to Figures 4 and / or 5) can be implemented. One example flow chart according to embodiments of the present disclosure is shown in Figure 6. A UE is in dual connectivity with an MN and an SN. The MN requests (at step 601) and receives (steps 601 to 604) from the SN a set of UE associated metrics for dual connectivity. In this case, the SN sends the UE associated metrics periodically. When the reported metrics (e.g., a measured or a predicted UE throughput) indicates that a condition is fulfilled, e.g. a significant degradation in the predicted UE throughput at the SN, the MN triggers an SN Change (at step 605).

[0082] Another example of chart is shown in Figure 7. A UE is in single connectivity with a first network node (to become MN). The first network node requests (step 701) and receives (steps 702 to 704) from a candidate second network node a set of UE associated metrics for dual connectivity. The second network node sends the requested metrics to the first network node (in this case periodically). When the metrics (e.g., a predicted UE throughput) indicates a significant value (or a significant improvement compared to the current value), the first network node triggers (step 705) an SN Addition towards the second network node.

[0083] Another example flow chart according to embodiments of the present disclosure is shown in Figure 8. In this case, the first network node has identified two potential candidate SNs and collects UE associated metrics for dual connectivity from them. Two options are shown in the diagram. In option A), messages containing updates (only described, not shown for better visibility) are sent from each one of the candidate secondary network nodes to the first network node (step 801). The first network node, based on this input, determines if / when to add one of the candidates as SN. In option B), the reporting occurs only when one or more conditions (explicitly indicated in the request, or not explicitly indicated in the request) is(are) fulfilled at a certain candidate second network node (in the example the first candidate) (step 802). Based on this, the first network node triggers SN Addition towards the first candidate (step 803).

[0084] Another example flow chart according to embodiments of the present disclosure is shown in Figure 9. The Data Collection Reporting Initiation procedure is extended to request UE associated metrics for dual connectivity (step 901), and embodiments of the presentdisclosure are executed when the UE is already in dual connectivity (the S-NG-RAN node Addition Preparation procedure is shown for this purpose). The reporting is realized extending the existing Data Collection Reporting procedure. The reporting is implicitly stopped when the SN is released (in the example, an MN-initiated SN release) (step 902).

[0085] Another example flow chart according to embodiments of the present disclosure is shown in Figure 10. The Data Collection Reporting Initiation procedure is extended to request / collect UE associated metrics for dual connectivity after an S-NG-RAN node Addition Preparation procedure is executed towards a set of potential candidate SNs (steps 1001 and 1002). That is, the Data Collection Reporting procedure for collecting UE associated metrics for dual connectivity is initiated by the MN after the conditional SN Addition. The reporting is realized by extending the existing Data Collection Reporting procedure, and the reporting from a candidate SN continues until it is released (step 1003). That is, UE associated metrics for dual connectivity are collected until conditional SN Addition is terminated (the candidate SN prepared for Conditional SN Addition is released).

[0086] Another example flow chart according to embodiments of the present disclosure is shown in Figure 11. The first network node initiates a Data Collection Reporting Initiation procedure to handshake with a second network node for the sending of UE associated metrics for dual connectivity (steps 1101 and 1102). The S-Node Preparation procedure is used to activate the reporting, inserting in the S-NODE ADDITION REQUEST a pointer to the request previously agreed (e.g., adding a “Data Collection ID” in the S-NODE ADDITION REQUEST message) (steps 1103 and 1104). The reporting is executed via a Data Collection Reporting procedure.Another example flow chart according to embodiments of the present disclosure is shown in Figure 12. It is in fact a variant of the example shown in Error! Reference source not found.11, wherein the M-NG-RAN node initiated S-NG-RAN node Modification Preparation XnAP procedure is used to activate / trigger the reporting (of UE associated metrics requested for NR-DC) on which the MN and the SN have agreed beforehand (steps 1201 and 1202). That is, the first network node and the second node already agreed on the UE associated metrics to be reported, and how the reporting is to be done. In this case the pointer to the request is comprised in the in the S-NODE MODIFICATION REQUEST message.

[0087] Another example flow chart according to embodiments of the present disclosure is shown in Figure 13. In this case, it is the second network node initiates the request for non-UE associated metrics for dual connectivity of the first network node (step 1301). The first networknode and the second node already agreed on the UE associated metrics to be reported, and how the reporting is to be done. The reporting is triggered by the second network node when it has become the SN (step 1302). That is, an S-NG-RAN node initiated S-NG-RAN node Modification Preparation procedure is used to trigger the reporting of UE associated metrics requested for NR-DC. In the example shown in the figure, a pointer used to trigger the reporting is comprised in a S-NODE MODIFICATION REQUIRED message, but a similar example can be built where the trigger is comprised in an S-NODE ADDITION REQUEST ACKNOWLEDGE message. The SN can use the metrics e.g., to decide when it is time to trigger an SN-Initiated SN release (e.g., the SN determines that the reported Energy Cost is low and wishes to save energy at its side).

[0088] Another example flow chart according to embodiments of the present disclosure is shown in Figure 14, wherein the MN requests to the SN the reporting of UE associated metrics for dual connectivity (and / or non-UE associated metrics for dual connectivity) in a DATA COLLECTION REQUEST message (step 1401), and subsequently receives the information from the SN in an existing signaling message extended to include the UE associated metrics (such as a SECONDARY RAT DATA USAGE REPORT message), or in a newly defined signaling message (e.g., a S-NODE DATA USAGE REPORT message) (step 1402). In other words, a new S-NODE DATA USAGE REPORT message is used to report UE associated metrics requested for NR-DC. The reporting is preceded by a request sent in Data Collection Reporting Initiation procedure.

[0089] A similar flow chart can be built wherein the SN requests the MN the reporting of UE associated metrics for dual connectivity (and / or non-UE associated metrics for dual connectivity) in a DATA COLLECTION REQUEST message, and subsequently receives the information from the MN in a newly defined M-NODE DATA USAGE REPORT message.

[0090] Another example flow chart according to embodiments of the present disclosure is shown in Figure 15 where the SN node sends to the SN node one or more UE associated metrics for dual connectivity (and / or non-UE associated metrics for dual connectivity) in an existing signaling message extended to include the UE associated metrics (such as a SECONDARY RAT DATA USAGE REPORT XnAP message extended for this purpose), or in a newly defined signaling message (e.g., a S-NODE DATA USAGE REPORT message) (step 1501). In other words, a new S-NODE DATA USAGE REPORT message is used to report UE associated metrics requested for NR-DC.

[0091] A similar flow chart can be built wherein the SN sends to the MN the reporting of UE associated metrics for dual connectivity (and / or non-UE associated metrics for dualconnectivity) in a newly defined M-NODE DATA USAGE REPORT message. In this case, there is no preceding request for providing this information, or the request is implicit.Another example comprises the first network node requesting non-UE associated metrics from neighbour network nodes (see, for example, Figure 16 (steps 1601)). Such metrics may include current and predicted interface delay measurements. Figure 16 illustrates use of non-UE associated information to enable the serving network node to deduce the best network node to select as SN. When the first network node, serving the UE, realizes that such metrics identify appropriate conditions for the addition of one of the neighbour network nodes as SN, the first network node triggers an SN addition request procedure towards such network node (steps 1602). Note that the interface delay measurements are an essential piece of information to determine whether dual connectivity split bearers can be effectively established between MN and SN.

[0092] In another example, the UE is configured with NR-DC with a first and third network node (see, for example, Figure 17). Figure 17 illustrates the use of non UE associated information to enable the SN to deduce the best network node to select as SN in an SN triggered SN change. The third network node requests its neighbour network nodes for non UE associated information (1701). Note that the third network node may request other nodes for non UE associated statistics via the first network node (i.e. the MN). In this case the first network node (the MN) would forward the request to the nodes of relevance and it may collect the measurements from such neighbour nodes for then forwarding them to the third network node.

[0093] In this example, the third network node is able to determine whether there are other nodes that are good candidate SN. If that is the case, the third network node (serving as SN) can trigger an SN triggered SN change, namely in the form of an SN change required message towards the MN (step 1702). The MN will then remove the third network node as SN and add the new, e.g. second, network node as new SN.

[0043] Figure 18 shows an example of a communication system 1800 in accordance with some embodiments.

[0044] In the example, the communication system 1800 includes a telecommunication network 1802 that includes an access network 1804, such as a radio access network (RAN), and a core network 1806, which includes one or more core network nodes 1808. The access network 1804 includes one or more access network nodes, such as network nodes 1810a and 1810b (one or more of which may be generally referred to as network nodes 1810), or any othersimilar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 1802 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 1802 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 1802, including one or more network nodes 1810 and / or core network nodes 1808.

[0045] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O- CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 1810 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1812a, 1812b, 1812c, and 1812d (one or more of which may be generally referred to as UEs 1812) to the core network 1806 over one or more wireless connections.

[0046] 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 1800 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 communicationof data and / or signals whether via wired or wireless connections. The communication system 1800 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0047] The UEs 1812 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 1810 and other communication devices. Similarly, the network nodes 1810 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 1812 and / or with other network nodes or equipment in the telecommunication network 1802 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 1802.

[0048] In the depicted example, the core network 1806 connects the network nodes 1810 to one or more host computing systems, such as host 1816. 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 1806 includes one more core network nodes (e.g., core network node 1808) 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 1808. 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).

[0049] The host 1816 may be under the ownership or control of a service provider other than an operator or provider of the access network 1804 and / or the telecommunication network 1802. The host 1816 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0050] As a whole, the communication system 1800 of Figure 18 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may beconfigured 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.

[0051] In some examples, the telecommunication network 1802 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1802 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1802. For example, the telecommunications network 1802 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)ZMassive loT services to yet further UEs.

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

[0053] In the example, the hub 1814 communicates with the access network 1804 to facilitate indirect communication between one or more UEs (e.g., UE 1812c and / or 1812d) and network nodes (e.g., network node 1810b). In some examples, the hub 1814 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1814 may be a broadband router enabling access to the core network 1806 for the UEs. As another example, the hub 1814 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 1810, or by executable code, script, process, or other instructions in the hub 1814. As another example, thehub 1814 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 1814 may be a content source. For example, for a UE that is a VR device, display, loudspeaker, or other media delivery device, the hub 1814 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1814 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 1814 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

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

[0055] Figure 19 shows a UE 1900 in accordance with some embodiments. The UE 1900 presents additional details of some embodiments of the UE 1812 of Figure 1. 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 cameras, gaming console or device, music storage / playback device, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), an Augmented Reality (AR) or Virtual Reality (VR) device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project(3 GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0056] A UE may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), orvehicle- 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).

[0057] The UE 1900 includes processing circuitry 1902 that is operatively coupled via a bus 1904 to an input / output interface 1906, a power source 1908, a memory 1910, a communication interface 1912, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 19. 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.

[0058] The processing circuitry 1902 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 1910. The processing circuitry 1902 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 1902 may include multiple central processing units (CPUs).

[0059] In the example, the input / output interface 1906 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 1900. Examples of an input device include a touch-sensitive or presence-sensitive display, acamera (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.

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

[0061] The memory 1910 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 1910 includes one or more application programs 1914, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1916. The memory 1910 may store, for use by the UE 1900, any of a variety of various operating systems or combinations of operating systems.

[0062] The memory 1910 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), suchas 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 1910 may allow the UE 1900 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 1910, which may be or comprise a device-readable storage medium.

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

[0064] In the illustrated embodiment, communication functions of the communication interface 1912 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.

[0065] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1912, 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 ifit 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).

[0066] 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 to a robotic arm performing a medical procedure according to the received input.

[0067] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 1900 shown in Figure 19.

[0068] As yet another specific example, in an loT 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 3 GPP 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.

[0069] 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.

[0070] Figure 20 a shows a network node 2000 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)), 0-RAN nodes or components of an 0-RAN node (e.g., 0-RU, 0-DU, O-CU).

[0071] 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, distributed units (e.g., in an 0-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0072] 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).

[0073] The network node 2000 includes a processing circuitry 2002, a memory 2004, a communication interface 2006, and a power source 2008. The network node 2000 may becomposed 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 2000 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 2000 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 2004 for different RATs) and some components may be reused (e.g., a same antenna 2010 may be shared by different RATs). The network node 2000 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 2000, 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 2000.

[0074] The processing circuitry 2002 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 2000 components, such as the memory 2004, to provide network node 2000 functionality. For example, the processing circuitry 2002 may be configured to cause the network node to perform the methods as described with reference to Figures 4 and / or 5, and / or the signalling and actions of the first network node or the second network node shown in any of Figures 3 to 14.

[0075] In some embodiments, the processing circuitry 2002 includes a system on a chip (SOC). In some embodiments, the processing circuitry 2002 includes one or more of radio frequency (RF) transceiver circuitry 2012 and baseband processing circuitry 2014. In some embodiments, the radio frequency (RF) transceiver circuitry 2012 and the baseband processing circuitry 2014 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 2012 and baseband processing circuitry 2014 may be on the same chip or set of chips, boards, or units.

[0076] The memory 2004 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory,remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computerexecutable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 2002. The memory 2004 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 2002 and utilized by the network node 2000. The memory 2004 may be used to store any calculations made by the processing circuitry 2002 and / or any data received via the communication interface 2006. In some embodiments, the processing circuitry 2002 and memory 2004 is integrated.

[0077] The communication interface 2006 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 2006 comprises port(s) / terminal(s) 2016 to send and receive data, for example to and from a network over a wired connection. The communication interface 2006 also includes radio front-end circuitry 2018 that may be coupled to, or in certain embodiments a part of, the antenna 2010. Radio front-end circuitry 2018 comprises filters 2020 and amplifiers 2022. The radio front-end circuitry 2018 may be connected to an antenna 2010 and processing circuitry 2002. The radio front-end circuitry may be configured to condition signals communicated between antenna 2010 and processing circuitry 2002. The radio front-end circuitry 2018 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 2018 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 2020 and / or amplifiers 2022. The radio signal may then be transmitted via the antenna 2010. Similarly, when receiving data, the antenna 2010 may collect radio signals which are then converted into digital data by the radio front-end circuitry 2018. The digital data may be passed to the processing circuitry 2002. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0078] In certain alternative embodiments, the network node 2000 does not include separate radio front-end circuitry 2018, instead, the processing circuitry 2002 includes radio front-end circuitry and is connected to the antenna 2010. Similarly, in some embodiments, all or some of the RF transceiver circuitry 2012 is part of the communication interface 2006. In still other embodiments, the communication interface 2006 includes one or more ports orterminals 2016, the radio front-end circuitry 2018, and the RF transceiver circuitry 2012, as part of a radio unit (not shown), and the communication interface 2006 communicates with the baseband processing circuitry 2014, which is part of a digital unit (not shown).

[0079] The antenna 2010 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 2010 may be coupled to the radio frontend circuitry 2018 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 2010 is separate from the network node 2000 and connectable to the network node 2000 through an interface or port.

[0080] The antenna 2010, communication interface 2006, and / or the processing circuitry 2002 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 2010, the communication interface 2006, and / or the processing circuitry 2002 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.

[0081] The power source 2008 provides power to the various components of network node 2000 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 2008 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 2000 with power for performing the functionality described herein. For example, the network node 2000 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 2008. As a further example, the power source 2008 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.

[0082] Embodiments of the network node 2000 may include additional components beyond those shown in Figure 20 a 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 2000 may include user interface equipment to allow input of information into the network node 2000 and to allow output of information from the network node 2000. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the networknode 2000. In some embodiments providing a core network node, such as core network node 108 of FIG. 18, some components, such as the radio front-end circuitry 2018 and the RF transceiver circuitry 2012 may be omitted.

[0083] Figure 21 is a block diagram illustrating a virtualization environment 2100 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 2100 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. In some embodiments, the virtualization environment 2100 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface. Virtualization may facilitate distributed implementations of a network node, UE, core network node, or host.

[0084] Applications 2102 (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.

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

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

[0087] In the context of NFV, a VM 2108 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 2108, and that part of hardware 2104 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 2108 on top of the hardware 2104 and corresponds to the application 2102.

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

[0089] Although the computing devices described herein (e.g., UEs, network nodes) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based onthe 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.

[0090] 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.

[0091] The following groups of numbered statements set out embodiments of the disclosure.Group Bl Embodiments1. A method performed by a first network node, the method comprising: receiving, from one or more second network nodes, first information comprising at least one User Equipment, UE, associated metric for dual connectivity and / or at least one non-UE associated metric for dual connectivity.2. The method of embodiment 1, wherein the first network node is a master node or a serving node configured for a UE and the one or more second network nodes comprise at least one secondary node configured for a UE and / or at least one candidate secondarynode configured for a UE. The method of embodiment 1, wherein the first network node is a secondary node configured for a UE and the one or more second network nodes comprise a master node configured for a UE and / or a candidate secondary network node for the UE. The method of any of embodiments 1-3, wherein the at least one UE-associated metric for dual connectivity is associated with at least one UE served by the first network node and / or the one or more second network nodes. The method of embodiment 4, wherein the at least one UE-associated metric for dual connectivity relates to a single UE served by the first network node and / or the one or more second network nodes. The method of any of embodiments 1-5, wherein the at least one UE-associated metric for dual connectivity comprises any one or more of the following:- one or more metrics of a network node associated with a UE; one or more UE metrics;- one or metrics related to a UE trajectory; and- one or more predicted Radio Access Network, RAN, delay components. The method of any of embodiments 1-6, wherein the at least one non-UE associated metric for dual connectivity comprises a measurement and / or a prediction associated with a plurality of user equipments and / or at least one network entity. The method of embodiment 7, wherein the at least one network entity comprises:- a network entity involved in a dual connectivity operation for at least one UE;- a network entity previously involved in a dual connectivity operation for at least one UE; or a network entity that is a candidate for being involved in a dual connectivity operation for at least one UE.The method of any of embodiments 1-8, wherein the at least one non-UE associated metric for dual connectivity relates to one or more of the following:- a network node;- an entity served and / or controlled by a network node;- an entity served and / or controlled by a network function;- a function served and / or controlled by a network node;- a function served and / or controlled by a network function; and- a set of UEs sharing at least one common characteristic. . The method of any of embodiments 1-9, wherein the at least one non-UE associated metric for dual connectivity comprises one or more of the following:- one or more network node related metrics;- one or more resource related metrics;- one or more energy related metrics;- one or more metrics relating to a group of UEs; and- one or more predicted Radio Access Network, RAN, delay components. . The method of any of embodiments 1-10, wherein the first network node receives the first information from a second network node:- whilst a UE is operating in single connectivity with the first network node and the second node is a candidate for being involved in a dual connectivity operation for the UE;- whilst a UE operating in single connectivity is being reconfigured to operate in dual connectivity with the first network node and the second network node;- whilst a UE is operating in dual connectivity with the first network node and the second network node;- whilst a UE operating in dual connectivity with the first network node and the second network node is being reconfigured to operate in single connectivity;- whilst a dual connectivity operation of a UE operating in dual connectivity with the first network node and the second network node, and a further second network node is a candidate for being involved in a dual connectivity operation for the UE; or- whilst a dual connectivity operation of a UE operating in dual connectivity with the firstnetwork node and the second network node is modified by changing a secondary node and / or a master node of the UE. . The method of any of embodiments 1-11, further comprising sending, to the one or more second network nodes, a first message comprising a request for reporting one or more UE-associated metrics for dual connectivity and / or one or more non-UE associated metrics for dual connectivity. . The method of any of embodiments 12, further comprising sending, to the one or more second network nodes, parameters relating to a UE for which the one or more UE- associated metrics for dual connectivity are requested. . The method of any of embodiments 12-13, further comprising sending, to the one or more second network nodes, one or more target values for the one or more UE-associated metrics for dual connectivity and / or the one or more non-UE associated metrics for dual connectivity. . The method of embodiment 14, wherein the one or more target values are communicated as one or more time-varying parameters. . The method of any of embodiments 12-15, wherein the first message further comprises:- weights and / or priorities for the one or more UE-associated metrics for dual connectivity; and / or- weights and / or priorities for the one or more non-UE associated metrics for dual connectivity. . The method of any of embodiments 12-16, wherein the first message configures the one or more second network nodes to report the first information responsive to:- the at least one UE-associated metric and / or the at least one non-UE associated metric reaching a specific value; or- the at least one UE-associated metric and / or the at least one non-UE associated metric being within a value range.The method of any of embodiments 12-17, further comprising indicating to the one or more second network nodes that the one or more second network nodes are to pause or terminate the reporting of the one or more UE-associated metrics for dual connectivity and / or the one or more non-UE associated metrics for dual connectivity. The method of any of embodiments 12-18, further comprising indicating to the one or more second network nodes that the one or more second network nodes are to continue the reporting of the one or more UE-associated metrics for dual connectivity and / or the one or more non-UE associated metrics for dual connectivity. The method of any of embodiments 12-19, further comprising indicating to the one or more second network nodes, that the one or more second network nodes are to initiate and / or resume the reporting of the one or more UE-associated metrics for dual connectivity and / or the one or more non-UE associated metrics for dual connectivity. The method of any of embodiments 12-20, wherein the first message further comprises one or more configuration parameters, wherein the one or more configuration parameters are for: configuring the second network node for the reporting of the first information; and / or configuring the second network node for collecting the at least one UE-associated metric and / or the at least one non-UE associated metric. The method of any of embodiments 1-21, further comprising determining, based at least in part on the first information, one or more actions relating to dual connectivity and / or handover for a UE. The method of embodiment 22, wherein the one or more actions comprise at least one of the following: an initiation of a secondary node addition for a UE; an initiation of a secondary node change for a UE; an initiation of a secondary node modification for a UE; an initiation of a secondary node release for a UE; an initiation of a handover procedure for a UE; anda type of bearer to be configured for a UE. . The method of any of embodiments 1-23, further comprising sending the first information to a third network node deploying a machine learning model or function. . The method of any of embodiments 1-24, wherein a machine learning model or function is deployed at the first network node, and the method further comprises using the first information as at least one of: an input for training, validating, testing, and / or retraining the machine learning model or function; an input for triggering a retraining of the machine learning model or function; and an input and / or feedback for the machine learning model or function. . The method of embodiment 25 when dependent upon embodiment 22 or 23, wherein the machine learning model or function is used to determine the one or more actions. . The method of any of embodiments 25-26, wherein the machine learning model or function is used to derive predictions of the one or more UE-associated metrics and / or the one or more non-UE associated metrics. . The method of any of embodiments 1-27, wherein the first information further comprises one or more of the following:- a master cell group, MCG, recovery failure cause;- a secondary cell group, SCG, failure cause;- a primary secondary cell, PSCell, identifier; and- a time elapsed between an MCG failure and an SCG failure. . The method of any of embodiments 1-28, wherein the at least one UE-associated metric is for New Radio, NR, dual connectivity, NR-DC, and the at least one non-UE associated metric is for NR-DC. . The method of any of embodiments 1-29, wherein the at least one UE-associated metric is additionally for single connectivity and / or the at least one non-UE associated metric isadditionally for single connectivity.B2 Embodiments . A method performed by a second network node, the method comprising: sending, to a first network node, first information comprising at least one User Equipment, UE, associated metric for dual connectivity and / or at least one non-UE associated metric for dual connectivity. . The method of embodiment 31, wherein the first network node is a master node or a serving node configured for a UE and the second network node is a secondary node configured for a UE or a candidate secondary node configured for a UE. . The method of embodiment 31, wherein the first network node is a secondary node configured for a UE and the second network node is a master node configured for a UE and / or a candidate secondary network node for the UE. . The method of any of embodiments 31-33, wherein the at least one UE-associated metric for dual connectivity is associated with at least one UE served by the first network node and / or the second network node. . The method of embodiment 34, wherein the at least one UE-associated metric for dual connectivity relates to a single UE served by the first network node and / or the second network node. . The method of any of embodiments 31-35, wherein the at least one UE-associated metric for dual connectivity comprises any one or more of the following:- one or more metrics of a network node associated with a UE; one or more UE metrics;- one or metrics related to a UE trajectory; and- one or more predicted RAN delay components.37. The method of any of embodiments 31-36, wherein the at least one non-UE associated metric for dual connectivity comprises a measurement and / or a prediction associated with a plurality of user equipments and / or at least one network entity.38. The method of embodiment 37, wherein the at least one network entity comprises a network entity:- involved in a dual connectivity operation for at least one UE;- previously involved in a dual connectivity operation for at least one UE; or- that is a candidate for being involved in a dual connectivity operation for at least one UE.39. The method of any of embodiments 31-38, wherein the at least one non-UE associated metric for dual connectivity relates to one or more of the following:- a network node;- an entity served and / or controlled by a network node;- an entity served and / or controlled by a network function;- a function served and / or controlled by a network node;- a function served and / or controlled by a network function; and- a set of UEs sharing at least one common characteristic.40. The method of any of embodiments 31-39, wherein the at least one non-UE associated metric for dual connectivity comprises one or more of the following:- one or more network node related metrics;- one or more resource related metrics;- one or more energy related metrics;- one or more metrics relating to a group of UEs; and- one or more predicted Radio Access Network, RAN, delay components.41. The method of any of embodiments 31-40, wherein the second network node sends the first information to the first network node:- whilst a UE is operating in single connectivity with the first network node and the second node is a candidate for being involved in a dual connectivity operation for the UE;- whilst a UE operating in single connectivity is being reconfigured to operate in dualconnectivity with the first network node and the second network node;- whilst a UE is operating in dual connectivity with the first network node and the second network node;- whilst a UE operating in dual connectivity with the first network node and the second network node is being reconfigured to operate in single connectivity;- whilst a dual connectivity operation of a UE operating in dual connectivity with the first network node and the second network node, and a further second network node is a candidate for being involved in a dual connectivity operation for the UE; or- whilst a dual connectivity operation of a UE operating in dual connectivity with the first network node and the second network node is modified by changing a secondary node and / or a master node of the UE.42. The method of any of embodiments 31-41, further comprising receiving, from the first network node, a first message comprising a request for reporting one or more UE- associated metrics for dual connectivity and / or one or more non-UE associated metrics for dual connectivity.43. The method of embodiment 42, further comprising receiving, from the first network node, parameters relating to a UE for which the one or more UE-associated metrics for dual connectivity are requested.44. The method of any of embodiments 42-43, further comprising receiving, from the first network node, one or more target values for the one or more UE-associated metrics for dual connectivity and / or the one or more non-UE associated metrics for dual connectivity.45. The method of embodiment 44, wherein the one or more target values are communicated as one or more time-varying parameters.46. The method of any of embodiments 42-45, wherein the first message further comprises:- weights and / or priorities for the one or more UE-associated metrics for dual connectivity; and / or- weights and / or priorities for the one or more non-UE associated metrics for dualconnectivity. . The method of any of embodiments 42-46, wherein the first message configures the second network node to report the first information responsive to:- the at least one UE-associated metric and / or the at least one non-UE associated metric reaching a specific value; or- the at least one UE-associated metric and / or the at least one non-UE associated metric being within a value range. . The method of any of embodiments 42-47, further comprising receiving, from the first network node, an indication that the second network node is to pause or terminate the reporting of the one or more UE-associated metrics for dual connectivity and / or the one or more non-UE associated metrics for dual connectivity. . The method of any of embodiments 42-48, further comprising receiving, from the first network node, an indication that the second network node is to continue reporting of the one or more UE-associated metrics for dual connectivity and / or the one or more non-UE associated metrics for dual connectivity. . The method of any of embodiments 42-49, further comprising receiving, from the first network node, an indication that the second network node is to initiate and / or resume the reporting of the one or more UE-associated metrics for dual connectivity and / or the one or more non-UE associated metrics for dual connectivity. . The method of any of embodiments 31-50, wherein the first message further comprises one or more configuration parameters, wherein the one or more configuration parameters are for: configuring the second network node for the reporting of the first information; and / or configuring the second network node for collecting the at least one UE-associated metric and / or the at least one non-UE associated metric. . The method of any of embodiments 31-51, wherein the first information further comprises one or more of the following:- a master cell group, MCG, recovery failure cause;- a secondary cell group, SCG, failure cause;- a primary secondary cell, PSCell, identifier; and- a time elapsed between an MCG failure and an SCG failure.53. The method of any of embodiments 31-52, wherein the at least one UE-associated metric is for New Radio, NR, dual connectivity, NR-DC, and the at least one non-UE associated metric is for NR-DC.54. The method of any of embodiments 30-53, wherein the at least one UE-associated metric is additionally for single connectivity and / or the at least one non-UE associated metric is additionally for single connectivity.Group C Embodiments55. A first network node, the first network node comprising: processing circuitry configured to cause the first network node to perform any of the steps of any of the Group Bl embodiments; power supply circuitry configured to supply power to the processing circuitry.56. A second network node, the second network node comprising: processing circuitry configured to cause the second network node to perform any of the steps of any of the Group B2 embodiments; power supply circuitry configured to supply power to the processing circuitry.

Claims

CLAIMS1. A method performed by a first network node, wherein the first network node is a master node or a serving node configured for a user equipment, UE, the method comprising: receiving (404, 602, 702, 703), from one or more second network nodes, first information comprising at least one UE-associated metric for dual connectivity and / or at least one non-UE associated metric for dual connectivity, wherein the one or more second network nodes comprise at least one secondary node configured for the UE and / or at least one candidate secondary node for the UE,- wherein the at least one UE-associated metric for dual connectivity relates to a single UE served by the first network node, and- wherein the at least one non-UE associated metric for dual connectivity is not specific to a single UE, and comprises a measurement and / or a prediction associated with a plurality of user equipments and / or at least one network entity.

2. The method of claim 1, wherein the at least one UE-associated metric for dual connectivity comprises any one or more of the following:- one or more metrics of a network node associated with the single UE; one or more UE metrics;- one or metrics related to a UE trajectory; and- one or more predicted Radio Access Network, RAN, delay components.

3. The method of any of claims 1-2, wherein the at least one UE-associated metric for dual connectivity comprises one or more of the following:- a master cell group, MCG, recovery failure cause;- a secondary cell group, SCG, failure cause;- a primary secondary cell, PSCell, identifier; and- a time elapsed between an MCG failure and an SCG failure.

4. The method of any of claims 1-3, wherein a machine learning model or function is deployed at the first network node, and the method further comprises using the first information as at least one of:an input for training, validating, testing, and / or retraining the machine learning model or function; an input for triggering a retraining of the machine learning model or function; and an input and / or feedback for the machine learning model or function.

5. The method of claim 4, wherein the machine learning model or function is used to derive predictions of the one or more UE-associated metrics and / or the one or more non-UE associated metrics.

6. The method of claims 1-5, wherein the at least one network entity comprises:- a network entity involved in a dual connectivity operation for at least one UE;- a network entity previously involved in a dual connectivity operation for at least one UE; or- a network entity that is a candidate for being involved in a dual connectivity operation for at least one UE.

7. The method of any of claims 1-6, wherein the first network node receives the first information from a second network node:- whilst a UE is operating in single connectivity with the first network node and the second node is a candidate for being involved in a dual connectivity operation for the UE;- whilst a UE operating in single connectivity is being reconfigured to operate in dual connectivity with the first network node and the second network node;- whilst a UE is operating in dual connectivity with the first network node and the second network node;- whilst a UE operating in dual connectivity with the first network node and the second network node is being reconfigured to operate in single connectivity;- whilst a UE is operating in dual connectivity with the first network node and the second network node, and a further second network node is a candidate for being involved in a dual connectivity operation for the UE; or- whilst a UE is operating in dual connectivity with the first network node and the second network node is modified by changing a secondary node and / or a master node of the UE.

8. The method of any of claims 1-7, further comprising sending (402, 601, 701), to the one or more second network nodes, a first message comprising a request for reporting one ormore UE-associated metrics for dual connectivity and / or one or more non-UE associated metrics for dual connectivity.

9. The method of claim 8, further comprising sending, to the one or more second network nodes, parameters relating to a UE for which the one or more UE-associated metrics for dual connectivity are requested.

10. The method of any of claims 8-9, wherein the first message configures the one or more second network nodes to report the first information responsive to:- the at least one UE-associated metric and / or the at least one non-UE associated metric reaching a specific value; or- the at least one UE-associated metric and / or the at least one non-UE associated metric being within a value range.

11. The method of any of claims 8-10, wherein the first message further comprises one or more configuration parameters, wherein the one or more configuration parameters are for: configuring the second network node for the reporting of the first information; and / or configuring the second network node for collecting the at least one UE-associated metric and / or the at least one non-UE associated metric.

12. The method of any of claims 1-11, further comprising determining (406), based at least in part on the first information, one or more actions relating to dual connectivity and / or handover for a UE.

13. The method of claim 12, wherein the one or more actions comprise at least one of the following: an initiation of a secondary node addition for a UE; an initiation of a secondary node change for a UE; an initiation of a secondary node modification for a UE; an initiation of a secondary node release for a UE; an initiation of a handover procedure for a UE; and a type of bearer to be configured for a UE.

14. A method performed by a second network node, wherein the second network node comprises a secondary node configured for a user equipment, UE, and / or a candidate secondary node for the UE, the method comprising: sending (504, 602, 702, 703) to a first network node, first information comprising at least one User Equipment, UE, associated metric for dual connectivity and / or at least one non-UE associated metric for dual connectivity, wherein the first network node is a master node or a serving node configured for the UE,- wherein the at least one UE-associated metric for dual connectivity relates to a single UE served by the first network node, and- wherein the at least one non-UE associated metric for dual connectivity is not specific to a single UE, and comprises a measurement and / or a prediction associated with a plurality of user equipments and / or at least one network entity.

15. The method of claim 14, wherein the at least one UE-associated metric for dual connectivity comprises any one or more of the following:- one or more metrics of a network node associated with a UE; one or more UE metrics;- one or metrics related to a UE trajectory; and- one or more predicted RAN delay components.

16. The method of any of claims 14-15, wherein the at least one UE-associated metric for dual connectivity comprises one or more of the following:- a master cell group, MCG, recovery failure cause;- a secondary cell group, SCG, failure cause;- a primary secondary cell, PSCell, identifier; and- a time elapsed between an MCG failure and an SCG failure.

17. The method of any of claims 14-16, wherein the at least one network entity comprises a network entity:- involved in a dual connectivity operation for at least one UE;- previously involved in a dual connectivity operation for at least one UE; or- that is a candidate for being involved in a dual connectivity operation for at least one UE.

18. The method of any of claims 14-17, wherein the second network node sends the first information to the first network node:- whilst a UE is operating in single connectivity with the first network node and the second node is a candidate for being involved in a dual connectivity operation for the UE;- whilst a UE operating in single connectivity is being reconfigured to operate in dual connectivity with the first network node and the second network node;- whilst a UE is operating in dual connectivity with the first network node and the second network node;- whilst a UE operating in dual connectivity with the first network node and the second network node is being reconfigured to operate in single connectivity;- whilst a UE is operating in dual connectivity with the first network node and the second network node, and a further second network node is a candidate for being involved in a dual connectivity operation for the UE; or- whilst a UE is operating in dual connectivity with the first network node and the second network node is modified by changing a secondary node and / or a master node of the UE.

19. The method of any of claims 14-18, further comprising receiving (502, 601, 701), from the first network node, a first message comprising a request for reporting one or more UE-associated metrics for dual connectivity and / or one or more non-UE associated metrics for dual connectivity.

20. The method of claim 19, further comprising receiving, from the first network node, parameters relating to a UE for which the one or more UE-associated metrics for dual connectivity are requested.

21. The method of any of claims 19-20, wherein the first message configures the second network node to report the first information responsive to:- the at least one UE-associated metric and / or the at least one non-UE associated metric reaching a specific value; or- the at least one UE-associated metric and / or the at least one non-UE associated metric being within a value range.

22. The method of any of claims 19-21, wherein the first message further comprises one or more configuration parameters, wherein the one or more configuration parameters arefor: configuring the second network node for the reporting of the first information; and / or configuring the second network node for collecting the at least one UE-associated metric and / or the at least one non-UE associated metric.

23. A first network node (2000), the first network node comprising: processing circuitry (2002) configured to cause the first network node to: receive, from one or more second network nodes, first information comprising at least one user equipment, UE, associated metric for dual connectivity and / or at least one non- UE associated metric for dual connectivity, wherein the first network node is a master node or a serving node configured for a UE, and wherein the one or more second network nodes comprise at least one secondary node configured for the UE and / or at least one candidate secondary node for the UE,- wherein the at least one UE-associated metric for dual connectivity relates to a single UE served by the first network node, and- wherein the at least one non-UE associated metric for dual connectivity is not specific to a single UE, and comprises a measurement and / or a prediction associated with a plurality of user equipments and / or at least one network entity.

24. The first network node of claim 23, wherein the processing circuitry (2002) is further configured to cause the first network node to perform the method of any one of claims 2 to 13.

25. A first network node adapted (2000) to perform the method according to any one of claims 1 to 13.

26. A computer program product comprising code which, when executed by processing circuitry of a first network node, causes the first network node to perform the method of any one of claims 1 to 13.

27. A second network node (2000), the second network node comprising: processing circuitry (2002) configured to cause the second network node to: send, to a first network node, first information comprising at least one User Equipment, UE, associated metric for dual connectivity and / or at least one non-UE associated metric for dual connectivity, wherein the first network node is a master node or aserving node configured for a UE, and wherein the second network node comprises a secondary node configured for the UE, and / or a candidate secondary node for the UE,- wherein the at least one UE-associated metric for dual connectivity relates to a single UE served by the first network node, and - wherein the at least one non-UE associated metric for dual connectivity is not specific to a single UE, and comprises a measurement and / or a prediction associated with a plurality of user equipments and / or at least one network entity.

28. The second network node of claim 27, wherein the processing circuitry is further configured to cause the second network node to perform the method of any one of claims 15 to22.

29. A second network node adapted to perform the method according to any one of claims 14 to 22.

30. A computer program product comprising code which, when executed by processing circuitry of a second network node, causes the second network node to perform the method of any one of claims 14 to 22.

Images