WO2025005854A1

WO2025005854A1 - Configurations relating to a mobility operation

Info

Publication number: WO2025005854A1
Application number: PCT/SE2024/050620
Authority: WO
Inventors: Ali PARICHEHREHTEROUJENI; Marco BELLESCHI; Pradeepa Ramachandra
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2023-06-28
Filing date: 2024-06-24
Publication date: 2025-01-02
Anticipated expiration: 2025-12-28

Abstract

According to an aspect, there is provided a method performed by a user equipment (UE). The UE has a first configuration associated with a Master Node (MN) in a communication network and a second configuration associated with a Secondary Node (SN) in the communication network. The first configuration and the second configuration indicate information to be provided in a report relating to a mobility operation with respect to the SN. The method comprises, if the MN initiated the mobility operation, obtaining information (601) according to the first configuration for the mobility operation. If the SN initiated the mobility operation, obtaining (601) information according to the second configuration for the mobility operation; and generating (603) a report relating to the mobility operation, the report comprising the obtained information.

Description

CONFIGURATIONS RELATING TO A MOBILITY OPERATION

Technical Field

This disclosure relates to User Equipments (UEs) and methods performed by a UE when the UE has a configuration relating to a mobility operation.

Background

Overall Architecture of NG-RAN

The current 5^th Generation (5G) Radio Access Network (RAN) (NG-RAN) architecture is depicted in Fig. 1 and described in the 3^rd Generation Partnership Project (3GPP) Technical Standard (TS) 38.401 v17.2.0 as follows:

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

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.

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

• gNBs can be interconnected through the Xn interface.

• 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.

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

• NG, Xn and F1 are logical interfaces.

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.

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.

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.

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

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.

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).

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.

Self-Organising Networks (SON) in 3GPP

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).

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.

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.

Fig. 2 illustrates the ramifications of Self-Configuration/Self-Optimisation functionality, and 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:

• Basic Setup; and

• Initial Radio Configuration. are covered by the Self Configuration process.

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.

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

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.

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.

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).

Mobility Robustness Optimisation (MRO) in 3GPP

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).

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.

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

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

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);

3) Upon reaching the maximum number of RLC retransmissions;

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

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.

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.

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:

1) Measurement quantities (Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ)) of the last serving cell (Primary Cell (PCell)). 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).

4) Measurement quantity (RSSI) associated to Bluetooth beacons.

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

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.

7) Tracking area code of the PCell.

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

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

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.

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.

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.

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. 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.

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.

Successful Handover report

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:

*********************************************************

5.7.10.6 Actions for the successful handover report determination

The UE shall for the PCell:

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

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 -Config if configured by the source PCell before executing the last reconfiguration with sync; or > 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 success! lO-Config if configured by the source PCell before executing the last reconfiguration with sync; or > 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:

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

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

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

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

3> for the source PCell in which the last RRCReconflguration message including reconfigurationWithSync was applied:

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

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;

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;

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:

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

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;

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;

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;

4> if the last applied RRCReconflguration message including reconfigurationWithSync was included in the stored condRRCReconflg'.

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;

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- Conflg received before executing the last reconfiguration with sync:

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

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;

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:

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

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 successHO-Conflg if configured by the source PCell before executing the last reconfiguration with sync:

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

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:

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

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

4> if measurements are available for the measObjectNR'.

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

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;

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

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.

5> if the CSI-RS measurement quantities are available: 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;

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.

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

4> if measurements are available for the measObjectEUTRA'.

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 RRCReconfigurationComplete message;

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

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

4> if the cell was a candidate target cell included in the condRRCReconfig within the conditionalReconfiguration configured by the source PCell, in which the last RRCReconfiguration message including reconflgurationWithSync was applied:

5> set the choCandidate to true in measResultNR',

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

1> release successHO-Conflg configured by the source PCell and threshold? ercentageTS 04 if configured by the target PCell.

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.

5.7.10 UE Information

5.7.10.1 General

[See Fig. 3: Figure 5.7.10.1-1: UE information procedure]

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

- UElnformationResponse

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) RLC-SAP: AM

Logical channel: DCCH

Direction: UE to network

UElnformationResponse message

*********************************************************

Successful PSCell chanqe/addition report

A Successful Primary Secondary Cell Group (SCG) Cell (PSCell) 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 principle of the successful handover (HO) report but potentially three nodes can be involved in the procedure. Therefore, potentially three nodes can configure and request forthe 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.

Summary

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 a so-called Successful PSCell change/addition Report (SPR)) as well as mobility procedures (with a report called Successful Handover Report (SHR)).

Including the location information in such reports is agreed and implemented in the running Change Request (CR) [3GPP R2-2305986] as shown in the following:

5.7.10. X Actions for the successful PSCell addition/change report determination

The UE shall for the PSCell:

[some procedural text omitted]

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

4> if the cell was a candidate target cell included in the condRRCReconflg within the conditionalReconflguration, in which the last RRCReconflguration message forthe SCG including reconfigurationWithSync was applied: 5> set the choCandidate to true vameasResultNR

3> if available, set the locationinfo as in 5.33.7;

Editor's note: How to capture the release of the successPSCell-Config.

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.

However, as shown in the extract from the RRC specification 3GPP TS 38.331 v17.4.0 below, the setting locationinfo includes setting Bluetooth, WLAN and sensor measurements that requires the UE to follow specific configurations provided by the network.

Locationinfo

The IE Locationinfo is used to transfer available detailed location information, Bluetooth, WLAN and sensor available measurement results at the UE.

Locationinfo information element

Such configuration is shown in the following excerpt from the RRC specification 3GPP TS

38.331 V17.4.0:

Such configurations are provided as part of otherConfig in the RRCReconfiguration message. In a Dual Connectivity (DC) scenario there can be multiple instances of otherConfig(s), one configured by the MN and one configured by the SN, and one received as part of otherConfig of the RRCReconfiguration message received from the target cell. Therefore, there might be multiple/three different Bluetooth name (LOCAL NAME) list or WLAN name list (i.e. Service Set Identifier (SSID)) etc. associated to different Cell Groups at the UE.

The problem with the existing solution in the specifications is that there is no straightforward approach to log the locationinfo based on the plurality of the location configurations provided by multiple RAN nodes involved in the mobility and dual connectivity operations. In other words, it is not clear what configuration(s) the UE shall apply when setting the content of the location information. This is shown in Fig. 4 for the dual connectivity scenarios in which three location information configurations can be configured by three different nodes.

