Reports relating to successful DC mobility operations

Abstract

According to an aspect, there is provided a user equipment (UE) that is using dual connectivity (DC). The UE has a first Successful Primary Secondary Cell Group Cell Change / Addition Report (SPR) configuration associated with a first network node in a communication network, and a second reporting SPR configuration associated with a second network node in the communication network. A SPR configuration indicates respective criteria for triggering a SPR for a successful Primary Secondary Cell Group Cell (PSCell) change or addition relating to the first network node and / or the second network node. The method comprises: determining (501) that the first network node triggered or initiated a PSCell change or addition relating to the first network node and / or the second network node and evaluating the criteria for the first SPR configuration; if the criteria for the first SPR configuration is met: obtaining (503) information for the SPR for a successful PSCell change or addition; and generating (505) a SPR relating to the successful PSCell change or addition comprising the information.

Description

[0001] REPORTS RELATING TO SUCCESSFUL DC MOBILITY OPERATIONS

[0002] Technical Field

[0003] This disclosure relates to the generation, storing or logging of reports relating to a successful dual connectivity (DC) mobility operation.

[0004] Background

[0005] Overall Architecture of NG-RAN

[0006] The current 5thGeneration (5G) Radio Access Network (RAN) (NG-RAN) architecture is depicted and described in the 3rdGeneration Partnership Project (3GPP) Technical Standard (TS) 38.401 V17.2.0 as shown in Fig. 1.

[0007] The NG-RAN consists of a set of gNBs connected to the 5G Core (5GC) through the Next Generation (NG) interface.

[0008] As specified in 3GPP TS 38.300 v17.4.0, NG-RAN could also consist of a set of ng-eNBs, where an ng-eNB may consist of an ng-eNB-Central Unit (CU, eNB-CU) and one or more ng- eNB-Distributed Unit(s) (DU(s), eNB-DU(s)). An ng-eNB-CU and an ng-eNB-DU is connected via W1 interface. The general principle described in this clause also applies to ng-eNB and W1 interface, if not explicitly specified otherwise.

[0009] • An gNB can support Frequency Division Duplex (FDD) mode, Time Division Duplex (TDD) mode or dual mode operation.

[0010] • gNBs can be interconnected through the Xn interface.

[0011] • A gNB may consist of a gNB-CU and one or more gNB-DU(s). A gNB-CU and a gNB-DU is connected via F1 interface.

[0012] • One gNB-DU is connected to only one gNB-CU.

[0013] • NG, Xn and F1 are logical interfaces.

[0014] For NG-RAN, the NG and Xn-C interfaces for a gNB consist of a gNB-CU and gNB-DUs, terminate in the gNB-CU. For E-UTRAN (Evolved-UTRA (UMTS Terrestrial Radio Access) Network) New Radio - Dual Connectivity (EN-DC), the S1-U and X2-C interfaces for a gNB consist of a gNB-CU and gNB-DUs terminating in the gNB-CU. The gNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GC as a gNB.

[0015] The node hosting the user plane (UP) part of New Radio (NR) Packet Data Convergence Protocol (PDCP) (e.g. gNB-CU, gNB-CU-UP, and for EN-DC, Master eNB (MeNB) or Secondary gNB (SgNB) depending on the bearer split) shall perform user inactivity monitoring and further informs its inactivity or (re)activation to the node having control plane (CP) connection towards the core network (e.g. over E1 , X2). The node hosting NR Radio Link Control (RLC) (e.g. gNB- DU) may perform user inactivity monitoring and further inform its inactivity or (re)activation to the node hosting control plane, e.g. gNB-CU or gNB-CU-CP.

[0016] Uplink (UL) PDCP configuration (i.e. how the UE uses the UL at the assisting node) is indicated via X2-C (for EN-DC), Xn-C (for NG-RAN) and F1-C. Radio Link Outage / Resume for Downlink (DL) and / or UL is indicated via X2-U (for EN-DC), Xn-U (for NG-RAN) and F1-U.

[0017] The NG-RAN is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL).

[0018] The NG-RAN architecture, i.e. the NG-RAN logical nodes and interfaces between them, is defined as part of the RNL. For each NG-RAN interface (NG, Xn, F1) the related TNL protocol and the functionality are specified. The TNL provides services for user plane transport, signalling transport.

[0019] The architecture shown above is that defined by 3GPP for 5G. Other standardisation groups, such as Open RAN (ORAN), 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 RLC and Medium Access Control (MAC). In ORAN the upper node is called ORAN Distributed Unit (O-DU), while the lower node is called ORAN-Radio Unit (O-RU).

[0020] At current state-of-art, the coordination across RAN and Transport domains is typically managed in a non-real-time mode (e.g. pre-planning and provisioning the Transport domain) with the alternative to coordinate Radio and Transport domains at Service Orchestration level, even though no products are yet available on the market.

[0021] Self-Organising Networks (SON) in 3GPP

[0022] A Self-Organising Network (SON) is an automation technology designed to make the planning, configuration, management, optimisation and healing of mobile radio access networks simpler and faster. SON functionality and behaviour has been defined and specified in generally accepted mobile industry recommendations produced by organisations such as 3GPP and the NGMN (Next Generation Mobile Networks).

[0023] In 3GPP, the processes within the SON area are classified into a Self-configuration process and a Self-optimisation process. The Self-configuration process is the process where newly deployed nodes are configured by automatic installation procedures to get the necessary basic configuration for system operation.

[0024] This process works in a pre-operational state. A pre-operational state is understood as the state from when the eNB is powered up and has backbone connectivity until the RF transmitter is switched on.

[0025] Fig. 2 illustrates some of the ramifications of Self-Configuration / Self-Optimisation functionality. Fig. 2 corresponds to Figure 22.1-1 in 3GPP TS 36.300 v17.4.0. As illustrated in Fig. 2, functions handled in the pre-operational state like:

[0026] • Basic Setup; and

[0027] • Initial Radio Configuration. are covered by the Self Configuration process.

[0028] The self-optimisation process is defined as the process where the User Equipment (UE) and access node measurements and performance measurements are used to auto-tune the network.

[0029] This process works in the operational state. The operational state is understood as the state where the RF interface is additionally switched on.

[0030] As described in Fig. 2Error! Reference source not found., functions handled in the operational state like Optimisation / Adaptation are covered by the Self Optimisation process.

[0031] In Long Term Evolution (LTE), support for Self-Configuration and Self-Optimisation is specified, as described in 3GPP TS 36.300 v17.4.0 section 22.2, including features such as Dynamic configuration, Automatic Neighbour Relation (ANR), Mobility load balancing, Mobility Robustness Optimisation (MRO), Random Access Channel (RACH) optimisation and support for energy saving.

[0032] In NR, support for Self-Configuration and Self-Optimisation is specified as well, starting with Self-Configuration features such as Dynamic configuration, Automatic Neighbour Relation (ANR) in Release 15 (Rel-15), as described in 3GPP TS 38.300 V15.14.0 section 15. In NR Release 16 (Rel-16), more SON features are being specified, including Self-Optimisation features such as Mobility Robustness Optimisation (MRO).

[0033] Mobility Robustness Optimisation (MRO) in 3GPP

[0034] Seamless handovers are a key feature of 3GPP technologies. Successful handovers ensure that the UE moves around in the coverage area of different cells without causing too many interruptions in the data transmission. However, there will be scenarios when the network fails to handover the UE to the ‘correct’ neighbour cell in time, and in such scenarios the UE will declare a radio link failure (RLF) or Handover Failure (HOF).

[0035] Upon HOF and / or RLF, the UE may take autonomous actions, i.e. trying to select a cell and initiate re-establishment procedure to make sure the UE is trying to get back as soon as it can, so that it can be reachable by the network again. The RLF will cause a poor user experience as the RLF is declared by the UE only when it realises that there is no reliable communication channel (radio link) available between itself and the network. Also, re-establishing the connection requires signalling with the newly selected cell (random access procedure, Radio Resource Control (RRC) Reestablishment Request, RRC Reestablishment RRC Reestablishment Complete, RRC Reconfiguration and RRC Reconfiguration Complete) and adds some latency, until the UE can exchange data with the network again.

[0036] According to the specifications (3GPP TS 36.331 v17.4.0), the possible causes forthe radio link failure could be one of the following:

[0037] 1) Expiry of the radio link monitoring related timer T310;

[0038] 2) Expiry of the measurement reporting associated timer T312 (not receiving the handover command from the network within this timer’s duration despite sending the measurement report when T310 was running);

[0039] 3) Upon reaching the maximum number of RLC retransmissions;

[0040] 4) Upon receiving random access problem indication from the MAC entity.

[0041] As RLF leads to re-establishment which degrades performance and user experience, it is in the interest of the network to understand the reasons for RLF and try to optimise mobility related parameters (e.g. trigger conditions of measurement reports) to avoid later RLFs. Before the standardisation of MRO-related report handling in the network, only the UE was aware of some information associated with the radio quality at the time of RLF, the actual reason for declaring RLF etc. Forthe network to identify the reason for the RLF, the network needs more information, both from the UE and also from the neighbouring base stations.

[0042] As part of the MRO solution in LTE, the RLF reporting procedure was introduced in the RRC specification in Release 9 (Rel-9) RAN2 work. That has impacted the RRC specifications (3GPP TS 36.331 v17.4.0) in the sense that it was standardised that the UE would log relevant information at the moment of an RLF and later report to a target cell the UE succeeds to connect (e.g. after reestablishment). That has also impacted the inter-gNodeB interface, i.e., X2 Application Protocol (X2AP) specifications (3GPP TS 36.423 v17.4.0), as an eNodeB receiving an RLF report could forward to the eNodeB where the failure originated.

[0043] For the RLF report generated by the UE, its contents have been enhanced with more details in subsequent releases. The measurements included in the measurement report based on the latest LTE RRC specification 3GPP TS 36.331 v17.4.0 are:

[0044] 1) Measurement quantities (Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ)) of the last serving cell (Primary Cell (PCell)).

[0045] 2) Measurement quantities of the neighbour cells in different frequencies of different Radio Access Technologies (RATs) (EUTRA, UTRA, Global System for Mobile (GSM) Enhanced Data rates for GSM Evolution (EDGE) RAN (GERAN), CDMA2000). 3) Measurement quantity (Received Signal Strength Indicator (RSSI)) associated to Wireless Local Area Network (WLAN) Access Points (APs).

[0046] 4) Measurement quantity (RSSI) associated to Bluetooth beacons.

[0047] 5) Location information, if available (including location coordinates and velocity).

[0048] 6) Globally unique identity of the last serving cell, if available, otherwise the Physical Cell Identity (PCI) and the carrier frequency of the last serving cell.

[0049] 7) Tracking area code of the PCell.

