Wireless device, network node, and method performed by same for processing re-establishment information after a failure - Patents.com

Abstract

A method performed on a wireless device (130). The method is for processing re-establishment information after a radio link failure. The wireless device (130) operates within a wireless communication network (100). The wireless device (130) stores (304) one or more indications in response to a declared radio link failure. The one or more indications indicate the radio link failure. The one or more indications include at least a first indication. The first indication indicates whether a first cell (123) selected by the wireless device (130) for a re-establishment procedure triggered by the radio link failure was a candidate cell in an inter-cell mobility configuration. The inter-cell mobility configuration was received in a previous indication to perform an L1 / L2 mobility procedure.

Description

[Technical Field]

[0001] The present disclosure relates generally to wireless devices and methods performed by wireless devices for processing re-establishment information after a failure. The present disclosure further relates generally to network nodes and methods performed by network nodes for processing re-establishment information after a failure. [Background technology]

[0002] A wireless device in a wireless communication network may be, for example, a user equipment (UE), a station (STA), a mobile terminal, a wireless terminal, a terminal, and / or a mobile station (MS). A wireless device may communicate wirelessly in a cellular or wireless communication network, sometimes also referred to as a cellular radio system, a cellular system, or a cellular network. Communication may occur, for example, between two wireless devices, between a wireless device and a landline phone, and / or between a wireless device and a server, via a radio access network (RAN) and possibly one or more core networks included within the wireless communication network. A wireless device may also be further referred to as a mobile phone, a cellular phone, a wireless laptop or tablet, etc., to name a few examples. A wireless device in this context may be, for example, a portable, pocketable, handheld, computer-based, or vehicle-mounted mobile device, and may communicate voice and / or data with another entity, such as another terminal or a server, via the RAN.

[0003] A wireless communication network covers a geographical area that may be divided into cell areas, each cell area being served by a network node, which may be a radio network node, a radio node, or an access node, such as a base station, e.g., a radio base station (RBS), which may also be referred to as a gNB, evolved Node B ("eNB"), "eNodeB," "Node B," "B node," transmission point (TP), or base transceiver station (BTS), depending on the technology and terminology used. Base stations may be of various classes, e.g., wide-area base station, medium-range base station, local-area base station, home base station, pico base station, etc., based on transmit power and therefore cell size. A cell is a geographical area where radio coverage is provided by a base station or radio node located at a base station site or radio node site, respectively. One base station at a base station site can serve one or multiple cells. Furthermore, each base station can support one or multiple communication technologies. The base stations communicate with terminals within their range over the air interface operating on radio frequencies. A wireless communication network may be a non-cellular system that includes a network node that can provide service to a receiving node, such as a wireless device, using a serving beam. In 3rd Generation Partnership Project (3GPP®) Long Term Evolution (LTE), a base station, which may also be referred to as an eNodeB or eNB, can be directly connected to one or more core networks. In the context of this disclosure, the term downlink (DL) can be used for a transmission path from a base station to a wireless device. The term uplink (UL) can be used for a transmission path in the opposite direction, i.e., from a wireless device to a base station.

[0004] The standards organization 3GPP® is currently developing specifications for a new radio interface, called NR or 5G-UTRA, and a fifth-generation (5G) packet core network (CN), which may also be referred to as the next-generation (NG) core network and abbreviated as NG-CN, NGC, 5G CN, or 5G Core (5GC). NG may be understood to refer to the interface / reference point between a 5G / NR radio access network (RAN) and the CN. In a 5G system (5GS), an NR radio base station may also be referred to as a gNB or 5G Node B. An NR UE may also be referred to as an nUE.

[0005] Further NR Mobility Enhancements in 3GPP Rel-18 A new work item known as Further NR Mobility Enhancements is being initiated as part of 3GPP Release 18. This work item aims to, among other things, specify Layer 1 (L1) / Layer 2 (L2)-based inter-cell mobility. According to the Work Item Description (WID) [1], one of the objectives of the work is to specify mechanisms and procedures for L1 / L2-based inter-cell mobility for mobility latency reduction. This may include the configuration and maintenance of multiple candidate cells so that the candidate cell configuration can be applied quickly [RAN2, RAN3]. The mechanisms and procedures for L1 / L2-based inter-cell mobility for mobility latency reduction may also include dynamic switching mechanisms between candidate serving cells, including special cells (SpCells) and secondary cells (Scells), for potentially applicable scenarios based on L1 / L2 signaling [RAN2, RAN1]. L1 / L2-based inter-cell mobility mechanisms and procedures for mobility latency reduction may further include L1 enhancements for inter-cell beam management, including L1 measurement and reporting and beam indication [RAN1, RAN2]. It was noted that early involvement of RAN2 may be required, including the possibility of further clarifying the interaction between this and the previous point. L1 / L2-based inter-cell mobility mechanisms and procedures for mobility latency reduction may also include timing advance management [RAN1, RAN2]. L1 / L2-based inter-cell mobility mechanisms and procedures for mobility latency reduction may further include central unit (CU)-distributed unit (DU) interface signaling to support L1 / L2 mobility, if necessary [RAN3]. It was noted that frequency band 2 (FR2)-specific enhancements, if any, are not excluded.Furthermore, it was pointed out that the L1 / L2-based inter-cell mobility procedures may be applicable to the following scenarios: standalone, carrier aggregation (CA), and NR dual connectivity (DC) cases with a serving cell change within one cell group (CG), intra-DU case, intra-CU inter-DU case, applicable to standalone and CA: no new RAN interfaces are expected, both intra-frequency and inter-frequency, both Frequency 1 (FR1) and FR2, source and target cells may be synchronous or asynchronous.

[0006] The work item description [1] states as part of the justification: "As a UE moves from the coverage area of ​​one cell to another, it may need to perform a serving cell change at some point. Currently, the serving cell change can be triggered by L3 measurements and performed by Radio Resource Control (RRC) signaling, which triggers a reconfiguration with synchronization for the change of Primary Cell (PCell) and Primary Secondary Cell (PSCell), and the release and addition of SCells, if applicable. In all cases, a full L2 and L1 reset may occur, resulting in longer latency, higher overhead, and longer disruption than beam-switched mobility. The goal of the L1 / L2 mobility enhancements can be understood to be to enable the serving cell change via L1 / L2 signaling in order to reduce latency, overhead, and disruption."

[0007] Self-Organizing Networks (SON) in 3GPP Self-organizing networks (SONs) can be understood as automated technologies designed to make planning, configuration, management, optimization, and repair of mobile radio access networks simpler and faster. SON functions and operations are defined and specified in generally accepted mobile industry recommendations produced by organizations such as the 3rd Generation Partnership Project (3GPP®) and Next Generation Mobile Networks (NGMN).

[0008] In 3GPP, processes within the SON area can be categorized into self-configuration and self-optimization processes. The self-configuration process can be understood as a process in which a newly deployed node can be configured by an automatic installation procedure to obtain the basic configuration required for system operation. This process can function in a pre-operational state. The pre-operational state can be understood as the state after the eNB is powered up and has backbone connectivity, until the radio frequency (RF) transmitter can be turned on.

[0009] FIG. 1 is a schematic signaling diagram illustrating the branching of the self-configuration / self-optimization function according to Figure 22.1-1 of 3GPP TS 36.300, v.17.1.0.

[0010] As shown in Figure 1, functions handled in the pre-operational state, such as basic configuration and initial radio configuration, can be covered by the self-configuration process. As shown in Figure 1, basic configuration (A) functions can include a-1) Internet Protocol (IP) address configuration and operation, administration, and maintenance (OAM) discovery, a-2) eNB / network (NW) authentication, a-3) association with a gateway (GW), a-4) eNB software (and operating parameters) download, etc. Initial radio configuration (B) functions can include b-1) neighbor list configuration, b-2) coverage / capacity related parameter configuration, etc.

[0011] The self-optimization process may be defined as a process in which user equipment (UE) and access node measurements and performance measurements may be used to automatically adjust the network. This process may operate in an operational state, which may be understood as a state in which the RF interface may further be turned on.

[0012] As shown in Figure 1, functions handled in operational state, such as optimization / adaptation, can be covered by a self-optimization process. As shown in Figure 1, optimization / adaptation (C) functions can include c-1) neighbor list optimization, c-2) coverage and capacity control, etc.

[0013] In LTE, support for self-configuration and self-optimization may be specified, including features such as dynamic configuration, automatic neighbor relation (ANR), mobility load balancing, mobility robustness optimization (MRO), radio access channel (RACH) optimization, and power saving support, as described in section 22.2 of 3GPP TS 36.300, v.17.1.0.

[0014] In NR, support for self-configuration and self-optimization may also be specified, starting with self-configuration features such as dynamic configuration, automatic neighbor relationship (ANR) in Rel-15, as described in Section 15 of 3GPP TS 38.300, v.17.1.0. In NR Rel-16, more SON features are specified for NR UEs, including self-optimization features such as mobility robustness optimization (MRO).

[0015] Mobility Robustness Optimization (MRO) in 3GPP Seamless handover can be understood to be a key feature of 3GPP technology. A successful handover can allow a UE to move within the coverage areas of different cells without significant interruption in data transmission. However, there can be scenarios in which the network may fail to handover the UE to the "correct" neighboring cell in time, and in such scenarios the UE may declare a Radio Link Failure (RLF) or Handover Failure (HOF).

[0016] When HOF and RLF occur, the UE may take autonomous actions, such as attempting to initiate cell selection and re-establishment procedures, to ensure that the UE attempts to recover and become reachable again as soon as possible. RLF may be understood as a source of degradation in user experience, as it may only be declared by the UE when it recognizes that there may not be a reliable communication channel, i.e., an available radio link, between the UE and the network. Furthermore, re-establishing the connection may require signaling with the newly selected cell, such as random access procedures, RRC re-establishment request, RRC re-establishment, RRC re-establishment complete, RRC reconfiguration, and RRC reconfiguration complete, which may result in some delay before the UE can exchange data with the network again.

[0017] According to specifications, e.g. 3GPP TS36.331, v.17.1.0, possible causes of a radio link failure may be one of the following: a) expiration of the radio link monitoring related timer T310, b) expiration of the measurement report related timer T312, i.e. if a measurement report is sent during T310 but no handover command is received from the network within the period of this timer, c) when the maximum number of Radio Link Control (RLC) retransmissions is reached, d) when an indication of a random access problem is received from the Medium Access Control (MAC) entity.

[0018] It can be appreciated that RLF can lead to re-establishments, which can degrade performance and user experience, and therefore it can be appreciated that it is in the interest of the network to understand the reason for the RLF and try to optimize mobility-related parameters such as the trigger conditions for measurement reports to avoid future RLFs. Prior to standardization of MRO-related report handling in the network, only the UE knew some information related to the state of radio quality at the time of the RLF occurrence and the actual reason for declaring the RLF. It can be appreciated that in order for the network to identify the reason for the RLF, the network needs more information from both the UE and neighboring base stations.

[0019] As part of the MRO approach for LTE, RLF reporting procedures were introduced into the RRC specifications of the RAN2 work in Rel-9. This impacted the RRC specifications (e.g., TS36.331, v.17.1.0) in the sense that it was standardized that the UE would log relevant information at the moment of RLF and then later report it to, for example, a target cell to which the UE was able to successfully connect after re-establishment. This also impacted the gNodeB-to-NodeB interface, i.e., X2AP specifications (e.g., 3GPP TS36.423, v.17.1.0), since an eNodeB receiving an RLF report could forward it to a potentially failed eNodeB.

[0020] The RLF reports generated by the UE have been expanded in subsequent releases with more details. Measurement reports based on the latest LTE RRC specification [1] may include: a) measurements of the last serving cell, e.g., PCell, such as Reference Signal Received Power (RSRP) and Reference Signal Received Quality (RSRQ); b) measurements of neighboring cells at different frequencies for different RATs, e.g., Universal Terrestrial Radio Access (EUTRA), Universal Terrestrial Radio Access (UTRA), Global System for Mobile Communications Enhanced Data Rates for GSM Evolution Radio Access Networks (GERAN), Code Division Multiple Access 2000 (CDMA2000); c) measurements of reception frequencies associated with Wireless Local Area Network (WLAN) Access Points (APs). d) RSSI and other measurements associated with Bluetooth beacons; e) location information including location coordinates and velocity, if available; f) Globally Unique Identifier of the last serving cell, if available; otherwise Physical Cell Identifier (PCI) and carrier frequency of the last serving cell; g) Tracking Area Code of the PCell; h) Time since last reception of a "Handover Command" message; i) Cell Radio Network Temporary Identifier (C-RNTI) used in the previous serving cell; j) Whether the UE is configured with a Data Radio Bearer (DRB) with a Quality of Service Class Identifier (QCI) of value 1.

[0021] After the RLF is declared, the RLF report may be logged and included in the VarRLF report, and if the UE selects a cell and the re-establishment is successful, the UE may include an indication that it has an available RLF report in the RRC Re-establishment Complete message, making the target cell aware of its availability. Then, upon receiving a UEInformationRequest message containing the flag "rlf-ReportReq-r9", the UE may be requested to send the RLF report stored in the UE Variable VarRLF report to the network, for example, in a UEInformationResponse message, as described above.

[0022] Based on the RLF report from the UE and knowledge of which cell the UE reestablished on, the original source cell may be able to infer whether the RLF was caused by a coverage hole or a handover-related parameter configuration. If it is determined that the RLF was caused by a handover-related parameter configuration, the original serving cell may further classify the handover-related failure into the following classes: too early, too late, or handover to the wrong cell. These handover failure classes are briefly described below. The first handover failure class may relate to whether the handover failure was caused by a "too late handover / mobility" case. The original serving cell may classify the handover failure as "too late handover / mobility" if it may have failed to send a handover command to the UE associated with the handover to a specific target cell, and if the UE reestablishes itself on this target cell after the RLF. An example of a corrective action from the original serving cell could be to start the handover procedure to the target cell a little earlier by reducing the Cell Individual Offset (CIO) to this target cell, and the target cell could control when information elements (IEs) send event-triggered measurement reports that could lead to a handover decision.

[0023] A second handover failure class may concern whether the handover failure is caused by a "premature handover / mobility" case. If the original serving cell may have successfully sent a handover command to the UE involved in the handover, but the UE fails to perform random access to this target cell or the UE declares RLF on the target cell shortly thereafter, the handover failure may be classified as "premature handover / mobility". An example of a corrective action from the original serving cell may be to start the handover procedure to this target cell with a slight delay by increasing the Cell Individual Offset (CIO) to this target cell, and the target cell may control when the IE sends the event-triggered measurement report that leads to the handover decision.

[0024] A third handover failure class may concern whether the handover failure is caused by a "handover / mobility to wrong cell" case. The original serving cell may intend to perform a handover of this UE to a specific target cell, but the UE may declare a failure or declare a failure immediately after successfully completing the handover and being able to re-establish on a third cell, in which case the handover failure may be classified as "handover / mobility to wrong cell". Corrective actions from the original serving cell may be to initiate a measurement reporting procedure that may lead to a handover to the target cell a little later by reducing the CIO to the target cell, or to initiate a handover to the cell where the UE has re-established a little earlier by increasing the CIO to the re-established cell.

[0025] Existing methods for handling handover failures can result in wasted resources such as unnecessary signaling and / or unnecessary delays. Summary of the Invention [Problem to be solved by the invention]

[0026] As part of the development of the present embodiments, one or more problems with existing technology are first identified and discussed.

[0027] The overall procedures and signaling for L1 / L2-based inter-cell mobility, as described in the 3GPP work item description WID [1], are still open. The goal of L1 / L2-based inter-cell mobility is to reduce latency, overhead, and disruption time. L1 / L2 inter-cell mobility decisions can be made by the source DU, compared to traditional L3 mobility decisions made by the source CU (control plane). L1 / L2 inter-cell mobility candidates are expected to be configured in a UE-specific manner. A UE may have a limited number of inter-cell mobility candidates it can hold in memory, e.g., eight L1 / L2 inter-cell mobility candidates. Therefore, different UEs within the same DU may be configured with different L1 / L2 inter-cell mobility candidates depending on the UE's location, mobility characteristics, and other parameters.

[0028] If the UE may declare RLF, the UE may perform a re-establishment procedure. The cell on which the UE may perform the re-establishment procedure may have been a candidate for L1 / L2 inter-cell mobility. In that case, this may imply that the L1 / L2 inter-cell mobility decision may not have been optimal, since the UE would have to declare a failure to return to a connected state on the re-established cell rather than being instructed via L1 / L2 to perform mobility to the re-established cell. However, with the current content of the RLF report, the network may not know whether the UE was configured with the re-established cell as a candidate for L1 / L2 inter-cell mobility. Thus, the network node may not know whether the problem lies in the triggering of L1 / L2 inter-cell mobility at the DU, the selection of L1 / L2 inter-cell mobility candidates, or the L3 mobility configuration.

[0029] Certain aspects of the present disclosure and embodiments thereof may provide solutions to these and other problems.

[0030] As mentioned above, the purpose of this embodiment is to improve the handling of re-establishment information after a failure. [Means for solving the problem]

[0031] According to a first aspect of this embodiment, this object is achieved by a method performed by a wireless device for processing re-establishment information after a failure. The wireless device operates within a wireless communication network. In response to a declared radio link failure, the wireless device stores one or more indications, the one or more indications indicating the failure. The one or more indications include at least a first indication, the first indication indicating whether a first cell selected by the wireless device for the failure-triggered re-establishment procedure was a candidate cell in an inter-cell mobility configuration, the inter-cell mobility configuration having been received in a previous indication to perform an L1 / L2 mobility procedure.

[0032] According to a second aspect of this embodiment, this object is achieved by a method performed by a network node for processing re-establishment information after a failure by a wireless device. The network node operates in a wireless communication network. The network node receives one or more indications from the wireless device, the one or more indications indicating a failure. The one or more indications include at least a first indication, the first indication indicating whether a first cell selected by the wireless device for a re-establishment procedure triggered by the failure was a candidate cell in an inter-cell mobility configuration, the inter-cell mobility configuration having been received by the wireless device in a previous indication to perform an L1 / L2 mobility procedure.

[0033] According to a third aspect of this embodiment, this object is achieved by a wireless device configured to perform the above method. The wireless device may be understood as being for processing re-establishment information after a failure. The wireless device is configured to operate within a wireless communication network. The wireless device is configured to store, in response to a declared failure, one or more indications configured to indicate the failure. The one or more indications are configured to include at least a first indication. The first indication is configured to indicate whether a first cell configured to be selected by the wireless device for a re-establishment procedure configured to be triggered by the failure was a candidate cell in an inter-cell mobility configuration configured to be received in a previous indication. The previous indication is for performing an L1 / L2 mobility procedure.

[0034] According to a fourth aspect of this embodiment, this object is achieved by a network node configured to perform the above method. The network node may be understood as being for processing re-establishment information after a failure by a wireless device. The network node is configured to operate within a wireless communication network. The network node is configured to receive one or more indications from the wireless device configured to indicate a failure. The one or more indications are configured to include at least a first indication. The first indication is configured to indicate whether a first cell configured to be selected by the wireless device for a re-establishment procedure configured to be triggered by a failure was a candidate cell in an inter-cell mobility configuration. The inter-cell mobility configuration is configured to be received by the wireless device in a previous indication to perform an L1 / L2 mobility procedure.

[0035] By storing one or more indications, the wireless device may be able to transmit the stored one or more indications to a network node. By receiving one or more indications, the network node may be able to identify whether a cell with which the wireless device may later perform re-establishment, e.g., a first cell, was part of the L1 / L2 inter-cell mobility configuration based on the one or more indications stored in the embodiments herein. The wireless device may thereby enable the network node to know whether the problem may be with triggering L1 / L2 inter-cell mobility at the DU, with the selection of L1 / L2 inter-cell mobility candidates, or with the L3 mobility configuration. This may enable the network node to adjust the L1 / L2 inter-cell mobility configuration through analysis of the one or more indications. This may optimize mobility procedures, reduce delays, reduce communication interruptions, and result in more efficient use of wireless communication network resources.

[0036] Examples of the present embodiment will be described in more detail according to the following description and with reference to the accompanying drawings. [Brief explanation of the drawings]