The UE can be configured with multiple location configurations provided by the source SN, MN and target SN. The location configurations can be provided to the UE in the form of RRCReconfigurations.

The RRCReconfiguration sent by the source SN can include an otherConfig associated to the Source SN (source SCG) which includes a SPR configuration (e.g. T310/T312 thresholds) and the location information configuration. This RRCReconfiguration message can be sent via SRB3 or SRB1 relayed by the MN.

The RRCReconfiguration sent by the MN can include an otherConfig associated to the MN which includes a SPR configuration (e.g. T310/T312 thresholds) and the location information configuration. This RRCReconfiguration message can be sent via SRB1.

The RRCReconfiguration sent by the target SN can include an otherConfig associated to the Target SN (target SCG) which includes a SPR configuration (e.g. T304 thresholds) and the location information configuration. This RRC message is sent inside the outer RRC Reconfiguration.

When the UE wants to log the locationinfo in the Successful PSCell change/addition Report (SPR), it is not clear which location information configuration should be considered for logging the associated location info.

The same problem exists in case of logging the location information in the Successful Handover Report (SHR) when both source and target RAN nodes provide location configuration. This is schematically exemplified in Fig. 5.

The UE can be configured with two location configurations provided by the source and target RAN node of the HOs. The location configurations can be provided to the UE in the form of RRCReconfigurations.

The RRCReconfiguration prepared and sent by the source RAN node can include an otherConfig associated to the source cell which includes a SPR configuration (e.g. T310/T312 thresholds) and the location information configuration.

The RRCReconfiguration sent by the target RAN node can include an otherConfig associated to the target cell which includes a SPR configuration (e.g. T304 thresholds) and the location information configuration. This RRC message is sent inside the outer RRC Reconfiguration.

When the UE wants to log the locationinfo in the Successful Handover Report (SHR), it is not clear which location information configuration should be considered for logging the associated location info in the report.

Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges.

In a first main embodiment of this disclosure, the UE can log a set of information (e.g. location information) based on triggering/fulfilling one or more thresholds/conditions configured by the network node for the generation of a SON report. These thresholds/conditions are generally referred to herein as ‘criteria’. The SON report can be any of SPR, SHR, and based on one or more configurations needed for the UE log in the said report the location information and measurements.

For the case of SPR/SHR, in a non-limiting example embodiment, the UE can include information according to any one or more of the following:

• The UE can include a first set of location information and measurements associated to a first configuration configured by a first network node, if the fulfilled triggering thresholds/conditions (to log the SON report e.g. SPR, SHR) are provided by a first network (NW) node.

• The UE can include a second set of information (e.g. location information) associated to a second configuration configured by a second network node, if the fulfilled triggering conditions are provided by a second NW node. If the fulfilled triggered thresholds/conditions are both provided by first and second network nodes, the UE can include both the first and second sets of information.

• The UE can include a third set of information (e.g. location information) associated to a first and second configuration configured by the first and second network node respectively, irrespective of whether the fulfilled triggering conditions are provided by a first or second NW node.

• The UE can include a fourth set of information (e.g. location information) associated to a first or second configuration configured by the first or second network node respectively, whichever has provided a configuration used by the UE to include the said set of information. This method can be applicable, for example, in case the fulfilled triggering conditions are the ones provided by the second network node, but only the first network node has provided a configuration that the UE can use to provide the said set of information.

• The UE can include a fifth set of information (e.g. location information) associated to a fifth configuration configured by a third network node, which has provided the last configuration used by the UE to include the said set of information. This method can be applicable, for example, in case neither the first nor the second network node that configured the fulfilled triggering conditions, have provided a configuration that the UE can use to provide the said set of information. The third network node is a node to which the UE has been previously connected.

• For the case of PSCell change or addition, the UE can include a sixth set of location information and measurements associated to a first configuration configured by the first network node, if the first network node is the MN, and the PSCell change/addition is MN initiated.

• For the case of PSCell change, the UE can include a seventh set of information (e.g. location information) associated to a second configuration configured by the second network node, if the second network node is the SN and the PSCell change is SN initiated.

Any or each of the first/second/third/fourth/fifth/sixth/seventh set of information mentioned above may comprise any one or more of location info, measurement results, and/or CHO configuration. In the above embodiments, the first NW node can be the MN of a DC configuration, and the second network node can be the SN of a DC configuration.

In the above example embodiment, only two network nodes (two gNBs) are considered. However the techniques described herein can be applied to more than two network nodes. For example, three gNBs can be considered, e.g. in a dual connectivity scenario, where the first configuration is provided by the first network node, i.e. MN, the second configuration is provided by the second network node, i.e. source SN, and the third configuration is provided by the third network node, i.e. target SN in a mobility procedure. Hence the UE can provide:

• The first set of information and measurements based on the first configuration if the first set of triggering conditions are fulfilled.

• The second set of information and measurements based on the second configuration if the second set of triggering conditions are fulfilled.

• The third set of information and measurements based on the third configuration if the third set of triggering conditions are fulfilled.

• The fourth set of information and measurements associated to a first and/or second and/or third configuration configured by the first, second and third network node respectively, irrespective of whether the fulfilled triggering conditions are provided by a first, second or third network node.

• The UE can include a fifth set of information (e.g. location information) associated to a first/second/third configuration configured by the first/second/third network node respectively, whichever has provided a configuration used by the UE to include the said set of information. This method can be applicable for example in case the fulfilled triggering conditions are the one provided by the second network node, but only the first network node has provided a configuration that the UE can use to provide the said set of information.

• The UE can include a sixth set of information (e.g. location information) associated to a sixth configuration configured by a fourth network node, which has provided the last configuration used by the UE to include the said set of information. This method can be applicable, for example, in case neither the first, second or third network node, that configured the fulfilled triggering conditions, have provided a configuration that the UE can use to provide the said set of information. The fourth network node can be a node to which the UE has been previously connected.

• For the case of PSCell change or addition, the UE can include a seventh set of location information and measurements associated to a first configuration configured by the first network node, if the first network node is the MN and the PSCell change/addition is MN initiated.

• For the case of PSCell change, the UE can include an eighth set of information (e.g. location information) associated to a second configuration configured by the second network node, if the second network node is the SN and the PSCell change is SN initiated.

In a second main embodiment of this disclosure, for the case of RLF/HOF, the UE can log a set of information (e.g. location information) in a SON report, e.g. an RLF-Report, based on one or more configurations configured to the UE:

