Wireless devices, network nodes, and methods performed by them to process re-establishment information after a failure.

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 generally relates to a wireless device and a method performed by the wireless device for processing re-establishment information after a failure. The present disclosure further generally relates to a network node and a method performed by the network node for processing re-establishment information after a failure.

Background Art

[0002] A wireless device in a wireless communication network may be, for example, user equipment (UE), a station (STA), a mobile terminal, a wireless terminal, a terminal and / or a mobile station (MS). The wireless device can perform wireless communication in a cellular communication network or a wireless communication network, which is sometimes also referred to as a cellular wireless system, a cellular system, or a cellular network. Communication may, for example, be performed between two wireless devices, between a wireless device and a fixed telephone, and / or between a wireless device and a server via a radio access network (RAN) comprised in the wireless communication network and possibly via one or more core networks. To name a few more examples, the wireless device may further be referred to as a mobile phone, a cellular phone, a laptop or tablet with wireless functionality, etc. A wireless device in the present context may be, for example, a portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile device, which can 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 can be divided into cell areas, each cell area being serviced by network nodes, which may be access nodes such as radio network nodes, radio nodes, or base stations (RBS), which may also be referred to as gNBs, evolved node B ("eNB"), "enode B", "node B", "B node", transmit point (TP), or base transceiver station (BTS), depending on the technology and terminology used. Base stations may be of various classes, such as wide-area base stations, medium-range base stations, local area base stations, home base stations, pico base stations, etc., based on their transmit power and the resulting cell size. Each cell is a geographical area whose radio coverage is provided by a base station or radio node located at a base station site or radio node site. A single base station at a base station site can service one or more cells. Furthermore, each base station can support one or more communication technologies. Base stations communicate with terminals within their range via an air interface operating on radio frequencies. The wireless communication network may also be a non-cellular system, which includes network nodes that can provide services to receiving nodes such as wireless devices using service beams. In the Third Generation Partnership Project (3GPP®) Long-Term Evolution (LTE), base stations, which may also be referred to as e-node B or eNB, may be directly connected to one or more core networks. In the context of this disclosure, the term downlink (DL) may be used for the transmission path from the base station to the wireless device. The term uplink (UL) may be used for the transmission path in the opposite direction, i.e., from the wireless device to the base station.

[0004] The standardization body 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, abbreviated as NG-CN, NGC, 5G CN, or 5G core (5GC). NG can be understood as referring to the interface / reference point between the 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 function enhancements for 3GPP® Rel-18 As part of 3GPP® Release 18, a new work item known as further NR mobility enhancements is about to be initiated. This work item aims, among other things, to 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 to reduce mobility delay. This may include the configuration and maintenance of multiple candidate cells so that the configuration of candidate cells can be rapidly applied [RAN2, RAN3]. Mechanisms and procedures for L1 / L2 based inter-cell mobility to reduce mobility delay may also include dynamic switching mechanisms between candidate serving cells, including special cells (SpCell) and secondary cells (Scell), for potentially applicable scenarios based on L1 / L2 signaling [RAN2, RAN1]. The mechanisms and procedures for L1 / L2-based inter-cell mobility to reduce mobility delay may further include L1 function 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 necessary, including the possibility of further clarifying the interaction between this point and the previous point. The mechanisms and procedures for L1 / L2-based inter-cell mobility to reduce mobility delay may also include timing advance management [RAN1, RAN2]. The mechanisms and procedures for L1 / L2-based inter-cell mobility to reduce mobility delay may further include central unit (CU)-distributed unit (DU) interface signaling to support L1 / L2 mobility, if necessary [RAN3]. It was noted that frequency 2 (FR2) specific function enhancements, if any, are not ruled out.Furthermore, it was noted that the L1 / L2-based inter-cell mobility procedure could potentially be applied to the following scenarios: standalone, carrier aggregation (CA), and NR dual connectivity (DC) cases involving changes in serving cells within a single cell group (CG), intra-DU cases, intra-CU inter-DU cases, and applicable to standalone and CA: no new RAN interface is expected, both within and between frequencies, both frequency 1 (FR1) and FR2, and source and target cells can be synchronous or asynchronous.

[0006] According to the work item description [1], as part of the justification, it is written: When a UE moves from the coverage area of ​​one cell to another, it may be necessary to perform a serving cell change at some point. Currently, serving cell changes can be triggered by L3 measurements and can be 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 of SCells where applicable. In all cases, a full L2 and L1 reset may occur, resulting in longer delays, greater overhead, and longer downtime than beam switch mobility. The goal of the L1 / L2 mobility enhancement can be understood as enabling serving cell changes via L1 / L2 signaling to reduce delays, overhead, and downtime.

[0007] Self-organizing networks (SON) in 3GPP® Self-organizing networks (SONs) can be understood as automated technologies designed to make planning, configuring, managing, optimizing, and remediating mobile radio access networks simpler and faster. The functions and operations of SONs ​​are defined and specified in generally accepted mobile industry recommendations created by organizations such as the Third Generation Partnership Project (3GPP®) and Next Generation Mobile Networks (NGMN).

[0008] In 3GPP®, processes within a SON area can be classified into self-configuration processes and self-optimization processes. Self-configuration processes can be understood as processes that can be configured by an automated installation procedure for a newly deployed node to acquire the basic configuration necessary for system operation. This process can function in the pre-operational state. The pre-operational state can be understood as the state from when the eNB is powered on and has a backbone connection until the radio frequency (RF) transmitter can be turned on.

[0009] Figure 1 is a schematic signaling diagram showing the branching of self-configuration / self-optimization functions, according to Figure 22.1-1 of 3GPP® TS36.300, v.17.1.0.

[0010] As shown in Figure 1, functions processed in the pre-operation state, such as basic settings and initial wireless configuration, can be covered by the self-configuration process. As shown in Figure 1, basic settings (A) functions may include a-1) configuration of Internet Protocol (IP) addresses and detection of Operation, Management and Maintenance (OAM), a-2) authentication of eNB / network (NW), a-3) association with gateway (GW), a-4) download of eNB software (and operating parameters), etc. Initial wireless configuration (B) functions may include b-1) adjacent list configuration, b-2) configuration of coverage / capacity-related parameters, etc.

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

[0012] As shown in Figure 1, functions processed in operational states such as optimization / adaptation can be covered by a self-optimization process. As shown in Figure 1, the optimization / adaptation (C) function may include c-1) adjacency 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 adjacency (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® TS36.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 and automatic adjacency relationships (ANR) in Rel-15, as described in Section 15 of 3GPP® TS38.300, v.17.1.0. In NR Rel-16, more SON features are specified for NR UE, including self-optimization features such as mobility robustness optimization (MRO).

[0015] Mobility Robustness Optimization (MRO) in 3GPP® Seamless handover can be understood as a key feature of 3GPP® technology. When handover is successful, the UE can move within the coverage area of ​​various cells with minimal disruption to data transmission. However, there may be scenarios in which the network fails to hand over the UE to the "correct" adjacent cell in time, in which case 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, which may ensure that the UE can recover as quickly as possible and become reachable again. RLF may only be declared by the UE if it perceives that there may be no reliable communication channel, i.e., an available radio link, between the UE and the network, and can therefore be understood as a cause of a degraded user experience. Furthermore, re-establishing the connection may require signaling with a newly selected cell, such as random access procedures, RRC re-establishment requests, RRC re-establishment, RRC re-establishment completion, RRC reconfiguration, and RRC reconfiguration completion, and some delay may occur before the UE can exchange data with the network again.

[0017] According to specifications, for example, 3GPP® TS36.331, v.17.1.0, possible causes of wireless link failure include: a) expiration of the wireless link monitoring timer T310; b) expiration of the measurement report timer T312, i.e., if a measurement report was sent while T310 was running but no handover command was received from the network within the timer period; c) reaching the maximum number of wireless link control (RLC) retransmissions; and d) receiving an indication of a random access problem from a media access control (MAC) entity.

[0018] Since RLF can lead to re-establishment and degrade performance and user experience, it can be understood that it is in the network's best interest to understand the reasons for RLF and attempt to optimize mobility-related parameters such as trigger conditions for measurement reports to avoid future RLFs. Prior to the standardization of MRO-related report processing in the network, only the UE was aware of some information related to the state of radio quality at the time of RLF occurrence and the actual reason for declaring the RLF. It can be understood that in order for the network to identify the reason for RLF, it needs more information from both the UE and neighboring base stations.

[0019] As part of the LTE MRO approach, an RLF reporting procedure was introduced into the RRC specification for RAN2 work in Rel-9. This affected the RRC specification (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 report it later to, for example, the target cell to which the UE was able to successfully connect after re-establishment. This also affected the g-node-B interface, i.e., the X2AP specification, e.g., 3GPP® TS36.423, v.17.1.0, as an e-node B that receives an RLF report may forward it to any other potentially failed e-node B.

[0020] The RLF reports generated by the UE have been further expanded in subsequent releases. Measurements included in measurement reports based on the latest LTE RRC specification [1] may include: a) measurements of the last serving cell, e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), etc.; b) measurements of adjacent cells at different frequencies for different RATs, e.g., Evolutionary Universal Terrestrial Radio Access (EUTRA), Universal Terrestrial Radio Access (UTRA), Global System Mobile Communications Enhanced Data Rate for GSM Evolution Radio Access Networks (GERAN), Code Division Multiple Access 2000 (CDMA2000); c) reception associated with a Wireless Local Area Network (WLAN) access point (Aps). d) Measured values ​​of the Signal Strength Indicator (RSSI), e) Measured values ​​such as RSSI associated with the Bluetooth beacon, f) Location information including location coordinates and velocity, if available, g) Global unique identifier of the last serving cell, if available, otherwise the physical cell identifier (PCI) and carrier frequency of the last serving cell, g) PCell tracking area code, h) Time elapsed since the last reception of the "Handover Command" message, i) Cell Radio Network Temporary Identifier (C-RNTI) used by the previous serving cell, j) Whether or not the UE consists of a data radio bearer (DRB) with a Quality of Service Class Identifier (QCI) value of 1.

[0021] After an RLF is declared, an RLF report is logged and may be included in a VarRLF report. If the UE can select a cell and successfully re-establish contact, the UE may include an indication in the RRC re-establishment complete message that it has an available RLF report, making the target cell aware of its availability. Then, upon receiving a UEInformationRequest message containing the flag "rlf-ReportReq-r9", the UE may be asked to include the RLF report, for example stored in the UE variable VarRLF report, in a UEInformationResponse message and send it to the network, as described above.

[0022] Based on the RLF report from the UE and knowledge of which cell the UE re-established itself in, the original source cell may be able to infer whether the RLF was caused by a coverage hole or by 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 classes of handover to too early, too late, or wrong cell. These handover failure classes are briefly described below. The first handover failure class may concern 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 particular target cell, and the UE re-establishes itself in this target cell after the RLF. An example of a corrective action from the original serving cell might be to reduce the cell individual offset (CIO) to the target cell, thereby initiating the handover procedure to that target cell slightly earlier, and the target cell might be able to control when the information element (IE) sends event trigger metric reports that could lead to a handover decision.

[0023] The second handover failure class may concern whether the handover failure was caused by a “premature handover / mobility” case. A handover failure can be classified as “premature handover / mobility” if the original serving cell was able to successfully send the handover command to the UE involved in the handover, but the UE failed to perform random access to this target cell, or if the UE subsequently declared an RLF on the target cell. An example of corrective action from the original serving cell might be to slightly delay the initiation of the handover procedure to the target cell by increasing the cell individual offset (CIO) to the target cell, and the target cell may be able to control when the IE sends event trigger metric reports that lead to the handover decision.

[0024] The third handover failure class may concern whether the handover failure was caused by a “handover / mobility to the wrong cell” case. The original serving cell may have intended to perform a handover of this UE to a specific target cell, but the handover failure can be classified as “handover / mobility to the wrong cell” if the UE declares a failure, or declares a failure immediately after successfully completing the handover, and is able to re-establish in the third cell. Corrective actions from the original serving cell may include slightly delaying the initiation of measurement reporting procedures that could lead to a handover to the target cell by reducing the CIO to the target cell, or slightly increasing the CIO to the re-established cell so that the UE starts the handover to the re-established cell a little earlier.

[0025] Existing methods for handling handover failures can result in wasted resources, such as unnecessary signaling and / or unnecessary delays. [Overview of the Initiative] [Problems that the invention aims to solve]

[0026] As part of the development of the present embodiment, one or more problems related to existing technologies are first identified and discussed.

[0027] Regarding L1 / L2-based inter-cell mobility described in the Work Item Description WID[1] of 3GPP (registered trademark), the overall procedure and signaling remain unsolved. The goal of L1 / L2-based inter-cell mobility is to reduce delay, overhead and interruption time. The decision on L1 / L2 inter-cell mobility may be made by the source DU, compared with the conventional L3 mobility decision made by the source CU-Control Plane (CP). It can be expected that L1 / L2 inter-cell mobility candidates are configured in a UE-specific manner. A UE may have a limit on the number of inter-cell mobility candidates that can be stored in its memory, for example, a limit of 8 L1 / L2 inter-cell mobility candidates. Therefore, different UEs within the same DU may be configured with different candidate L1 / L2 inter-cell mobility candidates according to the UE's position, mobility characteristics and other parameters.

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

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

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

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

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

[0033] According to a third aspect of this embodiment, this objective is achieved by a wireless device configured to perform the above method. The wireless device can be understood to be 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 one or more indicators configured to indicate a failure in response to a declared failure. The one or more indicators are configured to include at least a first indicator. The first indicator 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 by a previous indicator. The previous indicator is for performing an L1 / L2 mobility procedure.