[0037] [Figure 1] Schematic signaling diagram illustrating the branching of the self-configuration / self-optimization functionality according to Figure 22.1-1 of 3GPP TS 36.300, v.17.1.0. [Figure 2] 1 is a schematic diagram illustrating an example of a wireless communication network according to an embodiment; [Figure 3] 4 is a flowchart illustrating a method in a wireless device according to the present embodiment. [Figure 4] 4 is a flowchart illustrating a method in a network node, referred to herein as a "third network node," according to a present embodiment. [Figure 5] 1A and 1B are schematic block diagrams illustrating two embodiments of a wireless device according to the present invention, panels a) and b). [Figure 6]1 is a schematic block diagram illustrating two embodiments of a network node, panels a) and b), according to the present embodiment. [Figure 7] 1 is a flowchart illustrating a method in a wireless device according to an example related to the present embodiment. [Figure 8] 10 is a flowchart illustrating a method in a network node, referred to herein as a "third network node," according to an example related to the present embodiments. [Figure 9] 9 illustrates an example of a communication system 900 according to some embodiments. [Figure 10] 10 is a block diagram of a host 1000, which may be an embodiment of host 916 in FIG. 9, in accordance with various aspects described herein. [Figure 11] 1 is a communication diagram of a host 1102 communicating with a UE 1106 via a network node 1104 over a partial wireless connection according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0038] This embodiment may be understood to generally relate to re-establishment cell type information according to L1 / L2 inter-cell mobility configuration, and may be understood to enable enhancement of reports, e.g., RLF reports, to include an indication of whether the cell on which the re-establishment procedure was performed was an L1 / L2 inter-cell mobility candidate.

[0039] This embodiment may further allow for all configured L1 / L2 inter-cell mobility candidates and their associated measurements to be included as part of a report, eg, an RLF report.

[0040] Some of the embodiments discussed herein are described more fully below with reference to the accompanying drawings, in which examples are shown. In this section, the present embodiments are described in more detail by way of some exemplary embodiments. However, other embodiments are within the scope of the subject matter disclosed herein. The disclosed subject matter should not be construed as limited to only the embodiments described herein. Rather, these embodiments are provided as examples to convey the scope of the subject matter to those skilled in the art. It should be noted that the exemplary embodiments herein are not mutually exclusive. Components of one embodiment may be implicitly assumed to be present in another embodiment, and it will be apparent to one skilled in the art how those components may be used in other exemplary embodiments.

[0041] 2 illustrates, in panels a) and b), two non-limiting examples of a radio network or wireless communication network 100, also sometimes referred to as a radio communication system, a cellular radio system, or a cellular network, in which the present embodiments may be implemented. The radio communication network 100 may be a 5G system, a 5G network, or a next-generation system or network. In other examples, the radio communication network 100 may also support other technologies, such as Long Term Evolution (LTE), LTE for machines (LTE-M), LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), LTE Half Duplex Frequency Division Duplex (HD-FDD), LTE Licensed Access (LAA), enhanced LAA (eLAA), further enhanced LAA (feLAA), and / or LTE operating in unlicensed bands, such as MultiFire. In yet other examples, the wireless communication network 100 may further support other technologies, such as, for example, Wideband Code Division Multiple Access (WCDMA), Universal Terrestrial Radio Access (UTRA) TDD, Global System for Mobile Communications (GSM) networks, GSM / Enhanced Data Rates for GSM Evolution (EDGE) Radio Access Networks (GERAN) networks, Ultra Mobile Broadband (UMB), EDGE networks, networks consisting of any combination of radio access technologies (RATs), such as multi-standard radio (MSR) base stations, multi-RAT base stations, any 3rd Generation Partnership Project (3GPP) cellular networks, WiFi networks, Worldwide Interoperability for Microwave Access (WiMax), Machine Type Communications (MTC), enhanced MTC (eMTC), Internet of Things (IoT) and / or Narrowband IoT (NB-IoT), or any cellular network or system. Therefore, although 5G / NR and LTE terms may be used in this disclosure to illustrate embodiments, this should not be seen as limiting the scope of the embodiments herein to only the aforementioned systems.

[0042] The wireless communication network 100 may include multiple network nodes, of which a first network node 111, a second network node 112, and a third network node 113 are shown in the non-limiting example of FIG. 2. Any of the first network node 111, the second network node 112, and the third network node 113 may be a radio network node, i.e., a radio base station, a transmission point such as a gNB or eNB, or other network node with similar functionality capable of providing services to user equipment, such as wireless devices or machine-type communication devices, in the wireless communication network 100. In some examples shown in FIG. 2b for the third network node 113, any of the first network node 111, the second network node 112, and the third network node 113 may be a distributed node and may partially perform its functions in cooperation with a virtualization node 114 in a cloud 115. The third network node 113 may also be referred to herein simply as a network node 113, as will be further described in connection with action 306.

[0043] The wireless communication network 100 may cover a geographical area, which in some embodiments may be divided into cell areas, and each cell area may be served by a radio network node, where one radio network node may serve one or more cells. In the example of FIG. 2, the first network node 111 may serve the source cell 121, the second network node 112 may serve the target cell 122, and the third network node 113 may serve each cell. In the non-limiting example shown in FIG. 2, each cell served by the third network node 113 is the first cell 123 and may be referred to herein simply as a cell 123. However, this is not necessarily the case. Each cell served by the third network node 113 may be a cell other than the first cell 123. Any of the first network node 111, the second network node 112, and the third network node 113 may be of a different class, such as a macro base station, a home base station, or a pico base station, based on their transmit power and therefore cell size. In some examples, any of the first network node 111, the second network node 112, and the third network node 113 may serve a receiving node in a serving beam. Any of the first network node 111, the second network node 112, and the third network node 113 may support one or more communication technologies, the names of which may vary depending on the technology and terminology used. Any of the radio network nodes that may be included in the communications network 100 may be directly connected to one or more core networks, e.g., one or more network nodes within the one or more core networks.

[0044] In some examples, any of the source cell 121, the target cell 122, and the first cell 123 may be served by one or more beams.

[0045] In some examples, the first network node 111, the second network node 112, and the third network node 113 may be different network nodes.

[0046] In some examples, any of the first network node 111, the second network node 112, and the third network node 113 may be co-located or may be the same node.

[0047] The wireless communication network 100 may further include a second cell 124, one or more candidate cells 125, which may include a first candidate cell 126, and a first neighbor cell 127. The one or more candidate cells 125 are shown in FIG. 2 to include three cells. However, it may be understood that this is for illustrative purposes and not by way of limitation. The one or more candidate cells 125 may include fewer or additional cells. It may also be understood that the wireless communication network 100 may include other cells. To simplify the illustration, the network nodes serving each of the illustrated cells are not shown. One or more of the illustrated cells may be served by the same network node.

[0048] There may be multiple wireless devices located in the wireless communication network 100, one of which, wireless device 130, is shown in the non-limiting example of FIG. 2. The wireless device 130 included in the wireless communication network 100 may be a wireless communication device such as a 5G user equipment (UE) or nUE, or UE, which may also be known as, for example, a mobile terminal, wireless terminal and / or mobile station, a mobile phone, a cellular phone, or a laptop with wireless capabilities, to name a few further examples. Any of the wireless devices included in the wireless communication network 100 may be, for example, a portable, pocketable, handheld, computer-integrated, or vehicle-mounted mobile device, and may communicate voice and / or data via the RAN with another entity, such as a server, a laptop, a personal digital assistant (PDA), a tablet, a machine-to-machine (M2M) device, a sensor, an IoT device, a NB-IoT device, a device with a wireless interface such as a printer or file storage device, a modem, or other wireless network unit capable of communicating via a wireless link within a communication system. The wireless device 130 included in the wireless communication network 100 may be enabled for wireless communication within the wireless communication network 100. Communications may be performed, for example, via a RAN and possibly one or more core networks, which may be included in the wireless communication network 100.

[0049] The wireless device 130 may be configured to communicate with the third network node 113 via a first link 141, e.g., a wireless link, within the wireless communication network 100. The third network node 113 may be configured to communicate with the virtual network node 114 via a second link 142, e.g., a wireless link or a wired link, within the wireless communication network 100. Although not shown in FIG. 2 , the wireless device 130 may be configured to communicate with the first network node 111 via a third link, e.g., a wireless link, within the wireless communication network 100, and the wireless device 130 may be configured to communicate with the second network node 112 via a fourth link, e.g., a wireless link, within the wireless communication network 100. It may be understood that the wireless device 130 may communicate with the cells shown in FIG. 2 via respective links, e.g., wireless links, which are not shown to simplify the illustration.

[0050] In general, all terms used herein should be interpreted according to their ordinary meaning in the relevant technical field unless a different meaning is clearly provided and / or a different meaning is suggested by the context in which they are used. All references to an element, apparatus, component, means, step, etc. should be openly interpreted as a reference to at least one instance of that element, apparatus, component, means, step, etc., unless expressly stated otherwise. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless a step is expressly described as following or preceding another step and / or unless there is an implicit indication that a step must precede or follow another step. Any feature of any embodiment disclosed herein may be applied to any other embodiment, where appropriate. Similarly, any advantage of any embodiment may also apply to any other embodiment, and vice versa. Other objects, features, and advantages of the included embodiments will become apparent from the following description.

[0051] In general, the use of "first," "second," "third," "fourth," and / or "fifth" herein may be understood as any way of indicating different elements or entities and not as conferring cumulative or chronological character on the nouns they modify, unless otherwise indicated by the context.

[0052] Several embodiments are included herein. It should be noted that the examples herein are not mutually exclusive. Components of one embodiment may be implicitly assumed to be present in another embodiment, and it will be clear to one skilled in the art how those components may be used in other exemplary embodiments.

[0053] More specifically, the following are embodiments related to a wireless device, e.g., wireless device 130, e.g., a 5G UE, nUE, or UE, and embodiments related to a network node, e.g., a third network node 113, e.g., a gNB.

[0054] Some embodiments will now be further described with some non-limiting examples.

[0055] In the following description, references to a UE or simply "UE" may be understood to similarly refer to a wireless device 130, and references to a gNB and / or network may be understood to similarly refer to a network node 113.

[0056] An embodiment of a method performed by a wireless device, such as wireless device 130, is described below with reference to the flowchart shown in Figure 3. The method may be understood to be for processing re-establishment information after a failure.

[0057] The failure may be in the mobility procedure.

[0058] The mobility procedure may be, for example, an L1 / L2 mobility procedure.

[0059] The failure may be a radio link failure or a handover failure.

[0060] The failure may be in a mobility procedure by the wireless device 130, for example, from the first network node 111 to the second network node 112. A mobility procedure failure may be understood as any problem occurring in the handling of the mobility, for example L1 / L2 mobility. The problem may be a radio link failure or a handover failure. The mobility procedure may also be referred to herein simply as mobility.

[0061] From a first network node 111 to a second network node 112 may in some instances mean that the mobility is inter-cell, although it may be noted that, as mentioned above, in some instances the first network node 111 and the second network node 112 may be the same node.

[0062] The radio link failure may be an example of a failure of a mobility procedure by the wireless device 130, for example from the first network node 111 to the second network node 112. The wireless device 130 operates in a wireless communication network, such as the wireless communication network 100. The method may be understood to be computer-implemented.

[0063] In some particular embodiments, the wireless communication network 100 may support New Radio (NR).

[0064] The method may include one or more of the following actions. In some embodiments, all actions may be performed. One or more embodiments may be combined where applicable. Components of one embodiment may be implicitly assumed to be present in another embodiment, and it will be apparent to one skilled in the art how those components may be used in other example embodiments. For simplicity, not all possible combinations are described. A non-limiting example of a method performed by wireless device 130 is shown in FIG. 3. Optional actions in some embodiments may be indicated by dashed lines in FIG. 3. In some embodiments, actions may be performed in a different order than shown in FIG. 3.

[0065] Action 301 In this action 301, the wireless device 130 may receive a previous indication. The previous indication may be to perform an L1 / L2 mobility procedure. The previous indication may include a received inter-cell mobility configuration for performing the L1 / L2 mobility procedure.

[0066] In a non-limiting example, an L1 / L2 mobility procedure may be understood as a mobility procedure involving L1 and / or L2 signaling.

[0067] The receipt in this action 301 may be from the first network node 111. In other related examples, the receipt in this action 301 may be from the second network node 112, for example, or from another network node operating in the wireless communication network 100.

[0068] This may be understood to mean that the wireless device 130 may receive the previous indication from the same network node as the network node from which it may ultimately send a report about the failure, but the network node from which it may receive the previous indication may be a different network node.

[0069] Action 302 At this action 302, the wireless device 130 may perform an L1 / L2 inter-cell mobility procedure, which may be in response to, for example, a previous indication received.

[0070] The mobility procedure may be from a first network node 111 to a second network node 112 operating in the wireless communication network 100 , for example from a source cell 121 to a target cell 122 .

[0071] Action 303 In this action 303, the wireless device 130 may declare a failure of the mobility procedure. The failure may be, for example, a radio link failure. That is, in this action 303, the wireless device 130 may declare a radio link failure. It is understood that the radio link failure in this embodiment does not necessarily occur during the process or attempt of a handover from the source cell 121 to the target cell 122. A radio link failure occurring during such a handover may be an example of a case where a radio link failure may occur. As mentioned above, in some examples, any of the first network node 111, the second network node 112, and the third network node 113 may be co-located or may be the same node. Therefore, another example where a radio link failure may occur may be within the same cell from which the wireless device 130 received the configuration in action 301.

[0072] As previously mentioned, the failure may be a HOF. In such an example, the wireless device 130 may declare a HOF in this action 303.

[0073] Action 304 In this action 304, the wireless device 130 saves one or more indications. Saving may include, for example, logging or recording. The saving / logging / recording in this action 304 may be in response to a declared failure. The one or more indications indicate a failure. That is, the one or more indications indicate a failed mobility procedure, in the sense that something went wrong with the mobility procedure. A failed mobility procedure, in some examples herein, may be understood as an L1 / L2 mobility procedure that may have gone wrong, such as an RLF and / or a HOF.

[0074] The one or more indications include at least a first indication indicating whether the cell selected by the wireless device 130 for the re-establishment procedure triggered by a failed, i.e., failed, mobility procedure, e.g., the first cell 123, was a candidate cell in the inter-cell mobility configuration received in a previous indication to perform an L1 / L2 mobility procedure, i.e., failed, mobility procedure.

[0075] Triggered by a failed mobility procedure may be understood as triggered by some L1 / L2 mobility procedure that may have gone wrong, for example RLF / HOF.

[0076] As previously mentioned, the previous indication may have been received, for example, from the first network node 111 , the second network node 112 , or another network node operating in the wireless communication network 100 .

[0077] In some embodiments, the one or more indications may further include at least one of the following options: According to a first option, the one or more indications may further include a second indication: The second indication may indicate one or more candidate cells 125 configured with inter-cell mobility, e.g., an L1 / L2 inter-cell mobility configuration.

[0078] According to a second option, the one or more indications may further include a third indication, which may indicate an elapsed time between a first time of receiving an inter-cell mobility configuration, e.g., an L1 / L2 inter-cell mobility configuration, in action 301, and a second time that a failure, e.g., a radio link failure, is declared in action 303.

[0079] In one example, the timer may be started upon receipt of the last L1 / L2 inter-cell mobility configuration before the failure, and in another example, the timer may be started upon receipt of the last L1 / L2 inter-cell mobility configuration that includes the cell selected for the re-establishment procedure as a candidate cell. According to a third option, the one or more indications may further include the above-mentioned third indication, further indicating a third elapsed time between a fourth time of receipt of the last inter-cell mobility configuration, e.g., L1 / L2 inter-cell mobility configuration, that includes the first cell 123 selected for the re-establishment procedure as a candidate cell, and the second time that the failure, e.g., radio link failure, was declared.

[0080] According to a fourth option, the one or more indications may further include a fourth indication, which may indicate at least one of: a) the first location information at a fourth time; and b) the second location information at a second time.

[0081] In some embodiments, at least one of the following options may be applied: According to a first option, the first indication may be indicated by a one-bit flag; According to a second option, the first indication may be indicated by a reest-L1L2Candidate information element (IE). In some examples, such an indication may be a one-bit flag, for example, reest-L1L2Candidate in the implementation example shown below in the description of action 306.

[0082] According to a third option, the first indication may further indicate additional L1 / L2 mobility related measurements.

[0083] According to a fourth option, the first indication including additional L1 / L2 mobility related measurements may be indicated in a reest-L1L2meas IE. In some examples, an explicit indication with additional L1 / L2 mobility related measurements may be used, for example, reest-L1L2meas in the following implementation example.

[0084] According to a fifth option, the first indication including additional L1 / L2 mobility related measurements may be indicated by reConnect-L1L2meas.

[0085] According to a sixth option, the second indication may be indicated in a candidates-L1L2Mobility IE. According to a seventh option, the second indication may be indicated in a candidate-L1L2flag flag.

[0086] According to the eighth option, the second indication may further indicate an additional L1 / L2 mobility-related measurement. This may be understood to mean that the second indication, rather than the first indication, may further indicate an additional L1 / L2-related measurement. It may not be understood to mean that the second indication may indicate the same additional L1 / L2 mobility-related measurement as the first indication.

[0087] According to the ninth option, the second indication, including additional L1 / L2 mobility related measurements, may be indicated in the candidate-L1L2meas IE. According to the tenth option, the third indication may be indicated in another IE. According to the eleventh option, the fourth indication may be indicated in yet another IE.

[0088] Storing one or more indications in this action 304 may enable the wireless device 130 to transmit the stored one or more indications to the network node 113. This may enable the network, e.g., the network node 113, to identify whether a cell with which the wireless device 130 may later perform re-establishment, e.g., the first cell 123, was part of the L1 / L2 inter-cell mobility configuration based on the one or more indications stored in the embodiments herein. The wireless device 130 may thereby enable the network, e.g., the network node 113, to know whether the issue lies in the triggering of L1 / L2 inter-cell mobility at the DU, the selection of L1 / L2 inter-cell mobility candidates, or the L3 mobility configuration. This may enable the network node 113 to adjust the L1 / L2 inter-cell mobility configuration based on the analysis of the one or more indications. This may optimize mobility procedures, reduce delays, shorten communication interruptions, and result in more efficient use of wireless communication network 100 resources.

[0089] Action 305 In this action 305, the wireless device 130 may perform a re-establishment or re-connection procedure. The re-establishment or re-connection procedure may be, for example, to a third network node 113 operating in the wireless communication network 100.

[0090] This action 305 execution may be, for example, in response to a declared fault.

[0091] In some embodiments, one of the following may apply: According to a first option, the wireless device 130 may perform a re-establishment procedure after transitioning to idle mode or after a radio link failure, i.e., a failed mobility procedure; According to a second option, the re-establishment procedure may fail and the wireless device 130 may reconnect to a network node 113, for example a third network node 113. In some of these embodiments, the saving of action 304 may further include saving at least one of the following indications: According to the first option, a fifth indication; the fifth indication may indicate whether the second cell 124 selected by the wireless device 130 for the re-connection procedure triggered by the failed re-establishment procedure was a candidate cell in the inter-cell mobility configuration received in the previous indication. According to a first option, the saving at action 304 may further include saving a sixth indication, which may indicate an elapsed time between a first time of receiving an inter-cell mobility configuration, e.g., an L1 / L2 inter-cell mobility configuration, and a fifth time of reconnection upon selection of the second cell 124.

[0092] This embodiment allows the wireless device 130 to include an indication regarding whether a reconnection cell, e.g., a cell that the wireless device 130 selected to connect to after a reestablishment failure and transition to RRC IDLE mode, was a candidate for L1 / L2 inter-cell mobility. In some examples, such an indication may be a one-bit flag, e.g., reConnect-L1L2Candidate. In some embodiments, a fifth indication may be indicated in the reConnect-L1L2Candidate IE.

[0093] Action 306 In this action 306, the wireless device 130 may transmit any of the one or more stored indications to a network node 113 operating in the wireless communication network 100. The transmission in this action 306 may be to, for example, the third network node 113, which may also be referred to simply as the network node 113. The third network node 113 may provide service to the wireless device 130 within the wireless communication network 100.

[0094] The network node 113 may be understood here to refer to a network node that may receive one or more indications from the wireless device 130. Generally, this will be the same network node as the third network node 113. If the re-establishment procedure of action 305 is successful, the network node 113 may become the third network node 113. If the re-establishment procedure fails, the wireless device 130 may, in some examples, reconnect to the third network node 113; in other examples, the wireless device 130 may reconnect to a network node other than the third network node 113, in which case the transmission in this action 306 may be to a network node different from the third network node 113. This distinction may be denoted here as the (third) network node 113.

[0095] This sending in action 306 may be performed, for example, via first link 141 .

[0096] The one or more indications transmitted may be, for example, a selected subset of the one or more stored indications.

