Performing a mobility procedure

Abstract

In an example, a method performed by a wireless communication device for performing a mobility procedure is provided The method comprises performing a mobility procedure, and determining if at least one condition for generating a Successful Handover Report (SHR) has been met. The method also comprises, before sending, to a network node, a message indicating that the wireless communication device has performed the mobility procedure, if the at least one condition has been met, and the wireless communication device is storing a previous SHR, deleting the previous SHR, and if the at least one condition has not been met, and the wireless communication device is storing a previous SHR, maintaining the previous SHR.

Description

[0001] PERFORMING A MOBILITY PROCEDURE

[0002]

[0003] General on 3GPP

[0004] In release 8 of the 3GPP standard, the Evolved Packet System (EPS) was specified. EPS is based on the Long-Term Evolution (LTE) radio network and the Evolved Packet Core (EPC). It was originally intended to provide voice and mobile broadband (MBB) services but has continuously evolved to broaden its functionality. Since Release 13 NB-loT and LTE-M are part of the LTE specifications and provide connectivity to massive machine type communications (mMTC) services.

[0005] In 3GPP release 15, the first release of the 5G system (5GS) was specified. This is a new generation radio access technology intended to serve use cases such as enhanced mobile broadband (eMBB), ultra-reliable and low latency communication (URLLC) and mMTC services. 5G includes the New Radio (NR) access stratum interface and the 5G Core Network (5GC). The NR physical and higher layers are reusing parts of the LTE specification, and additional components are introduced when motivated by the new use cases. One such component is the introduction of a sophisticated framework for beam forming and beam management to extend the support of the 3GPP technologies to a frequency range going beyond 6 GHz.

[0006] Self-Orqanizinq Network

[0007] Self-Organizing Networks (SON) is a collection of functions for automatic configuration, optimization, and healing of networks. The aim of the framework is to perform routine maintenance and optimization where necessary without additional configuration. To enable this functionality, multiple reports are defined and collected from the UE. Some relevant ones are introduced in the following.

[0008] Successful PSCell Report (SPR) is generated by a UE performing a PSCell change if the conditions set by the network are fulfilled. Generation of SPR refers to UE being close to failure of the PSCell change.

[0009] If a RRC connected UE declares radio link failure it creates a Radio Link Failure report and network can fetch it from the UE. In a RLF report, UE includes necessary information and measurements for the network to analyze the radio condition and possibly physical location of the UE. Network thus can take appropriate action upon analyzing the RLF report. Thereare multiple scenarios where UE may declare radio link failure; details can be found in TS 38.300 version 18.0.0 and TS 38.331 version 18.0.0.

[0010] A UE operating in dual connectivity may encounter problems in the Secondary Cell Group (SCG) and declare failure on the SCG leg. If the connection to the Master Cell Group (MCG) leg is active, UE does not declare radio link failure, it sends a SCGFailureInformation message to the MN. Upon receiving the message, MN can take necessary actions to solve the problems.

[0011] Successful Handover Report (SHR) is generated by a UE performing a PCell handover if the conditions set by the network are fulfilled. Generation of SHR refers to UE being close to failure of the handover.

[0012] ########### START OF EXTRACT FROM 3GPP TS 38.300 version 18.0.0 ###########

[0013] 15.5.2.7 Successful HO

[0014] One of the functions of Mobility Robustness Optimization is to detect a suboptimal successful handover event. The aim is to identify underlying conditions during successful ordinary handovers, successful DAPS handovers, or successful Conditional handovers.

[0015] For analysis of successful handover, the UE may collect Successful Handover Report (SHR) based on configuration by network, if stored, and makes the SHR available to the network as specified in TS 38.331

[0012] , The UE stores the SHR until it is fetched by the network or for 48 hours after the SHR is recorded.

[0016] For SHR collected during intra-NR handover, if the target NR node fetches the SHR from the UE and the trigger of SHR is T310 / T312, it may forward the information to the source NR node, i.e. the node handling the cell reported as source cell in this SHR, by using the ACCESS AND MOBILITY INDICATION message over Xn or by means of the Uplink RAN configuration transfer procedure and Downlink RAN configuration transfer procedure over NG.

[0017] If the NG-RAN node that fetches the SHR from the UE is neither the source node nor the target node of the handover, it forwards the information to the node(s) which configured the SHR trigger causing the SHR to be generated, by using the ACCESS AND MOBILITY INDICATION message overXn or by means of the Uplink RAN configuration transfer procedure and Downlink RAN configuration transfer procedure over NG.In case of failure shortly after successful Handover, the same mobility event may generate both a SHR and a RLF report. In this case, the node(s), which configured the SHR trigger causing the SHR, may take the duplication into account e.g. ignore the SHR.

[0018] Upon retrieval of an SHR, the receiving node may analyse whether its mobility configuration needs adjustment.

[0019] The SHR report can be used to detect one case of Intra-system Too Late Handover, namely when DAPS HO is configured but an RLF is detected in the source cell during a successful DAPS HO.

[0020] ############ END OF EXTRACT FROM 3GPP TS 38.300 version 18.0.0 ############

[0021] The triggering conditions for the generation of the SHR can be configured by the source cell (before the HO execution), or by the target cell (in the HO command):

[0022] • Elapsed T304 above configured T304 threshold (condition configured by the target cell)

[0023] • Elapsed T310 above configured T310 threshold (condition configured by the source cell)

[0024] • Elapsed T312 above configured T312 threshold (condition configured by the source cell)

[0025] • RLF in source cell during DAPS HO (condition configured by the source cell)

[0026] Generated SHRs are stored in the UE variable VarSuccessHO-Report, which is defined by the following ASN.1 code in version 18.4.0 of 3GPP TS 38.331.

[0027] — ASN1START

[0028] — TAG-VARSUCCESSPSCELL-Report-START