[0034] According to a fourth aspect of this embodiment, this objective is achieved by a network node configured to perform the above method. The network node can 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 that are configured to indicate a failure. 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. The inter-cell mobility configuration is configured to be received by the wireless device in a previous indication for performing 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, based on the one or more indications stored in this embodiment, whether a cell that the wireless device may later re-establish, for example, a first cell, was part of an L1 / L2 inter-cell mobility configuration. The wireless device may thus enable the network node to know whether the problem lies in triggering L1 / L2 inter-cell mobility at the DU, in selecting L1 / L2 inter-cell mobility candidates, or in an L3 mobility configuration. This may enable the network node to adjust the L1 / L2 inter-cell mobility configuration by analyzing one or more indications. This may optimize mobility procedures, reduce latency, minimize communication interruptions, and allow for more efficient use of wireless communication network resources.

[0036] An example of this embodiment will be described in more detail below with reference to the accompanying drawings. [Brief explanation of the drawing]

[0037] [Figure 1] A schematic signaling diagram showing the branching of self-configuration / self-optimization functions, according to Figure 22.1-1 of 3GPP(registered trademark) TS36.300, v.17.1.0. [Figure 2] A schematic diagram showing an example of a wireless communication network according to this embodiment. [Figure 3] A flowchart illustrating the method in the wireless device according to this embodiment. [Figure 4] A flowchart illustrating the method in a network node, referred to herein as the "third network node," according to this embodiment. [Figure 5] A schematic block diagram showing two embodiments of the wireless device in panel a) and panel b) according to this embodiment. [Figure 6]A schematic block diagram showing two embodiments of the network nodes in panel a) and panel b) according to this embodiment. [Figure 7] A flowchart illustrating a method in a wireless device according to an example related to this embodiment. [Figure 8] A flowchart illustrating a method in a network node, referred to herein as the "third network node," according to an example related to this embodiment. [Figure 9] A diagram showing examples of communication systems 900 according to several embodiments. [Figure 10] A block diagram of host 1000, which may be an embodiment of host 916 in Figure 9, following the various perspectives described here. [Figure 11] A communication diagram of host 1102 communicating with UE 1106 via network node 1104 through a partial wireless connection according to several embodiments. [Modes for carrying out the invention]

[0038] This embodiment can generally be understood as relating to re-established cell type information based on L1 / L2 inter-cell mobility configurations. This embodiment can be understood as enabling an enhancement to reports, such as RLF reports, that include an indication of whether a cell on which a re-establishment procedure was performed was a candidate for L1 / L2 inter-cell mobility.

[0039] This embodiment may further enable the inclusion of all configured L1 / L2 inter-cell mobility candidates and their associated measurements as part of a report, for example, an RLF report.

[0040] Some of the embodiments considered herein are described more fully below with reference to the accompanying drawings illustrating examples. This section describes these embodiments in more detail by several exemplary embodiments. However, other embodiments are included within the scope of the subject matter disclosed herein. The disclosed subject matter should not be construed as being limited only to 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 how those components may be used in other exemplary embodiments will be obvious to those skilled in the art.

[0041] Figure 2 shows two non-limiting examples of a wireless network or wireless communication network 100, often also referred to as a wireless communication system, cellular wireless system, or cellular network, in panels a) and b), respectively, in which this embodiment may be implemented. The wireless communication network 100 may be a 5G system, a 5G network, or a next-generation system or network. In other examples, the wireless communication network 100 may further support other technologies such as Long-Term Evolution (LTE), e.g., 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 Assisted Access (LAA), Enhanced LAA (eLAA), Further Enhanced LAA (feLAA), and / or LTE operating in unlicensed bands such as MultiFire. In further examples, the wireless communication network 100 may further support other technologies such as, for example, broadband code division multiplexing access (WCDMA®), universal terrestrial radio access (UTRA) TDD, global systems for mobile communications (GSM) networks, GSM / enhanced data rate for GSM evolution (EDGE) radio access network (GERAN) networks, ultra-mobile broadband (UMB), EDGE networks, networks composed of any combination of radio access technologies (RATs) such as multi-standard radio (MSR) base stations, multi-RAT base stations, any third-generation partnership project (3GPP®) cellular networks, WiFi networks, worldwide interoperability for microwave access (WiMAX), machine-type communications (MTC), enhanced MTC (eMTC), the Internet of Things (IoT) and / or narrowband IoT (NB-IoT), or any cellular network or system. Therefore, while the terms 5G / NR and LTE may be used in this disclosure to illustrate embodiments, this should not be considered to limit the scope of embodiments herein to the aforementioned systems only.

