MRO-related enhancements for conditional handover

Abstract

A method, performed by a wireless communication device The method comprises triggering (302) a mobility-related report for a neighbouring cell (1008). The method further comprises transmitting (303) the mobility-related report to a network node without RRM measurements on the neighbouring cell. The mobility-related report comprises Conditional Hand-Over-related information.

Description

[0001] MRO-RELATED ENHANCEMENTS FOR CONDITIONAL HANDOVER

[0002] TECHNICAL FIELD

[0003] The embodiments herein relate to methods, a wireless communications device, and a network node for conditional handover. A corresponding computer program and a computer program carrier are also disclosed.

[0004] BAC}GROUND

[0005] In a typical wireless communication network, wireless devices, also known as wireless communication devices, mobile stations, stations (STA) and / or User Equipments (UE), communicate via a Local Area Network such as a Wi-Fi network or a Radio Access Network (RAN) to one or more core networks (CN). The RAN covers a geographical area which is divided into service areas or cell areas, which may also be referred to as a beam or a beam group, with each service area or cell area being served by a radio access node such as a radio access node e.g., a Wi-Fi access point or a radio base station (RBS), which in some networks may also be denoted, for example, a NodeB, eNodeB (eNB), or gNB as denoted in 5G. A service area or cell area is a geographical area where radio coverage is provided by the radio access node. The radio access node communicates over an air interface operating on radio frequencies with the wireless device within range of the radio access node.

[0006] Specifications for the Evolved Packet System (EPS), also called a Fourth Generation (4G) network, have been completed within the 3rd Generation Partnership Project (3GPP) and this work continues in the coming 3GPP releases, for example to specify a Fifth Generation (5G) network also referred to as 5G New Radio (NR). The EPS comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as System Architecture Evolution (SAE) core network. E-UTRAN / LTE is a variant of a 3GPP radio access network wherein the radio access nodes are directly connected to the EPC core network rather than to RNCs used in 3G networks. In general, in E-UTRAN / LTE the functions of a 3G RNC are distributed between the radio access nodes, e.g. eNodeBs in LTE, and the core network. As such, the RAN of an EPS has an essentially “flat” architecture comprising radio access nodes connected directly to one or more core networks, i.e. they are not connected to RNCs. To compensate for that,the E-UTRAN specification defines a direct interface between the radio access nodes, this interface being denoted the X2 interface.

[0007] Wireless communication systems in 3GPP

[0008] Figure 1 illustrates a simplified wireless communication system with a UE 12, which communicates with one or multiple access nodes 103-104, which in turn is connected to a network node 106. The access nodes 103-104 are part of a radio access network 10.

[0009] For wireless communication systems pursuant to 3GPP Evolved Packet System, (EPS), also referred to as Long Term Evolution, LTE, or 4G, standard specifications, such as specified in 3GPP TS 36.300 and related specifications, the access nodes 103-104 corresponds typically to a Evolved NodeBs (eNBs) and the network node 106 corresponds typically to either a Mobility Management Entity (MME) and / or a Serving Gateway (SGW). The eNB is part of the radio access network 10, which in this case is the E-UTRAN (Evolved Universal Terrestrial Radio Access Network), while the MME and SGW are both part of the EPC (Evolved Packet Core network). The eNBs are interconnected via the X2 interface, and connected to EPC via the S1 interface, more specifically via S1-C to the MME and S1-U to the SGW.

[0010] For wireless communication systems pursuant to 3GPP 5G System, 5GS (also referred to as New Radio, NR, or 5G) standard specifications, such as specified in 3GPP TS 38.300 and related specifications, on the other hand, the access nodes 103-104 corresponds typically to an 5G NodeB (gNB) and the network node 106 corresponds typically to either an Access and Mobility Management Function (AMF) and / or a User Plane Function (UPF). The gNB is part of the radio access network 10, which in this case is the NG-RAN (Next Generation Radio Access Network), while the AMF and UPF are both part of the 5G Core Network (5GC). The gNBs are inter-connected via the Xn interface, and connected to 5GC via the NG interface, more specifically via NG-C to the AMF and NG-U to the UPF.

[0011] To support fast mobility between NR and LTE and avoid change of core network, LTE eNBs may also be connected to the 5G-CN via NG-U / NG-C and support the Xn interface. An eNB connected to 5GC is called a next generation eNB (ng-eNB) and is considered part of the NG-RAN. LTE connected to 5GC will not be discussed further in this document; however, it should be noted that most of the solutions / features described for LTE and NR in this document also apply to LTE connected to 5GC. In this document, when the term LTE is used without further specification it refers to LTE-EPC.Mobility Robustness Optimization (MRO) in Self-Organized Network (SON) MRO aims at detecting and enabling correction of the following problems:

[0012] Connection failure due to intra-system or inter-system mobility;

[0013] Inter-system Unnecessary HO (too early inter-system HO from NR to E-UTRAN with no radio link failure);

[0014] Inter-system HO ping-pong;

[0015] PSCell change failure;

[0016] Inter-system voice fallback failure;

[0017] Fast Master Cell Group (MCG) recovery failure.

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

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

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

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

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

[0023] Successful PSCell addition / change.

[0024] Conditional Handover (CHO) in Non-Terrestrial Network (NTN)

[0025] Rel-16 CHO procedure and trigger conditions (A3 / A5 events) is the baseline for CHO in NTN. In order to support CHO for NTN scenarios, three new trigger conditions were defined in Rel-17:

[0026] - A time-based trigger condition, condEventT 1 - a time window in which the UE may execute CHO to the candidate target cell.

[0027] - A UE location-based trigger condition, condEventDI - a distance between the UE and a first reference location (location 1) becomes larger than a configured threshold, and a distance between the UE and a second reference location (location 2) in a candidate target cell becomes shorter than a second configured threshold.

[0028] - A4 event, condEventA4 - Neighbour becomes better than threshold.Time-based or location-based trigger conditions may be configured independently from the measurement condition for CHO in NTN in at least hard satellite switch cases where the service discontinuity gap time length is assumed to be zero or negligible.

[0029] Otherwise, a time-based or a location-based trigger condition is always configured together with one of the measurement-based trigger conditions (CHO events A3 / A4 / A5) as defined in 3gpp TS 38.331.

[0030] It is up to UE implementation how the UE evaluates the time- or location-based trigger condition together with the RRM measurement-based event.

[0031] When a time-based trigger condition is used, the source gNB may signal the corresponding parameters to a single target gNB via the Source NG-RAN Node to Target NG-RAN Node Transparent Container in an NG-C based handover, see 3gpp TS 23.502. The source gNB signals the corresponding CHO configuration to the UE in the RRC Reconfiguration message during handover execution.

[0032] When the time-based trigger condition is used, the source NG-RAN node should consider the time indicated to the UE to decide when to start the early data forwarding to the target NG-RAN node.

[0033] Time-based CHO may be performed via RACH-less handover.

[0034] MRO for CHO Optimization

[0035] Rel-17 has enhanced MRO to support CHO. CHO Execution failures may be classified in analogy to legacy handover failures, with the addition that the target cell was prepared for CHO, including too late CHO execution, too early CHO execution and CHO execution to the wrong cell.

[0036] A variety of information is logged in a Radio Link Failure (RLF) Report, Successful Handover report (SHR) and Successful PSCell Change Report (SPR) to help the network to identify CHO configuration problems, for example, choCandidate, choConfig, triggeredEvent as shown below:

[0037] MeasResultNR:: = SEQUENCE {

[0038] physCellld PhysCellld

[0039] OPTIONAL,

[0040] measResult SEQUENCE {

[0041] cellResults SEQUENCE {

[0042] results SSB-Cell Meas Quant ityResults

[0043] OPTIONAL,

[0044] resultsCSI-RS-Cell Me a s Quant ityRe suits

[0045] OPTIONAL

[0046] rsIndexResults SEQUENCE {

[0047] results S SB- Indexes ResultsPerSSB-IndexList

[0048] OPTIONAL,re suit sCSI -RS- Indexes ResultsPerCSI-RS-IndexList OPTIONAL

[0049] }

[0050] OPTIONAL

[0051] },

[0052] [ [

[0053] cgi-Inf o CGI-InfoNR

[0054] OPTIONAL

[0055] ] ]r

[0056] [ [

[0057] choCandidate-rl7 ENUMERATED { true }

[0058] OPTIONAL,

[0059] choConf ig-rl7 SEQUENCE ( SIZE ( 1..2 ) ) OF CondTriggerConfig-rl6 OPTIONAL,

[0060] triggeredEvent-r 17 SEQUENCE {

[0061] timeBetweenEvents-r 17 TimeBetweenEvent-r 17

[0062] OPTIONAL,

[0063] f irstTriggeredEvent-r 17 ENUMERATED { condFirstEventrcondSecondEvent } OPTIONAL

[0064] }

[0065] OPTIONAL

[0066] ] ]r

[0067] [ [

[0068] entering-rl8 ENUMERATED { true }

[0069] OPTIONAL

[0070] ] ]

[0071] }

[0072] choCandidate

[0073] This field indicates whether the associated cell is a candidate target cell for conditional handover or conditional PSCell change or addition. This field may be included only in the SuccessHO-Report or SuccessPSCell-Report within UElnformationResponse message.

[0074] choConfig

[0075] If the associated cell is a candidate target cell for conditional handover, this field indicates the conditional handover execution condition for each measld within condTriggerConfig associated to the cell. This field may be included only in the r / f-repo / t within UElnformationResponse message.

[0076] firstTriggeredEvent

[0077] This field is set to condFirstEvent if the execution condition associated to the first entry of choConfig was fulfilled first in time. This field is set to condSecondEvent if the execution condition associated to the second entry of choConfig was fulfilled first in time. This field may be included in rlf-report with in UElnformationResponse message or in SCGFailurelnformation message.

[0078] timeBetweenEvents

[0079] Indicates the time elapsed between fulfilling the conditional execution conditions included in choConfig. Value in milliseconds. The maximum value 1023 means 1023ms or longer. This field may be included in the reports associated to UElnformationResponse message, e.g., rlf-Report or in the

[0080]

[0081] SCGFailurelnformation message.

[0082] SUMMARY

[0083] In current standards, some of the MRO-related information elements related to CHO is reported within the Information Element MeasResultNR. Moreover, MeasResultNR is reported in the RLF Report, SHR and SPR only when there is available RRM measurement for a certain neighboring cell. However, in NTN with time- or location-based CHO, there may be no RRM measurements because the UE may not start performing RRM measurements on neighbouring cells before the time- / location-based CHO triggering conditions are triggered. Thus, the CHO information (such as CHO candidate cells, CHO configurations including the configured triggered conditions, etc) related toNTN MRO may be missing in MRO reports from the UE, and the network may not have enough information to detect the reason for the failure or near failure case and thus will not be able to do the optimization accordingly.

[0084] In another scenario in an NTN network, it is possible to configure the UE only with the time- or location-based triggering conditions for CHO, in such scenario the UE may not have any measurement available for some of the measurement objects for which candidate handover cells are configured for. Given the absence of the measurements, in prior art the CHO configuration and related information will not be logged in the RLF report and hence optimization of the time / location-based CHO may not be possible for the network.

[0085] There is thus a need for a more efficient approach for CHO.

[0086] An object of embodiments herein may be to obviate some of the problems mentioned above.

[0087] In order to address the above challenges, embodiments herein present solutions for how a UE may log and report the time- or location-based CHO configuration-related information to a network node, such as the source gNB. The UE is triggered to send a mobility-related report, such as an MRO report, e.g. the RLF report, with time- or locationbased CHO information but without RRM measurement on neighbouring cells. The mobility-related report may be triggered by a time-based trigger condition or a UE location-based trigger condition.

[0088] The mobility-related report may be sent to any network node if it is required to do so and the report has not been sent to the network before. Then the network node receiving this report may forward this information to the source network node. 302

[0089] The time- or location-based CHO configuration-related information may further comprise CHO candidate cells, CHO configurations including the configured triggered conditions, e.g. trigger conditions related to NTN MRO, such as time- or location-based trigger conditions for CHO. However, the mobility-related report may lack RRM measurements as these may not be available at the time of preparing the report.

[0090] Reporting the time- or location-based CHO configuration-related information to the network node may comprise transmitting the information to the network node.

[0091] In one solution, the time- and / or location-based CHO configuration-related information is reported within the Information Element MeasResultNR, even when there is no available RRM measurements.In an alternative solution, the time- and / or location-based CHO configuration-related information is decoupled from RRM measurement reporting. New information elements are introduced in RLF-Report, SHR, SPR and other MRO reports.

[0092] Thus, in both of these solutions the UE transmits an indication of the configured time- or location-based CHO related information to a network node. Also, in both of these solutions the UE transmits the indication of the configured time- or location-based CHO-related information without transmitting RRM measurements to the network node.

[0093] According to a first aspect, the object is achieved by a method performed by a wireless communications device. The method comprises triggering a mobility-related report for a neighbouring cell. The method further comprises transmitting the mobility-related report to a network node without RRM measurements on the neighbouring cell. The mobility-related report comprises Conditional Hand-Over-related information.

[0094] According to a second aspect, the object is achieved by a wireless communications device adapted to trigger a mobility-related report for a neighbouring cell.

[0095] The wireless communications device is further adapted to transmit the mobility-related report to a network node without RRM measurements on the neighbouring cell. The mobility-related report comprises CHO-related information.

[0096] According to a third aspect, the object is achieved by a method, performed by a network node.

[0097] The method comprises receiving, from a wireless communication device, a mobility-related report without RRM measurements and comprising CHO-related information.

[0098] According to a fourth aspect, the object is achieved by a network node. The network node is adapted to receive, from a wireless communication device, a mobility-related report without RRM measurements and comprising CHO-related information.

[0099] The CHO-related information may comprise time- or location-based CHO configuration-related information or both.

[0100] According to a further aspect, the object is achieved by a computer program comprising instructions, which when executed by a processor, causes the processor to perform actions according to any of the aspects above.According to a further aspect, the object is achieved by a carrier comprising the computer program of the aspect above, wherein the carrier is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0101] Since the wireless communications device transmits the mobility-related report without RRM measurements but with CHO-related information, the network may still get enough reported CHO-related information for MRO optimization.

[0102] An advantage of embodiments disclosed herein is that they enable the UE to report the CHO-related (MRO) information to the network, such as time- or location-based CHO-related MRO information. Even when there is no available RRM measurements, the network may still get enough reported time- or location-based CHO-related information for MRO optimization similarly with the other CHO event configuration. For example, according to some embodiments herein choConfigure inside MeasResultNR may be logged no matter if there is an available RRM measurement or not.

[0103] BRIEF DESCRIPTION OF THE DRAWINGS

[0104] The various aspects of embodiments disclosed herein, including particular features and advantages thereof, will be readily understood from the following detailed description and the accompanying drawings, in which:

[0105] Figure 1 is a block diagram schematically illustrating a simplified wireless communication system according to prior art,

[0106] Figure 2 is a block diagram schematically illustrating a system structure including entities involved in embodiments disclosed herein, Figure 3 is a flow chart schematically illustrating a method according to embodiments herein,

[0107] Figure 4 is a flow chart schematically illustrating a method according to some further embodiments herein,

[0108] Figure 5 is a block diagram illustrating a wireless communications device according to some embodiments herein,

[0109] Figure 6 is a block diagram illustrating a network node according to some embodiments herein.

[0110] DETAILED DESCRIPTIONThe text uses the term “cell” to identify a location (or coverage) on which the UE is located. However, the term “cell” may also be exchanged without any loss of meaning with the terms “radio resources”, “beams”, “TCI state”, or “TRS”. This is just to clarify that embodiments herein do not target specifically a scenario where there is a cell, but rather when a UE uses a set of source radio resources and need to switch to a target set of radio resources. In such a case, radio resource may also identify a set of configurations, field, parameters, or ASN.1 structures or lEs.

[0111] Embodiments disclosed herein are described mainly focusing on time- or locationbased CHO in NTN. However, the embodiments, methods, options and examples described may also be applied to time- or location-based CHO in TN deployment, and other non RRM measurement-based CHO in NTN or TN deployment.

[0112] Embodiments disclosed herein are described mainly focusing on RLF report and SHR in MCG. However, the embodiments, methods, options and examples described herein may also be applied to SCG, e.g SPR, and also other SON reports.

[0113] System overview

[0114] Figure 2 illustrates a system structure including the entities involved in embodiments herein.

[0115] A User Equipment (UE) 1001 may be a wireless terminal, such as a cellular smartphone, sometimes connected to a source network node 1002 over a wireless interface 1004 and sometimes connected to a target network node 1003, to which the UE 1001 is connected over a wireless interface 1005.

[0116] The source network node 1002 controls a source cell 1007 (sometimes called serving cell or Special Cell, SpCell, PCell or PSCell. The target network node 1003, sometimes referred to as a candidate network node, controls a target cell 1008, sometimes referred to as neighbour cell, candidate cell, LTM candidate cell or inter-CU LTM candidate cell.

[0117] Each of the source network node 1002 and the target network node 1003 may be a base station such as, when they e.g. are part of NG-RAN, e.g. a gNB. The source network node and the target network node are connected over an interface 1006, which may be an Xn or Xn-C type of interface, for example when the source network node and target network node are of type gNB and part of an NG-RAN.

[0118] In case of a distributed CU / DU RAN architecture, each of the source network node 1002 and / or the target network node 1003 may be divided into a distributed unit,sometimes known as gNB-Dll or DU, and a central unit, CU, sometimes referred to as gNB-CU, CU, gNB-CU-CP or gNB-CU-UP. Thus, in such a case the source network node 1002 may be divided into a source central unit, CU 1009, sometimes referred to as serving CU, and a source distributed unit, DU, 1010, and the target network node 1003 may be divided into a target central unit, CU 1012, sometimes referred to as target CU or candidate CU, and a target distributed unit, DU, 1013. Sometimes the source central unit, CU, is referred to as the source network node and the target central unit, CU, is referred to as the target network node.

[0119] The source CU 1009 and the source DU 1010 are connected over a source interface 1011, which may be an F1 type of interface in case of NG-RAN.

[0120] Correspondingly, the target CU 1012 and the target DU 1013 are connected over a target interface 1014, which may be an F1 type of interface in case of NG-RAN.

[0121] The source network node 1002 and the target network node 1003 may be connected to a further network node 1015 over second and third interfaces 1016 and 1017, respectively. The further network node 1015 may be a base station such as, when it is e.g. part of NG-RAN, a gNB. In the latter case the interfaces 1016 and 1017 may both be an Xn or Xn-C type of interface. The UE 1001 may sometimes be connected to the further network node 1015 over a wireless interface (not shown in Figure 2).

[0122] Flowcharts

[0123] Figure 3 illustrates a flow chart with the actions performed by a wireless communication device, such as the UE 1001, according to some embodiments disclosed herein.

[0124] Action 301.

[0125] The wireless communication device may log time- or location-based CHO-related information, or other CHO-related information, such as time information or location information when failure happens. Such information may be sent to the network (e.g. to a network node, such as the source network node 1002 or the target network node 1003) such that the network may base it’s decision-making on this information. For example, the network may: enable or disable time- or location based CHO, or adjust the related configurations.

[0126] Action 302.The wireless communication device triggers a mobility-related report for a neighbouring cell, such as the target cell 1008.

[0127] The wireless communication device triggers a mobility-related report, such as an MRO report, which also may be referred to as a SON report. The triggering of the mobility-related report may be for a neighbouring cell. The triggering of the mobility-related report may be performed without any available RRM measurement on the neighbouring cell. That is, there may not be any RRM measurements available at the time of the triggering of the report.

[0128] Triggering the mobility-related report may be based on a time- or a location-based CHO event or both. For example, the logged time- or location-based CHO-related information may trigger a CHO event (a time- or a location-based CHO event). Thus, a CHO may be triggered which is not based on RRM measurements, but based on time- or a location-based CHO-related information.

[0129] Action 303.

[0130] The wireless communication device transmits the mobility-related report to a network node, such as the source network node 1002 or the target network node 1003, e.g. via the source network node 1002, without RRM measurements on the neighbouring cell. The mobility-related report comprises CHO-related information. The CHO-related information may comprise CHO configuration information. The CHO- related information may comprise time- or location-based CHO-related information or both.

[0131] The CHO-related information may comprise time- or location-based CHO configuration-related information or both. In some embodiments disclosed herein the time- or location-based CHO configuration-related information or both comprises time- or location-based CHO configured candidate cells and / or a time- or location-based trigger condition for CHO.

[0132] The time- or location-based CHO configuration-related information or both may be reported to the network node (600) in:

[0133] 1) an information element for reporting RRM measurements; or

[0134] 2) one or more other fields in the mobility-related report outside the information element for reporting RRM measurements; or

[0135] 3) both 1) and 2) above.In some embodiments disclosed herein the information element comprising the time- or location-based CHO-related information does not comprise RRM measurements.

[0136] The CHO-related information may pertain to neighbouring cells, such as the target cell 1008, for which no RRM measurements are available.

[0137] In some embodiments disclosed herein the mobility-related report is transmitted without RRM measurements.

[0138] Figure 4 illustrates a flow chart with method actions performed by a network node, such as the source network node 1002 or the target network node 1003, according to some embodiments disclosed herein.

[0139] The method actions may be performed in any suitable order.

[0140] Action 401.

[0141] The network node receives, from the wireless communication device, a mobility-related report without RRM measurements and comprising CHO-related information.

[0142] The CHO-related information may comprise CHO configuration-related information. The CHO-related information may comprise time- or location-based CHO-related information or both. The CHO-related information may comprise time- or location-based CHO configuration-related information or both. As mentioned above, the mobility-related report does not comprise RRM measurements.

[0143] The time- or location-based CHO configuration-related information or both may be received from the wireless communication device in:

[0144] 1) an information element for reporting RRM measurements; or

[0145] 2) one or more other fields in the mobility report outside the information element for reporting RRM measurements; or

[0146] 3) both 1) and 2) above.

[0147] Action 402. The network node may perform MRO based on the received time- or location-based CHO configuration-related information, or other CHO-related information, such as time information or location information when failure happens. The MRO optimization may be performed in response to receiving the CHO-related information in action 401.Thus, even when there are no available RRM measurements, the network node may still get enough reported time- or location-based CHO-related information for MRO optimization similarly with the other CHO event configuration. With the received time- or location-based CHO-related information, the network node is able to perform one or more of the following actions: enable or disable time- or location-based CHO, or adjust the related configurations.

[0148] Detailed embodiments will be disclosed below.

[0149] First embodiments

[0150] To address the problem described above, some first embodiments comprise logging time- or location-based CHO-related information, or other CHO-related information, such as time information or location information when failure happens, by the UE 1001 and report this information to the network.

[0151] With these embodiments, the time- or location- based CHO related information may be logged in the RLF Report or the SHR or both, using current information elements, e.g. MeasResultNR, even when there is no available RRM measurements for the neighbor cell.