[0029] VarSuccessPSCell-Report-rl8:: = SEQUENCE { successPSCell-Report-rl8 SuccessPSCell-Report-rl8, identityList-rl8 CHOICE { plmn-IdentityList-rl8 PLMN-IdentityList2-rl6, snpn-IdentityList-rl8 SEQUENCE (SIZE (1..maxNPN-rl6) ) OF SNPN-Identity-rl8 }

[0030]

[0031] — TAG-VARSUCCESSPSCELL-Report-STOP

[0032] — ASN1STOP

[0033] Mobility Robustness Optimisation in Self-Organized Network (SON)

[0034] Mobility Robustness Optimisation aims at detecting and enabling correction of following problems:

[0035] - Connection failure due to intra-system or inter-system mobility;- Inter-system Unnecessary HO (too early inter-system HO from NR to E-UTRAN with no radio link failure);

[0036] - Inter-system HO ping-pong;

[0037] - PSCell change failure;

[0038] - Inter-system voice fallback failure;

[0039] - Fast MCG recovery failure.

[0040] MRO provides means to distinguish the above problems from NR coverage related problems and other problems, not related to mobility.

[0041] For detection of sub-optimal successful handovers, MRO additionally enables observability of:

[0042] - Successful HO due to intra-NR mobility;

[0043] - Successful HO due to inter-RAT mobility.

[0044] For detection of a sub-optimal successful PSCell addition / change, MRO additionally enables observability of:

[0045] - Successful PSCell addition / change.

[0046] MRO reports and LTM

[0047] One of the main objectives of the SON / MDT enhancement Wl in Rel-19 WID [RP-234038] is to enhance the MRO features to optimize the LTM cell switch procedure.

[0048] MRO enhancement for R18 mobility mechanisms, including, Lower layer triggered mobility (LTM), CHO with candidate SCGs, subsequent CPAC [RAN3, RAN2]:

[0049] o Specification of the inter-node information exchange, including possible enhancements to interfaces [RAN3]

[0050] o Identify and specify necessary UE reporting to enhance the mobility parameter tuning [RAN2]

[0051] There currently exist certain challenge(s). For example, a problem is related to the determination of whether to generate an SHR and the generation of an SHR in a UE, in combination with the network’s retrieval of an SHR from the UE.

[0052] The following is an extract from section 5.3.5.3 (titled “Reception of an RRCReconfiguration by the UE”) in 3GPP TS 38.331 version 18.4.0 (parts of special interest are indicated by underlined text).####### Start of extract from section 5.3.5.3 in 3GPP TS 38.331 version 18.4.0 ######

[0053] The UE shall perform the following actions upon reception of the RRCReconfiguration, upon execution of the conditional reconfiguration (CHO, CPA, CPC, or subsequent CP AC), or upon execution of an LTM cell switch:

[0054] < Omitted text>

[0055] 2> if the RRCReconfiguration includes the reconfigurationWithSync in spCellConfig of an MCG:

[0056] 3 > if the UE has logged measurements available for NR and if the RPLMN is included in plmn- IdentityList stored in VarLogMeasReport, or

[0057] 3 > if the UE has logged measurements available for NR and if the current registered SNPN identity is included in snpn-ConfigID-List stored in the VarLogMeasReport.

[0058] 4> include the logMeasAvailable in the RRCReconfigurationComplete message;

[0059] 4> if Bluetooth measurement results are included in the logged measurements the UE has available for NR:

[0060] 5> include the logMeasAvailableBT in the RRCReconfigurationComplete message;

[0061] 4> if WLAN measurement results are included in the logged measurements the UE has available for NR:

[0062] 5> include the logMeasAvailableWLAN in the RRCReconfigurationComplete message;

[0063] 3> if the sigLoggedMeasType in VarLogMeasReport is included; or

[0064] 3> if the UE supports the override protection of the signalling based logged MDT for inter-RAT (i.e. LTE to NR), and if the sigLoggedMeasType in VarLogMeasReport of TS 36.331

[0010] is included: 4> if T330 timer is running (associated to the logged measurement configuration for NR or for LTE):

[0065] 5> set sigLogMeasConfigAvailable to true in the RRCReconfigurationComplete message; 4> else:

[0066] 5> if the UE has logged measurements in VarLogMeasReport or in VarLogMeasReport of TS 36.331

[0010] :

[0067] 6> set sigLogMeasConfigAvailable to false in the RRCReconfigurationComplete message; 3 > if the UE has connection establishment failure or connection resume failure information available in VarConnEstFailReport or VarConnEstFailReportList and if the RPLMN is equal to plmn- Identity stored in VarConnEstFailReport or in at least one of the entries of VarConnEstFailReportList, or

[0068] 3> if the UE has connection establishment failure information or connection resume failure information available in VarConnEstFailReport or VarConnEstFailReportList and if the registered SNPN identity is equal to snpn-Identity in networkidentity stored in VarConnEstFailReport or any entry of VarConnEstFailReportList.4> include connEstFailInfoAvailable in the RRCReconfigurationComplete message;

[0069] 3> if the UE has radio link failure or handover failure information available in VarRLF-Report and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report, or

[0070] 3> if the UE has radio link failure or handover failure information available in VarRLF-Report of TS 36.331

[0010] and if the UE is capable of cross-RAT RLF reporting and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report of TS 36.331

[0010] ; or

[0071] 3> if the UE has radio link failure or handover failure information available in VarRLF-Report and if the current registered SNPN identity is included in snpn-IdentityList stored in VarRLF-Report.

[0072] 4> include rlf-InfoAvailable in the RRCReconfigurationComplete message;

[0073] 3> if the UE was configured with successHO-Config when connected to the source PCell:

[0074] 4> if the applied RRCReconfiguration is not due to a conditional reconfiguration execution upon cell selection performed while timer T311 was running, as defined in 5.3.7.3; or 4> if the applied RRCReconfiguration is not received when T316 was running:

[0075] 5> perform the actions for the successful handover report determination as specified in clause 5.7.10.6, upon successfully completing the Random Access procedure triggered for the reconfigurationWithSync in spCellConfig of the MCG;

[0076] 4> if applied RRCReconfiguration is received when T316 was running:

[0077] 5> release successHO-Config configured by the source PCell and thresholdPercentageT304 if configured by the target PCell;

[0078] 3> if the UE has successful handover information available in VarSuccessHO-Report and if the RPLMN is included in plmn-IdentityList stored in VarSuccessHO-Report, or

[0079] 3> if the UE has successful handover information available in VarSuccessHO-Report and if the current registered SNPN identity is included in snpn-IdentityList stored in the VarSuccessHO- Report.

[0080] 4> include successHO-InfoAvailable in the RRCReconfigurationComplete message;

[0081] 3> release successPSCell-Config configured by the source PCell, if available;

[0082] 3> if the UE has successful PSCell change or addition information available in VarSuccessPSCell- Report and if the RPLMN is included in plmn-IdentityList stored in VarSuccessPSCell-Report, or 3> if the UE has successful PSCell change or addition information available in VarSuccessPSCell- Report and if the current registered SNPN identity is included in snpn-IdentityList stored in the VarSuccessPSCell-Report.

[0083] 4> include successPSCell-InfoAvailable in the RRCReconfigurationComplete message;

[0084] < Omitted text>

[0085] > if reconfigurationWithSync was included in spCellConfig of an MCG or SCG and when MAC of an NR cell group successfully completes a Random Access procedure triggered above; or,1> if sl-PathSwitchConfig was included in reconfigurationWithSync included in spCellConfig of an MCG, and when successfully sending RRCReconfigurationComplete message (i.e., PC5 RLC acknowledgement is received from target L2 U2N Relay UE); or,

[0086] 1> if rach-LessHO was included in reconfigurationWithSync included in spCellConfig of an MCG, and upon indication from lower layers that the RACH-less handover has been successfully completed; or, 1> if reconfigurationWithSync was included in spCellConfig of an MCG or SCG and the RRCReconfiguration message is applied due to an LTM cell switch execution and upon an indication from lower layer that the LTM cell switch execution has been successfully completed:

[0087] 2> stop timer T304 for that cell group if running;

[0088] < Omitted text>

[0089] ######## End of extract from section 5.3.5.3 in 3GPP TS 38.331 version 18.4.0 #######

[0090] As can be seen from the highlighted underlined text above, section 5.7.10.6 is referenced, and the logic in that section is executed if the UE was configured with successHO-Config when connected to the source PCell. This is because the UE undergoing a mobility procedure should evaluate if it should generate an SHR and, if so, generate and store this SHR, as well as indicate its availability to the network by including successHO-InfoAvailable in the RRCReconfigurationComplete message.

[0091] The following is an extract from section 5.7.10.6 (titled “Actions for the successful handover report determination”) in 3GPP TS 38.331 version 18.4.0 (parts of special interest are indicated by underlined text).

[0092] ####### Start of extract from section 5.7.10.6 in 3GPP TS 38.331 version 18.4.0 ######

[0093] The UE shall for the PCell:

[0094] 1> if the procedure is triggered due to successful completion of reconfiguration with sync, and 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 RRCReconfiguration message including the reconfigurationWithSync, is greater than threshold? ercentageT 304 if included in the successHO-Config received before executing the last reconfiguration with sync; or

[0095] 1> if the procedure is triggered due to successful completion of reconfiguration with sync, and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT310 included in the successHO-Config if configured by the source PCell before executing the last reconfiguration with sync; or

[0096] 1> if the procedure is triggered due to successful completion of reconfiguration with sync, and if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the reconfiguration with sync procedure and if the ratio between the value of the elapsedtime of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312 included in the successHO-Config if configured by the source PCell before executing the last reconfiguration with sync; or

[0097] 1> if the procedure is triggered due to successful completion of reconfiguration with sync, and if sourceDAPS-FailureReporting is included in the successHO-Config 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; or:

[0098] 1> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PCell before executing the last Mobility from NR to E-UTRA, is greater than thresholdPercentageT310 included in the successHO-Config if configured by the source PCell before executing the last Mobility from NR to E-UTRA; or

[0099] 1> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, and if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the Mobility from NR to E-UTRA 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 Mobility from NR to E-UTRA, is greater than thresholdPercentageT312 included in the successHO-Config if configured by the source PCell before executing the last Mobility from NR to E-UTRA:

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

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

[0102] < Omitted text about setting of the content of the SHR>

[0103] 1> release successHO-Config configured by the source PCell and thresholdPercentageT304 if configured by the target PCell.

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

[0105] ####### End of extract from section 5.7.10.6 in 3GPP TS 38.331 version 18.4.0 #######

[0106] The essence of the problem can be seen when analyzing the highlighted parts of the above extracts from the RRC specification.

[0107] One problem stems from the fact that successHO-InfoAvailable, which indicates to the network (the gNB) that an SHR is available for retrieval in the UE, is supposed to be included in the RRCReconfigurationComplete message which indicates the completion of the mobility procedure. This means that the determination of whether the condition forgenerating an SHR is met has to be performed before the RRCReconfigurationComplete message is sent, but in principle, the mobility procedure is not fully concluded before the RRCReconfigurationComplete message is successfully transmitted.

[0108] As a result, in some cases the condition for generating an SHR is not met before the RRCReconfigurationComplete message is sent (and consequently no SHR is generated), but it is met after the successful transmission of the RRCReconfigurationComplete message. For instance, if the condition for generating an SHR is the condition related to the mobility supervision timer T304, the configured percentage threshold may not be exceeded before the transmission of the RRCReconfigurationComplete message, but subsequently, after an a priori unknown number of HARQ retransmissions of the RRCReconfigurationComplete message, the percentage threshold may have been exceeded and hence the condition for generating an SHR is met, but no SHR will be generated.

[0109] Contributing to the problem is also the fact that the SHR generation determination always -regardless of the outcome of the determination - follows a clearing of VarSuccessHO-Report, where any previously generated (but not yet retrieved by the network) is stored, i.e. any previously generated and stored SHR is discarded.

[0110] Delaying the SHR generation determination until after the transmission of the RRCReconfigurationComplete message is also problematic. If this determination results in that an SHR is generated and stored in VarSuccessHO-Report in the UE, this would result in:

[0111] 1. The network (gNB) will not be informed of the availability of the stored SHR in the RRCReconfigurationComplete message.

[0112] 2. The SHR, which the UE has generated and stored in VarSuccessHO-Report will be deleted in conjunction with the next mobility procedure, and unless the network has been informed of its availability and retrieved it from the UE in the meantime, the SHR is lost, potentially without the network even being aware that it ever existed.

[0113] Summary

[0114] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Examples of this disclosure provide a number of alternative solutions involving ways to modify the logic of the RRC procedures, to avoid or mitigate the problems described above. For example, examples of this disclosure propose modifications of the RRC procedure logic, e.g. ensuring that the SHR generation condition is evaluated after sending the RRCReconfigurationComplete message that concludes the mobility procedure.An example aspect of this disclosure provides a method performed by a wireless communication device for performing a mobility procedure. The method comprises performing a mobility procedure, and determining if at least one condition for generating a Successful Handover Report, SHR, has been met. The method also comprises, before sending, to a network node, a message indicating that the wireless communication device has performed the mobility procedure, if the at least one condition has been met, and the wireless communication device is storing a previous SHR, deleting the previous SHR, and if the at least one condition has not been met, and the wireless communication device is storing a previous SHR, maintaining the previous SHR.

[0115] Another example aspect of this disclosure provides a method performed by a wireless communication device for performing a mobility procedure. The method comprises performing a mobility procedure, and sending, to a network node, a message indicating that the wireless communication device has performed the mobility procedure. The method also comprises, after sending, to the network node, the message indicating that the wireless communication device has performed the mobility procedure, determining if at least one condition for generating a Successful Handover Report, SHR, has been met.

[0116] A further example aspect of this disclosure provides a tangible, non-transient computer-readable medium comprising instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations in a wireless communication device for performing a mobility procedure. The operations comprise performing a mobility procedure, and determining if at least one condition for generating a Successful Handover Report, SHR, has been met. The operations also comprise, before sending, to a network node, a message indicating that the wireless communication device has performed the mobility procedure, if the at least one condition has been met, and the wireless communication device is storing a previous SHR, deleting the previous SHR, and if the at least one condition has not been met, and the wireless communication device is storing a previous SHR, maintaining the previous SHR.

[0117] A still further example aspect of this disclosure provides a tangible, non-transient computer-readable medium comprising instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations in a wireless communication device for performing a mobility procedure. The operations comprise performing a mobility procedure, and sending, to a network node, a message indicating that the wireless communication device has performed the mobility procedure. The operations also comprise, after sending, to the network node, the message indicating that the wireless communication device hasperformed the mobility procedure, determining if at least one condition for generating a Successful Handover Report, SHR, has been met.

[0118] An additional example aspect of the present disclosure provides apparatus in a wireless communication device for performing a mobility procedure. The apparatus comprises processing circuitry and a memory. The apparatus is configured to perform a mobility procedure, and determine if at least one condition for generating a Successful Handover Report, SHR, has been met. The apparatus is also configured to, before sending, to a network node, a message indicating that the wireless communication device has performed the mobility procedure, if the at least one condition has been met, and the wireless communication device is storing a previous SHR, delete the previous SHR, and if the at least one condition has not been met, and the wireless communication device is storing a previous SHR, maintain the previous SHR.

[0119] Another example aspect of the present disclosure provides apparatus in a network node for receiving an indication from a wireless communication device. The apparatus comprises processing circuitry and a memory. The apparatus is configured to perform a mobility procedure, and send, to a network node, a message indicating that the wireless communication device has performed the mobility procedure. The apparatus is also configured to, after sending, to the network node, the message indicating that the wireless communication device has performed the mobility procedure, determine if at least one condition for generating a Successful Handover Report, SHR, has been met.

[0120] Certain embodiments may provide one or more of the following technical advantage(s). For example, examples of this disclosure may mitigate the problems described above, and ensures that the UE does not fail to generate an SHR when the SHR generation condition is fulfilled close to the conclusion of the mobility procedure (e.g. while HARQ retransmissions of the RRCReconfigurationComplete message that concludes the mobility procedure are ongoing).

[0121] Brief Description of the Drawings

[0122] For a better understanding of the embodiments of the present disclosure, and to show how it may be put into effect, reference will now be made, by way of example only, to the accompanying drawings, in which:

[0123] Figure 1 is a flow chart illustrating a method in accordance with some embodiments; Figure 2 is a flow chart illustrating a method in accordance with some embodiments;Figure 3 shows an example of a communication system in accordance with some embodiments;

[0124] Figure 4 shows an example of another communication system in accordance with some embodiments;

[0125] Figure 5 shows a wireless device in accordance with some embodiments;

[0126] Figure 6 shows a network node in accordance with some embodiments; and Figure 7 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.

[0127] Detailed Description

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

[0129] Figure 1 depicts a method 100 in accordance with particular embodiments, for example a method performed by a wireless communication device for performing a mobility procedure. The method 100 may be performed by a wireless device (e.g. UE QQ112, station QQ212 or wireless device QQ300 as described later with reference to Figures 3, 4 and 5 respectively).

[0130] The method 100 begins at step 102, comprising performing a mobility procedure. Step 104 comprises determining if at least one condition for generating a Successful Handover Report (SHR) has been met. Step 106 comprises, before sending, to a network node, a message indicating that the wireless communication device has performed the mobility procedure: if the at least one condition has been met, and the wireless communication device is storing a previous SHR, deleting the previous SHR; and if the at least one condition has not been met, and the wireless communication device is storing a previous SHR, maintaining the previous SHR.

[0131] Figure 2 depicts a method 200 in accordance with particular embodiments, for example a method performed by a wireless communication device for performing a mobility procedure. The method 200 may be performed by a wireless device (e.g. UE QQ112, station QQ212 or wireless device QQ300 as described later with reference to Figures 3, 4 and 5 respectively).

[0132] The method 200 begins at step 202, comprising performing a mobility procedure. Step 204 comprises sending, to a network node, a message indicating that the wireless communication device has performed the mobility procedure. Step 206 comprises, after sending, to the network node, the message indicating that the wireless communicationdevice has performed the mobility procedure, determining if at least one condition for generating a Successful Handover Report (SHR) has been met.

[0133] The following provides illustrative examples of this disclosure.

[0134] In examples of this disclosure, it is assumed that a UE generates an SHR and that UE logs an SHR are herein considered to be the same type of action. Further, examples are described as applied to 5G NR technology, but may potentially also be applicable, perhaps with some modification, to 6G or other wireless communication tehnologies..

[0135] This disclosure provides multiple alternative examples to address the problems described above.

[0136] Example 1

[0137] In this example, the determination of whether an SHR should be generated is separated from the clearing of the VarSuccessHO-Report variable, i.e. separated from the deletion of any previously stored SHR. The UE can thus check the SHR generation condition before sending the RRCReconfigurationComplete message without deleting any previously stored SHR if the UE determines that the condition for generating an SHR is not met. But if the UE at that point determines that the condition for generating an SHR is met, the UE will generate an SHR and store it in VarSuccessHO-Report, thereby overwriting any SHR that was previously stored in VarSuccessHO-Report. The UE will then also include the indication of SHR availability, i.e. successHO-InfoAvailable, in the RRCReconfigurationComplete message, but otherwise it will not.

[0138] This example further comprises that the UE, if the condition for SHR generation was not met before sending the RRCReconfigurationComplete message, can evaluate this condition a second time after sending the RRCReconfigurationComplete message. If the condition is met at this second evaluation, the UE generates an SHR and stores it in VarSuccessHO-Report. The UE will subsequently include successHO-InfoAvailable in the message the next time it sends either of an RRCReconfigurationComplete message, an RRCReestablishmentComplete message, an RRCResumeComplete message or an RRCSetupComplete message.

[0139] This example can be realized through the following example modifications of sections 5.3.5.3 and 5.7.10.6 in 3GPP TS 38.331 version 18.4.0 (additions indicated by underlined text, and deletions are indicated by strikethrough text).

[0140] ######## Start of specification text modified in accordance with Example 1 ########5.3.5.3 Reception of an RRCReconfiguration by the UE

[0141] The UE shall perform the following actions upon reception of the RRCReconfiguration, upon execution of the conditional reconfiguration (CHO, CPA, CPC, or subsequent CP AC), or upon execution of an LTM cell switch:

[0142] < Omitted text>

[0143] 2> if the RRCReconfiguration includes the reconfigurationWithSync in spCellConfig of an MCG:

[0144] 3 > if the UE has logged measurements available for NR and if the RPLMN is included in plmn- IdentityList stored in VarLogMeasReport, or

[0145] 3 > if the UE has logged measurements available for NR and if the current registered SNPN identity is included in snpn-ConfigID-List stored in the VarLogMeasReport.

[0146] 4> include the logMeasAvailable in the RRCReconfigurationComplete message;

[0147] 4> if Bluetooth measurement results are included in the logged measurements the UE has available for NR:

[0148] 5> include the logMeasAvailableBT in the RRCReconfigurationComplete message;

[0149] 4> if WLAN measurement results are included in the logged measurements the UE has available for NR:

[0150] 5> include the logMeasAvailableWLAN in the RRCReconfigurationComplete message;

[0151] 3> if the sigLoggedMeasType in VarLogMeasReport is included; or

[0152] 3> if the UE supports the override protection of the signalling based logged MDT for inter-RAT (i.e. LTE to NR), and if the sigLoggedMeasType in VarLogMeasReport of TS 36.331

[0010] is included: 4> if T330 timer is running (associated to the logged measurement configuration for NR or for LTE):

[0153] 5> set sigLogMeasConfigAvailable to true in the RRCReconfigurationComplete message; 4> else:

[0154] 5> if the UE has logged measurements in VarLogMeasReport or in VarLogMeasReport of TS 36.331

[0010] :

[0155] 6> set sigLogMeasConfigAvailable to false in the RRCReconfigurationComplete message; 3 > if the UE has connection establishment failure or connection resume failure information available in VarConnEstFailReport or VarConnEstFailReportList and if the RPLMN is equal to plmn- Identity stored in VarConnEstFailReport or in at least one of the entries of VarConnEstFailReportList, or

[0156] 3> if the UE has connection establishment failure information or connection resume failure information available in VarConnEstFailReport or VarConnEstFailReportList and if the registered SNPN identity is equal to snpn-Identity in networkidentity stored in VarConnEstFailReport or any entry of VarConnEstFailReportList.

[0157] 4> include connEstFaillnfoAvailable in the RRCReconfigurationComplete message;3> if the UE has radio link failure or handover failure information available in VarRLF-Report and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report, or

[0158] 3> if the UE has radio link failure or handover failure information available in VarRLF-Report of TS 36.331

[0010] and if the UE is capable of cross-RAT RLF reporting and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report of TS 36.331

[0010] ; or

[0159] 3> if the UE has radio link failure or handover failure information available in VarRLF-Report and if the current registered SNPN identity is included in snpn-IdentityList stored in VarRLF-Report. 4> include rlf-InfoAvailable in the RRCReconfigurationComplete message;

[0160] 3> if the UE was configured with successHO-Config when connected to the source PCell:

[0161] 4> if the applied RRCReconfiguration is not due to a conditional reconfiguration execution upon cell selection performed while timer T311 was running, as defined in 5.3.7.3; or 4> if the applied RRCReconfiguration is not received when T316 was running:

[0162] 5> perform the actions for the successful handover report determination as specified in clause 5.7.10.6, upon successfully completing the Random Access procedure triggered for the reconfigurationWithSync m spCellConfig of the MCG;

[0163] 4> if applied RRCReconfiguration is received when T316 was running:

[0164] 5> release successHO-Config configured by the source PCell and thresholdPercentageT304 if configured by the target PCell;

[0165] 3> if the UE has successful handover information available in VarSuccessHO-Report and if the RPLMN is included in plmn-IdentityList stored in VarSuccessHO-Report, or

[0166] 3> if the UE has successful handover information available in VarSuccessHO-Report and if the current registered SNPN identity is included in snpn-IdentityList stored in the VarSuccessHO- Report-. or

[0167] 3> if the UE has determined that the condition for generating a successful handover report is fulfilled:

[0168] 4> include successHO-InfoAvailable in the RRCReconfigurationComplete message;

[0169] 3> release successPSCell-Config configured by the source PCell, if available;

[0170] 3> if the UE has successful PSCell change or addition information available in VarSuccessPSCell- Report and if the RPLMN is included in plmn-IdentityList stored in VarSuccessPSCell-Report, or 3> if the UE has successful PSCell change or addition information available in VarSuccessPSCell- Report and if the current registered SNPN identity is included in snpn-IdentityList stored in the VarSuccessPSCell-Report.

[0171] 4> include successPSCell-InfoAvailable in the RRCReconfigurationComplete message;

[0172] < Omitted text>

[0173] > if reconfigurationWithSync was included in spCellConfig of an MCG or SCG and when MAC of an NR cell group successfully completes a Random Access procedure triggered above; or,1> if sl-PathSwitchConfig was included in reconfigurationWithSync included in spCellConfig of an MCG, and when successfully sending RRCReconfigurationComplete message (i.e., PC5 RLC acknowledgement is received from target L2 U2N Relay UE); or,

[0174] 1> if rach-LessHO was included in reconfigurationWithSync included in spCellConfig of an MCG, and upon indication from lower layers that the RACH-less handover has been successfully completed; or, 1> if reconfigurationWithSync was included in spCellConfig of an MCG or SCG and the RRCReconfiguration message is applied due to an LTM cell switch execution and upon an indication from lower layer that the LTM cell switch execution has been successfully completed:

[0175] 2> stop timer T304 for that cell group if running;

[0176] 2> if the UE has not determined that the condition for generating a successful handover report is fulfilled:

[0177] 3> perform the actions for the successful handover report determination as specified in clause 5,7.10.6;

[0178] 2> if the UE has determined that the condition for generating a successful handover report is fulfilled:

[0179] 3> perform the actions for generation of a successful handover report as specified in clause 5,7.10.6a; 2> release successHO-Config configured by the source PCell and thresholdPercentageT304 if configured by the target PCell.

[0180] < Omitted text>

[0181] 5.7.10.6 Actions for the successful handover report determination

[0182] The UE shall for the PCell:

[0183] 1> if the procedure is triggered due to successful completion of reconfiguration with sync, and 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 RRCReconfiguration message including the reconfigurationWithSync, is greater than thresholdPercentageT304 if included in the successHO-Config received before executing the last reconfiguration with sync; or

[0184] 1> if the procedure is triggered due to successful completion of reconfiguration with sync, and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT310 included in the successHO-Config if configured by the source PCell before executing the last reconfiguration with sync; or

[0185] 1> if the procedure is triggered due to successful completion of reconfiguration with sync, and if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the reconfiguration with sync procedure and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312 included in the successHO- Config if configured by the source PCell before executing the last reconfiguration with sync; or1> if the procedure is triggered due to successful completion of reconfiguration with sync, and if sourceDAPS-FailureReporting is included in the successHO-Config 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; or:

[0186] 1> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PCell before executing the last Mobility from NR to E-UTRA, is greater than thresholdPercentageT310 included in the successHO-Config if configured by the source PCell before executing the last Mobility from NR to E-UTRA; or

[0187] 1> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, and if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the Mobility from NR to E-UTRA 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 Mobility from NR to E-UTRA, is greater than thresholdPercentageT312 included in the successHO- Config if configured by the source PCell before executing the last Mobility from NR to E- UTRA:

[0188] 2> determine that the conditions for generating a successful handover report are fulfilled.

[0189] 5.7.10.6a Actions for generation of a successful handover report

[0190] The UE shall for the PCell:

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

[0192] 24> clear the information included in VarSuccessHO-Report, if any;

[0193] < Omitted text about setting of the content of the SHR>

[0194] 1> release successHO Config configured by the source PCell and thresholdPercentageT30 / ! if configured by the target PCell.

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

[0196] ######## End of specification text modified in accordance with Example 1 ########

[0197] In a variation of the above example realization, the modifications of the specification text may be written with the condition that they only apply when the mobility procedure (or thereconfiguration with sync procedure) is an LTM cell switch, while the unchanged logic is applied when the mobility procedure was another, legacy mobility procedure.

[0198] Example 2

[0199] In this example, the determination of whether the condition for generation an SHR is delayed until after sending of the RRCReconfigurationComplete message, and if the condition is determined to be fulfilled, the UE generates an SHR and stores it in VarSuccessHO-Report, the indication of its availability (indicated by successHO-InfoAvailable) will be included in the next RRCReconfigurationComplete message, RRCReestablishmentComplete message, RRCResumeComplete message or RRCSetupComplete message.

[0200] Example 3

[0201] In this example, the UE always includes an indication of SHR availability (successHO-InfoAvailable) in the RRCReconfigurationComplete message that concludes the mobility procedure (e.g. always indicates that a SHR is available), provided that it is configured to generate an SHR when the condition for this is fulfilled (i.e. the UE is configured with successHO-Config). Optionally, a further condition may be that the reconfiguration with sync concerns a RACH-less LTM cell switch (i.e. the full condition would be that the UE is configured with successHO-Config and the reconfiguration with sync concerns a RACH-less LTM cell switch.

[0202] The network knows that this is not a guarantee for an SHR to actually be stored in the UE, but may still opportunistically attempt to retrieve it.

[0203] An observation is that this SHR availability indication may in some examples only indicate that the UE is configured with successHO-Config, which the network may know anyway.

[0204] Additional value can however be added by adding the functionality that the UE includes the SHR availability indication (successHO-InfoAvailable) in the next RRCReconfigurationComplete message, RRCReestablishmentComplete message, RRCResumeComplete message or RRCSetupComplete message, only if an SHR is actually stored in VarSuccessHO-Report.

[0205] Example 4

[0206] In this example, a “preliminary evaluation of the condition for SHR generation” is introduced. This preliminary evaluation is done before sending the RRCReconfigurationComplete message that concludes the mobility procedure. If the preliminary evaluation outcome is thatthe condition for generating an SHR is fulfilled, the UE includes the indication of SHR availability in the RRCReconfigurationComplete message that concludes the mobility procedure. If the preliminary evaluation outcome is that the condition for generating an SHR is not fulfilled, as one option, the UE includes in the RRCReconfigurationComplete message an indication that the preliminary evaluation is that no SHR will be generated, or, as another option, the UE includes no indication in the RRCReconfigurationComplete message.

[0207] Unless the preliminary evaluation already concluded that the SHR generation condition was fulfilled, the UE performs a final evaluation of the SHR generation condition after sending the RRCReconfigurationComplete message that concludes the mobility procedure, and, if the final evaluation determines that the SHR generation condition is fulfilled, generates and stores an SHR (and indicates its availability in the next RRCReconfigurationComplete message, RRCReestablishmentComplete message, RRCResumeComplete message or RRCSetupComplete message).

[0208] Example 5

[0209] This example is similar to example 4, but adds that the UE may include more information related to its preliminary evaluation of the SHR generation condition in the RRCReconfigurationComplete message that concludes the mobility procedure.

[0210] As one possibility, the UE may include in the RRCReconfigurationComplete message a snapshot of the value of the running T304 timer, optionally only if the SHR generation condition is related to the T304 timer (i.e. thresholdPercentageT304 is configured in the UE). This snapshot may have the form of a percentage of the full run time or another indication of its value relative the condition threshold thresholdPercentageT304. Optionally, this information is included in the RRCReconfigurationComplete message only if the preliminary evaluation of the SHR generation condition is that the condition is fulfilled, or that it is likely to be fulfilled before the RRCReconfigurationComplete message is successfully transmitted to the network (gNB). As another option, the information is included in the RRCReconfigurationComplete message only if the preliminary evaluation is that it is not fulfilled at the time of the preliminary evaluation.

[0211] This information allows the network (gNB) to make a reasonably well-based estimate of whether the T304-based SHR generation condition was eventually fulfilled after the successful transmission of the RRCReconfigurationComplete message, e.g. based on the number of HARQ retransmissions, which the network can use when determining whether to request the UE to send the SHR.As a further option, if the UE includes the value of timer T304 (and / or its relation to the percentage threshold) in the RRCReconfigurationComplete message, the UE may also indicate in the RRCReconfigurationComplete message a timestamp indicating the time of the preliminary evaluation of the SHR generation condition or the time when the T304 timer had the indicated value or the time when the RRCReconfigurationComplete message was compiled. This timestamp allows the network (gNB) to calculate the value of timer T304 in the UE when the RRCReconfigurationComplete message is successfully received and / or its successful reception is confirmed to the UE (which is the time the UE will stop the T304 timer and compare its value with its associated percentage threshold).

[0212] Example 6

[0213] In this example, UE assistance information is extended for the UE to inform the network of its availability of an SHR report.

[0214] Whether the condition for generation an SHR is determined after successful completion of reconfiguration with sync, which in some case is after successful sending RRCReconfigurationComplete message. And if the condition is determined to be fulfilled, the UE generates an SHR and stores it in VarSuccessHO-Report, the indication of its availability will be included in UE assistance information, or possibly the next RRCReconfigurationComplete message, RRCReestablishmentComplete message, RRCResumeComplete message or RRCSetupComplete message.

[0215] A UE capable of indicating the availability of SHR report may initiate the UE Assistance Information procedure, if it was configured to do so, upon determining that an initial or updated SHR is available.

[0216] One example of the ASN.1 implementation is realized through the following example modifications based on 3GPP TS 38.331 version 18.4.0, with indicated by underlined text, and deletions indicated by strikethrough text.

[0217] UEAssistancelnf ormation-vl800-IEs SEQUENCE {

[0218] idc-FDM-Assistance-rl8 IDC-FDM-Assistance-rl8

[0219] OPTIONAL

[0220] idc-TDM-Assistance-rl8 IDC-TDM-Assistance-rl8

[0221] OPTIONAL

[0222] multiRx-PreferenceFR2-rl8 ENUMERATED {single, multiple }

[0223] OPTIONAL

[0224] musim-Assistance-vl800 MUSIM-Assistance-vl800

[0225] OPTIONAL

[0226] f lightPathlnf ©Available -r 18 ENUMERATED {true}

[0227] OPTIONALul-TrafficInfo-r18 UL-TrafficInfo-r18

[0228] OPTIONAL,

[0229] n3c-RelayUE-InfoList-rl8 SEQUENCE (SIZE (0..8) ) OF N3C-RelayUE-Inf o-rl8 OPTIONAL,

[0230] sl-PRS-UE-AssistanceInformationNR-r18 SL-PRS-UE-AssistanceInformationNR-r18 OPTIONAL,

[0231] nonCriticalExtension SEQUENCE { } UEAssistanceInformation-v1900-IEs OPTIONAL

[0232] }

[0233]

[0234] UEAssistanceInformation-v1900-IEs ::= SEQUENCE {

[0235] successHO-InfoAvailable-r19 ENUMERATED {true}

[0236] OPTIONAL,

[0237] nonCriticalExtension SEQUENCE { } OPTIONAL

[0238] }

[0239] Possible alternatives to the above examples

[0240] Any the above-described examples may be combined with an enhancement of the UE variable VarSuccessHO-Report, so that it can contain a list of SHRs, e.g. at least two SHR, instead of just one, and thus provide alternative examples of this disclosure. This will allow the UE to store a new SHR without deleting a previously generated SHR which is still stored in VarSuccessHO-Report, because the network has not retrieved it yet. With this extension, the UE would deliver all the SHRs stored in VarSuccessHO-Report, when the network (gNB) requests (in the UElnformationRequest RRC message) the UE to send the SHR(s) to the network (in the UElnformationResponse RRC message).

[0241] The following is an example of how this enhancement could be realized in ASN.1 code, with new code underlined, and removed code as strikethrough text.

[0242] — ASN1START

[0243] — TAG-VARSUCCESSHO-Report-START

[0244] VarSuccessHO-Report-r17 ::= SEQUENCE {

[0245] successHO-ReportList-r19 SEQUENCE (SIZE (1..maxSHR)) OF SuccessHO-Report-r17,successHO-Report-r17 SuccessHO-Report-r17,

[0246] identityList-rl8 CHOICE {

[0247] plmn-IdentityList-rl8 PLMN-IdentityList2-rl6,

[0248] snpn-IdentityList-rl8 SEQUENCE (SIZE (1..maxNPN-rl6) ) OF SNPN-Identity-rl8 }

[0249] }

[0250] — TAG-VARSUCCESSHO-Report-STOP

[0251] -- ASN1STOP

[0252] Figure 3 shows an example of a communication system QQ100 in accordance with some embodiments.

[0253] In the example, the communication system QQ100 includes a telecommunications network QQ102 that includes an access network QQ104, such as a radio access network (RAN), anda core network QQ106, which includes one or more core network nodes QQ108. The access network QQ104 includes one or more access network nodes or base stations of various types, access network nodes QQ110A and QQ110B are depicted (which may be collectively referred to as network nodes QQ110), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network QQ104 may include more than one access network technology. The network nodes QQ110 of access network QQ104 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs QQ112A, QQ112B, QQ112C, and QQ112D (one or more of which may be generally referred to as UEs QQ112) to the core network QQ106 over one or more wireless connections.

[0254] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network QQ102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network QQ102 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 network nodes to implement one or more functionalities of any network node in the telecommunications network QQ102, including one or more access network nodes QQ110 and / or core network nodes QQ108.

[0255] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN 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 network 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 0-2 interface defined by the O-RAN Alliance or comparable technologies.The network nodes QQ110 facilitate direct or indirect connection of one or more UEs QQ112 to the core network QQ106 over one or more wireless connections. 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 QQ100 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 QQ100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0256] The UEs QQ112 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 QQ110 and other communication devices. Similarly, the network nodes QQ108, QQ110 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network QQ102) with the UEs QQ112 and / or with other network nodes or equipment in the telecommunications network QQ102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network QQ102. More specifically, UEs QQ112 may send messages, data, and / or other signals to network nodes QQ108, QQ110 or other elements of the telecommunications network QQ102 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes QQ108, QQ110 may send messages, data, and other signals to UEs QQ1122, other network nodes QQ108, QQ110, and other devices in telecommunications network QQ102 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE QQ112 by transmitting the message to an access network node QQ110 that will then transmit the message to the intended UE QQ112. Similarly, a core network node 108 may receive a particular message from a UE QQ112 by receiving the message from an access network node QQ110 that itself received the message from the UE QQ112.