[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 Figure 2. Any of the first network node 111, the second network node 112, and the third network node 113 may be a wireless network node; that is, a wireless base station, a transmission point such as a gNB or eNB, or another network node with similar functionality that can provide services to user equipment such as wireless devices or machine-type communication devices within the wireless communication network 100. In some examples shown in Figure 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 that can partially perform its functions in conjunction with a virtual node 114 in the cloud 115. The third network node 113 may also be referred to here simply as network node 113. This will be further explained in relation to action 306.

[0043] The wireless communication network 100 can cover a geographical area, and in some embodiments, this geographical area may be divided into cell areas, each cell area may be serviced by a wireless network node, but one wireless network node may service one or more cells. In the example in Figure 2, the first network node 111 may service the source cell 121, the second network node 112 may service the target cell 122, and the third network node 113 may service each of these cells. In the non-limiting example shown in Figure 2, each cell serviced by the third network node 113 is the first cell 123, which can be referred to here simply as cell 123. However, this is not necessarily the case. Each cell serviced by the third network node 113 may be a cell other than the first cell 123. The first network node 111, the second network node 112, and the third network node 113 may be different classes based on transmit power, and therefore cell size, such as macro base stations, home base stations, or pico base stations. 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 with a serving beam. Any of the first network node 111, the second network node 112, and the third network node 113 may also support one or more communication technologies, the names of which may differ depending on the technology and terminology used. Any of the wireless network nodes that may be included in the communication network 100 may be directly connected to one or more core networks, for example, one or more network nodes within one or more core networks.

[0044] In some examples, source cell 121, target cell 122, and 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, the first network node 111, the second network node 112, and the third network node 113 may be located in the same place, or they 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 Figure 2 as including three cells; however, this should be understood to be for illustrative purposes only and not limiting. The one or more candidate cells 125 may include fewer or additional cells. It should also be understood that the wireless communication network 100 may include other cells. For the sake of simplicity in the diagram, the network nodes that provide service to each of the shown cells are not shown. One or more of the shown cells may be serviced by the same network node.

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

[0049] The wireless device 130 may be configured to communicate with a third network node 113 via a first link 141, for example, a wireless link, within the wireless communication network 100. The third network node 113 may be configured to communicate with a virtual network node 114 via a second link 142, for example, a wireless link or a wired link, within the wireless communication network 100. Although not shown in Figure 2, the wireless device 130 may be configured to communicate with a first network node 111 via a third link, for example, a wireless link, within the wireless communication network 100, and the wireless device 130 may be configured to communicate with a second network node 112 via a fourth link, for example, a wireless link, within the wireless communication network 100. It can be understood that the wireless device 130 can communicate with the cells shown in Figure 2 via their respective links, for example, wireless links. This is not shown for the sake of simplification of the figure.

[0050] In general, all terms used herein should be interpreted according to their common meanings in the art relating to them, unless otherwise explicitly stated, and / or unless otherwise indicated by the context in which they are used. All references to an element, apparatus, component, means, step, etc., should be openly interpreted as references to at least one example of that element, apparatus, component, means, step, etc., unless otherwise explicitly stated. Steps of any method disclosed herein do not need to be performed in the exact order disclosed unless otherwise explicitly stated, and / or unless it is implicitly indicated 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 apply to any other embodiment, and vice versa. Other purposes, features, and advantages of the embodiments contained herein will become apparent from the following description.

[0051] In general, the use of “first,” “second,” “third,” “fourth,” and / or “fifth” in this specification is understood to be any way of indicating different elements or entities and, unless specifically stated in context, is not understood to give cumulative or chronological character to the noun it modifies.

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

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

[0054] Here, several embodiments will be further described using some non-limiting examples.

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

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

[0057] The obstacle may be within the mobility procedure.

[0058] A mobility procedure could be, for example, an L1 / L2 mobility procedure.

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

[0060] The failure may occur, for example, within the mobility procedure performed by the wireless device 130 from the first network node 111 to the second network node 112. A failure in the mobility procedure can be understood as a problem occurring in the processing of mobility, such as L1 / L2 mobility. The problem may be a wireless link failure or a handover failure. The mobility procedure may also be referred to here simply as mobility.

[0061] In some examples, the movement from the first network node 111 to the second network node 112 may mean that the mobility is between cells. However, as mentioned above, it should be noted that in some examples, the first network node 111 and the second network node 112 may be the same node.

[0062] A wireless link failure could be an example of a failure in the 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 on a wireless communication network, such as the wireless communication network 100. The method can be understood as being implemented on a computer.

[0063] In some specific 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 how those components may be used in other exemplary embodiments will be obvious to those skilled in the art. For the sake of brevity, not all possible combinations are described. A non-limiting example of a method performed by the wireless device 130 is shown in Figure 3. In Figure 3, optional actions of some embodiments may be indicated by dashed lines. In some embodiments, the actions may be performed in an order different from the order shown in Figure 3.

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

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

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

[0068] This can be understood to mean that while wireless device 130 may receive previous indications from the same network node from which it may ultimately send fault reports, that network node from which it may receive previous indications could be a different network node.

[0069] Action 302 In action 302, the wireless device 130 may perform an L1 / L2 inter-cell mobility procedure. This action 302 may, for example, be a response to a previously received indication.

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

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

[0072] As mentioned above, the fault may be a HOF (Hospital of Failure). 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. Saving / logging / recording in this action 304 may be in response to a declared failure. One or more indications indicate a failure; that is, one or more indications indicate a failed mobility procedure in the sense that something went wrong with the mobility procedure. A failed mobility procedure may be understood in some examples here as an L1 / L2 mobility procedure where something may have gone wrong, such as RLF and / or HOF.

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

[0075] The fact that it is triggered by a malfunctioning mobility procedure can be understood as being triggered by an L1 / L2 mobility procedure that may have gone wrong, such as RLF / HOF.

[0076] As mentioned above, previous indications may have been received from, for example, 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, one or more indications may further include at least one of the following options: According to the first option, one or more indications may further include a second indication. The second indication may indicate one or more candidate cells 125 configured in inter-cell mobility, for example, an L1 / L2 inter-cell mobility configuration.

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

[0079] In one example, the timer may be started when the last L1 / L2 inter-cell mobility configuration prior to the failure is received, and in another example, the timer may be started when the last L1 / L2 inter-cell mobility configuration including the cell selected as a candidate cell for the re-establishment procedure is received. According to a third option, one or more indications may further include the above third indications indicating a fourth time between the reception of the last inter-cell mobility configuration, e.g., an L1 / L2 inter-cell mobility configuration including the first cell 123 selected as a candidate cell for the re-establishment procedure, and a third elapsed time between the second time when a failure, e.g., a radio link failure, is declared.

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

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

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

[0083] According to the fourth option, the first indication, which includes additional L1 / L2 mobility-related measurements, may be shown in reest-L1L2meas IE. In some examples, explicit indications with additional L1 / L2 mobility-related measurements, e.g., reest-L1L2meas in the implementation example below, may be used.

[0084] According to option 5, the first indication, which includes additional L1 / L2 mobility-related measurements, may be shown in reConnect-L1L2meas.

[0085] According to option 6, the second indication can be shown with candidate-L1L2Mobility IE. According to option 7, the second indication can be shown with the candidate-L1L2flag flag.

[0086] According to option 8, the second indication may indicate additional L1 / L2 mobility-related measurements. This can be understood as meaning that the second indication, rather than the first indication, may indicate additional L1 / L2 mobility-related measurements. It can be understood as not meaning that the second indication may indicate the same additional L1 / L2 mobility-related measurements as the first indication.

[0087] According to option 9, a second indication, including additional L1 / L2 mobility-related measurements, may be shown in candidate-L1L2meas IE. According to option 10, a third indication may be shown in a different IE. According to option 11, a fourth indication may be shown in yet another IE.

[0088] By saving one or more indications in this action 304, the wireless device 130 may be able to transmit the saved one or more indications to the network node 113. This may enable the network, for example, the network node 113, to identify, based on the one or more indications saved in this embodiment, whether a cell that the wireless device 130 can later re-establish, for example, the first cell 123, was part of an L1 / L2 inter-cell mobility configuration. The wireless device 130 may thus enable the network, for example, the network node 113, to know whether the problem lies in triggering L1 / L2 inter-cell mobility at the DU, in selecting L1 / L2 inter-cell mobility candidates, or in an L3 mobility configuration. This may enable the network node 113 to adjust the L1 / L2 inter-cell mobility configuration based on an analysis of the one or more indications. This may enable the mobility procedure to be optimized, latency to be reduced, communication interruptions to be shortened, and the resources of the wireless communication network 100 to be used more efficiently.

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

[0090] The actions performed in this action 305 could, for example, be in response to a declared failure.

[0091] In several embodiments, one of the following may apply: According to the first option, the wireless device 130 may perform a re-establishment procedure after transitioning to idle mode or after a wireless link failure; that is, a failed mobility procedure. According to the 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, saving 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 a reconnection procedure triggered by a failed re-establishment procedure was a candidate cell in the inter-cell mobility configuration received in the previous indication. According to the first option, saving in action 304 may further include saving a sixth indication, which may indicate the 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 by selection of the second cell 124.

[0092] This embodiment allows the wireless device 130 to include an indication regarding whether the cell selected by the wireless device 130 to connect to after a reconnection failure, e.g., 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. In some embodiments, a fifth indication may be represented by reConnect-L1L2Candidate IE.

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

[0094] Network node 113 can be understood here as referring to a network node that can receive one or more indications from 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, network node 113 may be the third network node 113. If the re-establishment procedure fails, wireless device 130 will, in some examples, reconnect to the third network node 113, and in other examples, wireless device 130 will reconnect to a network node other than the third network node 113, in which case the transmission in action 306 may be made to a network node different from the third network node 113. This distinction may be indicated here as (third) network node 113.

[0095] The transmission in this action 306 may be performed, for example, via the first link 141.

[0096] The one or more indications sent may, for example, be a subset selected from one or more stored indications.

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

[0098] As described above, this embodiment may enable the wireless device 130 to include an indication, a first indication, regarding whether a re-established cell, for example, the first cell 123, was a candidate for L1 / L2 inter-cell mobility. Including reest-L1L2meas implicitly indicates to the network that the re-established cell was a candidate for L1 / L2 inter-cell mobility at the time the RLF was declared.

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

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

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

[0102] In some examples, some of the above information, such as a list of candidate L1 / L2 cells, measurement results of L1 / L2 cells, a flag indicating whether the measured adjacent cell was a candidate L1 / L2 cell, and the elapsed time since the L1 / L2 mobility configuration, may be included regardless of whether the wireless device 130 can successfully re-establish itself in a cell that was a candidate cell for the L1 / L2 mobility configuration, or in a cell that was not a candidate cell for L1 / L2 mobility, or whether the re-establishment attempt is unsuccessful or the device enters idle mode because a suitable cell cannot be found.

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

[0104] Some embodiments may relate to a reconnection cell, e.g., a second cell 124, in case re-establishment fails or if a suitable cell is not found during the execution of a monitoring timer, e.g., T311.

[0105] This embodiment may allow the wireless device 130 to include an indication regarding whether the cell selected by the wireless device 130 to connect to after a reconnection failure, for example, 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, for example, reConnect-L1L2Candidate.

[0106] In some cases, the wireless device 130 may transmit an explicit indication that includes additional L1 / L2 mobility-related measurements, such as reConnect-L1L2meas. Including reConnect-L1L2meas implicitly indicates to the network that the reconnected cell was a candidate for L1 / L2 inter-cell mobility at the time the RLF was declared.

[0107] In some examples, the wireless device 130 may include an indication of the configuration of L1 / L2 inter-cell mobility and the elapsed time since the reconnection point due to cell selection. In one example, this time may start when the last L1 / L2 inter-cell mobility configuration before the failure is received, and in another example, this timer may start when the last L1 / L2 inter-cell mobility configuration is received that includes the cell selected as a candidate cell for the reconnection procedure after the re-establishment failure. In some examples, some of the above information, such as a list of candidate L1 / L2 cells, the measurement results of the L1 / L2 cells, a flag indicating whether the measured adjacent cell was a candidate L1 / L2 cell, and the elapsed time since the L1 / L2 mobility configuration, may be included regardless of whether the wireless device 130 can perform a 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 L1 / L2 mobility.

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

[0109] Example Implementation An implementation example of the above example regarding re-established cells is shown below, with TS38.331 v17.0.0 as the baseline. Note that the following implementation example attempts to cover all of the above examples, and only some of this implementation example, i.e., those related to specific examples or combinations of examples, may be implemented in the final specification. In the provided implementation example, the wireless device 130 is the UE. The network node 113, for example, the third network node 113, can be understood as an example of a network.

[0110] ****************************** UEInformationResponse The UEInformationResponse message can be used by a UE to forward 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 the appropriate NR cell, the UE may be required to: 1>Ensure that valid and up-to-date essential system information is obtained, as stipulated in Section 5.2.2.2; 1> Stop timer T311; 1>When T390 is running: 2> Stop timer T390 for all access categories; 2>Execute the action specified in 5.3.14.4; 1>If the selected cell is one of the candidate cells for L1 / L2 cell mobility: 2> Set reest-L1L2Candidate to true in the VarRLF report; 2> Set the VarRLF report's reest-L1L2meas along with the available L1 RSRP and L1 SINR measurements for the SSB configured for L1 / L2 inter-cell mobility measurement; 1>When cell selection is triggered by detection of MCG radio link failure, MCG reconfiguration with synchronization failure, or mobility from NR failure, and 1>If attemptCondReconfig is configured; and 1> If the selected cell is one of the candidate cells in VarConditionalReconfig's masterCellGroup that contains reconfigurationWithSync: 2> Set the 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: In the case of CHO-based recovery after a handover fails without a key change, the method for avoiding key stream reuse is left to the network implementation. 1>Otherwise: 2>If UE is configured with conditionalReconfiguration: 3> Reset your Mac; 3> If configured, release spCellConfig; 3> If configured, release the MCG SCell; 3> If configured, release delayBudgetReportingConfig, and if running, stop timer T342; 3> If configured, release overheatingAssistanceConfig, and if running, stop timer T345; 3>If MR-DC is configured: Perform MR-DC release as specified in Section 4>5.3.5.10; 3> If configured, release idc-AssistanceConfig; 3> If configured, release btNameList; 3> If configured, release wlanNameList; 3> If configured, release sensorNameList; 3> If configured, release drx-PreferenceConfig for MCG, and if running, stop timer T346a associated with MCG; 3> If configured, release maxBW-PreferenceConfig for MCG, and if running, stop timer T346b associated with MCG; 3> If configured, release maxCC-PreferenceConfig for MCG, and if running, stop timer T346c associated with MCG; 3> If configured, release maxMIMO-LayerPreferenceConfig for MCG, and if running, stop timer T346d associated with MCG; 3> If configured, release minSchedulingOffsetPreferenceConfig for MCG, and if running, stop timer T346e associated with MCG; 3> If configured, release rlm-RelaxationReportingConfig for MCG, and if running, stop timer T346j associated with MCG; 3> If configured, release bfd-RelaxationReportingConfig for MCG, and if running, stop timer T346k associated with MCG; 3> If configured, release PreferenceConfig, and if running, stop timer T346f; 3> If configured, release onDemandSIB-Request and stop timer T350 if running; 3> If configured, release referenceTimePreferenceReporting; 3> If configured, release sl-AssistanceConfigNR; 3> If configured, release obtainCommonLocation; 3> If configured, release scg-DeactivationPreferenceConfig, and if running, stop timer T346i; 3> Pause all RBs except SRB0; 2> Delete all entries in VarConditionalReconfig if they exist; 2> For each measId, if the associated reportConfig has the reportType set in condTriggerConfig: 3>Regarding the associated reportConfigId: 4> Remove the entry matching reportConfigId from reportConfigList in VarMeasConfig; 3> If the associated measObjectId is only associated with a reportConfig where reportType is set to condTriggerConfig: 4> Remove entries with matching measObjectId from measObjectList in VarMeasConfig; 3> Remove entries with matching measId from measIdList in VarMeasConfig; 2> Start Timer T301; 2> Except for parameters for which values ​​are provided in SIB1, apply the default L1 parameter values ​​specified in the corresponding physical layer specification; Apply the default MAC cell group configuration specified in 2>9.2.2; Apply the CCCH configuration specified in 2>9.1.1.2; 2>Apply timeAlignmentTimerCommon included in SIB1; 2>Initiate sending the RRCReestablishmentRequest message according to 5.3.7.4; Note 2: This procedure also applies when the UE returns to the source PCell. When a cell between RATs is selected, the UE performs the following: As specified in 1>5.3.11, the action is executed when transitioning to RRC_IDLE due to a release cause "RRC connection failure". 5.3.7.4 Actions related to sending RRCReestablishmentRequest messages The UE may need to configure the contents of the RRCReEstablishmentRequest message as follows: 1> If the procedure is initiated by a wireless link failure as defined in 5.3.10.3, or by a reconfiguration due to a synchronization failure as defined 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 cell-to-cell mobility: 3> Set reest-L1L2Candidate to true in the VarRLF report; 3> Set the VarRLF report's reest-L1L2meas along with the available L1 RSRP and L1 SINR measurements for the SSB configured for L1 / L2 inter-cell mobility measurements; 1> Set ue-Identity as follows: 2> Set the c-RNTI to the C-RNTI used by the source PCell (reconfiguration by synchronization or mobility from NR failure), or to the C-RNTI used by the PCell that triggered the re-establishment (otherwise); 2> Set physCellId to the physical cell identifier of the source PCell (reconfiguration by synchronization or mobility from NR failure), or to the physical cell identifier of the PCell (otherwise) where the re-establishment trigger occurred; 2>Set shortMAC-I to the least significant 16 bits of the calculated MAC-I: 3 > Term 8 (i.e., multiples of 8 bits) via ASN.1 encoded according to VarShortMAC-Input; 3> K used in the source PCell (reconfiguration by synchronization or mobility from NR failure) or in the PCell (otherwise) where the re-establishment trigger occurred. 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 as follows: 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 a re-establishment procedure is initiated due to a failure of synchronous reconfiguration 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> Re-establish PDCP for SRB1; 1>When the UE is connected to the L2 U2N relay UE via a PC5-RRC connection (i.e., when the UE is an L2 U2N remote UE): 2>Apply the default SL-RLC1 configuration specified in 9.2.4 to SRB1; 2> Apply the default PDCP configuration specified in 9.2.1 to SRB1; 1>Otherwise: 2> Re-establish the RLC of SRB1; 2>Apply the default configuration specified in 9.2.1 to SRB1; 1> Configure the lower layers to temporarily suspend integrity protection and encryption of SRB1; Note: Subsequent RRCReestablishment messages used to re-establish the connection are not encrypted. Integrity checks are performed by lower layers, but only if requested by the 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 content of the VarRLF report as follows: 1> Clear any information contained in the VarRLF report; 1> Set plmn-IdentityList to include the list of EPLMNs (i.e., RPLMNs) saved by UE; 1>If the UE was configured in an L1 / L2 inter-cell mobility configuration at the time the UE declared a failure: 2> If a global cell identifier is available, set the L1L2CellID to the global cell identifier; 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>Include the following for each candidate cell contained in L1L2CellID: 3> For each SSB configured in an L1 / L2 inter-cell mobility configuration, include the available SSB index, L1 RSRP, and L1 SINR; ... As described in 1>5.3.5.8.3, if a failure is detected due to a reconfiguration with a synchronization failure, set the fields in the VarRLF report as follows: 2> Set connectionFailureType to hof; ... 1> Instead, as explained in 5.4.3.5, if the failure is detected due to a mobility failure from the NR, set the fields in the VarRLF report as follows: 2> Set connectionFailureType to hof; ... 1> Instead, as explained in 5.3.10.3, if the failure is detected due to a wireless link failure, set the fields in the VarRLF report as follows: 2> Set connectionFailureType to rlf; 2>Set rlf-Cause as a trigger for detecting wireless link faults, in accordance with section 5.3.10.4; 2> Set nrFailedPCellId in failedPCellId to the global cell identifier and tracking area code (if available), otherwise set to the physical cell identifier and carrier frequency of the PCell where the wireless link failure was detected; 2>If the UE received an RRCReconfiguration message including reconfigurationWithSync before connecting: 3>If the last RRCReconfiguration Message, including reconfigurationWithSync, was about an in-NR handover: 4>Include nrPreviousCell in previousPCellId and set it to the global cell identifier and tracking area code of the PCell that received the last executed RRCReconfiguration message, including reconfigurationWithSync; 4>If the last executed RRCReconfiguration message, including reconfigurationWithSync, was related to a DAPS handover: 5> Set lastHO-Type to daps; 4> If the last executed RRCReconfiguration message, including reconfigurationWithSync, was related to a conditional handover: 5> Set lastHO-Type to cho; 4> Set timeConnFailure to the elapsed time since the execution of the last RRCReconfiguration message, including reconfigurationWithSync; 3> Rather, if the last RRCReconfiguration message, including reconfigurationWithSync, concerns a handover from E-UTRA to NR, and the UE supports RAT-to-RAT MRO EUTRA radio link failure reporting: 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, which includes reconfigurationWithSync embedded in the E-UTRA RRC message MobilityFromEUTRACommand message, as specified in TS36.331

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

[10] 5.4.3.3; 3> If a conditional handover configuration is available in VarConditionalReconfig at the time of wireless link failure: 3> Set choCandidateCellList to include the global cell identifier and tracking area code of all candidate target cells in the conditional handover included in condRRCReconfig within VarConditionalReconfig when a wireless link failure occurs (excluding candidate target cells included in measResulNeighCells); 2> If a conditional handover configuration is available in VarConditionalReconfig at the time a wireless link failure is declared: 3> Set timeSinceCHO-Reconfig to the elapsed time between the detection of a wireless link failure and the reception of the last conditionalReconfiguration containing the condRRCReconfig message on the source PCell; 2> If L1 / L2 mobility configuration is available at the time a wireless link failure is declared: 3> Set timeSinceL1L2Config to the elapsed time between the detection of a wireless link failure and the reception of the last L1 / L2 mobility configuration on the PCell; 1>When connectionFailureType is rlf and rlf-Cause is set to randomAccessProblem or beamFailureRecoveryFailure; or 1>If connectionFailureType is hof and the failed handover was an intra-RAT handover: 2> Configure ra-InformationCommon to include random access-related information as described in section 5.7.10.5; 1> If available, set locationInfo as shown in 5.3.3.7. The UE can discard the wireless link failure information or handover failure information, i.e., release the UE variable VarRLF report, 48 hours after a wireless 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 further embodiments, for each adjacent cell included in the RLF report, the UE may also include corresponding L1 / L2 inter-cell mobility-related measurements if that adjacent cell is, for example, a candidate for L1 / L2 inter-cell mobility in candidate-L1L2meas of the following implementation example.

[0121] In this action 306, by transmitting one or more stored indications to the third network node 113, the wireless device 130 may enable the network, for example, the third network node 113, to identify, based on additional content of a report, for example, an RLF report, whether a re-established cell, for example, the first cell 123, was part of an L1 / L2 inter-cell mobility configuration, as proposed in the embodiment. The wireless device 130 thus enables the network, for example, the third network node 113, to know whether the problem lies in triggering L1 / L2 inter-cell mobility at the DU, in selecting an L1 / L2 inter-cell mobility candidate, or in an L3 mobility configuration.

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

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

[0124] If a re-established cell is not part of the candidate list for L1 / L2 inter-cell mobility, and the radio device 130 is a cell that 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 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 action 307 may be from the third network node 113.

[0126] Receipt in this action 307 may be based, for example, on one or more indications that have been sent.

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

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

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

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

[0131] Several embodiments are included here. 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 how those components may be used in other exemplary embodiments will be obvious to those skilled in the art. For the sake of brevity, not all possible combinations are described. A non-limiting example of a method performed by a third network node 113, also referred to simply as network node 113, is shown in Figure 4. In Figure 4, optional actions of some embodiments may be indicated by dashed lines. In some embodiments, the actions may be performed in an order different from the order shown in Figure 4.

[0132] Some of the detailed descriptions below correspond to the same references given above with respect to the actions described for wireless device 130, and therefore will not be repeated here for the sake of brevity. For example, a fault could be, for example, a wireless link fault. Mobility procedures may also be referred to here simply as mobility.

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

[0134] In some embodiments, one of the following options may be applied. According to the first option, the re-establishment procedure may be performed after the wireless device 130 may have entered idle mode following a failed mobility procedure. According to the 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. One or more indications may indicate a failed mobility procedure; that is, one or more indications indicate a failure. One or more indications include at least a first indication.

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

[0137] As mentioned above, the obstacle can be considered the mobility procedure that became the obstacle.

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

[0139] Previous indications 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 either a radio link failure or a handover failure; c) the mobility, e.g., the mobility procedure, may be L1 / L2 inter-cell mobility; d) one or more indications may be received in a report, e.g., an RLF report; e) 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, one or more indications may further include at least one of the following: a) a second indication, wherein the second indication may indicate one or more candidate cells 125 configured in inter-cell mobility, e.g., L1 / L2 inter-cell mobility configurations; b) a third indication, wherein the third indication may indicate the elapsed time between a first time for receiving an inter-cell mobility configuration, e.g., an L1 / L2 inter-cell mobility configuration and a second time for which a fault, e.g., a radio link fault, is declared; c) the third indication may further indicate a third elapsed time between a fourth time for receiving a final inter-cell mobility configuration, e.g., an L1 / L2 inter-cell mobility configuration and a second time for which a fault, e.g., a radio link fault, is declared; d) a fourth indication, wherein the fourth indication may indicate at least one of i) a first location information at the fourth time and ii) a 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 1-bit flag; b) the first indication may be indicated by the 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 the reest-L1L2meas IE; e) the first indication including additional L1 / L2 mobility-related measurements may be indicated by the 38econnect-L1L2meas; f) the second indication may be candidates-L1L2Mobility g) A second indication may be indicated by the candidate-L1L2flag flag, h) A second indication may further indicate additional L1 / L2 mobility-related measurements, i) A second indication including additional L1 / L2 mobility-related measurements may be indicated by the candidate-L1L2meas IE, j) A third indication may be indicated by another IE, k) A 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, and 406.

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

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