[0050] 8) Time elapsed since the last reception of the ‘Handover command’ message.

[0051] 9) Cell-Radio Network Temporary Identifier (C-RNTI) used in the previous serving cell.

[0052] 10) Whether or not the UE was configured with a Data Radio Bearer (DRB) having Quality of Service (QoS) Class Identifier (QCI) value of 1.

[0053] After the RLF is declared, the RLF report is logged and include in the VarRLF-Report and, once the UE selects a cell and succeeds with a reestablishment, it includes an indication that it has an RLF report available in the RRC Reestablishment Complete message, to make the target cell aware of that availability. Then, upon receiving a UElnformationRequest message with a flag “rlf-ReportReq-r9”, the UE shall include the RLF report (stored in a UE variable VarRLF-Report, as described above) in an UElnformationResponse message and send it to the network.

[0054] Based on the RLF report from the UE and the knowledge about which cell the UE reestablished itself with, the original source cell can deduce whether the RLF was caused due to a coverage hole or due to handover-associated parameter configurations. If the RLF was deemed to be due to handover-associated parameter configurations, the original serving cell can further classify the handover-related failure as too early, too late or handover to wrong cell classes. These handover failure classes are explained in brief below.

[0055] 1) Whether the handover failure occurred due to the ‘too late handover / mobility’ cases: a. The original serving cell can classify a handover failure to be ‘too late handover / mobility’ when the original serving cell fails to send the handover command to the UE associated to a handover towards a particular target cell and if the UE re-establishes itself in this target cell post RLF. b. An example corrective action from the original serving cell could be to initiate the handover procedure towards this target cell a bit earlier by decreasing the Cell Individual Offset (CIO) towards the target cell that controls when the UE sends the event triggered measurement report that leads to taking the handover decision.

[0056] 2) Whether the handover failure occurred due to the ‘too early handover / mobility’ cases: a. The original serving cell can classify a handover failure to be ‘too early handover / mobility’ when the original serving cell is successful in sending the handover command to the UE associated to a handover, however the UE fails to perform the random access towards this target cell or the UE declares RLF in the target cell soon afterwards. b. An example corrective action from the original serving cell could be to initiate the handover procedure towards this target cell a bit later by increasing the CIO towards the target cell that controls when the UE sends the event triggered measurement report that leads to taking the handover decision.

[0057] 3) Whether the handover failure occurred due to the ‘handover / mobility-to-wrong-cell’ cases: a. The original serving cell can classify a handover failure to be ‘handover / mobility- to-wrong-cell’ when the original serving cell intends to perform the handover for this UE towards a particular target cell but the UE declares failure or declares failure shortly after successfully completing the handover and then re-establishes itself in a third cell. b. A corrective action from the original serving cell could be to initiate the measurement reporting procedure that leads to handover towards the target cell a bit later by decreasing the CIO towards the target cell or via initiating the handover towards the cell in which the UE re-established a bit earlier by increasing the CIO towards the re-establishment cell.

[0058] Successful Handover report

[0059] The current state of the art concerning the successful handover procedure and collection of the user plane interruption time from RRC 3GPP TS 38.331 version 17.3.0 is shown in the following:

[0060] *********************************************************

[0061] 5.7.10 UE Information

[0062] 5.7.10.1 General

[0063] [Fig. 3 shows the UE information procedure found in Figure 5.7.10.1-1 of this section of 3GPP TS 38.331 version 17.3.0]

[0064] The UE information procedure is used by the network to request the UE to report information.

[0065] 6.2.2 Message definitions

[0066] - UElnformationResponse

[0067] The UElnformationResponse message is used by the UE to transfer information requested by the network. Signalling radio bearer: SRB 1 or SRB2 (when logged measurement information is included)

[0068] RLC-SAP: AM

[0069] Logical channel: DCCH

[0070] Direction: UE to network

[0071] UElnformationResponse message

[0072] 5.7.10.6 Actions for the successful handover report determination

[0073] The UE shall for the PCell:

[0074] 1> if the ratio between the value of the elapsed time of the timer T304 and the configured value of the timer T304, included in the last applied RRCReconflguration message including the reconflgurationWithSync, is greater than thresholdPercentageT304 if included in the successHO-Conflg received before executing the last reconfiguration with sync; or

[0075] 1> if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync, is greater than thresholdPercentageTS 10 included in the successHO-Conflg if configured by the source PCell before executing the last reconfiguration with sync; or

[0076] 1> if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the reconfiguration with sync procedure and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync, is greater than thresholdPercentageTS 12 included in the successHO-Conflg if configured by the source PCell before executing the last reconfiguration with sync; or

[0077] 1> if sourceDAPS-FailureReporting is included in the successHO-Conflg before executing the last reconfiguration with sync and is set to true and if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running:

[0078] 2> store the successful handover information in VarSuccessHO-Report and determine the content in VarSuccessHO-Report as follows:

[0079] 3> clear the information included in VarSuccessHO-Report, if any;

[0080] 3> set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e., includes the RPLMN);

[0081] 3> set the c-RNTI to the C-RNTI assigned by the target PCell of the handover;

[0082] 3> for the source PCell in which the last RRCReconflguration message including reconflgurationWithSync was applied:

[0083] 4> set the sourceCelUD in sourceCelllnfo to the global cell identity and tracking area code, if available, of the source PCell;

[0084] 4> set the sourceCellMeas in sourceCelllnfo to include the cell level RSRP, RSRQ and the available SINR, of the source PCell based on the available SSB and CSI-RS measurements collected up to the moment the UE sends RRCReconfigurationComplete message;

[0085] 4> set the rsIndexRe suits in sourceCellMeas to include all the available SSB and CSI-RS measurement quantities of the source PCell collected up to the moment the UE sends RRCReconfigurationComplete message;

[0086] 4> if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running:

[0087] 5> set the rlf-InSourceDAPS in sourceCelllnfo to true',

[0088] 3> for the target PCell indicated in the last applied RRCReconflguration message including reconfiguration WithSync: 4> set the targetCelllD in targetCelllnfo to the global cell identity and tracking area code, if available, of the target PCell;

[0089] 4> set the targetCellMeas in targetCelllnfo to include the cell level RSRP, RSRQ and the available SINR, of the target PCell based on the available SSB and CSI-RS measurements collected up to the moment the UE sends RRCReconfigurationComplete message;

[0090] 4> set the rsIndexRe suits in targetCellMeas to include all the available SSB and CSI-RS measurement quantities of the target PCell collected up to the moment the UE sends RRCReconfigurationComplete message;

[0091] 4> if the last applied RRCReconflguration message including reconflgurationWithSync was included in the stored condRRCReconflg'.

[0092] 5> set the timeSinceCHO-Reconflg to the time elapsed between the initiation of the execution of conditional reconfiguration for the target PCell and the reception of the last conditionalReconflguration including the condRRCReconflg of the target PCell in the source PCell;

[0093] 3> if the ratio between the value of the elapsed time of the timer T304 and the configured value of the T304 timer, included in the last applied RRCReconflguration message including the reconflgurationWithSync, is greater than thresholdPercentageT304 if included in the successHO- Config received before executing the last reconfiguration with sync:

[0094] 4> set t304-cause in shr-Cause to true',

[0095] 4> set the ra-InformationCommon to include the random-access related information associated to the random access procedure in the target PCell, as specified in clause 5.7.10.5;

[0096] 3> if the ratio between the value of the elapsed time of the timer T310 and the configured value of the T310 timer, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync, is greater than threshold? ercentageTS 10 included in the successHO-Conflg if configured by the source PCell before executing the last reconfiguration with sync:

[0097] 4> set t310-cause in shr-Cause to true',

[0098] 3> if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the reconfiguration with sync procedure and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the T312 timer, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312 included in the success! I()-Config if configured by the source PCell before executing the last reconfiguration with sync:

[0099] 4> set t312-cause in shr-Cause to true',

[0100] 3> if sourceDAPS-FailureReporting included in the successHO-Conflg if configured by the source PCell before executing the last reconfiguration with sync is set to true, and if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was miming:

[0101] 4> set sourceDAPS-Failure in shr-Cause to true',

[0102] 3> for each of the measObjectNR, configured by the source PCell, in which the last RRCReconflguration message including reconflgurationWithSync was applied:

[0103] 4> if measurements are available for the measObjectNR'.

[0104] 5> if the SS / PBCH block-based measurement quantities are available:

[0105] 6> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell or target PCell, ordered such that the cell with highest SS / PBCH block RSRP is listed first if SS / PBCH block RSRP measurement results are available, otherwise the cell with highest SS / PBCH block RSRQ is listed first if SS / PBCH block RSRQ measurement results are available, otherwise the cell with highest SS / PBCH block SINR is listed first, based on the available SS / PBCH block based measurements collected up to the moment the UE sends the RRCReconflgurationComplete message;

[0106] 6> for each neighbour cell included, include the optional fields that are available;

[0107] NOTE 1 : For the neighboring cells set included in measResultListNR in measResultNeighCells ordered based on the SS / PBCH block measurement quantities, the UE includes also the CSI-RS based measurement quantities, if available.

[0108] 5> if the CSI-RS measurement quantities are available:

[0109] 6> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell and target PCell, ordered such that the cell with highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the cell with highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the cell with highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE sends the RRCReconflgurationComplete message;

[0110] 6> for each neighbour cell included, include the optional fields that are available;

[0111] NOTE 2: For the neighboring cells set ordered based on the CSI-RS measurement quantities, the UE includes measurements only for the cells not yet included in measResultListNR in measResultNeighCells to avoid overriding SS / PBCH block-based ordered measurements.

[0112] 3> for each of the measObjectEUTRA, configured by the source PCell in which the last RRCReconflguration message including reconfligurationWithSync was applied:

[0113] 4> if measurements are available for the measObjectEUTRA'.

[0114] 5> set the measResultListEUTRA in measResultNeighCells to include the best measured cells ordered such that the cell with highest RSRP is listed first if RSRP measurement results are available, otherwise the cell with highest RSRQ is listed first, based on measurements collected up to the moment the UE sends the RRCReconflgurationComplete message;

[0115] 5> for each neighbour cell included, include the optional fields that are available;

[0116] 3> for each of the neighbour cells included in measResultNeighCells'.

[0117] 4> if the cell was a candidate target cell included in the condRRCReconflg within the conditionalReconflguration configured by the source PCell, in which the last RRCReconflguration message including reconfligurationWithSync was applied:

[0118] 5> set the choCandidate to true in measResultNR',

[0119] 3> if available, set the locationinfo as in 5.3.3.7;

[0120] 1> release successHO-Config configured by the source PCell and threshold? ercentageTS 04 if configured by the target PCell.