• The UE can include the location information and measurements associated to a first configuration configured by the first network node, with the first network node being the source node of the failed handover (for the case of HOF) or the last serving node before the RLF (for the case of RLF).

• The UE can include the location information and measurements associated to a second configuration configured by the second network node, with the second network node being the target node of the failed handover.

• The UE can include the location information and measurements associated to a first and second configuration configured by the first and second network node, with the first network node being the source node of the failed handover, and the second network node being the target node of the failed handover.

• The UE can include the location information and measurements associated to a first or second configuration configured by the first or second network node, with the first network node being the source node of the failed handover, and the second network node being the target node of the failed handover, whichever has provided a configuration used by the UE to log the said location information and measurements.

• The UE can include the location information and measurements associated to a third configuration configured by the third network node, with the third network node being the last node that provided the UE with a configuration used by the UE to log the said location information and measurements.

Thus, the techniques described herein provide for the logging of information and measurements, e.g. location information in SON reports like SHR or SPR reports, based on a certain set of configurations provided by one or more of the multiple network nodes involved in a mobility operation (e.g. source node and target node), or in a dual connectivity operation (e.g. source SN, MN or target SN).

This disclosure provides methods for the UE to determine when to include the location information based on the configuration provided by the source MN, when to include the location information based on the configuration provided by the target MN, when to include the location information based on the configuration provided by the source SN, and when to include the location information based on the configuration provided by the target SN.

According to a first aspect, there is provided a method performed by a user equipment, UE. The UE has a first configuration associated with a Master Node, MN, in a communication network and a second configuration associated with a Secondary Node, SN, in the communication network. The first configuration and the second configuration indicate information to be provided in a report relating to a mobility operation with respect to the SN. The method comprises: if the MN initiated the mobility operation, obtaining information according to the first configuration for the mobility operation, and if the SN initiated the mobility operation, obtaining information according to the second configuration for the mobility operation; and generating a report relating to the mobility operation, the report comprising the obtained information.

According to a second 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 or any embodiment thereof.

According to a third aspect, there is provided a user equipment, UE, configured to perform the method according to the first aspect or any embodiment thereof.

According to a fourth aspect, there is provided 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 according to the first aspect or any embodiment thereof.

Certain embodiments may provide one or more of the following technical advantage(s). Embodiments described herein can enable the UE to provide the measurements, such as location information in a SON report, where the included measurements are based on a set of configurations provided by the network node that is supposed to receive the SON report and perform the related analysis. In other words, without the proposed solutions, the provided measurement and information (e.g. location Information) may not be provided in such a way that the network node responsible for analysis of the SON report (e.g. taking the proper corrective decision) could understand and perform the analysis.

Brief Description of the Drawings

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

Fig. 1 is an illustration of a NG-RAN architecture;

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

Fig. 3 is a signalling diagram from a 3GPP standard illustrating a UE information procedure;

Fig. 4 illustrates problems in logging locationinfo in dual connectivity scenarios in which three location information configurations can be configured by three different nodes;

Fig. 5 illustrates problems in logging location information in a SHR;

Fig. 6 is a flow chart illustrating an exemplary method in a UE;

Fig. 7 is a flow chart illustrating another exemplary method in a UE;

Fig. 8 is a flow chart illustrating yet another exemplary method in a UE;

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

Fig. 10 shows a UE in accordance with some embodiments.

Detailed Description

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.

The techniques described herein are applicable to both single connectivity (e.g. logging the SHR when executing a handover procedure) and the dual connectivity-related mobility procedures (e.g. logging SPR when executing a PSCell change/addition).

UE embodiments in a successful handover scenario

This disclosure provides methods performed by a wireless terminal/user equipment (UE). In these methods, the UE can receive a first set of configurations from a first network node (here the source of the HO). The first set of configurations can comprise one or more configurations. The first set of configurations, e.g. based on the network request, may include:

• Triggering conditions (i.e. a set of criteria) for the SHR ‘successful handover’ configuration (e.g. these triggering conditions can be T310/T312 based SHR triggering conditions);

• A configuration for the location information, such as a Bluetooth name list and a WLAN name list, etc. This configuration indicates the information to be included in a generated report.

It should be noted that the above configurations (successful handover configuration and the location information) and the location information configuration can be received at different points in time. The UE can also receive a second set of configurations from a second network node (here the target of the HO). The second set of configurations can comprise one or more configurations. The second set of configurations, based on the network request, may include:

• Triggering conditions (i.e. a set of criteria) for the SHR ‘successful handover’ configuration (e.g. T304 based SHR triggering condition);

• A configuration for the location information, such as a Bluetooth name list and a WLAN name list, etc.

It should be noted that the above configurations (successful handover configuration and the location information) and the location info configuration can be received at different points in time.

The UE can performing a reconfiguration with sync (handover) procedure toward the target cell served by the second network/RAN node or served by another network node that leads to the fulfilment of one or more configured SHR triggering conditions by the source RAN node, or the target RAN node.

The UE logs the SHR (i.e. obtains information relating to the handover), and can include any of the following in the SHR:

• a first set of information and measurements based on first set of configurations configured by the first network node (source node), if a first set of conditions (criteria) are fulfilled;

• a second set of information associated to a second configuration configured by the second network node (target gNB), if a second set of conditions (criteria) are fulfilled;

• a third set of information associated to a first and second configuration configured by the first and second network node respectively, irrespective of whether the first or second set of conditions are fulfilled. For example, if the first network node provides a first Bluetooth name list and a first WLAN name list for which the UE should provide the set of information, and the second network node provides a second Bluetooth name list and a second WLAN name list for which the UE should provide the said set of information, the UE can log a set of information taking into account both the said first and second list (possibly discarding duplicate Bluetooth/WLAN names across the two lists);

• a fourth set of information associated to a third configuration configured by the third network node, if the third network node is the last node that has provided the last configuration used by the UE to include the said first set of information, wherein the third network node is a node to which the UE has been previously connected. For example, in case neither the source (first) nor the target (second) network node that configured the fulfilled set of conditions have provided a configuration that the UE can use to provide the said set of information, the UE can adopt a previously received configuration from the third network node. The first set of conditions/criteria can include one or more of the following:

1) the UE is always to include the location information based on the configuration provided by the first network node (source node). An advantage of such an embodiment would be that the inclusion of the location information in the SHR would aid the source network node in using this information in future mobility decisions, i.e. in mobility decisions when handovers are influenced by the location information. For example, if the UE includes the location information based on the source node’s configuration, and if this handover was deemed to be close to a ‘too late’ handover then this information could be useful in future handovers. If a UE sends a measurement report including a location information that is close (with ‘closeness’ being defined in terms of the distance) to the location information as included in the SHR, then the source node can take actions faster to ensure a future handover is not delayed as there is a risk of a ‘too late’ handover. In another example, if the UE includes the location information based on the source node’s configuration, and if this handover was deemed to be close to a ‘too early’ handover then this information could be useful in future handovers. A UE that sends a measurement report including a location information that is close (where closeness could be defined in terms of distance) to the location information as included in the SHR, then the source node can take actions to delay a future handover to a specific target node if such a handover was deemed to be a candidate for a ‘too early’ handover towards such a target node at that location.

2) if the SHR triggering conditions/thresholds as configured by the first network node are fulfilled. An advantage of such an embodiment is that the UE can include the location information based on the source cell’s configuration only if a handover was close to a ‘too late’ handover, and thus the action to change the handover parameters are underthe supervision of the source node.

3) if the SHR triggering conditions/thresholds as configured by the second network node are fulfilled, but only the first network node has provided a configuration used by the UE to include the first set of information.

The second set of conditions/criteria can include one or more of the following:

1) the UE always includes the location information based on the configuration provided by the second network node (target node). An advantage of such an embodiment would be that the inclusion of the location information in the SHR would enable the target network node to use this information in the future mobility decisions, i.e. in mobility decisions when the handovers are influenced by the location information. For example, if the UE includes the location information based on the target node’s configuration and if this handover was deemed to be close to a ‘too early’ handover then this information could be useful in future handovers. Any UE in the future that sends a measurement report including a location information that is close (where closeness could be defined in terms of the distance) to the location information as included in the SHR and such a measurement report is received by the target node from the source node in a handover request, then the target node can take actions to ensure there is enough time for the random access procedure for the UE, i.e. by configuring the T304 with a larger value.

2) if the SHR triggering conditions/thresholds as configured by the second network node are fulfilled. An advantage of such an embodiment would be that the UE includes the location information based on the target cell’s configuration only if a handover was close to failing due to the expiry of T304 timer, and thus the action to configure such a timer’s value lies with the target node.

3) if the SHR triggering conditions/thresholds as configured by the first network node are fulfilled, but only the second network node has provided a configuration used by the UE to include the said second set of information.

In some embodiments, the first set of information may be location information (locationinfo) based on the location configuration that the UE received from the first network node, and the second set of information may be location information (location Info) based on the location configuration that the UE received from the second network node.

In some embodiments, the first set of information can include Layer 3 filtered Radio Resource Management (RRM) measurements based on the configurations that the UE received from the first network node. The second set of information can include Layer 3 filtered RRM measurements based on the configurations that the UE received from the second network node. The measurements can include cell and/or beam level measurements of signal/radio quality parameters such as RSRP, RSRQ, Signal to Interference plus Noise Ratio (SINR), etc.

UE embodiments in PSCell chanqe/addition scenarios (SPR)

This disclosure provides methods performed by a wireless terminal/UE in which the UE can receive a first set of configurations from a first network node (here the source SN in case of PSCell change). The first set of configurations can comprise one or more configurations. The first set of configurations, e.g. based on the first node request, may include:

• T riggering conditions (i.e. a set of criteria) for the SPR ‘successful PSCell change/addition’ configuration (e.g. T310/T312 based SPR triggering conditions);

It should be noted that the above configurations (i.e. successful PSCell change configuration and the location information) and the location info configuration can be received at different points in time. It should also be noted that in the case of PSCell addition the above configurations are absent.

The method in the UE can also comprise the UE receiving a second set of configurations from the second network node (here the master node (MN)). The second set of configurations can comprise one or more configurations. The second set of configurations, e.g. based on the second node request, may include:

• Triggering conditions for the SPR ‘successful PSCell change/addition’ configuration (e.g. T311/T312 based SHR triggering condition);

It should be noted that the above configurations (i.e. successful handover configuration and the location information) and the location info configuration can be received at different points in time.

The method in the UE can also comprise receiving a third set of configurations from the third network node (here the target secondary node (target SN)). The third set of configurations can comprise one or more configurations. The third set of configurations, e.g. based on the third node request, may include:

It should be noted that the above configurations (i.e. successful PSCell change/addition configuration and the location information) and the location info configuration can be received at different points in time.

The method in the UE can also comprise performing a reconfiguration with sync (handover) procedure towards the target cell served by the target SN, or served by another RAN node that leads to the fulfilment of one or more configured SPR triggering conditions configured as part of the first, second or third configurations configured by the source SN, MN, and the target SN.

The method in the UE can also comprise logging the SPR. The SPR can include any of:

• a first set of information and/or measurements based on first set of configurations configured by the first network node (source MN node), if the fulfilled triggering thresholds/conditions are provided by a first network node;

• a second set of information and/or measurements based on the second configuration configured by the second network node (source SN gNB), if the fulfilled triggering conditions are provided by a second network node; • a third set of information and/or measurements based on the third configuration configured by the third network node (target SN gNB), if the fulfilled triggering conditions are provided by a third network node;

• both the first and second sets of information and/or measurements if the fulfilled triggered thresholds/conditions are provided by first and second network node. In an embodiment, the UE can include a union subset of the information and/or measurements based on the first and second configuration;

• both the first and third sets of information and/or measurements if the fulfilled triggered thresholds/conditions are provided by first and third network node. In an embodiment, the UE can include a union subset of the information and/or measurements based on the first and third configuration;

• both the second and third sets of information and/or measurements if the fulfilled triggered thresholds/conditions are provided by second and third network node. In an embodiment, the UE can include a union subset of the information and/or measurements based on the second and third configuration;

• all of the first, second and third sets of information and/or measurements if the fulfilled triggered thresholds/conditions are provided by the first, second and third network nodes. In an embodiment, the UE can include a union subset of the information and/or measurements based on the first, second and third configurations;

• a union subset of the information and/or measurements based on the first, second and third configurations.

In an alternative step of logging the SPR, the UE can include any one or more of the following in the SPR:

• a first set of information and/or measurements based on the first set of configurations configured by the first network node (source MN node), if the first set of conditions are fulfilled;