[0147] One or more characteristics of the determined 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) the measurement results of one or more candidate cells 125 configured in an inter-cell mobility configuration, such as an L1 / L2 inter-cell mobility configuration, and iii) the period before the failure occurred, i.e., before the wireless link failure occurred, during which the wireless device 130 was configured in an inter-cell mobility configuration, such as an L1 / L2 inter-cell mobility configuration.

[0148] Action 404 In this action 404, the network node 113 may initiate the adaptation of one or more steps of an inter-cell mobility configuration, such as an L1 / L2 inter-cell mobility configuration.

[0149] "Start" can be understood as beginning, facilitating, activating, triggering, etc.

[0150] In some examples, adapting one or more steps of an inter-cell mobility configuration, such as an L1 / L2 inter-cell mobility configuration, could be at least one of the following: candidate cell selection, mobility procedure trigger thresholds, and L3 mobility parameters.

[0151] The initiation of this action 404 can be based, for example, on the result of a judgment.

[0152] Action 405 In action 405, network node 113 may transmit an updated inter-cell mobility configuration, such as an L1 / L2 inter-cell mobility configuration, which is the inter-cell mobility procedure configuration described in action 307.

[0153] An updated inter-cell mobility configuration, such as an L1 / L2 inter-cell mobility configuration, may include one or more adapted procedures.

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

[0155] In some embodiments, at least one of the following options may apply. According to the first option a), if the first cell 123 was not a candidate cell in the inter-cell mobility configuration, the adaptation may include, for example, adding the first cell 123 to the list of candidate cells for the inter-cell mobility configuration for a cell in which a failed mobility procedure was detected, such as a device connected to a PCell. 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 the list of candidate cells for UEs connected to a PCell in which a wireless link failure was detected.

[0156] According to the second option b), the adaptation 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, network node 113 may derive measurement results for candidate L1 / L2 cells from the RLF report and, based on that, trigger an earlier L1 / L2 mobility to one of the candidate L1 / L2 cells with better measurement results.

[0157] According to the third option c), if the measurement results indicate that the first candidate cell 126 has poor measurement results, the adaptation may include removing the first candidate cell 126 from one or more candidate cells 125. In another example, the network node 113 may derive the measurement results of candidate L1 / L2 cells from a report, such as an RLF report, and based on that, remove candidate cells that may have insufficient measurement results from the list of candidate cells configured for L1 / L2 mobility.

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

[0159] In several other examples, network node 113 may, in action 403, derive the period during which the wireless device 130 was configured for L1 / L2 mobility before the failure occurred. If the period is determined to be short, network node 113 may, in action 404 and / or action 405, configure the L1 / L2 mobility configuration a little earlier. This can be understood as the case because if the wireless device 130 failed immediately after the L1 / L2 mobility configuration, network node 113 may not have had enough time to collect sufficient L1 / L2 measurements to trigger L1 / L2 mobility. On the other hand, if action 403 determines that the timeframe is too long, network node 113 may slightly delay configuring the L1 / L2 mobility configuration in action 404 and / or action 405, because the L1 / L2 mobility configuration may require additional UE resources such as memory resources, energy, and possibly radio resources, if it implies a new set of measurements and signaling reports to network node 113. Also, configuring the L1 / L2 mobility configuration too early may require extra resources on the network node 113 side, especially if it may need to pre-prepare target cells that may belong to different nodes for potential handovers.

[0160] Action 406 Action 406 may be performed in an embodiment in which 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 and sixth indications.

[0161] The reception in this action 406 could be, for example, from the wireless device 130 after reconnection.

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

[0163] In some embodiments, the fifth indication may be represented by reConnect-L1L2Candidate IE.

[0164] In summary, examples of embodiments disclosed herein may relate to wireless devices, network nodes, and methods performed by them to process re-establishment information after a failure of a mobility procedure. The failure may be a wireless link failure.

[0165] As summarized above, examples of embodiments disclosed herein may relate to a method performed by a wireless device 130, e.g., a UE, the method of a) receiving an L1 / L2 inter-cell mobility configuration from a first network node 111, b) declaring a wireless link failure, and c) storing a first set of information relating to the wireless link failure in a first report, the first set of information including i) an indication that a cell that could be selected for a re-establishment procedure was a candidate cell in the L1 / L2 inter-cell mobility configuration, and ii) an indication of a candidate cell configured in the L1 / L2 inter-cell mobility configuration. The system may include one or more of the following: iii) an indication showing the time elapsed since the reception of an L1 / L2 inter-cell mobility configuration and a radio link failure; iv) in one example, the indication may show the time elapsed since the last reception of an L1 / L2 mobility configuration and a radio link failure; v) an indication showing the location information at the time of the last reception of an 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 for a cell that was a candidate for an 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-established cell collected by the wireless device 130 may also be applicable to scenarios where the wireless device 130 fails to perform re-establishment and reconnects to another cell after transitioning to RRC_IDLE mode.

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

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

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

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

[0171] If a re-established cell is not part of the candidate list for L1 / L2 inter-cell mobility, and the radio device 130 is a cell that has declared RLF, and the re-established 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 the handover parameters.

[0172] Figure 5 shows two different examples of configurations that the wireless device 130 may have to perform the method action described above in relation to Figure 3, in panels a) and b), respectively. In some embodiments, the wireless device 130 may have the following configuration as 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 a wireless communication network 100.

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

[0174] Several embodiments are included here. It should be noted that the examples here are not mutually exclusive. Where applicable, one or more embodiments may be combined. For the sake of brevity, not all possible combinations are described. Components of one embodiment may be implicitly assumed to be present in another embodiment, and how those components may be used in other exemplary embodiments will be obvious to those skilled in the art. Some of the detailed descriptions below relate to the actions described for the wireless device 130 and correspond to the same references given above, and are therefore not repeated here for the sake of brevity. 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 saving / logging / recording action 304 by means of, for example, a storage unit 501 within the wireless device 130, which is configured to store one or more indicators configured to indicate a fault in response to a declared fault. The one or more indicators are configured to include at least a first indicator configured to indicate whether a first cell 123, which is configured to be selected by the wireless device 130 for a re-establishment procedure configured to be triggered by a fault, was a candidate cell in an inter-cell mobility configuration received in a previous indicator for performing an L1 / L2 mobility procedure.

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

[0178] In some embodiments, one or more indicators may further include at least one of the following: a) a second indicator configured to indicate one or more candidate cells 125 configured in an inter-cell mobility configuration; b) a third indicator configured to indicate the elapsed time between a first time for receiving the inter-cell mobility configuration and a second time for which a failure was declared; c) a third indicator configured to indicate a third elapsed time between a fourth time for receiving the last inter-cell mobility configuration, including a first cell 123 configured to be selected as a candidate cell for a re-establishment procedure, and a second time for which a failure was declared; d) a fourth indicator configured to indicate at least one of i) a first position information at the fourth time, and ii) a second position 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 1-bit flag; b) the first indication may be configured to be indicated by 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 reest-L1L2meas IE; e) the first indication including additional L1 / L2 mobility-related measurements may be configured to be indicated by reConnect-L1L2meas; f) the second indication may be candidates-L1L2Mobility g) a second indication may be configured as indicated by the candidate-L1L2flag flag, h) a second indication may be configured to further indicate additional L1 / L2 mobility-related measurements, i) a second indication including additional L1 / L2 mobility-related measurements may be configured as indicated by the candidate-L1L2measIE, j) a third indication may be configured as indicated by another IE, k) a fourth indication may be configured as indicated by yet another IE.

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

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

[0182] The wireless device 130 may be configured to perform the reception of action 301, for example, by means of a receiving unit 503 within the wireless device 130, which is configured to receive previous indications 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, which is 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 declaration of action 303 by means of a declaration unit 505 within the wireless device 130, for example, configured to declare a fault, such as a wireless link fault.

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

[0186] The wireless device 130 may be configured to perform reception in action 307, for example by means of a receiving unit 503 within the wireless device 130, which is configured to receive an updated inter-cell mobility procedure configuration from the network node 113 based on one or more indications 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 wireless link failure; or 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 a re-establishment procedure fails, and saving may further include saving at least one of the following: a) 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 an inter-cell mobility configuration configured to be received in a previous indication; and b) 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 reconnection by selection of the second cell 124.

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

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

[0191] This embodiment of the wireless device 130 may be implemented via one or more processors, such as the processor 507 of the wireless device 130 shown in Figure 5a, and computer program code for performing the functions and actions of this embodiment. The processors used herein may be understood as hardware components. The program code may also be provided as a computer program product, for example, in the form of a data carrier that, when loaded into the wireless device 130, carries the computer program code that performs this embodiment. 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 comprising one or more memory units. When the wireless device 130 is running, the memory 508 is configured to be used to store acquired information, data, configurations, schedules, applications, etc., in order to perform the method of this specification.

[0193] In some embodiments, the wireless device 130 may receive information via the receiving port 509 from, for example, a first network node 111, a second network node 112, a third network node 113, a network node 113, a source cell 121, a target cell 122, a first cell 123, a second cell 124, one or more candidate cells 125, a first candidate cell 126, a first neighboring cell 127, and / or another cell, network node, or node. In some embodiments, the receiving 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 receiving port 509 from another structure within the wireless communication network 100. Since the receiving port 509 can communicate with the processor 507, the receiving port 509 can transmit the received information to the processor 507. The receiving 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 via a transmit port 510 and memory 508 that can communicate with the processor 507 to, for example, a first network node 111, a second network node 112, a third network node 113, a network node 113, a source cell 121, a target cell 122, a first cell 123, a second cell 124, one or more candidate cells 125, a first candidate cell 126, a first neighboring cell 127, another cell, a network node, or a node, or another structure within the wireless communication network 100.

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

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