[0257] In the depicted example, the core network QQ106 connects elements of the access network QQ104 (e.g., one or more of the network nodes QQ110) to one or more host computing systems, such as host QQ116. These connections may be direct or indirect via one or moreintermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network QQ106 includes one or more core network nodes (e.g., core network node QQ108) of various types, one or more of which may be generally referred to as network nodes QQ108. Network nodes QQ108 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node QQ108. Example core network nodes provide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

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

[0259] As a whole, the communication system QQ100 of Figure 3 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system QQ100 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system QQ100 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all ofthe relevant rule sets or with different components or sub-systems within the communication system QQ100 supporting different standards, protocols, or rule sets.

[0260] As one example, in certain embodiments, access network QQ104 may contain some access network nodes QQ110 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes QQ110 support (or the same access network nodes QQ110 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network QQ102 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result, may include an access network 104 and / or a core network 106 that supports multiple different standard generations or may include multiple access networks 104 and / or multiple core networks 106 with individual networks 104, 106 supporting different standard generations.

[0261] Telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network QQ102. For example, the telecommunications network QQ102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

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

[0263] In the example, the hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112C and / or QQ112D) and network nodes (e.g., network node QQ110B). In some examples, the hub QQ114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs. As another example, the hub QQ114 may be a controller that sends commands or instructions to one or more actuators inthe UEs. Commands or instructions may be received from the UEs, network nodes QQ110, or by executable code, script, process, or other instructions in the hub QQ114.