• a second set of information and/or measurements based on the second configuration configured by the second network node (source SN gNB), if the second set of conditions are fulfilled;

• a third set of information and/or measurements based on the third configuration configured by the third network node (target SN gNB), if the third set of conditions are fulfilled;

• a fourth set of information and/or measurements associated to a first and/or second and/or third configuration configured by the first, second and/or third network node respectively, irrespective of whether the fulfilled triggering conditions are provided by the first, second or third network node. For example, if the first network node provides a first Bluetooth name list and a first WLAN name list for which the UE should provide the said set of information, the second network node provides a second Bluetooth name list and a second WLAN name list for which the UE should provide the said set of information, and the third network node provides a third Bluetooth name list and a third WLAN name list for which the UE should provide the said set of information, the UE can log a set of information taking into account all of the first, second and third lists (possibly discarding duplicate Bluetooth/WLAN names across the three lists);

• a fifth set of information associated to a fourth configuration configured by a fourth network node, if the fourth network node is the last node that has provided the last configuration used by the UE to include the said first set of information. The fourth network node may be a node to which the UE has previously been connected. For example, in case neither the MN (first), nor the source SN (second) nor the target SN (third) network node, that configured the fulfilled set of conditions have provided a configuration that the UE can use to provide the said set of information, the UE can adopt a previously received configuration from the fourth network node.

The first set of conditions/criteria can include one or more of the following:

1) the UE is always to include the location information based on the configuration provided by the first network node (source MN). An advantage of such an embodiment would be that the inclusion of the location information in the SPR would aid the source MN in using this information in future SN change or SN addition decisions, i.e. in SN addition/change decisions when the decisions are influenced by the location information. For example, if the UE includes the location information based on the source MN’s configuration, and if this SN change was deemed to be close to a ‘too late’ SN change, then this information could be useful in future SN change decisions. If a UE sends a measurement report including a location information that is close (with ‘closeness’ being defined in terms of the distance) to the location information as included in the SPR, then the source MN node can take actions faster to ensure the SN change is not delayed as there is a risk of a ‘too late’ SN change. In another example, if the UE includes the location information based on the source MN node’s configuration and if this SN addition/change was deemed to be close to a ‘too early’ SN addition/change, then this information could be useful in future SN addition/change decisions. A UE that sends a measurement report including a location information that is close (e.g. in terms of the distance) to the location information as included in the SPR, then the source MN node can take actions to delay a SN addition/change to a specific target node if such a SN addition/change was deemed to be a candidate for a ‘too early’ SN addition/change towards such a target node at that location. 2) if the SPR triggering conditions/thresholds as configured by the first network node (source MN) are fulfilled and if the associated SN addition/change was a MN-initiated operation. An advantage of such an embodiment would be that the UE includes the location information based on the source MN’s configuration only if a SN change was close to a ‘too late’ SN change, and thus the action to change the SN addition/change parameters are under the supervision of the source node.

3) if the SPR triggering conditions/thresholds as configured by the third network node (target SN) are fulfilled and if the associated SN addition/change was a MN-initiated operation. An advantage of such an embodiment would be that the UE includes the location information based on the source MN’s configuration only if the MN had initiated the SN change/addition, and if the SN addition/change was close to being declared as a handover failure (i.e., T304 expiry). In such a case, the source MN could delay a future SN addition/change at this location (or in the close by location) so that the UE is already had better uplink (UL) towards the target SN.

4) if the associated SN addition/change was a MN-initiated operation, irrespective of whether the SPR triggering conditions/thresholds are the ones configured by the first, second or third network node.

5) if the SPR triggering conditions/thresholds as configured by the second or third network node are fulfilled, but only the first network node has provided a configuration used by the UE to include the said first set of information.

The second set of conditions/criteria can include one or more of the following:

1) if the SPR triggering conditions/thresholds as configured by the second network node (source SN) are fulfilled and if the associated SN change was a SN-initiated operation. An advantage of such an embodiment would be that the UE includes the location information based on the source SN’s configuration only if a SN change was close to a ‘too late’ SN change, and thus the action to change the SN change parameters are under the supervision of the source SN node.

2) if the SPR triggering conditions/thresholds as configured by the third network node (target SN) are fulfilled and if the associated SN change was a SN-initiated operation. An advantage of such an embodiment would be that the UE includes the location information based on the source SN’s configuration only if the SN had initiated the SN change, and if the SN change was close to being declared as a handover failure (i.e., T304 expiry). In such a case, the source SN could for example delay a future SN change at this location (or close by to this location).

3) if the associated SN addition/change was an SN-initiated operation, irrespective of whether the SPR triggering conditions/thresholds are the ones configured by the first, second or third network node. 4) if the SPR triggering conditions/thresholds as configured by the first or third network node are fulfilled, but only the second network node has provided a configuration used by the UE to include the said set of information.

The third set of conditions/criteria can include one or more of the following:

1) if the SPR triggering conditions/thresholds as configured by the third network node (target SN) are fulfilled. An advantage of such an embodiment would be that the UE includes the location information based on the target SN’s configuration only if a SN change was close to a handover failure (i.e. T304 expiry). Thus, for a UE to which the source MN or the source SN sends a future SN change request and the location included in the measurement report associated to such a request is close to the location information included in the SPR associated to the target SN configuration, then the target SN can configure a larger value of T304 timer for that future SN change to ensure that there is enough time for the SN change operation.

2) if the SPR triggering conditions/thresholds as configured by the first or second network node are fulfilled, but only the third network node has provided a configuration used by the UE to include the said set of information.

In some embodiments, the first set of information can be location information (location Info) based on the location configuration that the UE received from the first network node. The second set of information can be location information (location Info) based on the location configuration that the UE received from the second network node. The third set of information can be location information (location Info) based on the location configuration that the UE received from the third network node.

In some embodiments, the first set of information can include Layer 3 filtered RRM measurements based on the configurations that the UE received from the first network node. The second set of information can include Layer 3 filtered RRM measurements based on the configurations that the UE received from the second network node. The third set of information can include Layer 3 filtered RRM measurements based on the configurations that the UE received from the third network node. The measurements can include cell and/or beam level measurements of signal/radio quality parameters such as RSRP, RSRQ, Signal to Interference plus Noise Ratio (SI NR), etc.

UE embodiments in RLF/HOF scenarios (RLF-Report)