[0152] choConfig inside MeasResultNR is extended to include the time- or location- based CHO configuration for RLF report and SHR, which may be used to indicate whether a neighbor cell is a CHO candidate cell or not and the related detailed CHO configuration.

[0153] Non-limiting example implementations of the above solution are given below (3GPP TS 38.331 v18.4.0 is taken as the baseline), wherein it is considered the case using the choConfig inside MeasResultNR to report the time- or location-based CHO related information in the RLF report and SHR. Please note that the modifications to 3GPP TS 38.331 v18.4.0 according to embodiments disclosed herein are underlined below.

[0154] Implementation example 1 of first embodiments, procedural logic for the RLF report: 5.3.10.5 RLF report content determination (Note that the section number is from 3GPP TS 38.331 version 18.4.0.)

[0155] The UE shall determine the content in the VarRLF-Report as follows:

[0156] 1> clear the information included in VarRLF-Report, if any;

[0157] 1 > if the UE is not in SNPN access mode, set the plmn-ldentityList to include the list of EPLMNs stored by the UE (i.e. including the RPLMN);

[0158] 1>else if the UE is in SNPN access mode, set the snpn-ldentityList to include the list of equivalent SNPNs stored by the UE (i.e., including the registered SNPN identity); 1> set the measResultLastServCell to include the cell level RSRP, RSRQ and the available SINR, of the source PCell (in case HO failure) or PCell (in case RLF)based on the available SSB and CSI-RS measurements collected up to the moment the UE detected failure;

[0159] 1 > if measRSSI-ReportConfig is configured for the measObject indicated as the servingCellMO of the source PCell (in case HO failure) or PCell (in case of RLF), set the measResultLastServCellRSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency of the source PCell (in case HO failure) or PCell (in case of RLF) up to the moment the UE detected the failure;

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

[0161] 2>set the rsIndexResults in measResultLastServCell to include all the available measurement quantities of the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the highest SS / PBCH block RSRP is listed first if SS / PBCH block RSRP measurement results are available, otherwise the highest SS / PBCH block RSRQ is listed first if SS / PBCH block RSRQ measurement results are available, otherwise the highest SS / PBCH block SI NR is listed first, based on the available SS / PBCH block based measurements collected up to the moment the UE detected failure;

[0162] 1 > if the CSI-RS based measurement quantities are available:

[0163] 2>set the rsIndexResults in measResultLastServCell to include all the available measurement quantities of the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE detected failure;

[0164] 1>for each of the configured measObjectNR in which measurements are available or for which the associated reportConfig NR is configured as a time- or location-based conditional reconfiguration:

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

[0166] 3>set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the cell with highest SS / PBCH block RSRP is listed first if SS / PBCH block RSRP measurement results are available, otherwise the cell with highest SS / PBCH block RSRQ is listed first if SS / PBCH block RSRQ measurement results are available, otherwise the cell with highest SS / PBCH block SINR is listed first, based on the available SS / PBCH block based measurements collected up to the moment the UE detected failure;

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

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

[0169] 2> if the CSI-RS based measurement quantities are available:3>set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the cell with highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the cell with highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the cell with highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE detected radio link failure; 4>for each neighbour cell included, include the optional fields that are available;

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

[0171] 2>for each neighbour cell, if any, included in measResultListNR in measResultNeighCells or with an associated reportConfig NR is configured as a time- or location-based conditional reconfiguration:

[0172] 3> if the UE supports RLF-Report for conditional handover and if the neighbour cell is one of the candidate cells for which the reconfigurationWithSync is included in the masterCellGroup in the MCG VarConditional Reconfig at the moment of the detected failure:

[0173] 4>set choConfig in MeasResult2NR to the execution condition for each measld within condTriggerConfig associated to the neighbour cell within the MCG VarConditionalReconfig-,

[0174] 4> if the first entry of choConfig corresponds to a fulfilled execution condition at the moment of handover failure, or radio link failure; or

[0175] 4> if the second entry of choConfig, if available, corresponds to a fulfilled execution condition at the moment of handover failure, or radio link failure: 5>set firstTriggeredEvent to the execution condition condFirstEvent corresponding to the first entry of choConfig or to the execution condition condSecondEvent corresponding to the second entry of choConfig, whichever execution condition was fulfilled first in time; 5> set timeBetweenEvents to the elapsed time between the point in time of fulfilling the condition in choConfig that was fulfilled first in time, and the point in time of fulfilling the condition in choConfig that was fulfilled second in time, if both the first execution condition corresponding to the first entry and the second execution condition corresponding to the second entry in the choConfig were fulfilled;

[0176] 1>for each of the configured measObjectNR associated with neighboring cells if the associated reportConfig NR includes measRSSI-ReportConfig-.

[0177] 2> set the measResultNeighFreqRSSI in the measResultNeighFreqListRSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequencies other than the frequency of the source PCell (in case HO failure) or of the PCell (in case RLF), up to the moment the UE detected failure:3>for each neighbour frequency included, include the optional fields that are available;

[0178] 1>for each of the configured EUTRA frequencies in which measurements are available;

[0179] 2>set the measResultListEUTRA in measResultNeighCells to include the best measured cells ordered such that the cell with highest RSRP is listed first if RSRP measurement results are available, otherwise the cell with highest RSRQ is listed first, and based on measurements collected up to the moment the UE detected failure;

[0180] 3>for each neighbour cell included, include the optional fields that are available; NOTE 1: The measured quantities are filtered by the L3 filter as configured in the mobility measurement configuration. The measurements are based on the time domain measurement resource restriction, if configured. Exclude-listed cells are not required to be reported.

[0181] 1>set the c-RNTI to the C-RNTI used in the source PCell (in case HO failure) or PCell (in case RLF);

[0182] 1 > if the failure is detected due to reconfiguration with sync failure as described in 5.3.5.8.3, set the fields in VarRLF-Report as follows:

[0183] 2> set the connectionFailureType to hof,

[0184] 2> if the UE supports RLF-Report for DAPS handover and if any DAPS bearer was configured while T304 was running:

[0185] 3> set lastHO-Type to daps,

[0186] 3> if radio link failure was detected in the source PCell, according to clause 5.3.10.3:

[0187] 4>set timeConnSourceDAPS-Failure to the time between the initiation of the DAPS handover execution and the radio link failure detected in the source PCell while T304 was running;

[0188] 4>set the rlf-Cause to the trigger for detecting the source radio link failure in accordance with clause 5.3.10.4;

[0189] 2> if the UE supports RLF-Report for conditional handover and if configuration of the conditional handover is available in the MCG VarConditionalReconfig at the moment of the handover failure:

[0190] 3> if the UE executed a conditional handover toward target PCell according to the condRRCReconfig of the target PCell:

[0191] 4>set timeSinceCHO-Reconfig to the time elapsed between the execution of the last RRCReconfiguration message including reconfigurationWithSync for the target PCell of the failed conditional handover, and the reception in the source PCell of the last conditionalReconfiguration including the condRRCReconfig of the target PCell of the failed conditional handover; 3>else:4>set timeSinceCHO-Reconfig to the time elapsed between the execution of the last RRCReconfiguration message including reconfigurationWithSync for the target PCell of the failed handover, and the reception in the source PCell of the last conditionalReconfiguration including the condRRCReconfig-,

[0192] 3>set choCandidateCellList to include the global cell identity, if available, and otherwise to the physical cell identity and carrier frequency of each of the candidate target cells for conditional handover included in condRRCReconfig within the MCG VarConditionalReconfig at the time of the failed handover, excluding the candidate target cells included in measResultNeighCells-, 2> if the UE supports RLF-Report for conditional handover and if the last executed RRCReconfiguration message including reconfigurationWithSync was concerning a conditional handover:

[0193] 3> set lastHO-Type to cho;

[0194] 2>set the nrFailedPCellld in failedPCellld to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell of the failed handover;

[0195] 2> include nrPreviousCell in previousPCellld and set it to the global cell identity and tracking area code of the PCell where the last RRCReconfiguration message including reconfigurationWithSync was received;

[0196] 2> set the timeConnFailure to the elapsed time since the execution of the last RRCReconfiguration message including the reconfigurationWithSync, 1>else if the failure is detected due to Mobility from NR failure as described in 5.4.3.5, set the fields in VarRLF-Report as follows:

[0197] 2> set the connectionFailureType to hof,

[0198] 2> if last MobilityFromNRCommand concerned a failed inter-RAT handover from NR to E-UTRA and if the UE supports Radio Link Failure Report for Inter-RAT MRO EUTRA (NR to EUTRA):

[0199] 3>set the eutraFailedPCellld in failedPCellld to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell of the failed handover;

[0200] 2> include nrPreviousCell in previousPCellld and set it to the global cell identity and tracking area code of the PCell where the last MobilityFromNRCommand message was received;

[0201] 2> set the timeConnFailure to the elapsed time since the initialization of the handover associated to the last MobilityFromNRCommand message;

[0202] 2> if the UE supports RLF report for inter-system handover for voice fallback and if voiceFallbacklndication is included in the last MobilityFromNRCommand'.

[0203] 3> include the voiceFallbackHO;

[0204] 1>else if the failure is detected due to radio link failure as described in 5.3.10.3, set the fields in VarRLF-Report as follows:> set the connectionFailureType to rlf,

[0205] >set the rlf-Cause to the trigger for detecting radio link failure in accordance with clause 5.3.10.4;

[0206] >set the nrFailedPCellld in failedPCellld to the global cell identity and the tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the PCell where radio link failure is detected;

[0207] > if an RRCReconfiguration message including the reconfigurationWithSync was received before the connection failure:

[0208] 3> if the last successfully executed RRCReconfiguration message including the reconfigurationWithSync concerned an intra NR handover and it was received while connected to the previous PCell to which the UE was connected before connecting to the PCell where radio link failure is detected; and

[0209] 3> if T316 was not running before entering the PCell in which the radio link failure was detected; and

[0210] 3> if T311 was not running before entering the PCell in which the radio link failure was detected:

[0211] 4> include the nrPreviousCell in previousPCellld and set it to the global cell identity and the tracking area code of the PCell where the last executed RRCReconfiguration message including reconfigurationWithSync was received;

[0212] 4> if the last executed RRCReconfiguration message including reconfigurationWithSync was concerning a DAPS handover:

[0213] 5> set lastHO-Type to daps,

[0214] 4>else if the last executed RRCReconfiguration message including reconfigurationWithSync was concerning a conditional handover:

[0215] 5> set lastHO-Type to cho;

[0216] 4> set the timeConnFailure to the elapsed time since the execution of the last RRCReconfiguration message including the reconfigurationWithSync, 3>else if the last RRCReconfiguration message including the reconfigurationWithSync concerned a handover to NR from E-UTRA and if the UE supports Radio Link Failure Report for Inter-RAT MRO EUTRA:

[0217] 4> include the eutraPreviousCell in previousPCellld and set it to the global cell identity and the tracking area code of the E-UTRA PCell where the last RRCReconfiguration message including reconfigurationWithSync was received embedded in E-UTRA RRC message MobilityFromEUTRACommand message as specified in TS 36.331

[0010] clause 5.4.3.3;

[0218] 4> set the timeConnFailure to the elapsed time since reception of the last RRCReconfiguration message including the reconfigurationWithSync embedded in E-UTRA RRC message MobilityFromEUTRACommand message as specified in TS 36.331

[0010] clause 5.4.3.3;2> if configuration of the conditional handover is available in the MCG VarConditionalReconfig at the moment of declaring the radio link failure:

[0219] 3>set timeSinceCHO-Reconfig to the time elapsed between the detection of the radio link failure, and the reception, in the source PCell, of the last conditionalReconfiguration including the condRRCReconfig message;

[0220] 3>set choCandidateCellList to include the global cell identity if available, and otherwise to the physical cell identity and carrier frequency of each of all the candidate target cells for conditional handover included in condRRCReconfig within the MCG VarConditionalReconfig at the time of radio link failure, excluding the candidate target cells included in measResultNeighCells', 1 > if connectionFailureType is rlf and the rlf-Cause is set to randomAccessProblem or beamFailureRecoveryFailure', or

[0221] 1 > if connectionFailureType is rlf and the rlf-Cause is set to IbtFailure and the radio link failure is detected during the random access procedure; or

[0222] 1 > if connectionFailureType is hof and if the failed handover is an intra-RAT handover: 2>set the ra-InformationCommon to include the random-access related information as described in clause 5.7.10.5;

[0223] 1 > if connectionFailureType is rlf and the rlf-Cause is set to IbtFailure, and the radio link failure is not detected during the random access procedure:

[0224] 2>set the locationAndBandwidth and subcarrierSpacing in bwp-lnfo associated to the UL BWP in which the consistent uplink LBT failure was detected;

[0225] 1 > if the rlf-Cause is set to t310-Expiry or t312-Expiry.

[0226] 2>set the ssbRLMConfigBitmap and / or csi-rsRLMConfigBitmap in measResultLastServCell to include the radio link monitoring configuration of the last serving cell, if available;

[0227] 1 > if available, set the locationinfo as in 5.3.3.7.

[0228] The UE may discard the radio link failure information or handover failure information, i.e. release the UE variable VarRLF-Report, 48 hours after the radio link failure / handover failure is detected.

[0229] NOTE 2: In this clause, the term 'handover failure' has been used to refer to 'reconfiguration with sync failure'.

[0230] Implementation example 2 of the first embodiments, procedural logic for the successful handover report:

[0231] 5.7.10.6 Actions for the successful handover report determination [Note that the section number is from 3GPP TS 38.331 version 18.4.0.]

[0232] The UE shall for the PCell:

[0233] 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 greaterthan thresholdPercentageT304 if included in the successHO-Config received before executing the last reconfiguration with sync; or

[0234] > 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

[0235] > 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; or

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

[0237] > 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

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

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

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

[0241] 3> if the UE is not in SNPN access mode, set the plmn-ldentityList to include the list of EPLMNs stored by the UE (i.e., includes the RPLMN);

[0242] 3>else if the UE is in SNPN access mode, set the snpn-ldentityList to include the list of equivalent SNPNs stored by the UE (i.e., including the registered SNPN identity), if available;

[0243] 3>for intra-NR handover, set the c-RNTI to the C-RNTI assigned by the target PCell of the handover;3> if the procedure is triggered due to successful completion of reconfiguration with sync, for the source PCell in which the last RRCReconfiguration message including reconfigurationWithSync was applied; or

[0244] 3> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, for the source PCell in which the last MobilityFromNRCommand concerning an inter-RAT handover from NR to E-UTRA was applied:

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

[0246] 4>set the sourceCellMeas in sourceCelllnfo to include the cell level RSRP, RSRQ and the available SINR, of the source PCell based on the available SSB and CSI-RS measurements collected up to the moment the UE sends RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA;

[0247] 4>set the rsIndexResults in sourceCellMeas to include all the available SSB and CSI-RS measurement quantities of the source PCell collected up to the moment the UE sends RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA; 4> if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running:

[0248] 5> set the rlf-lnSourceDAPS in sourceCelllnfo to true,

[0249] 3> if the procedure is triggered due to successful completion of reconfiguration with sync, for the target PCell indicated in the last applied RRCReconfiguration message including reconfigurationWithSync.

[0250] 4>set the targetPCellID in targetCellInfo to the global cell identity and tracking area code, if available, of the target PCell; otherwise, set the targetCell- PCI-ARFCN to the physical cell identity and carrier frequency of the target PCell;

[0251] NOTE 00: If targetCell-PCI-ARFCN is included, it is left to UE implementation how to set the targetPCellID.

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

[0253] 4>set the rsIndexResults in targetCellMeas to include all the available SSB and CSI-RS measurement quantities of the target PCell collected up to the moment the UE sends RRCReconfigurationComplete message;4> if the last applied RRCReconfiguration message including reconfigurationWithSync was included in the stored condRRCReconfig: 5> set the timeSinceCHO-Reconfig to the time elapsed between the initiation of the execution of conditional reconfiguration for the target PCell and the reception of the last conditionalReconfiguration including the condRRCReconfig of the target PCell in the source PCell;

[0254] 3> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, for the target PCell indicated in the last applied MobilityFromNRCommand concerning an inter-RAT handover from NR to E- UTRA:

[0255] 4>set the targetPCellId in eutra-TargetCellInfo to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell;

[0256] 4>set the targetCellMeas in eutra-TargetCelllnfo to include the cell level RSRP, RSRQ and the available SINR, of the target PCell based on the available measurements collected up to the moment the UE sends RRCConnectionReconfigurationComplete message;

[0257] NOTE 0: If eutra-TargetCellInfo is included, it is left to UE implementation how to set the targetCell Info.

[0258] 3> 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 T304 timer, 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:

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

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

[0261] 3> if the ratio between the value of the elapsed time of the timer T310 and the configured value of the T310 timer, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync or 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 reconfiguration with sync or Mobility from NR to E-UTRA: 4>set t310-cause in shr-Cause to true,

[0262] 3> if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the reconfiguration with sync procedure or 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 T312 timer, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync or 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 reconfiguration with sync, or Mobility from NR to E-UTRA:4>set t312-cause in shr-Cause to true,

[0263] > if the procedure is triggered due to successful completion of reconfiguration with sync and if sourceDAPS-FailureReporting included in the successHO- Config if configured by the source PCell before executing the last reconfiguration with sync is set to true, and if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running:

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

[0265] > if the procedure is triggered due to successful completion of reconfiguration with sync, for each of the measObjectNR, configured by the source PCell, in which the last RRCReconfiguration message including reconfigurationWithSync was applied;or:

[0266] > if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, for each of the measObjectNR, configured by the source PCell, in which the last MobilityFromNRCommand concerning an inter-RAT handover from NR to E-UTRA was applied:

[0267] 4> if measRSSI-ReportConfig is configured for the frequency of the source PCell:

[0268] 5> if the procedure is triggered due to successful completion of reconfiguration with sync:

[0269] 6> set the measResultServCellRSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency of the source PCell up to the moment the UE sends the RRCReconfigurationComplete message;

[0270] 5> else if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA:

[0271] 6> set the measResultServCellRSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency of the source PCell up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message;

[0272] 4>for each of the configured measObjectNR if measRSSI-ReportConfig is configured for the configured frequency:

[0273] 5> if the procedure is triggered due to successful completion of reconfiguration with sync:

[0274] 6> set the measResultNeighFreqRSSI in the measResultNeighFreqListRSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the associated neighbouring frequency up to the moment the UE sends the RRCReconfigurationComplete message:

[0275] 7>for each neighbour frequency included, include the optional fields that are available;

[0276] 5> else if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA:6> set the measResultNeighFreqRSSI in the measResultNeighFreqListRSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the associated neighbouring frequency up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message:

[0277] 7>for each neighbour frequency included, include the optional fields that are available;

[0278] 4> if measurements are available for the measObjectNR:

[0279] 5> if the SS / PBCH block-based measurement quantities are available: 6> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell or target PCell, ordered such that the cell with highest SS / PBCH block RSRP is listed first if SS / PBCH block RSRP measurement results are available, otherwise the cell with highest SS / PBCH block RSRQ is listed first if SS / PBCH block RSRQ measurement results are available, otherwise the cell with highest SS / PBCH block SINR is listed first, based on the available SS / PBCH block based measurements collected up to the moment the UE sends the RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E- UTRA;

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

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

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

[0283] 6> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell and target PCell, ordered such that the cell with highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the cell with highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the cell with highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE sends the RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA;6>for each neighbour cell included, include the optional fields that are available;

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

[0285] 3> if the procedure is triggered due to successful completion of reconfiguration with sync, for each of the measObjectEUTRA, configured by the source PCell in which the last RRCReconfiguration message including reconfigurationWithSync was applied; or:

[0286] 3> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, for each of the measObjectEUTRA, configured by the source PCell in which the last MobilityFromNRCommand concerning an inter-RAT handover from NR to E-UTRA was applied:

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

[0288] 5> set the measResultListEUTRA in measResultNeighCells to include the best measured cells ordered such that the cell with highest RSRP is listed first if RSRP measurement results are available, otherwise the cell with highest RSRQ is listed first, based on measurements collected up to the moment the UE sends the RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA; 5>for each neighbour cell included, include the optional fields that are available;

[0289] 3>for each of the neighbour cells included in measResultNeighCells or each of the neighbour cells configured as a time- or location-based conditional reconfiguration candidate cell according to the associated reportConfig NR’. 4> if the cell was a candidate target cell included in the condRRCReconfig within the conditionalReconfiguration configured by the source PCell, in which the last RRCReconfiguration message including reconfigurationWithSync was applied:

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

[0291] 4>for each neighbour cell included, include the optional fields that are available in measResult2NR and measResultNR',

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

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

[0294] 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.****************************************************************************************** Implementation example 3 of the first embodiments, procedural logic for the RLF report: 5.3.10.5 RLF report content determination [Note that the section number is from 3GPP TS 38.331 version 18.4.0.]

[0295] The UE shall determine the content in the VarRLF-Report as follows:

[0296] 1> clear the information included in VarRLF-Report, if any;

[0297] 1 > if the UE is not in SNPN access mode, set the plmn-ldentityList to include the list of EPLMNs stored by the UE (i.e. including the RPLMN);

[0298] 1>else if the UE is in SNPN access mode, set the snpn-ldentityList to include the list of equivalent SNPNs stored by the UE (i.e., including the registered SNPN identity); 1> set the measResultLastServCell to include the cell level RSRP, RSRQ and the available SINR, of the source PCell (in case HO failure) or PCell (in case RLF) based on the available SSB and CSI-RS measurements collected up to the moment the UE detected failure;

[0299] 1 > if measRSSI-ReportConfig is configured for the measObject indicated as the servingCellMO of the source PCell (in case HO failure) or PCell (in case of RLF), set the measResultLastServCellRSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency of the source PCell (in case HO failure) or PCell (in case of RLF) up to the moment the UE detected the failure;

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

[0301] 2>set the rsIndexResults in measResultLastServCell to include all the available measurement quantities of the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the highest SS / PBCH block RSRP is listed first if SS / PBCH block RSRP measurement results are available, otherwise the highest SS / PBCH block RSRQ is listed first if SS / PBCH block RSRQ measurement results are available, otherwise the highest SS / PBCH block SINR is listed first, based on the available SS / PBCH block based measurements collected up to the moment the UE detected failure;

[0302] 1 > if the CSI-RS based measurement quantities are available:

[0303] 2>set the rsIndexResults in measResultLastServCell to include all the available measurement quantities of the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE detected failure;

[0304] 1>for each of the configured measObjectNR in which measurements are available or for which the associated reportConfig NR includes a condEventTI, condtEventD1 or condEventD2'.

[0305] 2> if the SS / PBCH block-based measurement quantities are available:3>set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the cell with highest SS / PBCH block RSRP is listed first if SS / PBCH block RSRP measurement results are available, otherwise the cell with highest SS / PBCH block RSRQ is listed first if SS / PBCH block RSRQ measurement results are available, otherwise the cell with highest SS / PBCH block SINR is listed first, based on the available SS / PBCH block based measurements collected up to the moment the UE detected failure;

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

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