[0264] As another example, the hub QQ114 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 QQ114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0265] The hub QQ114 may have a constant / persistent or intermittent connection to the network node QQ110B. The hub QQ114 may also allow for a different communication scheme and / or schedule between the hub QQ114 and UEs (e.g., UE QQ112C and / or QQ112D), and between the hub QQ114 and the core network QQ106. In other examples, the hub QQ114 is connected to the core network QQ106 and / or one or more UEs via a wired connection.

[0266] Moreover, the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection. In some embodiments, the hub QQ114 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 QQ110B. In other embodiments, the hub QQ114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node QQ110B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0267] Figure 4 is another example of a communication system QQ200 according to some embodiments. As used herein, the communication system QQ200 includes multiple access points (APs) QQ210 (with four exemplary APs QQ210A, QQ210B, QQ210C, and QQ210D being depicted) and multiple wireless devices, referred to in the context of communication system QQ200 as stations (STAs) QQ212 (referred to individually as STA QQ212A, STA QQ212B, STA QQ212C, STA QQ212D, and STA QQ212E). STA QQ212A is served by AP QQ210A in a first basic service set (BSS) QQ220A. STA QQ210B and STA QQ210C are served by AP QQ210B in a second BSS, BSS QQ220B. STA QQ212D is served by AP QQ210C in a third BSS, BSS QQ220C. STA QQ212E is served by AP QQ210D in a fourthBSS, BSS QQ220D. Stations QQ212 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations QQ212 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0268] Each of STAs QQ212 may connect through a radio link to one of APs QQ210. For example, depending on location or channel conditions experienced by a given STA QQ212, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.