This disclosure provides methods performed by a wireless terminal/UE in which the UE can receive a first set of configurations from the first network node (here the MN). The first set of configurations can comprise one or more configurations. The first set of configurations may include configuration for the location information, such as a Bluetooth name list and a WLAN name list, etc.

The UE may also receive a second set of configurations from the second network node (here SN). The second set of configurations can comprise one or more configurations. The second set of configurations may include configuration for the location information, such as a Bluetooth name list and a WLAN name list, etc.

Upon declaring RLF or HOF, the UE can log the RLF-Report. The UE can include any one or more of the following in the RLF-Report:

• a first set of information and/or measurements based on the first set of configurations configured by the first network node (MN), if a first set of conditions are fulfilled;

• a second set of information associated to a second configuration configured by the second network node (SN), if a second set of conditions are fulfilled;

• for the case of HOF, a third set of information associated to a first and second configuration configured by the first and second network node, where the first network node is the source node of the failed handover, and the second network node is the target node of the failed handover. For example, if the first network node provides a first Bluetooth name list and a first WLAN name list for which the UE should provide the said set of information, and the second network node provides a second Bluetooth name list and a second WLAN name list for which the UE should provide the said set of information, the UE can log a set of information taking into account both the said first and second list (possibly discarding duplicate Bluetooth/WLAN names across the two lists).

• a third set of information associated to a third configuration configured by the third network node, where the third network node is the last node that provided the UE with a configuration used by the UE to log the said location information and measurements prior the RLF/HOF.

The first set of conditions/criteria can be that the UE always includes the location information based on the configuration provided by the first network node (MN), which is the source node of the failed handover (for the case of HOF) or the last serving node before the RLF (for the case of RLF).

The second set of conditions/criteria include one or more of the following:

• that the connection failure is an handover failure, where the second network node is the target node of the failed handover;

• that the connection failure is an RLF, and the first network node has not provided a configuration used by the UE to log the said location information and measurements.

In some embodiments, the first set of information may be location information (locationinfo) based on the location configuration that the UE received from the first network node, and the second set of information can be location information (location Info) based on the location configuration that the UE received from the second network node.

Implementation examples to the UE report in SHR

A non-limiting example implementation of the method proposed in this disclosure for logging the location information in SHR is shown in the following, where the parts implementing the techniques described herein are marked in bold and underline.

*********************************************************

5.7.10.6 Actions for the successful handover report determination

The UE shall for the PCell:

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

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

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:

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

3> set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e., includes the RPLMN); 3> set the c-R\ TI to the C-RNTI assigned by the target PCell of the handover;

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

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

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

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:

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

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

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! IO-Conjig if configured by the source PCell before executing the last reconfiguration with sync:

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

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

4> if measurements are available for the measObjectNR'.

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

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

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;

4> if measurements are available for the measObjectEUTRA'.

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; 5> for each neighbour cell included, include the optional fields that are available;

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

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 reconfigurationWithSync was applied:

5> set the choCandidate to true in measResultNR',

3> if shr-Cause is set to t304-cause'.

4> if available, set the location I nfo Target according to the otherConfig associated with the target PCell RRC Reconfiguration, as in 5.3.3.7;

3> if shr-Cause is set to t312-cause or t310-cause'.

4> if available, set the locationlnfoSource according to the otherConfig associated with the source PCell RRC Reconfiguration, as in 5.3.3.7;

Implementation examples to the UE report in SPR

A non-limiting example implementation of the method proposed in this disclosure to log the location information in the SPR is shown in the following, where the parts implementing the techniques described herein are marked in bold and underline. This example is implemented on top of the first draft of the MRO running CR [R2-2305986] submitted to the meeting RAN2#122.

*********************************************************

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

The UE shall for the PSCell:

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 success? SCell- Config received before executing the last reconfiguration with sync for the SCG:

Editor's Note: Conditions related to T310/T312 will be included once configuration settings is agreed.

Editor's Note: Other triggering conditions are FFS.

2> clear the information included in VarSuccessPSCell-Report, if any; 2> store the successful PSCell change/addition information in VarSuccessPSCell-Report and determine the content in VarSuccessPSCell-Report as follows:

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.

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

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

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;

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;

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

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

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;

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;

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

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;

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:

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;

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

4> if measurements are available for the measObjectNR'.

5> if the SS/PBCH block-based measurement quantities are available: 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;

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.

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

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;

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

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

4> if the cell was a candidate target cell included in the condRRCReconfig within the conditionalReconfiguration, in which the last RRCReconfiguration message for the SCG including reconfigurationWithSync was applied:

5> set the choCandidate to true in measResultNR',

3> if spr-Cause is set to t304-

4> if available, set the locationlnfoTargetSN according to the otherConfig associated with the target PSCell, as in 5.3.3.7;

3> if the spr-Cause is set to t310-cause or t312-cause and PSCell change was an MN initiated procedure

4> if available, set the locationlnfoMN according to the otherConfig associated with the source PCell, as in 5.3.3.7;

3> if the spr-Cause is set to t310-cause or t312-cause and PSCell change was an SN initiated procedure

4> if available, set the locationlnfoSourceSN according to the otherConfig associated with the source PSCell, as in 5.3.3.7; In another example implementation the above non-limiting example text capturing the techniques described herein can be formulated as follows

3> if spr-Cause is set to t304-cause‘,

4> if available, set the locationlnfoTargetSN according to the otherConfig associated with the target PSCell (or associated with the otherConfig of the target SCG), as in 5.3.3.7;

3> if the spr-Cause is set to t310-cause or t312-cause and the triggering conditions were configured by the source SN (or were associated with the otherConfig of the source SCG)

4> if available, set the locationlnfoSourceSN according to the otherConfig associated with the source PSCell (or associated with the source SCG), as in 5.3.3.7;

3> if the spr-Cause is set to t310-cause or t312-cause and the triggering conditions were configured by the MN (or were associated with the otherConfig of the MCG)

Another example implementation of the techniques described herein can be formulated as follows:

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

4> if the cell was a candidate target cell included in the condRRCReconflg within the conditionalReconflguration, in which the last RRCReconflguration message for the SCG including reconfigurationWithSync was applied:

5> set the choCandidate to true in measResultNR',

3> if available, set the locationlnfoSourceSN, locationlnfoMN and locationlnfoTargetSN according to the otherConfig associated with the source SCG, MCG and target SCG respectively, as in 5.3.3.7;

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

*********************************************************