[0121] The UE may discard the successful handover information, i.e. , release the UE variable VarSuccessHO-Report, 48 hours after the last successful handover information is added to the VarSuccessHO-Report. Successful Primary Secondary Cell Group (SCG) Cell (PSCell) chanqe / addition report

[0122] A Successful Primary Secondary Cell Group Cell (PSCell) Change / Addition report (SPR) is a Rel-18 feature that enables logging information and measurements concerning a successful PSCell change / addition based on some triggering conditions configured by the network node. The overall procedure follows the same principal of the successful handover (HO) report but potentially three nodes can be involved in the procedure. Therefore, potentially three nodes can configure and request for the SPR i.e., source Secondary Node (SN), Master Node (MN) and target SN, wherein source SN and MN can configure T310 and T312 thresholds and target SN can configure the T304 threshold.

[0123] The SPR may contain any of the following information:

[0124] • radio measurement results of the source PSCell and / or target PSCell at the moment of the PSCell addition / change;

[0125] • radio measurement results of the PCell;

[0126] • location information;

[0127] • conditional PSCell change / addition configuration;

[0128] • cause of the SPR generation, which could be: o exceeding the T304 threshold as configured by the PCell, and / or source PSCell and / or target PSCell; o exceeding the T310 threshold as configured by the PCell, and / or source PSCell and / or target PSCell; o exceeding the T312 threshold as configured by the PCell, and / or source PSCell and / or target PSCell;

[0129] • time elapsed since the execution of the PSCell change / addition and the PSCell change / addition completion;

[0130] • time elapsed between the initiation of the last conditional reconfiguration execution towards the target PSCell and the reception of the latest conditional reconfiguration for this target PSCell.

[0131] Summary

[0132] There currently exist certain challenge(s). SON / MDT has been enhanced in Rel-18 to include UE report and measurements for the successful dual connectivity (DC) operations, with this report being called a Successful PSCell change / addition Report (SPR)).

[0133] Triggering and / or logging of the SPR by the UE is agreed by 3GPP to be based on SPR configurations that should be configured by the RAN node before / upon sending a PSCell change / addition command to the UE. SPR triggering thresholds are adopted from SHR triggering configurations and currently include the following triggering thresholds:

[0134] • T310 triggering threshold;

[0135] • T312 triggering threshold;

[0136] • T304 triggering threshold.

[0137] The T310 and T312 triggering thresholds can be configured / sent to the UE by the source SN or MN, and the T304 triggering threshold can be configured by the target SN. This means that at the time of PSCell change / addition, there might be two instances of SPR configurations (in particular two instances of T310 / T312 thresholds). However, in the current SHR and SPR solution there is no mechanism to handle two instances of the SPR configurations when monitoring the SPR triggering conditions. This problem is schematically shown in Fig. 4.

[0138] Thus, the UE can be configured with multiple SPR configurations provided by the source SN, the MN (T310 / T312 thresholds) and the target SN (T310 threshold). When the UE performs a PSCell change (or addition) successfully, it is not clear which SPR configuration (e.g. which T310 / T312 thresholds configured by the (source) SN or the MN the UE) should be monitored for generating the SPR.

[0139] It should be noted that at the time of PSCell change and monitoring the SPR triggering conditions, there is only one T304 triggering threshold, which is not problematic. However there can be two instances of the T310 and T312 triggering thresholds, which is problematic, as there is no clear solution on how the UE generates SPR when both configurations exist at the UE.

[0140] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Particular embodiments relate to SPR generation, storage or logging when a plurality of SPR configurations have been received from various RAN nodes. In some embodiments of this disclosure, the wireless terminal, e.g. UE, determines whether to generate / log / store the SPR based on triggering / fulfilling one or more configured thresholds / conditions according to the node that initiated the PSCell change. In other embodiments, the UE determines to generate / log / store the SPR based on triggering / fulfilling configured thresholds / conditions provided by the Master Node (MN). In other embodiments, the UE determines to generate / log / store the SPR based on triggering / fulfilling configured thresholds / conditions provided by a target Secondary Node (SN).

[0141] Where the UE has one or more SPR configurations for which the SPR can be generated, and in the event that the UE determines whether to generate / log / store the SPR based on all available SPR configurations, e.g. regardless of which node initiated the SPR, embodiments provide for the UE to log an indication in the SPR that indicates which node’s SPR configuration was used to generate the SPR.

[0142] In a first specific method of this disclosure relating to PSCell change, the UE can conditionally check / monitor different instances of the SPR triggering configurations configured by the source SN or the MN.

[0143] • If the PSCell change was initiated by the source SN: o The UE can determine whether to create / log / store the SPR based on the SPR configuration (T310 / T312 triggering thresholds) provided by the source SN.

[0144] • If the PSCell change was initiated by the MN: o The UE can determine whether to create / log / store the SPR based on the SPR configuration (T310 / T312 triggering thresholds) provided by the MN.

[0145] • In response to creating / logging / storing the SPR based on one of the MN or SN-provided SPR configurations, the UE can include an indication in the SPR indicating which SPR configuration, i.e. from the MN or SN, led to the creation / logging / storage of the SPR upon PSCell change, or equivalently the UE can include an indication indicating which network node, i.e. MN or SN, initiated the PSCell change.

[0146] In a second (alternative) method of this disclosure relating to PSCell change, the UE can determine whether to generate / log / store the SPR based on all the existing SPR configurations, regardless of which node initiated the PSCell change. This method can comprise:

[0147] • In response to creating / logging / storing the SPR, regardless of which node initiated the PSCell change, the UE can log any of the following information in the SPR report: o Indication associated to which node initiated the executed PSCell change procedure, e.g. MN or SN. o Indication associated to the one or more configurations that triggered the SPR generation (e.g. the SPR configuration provided by the MN and / or by the SN).

[0148] In a third method of this disclosure relating to PSCell addition, the UE can determine whether to generate / log / store the SPR based on the existing SPR configuration provided by the MN.

[0149] In a fourth method of this disclosure relating to PSCell change to a target PSCell, or addition of a target PSCell, the UE can determine whether to generate the SPR based on the SPR configuration of a target RAN node for the target PSCell, irrespective of which node initiated the SPR.

[0150] According to a first aspect, there is provided a method performed by a user equipment (UE) that is using dual connectivity (DC). The UE has a first Successful Primary Secondary Cell Group Cell Change / Addition Report (SPR) configuration associated with a first network node in a communication network, and a second SPR configuration associated with a second network node in the communication network. A SPR configuration indicates respective criteria for triggering a SPR for a successful Primary Secondary Cell Group Cell (PSCell) change or addition relating to the first network node and / or the second network node. The method comprises: determining that the first network node triggered or initiated a PSCell change or addition relating to the first network node and / or the second network node and evaluating the criteria for the first SPR configuration; if the criteria for the first SPR configuration is met: obtaining information for the SPR for a successful PSCell change or addition; and generating a SPR relating to the successful PSCell change or addition comprising the information.

[0151] According to a second aspect, there is provided a method performed by a first network node. The method comprises receiving, from a user equipment (UE) a Successful Primary Secondary Cell Group Cell Change / Addition Report (SPR) relating to a successful Primary Secondary Cell Group Cell (PSCell) change or addition by the UE with respect to the first network node and / or a second network node. The SPR was generated according to a first SPR configuration associated with a network node. The method also comprises determining, from the received SPR, which network node provided the first SPR configuration to the UE.

[0152] According to a third aspect, there is provided a computer program product comprising a computer readable medium having computer readable code embodied therein, the computer readable code being configured such that, on execution by a suitable computer or processor, the computer or processor is caused to perform the method according to the first aspect, the second aspect, or any embodiment thereof.

[0153] According to a fourth aspect, there is provided a UE configured to perform the method according to the first aspect or any embodiment thereof.

[0154] According to a fifth aspect, there is provided a UE comprising a processor and a memory, said memory containing instructions executable by said processor whereby said UE is operative to perform the method according to the first aspect or any embodiment thereof.

[0155] According to a sixth aspect, there is provided a network node configured to perform the method according to the second aspect or any embodiment thereof.

[0156] According to a seventh aspect, there is provided a network node comprising a processor and a memory, said memory containing instructions executable by said processor whereby said network node is operative to perform the method according to the second aspect or any embodiment thereof.

[0157] Certain embodiments may provide one or more of the following technical advantage(s). In particular, the first method enables the UE to decide whether to create / log / store a SPR upon execution of a PSCell change according to certain conditions based on which the PSCell change was executed. In a non-limiting example one certain condition that the UE can check is the node that initiated the PSCell change. Thus, if the PSCell change was an MN-initiated PSCell change, the SPR configuration generated by the MN (associated to the Master Cell Group (MCG)) should be considered to create / log / store the SPR. If the PSCell change was a SN-initiated PSCell change, the SPR configuration generated by the SN should be considered to create / log / store the SPR. Such a solution enables the UE to report which SPR configuration is used to generate the SPR. In addition, embodiments of the solution enable the UE to indicate to the network which SPR configuration led to creating / logging / storing the SPR at the UE.

[0158] The second method of this disclosure enables the UE to create / log / store the SPR based on all the available configurations. This method not only provides more information to the network (i.e. more SPR will be generated), but it also indicates which SPR configuration led to creating / logging / storing the SPR.

[0159] Brief Description of the Drawings

[0160] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings, in which:

[0161] Fig. 1 is a block diagram of a NG-RAN architecture;

[0162] Fig. 2 illustrates ramifications of Self-Configuration / Self-Optimisation functionality;

[0163] Fig. 3 shows a UE information procedure;

[0164] Fig. 4 illustrates a problem with handling two instances of SPR configurations when monitoring SPR triggering conditions;

[0165] Fig. 5 is a flow chart illustrating a method performed by a user equipment in accordance with some embodiments;

[0166] Fig. 6 is a flow chart illustrating a method performed by a first network node in accordance with some embodiments;

[0167] Fig. 7 is a flow chart illustrating a method performed by a user equipment in accordance with some alternative embodiments;

[0168] Fig. 8 is a flow chart illustrating a method performed by a first network node in accordance with some alternative embodiments;

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

[0170] Fig. 10 shows a UE in accordance with some embodiments;

[0171] Fig. 11 shows a RAN network node in accordance with some embodiments; and

[0172] Fig. 12 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized. Detailed Description

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

[0174] As noted above, in some embodiments of this disclosure, the UE determines whether to generate / log / store the SPR based on triggering / fulfilling one or more configured thresholds / conditions according to the node that initiated the PSCell change. In other embodiments, the UE determines to generate / log / store the SPR based on triggering / fulfilling configured thresholds / conditions provided by the Master Node (MN). In other embodiments, the UE determines to generate / log / store the SPR based on triggering / fulfilling configured thresholds / conditions provided by a target Secondary Node (SN).