[0269] Each AP QQ210 may provide data connectivity to STAs QQ212 connected to a particular AP QQ210. As illustrated, APs QQ210 may be connected to a data network QQ230. In this way, APs QQ210 may also provide data connectivity between STAs QQ212 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA QQ212 and its serving AP QQ210 may be used for providing various kinds of services to STA QQ212, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA QQ212 and / or on a device linked to STA QQ212. By way of example, Figure 4 illustrates an application service platform QQ232 provided in data network QQ230. The application(s) executed on STA QQ212 and / or on one or more other devices linked to STA QQ212 may use the radio link for data communication with one or more other STA QQ212 and / or the application service platform QQ232, thereby enabling utilization of the corresponding service(s) at STA QQ212.

[0270] Figure 5 shows a wireless device QQ300, which may be configured to operate in communication system QQ100 of Figure 3 or in communication system QQ200 of Figure 4. The wireless device QQ300 may be alternatively referred to as a UE QQ300, like a UE QQ112 within the context of communication system QQ100, or as a station (STA) QQ300 or as a non-access-point station (non-AP STA) QQ300, like a STA QQ212 within the context of the communication system QQ200, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of awireless device include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage 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, and wireless terminal. Other examples include any type of 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.

[0271] A wireless device QQ300 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, wireless device QQ300 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device QQ300 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, wireless device QQ300 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).

