EP4193676A1

EP4193676A1 - Conditional handover failure reporting in minimization of drive tests (mdt)

Info

Publication number: EP4193676A1
Application number: EP21854263.7A
Authority: EP
Inventors: Candy YIU; Yi Guo
Original assignee: Intel Corp
Current assignee: Intel Corp
Priority date: 2020-08-06
Filing date: 2021-08-06
Publication date: 2023-06-14
Also published as: WO2022032205A1

Abstract

The apparatus of UE, a system, a method and a machine-readable medium. The apparatus includes one or more processors to: generate a report including report information in the memory including an indication of a radio link failure (RLF) at the source cell before CHO execution and after CHO recovery success; and send the report to communications resources of the UE for transmission.

Description

CONDITIONAL HANDOVER FAILURE REPORTING IN MINIMIZATION OF DRIVE TESTS (MDT)

CROSS REFERENCE TO RELATED APPLICATIONS

[0001] This Application claims the benefit of, and priority from, U.S. Provisional Patent Application No. 63/062,255 filed on August 6, 2020 and entitled "CONDITIONAL HANDOVER FAILURE REPORTING IN MINIMIZATION OF DRIVE TESTS (MDT)". The disclosure of the prior application is considered part of and is hereby incorporated by reference in its entirety in the disclosure of this application.

BACKGROUND

[0002] Various embodiments generally may relate to the field of wireless communications, and in particular, to the field of communication in a cellular network compliant with one of more Third Generation Partnership Project (3GPP) specifications.

BRIEF DESCRIPTION OF THE DRAWINGS

[0003] In the drawings, which are not necessarily drawn to scale, like numerals may describe similar components in different views. Like numerals having different letter suffixes may represent different instances of similar components. The drawings illustrate generally, by way of example, but not by way of limitation, various embodiments discussed in the present document.

[0004] Fig. 1 illustrates a flow chart for a process according to a first embodiment.

[0005] Fig. 2 illustrates a flow chart for a process according to a second embodiment.

[0006] Fig. 3 illustrates a wireless network in accordance with various embodiments.

[0007] Fig. 4 illustrates a User Equipment (UE) and a Radio Access Node (RAN) in wireless communication according to various embodiments.

[0008] Fig. 5 illustrates components according to some example embodiments, the components able to read instructions from a machine-readable or computer-readable medium and perform any one or more of the methodologies discussed herein. DETAILED DESCRIPTION

[0009] The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present document, the phrases "A or B" and "A/B" mean (A), (B), or (A and B).

[0010] Self-Organizing Networks (SON), which is a concept that encompasses solutions for network self-configuration and self-optimization, was introduced in 3GPP's Long Term Evolution (LTE) to support deployment of system and performance optimizations. The first SON features, physical cell identification (physical cell ID or PCI) allocation and Automatic Neighbor Relations (ANR) were introduced already in Rel.8 (while the term "SON" was introduced in Rel-9). Success of these two features encouraged further study on the topic and resulted in a Rel.9 work item that eventually enabled 3 SON features: Mobility Robustness Optimization (MRO), Mobility Load Balancing (MLB) and random access channel (RACH) optimization. The two first features, MRO and MLB, turned out to be key enablers of LTE, and were further enhanced in following releases to match increasing LTE complexity. Besides ANR, MRO, MLB and RACH optimization, other features enabling particular aspects of network self-optimization were discussed and enabled in separate study items (Sls)/work items (WIs): Minimization of Drive Tests (MDT), Energy Saving (ES), interference cancelation (inter-cell interference coordination (ICIC), enhanced ICIC (elCIC)), time division duplexing (TDD) uplink (UL)/downlink (DL) traffic adaptation (enhanced interference mitigation and traffic adaptation (elMTA)), collaborative multi-point operation (CoMP), etc.

[0011] The 3GPP study item #801000 "Study on RAN-centric Data Collection and Utilization for LTE and NR" studied use cases of SON/MDT and other use cases related to data collection and utilization, and identified potential solutions for these use cases. The studies in study item #801000 use LTE solutions as a baseline, and take the New Radio (NR) new architectures and features into account, e.g., multi radio access technology (RAT) dual connectivity (MR-DC), centralized unit (CU)-distributed unit (DU) split architecture, beam, inactive state, etc. The feasibility check of layer 1/layer 2 (L1/L2) measurements specified in system aspect work group 5( SA5) technical specification (TS) 28.552 was also accomplished. However, due to limited time, only a subset of potential SON/MDT functions and initial considerations have been studied in 801000. [0012] Moreover, due to the time constrains, it was difficult to accomplish all of the objectives listed in the Rel-16 SON and MDT work item description WID). Some of the leftover features could be considered in Rel-17, potentially including PCI selection, energy efficiency, MDT for MR-DC, RACH Optimization enhancements, enhancement to UE reports for mobility optimization, etc. [0013] Therefore, some embodiments tackle the leftover use cases in listed in the Rel-16 SON and MDT WID ,and further enhancement of SON/MDT, including leftover of Rel-16 Sl/Wls, e.g., CCO, energy saving, Successful HO reports, etc, enhancement of R16 new features enabled by data collection, e.g. 2-step RACH, mobility enhancements.