[0308] 2> if the CSI-RS based measurement quantities are available:

[0309] 3>set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the cell with highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the cell with highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the cell with highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE detected radio link failure; 4>for each neighbour cell included, include the optional fields that are available;

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

[0311] 2> if measResultListNR in measResultNeighCells includes fewer than maxCellReport MeasResultNR lEs and the measObjectNR is associated with a reportConfig NR including a condEventTI, condtEvenD1 or condEventD2'.

[0312] 3> for each neighbour cell associated with the measObjectNR for which no measurement Quantities are available:

[0313] 4> if measResultListNR in measResultNeighCells includes fewer than maxCellReport MeasResultNR lEs:

[0314] 5> include a MeasResultNR IE in measResultListNR in measResultNeighCells and leave the resultsSSB-Cell, resultsCSI-RS- Cell and rsIndexResults absent;

[0315] NOTE 0c: Neighbouring cells for which no measurement Quantities are available are placed after neighbouring cells for which measurement Quantities are available in measResultListNR in measResultNeighCells.2>for each neighbour cell, if any, included in measResultListNR in measResultNeighCells:

[0316] 3> if the UE supports RLF-Report for conditional handover and if the neighbour cell is one of the candidate cells for which the reconfigurationWithSync is included in the masterCellGroup in the MCG VarConditional Reconfig at the moment of the detected failure:

[0317] 4> set the choCandidate to true in measResultNR (In variations of this implementation example, this statement may be omitted.)

[0318] 4>set choConfig in MeasResult2NR to the execution condition for each measld within condTriggerConfig associated to the neighbour cell within the MCG VarConditionalReconfig-,

[0319] 4> if the first entry of choConfig corresponds to a fulfilled execution condition at the moment of handover failure, or radio link failure; or

[0320] 4> if the second entry of choConfig, if available, corresponds to a fulfilled execution condition at the moment of handover failure, or radio link failure: 5>set firstTriggeredEvent to the execution condition condFirstEvent corresponding to the first entry of choConfig or to the execution condition condSecondEvent corresponding to the second entry of choConfig, whichever execution condition was fulfilled first in time; 5> set timeBetweenEvents to the elapsed time between the point in time of fulfilling the condition in choConfig that was fulfilled first in time, and the point in time of fulfilling the condition in choConfig that was fulfilled second in time, if both the first execution condition corresponding to the first entry and the second execution condition corresponding to the second entry in the choConfig were fulfilled;

[0321] >for each of the configured measObjectNR associated with neighboring cells if the associated reportConfig NR includes measRSSI-ReportConfig-.

[0322] 2> set the measResultNeighFreqRSSI in the measResultNeighFreqListRSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequencies other than the frequency of the source PCell (in case HO failure) or of the PCell (in case RLF), up to the moment the UE detected failure:

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

[0324] >for each of the configured EUTRA frequencies in which measurements are available;

[0325] 2>set the measResultListEUTRA in measResultNeighCells to include the best measured cells ordered such that the cell with highest RSRP is listed first if RSRP measurement results are available, otherwise the cell with highest RSRQ is listed first, and based on measurements collected up to the moment the UE detected failure;

[0326] 3>for each neighbour cell included, include the optional fields that are available;NOTE 1: The measured quantities are filtered by the L3 filter as configured in the mobility measurement configuration. The measurements are based on the time domain measurement resource restriction, if configured. Exclude-listed cells are not required to be reported.

[0327] 1>set the c-RNTI to the C-RNTI used in the source PCell (in case HO failure) or PCell (in case RLF);

[0328] 1 > if the failure is detected due to reconfiguration with sync failure as described in 5.3.5.8.3, set the fields in VarRLF-Report as follows:

[0329] 2> set the connectionFailureType to hof,

[0330] 2> if the UE supports RLF-Report for DAPS handover and if any DAPS bearer was configured while T304 was running:

[0331] 3> set lastHO-Type to daps,

[0332] 3> if radio link failure was detected in the source PCell, according to clause 5.3.10.3:

[0333] 4>set timeConnSourceDAPS-Failure to the time between the initiation of the DAPS handover execution and the radio link failure detected in the source PCell while T304 was running;

[0334] 4>set the rlf-Cause to the trigger for detecting the source radio link failure in accordance with clause 5.3.10.4;

[0335] 2> if the UE supports RLF-Report for conditional handover and if configuration of the conditional handover is available in the MCG VarConditionalReconfig at the moment of the handover failure:

[0336] 3> if the UE executed a conditional handover toward target PCell according to the condRRCReconfig of the target PCell:

[0337] 4>set timeSinceCHO-Reconfig to the time elapsed between the execution of the last RRCReconfiguration message including reconfigurationWithSync for the target PCell of the failed conditional handover, and the reception in the source PCell of the last conditionalReconfiguration including the condRRCReconfig of the target PCell of the failed conditional handover; 3>else:

[0338] 4>set timeSinceCHO-Reconfig to the time elapsed between the execution of the last RRCReconfiguration message including reconfigurationWithSync for the target PCell of the failed handover, and the reception in the source PCell of the last conditionalReconfiguration including the condRRCReconfig-,

[0339] 3>set choCandidateCellList to include the global cell identity, if available, and otherwise to the physical cell identity and carrier frequency of each of the candidate target cells for conditional handover included in condRRCReconfig within the MCG VarConditionalReconfig at the time of the failed handover, excluding the candidate target cells included in measResultNeighCells-,2> if the UE supports RLF-Report for conditional handover and if the last executed RRCReconfiguration message including reconfigurationWithSync was concerning a conditional handover:

[0340] 3> set lastHO-Type to cho;

[0341] 2>set the nrFailedPCellld in failedPCellld to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell of the failed handover;

[0342] 2> include nrPreviousCell in previousPCellld and set it to the global cell identity and tracking area code of the PCell where the last RRCReconfiguration message including reconfigurationWithSync was received;

[0343] 2> set the timeConnFailure to the elapsed time since the execution of the last RRCReconfiguration message including the reconfigurationWithSync, >else if the failure is detected due to Mobility from NR failure as described in 5.4.3.5, set the fields in VarRLF-Report as follows:

[0344] 2> set the connectionFailureType to hof,

[0345] 2> if last MobilityFromNRCommand concerned a failed inter-RAT handover from NR to E-UTRA and if the UE supports Radio Link Failure Report for Inter-RAT MRO EUTRA (NR to EUTRA):

[0346] 3>set the eutraFailedPCellld in failedPCellld to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell of the failed handover;

[0347] 2> include nrPreviousCell in previousPCellld and set it to the global cell identity and tracking area code of the PCell where the last MobilityFromNRCommand message was received;

[0348] 2> set the timeConnFailure to the elapsed time since the initialization of the handover associated to the last MobilityFromNRCommand message;

[0349] 2> if the UE supports RLF report for inter-system handover for voice fallback and if voiceFallbacklndication is included in the last MobilityFromNRCommand'.

[0350] 3> include the voiceFallbackHO;

[0351] >else if the failure is detected due to radio link failure as described in 5.3.10.3, set the fields in VarRLF-Report as follows:

[0352] 2> set the connectionFailureType to rlf,

[0353] 2>set the rlf-Cause to the trigger for detecting radio link failure in accordance with clause 5.3.10.4;

[0354] 2>set the nrFailedPCellld in failedPCellld to the global cell identity and the tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the PCell where radio link failure is detected;

[0355] 2> if an RRCReconfiguration message including the reconfigurationWithSync was received before the connection failure:3> if the last successfully executed RRCReconfiguration message including the reconfigurationWithSync concerned an intra NR handover and it was received while connected to the previous PCell to which the UE was connected before connecting to the PCell where radio link failure is detected; and

[0356] 3> if T316 was not running before entering the PCell in which the radio link failure was detected; and

[0357] 3> if T311 was not running before entering the PCell in which the radio link failure was detected:

[0358] 4> include the nrPreviousCell in previousPCellld and set it to the global cell identity and the tracking area code of the PCell where the last executed RRCReconfiguration message including reconfigurationWithSync was received;

[0359] 4> if the last executed RRCReconfiguration message including reconfigurationWithSync was concerning a DAPS handover:

[0360] 5> set lastHO-Type to daps,

[0361] 4>else if the last executed RRCReconfiguration message including reconfigurationWithSync was concerning a conditional handover:

[0362] 5> set lastHO-Type to cho;

[0363] 4> set the timeConnFailure to the elapsed time since the execution of the last RRCReconfiguration message including the reconfigurationWithSync, 3>else if the last RRCReconfiguration message including the reconfigurationWithSync concerned a handover to NR from E-UTRA and if the UE supports Radio Link Failure Report for Inter-RAT MRO EUTRA:

[0364] 4> include the eutraPreviousCell in previousPCellld and set it to the global cell identity and the tracking area code of the E-UTRA PCell where the last RRCReconfiguration message including reconfigurationWithSync was received embedded in E-UTRA RRC message MobilityFromEUTRACommand message as specified in TS 36.331

[0010] clause 5.4.3.3;

[0365] 4> set the timeConnFailure to the elapsed time since reception of the last RRCReconfiguration message including the reconfigurationWithSync embedded in E-UTRA RRC message MobilityFromEUTRACommand message as specified in TS 36.331

[0010] clause 5.4.3.3;

[0366] > if configuration of the conditional handover is available in the MCG VarConditionalReconfig at the moment of declaring the radio link failure:

[0367] 3>set timeSinceCHO-Reconfig to the time elapsed between the detection of the radio link failure, and the reception, in the source PCell, of the last conditionalReconfiguration including the condRRCReconfig message;

[0368] 3>set choCandidateCellList to include the global cell identity if available, and otherwise to the physical cell identity and carrier frequency of each of all the candidate target cells for conditional handover included in condRRCReconfig within the MCG VarConditionalReconfig at the time of radio link failure, excluding the candidate target cells included in measResultNeighCells',1 > if connectionFailureType is rlf and the rlf-Cause is set to randomAccessProblem or beamFailureRecoveryFailure', or

[0369] 1 > if connectionFailureType is rlf and the rlf-Cause is set to IbtFailure and the radio link failure is detected during the random access procedure; or

[0370] 1 > if connectionFailureType is hof and if the failed handover is an intra-RAT handover: 2>set the ra-InformationCommon to include the random-access related information as described in clause 5.7.10.5;

[0371] 1 > if connectionFailureType is rlf and the rlf-Cause is set to IbtFailure, and the radio link failure is not detected during the random access procedure:

[0372] 2>set the locationAndBandwidth and subcarrierSpacing in bwp-lnfo associated to the UL BWP in which the consistent uplink LBT failure was detected;

[0373] 1 > if the rlf-Cause is set to t310-Expiry or t312-Expiry.

[0374] 2>set the ssbRLMConfigBitmap and / or csi-rsRLMConfigBitmap in measResultLastSen / Cell to include the radio link monitoring configuration of the last serving cell, if available;

[0375] 1 > if available, set the locationinfo as in 5.3.3.7.

[0376] The UE may discard the radio link failure information or handover failure information, i.e. release the UE variable VarRLF-Report, 48 hours after the radio link failure / handover failure is detected.

[0377] NOTE 2: In this clause, the term 'handover failure' has been used to refer to 'reconfiguration with sync failure'.

[0378] ****************************************************************************************** Implementation example 4 of the first embodiments, procedural logic for the successful handover report:

[0379] 5.7.10.6 Actions for the successful handover report determination [Note that the section number is from 3GPP TS 38.331 version 18.4.0.]

[0380] The UE shall for the PCell:

[0381] 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

[0382] 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; or1 > 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; or

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

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

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

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

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

[0388] 3> if the UE is not in SNPN access mode, set the plmn-ldentityList to include the list of EPLMNs stored by the UE (i.e., includes the RPLMN);

[0389] 3>else if the UE is in SNPN access mode, set the snpn-ldentityList to include the list of equivalent SNPNs stored by the UE (i.e., including the registered SNPN identity), if available;

[0390] 3>for intra-NR handover, set the c-RNTI to the C-RNTI assigned by the target PCell of the handover;

[0391] 3> if the procedure is triggered due to successful completion of reconfiguration with sync, for the source PCell in which the last RRCReconfiguration message including reconfigurationWithSync was applied; or

[0392] 3> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, for the source PCell in which the last MobilityFromNRCommand concerning an inter-RAT handover from NR to E-UTRA was applied:

[0393] 4>set the sourcePCelllD in sourceCelllnfo to the global cell identity and tracking area code, if available, of the source PCell;4>set the sourceCellMeas in sourceCellInfo to include the cell level RSRP, RSRQ and the available SINR, of the source PCell based on the available SSB and CSI-RS measurements collected up to the moment the UE sends RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA;

[0394] 4>set the rsIndexResults in sourceCellMeas to include all the available SSB and CSI-RS measurement quantities of the source PCell collected up to the moment the UE sends RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA; 4> if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running:

[0395] 5> set the rlf-lnSourceDAPS in sourceCelllnfo to true,

[0396] 3> if the procedure is triggered due to successful completion of reconfiguration with sync, for the target PCell indicated in the last applied RRCReconfiguration message including reconfigurationWithSync.

[0397] 4>set the targetPCellID in targetCellInfo to the global cell identity and tracking area code, if available, of the target PCell; otherwise, set the targetCell- PCI-ARFCN to the physical cell identity and carrier frequency of the target PCell;

[0398] NOTE 00: If targetCell-PCI-ARFCN is included, it is left to UE implementation how to set the targetPCellID.

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

[0400] 4>set the rsIndexResults in targetCellMeas to include all the available SSB and CSI-RS measurement quantities of the target PCell collected up to the moment the UE sends RRCReconfigurationComplete message; 4> if the last applied RRCReconfiguration message including reconfigurationWithSync was included in the stored condRRCReconfig: 5> set the timeSinceCHO-Reconfig to the time elapsed between the initiation of the execution of conditional reconfiguration for the target PCell and the reception of the last conditionalReconfiguration including the condRRCReconfig of the target PCell in the source PCell;

[0401] 3> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, for the target PCell indicated in the last applied MobilityFromNRCommand concerning an inter-RAT handover from NR to E- UTRA:4>set the targetPCellId in eutra-TargetCellInfo to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell;

[0402] 4>set the targetCellMeas in eutra-TargetCelllnfo to include the cell level RSRP, RSRQ and the available SINR, of the target PCell based on the available measurements collected up to the moment the UE sends RRCConnectionReconfigurationComplete message;

[0403] NOTE 0: If eutra-TargetCellInfo is included, it is left to UE implementation how to set the targetCell Info.

[0404] 3> 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 T304 timer, 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:

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

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

[0407] 3> if the ratio between the value of the elapsed time of the timer T310 and the configured value of the T310 timer, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync or 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 reconfiguration with sync or Mobility from NR to E-UTRA: 4>set t310-cause in shr-Cause to true,

[0408] 3> if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the reconfiguration with sync procedure or 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 T312 timer, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync or 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 reconfiguration with sync, or Mobility from NR to E-UTRA:

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

[0410] 3> if the procedure is triggered due to successful completion of reconfiguration with sync and if sourceDAPS-FailureReporting included in the successHO- Config if configured by the source PCell before executing the last reconfiguration with sync is set to true, and if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running:

[0411] 4>set sourceDAPS-Failure in shr-Cause to true,3> if the procedure is triggered due to successful completion of reconfiguration with sync, for each of the measObjectNR, configured by the source PCell, in which the last RRCReconfiguration message including reconfigurationWithSync was applied;or:

[0412] 3> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, for each of the measObjectNR, configured by the source PCell, in which the last MobilityFromNRCommand concerning an inter-RAT handover from NR to E-UTRA was applied:

[0413] 4> if measRSSI-ReportConfig is configured for the frequency of the source PCell:

[0414] 5> if the procedure is triggered due to successful completion of reconfiguration with sync:

[0415] 6> set the measResultServCellRSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency of the source PCell up to the moment the UE sends the RRCReconfigurationComplete message;

[0416] 5> else if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA:

[0417] 6> set the measResultServCellRSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency of the source PCell up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message;

[0418] 4>for each of the configured measObjectNR if measRSSI-ReportConfig is configured for the configured frequency:

[0419] 5> if the procedure is triggered due to successful completion of reconfiguration with sync:

[0420] 6> set the measResultNeighFreqRSSI in the measResultNeighFreqListRSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the associated neighbouring frequency up to the moment the UE sends the RRCReconfigurationComplete message:

[0421] 7>for each neighbour frequency included, include the optional fields that are available;

[0422] 5> else if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA:

[0423] 6> set the measResultNeighFreqRSSI in the measResultNeighFreqListRSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the associated neighbouring frequency up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message:

[0424] 7>for each neighbour frequency included, include the optional fields that are available;4> if measurements are available for the measObjectNR or the measObjectNR is associated with a reportConfig NR including a condEventT1, condtEvenD1 or condEventD2'.

[0425] 5> if the SS / PBCH block-based measurement quantities are available: 6> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell or target PCell, ordered such that the cell with highest SS / PBCH block RSRP is listed first if SS / PBCH block RSRP measurement results are available, otherwise the cell with highest SS / PBCH block RSRQ is listed first if SS / PBCH block RSRQ measurement results are available, otherwise the cell with highest SS / PBCH block SINR is listed first, based on the available SS / PBCH block based measurements collected up to the moment the UE sends the RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E- UTRA;

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

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

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

[0429] 6> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell and target PCell, ordered such that the cell with highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the cell with highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the cell with highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE sends the RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA;

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

[0431] NOTE 2: For the neighboring cells set ordered based on the CSI-RS measurement quantities, the UE includes measurements only for the cells not yet included in measResultListNR in measResultNeighCells to avoid overriding SS / PBCH block-based ordered measurements.5> if measResultListNR in measResultNeighCells includes fewer than maxCellReport MeasResultNR IEs and the measObjectNR is associated with a reportConfig NR including a condEventT1, condtEvenD1 or condEventD2'.

[0432] 6> for each neighbour cell associated with the measObjectNR for which no measurement Quantities are available:

[0433] 7> if measResultListNR in measResultNeighCells includes fewer than maxCellReport MeasResultNR IEs:

[0434] 8> include a MeasResultNR IE in measResultListNR in measResultNeighCells and leave the resultsSSB-Cell, resultsCSI-RS-Cell and rsIndexResults absent;

[0435] NOTE 3: Neighbouring cells for which no measurement Quantities are available are placed after neighbouring cells for which measurement Quantities are available in measResultListNR in measResultNeighCells.

[0436] 3> if the procedure is triggered due to successful completion of reconfiguration with sync, for each of the measObjectEUTRA, configured by the source PCell in which the last RRCReconfiguration message including reconfigurationWithSync was applied; or:

[0437] 3> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, for each of the measObjectEUTRA, configured by the source PCell in which the last MobilityFromNRCommand concerning an inter-RAT handover from NR to E-UTRA was applied:

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

[0439] 5> set the measResultListEUTRA in measResultNeighCells to include the best measured cells ordered such that the cell with highest RSRP is listed first if RSRP measurement results are available, otherwise the cell with highest RSRQ is listed first, based on measurements collected up to the moment the UE sends the RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA; 5>for each neighbour cell included, include the optional fields that are available;

[0440] 3>for each of the neighbour cells included in measResultNeighCells:

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

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

[0443] 5> set choConfig in MeasResultNR to the execution condition for each measld within condTriggerConfig associated with the neighbour cellwithin the MCG VarConditionalReconfig (Note that for some variations of this implementation example, this statement may be absent.) 3> if available, set the locationinfo as in 5.3.3.7;

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

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

[0446] Implementation example 5 of the first embodiments, procedural logic for the successful PSCell addition or change report:

[0447] 5.7.10.7 Actions for the successful PSCell change or addition report determination [Note that the section number is from 3GPP TS 38.331 version 18.4.0.]

[0448] The UE shall for the PSCell:

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

[0450] 1 > if sn-lnitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is configured and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync for the SCG, is greater than thresholdPercentageT310-SCG included in the successPSCell-Config if configured by the source PSCell before executing the last reconfiguration with sync for the SCG; or

[0451] 1 > if sn-lnitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is configured and if the T312 associated to the measurement identity of the target PSCell was running at the time of initiating the execution of the reconfiguration with sync procedure for the SCG and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312-SCG included in the successPSCell-Config if configured by the source PSCell before executing the last reconfiguration with sync for the SCG:

[0452] 1 > if sn-lnitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is not configured and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync for the SCG, is greater thanthresholdPercentageT310-SCG included in the successPSCell-Config if configured by the PCell before executing the last reconfiguration with sync for the SCG; or > if sn-lnitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is not configured and if the T312 associated to the measurement identity of the target PSCell was running at the time of initiating the execution of the reconfiguration with sync procedure for the SCG and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312-SCG included in the successPSCell-Config if configured by the PCell before executing the last reconfiguration with sync for the SCG:

[0453] 2> clear the information included in VarSuccessPSCell-Report, if any;

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

[0455] 3> if the UE is not in SNPN access mode, set the plmn-ldentityList to include the list of EPLMNs (including the RPLMN) stored by the UE;

[0456] 3>else if the UE is in SNPN access mode, set the snpn-ldentityList to include the list of equivalent SNPN identities (including the registered SNPN identity) stored by the UE, if available;

[0457] 3>set the pCellld to the global cell identity and tracking area code, if available, of the PCell;

[0458] 3>for the source PSCell (in case of PSCell change procedure) in which the last RRCReconfiguration message for the SCG including reconfigurationWithSync was applied:

[0459] 4>set the sourcePSCellld in sourcePSCelllnfo to the global cell identity and tracking area code, and otherwise to the physical cell identity and carrier frequency of the source PSCell;

[0460] 4>set the sourcePSCellMeas in sourcePSCelllnfo to include the cell level RSRP, RSRQ and the available SINR, of the source PSCell based on the available SSB and CSI-RS measurements collected up to the moment the UE successfully completed the random access procedure for the SCG; 4>set the rsIndexResults in sourcePSCellMeas to include all the available SSB and CSI-RS measurement quantities of the source PSCell collected up to the moment the UE successfully completed the random access procedure for the SCG;

[0461] 3>for the target PSCell indicated in the last applied RRCReconfiguration message for the SCG including reconfigurationWithSync.

[0462] 4>set the targetPSCelllD in targetPSCelllnfo to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PSCell;

[0463] 4>set the targetPSCellMeas in targetPSCelllnfo to include the cell level RSRP, RSRQ and the available SINR, of the target PSCell based on theavailable SSB and CSI-RS measurements collected up to the moment the UE successfully completed the random access procedure for the SCG; 4>set the rsIndexResults in targetPSCellMeas to include all the available SSB and CSI-RS measurement quantities of the target PSCell collected up to the moment the UE successfully completed the random access procedure for the SCG;