[0272] In particular embodiments, wireless device QQ300 includes processing circuitry QQ302 that is operatively coupled via a bus QQ304 to an input / output interface QQ306, a power source QQ308, a memory QQ310, a communication interface QQ312, and / or any other component, or any combination thereof. Certain embodiments of wireless device QQ300 may include all or a subset of the components shown in Figure 5. The level of integration between the components may vary from one embodiment of wireless device QQ300 to another. In general, in a particular embodiment of wireless device QQ300, processing circuitry QQ302, input / output interface QQ306, power source QQ308, memory QQ310, and communication interface QQ312 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device QQ300.

[0273] Further, certain embodiments of wireless devices QQ300 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0274] The processing circuitry QQ302 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructionsstored as machine-readable computer programs in the memory QQ310. The processing circuitry QQ302 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 QQ302 may include multiple central processing units (CPUs). The processing circuitry QQ302 may be configured to cause the wireless device QQ300 to perform the methods as described with reference to Figure 1 and / or 2.

[0275] In the example, the input / output interface QQ306 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 wireless device QQ300. 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.

[0276] In some embodiments, the power source QQ308 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 to supply power to circuitry or to charge an associated battery. The power source QQ308 may further include power circuitry for delivering power from the power source QQ308 itself, and / or an external power source, to the various parts of wireless device QQ300 via input circuitry or an interface such as an electrical power cable. Power source QQ308 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device QQ300 to which power is supplied.

[0277] The memory QQ310 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 QQ310 includes one or more programs QQ314, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data QQ316. The memory QQ310 may store, for use by wireless device QQ300, any of a variety of various operating systems or combinations of operating systems.

[0278] The memory QQ310 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory QQ310 may allow wireless device QQ300 to access instructions, programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory QQ310, which may be or comprise a device-readable storage medium.

[0279] The processing circuitry QQ302 may be configured to communicate with an access network or other network via or using the communication interface QQ312. The communication interface QQ312 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna QQ322. The communication interface QQ312 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 wireless device or a network node in an access network). Each transceiver may include a transmitter QQ318 and / or a receiver QQ320 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter QQ318 and receiver QQ320 may be coupled to one or more antennas (e.g., antenna QQ322) and may share circuit components, software or firmware, or alternatively be implemented separately.In the illustrated embodiment, communication functions of the communication interface QQ312 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0280] In particular embodiments, wireless device QQ300 may provide an output of data captured via a sensor, through its communication interface QQ312, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device QQ300 can be communicated through a wireless connection to a network node via another wireless device QQ300. In particular embodiments, such 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).

[0281] As another example, wireless device QQ300 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, wireless device QQ300 may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0282] Wireless device QQ300, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, anelectrical 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 smartwatch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. In particular embodiments, wireless device QQ300 represents an loT device that comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the example embodiment of wireless device QQ300 shown in Figure 5.

[0283] As yet another specific example, in an loT scenario, wireless device QQ300 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 wireless device and / or a network node. Wireless device QQ300 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, wireless device QQ300 may implement the 3GPP NB-loT standard. In other scenarios, wireless device QQ300 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.

[0284] In practice, any number of wireless devices QQ300 may be used together with respect to a single use case. For example, a first wireless device QQ300 might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second wireless device QQ300 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device QQ300 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 wireless device QQ300 can also include more than one of the functionalities described above. For example, wireless device QQ300 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0285] Figure 6 shows a network node QQ400 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunications network. In accordance with respective embodiments, network node QQ400 may be configured to operate in communication system QQ100 of Figure 3, like network nodes QQ108 or QQ110, or in communication system QQ200 of Figure 4, likean AP QQ210 or a station QQ212. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0286] Network nodes QQ400 may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Network node QQ400 may be a relay node or a relay donor node controlling a relay. Network nodes QQ400 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0287] Other examples of network nodes QQ400 include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O& M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0288] In particular embodiments, network node QQ400 includes a processing circuitry QQ402, a memory QQ404, a communication interface QQ406, and a power source QQ408. In general, in a particular embodiment of network node QQ400, processing circuitry QQ402, memory QQ404, communication interface QQ406, and power source QQ408 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node QQ400.

[0289] The network node QQ400 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node QQ400 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair,may in some instances be considered a single separate network node. In some embodiments, the network node QQ400 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories QQ404 or portions of memory QQ404 for different RATs) and some components may be reused (e.g., a same antenna QQ410 may be shared by different RATs). The network node QQ400 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ400, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ400.

[0290] The processing circuitry QQ402 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other components, such as the memory QQ404, to provide network node QQ400 functionality.

[0291] In some embodiments, the processing circuitry QQ402 includes a system on a chip (SOC). In some embodiments, the processing circuitry QQ402 includes one or more of radio frequency (RF) transceiver circuitry QQ412 and baseband processing circuitry QQ414. In some embodiments, the RF transceiver circuitry QQ412 and the baseband processing circuitry QQ414 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry QQ412 and baseband processing circuitry QQ414 may be on the same chip or set of chips, boards, or units.

[0292] The memory QQ404 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry QQ402. The memory QQ404 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by theprocessing circuitry QQ402 and utilized by the network node QQ400. The memory QQ404 may be used to store any calculations made by the processing circuitry QQ402 and / or any data received via the communication interface QQ406. In some embodiments, the processing circuitry QQ402 and memory QQ404 is integrated.

[0293] The communication interface QQ406 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface QQ406 comprises port(s) / terminal(s) QQ416 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node QQ300 may be capable of wireless communication and communication interface QQ406 may also include radio front-end circuitry QQ418 that may be coupled to, or in certain embodiments a part of, an antenna QQ410. Particular embodiments of radio front-end circuitry QQ418 include filter(s) QQ420 and amplifier(s) QQ422. The radio front-end circuitry QQ418 may be connected to an antenna QQ410 and processing circuitry QQ402. The radio front-end circuitry may be configured to condition signals communicated between antenna QQ410 and processing circuitry QQ402. The radio front-end circuitry QQ418 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry QQ418 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters QQ420 and / or amplifiers QQ422. The radio signal(s) may then be transmitted via the antenna QQ410. Similarly, when receiving data, the antenna QQ410 may collect radio signals which are then converted into digital data by the radio front-end circuitry QQ418. The digital data may be passed to the processing circuitry QQ402. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0294] In certain alternative embodiments, network node QQ400 may be capable of wireless communication but does not include separate radio front-end circuitry QQ418, instead, the processing circuitry QQ402 includes radio front-end circuitry and is connected to the antenna QQ410. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ412 is part of the communication interface QQ406. In still other embodiments, the communication interface QQ406 includes one or more ports or terminals QQ416, the radio front-end circuitry QQ418, and the RF transceiver circuitry QQ412, as part of a radio unit (not shown), and the communication interface QQ406 communicates with the baseband processing circuitry QQ414, which is part of a digital unit (not shown).

[0295] The antenna QQ410 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna QQ410 may be coupled to the radio front-end circuitry QQ418 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna QQ410 is separate from the network node QQ400 and connectable to the network node QQ400 through one or more interfaces or ports.

[0296] The antenna QQ410, communication interface QQ406, and / or the processing circuitry QQ402 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node QQ400. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna QQ410, the communication interface QQ406, and / or the processing circuitry QQ402 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node QQ400. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0297] The power source QQ408 provides power to the various components of network node QQ400 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source QQ408 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ400 with power for performing the functionality described herein. For example, the network node QQ400 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source QQ408. As a further example, the power source QQ408 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0298] Embodiments of the network node QQ400 may include additional components beyond those shown in Figure 6 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node QQ400 may include user interface equipment to allow input of information into the network node QQ400 and to allow output of information from the network node QQ400. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ400.

[0299] Figure 7 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized. In the present context,virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments QQ500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment QQ500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

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