[0175] Where the UE has one or more SPR configurations for which the SPR can be generated, and in the event that the UE determines whether to generate / log / store the SPR based on all available SPR configurations, e.g. regardless of which node initiated the SPR, embodiments provide for the UE to log an indication in the SPR that indicates which node’s SPR configuration was used to generate the SPR.

[0176] In the first specific method of this disclosure relating to PSCell change, the UE can conditionally check / monitor different instances of the SPR triggering configurations configured by the source SN or the MN.

[0177] If the PSCell change was initiated by the source SN, the UE can determine whether to create / log / store the SPR based on the SPR configuration (T310 / T312 triggering thresholds) provided by the source SN. However, if the PSCell change was initiated by the MN, the UE can determine whether to create / log / store the SPR based on the SPR configuration (T310 / T312 triggering thresholds) provided by the MN.

[0178] In response to creating / logging / storing the SPR based on one of the MN or SN-provided SPR configurations, the UE can include an indication in the SPR indicating which SPR configuration, i.e. from the MN or SN, led to the creation / logging / storage of the SPR upon PSCell change, or equivalently the UE can include an indication indicating which network node, i.e. MN or SN, initiated the PSCell change.

[0179] In some embodiments the indication indicating the SPR configuration that led to creating / logging / storing the SPR, or the indication indicating which node initiated the PSCell change, can be represented by a field indicating ‘MN’ or ‘SN’. Alternatively the indication can be represented by a field indicating ‘PCell’ (in case the relevant SPR configuration is the one provided by the MN, or the PSCell change was initiated by the MN) or ‘PSCell’ (in case the relevant SPR configuration is the one provided by the SN, or the PSCell change was initiated by the SN). As another alternative, the indication can be represented by a field indicating the PCell identity (ID) / Cell Global Identity (CGI) (in case the concerned SPR configuration is the one provided by the MN or the PSCell change was initiated by the MN) or PSCell ID / CGI (in case the concerned SPR configuration is the one provided by the SN or the PSCell was initiated by the SN).

[0180] The above indication may be logged in the SPR by the UE only if the SPR was logged due to the SN configuring the SPR (or equivalently the SN initiating the PSCell change). The absence of such an indication can refer to SPR being configured by the MN (or equivalently the MN initiating the PSCell change).

[0181] Alternatively, the above indication may be logged by the UE only if the SPR was logged due to the MN configuring the SPR (or equivalently the MN initiating the PSCell change). The absence of such an indication can referto SPR being configured by the SN (or equivalently the SN initiating the PSCell change).

[0182] In some embodiments, the indication in the SPR can comprise one or more of the specific triggering conditions for the logging of the SPR configured by the MN or by the SN that are fulfilled for the concerned PSCell change. For example, if the T310 triggering condition as provided by the MN is fulfilled, the UE can log the indication “T310Threshold-MCG” (or similar); if the T312 triggering condition as provided by the MN is fulfilled, the UE logs the indication “T312Threshold- MCG” (or similar); if the T310 triggering condition as provided by the SN is fulfilled, the UE logs the indication “T310Threshold-SCG” (or similar); if the T312 triggering condition as provided by the SN is fulfilled, the UE logs the indication “T312Threshold-SCG” (or similar).

[0183] The above indication of the specific triggering conditions may be logged in the SPR by the UE only if the SPR was logged due to the SN configuring the SPR (or equivalently the SN initiating the PSCell change). The absence of such an indication can refer to SPR being configured by the MN (or equivalently the MN initiating the PSCell change).

[0184] Alternatively, the above indication of the specific triggering conditions may be logged by the UE only if the SPR was logged due to the MN configuring the SPR (or equivalently the MN initiating the PSCell change). The absence of such an indication can refer to SPR being configured by the SN (or equivalently the SN initiating the PSCell change).

[0185] In the second specific method of this disclosure relating to PSCell change, the UE can determine whether to generate / log / store the SPR based on all the existing SPR configurations, regardless of which node initiated the PSCell change.

[0186] In this method, in response to creating / logging / storing the SPR, regardless of which node initiated the PSCell change, the UE can log, in the SPR report, an indication associated to which node initiated the executed PSCell change procedure, e.g. MN or SN.

[0187] In some embodiments the indication indicating which node executed the PSCell change procedure is represented by a field indicating ‘MN’ or ‘SN’. Alternatively the indication can be represented by a field indicating ‘PCell’ (in case the concerned PSCell change was initiated by the MN) or ‘PSCell’ (in case the concerned PSCell change was initiated by the SN). As another alternative, the indication can be represented by a field indicating the PCell ID / CGI (in case the concerned PSCell change was initiated by the MN) or PSCell ID / CGI (in case the concerned PSCell change was initiated by the SN).

[0188] The above indication may be logged by the UE only if the PSCell change was initiated by the SN. The absence of such indication can refer to PSCell change initiated by the MN.

[0189] Alternatively, the above indication may be logged by the UE only if the PSCell change was initiated by the MN. The absence of such indication can refer to PSCell change initiated by the SN.

[0190] In addition or alternatively to the indication associated to which node initiated the executed PSCell change procedure, the UE can log, in the SPR report, an indication associated to the one or more configurations that triggered the SPR generation (e.g. the SPR configuration provided by the MN and / or by the SN).

[0191] In some embodiments the indication indicating the SPR configuration(s) that led to creating / logging / storing the SPR is represented by a field indicating ‘MN’ and / or ‘SN’; or ‘PCell’ (in case the concerned SPR configuration is the one provided by the MN) and / or ‘PSCell’ (in case the concerned SPR configuration is the one provided by the SN); and / or the PCell ID / CGI (in case the concerned SPR configuration is the one provided by the MN) and / or PSCell ID / CGI (in case the concerned SPR configuration is the one provided by the SN).

[0192] The above indication may be logged by the UE only if the SPR was logged due to SN configuring the SPR. The absence of such indication can refer to the SPR being configured by the MN.

[0193] Alternatively, the indication may be logged by the UE only if the SPR was logged due to MN configuring the SPR. The absence of such indication can refer to the SPR being configured by the SN.

[0194] In some embodiments, the indication in the SPR can comprise one or more of the specific triggering conditions for the logging of the SPR configured by the MN and / or by the SN that are fulfilled for the concerned PSCell change. For example, if the T310 triggering condition as provided by the MN is fulfilled, the UE can log the indication “T31 OThreshold-MCG” (or similar); if the T312 triggering condition as provided by the MN is fulfilled, the UE logs the indication “T312Threshold-MCG” (or similar); if the T310 triggering condition as provided by the SN is fulfilled, the UE logs the indication “T310Threshold-SCG” (or similar); if the T312 triggering condition as provided by the SN is fulfilled, the UE logs the indication “T312Threshold-SCG” (or similar).

[0195] The above indication of the specific triggering conditions may be logged in the SPR by the UE only if the SPR was logged due to the SN configuring the SPR. The absence of such an indication can refer to SPR being configured by the MN.

[0196] Alternatively, the above indication of the specific triggering conditions may be logged by the UE only if the SPR was logged due to the MN configuring the SPR. The absence of such an indication can refer to SPR being configured by the SN.

[0197] In some embodiments of the second method, if the UE is configured with both SPR configurations provided by the MN and SN, upon successful PSCell change completion the UE can perform any of the following:

[0198] • The UE can first check if any of the conditions for the logging of the SPR included in the MN-provided SPR configuration are fulfilled, and then log them in the SPR. The UE can then check if any of the conditions for the logging of the SPR included in the SN-provided SPR configuration are fulfilled, and then logs them in the SPR.

[0199] • The UE can first check if any of the conditions for the logging of the SPR included in the SN-provided SPR configuration are fulfilled, and then log them in the SPR. The UE can then check if any of the conditions for the logging of the SPR included in the MN-provided SPR configuration are fulfilled, and then logs them in the SPR.

[0200] • If the PSCell change is MN-initiated, the UE can first check if any of the conditions for the logging of the SPR included in the MN-provided SPR configuration are fulfilled, and then log them in the SPR. The UE can then check if any of the conditions for the logging of the SPR included in the SN-provided SPR configuration are fulfilled, and then logs them in the SPR.

[0201] • If the PSCell change is SN-initiated, the UE can first check if any of the conditions for the logging of the SPR included in the SN-provided SPR configuration are fulfilled, and then log them in the SPR. The UE can then check if any of the conditions for the logging of the SPR included in the MN-provided SPR configuration are fulfilled, and then log them in the SPR.

[0202] • The UE can check if any of the conditions for the logging of the SPR included in the MN- and in the SN-provided SPR configurations are fulfilled, and then log them in the SPR in chronological order, i.e. in the order of conditions that were fulfilled first. For example, if the triggering T310 triggering condition as provided by the SN is fulfilled first, and the triggering T312 triggering condition as provided by the MN is fulfilled second, the UE first logs the indication of “T310Threshold-SCG” in the SPR, followed by “T312Threshold- MCG”.

[0203] • The UE can check which of the conditions for the logging of the SPR are fulfilled first. If a condition provided by the MN is fulfilled first, the UE may only log in the SPR indication associated to the MN-provided SPR configuration. If a condition provided by the SN is fulfilled first, the UE may only log in the SPR indication associated to the SN-provided SPR configuration.

[0204] In the third specific method of this disclosure relating to PSCell addition, the UE can determine whether to generate / log / store the SPR based on the existing SPR configuration provided by the MN. The UE may log an indication in the SPR that the SPR was for the PSCell addition. This indication may be provided implicitly, e.g. by not including in the SPR the information associated to the source PSCell. The UE may also or alternatively log an indication in the SPR that comprises or indicates one or more of the specific triggering conditions for the logging of the SPR configured by the MN. For example, if the T310 triggering condition as provided by the MN is fulfilled, the UE can log the indication “T31 OThreshold-MCG” (or similar); if the T312 triggering condition as provided by the MN is fulfilled, the UE can log the indication “T312Threshold-MCG” (or similar).

[0205] In the fourth specific method of this disclosure relating to PSCell change to a target PSCell, or addition of a target PSCell, the UE can determine whether to generate the SPR based on the SPR configuration of a target RAN node for the target PSCell, irrespective of which node initiated the SPR.

[0206] In the SPR the UE may log an indication indicating which network node, i.e. the MN or SN, initiated the PSCell change. This indication can be as described above with respect to the other specific methods of this disclosure.

[0207] In the SPR the UE may also or alternatively log an indication indicating whether the concerned PSCell change / addition was a PSCell change or a PSCell addition. This indication can be as described above with respect to the other specific methods of this disclosure.