[0464] 4> if the last applied RRCReconfiguration message for the SCG including reconfigurationWithSync was included in the stored condRRCReconfig: 5> set the timeSinceCPAC-Reconfig to the time elapsed between the initiation of the execution of conditional reconfiguration for the target PSCell and the reception of the last conditionalReconfiguration for the SCG including the condRRCReconfig of the target PSCell;

[0465] 3> if triggering threshold for storing the successful PSCell change or addition information in VarSuccessPSCell-Report based on the thresholdPercentageT304-SCG is met:

[0466] 4>set t304-cause in spr-Cause to true

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

[0468] 3> if triggering threshold for storing the successful PSCell change or addition information in VarSuccessPSCell-Report based on the thresholdPercentageT310-SCG is met:

[0469] 4>set t310-cause in spr-Cause to true

[0470] 3> if triggering threshold for storing the successful PSCell change or addition information in VarSuccessPSCell-Report based on the thresholdPercentageT312-SCG is met:

[0471] 4>set t312-cause in spr-Cause to true]

[0472] 3> if sn-lnitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is configured: 4> consider all measObjectNR configured by the source PSCell;

[0473] 3>else:

[0474] 4> consider all measObjectNR configured by the PCell;

[0475] 3> for each of the considered measObjectNR:

[0476] 4> if measurements are available for the measObjectNR or the measObjectNR is associated with a reportConfi NR including a condEventT1, condtEvenD1 or condEventD2'.

[0477] 5> if the SS / PBCH block-based measurement quantities are available: 6> include in the measResultListNR in measResultNeighCells all the available measurement quantities of the best measured cells, other than the source PSCell (in case of PSCell change procedure) ortarget PSCell, ordered such that the cell with highest SS / PBCH block RSRP is listed first if SS / PBCH block RSRP measurement results are available, otherwise the cell with highest SS / PBCH block RSRQ is listed first if SS / PBCH block RSRQ measurement results are available, otherwise the cell with highest SS / PBCH block SINR is listed first, based on the available SS / PBCH block based measurements collected up to the moment the UE successfully completed the random access procedure;

[0478] 6>for each neighbour cell included, include the optional fields that are available (including the CSI-RS based measurement quantities, if available);

[0479] 5> if the CSI-RS measurement quantities are available for the cells not yet included in measResultListNR in measResultNeighCells:

[0480] 6> include in the measResultListNR in measResultNeighCells all the available measurement quantities of the best measured cells, other than the source PSCell (in case of PSCell change procedure) and target PSCell, ordered such that the cell with highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the cell with highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the cell with highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE successfully completed the random access procedure;

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

[0482] 5> if measResultListNR in measResultNeighCells includes fewer than maxCellReport MeasResultNR lEs and the measObjectNR is associated with a reportConfig NR including a condEventTL condtEvenD1 or condEventD2'.

[0483] 6> for each neighbour cell associated with the measObjectNR for which no measurement Quantities are available:

[0484] 7> if measResultListNR in measResultNeighCells includes fewer than maxCellReport MeasResultNR IEs:

[0485] 8> include a MeasResultNR IE in measResultListNR in measResultNeighCells and leave the resultsSSB-Cell, resultsCSI-RS-Cell and rsIndexResults absent;

[0486] NOTE 1: Neighbouring cells for which no measurement Quantities are available are placed after neighbouring cells for which measurement Quantities are available in measResultListNR in measResultNeighCells.

[0487] 3>for each of the neighbour cells included in measResultNeighCells:

[0488] 4> if the cell was a candidate target cell included in the condRRCReconfig within the conditionalReconfiguration, configured by the source PCell including the condExecutionCond within the conditionalReconfiguration associated to condEventA4 or by the source PSCell (in case of PSCellchange) when the last RRCReconfiguration message for the SCG including reconfigurationWithSync was applied:

[0489] 5> set the choCandidate to true in measResultNR’,

[0490] 5> set choConfig in MeasResultNR to the execution condition for each measld within condTriggerConfig associated with the neighbour cell within the MCG VarConditionalReconfig (Note for some variations of this implementation example, this statement may be absent.)

[0491] 3> if sn-lnitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is configured: 4> if available, set the locationinfo as in 5.3.3.7 according to the otherConfig associated with the source PSCell;

[0492] 4> include sn-lnitiatedPSCellChange',

[0493] 3>else:

[0494] 4> if available, set the locationinfo as in 5.3.3.7 according to the otherConfig associated with the PCell;

[0495] 1> release successPSCell-Config configured by the source PSCell if available and thresholdPercentageT304 if configured by the target PSCell.

[0496] The UE may discard the successful PSCell change or addition information, i.e., release the UE variable VarSuccessPSCell-Report, 48 hours after the last successful PSCell change or addition information is added to the VarSuccessPSCell-Report or upon deregistration from the network as specified in TS 23.502

[0043] ,

[0497] Some second embodiments

[0498] To address the problems described above, some second embodiments comprise logging time- or location-based CHO-related information by the UE and report this information to the network in one or more other field(s) in the concerned SON report(s) outside the measResultNeighCells field.

[0499] With this solution, the UE configured with the time- or location- based CHO may log in a SON report one or more of the following information items:

[0500] - A cell list indicating the time- or location-based CHO configured candidate cells. - A cell list indicating the time- or location-based CHO configured candidate cells if there is no available RRM measurement.

[0501] - A list indicating the time- or location-based CHO configuration for each candidate cell.

[0502] - A list indicating the time- or location-based CHO configuration for each candidate cell if there is no available RRM measurement.

[0503] Non-limiting example implementations of the above solution are given below by modification of TS 38.331 v18.4.0. Please note that the modifications are underlined.****************************************************************************************** Implementation example 1 of second embodiments, procedural logic for the RLF report: 5.3.10.5 RLF report content determination [Note that the section number is from 3GPP TS 38.331 version 18.4.0.]

[0504] The UE shall determine the content in the VarRLF-Report as follows:

[0505] 1> clear the information included in VarRLF-Report, if any;

[0506] 1> if the UE is not in SNPN access mode, set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e. including the RPLMN);

[0507] 1> else if the UE is in SNPN access mode, set the snpn-IdentityList to include the list of equivalent SNPNs stored by the UE (i.e., including the registered SNPN identity);

[0508] 1> set the measResultLastServCell to include the cell level RSRP, RSRQ and the available SINR, of the source PCell (in case HO failure) or PCell (in case RLF) based on the available SSB and CSI-RS measurements collected up to the moment the UE detected failure;

[0509] 1> if measRSSI-ReportConfig is configured for the measObject indicated as the servingCellMO of the source PCell (in case HO failure) or PCell (in case of RLF), set the measResultLastServCellRSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency of the source PCell (in case HO failure) or PCell (in case of RLF) up to the moment the UE detected the failure;

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

[0511] 2> set the rsIndexResults in measResultLastServCell to include all the available measurement quantities of the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the highest SS / PBCH block RSRP is listed first if SS / PBCH block RSRP measurement results are available, otherwise the highest SS / PBCH block RSRQ is listed first if SS / PBCH block RSRQ measurement results are available, otherwise the highest SS / PBCH block SINR is listed first, based on the available SS / PBCH block based measurements collected up to the moment the UE detected failure;

[0512] 1> if the CSI-RS based measurement quantities are available:

[0513] 2> set the rsIndexResults in measResultLastServCell to include all the available measurement quantities of the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE detected failure;

[0514] 1> for each of the configured measObjectNR in which measurements are available:

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

[0516] 3> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the cell with highest SS / PBCH block RSRP is listed first if SS / PBCH block RSRP measurement results are available, otherwise the cell with highest SS / PBCH block RSRQ is listed first if SS / PBCH block RSRQ measurement results are available, otherwise the cell with highest SS / PBCH block SINR is listed first, based on the available SS / PBCH block based measurements collected up to the moment the UE detected failure;

[0517] 4> for each neighbour cell included, include the optional fields that are available;NOTE 0a: For the neighboring cells included in measResultListNR in measResultNeighCells ordered based on the SS / PBCH block measurement quantities, UE also includes the CSI-RS based measurement quantities, if available.

[0518] 2> if the CSI-RS based measurement quantities are available:

[0519] 3> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the cell with highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the cell with highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the cell with highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE detected radio link failure;

[0520] 4> for each neighbour cell included, include the optional fields that are available; NOTE 0b: For ordering the neighboring cells based on the CSI-RS measurement quantities, UE includes measurements only for the cells not yet included in measResultListNR in measResultNeighCells to avoid overriding SS / PBCH block-based ordered measurements.

[0521] 2> for each neighbour cell, if any, included in measResultListNR in measResultNeighCells:

[0522] 3 > if the UE supports RLF-Report for conditional handover and if the neighbour cell is one of the candidate cells for which the reconfigurationWithSync is included in the masterCellGroup in the MCG VarConditionalReconfig at the moment of the detected failure:

[0523] 4> set choConfig in MeasResult2NR to the execution condition for each measld within condTriggerConfig associated to the neighbour cell within the MCG VarConditionalReconfig;

[0524] 4> if the first entry of choConfig corresponds to a fulfilled execution condition at the moment of handover failure, or radio link failure; or

[0525] 4> if the second entry of choConfig, if available, corresponds to a fulfilled execution condition at the moment of handover failure, or radio link failure:

[0526] 5> set firstTriggeredEvent to the execution condition condFirstEvent corresponding to the first entry of choConfig or to the execution condition condSecondEvent corresponding to the second entry of choConfig, whichever execution condition was fulfilled first in time;

[0527] 5> set timeBetweenEvents to the elapsed time between the point in time of fulfilling the condition in choConfig that was fulfilled first in time, and the point in time of fulfilling the condition in choConfig that was fulfilled second in time, if both the first execution condition corresponding to the first entry and the second execution condition corresponding to the second entry in the choConfig were fulfilled;

[0528] 1> for each of the configured measObjectNR associated with neighboring cells if the associated reportConfigNR includes measRSSI-ReportConfig'.

[0529] 2> set the measResultNeighFreqRSSI in the measResultNeighFreqListRSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequencies other than the frequency of the source PCell (in case HO failure) or of the PCell (in case RLF), up to the moment the UE detected failure:

[0530] 3> for each neighbour frequency included, include the optional fields that are available;1> for each of the configured EUTRA frequencies in which measurements are available;

[0531] 2> set the measResultListEUTRA in measResultNeighCells to include the best measured cells ordered such that the cell with highest RSRP is listed first if RSRP measurement results are available, otherwise the cell with highest RSRQ is listed first, and based on measurements collected up to the moment the UE detected failure;

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

[0533] NOTE 1: The measured quantities are filtered by the L3 filter as configured in the mobility measurement configuration. The measurements are based on the time domain measurement resource restriction, if configured. Exclude-listed cells are not required to be reported.

[0534] 1> set the c-RNTI to the C-RNTI used in the source PCell (in case HO failure) or PCell (in case RLF);

[0535] 1> if the failure is detected due to reconfiguration with sync failure as described in 5.3.5.8.3, set the fields in VarRLF-Report as follows:

[0536] 2> set the connectionFailureType to hof

[0537] 2> if the UE supports RLF-Report for DAPS handover and if any DAPS bearer was configured while T304 was running:

[0538] 3> set lastHO-Type to daps',

[0539] 3 > if radio link failure was detected in the source PCell, according to clause 5.3.10.3:

[0540] 4> set timeConnSourceDAPS-Failure to the time between the initiation of the DAPS handover execution and the radio link failure detected in the source PCell while T304 was running;

[0541] 4> set the rlf-Cause to the trigger for detecting the source radio link failure in accordance with clause 5.3.10.4;

[0542] 2> if the UE supports RLF-Report for conditional handover and if configuration of the conditional handover is available in the MCG VarConditionalReconfig at the moment of the handover failure: 3 > if the UE executed a conditional handover toward target PCell according to the condRRCReconfig of the target PCell:

[0543] 4> set timeSinceCHO-Reconfig to the time elapsed between the execution of the last RRCReconfiguration message including reconfigurationWithSync for the target PCell of the failed conditional handover, and the reception in the source PCell of the last conditionalReconfiguration including the condRRCReconfig of the target PCell of the failed conditional handover;

[0544] 3> else:

[0545] 4> set timeSinceCHO-Reconfig to the time elapsed between the execution of the last RRCReconfiguration message including reconfigurationWithSync for the target PCell of the failed handover, and the reception in the source PCell of the last conditionalReconfiguration including the condRRCReconfig,'

[0546] 3> set choCandidateCellList to include the global cell identity, if available, and otherwise to the physical cell identity and carrier frequency of each of the candidate target cells for conditional handover included in condRRCReconfig within the MCG VarConditionalReconfig at the time of the failed handover, excluding the candidate target cells included in measResultNeighCells',3> set choConfigCellList to include the execution condition for each measld within condTriggerConfig associated to the candidate target cells within the MCG VarConditionalReconfig at the time of the failed handover, excluding the candidate target cells included in measResultNeighCell',

[0547] 2> if the UE supports RLF-Report for conditional handover and if the last executed RRCReconfiguration message including reconfigurationWithSync was concerning a conditional handover:

[0548] 3> set lastHO-Type to c / zo;

[0549] 2> set the nrFailedPCellld in failedPCellld to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell of the failed handover;

[0550] 2> include nrPreviousCell in previousPCellld and set it to the global cell identity and tracking area code of the PCell where the last RRCReconfiguration message including reconfigurationWithSync was received;

[0551] 2> set the timeConnFailure to the elapsed time since the execution of the last RRCReconfiguration message including the reconfigurationWithSync,

[0552] > else if the failure is detected due to Mobility from NR failure as described in 5.4.3.5, set the fields in VarRLF-Report as follows:

[0553] 2> set the connectionFailureType to hofi

[0554] 2> if last MobilityFromNRCommand concerned a failed inter-RAT handover from NR to E-UTRA and if the UE supports Radio Link Failure Report for Inter-RAT MRO EUTRA (NR to EUTRA): 3> set the eutraFailedPCellld in failedPCellld to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell of the failed handover;

[0555] 2> include nrPreviousCell in previousPCellld and set it to the global cell identity and tracking area code of the PCell where the last MobilityFromNRCommand message was received;

[0556] 2> set the timeConnFailure to the elapsed time since the initialization of the handover associated to the last MobilityFromNRCommand message;

[0557] 2> if the UE supports RLF report for inter-system handover for voice fallback and if voiceFallbacklndication is included in the last MobilityFromNRCommand.

[0558] 3> include the voiceFallbackHO;

[0559] > else if the failure is detected due to radio link failure as described in 5.3.10.3, set the fields in VarRLF-Report as follows:

[0560] 2> set the connectionFailureType to rlfi

[0561] 2> set the rlf-Cause to the trigger for detecting radio link failure in accordance with clause 5.3.10.4; 2> set the nrFailedPCellld in failedPCellld to the global cell identity and the tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the PCell where radio link failure is detected;

[0562] 2> if an RRCReconfiguration message including the reconfigurationWithSync was received before the connection failure:

[0563] 3> if the last successfully executed RRCReconfiguration message including the reconfigurationWithSync concerned an intra NR handover and it was received while connectedto the previous PCell to which the UE was connected before connecting to the PCell where radio link failure is detected; and

[0564] 3> if T316 was not running before entering the PCell in which the radio link failure was detected; and

[0565] 3> if T311 was not running before entering the PCell in which the radio link failure was detected: 4> include the nrPreviousCell in previousPCellld and set it to the global cell identity and the tracking area code of the PCell where the last executed RRCReconfiguration message including reconfigurationWithSync was received; 4> if the last executed RRCReconfiguration message including reconfigurationWithSync was concerning a DAPS handover:

[0566] 5> set lastHO-Type to daps,'

[0567] 4> else if the last executed RRCReconfiguration message including reconfigurationWithSync was concerning a conditional handover:

[0568] 5> set lastHO-Type to cho'.

[0569] 4> set the timeConnFailure to the elapsed time since the execution of the last RRCReconfiguration message including the reconfigurationWithSync,

[0570] 3> else if the last RRCReconfiguration message including the reconfigurationWithSync concerned a handover to NR from E-UTRA and if the UE supports Radio Link Failure Report for Inter- RAT MRO EUTRA:

[0571] 4> include the eutraPreviousCell in previousPCellld and set it to the global cell identity and the tracking area code of the E-UTRA PCell where the last RRCReconfiguration message including reconfigurationWithSync was received embedded in E-UTRA RRC message MohilityFromEUTRACommand message as specified in TS 36.331

[0010] clause 5.4.3.3;

[0572] 4> set the timeConnFailure to the elapsed time since reception of the last RRCReconfiguration message including the reconfigurationWithSync embedded in E-UTRA RRC message MohilityFromEUTRACommand message as specified in TS 36.331

[0010] clause 5.4.3.3;

[0573] > if configuration of the conditional handover is available in the MCG VarConditionalReconfig at the moment of declaring the radio link failure:

[0574] 3> set timeSinceCHO-Reconfig to the time elapsed between the detection of the radio link failure, and the reception, in the source PCell, of the last conditionalReconfiguration including the condRRCReconfig message;

[0575] 3> set choCandidateCellList to include the global cell identity if available, and otherwise to the physical cell identity and carrier frequency of each of all the candidate target cells for conditional handover included in condRRCReconfig within the MCG VarConditionalReconfig at the time of radio link failure, excluding the candidate target cells included in measResultNeighCells',

[0576] 3> set choConfigCellList to include the execution condition for each measld within condTriggerConfig associated to the candidate target cells within the MCG VarConditionalReconfig at the time of radio link failure, excluding the candidate target cells included in measResultNeighCell;1> if connectionFailureType is / 7 / and the rlf-Cause is set to randomAccessProblem or beamFailureRecoveryFailure,' or

[0577] 1> if connectionFailureType is rlf and the rlf-Cause is set to IbtFailure and the radio link failure is detected during the random access procedure; or

[0578] 1> if connectionFailureType is hof and if the failed handover is an intra-RAT handover:

[0579] 2> set the ra-InformationCommon to include the random-access related information as described in clause 5.7.10.5;

[0580] 1> if connectionFailureType is rlf and the rlf-Cause is set to IbtFailure, and the radio link failure is not detected during the random access procedure:

[0581] 2> set the locationAndBandwidth and subcarrierSpacing in bwp-Info associated to the UL BWP in which the consistent uplink LBT failure was detected;

[0582] 1> if the rlf-Cause is set to t310-Expiry or t312-Expiry.

[0583] 2> set the ssbRLMConfigBitmap and / or csi-rsRLMConfigBitmap in measResultLastServCell to include the radio link monitoring configuration of the last serving cell, if available;

[0584] 1> if available, set the locationinfo as in 5.3.3.7.

[0585] The UE may discard the radio link failure information or handover failure information, i.e. release the UE variable VarRLF-Report, 48 hours after the radio link failure / handover failure is detected. NOTE 2: In this clause, the term 'handover failure' has been used to refer to 'reconfiguration with sync failure'.

[0586] ******************************************************************************************

[0587] Implementation example 2 of the second embodiments, procedural logic for the successful handover report:

[0588] 5.7.10.6 Actions for the successful handover report determination [Note that the section number is from 3GPP TS 38.331 version 18.4.0.]

[0589] The UE shall for the PCell:

[0590] 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

[0591] 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

[0592] 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 thelast 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

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

[0594] 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

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

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

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

[0598] 3> if the UE is not in SNPN access mode, set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e., includes the RPLMN);

[0599] 3> else if the UE is in SNPN access mode, set the snpn-IdentityList to include the list of equivalent SNPNs stored by the UE (i.e., including the registered SNPN identity), if available;

[0600] 3> for intra-NR handover, set the c-RNTI to the C-RNTI assigned by the target PCell of the handover;

[0601] 3> if the procedure is triggered due to successful completion of reconfiguration with sync, for the source PCell in which the last RRCReconfiguration message including reconfigurationWithSync was applied; or

[0602] 3> if the procedure is triggered due to successful completion of Mobility from NR to E- UTRA, for the source PCell in which the last MobilityFromNRCommand concerning an inter-RAT handover from NR to E-UTRA was applied:

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

[0604] 4> set the sourceCellMeas in sourceCelllnfo to include the cell level RSRP, RSRQ and the available SINR, of the source PCell based on the available SSB and CSI- RS measurements collected up to the moment the UE sends RRCReconfigurationComplete message if the procedure is triggered due tosuccessful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E- UTRA;

[0605] 4> set the rsIndexResults in sourceCellMeas to include all the available SSB and CSI- RS measurement quantities of the source PCell collected up to the moment the UE sends RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E- UTRA;

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

[0607] 5> set the rlf-InSourceDAPS in sourceCellInfo to true;

[0608] 3> if the procedure is triggered due to successful completion of reconfiguration with sync, for the target PCell indicated in the last applied RRCReconfiguration message including reconfigurationWithSync.

[0609] 4> set the targetPCellID in targetCellInfo to the global cell identity and tracking area code, if available, of the target PCell; otherwise, set the targetCell-PCI-ARFCN to the physical cell identity and carrier frequency of the target PCell;

[0610] NOTE 00: If targetCell-PCI-ARFCN is included, it is left to UE implementation how to set the targetPCellID.

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

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

[0613] 4> if the last applied RRCReconfiguration message including reconfigurationWithSync was included in the stored condRRCReconfig:

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

[0615] 3> if the procedure is triggered due to successful completion of Mobility from NR to E- UTRA, for the target PCell indicated in the last applied MobilityFromNRCommand concerning an inter-RAT handover from NR to E-UTRA:

[0616] 4> set the targetPCellId in eutra-TargetCellInfo to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell;

[0617] 4> set the targetCellMeas in eutra-TargetCelllnfo to include the cell level RSRP, RSRQ and the available SINR, of the target PCell based on the availablemeasurements collected up to the moment the UE sends RRCConnectionReconfigurationComplete message;

[0618] NOTE 0: If eutra-TargetCellInfo is included, it is left to UE implementation how to set the targetCelllnfo.

[0619] 3> 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 T304 timer, 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:

[0620] 4> set t304-cause in shr-Cause to true;

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

[0622] 3> if the ratio between the value of the elapsed time of the timer T310 and the configured value of the T310 timer, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync or 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 reconfiguration with sync or Mobility from NR to E-UTRA:

[0623] 4> set t310-cause in shr-Cause to true;

[0624] 3> if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the reconfiguration with sync procedure or 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 T312 timer, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync or 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 reconfiguration with sync, or Mobility from NR to E-UTRA:

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

[0626] 3> if the procedure is triggered due to successful completion of reconfiguration with sync and if sourceDAPS-FailureReporting included in the successHO-Config if configured by the source PCell before executing the last reconfiguration with sync is set to true, and if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running:

[0627] 4> set sourceDAPS-Failure in shr-Cause to true;

[0628] 3> if the procedure is triggered due to successful completion of reconfiguration with sync, for each of the measObjectNR, configured by the source PCell, in which the last RRCReconfiguration message including reconfigurationWithSync was applied;or: 3> if the procedure is triggered due to successful completion of Mobility from NR to E- UTRA, for each of the measObjectNR, configured by the source PCell, in which the last MobilityFromNRCommand concerning an inter-RAT handover from NR to E- UTRA was applied:> if measRSSI-ReportConfig is configured for the frequency of the source PCell: 5> if the procedure is triggered due to successful completion of reconfiguration with sync:

[0629] 6> set the measResultServCellRSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency of the source PCell up to the moment the UE sends the RRCReconfigurationComplete message;

[0630] 5> else if the procedure is triggered due to successful completion of Mobility from NRto E-UTRA:

[0631] 6> set the measResultServCellRSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency of the source PCell up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message;

[0632] > for each of the configured measObjectNR if measRSSI-ReportConfig is configured for the configured frequency:

[0633] 5> if the procedure is triggered due to successful completion of reconfiguration with sync:

[0634] 6> set the measResultNeighFreqRSSI in the measResultNeighFreqListRSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the associated neighbouring frequency up to the moment the UE sends the RRCReconfigurationComplete message:

[0635] 7> for each neighbour frequency included, include the optional fields that are available;

[0636] 5> else if the procedure is triggered due to successful completion of Mobility from NRto E-UTRA:

[0637] 6> set the measResultNeighFreqRSSI in the measResultNeighFreqListRSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the associated neighbouring frequency up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message: 7> for each neighbour frequency included, include the optional fields that are available;

[0638] > if measurements are available for the measObjectNR:

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

[0640] 6> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell or target PCell, ordered such that the cell with highest SS / PBCH block RSRP is listed first if SS / PBCH block RSRP measurement results are available, otherwise the cell with highest SS / PBCH block RSRQ is listed first if SS / PBCH block RSRQ measurement results are available, otherwise the cell with highest SS / PBCH block SINR is listed first, based on the available SS / PBCH block based measurements collected up to the moment the UE sends the RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration withsync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA; 6> for each neighbour cell included, include the optional fields that are available;

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

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

[0643] 6> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell and target PCell, ordered such that the cell with highest CSI- RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the cell with highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the cell with highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE sends the RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA; 6> for each neighbour cell included, include the optional fields that are available;

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

[0645] 3> if the procedure is triggered due to successful completion of reconfiguration with sync, for each of the measObjectEUTRA, configured by the source PCell in which the last RRCReconfiguration message including reconfigurationWithSync was applied; or: 3> if the procedure is triggered due to successful completion of Mobility from NR to E- UTRA, for each of the measObjectEUTRA, configured by the source PCell in which the last MobilityFromNRCommand concerning an inter-RAT handover from NR to E- UTRA was applied:

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

[0647] 5> set the measResultListEUTRA in measResultNeighCells to include the best measured cells ordered such that the cell with highest RSRP is listed first if RSRP measurement results are available, otherwise the cell with highest RSRQ is listed first, based on measurements collected up to the moment the UE sends the RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E- UTRA;

[0648] 5> for each neighbour cell included, include the optional fields that are available;3> for each of the neighbour cells included in measResultNeighCells:

[0649] 4> if the cell was a candidate target cell included in the condRRCReconfig within the conditionalReconfiguration configured by the source PCell, in which the last RRCReconfiguration message including reconfigurationWithSync was applied: 5> set the choCandidate to true in measResultNR;

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

[0651] 3> if the procedure is triggered due to successful completion of reconfiguration with sync, and the last applied RRCReconfiguration message including reconfigurationWithSync was concerning a conditional handover:

[0652] 4> set choCandidateCellList to include the global cell identity if available, and otherwise to the physical cell identity and carrier frequency of each of all the candidate target cells for time- or location-based conditional handover included in condRRCReconfig within the MCG VarConditionalReconfig, excluding the candidate target cells included in measResultNeighCells: (In some variations of this implementation example, choCandidateCellList is set to include the identity of all the concerned candidate target cells that are not included in measResultNeighCells, regardless of which condEvent(s) are included in their respective associated reportConfigNR.)

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

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

[0655] Implementation example 3 of the second embodiments, ASN.1 code for the RLF report and the successful handover report:

[0656] RLF-Report-rl6 CHOICE { nr-RLF-Report-r16 SEQUENCE { measResultLastServCell-r16 MeasResultRLFNR-r16, measResultNeighCells-r16 SEQUENCE { measResultListNR-r16 MeasResultList2NR-r16 OPTIONAL, measResultListEUTRA-r16 MeasResultList2EUTRA-r16 OPTIONAL } OPTIONAL, c-RNTI-r16 RNTI-Value, previousPCellId-r16 CHOICE { nrPreviousCell-r16 CGI-Info-Logging-r16, eutraPreviousCell-r16 CGI-InfoEUTRALogging } OPTIONAL, failedPCellId-r16 CHOICE { nrFailedPCellId-r16 CHOICE { cellGlobalId-r16 CGI-Info-Logging-r16, pci-arfcn-r16 PCI-ARFCN-NR-r16 eutraFailedPCellId-r16 CHOICE { cellGlobalId-r16 CGI-InfoEUTRALogging, pci-arfcn-r16 PCI-ARFCN-EUTRA-r16 } reconnectCellld-r 16 CHOICE { nrReconnectCellId-r16 CGI-Info-Logging-r16, eutraReconnectCellId-r16 CGI-InfoEUTRALogging } OPTIONAL, timeUntilReconnection-r16 TimeUntilReconnection-r16 O

[0657]

[0658] PTIONAL,reestablishmentCellId-r16 CGI-Info-Logging-r16

[0659] OPTIONAL,

[0660] timeConnFailure-r16 INTEGER (0..1023)

[0661] OPTIONAL,

[0662] timeSinceFailure-r16 TimeSinceFailure-r16,

[0663] connectionFailureType-r16 ENUMERATED { rlf, hof },

[0664] rlf-Cause-r16 ENUMERATED { t310-Expiry, randomAccessProblem, rlc-MaxNumRetx,

[0665] beamFailureRecoveryFailure, lbtFailure-r16,

[0666] bh-rlfRecoveryFailure, t312-expiry-r17, spare1 },

[0667] locationInfo-r16 LocationInfo-r16

[0668] OPTIONAL,

[0669] noSuitableCellFound-r16 ENUMERATED { true }

[0670] OPTIONAL,

[0671] ra-InformationCommon-r16 RA-InformationCommon-r16

[0672] OPTIONAL,

[0673] [ [

[0674] csi-rsRLMConfigBitmap-v1650 BIT STRING (SIZE (96))

[0675] OPTIONAL

[0676] ] ]r

[0677] [ [

[0678] lastHO-Type-r17 ENUMERATED { cho, daps, spare2, spare1 } OPTIONAL,

[0679] timeConnSourceDAPS-Failure-r17 TimeConnSourceDAPS-Failure-r17

[0680] OPTIONAL,

[0681] timeSinceCHO-Reconfig-r17 TimeSinceCHO-Reconfig-r17

[0682] OPTIONAL,

[0683] choCellId-r17 CHOICE {

[0684] cellGlobalId-r17 CGI-Info-Logging-r16,

[0685] pci-arfcn-r17 PCI-ARFCN-NR-r16

[0686] }

[0687] OPTIONAL,

[0688] choCandidateCellList-r17 ChoCandidateCellList-r17

[0689] OPTIONAL

[0690] ] ],

[0691] [ [

[0692] pSCellId-r18 CHOICE {

[0693] cellGlobalId-r18 CGI-Info-Logging-r16,

[0694] pci-arfcn-r18 PCI-ARFCN-NR-r16

[0695] }

[0696] OPTIONAL,

[0697] mcg-RecoveryFailureCause-r18 ENUMERATED { t316-Expiry, scg-Deactivated, spare2, spare1 } OPTIONAL,

[0698] scg-FailureCause-r18 ENUMERATED { t310-Expiry, randomAccessProblem, rlc-MaxNumRetx,

[0699] synchReconfigFailureSCG, scg-ReconfigFailure,

[0700] srb3-IntegrityFailure, scg-lbtFailure, beamFailureRecoveryFailure,

[0701] t312-Expiry, bh-RLF, beamFailure, spare5, spare4, spare3, spare2, spare1 }

[0702] OPTIONAL,

[0703] elapsedTimeSCG-Failure-r18 ElapsedTimeSCG-Failure-r18

[0704] OPTIONAL,

[0705] voiceFallbackHO-r18 ENUMERATED { true }

[0706] OPTIONAL,

[0707] measResultLastServCellRSSI-r18 RSSI-Range-r16

[0708] OPTIONAL,

[0709] measResultNeighFreqListRSSI-r18 MeasResultNeighFreqListRSSI-r18

[0710] OPTIONAL,

[0711] bwp-Info-r18 AttemptedBWP-Info-r18

[0712] OPTIONAL,

[0713] elapsedTimeT316-r18 ElapsedTimeT316-r18

[0714] OPTIONAL,

[0715] scg-FailedAfterMCG-r18 ENUMERATED { true }

[0716] OPTIONAL

[0717] ] ],

[0718] [ [

[0719] choConfigCellList-r19 ChoConfigCellList-r19

[0720] OPTIONAL] ]

[0721] },

[0722] eutra-RLF-Report-r 16 SEQUENCE {

[0723] failedPCellId-EUTRA CGI-InfoEUTRALogging, measResult-RLF-Report-EUTRA-rl6 OCTET STRING,

[0724] [ [

[0725] measResult-RLF-Report-EUTRA-vl690 OCTET STRING

[0726] OPTIONAL

[0727] ] ]

[0728] }

[0729] SuccessHO-Report-r17 ::= SEQUENCE {

[0730] sourceCellInfo-r17 SEQUENCE {

[0731] sourcePCellId-r17 CGI-Info-Logging-r16, sourceCellMeas-r17 MeasResultSuccessHONR-r17 OPTIONAL,

[0732] rlf-InSourceDAPS-r17 ENUMERATED { true } OPTIONAL

[0733] b

[0734] targetCellInfo-r17 SEQUENCE {

[0735] targetPCellId-r17 CGI-Info-Logging-r16, targetCellMeas-r17 MeasResultSuccessHONR-r17 OPTIONAL

[0736] measResultNeighCells-r17 SEQUENCE {

[0737] measResultListNR-r17 MeasResultList2NR-r17 OPTIONAL,

[0738] measResultListEUTRA-r17 MeasResultList2EUTRA-r17 OPTIONAL

[0739] }

[0740] OPTIONAL,

[0741] locationInfo-r17 LocationInfo-r16

[0742] OPTIONAL,

[0743] timeSinceCHO-Reconfig-r17 TimeSinceCHO-Reconfig-r17 OPTIONAL,

[0744] shr-Cause-r17 SHR-Cause-r17

[0745] OPTIONAL,

[0746] ra-InformationCommon-r17 RA-InformationCommon-r17 OPTIONAL,

[0747] upInterruptionTimeAtHO-r17 UPInterruptionTimeAtHO-r17 OPTIONAL,

[0748] c-RNTI-r17 RNTI-Value

[0749] OPTIONAL,

[0750] [ [

[0751] targetCell-PCI-ARFCN-r17 PCI-ARFCN-NR-r16

[0752] OPTIONAL

[0753] ] ],

[0754] [ [

[0755] eutra-TargetCellInfo-r18 SEQUENCE {

[0756] targetPCellId-r18 CHOICE {

[0757] cellGlobalId-r18 CGI-Info-Logging-r16, pci-arfcn-r18 PCI-ARFCN-EUTRA-r16 targetCellMeas-r18 MeasQuantityResultsEUTRA OPTIONAL

[0758] }

[0759] OPTIONAL,

[0760] measResultServCellRSSI-r18 RSSI-Range-r16

[0761] OPTIONAL,

[0762] measResultNeighFreqListRSSI-r18 MeasResultNeighFreqListRSSI-r18 OPTIONAL,

[0763] eutra-C-RNTI-r18 EUTRA-C-RNTI

[0764] OPTIONAL,

[0765] timeSinceSHR-r18 TimeSinceSHR-r18

[0766] OPTIONAL }

[0767] }

[0768] choCandidateCellList-r19 ChoCandidateCellList-r17

[0769] OPTIONALChoCandidateCellList-r17 ::= SEQUENCE (SIZE (1..maxNrofCondCells-r16)) OF ChoCandiateCell-r17

[0770] ChoCandidateCell-r17 ::= CHOICE {

[0771] cellGlobalId-r17 CGI-Info-Logging-r16,

[0772] pci-arfcn-r17 PCI-ARFCN-NR-r16

[0773] }

[0774] ChoConfigCellList-rl9 _ SEQUENCE ( SIZE ( 1 ■ ■ maxNrof CondCells-r 16 ) ) OF ChoConfigPerCell-rl9 ChoConfigPerCell-rl9: _ SEQUENCE { cellld-rl9 _ CHOICE { cellGlobalId-r17 CGI-Info-Logging-r16, _ pci-ar f cn-r 17 _ PCI-ARFCN-NR-rl6 _ }, choConfig-rl9 _ SEQUENCE ( SIZE ( 1..2 ) ) OF CondTriggerConfig-rl6 1

[0775]

[0776] _ RLF-Report field descriptions _

[0777] choConfigCellList

[0778] This field is used to indicate the list of candidate target cells and associated time- or location-based conditional handover execution conditions for each measld within condTriggerConfig associated to the cell at the time of connection failure. The field does not include the candidate target cells included in

[0779]

[0780] measResultNeighCells.

[0781] _ SuccessHO-Report field descriptions _

[0782] choCandidateCellList

[0783] This field is used to indicate the list of candidate target cells for time- or location-based conditional handover included in condRRCReconfig at the time of handover. The field does not include the candidate target cells included in measResultNeighCells.

[0784] [In a variation of this implementation example, choCandidateCellList includes the identity of all the concerned candidate target cells that are not included in measResultNeighCells, regardless of which

[0785]

[0786] condEvent(s) are included in their respective associated reportConfigNR.] ******************************************************************************************

[0787] Implementation example 4 of the second embodiments, procedural logic for the RLF report:

[0788] 5.3.10.5 RLF report content determination [Note that the section number is from 3GPP TS 38.331 version 18.4.0.]

[0789] The UE shall determine the content in the VarRLF-Report as follows:

[0790] 1> clear the information included in VarRLF-Report, if any;

[0791] 1> if the UE is not in SNPN access mode, set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e. including the RPLMN);

[0792] 1> else if the UE is in SNPN access mode, set the snpn-IdentityList to include the list of equivalent SNPNs stored by the UE (i.e., including the registered SNPN identity);

[0793] 1> set the measResultLastServCell to include the cell level RSRP, RSRQ and the available SINR, of the source PCell (in case HO failure) or PCell (in case RLF) based on the available SSB and CSI-RS measurements collected up to the moment the UE detected failure;

[0794] 1> if measRSSI-ReportConfig is configured for the measObject indicated as the servingCellMO of the source PCell (in case HO failure) or PCell (in case of RLF), set themeasResultLastServCellRSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency of the source PCell (in case HO failure) or PCell (in case of RLF) up to the moment the UE detected the failure;

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

[0796] 2> set the rsIndexResults in measResultLastServCell to include all the available measurement quantities of the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the highest SS / PBCH block RSRP is listed first if SS / PBCH block RSRP measurement results are available, otherwise the highest SS / PBCH block RSRQ is listed first if SS / PBCH block RSRQ measurement results are available, otherwise the highest SS / PBCH block SINR is listed first, based on the available SS / PBCH block based measurements collected up to the moment the UE detected failure;

[0797] 1> if the CSI-RS based measurement quantities are available:

[0798] 2> set the rsIndexResults in measResultLastServCell to include all the available measurement quantities of the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE detected failure;

[0799] 1> for each of the configured measObjectNR in which measurements are available:

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

[0801] 3> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the cell with highest SS / PBCH block RSRP is listed first if SS / PBCH block RSRP measurement results are available, otherwise the cell with highest SS / PBCH block RSRQ is listed first if SS / PBCH block RSRQ measurement results are available, otherwise the cell with highest SS / PBCH block SINR is listed first, based on the available SS / PBCH block based measurements collected up to the moment the UE detected failure;

[0802] 4> for each neighbour cell included, include the optional fields that are available; NOTE 0a: For the neighboring cells included in measResultListNR in measResultNeighCells ordered based on the SS / PBCH block measurement quantities, UE also includes the CSI-RS based measurement quantities, if available.

[0803] 2> if the CSI-RS based measurement quantities are available:

[0804] 3> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the cell with highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the cell with highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the cell with highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE detected radio link failure;

[0805] 4> for each neighbour cell included, include the optional fields that are available; NOTE 0b: For ordering the neighboring cells based on the CSI-RS measurement quantities, UE includes measurements only for the cells not yet included in measResultListNR in measResultNeighCells to avoid overriding SS / PBCH block-based ordered measurements.2> for each neighbour cell, if any, included in measResultListNR in measResultNeighCells:

[0806] 3 > if the UE supports RLF-Report for conditional handover and if the neighbour cell is one of the candidate cells for which the reconfigurationWithSync is included in the masterCellGroup in the MCG VarConditionalReconfig at the moment of the detected failure:

[0807] 4> set choConfig in MeasResult2NR to the execution condition for each measld within condTriggerConfig associated to the neighbour cell within the MCG VarConditionalReconfig;

[0808] 4> if the first entry of choConfig corresponds to a fulfilled execution condition at the moment of handover failure, or radio link failure; or

[0809] 4> if the second entry of choConfig, if available, corresponds to a fulfilled execution condition at the moment of handover failure, or radio link failure:

[0810] 5> set firstTriggeredEvent to the execution condition condFirstEvent corresponding to the first entry of choConfig or to the execution condition condSecondEvent corresponding to the second entry of choConfig, whichever execution condition was fulfilled first in time;

[0811] 5> set timeBetweenEvents to the elapsed time between the point in time of fulfilling the condition in choConfig that was fulfilled first in time, and the point in time of fulfilling the condition in choConfig that was fulfilled second in time, if both the first execution condition corresponding to the first entry and the second execution condition corresponding to the second entry in the choConfig were fulfilled;

[0812] 1> for each of the configured measObjectNR associated with neighboring cells if the associated reportConfigNR includes measRSSI-ReportConfig'.

[0813] 2> set the measResultNeighFreqRSSI in the measResultNeighFreqListRSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequencies other than the frequency of the source PCell (in case HO failure) or of the PCell (in case RLF), up to the moment the UE detected failure:

[0814] 3> for each neighbour frequency included, include the optional fields that are available;

[0815] 1> for each of the configured EUTRA frequencies in which measurements are available;

[0816] 2> set the measResultListEUTRA in measResultNeighCells to include the best measured cells ordered such that the cell with highest RSRP is listed first if RSRP measurement results are available, otherwise the cell with highest RSRQ is listed first, and based on measurements collected up to the moment the UE detected failure;

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

[0818] NOTE 1: The measured quantities are filtered by the L3 filter as configured in the mobility measurement configuration. The measurements are based on the time domain measurement resource restriction, if configured. Exclude-listed cells are not required to be reported.

[0819] 1> set the c-RNTI to the C-RNTI used in the source PCell (in case HO failure) or PCell (in case RLF);

[0820] 1> if the failure is detected due to reconfiguration with sync failure as described in 5.3.5.8.3, set the fields in VarRLF-Report as follows:

[0821] 2> set the connectionFailureType to hof,2> if the UE supports RLF-Report for DAPS handover and if any DAPS bearer was configured while T304 was running:

[0822] 3> set lastHO-Type to daps',

[0823] 3 > if radio link failure was detected in the source PCell, according to clause 5.3.10.3:

[0824] 4> set timeConnSourceDAPS-Failure to the time between the initiation of the DAPS handover execution and the radio link failure detected in the source PCell while T304 was running;

[0825] 4> set the rlf-Cause to the trigger for detecting the source radio link failure in accordance with clause 5.3.10.4;

[0826] 2> if the UE supports RLF-Report for conditional handover and if configuration of the conditional handover is available in the MCG VarConditionalReconfig at the moment of the handover failure: 3 > if the UE executed a conditional handover toward target PCell according to the condRRCReconfig of the target PCell:

[0827] 4> set timeSinceCHO-Reconfig to the time elapsed between the execution of the last RRCReconfiguration message including reconfigurationWithSync for the target PCell of the failed conditional handover, and the reception in the source PCell of the last conditionalReconfiguration including the condRRCReconfig of the target PCell of the failed conditional handover;

[0828] 3> else:

[0829] 4> set timeSinceCHO-Reconfig to the time elapsed between the execution of the last RRCReconfiguration message including reconfigurationWithSync for the target PCell of the failed handover, and the reception in the source PCell of the last conditionalReconfiguration including the condRRCReconfig,'

[0830] 3> set choCandidateCellList to include the global cell identity, if available, and otherwise to-the phy sical cell identity and carrier frequency of each of the candidate target cells for conditional handover included in condRRCReconfig within the MCG VarConditionalReconfig at the -time ef-tlic failed handover, excluding the candidate target cells included in measResultNeighCells.- 3> set choConfigCellList to include the execution condition (one or two trigger event(s)) for the measld within condTriggerConfig associated with each of the candidate target cells within the MCG VarConditionalReconfig at the time of the failed handover, excluding the candidate target cells included in measResultNeighCell',

[0831] 2> if the UE supports RLF-Report for conditional handover and if the last executed RRCReconfiguration message including reconfigurationWithSync was concerning a conditional handover:

[0832] 3> set lastHO-Type to cho',

[0833] 2> set the nrFailedPCellld in failedPCellld to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell of the failed handover;

[0834] 2> include nrPreviousCell in previousPCellld and set it to the global cell identity and tracking area code of the PCell where the last RRCReconfiguration message including reconfigurationWithSync was received;

[0835] 2> set the timeConnFailure to the elapsed time since the execution of the last RRCReconfiguration message including the reconfigurationWithSync,> else if the failure is detected due to Mobility from NR failure as described in 5.4.3.5, set the fields in VarRLF-Report as follows:

[0836] 2> set the connectionFailureType to hof

[0837] 2> if last MobilityFromNRCommand concerned a failed inter-RAT handover from NR to E-UTRA and if the UE supports Radio Link Failure Report for Inter-RAT MRO EUTRA (NR to EUTRA): 3> set the eutraFailedPCellld in failedPCellld to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell of the failed handover;

[0838] 2> include nrPreviousCell in previousPCellld and set it to the global cell identity and tracking area code of the PCell where the last MobilityFromNRCommand message was received;

[0839] 2> set the timeConnFailure to the elapsed time since the initialization of the handover associated to the last MobilityFromNRCommand message;

[0840] 2> if the UE supports RLF report for inter-system handover for voice fallback and if voiceFallbacklndication is included in the last MobilityFromNRCommand.

[0841] 3> include the voiceFallbackHO;

[0842] > else if the failure is detected due to radio link failure as described in 5.3.10.3, set the fields in VarRLF-Report as follows:

[0843] 2> set the connectionFailureType to rlf,

[0844] 2> set the rlf-Cause to the trigger for detecting radio link failure in accordance with clause 5.3.10.4; 2> set the nrFailedPCellld in failedPCellld to the global cell identity and the tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the PCell where radio link failure is detected;

[0845] 2> if an RRCReconfiguration message including the reconfigurationWithSync was received before the connection failure:

[0846] 3> if the last successfully executed RRCReconfiguration message including the reconfigurationWithSync concerned an intra NR handover and it was received while connected to the previous PCell to which the UE was connected before connecting to the PCell where radio link failure is detected; and

[0847] 3> if T316 was not running before entering the PCell in which the radio link failure was detected; and

[0848] 3> if T311 was not running before entering the PCell in which the radio link failure was detected: 4> include the nrPreviousCell in previousPCellld and set it to the global cell identity and the tracking area code of the PCell where the last executed RRCReconfiguration message including reconfigurationWithSync was received; 4> if the last executed RRCReconfiguration message including reconfigurationWithSync was concerning a DAPS handover:

[0849] 5> set lastHO-Type to daps,'

[0850] 4> else if the last executed RRCReconfiguration message including reconfigurationWithSync was concerning a conditional handover:

[0851] 5> set lastHO-Type to cho.'4> set the timeConnFailure to the elapsed time since the execution of the last RRCReconfiguration message including the reconfigurationWithSync, 3> else if the last RRCReconfiguration message including the reconfigurationWithSync concerned a handover to NR from E-UTRA and if the UE supports Radio Link Failure Report for Inter- RAT MRO EUTRA:

[0852] 4> include the eutraPreviousCell in previousPCellld and set it to the global cell identity and the tracking area code of the E-UTRA PCell where the last RRCReconfiguration message including reconfigurationWithSync was received embedded in E-UTRA RRC message MohilityFromEUTRACommand message as specified in TS 36.331

[0010] clause 5.4.3.3;

[0853] 4> set the timeConnFailure to the elapsed time since reception of the last RRCReconfiguration message including the reconfigurationWithSync embedded in E-UTRA RRC message MohilityFromEUTRACommand message as specified in TS 36.331

[0010] clause 5.4.3.3;

[0854] 2> if configuration of the conditional handover is available in the MCG VarConditionalReconfig at the moment of declaring the radio link failure:

[0855] 3> set timeSinceCHO-Reconfig to the time elapsed between the detection of the radio link failure, and the reception, in the source PCell, of the last conditionalReconfiguration including the condRRCReconfig message;

[0856] 3> set choCandidateCellList to include the global cell identity if available, and otherwise to the physical cell identity and carrier frequency of each of all the candidate target cells for conditional handover included in condRRCReconfig within the MCG VarConditionalReconfig at the time of radio link failure, excluding the candidate target cells included in measResultNeighCells',

[0857] 3> set choConfigCellList to include the execution condition (one or two trigger event(s)) for the measld within condTriggerConfig associated with each of the candidate target cells within the MCG VarConditionalReconfig at the time of the radio link failure, excluding the candidate target cells included in measResultNeighCell',

[0858] 1> if connectionFailureType is rlf and the rlf-Cause is set to randomAccessProhlem or heamFailureRecoveryFailure,' or

[0859] 1> if connectionFailureType is rlf and the rlf-Cause is set to IhtFailure and the radio link failure is detected during the random access procedure; or

[0860] 1> if connectionFailureType is hof and if the failed handover is an intra-RAT handover:

[0861] 2> set the ra-InformationCommon to include the random-access related information as described in clause 5.7.10.5;

[0862] 1> if connectionFailureType is rlf and the rlf-Cause is set to IhtFailure, and the radio link failure is not detected during the random access procedure:

[0863] 2> set the locationAndBandwidth and suhcarrierSpacing in hwp-Info associated to the UL BWP in which the consistent uplink LBT failure was detected;

[0864] 1> if the rlf-Cause is set to t310-Expiry or t312-Expiry.

[0865] 2> set the ssbRLMConfigBitmap and / or csi-rsRLMConfigBitmap in measResultLastServCell to include the radio link monitoring configuration of the last serving cell, if available;

[0866] 1> if available, set the locationinfo as in 5.3.3.7.The UE may discard the radio link failure information or handover failure information, i.e. release the UE variable VarRLF-Report, 48 hours after the radio link failure / handover failure is detected. NOTE 2: In this clause, the term 'handover failure' has been used to refer to 'reconfiguration with sync failure'.

[0867] ******************************************************************************************

[0868] Implementation example 5 of the second embodiments, procedural logic for the successful handover report:

[0869] 5.7.10.6 Actions for the successful handover report determination (Note thatthe section number is from 3GPP TS 38.331 version 18.4.0.)

[0870] The UE shall for the PCell:

[0871] 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

[0872] 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

[0873] 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; or

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

[0875] 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

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

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

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

[0879] 3> if the UE is not in SNPN access mode, set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e., includes the RPLMN);

[0880] 3> else if the UE is in SNPN access mode, set the snpn-IdentityList to include the list of equivalent SNPNs stored by the UE (i.e., including the registered SNPN identity), if available;

[0881] 3> for intra-NR handover, set the c-RNTI to the C-RNTI assigned by the target PCell of the handover;

[0882] 3> if the procedure is triggered due to successful completion of reconfiguration with sync, for the source PCell in which the last RRCReconfiguration message including reconfigurationWithSync was applied; or

[0883] 3> if the procedure is triggered due to successful completion of Mobility from NR to E- UTRA, for the source PCell in which the last MobilityFromNRCommand concerning an inter-RAT handover from NR to E-UTRA was applied:

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

[0885] 4> set the sourceCellMeas in sourceCelllnfo to include the cell level RSRP, RSRQ and the available SINR, of the source PCell based on the available SSB and CSI- RS measurements collected up to the moment the UE sends RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E- UTRA;

[0886] 4> set the rsIndexResults in sourceCellMeas to include all the available SSB and CSI- RS measurement quantities of the source PCell collected up to the moment the UE sends RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E- UTRA;

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

[0888] 5> set the rlf-InSourceDAPS in sourceCellInfo to true;

[0889] 3> if the procedure is triggered due to successful completion of reconfiguration with sync, for the target PCell indicated in the last applied RRCReconfiguration message including reconfigurationWithSync.4> set the targetPCellID in targetCellInfo to the global cell identity and tracking area code, if available, of the target PCell; otherwise, set the targetCell-PCI-ARFCN to the physical cell identity and carrier frequency of the target PCell;

[0890] NOTE 00: If targetCell-PCI-ARFCN is included, it is left to UE implementation how to set the targetPCellID.

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

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

[0893] 4> if the last applied RRCReconfiguration message including reconfigurationWithSync was included in the stored condRRCReconfig:

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

[0895] 3> if the procedure is triggered due to successful completion of Mobility from NR to E- UTRA, for the target PCell indicated in the last applied MobilityFromNRCommand concerning an inter-RAT handover from NR to E-UTRA:

[0896] 4> set the targetPCellId in eutra-TargetCellInfo to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell;

[0897] 4> set the targetCellMeas in eutra-TargetCelllnfo to include the cell level RSRP, RSRQ and the available SINR, of the target PCell based on the available measurements collected up to the moment the UE sends RRCConnectionReconfigurationComplete message;

[0898] NOTE 0: If eutra-TargetCellInfo is included, it is left to UE implementation how to set the targetCelllnfo.

[0899] 3> 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 T304 timer, included in the last applied RRCReconfiguration message including the reconfigurationWithSync, is greater than

[0900] thresholdPercentageT304 if included in the successHO-Config received before executing the last reconfiguration with sync:

[0901] 4> set t304-cause in shr-Cause to true;

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

[0903] 3> if the ratio between the value of the elapsed time of the timer T310 and the configured value of the T310 timer, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync or 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 reconfiguration with sync or Mobility from NR to E-UTRA:

[0904] 4> set t310-cause in shr-Cause to true;

[0905] 3> if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the reconfiguration with sync procedure or 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 T312 timer, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync or 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 reconfiguration with sync, or Mobility from NR to E-UTRA:

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

[0907] 3> if the procedure is triggered due to successful completion of reconfiguration with sync and if sourceDAPS-FailureReporting included in the successHO-Config if configured by the source PCell before executing the last reconfiguration with sync is set to true, and if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running:

[0908] 4> set sourceDAPS-Failure in shr-Cause to true;

[0909] 3> if the procedure is triggered due to successful completion of reconfiguration with sync, for each of the measObjectNR, configured by the source PCell, in which the last RRCReconfiguration message including reconfigurationWithSync was applied;or: 3> if the procedure is triggered due to successful completion of Mobility from NR to E- UTRA, for each of the measObjectNR, configured by the source PCell, in which the last MobilityFromNRCommand concerning an inter-RAT handover from NR to E- UTRA was applied:

[0910] 4> if measRSSI-ReportConfig is configured for the frequency of the source PCell: 5> if the procedure is triggered due to successful completion of reconfiguration with sync:

[0911] 6> set the measResultServCellRSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency of the source PCell up to the moment the UE sends the RRCReconfigurationComplete message;

[0912] 5> else if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA:

[0913] 6> set the measResultServCellRSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency of the source PCell up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message;

[0914] 4> for each of the configured measObjectNR if measRSSI-ReportConfig is configured for the configured frequency:

[0915] 5> if the procedure is triggered due to successful completion of reconfiguration with sync:6> set the measResultNeighFreqRSSI in the measResultNeighFreqListRSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the associated neighbouring frequency up to the moment the UE sends the RRCReconfigurationComplete message:

[0916] 7> for each neighbour frequency included, include the optional fields that are available;

[0917] 5> else if the procedure is triggered due to successful completion of Mobility from NRto E-UTRA:

[0918] 6> set the measResultNeighFreqRSSI in the measResultNeighFreqListRSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the associated neighbouring frequency up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message: 7> for each neighbour frequency included, include the optional fields that are available;

[0919] 4> if measurements are available for the measObjectNR:

[0920] 5> if the SS / PBCH block-based measurement quantities are available: 6> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell or target PCell, ordered such that the cell with highest SS / PBCH block RSRP is listed first if SS / PBCH block RSRP measurement results are available, otherwise the cell with highest SS / PBCH block RSRQ is listed first if SS / PBCH block RSRQ measurement results are available, otherwise the cell with highest SS / PBCH block SINR is listed first, based on the available SS / PBCH block based measurements collected up to the moment the UE sends the RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA; 6> for each neighbour cell included, include the optional fields that are available;

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

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

[0923] 6> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell and target PCell, ordered such that the cell with highest CSI- RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the cell with highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the cell with highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE sends the RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRARRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA; 6> for each neighbour cell included, include the optional fields that are available;

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

[0925] 3> if the procedure is triggered due to successful completion of reconfiguration with sync, for each of the measObjectEUTRA, configured by the source PCell in which the last RRCReconfiguration message including reconfigurationWithSync was applied; or: 3> if the procedure is triggered due to successful completion of Mobility from NR to E- UTRA, for each of the measObjectEUTRA, configured by the source PCell in which the last MobilityFromNRCommand concerning an inter-RAT handover from NR to E- UTRA was applied:

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

[0927] 5> set the measResultListEUTRA in measResultNeighCells to include the best measured cells ordered such that the cell with highest RSRP is listed first if RSRP measurement results are available, otherwise the cell with highest RSRQ is listed first, based on measurements collected up to the moment the UE sends the RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E- UTRA;

[0928] 5> for each neighbour cell included, include the optional fields that are available; 3> for each of the neighbour cells included in measResultNeighCells:

[0929] 4> if the cell was a candidate target cell included in the condRRCReconfig within the conditionalReconfiguration configured by the source PCell, in which the last RRCReconfiguration message including reconfigurationWithSync was applied: 5> set the choCandidate to true in measResultNR,'

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

[0931] 3> if the procedure is triggered due to successful completion of reconfiguration with sync, and the last applied RRCReconfiguration message including reconfigurationWithSync was concerning a conditional handover:

[0932] 4> set choConflgCellList to include the execution condition (one or two trigger event(s)) for the measld within condTriggerConfig associated with each of the candidate target cells within the MCG VarConditionalReconfig at the time of successful conditional handover, excluding the candidate target cells included in measResultNeighCell',

[0933] 1> release successHO-Config configured by the source PCell and thresholdPercentageT304 if configured by the target PCell.The UE may discard the successful handover information, i.e., release the UE variable VarSuccessHO-Report, 48 hours after the last successful handover information is added to the VarSuccessHO-Report.

[0934] Implementation example 6 of the second embodiments, procedural logic for the successful PSCell addition or change report:

[0935] 5.7.10.7 Actions for the successful PSCell change or addition report determination [Note that the section number is from 3GPP TS 38.331 version 18.4.0.]

[0936] The UE shall for the PSCell:

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

[0938] 1> if sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is configured and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync for the SCG, is greater than thresholdPercentageT310-SCG included in the successPSCell-Config if configured by the source PSCell before executing the last reconfiguration with sync for the SCG; or

[0939] 1> if sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is configured and if the T312 associated to the measurement identity of the target PSCell was running at the time of initiating the execution of the reconfiguration with sync procedure for the SCG and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312-SCG included in the successPSCell- Config if configured by the source PSCell before executing the last reconfiguration with sync for the SCG:

[0940] 1> if sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is not configured and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync for the SCG, is greater than thresholdPercentageT310-SCG included in the successPSCell-Config if configured by the PCell before executing the last reconfiguration with sync for the SCG; or

[0941] 1> if sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is not configured and if the T312 associated to the measurement identity of the target PSCell was running at the time of initiating the execution of the reconfiguration with sync procedure for the SCG and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312-SCG included in the successPSCell- Config if configured by the PCell before executing the last reconfiguration with sync for the SCG:> clear the information included in VarSuccessPSCell-Report, if any;

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

[0943] 3> if the UE is not in SNPN access mode, set the plmn-IdentityList to include the list of EPLMNs (including the RPLMN) stored by the UE;

[0944] 3> else if the UE is in SNPN access mode, set the snpn-IdentityList to include the list of equivalent SNPN identities (including the registered SNPN identity) stored by the UE, if available;

[0945] 3> set the pCellld to the global cell identity and tracking area code, if available, of the PCell; 3> for the source PSCell (in case of PSCell change procedure) in which the last RRCReconfiguration message for the SCG including reconfigurationWithSync was applied: 4> set the sourcePSCellld in sourcePSCelllnfo to the global cell identity and tracking area code, and otherwise to the physical cell identity and carrier frequency of the source PSCell;

[0946] 4> set the sourcePSCellMeas in sourcePSCelllnfo to include the cell level RSRP, RSRQ and the available SINR, of the source PSCell based on the available SSB and CSI-RS measurements collected up to the moment the UE successfully completed the random access procedure for the SCG;

[0947] 4> set the rsIndexResults in sourcePSCellMeas to include all the available SSB and CSI-RS measurement quantities of the source PSCell collected up to the moment the UE successfully completed the random access procedure for the SCG;

[0948] 3> for the target PSCell indicated in the last applied RRCReconfiguration message for the SCG including reconfigurationWithSync.

[0949] 4> set the targetPSCellID in targetPSCelllnfo to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PSCell;

[0950] 4> set the targetPSCellMeas in targetPSCelllnfo to include the cell level RSRP, RSRQ and the available SINR, of the target PSCell based on the available SSB and CSI-RS measurements collected up to the moment the UE successfully completed the random access procedure for the SCG;

[0951] 4> set the rsIndexResults in targetPSCellMeas to include all the available SSB and CSI-RS measurement quantities of the target PSCell collected up to the moment the UE successfully completed the random access procedure for the SCG;

[0952] 4> if the last applied RRCReconfiguration message for the SCG including reconfigurationWithSync was included in the stored condRRCReconfig:

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

[0954] 3> if triggering threshold for storing the successful PSCell change or addition information in VarSuccessPSCell-Report based on the thresholdPercentageT304-SCG is met:

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

[0956] 3> if triggering threshold for storing the successful PSCell change or addition information in VarSuccessPSCell-Report based on the thresholdPercentageT310-SCG is met:

[0957] 4> set t310-cause in spr-Cause to true,'

[0958] 3> if triggering threshold for storing the successful PSCell change or addition information in VarSuccessPSCell-ReporfbasQ& on the thresholdPercentageT312-SCG is met:

[0959] 4> set t312-cause in spr-Cause to true,'

[0960] 3> if sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is configured:

[0961] 4> consider all measObjectNR configured by the source PSCell;

[0962] 3> else:

[0963] 4> consider all measObjectNR configured by the PCell;

[0964] 3> for each of the considered measObjectNR:

[0965] 4> if measurements are available for the measObjectNR

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

[0967] 6> include in the measResultListNR in measResultNeighCells all the available measurement quantities of the best measured cells, other than the source PSCell (in case of PSCell change procedure) or target PSCell, ordered such that the cell with highest SS / PBCH block RSRP is listed first if SS / PBCH block RSRP measurement results are available, otherwise the cell with highest SS / PBCH block RSRQ is listed first if SS / PBCH block RSRQ measurement results are available, otherwise the cell with highest SS / PBCH block SINR is listed first, based on the available SS / PBCH block based measurements collected up to the moment the UE successfully completed the random access procedure;

[0968] 6> for each neighbour cell included, include the optional fields that are available (including the CSI-RS based measurement quantities, if available); 5> if the CSI-RS measurement quantities are available for the cells not yet included in measResultListNR in measResultNeighCells:

[0969] 6> include in the measResultListNR in measResultNeighCells all the available measurement quantities of the best measured cells, other than the source PSCell (in case of PSCell change procedure) and target PSCell, ordered such that the cell with highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the cell with highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the cell with highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE successfully completed the random access procedure;

[0970] 6> for each neighbour cell included, include the optional fields that are available;3> for each of the neighbour cells included in measResultNeighCells:

[0971] 4> if the cell was a candidate target cell included in the condRRCReconfig within the conditionalReconfiguration, configured by the source PCell including the condExecutionCond within the conditionalReconfiguration associated to condEventA4 or by the source PSCell (in case of PSCell change) when the last RRCReconfiguration message for the SCG including reconfigurationWithSync was applied:5> set the choCandidate to true in measResultNR;3> if the procedure is triggered due to successful completion of reconfiguration with sync, and the last applied RRCReconfiguration message including reconfigurationWithSync was concerning a conditional PSCell addition or change:4> set choConfigCellList to include the execution condition (one or two trigger event(s)) for the measld within condTriggerConfig associated with each of the candidate target cells within the MCG VarConditionalReconfig at the time of successful conditional PSCell addition or change, excluding the candidate target cells included in measResultNeighCell; 3> if sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is configured:

[0972] 4> if available, set the locationinfo as in 5.3.3.7 according to the otherConfig associated with the source PSCell;

[0973] 4> include sn-InitiatedPSCellChange,'

[0974] 3> else:

[0975] 4> if available, set the locationinfo as in 5.3.3.7 according to the otherConfig associated with the PCell;

[0976] 1> release successPSCell-Config configured by the source PSCell if available and thresholdPercentageT304 if configured by the target PSCell.

[0977] The UE may discard the successful PSCell change or addition information, i.e., release the UE variable VarSuccessPSCell-Report, 48 hours after the last successful PSCell change or addition information is added to the VarSuccessPSCell-Report or upon deregistration from the network as specified in TS 23.502

[0043] ,

[0978] Implementation example 7 of the second embodiments, ASN.1 code for the RLF report the successful handover report and the successful PSCell addition or change report: RLF-Report-rl6 CHOICE { nr-RLF-Report-r16 SEQUENCE { measResultLastServCell-r16 MeasResultRLFNR-r16, measResultNeighCells-r16 SEQUENCE { measResultListNR-r16 MeasResultList2NR-r16 OPTIONAL, measResultListEUTRA-r16 MeasResultList2EUTRA-r16 OPTIONAL } OPTIONAL, c-RNTI-r16 RNTI-Value, previousPCellId-rl6 CHOICE { nrPreviousCell-r16 CGI-Info-Logging-r16, eutraPreviousCell-r16 CGI-InfoEUTRALogging } OPTIONAL, failedPCellId-r16 CHOICE {

[0979]

[0980] nrFailedPCellId-rl6 CHOICE {cellGlobalId-rl6 CGI-Inf o-Logging-r 16r

[0981] pci-arfcn-r16 PCI-ARFCN-NR-r16

[0982] },

[0983] eutraFailedPCellId-rl6 CHOICE {

[0984] cellGlobalId-rl6 CGI-Inf oEUTRALogging,

[0985] pci-ar f cn-r 16 PCI-ARFCN-EUTRA-rl6

[0986] }

[0987] }f

[0988] reconnectCellld-r 16 CHOICE {

[0989] nrReconnectCellId-r16 CGI-Info-Logging-r16, eutraReconnectCellld-r 16 CGI-Inf oEUTRALogging

[0990] }

[0991] OPTIONAL,

[0992] timeUntilRe connect ion- r 16 TimeUntilRe connect ion- r 1

[0993] OPTIONAL,

[0994] reestablishmentCellId-r16 CGI-Info-Logging-r16

[0995] OPTIONAL,

[0996] timeConnFailure-r16 INTEGER (0..1023)

[0997] OPTIONAL,

[0998] timeSinceFailure-r16 TimeSinceFailure-r16,

[0999] connectionFailureType-r16 ENUMERATED { rlf, hof },

[1000] rlf-Cause-r16 ENUMERATED { t310-Expiry, randomAccessProblem, rlc-MaxNumRetx,

[1001] beamFailureRecoveryFailure, lbtFailure-r16,

[1002] bh-rlfRecoveryFailure, t312-expiry-r17, spare1 },

[1003] locationInfo-r16 LocationInfo-r16

[1004] OPTIONAL,

[1005] noSuitableCellFound-r16 ENUMERATED { true }

[1006] OPTIONAL,

[1007] ra-InformationCommon-r16 RA-InformationCommon-r166

[1008] OPTIONAL,

[1009] [ [

[1010] csi-rsRLMConfigBitmap-v1650 BIT STRING (SIZE (96))

[1011] OPTIONAL

[1012] ] ]f

[1013] [ [

[1014] lastHO-Type-r17 ENUMERATED { cho, daps, spare2, spare1 } OPTIONAL,

[1015] timeConnSourceDAPS-Failure-r17 TimeConnSourceDAPS-Failure-r17

[1016] OPTIONAL,

[1017] timeSinceCHO-Reconfig-r17 TimeSinceCHO-Reconfig-r17

[1018] OPTIONAL,

[1019] choCellId-rl7 CHOICE {

[1020] cellGlobalId-rl7 CGI-Inf o-Logging-r 16,

[1021] pci-arfcn-r17 PCI-ARFCN-NR-r16

[1022] }

[1023] OPTIONAL,

[1024] choCandidateCellList-r17 ChoCandidateCellList-r17

[1025] OPTIONAL

[1026] ] ]r

[1027] [ [

[1028] pSCellId-rl8 CHOICE {

[1029] cellGlobalId-r18 CGI-Info-Logging-r16,

[1030] pci-arfcn-r18 PCI-ARFCN-NR-r16

[1031] }

[1032] OPTIONAL,

[1033] mcg-RecoveryFailureCause-r18 ENUMERATED { t316-Expiry, scg-Deactivated, spare2, spare1 } OPTIONAL,

[1034] scg-FailureCause-r18 ENUMERATED { t310-Expiry, randomAccessProblem, rlc-MaxNumRetx,

[1035] synchReconfigFailureSCG, scg-ReconfigFailure,

[1036] srb3-IntegrityFailure, scg-lbtFailure, beamFailureRecoveryFailure,

[1037] t312-Expiry, bh-RLF, beamFailure, spare5, spare4, spare3, spare2, spare1 }

[1038] OPTIONAL,

[1039] elapse TimeSCG-Failure-rl8 ElapsedTimeSCG-Failure-rl8

[1040] OPTIONAL,voiceFallbackHO-r18 ENUMERATED { true } OPTIONAL,

[1041] measResultLastServCellRSSI-r18 RSSI-Range-r16

[1042] OPTIONAL,

[1043] measResultNeighFreqListRSSI-r18 MeasResultNeighFreqListRSSI-r18 OPTIONAL,

[1044] bwp-Info-r18 AttemptedBWP-Info-r18 OPTIONAL,

[1045] elapsedTimeT316-r18 ElapsedTimeT316-r18 OPTIONAL,

[1046] scg-FailedAfterMCG-r18 ENUMERATED { true } OPTIONAL

[1047] choConf igCellList-r 19 ChoConf igCellList-r 19 OPTIONAL

[1048] ] ]

[1049] eutra-RLF-Report-r 16 SEQUENCE {

[1050] failedPCellId-EUTRA CGI-InfoEUTRALogging, measResult-RLF-Report-EUTRA-rl6 OCTET STRING,

[1051] measResult-RLF-Report-EUTRA-vl690 OCTET STRING

[1052] OPTIONAL

[1053] ] ]

[1054] }

[1055] SuccessHO-Report-r17 ::= SEQUENCE {

[1056] sourceCellInfo-r17 SEQUENCE {

[1057] sourcePCell!d-rl7 CGI-Inf o-Logging-rl, sourceCellMeas-r17 MeasResultSuccessHONR-r17 OPTIONAL,

[1058] rlf-InSourceDAPS-r17 ENUMERATED { true } OPTIONAL

[1059] }f

[1060] targetCellInfo-r17 SEQUENCE {

[1061] targetPCellId-r17 CGI-Info-Logging-r17, targetCellMeas-r17 MeasResultSuccessHONR-r17 OPTIONAL

[1062] b

[1063] measResultNeighCells-r17 SEQUENCE { measResultListNR-rl7 MeasResultList2NR-rl6 OPTIONAL,

[1064] measResultListEUTRA-r 17 MeasResultList2EUTRA-rl6 OPTIONAL

[1065] }

[1066] OPTIONAL,

[1067] locationInfo-r17 LocationInfo-r16 OPTIONAL,

[1068] timeSinceCHO-Reconfig-r17 TimeSinceCHO-Reconfig-r17 OPTIONAL,

[1069] shr-Cause-r17 SHR-Cause-r17

[1070] OPTIONAL,

[1071] ra-InformationCommon-r167 RA-Inf ormat ionCommon- r 16 OPTIONAL,

[1072] upInterruptionTimeAtHO-r17 UPInterruptionTimeAtHO-r17 OPTIONAL,

[1073] c-RNTI-r17 RNTI-Value

[1074] OPTIONAL,

[1075] [ [

[1076] targetCell-PCI-ARFCN-r17 PCI-ARFCN-NR-r16 OPTIONAL

[1077] ] ]r

[1078] [ [

[1079] eutra-TargetCellInfo-r18 SEQUENCE {

[1080] targetPCellId-r18 CHOICE { cellGlobalId-r18 CGI-Info-Logging-r16, pci-ar f cn-r 18 PCI-ARFCN-EUTRA-rl6 }r

[1081] targetCellMeas-rl8 Meas Quant ityResultsEUTRA OPTIONAL} OPTIONAL, measResultServCellRSSI-r18 RSSI-Range-r16 OPTIONAL, measResultNeighFreqListRSSI-r18 MeasResultNeighFreqListRSSI-r18 OPTIONAL, eutra-C-RNTI-r18 EUTRA-C-RNTI OPTIONAL, timeSinceSHR-r18 TimeSinceSHR-r18 OPTIONAL

[1082] ] ], II

[1083] choConf igCellList-r 19 ChoConf igCellList-r 19 OPTIONAL }I

[1084]

[1085] SuccessPSCell-Report-rl8:: = SEQUENCE {

[1086] pCellId-r18 CGI-Info-Logging-r18,

[1087] source PSCellInfo-rl8 SEQUENCE {

[1088] source PSCellId-rl8 CHOICE {

[1089] cellGloballd-r 18 CGI-Inf o-Logging-r 1, pci-arfcn-r18 PCI-ARFCN-EUTRA-r16 sourcePSCellMeas-rl8 MeasResultSuccessH0NR-rl7 OPTIONAL

[1090] }

[1091] OPTIONAL,

[1092] target PSCelllnf o-rl8 SEQUENCE {

[1093] target PSCellld-r 18 CHOICE {

[1094] cellGlobalId-r18 CGI-Info-Logging-r16, pci-arfcn-r18 PCI-ARFCN-NR-r16 b

[1095] target PSCellMeas-r 18 MeasResultSuccessH0NR-rl7 OPTIONAL

[1096] measResultNeighCells-r 18 SEQUENCE {

[1097] measResultListNR-rl8 MeasResultList2NR-rl6 OPTIONAL,

[1098] measResultListEUTRA-rl8 MeasResultList2EUTRA-rl6 OPTIONAL

[1099] }

[1100] OPTIONAL,

[1101] spr-Cause-rl8 SPR-Cause-rl8

[1102] OPTIONAL,

[1103] time SinceCPAC-Re conf ig-rl8 TimeSinceCPAC-Reconfig-rl8 OPTIONAL,

[1104] locationlnfo-rl8 Locationlnfo-rl6

[1105] OPTIONAL,

[1106] ra-InformationCommon-r168 RA-Inf ormat ionCommon- r 16 OPTIONAL,

[1107] sn-InitiatedPSCellChange-rl8 ENUMERATED { true }

[1108] OPTIONAL,

[1109] II

[1110] choConf igCellList-r 19 ChoConf igCellList-r 19 OPTIONAL

[1111] I

[1112] }

[1113] ChoCandidateCellList-rl7:: = SEQUENCE ( SIZE ( 1.. maxNro f CondCells -r 16 ) ) OF ChoCandidateCell-rl7

[1114] ChoCandidateCell-rl7:: = CHOICE {

[1115] cellGlobalId-r17 CGI-Info-Logging-r16,

[1116] pci-arfcn-r17 PCI-ARFCN-NR-r16

[1117] }

[1118] ChoConfigCellList-r19 ::= SEQUENCE ( SIZE ( 1.. maxNro f CondCells -rl 6 ) ) OF ChoConf igPerCell-r 19 ChoConfigPerCell-r19 ::= SEQUENCE { cellId-r19 CHOICE { cellGlobalId-r17 CGI-Info-Logging-r16,

[1119]

[1120] pci-arfcn-r17 PCI-ARFCN-NR-r16SEQUENCE ( SIZE ( 1..2 ) ) OF CondTriggerConfig-rl6

[1121]

[1122] _ RLF-Report field descriptions _

[1123] choConfigCellList

[1124] This field is used to indicate the execution condition (one or two trigger event(s)) for the measld within condTriggerConfig associated with each of the candidate target cells within the MCG VarConditionalReconfiq at the time of the connection failure, excluding the candidate target cells included in measResultNeiqhCell. When this field is present in the RLF-Report, the field choCandidateList may be absent. The field is optional in the SuccessHO-Report and SuccessPSCell-

[1125]

[1126] Report too.

[1127] Some third embodiments

[1128] In the third embodiments, the first embodiments and the second embodiments are combined in a way that the time- or location- based CHO related information is logged in a SON report, such as the RLF report MeasResultNR, even when there is no available RRM measurements for the neighbor cell, and in addition, time- or location-based CHO related information for the candidate target cells which did not fit in measResultListNR in measResultNeighCells are logged in one or more other field(s) in the concerned SON report(s) outside the measResultNeighCells field.

[1129] For instance, an implementation example of the first embodiments may be combined with an implementation example of the second embodiments. This may for instance result in the following implementation examples of the third embodiments.

[1130] ****************************************************************************************** Implementation example 1 of the third embodiments, procedural logic for the RLF report: 5.3.10.5 RLF report content determination (Note that the section number is from 3GPP TS 38.331 version 18.4.0.)

[1131] The UE shall determine the content in the Var RLF-Report as follows:

[1132] 1> clear the information included in Var RLF-Report, if any;

[1133] 1> if the UE is not in SNPN access mode, set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e. including the RPLMN);

[1134] 1> else if the UE is in SNPN access mode, set the snpn-IdentityList to include the list of equivalent SNPNs stored by the UE (i.e., including the registered SNPN identity);

[1135] 1> set the measResultLastServCell to include the cell level RSRP, RSRQ and the available SINR, of the source PCell (in case HO failure) or PCell (in case RLF) based on the available SSB and CSI-RS measurements collected up to the moment the UE detected failure;1> if measRSSI-ReportConfig is configured for the measObject indicated as the servingCellMO of the source PCell (in case HO failure) or PCell (in case of RLF), set the measResultLastServCellRSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency of the source PCell (in case HO failure) or PCell (in case of RLF) up to the moment the UE detected the failure;

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

[1137] 2> set the rsIndexResults in measResultLastServCell to include all the available measurement quantities of the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the highest SS / PBCH block RSRP is listed first if SS / PBCH block RSRP measurement results are available, otherwise the highest SS / PBCH block RSRQ is listed first if SS / PBCH block RSRQ measurement results are available, otherwise the highest SS / PBCH block SINR is listed first, based on the available SS / PBCH block based measurements collected up to the moment the UE detected failure;

[1138] 1> if the CSI-RS based measurement quantities are available:

[1139] 2> set the rsIndexResults in measResultLastServCell to include all the available measurement quantities of the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE detected failure;

[1140] 1> for each of the configured measObjectNR in which measurements are available or for which the associated reportConfigNR includes a condEventT1, condtEventD1 or condEventD2:

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

[1142] 3> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the cell with highest SS / PBCH block RSRP is listed first if SS / PBCH block RSRP measurement results are available, otherwise the cell with highest SS / PBCH block RSRQ is listed first if SS / PBCH block RSRQ measurement results are available, otherwise the cell with highest SS / PBCH block SINR is listed first, based on the available SS / PBCH block based measurements collected up to the moment the UE detected failure;

[1143] 4> for each neighbour cell included, include the optional fields that are available; NOTE 0a: For the neighboring cells included in measResultListNR in measResultNeighCells ordered based on the SS / PBCH block measurement quantities, UE also includes the CSI-RS based measurement quantities, if available.

[1144] 2> if the CSI-RS based measurement quantities are available:

[1145] 3> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the cell with highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the cell with highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the cell with highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE detected radio link failure;

[1146] 4> for each neighbour cell included, include the optional fields that are available;NOTE 0b: For ordering the neighboring cells based on the CSI-RS measurement quantities, UE includes measurements only for the cells not yet included in measResultListNR in measResultNeighCells to avoid overriding SS / PBCH block-based ordered measurements.

[1147] 2> if measResultListNR in measResultNeighCells includes fewer than maxCellReport MeasResultNR IES and the measObjectNR is associated with a reportConfigNR including a condEventT1, condtEventD1 or condEventD2:

[1148] 3> for each neighbour cell associated with the measObjectNR for which no measurement quantities are available:

[1149] 4> if measResultListNR in measResultNeighCells includes fewer than maxCellReport MeasResultNR IEs:

[1150] 5> include a MeasResultNR IE in measResultListNR in measResultNeighCells and leave the resultsSSB-Cell, resultsCSI-RS-Cell and rsIndexResults absent;

[1151] NOTE 0c: Neighbouring cells for which no measurement quantities are available are placed after neighbouring cells for which measurement quantities are available in measResultListNR in measResultNeighCells.

[1152] 2> for each neighbour cell, if any, included in measResultListNR in measResultNeighCells:

[1153] 3 > if the UE supports RLF-Report for conditional handover and if the neighbour cell is one of the candidate cells for which the reconfigurationWithSync is included in the masterCellGroup in the MCG VarConditionalReconfig at the moment of the detected failure:

[1154] 4> set the choCandidate to true in measResultNR; (In a variation of this implementation example, this statement is omitted.)

[1155] 4> set choConfig in MeasResult2NR to the execution condition for each measld within condTriggerConfig associated to the neighbour cell within the MCG VarConditionalReconfig;

[1156] 4> if the first entry of choConfig corresponds to a fulfilled execution condition at the moment of handover failure, or radio link failure; or

[1157] 4> if the second entry of choConfig, if available, corresponds to a fulfilled execution condition at the moment of handover failure, or radio link failure:

[1158] 5> set firstTriggeredEvent to the execution condition condFirstEvent corresponding to the first entry of choConfig or to the execution condition condSecondEvent corresponding to the second entry of choConfig, whichever execution condition was fulfilled first in time;

[1159] 5> set timeBetweenEvents to the elapsed time between the point in time of fulfilling the condition in choConfig that was fulfilled first in time, and the point in time of fulfilling the condition in choConfig that was fulfilled second in time, if both the first execution condition corresponding to the first entry and the second execution condition corresponding to the second entry in the choConfig were fulfilled;

[1160] 1> for each of the configured measObjectNR associated with neighboring cells if the associated reportConfigNR includes measRSSI-ReportConfig'.

[1161] 2> set the measResultNeighFreqRSSI in the measResultNeighFreqListRSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequencies other than thefrequency of the source PCell (in case HO failure) or of the PCell (in case RLF), up to the moment the UE detected failure:

[1162] 3> for each neighbour frequency included, include the optional fields that are available;

[1163] 1> for each of the configured EUTRA frequencies in which measurements are available;

[1164] 2> set the measResultListEUTRA in measResultNeighCells to include the best measured cells ordered such that the cell with highest RSRP is listed first if RSRP measurement results are available, otherwise the cell with highest RSRQ is listed first, and based on measurements collected up to the moment the UE detected failure;

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

[1166] NOTE 1: The measured quantities are filtered by the L3 filter as configured in the mobility measurement configuration. The measurements are based on the time domain measurement resource restriction, if configured. Exclude-listed cells are not required to be reported.

[1167] 1> set the c-RNTI to the C-RNTI used in the source PCell (in case HO failure) or PCell (in case RLF);

[1168] 1> if the failure is detected due to reconfiguration with sync failure as described in 5.3.5.8.3, set the fields in VarRLF-Report as follows:

[1169] 2> set the connectionFailureType to hof

[1170] 2> if the UE supports RLF-Report for DAPS handover and if any DAPS bearer was configured while T304 was running:

[1171] 3> set lastHO-Type to daps',

[1172] 3 > if radio link failure was detected in the source PCell, according to clause 5.3.10.3:

[1173] 4> set timeConnSourceDAPS-Failure to the time between the initiation of the DAPS handover execution and the radio link failure detected in the source PCell while T304 was running;

[1174] 4> set the rlf-Cause to the trigger for detecting the source radio link failure in accordance with clause 5.3.10.4;

[1175] 2> if the UE supports RLF-Report for conditional handover and if configuration of the conditional handover is available in the MCG VarConditionalReconfig at the moment of the handover failure: 3 > if the UE executed a conditional handover toward target PCell according to the condRRCReconfig of the target PCell:

[1176] 4> set timeSinceCHO-Reconfig to the time elapsed between the execution of the last RRCReconfiguration message including reconfigurationWithSync for the target PCell of the failed conditional handover, and the reception in the source PCell of the last conditionalReconfiguration including the condRRCReconfig of the target PCell of the failed conditional handover;

[1177] 3> else:

[1178] 4> set timeSinceCHO-Reconfig to the time elapsed between the execution of the last RRCReconfiguration message including reconfigurationWithSync for the target PCell of the failed handover, and the reception in the source PCell of the last conditionalReconfiguration including the condRRCReconfig,'3> set choCandidateCellList to include the global cell identity, if available, and otherwise to the physical cell identity and carrier frequency of each of the candidate target cells for conditional handover included in condRRCReconfig within the MCG VarConditionalReconfig at the time of the failed handover, excluding the candidate target cells included in measResultNeighCells; 3> set choConfigCellList to include the execution condition (one or two trigger event(s)) for the measld within condTriggerConfig associated with each of the candidate target cells within the MCG VarConditionalReconfig at the time of the failed handover, excluding the candidate target cells included in measResultNeighCell',

[1179] 2> if the UE supports RLF-Report for conditional handover and if the last executed RRCReconfiguration message including reconfigurationWithSync was concerning a conditional handover:

[1180] 3> set lastHO-Type to c / zo;

[1181] 2> set the nrFailedPCellld in failedPCellld to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell of the failed handover;

[1182] 2> include nrPreviousCell in previousPCellld and set it to the global cell identity and tracking area code of the PCell where the last RRCReconfiguration message including reconfigurationWithSync was received;

[1183] 2> set the timeConnFailure to the elapsed time since the execution of the last RRCReconfiguration message including the reconfigurationWithSync,

[1184] > else if the failure is detected due to Mobility from NR failure as described in 5.4.3.5, set the fields in VarRLF-Report as follows:

[1185] 2> set the connectionFailureType to hofi

[1186] 2> if last MobilityFromNRCommand concerned a failed inter-RAT handover from NR to E-UTRA and if the UE supports Radio Link Failure Report for Inter-RAT MRO EUTRA (NR to EUTRA): 3> set the eutraFailedPCellld in failedPCellld to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell of the failed handover;

[1187] 2> include nrPreviousCell in previousPCellld and set it to the global cell identity and tracking area code of the PCell where the last MobilityFromNRCommand message was received;

[1188] 2> set the timeConnFailure to the elapsed time since the initialization of the handover associated to the last MobilityFromNRCommand message;

[1189] 2> if the UE supports RLF report for inter-system handover for voice fallback and if voiceFallbacklndication is included in the last MobilityFromNRCommand.

[1190] 3> include the voiceFallbackHO;

[1191] > else if the failure is detected due to radio link failure as described in 5.3.10.3, set the fields in VarRLF-Report as follows:

[1192] 2> set the connectionFailureType to rlfi

[1193] 2> set the rlf-Cause to the trigger for detecting radio link failure in accordance with clause 5.3.10.4; 2> set the nrFailedPCellld in failedPCellld to the global cell identity and the tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the PCell where radio link failure is detected;> if an RRCReconfiguration message including the reconfigurationWithSync was received before the connection failure:

[1194] 3> if the last successfully executed RRCReconfiguration message including the reconfigurationWithSync concerned an intra NR handover and it was received while connected to the previous PCell to which the UE was connected before connecting to the PCell where radio link failure is detected; and

[1195] 3> if T316 was not running before entering the PCell in which the radio link failure was detected; and

[1196] 3> if T311 was not running before entering the PCell in which the radio link failure was detected: 4> include the nrPreviousCell in previousPCellld and set it to the global cell identity and the tracking area code of the PCell where the last executed RRCReconfiguration message including reconfigurationWithSync was received; 4> if the last executed RRCReconfiguration message including reconfigurationWithSync was concerning a DAPS handover:

[1197] 5> set lastHO-Type to daps,'

[1198] 4> else if the last executed RRCReconfiguration message including reconfigurationWithSync was concerning a conditional handover:

[1199] 5> set lastHO-Type to cho'.

[1200] 4> set the timeConnFailure to the elapsed time since the execution of the last RRCReconfiguration message including the reconfigurationWithSync,

[1201] 3> else if the last RRCReconfiguration message including the reconfigurationWithSync concerned a handover to NR from E-UTRA and if the UE supports Radio Link Failure Report for Inter- RAT MRO EUTRA:

[1202] 4> include the eutraPreviousCell in previousPCellld and set it to the global cell identity and the tracking area code of the E-UTRA PCell where the last RRCReconfiguration message including reconfigurationWithSync was received embedded in E-UTRA RRC message MohilityFromEUTRACommand message as specified in TS 36.331

[0010] clause 5.4.3.3;

[1203] 4> set the timeConnFailure to the elapsed time since reception of the last RRCReconfiguration message including the reconfigurationWithSync embedded in E-UTRA RRC message MohilityFromEUTRACommand message as specified in TS 36.331

[0010] clause 5.4.3.3;

[1204] > if configuration of the conditional handover is available in the MCG VarConditionalReconfig at the moment of declaring the radio link failure:

[1205] 3> set timeSinceCHO-Reconfig to the time elapsed between the detection of the radio link failure, and the reception, in the source PCell, of the last conditionalReconfiguration including the condRRCReconfig message;

[1206] 3> set choCandidateCellList to include the global cell identity if available, and otherwise to -the physical cell identity and carrier frequency of each of all the candidate target cells for conditional handover included in condRRCReconfig within the MCG VarConditionalReconfig atfhe time of radio link failure, excluding the candidate target cells included in

[1207] measResultNeighCells;3> set choConfigCellList to include the execution condition (one or two trigger event(s)) for the measld within condTriggerConfig associated with each of the candidate target cells within the MCG VarConditionalReconfig at the time of the radio link failure, excluding the candidate target cells included in measResultNeighCell',

[1208] 1> if connectionFailureType is rlf and the rlf-Cause is set to randomAccessProblem or beamFailureRecoveryFailure,' or

[1209] 1> if connectionFailureType is rlf and the rlf-Cause is set to IbtFailure and the radio link failure is detected during the random access procedure; or

[1210] 1> if connectionFailureType is hof and if the failed handover is an intra-RAT handover:

[1211] 2> set the ra-InformationCommon to include the random-access related information as described in clause 5.7.10.5;

[1212] 1> if connectionFailureType is rlf and the rlf-Cause is set to IbtFailure, and the radio link failure is not detected during the random access procedure:

[1213] 2> set the locationAndBandwidth and subcarrierSpacing in bwp-Info associated to the UL BWP in which the consistent uplink LBT failure was detected;

[1214] 1> if the rlf-Cause is set to t310-Expiry or t312-Expiry.

[1215] 2> set the ssbRLMConfigBitmap and / or csi-rsRLMConfigBitmap in measResultLastServCell to include the radio link monitoring configuration of the last serving cell, if available;

[1216] 1> if available, set the locationinfo as in 5.3.3.7.

[1217] The UE may discard the radio link failure information or handover failure information, i.e. release the UE variable VarRLF-Report, 48 hours after the radio link failure / handover failure is detected. NOTE 2: In this clause, the term 'handover failure' has been used to refer to 'reconfiguration with sync failure'.

[1218] ****************************************************************************************** Implementation example 2 of the third embodiments, procedural logic for the successful handover report:

[1219] 5.7.10.6 Actions for the successful handover report determination [Note that the section number is from 3GPP TS 38.331 version 18.4.0.]

[1220] The UE shall for the PCell:

[1221] 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

[1222] 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; or1> 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; or

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

[1224] 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

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

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

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

[1228] 3> if the UE is not in SNPN access mode, set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e., includes the RPLMN);

[1229] 3> else if the UE is in SNPN access mode, set the snpn-IdentityList to include the list of equivalent SNPNs stored by the UE (i.e., including the registered SNPN identity), if available;

[1230] 3> for intra-NR handover, set the c-RNTI to the C-RNTI assigned by the target PCell of the handover;

[1231] 3> if the procedure is triggered due to successful completion of reconfiguration with sync, for the source PCell in which the last RRCReconfiguration message including reconfigurationWithSync was applied; or

[1232] 3> if the procedure is triggered due to successful completion of Mobility from NR to E- UTRA, for the source PCell in which the last MobilityFromNRCommand concerning an inter-RAT handover from NR to E-UTRA was applied:

[1233] 4> set the sourcePCelllD in sourceCelllnfo to the global cell identity and tracking area code, if available, of the source PCell;4> set the sourceCellMeas in sourceCelllnfo to include the cell level RSRP, RSRQ and the available SINR, of the source PCell based on the available SSB and CSI- RS measurements collected up to the moment the UE sends RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E- UTRA;

[1234] 4> set the rsIndexResults in sourceCellMeas to include all the available SSB and CSI- RS measurement quantities of the source PCell collected up to the moment the UE sends RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E- UTRA;

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

[1236] 5> set the rlf-InSourceDAPS in sourceCellInfo to true;

[1237] 3> if the procedure is triggered due to successful completion of reconfiguration with sync, for the target PCell indicated in the last applied RRCReconfiguration message including reconfigurationWithSync.

[1238] 4> set the targetPCellID in targetCellInfo to the global cell identity and tracking area code, if available, of the target PCell; otherwise, set the targetCell-PCI-ARFCN to the physical cell identity and carrier frequency of the target PCell;

[1239] NOTE 00: If targetCell-PCI-ARFCN is included, it is left to UE implementation how to set the targetPCellID.

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

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

[1242] 4> if the last applied RRCReconfiguration message including reconfigurationWithSync was included in the stored condRRCReconfig:

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

[1244] 3> if the procedure is triggered due to successful completion of Mobility from NR to E- UTRA, for the target PCell indicated in the last applied MobilityFromNRCommand concerning an inter-RAT handover from NR to E-UTRA:4> set the targetPCellId in eutra-TargetCellInfo to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell;

[1245] 4> set the targetCellMeas in eutra-TargetCelllnfo to include the cell level RSRP, RSRQ and the available SINR, of the target PCell based on the available measurements collected up to the moment the UE sends RRCConnectionReconfigurationComplete message;

[1246] NOTE 0: If eutra-TargetCellInfo is included, it is left to UE implementation how to set the targetCelllnfo.

[1247] 3> 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 T304 timer, 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:

[1248] 4> set t304-cause in shr-Cause to true;

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

[1250] 3> if the ratio between the value of the elapsed time of the timer T310 and the configured value of the T310 timer, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync or 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 reconfiguration with sync or Mobility from NR to E-UTRA:

[1251] 4> set t310-cause in shr-Cause to true;

[1252] 3> if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the reconfiguration with sync procedure or 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 T312 timer, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync or 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 reconfiguration with sync, or Mobility from NR to E-UTRA:

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

[1254] 3> if the procedure is triggered due to successful completion of reconfiguration with sync and if sourceDAPS-FailureReporting included in the successHO-Config if configured by the source PCell before executing the last reconfiguration with sync is set to true, and if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running:

[1255] 4> set sourceDAPS-Failure in shr-Cause to true;

[1256] 3> if the procedure is triggered due to successful completion of reconfiguration with sync, for each of the measObjectNR, configured by the source PCell, in which the last RRCReconfiguration message including reconfigurationWithSync was applied;or:> if the procedure is triggered due to successful completion of Mobility from NR to E- UTRA, for each of the measObjectNR, configured by the source PCell, in which the last MobilityFromNRCommand concerning an inter-RAT handover from NR to E- UTRA was applied:

[1257] 4> if measRSSI-ReportConfig is configured for the frequency of the source PCell: 5> if the procedure is triggered due to successful completion of reconfiguration with sync:

[1258] 6> set the measResultServCellRSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency of the source PCell up to the moment the UE sends the RRCReconfigurationComplete message;

[1259] 5> else if the procedure is triggered due to successful completion of Mobility from NRto E-UTRA:

[1260] 6> set the measResultServCellRSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency of the source PCell up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message;

[1261] 4> for each of the configured measObjectNR if measRSSI-ReportConfig is configured for the configured frequency:

[1262] 5> if the procedure is triggered due to successful completion of reconfiguration with sync:

[1263] 6> set the measResultNeighFreqRSSI in the measResultNeighFreqListRSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the associated neighbouring frequency up to the moment the UE sends the RRCReconfigurationComplete message:

[1264] 7> for each neighbour frequency included, include the optional fields that are available;

[1265] 5> else if the procedure is triggered due to successful completion of Mobility from NRto E-UTRA:

[1266] 6> set the measResultNeighFreqRSSI in the measResultNeighFreqListRSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the associated neighbouring frequency up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message: 7> for each neighbour frequency included, include the optional fields that are available;

[1267] 4> if measurements are available for the measObjectNR or the measObjectNR is associated with a reportConfigNR including a condEventT1, condEventD1 or condEventD2.

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

[1269] 6> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell or target PCell, ordered such that the cell with highestSS / PBCH block RSRP is listed first if SS / PBCH block RSRP measurement results are available, otherwise the cell with highest SS / PBCH block RSRQ is listed first if SS / PBCH block RSRQ measurement results are available, otherwise the cell with highest SS / PBCH block SINR is listed first, based on the available SS / PBCH block based measurements collected up to the moment the UE sends the RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA; 6> for each neighbour cell included, include the optional fields that are available;

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

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

[1272] 6> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell and target PCell, ordered such that the cell with highest CSI- RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the cell with highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the cell with highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE sends the RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA; 6> for each neighbour cell included, include the optional fields that are available;

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

[1274] 5> if measResultListNR in measResultNeighCells includes fewer than maxCellReport MeasResultNR IES and the measObjectNR is associated with a reportConfigNR including a condEventT1, condEventD1 or condEventD2;

[1275] 6> for each neighbour cell associated with the measObjectNR for which no measurement quantities are available:

[1276] 7> if measResultListNR in measResultNeighCells includes fewer than maxCellReport MeasResultNR IEs:

[1277] 8> include a MeasResultNR IE in measResultListNR in measResultNeighCells and leave the resultsSSB-Cell, resultsCSI-RS-Cell and rsIndexResults absent; NOTE 3: Neighbouring cells for which no measurement quantities are available are placed after neighbouring cells for which measurement quantities are available in measResultListNR in measResultNeighCells.3> if the procedure is triggered due to successful completion of reconfiguration with sync, for each of the measObjectEUTRA, configured by the source PCell in which the last RRCReconfiguration message including reconfigurationWithSync was applied; or: 3> if the procedure is triggered due to successful completion of Mobility from NR to E- UTRA, for each of the measObjectEUTRA, configured by the source PCell in which the last MobilityFromNRCommand concerning an inter-RAT handover from NR to E- UTRA was applied:

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

[1279] 5> set the measResultListEUTRA in measResultNeighCells to include the best measured cells ordered such that the cell with highest RSRP is listed first if RSRP measurement results are available, otherwise the cell with highest RSRQ is listed first, based on measurements collected up to the moment the UE sends the RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E- UTRA;

[1280] 5> for each neighbour cell included, include the optional fields that are available; 3> for each of the neighbour cells included in measResultNeighCells:

[1281] 4> if the cell was a candidate target cell included in the condRRCReconfig within the conditionalReconfiguration configured by the source PCell, in which the last RRCReconfiguration message including reconfigurationWithSync was applied: 5> set the choCandidate to true in measResultNR,'

[1282] 5> set choConfig in MeasResultNR to the execution condition for each measld within condTriggerConfig associated with the neighbour cell within the MCG VarConditionalReconfig, (Note that in a possible variation of this implementation example, this statement is absent.)

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

[1284] 3> if the procedure is triggered due to successful completion of reconfiguration with sync, and the last applied RRCReconfiguration message including reconfigurationWithSync was concerning a conditional handover:

[1285] 4> set choConfigCellList to include the execution condition (one or two trigger event(s)) for the measld within condTriggerConfig associated with each of the candidate target cells within the MCG VarConditionalReconfig at the time of successful conditional handover, excluding the candidate target cells included in measResultNeighCell',

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

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

[1288] ******************************************************************************************Implementation example 3 of the third embodiments, procedural logic for the successful PSCell addition or change report:

[1289] 5.7.10.7 Actions for the successful PSCell change or addition report determination (Note that the section number is from 3GPP TS 38.331 version 18.4.0.)

[1290] The UE shall for the PSCell:

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

[1292] 1> if sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is configured and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync for the SCG, is greater than thresholdPercentageT310-SCG included in the successPSCell-Config if configured by the source PSCell before executing the last reconfiguration with sync for the SCG; or

[1293] 1> if sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is configured and if the T312 associated to the measurement identity of the target PSCell was running at the time of initiating the execution of the reconfiguration with sync procedure for the SCG and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312-SCG included in the successPSCell- Config if configured by the source PSCell before executing the last reconfiguration with sync for the SCG:

[1294] 1> if sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is not configured and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync for the SCG, is greater than thresholdPercentageT310-SCG included in the successPSCell-Config if configured by the PCell before executing the last reconfiguration with sync for the SCG; or

[1295] 1> if sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is not configured and if the T312 associated to the measurement identity of the target PSCell was running at the time of initiating the execution of the reconfiguration with sync procedure for the SCG and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312-SCG included in the successPSCell- Config if configured by the PCell before executing the last reconfiguration with sync for the SCG:

[1296] 2> clear the information included in VarSuccessPSCell-Report, if any;

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

[1298] 3> if the UE is not in SNPN access mode, set the plmn-IdentityList to include the list of EPLMNs (including the RPLMN) stored by the UE;3> else if the UE is in SNPN access mode, set the snpn-IdentityList to include the list of equivalent SNPN identities (including the registered SNPN identity) stored by the UE, if available;

[1299] 3> set the pCellld to the global cell identity and tracking area code, if available, of the PCell; 3> for the source PSCell (in case of PSCell change procedure) in which the last RRCReconfiguration message for the SCG including reconfigurationWithSync was applied: 4> set the sourcePSCellld in sourcePSCelllnfo to the global cell identity and tracking area code, and otherwise to the physical cell identity and carrier frequency of the source PSCell;

[1300] 4> set the sourcePSCellMeas in sourcePSCelllnfo to include the cell level RSRP, RSRQ and the available SINR, of the source PSCell based on the available SSB and CSI-RS measurements collected up to the moment the UE successfully completed the random access procedure for the SCG;

[1301] 4> set the rsIndexResults in sourcePSCellMeas to include all the available SSB and CSI-RS measurement quantities of the source PSCell collected up to the moment the UE successfully completed the random access procedure for the SCG;

[1302] 3> for the target PSCell indicated in the last applied RRCReconfiguration message for the SCG including reconfigurationWithSync.

[1303] 4> set the targetPSCellID in targetPSCelllnfo to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PSCell;

[1304] 4> set the targetPSCellMeas in targetPSCelllnfo to include the cell level RSRP, RSRQ and the available SINR, of the target PSCell based on the available SSB and CSI-RS measurements collected up to the moment the UE successfully completed the random access procedure for the SCG;

[1305] 4> set the rsIndexResults in targetPSCellMeas to include all the available SSB and CSI-RS measurement quantities of the target PSCell collected up to the moment the UE successfully completed the random access procedure for the SCG;

[1306] 4> if the last applied RRCReconfiguration message for the SCG including reconfigurationWithSync was included in the stored condRRCReconfig:

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

[1308] 3> if triggering threshold for storing the successful PSCell change or addition information in VarSuccessPSCell-Report\)asQ& on the thresholdPercentageT304-SCG is met:

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

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

[1311] 3> if triggering threshold for storing the successful PSCell change or addition information in VarSuccessPSCell-Report based on the thresholdPercentageT310-SCG is met:4> set t310-cause in spr-Cause to true,'

[1312] 3> if triggering threshold for storing the successful PSCell change or addition information in VarSuccessPSCell-Report based on the thresholdPercentageT312-SCG is met:

[1313] 4> set t312-cause in spr-Cause to true,'

[1314] 3> if sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is configured:

[1315] 4> consider all measObjectNR configured by the source PSCell;

[1316] 3> else:

[1317] 4> consider all measObjectNR configured by the PCell;

[1318] 3> for each of the considered measObjectNR:

[1319] 4> if measurements are available for the measObjectNR or the measObjectNR is associated with a reportConfigNR including a condEventT1, condEventD1 or condEventD2.

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

[1321] 6> include in the measResultListNR in measResultNeighCells all the available measurement quantities of the best measured cells, other than the source PSCell (in case of PSCell change procedure) or target PSCell, ordered such that the cell with highest SS / PBCH block RSRP is listed first if SS / PBCH block RSRP measurement results are available, otherwise the cell with highest SS / PBCH block RSRQ is listed first if SS / PBCH block RSRQ measurement results are available, otherwise the cell with highest SS / PBCH block SINR is listed first, based on the available SS / PBCH block based measurements collected up to the moment the UE successfully completed the random access procedure;

[1322] 6> for each neighbour cell included, include the optional fields that are available (including the CSI-RS based measurement quantities, if available); 5> if the CSI-RS measurement quantities are available for the cells not yet included in measResultListNR in measResultNeighCells:

[1323] 6> include in the measResultListNR in measResultNeighCells all the available measurement quantities of the best measured cells, other than the source PSCell (in case of PSCell change procedure) and target PSCell, ordered such that the cell with highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the cell with highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the cell with highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE successfully completed the random access procedure;

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

[1325] 5> if measResultListNR in measResultNeighCells includes fewer than maxCellReport MeasResultNR IES and the measObjectNR is associated with a reportConfigNR including a condEventT1, condEventD1 or condEventD2;6> for each neighbour cell associated with the measObjectNR for which no measurement quantities are available:

[1326] 7> if measResultListNR in measResultNeighCells includes fewer than maxCellReport MeasResultNR IES:

[1327] 8> include a MeasResultNR IE in measResultListNR in measResultNeighCells and leave the resultsSSB-Cell, resultsCSI-RS-Cell and rsIndexResults absent; NOTE 1: Neighbouring cells for which no measurement quantities are available are placed after neighbouring cells for which measurement quantities are available in measResultListNR in measResultNeighCells.

[1328] 3> for each of the neighbour cells included in measResultNeighCells:

[1329] 4> if the cell was a candidate target cell included in the condRRCReconfig within the conditionalReconfiguration, configured by the source PCell including the condExecutionCond within the conditionalReconfiguration associated to condEventA4 or by the source PSCell (in case of PSCell change) when the last RRCReconfiguration message for the SCG including reconfigurationWithSync was applied:

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

[1331] 5> set choConfig in MeasResultNR to the execution condition for each measld within condTriggerConfig associated with the neighbour cell within the MCG VarConditionalReconfig; (Note that in a possible variation of this implementation example, this statement is absent.)

[1332] 3> if the procedure is triggered due to successful completion of reconfiguration with sync, and the last applied RRCReconfiguration message including reconfigurationWithSync was concerning a conditional PSCell addition or change: 4> set choConfigCellList to include the execution condition (one or two trigger event(s)) for the measld within condTriggerConfig associated with each of the candidate target cells within the MCG VarConditionalReconfig at the time of successful conditional PSCell addition or change, excluding the candidate target cells included in measResultNeighCell.

[1333] 3> if sn-InitiatedPSCellChange associated to the last applied RRCReconfiguration with reconfigurationWithSync for the SCG is configured:

[1334] 4> if available, set the locationinfo as in 5.3.3.7 according to the otherConfig associated with the source PSCell;

[1335] 4> include sn-InitiatedPSCellChange,'

[1336] 3> else:

[1337] 4> if available, set the locationinfo as in 5.3.3.7 according to the otherConfig associated with the PCell;

[1338] 1> release successPSCell-Config configured by the source PSCell if available and thresholdPercentageT304 if configured by the target PSCell.

[1339] The UE may discard the successful PSCell change or addition information, i.e., release the UE variable VarSuccessPSCell-Report, 48 hours after the last successful PSCell change or addition information is added to the VarSuccessPSCell-Report or upon deregistration from the network as specified in TS 23.502

[0043] ,Figure 5 and Figure 6 illustrate further optional details of the UE 1001 and a network node 600, such as the source network node 1002 or the target network node 1003. The UE 1001 is configured to perform the method actions of Figure 3 above. The network node 600 is configured to perform actions described above, for example in relation Figure 4.

[1340] The embodiments herein may be implemented through a processor or one or more processors, such as the processor 504, 604 of a processing circuitry of the UE 1001 and the network node 600, and depicted in Figures 5-6 together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the UE 1001 and the network node 600. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the UE 1001 and the network node 600.

[1341] The UE 1001 and the network node 600 may further comprise a memory 502, 602 comprising one or more memory units. The memory comprises instructions executable by the processor in the UE 1001 and the network node 600.

[1342] The respective memory 502, 602 is arranged to be used to store e.g. information, data, configurations, and applications to perform the methods herein when being executed in the UE 1001 and the network node 600.

[1343] In some embodiments, a computer program 503, 603 comprises instructions, which when executed by the at least one processor, cause the at least one processor of the UE 1001 and the network node 600 to perform the actions above.

[1344] In some embodiments, a carrier 505, 605 comprises the computer program, wherein the carrier is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.The UE 1001 and the network node 600 may further comprise an input and output interface, I / O, 506, 606 configured to communicate with other devices. The input and output interface 506, 606 may comprise a wireless transceiver.

[1345] Those skilled in the art will also appreciate that the units described above may refer to a combination of analog and digital circuits, and / or one or more processors configured with software and / or firmware, e.g. stored in the UE 1001 and the network node 600, that when executed by the respective one or more processors such as the processors described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuitry (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a system-on-a-chip (SoC).

[1346] When using the word "comprise" or “comprising” it shall be interpreted as non-limiting, i.e. meaning "consist at least of".

[1347] The embodiments herein are not limited to the above-described preferred embodiments. Various alternatives, modifications and equivalents may be used.Figure QQ1 shows an example of a communication system QQ100 in accordance with some embodiments.

[1348] 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), and a 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 3rd Generation 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.

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

[1350] 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 planeinterface. 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.

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

[1352] 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 QQ112, other network nodes QQ108, QQ110, and other devices in telecommunications network QQ102 directly or indirectly. As one specific example, a core network node QQ108 maytransmit 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 QQ108 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.

[1353] 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 more intermediary 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).

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

[1355] As a whole, the communication system QQ100 of Figure QQ1 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 MobileCommunications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (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 of the relevant rule sets or with different components or sub-systems within the communication system QQ100 supporting different standards, protocols, or rule sets.

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

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

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

[1359] 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 in the 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.

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

[1361] 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. 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 andnetwork node QQ110B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[1362] Figure QQ2 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 fourth BSS, 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.

[1363] 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 contentionbased 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.

[1364] 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 QQ2 illustrates an application service platform QQ232 provided in data network QQ230. The application(s) executed onSTA 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.

[1365] Figure QQ3 shows a wireless device QQ300, which may be configured to operate in communication system QQ100 of Figure QQ1 or in communication system QQ200 of Figure QQ2. 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 a wireless 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.

[1366] 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).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 QQ3. 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. Further, certain embodiments of wireless devices QQ300 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[1367] The processing circuitry QQ302 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 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).

[1368] 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 anycombination 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.

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

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

[1371] 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 (eUlCC), 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 ofmanufacture, 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.

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

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

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

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

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

[1377] 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. Nonlimiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a 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 QQ3.

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

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

[1380] Figure QQ4 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 QQ1, like network nodes QQ108 or QQ110, or in communication system QQ200 of Figure QQ2, like an 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., 0-Rll, O-DU, O-CU).

[1381] 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).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-cel l / 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).

[1382] 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 powe...

Claims

CLAIMS1. A method, performed by a wireless communication device (1001), the method comprises:triggering (302) a mobility-related report for a neighbouring cell (1008); and transmitting (303) the mobility-related report to a network node (600) without RRM measurements on the neighbouring cell (1008), wherein the mobility-related report comprises Conditional Hand-Over, CHO, -related information.

2. The method according to claim 1, wherein the CHO-related information comprises time- or location-based CHO configuration-related information or both.

3. The method according to claim 2, wherein the time- or location-based CHO configuration-related information or both comprises time- or location-based CHO configured candidate cells and / or a time- or location-based trigger condition for CHO.

4. The method according to any of the claims 2-3, wherein the time- or location-based CHO configuration-related information or both is reported to the network node (600) in:4) an information element for reporting RRM measurements; or 5) one or more other fields in the mobility-related report outside the information element for reporting RRM measurements; or 6) both 1) and 2) above.