[0301] Hardware QQ504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM QQ508A and VM QQ508B (which may be collectively referred to as VMs QQ508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to one or more of the VMs QQ508.

[0302] The VMs QQ508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer QQ506. Different embodiments of the instance of a virtual appliance QQ502 may be implemented on one or more of VMs QQ508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.In the context of NFV, each of the VMs QQ508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs QQ508, and that part of hardware QQ504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more of the VMs QQ508 on top of the hardware QQ504 and corresponds to an application QQ502.

[0303] Hardware QQ504 may be implemented in a standalone network node with generic or specific components. Hardware QQ504 may implement some functions via virtualization. Alternatively, hardware QQ504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration QQ510, which, among others, oversees lifecycle management of applications QQ502. In some embodiments, hardware QQ504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system QQ512 which may alternatively be used for communication between hardware nodes and radio units.

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

[0305] Examples of this disclosure include the following enumerated embodiments.

[0306] Group A Embodiments

[0307] 1. A method performed by a wireless communication device for performing a mobility procedure, the method comprising:

[0308] performing a mobility procedure;

[0309] determining if at least one condition for generating a Successful Handover Report (SHR) has been met;

[0310] before sending, to a network node, a message indicating that the wireless communication device has performed the mobility procedure:

[0311] if the at least one condition has been met, and the wireless communication device is storing a previous SHR, deleting the previous SHR; and

[0312] if the at least one condition has not been met, and the wireless communication device is storing a previous SHR, maintaining the previous SHR.

[0313] 2. The method of embodiment 1, comprising sending, to the network node, the message indicating that the wireless communication device has performed the mobility procedure.

[0314] 3. The method of embodiment 2, wherein the message indicating that the wireless communication device has performed the mobility procedure comprises a Radio Resource Control (RRC) Reconfiguration Complete message.

[0315] 4. The method of embodiment 2 or 3, comprising, if the at least one condition has been met, including, in the message indicating that the wireless communication device has performed the mobility procedure, an indication that the at least one condition has been met and / or a SHR is available.

[0316] 5. The method of embodiment 4, wherein the indication that the at least one condition has been met and / or a SHR is available comprises a successHO-InfoAvailable Information Element (IE).6. The method of any of embodiments 2 to 5, comprising, the at least one condition has not been met, including, in the message indicating that the wireless communication device has performed the mobility procedure, an indication that the at least one condition has not been met and / or a SHR is not available.

[0317] 7. The method of any of embodiments 1 to 6, wherein maintaining the previous SHR comprises keeping, storing and / or refraining from deleting the previous SHR.

[0318] 8. The method of any of embodiments 1 to 7, comprising, if the at least one condition has been met, generating and / or storing the SHR.

[0319] 9. The method of any of embodiments 1 to 8, comprising, if the at least one condition has not been met, redetermining if the at least one condition for generating the SHR has been met after sending, to the network node, the message indicating that the wireless communication device has performed the mobility procedure.

[0320] 10. The method of embodiment 9, comprising, if the redetermining determines that the at least one condition for generating the SHR has been met, sending, to the network node in a further message, a further indication that the at least one condition has been met and / or a SHR is available.

[0321] 11. The method of embodiment 10, wherein the further indication that the at least one condition has been met and / or a SHR is available comprises a successHO-InfoAvailable Information Element (IE).

[0322] 12. The method of embodiment 10 or 11, wherein the further message comprises a RRC Reconfiguration Complete, RRC Reestablishment Complete, RRC Resume Complete, RRC Setup Complete or UE Assistance Information (UAI) message.

[0323] 13. The method of any of embodiments 1 to 12, wherein determining if the at least one condition for generating the SHR has been met comprises performing a preliminary evaluation of the at least one condition.

[0324] 14. The method of embodiment 13, comprising sending, to the network node, the message indicating that the wireless communication device has performed the mobility procedure.15. The method of embodiment 14, wherein the message indicating that the wireless communication device has performed the mobility procedure comprises a Radio Resource Control (RRC) Reconfiguration Complete message.

[0325] 16. The method of any of embodiments 13 to 15, comprising, if the preliminary evaluation indicates that the at least one condition has been met, including, in the message indicating that the wireless communication device has performed the mobility procedure, an indication that the preliminary evaluation indicates that the at least one condition has been met and / or a SHR is available.

[0326] 17. The method of embodiment 16, wherein the indication that the preliminary evaluation indicates that the at least one condition has been met and / or a SHR is available comprises a successHO-InfoAvailable Information Element (IE).

[0327] 18. The method of any of embodiments 13 to 17, comprising redetermining if the at least one condition for generating the SHR has been met after sending, to the network node, the message indicating that the wireless communication device has performed the mobility procedure.

[0328] 19. The method of embodiment 18, comprising, if the redetermining determines that the at least one condition for generating the SHR has been met, sending, to the network node in a further message, a further indication that the at least one condition has been met and / or a SHR is available.

[0329] 20. The method of embodiment 19, wherein the further indication that the at least one condition has been met and / or a SHR is available comprises a successHO-InfoAvailable Information Element (IE).

[0330] 21. The method of embodiment 19 or 20, wherein the further message comprises a RRC Reconfiguration Complete, RRC Reestablishment Complete, RRC Resume Complete, RRC Setup Complete or UE Assistance Information (UAI) message.

[0331] 22. The method of any of embodiments 13 to 21, comprising including, in the message indicating that the wireless communication device has performed the mobility procedure, information relating to the preliminary evaluation.

[0332] 23. The method of embodiment 22, wherein the information relating to the preliminary evaluation comprises one or more of:a value of a timer;

[0333] a remaining time on the timer;

[0334] a percentage of total time of the timer remaining on the timer;

[0335] a time at which the timer had the value;

[0336] a time at which the timer had the remaining time;

[0337] a time at which the timer had the percentage of the total time remaining on the timer; a time at which the preliminary evaluation was performed.

[0338] 24. The method of embodiment 23, wherein the timer comprises a T304 timer.

[0339] 25. The method of embodiment 23 or 24, wherein performing the preliminary evaluation of the at least one condition comprises determining whether, before the network node acknowledges the message indicating that the wireless communication device has performed the mobility procedure, the timer will expire, or will fall below a threshold remaining time, or a remaining time will fall below a threshold percentage of the total time of the timer.

[0340] 26. The method of any of embodiments 1 to 25, wherein the mobility procedure comprises a Reconfiguration with Sync procedure and / or a handover (HO) procedure.

[0341] 27. The method of any of embodiments 1 to 26, wherein the at least one condition includes a condition that the wireless communication device is configured to generate the SHR when the at least one condition has been met.

[0342] 28. The method of embodiment 27, wherein the wireless communication device is configured to generate the SHR when the wireless communication device is configured with successHO-ConFigure

[0343] 29. The method of any of embodiments 1 to 28, wherein sending, to the network node, the message indicating that the wireless communication device has performed the mobility procedure competes the mobility procedure.

[0344] 30. The method of any of embodiments 1 to 29, wherein the message indicating that the wireless communication device has performed the mobility procedure identifies a time that the wireless communication device determined if the at least one condition for generating the SHR has been met and / or a time that the wireless communication device generated the message indicating that the wireless communication device has performed the mobility procedure.31. The method of any of embodiments 1 to 30, wherein the network node comprises a base station, eNodeB or gNodeB.

[0345] 32. A method performed by a wireless communication device for performing a mobility procedure, the method comprising:

[0346] performing a mobility procedure;

[0347] sending, to a network node, a message indicating that the wireless communication device has performed the mobility procedure; and

[0348] after sending, to the network node, the message indicating that the wireless communication device has performed the mobility procedure, determining if at least one condition for generating a Successful Handover Report (SHR) has been met.

[0349] 33. The method of embodiment 32, wherein, if the at least one condition has not been met, and the wireless communication device is storing a previous SHR, maintaining the previous SHR.

[0350] 34. The method of embodiment 33, wherein maintaining the previous SHR comprises keeping, storing and / or refraining from deleting the previous SHR.

[0351] 35. The method of any of embodiments 32 to 34, wherein the message indicating that the wireless communication device has performed the mobility procedure comprises a Radio Resource Control (RRC) Reconfiguration Complete message.

[0352] 36. The method of any of embodiments 32 to 35, comprising including, in the message indicating that the wireless communication device has performed the mobility procedure, an indication that the at least one condition has been met and / or a SHR is available.

[0353] 37. The method of embodiment 36, wherein the indication that the at least one condition has been met and / or a SHR is available comprises a successHO-InfoAvailable Information Element (IE).

[0354] 38. The method of embodiment 36 or 37, wherein the at least one condition includes a condition that the mobility procedure comprises a RACH-less Layer 1 / Layer2 Triggered Mobility (LTM) cell switch.

[0355] 39. The method of any of embodiments 32 to 38, comprising, if the at least one condition has been met, generating and / or storing the SHR.40. The method of embodiment 39, comprising, if the at least one condition has been met, and the wireless communication device is storing a previous SHR:

[0356] deleting the previous SHR; or

[0357] including, in the message indicating that the wireless communication device has performed the mobility procedure, an indication that multiple SHRs are available at the wireless communication device.

[0358] 41. The method of any of embodiments 32 to 40, comprising, if the at least one condition for generating the SHR has been met, sending, to the network node in a further message, an indication that the at least one condition has been met and / or a SHR is available.

[0359] 42. The method of embodiment 41, wherein the indication that the at least one condition has been met and / or a SHR is available comprises a successHO-InfoAvailable Information Element (IE).

[0360] 43. The method of embodiment 41 or 42, wherein the further message comprises a RRC Reconfiguration Complete, RRC Reestablishment Complete, RRC Resume Complete, RRC Setup Complete or UE Assistance Information (UAI) message.

[0361] 44. The method of any of embodiments 32 to 43, wherein the mobility procedure comprises a Reconfiguration with Sync procedure and / or a handover (HO) procedure.

[0362] 45. The method of any of embodiments 32 to 44, wherein the at least one condition includes a condition that the wireless communication device is configured to generate the SHR when the at least one condition has been met.

[0363] 46. The method of embodiment 45, wherein the wireless communication device is configured to generate the SHR when the wireless communication device is configured with successHO-ConFigure

[0364] 47. The method of any of embodiments 32 to 46, wherein sending, to the network node, the message indicating that the wireless communication device has performed the mobility procedure competes the mobility procedure.

[0365] 48. The method of any of embodiments 32 to 47, wherein the message indicating that the wireless communication device has performed the mobility procedure identifies a time that the wireless communication device determined if the at least one condition for generating theSHR has been met and / or a time that the wireless communication device generated the message indicating that the wireless communication device has performed the mobility procedure.

[0366] 49. The method of any of embodiments 32 to 48, wherein the network node comprises a base station, eNodeB or gNodeB.

[0367] Group C Embodiments

[0368] 50. A wireless device (QQ112, QQ212, QQ300) for performing a mobility procedure, comprising:

[0369] processing circuitry (QQ302) configured to cause the wireless device to perform any of the operations of any of the Group A embodiments; and

[0370] a power source (QQ308) configured to supply power to the processing circuitry (QQ302).

[0371] 51. A wireless device for performing a mobility procedure, the wireless device comprising:

[0372] one or more antennas;

[0373] communication interface connected to the one or more antennas and to processing circuitry;

[0374] the processing circuitry being configured to cause the wireless device to perform any of the operations of any of the Group A embodiments;

[0375] an input interface connected to the processing circuitry and configured to allow input of information into the wireless device to be processed by the processing circuitry;

[0376] an output interface connected to the processing circuitry and configured to output information from the wireless device that has been processed by the processing circuitry; and

[0377] a power source connected to the processing circuitry and configured to supply power to the wireless device.

[0378] 52. A computer program product comprising a non-transitory computer-readable medium having computer-readable code embodied therein, the computer-readable code being configured such that, on execution by a suitable computer or processing circuitry, the computer or processing circuitry is caused to perform the method of any of the Group A embodiments.

[0379] 53. A wireless device (QQ112, QQ212, QQ300) configured to perform the method of any of the Group A embodiments.54. A wireless device (QQ112, QQ212, QQ300) comprising processing circuitry (QQ302) and a memory (QQ310), said memory containing instructions executable by said processing circuitry whereby said wireless device is operative to perform the method of any of the Group A embodiments.

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

Claims

Claims1. A method (100) performed by a wireless communication device for performing a mobility procedure, the method comprising:performing (102) a mobility procedure;determining (104) if at least one condition for generating a Successful Handover Report, SHR, has been met;before sending, to a network node, a message indicating that the wireless communication device has performed the mobility procedure:if the at least one condition has been met, and the wireless communication device is storing a previous SHR, deleting (106) the previous SHR; andif the at least one condition has not been met, and the wireless communication device is storing a previous SHR, maintaining (106) the previous SHR.

2. The method of claim 1, comprising sending, to the network node, the message indicating that the wireless communication device has performed the mobility procedure, and, if the at least one condition has been met, including, in the message indicating that the wireless communication device has performed the mobility procedure, an indication that the at least one condition has been met and / or a SHR is available.

3. The method of claim 2, comprising, if the at least one condition has not been met, including, in the message indicating that the wireless communication device has performed the mobility procedure, an indication that the at least one condition has not been met and / or a SHR is not available.

4. The method of any of claims 1 to 3, wherein maintaining (106) the previous SHR comprises keeping, storing and / or refraining from deleting the previous SHR.

5. The method of any of claims 1 to 4, comprising, if the at least one condition has been met, generating and / or storing the SHR.

6. The method of any of claims 1 to 5, comprising, if the at least one condition has not been met, redetermining if the at least one condition for generating the SHR has been met after sending, to the network node, the message indicating that the wireless communication device has performed the mobility procedure, and, if the redetermining determines that the at least one condition for generating the SHR has been met, sending, to the network node in afurther message, a further indication that the at least one condition has been met and / or a SHR is available.

7. The method of any of claims 1 to 6, wherein determining (104) if the at least one condition for generating the SHR has been met comprises performing a preliminary evaluation of the at least one condition.

8. The method of claim 7, comprising sending, to the network node, the message indicating that the wireless communication device has performed the mobility procedure, and, if the preliminary evaluation indicates that the at least one condition has been met, including, in the message indicating that the wireless communication device has performed the mobility procedure, an indication that the preliminary evaluation indicates that the at least one condition has been met and / or a SHR is available.

9. The method of claim 7 or 8, comprising redetermining if the at least one condition for generating the SHR has been met after sending, to the network node, the message indicating that the wireless communication device has performed the mobility procedure, and, if the redetermining determines that the at least one condition for generating the SHR has been met, sending, to the network node in a further message, a further indication that the at least one condition has been met and / or a SHR is available.

10. The method of any of claims 7 to 9, comprising including, in the message indicating that the wireless communication device has performed the mobility procedure, information relating to the preliminary evaluation.

11. The method of claim 10, wherein the information relating to the preliminary evaluation comprises one or more of:a value of a timer or a T304 timer;a remaining time on the timer or the T304 timer;a percentage of total time of the timer remaining on the timer or the T304 timer;a time at which the timer or the T304 timer had the value;a time at which the timer or the T304 timer had the remaining time;a time at which the timer or the T304 timer had the percentage of the total time remaining on the timer;a time at which the preliminary evaluation was performed.

12. The method of claim 11, wherein performing the preliminary evaluation of the at least one condition comprises determining whether, before the network node acknowledges themessage indicating that the wireless communication device has performed the mobility procedure, the timer will expire, or will fall below a threshold remaining time, or a remaining time will fall below a threshold percentage of the total time of the timer.

13. The method of any of claims 1 to 12, wherein the at least one condition includes a condition that the wireless communication device is configured to generate the SHR when the at least one condition has been met.

14. The method of any of claims 1 to 13, wherein the message indicating that the wireless communication device has performed the mobility procedure identifies a time that the wireless communication device determined if the at least one condition for generating the SHR has been met and / or a time that the wireless communication device generated the message indicating that the wireless communication device has performed the mobility procedure.

15. A method (200) performed by a wireless communication device for performing a mobility procedure, the method comprising:performing (202) a mobility procedure;sending (204), to a network node, a message indicating that the wireless communication device has performed the mobility procedure; andafter sending, to the network node, the message indicating that the wireless communication device has performed the mobility procedure, determining (206) if at least one condition for generating a Successful Handover Report, SHR, has been met.

16. The method of claim 15, wherein, if the at least one condition has not been met, and the wireless communication device is storing a previous SHR, maintaining, keeping, storing and / or refraining from deleting the previous SHR.

17. The method of claim 15 or 16, comprising including, in the message indicating that the wireless communication device has performed the mobility procedure, an indication that the at least one condition has been met and / or a SHR is available.

18. The method of claim 17, wherein the at least one condition includes a condition that the mobility procedure comprises a RACH-less Layer 1 / Layer2 Triggered Mobility, LTM, cell switch.

19. The method of any of claims 15 to 18, comprising, if the at least one condition has been met, generating and / or storing the SHR.

20. The method of claim 19, comprising, if the at least one condition has been met, and the wireless communication device is storing a previous SHR:deleting the previous SHR; orincluding, in the message indicating that the wireless communication device has performed the mobility procedure, an indication that multiple SHRs are available at the wireless communication device.

21. The method of any of claims 15 to 20, comprising, if the at least one condition for generating the SHR has been met, sending, to the network node in a further message, an indication that the at least one condition has been met and / or a SHR is available.

22. The method of any of claims 15 to 21, wherein the at least one condition includes a condition that the wireless communication device is configured to generate the SHR when the at least one condition has been met.

23. The method of any of claims 15 to 22, wherein sending (204), to the network node, the message indicating that the wireless communication device has performed the mobility procedure competes the mobility procedure.

24. The method of any of claims 15 to 23, wherein the message indicating that the wireless communication device has performed the mobility procedure identifies a time that the wireless communication device determined if the at least one condition for generating the SHR has been met and / or a time that the wireless communication device generated the message indicating that the wireless communication device has performed the mobility procedure.

25. A tangible, non-transient computer-readable medium comprising instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations in a wireless communication device for performing a mobility procedure, the operations comprising:performing (102) a mobility procedure;determining (104) if at least one condition for generating a Successful Handover Report, SHR, has been met;before sending, to a network node, a message indicating that the wireless communication device has performed the mobility procedure:if the at least one condition has been met, and the wireless communication device is storing a previous SHR, deleting (106) the previous SHR; andif the at least one condition has not been met, and the wireless communication device is storing a previous SHR, maintaining (106) the previous SHR.

26. The computer-readable medium of claim 25, comprising instructions that, when executed by processing circuitry, cause the processing circuitry to perform the method (100) of any of claims 2 to 14.

27. A tangible, non-transient computer-readable medium comprising instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations in a wireless communication device for performing a mobility procedure, the operations comprising:performing (202) a mobility procedure;sending (204), to a network node, a message indicating that the wireless communication device has performed the mobility procedure; andafter sending, to the network node, the message indicating that the wireless communication device has performed the mobility procedure, determining (206) if at least one condition for generating a Successful Handover Report, SHR, has been met.

28. The computer-readable medium of claim 27, comprising instructions that, when executed by processing circuitry, cause the processing circuitry to perform the method (200) of any of claims 16 to 24.

29. A computer-readable medium comprising instructions that, when executed by processing circuitry, cause the processing circuitry to carry out the method (100, 200) according to any of claims 1 to 24.

30. A computer program, comprising instructions that, when executed by processing circuitry, cause the processing circuitry to carry out the method (100, 200) according to any of claims 1 to 24.

31. A carrier containing the computer program of claim 30, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer-readable medium.

32. Apparatus in a wireless communication device for performing a mobility procedure, the apparatus comprising processing circuitry and a memory, the apparatus configured to: perform (102) a mobility procedure;determine (104) if at least one condition for generating a Successful Handover Report, SHR, has been met;before sending, to a network node, a message indicating that the wireless communication device has performed the mobility procedure:if the at least one condition has been met, and the wireless communication device is storing a previous SHR, delete (106) the previous SHR; andif the at least one condition has not been met, and the wireless communication device is storing a previous SHR, maintain (106) the previous SHR.

33. The apparatus of claim 32, wherein the apparatus is configured to perform the method (100) of any of claims 2 to 14.

34. Apparatus in a network node for receiving an indication from a wireless communication device, the apparatus comprising processing circuitry and a memory, the apparatus configured to:perform (202) a mobility procedure;send (204), to a network node, a message indicating that the wireless communication device has performed the mobility procedure; andafter sending, to the network node, the message indicating that the wireless communication device has performed the mobility procedure, determine (206) if at least one condition for generating a Successful Handover Report, SHR, has been met.

35. The apparatus of claim 34, wherein the apparatus is configured to perform the method (200) of any of claims 16 to 24.

Images