Fig. 6 is a flow chart illustrating an exemplary method in a UE. The UE may be the UE 912 or UE 1000 as described later with reference to Figs. 9 and 10 respectively). 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 has a first configuration associated with a MN in a communication network and a second configuration associated with a SN in the communication network. The first configuration and the second configuration indicate information to be provided in a report relating to a mobility operation with respect to the SN.

In the method of Fig. 6, information is obtained according to one of the configurations. In particular, if the MN initiated the mobility operation, in step 601 information is obtained according to the first configuration for the mobility operation. However, if the SN initiated the mobility operation, then in step 601 information is obtained according to the second configuration for the mobility operation.

In step 603, the UE generates a report relating to the mobility operation that comprises the obtained information.

In some embodiments, the UE sends the generated report to the MN. The generated report may be sent to the MN in response to a request from the MN.

The communication network may be a Self-Organising Network (SON), and the generated report can be a SON report.

The information to be provided in the report relating to the mobility operation can comprise any one or more of: location information; radio measurement results; and a Conditional Handover (CHO) configuration.

The first configuration and the second configuration may be location configurations.

The first configuration and the second configuration may be part of a set of configurations associated with the MN and SN respectively.

The UE may have a first set of criteria relating to the first configuration, and step 601 and/or step 603 can be performed if the one or more of the first set of criteria are fulfilled.

The mobility operation may be a handover to or from the SN. The handover can be between the SN and another network node in the communication network.

The UE may be using Dual Connectivity (DC), and the mobility operation may be a Primary Secondary Cell Group Cell (PSCell) Addition or Change operation. In this case, the SN is one of: (i) the SN providing the PSCell before the PSCell Change operation; and (ii) the SN providing the PSCell after the PSCell Addition or Change operation. In these embodiments, the MN may be the node that provided the last used configuration to the UE.

The first configuration may relate to a report to be generated in the event of a failure of the handover. Alternatively, the first configuration and second configuration may relate to a report to be generated if the mobility operation is successful. The report to be generated can be a Successful Handover Report (SHR), or a Successful Primary Secondary Cell Group Cell (PSCell) Addition or Change Report (SPR). The UE may have a first set of criteria relating to the first configuration and the second configuration, and step 605 can be performed if the mobility operation is successful and one or more of the first set of criteria are fulfilled. Fig. 7 is a flow chart illustrating another exemplary method in a UE. The UE may be the UE 912 or UE 1000 as described later with reference to Figs. 9 and 10 respectively). 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 has a first reporting configuration associated with a first network node in a communication network, and the first reporting configuration indicates information to be provided in a report relating to a mobility operation.

In step 701 , the UE obtains information according to the first reporting configuration for a mobility operation with respect to a second network node in the communication network.

In step 703, the UE generates a report relating to the mobility operation that comprises the information obtained according to the first reporting configuration.

Fig. 8 is a flow chart illustrating yet another exemplary method in a UE. The UE may be the UE 912 or UE 1000 as described later with reference to Figs. 9 and 10 respectively). 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 has a first reporting configuration associated with a first network node in a communication network, and the first reporting configuration indicates information to be provided in a report relating to a failure of a radio link for the UE.

In step 801 , the UE obtains information according to the first reporting configuration in the event of a failure of the radio link.

In step 803, the generates a report relating to the failure of the radio link comprising the obtained information according to the first reporting configuration.

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 3^rd Generation 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.

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.

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)).

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

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.

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.

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).

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. 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 2^nd Generation (2G), 3^rd Generation (3G), 4^th Generation (4G), 5^th Generation (5G) standards, or any applicable future generation standard (e.g. 6^th Generation (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.

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.

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).

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.

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.

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. 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).

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.

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 any of the methods as described herein.

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.

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.

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.

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.

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.

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.

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).

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.

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.

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.

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.

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.

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.

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.

The following numbered statements set out some exemplary embodiments of the techniques described herein.

1. A method performed by a user equipment, UE, wherein the UE has a first reporting configuration associated with a first network node in a communication network, wherein the first reporting configuration indicates information to be provided in a report relating to a mobility operation, the method comprising: obtaining information according to the first reporting configuration for a mobility operation with respect to a second network node in the communication network; and generating a report relating to the mobility operation, the report comprising the information obtained according to the first reporting configuration.

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 information to be provided in the report relating to the mobility operation comprises any one or more of: location information; radio measurement results; and a Conditional Handover, CHO, configuration.

4. The method of any of Embodiments 1 -3, wherein the UE has a first set of criteria relating to the first reporting configuration, and wherein the step of obtaining information and/or the step of generating the report is performed if the one or more of the first set of criteria are fulfilled.

5. The method of any of Embodiments 1-4, wherein the UE has a second reporting configuration for another network node in the communication network, wherein the second reporting configuration indicates information to be provided in a report relating to the mobility operation. 6. The method of Embodiment 5, wherein the method further comprises: obtaining information according to the second reporting configuration for the mobility operation; and wherein the step of generating comprises generating the report comprising the information obtained according to the first reporting configuration and/or the second reporting configuration.

7. The method of Embodiment 6, wherein the UE has a first set of criteria relating to the first reporting configuration and a second set of criteria relating to the second reporting configuration, and wherein the steps of obtaining information and/or the steps of generating the report are performed according to which of the first set of criteria and/or second set of criteria are fulfilled.

8. The method of any of Embodiments 5-7, wherein the method further comprises: evaluating whether to obtain information according to the first reporting configuration or second reporting configuration.

9. The method of any of Embodiments 1-8, wherein the method further comprises: sending the generated report to the first network node.

10. The method of Embodiment 9, wherein the generated report is sent to the first network node in response to a request from the first network node.

11. The method of any of Embodiments 1-10, wherein the mobility operation is a handover to or from the second network node.

12. The method of any of Embodiments 1-11 , wherein the mobility operation is a handover between the first network node and the second network node.

13. The method of any of Embodiments 1-11 , wherein the mobility operation is a handover between the second network node and a third network node in the communication network.

14. The method of Embodiment 13, wherein the first network node is a network node to which the UE has previously been connected or that provided the last used reporting configuration to the UE. 15. The method of any of Embodiments 1-10, wherein the UE is using Dual Connectivity, DC, and the mobility operation is a Primary Secondary Cell Group Cell, PSCell, Addition or Change operation; wherein the second network node is one of: (i) the Secondary Node, SN, providing the PSCell before the PSCell Addition or Change operation; and (ii) the SN providing the PSCell after the PSCell Addition or Change operation.