[0197] Accordingly, the methods according to this embodiment, as described with respect to the wireless device 130, may each be implemented by means of instructions, i.e., a computer program 511 product including a software code portion, which, when executed on at least one processor 507, causes 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 in a computer-readable storage medium 512. The computer-readable storage medium 512 storing the computer program 511 may, when executed on at least one processor 507, include instructions that cause 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-temporary 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 in a carrier containing the aforementioned computer program 511, which, as described above, is one of electronic signals, optical signals, wireless signals, or the computer-readable storage medium 512.

[0198] The wireless device 130 may include 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, network node 113, source cell 121, target cell 122, first cell 123, second cell 124, one or more candidate cells 125, first candidate cell 126, first neighboring cell 127, another cell, network node or node, or another structure within the wireless communication network 100. The interface may include, for example, a transceiver configured to send and receive wireless signals via an air interface in accordance with an appropriate standard.

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

[0200] Therefore, this embodiment also relates to a wireless device 130 including a processing circuit 507 and a memory 508, the memory 508 containing instructions that can be executed by the processing circuit 507, so that the wireless device 130 operates to perform actions described herein with respect to the wireless device 130, for example, as shown in Figure 3.

[0201] Figure 6 shows two different examples of configurations that a third network node 113, which may also be referred to as network node 113, may have in order to perform the method actions described above in relation to Figure 4, in panels a) and b), respectively. In some embodiments, the third network node 113 may have the following configuration as 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 here. It should be noted that the examples here are not mutually exclusive. Where applicable, one or more embodiments may be combined. For the sake of brevity, not all possible combinations are described. Components of one embodiment may be implicitly assumed to be present in another embodiment, and how those components may be used in other exemplary embodiments will be obvious to those skilled in the art. Some of the detailed descriptions below correspond to the same references given above with respect to the actions described for wireless device 130, and are therefore not repeated here for the sake of brevity. 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] Network node 113, for example, third network node 113, is configured to perform reception in action 402 by means of a receiving unit 601 in (third) network node 113, which is configured to receive one or more indications configured to indicate a fault from the radio device 130. One or more indications are configured to include at least a first indication. The first indication is configured to indicate whether a first cell 123, which is configured to be selected by the radio device 130 for a re-establishment procedure configured to be triggered by a fault, was a candidate cell in an inter-cell mobility configuration. The inter-cell mobility configuration is configured to be received by the radio device 130 in a previous indication for performing an L1 / L2 mobility procedure.

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

[0207] In some embodiments, one or more indications may further include at least one of the following: a) a second indication configured to show one or more candidate cells 125 configured in an inter-cell mobility configuration; b) a third indication configured to show the elapsed time between a first time for receiving the inter-cell mobility configuration and a second time for which a failure was declared; c) a third indication configured to show a third elapsed time between a fourth time for receiving the last inter-cell mobility configuration configured to include a first cell 123 configured to be selected as a candidate cell for a re-establishment procedure and a second time for which a failure was declared; d) a fourth indication configured to show at least one of i) first position information at the fourth time and ii) second position 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 1-bit flag; b) the first indication may be configured to be indicated by 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 reest-L1L2meas IE; e) the first indication including additional L1 / L2 mobility-related measurements may be configured to be indicated by reConnect-L1L2meas; f) the second indication may be candidates-L1L2Mobility g) a second indication may be configured as indicated by the candidate-L1L2flag flag, h) a second indication may be configured to further indicate additional L1 / L2 mobility-related measurements, i) a second indication including additional L1 / L2 mobility-related measurements may be configured as indicated by the candidate-L1L2meas IE, j) a third indication may be configured as indicated by another IE, k) a fourth indication may be configured as indicated by yet another IE.

[0209] A network node 113, for example, a third network node 113, may be configured to perform an execution in action 401 by means of an execution unit 602 within the (third) network node 113, for example, to perform a re-establishment or 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, one of the following may apply: a) the re-establishment procedure may be configured to run after the wireless device 130 has been configured to enter idle mode after the mobility procedure has failed; b) the wireless device 130 may be configured to reconnect to the network node 113 after the re-establishment procedure has failed.

[0211] In some embodiments, the wireless device 130 may be configured to reconnect to a network node 113 after a re-establishment procedure fails, and the network node 113, for example, a third network node 113, may be further configured to receive action 406 after reconnection, by means of a receiving unit 601 in the (third) network node 113, configured to receive at least one of the following from the wireless device 130: i) 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 an inter-cell mobility configuration configured to be received in a previous indication; and ii) a sixth indication configured to indicate the elapsed time between a first time for receiving the inter-cell mobility configuration and a fifth time for reconnection by selection of the second cell 124.

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

[0213] In some embodiments, the network node 113 may be further configured with 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 determination unit 603 in the (third) network node 113, wherein the determination unit 603 is configured to determine one or more characteristics of an inter-cell mobility configuration configured to be selected from the following based on a received indication: i) whether the first cell 123 configured to be selected by the wireless device 130 for a 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 iii) a period during which the wireless device 130 was configured with the inter-cell mobility configuration before a failure occurred.

[0215] In some embodiments, the network node 113, for example, the third network node 113, may be configured to initiate performing action 404, for example, by means of an initiating unit 604 in the (third) network node 113, wherein the initiating unit 604 is configured to start adapting one or more procedures of the inter-cell mobility configuration based on the determination result.

[0216] In some embodiments, the network node 113, for example, the third network node 113, may be configured to perform the determination in action 405, for example, by means of a transmitting unit 605 in the third network node 113, wherein the transmitting unit 605 is configured to transmit an updated inter-cell mobility configuration configured to include one or more procedures configured to be adapted based on the adaptation.

[0217] In some embodiments, at least one of the following may be applied: 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 comprise adding the first cell 123 to the list of candidate cells for the inter-cell mobility configuration; b) on condition that the measurement result indicates that the first candidate cell 126 has a better measurement result, the adapting may be configured to comprise triggering a mobility procedure to the first candidate cell 126; c) on condition that the measurement result indicates that the first candidate cell 126 has a poor measurement result, the adapting may be configured to comprise removing the first candidate cell 126 from the one or more candidate cells 125; d) 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 configured as a candidate cell in the inter-cell mobility configuration, the adapting may be configured to comprise adding the first neighboring cell 127 to the list of candidate cells for the inter-cell mobility configuration.

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

[0219] The present embodiments relating to 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 executing the functions and actions of the present embodiments. A processor as used herein may be understood to be a hardware component. Said program code may also be provided as a computer program product, for example in the form of a data carrier carrying computer program code for executing the present embodiments when loaded into the third network node 113. One such carrier may be in the form of a CD ROM disc. However, other data carriers such as a memory stick are also possible. The computer program code may further 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 include a memory 608 comprising one or more memory units. When running on the third network node 113, the memory 608 is configured to be used to store acquired information, data, configurations, schedules, applications, etc., in order to perform the method described herein.

[0221] In some embodiments, the third network node 113 may receive information via the receiving port 609 from, for example, a wireless device 130, a first network node 111, a second network node 112, a source cell 121, a target cell 122, a first cell 123, a second cell 124, one or more candidate cells 125, a first candidate cell 126, a first neighboring cell 127, and / or other cells, network nodes, or nodes. In some embodiments, the receiving 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 via the receiving port 609 from other structures within the wireless communication network 100. Since the receiving port 609 can communicate with the processor 607, the receiving port 609 can transmit the received information to the processor 607. The receiving 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 via a transmit port 610 and memory 608 that can communicate with the processor 607 to, for example, a wireless device 130, a first network node 111, a second network node 112, a source cell 121, a target cell 122, a first cell 123, a second cell 124, one or more candidate cells 125, a first candidate cell 126, a first neighboring cell 127, another cell, a network node, or a node, and / or another structure within the wireless communication network 100.

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

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

[0225] Accordingly, the methods according to this embodiment, as described for the third network node 113, may each be implemented by means of instructions, i.e., a computer program 611 product including a software code portion, which, when executed on at least one processor 607, causes at least one processor 607 to perform the actions described herein as being executed by the third network node 113. The computer program 611 product may be stored in a computer-readable storage medium 612. The computer-readable storage medium 612 storing the computer program 611 may, when executed on at least one processor 607, include instructions that cause at least one processor 607 to perform the actions described herein as being executed by the third network node 113. In some embodiments, the computer-readable storage medium 612 may be a non-temporary computer-readable storage medium, such as a CD-ROM disk or a memory stick. In other embodiments, the computer program 611 product may be stored in a carrier containing the aforementioned computer program 611, which, as described above, is one of electronic signals, optical signals, radio signals, or the computer-readable storage medium 612.

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

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

[0228] Therefore, this embodiment also relates to a third network node 113 including a processing circuit 607 and a memory 608, the memory 608 containing instructions that can be executed by the processing circuit 607, so 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 Figure 4.

[0229] In general, all terms used herein should be interpreted according to their common meanings in the art relating to them, unless otherwise explicitly stated, and / or unless otherwise suggested by the context in which they are used. All references to an element, apparatus, component, means, step, etc., should be openly interpreted as references to at least one example of such element, apparatus, component, means, step, etc., unless otherwise explicitly stated. Steps of any method disclosed herein do not need to be performed in the exact order disclosed unless it is explicitly stated that one step follows or precedes another, and / or it is implicitly indicated that a step must follow or precede another. Any feature of any embodiment disclosed herein may be applied to any other embodiment, where appropriate. Similarly, any advantage of any embodiment may apply to any other embodiment, and vice versa. Other purposes, features, and advantages of the embodiments contained herein will become apparent from the following description.

[0230] As used herein, when the expression "at least one" is followed by a comma-separated list of options, and the last option is preceded by the term "and," it can be understood that only one of the options in the list may apply, two or more of the options may apply, or all of the options in the list may apply. This expression can be understood as equivalent to when the expression "at least one" is followed by a comma-separated list of options, and the last option is preceded by the term "or."

[0231] In a non-limiting example, L1 signaling may be understood as any operation involving interaction / signaling between a physical (PHY) layer of a radio network node such as a gNB and a 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 layer 2 such as a MAC layer or an RLC layer between a RAN node such as a gNB-DU and a device such as a UE.

[0232] In a non-limiting example, a mobility procedure may be understood as a procedure involving a change of a 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 involving a change of a 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 FIG. 7, FIG. 5, FIG. 7 and FIG. 9.

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

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

[0237] The mobility procedure may also be simply referred to as mobility herein.

[0238] In some specific 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 how those components may be used in other exemplary embodiments will be apparent to those skilled in the art. For the sake of brevity, not all possible combinations are described. A non-limiting example of a method performed by the wireless device 130 is shown in Figure 7. In Figure 7, optional actions in some embodiments may be indicated by dashed lines. In some embodiments, the actions may be performed in an order different from the order shown in Figure 7.

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

[0241] The save / logging / recording in this action 704 may be in response to a declared failure.

[0242] One or more indications may indicate a mobility procedure that was disrupted.

[0243] One or more indications may include at least the first indication.

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

[0245] Previous indications 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] ○ Transmit one or more of the stored indications 706. The wireless device 130 may be configured to transmit this action 706 by means of, for example, a transmitting unit 502 of the wireless device configured to perform this action.

[0248] The transmission in this action 705 may be made, for example, to a third network node 113, which may also be referred to simply as network node 113. The third network node 113 may provide services to the wireless device 130 within the wireless communication network 100.

[0249] The transmission in this action 706 may be performed, for example, via the first link 141.

[0250] The one or more indications sent may, for example, be a subset selected from one or more stored indications.

[0251] In some cases, 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 problem could be a wireless link failure. - Mobility, for example, mobility procedures, could be L1 / L2 cell-to-cell mobility. - The inter-cell mobility configuration can be an L1 / L2 inter-cell mobility configuration.

[0252] In some examples, one or more indications may further include at least one of the following: - Second indication; the second indication may indicate one or more candidate cells 125 configured in an inter-cell mobility configuration, for example, an L1 / L2 inter-cell mobility configuration. - Third indication; The third indication may indicate the elapsed time between a first time of reception of an inter-cell mobility configuration, e.g., an L1 / L2 inter-cell mobility configuration, and a second time when a fault, e.g., a radio link fault, is declared. - The third indication further shows the third elapsed time between the fourth time of reception of the last inter-cell mobility configuration, e.g., L1 / L2 inter-cell mobility configuration, and the second time when a fault, e.g., a radio link failure, was declared. - Fourth indication; the fourth indication may indicate at least one of a) first position information in the fourth time, and b) second position information in the second time.

[0253] In some cases, at least one of the following may apply: - The first indication may be shown by the reest-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 shown in the reest-L1L2meas IE. - The first indication, including additional L1 / L2 mobility-related measurements, may be shown in reConnect-L1L2meas. - The second indication may be shown in candidate-L1L2Mobility IE, - The second indication can be shown by the candidate-L1L2flag flag. - The second indication may show additional L1 / L2 mobility-related measurements. - A second indication, including additional L1 / L2 mobility-related measurements, may be shown in candidate-L1L2meas IE. - The third indication may be shown in another IE. -The fourth indication may be shown in yet another IE.

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

[0255] ○Receive a previous indication 701. The wireless device 130 may be configured to perform the reception in 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 from, for example, a first network node 111, a second network node 112, or another network node operating in the wireless communication network 100.

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