5. The method according to claim 4, wherein the information element comprising the time- or location-based CHO-related information does not comprise RRM measurements.

6. The method according to any of the claims 1-5, wherein the CHO-related information pertains to neighbouring cells (1008) for which no RRM measurements are available.

7. The method according to any of the claims 1-6, wherein the mobility-related report is transmitted without RRM measurements.

8. A wireless communication device (1001) adapted for Conditional Hand-Over, CHO, and further adapted to:trigger a mobility-related report for a neighbouring cell (1008); and transmit the mobility-related report to a network node (600) without RRM measurements on the neighbouring cell (1008), wherein the mobility-related report comprises CHO-related information.

9. The wireless communication device (1001) according to claim 8, further adapted to perform the method of any of the claims 2-7.

10. A method performed by a network node (600), the method comprising:receiving (401), from a wireless communication device (1001), a mobility- related report without RRM measurements and comprising CHO-related information.

11. The method according to claim 10, wherein the CHO-related information comprises time- or location-based CHO configuration-related information or both.

12. A network node (600) adapted for Conditional Hand-Over, CHO, of a wireless communication device (1001), and further adapted to:receive, from a wireless communication device (1001), a mobility-related report without RRM measurements and comprising CHO-related information.

13. The network node (600), further configured to perform the method of claim 11.

14. A computer program (503), comprising computer readable code units which when executed on a computer causes the computer to perform the method according to any of the claims 1-7.

15. A computer program (603), comprising computer readable code units which when executed on a computer causes the computer to perform the method according to any of the claims 10-11.

16. A carrier (505, 605) comprising the computer program (503, 603) according to any of the claims 14-15, wherein the carrier (505, 605) is one of an electronic signal, an optical signal, a radio signal and a computer readable medium.

Images