16. The method of Embodiment 15, wherein the first network node is the other one of the SN providing the PSCell before or after the PSCell Addition or Change operation.

17. The method of Embodiment 15, wherein the first network node is the Master Node.

18. The method of Embodiment 15, wherein the first network node is a network node that provided the last used reporting configuration to the UE.

19. The method of any of Embodiments 1-18, wherein the first reporting configuration relates to a report to be generated if the mobility operation is successful.

20. The method of Embodiment 19, wherein the report to be generated is a Successful Handover Report, SHR, or a Successful Primary Secondary Cell Group Cell, PSCell, Addition or Change Report, SPR.

21. The method of Embodiment 19 or 20, wherein the UE has a first set of criteria relating to the first reporting configuration, and wherein the step of generating the report is performed if the mobility operation is successful and one or more of the first set of criteria are fulfilled.

22. The method of any of Embodiments 19-21 , wherein the UE has a second reporting configuration associated with another network node in the communication network, wherein the second reporting configuration indicates information to be provided in a report relating to a successful mobility operation, and wherein the method further comprises: obtaining information according to the second reporting configuration for the mobility operation. 23. The method of Embodiment 22, wherein the step of generating comprises generating the report comprising the information obtained according to the first reporting configuration and/or the information obtained according to the second reporting configuration.

24. The method of any of Embodiments 22-24, wherein the UE has a first set of criteria relating to the first reporting configuration, and the UE has a second set of criteria relating to the second reporting configuration.

25. The method of Embodiment 24, wherein the step of generating comprises generating the report comprising one of:

(i) the information obtained according to the first reporting configuration if one or more of the first set of criteria are fulfilled;

(ii) the information obtained according to the second reporting configuration if one or more of the second set of criteria are fulfilled;

(iii) the information obtained according to the first reporting configuration and the second reporting configuration regardless of whether the first set of criteria and the second set of criteria are fulfilled; and

(iv) the information obtained according to the first reporting configuration and the second reporting configuration if one or more of the first set of criteria and one or more of the second set of criteria are fulfilled.

26. The method of any of Embodiments 22-25, wherein said another network node is the second network node, or a third network node in the communication network.

27. The method of any of Embodiments 11-13, wherein the first reporting configuration relates to a report to be generated in the event of a failure of the handover.

28. A method performed by a user equipment, UE, wherein the UE has a first reporting configuration associated with a first network node in a communication network, wherein the first reporting configuration indicates information to be provided in a report relating to a failure of a radio link for the UE, the method comprising: obtaining information according to the first reporting configuration in the event of a failure of the radio link; and generating a report relating to the failure of the radio link, the report comprising the obtained information according to the first reporting configuration. 29. The method of Embodiment 28, wherein the communication network is a Self-Organising Network, SON, and the generated report is a SON report.

30. The method of Embodiment 28 or 29, wherein the information to be provided in the report relating to the failure of the radio link comprises any one or more of: location information; radio measurement results; and a Conditional Handover, CHO, configuration.

31. The method of any of Embodiments- 28-30, wherein the first network node is the last network node serving the UE prior to the failure of the radio link.

32. The method of any of Embodiments 28-31 , wherein the method further comprises: sending the generated report to the first network node.

33. The method of Embodiment 32, wherein the generated report is sent to the first network node in response to a request from the first network node.

34. 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 Embodiments 1-33.

35. A user equipment, UE, configured to perform the method of any of Embodiments 1-33.

36. 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 Embodiments 1-33.

37. A user equipment, UE, comprising: processing circuitry configured to cause the user equipment to perform any of the steps of any of Embodiments 1-33; and power supply circuitry configured to supply power to the processing circuitry. 38. 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 Embodiments 1-33; 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

1 . A method performed by a user equipment, UE, wherein the UE has a first configuration associated with a Master Node, MN, in a communication network and a second configuration associated with a Secondary Node, SN, in the communication network, wherein the first configuration and the second configuration indicate information to be provided in a report relating to a mobility operation with respect to the SN, the method comprising: if the MN initiated the mobility operation, obtaining (601) information according to the first configuration for the mobility operation, and if the SN initiated the mobility operation, obtaining (601) information according to the second configuration for the mobility operation; and generating (603) a report relating to the mobility operation, the report comprising the obtained information.

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

3. The method of claim 1 or 2, wherein the information to be provided in the report relating to the mobility operation comprises any one or more of: location information; radio measurement results; and a Conditional Handover, CHO, configuration.

4. The method of any of claims 1-3, wherein the first configuration and the second configuration are location configurations.

5. The method of any of claims 1-4, wherein the first configuration and the second configuration are part of a set of configurations associated with the MN and SN respectively.

6. The method of any of claims 1-5, wherein the UE has a first set of criteria relating to the first configuration, and wherein the step of obtaining (601) information and/orthe step of generating (603) the report is performed if the one or more of the first set of criteria are fulfilled.

7. The method of any of claims 1-6, wherein the method further comprises: sending the generated report to the MN.

8. The method of claim 7, wherein the generated report is sent to the MN in response to a request from the MN.

9. The method of any of claims 1-8, wherein the mobility operation is a handover to or from the SN.

10. The method of any of claims 1 -9, wherein the mobility operation is a handover between the SN and another network node in the communication network.

11. The method of any of claims 1-8, wherein the UE is using Dual Connectivity, DC, and the mobility operation is a Primary Secondary Cell Group Cell, PSCell, Addition or Change operation; wherein the SN is one of: (i) the SN providing the PSCell before the PSCell Change operation; and (ii) the SN providing the PSCell after the PSCell Addition or Change operation.

12. The method of claim 11 , wherein the MN provided the last used configuration to the UE.

13. The method of any of claims 1-12, wherein the first configuration and second configuration relate to a report to be generated if the mobility operation is successful.

14. The method of claim 13, wherein the report to be generated is a Successful Handover Report, SHR, or a Successful Primary Secondary Cell Group Cell, PSCell, Addition or Change Report, SPR.

15. The method of claim 13 or 14, wherein the UE has a first set of criteria relating to the first configuration and the second configuration, and wherein the step of generating (603) the report is performed if the mobility operation is successful and one or more of the first set of criteria are fulfilled.

16. The method of any of claims 9 or 10, wherein the first configuration relates to a report to be generated in the event of a failure of the handover.

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-16.

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-16.