[0258] A mobility procedure could be, for example, an L1 / L2 cell-to-cell mobility procedure.

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

[0260] The execution of this action 702 could, for example, be a response to a previously received indication.

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

[0262] The malfunction could be, for example, a wireless link failure.

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

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

[0265] The actions performed in this action 705 could, for example, be in response to a declared failure.

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

[0267] A mobility procedure could be, for example, an L1 / L2 cell-to-cell mobility procedure.

[0268] The reception in this action 707 may originate from the third network node 113.

[0269] Receipt in this action 707 may be based, for example, on one or more indications that have been sent.

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

[0271] In some cases, one of the following may be applied: 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 be an obstacle, causing the wireless device 130 to reconnect to the third network node 113.

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

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

[0274] In some cases, the fifth indication may be shown as 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 host application units in hosts 716, 800, and 902 via an OTT connection, such as an OTT connection 950.

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

[0278] The wireless device 130 may include an interface unit to facilitate communication between the wireless device 130 and other nodes or devices, such as the third network node 113, hosts 716, 800, 902, or any other node. In some specific examples, the interface may include, for example, a transceiver configured to send and receive wireless signals via an air interface according to an appropriate standard.

[0279] Embodiments of the third network node 113 are related to Figures 8, 6, 7, and 9.

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

[0281] Mobility procedures can also be referred to simply as mobility here.

[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 how those components may be used in other exemplary embodiments will be apparent to those skilled in the art. For the sake of brevity, not all possible combinations are described. A non-limiting example of a method performed by the third network node 113 is shown in Figure 8. In Figure 8, optional actions of some embodiments may be indicated by dashed lines. In some embodiments, the actions may be performed in an order different from the order shown in Figure 8.

[0284] Some of the detailed descriptions below correspond to the same references given above regarding the actions described for wireless device 130, and therefore will not be repeated here for the sake of brevity. For example, a fault could be, for example, a wireless link fault.

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

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

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

[0288] One or more indications may indicate a mobility procedure that was disrupted.

[0289] One or more indications may include at least the first indication.

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

[0291] Previous indications 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 cases, 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 problem could be a wireless link failure. - Mobility, for example, mobility procedures, could be L1 / L2 cell-to-cell mobility. - The inter-cell mobility configuration can be an L1 / L2 inter-cell mobility configuration.

[0293] In some examples, one or more indications may further include at least one of the following: - Second indication; the second indication may indicate one or more candidate cells 125 configured in an inter-cell mobility configuration, for example, an L1 / L2 inter-cell mobility configuration. - Third indication; The third indication may indicate the elapsed time between a first time of reception of an inter-cell mobility configuration, e.g., an L1 / L2 inter-cell mobility configuration, and a second time when a fault, e.g., a radio link fault, is declared. - The third indication further shows the third elapsed time between the fourth time of reception of the last inter-cell mobility configuration, e.g., L1 / L2 inter-cell mobility configuration, and the second time when a fault, e.g., a radio link failure, was declared. - Fourth indication; the fourth indication may indicate at least one of a) first position information in the fourth time, and b) second position information in the second time.

[0294] In some cases, at least one of the following may apply: - The first indication may be shown by the reest-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 shown in the reest-L1L2meas IE. - The first indication, including additional L1 / L2 mobility-related measurements, may be shown in reConnect-L1L2meas. - The second indication may be shown in candidate-L1L2Mobility IE, - The second indication can be shown by the candidate-L1L2flag flag. -The second indication may further show additional L1 / L2 mobility-related measurements. - A second indication, including additional L1 / L2 mobility-related measurements, may be shown in candidate-L1L2meas IE. - The third indication may be shown in another IE. -The fourth indication may be shown in yet another IE.

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

[0296] ○ Perform a re-establishment procedure or a 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 re-establishment or reconnection procedure in this action 801 may be performed with the wireless device 130.

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

[0299] In some cases, one of the following may apply: a) The re-establishment procedure may be performed after the wireless device 130 may have entered idle mode following the failed mobility procedure. b) The re-establishment procedure may be an obstacle, causing the wireless device 130 to reconnect to the third network node 113.

[0300] In some embodiments, for example, the re-establishment procedure may be an obstacle, 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] ○Receive at least one of the fifth indication and the sixth indication. The third network node 113 may be configured to perform the reception in this action 806 by means of, for example, a receiving unit 601 of the third network node 113 configured to perform this action.

[0302] The reception in this action 806 could be, for example, from the wireless device 130 after reconnection. -The fifth indication may indicate whether the second cell 124 selected by the wireless device 130 for a reconnection procedure triggered by a failed re-establishment procedure was a candidate cell in the inter-cell mobility configuration received in a previous indication. - The sixth indication may indicate the elapsed time between the first time of reception of an inter-cell mobility configuration, for example, an L1 / L2 inter-cell mobility configuration, and the fifth time of reconnection due to the selection of the second cell 124.

[0303] In some cases, the fifth indication may be shown as reConnect-L1L2Candidate IE.

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

[0305] ○ Determine 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 by means of a determination unit 603 of the third network node 113 that is configured to perform this action.

[0306] The decision in action 803 may be based on one or more received indications, e.g., a subset.

[0307] One or more characteristics of the determined inter-cell mobility configuration may be selected from, for example, 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 in an inter-cell mobility configuration, for example, an L1 / L2 inter-cell mobility configuration, iii. The period during which the wireless device 130 was configured in an inter-cell mobility configuration, for example, an L1 / L2 inter-cell mobility configuration, prior to the occurrence of the failure.

[0308] The third network node 113 may be configured to initiate action 804 by means of an initiation unit 604 of the third network node 113 configured to perform this action.

[0309] "Start" can be understood as beginning, facilitating, activating, triggering, etc.

[0310] In some examples, the adaptation of one or more steps in an inter-cell mobility configuration, such as an L1 / L2 inter-cell mobility configuration, may be at least one of the following: candidate cell selection, mobility procedure trigger thresholds, and L3 mobility parameters.

[0311] The initiation of this action 804 could be based, for example, on the result of a determination.

[0312] The updated inter-cell mobility configuration, for example, the L1 / L2 inter-cell mobility configuration, is transmitted 805. The third network node 113 may be configured to perform the determination in this action 803 by means of, for example, the transmission unit 605 of the third network node 113 configured to perform this action.

[0313] An updated inter-cell mobility configuration, such as an L1 / L2 inter-cell mobility configuration, may include one or more adapted procedures.

[0314] The transmission of the updated inter-cell mobility configuration in Action 805, for example, the L1 / L2 inter-cell mobility configuration, may be based on the adaptation initiated in Action 804.

[0315] In some cases, at least one of the following may apply: - If the first cell 123 was not a candidate cell in the inter-cell mobility configuration, the adaptation may include, for example, adding the first cell 123 to the list of candidate cells in the inter-cell mobility configuration for a cell in which a failed mobility procedure was detected, such as a device connected to a PCell. -Provided that the measurement results indicate that the first candidate cell 126 has better measurement results, the adaptation may include triggering a mobility procedure to the first candidate cell 126. - Under the condition that the measurement results indicate that the first candidate cell 126 has a poor measurement result, the adaptation may include removing the first candidate cell 126 from one or more candidate cells 125. - If the measurement results indicate that the first adjacent cell 127 has good measurement results, and the first adjacent cell 127 is not a candidate cell in the inter-cell mobility configuration, then adapting the configuration may include adding the first adjacent cell 127 to the list of candidate cells in the inter-cell mobility configuration.

[0316] Other 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 host application units in hosts 716, 800, and 902, for example, via connection 960.

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

[0319] The third network node 113 may include an interface unit to facilitate 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, hosts 716, 800, 902, or any other node. In some specific examples, the interface may include, for example, a transceiver configured to send and receive radio signals via an air interface according to an appropriate standard.

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

[0321] example:

[0322] Example 1. A method performed by a wireless device (130) operating on a wireless communication network (100) to process re-establishment information after a failure in a mobility procedure from a first network node (111) to a second network node (112), the wireless device (130) being operated on the wireless communication network (100), - A method comprising storing (704) one or more indications indicating a failed mobility procedure in response to a declared failure, wherein the one or more indications include at least one first indication indicating whether a first cell (123) selected by a radio 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 a first network node (111) for performing the failed mobility procedure.

[0323] Example 2. The method described in Example 1, - One or more indications will be sent in the report, - One or more indications are sent in the UEInformationResponse message, - The problem is a wireless link failure, - Mobility, for example, mobility procedures, are L1 / L2 cell-to-cell mobility, - The inter-cell mobility configuration is an L1 / L2 inter-cell mobility configuration, A method that is at least one of the following.

[0324] Example 7. The method described in Example 1 or 2, wherein one or more indications further: - A second indication showing one or more candidate cells (125) configured in an inter-cell mobility configuration, for example, an L1 / L2 inter-cell mobility configuration, - A third indication showing the elapsed time between a first time of reception of an inter-cell mobility configuration, e.g., an L1 / L2 inter-cell mobility configuration, and a second time when a fault, e.g., a radio link fault, is declared. -The third indication further indicates a third elapsed time between the fourth time of reception of the last inter-cell mobility configuration, e.g., L1 / L2 inter-cell mobility configuration, and the second time when a fault, e.g., a radio link fault, was declared. -a) a fourth indication showing at least one of the first position information in the fourth time and b) the second position information in the second time, A method that includes at least one of the following.

[0325] Example 8. The method described in Example 7, - The first indication is shown by the reest-L1L2Candidate information element (IE), - The first indication further shows additional L1 / L2 mobility-related measurements, - The first indication, including additional L1 / L2 mobility-related measurements, is shown in reest-L1L2meas IE, - The first indication, including additional L1 / L2 mobility-related measurements, is shown in reConnect-L1L2meas, - The second indication is shown in candidate-L1L2Mobility IE, - The second indication is shown by the candidate-L1L2flag flag, - The second indication is to show additional L1 / L2 mobility-related measurements, - The second indication, including additional L1 / L2 mobility-related measurements, will be shown in candidate-L1L2meas IE, - The third indication will be shown in a separate IE, -The fourth indication will be shown in yet another IE, A method that is at least one of the following.

[0326] Example 5. A method according to any one of Examples 1 to 4, further comprising - Receiving a previous indication (701) from the first network node (111), -In response to a previously received indication, perform mobility from the first network node (111) to the second network node (112), for example, perform an L1 / L2 inter-cell mobility procedure (702), - Declaring a failure in mobility procedures, such as a radio link failure (703), - Performing a re-establishment or reconnection procedure (705) to a third network node (113) operating in the wireless communication network (100), - Sending (706) one or more of the stored indications to the (third) network node (113), - Receiving (707) an updated inter-cell mobility procedure, e.g., an L1 / L2 inter-cell mobility procedure configuration, from a (third) network node (113) based on one or more transmitted indications, wherein the updated configuration includes at least one of the adapted procedures, e.g., candidate cell selection, mobility procedure trigger thresholds, and L3 mobility parameters. A method that includes one or more of the following.

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

[0328] Example 7. The method described in Example 6, wherein the re-establishment procedure fails, and the wireless device (130) reconnects to the (third) network node (113) and saves (704), further, - A fifth indication showing whether the second cell (124) selected by the wireless device (130) for a reconnection procedure triggered by a failed re-establishment procedure was a candidate cell in the inter-cell mobility configuration received in a previous indication, - A sixth indication showing the elapsed time between the first time of reception of an inter-cell mobility configuration, for example, an L1 / L2 inter-cell mobility configuration, and the fifth time of reconnection due to the selection of the second cell (124), A method that includes saving at least one of the following.

[0329] Example 8. The method described in Example 7, wherein the fifth indication is shown by reConnect-L1L2Candidate IE.

[0330] Example 9. A method performed by a (third) network node (113) to process re-establishment information after a failure in the mobility procedure of a wireless device (130) from a first network node (111) to a second network node (112), wherein the third network node (113) operates in a wireless communication network (100), and the method is: - A method comprising receiving (802) one or more indications from a radio device (13) indicating a failed mobility procedure, wherein the one or more indications include at least one first indication indicating that a first cell (123) selected by the radio 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 from a first network node (111) received by the radio device (130) for performing the failed mobility procedure.

[0331] Example 10. The method described in Example 9, - One or more indications are received in the report, - One or more indications are received in the UEInformationResponse message, - The problem is a wireless link failure, - The mobility is L1 / L2 cell-to-cell mobility. - The inter-cell mobility configuration is an L1 / L2 inter-cell mobility configuration, A method that is at least one of the following.

[0332] Example 11. The method described in Example 9 or 10, wherein one or more indications further: - A second indication showing one or more candidate cells (125) configured in an inter-cell mobility configuration, for example, an L1 / L2 inter-cell mobility configuration, - A third indication showing the elapsed time between a first time of reception of an inter-cell mobility configuration, e.g., an L1 / L2 inter-cell mobility configuration, and a second time when a fault, e.g., a radio link fault, is declared. -The third indication further indicates a third elapsed time between the fourth time of reception of the last inter-cell mobility configuration, e.g., L1 / L2 inter-cell mobility configuration, and the second time when a fault, e.g., a radio link fault, was declared. -a) a fourth indication showing at least one of the first position information in the fourth time and b) the second position information in the second time, A method that includes at least one of the following.

