Method and device for predicting and recovering wireless link problem in mobile communication in advance

By predicting and recovering wireless link problems in mobile communications, the problem of too long service interruption time during traditional RLF recovery is solved, and faster and more reliable link recovery is achieved.

CN118945696APending Publication Date: 2024-11-12MEDIATEK SINGAPORE PTE LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410523843.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-05-12
Filing Date
2024-04-28
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

In mobile communications, traditional wireless link failure recovery processes may result in service interruption times too long because link problems cannot be recovered in a short period of time, especially when downlink failures or uplink random access fails.

Method used

The user equipment (UE) performs wireless link problem prediction before the RLF occurs and sends a measurement report to the network node based on the prediction results, deciding whether to perform an early recovery process, including handover or reconstruction, to avoid RLF.

Benefits of technology

It effectively reduces the time of service interruption before wireless link failure recovery, improves the speed and reliability of link recovery, and avoids long-term service interruption caused by RLF.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118945696A_ABST
    Figure CN118945696A_ABST
Patent Text Reader

Abstract

Various solutions are described for radio link (RL) problem prediction for user equipment and network nodes in mobile communications. A device may perform radio link failure (RLF) problem prediction according to a device context to generate a pre-result prior to an occurrence of an RL failure. The apparatus may determine whether to perform an RL problem early recovery based on the prediction result.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention generally relates to mobile communications, and more particularly to prediction and early recovery of radio link (RL) problems between user equipment (UE) and network equipment in mobile communications. Background Art

[0002] Unless otherwise indicated in this section, the approaches described in this section are not prior art to the claims listed below and are not admitted to be prior art by inclusion in this section.

[0003] In mobile communications, when a radio link failure (RLF) occurs, an RLF recovery process is performed between the UE and the network node. However, in the traditional RLF recovery process, when the reestablishment process is performed for the RLF, the link problem may have occurred for a long time, that is, the radio link problem cannot be recovered in a short time. Therefore, the service may be interrupted for a long time before the reestablishment is performed for the RLF.

[0004] For example, for a downlink (DL) RLF, the reestablishment procedure will not be performed until the timer T310 expires. Therefore, a radio link problem (e.g., out of synchronazition) may have occurred for a long time before the timer T310 expires. In another example, for an uplink (UL) RLF, the reestablishment procedure will not be performed until a default number of random access (RA) attempts have been performed. Therefore, a radio link problem may have occurred for a long time before the maximum number of RA attempts is reached.

[0005] Therefore, how to restore the wireless link problem earlier may be an important issue for newly developed wireless communication systems. Therefore, it is necessary to provide appropriate solutions and designs to solve this problem. Summary of the invention

[0006] The following summary is illustrative only and is not intended to be limiting in any way. That is, the following summary is provided to introduce the concepts, highlights, benefits and advantages of the novel and non-obvious technology described in the present invention. Selected embodiments are further described in the detailed description below. Therefore, the following summary is not intended to identify essential features of the claimed subject matter, nor is it intended to be used to determine the scope of the claimed subject matter.

[0007] An object of the present invention is to propose solutions, concepts, designs, systems, methods and devices for predicting and recovering RL problems related to user equipment and network equipment in mobile communications. It is believed that by implementing one or more of the proposed solutions described in the present invention, the problems described above will be avoided or otherwise alleviated.

[0008] In one aspect, a method may include a device performing RL problem prediction according to a device context to generate a prediction result before RLF occurs. The method may also include the device determining whether to perform RL early recovery based on the prediction result.

[0009] In another aspect, a method may include a network node receiving a measurement report with a prediction result of an RL problem prediction from a UE. The method may also include the network node determining whether to respond to the measurement report based on the prediction result.

[0010] It is worth noting that although the description provided herein may be in the context of certain radio access technologies, networks and network topologies such as the fifth generation (5G), 4GEPS mobile networks, the concepts, schemes and any variants / derivatives thereof may be implemented, applied and used in, for example, but not limited to, Ethernet, Universal Terrestrial Radio Access Network (UTRAN), E-UTRAN, Global System for Mobile communications (GSM), General Packet Radio Service (GPRS) / Enhanced Data rates for Global Evolution (EDGE) radio access network (GERAN), Long-Term Evolution (LTE), LTE-Advanced, LTE-Advanced Pro, Internet of Things, Industrial Internet of Things (IIoT), Narrow Band Internet of Things (NB-IoT), other types of radio access technologies, networks and network topologies of the sixth generation (6G) and any future developed network technologies. Therefore, the scope of the present invention is not limited to the examples described herein. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The accompanying drawings are included to provide a further understanding of the present invention and are incorporated into and constitute a part of this invention. The accompanying drawings illustrate embodiments of the present invention and together with the description are used to explain the principles of the present invention. It should be noted that the accompanying drawings are not necessarily drawn to scale, as some components may be shown out of scale in actual implementations in order to clearly illustrate the concepts of the present invention.

[0012] Figure 1 is a diagram depicting an example scenario of a communication environment in which various solutions and approaches according to the present invention may be implemented.

[0013] Figure 2 is a diagram describing an example scenario of a measurement process for RL problem prediction according to an embodiment of the present invention.

[0014] Figure 3 FIG. 4 is a diagram for describing an example scenario of an early recovery process under a first proposed solution according to an embodiment of the present invention.

[0015] Figure 4 FIG. 4 is a diagram for describing an example scenario of an early recovery process under a second proposed solution according to an embodiment of the present invention.

[0016] Figure 5 is a diagram describing an example flow of an early recovery process according to an embodiment of the present invention.

[0017] Figure 6 FIG. 4 is a diagram for describing an example scenario of an early recovery process under the third proposed solution according to an embodiment of the present invention.

[0018] Figure 7 is a diagram describing an example scenario of a prediction result according to an embodiment of the present invention.