[0097] In some embodiments, at least one of the following options may be applied: According to a first option, the failure may be a mobility procedure; According to a second option, the failure may be one of a radio link failure and a handover failure; According to a third option, the mobility, e.g., the mobility procedure, may be L1 / L2 inter-cell mobility; According to a fourth option, the one or more indications may be sent in a report, e.g., an RLF report; According to a fifth option, the one or more indications may be sent in a UEInformationResponse message; According to a sixth option, the inter-cell mobility configuration may be an L1 / L2 inter-cell mobility configuration.

[0098] As mentioned above, this embodiment may enable the wireless device 130 to include an indication, a first indication, regarding whether the re-establishment cell, e.g., the first cell 123, was a candidate for L1 / L2 inter-cell mobility. The inclusion of the re-establishment-L1L2meas may implicitly indicate to the network that the re-establishment cell was a candidate for L1 / L2 inter-cell mobility at the time it declared RLF.

[0099] In some examples of this embodiment, wireless device 130 may include in the RLF report the L1 / L2 inter-cell mobility candidates configured at the time of declaring RLF, such as candidates-L1L2Mobility in the implementation example below. In some examples, this may be neighbor cell-related information included in the RLF report, such as a flag in a measurement result associated with the neighbor cell, such as candidate-L1L2flag in the implementation example below, where the flag may indicate whether the corresponding neighbor cell was an L1 / L2 inter-cell mobility candidate.

[0100] In some examples, the wireless device 130 can include a third indication indicating the configuration of L1 / L2 inter-cell mobility and the elapsed time since the radio link failure. In another example, the wireless device 130 can include a fourth indication indicating the location information at the time of receiving the last L1 / L2 mobility configuration in addition to the location information at the time of the radio link failure.

[0101] In some examples, wireless device 130 may include measurements associated with L1 / L2 inter-cell mobility configurations as part of the RLF report, such as candidate-L1L2meas in the implementation example below.

[0102] In some examples, some of the above information, such as the list of candidate L1 / L2 cells, the measurement results of the L1 / L2 cells, a flag indicating whether the measured neighbor cell was a candidate L1 / L2 cell, the time elapsed since L1 / L2 mobility configuration, etc., may be included regardless of whether the wireless device 130 is able to successfully perform re-establishment with a cell that was a candidate cell for L1 / L2 mobility configuration, whether it is able to perform re-establishment with a cell that was not a candidate cell for L1 / L2 mobility, or whether the re-establishment attempt is unsuccessful or fails to find a suitable cell and goes into idle mode.

[0103] Either the fifth indication or the sixth indication may optionally be transmitted to the third network node 113, for example.

[0104] Some embodiments may relate to a reconnection cell, eg, second cell 124, in the event of a re-establishment failure or if no suitable cell is found during the execution of a watchdog timer, eg, T311.

[0105] This embodiment may enable the wireless device 130 to include an indication regarding whether a reconnect cell, e.g., the cell that the wireless device 130 selected to connect to after a re-establishment failure and transition to RRC IDLE mode, was a candidate for L1 / L2 inter-cell mobility. In some examples, such an indication may be a one-bit flag, e.g., reConnect-L1L2Candidate.

[0106] In some examples, wireless device 130 may transmit an explicit indication including additional L1 / L2 mobility-related measurements, such as reConnect-L1L2meas, which may implicitly indicate to the network that the reconnecting cell at the time of declaring RLF was a candidate for L1 / L2 inter-cell mobility.

[0107] In some examples, the wireless device 130 may include an indication of the time elapsed since the configuration of L1 / L2 inter-cell mobility and the cell selection reconnection. In one example, this time may be started upon receipt of the last L1 / L2 inter-cell mobility configuration before the failure. In another example, this timer may be started upon receipt of the last L1 / L2 inter-cell mobility configuration including the cell selected for the reconnection procedure as a candidate cell after the reestablishment failure. In some examples, some of the above information, such as the list of candidate L1 / L2 cells, the measurement results of the L1 / L2 cells, a flag indicating whether the measured neighbor cell was a candidate L1 / L2 cell, the time elapsed since the L1 / L2 mobility configuration, etc., may be included regardless of whether the wireless device 130 can perform reconnection on a cell that was a candidate cell for the L1 / L2 mobility configuration or on a cell that was not a candidate cell for the L1 / L2 mobility configuration.

[0108] In another example, the wireless device 130 may include an indication of its location information at the time of receiving the last L1 / L2 mobility configuration, as well as its location information at the time of reconnection to the network after a re-establishment failure.

[0109] Exemplary Implementation An implementation example of the above example regarding the re-establishment cell is shown below, and TS38.331 v17.0.0 is used as the baseline. Note that the following implementation example is intended to cover all of the above examples, and only a portion of the implementation example, i.e., related to a specific example or combination of examples, may be implemented in the final specification. In the provided implementation example, the wireless device 130 is a UE. The network node 113, for example, the third network node 113, may be understood as an example of a network.

[0110] ****************************** UEInformationResponse The UEInformationResponse message may be used by the UE to transfer information requested by the network. Signaling radio bearer: SRB1 or SRB2, if logged measurement information is included RLC-SAP:AM Logical channel: DCCH Direction: UE to network UEInformationResponse Message

[0111] [Table 1]

[0112] [Table 2]

[0113] [Table 3]

[0114] [Table 4]

[0115] [Table 5]

[0116] [Table 6]

[0117] [Table 7]

[0118] [Table 8]

[0119] 5.3.7.3 Actions following cell selection during T311 operation When selecting a suitable NR cell, the UE may be required to: 1>Ensuring availability of valid and up-to-date required system information as specified in Section 5.2.2.2; 1> Stop timer T311; 1>When the T390 is running: 2>Stop timer T390 for all access categories; 2>Perform the actions specified in 5.3.14.4; 1> If the selected cell is one of the candidate cells for L1 / L2 inter-cell mobility: 2>Set reest-L1L2Candidate in VarRLF report to true; 2>Set reest-L1L2meas in VarRLF report with available L1 RSRP, L1 SINR measurements of SSBs configured for L1 / L2 inter-cell mobility measurements; 1> Cell selection is triggered by the detection of a radio link failure of the MCG, a reconfiguration with synchronization failure of the MCG, or mobility from an NR failure, and 1> if attemptCondReconfig is configured; and 1> If the selected cell is one of the candidate cells whose masterCellGroup in VarConditionalReconfig contains reconfigurationWithSync: 2>Set choCellId in the VarRLF report to the global cell identifier and tracking area code if available, otherwise set it to the physical cell identifier and carrier frequency of the selected cell; 2>Apply the saved condRRCReconfig associated with the selected cell and perform the actions specified in 5.3.5.3; Note 1: How to avoid keystream reuse in case of CHO-based recovery after handover failure without key rekeying is left to the network implementation. 1> Otherwise: 2>If the UE is configured with conditionalReconfiguration: 3>Reset MAC; 3> Release spCellConfig if configured; 3> Release MCG SCell if configured; 3> Release delayBudgetReportingConfig if configured and stop timer T342 if running; 3> Release overheatingAssistanceConfig if configured and stop timer T345 if running; 3>If MR-DC is configured: 4>Perform MR-DC release as specified in section 5.3.5.10; 3> Release idc-AssistanceConfig if configured; 3> Release btNameList if configured; 3> Release wlanNameList if configured; 3> Release sensorNameList if configured; 3> releases the drx-PreferenceConfig for the MCG, if configured, and stops timer T346a associated with the MCG, if running; 3> release the maxBW-PreferenceConfig for the MCG, if configured, and stop timer T346b associated with the MCG, if running; 3> release maxCC-PreferenceConfig for the MCG, if configured, and stop timer T346c associated with the MCG, if running; 3> release the maxMIMO-LayerPreferenceConfig for the MCG, if configured, and stop timer T346d associated with the MCG, if running; 3> Releases the minSchedulingOffsetPreferenceConfig for the MCG, if configured, and stops timer T346e associated with the MCG, if running; 3> Releases the rlm-RelaxationReportingConfig for the MCG, if configured, and stops the timer T346j associated with the MCG, if running; 3> Releases the bfd-RelaxationReportingConfig for the MCG, if configured, and stops timer T346k associated with the MCG, if running; 3> releasePreferenceConfig if configured and stop timer T346f if running; 3> Release the onDemandSIB-Request, if configured, and stop timer T350, if running; 3> Release referenceTimePreferenceReporting if configured; 3> release sl-AssistanceConfigNR if configured; 3> Release obtainCommonLocation if configured; 3> release scg-DeactivationPreferenceConfig if configured and stop timer T346i if running; 3>Suspend all RBs except SRB0; 2>Delete all entries in VarConditionalReconfig if any; 2>For each measId, if the associated reportConfig has reportType set to condTriggerConfig: 3> Regarding the associated reportConfigId: 4>Delete the entry that matches reportConfigId from reportConfigList in VarMeasConfig; 3> If the associated measObjectId is only associated with a reportConfig whose reportType is set to condTriggerConfig: 4>Remove the entry with the matching measObjectId from measObjectList in VarMeasConfig; 3>Delete the entry with the matching measId from measIdList in VarMeasConfig; 2>Start timer T301; 2> Apply the default L1 parameter values ​​specified in the corresponding physical layer specification, except for parameters whose values ​​are provided in SIB1; 2>Apply the default MAC cell group configuration specified in 9.2.2; 2>Apply the CCCH configuration specified in 9.1.1.2; 2>Apply timeAlignmentTimerCommon included in SIB1; 2>Start sending RRCReestablishmentRequest message according to 5.3.7.4; NOTE 2: This procedure also applies when the UE returns to the source PCell. Upon selecting an inter-RAT cell, the UE shall: 1> As specified in 5.3.11, the action is taken when the system transitions to RRC_IDLE due to release cause "RRC connection failure". 5.3.7.4 Actions related to sending an RRCReestablishmentRequest message The UE may need to set the content of the RRCReestablishmentRequest message as follows: 1> If the procedure is initiated due to a radio link failure as specified in 5.3.10.3 or due to a reconfiguration due to a synchronization failure as specified in 5.3.5.8.3: 2>Set the reestablishmentCellId in the VarRLF report to the global cell identifier of the selected cell; 2> If the selected cell is one of the candidate cells for L1 / L2 inter-cell mobility: 3>Set reest-L1L2Candidate in VarRLF report to true; 3>Set reest-L1L2meas in VarRLF report with available L1 RSRP, L1 SINR measurements for SSBs configured for L1 / L2 inter-cell mobility measurements; 1>Set ue-Identity as follows: 2> Set c-RNTI to the C-RNTI used by the source PCell (reconfiguration due to synchronization or mobility from NR failure) or the C-RNTI used by the PCell where the re-establishment trigger occurred (in other cases); 2> Set physCellId to the physical cell identifier of the source PCell (reconfiguration due to synchronization or mobility from NR failure) or the physical cell identifier of the PCell where the re-establishment was triggered (in other cases); 2>Set shortMAC-I to the least significant 16 bits of the calculated MAC-I: 3>Term 8 (i.e., multiple of 8 bits) via ASN.1 encoded according to VarShortMAC-Input; 3> K used on the source PCell (reconfiguration due to synchronization or mobility from NR failure) or on the PCell where the re-establishment trigger occurred (in other cases) RRCint with key and integrity protection algorithms; and 3>By setting all input bits of COUNT, BEARER, and DIRECTION to binary 1; 1>Set reestablishmentCause to: 2>If a re-establishment procedure is initiated due to a reconfiguration failure as specified in 5.3.5.8.2: 3>Set reestablishmentCause to the value reconfigurationFailure; 2> Otherwise, if the re-establishment procedure was initiated due to a synchronization reconfiguration failure as specified in 5.3.5.8.3 (intra-NR handover failure) or 5.4.3.5 (inter-RAT mobility from NR failure): 3>Set reestablishmentCause to the value handoverFailure; 2> Otherwise: 3>Set reestablishmentCause to the value otherFailure; 1>Reestablishing PDCP of SRB1; 1> If the UE is connected to an L2 U2N relay UE via a PC5-RRC connection (i.e., the UE is an L2 U2N remote UE): 2>Apply the default configuration of SL-RLC1 as specified in 9.2.4 to SRB1; 2>Apply the default PDCP configuration specified in 9.2.1 to SRB1; 1> Otherwise: 2>Reestablishment of RLCs in SRB1; 2>Apply the default configuration specified in 9.2.1 to SRB1; 1> Configure lower layers to suspend SRB1 integrity protection and encryption; Note: No ciphering is applied to subsequent RRCReestablishment messages used to resume the connection. Integrity checks are performed by lower layers, but only upon request from RRC. 1>Restart SRB1; 1> Submit an RRCReestablishmentRequest message to the lower layer for transmission; 5.3.10.5 Determining RLF Report Content The UE may need to determine the contents of the VarRLF report as follows: 1>Clear the information contained in the VarRLF report, if any; 1> Set plmn-IdentityList to contain the list of EPLMNs stored by the UE (i.e., including RPLMNs); 1> If the UE was configured with L1 / L2 inter-cell mobility configuration at the time it declared the failure: 2> Set L1L2CellID to the global cell identifier if a global cell identifier is available, otherwise set it to the physical cell identifier and carrier frequency of each candidate cell configured in the L1 / L2 inter-cell mobility configuration; 2>For each candidate cell included in L1L2CellID include: 3> For each SSB configured in the L1 / L2 inter-cell mobility configuration, include the available SSB index, L1 RSRP, and L1 SINR; ... 1>If the failure is detected due to a reconfiguration with synchronization failure as described in 5.3.5.8.3, set the VarRLF report fields as follows: 2>Set connectionFailureType to hof; ... 1> Otherwise, if the failure is detected due to a mobility failure from NR as described in 5.4.3.5, set the fields in the VarRLF report to: 2>Set connectionFailureType to hof; ... 1> Otherwise, if the failure is detected due to radio link failure as described in 5.3.10.3, set the fields in the VarRLF report as follows: 2>Set connectionFailureType to rlf; 2>Set rlf-Cause to the trigger for detecting radio link failure according to Section 5.3.10.4; 2>Set nrFailedPCellId of failedPCellId to the global cell identifier and tracking area code (if available), otherwise set it to the physical cell identifier and carrier frequency of the PCell where the radio link failure was detected; 2> If the UE received an RRCReconfiguration message containing reconfigurationWithSync before connection: 3>If the last RRCReconfiguration message containing reconfigurationWithSync was for an intra-NR handover: 4> previousPCellId includes nrPreviousCell and is set to the global cell identifier and tracking area code of the PCell on which the last RRCReconfiguration message including reconfigurationWithSync was received; 4>If the last executed RRCReconfiguration message containing reconfigurationWithSync was for a DAPS handover: 5>Set lastHO-Type to daps; 4> Otherwise, if the last executed RRCReconfiguration message containing reconfigurationWithSync was for a conditional handover: 5>Set lastHO-Type to cho; 4>set timeConnFailure to the time elapsed since the execution of the last RRCReconfiguration message containing reconfigurationWithSync; 3> Otherwise, if the last RRCReconfiguration message containing reconfigurationWithSync is for a handover from E-UTRA to NR and the UE supports radio link failure reporting for inter-RAT MRO EUTRA: 4>Include eutraPreviousCell in previousPCellId and set it to the global cell identifier and tracking area code of the E-UTRA PCell that received the last RRCReconfiguration message containing reconfigurationWithSync embedded in the E-UTRA RRC message MobilityFromEUTRACommand message, as specified in TS36.331

[10] clause 5.4.3.3; 4>set timeConnFailure to the time elapsed since the reception of the last RRCReconfiguration message containing reconfigurationWithSync embedded in the E-UTRA RRC message MobilityFromEUTRACommand message, as specified in TS36.331

[10] clause 5.4.3.3; 3> At the time of radio link failure, if conditional handover configuration is available in VarConditionalReconfig: 3>Set choCandidateCellList to include the global cell identities and tracking area codes of all candidate target cells for conditional handover included in condRRCReconfig in VarConditionalReconfig when a radio link failure occurs (excluding candidate target cells included in measResulNeighCells); 2> If conditional handover configuration is available in VarConditionalReconfig at the time of declaring radio link failure: 3>setting timeSinceCHO-Reconfig to the time elapsed between the detection of radio link failure and the reception of the last conditionalReconfiguration containing condRRCReconfig message on the source PCell; 2> If L1 / L2 mobility configuration is available at the time of declaring radio link failure: 3>set timeSinceL1L2Config to the time elapsed between the detection of radio link failure and the receipt of the last L1 / L2 mobility configuration on the PCell; 1> connectionFailureType is rlf and rlf-Cause is set to randomAccessProblem or beamFailureRecoveryFailure; or 1>If connectionFailureType is hof and the failed handover is an intra-RAT handover: 2>Set ra-InformationCommon to include random access related information as described in Section 5.7.10.5; 1> If available, set locationInfo as per 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 section, the term "handover failure" is used to refer to "reconfiguration due to synchronization failure." *****************************

[0120] In yet another embodiment, for each neighboring cell included in the RLF report, the UE may also include corresponding L1 / L2 inter-cell mobility related measurements if that neighboring cell is a candidate for L1 / L2 inter-cell mobility, for example, in candidate-L1L2meas in the implementation example below.

[0121] By transmitting the one or more stored indications to the third network node 113 in this action 306, the wireless device 130 may enable the network, e.g., the third network node 113, to identify, based on the additional content of the report, e.g., the RLF report, whether the re-established cell, e.g., the first cell 123, was part of an L1 / L2 inter-cell mobility configuration as proposed in the embodiments. The wireless device 130 may thereby enable the network, e.g., the third network node 113, to know whether the problem may lie in the triggering of L1 / L2 inter-cell mobility at the DU, in the selection of L1 / L2 inter-cell mobility candidates, or in the L3 mobility configuration.

[0122] If the re-established cell was part of the candidate list for L1 / L2 inter-cell mobility, the network may be able to fine-tune the triggering of L1 / L2 inter-cell mobility among the candidates, for example via the third network node 113. For example, the gNB-DU may be able to optimize the L1 / L2 inter-cell mobility parameters.

[0123] If the re-established cell is not part of the candidate list for L1 / L2 inter-cell mobility, is the cell where the wireless device 130 declared failure, e.g., RLF, and the re-established cell can be configured as an L1 / L2 inter-cell mobility candidate, the network, e.g., the third network node 113, may fine-tune the configuration of candidates for L1 / L2 inter-cell mobility. For example, the CU-CP and DU may optimize the candidate selection algorithm. Furthermore, based on measurements of L1 / L2 provisioning, the DU may find an optimal trigger threshold for L1 / L2 mobility from the failed cell to the re-established cell.

[0124] If the re-established cell is not part of the candidate list for L1 / L2 inter-cell mobility and is the cell where the wireless device 130 has declared a failure, e.g., RLF, and the re-established cell cannot be configured as an L1 / L2 inter-cell mobility candidate, the network, e.g., the third network node 113, may fine-tune the L3 mobility parameters. For example, the CU-CP may optimize the handover parameters.

[0125] Action 307 In this action 307, the wireless device 130 may receive an updated inter-cell mobility procedure configuration. The mobility procedure may be, for example, an L1 / L2 inter-cell mobility procedure. The reception in this action 307 may be from the third network node 113.

[0126] This receipt at action 307 may be based, for example, on one or more transmitted indications.

[0127] The updated configuration may include adapted one or more procedures, such as candidate cell selection, mobility procedure trigger thresholds, and / or L3 mobility parameters.

[0128] By receiving the updated inter-cell mobility procedure configuration in this action 307, the wireless device 130 may be able to perform optimized mobility procedures with reduced delays, fewer communication interruptions, and more efficient use of resources within the wireless communication network 100.

[0129] An embodiment of a method performed by a network node, such as the third network node 113, will now be described with reference to the flowchart shown in Figure 4. The method may be understood to be for processing re-establishment information after a failure of a mobility procedure by a wireless device 130, for example from the first network node 111 to the second network node 112. The network node 113, for example the third network node 113, operates in a wireless communication network, such as the wireless communication network 100. The method may be understood to be computer-implemented.

[0130] In some embodiments, the wireless communication network 100 may support New Radio (NR).

[0131] Several embodiments are included herein. The method may include one or more of the following actions. In some embodiments, all actions may be performed. Where applicable, one or more embodiments may be combined. Components of one embodiment may be implicitly assumed to be present in another embodiment, and it will be apparent to one skilled in the art how those components may be used in other example embodiments. For simplicity of explanation, not all possible combinations are described. A non-limiting example of a method performed by the third network node 113, also referred to simply as network node 113, is shown in FIG. 4. In FIG. 4, optional actions in some embodiments may be indicated with dashed lines. In some embodiments, actions may be performed in a different order than shown in FIG. 4.