[0333] Example 12. The method described in Example 11, - The first indication is shown by the reest-L1L2Candidate information element (IE), - The first indication further shows additional L1 / L2 mobility-related measurements, - The first indication, including additional L1 / L2 mobility-related measurements, is shown in reest-L1L2meas IE, - The first indication, including additional L1 / L2 mobility-related measurements, is shown in reConnect-L1L2meas, - The second indication is shown in candidate-L1L2Mobility IE, - The second indication is shown by the candidate-L1L2flag flag, - The second indication is to show additional L1 / L2 mobility-related measurements, - The second indication, including additional L1 / L2 mobility-related measurements, will be shown in candidate-L1L2meas IE, - The third indication will be shown in a separate IE, -The fourth indication will be shown in yet another IE, A method that is at least one of the following.

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

[0335] Example 14. The method described in Example 13, -a) The re-establishment procedure is performed after the radio device (130) has entered idle mode following the failed mobility procedure, or -b) A method for reconnecting a wireless device (130) to, for example, a (third) network node (113) if the re-establishment procedure fails.

[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), and the method further, After reconnecting, from the wireless device (130), i. A fifth indication showing whether the second cell (124) selected by the wireless device (130) for a reconnection procedure triggered by a failed re-establishment procedure was a candidate cell in the inter-cell mobility configuration received in a previous indication, ii. A sixth indication showing the elapsed time between the first time of reception of an inter-cell mobility configuration, for example, an L1 / L2 inter-cell mobility configuration, and the fifth time of reconnection due to the selection of the second cell (124), A method comprising receiving at least one of (806).

[0337] Example 16. The method described in Example 15, wherein the fifth indication is shown by reConnect-L1L2Candidate IE.

[0338] Example 17. A method according to any one of Examples 9 to 16, wherein the method further comprises: -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 in an inter-cell mobility configuration, for example, an L1 / L2 inter-cell mobility configuration, iii. The period during which the wireless device (130) was configured in an inter-cell mobility configuration, for example, an L1 / L2 inter-cell mobility configuration, before the failure occurred. For example, determining one or more characteristics of the selected inter-cell mobility configuration (803), -Based on the determination result, initiate (804) the application of one or more steps of the inter-cell mobility configuration, for example, the L1 / L2 inter-cell mobility configuration, such as candidate cell selection, mobility procedure trigger threshold, and L3 mobility parameter. - Based on the adaptation, send an updated inter-cell mobility configuration, e.g., an L1 / L2 inter-cell mobility configuration, which includes one or more adapted procedures (805), A method that includes at least one of the following.

[0339] Example 18. The method described in Example 17, further comprising... - The condition that the first cell (123) was not a candidate cell in the inter-cell mobility configuration means, for example, adding the first cell (123) to the list of candidate cells in the inter-cell mobility configuration for a cell in which a failed mobility procedure was detected, such as a device connected to a PCell. - The condition that the measurement results indicate that the first candidate cell (126) has better measurement results, the adaptation includes triggering a mobility procedure to the first candidate cell (126), - The condition that the measurement results indicate that the first candidate cell (126) has a poor measurement result means that the adaptation includes removing the first candidate cell (126) from one or more candidate cells (125), - The measurement results indicate that the first adjacent cell (127) has good measurement results, and under the condition that the first adjacent cell (127) is not a candidate cell in the inter-cell mobility configuration, the adaptation is to add the first adjacent cell (127) to the list of candidate cells in the inter-cell mobility configuration. A method that includes at least one of the following.

[0340] Further expansion and variations

[0341] Figure 9 shows examples of communication systems 900 according to several embodiments.

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

[0343] In relation to Figures 9, 10, and 11 described below, each UE is an example of the wireless device 130, and it can be understood that any description provided for UE 912 or UE 1106 applies equally to the wireless device 130. Similarly, each network node is an example of the third network node 113 or network node 113, and it can be understood that any description provided for either network node 910 or network node 1104 applies equally to the third network node 113 or network node 113. Furthermore, the communication system 900 is an example of the wireless communication network 100, and it can be understood that any description provided for the communication system 900 applies equally to the wireless communication network 100.

[0344] Exemplary wireless communication on a wireless connection includes transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for carrying information without using wires, cables, or other physical conductors. Furthermore, in various embodiments, the communication system 900 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that can facilitate or participate in the communication of data and / or signals, whether wired or wireless. The communication system 900 may include and / or interface with any type of communication, telecommunications, data, cellular, wireless network, and / or other similar types of systems.

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

[0346] In the illustrated example, the core network 906 connects network node 910 to one or more hosts, such as host 916. These connections may be direct or indirect, via one or more intermediate networks or devices. In other examples, network nodes may be directly connected to hosts. The core network 906 includes one or more core network nodes (e.g., core network node 908) structured with hardware and software components. The functions of these components may be substantially the same as those described for the UE, network nodes, and / or hosts, and therefore those descriptions are generally applicable to the corresponding components of core network node 908. An exemplary core network node includes one or more of the following functions: Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier Decryption Function (SIDF), Unified Data Management (UDM), Security Edge Protected Proxy (SEPP), Network Exposure Function (NEF), and / or User Plane Function (UPF).

[0347] Host 916 may be owned by or under the control of a service provider other than the operator, or a provider of the access network 904 and / or the telecommunications network 902, and may be operated by or on behalf of such service provider. Host 916 may host a variety of applications and provide one or more services. Examples of such applications include live and pre-recorded audio / video content, data acquisition services such as acquisition and editing of data on a variety of ambient conditions detected by multiple UEs, analytical functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for alarm and monitoring centers, or any other such functions performed by a server.

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

[0349] In some cases, the telecommunications network 902 is a cellular network that implements functions standardized by 3GPP®. Therefore, the telecommunications network 902 may support network slicing to provide various logical networks to various devices connected to the telecommunications network 902. For example, the telecommunications network 902 may provide ultra-high reliability low latency communication (URLLC) services to some UEs while providing extended mobile broadband (eMBB) services to other UEs, and may also provide massive machine type communication (mMTC) / massive IoT services to further UEs.

[0350] In some examples, UE912 is configured to transmit and / or receive information without direct human interaction. For example, the UE may be designed to transmit information to access network 904 on a predetermined schedule, triggered by internal or external events, or in response to a request from access network 904. Additionally, the UE may be configured to operate in single or multi-RAT, or multi-standards mode. For example, the UE may be configured to operate in any one or a combination of Wi-Fi, NR (New Radio), 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., UE912c 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 and analytics, or any other communication device described herein with respect to the UE. For example, the hub 914 may be a broadband router that enables the UE to access the core network 906. In another example, the hub 914 may be a controller that sends commands or instructions to one or more actuators within the UE. Commands or instructions may be received from the UE or network node 910, or accepted by executable code, scripts, processes, or other instructions within the hub 914. In yet another example, the hub 914 may be a data collector that acts as temporary storage for the UE's data, and in some embodiments, it may perform analysis or other processing of that data. In yet another example, the hub 914 may be a content source. For example, with respect to a UE that is a VR headset, display, loudspeaker, or other media delivery device, the hub 914 may acquire media or data related to VR assets, video, audio, or other sensory information via network nodes, in which case the hub 914 provides it to the UE either directly, after performing local processing, and / or after adding additional local content. In another example, the hub 914 acts as a proxy server or orchestrator for the UE, in particular when one or more of the UEs are low-energy IoT devices.

[0352] Hub 914 may have a steady / persistent or intermittent connection to network node 910b. Furthermore, hub 914 may enable different communication methods and / or schedules between hub 914 and UEs (UE912c and / or 912d), and between hub 914 and the core network 906. In another example, hub 914 is connected to the 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 on the access network 904 and / or to other UEs via a direct connection. In some scenarios, a UE may establish a wireless connection with network node 910 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 communication between UEs and network node 910b. In other embodiments, the hub 914 may be a non-dedicated hub, i.e., a device capable of routing communication between the UE and the network node 910b, but also capable of acting as a source and / or destination for some data channel.

[0353] Figure 10 is a block diagram of a host 1000 that may be an embodiment of host 916 in Figure 9, relating to the various aspects described herein. Where used herein, host 1000 may be, or include, a variety of hardware and / or software, including standalone servers, blade servers, cloud-implemented servers, distributed servers, virtual machines, containers, or processing resources within a server farm. Host 1000 may provide one or more services to one or more UEs.

[0354] The host 1000 includes a processing circuit 1002 operably connected to an input / output interface 1006 via a bus 1004, a network interface 1008, a power supply 1010, and memory 1012. In other embodiments, other components may be included. The functions of these components may be substantially the same as those described with respect to the devices of the drawings to date, and thus those descriptions are generally applicable to the corresponding components of the 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 the UE for the host 1000 or data generated by the host 1000 for the UE. Embodiments of the host 1000 may utilize only a subset or all of the illustrated components. The host application program 1014 may be implemented in a container-based architecture and may provide support for video codecs (VVC (Versatile Video Coding), HEVC (High Efficiency Video Coding), AVC (Advanced Video Coding), MPEG, VP9) and audio codecs (e.g., FLAC, AAC (Advanced Audio Coding), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, head-up display systems). Furthermore, the host application program 1014 may provide user authentication and license checks, and may periodically report health, route, and content availability to central nodes such as devices within or at the edge of the core network. Thus, 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), Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), and MPEG-DASH (Dynamic Adaptive Streaming over HTTP).

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

[0357] Similar to host 1000, embodiments of host 1102 include hardware such as a communication interface, processing circuitry, and memory. Host 1102 further includes software stored within or accessible by host 1102, which is executable by the processing circuitry. This software may include a host application that can operate to provide services to remote users, such as UE 1106, connected via an over-the-top (OTT) connection 1150 extending between UE 1106 and host 1102. While providing services to remote users, the host application may provide user data transmitted using the OTT connection 1150.

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

[0359] UE1106 includes hardware and software stored within or accessible by UE1106, which is executable by the UE's processing circuitry. This software may include a client application, such as a web browser or a service provider-specific “app,” which, with the support of host 1102, may operate to provide services to human or non-human users via UE1106. On host 1102, a running host application can communicate with a running client application via an OTT connection 1150 terminating at UE1106 and host 1102. While providing services to a user, the UE's client application may receive request data from the host's host application and provide user data in response to that request data. The OTT connection 1150 may transfer both the request data and the user data. The UE's client application may interact with the user to generate user data that it provides to the host application via the OTT connection 1150.

[0360] The OTT connection 1150 extends via connection 1160 between host 1102 and network node 1104, and via wireless connection 1170 between network node 1104 and UE 1106, and may provide connectivity between host 1102 and UE 1106. To illustrate the communication between host 1102 and UE 1106 via network node 1104, without any explicit reference to any intermediate devices and the precise routing of messages through those devices, the connections 1160 and wireless connection 1170, which may be provided by the OTT connection 1150, are depicted abstractly.

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

[0362] In some examples, UE1106 runs a client application, thereby providing user data destined for host 1102. User data may be provided in reaction to or in response to receiving data from host 1102. Accordingly, in step 1116, UE1106 may provide user data, which may be done by running a client application. While providing user data, the client application may further consider user input received from the user via the input / output interface of UE1106. Regardless of the specific way in which the user data is provided, in step 1118, UE1106 initiates transmission of the user data to host 1102 via network node 1104. In step 1120, in accordance with the teachings of the embodiments described through this disclosure, network node 1104 receives user data from UE1106 and initiates transmission of the received user data to host 1102. In step 1122, host 1102 receives the user data carried in the transmission initiated by UE1106.

[0363] One or more different embodiments improve the performance of OTT services provided to UE 1106 by using an OTT connection 1150 in which the wireless 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, Host 1102 may collect and analyze factory status information. In another example, Host 1102 may process audio and video data, which may be acquired from the UE, for use in generating maps. In yet another example, Host 1102 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., traffic light control). In yet another example, Host 1102 may store surveillance video uploaded by the UE. In yet another example, Host 1102 may store or control access to media content such as video, audio, VR, or AR that can be broadcast, multicast, or unicast to the UE. In yet another example, 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., editing diagrams from data collected from remote devices), or any other function of collecting, acquiring, storing, analyzing, and / or transmitting data.

[0365] In some examples, measurement procedures may be provided for the purpose of monitoring data rate, latency, and other factors that may be improved by one or more embodiments. Furthermore, there may be optional network functions for reconfiguring the OTT connection 1150 between host 1102 and UE 1106 in response to variations in the measurement results. The measurement procedures and / or network functions for reconfiguring the OTT connection may be implemented in the software and hardware of host 1102 and / or UE 1106. In some embodiments, sensors (not shown) through which the OTT connection 1150 passes may be deployed in or associated with other devices, and these sensors may participate in the measurement procedures by supplying numerical values ​​of the monitoring results exemplified above or values ​​of other physical quantities, from which the monitored quantities may be calculated or estimated by software. Reconfiguration of the OTT connection 1150 may include message formatting, retransmission settings, preferred routing, etc., and such reconfiguration does not need to directly change the operation of network node 1104. Such procedures and functionalities may be known or in practice in the art. In one embodiment, the measurement may include proprietary UE signaling that facilitates the measurement of throughput, propagation time, and delay by the host 1102. The measurement may be implemented by the software monitoring propagation time, errors, etc., while sending messages that are specifically empty or "dummy" messages using the OTT connection 1150.

[0366] Embodiments of the wireless device 130 are related to Figures 3, 5, 7, 9, and 11.

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

[0368] The wireless device 130 may include an interface unit to facilitate communication between the wireless device 130 and other nodes or devices, such as a third network node 113 or network node 113, hosts 916, 1000, 1102, or any other node. In some specific examples, the interface may include, for example, a transceiver configured to send and receive wireless signals via an air interface in accordance with a suitable standard.

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

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