[0208] In the SPR the UE may also or alternatively log an indication indicating which of the specific triggering conditions for the logging of the SPR, as provided by the target RAN node for the target PSCell, are fulfilled. This indication can be as described above with respect to the other specific methods of this disclosure.

[0209] Fig. 5 is a flow chart illustrating a method performed by a UE in accordance with some embodiments. The UE may perform the method in response to executing suitably formulated computer readable code. The computer readable code may be embodied or stored on a computer readable medium, such as a memory chip, optical disc, or other storage medium. The computer readable medium may be part of a computer program product. The UE may be the UE 912 or UE 1000 as described later with reference to Figs. 9 and 10 respectively.

[0210] The UE is using dual connectivity (DC) and has a first Successful Primary Secondary Cell Group Cell Change / Addition Report (SPR) configuration associated with a first network node in a communication network, and a second SPR configuration associated with a second network node in the communication network. A SPR configuration indicates respective criteria for triggering a SPR for a successful Primary Secondary Cell Group Cell (PSCell) change or addition relating to the first network node and / or the second network node. The communication network may be a Self-Organising Network (SON), and the SPR can be a SON report.

[0211] In step 501 , the UE determines that the first network node triggered or initiated a PSCell change or addition relating to the first network node and / or the second network node, and evaluates the criteria for the first SPR configuration.

[0212] If the criteria for the first SPR configuration is met, then in step 503 the UE obtains information for the SPR for a successful PSCell change or addition, and in step 503 the UE generates a SPR relating to the successful PSCell change or addition comprising the information.

[0213] In some embodiments, the UE can send the generated SPR to any one or more of the first network node, the second node and a third network node in the communication network.

[0214] The criteria for each SPR configuration may comprise timer values. The timer values may comprise T310 and / or T312 thresholds.

[0215] The first network node can be one of a Master Node (MN), a source Secondary Node (SN) providing the PSCell before the PSCell Change operation, and a target SN providing the PSCell after the PSCell Addition or Change operation.

[0216] The second network node can be one of: a Master Node (MN), a source Secondary Node (SN) providing the PSCell before the PSCell Change operation; and a target SN providing the PSCell after the PSCell Addition or Change operation.

[0217] In other embodiments, the first network node can be one of a Master Node (MN) for the UE or a Secondary Node (SN) providing a source PSCell for the UE. In these embodiments, the second network node can be the other one of the MN and Secondary Node (SN) providing the source PSCell.

[0218] The generated SPR may comprise an indication that the SPR was generated according to the first SPR configuration.

[0219] The generated SPR may comprise an indication that the first network node triggered or initiated the PSCell change or addition. The generated SPR may comprise an indication of the criteria for the first SPR configuration that were fulfilled in order to generate the SPR.

[0220] Fig. 6 is a flow chart illustrating a method performed by a first network node in accordance with some embodiments. The first network node may perform the method in response to executing suitably formulated computer readable code. The computer readable code may be embodied or stored on a computer readable medium, such as a memory chip, optical disc, or other storage medium. The computer readable medium may be part of a computer program product. The first network node may be the network node 910 or network node 1100 as described later with reference to Figs. 9 and 11 respectively.

[0221] In step 601 , the network node receives a SPR relating to a successful PSCell change or addition by a UE with respect to the first network node and / or a second network node. The SPR is received from the UE. The SPR was generated according to a first SPR configuration associated with a network node, i.e. the first network node, or a different network node.

[0222] In step 603, the network node determines which network node provided the first reporting configuration to the UE from the received report.

[0223] The method performed by the network node may also include the network node determining which network node initiated the successful PSCell change or addition from the received SPR. In this respect, the received SPR may comprise an indication that the first network node triggered or initiated the PSCell change or addition.

[0224] In some embodiments, the received SPR may comprise an indication that the SPR was generated according to the first reporting configuration.

[0225] The first network node may be a MN for the UE that the SPR was received from, or a SN that is providing a source PSCell for the UE.

[0226] Fig. 7 is a flow chart illustrating a method performed by a UE in accordance with some embodiments. The UE may perform the method in response to executing suitably formulated computer readable code. The computer readable code may be embodied or stored on a computer readable medium, such as a memory chip, optical disc, or other storage medium. The computer readable medium may be part of a computer program product. The UE may be the UE 912 or UE 1000 as described later with reference to Figs. 9 and 10 respectively.

[0227] The UE is using dual connectivity (DC) and has a first reporting configuration associated with a first network node in a communication network and a second reporting configuration associated with a second network node in the communication network. A reporting configuration indicates information to be provided in a report for a successful DC mobility operation relating to the first network node and / or the second network node. The communication network may be a Self-Organising Network (SON), and the report can be a SON report. The report can be a Successful PSCell Report, SPR.

[0228] The information to be provided in the report relating to the DC mobility operation can comprise any one or more of location information; radio measurement results; and a CHO configuration.

[0229] The mobility operation may be a PSCell Addition or Change operation. In this case, the first network node is one of a MN, a source SN (that was providing the PSCell before the PSCell Addition or Change operation) and a target SN (that is providing the PSCell after the PSCell Addition or Change operation). The second network node can be one of a MN, a source SN, and a target SN.

[0230] In step 701 , the UE obtains information according to the first reporting configuration for a successful DC mobility operation.

[0231] In step 703, the UE generates a report relating to the successful DC mobility operation. The report comprises the information obtained according to the first reporting configuration.

[0232] In some embodiments, the UE can send the generated report to any one or more of the first network node, the second node and a third network node in the communication network.

[0233] The UE may have a first set of criteria relating to the first reporting configuration. The UE may also have a second set of criteria relating to the second reporting configuration. The (set(s) of) criteria can comprise timer values. Steps 701 and / or 703 can be performed if the criteria are met.

[0234] In certain embodiments of step 701 , the UE may obtain information according to only the first reporting configuration. That is, the UE may not obtain information according to the second reporting configuration. In certain embodiments of step 703, the UE may generate the report comprising information obtained only according to the first reporting configuration. That is, the generated report may not contain information obtained according to the second reporting configuration.

[0235] In the above certain embodiments of steps 701 and / or 703, the first network node may be the network node that triggered or initiated the DC mobility operation. In these embodiments, the first network node is a MN for the UE or a SN that is providing a source PSCell for the UE. The second network node may be the other one of the MN and SN that is providing the source PSCell. The UE may perform a further step in which the UE determines that the first network node is the network node that triggered or initiated the DC mobility operation.

[0236] Alternatively, in the above certain embodiments, the first network node can be a MN for the UE. The second network node can be a SN that is providing a source PSCell for the UE. That is, in these embodiments, the first reporting configuration (i.e. the only reporting configuration used to obtain information and / or include information in the report) is provided by the MN. In another alternative, in the above certain embodiments, the first network node is a SN that is providing a target PSCell for the UE. The second network node is one of a MN for the UE and a SN providing a source PSCell for the UE. That is, in these embodiments, the first reporting configuration (i.e. the only reporting configuration used to obtain information and / or include information in the report) is provided by the SN providing the target PSCell.

[0237] In alternative embodiments of step 701 , information according to both the first reporting configuration and the second reporting configuration can be obtained, and the report generated in step 503 can comprise information obtained according to both reporting configurations. In these embodiments, the first reporting configuration may comprise one or more first criteria, the second reporting configuration may comprise one or more second criteria, and the one or more first criteria and one or more second criteria are fulfilled. The information obtained according to the first reporting configuration and information obtained according to the second reporting configuration may be ordered in the generated report according to an order in which the one or more first criteria and one or more second criteria are fulfilled.

[0238] In any of the above embodiments of Fig. 7, the report generated by the UE in step 703 can comprise an indication that the report was generated according to the first reporting configuration.

[0239] In any of the above embodiments of Fig. 7, the report generated by the UE in step 703 can comprise an indication of which network node triggered or initiated the DC mobility operation. Where the first network node triggered or initiated the DC mobility operation, the generated report can comprise an indication that the first network node triggered or initiated the DC mobility operation.

[0240] In any of the above embodiments of Fig. 7, the report generated by the UE in step 703 can comprise an indication of one or more criteria for the first reporting configuration that were fulfilled in order to generate the report.

[0241] Fig. 8 is a flow chart illustrating a method performed by a first network node in accordance with some embodiments. The first network node may perform the method in response to executing suitably formulated computer readable code. The computer readable code may be embodied or stored on a computer readable medium, such as a memory chip, optical disc, or other storage medium. The computer readable medium may be part of a computer program product. The first network node may be the network node 910 or network node 1100 as described later with reference to Figs. 9 and 11 respectively.

[0242] In step 801 , the network node receives a report relating to a successful DC mobility operation by a UE with respect to the first network node and / or a second network node. The report is received from the UE. The report was generated according to a first reporting configuration associated with a network node, i.e. the first network node, or a different network node.

[0243] In step 803, the network node determines which network node provided the first reporting configuration to the UE from the received report.

[0244] The method performed by the network node may also include the network node determining which network node initiated the successful DC mobility operation from the received report. In this respect, the received report may comprise an indication that the first network node triggered or initiated the DC mobility operation.

[0245] In some embodiments, the received report may comprise an indication that the report was generated according to the first reporting configuration.

[0246] The first network node may be a MN for the UE that the report was received from, or a SN that is providing a source PSCell for the UE.

[0247] Implementation examples of the first specific method for how the UE determines whether to create / store / loq the SPR

[0248] A non-limiting example implementation of the first specific method in this disclosure to determine whether to create / log SPR in the SPR report is highlighted in bold and underline in the following. This example is implemented on top of the first draft of the MRO running 3GPP Change Request (CR) [R2-2305986] submitted to the meeting RAN2#122.

[0249] *********************************************************

[0250] 5.7.10.X Actions for the successful PSCell oddition / chonge report determination

[0251] The UE shall for the PSCell:

[0252] 1> if the ratio between the value of the elapsed time of the timer T304 and the configured value of the timer T304, included in the last applied RRCReconflguration message for the SCG including the reconfigurationWithSync, is greater than thresholdPercentageT304-SCG if included in the successPSCell- Config received before executing the last reconfiguration with sync for the SCG:

[0253] 1> if the executed PSCell change is initiated by the source SN, and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageTS 10-SCG included in the successPSCell-Conflg associated to (or configured by) the SCG before executing the last reconfiguration with sync; or

[0254] 1> if the executed PSCell change is initiated by the source SN, and if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the reconfiguration with sync procedure and, if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageTS 12-SCG included in the successPSCell-Conflg of the otherConflg of SCG before executing the last reconfiguration with sync; or

[0255] 1> if the executed PSCell change is initiated by the MN, and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync, is greater than thresholdPercentageTS 10- SCG included in the successPSCell-Conflg of the otherConflg of MCG before executing the last reconfiguration with sync; or