[0019] Figure 8 is a diagram for describing another example of a prediction result according to an embodiment of the present invention.

[0020] Fig. 9 is a diagram for describing another example of a prediction result according to an embodiment of the present invention.

[0021] Fig.10 is a diagram describing an example scenario of early recovery of a DL RL problem through switching according to an embodiment of the present invention.

[0022] Fig.11 is a diagram describing an example scenario of early recovery of UL RL problems through switching according to an embodiment of the present invention.

[0023] Fig.12 is a diagram describing an example scenario of early recovery of a DL RL problem through reconstruction according to an embodiment of the present invention.

[0024] Fig.13 is a diagram describing an example scenario of early recovery of UL RL problems through reconstruction according to an embodiment of the present invention.

[0025] Fig.14 is a block diagram of an example communication system according to one embodiment of the present invention.

[0026] Fig.15 is an example process diagram according to one embodiment of the present invention.

[0027] Fig.16 is an example process diagram according to another embodiment of the present invention. DETAILED DESCRIPTION

[0028] The present invention discloses detailed embodiments and implementations of the claimed subject matter. However, it should be understood that the disclosed embodiments and implementations are merely illustrations of the claimed subject matter that may be embodied in various forms. However, the present invention may be embodied in many different forms and should not be construed as being limited to the exemplary embodiments and implementations set forth herein. On the contrary, these exemplary embodiments and implementations are provided to make the description of the present invention thorough and complete, and will fully convey the scope of the present invention to those skilled in the art. In the following description, details of well-known features and technologies may be omitted to avoid unnecessary confusion of the presented embodiments and implementations.

[0029] Overview

[0030] Embodiments according to the present invention relate to various technologies, methods, schemes and / or solutions for predicting and recovering RL problems in advance for user equipment and network equipment in mobile communications. According to the present invention, many possible solutions can be implemented individually or in combination. That is, although these possible solutions may be described separately below, two or more of these possible solutions can be implemented in one or another combination.

[0031] Figure 1An example scenario 100 of a communication environment is shown in which various solutions and schemes according to the present invention may be implemented. Scenario 100 includes UE 110 wirelessly communicating with a network 120 (e.g., a wireless network including a non-terrestrial network (NTN) and a terrestrial network (TN)) via a terrestrial network node 125 (e.g., an evolved Node-B (eNB), a Next Generation Node-B (gNB), or a transmission / reception point (TRP)) and / or a non-terrestrial network node 128 (e.g., a satellite). For example, the terrestrial network node 125 and / or the non-terrestrial network node 128 may form an NTN serving cell for wirelessly communicating with the UE 110. In some embodiments, UE 110 may be an IoT device, such as a NB-IoT UE or an enhanced machine-type communication (eMTC) UE (e.g., a bandwidth reduced low complexity (BL) UE or a coverage enhancement (CE) UE). In such a communication environment, as described below, UE 110, network 120, ground network node 125, and non-ground network node 128 may implement various schemes for RL problem prediction according to the present invention. It is worth noting that although various proposed schemes may be described separately or separately, in actual implementation, some or all of the proposed schemes may be used in combination or implemented in other ways. Of course, each proposed scheme may be used separately or separately or implemented in other ways.

[0032] According to an embodiment of the present invention, a UE (e.g., UE 110) may perform RL problem prediction according to a device context to generate a prediction result before RLF occurs. The UE may then send a measurement report with the prediction result to a network node (e.g., ground network node 125 or non-ground network node 128) of a wireless network (e.g., network 120).

[0033] RL problems may include at least one of DL desynchronization, radio link control (RLC) retransmission failure, and UL random access (RA) procedure failure. The UL RA procedure may occur during a connection establishment procedure, a handover procedure, a reestablishment procedure, or other connected state RA procedures.

[0034] The UE can predict whether RLF may occur before the RLF actually occurs based on the information of the device's historical context. According to an embodiment of the present invention, the device context is the context information of the UE within a recent period of time, which may include at least one of cell measurement results, channel state information, power information, control commands, configuration parameter information, historical resident cell information, device state information and service type.

[0035] The measurement results may include measurement results of the serving cell and the neighboring cell, for example, at least one of the received signal strength indication (RSSI), reference symbol received power (RSRP), reference symbol received quality (RSRQ) and signal to interference plus noise ratio (SINR) of the serving cell and the neighboring cell.

[0036] The channel state information may include a channel quality indicator (CQI), a rank indication (RI), a UL block error rate (BLER) of a physical (PHY) layer, a DL BLER of a PHY layer, the number of retransmissions of a hybrid automatic repeat request (HARQ) of a media access control (MAC) layer, the retransmission rate of HARQ of a MAC layer, the number of retransmissions of a protocol data unit (PDU) of a radio link control (RLC) layer and a packet data convergence protocol (PDCP) layer, the PDU retransmission rate of the RLC layer and the PDCP layer, and at least one of a PDU packet loss rate of the RLC layer and the PDCP layer.

[0037] The power information may include terminal transmission power information, for example, at least one of real-time terminal transmission power, a maximum value of terminal transmission power, and power headroom rate (PHR) information.

[0038] The control command or configured parameter information may include time advance (TA), transmission power control (TPC) command information, modulation and coding scheme (MCS), scheduling of multiple-input multi-output (MIMO) layers, time and frequency resource allocation (for example, the number of allocated resource blocks (RBs), the number of UL authorizations, etc.), cell selection and cell reselection parameters, and other information that can be used to improve the prediction accuracy (for example, RSRP, RSRQ, SINR, BLER of the signal received by the network, the load of the current serving cell (for example, the number of UEs accessing the serving cell), etc.) at least one.