[0014] One objective of embodiments is to specify data collection enhancement in NR for the purpose SON/MDT mechanisms. Some objectives of embodiments are as follows:

• supporting of data collection for SON features, including coverage and capacity optimization (CCO), inter-system inter-radio access technology (RAT) energy saving, intersystem load balancing, 2-step RACH optimization, mobility enhancement optimization, and leftovers of Rel-16 SON/MDT Wl (PCI selection, energy efficiency (operations, administration and maintenance (0AM) requirements), Successful Handovers Reports, UE history information in Evolved-Universal Terrestrial Radio Access-New Radio dual connectivity(EN-DC), load balancing enhancement, MRO for secondary node (SN) change failure, RACH Optimization enhancements) [radio access node 3 (RAN3), radio access node 2 (RAN2)], including, for example:

- specification of the UE reporting necessary to enhance the network configuration [RAN2]; and/or

- specification of the inter-node information exchange, including possible enhancements to the interface between the RAN (gNB) and Core Network (CN) (Sl/NG), X2/Xn, and Fl/El interfaces [RAN3]; supporting of data collection for MDT features for identified use cases, including 2-step RACH optimization and leftovers of Rel-16 SON/MDT Wl (MDT enhancements and MDT for MR-DC) [RAN2, RAN3, RAN4], such as:

- enhancement of logged and immediate MDT (including coexistence with in-device coexistence (IDC)) [RAN2, RAN3]

- enhancement of reporting e.g. RLF and accessibility measurements, successful handover reporting [RAN2, RAN3],

- specification of MDT for MR-DC [RAN2, RAN3, RAN4]

• specification of L2 measurements, if needed [RAN2, RAN3],

[0015] Some embodiments herein pertain to managing UE handover failure when using CHO in different cases in MDT to assist the network to better configure CHO.

[0016] In Rel. 16, NR introduced conditional handover (CHO), where the network will configure conditional handover conditions to the UE. The UE will elevate the condition during measurement, and, if one or more condition is met, the UE will perform conditional handover execution where the UE will handover (performing RACH) to the target cell. However, there may be cases where the UE handover (HO) will fail. The below lists the cases and the information the UE may need to store for MDT reporting.

• case 1: for radio link failure (RLF) in source cell before conditional handover(CHO) execution:

- in this case, the UE faces RLF in source cell before CHO is triggered;

- the reason could be poor execution of condition configuration (for example, the condition configured reference signal received power (RSRP) to high or "AND" condition is configured, but one of the conditions is never met or a different target cell is configured);

- case 1-1: RLF happens in the source cell before CHO execution but recovery is successful using CHO: o in this case, the UE RLF is at the source cell but then recovery is performed using CHO and is successful; o the information UE may need to store for reporting includes: - indication of RLF at source cell before CHO execution and recovery successful with CHO;

- the execution condition that is configured to the UE (per candidate cell);

- corresponding measurements for candidate cells;

- corresponding cell ID;

- time of receiving condition configuration;

- time of RLF at source cell; and/or

- recovery cell information (includes cell ID, measurement, RACH information, time etc);

- case 1-2: RLF in source cell before CHO execution but recovery failure happens using CHO: o the information the UE may need to store for reporting includes:

- indication of RLF at source cell before CHO execution and recovery failure with CHO;

- the execution condition that is configured to the UE (per candidate cell);

- corresponding measurements for candidate cells;

- corresponding cell ID;

- time of receiving condition configuration;

- time of RLF at source cell; and/or

- case 1-3: reestablishment o in this case, there is no candidate cells good enough during cell selection after failure; o the information UE may need to store for reporting includes: indication of reestablishment after CHO recovery failure; the execution condition that is configured to the UE (per candidate cell); - corresponding measurements for candidate cells;

- corresponding cell identification (ID);

- time of receiving condition configuration;

- time of RLF at source cell;

- recovery cell information (includes cell ID, measurement, RACH information, time etc); and/or

- cell information during cell selection (includes cell ID, measurement, RACH information, time etc);

• case 2: RLF does not get triggered in the source cell before the CHO is triggered:

- in this case, RLF does not get triggered in source cell before CHO is triggered;

- then, CHO is triggered but fails;

- the reason for the above may be poor execution condition configuration for candidate cells;