[0256] 1> if the executed PSCell change is initiated by the MN, and if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the reconfiguration with sync procedure and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312-SCG included in the successPSCell- Conflg of the otherConflg of the MCG before executing the last reconfiguration with sync;

[0257] 2> store the successful PSCell change / addition information in VarSuccessPSCell-Report and determine the content in VarSuccessPSCell-Report as follows:

[0258] Editor's note: FFS if the C-RNTI to be included is the one configured for the MCG or for the SCG, or both should be included.

[0259] Editor's note: FFS the setting of plmn-IdentityList.

[0260] 3> for the source PSCell in which the last RRCReconflguration message for the SCG including reconflgurationWithSync was applied:

[0261] 4> set the sourcePSCelllD in sourcePSCelllnfo to the global cell identity and tracking area code, if available, of the source PSCell;

[0262] 4> set the sourcePSCellMeas in sourcePSCelllnfo to include the cell level RSRP, RSRQ and the available SINR, of the source PSCell based on the available SSB and CSI-RS measurements collected up to the moment the UE sends RRCReconfigurationComplete message for the SCG;

[0263] 4> set the rsIndexRe suits in sourceCellMeas to include all the available SSB and CSI-RS measurement quantities of the source PCell collected up to the moment the UE sends RRCReconfigurationComplete message for the SCG;

[0264] 3> for the target PSCell indicated in the last applied RRCReconflguration message for the SCG including reconfiguration WithSync

[0265] 4> set the targetPSCelUD in targetPSCelllnfo to the global cell identity and tracking area code, if available, of the target PSCell;

[0266] 4> set the targetPSCellMeas in targetPSCelllnfo to include the cell level RSRP, RSRQ and the available SINR, of the target PCell based on the available SSB and CSI-RS measurements collected up to the moment the UE sends RRCReconfigurationComplete message for the SCG;

[0267] 4> set the rsIndexRe suits in targetCellMeas to include all the available SSB and CSI-RS measurement quantities of the target PCell collected up to the moment the UE sends RRCReconfigurationComplete message for the SCG;

[0268] 4> if the last applied RRCReconflguration message for the SCG including reconflgurationWithSync was included in the stored condRRCReconflg'.

[0269] 5> set the timeSinceCPAC-Reconflg to the time elapsed between the initiation of the execution of conditional reconfiguration for the target PSCell and the reception of the last conditionalReconflguration for the SCG including the condRRCReconflg of the target PCell in the source PCell;

[0270] 3> if the ratio between the value of the elapsed time of the timer T304 and the configured value of the T304 timer, included in the last applied RRCReconflguration message for the SCG including the reconflgurationWithSync, is greater than thresholdPercentageT304SCG if included in the successPSCell-Conflg received before executing the last reconfiguration with sync for the SCG:

[0271] 4> set t304-cause in spr-Cause to true', 4> set the ra-InformationCommon to include the random-access related information associated to the random access procedure in the target PSCell, as specified in clause 5.7.10.5;

[0272] 3> for each of the measObjectNR, in which the last RRCReconflguration message for the SCG including reconflgurationWithSync was applied:

[0273] 4> if measurements are available for the measObjectNR'.

[0274] 5> if the SS / PBCH block-based measurement quantities are available:

[0275] 6> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell or target PCell, ordered such that the cell with highest SS / PBCH block RSRP is listed first if SS / PBCH block RSRP measurement results are available, otherwise the cell with highest SS / PBCH block RSRQ is listed first if SS / PBCH block RSRQ measurement results are available, otherwise the cell with highest SS / PBCH block SINR is listed first, based on the available SS / PBCH block based measurements collected up to the moment the UE sends the RRCReconfigurationComplete message for the SCG;

[0276] 6> for each neighbour cell included, include the optional fields that are available;

[0277] NOTE 1 : For the neighboring cells set included in measResultListNR in measResultNeighCells ordered based on the SS / PBCH block measurement quantities, the UE includes also the CSI-RS based measurement quantities, if available.

[0278] 5> if the CSI-RS measurement quantities are available:

[0279] 6> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell and target PCell, ordered such that the cell with highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the cell with highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the cell with highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE sends the RRCReconfigurationComplete message for the SCG;

[0280] 6> for each neighbour cell included, include the optional fields that are available;

[0281] NOTE 2: For the neighboring cells set ordered based on the CSI-RS measurement quantities, the UE includes measurements only for the cells not yet included in measResultListNR in measResultNeighCells to avoid overriding SS / PBCH block-based ordered measurements.

[0282] Editor's note: FFS whether measResultListEUTRA should be included.

[0283] 3> for each of the neighbour cells included in measResultNeighCells'.

[0284] 4> if the cell was a candidate target cell included in the condRRCReconfig within the conditionalReconfiguration, in which the last RRCReconflguration message for the SCG including reconflgurationWithSync was applied:

[0285] 5> set the choCandidate to true in measResultNR',

[0286] 4> if available, set the locationinfo, as in 5.3.3.7;

[0287] Editor's note: How to capture the release of the successPSCell-Conflg.

[0288] The UE may discard the successful PSCell addition / change information, i.e. , release the UE variable VarSuccessPSCell-Report, 48 hours after the last successful PSCell addition / change information is added to the VarSuccessPSCell-Report or upon detaching from the network. Implementation examples of the second method for how the UE determines whether to create / store / loq the SPR

[0289] A non-limiting example implementation of the second specific method of this disclosure to determine whether to create / log SPR in the SPR report is highlighted in bold and underline in the following. This example is implemented on top of the first draft of the MRO running 3GPP OR [R2-2305986] submitted to the meeting RAN2#122.

[0290] 5.7.10.X Actions for the successful PSCell oddition / chonge report determination

[0291] The UE shall for the PSCell:

[0292] 1> if the ratio between the value of the elapsed time of the timer T304 and the configured value of the timer T304, included in the last applied RRCReconflguration message for the SCG including the reconfigurationWithSync, is greater than thresholdPercentageT304-SCG if included in the successPSCell- Config received before executing the last reconfiguration with sync for the SCG:

[0293] 1> if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT310-SCG associated to the otherConflg of the SCG included in the successPSCell-Conflg if configured by the source PSCell before executing the last reconfiguration with sync; or

[0294] 1> if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT310-SCG associated to the otherConflg of the MCG included in the successPSCell-Conflg if configured by the source PCell before executing the last reconfiguration with sync; or

[0295] 1> if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the reconfiguration with sync procedure and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312- SCG associated to the otherConflg of the SCG included in the successPSCell-Conflg if configured by the source PSCell before executing the last reconfiguration with sync; or

[0296] 1> if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the reconfiguration with sync procedure and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T310, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312- SCG associated to the otherConflg of the MCG included in the successPSCell-Conflg if configured by the source PCell before executing the last reconfiguration with sync:

[0297] 2> store the successful PSCell change / addition information in VarSuccessPSCell-Report and determine the content in VarSuccessPSCell-Report as follows:

[0298] 3> for the source PSCell in which the last RRCReconflguration message for the SCG including reconfigurationWithSync was applied:

[0299] 4> set the sourcePSCelllD in sourcePSCelllnfo to the global cell identity and tracking area code, if available, of the source PSCell; 4> set the sourcePSCellMeas in sourcePSCelllnfo to include the cell level RSRP, RSRQ and the available SINR, of the source PSCell based on the available SSB and CSI-RS measurements collected up to the moment the UE sends RRCReconfigurationComplete message for the SCG;

[0300] 4> set the rsIndexRe suits in sourceCellMeas to include all the available SSB and CSI-RS measurement quantities of the source PCell collected up to the moment the UE sends RRCReconfigurationComplete message for the SCG;

[0301] 3> for the target PSCell indicated in the last applied RRCReconfiguration message for the SCG including reconfiguration WithSync:

[0302] 4> set the targetPSCelUD in targetPSCelllnfo to the global cell identity and tracking area code, if available, of the target PSCell;

[0303] 4> set the targetPSCellMeas in targetPSCelllnfo to include the cell level RSRP, RSRQ and the available SINR, of the target PCell based on the available SSB and CSI-RS measurements collected up to the moment the UE sends RRCReconfigurationComplete message for the SCG;

[0304] 4> set the rsIndexRe suits in targetCellMeas to include all the available SSB and CSI-RS measurement quantities of the target PCell collected up to the moment the UE sends RRCReconfigurationComplete message for the SCG;

[0305] 4> if the last applied RRCReconfiguration message for the SCG including reconf iguration WithSync was included in the stored condRRCReconfig'.

[0306] 5> set the timeSinceCPAC-Reconfig to the time elapsed between the initiation of the execution of conditional reconfiguration for the target PSCell and the reception of the last conditionalReconfiguration for the SCG including the condRRCReconfig of the target PCell in the source PCell;

[0307] 3> if the ratio between the value of the elapsed time of the timer T304 and the configured value of the T304 timer, included in the last applied RRCReconfiguration message for the SCG including the reconfigurationWithSync, is greater than thresholdPercentageT304-SCG if included in the successPSCell-Config received before executing the last reconfiguration with sync for the SCG:

[0308] 4> set t304-cause in spr-Cause to true',

[0309] 4> set the ra-InformationCommon to include the random-access related information associated to the random access procedure in the target PSCell, as specified in clause 5.7.10.5;

[0310] 3> if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT310-SCG associated to the otherConflg of the SCG included in the successPSCell-Config if configured by the source PSCell before executing the last reconfiguration with sync; or

[0311] 3> if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT310-SCG associated to the otherConflg of the MCG included in the successPSCell-Config if configured by the source PCell before executing the last reconfiguration with sync:

[0312] 4> set t310-cause in shr-Cause to true',

[0313] 3> if the T312 associated to the measurement identity of the target cell was miming at the time of initiating the execution of the reconfiguration with sync procedure and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312-SCG associated to the otherConflg of the SCG included in the successPSCell-Config if configured by the source PSCell before executing the last reconfiguration with sync; or 3> if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the reconfiguration with sync procedure and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T310, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312-SCG associated to the otherConflg of the MCG included in the successPSCell-Conflg if configured by the source PCell before executing the last reconfiguration with sync:

[0314] 4> set t312-cause in shr-Cause to true;

[0315] 3> for each of the measObjectNR, in which the last RRCReconflguration message for the SCG including reconflgurationWithSync was applied:

[0316] 4> if measurements are available for the measObjectNR'.

[0317] 5> if the SS / PBCH block-based measurement quantities are available:

[0318] 6> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell or target PCell, ordered such that the cell with highest SS / PBCH block RSRP is listed first if SS / PBCH block RSRP measurement results are available, otherwise the cell with highest SS / PBCH block RSRQ is listed first if SS / PBCH block RSRQ measurement results are available, otherwise the cell with highest SS / PBCH block SINR is listed first, based on the available SS / PBCH block based measurements collected up to the moment the UE sends the RRCReconfigurationComplete message for the SCG;