[0039] The historical resident cell information may include a public land mobile network (PLMN) ID, a tracking area code (TAC), a cell ID, a radio access technology (RAT), a frequency, a physical cell identity (PCI), the order and time period of the resident cells, and the reason for triggering the UE to switch cells (for example, normal switching, reestablishment to a new cell after RLF, UE-triggered early switching, UE-triggered early reconstruction, inability to provide sufficient radio resources for the current service, etc.).

[0040] The status information of the device may include at least one of speed, temperature, voltage, interference from other wireless devices, and the location of the UE (indoors, outdoors, high-speed railway, basement, tunnel, etc.).

[0041] The service type may include the service that the UE is performing (eg, voice call, streaming media, online game) and the required quality of service (QoS).

[0042] According to an embodiment of the present invention, the UE may perform RL problem prediction using at least one of a rule-based algorithm, a machine learning (ML) algorithm, a deep learning (DL) algorithm, and an artificial intelligence (AI) algorithm.

[0043] Figure 2An example scenario 200 of a measurement process for RL problem prediction according to an embodiment of the present invention is shown. Scenario 200 includes a UE and a network node (e.g., a (macro / micro) base station) of a serving cell, which may be part of a wireless network (e.g., an LTE network, a 5G / NR network, an IoT, or a 6G network). Figure 2 In step S210, the UE may send capability information to the network node to indicate whether the UE supports RL problem prediction. For example, the UE may send capability information to the network node via a UECapabilityInformation message. When the UECapabilityInformation message includes a parameter support_RL_Problem_Prediction whose value is set to "true", it may indicate that the UE may support RL problem prediction.

[0044] In step S220, the UE may receive a measurement configuration from the network node. The measurement configuration may configure a measurement report. For example, the UE may receive the measurement configuration via an RRCReconfiguration message. When the RRCReconfiguration message includes a parameter include_RL_Problem_Prediction_result whose value is set to "true", it may indicate that a prediction result may be included in the measurement report.

[0045] In step S230 , the UE may perform RL problem prediction according to the device context to generate a prediction result before the RLF occurs.

[0046] In step S240, the UE may send a measurement report with the prediction result to the network node.

[0047] In step S250, the network node may decide whether to send a handover command to the UE based on the prediction result. For example, when the prediction result indicates that RLF will not occur or the possibility of suffering from RL problems is low, the network node may suspend the handover command to reduce unnecessary handovers. In another example, when the prediction result indicates that RL problems will occur or the possibility of UE suffering from RL problems is high, the network node may send a configuration with a handover command (e.g., RRCReconfiguration with a handover or conditional handover command) to the UE to start an early recovery process to avoid possible RLF. Then, the UE may switch to the target cell according to the handover command.

[0048] Figure 3An example scenario 300 of an early recovery process under a first proposed scheme according to an embodiment of the present invention is shown. Scenario 300 includes a UE, a network node implemented as a serving cell (e.g., a (macro / micro) base station), and a network node implemented as a target cell (e.g., a (macro / micro) base station), which may be part of a wireless network (e.g., an LTE network, a 5G / NR network, an IoT, or a 6G network). Figure 3 , in step S310, the UE predicts that it may suffer from RL problems (i.e., the prediction result indicates that the RL problem will occur or the possibility of the RL problem occurring is high) and determines that it is possible to change the serving cell through handover (e.g., the UE has received a measurement configuration for handover, the UE is not currently performing handover, the UE has measured at least one neighboring cell that meets a predefined signal quality, etc.).

[0049] In step S320, if the serving cell supports RL problem prediction result reporting, the UE may send a measurement report with prediction results to the serving cell, otherwise the UE may send a measurement report without prediction results to the serving cell. Whether the measurement report includes the prediction results depends on whether the network node supports RL problem prediction result reporting (i.e., the measurement configuration may indicate whether the measurement report may include the prediction results).

[0050] In step S330, the UE may receive a handover (HO) command (or a conditional handover (CHO) command) from the serving cell (eg, via an RRCReconfiguration message).

[0051] In step S340, the UE may perform a random access procedure based on the handover command to handover to the target cell, thereby completing early recovery to avoid RLF.

[0052] Figure 4 An example scenario 400 of an early recovery process under a second proposed scheme according to an embodiment of the present invention is shown. Scenario 400 includes a UE, a network node implemented as a serving cell (e.g., a (macro / micro) base station), and a network node implemented as a target cell (e.g., a (macro / micro) base station), which may be part of a wireless network (e.g., an LTE network, a 5G / NR network, an IoT, or a 6G network). Figure 4 In step S410, the UE predicts that it may suffer from RL problems (i.e., the prediction result indicates that RL problems will occur) and determines that it is possible to change the serving cell through handover (e.g., the UE has received measurement configuration for handover, the UE is not currently performing handover, the UE has measured at least one neighboring cell that meets a predefined signal quality, etc.).

[0053] In step S420, the UE may send a measurement report to the serving cell. Whether the measurement report includes the prediction result depends on whether the network node supports RL problem prediction result reporting (ie, the measurement configuration may indicate whether the measurement report may include the prediction result).

[0054] In step S430, the UE fails to receive a handover command (or a CHO command) from the serving cell (eg, the UE fails to receive an RRCReconfiguration message).