[0132] Some of the detailed description below corresponds to the same references given above with respect to the actions described for wireless device 130 and will not be repeated here for brevity. For example, the failure may be, for example, a radio link failure. Mobility procedures may also be referred to herein simply as mobility.

[0133] Action 401 In this action 401 , the network node 113 may perform a re-establishment or re-connection procedure with the wireless device 130 .

[0134] In some embodiments, one of the following options may be applied: According to a first option, the re-establishment procedure may be performed after the wireless device 130 may have entered idle mode after a failed mobility procedure; According to a second option, the re-establishment procedure may fail and the wireless device 130 may reconnect to the network node 113, i.e., the third network node 113.

[0135] Action 402 In this action 402, the network node 113 receives one or more indications, for example, a subset of one or more indications, from the wireless device 130. The one or more indications may indicate a failed mobility procedure, i.e., the one or more indications indicate a failure. The one or more indications include at least a first indication.

[0136] The first indication may indicate whether the first cell 123 selected by the wireless device 130 for the failure-triggered re-establishment procedure was a candidate cell in the inter-cell mobility configuration received by the wireless device 130 in a previous indication to perform an L1 / L2 mobility procedure, i.e., a failed mobility procedure, as described above.

[0137] The failure may be considered as a disrupted mobility procedure, as described above.

[0138] This receiving in action 402 may be performed, for example, via the first link 141 .

[0139] The previous indication may be received, for example, from the first network node 111 , the second network node 112 or another network node operating in the wireless communication network 100 .

[0140] In some embodiments, at least one of the following options may apply: a) the failure may be a mobility procedure; b) the failure may be any one of a radio link failure and a handover failure; c) the mobility, e.g., the mobility procedure, may be L1 / L2 inter-cell mobility; d) the one or more indications may be received in a report, e.g., an RLF report; e) the one or more indications may be received in a UEInformationResponse message; f) the inter-cell mobility configuration may be an L1 / L2 inter-cell mobility configuration.

[0141] In some embodiments, the one or more indications may further include at least one of the following: a) a second indication, where the second indication may indicate one or more candidate cells 125 configured with inter-cell mobility, e.g., L1 / L2 inter-cell mobility configuration; b) a third indication, where the third indication may indicate an elapsed time between a first time of receipt of the inter-cell mobility configuration, e.g., L1 / L2 inter-cell mobility configuration, and a second time at which a failure, e.g., a radio link failure, is declared; c) the third indication further indicates a third elapsed time between a fourth time of receipt of the last inter-cell mobility configuration, e.g., L1 / L2 inter-cell mobility configuration, and a second time at which a failure, e.g., a radio link failure, is declared; and d) a fourth indication, where the fourth indication may indicate at least one of i) the first location information at the fourth time, and ii) the second location information at the second time.

[0142] In some embodiments, at least one of the following may apply: a) the first indication may be indicated by a one-bit flag; b) the first indication may be indicated by a reest-L1L2Candidate IE; c) the first indication may further indicate additional L1 / L2 mobility related measurements; d) the first indication including additional L1 / L2 mobility related measurements may be indicated by a reest-L1L2meas IE; e) the first indication including additional L1 / L2 mobility related measurements may be indicated by a 38econnect-L1L2meas IE; f) the second indication may be indicated by a candidates-L1L2Mobility g) the second indication may be indicated by a candidate-L1L2flag flag; h) the second indication may further indicate additional L1 / L2 mobility related measurements; i) the second indication including additional L1 / L2 mobility related measurements may be indicated by a candidate-L1L2meas IE; j) the third indication may be indicated by another IE; k) the fourth indication may be indicated by yet another IE.

[0143] One or more indications may be received after the re-establishment procedure is performed.

[0144] In some embodiments, the method may further include one or more of the following actions 403, 404, 405, 406:

[0145] In some particular embodiments, the method may further include one or more of the following actions 403, 404, 405, 406, for example, a re-establishment procedure may fail and the wireless device 130 may reconnect to the network node 113.

[0146] Action 403 In this action 403, the network node 113 may determine one or more characteristics of the inter-cell mobility configuration. The determination in this action 403 may be based on one or more received indications, for example a subset.

[0147] The determined one or more characteristics of the inter-cell mobility configuration may be selected from, for example, i) whether the first cell 123 selected by the wireless device 130 for the re-establishment procedure was a candidate cell in the inter-cell mobility configuration, ii) measurement results of one or more candidate cells 125 configured with an inter-cell mobility configuration, e.g., an L1 / L2 inter-cell mobility configuration, and iii) the duration for which the wireless device 130 was configured with an inter-cell mobility configuration, e.g., an L1 / L2 inter-cell mobility configuration, before the failure occurred, i.e., before the radio link failure occurred.

[0148] Action 404 In this action 404, the network node 113 may initiate adapting one or more procedures of inter-cell mobility configuration, for example L1 / L2 inter-cell mobility configuration.

[0149] Initiation may be understood as initiating, promoting, enabling, triggering, etc.

[0150] In some examples, adapting one or more procedures of inter-cell mobility configuration, e.g., L1 / L2 inter-cell mobility configuration, may be at least one of candidate cell selection, mobility procedure trigger threshold, and L3 mobility parameters.

[0151] This initiation at action 404 may be based, for example, on the outcome of the determination.

[0152] Action 405 In this action 405, the network node 113 may send an updated inter-cell mobility configuration, for example an L1 / L2 inter-cell mobility configuration, i.e., an inter-cell mobility procedure configuration as described in action 307.

[0153] The updated inter-cell mobility configuration, eg, L1 / L2 inter-cell mobility configuration, may include one or more adapted procedures.

[0154] The sending of the updated inter-cell mobility configuration, eg, L1 / L2 inter-cell mobility configuration, in this action 405 may be based on the adaptation initiated in action 404 .

[0155] In some embodiments, at least one of the following options may be applied: According to the first option a), provided that the first cell 123 was not a candidate cell in the inter-cell mobility configuration, the adapting may include, for example, adding the first cell 123 to a list of candidate cells in the inter-cell mobility configuration for a device connected to the cell, e.g., PCell, where the failed mobility procedure was detected. In one example, if the re-established cell was not configured as a candidate cell for L1 / L2 mobility, the network node 113 may include the re-established cell in a list of candidate cells for a UE connected to the PCell where the radio link failure was detected.

[0156] According to the second option b), the adapting may include triggering a mobility procedure to the first candidate cell 126, provided that the measurement results indicate that the first candidate cell 126 has better measurement results. In another example, the network node 113 may derive the measurement results of the candidate L1 / L2 cells from the RLF report and based thereon may trigger L1 / L2 mobility to one of the candidate L1 / L2 cells with better measurement results earlier.

[0157] According to a third option c), on condition that the measurement results indicate that the first candidate cell 126 has poor measurement results, the adapting may include removing the first candidate cell 126 from the one or more candidate cells 125. In another example, the network node 113 may derive measurement results of candidate L1 / L2 cells from reports, e.g., RLF reports, etc., and based thereon may also remove candidate cells that may have poor measurement results from the list of candidate cells configured for L1 / L2 mobility.

[0158] According to a fourth option d), on condition that the measurement results indicate that the first neighboring cell 127 has good measurement results and the first neighboring cell 127 is not a candidate cell in the inter-cell mobility configuration, the adapting may include adding the first neighboring cell 127 to a list of candidate cells for the inter-cell mobility configuration. In another example, the network node 113 may derive measurement results for candidate L1 / L2 cells from a report, e.g., an RLF report, and based on the measurement results, may also include cells that have good measurement results but are not currently configured as candidate cells for L1 / L2 mobility in the configured list of candidate cells for L1 / L2 mobility for the UE connected to the failed PCell.

[0159] In some other examples, the network node 113 may derive the duration that the wireless device 130 was configured for L1 / L2 mobility before the failure occurred, in action 403. If the duration is determined to be short, the network node 113 may configure the L1 / L2 mobility configuration a little earlier, in action 404 and / or action 405. This may be understood because if the failure occurred in the wireless device 130 shortly after L1 / L2 mobility configuration, the network node 113 may not have had time to collect enough L1 / L2 measurements to trigger L1 / L2 mobility. On the other hand, if the period is determined to be too long in action 403, the network node 113 may configure the L1 / L2 mobility configuration a little later in action 404 and / or action 405, since L1 / L2 mobility configuration may require additional UE resources such as memory resources, energy and possibly radio resources if it means a new set of measurements and signaling reports to the network node 113. Also, performing the L1 / L2 mobility configuration too early may require extra resources on the network node 113 side, especially if a target cell that may belong to a different node may need to be prepared in advance for a potential handover.

[0160] Action 406 Action 406 may be performed in embodiments where the re-establishment procedure fails and the wireless device 130 may reconnect to the network node 113. In this action 406, the network node 113 may receive at least one of the fifth indication and the sixth indication.

[0161] This reception at action 406 may be, for example, from the wireless device 130 after it has reconnected.

[0162] The fifth indication may indicate whether the second cell 124 selected by the wireless device 130 for the reconnection procedure triggered by the failed re-establishment procedure was a candidate cell in the inter-cell mobility configuration received in the previous indication. The sixth indication may indicate the elapsed time between the first time of receipt of the inter-cell mobility configuration, e.g., L1 / L2 inter-cell mobility configuration, and the fifth time of reconnection due to the selection of the second cell 124.

[0163] In some embodiments, the fifth indication may be indicated in a reConnect-L1L2Candidate IE.

[0164] As a summary of the above, example embodiments disclosed herein may relate to wireless devices, network nodes, and methods performed by them to process re-establishment information after a mobility procedure failure, where the failure may be a radio link failure.

[0165] In summary summary above, example embodiments disclosed herein may relate to a method performed by a wireless device 130, e.g., a UE, the method comprising: a) receiving an L1 / L2 inter-cell mobility configuration from a first network node 111; b) declaring a radio link failure; and c) storing a first set of information related to the radio link failure in a first report, the first set of information including: i) an indication of whether a cell that may be selected for a re-establishment procedure was a candidate cell in the L1 / L2 inter-cell mobility configuration; ii) an indication of a candidate cell that is configured in the L1 / L2 inter-cell mobility configuration. iii) an indication indicating the time elapsed since receipt of the L1 / L2 inter-cell mobility configuration and radio link failure; iv) in one example, the indication may indicate the time elapsed since receipt of the last L1 / L2 mobility configuration and radio link failure; v) an indication indicating the location information at the time of receipt of the last L1 / L2 mobility configuration in addition to the location information at the time of the radio link failure; and d) possibly performing a re-establishment procedure with cells that were candidates for the L1 / L2 inter-cell mobility configuration, or transitioning to IDLE mode if no suitable cell is found.

[0166] The above information and indications regarding the re-establishment cell collected by the wireless device 130 may also be applicable to a scenario in which the wireless device 130 fails to perform re-establishment and reconnects to another cell after transitioning to RRC_IDLE mode.

[0167] Particular embodiments disclosed may provide one or more of the following technical advantages, which may be summarized as follows:

[0168] This embodiment can be understood as enabling the network to identify whether the re-establishment cell was part of an L1 / L2 inter-cell mobility configuration or not based on the additional content of the RLF report proposed in this embodiment.

[0169] If the re-established cell was part of the candidate list for L1 / L2 inter-cell mobility, the network may be able to fine-tune the triggering of L1 / L2 inter-cell mobility among the candidates. For example, the gNB-DU may be able to optimize L1 / L2 inter-cell mobility parameters.

[0170] If the re-established cell is not part of the candidate list for L1 / L2 inter-cell mobility, is the cell where the wireless device 130 declared RLF, and can be configured as an L1 / L2 inter-cell mobility candidate, the network may fine-tune the configuration of candidates for L1 / L2 inter-cell mobility. For example, the CU-CP and DU may optimize the candidate selection algorithm. Furthermore, based on measurements of L1 / L2 provisioning, the DU may find an optimal trigger threshold for L1 / L2 mobility from the failed cell to the re-established cell.

[0171] If the re-establishment cell is not part of the candidate list for L1 / L2 inter-cell mobility, is the cell where wireless device 130 declared RLF, and the re-establishment cell cannot be configured as an L1 / L2 inter-cell mobility candidate, the network may fine-tune the L3 mobility parameters. For example, the CU-CP may optimize handover parameters.

[0172] Figure 5 shows, in panels a) and b), two different examples of configurations that a wireless device 130 may have to perform the method actions described above in connection with Figure 3. In some embodiments, the wireless device 130 may have the following configurations shown in Figure 5a. The wireless device 130 may be understood to be for processing re-establishment information after a failure. The wireless device 130 may be configured to operate within the wireless communication network 100.

[0173] In some embodiments, wireless communication network 100 may be configured to support New Radio (NR)

[0174] Several embodiments are included herein. It should be noted that the examples herein are not mutually exclusive. Where applicable, one or more embodiments may be combined. For simplicity of explanation, not all possible combinations are described. Components of one embodiment may be implicitly assumed to be present in another embodiment, and it will be clear to one skilled in the art how those components may be used in other exemplary embodiments. Some of the detailed description below relates to actions described for wireless device 130 and corresponds to the same references set forth above, and therefore will not be repeated here for simplicity of explanation. For example, one or more indications may be configured to be transmitted in a report, which may be, for example, an RLF report.

[0175] In Figure 5, optional units are indicated by dashed boxes.

[0176] The wireless device 130 is configured to perform the saving / logging / recording action 304, for example by means of a storage unit 501 in the wireless device 130, configured to store one or more indications configured to indicate the failure in response to the declared failure. The one or more indications are configured to include at least a first indication configured to indicate whether the first cell 123 configured to be selected by the wireless device 130 for the re-establishment procedure configured to be triggered by the failure was a candidate cell in the inter-cell mobility configuration received in a previous indication to perform an L1 / L2 mobility procedure.

[0177] In some embodiments, at least one of the following may apply: a) the failure may be configured to be a mobility procedure; b) the failure may be configured to be one of a radio link failure and a handover failure; c) the mobility procedure may be configured to be L1 / L2 inter-cell mobility; d) the one or more indications may be configured to be sent in the report; e) the one or more indications may be configured to be sent in a UEInformationResponse message; f) the inter-cell mobility configuration may be configured to be L1 / L2 inter-cell mobility configuration.

[0178] In some embodiments, the one or more indications may be further configured to include at least one of the following: a) a second indication configured to indicate one or more candidate cells 125 configured with an inter-cell mobility configuration; b) a third indication configured to indicate an elapsed time between a first time of receipt of the inter-cell mobility configuration and a second time at which failure was declared; c) the third indication further configured to indicate a third elapsed time between a fourth time of receipt of the last inter-cell mobility configuration including the first cell 123 configured to be selected for the re-establishment procedure as a candidate cell and the second time at which failure was declared; d) a fourth indication configured to indicate at least one of i) the first location information at the fourth time, and ii) the second location information at the second time.

[0179] In some embodiments, at least one of the following may apply: a) the first indication may be configured to be indicated by a one-bit flag; b) the first indication may be configured to be indicated by a reest-L1L2Candidate IE; c) the first indication may be configured to further indicate additional L1 / L2 mobility related measurements; d) the first indication including additional L1 / L2 mobility related measurements may be configured to be indicated by a reest-L1L2meas IE; e) the first indication including additional L1 / L2 mobility related measurements may be configured to be indicated by a reConnect-L1L2meas IE; f) the second indication may be configured to indicate candidates-L1L2Mobility g) the second indication may be configured to be indicated by a candidate-L1L2flag flag; h) the second indication may be configured to further indicate additional L1 / L2 mobility related measurements; i) the second indication including additional L1 / L2 mobility related measurements may be configured to be indicated by a candidate-L1L2measIE; j) the third indication may be configured to be indicated by another IE; k) the fourth indication may be configured to be indicated by yet another IE.

[0180] In some embodiments, the wireless device 130 may further comprise one or more of the following:

[0181] The wireless device 130 may be configured to perform the sending of action 306 by means of, for example, a transmitting unit 502 within the wireless device configured to transmit any of one or more indications configured to be stored in a network node 113 configured to operate in the wireless communication network 100.

[0182] The wireless device 130 may be configured to perform the receiving action 301 by means of, for example, a receiving unit 503 in the wireless device 130 configured to receive a previous indication from the first network node 111 .

[0183] The wireless device 130 may be configured to perform the execution of action 302, for example by means of an execution unit 504 within the wireless device 130, configured to perform an L1 / L2 inter-cell mobility procedure from a first network node 111 to a second network node 112 configured to operate in the wireless communication network 100 in response to a previous indication configured to be received.

[0184] The wireless device 130 may be configured to perform the action 303 of declaring, for example by means of a declaring unit 505 in the wireless device 130, configured to declare a failure, for example a radio link failure.

[0185] The wireless device 130 may be configured to perform the execution in action 305, for example by means of an execution unit 504 within the wireless device 130, configured to perform a re-establishment procedure or a reconnection procedure to a third network node 113 configured to operate in the wireless communication network 100.

[0186] The wireless device 130 may be configured to perform the receiving in action 307, for example by means of a receiving unit 503 within the wireless device 130, configured to receive an updated inter-cell mobility procedure configuration from the network node 113 based on the one or more indications that the wireless device 130 is configured to transmit. The updated configuration may be configured to include one or more adapted procedures.

[0187] In some embodiments, one of the following may apply: a) the wireless device 130 may be configured to perform a re-establishment procedure after transitioning to idle mode or after a radio link failure; and b) the wireless device 130 may be configured to reconnect to the network node 113 after the re-establishment procedure may fail.

[0188] In some embodiments, the wireless device 130 may be configured to reconnect to the network node 113 after the re-establishment procedure fails, and the storing is further configured to include storing at least one of: a) a fifth indication configured to indicate whether the second cell 124 configured to be selected by the wireless device 130 for the re-establishment procedure configured to be triggered by the failed re-establishment procedure was a candidate cell in the inter-cell mobility configuration configured to be received in the previous indication; and b) a sixth indication configured to indicate the elapsed time between the first time of receipt of the inter-cell mobility configuration and the fifth time of re-connection due to selection of the second cell 124.

[0189] In some embodiments, the fifth indication may be configured as indicated in the reConnect-L1L2Candidate IE.

[0190] Other units 506 may be included in the wireless device 130 .

[0191] The present embodiments for the wireless device 130 may be implemented via one or more processors, such as the processor 507 of the wireless device 130 shown in FIG. 5a, and computer program code for performing the functions and actions of the present embodiments. A processor, as used herein, may be understood to be a hardware component. The program code may also be provided as a computer program product, for example in the form of a data carrier carrying computer program code that, when loaded into the wireless device 130, performs the present embodiments. One such carrier may be in the form of a CD-ROM disk. However, other data carriers, such as a memory stick, are also possible. The computer program code may also be provided as pure program code on a server and downloaded to the wireless device 130.

[0192] The wireless device 130 may further include a memory 508 including one or more memory units configured to be used to store information, data, configurations, schedules, applications, etc., acquired for performing the methods herein when executed on the wireless device 130.

[0193] In some embodiments, the wireless device 130 may receive information via the receive port 509 from, for example, the first network node 111, the second network node 112, the third network node 113, the network node 113, the source cell 121, the target cell 122, the first cell 123, the second cell 124, one or more candidate cells 125, the first candidate cell 126, the first neighbor cell 127, and / or another cell, network node, or node. In some embodiments, the receive port 509 may be connected to, for example, one or more antennas of the wireless device 130. In other embodiments, the wireless device 130 may receive information via the receive port 509 from another structure within the wireless communication network 100. The receive port 509 may be in communication with the processor 507 such that the receive port 509 can transmit the received information to the processor 507. The receive port 509 may also be configured to receive other information.

[0194] The processor 507 of the wireless device 130 may be further configured to transmit information to, for example, the first network node 111, the second network node 112, the third network node 113, the network node 113, the source cell 121, the target cell 122, the first cell 123, the second cell 124, one or more candidate cells 125, the first candidate cell 126, the first neighboring cell 127, another cell, network node, or node, or another structure within the wireless communication network 100, via a transmission port 510 and memory 508 that may be in communication with the processor 507.

[0195] Those skilled in the art will appreciate that the different units 501-506 described above may refer to a combination of analog and digital modules and / or one or more processors configured with software and / or firmware stored in, for example, memory, which when executed by one or more processors, such as processor 507, operates as described above. One or more of these processors, and other digital hardware, may be included in a single application specific integrated circuit (ASIC), or multiple processors and various digital hardware may be distributed across multiple individual components, whether individually packaged or assembled into a system on a chip (SoC).

[0196] Also, in some embodiments, the different units 501-506 may be implemented as one or more applications running on one or more processors, such as processor 507.