[0319] 6> for each neighbour cell included, include the optional fields that are available;

[0320] NOTE 1 : For the neighboring cells set included in measResultListNR in measResultNeighCells ordered based on the SS / PBCH block measurement quantities, the UE includes also the CSI-RS based measurement quantities, if available.

[0321] 5> if the CSI-RS measurement quantities are available:

[0322] 6> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell and target PCell, ordered such that the cell with highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the cell with highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the cell with highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE sends the RRCReconfigurationComplete message for the SCG;

[0323] 6> for each neighbour cell included, include the optional fields that are available;

[0324] NOTE 2: For the neighboring cells set ordered based on the CSI-RS measurement quantities, the UE includes measurements only for the cells not yet included in measResultListNR in measResultNeighCells to avoid overriding SS / PBCH block-based ordered measurements.

[0325] Editor's note: FFS whether measResultListEUTRA should be included.

[0326] 3> for each of the neighbour cells included in measResultNeighCells'.

[0327] 4> if the cell was a candidate target cell included in the condRRCReconfig within the conditionalReconfiguration, in which the last RRCReconflguration message for the SCG including reconflgurationWithSync was applied:

[0328] 5> set the choCandidate to true in measResultNR',

[0329] 3> if available, set the locationinfo, as in 5.3.3.7; 3> if the successful PSCell addition / change information is triggered by fulfilling at least one of the triggering conditions associated to the otherConfig of the MCG:

[0330] 4> include the sprTriggeredMN and set it to true1,

[0331] 3> if the successful PSCell addition / change information is triggered based on at least one of the triggering conditions associated to the otherConfig of the MCG and at least one of the triggering conditions associated to the otherConfig of the SCG:

[0332] 4> include the sprTriggeringNode and set it to false1.

[0333] Editor's note: How to capture the release of the successPSCell-Conflg.

[0334] The UE may discard the successful PSCell addition / change information, i.e. , release the UE variable VarSuccessPSCell-Report, 48 hours after the last successful PSCell addition / change information is added to the VarSuccessPSCell-Report or upon detaching from the network.

[0335] ********************************************************* Fig. 9 shows an example of a communication system 900 in accordance with some embodiments. In the example, the communication system 900 includes a telecommunication network 902 that includes an access network 904, such as a radio access network (RAN), and a core network 906, which includes one or more core network nodes 908. The access network 904 includes one or more access network nodes, such as access network nodes 910a and 910b (which are interchangeably referred to as RAN network nodes 910 herein), or any other similar 3rdGeneration Partnership Project (3GPP) access node or non-3GPP access point (AP). Moreover, as will be appreciated by those of skill in the art, a RAN 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 902 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 902 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 902, including one or more network nodes 910 and / or core network nodes 908.

[0336] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O- CU user plane (O-CU-UP), a RAN intelligent controller (RIC) (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1 , F1 , W1 , E1 , E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies.

[0337] The access network nodes 910 facilitate direct or indirect connection of wireless devices (also referred to interchangeably herein as user equipment (UE)), such as by connecting UEs 912a, 912b, 912c, and 912d (one or more of which may be generally referred to as UEs 912) to the core network 906 over one or more wireless connections. The access network nodes 910 may be, for example, access points (APs) (e.g. radio access points), base stations (BSs) (e.g. radio base stations, Node Bs, evolved Node Bs (eNBs) and New Radio (NR) NodeBs (gNBs)).

[0338] Unless otherwise indicated, the general term ‘network node’ as used herein refers to access network nodes 910 and core network nodes 908.

[0339] 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 900 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 900 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0340] The wireless devices / UEs 912 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 910 and other communication devices. Similarly, the access network nodes 910 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 912 and / or with other network nodes or equipment in the telecommunication network 902 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 902.

[0341] In the depicted example, the core network 906 connects the access network nodes 910 to one or more hosts, such as host 916. 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 906 includes one more core network nodes (e.g. core network node 908) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the wireless devices / UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 908. Example core network nodes include functions of one or more of a Mobile Switching Center (M SC), 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).

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

[0343] As a whole, the communication system 900 of Fig. 9 enables connectivity between the wireless devices / UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2ndGeneration (2G), 3rdGeneration (3G), 4thGeneration (4G), 5thGeneration (5G) standards, or any applicable future generation standard (e.g. 6thGeneration (6G)); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

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

[0345] In some examples, the UEs 912 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 904 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 904. Additionally, a UE may be configured for operating in single- or multi-radio access technology (RAT) or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved- UTRA (UMTS Terrestrial Radio Access) Network) New Radio - Dual Connectivity (EN-DC).

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

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

[0348] Fig. 10 shows a wireless device or UE 1000 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a wireless device / UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless camera, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0349] A wireless device / UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to- everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g. a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g. a smart power meter).

[0350] The UE 1000 includes processing circuitry 1002 that is operatively coupled via a bus 1004 to an input / output interface 1006, a power source 1008, a memory 1010, a communication interface 1012, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Fig. 10. 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.

[0351] The processing circuitry 1002 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 1010. The processing circuitry 1002 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 1002 may include multiple central processing units (CPUs). The processing circuitry 1002 may be operable to provide, either alone or in conjunction with other UE 1000 components, such as the memory 1010, to provide UE 1000 functionality. For example, the processing circuitry 1002 may be configured to cause the UE 1002 to perform the methods according to any of the embodiments described herein.

[0352] In the example, the input / output interface 1006 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 1000. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g. a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

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

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

[0355] The memory 1010 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a Universal Subscriber Identity Module (USIM) and / or integrated SIM (ISIM), other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 1010 may allow the UE 1000 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to offload 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 1010, which may be or comprise a device- readable storage medium.

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

[0357] In some embodiments, communication functions of the communication interface 1012 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) or other Global Navigation Satellite System (GNSS) 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, 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.

[0358] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1012, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g. once every 15 minutes if it reports the sensed temperature), random (e.g. to even out the load from reporting from several sensors), in response to a triggering event (e.g. when moisture is detected an alert is sent), in response to a request (e.g. a user initiated request), or a continuous stream (e.g. a live video feed of a patient).

[0359] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or controls a robotic arm performing a medical procedure according to the received input.

[0360] A UE, when in the form of an 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 devices which are or which are embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or VR, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence on the intended application of the loT device in addition to other components as described in relation to the UE 1000 shown in Fig. 10.

[0361] 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 3GPP NB-loT 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.

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

[0363] Fig. 11 shows an access network node 1100 or RAN network node 1100 in accordance with some embodiments. As used herein, access network node or RAN network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other RAN network nodes or equipment or core network nodes, in a telecommunication network. Examples of access network nodes include, but are not limited to, access network nodes such as APs (e.g. radio access points), base stations (BSs) (e.g. radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), Open RAN (O-RAN) nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU)..

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

[0365] Other examples of access 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).

[0366] The RAN network node 1100 includes processing circuitry 1102, a memory 1104, a communication interface 1106, and a power source 1108, and / or any other component, or any combination thereof. The RAN network node 1100 may be composed of multiple physically separate components (e.g. a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the RAN network node 1100 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 RAN network node 1100 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g. separate memory 1104 for different RATs) and some components may be reused (e.g. a same antenna 1110 may be shared by different RATs). The RAN network node 1100 may also include multiple sets of the various illustrated components for different wireless technologies integrated into RAN network node 1100, 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 RAN network node 1100.

[0367] The processing circuitry 1102 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 RAN network node 1100 components, such as the memory 1104, to provide network node 1100 functionality. For example, the processing circuitry 1102 may be configured to cause the RAN network node to perform the methods of any of the embodiments described herein.

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

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

[0370] The communication interface 1106 is used in wired or wireless communication of signalling and / or data between network nodes, the access network, the core network, and / or a UE. As illustrated, the communication interface 1106 comprises port(s) / terminal(s) 1116 to send and receive data, for example to and from a network over a wired connection.

[0371] The communication interface 1106 also includes radio front-end circuitry 1118 that may be coupled to, or in certain embodiments a part of, the antenna 1110. Radio front-end circuitry 1118 comprises filters 1120 and amplifiers 1122. The radio front-end circuitry 1118 may be connected to an antenna 1110 and processing circuitry 1102. The radio front-end circuitry may be configured to condition signals communicated between antenna 1110 and processing circuitry 1102. The radio front-end circuitry 1118 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 1118 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1120 and / or amplifiers 1122. The radio signal may then be transmitted via the antenna 1110. Similarly, when receiving data, the antenna 1110 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1118. The digital data may be passed to the processing circuitry 1102. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0372] In certain alternative embodiments, the access network node 1100 does not include separate radio front-end circuitry 1118, instead, the processing circuitry 1102 includes radio frontend circuitry and is connected to the antenna 1110. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1112 is part of the communication interface 1106. In still other embodiments, the communication interface 1106 includes one or more ports or terminals 1116, the radio front-end circuitry 1118, and the RF transceiver circuitry 1112, as part of a radio unit (not shown), and the communication interface 1106 communicates with the baseband processing circuitry 1114, which is part of a digital unit (not shown).

[0373] The antenna 1110 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 1110 may be coupled to the radio front-end circuitry 1118 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 1110 is separate from the network node 1100 and connectable to the RAN network node 1100 through an interface or port.

[0374] The antenna 1110, communication interface 1106, and / orthe processing circuitry 1102 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 1110, the communication interface 1106, and / or the processing circuitry 1102 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.

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

[0376] Embodiments of the RAN network node 1100 may include additional components beyond those shown in Fig. 11 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 RAN network node 1100 may include user interface equipment to allow input of information into the RAN network node 1100 and to allow output of information from the RAN network node 1100. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the RAN network node 1100.

[0377] Fig. 12 is a block diagram illustrating a virtualization environment 1200 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 1200 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, a wireless device / UE, a 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 1200 includes components defined by the Open-RAN (O-RAN) Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

[0378] Applications 1202 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 1200 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

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

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

[0381] In the context of NFV, a VM 1208 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 1208, and that part of hardware 1204 that executes that VM, be it hardware dedicated to thatVM 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 1208 on top of the hardware 1204 and corresponds to the application 1202.

[0382] Hardware 1204 may be implemented in a standalone network node with generic or specific components. Hardware 1204 may implement some functions via virtualization. Alternatively, hardware 1204 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 1210, which, among others, oversees lifecycle management of applications 1202. In some embodiments, hardware 1204 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signalling can be provided with the use of a control system 1212 which may alternatively be used for communication between hardware nodes and radio units.