- case 2-1: CHO failure and then recovery successful based on CHO: o in this case, the UE performs recovery using CHO after CHO failure, and is successful; o the information that the UE may need to store for reporting includes:

- indication of CHO failure and CHO recovery success;

- source cell measurement when CHO failure happens;

- the execution condition that is configured to the UE (per candidate cell);

- corresponding measurements for candidate cells;

- corresponding cell ID;

- time of receiving condition configuration;

- CHO Execution cell information (includes cell ID, measurement, RACH information, time perform CHO execution etc; and/or

- recovery cell information (includes cell ID, measurement, RACH information, time etc). case 2-2: CHO failure and then recovery failure based on CHO o in this case, after CHO failure, the UE perform recovery using CHO and fails; o the information the UE may need to store for reporting includes:

- indication of CHO failure and CHO recovery failure;

- source cell measurement when CHO failure happens;

- the execution condition that is configured to the UE (per candidate cell);

- corresponding measurements for candidate cells;

- corresponding cell ID;

- time of receiving condition configuration;

- recovery cell information (includes cell ID, measurement, RACH information, time etc).

- case 2-3: reestablishment (no candidate cells are good during cell selection) o in this case, after case 2-2, and after reestablishment is triggered and no good cell for cell selection is found; o the information UE should store for reporting:

- indication of CHO failure and CHO recovery failure;

- source cell measurement when CHO failure happens

- the execution condition that is configured to the UE (per candidate cell);

- corresponding measurements for candidate cells;

- corresponding cell ID;

- time of receiving condition configuration;

- CHO Execution cell information (includes cell ID, measurement, RACH information, time perform CHO execution etc;

- recovery cell information (includes cell ID, measurement, RACH information, time etc); and/or cell information during cell selection (includes cell ID, measurement, RACH information, time etc).

[0017] Embodiments Processes:

[0018] Fig. 1 shows a process 100 according to an embodiment. At operation 102, the process includes storing report information in the memory including an indication of a radio link failure (RLF) at the source cell before CHO execution and after CHO recovery success. At operation 104, the process includes generating a report including the report information for transmission by communications resources of the UE.

[0019] Fig. 2 shows a process 200 according to an embodiment. At operation 202, the process includes storing a report information in a memory including an indication of at least one of CHO failure, CHO execution cell information, and CHO recovery success. At operation 204, the process includes generating a report including the report information for transmission by communications resources of a UE.

[0020] Systems And Implementations

[0021] Figs. 3-5 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.

[0022] Fig. 3 illustrates a network 300 in accordance with various embodiments. The network 800 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems. However, the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems, or the like.

[0023] The network 300 may include a UE 302, which may include any mobile or non-mobile computing device designed to communicate with a RAN 304 via an over-the-air connection. The UE 302 may be communicatively coupled with the RAN 304 by a Uu interface. The UE 302 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, loT device, etc.

[0024] In some embodiments, the network 300 may include a plurality of UEs coupled directly with one another via a sidelink interface. The UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

[0025] In some embodiments, the UE 302 may additionally communicate with an AP 306 via an over-the-air connection. The AP 306 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 304. The connection between the UE 302 and the AP 306 may be consistent with any IEEE 302.11 protocol, wherein the AP 306 could be a wireless fidelity (Wi-Fi®) router. In some embodiments, the UE 302, RAN 304, and AP 306 may utilize cel lu la r- WLAN aggregation (for example, LWA/LWIP). Cellular-WLAN aggregation may involve the UE 302 being configured by the RAN 304 to utilize both cellular radio resources and WLAN resources.

[0026] The RAN 304 may include one or more access nodes, for example, AN 308. AN 308 may terminate air-interface protocols for the UE 302 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and LI protocols. In this manner, the AN 308 may enable data/voice connectivity between CN 320 and the UE 302. In some embodiments, the AN 308 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool. The AN 308 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 308 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

[0027] In embodiments in which the RAN 304 includes a plurality of ANs, they may be coupled with one another via an X2 interface (if the RAN 304 is an LTE RAN) or an Xn interface (if the RAN 304 is a 5G RAN). The X2/Xn interfaces, which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc.

[0028] The ANs of the RAN 304 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 302 with an air interface for network access. The UE 302 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 304. For example, the UE 302 and RAN 304 may use carrier aggregation to allow the UE 302 to connect with a plurality of component carriers, each corresponding to a Pcell or See II . In dual connectivity scenarios, a first AN may be a master node that provides an MCG and a second AN may be secondary node that provides an SCG. The first/second ANs may be any combination of eNB, gNB, ng-eNB, etc.

[0029] The RAN 304 may provide the air interface over a licensed spectrum or an unlicensed spectrum. To operate in the unlicensed spectrum, the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCel Is/Scel Is. Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.

[0030] In V2X scenarios the UE 302 or AN 308 may be or act as a RSU, which may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by: a UE may be referred to as a "UE-type RSU"; an eNB may be referred to as an "eNB-type RSU"; a gNB may be referred to as a "gNB-type RSU"; and the like. In one example, an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communications services. The components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.

[0031] In some embodiments, the RAN 304 may be an LTE RAN 310 with eNBs, for example, eNB 312. The LTE RAN 310 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE. The LTE air interface may operating on sub-6 GHz bands.

[0032] In some embodiments, the RAN 304 may be an NG-RAN 314 with gNBs, for example, gNB 316, or ng-eNBs, for example, ng-eNB 318. The gNB 316 may connect with 5G-enabled UEs using a 5G NR interface. The gNB 316 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 318 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface. The gNB 316 and the ng-eNB 318 may connect with each other over an Xn interface.

[0033] In some embodiments, the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 314 and a UPF 348 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN314 and an AMF 344 (e.g., N2 interface).

[0034] The NG-RAN 314 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data. The 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface. The 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking. The 5G-NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH.

[0035] In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWP can be used for dynamic adaptation of the SCS. For example, the UE 302 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 302, the SCS of the transmission is changed as well. Another use case example of BWP is related to power saving. In particular, multiple BWPs can be configured for the UE 302 with different amount of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 302 and in some cases at the gNB 316. A BWP containing a larger number of PRBs can be used for scenarios with higher traffic load. [0036] The RAN 304 is communicatively coupled to CN 320 that includes network elements to provide various functions to support data and telecommunications services to customers/subscribers (for example, users of UE 302). The components of the CN 320 may be implemented in one physical node or separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 320 onto physical compute/storage resources in servers, switches, etc. A logical instantiation of the CN 320 may be referred to as a network slice, and a logical instantiation of a portion of the CN 320 may be referred to as a network sub-slice.

[0037] In some embodiments, the CN 320 may be an LTE CN 322, which may also be referred to as an EPC. The LTE CN 322 may include MME 324, SGW 326, SGSN 328, HSS 330, PGW 332, and PCRF 334 coupled with one another over interfaces (or "reference points") as shown. Functions of the elements of the LTE CN 322 may be briefly introduced as follows.

[0038] The MME 324 may implement mobility management functions to track a current location of the UE 302 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.

[0039] The SGW 326 may terminate an SI interface toward the RAN and route data packets between the RAN and the LTE CN 322. The SGW 326 may be a local mobility anchor point for inter- RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.

[0040] The SGSN 328 may track a location of the UE 302 and perform security functions and access control. In addition, the SGSN 328 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 324; MME selection for handovers; etc. The S3 reference point between the MME 324 and the SGSN 328 may enable user and bearer information exchange for inter-3GPP access network mobility in idle/active states.

[0041] The HSS 330 may include a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The HSS 330 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc. An S6a reference point between the HSS 330 and the MME 324 may enable transfer of subscription and authentication data for authenticating/authorizing user access to the LTE CN 320.

[0042] The PGW 332 may terminate an SGi interface toward a data network (DN) 336 that may include an application/content server 338. The PGW 332 may route data packets between the LTE CN 322 and the data network 336. The PGW 332 may be coupled with the SGW 326 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 332 may further include a node for policy enforcement and charging data collection (for example, PCEF). Additionally, the SGi reference point between the PGW 332 and the data network YX 36 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services. The PGW 332 may be coupled with a PCRF 334 via a Gx reference point. [0043] The PCRF 334 is the policy and charging control element of the LTE CN 322. The PCRF 334 may be communicatively coupled to the app/content server 338 to determine appropriate QoS and charging parameters for service flows. The PCRF 332 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCL

[0044] In some embodiments, the CN 320 may be a 5GC 340. The 5GC 340 may include an AUSF 342, AMF 344, SMF 346, UPF 348, NSSF 350, NEF 352, NRF 354, PCF 356, UDM 358, and AF 360 coupled with one another over interfaces (or "reference points") as shown. Functions of the elements of the 5GC 340 may be briefly introduced as follows.

[0045] The AUSF 342 may store data for authentication of UE 302 and handle authentication- related functionality. The AUSF 342 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 340 over reference points as shown, the AUSF 342 may exhibit an Nausf service-based interface.

[0046] The AMF 344 may allow other functions of the 5GC 340 to communicate with the UE 302 and the RAN 304 and to subscribe to notifications about mobility events with respect to the UE 302. The AMF 344 may be responsible for registration management (for example, for registering UE 302), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 344 may provide transport for SM messages between the UE 302 and the SMF 346, and act as a transparent proxy for routing SM messages. AMF 344 may also provide transport for SMS messages between UE 302 and an SMSF. AMF 344 may interact with the AUSF 342 and the UE 302 to perform various security anchor and context management functions. Furthermore, AMF 344 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 304 and the AMF 344; and the AMF 344 may be a termination point of NAS (N 1) signaling, and perform NAS ciphering and integrity protection. AMF 344 may also support NAS signaling with the UE 302 over an N3 IWF interface.

[0047] The SMF 346 may be responsible for SM (for example, session establishment, tunnel management between UPF 348 and AN 308); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 348 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 344 over N2 to AN 308; and determining SSC mode of a session. SM may refer to management of a PDU session, and a PDU session or "session" may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 302 and the data network 336.

[0048] The UPF 348 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 336, and a branching point to support multi-homed PDU session. The UPF 348 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF-to- QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 348 may include an uplink classifier to support routing traffic flows to a data network.

[0049] The NSSF 350 may select a set of network slice instances serving the UE 302. The NSSF 350 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed. The NSSF 350 may also determine the AMF set to be used to serve the UE 302, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 354. The selection of a set of network slice instances for the UE 302 may be triggered by the AMF 344 with which the UE 302 is registered by interacting with the NSSF 350, which may lead to a change of AMF. The NSSF 350 may interact with the AMF 344 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 350 may exhibit an Nnssf service-based interface.

[0050] The NEF 352 may securely expose services and capabilities provided by 3GPP network functions for third party, internal exposure/re-exposure, AFs (e.g., AF 360), edge computing or fog computing systems, etc. In such embodiments, the NEF 352 may authenticate, authorize, or throttle the AFs. NEF 352 may also translate information exchanged with the AF 360 and information exchanged with internal network functions. For example, the NEF 352 may translate between an AF-Service-ldentifier and an internal 5GC information. NEF 352 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 352 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 352 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 352 may exhibit an Nnef servicebased interface.

[0051] The NRF 354 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 354 also maintains information of available NF instances and their supported services. As used herein, the terms "instantiate," "instantiation," and the like may refer to the creation of an instance, and an "instance" may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 354 may exhibit the Nnrf service-based interface.

[0052] The PCF 356 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior. The PCF 356 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 358. In addition to communicating with functions over reference points as shown, the PCF 356 exhibit an Npcf service-based interface.

[0053] The UDM 358 may handle subscription-related information to support the network entities' handling of communication sessions, and may store subscription data of UE 302. For example, subscription data may be communicated via an N8 reference point between the UDM 358 and the AMF 344. The UDM 358 may include two parts, an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 358 and the PCF 356, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 302) for the NEF 352. The Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 358, PCF 356, and NEF 352 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM may include a UDM-FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management. In addition to communicating with other NFs over reference points as shown, the UDM 358 may exhibit the Nudm service-based interface.

[0054] The AF 360 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control.

[0055] In some embodiments, the 5GC 340 may enable edge computing by selecting operator/3rd party services to be geographically close to a point that the UE 302 is attached to the network. This may reduce latency and load on the network. To provide edge-computing implementations, the 5GC 340 may select a UPF 348 close to the UE 302 and execute traffic steering from the UPF 348 to data network 336 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 360. In this way, the AF 360 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 360 is considered to be a trusted entity, the network operator may permit AF 360 to interact directly with relevant NFs. Additionally, the AF 360 may exhibit an Naf service-based interface.

[0056] The data network 336 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application/content server 338.

[0057] Fig. 4 schematically illustrates a wireless network 400 in accordance with various embodiments. The wireless network 400 may include a UE 402 in wireless communication with an AN 404. The UE 402 and AN 404 may be similar to, and substantially interchangeable with, like- named components described elsewhere herein.

[0058] The UE 402 may be communicatively coupled with the AN 404 via connection 406. The connection 406 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies.

[0059] The UE 402 may include a host platform 408 coupled with a modem platform 410. The host platform 408 may include application processing circuitry 412, which may be coupled with protocol processing circuitry 414 of the modem platform 410. The application processing circuitry 412 may run various applications for the UE 402 that source/sink application data. The application processing circuitry 412 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations

[0060] The protocol processing circuitry 414 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 406. The layer operations implemented by the protocol processing circuitry 414 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.

[0061] The modem platform 410 may further include digital baseband circuitry 416 that may implement one or more layer operations that are "below" layer operations performed by the protocol processing circuitry 414 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.

[0062] The modem platform 410 may further include transmit circuitry 418, receive circuitry 420, RF circuitry 422, and RF front end (RFFE) 424, which may include or connect to one or more antenna panels 426. Briefly, the transmit circuitry 418 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.; the receive circuitry 420 may include an analog-to-digital converter, mixer, IF components, etc.; the RF circuitry 422 may include a low- noise amplifier, a power amplifier, power tracking components, etc.; RFFE 424 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc. The selection and arrangement of the components of the transmit circuitry 418, receive circuitry 420, RF circuitry 422, RFFE 424, and antenna panels 426 (referred generically as "transmit/receive components") may be specific to details of a specific implementation such as, for example, whether communication is time division multiplexed (TDM) or frequency division multiplexed (FDM), in mmWave or sub-6 gHz frequencies, etc. In some embodiments, the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc.

[0063] In some embodiments, the protocol processing circuitry 414 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components.

[0064] A UE reception may be established by and via the antenna panels 426, RFFE 424, RF circuitry 422, receive circuitry 420, digital baseband circuitry 416, and protocol processing circuitry 414. In some embodiments, the antenna panels 426 may receive a transmission from the AN 404 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 426.

[0065] A UE transmission may be established by and via the protocol processing circuitry 414, digital baseband circuitry 416, transmit circuitry 418, RF circuitry 422, RFFE 424, and antenna panels 426. In some embodiments, the transmit components of the UE 404 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 426.

[0066] Similar to the UE 402, the AN 404 may include a host platform 428 coupled with a modem platform 430. The host platform 428 may include application processing circuitry 432 coupled with protocol processing circuitry 434 of the modem platform 430. The modem platform may further include digital baseband circuitry 436, transmit circuitry 438, receive circuitry 440, RF circuitry 442, RFFE circuitry 444, and antenna panels 446. The components of the AN 404 may be similar to and substantially interchangeable with like-named components of the UE 402. In addition to performing data transmission/reception as described above, the components of the AN 408 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

[0067] Fig. 5 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, Fig. 5 shows a diagrammatic representation of hardware resources 500 including one or more processors (or processor cores) 510, one or more memory/storage devices 520, and one or more communication resources 530, each of which may be communicatively coupled via a bus 540 or other interface circuitry. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 502 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 500.

[0068] The processors 510 may include, for example, a processor 512 and a processor 514. The processors 510 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

[0069] The memory/storage devices 520 may include main memory, disk storage, or any suitable combination thereof. The memory/storage devices 520 may include, but are not limited to, any type of volatile, non-volatile, or semi-volatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.

[0070] The communication resources 530 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 504 or one or more databases 506 or other network elements via a network 508. For example, the communication resources 530 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.

[0071] Instructions 550 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 510 to perform any one or more of the methodologies discussed herein. The instructions 550 may reside, completely or partially, within at least one of the processors 510 (e.g., within the processor's cache memory), the memory/storage devices 520, or any suitable combination thereof. Furthermore, any portion of the instructions 550 may be transferred to the hardware resources 500 from any combination of the peripheral devices 504 or the databases 506. Accordingly, the memory of processors 510, the memory/storage devices 520, the peripheral devices 504, and the databases 506 are examples of computer-readable and machine-readable media.

[0072] For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.

[0073] Examples:

[0074] Example 1 includes an apparatus of a New Radio (NR) User Equipment (UE), the apparatus including a memory, and one or more processors coupled to the memory, the one or more processors to: store a first report information in the memory including an indication of a radio link failure (RLF) at the source cell before CHO execution and after CHO recovery success; and generate a first report including the first report information for transmission by communications resources of the UE.

[0075] Example 2 includes the subject matter of Example 1, the one or more processors further to store a second report information in the memory including an indication of a radio link failure (RLF) at the source cell before CHO execution and after a CHO recovery failure, and generate a second report including the second report information for transmission by communications resources of the UE.

[0076] Example 3 includes the subject matter of Example 1, the one or more processors to store a third report information in the memory including at least one of: an indication of a radio link failure (RLF) at the source cell before CHO execution and after a CHO recovery failure, an indication of reestablishment after CHO recovery failure, or cell information during cell selection, and generate a third report including the second report information for transmission by the communications resources of the UE.

[0077] Example 4 includes the subject matter of any one of Examples 1-3, wherein the report information further includes an indication of a time of RFL at the source cell.

[0078] Example 5 includes the subject matter of any one of Examples 1-3, wherein the report information further includes at least one of: an execution condition configured to the UE, corresponding measurements for candidate cells, corresponding cell identification (ID), a time of receiving condition configuration, and recovery cell information.

[0079] Example 6 includes the subject matter of Example 1, the one or more processors to store a fourth report information in the memory including an indication of CHO failure and CHO recovery success, and generate a fourth report including the fourth report information for transmission by the communications resources of the UE.

[0080] Example 7 includes the subject matter of Example 1, the one or more processors to store a fifth report information in the memory including at least o7 of: an indication of CHO failure and CHO recovery failure, or source cell measurement when CHO failure happens, and generate a fifth report including the fifth report information for transmission by the communications resources of the UE.

[0081] Example 8 includes the subject matter of Example 1, the one or more processors to store sixth report information in the memory including at least one of: an indication of CHO failure and CHO recovery failure, source cell measurement when CHO failure happens, or cell information during cell selection, and generate a sixth report including the sixth report information for transmission by the communications resources of the UE.

[0082] Example 9 includes the subject matter of any one of Examples 6-8, wherein the report information including the indication of CHO failure further includes CHO execution cell information.

[0083] Example 10 includes the subject matter of any one of Examples 6-8, wherein the report information further includes at least one of: an execution condition configured to the UE, corresponding measurements for candidate cells, corresponding cell identification (ID), a time of receiving condition configuration, and recovery cell information.

[0084] Example 11 includes the subject matter of Example 10, wherein the recovery cell information includes random access channel (RACH) information.

[0085] Example 12 includes the subject matter of any one of Examples 1-3 and 6-8, further including the communications resources.

[0086] Example 13 includes a method to be performed at an apparatus of a New Radio (NR) User Equipment (UE), the method including: storing a first report information in the memory including an indication of a radio link failure (RLF) at the source cell before CHO execution and after CHO recovery success; and generating a first report including the first report information for transmission by communications resources of the UE.

[0087] Example 14 includes the subject matter of Example 13, the method further including storing a second report information in the memory including an indication of a radio link failure (RLF) at the source cell before CHO execution and after a CHO recovery failure, and generating a second report including the second report information for transmission by communications resources of the UE.

[0088] Example 15 includes the subject matter of Example 13, the method further including storing a third report information in the memory including at least one of: an indication of a radio link failure (RLF) at the source cell before CHO execution and after a CHO recovery failure, an indication of reestablishment after CHO recovery failure, or cell information during cell selection, and generating a third report including the second report information for transmission by the communications resources of the UE.

[0089] Example 16 includes the subject matter of Example 13, wherein the report information further includes an indication of a time of RFL at the source cell.

[0090] Example 17 includes the subject matter of Example 13, wherein the report information further includes at least one of: an execution condition configured to the UE, corresponding measurements for candidate cells, corresponding cell identification (ID), a time of receiving condition configuration, and recovery cell information.

[0091] Example 18 includes the subject matter of Example 13, the method further including storing a fourth report information in the memory including an indication of CHO failure and CHO recovery success, and generating a fourth report including the fourth report information for transmission by the communications resources of the UE.

[0092] Example 19 includes the subject matter of Example 13, the method further including storing a fifth report information in the memory including at least one of: an indication of CHO failure and CHO recovery failure, or source cell measurement when CHO failure happens, and generating a fifth report including the fifth report information for transmission by the communications resources of the UE.

[0093] Example 20 includes the subject matter of Example 13, the method further including storing sixth report information in the memory including at least one of: an indication of CHO failure and CHO recovery failure, source cell measurement when CHO failure happens, or cell information during cell selection, and generating a sixth report including the sixth report information for transmission by the communications resources of the UE.

[0094] Example 21 includes the subject matter of Example 18, wherein the report information including the indication of CHO failure further includes CHO execution cell information.

[0095] Example 22 includes the subject matter of Example 18, wherein the report information further includes at least one of: an execution condition configured to the UE, corresponding measurements for candidate cells, corresponding cell identification (ID), a time of receiving condition configuration, and recovery cell information. [0096] Example 23 includes the subject matter of Example 13, further including using the communications resources to communicate with the source cell..

[0097] Example 24 includes a machine readable medium including code, when executed, to cause a machine to perform the method of any one of claims 13-23.

[0098] Example 25 includes an apparatus including means to perform the method of any one of claims 13-23.

[0099] Example Z01 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-8, or any other method or process described herein.

[0100] Example Z02 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-8, or any other method or process described herein.

[0101] Example Z03 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1-8, or any other method or process described herein.

[0102] Example Z04 may include a method, technique, or process as described in or related to any of examples 1-8, or portions or parts thereof.

[0103] Example Z05 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-8, or portions thereof.

[0104] Example Z06 may include a signal as described in or related to any of examples 1-8, or portions or parts thereof.

[0105] Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-8, or portions or parts thereof, or otherwise described in the present disclosure.

[0106] Example Z08 may include a signal encoded with data as described in or related to any of examples 1-8, or portions or parts thereof, or otherwise described in the present disclosure. [0107] Example Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-8, or portions or parts thereof, or otherwise described in the present disclosure.

[0108] Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-8, or portions thereof.

[0109] Example Zll may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1-8, or portions thereof.

[0110] Example Z12 may include a signal in a wireless network as shown and described herein.

[0111] Example Z13 may include a method of communicating in a wireless network as shown and described herein.

[0112] Example Z14 may include a system for providing wireless communication as shown and described herein.

[0113] Example Z15 may include a device for providing wireless communication as shown and described herein.

[0114] Any of the above-described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

Claims

What is claimed is:

1. An apparatus of a New Radio (NR) User Equipment (UE), the apparatus including a memory, and one or more processors coupled to the memory, the one or more processors to: generate a first report including first report information, the first report information including an indication of a radio link failure (RLF) at the source cell before CHO execution and after CHO recovery success; and send the first report to communications resources of the UE for transmission.

2. The apparatus of claim 1, the one or more processors further to generate a second report including a second report information, the second report information including an indication of a radio link failure (RLF) at the source cell before CHO execution and after a CHO recovery failure, and send the second report to the communications resources of the UE for transmission.

3. The apparatus of claim 1, the one or more processors to generate a third report including a third report information including at least one of: an indication of a radio link failure (RLF) at the source cell before CHO execution and after a CHO recovery failure, an indication of reestablishment after CHO recovery failure, or cell information during cell selection, and send the third report to communications resources of the UE for transmission.

4. The apparatus of any one of claims 1-3, wherein the report information further includes an indication of a time of RFL at the source cell.

5. The apparatus of any one of claims 1-3, wherein the report information further includes at least one of: an execution condition configured to the UE, corresponding measurements for candidate cells, corresponding cell identification (ID), a time of receiving condition configuration, and recovery cell information.

26

6. The apparatus of claim 1, the one or more processors to generate a fourth report including a fourth report information including an indication of CHO failure and CHO recovery success, and send the fourth report to communications resources of the UE for transmission.

7. The apparatus of claim 1, the one or more processors to generate a fifth report including a fifth report information including at least one of: an indication of CHO failure and CHO recovery failure, or source cell measurement when CHO failure happens, and send the fifth report to communications resources of the UE for transmission.

8. The apparatus of claim 1, the one or more processors to generate a sixth report including sixth report information including at least one of: an indication of CHO failure and CHO recovery failure, source cell measurement when CHO failure happens, or cell information during cell selection, and send the sixth report to communications resources of the UE for transmission.

9. The apparatus of any one of claims 6-8, wherein the report information including the indication of CHO failure further includes CHO execution cell information.

10. The apparatus of any one of claims 6-8, wherein the report information further includes at least one of: an execution condition configured to the UE, corresponding measurements for candidate cells, corresponding cell identification (ID), a time of receiving condition configuration, and recovery cell information.

11. The apparatus of claim 10, wherein the recovery cell information includes random access channel (RACH) information.

12. The apparatus of any one of claims 1-3 and 6-8, further including the communications resources.

13. A method to be performed at an apparatus of a New Radio (NR) User Equipment (UE), the method including: generating a first report including first report information, the first report information including an indication of a radio link failure (RLF) at the source cell before CHO execution and after CHO recovery success; and sending the first report to communications resources of the UE for transmission.

14. The method of claim 13, further including generating a second report including a second report information, the second report information including an indication of a radio link failure (RLF) at the source cell before CHO execution and after a CHO recovery failure, and sending the second report to the communications resources of the UE for transmission.

15. The method of claim 13, further including generating a third report including a third report information including at least one of: an indication of a radio link failure (RLF) at the source cell before CHO execution and after a CHO recovery failure, an indication of reestablishment after CHO recovery failure, or cell information during cell selection, and sending the third report to communications resources of the UE for transmission.

16. The method of any one of claims 13-15, wherein the report information further includes an indication of a time of RFL at the source cell.

17. The method of any one of claims 13-16, wherein the report information further includes at least one of: an execution condition configured to the UE, corresponding measurements for candidate cells, corresponding cell identification (ID), a time of receiving condition configuration, and recovery cell information.

18. The method of claim 13, further including generating a fourth report including a fourth report information including an indication of CHO failure and CHO recovery success, and sending the fourth report to communications resources of the UE for transmission.

19. The method of claim 13, further including generating a fifth report including a fifth report information including at least one of: an indication of CHO failure and CHO recovery failure, or source cell measurement when CHO failure happens, and sending the fifth report to communications resources of the UE for transmission.

20. The method of claim 13, further including generating a sixth report including sixth report information including at least one of: an indication of CHO failure and CHO recovery failure, source cell measurement when CHO failure happens, or cell information during cell selection, and sending the sixth report to communications resources of the UE for transmission.

21. The method of any one of claims 18-20, wherein the report information including the indication of CHO failure further includes CHO execution cell information.

22. The method of any one of claims 18-20, wherein the report information further includes at least one of: an execution condition configured to the UE, corresponding measurements for candidate cells, corresponding cell identification (ID), a time of receiving condition configuration, and recovery cell information.

23. The method of claim 22, wherein the recovery cell information includes random access channel (RACH) information.

24. A machine readable medium including code, when executed, to cause a machine to perform the method of any one of claims 13-23.

25. An apparatus including means to perform the method of any one of claims 13-23.

29