[0197] Thus, the methods according to the present embodiments described with respect to the wireless device 130 may each be implemented by means of a computer program 511 product including instructions, i.e., software code portions, which, when executed on the at least one processor 507, cause the at least one processor 507 to perform the actions described herein as being performed by the wireless device 130. The computer program 511 product may be stored on a computer-readable storage medium 512. The computer-readable storage medium 512 having the computer program 511 stored thereon may include instructions, which, when executed on the at least one processor 507, cause the at least one processor 507 to perform the actions described herein as being performed by the wireless device 130. In some embodiments, the computer-readable storage medium 512 may be a non-transitory computer-readable storage medium, such as a CD-ROM disk or a memory stick. In other embodiments, the computer program 511 product may be stored on a carrier containing the aforementioned computer program 511, the carrier being any one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium 512, as described above.

[0198] The wireless device 130 may comprise a communication interface configured to facilitate communication between the wireless device 130 and other nodes or devices, such as the first network node 111, the second network node 112, the third network node 113, the network node 113, the source cell 121, the target cell 122, the first cell 123, the second cell 124, one or more candidate cells 125, the first candidate cell 126, the first neighbor cell 127, another cell, a network node or nodes, or another structure within the wireless communication network 100. The interface may include, for example, a transceiver configured to transmit and receive radio signals over an air interface according to an appropriate standard.

[0199] In another embodiment, the wireless device 130 may comprise the following components shown in FIG. 5b. The wireless device 130 may comprise processing circuitry 507, such as one or more processors, such as processor 507, within the wireless device 130, and memory 508. The wireless device 130 may also comprise radio circuitry 513, which may include, for example, a receiving port 509 and a transmitting port 510. The processing circuitry 513 may be configured or operable to perform the method actions according to FIG. 3 in a manner similar to that described in connection with FIG. 5a. The radio circuitry 513 may be configured to establish and maintain at least one wireless connection with the first network node 111, the second network node 112, the third network node 113, the network node 113, the source cell 121, the target cell 122, the first cell 123, the second cell 124, one or more candidate cells 125, the first candidate cell 126, the first neighbor cell 127, another cell, network node or nodes, or another structure within the wireless communication network 100. A circuit may be understood here as a hardware component.

[0200] Accordingly, the present embodiment also relates to a wireless device 130 including a processing circuit 507 and a memory 508, where the memory 508 includes instructions executable by the processing circuit 507, such that the wireless device 130 operates to perform the actions described herein with respect to the wireless device 130, for example as shown in FIG.

[0201] Figure 6 shows, in panels a) and b), respectively, two different examples of configurations that a third network node 113, which may also be referred to as network node 113, may comprise to perform the method actions described above in relation to Figure 4. In some embodiments, the third network node 113 may comprise the following configurations shown in Figure 6a: The network node 113 may be understood to be for processing re-establishment information after a failure by the wireless device 130. The network node 113 may be configured to operate within the wireless communication network 100.

[0202] In some embodiments, the wireless communication network 100 may support New Radio (NR).

[0203] Several embodiments are included herein. It should be noted that the examples herein are not mutually exclusive. Where applicable, one or more embodiments may be combined. For simplicity of explanation, not all possible combinations are described. Components of one embodiment may be implicitly assumed to be present in another embodiment, and it will be clear to one skilled in the art how those components may be used in other exemplary embodiments. Some of the detailed description below corresponds to the same references provided above with respect to the actions described for the wireless device 130, and therefore will not be repeated here for simplicity of explanation. For example, one or more indications may be configured to be received in a report, which may be, for example, an RLF report.

[0204] In Figure 6, optional units are indicated by dashed boxes.

[0205] The network node 113, e.g., the third network node 113, is configured to perform the receiving in action 402, e.g., by means of a receiving unit 601 in the (third) network node 113, configured to receive from the wireless device 130 one or more indications configured to indicate a failure. The one or more indications are configured to include at least a first indication. The first indication is configured to indicate whether the first cell 123 configured to be selected by the wireless device 130 for the re-establishment procedure configured to be triggered by the failure was a candidate cell in an inter-cell mobility configuration. The inter-cell mobility configuration is configured to be received by the wireless device 130 in a previous indication to perform an L1 / L2 mobility procedure.

[0206] In some embodiments, at least one of the following may apply: a) the failure may be configured to be a mobility procedure; b) the failure may be configured to be one of a radio link failure and a handover failure; c) the mobility procedure may be configured to be L1 / L2 inter-cell mobility; d) the one or more indications may be configured to be received in a report; e) the one or more indications may be configured to be received in a UEInformationResponse message; f) the inter-cell mobility configuration may be configured to be L1 / L2 inter-cell mobility configuration.

[0207] In some embodiments, the one or more indications may be further configured to include at least one of the following: a) a second indication configured to indicate one or more candidate cells 125 configured with an inter-cell mobility configuration; b) a third indication configured to indicate an elapsed time between a first time of receipt of the inter-cell mobility configuration and a second time at which failure was declared; c) the third indication further configured to indicate a third elapsed time between a fourth time of receipt of the last inter-cell mobility configuration configured to include the first cell 123 configured to be selected for the re-establishment procedure as a candidate cell and the second time at which failure was declared; d) a fourth indication configured to indicate at least one of i) the first location information at the fourth time, and ii) the second location information at the second time.

[0208] In some embodiments, at least one of the following may apply: a) the first indication may be configured to be indicated by a one-bit flag; b) the first indication may be configured to be indicated by a reest-L1L2Candidate IE; c) the first indication may be configured to further indicate additional L1 / L2 mobility related measurements; d) the first indication including additional L1 / L2 mobility related measurements may be configured to be indicated by a reest-L1L2meas IE; e) the first indication including additional L1 / L2 mobility related measurements may be configured to be indicated by a reConnect-L1L2meas IE; f) the second indication may be configured to indicate candidates-L1L2Mobility g) the second indication may be configured to be indicated by a candidate-L1L2flag flag; h) the second indication may be configured to further indicate additional L1 / L2 mobility related measurements; i) the second indication including additional L1 / L2 mobility related measurements may be configured to be indicated by a candidate-L1L2meas IE; j) the third indication may be configured to be indicated by another IE; k) the fourth indication may be configured to be indicated by yet another IE.

[0209] The network node 113, for example the third network node 113, may be configured to perform the execution in action 401, for example by means of an execution unit 602 in the (third) network node 113, configured to perform a re-establishment procedure or a reconnection procedure with the wireless device 130, and one or more indications may be configured to be received after the execution of the re-establishment procedure.

[0210] In some embodiments, any one of the following may apply: a) the re-establishment procedure may be configured to be performed after the mobility procedure has failed, the wireless device 130 may be configured to enter idle mode, or b) the wireless device 130 may be configured to reconnect to the network node 113 after the re-establishment procedure may have failed.

[0211] In some embodiments, the wireless device 130 may be configured to reconnect to the network node 113 after the re-establishment procedure fails, and the network node 113, e.g., the third network node 113, may be further configured to perform receiving of action 406, e.g., by means of a receiving unit 601 in the (third) network node 113, configured to receive, after the re-connection, from the wireless device 130, at least one of: i) a fifth indication configured to indicate whether the second cell 124 configured to be selected by the wireless device 130 for the re-connection procedure configured to be triggered by the failed re-establishment procedure was a candidate cell in the inter-cell mobility configuration configured to be received in the previous indication; and ii) a sixth indication configured to indicate the elapsed time between the first time of receipt of the inter-cell mobility configuration and the fifth time of re-connection due to the selection of the second cell 124.

[0212] In some embodiments, the fifth indication may be configured as indicated in the reConnect-L1L2Candidate IE.

[0213] In some embodiments, the network node 113 may be further configured in at least one of the following three configurations:

[0214] In some embodiments, the network node 113, for example the third network node 113, may be configured to perform the determination of action 403, for example by means of a determining unit 603 in the (third) network node 113, the determining unit 603 being configured to determine, based on an indication configured to be received, one or more characteristics of the inter-cell mobility configuration configured to be selected from among: i) whether the first cell 123 configured to be selected by the wireless device 130 for the re-establishment procedure was a candidate cell in the inter-cell mobility configuration, ii) measurement results of one or more candidate cells 125 configured in the inter-cell mobility configuration, and c) the duration for which the wireless device 130 was configured in the inter-cell mobility configuration before the failure occurred.

[0215] In some embodiments, the network node 113, e.g. the third network node 113, may be configured to perform the initiation of action 404, e.g. by means of an initiation unit 604 in the (third) network node 113, configured to initiate the adaptation of one or more procedures of the inter-cell mobility configuration based on the result of the determination.

[0216] In some embodiments, the network node 113, e.g. the third network node 113, may be configured to perform the determination in action 403 by means of, e.g. a sending unit 605 in the third network node 113, configured to send, based on the adaptation, an updated inter-cell mobility configuration configured to include one or more procedures configured to be adapted.

[0217] In some embodiments, at least one of the following may apply: a) on condition that the first cell 123 was not a candidate cell in the inter-cell mobility configuration, the adapting may be configured to include adding the first cell 123 to a list of candidate cells in the inter-cell mobility configuration; b) on condition that the measurement results indicate that the first candidate cell 126 has better measurement results, the adapting may be configured to include triggering a mobility procedure to the first candidate cell 126; c) on condition that the measurement results indicate that the first candidate cell 126 has poor measurement results, the adapting may be configured to include removing the first candidate cell 126 from the one or more candidate cells 125; d) on condition that the measurement results indicate that the first neighboring cell 127 has good measurement results and the first neighboring cell 127 is not configured as a candidate cell in the inter-cell mobility configuration, the adapting may be configured to include adding the first neighboring cell 127 to a list of candidate cells in the inter-cell mobility configuration.

[0218] Further units 606 may be included in the third network node 113 .

[0219] The present embodiments for the third network node 113 may be implemented via one or more processors, such as the processor 607 of the third network node 113 shown in FIG. 6a, and computer program code for performing the functions and actions of the present embodiments. A processor as used herein may be understood to be a hardware component. The program code may also be provided as a computer program product, for example in the form of a data carrier carrying computer program code which, when loaded into the third network node 113, performs the present embodiments. One such carrier may be in the form of a CD ROM disk. However, other data carriers, such as a memory stick, are also possible. The computer program code may also be provided as pure program code on a server and downloaded to the third network node 113.

[0220] The third network node 113 may further comprise a memory 608 including one or more memory units configured to be used to store information, data, configurations, schedules, applications, etc. obtained for performing the methods herein when executed on the third network node 113.

[0221] In some embodiments, the third network node 113 may receive information from, for example, the wireless device 130, the first network node 111, the second network node 112, the source cell 121, the target cell 122, the first cell 123, the second cell 124, one or more candidate cells 125, the first candidate cell 126, the first neighbor cell 127, and / or another cell, network node, or node via the receive port 609. In some embodiments, the receive port 609 may be connected to, for example, one or more antennas within the third network node 113. In other embodiments, the third network node 113 may receive information from another structure within the wireless communication network 100 via the receive port 609. The receive port 609 may be in communication with the processor 607 such that the receive port 609 can transmit the received information to the processor 607. The receive port 609 may also be configured to receive other information.

[0222] The processor 607 of the third network node 113 may be further configured to transmit information to, for example, the wireless device 130, the first network node 111, the second network node 112, the source cell 121, the target cell 122, the first cell 123, the second cell 124, one or more candidate cells 125, the first candidate cell 126, the first neighboring cell 127, another cell, network node, or node, and / or another structure within the wireless communication network 100 via a transmission port 610 and memory 608 that may be in communication with the processor 607.

[0223] Those skilled in the art will appreciate that the different units 601-606 described above may refer to a combination of analog and digital modules and / or one or more processors configured with software and / or firmware stored in, for example, memory, which when executed by one or more processors, such as processor 607, operates as described above. One or more of these processors, and other digital hardware, may be included in a single application-specific integrated circuit (ASIC), or multiple processors and various digital hardware may be distributed across multiple individual components, whether individually packaged or assembled into a system-on-chip (SoC).

[0224] Also, in some embodiments, the different units 601-606 may be implemented as one or more applications running on one or more processors, such as processor 607.

[0225] Thus, the methods according to the present embodiments described for the third network node 113 may each be implemented by means of a computer program 611 product including instructions, i.e., software code portions, which, when executed on the at least one processor 607, cause the at least one processor 607 to perform the actions described herein to be performed by the third network node 113. The computer program 611 product may be stored on a computer-readable storage medium 612. The computer-readable storage medium 612 having the computer program 611 stored thereon may include instructions, which, when executed on the at least one processor 607, cause the at least one processor 607 to perform the actions described herein to be performed by the third network node 113. In some embodiments, the computer-readable storage medium 612 may be a non-transitory computer-readable storage medium, for example, a CD-ROM disk or a memory stick. In other embodiments, the computer program 611 product may be stored on a carrier containing the aforementioned computer program 611, the carrier being any one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium 612, as described above.

[0226] The third network node 113 may comprise a communication interface configured to facilitate communication between the third network node 113 and other nodes or devices, such as the wireless device 130, the wireless device 130, the first network node 111, the second network node 112, the source cell 121, the target cell 122, the first cell 123, the second cell 124, one or more candidate cells 125, the first candidate cell 126, the first neighbor cell 127, another cell, a network node or nodes, and / or another structure within the wireless communication network 100. The interface may include, for example, a transceiver configured to transmit and receive wireless signals over an air interface according to an appropriate standard.

[0227] In another embodiment, the third network node 113 may comprise the following components shown in Figure 6b: The third network node 113 may comprise processing circuitry 607, such as one or more processors, such as processor 607, within the third network node 113, and memory 608. The third network node 113 may also comprise radio circuitry 613, which may include, for example, a receiving port 609 and a transmitting port 610. The processing circuitry 607 may be configured or operable to perform method actions according to Figure 4 in a similar manner as described in relation to Figure 6a. The radio circuitry 613 may be configured to establish and maintain at least one radio connection with the wireless device 130, the wireless device 130, the first network node 111, the second network node 112, the source cell 121, the target cell 122, the first cell 123, the second cell 124, one or more candidate cells 125, the first candidate cell 126, the first neighboring cell 127, another cell, a network node or nodes, and / or another structure within the wireless communication network 100. Circuitry may be understood herein as a hardware component.

[0228] Accordingly, this embodiment also relates to a third network node 113 including a processing circuit 607 and a memory 608, where the memory 608 includes instructions executable by the processing circuit 607, such that the third network node 113 operates to perform the actions described herein with respect to the third network node 113, for example as shown in FIG. 4.

[0229] In general, all terms used herein should be interpreted according to their ordinary meaning in the relevant technical field unless a different meaning is clearly provided and / or a different meaning is suggested from the context in which they are used. All references to elements, devices, components, means, steps, etc., unless expressly stated otherwise, should be openly interpreted as a reference to at least one instance of that element, device, component, means, step, etc. The steps of any method disclosed herein need not be performed in the exact order disclosed, unless a step is explicitly described as being after or before another step and / or there is an implicit indication that a step must be after or before another step. Any feature of any embodiment disclosed herein may be applied to any other embodiment, where appropriate. Similarly, any advantage of any embodiment may also apply to any other embodiment, and vice versa. Other objects, features, and advantages of the included embodiments will become apparent from the following description.

[0230] As used herein, the phrase "at least one" followed by a comma-separated list of alternatives where the last alternative is preceded by the word "and" may be understood to mean that only one of the list of alternatives may apply, more than one of the list of alternatives may apply, or all of the list of alternatives may apply. This phrase may be understood to be equivalent to the phrase "at least one" followed by a comma-separated list of alternatives where the last alternative is preceded by the word "or."

[0231] In a non-limiting example, L1 signaling may be understood as any operation involving interaction / signaling between the physical (PHY) layer of a radio network node, such as a gNB, and the PHY layer of a device, such as a UE. In a non-limiting example, L2 signaling may be understood as any operation involving interaction / signaling between a RAN node, such as a gNB-DU, and a device, such as a UE, at Layer 2, such as the MAC layer or RLC layer.

[0232] In a non-limiting example, a mobility procedure may be understood as a procedure that involves a change of serving cell, such as a PCell, a PSCell, or a secondary cell (SCell).

[0233] In a non-limiting example, a mobility procedure may be understood as a procedure that involves a change of serving cell, such as a PCell, a PSCell, or a secondary cell (SCell).

[0234] Examples Related to the Embodiments Embodiments of the wireless device 130 relate to FIGS.

[0235] Described herein is a method performed by a wireless device, such as wireless device 130. The method may be understood to be for processing re-establishment information after a failure of a mobility procedure by wireless device 130, for example from a first network node 111 to a second network node 112. Wireless device 130 may operate in a wireless communication network, such as wireless communication network 100.

[0236] The failure may be, for example, a radio link failure.

[0237] Mobility procedures may also be referred to herein simply as mobility.

[0238] In some particular embodiments, the wireless communication network 100 may support New Radio (NR).

[0239] The method may include one or more of the following actions. In some embodiments, all actions may be performed. Where applicable, one or more embodiments may be combined. Components of one embodiment may be implicitly assumed to be present in another embodiment, and it will be apparent to one skilled in the art how those components may be used in other example embodiments. For simplicity, not all possible combinations are described. A non-limiting example of a method performed by wireless device 130 is shown in FIG. 7. In FIG. 7, optional actions in some embodiments may be indicated with dashed lines. In some embodiments, actions may be performed in a different order than shown in FIG. 7.

[0240] o Save / log / record 704 one or more indications. The wireless device 130 may be configured to perform this action 704, for example by means of a storage unit 501 in the wireless device 130 configured to perform this action.

[0241] This saving / logging / recording in action 704 may be in response to a declared failure.

[0242] The one or more indications may indicate a failed mobility procedure.

[0243] The one or more indications may include at least a first indication.

[0244] The first indication may indicate whether the cell selected by the wireless device 130 for the re-establishment procedure triggered by the failed mobility procedure, e.g., the first cell 123, was a candidate cell in the inter-cell mobility configuration received in the previous indication to perform the failed mobility procedure.

[0245] The previous indication may be received, for example, from the first network node 111 , the second network node 112 or another network node operating in the wireless communication network 100 .

[0246] In some embodiments, the method may additionally or alternatively include the following actions.

[0247] o Transmit 706 any of the one or more stored indications. The wireless device 130 may be configured to perform this transmitting action 706, for example by means of a transmitting unit 502 of the wireless device configured to perform this action.

[0248] This sending in action 705 may be to, for example, a third network node 113, which may also be referred to simply as network node 113. The third network node 113 may provide service to the wireless device 130 in the wireless communication network 100.

[0249] This sending in action 706 may be performed, for example, via first link 141.

[0250] The one or more indications transmitted may be, for example, a selected subset of the one or more stored indications.

[0251] In some instances, at least one of the following may apply: One or more indications may be sent in the report, One or more indications may be sent in the UEInformationResponse message; The failure may be a radio link failure; Mobility, for example, the mobility procedure may be L1 / L2 inter-cell mobility; The inter-cell mobility configuration may be an L1 / L2 inter-cell mobility configuration.

[0252] In some examples, the one or more indications may further include at least one of the following: a second indication; the second indication may indicate one or more candidate cells 125 configured with an inter-cell mobility configuration, e.g., an L1 / L2 inter-cell mobility configuration; a third indication; the third indication may indicate an elapsed time between a first time of receipt of an inter-cell mobility configuration, e.g., an L1 / L2 inter-cell mobility configuration, and a second time at which a failure, e.g., a radio link failure, is declared; the third indication further indicates a third elapsed time between a fourth time of reception of the last inter-cell mobility configuration, e.g., L1 / L2 inter-cell mobility configuration, and a second time at which a failure, e.g., a radio link failure, was declared; - A fourth indication; the fourth indication may indicate at least one of a) the first location information at a fourth time, and b) the second location information at a second time.

[0253] In some instances, at least one of the following may apply: The first indication may be indicated by a Rest-L1L2Candidate information element (IE), The first indication may further indicate additional L1 / L2 mobility related measurements; The first indication including additional L1 / L2 mobility related measurements may be indicated in a best-L1L2meas IE; The first indication including additional L1 / L2 mobility-related measurements may be indicated by reConnect-L1L2meas; The second indication may be indicated in a candidates-L1L2Mobility IE, The second indication may be indicated by a candidate-L1L2flag flag; The second indication may further indicate additional L1 / L2 mobility related measurements, A second indication including additional L1 / L2 mobility-related measurements may be indicated in a candidate-L1L2meas IE; The third indication may be indicated by another IE, The fourth indication may be indicated by yet another IE.

[0254] In some embodiments, the method may include one or more of the following actions.

[0255] o Receive 701 a previous indication. The wireless device 130 may be configured to perform this action 701 by means of, for example, a receiving unit 503 of the wireless device 130 configured to perform this action.