[0371] The third network node 113 or network node 113 may include an interface unit to facilitate 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, hosts 916, 1000, 1102, or any other node. In some specific examples, the interface may include, for example, a transceiver configured to send and receive radio signals over an air interface in accordance with a suitable standard.

[0372] Further numbered embodiments

[0373] 1. A host configured to operate in a communication system to provide over-the-top (OTT) services, A processing circuit configured to provide user data, It comprises a network interface configured to initiate the transmission of user data to network nodes of a cellular network for transmission to a user device (UE), A network node comprises a communication interface and a processing circuit, the processing circuit of the network node being configured to perform one or more actions described herein when performed by a third network node 113 or network node 113, a host.

[0374] 2. The host of the previous embodiment, The host processing circuit is configured to run a host application that provides user data. The UE is a host that includes processing circuitry configured to run client applications associated with a host application, which receive user data transmitted from the host.

[0375] 3. A method performed on a host configured to operate in a communication system further including network nodes and user equipment (UEs), Providing UE user data, A method comprising initiating a transmission that carries user data to a UE via a cellular network including network nodes, wherein the network nodes perform one or more actions performed by a third network node 113 or by network node 113 as described herein.

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

[0377] 5. A method according to either of the two embodiments described above, User data is provided on the host by running a host application that interacts with a client application running on the UE, and the client application is associated with the host application.

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

[0379] 7. A communication system as described in the previous embodiment, further, Network nodes, and / or A communication system, including user equipment.

[0380] 8. A communication system according to the preceding two embodiments, The host processing circuit is configured to run the host application, thereby providing user data. A communication system in which a host application is configured to interact with client applications running on the UE, and the client applications are associated with the host application.

[0381] 9. A host configured to operate in a communication system that provides over-the-top (OTT) services, A processing circuit configured to start receiving user data, A host comprising a network interface configured to receive user data from network nodes of a cellular network, wherein the network node comprises a communication interface and processing circuitry, and the processing circuitry of the network node is configured to perform one or more actions performed by a third network node 113 or network node 113 as described herein.

[0382] 10. The host of the previous two embodiments, The host processing circuit is configured to run the host application, thereby providing user data. The host application is configured to interact with client applications running on the UE, and the client applications are associated with the host application.

[0383] 11. A host according to either of the preceding two embodiments, Initiating the reception of user data involves the host requesting user data.

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

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

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

[0387] 15. A host of the previous embodiment, The cellular network further includes a host, and network nodes configured to communicate with the UE in order to send user data from the host to the UE.

[0388] 16. The host of the previous two embodiments, The host processing circuit is configured to run the host application, thereby providing user data. The host application is configured to interact with client applications running on the UE, and the client applications are associated with the host application.

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

[0390] 18. The method of the previous embodiment, further, A method for a host to receive user data from a UE, including running a host application associated with a client application running on the UE.

[0391] 19. The method of the previous embodiment, further, On the host, input data to a client application running on the UE, which is provided by running the host application and includes sending the input data, A method by which 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 that provides over-the-top (OTT) services, A processing circuit configured to utilize user data, It includes a network interface configured to receive user data transmitted to a cellular network for transmission to a user device (UE), The UE comprises a communication interface and processing circuitry, the UE's communication interface and processing circuitry being configured to perform one or more actions described herein when performed by the wireless device 130, the host.

[0393] 21. A host of the previous embodiment, The cellular network further includes network nodes configured to communicate with the UE and send user data from the UE to the host.

[0394] 22. The host of the previous two embodiments, The host processing circuit is configured to run the host application, thereby providing user data. The host application is configured to interact with client applications running on the UE, and the client applications are associated with the host application.

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

[0396] 24. The method of the previous embodiment, further, A method for a host to receive user data from a UE, including running a host application associated with a client application running on the UE.

[0397] 25. The method of the previous embodiment, further, On the host, input data to a client application running on the UE, which is provided by running the host application and includes sending the input data, A method by which 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 enhancement of MIMO functionality in NR, Samsung, 3GPP® TSG RAN Meeting #92e, Electronic Meeting, June 14-18, 2021 2. RP-213565, 3GPP® Work Item Description: Further Functional Enhancement of NR Mobility, MediaTek, 3GPP® TSG RAN Meeting #94e, Electronic Meeting, December 6-17, 2021

[0399] Abbreviations and Explanations CE control element 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 Mastercell Group MN Master Node NR New Radio PCI Physical Cell Identifier RAN (Radio Access Network) RRC (Radio Resource Control) RLF Wireless Link Failure SCG Secondary Cell Group SN Secondary Node UE User Device gNB NR base station CU Central Unit DU Distributed Unit

Claims

1. A method performed by a wireless device (130) for processing re-establishment information after a failure, wherein the wireless device (130) operates on a wireless communication network (100), and the method is In response to a declared failure, the system includes storing one or more indications (304) that indicate the failure, the one or more indications including at least one first indication that 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 for performing an L1 / L2 mobility procedure. The one or more indications mentioned above may further include: A third indication showing the elapsed time between a first time for receiving the inter-cell mobility configuration and a second time for which the failure was declared, a fourth time for receiving the last inter-cell mobility configuration including the first cell (123) selected as a candidate cell for the re-establishment procedure, and a third time for which the failure was declared. a) a fourth indication showing at least one of the first position information in the fourth time and b) the second position information in the second time, A method that includes at least one of the following.

2. The method according to claim 1, The aforementioned failure is a failure in the mobility procedure, The aforementioned failure is one of the following: wireless link failure and handover failure. A method that is at least one of the following.

3. The method according to claim 1, A method wherein the mobility procedure is L1 / L2 cell-to-cell mobility.

4. The method according to claim 1, The above one or more indications are sent in the report, The one or more of the above indications are sent in a UEInformationResponse message, A method that is at least one of the following.

5. The method according to claim 1, A method wherein the inter-cell mobility configuration is an L1 / L2 inter-cell mobility configuration.

6. The method according to claim 1, The one or more indications mentioned above may further include: A method comprising a second indication showing one or more candidate cells (125) configured in the aforementioned inter-cell mobility configuration.

7. The method according to claim 6, The first indication is represented by a 1-bit flag, The first indication is represented by the rest-L1L2Candidate information element (IE), The first indication, which includes additional L1 / L2 mobility-related measurements, is shown as rest-L1L2meas IE, The first indication, which includes additional L1 / L2 mobility-related measurements, is indicated by reConnect-L1L2meas, A method that is at least one of the following.

8. The method according to claim 1, further, Receiving the aforementioned prior indication (301) from the first network node (111), In response to the previously received indication, the L1 / L2 inter-cell mobility procedure (302) is performed from the first network node (111) to the second network node (112) operating on the wireless communication network (100), Declaring the aforementioned fault (303), Execute the re-establishment procedure or reconnection procedure (305) to the third network node (113) operating in the wireless communication network (100), Transmit (306) one of the one or more stored indications to a network node (113) operating on the wireless communication network (100), Based on the one or more indications transmitted, receive (307) an updated inter-cell mobility procedure configuration from the network node (113) that includes one or more adapted procedures, Methods that include...

9. The method according to claim 8, A method for the wireless device (130) to perform the re-establishment procedure after transitioning to idle mode or after a wireless link failure.

10. The method according to claim 9, If the aforementioned re-establishment procedure fails, and the wireless device (130) reconnects to the network node (113) and the saving (304) is further, - 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, - A sixth indication showing the elapsed time between the first time of receiving the inter-cell mobility configuration and the fifth time of reconnection due to the selection of the second cell (124), A method that includes saving at least one of the following.

11. The method according to claim 10, The fifth indication is a method shown in reConnect-L1L2Candidate IE.

12. A method performed by a network node (113) operating in a wireless communication network (100) for processing re-establishment information after a failure in a wireless device (130), - Receiving (402) one or more indications from the wireless device (130) indicating the fault, the one or more indications including at least one first indication indicating whether a first cell (123) selected by the wireless device (130) for a re-establishment procedure triggered by the fault was a candidate cell in an inter-cell mobility configuration received by the wireless device (130) in a previous indication for performing an L1 / L2 mobility procedure. The one or more indications mentioned above may further include: A third indication showing the elapsed time between a first time for receiving the inter-cell mobility configuration and a second time for which the failure was declared, a fourth time for receiving the last inter-cell mobility configuration including the first cell (123) selected as a candidate cell for the re-establishment procedure, and a third time for which the failure was declared. a) a fourth indication showing at least one of the first position information in the fourth time and b) the second position information in the second time, A method that includes at least one of the following.

13. The method according to claim 12, The aforementioned failure is a failure in the mobility procedure, The aforementioned failure is one of the following: wireless link failure and handover failure. A method that is at least one of the following.

14. The method according to claim 12, A method wherein the mobility procedure is L1 / L2 cell-to-cell mobility.

15. The method according to claim 12, The fact that one or more of the above indications are received in the report, The fact that one or more of the above indications are received in a UEInformationResponse message, A method that is at least one of the following.

16. The method according to claim 12, A method wherein the inter-cell mobility configuration is an L1 / L2 inter-cell mobility configuration.

17. The method according to claim 12, The one or more indications mentioned above may further include: - A method comprising a second indication showing one or more candidate cells (125) configured in the inter-cell mobility configuration.

18. The method according to claim 17, The first indication is represented by a 1-bit flag, The first indication is represented by the rest-L1L2Candidate information element (IE), The first indication, which includes additional L1 / L2 mobility-related measurements, is shown as rest-L1L2meas IE, The first indication, which includes additional L1 / L2 mobility-related measurements, is indicated by reConnect-L1L2meas, A method that is at least one of the following.

19. The method according to claim 12, further, A method comprising performing the re-establishment or reconnection procedure (401) with the wireless device (130), wherein one or more indications are received after the re-establishment procedure has been performed.

20. The method according to claim 19, The re-establishment procedure is performed after the wireless device (130) has entered idle mode following the failed mobility procedure.

21. A method according to claim 20, wherein the re-establishment procedure fails and the wireless device (130) reconnects to the network node (113), and the method further, After reconnection, the wireless device (130) will receive the following message: i. 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, ii. A sixth indication showing the elapsed time between the first time of receiving the inter-cell mobility configuration and the fifth time of reconnection due to the selection of the second cell (124), A method comprising receiving (406) at least one of the following.

22. The method according to claim 21, The fifth indication is a method shown in reConnect-L1L2Candidate IE.

23. The method according to claim 12, The above method further, Based on the one or more indications received, 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 period during which the wireless device (130) was configured in the inter-cell mobility configuration before the aforementioned failure occurred, Determining one or more characteristics of the inter-cell mobility configuration selected from (403), Based on the result of the determination, the process of applying one or more steps of the inter-cell mobility configuration is initiated (404), Based on the above adaptation, transmit (405) an updated inter-cell mobility configuration including the adapted one or more steps, Methods that include...

24. The method according to claim 23, The adaptation includes adding the first cell (123) to the list of candidate cells for the inter-cell mobility configuration, provided that the first cell (123) was not a candidate cell for the inter-cell mobility configuration. The adaptation includes triggering a mobility procedure to the first candidate cell (126) on the condition that the measurement results indicate that the first candidate cell (126) has better measurement results, The above includes, on the condition that the measurement results indicate that the first candidate cell (126) has poor measurement results, removing the first candidate cell (126) from one or more candidate cells (125), The adaptation includes adding the first adjacent cell (127) to the list of candidate cells for the inter-cell mobility configuration, provided that the measurement results indicate that the first adjacent cell (127) has good measurement results and the first adjacent cell (127) is not a candidate cell for the inter-cell mobility configuration. A method that is at least one of the following.

25. A wireless device (130) for processing re-establishment information after a failure, wherein the wireless device (130) is configured to operate on a wireless communication network (100), and the wireless device (130) further... Configured to store one or more indications configured to indicate a declared fault, wherein the one or more indications include at least one 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 fault, was a candidate cell in an inter-cell mobility configuration configured to be received in a previous indication for performing an L1 / L2 mobility procedure. The one or more indications mentioned above may further include: A third indication showing the elapsed time between a first time for receiving the inter-cell mobility configuration and a second time for which the failure was declared, a fourth time for receiving the last inter-cell mobility configuration including the first cell (123) selected as a candidate cell for the re-establishment procedure, and a third time for which the failure was declared. a) a fourth indication showing at least one of the first position information in the fourth time and b) the second position information in the second time, A wireless device configured to include at least one of the following.

26. A wireless device (130) according to claim 25, A wireless device adapted to perform the method described in any one of claims 2 to 11.

27. A network node (113) configured to operate in a wireless communication network (100) for processing re-establishment information after a failure in a wireless device (130), The aforementioned network node (113) further, - The wireless device (130) is configured to receive one or more indications configured to indicate the fault, and the one or more indications include at least one 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 fault, was a candidate cell in an inter-cell mobility configuration configured to be received by the wireless device (130) in a previous indication for performing an L1 / L2 mobility procedure. The one or more indications mentioned above may further include: A third indication showing the elapsed time between a first time for receiving the inter-cell mobility configuration and a second time for which the failure was declared, a fourth time for receiving the last inter-cell mobility configuration including the first cell (123) selected as a candidate cell for the re-establishment procedure, and a third time for which the failure was declared. a) a fourth indication showing at least one of the first position information in the fourth time and b) the second position information in the second time, A network node configured to include at least one of the following.

28. A network node (113) according to claim 27, A network node adapted to perform the method described in any one of claims 13 to 24.

Images