[0383] Although the computing devices described herein (e.g. UEs, RAN network nodes, core network node, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

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

[0385] The foregoing merely illustrates the principles of the disclosure. Various modifications and alterations to the described embodiments will be apparent to those skilled in the art in view of the teachings herein. It will thus be appreciated that those skilled in the art will be able to devise numerous systems, arrangements, and procedures that, although not explicitly shown or described herein, embody the principles of the disclosure and can be thus within the scope of the disclosure. Various exemplary embodiments can be used together with one another, as well as interchangeably therewith, as should be understood by those having ordinary skill in the art.

[0386] The following numbered statements set out various exemplary embodiments of the techniques described herein.

[0387] Group A Embodiments

[0388] 1 . A method performed by a user equipment, UE, that is using dual connectivity, DC, wherein the UE has a first reporting configuration associated with a first network node in a communication network, and a second reporting configuration associated with a second network node in the communication network, wherein a reporting configuration indicates information to be provided in a report for a successful DC mobility operation relating to the first network node and / or the second network node, the method comprising: obtaining information according to the first reporting configuration for a successful DC mobility operation; and generating a report relating to the successful DC mobility operation, the report comprising the information obtained according to the first reporting configuration.

[0389] 2. The method of Embodiment 1 , wherein the communication network is a Self-Organising Network, SON, and the generated report is a SON report. 3. The method of Embodiment 1 or 2, wherein the report is a Successful Primary Secondary Cell Group Cell, PSCell, Report, SPR.

[0390] 4. The method of any of Embodiments 1 -3, wherein the information to be provided in the report relating to the DC mobility operation comprises any one or more of: location information; radio measurement results; and a Conditional Handover, CHO, configuration.

[0391] 5. The method of any of Embodiments 1-4, wherein the method further comprises: sending the generated report to any one or more of the first network node, the second node and a third network node in the communication network.

[0392] 6. The method of any of Embodiments 1 -5, wherein the UE has a first set of criteria relating to the first reporting configuration.

[0393] 7. The method of Embodiment 6, wherein the UE has a second set of criteria relating to the second reporting configuration.

[0394] 8. The method of Embodiment 6 or 7, wherein the criteria comprise timer values.

[0395] 9. The method of any of Embodiments 6-8, wherein the step of obtaining information and / or generating are performed if the criteria are met.

[0396] 10. The method of any of Embodiments 1-9, wherein the mobility operation is a Primary Secondary Cell Group Cell, PSCell, Addition or Change operation.

[0397] 11. The method of Embodiment 10, wherein the first network node is one of: (i) a Master Node, MN, (ii) a source Secondary Node, SN, providing the PSCell before the PSCell Addition or Change operation; and (iii) a target SN providing the PSCell after the PSCell Addition or Change operation.

[0398] 12. The method of Embodiment 10 or 11 , wherein the second network node is one of: (i) a Master Node, MN, (ii) a source Secondary Node, SN, providing the PSCell before the PSCell Addition or Change operation; and (iii) a target SN providing the PSCell after the PSCell Addition or Change operation.

[0399] 13. The method of any of Embodiments 1-12, wherein the step of obtaining comprises obtaining information according to only the first reporting configuration.

[0400] 14. The method of any of Embodiments 1-13, wherein the generated report comprises the information obtained according to only the first reporting configuration.

[0401] 15. The method of Embodiment 13 or 14, wherein the first network node is the network node that triggered or initiated the DC mobility operation.

[0402] 16. The method of Embodiment 15, wherein the first network node is one of a Master Node, MN, forthe UE or a Secondary Node, SN, providing a source Primary Secondary Cell Group Cell, PSCell, for the UE.

[0403] 17. The method of Embodiment 16, wherein the second network node is the other one of the MN and Secondary Node, SN, providing the source PSCell.

[0404] 18. The method of Embodiment 13 or 14, wherein the first network node is a Master Node, MN, for the UE.

[0405] 19. The method of Embodiment 18, wherein the second network node is a Secondary Node, SN, providing a source Primary Secondary Cell Group Cell, PSCell, for the UE.

[0406] 20. The method of Embodiment 13 or 14, wherein the first network node is a Secondary Node, SN, providing a target Primary Secondary Cell Group Cell, PSCell, for the UE.

[0407] 21. The method of Embodiment 20, wherein the second network node is one of a Master Node, MN, for the UE or a Secondary Node, SN, providing a source PSCell for the UE.

[0408] 22. The method of any of Embodiments 1-12, wherein the step of obtaining comprises obtaining information according to both the first reporting configuration and the second reporting configuration, and wherein the generated report comprises information obtained according to the first reporting configuration and information obtained according to the second reporting configuration. 23. The method of Embodiment 22, wherein the first reporting configuration comprises one or more first criteria, the second reporting configuration comprises one or more second criteria, and wherein the one or more first criteria and one or more second criteria are fulfilled.

[0409] 24. The method of Embodiment 23, wherein the information obtained according to the first reporting configuration and information obtained according to the second reporting configuration are ordered in the generated report according to an order in which the one or more first criteria and one or more second criteria are fulfilled.

[0410] 25. The method of any of Embodiments 1-24, wherein the generated report comprises an indication that the report was generated according to the first reporting configuration.

[0411] 26. The method of any of Embodiments 1-25, wherein the generated report comprises an indication of which network node triggered or initiated the DC mobility operation.

[0412] 27. The method of any of Embodiments 1-26, wherein the generated report comprises an indication of one or more criteria for the first reporting configuration that were fulfilled in order to generate the report.

[0413] Group B Embodiments

[0414] 28. A method performed by a first network node, the method comprising: receiving, from a user equipment, UE, a report relating to a successful dual connectivity, DC, mobility operation by the UE with respect to the first network node and / or a second network node, wherein the report was generated according to a first reporting configuration associated with a network node; and determining, from the received report, which network node provided the first reporting configuration to the UE.

[0415] Group C Embodiments

[0416] 29. A computer program product comprising a computer readable medium having computer readable code embodied therein, the computer readable code being configured such that, on execution by a suitable computer or processor, the computer or processor is caused to perform the method of any of the Group A embodiments or the Group B embodiments.

[0417] 30. A user equipment, UE, configured to perform the method of any of the Group A embodiments. 31. A user equipment, UE, comprising a processor and a memory, said memory containing instructions executable by said processor whereby said UE is operative to perform the method of any of the Group A embodiments.

[0418] 32. A network node configured to perform the method of any of the Group B embodiments.

[0419] 33. A network node comprising a processor and a memory, said memory containing instructions executable by said processor whereby said network node is operative to perform the method of any of the Group B embodiments.

[0420] 34. A user equipment, UE, comprising: processing circuitry configured to cause the user equipment to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry.

[0421] 35. A network node, the network node comprising: processing circuitry configured to cause the network node to perform any of the steps of any of the Group B embodiments; power supply circuitry configured to supply power to the processing circuitry.

[0422] 36. A user equipment, UE, the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.

Claims

Claims1 . A method performed by a user equipment, UE, that is using dual connectivity, DC, wherein the UE has a first Successful Primary Secondary Cell Group Cell Change / Addition Report, SPR, configuration associated with a first network node in a communication network, and a second SPR configuration associated with a second network node in the communication network, wherein a SPR configuration indicates respective criteria for triggering a SPR for a successful Primary Secondary Cell Group Cell, PSCell, change or addition relating to the first network node and / or the second network node, the method comprising: determining (501) that the first network node triggered or initiated a PSCell change or addition relating to the first network node and / or the second network node and evaluating the criteria for the first SPR configuration; if the criteria for the first SPR configuration is met: obtaining (503) information for the SPR for a successful PSCell change or addition; and generating (505) a SPR relating to the successful PSCell change or addition comprising the information.

2. The method of Claim 1 , wherein the communication network is a Self-Organising Network, SON, and the generated SPR is a SON report.

3. The method of any of Claims 1-2, wherein the method further comprises: sending the generated SPR to any one or more of the first network node, the second node and a third network node in the communication network.

4. The method of any of Claims 1-3, wherein the criteria for each SPR configuration comprise timer values.

5. The method of Claim 4, wherein the timer values comprise T310 and / or T312 thresholds.

6. The method of any of Claims 1-5, wherein the first network node is one of: (i) a Master Node, MN, (ii) a source Secondary Node, SN, providing the PSCell before the PSCell Change operation; and (iii) a target SN providing the PSCell after the PSCell Addition or Change operation.

7. The method of any of Claims 1-6, wherein the second network node is one of: (i) a Master Node, MN, (ii) a source Secondary Node, SN, providing the PSCell before the PSCell Change operation; and (iii) a target SN providing the PSCell after the PSCell Addition or Change operation.

8. The method of any of Claims 1-7, wherein the first network node is one of a Master Node, MN, for the UE or a Secondary Node, SN, providing a source PSCell for the UE.

9. The method of Claim 8, wherein the second network node is the other one of the MN and Secondary Node, SN, providing the source PSCell.

10. The method of any of Claims 1-9, wherein the generated SPR comprises an indication that the SPR was generated according to the first SPR configuration.

11. The method of any of Claims 1-10, wherein the generated SPR comprises an indication that the first network node triggered or initiated the PSCell change or addition.

12. The method of any of Claims 1-11 , wherein the generated SPR comprises an indication of the criteria for the first SPR configuration that were fulfilled in order to generate the SPR.

13. A method performed by a first network node, the method comprising: receiving (601), from a user equipment, UE, a Successful Primary Secondary Cell Group Cell Change / Addition Report, SPR, relating to a successful Primary Secondary Cell Group Cell, PSCell, change or addition by the UE with respect to the first network node and / or a second network node, wherein the SPR was generated according to a first SPR configuration associated with a network node; and determining (603), from the received SPR, which network node provided the first SPR configuration to the UE.

14. The method as claimed in claim 13, wherein the method further comprises: determining, from the received SPR, which network node initiated the successful PSCell change or addition.

15. The method as claimed in claim 13 or 14, wherein the received SPR comprises an indication that the SPR was generated according to the first SPR configuration.

16. The method as claimed in any of claims 13-15, wherein the received SPR comprises an indication that the first network node triggered or initiated the PSCell change or addition.

17. A computer program product comprising a computer readable medium having computer readable code embodied therein, the computer readable code being configured such that, on execution by a suitable computer or processor, the computer or processor is caused to perform the method of any of claims 1-16.

18. A user equipment, UE, configured to perform the method of any of claims 1-12.

19. A user equipment, UE, comprising a processor and a memory, said memory containing instructions executable by said processor whereby said UE is operative to perform the method of any of claims 1-12.

20. A network node configured to perform the method of any of claims 13-16.

21. A network node comprising a processor and a memory, said memory containing instructions executable by said processor whereby said network node is operative to perform the method of any of claims 13-16.

Images