[0256] The reception in this action 701 may be, for example, from the first network node 111 , from the second network node 112 or from another network node operating in the wireless communication network 100 .

[0257] o Execute a mobility procedure 702. The wireless device 130 may be configured to perform this action 702, for example by means of an execution unit 504 of the wireless device 130 configured to perform this action.

[0258] The mobility procedure may be, for example, an L1 / L2 inter-cell mobility procedure.

[0259] The mobility procedure may be from a first network node 111 to a second network node 112, for example from a source cell 121 to a target cell 122.

[0260] This execution of action 702 may be, for example, in response to a previous indication received.

[0261] Declare 703 a mobility procedure failure. The wireless device 130 may be configured to perform this action 703 by means of, for example, a declaring unit 505 of the wireless device 130 configured to perform this action.

[0262] The failure may be, for example, a radio link failure.

[0263] o Execute a re-establishment or reconnection procedure 705. The wireless device 130 may be configured to perform this action 702, for example by means of an execution unit 504 of the wireless device 130 configured to perform this action.

[0264] The re-establishment or re-connection procedure may be, for example, to a third network node 113 operating in the wireless communication network 100 .

[0265] This execution of action 705 may be, for example, in response to a declared fault.

[0266] o Receive 707 an updated inter-cell mobility procedure configuration. The wireless device 130 may be configured to perform this action 707 by means of, for example, a receiving unit 503 of the wireless device 130 configured to perform this action.

[0267] The mobility procedure may be, for example, an L1 / L2 inter-cell mobility procedure.

[0268] This reception in action 707 may be from the third network node 113 .

[0269] This receipt at action 707 may be based, for example, on one or more transmitted indications.

[0270] The updated configuration may include adapted one or more procedures, such as candidate cell selection, mobility procedure trigger thresholds, and / or L3 mobility parameters.

[0271] In some instances, one of the following may apply: a) the wireless device 130 may perform a re-establishment procedure after transitioning to idle mode following a failed mobility procedure; b) The re-establishment procedure may fail and the wireless device 130 may reconnect to the third network node 113 .

[0272] In some examples, the re-establishment procedure may fail and the wireless device 130 may reconnect to the third network node 113. In some of these examples, saving action 704 may further include saving at least one of the following: a fifth indication; the fifth indication may indicate whether the second cell 124 selected by the wireless device 130 for the reconnection procedure triggered by the failed re-establishment procedure was a candidate cell in the inter-cell mobility configuration received in the previous indication; - Sixth indication; the sixth indication may indicate the elapsed time between the first time of receiving the inter-cell mobility configuration, e.g., the L1 / L2 inter-cell mobility configuration, and the fifth time of reconnection upon selection of the second cell 124.

[0273] Either the fifth indication or the sixth indication may optionally be transmitted to the third network node 113, for example.

[0274] In some examples, the fifth indication may be indicated in a reConnect-L1L2Candidate IE.

[0275] Other units 506 may be included in the wireless device 130 .

[0276] The wireless device 130 may also be configured to communicate user data with a host application unit in the host 716 , 800 , 902 via an OTT connection, such as OTT connection 950 .

[0277] In Figure 5, optional units are indicated by dashed boxes.

[0278] The wireless device 130 may comprise an interface unit for facilitating communication between the wireless device 130 and other nodes or devices, such as the third network node 113, the host 716, 800, 902, or any other node. In some particular examples, the interface may include, for example, a transceiver configured to transmit and receive radio signals over an air interface in accordance with an appropriate standard.

[0279] Embodiments of the third network node 113 relate to FIGS.

[0280] Described herein is a method performed by a network node, such as the third network node 113. The method may be understood to be for processing re-establishment information after a failure of a mobility procedure by a wireless device 130, for example from the first network node 111 to the second network node 112. The third network node 113 may operate in a wireless communication network, such as the wireless communication network 100.

[0281] Mobility procedures may also be referred to herein simply as mobility.

[0282] In some embodiments, the wireless communication network 100 may support New Radio (NR).

[0283] The method may include one or more of the following actions. In some embodiments, all actions may be performed. Where applicable, one or more embodiments may be combined. Components of one embodiment may be implicitly assumed to be present in another embodiment, and it will be apparent to one skilled in the art how those components may be used in other example embodiments. For simplicity of explanation, not all possible combinations are described. A non-limiting example of a method performed by the third network node 113 is shown in FIG. 8. In FIG. 8, optional actions in some embodiments may be indicated with dashed lines. In some embodiments, actions may be performed in a different order than shown in FIG. 8.

[0284] Some of the detailed description below corresponds to the same references provided above with respect to the actions described for wireless device 130 and will not be repeated here for brevity. For example, the failure may be, for example, a wireless link failure.

[0285] o Receive 802 one or more indications, for example a subset of one or more indications. The third network node 113 may be configured to perform this receiving action 802 by means of, for example, a receiving unit 601 of the third network node 113 configured to perform this action.

[0286] This reception in action 801 may be from the wireless device 130 .

[0287] This receiving in action 801 may be performed, for example, via the first link 141 .

[0288] The one or more indications may indicate a failed mobility procedure.

[0289] The one or more indications may include at least a first indication.

[0290] The first indication may indicate whether the first cell 123 selected by the wireless device 130 for the re-establishment procedure triggered by the failed mobility procedure was a candidate cell in the inter-cell mobility configuration received by the wireless device 130 in a previous indication to perform the failed mobility procedure.

[0291] The previous indication may be received, for example, from the first network node 111 , the second network node 112 or another network node operating in the wireless communication network 100 .

[0292] In some instances, at least one of the following may apply: One or more indications may be received in the report, One or more indications may be received in the UEInformationResponse message; The failure may be a radio link failure; Mobility, for example, the mobility procedure may be L1 / L2 inter-cell mobility; The inter-cell mobility configuration may be an L1 / L2 inter-cell mobility configuration.

[0293] In some examples, the one or more indications may further include at least one of the following: a second indication; the second indication may indicate one or more candidate cells 125 configured with an inter-cell mobility configuration, e.g., an L1 / L2 inter-cell mobility configuration; a third indication; the third indication may indicate an elapsed time between a first time of receipt of an inter-cell mobility configuration, e.g., an L1 / L2 inter-cell mobility configuration, and a second time at which a failure, e.g., a radio link failure, is declared; the third indication further indicates a third elapsed time between a fourth time of reception of the last inter-cell mobility configuration, e.g., L1 / L2 inter-cell mobility configuration, and a second time at which a failure, e.g., a radio link failure, was declared; - A fourth indication; the fourth indication may indicate at least one of a) the first location information at a fourth time, and b) the second location information at a second time.

[0294] In some instances, at least one of the following may apply: The first indication may be indicated by a Rest-L1L2Candidate information element (IE), The first indication may further indicate additional L1 / L2 mobility related measurements; The first indication including additional L1 / L2 mobility related measurements may be indicated in a best-L1L2meas IE; The first indication including additional L1 / L2 mobility-related measurements may be indicated by reConnect-L1L2meas; The second indication may be indicated in a candidates-L1L2Mobility IE, The second indication may be indicated by a candidate-L1L2flag flag; The second indication may further indicate additional L1 / L2 mobility related measurements; A second indication including additional L1 / L2 mobility-related measurements may be indicated in a candidate-L1L2meas IE; The third indication may be indicated by another IE, The fourth indication may be indicated by yet another IE.

[0295] In some embodiments, the method may further include one or more of the following actions.

[0296] o Execute a re-establishment or reconnection procedure 801. The third network node 113 may be configured to perform this action 801 by means of, for example, an execution unit 602 of the third network node 113 configured to perform this action.

[0297] The execution of this re-establishment or reconnection procedure in action 801 may be with the wireless device 130 .

[0298] One or more indications may be received after the re-establishment procedure is performed.

[0299] In some instances, one of the following may apply: a) The re-establishment procedure may be performed after the wireless device 130 may be in idle mode after a failed mobility procedure; b) The re-establishment procedure may fail and the wireless device 130 may reconnect to the third network node 113 .

[0300] In some embodiments, for example, a re-establishment procedure may fail and the wireless device 130 may reconnect to the third network node 113, and the method may further include one or more of the following actions.

[0301] o Receive 806 at least one of the fifth indication and the sixth indication. The third network node 113 may be configured to perform this receiving action 806 by means of, for example, a receiving unit 601 of the third network node 113 configured to perform this action.

[0302] This reception at action 806 may be, for example, from the wireless device 130 after it has reconnected. The fifth indication may indicate whether the second cell 124 selected by the wireless device 130 for the reconnection procedure triggered by the failed re-establishment procedure was a candidate cell in the inter-cell mobility configuration received in the previous indication; The sixth indication may indicate the elapsed time between the first time of receiving the inter-cell mobility configuration, e.g., the L1 / L2 inter-cell mobility configuration, and the fifth time of reconnection upon selection of the second cell 124.

[0303] In some examples, the fifth indication may be indicated in a reConnect-L1L2Candidate IE.

[0304] In some embodiments, the method may further include one or more of the following actions.

[0305] Determine 803 one or more characteristics of the inter-cell mobility configuration. The third network node 113 may be configured to perform the determination in this action 803, for example by means of a determining unit 603 of the third network node 113 configured to perform this action.

[0306] This determination at action 803 may be based on one or more, for example a subset, of the received indications.

[0307] The one or more characteristics of the determined inter-cell mobility configuration may be selected, for example, from the following: i. whether the first cell 123 selected by the wireless device 130 for the re-establishment procedure was a candidate cell in the inter-cell mobility configuration; ii. Measurement results of one or more candidate cells 125 configured with an inter-cell mobility configuration, e.g., an L1 / L2 inter-cell mobility configuration; and iii. The period of time during which the wireless device 130 was configured in an inter-cell mobility configuration, eg, an L1 / L2 inter-cell mobility configuration, before the failure occurred.

[0308] Initiate 804 adapting one or more procedures of inter-cell mobility configuration, e.g. L1 / L2 inter-cell mobility configuration. The third network node 113 may be configured to perform this initiation in action 804, e.g. by means of an initiation unit 604 of the third network node 113 configured to perform this action.

[0309] Initiation may be understood as initiating, promoting, enabling, triggering, etc.

[0310] In some examples, the adaptation of one or more procedures of the inter-cell mobility configuration, e.g., L1 / L2 inter-cell mobility configuration, may be, for example, at least one of candidate cell selection, mobility procedure trigger threshold, and L3 mobility parameters.

[0311] This initiation at action 804 may be based on the outcome of the determination, for example.

[0312] Transmit 805 the updated inter-cell mobility configuration, e.g. L1 / L2 inter-cell mobility configuration. The third network node 113 may be configured to perform the determination at this action 803, e.g. by means of a transmitting unit 605 of the third network node 113 configured to perform this action.

[0313] The updated inter-cell mobility configuration, eg, L1 / L2 inter-cell mobility configuration, may include one or more adapted procedures.

[0314] The sending of the updated inter-cell mobility configuration, eg, L1 / L2 inter-cell mobility configuration, in this action 805 may be based on the adaptation initiated in action 804 .

[0315] In some instances, at least one of the following may apply: On the condition that the first cell 123 was not a candidate cell in the inter-cell mobility configuration, the adapting may include, for example, adding the first cell 123 to a list of candidate cells in the inter-cell mobility configuration for the device connected to the cell, e.g., PCell, where the failed mobility procedure was detected; On condition that the measurement results indicate that the first candidate cell 126 has better measurement results, the adapting may include triggering a mobility procedure to the first candidate cell 126; Adapting may include removing the first candidate cell 126 from the one or more candidate cells 125 on condition that the measurement results indicate that the first candidate cell 126 has poor measurement results; - If the measurement results indicate that the first neighboring cell 127 has good measurement results and the first neighboring cell 127 is not a candidate cell in the inter-cell mobility configuration, adapting may include adding the first neighboring cell 127 to a list of candidate cells for the inter-cell mobility configuration.

[0316] Further units 606 may be included in the third network node 113 .

[0317] The third network node 113 may also be configured to communicate user data with a host application unit in the host 716 , 800 , 902 , for example via connection 960 .

[0318] In Figure 6, optional units are indicated by dashed boxes.

[0319] The third network node 113 may comprise an interface unit for facilitating communication between the third network node 113 and other nodes or devices, such as the wireless device 130, the first network node 111, the second network node 112, another node, a host 716, 800, 902, or any other node. In some particular examples, the interface may include, for example, a transceiver configured to transmit and receive wireless signals over an air interface in accordance with an appropriate standard.

[0320] The third network node 113 may include the configuration shown in FIG.

[0321] example:

[0322] Example 1. A method performed by a wireless device (130) operating in a wireless communication network (100) for processing re-establishment information after a failure of a mobility procedure by the wireless device (130) from a first network node (111) to a second network node (112), comprising: - in response to a declared failure, storing (704) one or more indications indicative of the failed mobility procedure, wherein the one or more indications include at least a first indication indicating whether a first cell (123) selected by the wireless device (130) for a re-establishment procedure triggered by the failed mobility procedure was a candidate cell in an inter-cell mobility configuration received in a previous indication from the first network node (111) for performing the failed mobility procedure.

[0323] Example 2. The method of Example 1, - one or more indications are sent in the report; and -One or more indications are sent in a UEInformationResponse message; and the failure is a radio link failure; -Mobility, e.g., mobility procedure is L1 / L2 inter-cell mobility; -The inter-cell mobility configuration is an L1 / L2 inter-cell mobility configuration; The method is at least one of:

[0324] Example 7. The method of example 1 or 2, wherein the one or more indications further comprise: - a second indication indicating one or more candidate cells (125) configured with an inter-cell mobility configuration, e.g., an L1 / L2 inter-cell mobility configuration; a third indication indicating an elapsed time between a first time of receiving an inter-cell mobility configuration, e.g., an L1 / L2 inter-cell mobility configuration, and a second time at which a failure, e.g., a radio link failure, is declared; the third indication further indicating a third elapsed time between a fourth time of reception of a last inter-cell mobility configuration, e.g., L1 / L2 inter-cell mobility configuration, and a second time at which a failure, e.g., a radio link failure, was declared; - a fourth indication of at least one of a) the first position information at a fourth time, and b) the second position information at a second time; The method includes at least one of:

[0325] Example 8. The method of Example 7, The first indication is indicated by a Rest-L1L2Candidate information element (IE); the first indication further indicates additional L1 / L2 mobility related measurements; The first indication including additional L1 / L2 mobility related measurements is indicated in a best-L1L2meas IE; The first indication including additional L1 / L2 mobility-related measurements is indicated by reConnect-L1L2meas; The second indication is indicated by candidates-L1L2Mobility IE; The second indication is indicated by a candidate-L1L2flag flag; the second indication further indicates additional L1 / L2 mobility related measurements; The second indication including additional L1 / L2 mobility related measurements is indicated in a candidate-L1L2meas IE; The third indication is shown in another IE, The fourth indication is indicated by a further IE; The method is at least one of:

[0326] Example 5. The method of any one of Examples 1 to 4, further comprising: receiving (701) a previous indication from a first network node (111); - performing (702) a mobility, e.g., L1 / L2 inter-cell mobility procedure, from the first network node (111) to the second network node (112) in response to the received previous indication; - declaring (703) a failure in the mobility procedure, e.g. a radio link failure; - performing (705) a re-establishment or re-connection procedure to a third network node (113) operating in the wireless communication network (100); - transmitting (706) any of the one or more stored indications to a (third) network node (113); - receiving (707) an updated inter-cell mobility procedure, e.g., L1 / L2 inter-cell mobility procedure configuration from the (third) network node (113) based on the one or more transmitted indications, the updated configuration including at least one of adapted one or more procedures, e.g., candidate cell selection, mobility procedure trigger threshold, and L3 mobility parameters; The method includes one or more of the following:

[0327] Example 6. The method of Example 5, a) the wireless device 130 performs a re-establishment procedure after transitioning to idle mode following a failed mobility procedure, or -b) the re-establishment procedure fails and the wireless device (130) reconnects to the (third) network node (113).

[0328] Example 7. The method of Example 6, wherein the re-establishment procedure fails and the wireless device (130) reconnects to and saves (704) the (third) network node (113), further comprising: a fifth indication indicating whether the second cell (124) selected by the wireless device (130) for the reconnection procedure triggered by the failed re-establishment procedure was a candidate cell in the inter-cell mobility configuration received in the previous indication; and a sixth indication indicating an elapsed time between a first time of receiving an inter-cell mobility configuration, e.g., an L1 / L2 inter-cell mobility configuration, and a fifth time of reconnection upon selection of the second cell (124); storing at least one of

[0329] Example 8. The method of example 7, wherein the fifth indication is indicated by a reConnect-L1L2Candidate IE.

[0330] Example 9. A method performed by a (third) network node (113) for processing re-establishment information after a failure of a mobility procedure by a wireless device (130) from a first network node (111) to a second network node (112), the third network node (113) operating in a wireless communication network (100), the method comprising: -A method comprising receiving (802) from a wireless device (13) one or more indications indicating a failed mobility procedure, wherein the one or more indications include at least a first indication indicating whether a first cell (123) selected by the wireless device (130) for a re-establishment procedure triggered by the failed mobility procedure was a candidate cell in an inter-cell mobility configuration of a previous indication received by the wireless device (130) from a first network node (111) for performing the failed mobility procedure.

[0331] Example 10. The method of Example 9, - one or more indications are received in the report; and one or more indications are received in a UEInformationResponse message; and the failure is a radio link failure; -The mobility is L1 / L2 inter-cell mobility; -The inter-cell mobility configuration is an L1 / L2 inter-cell mobility configuration; The method is at least one of:

[0332] Example 11. The method of example 9 or 10, wherein the one or more indications further comprise: - a second indication indicating one or more candidate cells (125) configured with an inter-cell mobility configuration, e.g., an L1 / L2 inter-cell mobility configuration; a third indication indicating an elapsed time between a first time of receiving an inter-cell mobility configuration, e.g., an L1 / L2 inter-cell mobility configuration, and a second time at which a failure, e.g., a radio link failure, is declared; the third indication further indicating a third elapsed time between a fourth time of reception of a last inter-cell mobility configuration, e.g., L1 / L2 inter-cell mobility configuration, and a second time at which a failure, e.g., a radio link failure, was declared; - a fourth indication of at least one of a) the first position information at a fourth time, and b) the second position information at a second time; The method includes at least one of:

[0333] Example 12. The method of Example 11, The first indication is indicated by a Rest-L1L2Candidate information element (IE); the first indication further indicates additional L1 / L2 mobility related measurements; The first indication including additional L1 / L2 mobility related measurements is indicated in a best-L1L2meas IE; The first indication including additional L1 / L2 mobility-related measurements is indicated by reConnect-L1L2meas; The second indication is indicated by candidates-L1L2Mobility IE; The second indication is indicated by a candidate-L1L2flag flag; the second indication further indicates additional L1 / L2 mobility related measurements; The second indication including additional L1 / L2 mobility related measurements is indicated in a candidate-L1L2meas IE; The third indication is shown in another IE, The fourth indication is indicated by a further IE; The method is at least one of:

[0334] Example 13. The method of any one of Examples 9 to 12, further comprising: A method comprising: performing (801) a re-establishment or re-connection procedure with a wireless device (130), wherein one or more indications are received after performing the re-establishment procedure.

[0335] Example 14. The method of Example 13, a) the re-establishment procedure is performed after the wireless device 130 transitions to idle mode after a failed mobility procedure, or -b) A method in which the re-establishment procedure fails and the wireless device (130) reconnects, for example, to a (third) network node (113).

[0336] Example 15. The method of example 15, wherein the re-establishment procedure fails and the wireless device (130) reconnects to the (third) network node (113), the method further comprising: After reconnection, the wireless device (130) i. a fifth indication indicating whether the second cell (124) selected by the wireless device (130) for the reconnection procedure triggered by the failed re-establishment procedure was a candidate cell in the inter-cell mobility configuration received in the previous indication; and ii. a sixth indication indicating an elapsed time between a first time of receiving an inter-cell mobility configuration, e.g., an L1 / L2 inter-cell mobility configuration, and a fifth time of reconnection upon selection of the second cell (124); receiving (806) at least one of:

[0337] Example 16. The method of example 15, wherein the fifth indication is indicated by a reConnect-L1L2Candidate IE.