[0055] In step S440, the UE predicts that it may suffer from RL problems (i.e., the prediction result indicates that RL problems will occur) and determines that changing the serving cell by handover is not possible (e.g., a timer waiting for the serving cell's response to the measurement report (e.g., with the configuration of a handover command or a conditional handover command) has expired).

[0056] In step S450, the UE may send a reestablishment request (eg, RRCReestablishmentReq) or a connection establishment request (eg, RRCConnectionSetupReq) to the target cell to initiate early recovery to avoid long service interruption. It should be noted that in the second proposal, the target cell may be the same as the serving cell.

[0057] Figure 5 An example process 500 of an early recovery process according to an embodiment of the present invention is shown. Scenario 500 includes a UE, a network node implemented as a serving cell (e.g., a (macro / micro) base station), and a network node implemented as a target cell (e.g., a (macro / micro) base station), which may be part of a wireless network (e.g., an LTE network, a 5G / NR network, an Internet of Things, or a 6G network). In step S510, the UE may initialize a timer (e.g., a protection timer) T guard .

[0058] In step S520, the UE may select a candidate cell group. Specifically, the UE may select one or more candidate cells from the measured neighboring cells to form a candidate cell group according to the measured signal strength and / or signal quality of the neighboring cells. For example, when at least one signal condition of the neighboring cell is satisfied (for example, the RSRP of the neighboring cell is greater than the RSRP threshold, the RSRQ of the neighboring cell is greater than the RSRQ threshold, and the SINR of the neighboring cell is greater than the SINR threshold), the UE may select the neighboring cell as a candidate cell in the candidate cell group.

[0059] In step S530, the UE may select at least one target cell from the candidate cell group. Specifically, the UE may divide the candidate cells in the candidate cell group into different subgroups according to the frequency specified by the measurement object (Measurement Object) (i.e., candidate cells with the same frequency may be in the same subgroup). The UE may then select the candidate cell with the highest signal strength in each subgroup, and the signal strength of the selected candidate cell may be regarded as the signal strength value of its corresponding subgroup. The UE may then sort the subgroups according to their signal strength values. The UE may then select at least one target cell from the subgroup (e.g., according to a traversal rule).

[0060] In step S540, the UE may report the selected one or more target cells in a measurement report. That is, the measurement report may include information of the selected one or more target cells.

[0061] In step S550, the UE may activate the timer T guard , waiting for a response to the measurement report from the network node (eg, a configuration with a handover command or a conditional handover command).

[0062] In step S560, the UE may determine whether the timer T guard A response to the measurement report was received from the network node before expiration.

[0063] In step S570, if a response to the measurement report is received from the network node before the timer expires, the UE may stop the timer T guard , and then the UE can switch to the target cell according to the handover command in the response.

[0064] In step S580, if no response to the measurement report is received from the network node before the timer expires, the UE may trigger early re-establishment, that is, the UE may send a re-establishment request or a connection establishment request to the target cell.

[0065] Figure 6 An example scenario 600 of an early recovery process under the third proposed scheme according to an embodiment of the present invention is shown. Scenario 600 includes a UE and a network node (e.g., a (macro / micro) base station) implemented as a target cell, which may be part of a wireless network (e.g., an LTE network, a 5G / NR network, an IoT network, or a 6G network). Figure 6In step S610, the UE predicts that it may encounter an RL problem (i.e., the prediction result indicates that the RL problem will occur or the possibility of the RL problem occurring is high), and determines that it is impossible to change the serving cell through handover (for example, in the third proposed scheme, the reason is: the network node of the serving cell is not configured with the measurement configuration for handover, or the UE fails to receive a handover command after sending a measurement report to the network node of the serving cell, or the DL BLER or UL BLER is higher than a threshold that causes the UE to be unable to receive a handover command, or the measured neighboring cells do not meet a predetermined signal quality, etc.).

[0066] In step S620, the UE may send a reestablishment request (eg, RRCReestablishmentReq) or a connection establishment request (eg, RRCConnectionSetupReq) to the target cell to initiate early recovery to minimize service interruption before RLF occurs.

[0067] According to an embodiment of the present invention, the prediction result (eg, parameter rl_predict_result) may include at least one Boolean value (eg, true / false or yes / no), one or more levels, and a series of numbers.

[0068] Figure 7 FIG. 7 shows an example scenario 700 of prediction results according to an embodiment of the present invention. Figure 7 , the prediction result is represented by a Boolean value. In one example, the prediction result may be represented by "true" or "false". In step S710, the UE may determine whether the prediction result is "true". In step S720, when the prediction result is "true" (i.e., rl_predict_result = true), the prediction result may indicate that an RL problem will occur, i.e., an early recovery process will be triggered. In step S730, when the prediction result is "false" (i.e., rl_predict_result = false), the prediction result may indicate that an RL problem will not occur, i.e., an early recovery process will not be triggered.

[0069] Figure 8 FIG. 8 is another example scenario 800 of prediction results according to an embodiment of the present invention. Figure 8, the prediction result is represented by one or more levels (e.g., level 0, level 1... level n). A higher level may correspond to a higher probability of occurrence of the RL problem. In step S810, the UE can determine whether the prediction result is higher than or equal to the level threshold LEVEL_TH. In step S820, when the prediction result is higher than or equal to the level threshold LEVEL_TH (i.e., rl_predict_result ≥ LEVEL_TH), the prediction result can indicate that the RL problem will occur, that is, an early recovery process will be triggered. In step S830, when the prediction result is lower than the level threshold LEVEL_TH (i.e., rl_predict_result < LEVEL_TH), the prediction result can indicate that the RL problem will not occur, that is, the early recovery process will not be triggered.

[0070] Fig. 9 Another example scenario 900 of the prediction result according to an embodiment of the present invention is shown. Refer to Fig. 9 , the prediction result is represented by a series of numbers (e.g., 0 to 1.0). This series of numbers can mean the probability of occurrence of the RL problem. In step S910, the UE can determine whether the prediction result is higher than or equal to the numerical threshold TH. In step S920, when the prediction result is higher than or equal to the numerical threshold TH (i.e., rl_predict_result ≥ TH), the prediction result can indicate that the RL problem will occur, that is, an early recovery process will be triggered. In step S930, when the prediction result is lower than the numerical threshold TH (i.e., rl_predict_result < TH), the prediction result can indicate that the RL problem will not occur, that is, the early recovery process will not be triggered.

[0071] Fig.10 An example scenario 1000 of early recovery of DL RL problems by handover according to an embodiment of the present invention is shown. Refer to Fig.10 , when the UE predicts that it will suffer from a DL RL problem, the UE can trigger the early transmission of a measurement report (MR) (i.e., the UE can send a measurement report that may carry the prediction result to a network node), and switch to a better cell (i.e., the target cell) according to the handover command of the network node to avoid RLF. Compared with the traditional solution, the UE does not need to suffer from an out-of-sync problem and does not need to wait for the timer T310 to expire. The UE can switch to a better cell (i.e., the target cell) before RLF occurs. Therefore, service interruption caused by RLF can be avoided.

[0072] Fig.11 An example scenario 1100 of early recovery of UL RL problems by handover according to an embodiment of the present invention is shown. Refer to Fig.11, when the UE predicts that it will suffer from UL RL problems, the UE can trigger the sending of a measurement report in advance (i.e., the UE can send a measurement report that may carry a prediction result to the network node), and switch to a better cell (i.e., the target cell) according to the switching command of the network node to avoid RLF. Compared with the traditional solution, the UE does not need to suffer from UL radio link interruption and does not need to wait for the number of RA attempts to reach the maximum value configured by the network. The UE can switch to a better cell (i.e., the target cell) before RLF occurs. Therefore, service interruption caused by RLF can be avoided.

[0073] Fig.12 FIG. 1200 shows an example scenario 1200 of early recovery of a DL RL problem through a reconstruction process according to an embodiment of the present invention. Fig.12 , when the UE predicts that it will suffer from DL RL problems, the UE can trigger an early reestablishment process (i.e., the UE can send a reestablishment request or a connection establishment request to the target cell) to avoid long service interruption. Compared with the traditional solution, the UE does not need to wait for the timer T310 to expire. The UE can switch to a better cell (i.e., the target cell) before RLF occurs. Therefore, the service interruption before RLF occurs can be minimized.

[0074] Fig.13 FIG. 1300 shows an example scenario of early recovery of UL RL problems through a reestablishment process according to an embodiment of the present invention. Fig.13 , when the UE predicts that it will suffer from UL RL problems, the UE can trigger an early reestablishment process (i.e., the UE can send a reestablishment request or a connection establishment request to the target cell) to avoid long service interruption. Compared with the traditional solution, the UE will not wait for the maximum number of RA attempts. The UE can switch to a better cell (i.e., the target cell) in advance before RLF occurs. Therefore, the service interruption before RLF occurs can be minimized.

[0075] Example Embodiments

[0076] Fig.14 An example communication system 1400 including at least an example communication device 1410 and an example network device 1420 according to an embodiment of the present invention is shown. The communication device 1410 and the network device 1420 can each perform various functions to implement the schemes, techniques, processes and methods for RL problem prediction and early recovery described in the present invention, including the above-mentioned various proposed designs, concepts, schemes and methods and various schemes related to user equipment and network devices in mobile communications, including the above-mentioned scenarios / schemes and the following processes 1500 and 1600.

[0077] The communication device 1410 may be part of an electronic device, which may be a UE such as a portable or mobile device, a wearable device, a wireless communication device, or a computing device. For example, the communication device 1410 may be implemented in a smartphone, a smart watch, a personal digital assistant, a digital camera, or a computing device such as a tablet, a laptop, or a notebook computer. The communication device 1410 may also be part of a machine type device, which may be an IoT, NB-IoT, or IIoT device, such as a fixed or static device, a home device, a wired communication device, or a computing device. For example, the communication device 1410 may be implemented in a smart thermostat, a smart refrigerator, a smart door lock, a wireless speaker, or a home control center. Alternatively, the communication device 1410 may be implemented in the form of one or more integrated-circuit (IC) chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, one or more reduced-instruction set computing (RISC) processors, or one or more complex-instruction-set-computing (CISC) processors. The communication device 1410 may include Fig.14 The communication device 1410 may also include one or more other components not related to the solution proposed by the present invention (e.g., internal power supply, display device and / or user interface device), so for the sake of brevity, these components of the communication device 1410 are not shown in FIG. Fig.14 It is not shown in the figure and is not described below.

[0078] The network device 1420 may be part of a network device, which may be a network node, such as a satellite, a base station, a small base station, a router, or a gateway. For example, the network device 1420 may be implemented in an eNodeB in an LTE network, in a gNB in ​​a 5G / NR, IoT, NB-IoT, or IIoT network, or in a satellite or base station in a 6G network. Alternatively, the network device 1420 may be implemented in the form of one or more IC chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, or one or more RISC or CISC processors. The network device 1420 may include Fig.14 1420, such as processor 1422. Network device 1420 may also include one or more other components not related to the solution proposed by the present invention (e.g., internal power supply, display device and / or user interface device), so for the sake of brevity, these components of network device 1420 are not shown in FIG. Fig.14 It is not shown in the figure and is not described below.

[0079] In one aspect, processor 1412 and processor 1422 can each be implemented in the form of one or more single-core processors, one or more multi-core processors, or one or more CISC processors. That is, even if the singular term "a processor" is used herein to refer to processor 1412 and processor 1422, each processor 1412 and processor 1422 may include multiple processors in some embodiments of the present invention, and may include a single processor in other embodiments. In another aspect, processor 1412 and processor 1422 can each be implemented in the form of hardware (and, optionally, firmware) having electronic components, such as but not limited to, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memory resistors and / or one or more variable capacitors, which are configured and arranged to achieve specific purposes according to the present invention. In other words, in at least some embodiments, each processor 1412 and processor 1422 is a dedicated machine specially designed, arranged and configured to perform a specific task, which includes autonomous reliability enhancement in devices (e.g., represented by communication device 1410) and networks (e.g., represented by network device 1420) in various embodiments of the present invention.

[0080] In some implementations, the communication device 1410 may also include a transceiver 1416 coupled to the processor 1412, capable of wirelessly transmitting and receiving data. In some implementations, the communication device 1410 may further include a memory 1414 coupled to the processor 1412, the processor 1412 being able to access the memory and store data therein. In some implementations, the network device 1420 may also include a transceiver 1426 coupled to the processor 1422, capable of wirelessly transmitting and receiving data. In some implementations, the network device 1420 may further include a memory 1424 coupled to the processor 1422, the processor 1422 being able to access the memory and store data therein. Therefore, the communication device 1410 and the network device 1420 may wirelessly communicate with each other via the transceiver 1416 and the transceiver 1426. For better understanding, the following description of the operations, functions, and capabilities of the communication device 1410 and the network device 1420 is provided in the context of a mobile communication environment in which the communication device 1410 is implemented as or serves as a communication device or user equipment (UE) and the network device 1420 is implemented as or serves as a network node of a communication network.

[0081] In some implementations, the processor 1412 may perform RL problem prediction according to the device context to generate a prediction result before the RLF occurs. The processor 1412 may determine whether to perform RL problem early recovery based on the prediction result.

[0082] In some implementations, if the prediction result indicates that an RL problem will occur and the communication device 1410 believes that it is possible to perform a handover, the processor 1412 may send a measurement report to the network device 1420 via the transceiver 1416 .

[0083] In some implementations, the communication device 1410 considers that handover may be performed when the communication device 1410 has received a measurement configuration for handover and the communication device 1410 is not currently performing handover, and the communication device 1410 has measured at least one neighboring cell that meets a predefined signal quality.

[0084] In some implementations, whether the measurement report includes the prediction result depends on whether the network node supports RL problem prediction result reporting.

[0085] In some implementations, processor 1412 may send capability information to network device 1420 via transceiver 1416 to indicate whether the device supports RL problem prediction. Processor 1412 may receive measurement configuration from network device 1420 via transceiver 1416.

[0086] In some implementations, the processor 1412 may receive a configuration with a handover command from the network device 1420 via the transceiver 1416. The processor 1412 may handover to the target cell according to the handover command.

[0087] In some implementations, RL problem prediction may be performed using at least one of a rule-based algorithm, an ML algorithm, a deep learning (DL) algorithm, and an AI algorithm.

[0088] In some implementations, the prediction result can be represented as at least one of a Boolean value, one or more levels, and a series of numbers.

[0089] In some implementations, the device context is context information of the device within a recent period of time, which may include cell measurement results, channel state information, power information, control commands, configuration parameter information, historical resident cell information, status information of the communication device 1410, and at least one of the service types.

[0090] In some implementations, if the communication device 1410 fails to receive a response to the measurement report from the network device 1420 , the processor 1412 may send a reestablishment request or a connection establishment request to the network device 1420 via the transceiver 1416 .

[0091] In some implementations, the processor 1412 may select a candidate cell group. The processor 1412 may select at least one target cell from the candidate cell group, wherein the measurement report includes information of the at least one target cell.

[0092] In some implementations, processor 1412 may enable a timer. Processor 1412 determines whether a response to the measurement report including a handover command is received from network device 1420 before the timer expires.

[0093] In some implementations, processor 1412 may stop the timer if a response to the measurement report including a handover command is received from network device 1420 before the timer expires.

[0094] In some implementations, the RL problem includes at least one of a downlink (DL) desynchronization, a radio link control (RLC) retransmission failure, or an uplink (UL) random access procedure failure.

[0095] In some implementations, the processor 1412 may send a reestablishment request or a connection establishment request to a target cell in the wireless network via the transceiver 1416 if the prediction result indicates that an RL problem will occur and the communication device 1410 deems it impossible to perform a handover.

[0096] In some implementations, the communication device 1410 considers that it is impossible to perform the handover due to at least one of the following reasons: the network device 1420 is not configured with a measurement configuration for the handover, the communication device 1410 fails to receive a handover command after sending a measurement report to the network device 1420, the downlink (DL) or uplink (UL) block error rate (BLER) is higher than a threshold that causes the communication device 1410 to be unable to receive a handover command, or the measured neighboring cells do not meet a predetermined signal quality, etc.

[0097] In some implementations, the processor 1422 may receive a measurement report with a prediction result of the RL problem from the communication device 1410 via the transceiver 1426. The processor 1422 may determine whether to respond to the measurement report based on the prediction result.

[0098] In some implementations, the prediction result is received by the processor 1422 if the network node supports RL problem prediction result reporting.

[0099] In some implementations, the processor 1422 may receive capability information from the communication device 1410 via the transceiver 1426, wherein the capability information indicates whether the communication device 1410 supports RL problem prediction. The processor 1422 may send a measurement configuration to the communication device 1410 via the transceiver 1426 based on the capability information.

[0100] In some implementations, processor 1422 can suspend the switching command if the prediction result indicates that the RL problem will not occur.

[0101] In some implementations, the processor 1422 may send a configuration with a switching command to the communication device 141 via the transceiver 1426 if the prediction result indicates that an RL problem will occur.

[0102] In some implementations, the prediction result can be represented as at least one of a Boolean value, one or more levels, and a series of consecutive numbers.

[0103] In some implementations, the processor 1422 may receive a reestablishment request or a connection establishment request from the communication device 1410 via the transceiver 1426 .

[0104] Example Process

[0105] Fig.15 An example process 1500 is shown according to one embodiment of the present invention. Process 1500 may be an example implementation of the above-described scenario / scheme (whether partial or complete) regarding RL problem prediction and early recovery of the present invention. Process 1500 may represent one aspect of an implementation of features of communication device 1410. Process 1500 may include one or more operations, actions, or functions as shown in one or more of blocks 1510 and 1520. Although shown as discrete blocks, the various blocks of process 1500 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. In addition, the blocks of process 1500 may be arranged in Fig.15 1410 or in a different order. Process 1500 may be implemented by communication device 1410 or any suitable UE or machine type device. For illustrative purposes only and not limiting, process 1500 is described below in the context of communication device 1410. Process 1500 may begin at block 1510.

[0106] At 1510 , the process 1500 may include the processor 1412 of the communication device 1410 performing RL problem prediction according to the device context to generate a prediction result before the RLF occurs. The process 1500 may proceed from 1510 to 1520 .

[0107] At 1520 , process 1500 may include processor 1412 determining whether to perform RL early recovery based on the prediction result.

[0108] In some implementations, process 1500 may include processor 1412 sending a measurement report to network device 1420 via transceiver 1416 if the prediction result indicates that an RL problem will occur and a handover is considered likely.

[0109] In some implementations, handover is considered to be possible when a measurement configuration for handover has been received and handover is not currently being performed, and at least one neighboring cell satisfying a predefined signal quality has been measured.

[0110] In some implementations, whether the measurement report includes the prediction result depends on whether the network node supports RL problem prediction result reporting.

[0111] In some implementations, process 1500 may include processor 1412 sending capability information to a network node via transceiver 1416 to indicate whether the device supports RL problem prediction. Process 1500 may include processor 1412 receiving a measurement configuration from a network node via transceiver 1416.

[0112] In some implementations, the process 1500 may include the processor 1412 receiving a configuration with a handover command from a network node via the transceiver 1416. The process 1500 may include the processor 1412 handing over to a target cell according to the handover command.

[0113] In some implementations, process 1500 may include, if the apparatus fails to receive a response to the measurement report from the network node, processor 1412 sending a re-establishment request or a connection establishment request to the network node via transceiver 1416 .

[0114] In some implementations, the process 1500 may include the processor 1412 selecting a candidate cell group. The process 1500 may include the processor 1412 selecting at least one target cell from the candidate cell group, wherein the measurement report includes information of the at least one target cell.

[0115] In some implementations, process 1500 may include processor 1412 enabling a timer. Process 1500 may include processor 1412 determining whether a response to the measurement report including a handover command is received from the network node before the timer expires.

[0116] In some implementations, process 1500 may include processor 1412 stopping the timer if a response to the measurement report is received from the network node before the timer expires.

[0117] In some implementations, process 1500 may include processor 1412 sending a reestablishment request or a connection establishment request to a target cell of the wireless network via transceiver 1416 if the prediction result indicates that an RL problem will occur and a handover is deemed impossible.

[0118] Fig.16An example process 1600 is shown according to another embodiment of the present invention. Process 1600 may be an example implementation of the above-described scenario / scheme (whether partial or complete) regarding RL problem prediction and early recovery of the present invention. Process 1600 may represent one aspect of an implementation of features of network device 1420. Process 1600 may include one or more operations, actions, or functions as shown in one or more of blocks 1610 and 1620. Although shown as discrete blocks, the various blocks of process 1600 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. In addition, the blocks of process 1600 may be arranged in Fig.16 1420 or any base station or network node. For illustration purposes only and not limitation, process 1600 is described below in the context of network device 1420. Process 1600 may begin at block 1610.

[0119] At 1610, process 1600 can include processor 1422 of network device 1420 receiving a measurement report with a RL problem prediction result from a UE via transceiver 1426. Process 1600 can proceed from 1610 to 1620.

[0120] At 1620 , process 1600 can include processor 1422 determining whether to respond to the measurement report based on the prediction result.

[0121] In some implementations, the process 1600 may include the processor 1422 receiving capability information from the UE via the transceiver 1426, wherein the capability information indicates whether the UE supports RL problem prediction. The process 1600 may include the processor 1422 sending a measurement configuration to the UE via the transceiver 1426 based on the capability information, wherein the measurement configuration is used to configure a measurement report.

[0122] In some implementations, process 1600 can include processor 1422 suspending the switch command if the prediction result indicates that the RL problem will not occur.

[0123] In some implementations, process 1600 may include processor 1422 sending a configuration with a handover command to the UE via transceiver 1426 if the prediction result indicates that an RL problem will occur.

[0124] In some implementations, process 1600 may include processor 1422 receiving a reestablishment request or a connection establishment request from a UE via transceiver 1426 .

[0125] Additional Notes

[0126] The subject matter described in the present invention sometimes illustrates different components contained in or connected to different other components. It should be understood that this depicted architecture is only an example, and many other architectures that realize the same function can actually be implemented. In a conceptual sense, any arrangement of components that realize the same function is effectively "associated" to achieve the desired function. Therefore, no matter how the architecture or intermediate components are, the present invention is combined to achieve any two components of a specific function and can be regarded as "associated" to each other, so that the desired function is achieved. Similarly, any two components so associated can also be regarded as "workingly connected" or "workingly coupled" to each other to achieve the desired function, and any two components that can be so associated can also be regarded as "workingly coupleable" to each other to achieve the desired function. Specific examples of coupling at work include, but are not limited to: physically matching and / or physically interactive components and / or wirelessly interactive and / or wirelessly interactive components and / or logically interactive and / or logically interactive components.

[0127] Further, with respect to the extensive use of any plural and / or singular terms of the present invention, those skilled in the art may convert from plural to singular and / or from singular to plural as appropriate for context and / or application. For the sake of clarity, the present invention may explicitly set forth various singular / plural reciprocities.

[0128] Moreover, those skilled in the art will understand that, in general, the terms used in the present invention and especially in the appended claims (e.g., the body of the appended claims) are generally intended to be "open" terms (e.g., the term "including" should be interpreted as "including but not limited to", the term "having" should be interpreted as "having at least", the term "comprising" should be interpreted as "including but not limited to", etc.). Those skilled in the art will also understand that if a specific number of claim recitations is intentionally introduced, such intent will be explicitly recited in the claim, and in the absence of such a recitation, no such intent is present. For example, as an aid to understanding, the appended claims of the present invention may contain the use of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be interpreted as implying that the introduction of a claim recitation by the indefinite article "a" or "an" will include any particular claim of such introduced claim recitation limited to embodiments containing only one such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and an indefinite article such as "a" or "an" (e.g., "a" and / or "an" should be interpreted as meaning "at least one" or "one or more"); the same applies to the use of definite articles used to introduce claim recitations. In addition, even if a specific number of introduced claim recitations is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted as meaning at least the recited number (e.g., the unmodified recitation of "two recitations" means at least two recitations, or two or more recitations, in the absence of other modifiers). Furthermore, in those cases where a convention similar to "at least one of A, B, and C, etc." is used, generally, such interpretation will be understood by those skilled in the art to mean, for example, that "a system having at least one of A, B, and C" will include, but is not limited to, systems having A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc. In those cases where a convention similar to "at least one of A, B, or C, etc." is used, generally, such interpretation will be understood by those skilled in the art to mean, for example, that "a system having at least one of A, B, or C" will include, but is not limited to, systems having A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc. Those skilled in the art will also understand that any transitional words and / or phrases that actually present two or more alternatives, whether in the specification, claims, or drawings, should be understood to contemplate the possibility of including one, either, or both of these items. For example, the phrase "A or B" will be understood to include the possibilities of "A" or "B" or "A and B."

[0129] According to the foregoing, it will be understood that the present invention has been described various embodiments of the present invention for the purpose of illustration, and various modifications can be made without departing from the scope and spirit of the present invention. Therefore, the various embodiments disclosed by the present invention are not intended to be limiting, and the true scope and spirit are represented by the appended claims.

Claims

1. A method for predicting and recovering wireless link problems in mobile communications, comprising: A processor of the device performs radio link (RL) problem prediction according to the device context to generate a prediction result before a radio link failure (RLF) occurs; as well as The processor determines whether to perform RL early recovery based on the prediction result.

2. The method of claim 1, wherein: The RL early recovery includes: In a case where the prediction result indicates that the RL problem will occur and a handover may be performed, the processor sends a measurement report to the network node.

3. The method of claim 2, wherein: It is possible to perform the switching if all of the following factors are met: The device has received a measurement configuration for handover; The device is not currently performing a switch; The apparatus has measured at least one neighboring cell that meets a predefined signal quality.

4. The method of claim 1, wherein: Whether the measurement report includes the prediction result depends on whether the network node supports the RL problem prediction result reporting.

5. The method of claim 1, wherein: The RL problem prediction is performed using at least one of a rule-based algorithm, a machine learning (ML) algorithm, a deep learning (DL) algorithm, and an artificial intelligence (AI) algorithm.

6. The method of claim 1, wherein: The prediction result may be represented as at least one of a Boolean value, one or more levels, and a series of numbers.

7. The method of claim 1, wherein: The device context is device context information within a recent period of time, including at least one of cell measurement results, channel state information, power information, control commands, configured parameter information, historical resident cell information, state information of the device, and service type.

8. The method of claim 1, wherein the RL early recovery further comprises: In the case that the apparatus fails to receive a response to the measurement report from the network node, the processor sends a reestablishment request or a connection establishment request to the network node.

9. The method of claim 2, further comprising: selecting, by the processor, a candidate cell group; as well as At least one target cell is selected by the processor from the candidate cell group, wherein the measurement report contains information of the at least one target cell.

10. The method of claim 1, wherein the RL early recovery further comprises: enabling, by the processor, a timer; as well as A determination is made by the processor whether a response with a handover command to the measurement report is received from the network node before the timer expires.

11. The method of claim 10, further comprising: The timer is stopped by the processor in case a response with a handover command to the measurement report is received from the network node before the timer expires.

12. The method of claim 1, wherein: The RL problem includes at least one of a downlink (DL) desynchronization, a radio link control (RLC) retransmission failure, or an uplink (UL) random access procedure failure.

13. The method of claim 1, wherein the RL early recovery further comprises: In a case where the prediction result indicates that the RL problem will occur and it is impossible to perform handover, the processor sends a reestablishment request or a connection establishment request to a target cell in the wireless network.

14. The method of claim 13, wherein: The impossibility of performing the handover is due to at least one of the following factors: The network node is not configured with a measurement configuration for handover; or the apparatus fails to receive a handover command after sending a measurement report to the network node; or The downlink (DL) or uplink (UL) block error rate (BLER) is above a threshold; or The measured adjacent cells do not meet the predetermined signal quality.

15. A method for predicting and recovering wireless link problems in mobile communications, comprising: Receiving, by a processor of the network node, a measurement report with a prediction result of a radio link (RL) problem prediction from a user equipment (UE); as well as The processor determines whether to respond to the measurement report based on the prediction result.

16. The method of claim 15, wherein: The prediction result is received if the network node supports RL problem prediction result reporting.

17. The method of claim 15, further comprising: Receiving, by the processor, capability information from the UE, wherein the capability information indicates whether the UE supports RL problem prediction; as well as The processor sends a measurement configuration to the UE based on the capability information, wherein the measurement configuration is used to configure the measurement report.

18. The method of claim 15, further comprising: In case the prediction result indicates that the RL problem will not occur, the switching command is suspended by the processor.

19. The method of claim 15, further comprising: In case the prediction result indicates that an RL problem will occur, the processor sends a configuration with a handover command to the UE.

20. The method of claim 15, further comprising: A reestablishment request or a connection establishment request is received by the processor from the UE.

21. A non-volatile computer-readable storage medium storing a program and data, which, when executed by a processor of a device, causes the device to execute the method of any one of claims 1 to 20.