[0338] Example 17. The method of any one of Examples 9 to 16, further comprising: - based on one or more received indications, i. whether the first cell (123) selected by the wireless device (130) for the re-establishment procedure was a candidate cell in the inter-cell mobility configuration; ii. Measurement results of one or more candidate cells (125) configured with an inter-cell mobility configuration, e.g., an L1 / L2 inter-cell mobility configuration; iii. the duration that the wireless device (130) was configured in an inter-cell mobility configuration, e.g., an L1 / L2 inter-cell mobility configuration, before the failure occurred; and determining (803) one or more characteristics of an inter-cell mobility configuration, e.g., selected from - initiating (804) based on the determination result one or more procedures of inter-cell mobility configuration, e.g. L1 / L2 inter-cell mobility configuration, adapting at least one of candidate cell selection, mobility procedure trigger threshold, and L3 mobility parameters; - based on the adaptation, transmitting (805) an updated inter-cell mobility configuration, e.g., L1 / L2 inter-cell mobility configuration, including the adapted one or more procedures; The method includes at least one of the following:

[0339] Example 18. The method of Example 17, further comprising: - on the condition that the first cell (123) was not a candidate cell in the inter-cell mobility configuration, the adapting includes, for example, adding the first cell (123) to a list of candidate cells in the inter-cell mobility configuration for a device connected to a cell, e.g., a PCell, where the failed mobility procedure was detected; - on condition that the measurement results indicate that the first candidate cell (126) has better measurement results, the adapting includes triggering a mobility procedure to the first candidate cell (126); - on condition that the measurement results indicate that the first candidate cell (126) has a poor measurement result, the adapting includes removing the first candidate cell (126) from the one or more candidate cells (125); - if the measurement result indicates that the first neighboring cell (127) has a good measurement result and the first neighboring cell (127) is not a candidate cell in the inter-cell mobility configuration, the adapting includes adding the first neighboring cell (127) to a list of candidate cells in the inter-cell mobility configuration; The method includes at least one of:

[0340] Further expansion and variations

[0341] FIG. 9 illustrates an example of a communication system 900 according to some embodiments.

[0342] In this example, a communication system 900, such as wireless communication network 100, includes a telecommunications network 902 including an access network 904, such as a radio access network (RAN), and a core network 906 including one or more core network nodes 908. The access network 904 includes one or more access network nodes, such as third network node 113 or network node 113. For example, network nodes 910a and 910b or any other similar Third Generation Partnership Project (3GPP) access nodes or non-3GPP access points, one or more of which may be generally referred to as network node 910. The communication system 900 includes a plurality of wireless devices, such as wireless device 130. In FIG. 9, the plurality of wireless devices includes UEs 912a, 912b, 912c, and 912d, one or more of which may also be generally referred to as UEs 912. The network node 910 facilitates direct or indirect connectivity of user equipment (UE), such as by connecting UEs 912a, 912b, 912c, and 912d to the core network 906 over one or more wireless connections. UEs 912a, 912b, 912c, and 912d are all examples of wireless devices 130.

[0343] 9, 10, and 11 described next, it may be understood that any UE is an example of a wireless device 130, and any description provided for a UE 912 or a UE 1106 equally applies to the wireless device 130. It may also be understood that any network node is an example of a third network node 113 or a network node 113, and any description provided for a network node 910 or a network node 1104 equally applies to a third network node 113 or a network node 113. Furthermore, it may be understood that the communication system 900 is an example of a wireless communication network 100, and any description provided for the communication system 900 equally applies to the wireless communication network 100.

[0344] Exemplary wireless communications over wireless connections include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for carrying information without the use of wires, cables, or other material conductors. Moreover, in various embodiments, communications system 900 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals, whether via wired or wireless connections. Communications system 900 may include and / or interface with any type of communications, telecommunications, data, cellular, wireless networks, and / or other similar types of systems.

[0345] The wireless device 130, illustrated in Figure 9 as a UE 912, may be any of a wide variety of communications devices, including wireless devices and other communications devices arranged, configured, and / or operable to communicate wirelessly with the third network node 113, illustrated in Figure 9 as network node 910, or the network node 113. Similarly, the network node 910 is arranged, capable, configured, and / or operable to communicate, directly or indirectly, with the UE 912 and / or with other network nodes or equipment within the telecommunications network 902 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as management within the telecommunications network 902.

[0346] In the illustrated example, the core network 906 connects the network node 910 to one or more hosts, such as the host 916. These connections may be direct or indirect through one or more intermediate networks or devices. In other examples, the network nodes may be directly coupled to the hosts. The core network 906 includes one or more core network nodes (e.g., the core network node 908) structured with hardware and software components. The functionality of these components may be substantially similar to that described with respect to the UEs, network nodes, and / or hosts, and thus, these descriptions are generally applicable to the corresponding components of the core network node 908. Exemplary core network nodes include one or more of a Mobile Switching Center (MSC), a Mobility Management Entity (MME), a Home Subscriber Server (HSS), an Access and Mobility Management Function (AMF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Subscription Identifier Deciphering Function (SIDF), a Unified Data Management (UDM), a Security Edge Protection Proxy (SEPP), a Network Publishing Function (NEF), and / or a User Plane Function (UPF).

[0347] The host 916 may be owned or controlled by, and operated by or on behalf of, a non-operator service provider or provider of the access network 904 and / or telecommunications network 902. The host 916 may host a variety of applications to provide one or more services. Examples of such applications include live and pre-recorded audio / video content, data collection services such as acquiring and compiling data about various ambient conditions sensed by multiple UEs, analytics functionality, social media, functionality for controlling or otherwise interacting with remote devices, functionality for alarm and monitoring centers, or any other such functionality performed by a server.

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

[0349] In some examples, the telecommunications network 902 is a cellular network that implements functions standardized by 3GPP. Thus, the telecommunications network 902 may support network slicing to provide different logical networks to different devices connected to the telecommunications network 902. For example, the telecommunications network 902 may provide Ultra-Reliable Low Latency Communications (URLLC) services to some UEs, while providing enhanced Mobile Broadband (eMBB) services to other UEs and massive machine type communications (mMTC) / massive IoT services to still further UEs.

[0350] In some examples, the UE 912 is configured to transmit and / or receive information without direct human interaction. For example, the UE may be designed to transmit information to the access network 904 on a predetermined schedule, when triggered by an internal or external event, or upon request from the access network 904. Additionally, the UE may be configured to operate in a single or multi-RAT or multi-standard mode. For example, the UE may be configured and operate in any one or combination of Wi-Fi, New Radio (NR), and LTE, i.e., for Multi-Radio Dual Connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio-Dual Connectivity (EN-DC).

[0351] In the above example, the hub 914 communicates with the access network 904 to facilitate indirect communication between one or more UEs (e.g., UE 912c and / or 912d) and a network node (e.g., network node 910b). In some examples, the hub 914 may be a controller, router, content source, analytics, or any of the other communication devices described herein with respect to a UE. For example, the hub 914 may be a broadband router that enables access to the core network 906 for the UE. As another example, the hub 914 may be a controller that sends commands or instructions to one or more actuators in the UE. The commands or instructions may be received from the UE or the network node 910 or may be accepted by executable code, scripts, processes, or other instructions in the hub 914. As another example, the hub 914 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of that data. As another example, the hub 914 may be a content source. For example, for UEs that are VR headsets, displays, loudspeakers, or other media delivery devices, the hub 914 may obtain media or data related to VR assets, video, audio, or other sensory information via a network node, and then provide it to the UE either directly, after performing local processing, and / or after adding additional local content. In yet another example, the hub 914 acts as a proxy server or orchestrator for the UEs, especially if one or more of the UEs are low energy IoT devices.

[0352] Hub 914 may have a constant / permanent or intermittent connection to network node 910b. Hub 914 may also enable different communication schemes and / or schedules between hub 914 and UEs (UEs 912c and / or 912d) and between hub 914 and core network 906. In other examples, hub 914 is connected to core network 906 and / or one or more UEs via a wired connection. Additionally, hub 914 may be configured to connect to an M2M service provider over access network 904 and / or to other UEs over a direct connection. In some scenarios, a UE may establish a wireless connection with network node 910b while still being connected via hub 914 via a wired or wireless connection. In some embodiments, hub 914 may be a dedicated hub, i.e., a hub whose primary function is to route communications between UEs and network node 910b. In other embodiments, hub 914 may be a non-dedicated hub, i.e., a device that is operable to route communications between UEs and network node 910b, but that is also operable as an origination and / or termination point for communications for any data channel.

[0353] 10 is a block diagram of a host 1000, which may be an embodiment of the host 916 of FIG. 9, in accordance with various aspects described herein. As used herein, the host 1000 may be or include various combinations of hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, a container, or processing resources within a server farm. The host 1000 may provide one or more services to one or more UEs.

[0354] Host 1000 includes a processing circuit 1002 operably coupled via a bus 1004 to an input / output interface 1006, a network interface 1008, a power supply 1010, and memory 1012. In other embodiments, other components may be included, the functionality of which may be substantially similar to those described with respect to the devices of the previous figures, and therefore those descriptions are generally applicable to the corresponding components of host 1000.

[0355] Memory 1012 may include one or more computer programs, including one or more host application programs 1014, and data 1016, which may include user data, such as data generated by a UE for the host 1000 or data generated by the host 1000 for the UE. An embodiment of the host 1000 may utilize only a subset or all of the illustrated components. The host application programs 1014 may be implemented in a container-based architecture and may provide support for video codecs (Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for different UE classes, types, or implementations (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application program 1014 may also provide user authentication and license checks, and may periodically report health, route, and content availability to a central node, such as a device in or at the edge of the core network. Thus, the host 1000 may select and / or point to different hosts for over-the-top services for the UE. The host application program 1014 may support a variety of protocols, such as HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), MPEG-DASH (Dynamic Adaptive Streaming over HTTP), etc.

[0356] Figure 11 illustrates a communication diagram of a host 1102 communicating with a UE 1106 via a network node 1104 over a partial wireless connection according to some embodiments. Exemplary implementations according to various embodiments of a UE, such as UE 912a of Figure QQ, a network node, such as network node 910a of Figure 9, and a host, such as host 916 of Figure 9 and / or host 1000 of Figure 10, discussed in the preceding paragraphs, will now be described with reference to Figure 11.

[0357] Similar to the host 1000, an embodiment of the host 1102 includes hardware such as a communications interface, processing circuitry, and memory. The host 1102 also includes software stored within or accessible by the host 1102 and executable by the processing circuitry. The software includes a host application that may be operable to provide services to a remote user, such as a UE 1106, connecting via an over-the-top (OTT) connection 1150 extending between the UE 1106 and the host 1102. During the provision of services to the remote user, the host application may provide user data that is transmitted using the OTT connection 1150.

[0358] The network node 1104 includes hardware that enables communication with the host 1102 and the UE 1106. The connection 1160 may be direct or may pass through one or more other intermediate networks, such as a core network (such as the core network 906 in FIG. 9) and / or one or more public, private, or hosted networks. For example, the intermediate network may be a backbone network or the Internet.

[0359] The UE 1106 includes hardware and software stored within or accessible by the UE 1106 and executable by the UE's processing circuitry. This software includes a client application, such as a web browser or operator-specific "app," that may be operable, with the support of a host 1102, to provide services to a human or non-human user via the UE 1106. A host application running on the host 1102 can communicate with a client application running on the UE 1106 via an OTT connection 1150 that terminates at the host 1102. During the provision of a service to a user, the UE's client application may receive request data from the host application and provide user data in response to the request data. The OTT connection 1150 may transport both request data and user data. The UE's client application may interact with the user to generate user data that it provides to the host application through the OTT connection 1150.

[0360] The OTT connection 1150 may extend via a connection 1160 between the host 1102 and the network node 1104 and via a wireless connection 1170 between the network node 1104 and the UE 1106, providing a connection between the host 1102 and the UE 1106. The connection 1160 and the wireless connection 1170 over which the OTT connection 1150 may be provided are depicted abstractly to illustrate communication between the host 1102 and the UE 1106 via the network node 1104 without explicit reference to any intermediate devices and the exact routing of messages through those devices.

[0361] As an example of transmitting data over the OTT connection 1150, in step 1108, the host 1102 provides user data, which may be done by executing a host application. In some embodiments, the user data is associated with a specific human user interacting with the UE 1106. In other embodiments, the user data is associated with the UE 1106 sharing data with the host 1102 without explicit human interaction. In step 1110, the host 1102 initiates a transmission to the UE 1106 carrying user data. The host 1102 may initiate the transmission in response to a request sent by the UE 1106. The request may be triggered by human interaction with the UE 1106 or by the operation of a client application running on the UE 1106. In accordance with the teachings of embodiments described throughout this disclosure, the transmission may pass through the network node 1104. In response, at step 1112, the network node 1104 transmits the user data carried in the transmission initiated by the host 1102 to the UE 1106, in accordance with the teachings of embodiments described throughout this disclosure. At step 1114, the UE 1106 receives the user data carried in the transmission, which may be done by a client application running on the UE 1106 that is associated with a host application executed by the host 1102.

[0362] In some examples, the UE 1106 executes a client application, which provides user data destined for the host 1102. The user data may be provided in reaction or response to receiving data from the host 1102. In response, at step 1116, the UE 1106 may provide the user data, which may be done by executing the client application. During the provision of the user data, the client application may further consider user input received from a user via an input / output interface of the UE 1106. Regardless of the specific manner in which the user data is provided, the UE 1106 initiates transmission of the user data to the host 1102 via the network node 1104 at step 1118. At step 1120, in accordance with the teachings of embodiments described throughout this disclosure, the network node 1104 receives the user data from the UE 1106 and initiates transmission of the received user data to the host 1102. At step 1122, the host 1102 receives the user data carried in the transmission initiated by the UE 1106.

[0363] One or more various embodiments improve the performance of the OTT service provided to the UE 1106 using the OTT connection 1150, of which the radio connection 1170 forms the final segment. More precisely, the teachings of these embodiments can improve data rate, latency, and power consumption, thereby providing benefits such as reduced user latency, reduced overhead, and extended battery life.

[0364] In an exemplary scenario, factory status information may be collected and analyzed by the host 1102. As another example, the host 1102 may process audio and video data, possibly obtained from UEs, for use in generating maps. As another example, the host 1102 may collect and analyze real-time data to assist in traffic congestion control (e.g., traffic light control). As another example, the host 1102 may store surveillance video uploaded by UEs. As another example, the host 1102 may store or control access to media content, such as video, audio, VR, or AR, that may be broadcast, multicast, or unicast to UEs. As another example, the host 1102 may be used for energy pricing, remote control of non-time-critical power loads for balancing power generation needs, location services, presentation services (e.g., compiling diagrams from data collected from remote devices), or any other function that collects, acquires, stores, analyzes, and / or transmits data.

[0365] In some examples, measurement procedures may be provided to monitor data rates, delays, and other factors that are improved by one or more embodiments. Additionally, there may be optional network functionality for reconfiguring the OTT connection 1150 between the host 1102 and the UE 1106 in response to fluctuations in the measurements. The measurement procedures and / or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware in the host 1102 and / or the UE 1106. In some embodiments, sensors (not shown) may be deployed in or associated with other devices through which the OTT connection 1150 passes, and these sensors may participate in the measurement procedures by providing values ​​for the monitored quantities exemplified above or other physical quantities from which the monitored quantities may be calculated or estimated by software. Reconfiguration of the OTT connection 1150 may include message formats, retransmission settings, preferred routing, etc., and the reconfiguration need not directly alter the operation of the network node 1104. Such procedures and functionality may be known or practiced in the art. In one embodiment, the measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation time, delay, etc. by the host 1102. The measurements may be implemented by software sending messages over the OTT connection 1150, specifically empty or "dummy" messages, while monitoring propagation time, errors, etc.

[0366] Embodiments of the wireless device 130 relate to FIGS. 3, 5, 7, 9, and 11.

[0367] The wireless device 130 may also be configured to communicate user data with a host application unit in the host 916 , 1000 , 1102 via an OTT connection, such as OTT connection 1150 .

[0368] The wireless device 130 may comprise an interface unit for facilitating communication between the wireless device 130 and other nodes or devices, such as the third network node 113 or the network node 113, the host 916, 1000, 1102, or any other node. In some particular examples, the interface may include, for example, a transceiver configured to transmit and receive radio signals over an air interface in accordance with an appropriate standard.

[0369] Embodiments of the third network node 113 or network node 113 relate to Figures 4, 6, 8, 9 and 11.

[0370] The third network node 113 or network nodes 113 may also be configured to communicate user data with host application units in hosts 916 , 1000 , 1102 , for example via connection 1160 .

[0371] The third network node 113 or network node 113 may comprise an interface unit for facilitating communication between the third network node 113 or network node 113 and other nodes or devices, such as the wireless device 130, the first network node 111, the second network node 112, another node, a host 916, 1000, 1102, or any other node. In some particular examples, the interface may include, for example, a transceiver configured to transmit and receive wireless signals over an air interface in accordance with an appropriate standard.

[0372] Further Numbered Embodiments

[0373] 1. A host configured to operate in a communication system to provide over-the-top (OTT) services, comprising: processing circuitry configured to provide user data; a network interface configured to initiate transmission of user data to a network node of a cellular network for transmission to a user equipment (UE); The network node comprises a communications interface and processing circuitry, the processing circuitry of the network node configured to perform one or more of the actions described herein as being performed by a third network node 113 or the network node 113, a host.

[0374] 2. The host of the previous embodiment, processing circuitry of the host configured to execute a host application that provides user data; The UE includes processing circuitry configured to execute a client application associated with the host application that receives user data transmissions from the host.

[0375] 3. A method executed in a host configured to operate in a communication system further including a network node and a user equipment (UE), comprising: Providing user data of the UE; and initiating a transmission carrying user data to the UE via a cellular network including the network node, wherein the network node performs one or more of the actions described herein as being performed by a third network node 113 or the network node 113.

[0376] 4. The method of the previous embodiment, further comprising: A method comprising, at a network node, transmitting user data provided by a host for a UE.

[0377] 5. The method of either of the previous two embodiments, comprising: A method in which user data is provided at the host by executing a host application that interacts with a client application running on the UE, the client application being associated with the host application.

[0378] 6. A communication system configured to provide over-the-top services, comprising: A host, a processing circuit configured to provide user data associated with the over-the-top service to a user equipment (UE); a network interface configured to initiate transmission of user data towards a cellular network node for transmission to the UE, the network node comprising a communications interface and processing circuitry, the processing circuitry of the network node configured to perform one or more of the actions described herein as being performed by a third network node 113 or the network node 113.

[0379] 7. The communication system according to the previous embodiment, further comprising: network nodes, and / or A communication system including a user device.

[0380] 8. The communication system according to the previous two embodiments, the host processing circuitry is configured to execute a host application to provide user data; A communication system, wherein the host application is configured to interact with a client application running on the UE, the client application being associated with the host application.

[0381] 9. A host configured to operate in a communication system providing over-the-top (OTT) services, comprising: a processing circuit configured to initiate reception of user data; a network interface configured to receive user data from a network node of a cellular network, the network node comprising a communications interface and processing circuitry, the processing circuitry of the network node configured to perform one or more of the actions described herein as being performed by a third network node 113 or the network node 113.

[0382] 10. The host of the previous two embodiments, the host processing circuitry is configured to execute a host application to provide user data; The host application is configured to interact with a client application running on the UE, the client application being associated with the host application.

[0383] 11. The host of any of the previous two embodiments, Initiating reception of user data includes requesting the user data, the host.

[0384] 12. A method performed in a host configured to operate in a communication system further including a network node and a user equipment (UE), comprising: A method, in a host, initiating reception of user data from a UE, the user data originating from a transmission received by a network node from the UE, the network node performing one or more of the actions described herein as being performed by a third network node 113 or the network node 113.

[0385] 13. The method of the previous embodiment, further comprising: A method comprising, at a network node, transmitting received user data to a host.

[0386] 14. A host configured to operate in a communication system providing over-the-top (OTT) services, comprising: processing circuitry configured to provide user data; a host comprising: a network interface configured to initiate transmission of user data to a cellular network for transmission to a user equipment (UE), the UE comprising a communications interface and processing circuitry, the communications interface and processing circuitry of the UE configured to perform one or more of the actions described herein as being performed by wireless device 130;

[0387] 15. The host of the previous embodiment, The cellular network further includes a network node configured to communicate with the UE for transmitting user data from the host to the UE.

[0388] 16. The host of the previous two embodiments, the host processing circuitry is configured to execute a host application to provide user data; The host application is configured to interact with a client application running on the UE, the client application being associated with the host application.

[0389] 17. A method performed in a host operating in a communication system further including a network node and a user equipment (UE), comprising: Providing user data of the UE; and initiating a transmission carrying user data to a UE via a cellular network including a network node, wherein the UE performs one or more of the actions described herein as being performed by a wireless device 130.

[0390] 18. The method of the previous embodiment, further comprising: A method comprising: executing, at a host, a host application associated with a client application executing at the UE to receive user data from the UE.

[0391] 19. The method of the previous embodiment, further comprising: transmitting, at the host, input data to a client application executing on the UE, the input data being provided by the executing host application; A method wherein the user data is provided by a client application in response to input data from a host application.

[0392] 20. A host configured to operate in a communication system providing over-the-top (OTT) services, comprising: processing circuitry configured to utilize the user data; a network interface configured to receive a transmission of user data to a cellular network for transmission to a user equipment (UE); The UE comprises a communication interface and processing circuitry, and the communication interface and processing circuitry of the UE are configured to perform one or more of the actions described herein as being performed by the wireless device 130, a host.

[0393] 21. The host of the previous embodiment, The cellular network further includes a network node configured to communicate with the UE for transmitting user data from the UE to the host.

[0394] 22. The host of the previous two embodiments, the host processing circuitry is configured to execute a host application to provide user data; The host application is configured to interact with a client application running on the UE, the client application being associated with the host application.

[0395] 23. A method performed in a host configured to operate in a communication system further including a network node and a user equipment (UE), comprising: A method comprising receiving, at a host, user data transmitted by a UE to the host via a network node, wherein the UE performs one or more of the actions described herein as being performed by a wireless device 130.

[0396] 24. The method of the previous embodiment, further comprising: A method comprising: executing, at a host, a host application associated with a client application executing at the UE to receive user data from the UE.

[0397] 25. The method of the previous embodiment, further comprising: transmitting, at the host, input data to a client application executing on the UE, the input data being provided by the executing host application; A method wherein the user data is provided by a client application in response to input data from a host application.

[0398] reference 1. RP-211586, 3GPP® Work Item Description: Further MIMO Enhancements for NR, Samsung, 3GPP® TSG RAN Meeting #92e, e-Meeting, June 14-18, 2021 2. RP-213565, 3GPP® Work Item Description: Further Enhancements to NR Mobility, MediaTek, 3GPP® TSG RAN Meeting #94e, e-Meeting, December 6-17, 2021

[0399] Abbreviation Description CE Control Elements CHO Conditional Handover DCI Downlink Control Information HOF Handover Failure IE Information Elements LTE Long Term Evolution MAC Media Access Control MHI Mobility History Report MCG Master Cell Group MN Master Node NR New Radio PCI Physical Cell Identifier RAN Radio Access Network RRC Radio Resource Control RLF Radio Link Failure SCG Secondary Cell Group SN Secondary Node UE User Equipment gNB NR base station CU Central Unit DU Distributed Unit

Claims

1. 1. A method performed by a wireless device (130) for processing re-establishment information after a failure, the wireless device (130) operating in a wireless communication network (100), the method comprising: - in response to a declared failure, storing (304) one or more indications indicative of the failure, wherein the one or more indications include at least a first indication indicating whether a first cell (123) selected by the wireless device (130) for a re-establishment procedure triggered by the failure was a candidate cell in an inter-cell mobility configuration received in a previous indication to perform an L1 / L2 mobility procedure.

2. 10. The method of claim 1, - the failure is a mobility procedure; - the failure is one of a radio link failure and a handover failure; - the mobility procedure is L1 / L2 inter-cell mobility; - the one or more indications are sent in a report; and - the one or more indications are sent in a UEInformationResponse message; and - the inter-cell mobility configuration is an L1 / L2 inter-cell mobility configuration; and The method is at least one of:

3. 3. The method of claim 1 or 2, The one or more indications may further comprise: a second indication of one or more candidate cells (125) configured in said inter-cell mobility configuration; a third indication indicating the elapsed time between a first time of receipt of the inter-cell mobility configuration and a second time at which the failure was declared; - the third indication further indicating a third elapsed time between a fourth time of reception of a last inter-cell mobility configuration including the first cell (123) selected for the re-establishment procedure as a candidate cell and the second time the failure was declared; a fourth indication of at least one of a) the first position information at the fourth time, and b) the second position information at the second time; The method includes at least one of:

4. 4. The method of claim 3, the first indication is indicated by a one-bit flag; the first indication is indicated by a least-L1L2Candidate information element (IE); - the first indication further indicates additional L1 / L2 mobility related measurements; - the first indication including the additional L1 / L2 mobility related measurements is indicated in a lowest-L1L2meas IE; the first indication including the additional L1 / L2 mobility related measurements is denoted by reConnect-L1L2meas; the second indication is indicated by a candidate-L1L2Mobility IE; and the second indication is indicated by a candidate-L1L2 flag; - the second indication further indicates the additional L1 / L2 mobility related measurements; the second indication including the additional L1 / L2 mobility related measurements is indicated in a candidate-L1L2meas IE; the third indication is indicated in a separate IE; and the fourth indication is indicated by a further IE; and The method is at least one of:

5. 5. The method of any one of claims 1 to 4, further comprising: - receiving (301) said previous indication from the first network node (111); - performing (302) a L1 / L2 inter-cell mobility procedure from said first network node (111) to a second network node (112) operating in said wireless communication network (100) in response to said previous indication received; - declaring (303) said fault; - performing (305) said re-establishment or re-connection procedure to a third network node (113) operating in said wireless communication network (100); - transmitting (306) any of said one or more stored indications to a network node (113) operating in said wireless communication network (100); - receiving (307) from said network node (113) an updated inter-cell mobility procedure configuration comprising one or more adapted procedures based on said one or more transmitted indications; The method includes one or more of:

6. 6. The method of claim 5, - a) the wireless device (130) performs the re-establishment procedure after going into idle mode or after a radio link failure; - b) said re-establishment procedure fails and said wireless device (130) reconnects to said network node (113); The method is one of the above.

7. 7. The method of claim 6, The re-establishment procedure fails, the wireless device (130) reconnects to the network node (113), and the preservation (304) further comprises: a fifth indication indicating whether the second cell (124) selected by the wireless device (130) for a reconnection procedure triggered by the failed re-establishment procedure was a candidate cell in the inter-cell mobility configuration received in the previous indication; and a sixth indication indicating the elapsed time between a first time of receiving the inter-cell mobility configuration and a fifth time of the reconnection by selection of the second cell (124); storing at least one of:

8. 8. The method of claim 7, The method, wherein the fifth indication is indicated by a reConnect-L1L2Candidate IE.

9. 1. A method performed by a network node (113) operating in a wireless communication network (100) for processing re-establishment information after a failure by a wireless device (130), comprising: - A method comprising receiving (402) from the wireless device (130) one or more indications indicating the failure, wherein the one or more indications include at least a first indication indicating whether a first cell (123) selected by the wireless device (130) for a re-establishment procedure triggered by the failure was a candidate cell in an inter-cell mobility configuration received by the wireless device (130) in a previous indication to perform an L1 / L2 mobility procedure.

10. 10. The method of claim 9, - the failure is a mobility procedure; - the failure is one of a radio link failure and a handover failure; - the mobility procedure is L1 / L2 inter-cell mobility; - the one or more indications are received in a report; and - the one or more indications are received in a UEInformationResponse message; and - the inter-cell mobility configuration is an L1 / L2 inter-cell mobility configuration; and The method is at least one of:

11. 11. The method of claim 9 or 10, The one or more indications may further comprise: a second indication of one or more candidate cells (125) configured in said inter-cell mobility configuration; a third indication indicating the elapsed time between a first time of receipt of the inter-cell mobility configuration and a second time at which the failure was declared; - the third indication further indicating a third elapsed time between a fourth time of reception of a last inter-cell mobility configuration including the first cell (123) selected for the re-establishment procedure as a candidate cell and the second time the failure was declared; a fourth indication of at least one of a) the first position information at the fourth time, and b) the second position information at the second time; The method includes at least one of:

12. 12. The method of claim 11, the first indication is indicated by a one-bit flag; the first indication is indicated by a least-L1L2Candidate information element (IE); - the first indication further indicates additional L1 / L2 mobility related measurements; - the first indication including the additional L1 / L2 mobility related measurements is indicated in a lowest-L1L2meas IE; the first indication including the additional L1 / L2 mobility related measurements is denoted by reConnect-L1L2meas; the second indication is indicated by a candidate-L1L2Mobility IE; and the second indication is indicated by a candidate-L1L2 flag; - the second indication further indicates the additional L1 / L2 mobility related measurements; the second indication including the additional L1 / L2 mobility related measurements is indicated in a candidate-L1L2meas IE; the third indication is indicated in a separate IE; and the fourth indication is indicated by a further IE; and The method is at least one of:

13. 13. The method of any one of claims 9 to 12, further comprising: - performing (401) the re-establishment or re-connection procedure with the wireless device (130), wherein the one or more indications are received after performing the re-establishment procedure.

14. 14. The method of claim 13, - a) the re-establishment procedure is performed after the wireless device (130) has transitioned to an idle mode after the mobility procedure that failed; - b) said re-establishment procedure fails and said wireless device (130) reconnects to said network node (113); The method is one of the above.

15. 15. The method of claim 14, wherein the re-establishment procedure fails and the wireless device (130) reconnects to the network node (113), the method further comprising: - after reconnection, from said wireless device (130): a fifth indication indicating whether a second cell (124) selected by the wireless device (130) for a reconnection procedure triggered by the failed re-establishment procedure was a candidate cell in the inter-cell mobility configuration received in the previous indication; a sixth indication indicating an elapsed time between a first time of receiving the inter-cell mobility configuration and a fifth time of reconnection upon selection of the second cell (124); receiving (406) at least one of:

16. 16. The method of claim 15, The method, wherein the fifth indication is indicated by a reConnect-L1L2Candidate IE.

17. 17. The method of any one of claims 9 to 16, comprising: The method further comprises: - based on said one or more received indications, i. whether the first cell (123) selected by the wireless device (130) for the re-establishment procedure was a candidate cell in the inter-cell mobility configuration; ii. Measurement results of one or more candidate cells (125) configured in the inter-cell mobility configuration; iii. The duration that the wireless device (130) was configured in the inter-cell mobility configuration before the failure occurred; determining (403) one or more characteristics of the inter-cell mobility configuration selected from: - initiating (404) the adaptation of one or more procedures of said inter-cell mobility configuration based on the result of said determination; - transmitting (405) an updated inter-cell mobility configuration based on said adaptation, comprising said adapted one or more procedures; The method includes at least one of:

18. 18. The method of claim 17, - said adapting comprising adding said first cell (123) to a list of candidate cells of said inter-cell mobility configuration, provided that said first cell (123) was not a candidate cell in said inter-cell mobility configuration; - said adapting comprising triggering a mobility procedure to a first candidate cell (126) on condition that said measurement results indicate that said first candidate cell (126) has better measurement results; - the adapting includes removing the first candidate cell (126) from the one or more candidate cells (125) on condition that the measurement results indicate that the first candidate cell (126) has a poor measurement result; - the adapting includes adding the first neighboring cell (127) to the list of candidate cells of the inter-cell mobility configuration, on condition that the measurement result indicates that the first neighboring cell (127) has a good measurement result and the first neighboring cell (127) is not a candidate cell in the inter-cell mobility configuration; The method is at least one of:

19. 1. A wireless device (130) for processing re-establishment information after a failure, the wireless device (130) configured to operate in a wireless communication network (100), the wireless device (130) further comprising: - A wireless device configured to, in response to a declared failure, store one or more indications configured to indicate the failure, wherein the one or more indications include at least a first indication configured to indicate whether a first cell (123) configured to be selected by the wireless device (130) for a re-establishment procedure configured to be triggered by the failure was a candidate cell in an inter-cell mobility configuration configured to be received in a previous indication to perform an L1 / L2 mobility procedure.

20. 20. The wireless device (130) of claim 19, - the failure is configured to be a mobility procedure; - configured such that the failure is one of a radio link failure and a handover failure; - the mobility procedure is configured to be L1 / L2 inter-cell mobility; - said one or more indications are configured to be sent in a report; - the one or more indications are configured to be sent in a UEInformationResponse message; - the inter-cell mobility configuration is configured to be an L1 / L2 inter-cell mobility configuration; The wireless device is at least one of:

21. A wireless device (130) according to claim 19 or 20, comprising: The one or more indications may further comprise: a second indication configured to indicate one or more candidate cells (125) configured in said inter-cell mobility configuration; a third indication configured to indicate the elapsed time between a first time of receipt of the inter-cell mobility configuration and a second time at which the failure is declared; the third indication further configured to indicate a third elapsed time between a fourth time of reception of a last inter-cell mobility configuration including the first cell (123) configured to be selected for the re-establishment procedure as a candidate cell and the second time the failure was declared; a fourth indication configured to indicate at least one of a) the first position information at the fourth time, and b) the second position information at the second time; A wireless device configured to include at least one of:

22. 22. The wireless device (130) of claim 21, - the first indication is configured to be indicated by a one-bit flag; the first indication is configured as indicated by a least-L1L2Candidate information element (IE); the first indication is further configured to indicate additional L1 / L2 mobility related measurements; the first indication including the additional L1 / L2 mobility related measurements is configured as indicated in a least-L1L2meas IE; the first indication including the additional L1 / L2 mobility related measurements is configured as denoted reConnect-L1L2meas; the second indication is configured as indicated in a candidates-L1L2Mobility IE; the second indication is configured as indicated by a candidate-L1L2 flag; the second indication is further configured to indicate the additional L1 / L2 mobility related measurements; the second indication including the additional L1 / L2 mobility related measurements is configured as indicated in a candidate-L1L2meas IE; the third indication is configured to be indicated by another IE; the fourth indication is configured to be indicated by a further information element; The wireless device is at least one of:

23. A wireless device (130) according to any one of claims 19 to 22, further comprising: - receiving said previous indication from the first network node (111); - performing an L1 / L2 inter-cell mobility procedure from said first network node (111) to a second network node (112) configured to operate in said wireless communication network (100) in response to said previous indication that said first network node (111) is configured to receive; - declaring said disability; - performing said re-establishment or re-connection procedure to a third network node (113) configured to operate in said wireless communication network (100); - transmitting any of said one or more indications configured to be stored to a network node (113) configured to operate in said wireless communication network (100); receiving, from said network node (113), an updated inter-cell mobility procedure configuration based on said one or more indications configured to be transmitted, said updated inter-cell mobility procedure configuration being configured to include one or more adapted procedures; A wireless device configured to perform one or more of the following:

24. 24. A wireless device (130) according to claim 23, comprising: - a) said wireless device (130) is configured to perform said re-establishment procedure after entering an idle mode or after a radio link failure; - b) said wireless device (130) is configured to reconnect to said network node (113) after said re-establishment procedure has failed; A wireless device is one of the above.

25. 25. A wireless device (130) according to claim 24, comprising: The wireless device (130) is configured to reconnect to the network node (113) after the re-establishment procedure fails, and the storing further comprises: a fifth indication configured to indicate whether a second cell (124) configured to be selected by the wireless device (130) for a reconnection procedure configured to be triggered by the failed re-establishment procedure was a candidate cell in the inter-cell mobility configuration configured to be received in the previous indication; a sixth indication configured to indicate the elapsed time between a first time of receiving the inter-cell mobility configuration and a fifth time of the reconnection by selection of the second cell (124); The wireless device is configured to store at least one of:

26. 26. A wireless device (130) according to claim 25, comprising: The fifth indication is configured as indicated by a reConnect-L1L2Candidate IE.

27. A network node (113) configured to operate in a wireless communication network (100) for processing re-establishment information after a failure by a wireless device (130), comprising: The network node (113) further comprises: - A network node configured to receive from the wireless device (130) one or more indications configured to indicate the failure, the one or more indications including at least a first indication configured to indicate whether a first cell (123) configured to be selected by the wireless device (130) for a re-establishment procedure configured to be triggered by the failure was a candidate cell in an inter-cell mobility configuration configured to be received by the wireless device (130) in a previous indication to perform an L1 / L2 mobility procedure.

28. A network node (113) according to claim 27, comprising: - the failure is configured to be a mobility procedure; - configured such that the failure is one of a radio link failure and a handover failure; - the mobility procedure is configured to be L1 / L2 inter-cell mobility; - said one or more indications are configured to be received in a report; - the one or more indications are configured to be received in a UEInformationResponse message; - the inter-cell mobility configuration is configured to be an L1 / L2 inter-cell mobility configuration; a network node that is at least one of:

29. A network node (113) according to claim 27 or 28, comprising: The one or more indications may further comprise: a second indication configured to indicate one or more candidate cells (125) configured in said inter-cell mobility configuration; a third indication configured to indicate the elapsed time between a first time of receipt of the inter-cell mobility configuration and a second time at which the failure is declared; the third indication further configured to indicate a third elapsed time between a fourth time of reception of a last inter-cell mobility configuration configured to include the first cell (123) configured to be selected for the re-establishment procedure as a candidate cell and the second time the failure was declared; a fourth indication configured to indicate at least one of a) the first position information at the fourth time, and b) the second position information at the second time; A network node configured to include at least one of:

30. A network node (113) according to claim 29, comprising: - the first indication is configured to be indicated by a one-bit flag; the first indication is configured as indicated by a least-L1L2Candidate information element (IE); the first indication is further configured to indicate additional L1 / L2 mobility related measurements; the first indication including the additional L1 / L2 mobility related measurements is configured as indicated in a least-L1L2meas IE; the first indication including the additional L1 / L2 mobility related measurements is configured as denoted reConnect-L1L2meas; the second indication is configured as indicated in a candidates-L1L2Mobility IE; the second indication is configured as indicated by a candidate-L1L2 flag; the second indication is further configured to indicate the additional L1 / L2 mobility related measurements; the second indication including the additional L1 / L2 mobility related measurements is configured as indicated in a candidate-L1L2meas IE; the third indication is configured to be indicated by another IE; the fourth indication is configured to be indicated by a further information element; a network node that is at least one of:

31. A network node (113) according to any one of claims 27 to 30, further comprising: - A network node configured to perform the re-establishment or re-connection procedure with the wireless device (130), and wherein the one or more indications are received after performing the re-establishment procedure.

32. A network node (113) according to claim 31, comprising: a) the re-establishment procedure is configured to be performed after the wireless device (130) is configured to transition to an idle mode after the mobility procedure fails; - b) said wireless device (130) is configured to reconnect to said network node (113) after said re-establishment procedure has failed; A network node is one of the nodes.

33. A network node (113) according to claim 32, comprising: The wireless device (130) is configured to reconnect to the network node (113) after the re-establishment procedure fails, the network node (113) further comprising: - after reconnection, from said wireless device (130): a fifth indication configured to indicate whether a second cell (124) configured to be selected by the wireless device (130) for a reconnection procedure configured to be triggered by the failed re-establishment procedure was a candidate cell in the inter-cell mobility configuration configured to be received in the previous indication; a sixth indication configured to indicate an elapsed time between a first time of receiving the inter-cell mobility configuration and a fifth time of the reconnection upon selection of the second cell (124); a network node configured to receive at least one of:

34. A network node (113) according to claim 33, comprising: The fifth indication is configured as indicated by a reConnect-L1L2Candidate IE.

35. A network node (113) according to any one of claims 29 to 34, comprising: The network node (113) further comprises: - based on the one or more indications the device is configured to receive, i. whether the first cell (123) configured to be selected by the wireless device (130) for the re-establishment procedure was a candidate cell in the inter-cell mobility configuration; ii. Measurement results of one or more candidate cells (125) configured in the inter-cell mobility configuration; iii. The duration that the wireless device (130) was configured in the inter-cell mobility configuration before the failure occurred; determining one or more characteristics of the inter-cell mobility configuration, configured to be selected from: - initiating adaptation of one or more procedures of said inter-cell mobility configuration based on the result of said determination; - transmitting an updated inter-cell mobility configuration based on said adaptation, the updated inter-cell mobility configuration being configured to include said one or more procedures adapted to be adapted; a network node configured to perform at least one of the following:

36. 36. The method of claim 35, - the adapting is configured to include adding the first cell (123) to a list of candidate cells of the inter-cell mobility configuration, provided that the first cell (123) was not a candidate cell in the inter-cell mobility configuration; - the adapting is configured to include triggering a mobility procedure to a first candidate cell (126) on condition that the measurement results indicate that the first candidate cell (126) has better measurement results; - adapted to include removing the first candidate cell (126) from the one or more candidate cells (125) on condition that the measurement results indicate that the first candidate cell (126) has a poor measurement result; - the adapting is configured to include adding the first neighboring cell (127) to the list of candidate cells of the inter-cell mobility configuration, provided that the measurement result indicates that the first neighboring cell (127) has a good measurement result and the first neighboring cell (127) is not configured as a candidate cell in the inter-cell mobility configuration; The method is at least one of:

Images