Method, terminal device and chip for fast handover failure recovery

Abstract

The embodiment of the application discloses a method for fast switching failure recovery, a terminal device and a chip. The terminal device configures a first timer according to a reconfiguration message. After detecting a radio link failure, if the number of cells in a cell trigger list cellsTriggeredList corresponding to a measurement identifier measId configured with the first timer in a measurement report list VarMeasReportList is not 0, the first timer is started. If the first timer is timed out, RRC connection reconstruction is triggered.

Description

Technical Field

[0001] This invention relates to the field of wireless communication technology, and in particular to a method, terminal device, and chip for fast handover failure recovery. Background Technology

[0002] To meet the mobility requirements of seamless handover, it is necessary to minimize handover downtime. One solution to reduce handover downtime is Fast Handover Failure Recovery, which enables the rapid restoration of the radio link between the User Equipment (UE) and the network-side base station from a failed or predicted handover.

[0003] Currently, the fast handover failure recovery scheme can be implemented by configuring the T312 (Timer 312) timer. However, in actual execution, the triggering time of the measurement report configured with T312 is restricted, which makes it impossible to perform fast handover failure recovery in some scenarios, prolonging the handover interruption time and reducing the communication performance of the terminal device. Summary of the Invention

[0004] This application provides a method, terminal device, and chip for fast handover failure recovery, which overcomes the shortcomings of not being able to perform fast handover failure recovery in certain scenarios, thereby shortening the handover interruption time and improving the communication performance of the terminal device.

[0005] The technical solution of this application embodiment is implemented as follows:

[0006] In a first aspect, embodiments of this application provide a method for rapid recovery from a switchover failure, the method comprising:

[0007] Configure the first timer according to the reconfiguration message;

[0008] After a wireless link failure is detected, if the number of cells in the cellsTriggeredList corresponding to the measurement identifier measId configured with the first timer in the measurement report list VarMeasReportList is not 0, then the first timer is started.

[0009] If the first timer times out, an RRC connection reconstruction is triggered.

[0010] Secondly, embodiments of this application provide a chip, which includes programmable logic circuits and / or program instructions, and when the chip is running, it implements the fast switching failure recovery method described above.

[0011] Thirdly, embodiments of this application provide a terminal device, which includes a processor and a memory storing processor-executable instructions. When the instructions are executed by the processor, the above-described method for fast switching failure recovery is implemented.

[0012] This application provides a method, terminal device, and chip for rapid handover failure recovery. The terminal device configures a first timer based on a reconfiguration message. After detecting a radio link failure, if the number of cells in the cell trigger list (cellsTriggeredList) corresponding to the measurement identifier (measId) configured with the first timer in the measurement report list (VarMeasReportList) is not zero, the first timer is started. If the first timer times out, RRC connection reconstruction is triggered. Therefore, in this application's embodiment, after configuring the first timer, if a radio link failure is detected, the number of cells in the cell trigger list (cellsTriggeredList) corresponding to the measurement identifier (measId) configured with the first timer can be used to select whether to start the first timer, without restricting or requiring the triggering timing of the measurement report configured with the first timer. As long as the number of cells is not zero, the first timer can be started, thus overcoming the deficiency of not being able to perform rapid handover failure recovery in certain scenarios, thereby shortening the handover interruption time and improving the communication performance of the terminal device. Attached Figure Description

[0013] Figure 1 This is a schematic diagram of a common fast switchover failure recovery implementation. Figure 1 ;

[0014] Figure 2 This is a schematic diagram of a common fast switchover failure recovery implementation. Figure 2 ;

[0015] Figure 3 This is a diagram illustrating cell handover.

[0016] Figure 4 This is a schematic diagram of a communication system;

[0017] Figure 5 This is a schematic diagram of the implementation process of the fast handover failure recovery method proposed in the embodiments of this application. Figure 1 ;

[0018] Figure 6 This is a schematic diagram of the implementation process of the fast handover failure recovery method proposed in the embodiments of this application. Figure 2 ;

[0019] Figure 7 This is a schematic diagram of the implementation process of the fast handover failure recovery method proposed in the embodiments of this application. Figure 3 ;

[0020] Figure 8 A diagram illustrating the start method of the first timer. Figure 1 ;

[0021] Figure 9 A diagram illustrating the start method of the first timer. Figure 2 ;

[0022] Figure 10 A diagram illustrating the start method of the first timer. Figure 3 ;

[0023] Figure 11 A diagram illustrating the start method of the first timer. Figure 4 ;

[0024] Figure 12 This is a diagram illustrating a scenario where rapid switchover failure recovery is not possible.

[0025] Figure 13 Illustration of a scenario for rapid handover failure recovery Figure 1 ;

[0026] Figure 14 This is a schematic diagram of the implementation process of the fast handover failure recovery method proposed in the embodiments of this application. Figure 4 ;

[0027] Figure 15 Illustration of a scenario for rapid handover failure recovery Figure 2 ;

[0028] Figure 16 Illustration of a scenario for rapid handover failure recovery Figure 3 ;

[0029] Figure 17 Illustration of a scenario for rapid handover failure recovery Figure 4 ;

[0030] Figure 18 This is a schematic diagram of the composition structure of the terminal device. Detailed Implementation

[0031] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are only for explaining the relevant application and not for limiting the application. Furthermore, it should be noted that, for ease of description, only the parts related to the relevant application are shown in the accompanying drawings.

[0032] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0033] In the following description, references to "some embodiments" refer to a subset of all possible embodiments. It is understood that "some embodiments" may be the same or different subsets of all possible embodiments and may be combined with each other without conflict. It should also be noted that the terms "first, second, third" used in the embodiments of this application are merely for distinguishing similar objects and do not represent a specific ordering of objects. It is understood that "first, second, third" may be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0034] At the 3rd Generation Partnership Project (3GPP) RAN#80 plenary meeting, a new research project on 5G technology standards was approved. One of the project's research objectives is to find a way to meet one of the mobility requirements in New Radio (NR): seamless handover, i.e., achieving zero handover interruption time during cell handover. Among the solutions being researched to reduce handover interruption time, one approach is called Fast Handover Failure Recovery, which aims to quickly restore the radio link connection between User Equipment (UE) and the network-side base station from a failed or predicted handover.

[0035] The fast handover failure recovery solution in the NR system will be studied based on the fast handover failure recovery solution in the Long Term Evolution (LTE) system.

[0036] Current fast switchover failure recovery solutions can be implemented by configuring the T312 (Timer 312) timer. The configuration and startup process of the T312 in related technologies is as follows:

[0037] 1. After the UE enters the connected state, the network will configure T312 for event-triggered measurements. The activation conditions for T312 are as follows:

[0038] a) The UE detects a radio link failure (RLF) and activates T310 (Timer 310).

[0039] b) The T312 measurement was configured to trigger a measurement report, and the triggering method is one of the following two:

[0040] i. The first trigger occurs when the number of cellsTriggeredList corresponding to the measurement identifier (measId) in the VarMeasReportList is 0, meaning that a cell meets the entry conditions for this event for the first time within the timetoTrigger period.

[0041] (enter condition)

[0042] ii. A new trigger (a subsequent cell triggers the event), namely the VarMeas report list.

[0043] If the number of cellsTriggeredList corresponding to the measurement identifier (measId) in the Report tList is not 0, then there are other cells that meet the entry condition applied to this event within the timetoTrigger time period.

[0044] c) If T310 is still timing at this point, then immediately start T312.

[0045] 2. Due to wireless link issues, uplink measurement reports or downlink reconfiguration messages may not reach their destination smoothly, resulting in a T312 timeout. The UE will then trigger a reconstruction. Typically, the duration of T312 is shorter than that of T310, thus achieving the goal of rapid handover failure recovery.

[0046] Furthermore, Figure 1 This is a schematic diagram of a common fast switchover failure recovery implementation. Figure 1 ,like Figure 1 As shown, the terminal receives a reconfiguration message to configure measurement information, including T312 timer configuration (S1). The UE detects that the RLF starts the T310 timer (S2). The measurement with T312 configured triggers the measurement report (first trigger or new trigger) (S3). The T312 timer is started (S4). T312 times out (S5). Reconstruction is triggered (S6).

[0047] Correspondingly, Figure 2 This is a schematic diagram of a common fast switchover failure recovery implementation. Figure 2 ,like Figure 2As shown, after configuring T312, if the UE detects RLF, the T310 timer will be started. If the T310 is still running when the measurement report is triggered by the T312 configured measurement, the T312 timer can be started. When the T312 times out, a reconstruction will be triggered.

[0048] Figure 3 This is a diagram illustrating cell handover, such as... Figure 3 As shown, the user equipment (UE) can configure T312 through the received configuration information. After detecting a radio link failure (RLF), T310 can be started. When T310 is running, if the measurement that was configured to start T312 triggers a measurement report, then T312 is started. If T312 times out, a handover failure is declared, and the reconstruction speed is accelerated before T310 times out, triggering the RRC connection reconstruction and completing the RRC reconstruction and configuration.

[0049] It is evident that, on the one hand, when starting T312, only the scenario where T310 starts first, followed by the event-type measurement configured for T312, is considered. The scenario where the event-type measurement report configured for T312 is triggered first, followed by T310, is not considered. That is, the execution order of steps S2 and S3 in the above diagram cannot be interchanged. Therefore, T312 cannot be triggered in the following scenario: the measurement configured for T312 meets the triggering condition first. If the configured reporting count (reportAmount) is 1, T310 is then started. However, since reportAmount is 1, if no new cell triggers a measurement report, T312 cannot be started.

[0050] On the other hand, the conditions for activating T312 can be summarized as follows: during the T310 activation period, a new cell must meet the triggering conditions for T312 to be activated. Periodic reporting from old cells or reporting triggered when an old cell meets the leaving condition will not activate T312. In other words, the following scenarios will not meet the T312 activation conditions:

[0051] a) The T312 measurement was configured to meet the triggering conditions first, and the configured reporting count (reportAmount) was not 1, before T310 was started. Even if the old cell periodically triggers the T312 measurement later, it will not be able to start.

[0052] b) T312 is configured to start only after the measurement meets the triggering condition. Even if the old cell meets the leaving condition and the number of cellsTriggeredList is not 0, T312 cannot be started.

[0053] However, in the aforementioned situations where T312 cannot be started, there may still be cells that meet the conditions for fast handover failure recovery. For example, if the number of cellsTriggeredList is not 0, the cells stored in it are very likely to meet the corresponding triggering conditions.

[0054] In other words, common methods for quick handover failure recovery restrict the order in which T310 is started and the measurement report configured with T312 is triggered, which makes quick handover failure recovery impossible in some scenarios, prolonging the handover interruption time and reducing the communication performance of the terminal device.

[0055] To address the problems existing in common fast handover failure recovery schemes, in the embodiments of this application, the terminal device configures a first timer according to a reconfiguration message. After detecting a radio link failure, if the number of cells in the cell trigger list (cellsTriggeredList) corresponding to the measurement identifier (measId) configured with the first timer in the measurement report list (VarMeasReportList) is not zero, the first timer is started. If the first timer times out, RRC connection reconstruction is triggered. Therefore, in the embodiments of this application, after configuring the first timer, if a radio link failure is detected, the number of cells in the cell trigger list (cellsTriggeredList) corresponding to the measurement identifier (measId) configured with the first timer can be used to select whether to start the first timer, without restricting or requiring the triggering timing of the measurement report configured with the first timer. As long as the number of cells is not zero, the first timer can be started, thereby overcoming the deficiency of not being able to perform fast handover failure recovery in certain scenarios, thus shortening the handover interruption time and improving the communication performance of the terminal device.

[0056] It should be noted that the fast handover failure recovery method provided in this application embodiment can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), LTE system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, or 5G system, etc.

[0057] For example, in the embodiments of this application, Figure 4 A schematic diagram of a communication system, such as Figure 4 As shown, the communication system 100 may include a network device 110, which may be a device that communicates with the terminal device 100 (or a communication terminal, terminal). The network device 110 can provide communication coverage for a specific geographical area and can communicate with terminal devices located within that coverage area. The network device 110 may be a base station (BTS) in a GSM or CDMA system, a base station (NodeB, NB) in a WCDMA system, an evolved Node B (eNB or eNodeB) in an LTE system, or a radio controller in a Cloud Radio Access Network (CRAN). Alternatively, the network device may be a mobile switching center, relay station, access point, vehicle-mounted equipment, wearable device, hub, switch, bridge, router, network-side equipment in a 5G network, or network equipment in a future evolved Public Land Mobile Network (PLMN), etc.

[0058] It is understood that, in embodiments of this application, the communication system 100 also includes at least one terminal device 100 located within the coverage area of ​​the network device 110. As used herein, "terminal device" includes, but is not limited to, devices configured to receive / transmit communication signals via wired connections, such as via Public Switched Telephone Networks (PSTN), Digital Subscriber Line (DSL), digital cable, direct cable connection; and / or another data connection / network; and / or via a wireless interface, such as for cellular networks, Wireless Local Area Networks (WLAN), digital television networks such as DVB-H networks, satellite networks, AM-FM broadcast transmitters; and / or other terminal devices. Terminal devices configured to communicate via wireless interfaces may be referred to as "wireless communication terminals," "wireless terminals," or "mobile terminals." Examples of mobile terminals include, but are not limited to, satellite or cellular phones; personal communications system (PCS) terminals that can combine cellular radiotelephony with data processing, fax, and data communication capabilities; PDAs that may include radiotelephones, pagers, Internet / intranet access, web browsers, notebooks, calendars, and / or Global Positioning System (GPS) receivers; and conventional laptop and / or handheld receivers or other electronic devices that include radiotelephone transceivers. Terminal equipment can refer to access terminals, user equipment (UE), user units, user stations, mobile stations, mobile stations, remote stations, remote terminals, mobile devices, user terminals, terminals, wireless communication equipment, user agents, or user equipment. Access terminals can be cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminal devices in 5G networks, or terminal devices in future PLMNs, etc.

[0059] It should be noted that, in the embodiments of this application, terminal devices 100 can perform device-to-device (D2D) communication.

[0060] It should be noted that, in the embodiments of this application, the 5G system or 5G network may also be referred to as the NR system or NR network.

[0061] It is understood that, in the embodiments of this application, as Figure 4 The communication system shown exemplarily illustrates a network device and two terminal devices. The communication system 100 may include multiple network devices and each network device may include other numbers of terminal devices within its coverage area. This application embodiment does not limit this.

[0062] It should be noted that, in the embodiments of this application, the communication system 100 may also include other network entities such as a network controller and a mobility management entity, and the embodiments of this application do not limit this.

[0063] It is understood that, in the embodiments of this application, a device with communication function in the network / system can be referred to as a communication device. Taking communication system 100 as an example, the communication device may include network device 110 and terminal device 100 with communication function. Network device 110 and terminal device 100 can be the specific devices described above, which will not be repeated here. The communication device may also include other devices in communication system 100, such as network controllers, mobility management entities, and other network entities. This application embodiment does not limit this.

[0064] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0065] One embodiment of this application provides a method for rapid recovery from switchover failure. Figure 5 This is a schematic diagram of the implementation process of the fast handover failure recovery method proposed in the embodiments of this application. Figure 1 ,like Figure 5 As shown in the embodiments of this application, the method for a terminal device to perform fast handover failure recovery may include the following steps:

[0066] Step 101: Configure the first timer according to the reconfiguration message.

[0067] In the embodiments of this application, the terminal device may first configure a first timer according to the received reconfiguration message.

[0068] It should be noted that, in the embodiments of this application, the terminal device can be any form such as a device, chip, integrated circuit (IC), application specific integrated circuit (ASIC).

[0069] Furthermore, in the embodiments of this application, the first timer can be T312.

[0070] It should be noted that, in the embodiments of this application, the reconfiguration message can be sent from the network device to the terminal device. The network device can be the serving cell. The serving cell can be a PCell in an LTE system, a PCell in an NR system, a PSCell in an LTE system, or a PSCell in an NR system.

[0071] Furthermore, in the embodiments of this application, Figure 6 This is a schematic diagram of the implementation process of the fast handover failure recovery method proposed in the embodiments of this application. Figure 2 ,like Figure 6 As shown, before configuring the first timer according to the reconfiguration message, i.e. before step 101, the method for the terminal device to perform fast handover failure recovery may also include the following steps:

[0072] Step 104: Receive a reconfiguration message; wherein, the reconfiguration message is used for the configuration of the measurement object and the configuration of the first timer corresponding to the measurement object.

[0073] In the embodiments of this application, the terminal device may first receive a reconfiguration message sent by the network device, wherein the reconfiguration message may be used for the configuration of the measurement object and the configuration of the first timer corresponding to the measurement object.

[0074] It should be noted that, in the embodiments of this application, the reconfiguration message may include a first timer parameter, and the terminal device may use the first timer parameter to configure the first timer.

[0075] It is understood that, in the embodiments of this application, the terminal device can determine the radio link connection status of the serving cell based on a first timer. Specifically, the terminal device can determine the radio link connection status of the serving cell based on whether the first timer has timed out.

[0076] Furthermore, in the embodiments of this application, the measurement object can be a measurement frequency point. Specifically, based on the reconfiguration message, a corresponding first timer can be independently configured for different measurement objects.

[0077] Accordingly, in the embodiments of this application, the terminal device triggering a measurement event on the measurement object may include the terminal device triggering a measurement event at a measurement frequency point. The measurement event may be an A3 event.

[0078] It should be noted that, in the embodiments of this application, based on the reconfiguration message, it can also be determined whether one or more measurement event configurations apply the first timer.

[0079] For example, in the embodiments of this application, the serving cell can maintain multiple T312s corresponding to multiple measurement objects respectively. The length of each T312 can be flexibly configured, and the reporting time of different measurement objects can also be flexibly configured, so as to enable the terminal device to accurately determine the wireless link connection status of the serving cell.

[0080] In other words, in the embodiments of this application, the first timer can be configured by the network device. For example, T312 can be introduced and configured by the network to control behavior that is expected to minimize service interruption time.

[0081] Furthermore, in embodiments of this application, the terminal device can receive a reconfiguration message sent by the network device corresponding to the serving cell. The reconfiguration message includes at least one of the following: first timer parameters configured independently for different measurement objects and whether to apply the first timer for one or more measurement events.

[0082] For example, in an embodiment of this application, the terminal device can receive a reconfiguration message via an RRC message. That is, the network device can configure T312 parameters to the terminal device via an RRC message. The RRC message can be carried via SRB3 or SRB1.

[0083] It is understood that, in the embodiments of this application, the T312 parameter can be configured on one or more measurement objects, and the length of T312 corresponding to each measurement object can be configured separately; the length of T312 corresponding to different measurement objects can be the same or different.

[0084] Step 102: After detecting a wireless link failure, if the number of cells in the cell trigger list cellsTriggeredList corresponding to the measurement identifier measId configured with the first timer in the measurement report list VarMeasReportList is not 0, then start the first timer.

[0085] In the embodiments of this application, after the terminal device completes the configuration of the first timer, when a wireless link failure is detected, if the number of cells in the cell trigger list cellsTriggeredList corresponding to the measurement identifier measId configured with the first timer in the measurement report list VarMeasReportList is not 0, then the terminal device may choose to start the first timer.

[0086] It should be noted that, in the embodiments of this application, after a wireless link failure is detected, the terminal device may also start a second timer.

[0087] For example, in an embodiment of this application, the second timer can be T310. If the second timer is running, it can indicate that the serving cell corresponding to the terminal device has a radio link problem, that is, the radio link of the serving cell is abnormal, such as radio link failure (RLF).

[0088] For example, in the embodiments of this application, Figure 7 This is a schematic diagram of the implementation process of the fast handover failure recovery method proposed in the embodiments of this application. Figure 3 ,like Figure 7 As shown, after configuring the first timer according to the reconfiguration message, i.e., after step 101, the method for the terminal device to perform fast handover failure recovery may further include the following steps:

[0089] Step 105: After detecting a wireless link failure, start the second timer.

[0090] In the embodiments of this application, after configuring the first timer, the terminal device needs to start a second timer when a wireless link failure is detected. The second timer can be pre-configured, or it can be configured by the network device.

[0091] It should be noted that, in the embodiments of this application, the duration of the second timer can be greater than the duration of the first timer. Specifically, the duration of the second timer can be several thousand milliseconds, while the duration of the first timer can be tens or hundreds of milliseconds. For example, the configured runtime of the first timer is 20 milliseconds, and the runtime of the second timer is 1000 milliseconds.

[0092] For example, in the embodiments of this application, it is assumed that the first timer is T312 and the second timer is T310. When timer T312 expires, a reconstruction can be triggered until T310 times out, so as to achieve fast handover failure recovery; when timer T310 expires, the terminal device can declare radio link failure (RLF) and initiate a cell selection process to attempt recovery.

[0093] Furthermore, in the embodiments of this application, if the number of cells in the cell trigger list cellsTriggeredList corresponding to the measurement identifier measId configured with the first timer in the measurement report list VarMeasReportList is not 0, then it can be considered that there are cells that meet the fast recovery conditions. It can be determined that the cells stored in the cell trigger list cellsTriggeredList meet the trigger conditions of the corresponding measurement identifier (measId), so the first timer can be started.

[0094] In other words, in the embodiments of this application, assuming the first timer is T312 and the second timer is T310, the activation condition for T312 is that the number of cells in the cell trigger list (cellsTriggeredList) corresponding to the measurement identifier (measId) configured for the first timer is not zero. However, in related technologies, the activation condition for T312 requires that a measurement report is triggered after T310 has started running. In contrast, the fast handover failure recovery method proposed in this application no longer restricts the order between the activation of T310 and the triggering of the measurement report, but determines whether to activate the already configured T312 solely based on the number of cells in the cell trigger list (cellsTriggeredList).

[0095] Furthermore, in the embodiments of this application, after a wireless link failure is detected, if the number of cells in the cell trigger list cellsTriggeredList is not 0, the terminal device can start the first timer and the second timer.

[0096] It should be noted that, in the embodiments of this application, if the terminal device has already completed the configuration of the first timer, after detecting a wireless link failure, it can first determine the number of cells in the cell trigger list cellsTriggeredList corresponding to the measurement identifier measId configured with the first timer in the measurement report list VarMeasReportList. Since the cells in the cell trigger list cellsTriggeredList meet the triggering conditions of the corresponding measurement identifier measId, when the number of cells is not 0, it can be determined that there are cells that meet the fast recovery conditions, and then the first timer and the second timer can be started.

[0097] In other words, in the embodiments of this application, for the case where the event-type measurement report with the first timer is triggered first, and the second timer is started later, after a radio link failure is detected, the terminal device can choose whether to start the first timer by using the number of cells in the cellsTriggeredList corresponding to the measurement identifier measId configured with the first timer in the measurement report list VarMeasReportList. Specifically, after a radio link failure is detected, the terminal device can choose to start both the first and second timers simultaneously, or it can choose to start the second timer first.

[0098] For example, in the embodiments of this application, Figure 8 A diagram illustrating the start method of the first timer. Figure 1 ,like Figure 8As shown, after detecting a wireless link failure, if it is determined that the number of cells in the cell trigger list cellsTriggeredList corresponding to the measurement identifier measId configured with the first timer is not 0, then the second timer can be started first, and then the first timer can be started.

[0099] For example, in the embodiments of this application, Figure 9 A diagram illustrating the start method of the first timer. Figure 2 ,like Figure 9 As shown, after a wireless link failure is detected, if it is determined that the number of cells in the cell trigger list cellsTriggeredList corresponding to the measurement identifier measId configured with the first timer is not 0, then the second and first timers can be started simultaneously.

[0100] It should be noted that in the embodiments of this application, since the current protocol stipulates that T312 is only started when T310 has been started during the first trigger and new triggers, it does not stipulate that T312 is started if T310 has been started if the leaving condition or periodic reporting is met. However, the fast handover failure recovery method proposed in the embodiments of this application can further select whether to trigger T312 by combining the determination of whether the leaving condition or periodic reporting is met.

[0101] Furthermore, in the embodiments of this application, after detecting a wireless link failure, the terminal device can first start a second timer. After starting the second timer, if it is determined that the first cell meets the leave condition and the number of cells in the cell trigger list cellsTriggeredList corresponding to the measurement identifier measId configured with the first timer in the measurement report list VarMeasReportList is not 0, then the terminal device can choose to start the first timer.

[0102] It should be noted that, in the embodiments of this application, the first cell can be any cell in the cell trigger list cellsTriggeredList, that is, the first cell can be an existing old cell in the trigger list cellsTriggeredList.

[0103] It should be noted that, in the embodiments of this application, if the terminal device has already completed the configuration of the first timer, after detecting a wireless link failure, it can first start the second timer, and then further determine the number of cells in the cellsTriggeredList corresponding to the measurement identifier measId configured with the first timer in the measurement report list VarMeasReportList. It can also determine whether the first cell meets the leave condition, that is, whether the report was triggered when an old cell met the leave condition. Since the cells in the cellsTriggeredList meet the trigger conditions of the corresponding measurement identifier measId, when the first cell meets the leave condition and the number of cells is not zero, it can be determined that there is a cell that meets the fast recovery condition, and thus the first timer can be started.

[0104] In other words, in the embodiments of this application, for the case where the event-type measurement report with the first timer is triggered first, and the second timer starts later, after detecting a wireless link failure and starting the second timer, the terminal device can further select whether to start the first timer by determining whether the first cell (an old cell in the cell trigger list cellsTriggeredList) meets the leave condition, and by determining the number of cells in the cell trigger list cellsTriggeredList corresponding to the measurement identifier measId configured with the first timer in the measurement report list VarMeasReportList. Specifically, if the first cell meets the leave condition and the number of cells is not zero, then the first timer can be started.

[0105] For example, in the embodiments of this application, Figure 10 A diagram illustrating the start method of the first timer. Figure 3 ,like Figure 10 As shown, after detecting a wireless link failure, the second timer is started first. Then, after determining that the first cell meets the leave condition and the number of cells in the cell trigger list cellsTriggeredList corresponding to the measurement identifier measId configured for the first timer is not 0, the first timer is started.

[0106] In other words, in the embodiments of this application, when a cell meets the leaving condition, if T310 has already been started, it also checks whether the number of cells in cellsTriggeredList is 0. If the number of cells is not 0, T312 is started immediately.

[0107] Furthermore, in the embodiments of this application, after detecting a wireless link failure, the terminal device can first start a second timer. After starting the second timer, if the first cell reports periodically, then the first timer can be started directly.

[0108] It should be noted that, in the embodiments of this application, the first cell can be any cell in the cell trigger list cellsTriggeredList, that is, the first cell can be an existing old cell in the trigger list cellsTriggeredList.

[0109] It should be noted that, in the embodiments of this application, if the terminal device has already completed the configuration of the first timer, after detecting a wireless link failure, it can first start the second timer, and then further determine whether the first cell is periodically reporting, that is, whether it is periodically reporting from an old cell. If so, it can be considered that there is a cell that meets the conditions for fast recovery, and then the first timer can be started directly.

[0110] It is understood that, in the embodiments of this application, if it is determined that the first cell reports periodically, then it can be assumed that the number of cells in the cell trigger list cellsTriggeredList corresponding to the measurement identifier measId configured with the first timer in the measurement report list VarMeasReportList is not 0, that is, it is determined that the cells in the cell trigger list cellsTriggeredList meet the triggering conditions of the corresponding measurement identifier measId, so the first timer can be started directly.

[0111] In other words, in the embodiments of this application, for the case where an event-type measurement report with a first timer is triggered first, and the second timer starts later, after a wireless link failure is detected and the second timer is started, the terminal device can further choose whether to start the first timer by determining whether the first cell (an old cell in the cell trigger list cellsTriggeredList) reports periodically. Specifically, if the first cell reports periodically, then the first timer can be started.

[0112] For example, in the embodiments of this application, Figure 11 A diagram illustrating the start method of the first timer. Figure 4 ,like Figure 11 As shown, after detecting a wireless link failure, the second timer is started first, and then the first timer is started after determining that the first cell is periodically reporting.

[0113] In other words, in the embodiments of this application, when the cell meets the requirement of periodic reporting, if T310 has already been started, T312 will also be started.

[0114] Therefore, in the embodiments of this application, the starting condition of the first timer is no longer limited to starting the second timer first and then triggering the event-type measurement report configured with the first timer. Thus, in the case where the event-type measurement report configured with the first timer is triggered first and the second timer is started later, the terminal device can start the first timer after determining that the number of cells in the cell trigger list cellsTriggeredList corresponding to the measurement identifier measId configured with the first timer in the measurement report list VarMeasReportList is not 0, thereby ensuring the realization of fast handover failure recovery.

[0115] Step 103: If the first timer times out, trigger the RRC connection reconstruction.

[0116] In the embodiments of this application, after a wireless link failure is detected, if the number of cells in the cell trigger list cellsTriggeredList corresponding to the measurement identifier measId configured with the first timer in the measurement report list VarMeasReportList is not 0, then after the terminal device starts the first timer, if the first timer times out, the terminal device can further trigger RRC connection reconstruction.

[0117] It should be noted that, in the embodiments of this application, when the event-type measurement report with the first timer configured is triggered first and the second timer is started later, not only can the first timer be started under the premise that it is determined that there is a cell that meets the conditions for fast recovery, but also, since the measurement report is triggered before the second timer is started, the first timer is also started in advance, thereby triggering the reconstruction process in advance.

[0118] For example, in the embodiments of this application, Figure 12 This is an illustration of a scenario where rapid switchover failure recovery is not possible, such as... Figure 12 As shown, assuming the first timer is T312 and the second timer is T310, related technologies require that T312 be started when a measurement configured with T312 triggers a measurement report after T310 has started. Therefore, if a measurement configured with T312 triggers a measurement report before T310 starts, T312 cannot be started after T310 starts, and thus fast handover failure recovery via T312 is impossible until T310 times out, at which point the terminal device can declare a radio link failure (RLF) and trigger reconstruction.

[0119] For example, in the embodiments of this application, Figure 13 Illustration of a scenario for rapid handover failure recovery Figure 1 ,like Figure 13As shown, assuming the first timer is T312 and the second timer is T310, if the measurement configured with T312 triggers the measurement report before T310 starts, after detecting a wireless link failure, the number of cells in the cell trigger list cellsTriggeredList corresponding to the measurement identifier measId configured with T312 can be determined first. If the number of cells is determined to be not 0, T312 can be started, and then fast handover failure recovery can be performed through T312 until T312 times out, at which point the terminal device triggers reconstruction.

[0120] In contrast, the fast handover failure recovery method proposed in this application no longer restricts the order between the activation of T310 and the triggering of the measurement report. Instead, it determines whether to activate the already configured T312 based solely on the number of cells in the cell trigger list (cellsTriggeredList). This not only solves the problem of not being able to perform fast handover failure recovery in scenarios where the measurement report is triggered before T310 is activated, but also enables the early activation of the first timer, thereby achieving early triggering of the reconstruction process.

[0121] In summary, in the embodiments of this application, a new method for starting a first timer is introduced to achieve rapid handover failure recovery. Specifically, after detecting a radio link failure, the terminal device can first check if there are any cells that meet the criteria for rapid handover failure recovery by checking the number of cellsTriggeredList corresponding to the measurement identifier measId configured with the first timer in the measurement report list VarMeasReportList. If the number is not zero, it indicates that there are cells that meet the rapid recovery conditions, and therefore the first timer can be started immediately.

[0122] It is understood that the fast handover failure recovery method proposed in the embodiments of this application can be applied to various communication systems, such as 4G (LTE) systems or 5G systems, with 5G systems as an example.

[0123] This application provides a method for rapid handover failure recovery. The terminal device configures a first timer based on a reconfiguration message. After detecting a radio link failure, if the number of cells in the cellsTriggeredList corresponding to the measurement identifier (measId) configured with the first timer in the measurement report list (VarMeasReportList) is not zero, the first timer is started. If the first timer times out, RRC connection reconstruction is triggered. Therefore, in this embodiment, after configuring the first timer, if a radio link failure is detected, the number of cells in the cellsTriggeredList corresponding to the measurement identifier (measId) configured with the first timer can be used to select whether to start the first timer, without restricting or requiring the triggering timing of the measurement report configured with the first timer. As long as the number of cells is not zero, the first timer can be started, thus overcoming the deficiency of not being able to perform rapid handover failure recovery in certain scenarios, thereby shortening the handover interruption time and improving the communication performance of the terminal device.

[0124] Based on the above embodiments, in another embodiment of this application, to address the common technical issue of inability to perform fast handover failure recovery, the terminal device can determine whether to activate the first timer by the number of cells in the cell trigger list (cellsTriggeredList) corresponding to the measurement identifier (measId) configured with the first timer in the measurement report list (VarMeasReportList). When the number of cells is not zero, it can be assumed that there are cells meeting the fast recovery conditions, and therefore the first timer can be activated.

[0125] Furthermore, in the embodiments of this application, Figure 14 This is a schematic diagram of the implementation process of the fast handover failure recovery method proposed in the embodiments of this application. Figure 4 ,like Figure 14 As shown, assuming the first timer is T312 and the second timer is T310, the method for terminal devices to perform fast handover failure recovery may include the following steps:

[0126] Step 201: Receive the reconfiguration message and configure T312 based on the reconfiguration message.

[0127] In embodiments of this application, the terminal device may first receive a reconfiguration message sent by the network device. This reconfiguration message can be used to configure the measurement object and the corresponding T312. The reconfiguration message may carry T312 parameters, which the terminal device can use to configure the T312.

[0128] It is understood that, in the embodiments of this application, the terminal device can determine the radio link connection status of the serving cell based on T312. Specifically, the terminal device can determine the radio link connection status of the serving cell based on whether T312 has timed out.

[0129] It should be noted that, in the embodiments of this application, the serving cell can be a PCell in an LTE system, a PCell in an NR system, a PSCell in an LTE system, or a PSCell in an NR system.

[0130] Furthermore, in the embodiments of this application, the measurement object can be a measurement frequency point. Specifically, based on the reconfiguration message, a corresponding T312 can be configured independently for different measurement objects.

[0131] Accordingly, in the embodiments of this application, the terminal device triggering a measurement event on the measurement object may include the terminal device triggering a measurement event on the measurement frequency point. The measurement event may be an A3 event or an A5 event. Based on the reconfiguration message, it can also be determined whether one or more measurement event configurations apply T312.

[0132] It should be noted that, in the embodiments of this application, the serving cell can maintain multiple T312s corresponding to multiple measurement objects respectively. The length of each T312 can be flexibly configured, and the reporting time of different measurement objects can also be flexibly configured. In this way, the terminal device can accurately determine the wireless link connection status of the serving cell.

[0133] In other words, in the embodiments of this application, T312 can be configured by a network device. For example, T312 can be introduced and configured by the network to control behavior that is expected to minimize service interruption time.

[0134] Furthermore, in embodiments of this application, the terminal device can receive a reconfiguration message sent by the network device corresponding to the serving cell. The reconfiguration message includes at least one of the following: T312 parameters configured independently for different measurement objects, and whether to apply T312 for one or more measurement events.

[0135] It should be noted that, in the embodiments of this application, the terminal device can receive reconfiguration messages via RRC messages. That is, the network device can configure T312 parameters to the terminal device via RRC messages. RRC messages can be carried via SRB3 or SRB1.

[0136] It is understood that, in the embodiments of this application, the T312 parameter can be configured on one or more measurement objects, and the length of T312 corresponding to each measurement object can be configured separately; the length of T312 corresponding to different measurement objects can be the same or different.

[0137] Step 202: After detecting a wireless link failure, turn on T310.

[0138] In the embodiments of this application, after the terminal device completes the configuration of T312 according to the received reconfiguration message, it can first enable T310 when a radio link failure is detected. The operation of T310 can indicate that a radio link problem has occurred in the serving cell corresponding to the terminal device, such as a radio link failure (RLF).

[0139] It should be noted that, in the embodiments of this application, the duration of T310 can be greater than the duration of T312.

[0140] Step 203: Based on the number of cells in the cellsTriggeredList corresponding to the measurement identifier measId configured with T312 in the measurement report list VarMeasReportList, determine whether the T312 start-up conditions are met. If they are met, proceed to step 204; otherwise, proceed to step 205.

[0141] Step 204: Turn on T312.

[0142] Step 205: Skip the activation of T312.

[0143] In the embodiments of this application, if the number of cells in the cell trigger list cellsTriggeredList corresponding to the measurement identifier measId configured with T312 in the measurement report list VarMeasReportList is not 0, then it can be determined that the start condition of T312 is met, and T312 is selected to be started; otherwise, T312 is not started.

[0144] It is understood that, in the embodiments of this application, if the terminal device has already completed the T312 configuration, after detecting a radio link failure, it can first determine the number of cells in the cellsTriggeredList corresponding to the measurement identifier measId configured with T312 in the measurement report list VarMeasReportList. Since the cells in the cellsTriggeredList meet the triggering conditions of the corresponding measurement identifier measId, when the number of cells is not 0, it can be determined that there are cells that meet the fast recovery conditions, and thus T312 can be activated.

[0145] It should be noted that, in the embodiments of this application, the startup order of T312 and T310 is not strictly limited. That is, after detecting a radio link failure, if the number of cells in the cellTriggeredList is not 0, the terminal device can start T312 and T310. In other words, the terminal device can choose to start T312 and T310 simultaneously, or it can choose to start T310 first and then start T312.

[0146] Step 206: Determine if T312 has timed out. If it has timed out, proceed to step 207.

[0147] Step 207: Trigger RRC connection reconstruction.

[0148] In the embodiments of this application, after T312 is initiated, if T312 times out, the terminal device can further trigger RRC connection reconstruction. If T312 does not time out, step 206 is executed.

[0149] In other words, in the embodiments of this application, the start condition of T312 is no longer limited to starting T310 first and then triggering the event-type measurement report configured with T312. Therefore, in the case where the event-type measurement report configured with T312 is triggered first and T310 is started later, the terminal device can start T312 after determining that the number of cells in the cell trigger list cellsTriggeredList corresponding to the measurement identifier measId configured with T312 in the measurement report list VarMeasReportList is not 0, thereby ensuring the realization of fast handover failure recovery.

[0150] Therefore, the fast handover failure recovery method proposed in this application takes into account that the cells stored in the cell trigger list cellsTriggeredList all meet the trigger conditions of the corresponding measurement identifier measId in the cell trigger list cellsTriggeredList. Therefore, when T310 is started, the terminal device can first check the number of cellsTriggeredList cells corresponding to the measurement identifier measId configured with T312 in the measurement report list VarMeasReportList (number of cells). If the number is not 0, then it can be considered that there are cells that meet the conditions for fast recovery. Therefore, the terminal device can start T312 immediately, thereby solving the problem that fast handover failure recovery cannot be performed by triggering T312 when the event-type measurement report configured with T312 is triggered first and T310 is started later.

[0151] For example, in the embodiments of this application, such as Figure 12As shown, the relevant technology requires that T312 be started when a measurement configured with T312 triggers a measurement report after T310 has started. Therefore, if a measurement configured with T312 triggers a measurement report before T310 starts, T312 cannot be started after T310 starts, and thus fast handover failure recovery cannot be performed through T312 until T310 times out, at which point the terminal device can declare a radio link failure (RLF) and trigger reconstruction.

[0152] For example, in the embodiments of this application, Figure 15 Illustration of a scenario for rapid handover failure recovery Figure 2 ,like Figure 15 As shown, if the measurement report is triggered by the T312 configuration before T310 is started, T310 can be started first after a wireless link failure is detected. At the same time, the number of cells in the cellsTriggeredList corresponding to the measurement identifier measId configured by T312 is determined. If the number of cells is determined to be not 0, T312 can be started, and then T312 can be used for fast handover failure recovery until T312 times out, at which point the terminal device triggers reconstruction.

[0153] In contrast, the fast handover failure recovery method proposed in this application no longer restricts the order between the activation of T310 and the triggering of the measurement report. Instead, it determines whether to activate the already configured T312 based solely on the number of cells in the cell trigger list (cellsTriggeredList). This not only solves the problem of being unable to perform fast handover failure recovery in scenarios where the measurement report is triggered before T310 is activated, but also enables the early activation of T312, thereby achieving early triggering of the reconstruction process.

[0154] For example, in the embodiments of this application, Figure 16 Illustration of a scenario for rapid handover failure recovery Figure 3 ,like Figure 16 As shown, before T310 is started, if a measurement report is triggered by a measurement configured with T312, T310 can be started first after a radio link failure is detected. Simultaneously, the number of cells in the cellsTriggeredList corresponding to the measurement identifier (measId) configured with T312 is determined. It can also be determined whether the report was triggered when an old cell (the first cell) in the cellsTriggeredList meets the leave condition. If the old cell meets the leave condition and the number of cells is not zero, then T312 can be started, allowing for fast handover failure recovery until T312 times out, at which point the terminal device triggers reconstruction.

[0155] In other words, in the embodiments of this application, when a cell meets the leaving condition, if T310 has already been started, it also checks whether the number of cells in cellsTriggeredList is 0. If the number of cells is not 0, T312 is started immediately.

[0156] In contrast, the fast handover failure recovery method proposed in this application no longer restricts the order between the activation of T310 and the triggering of the measurement report. Instead, it determines whether to activate the already configured T312 based on the number of cells in the cell trigger list (cellsTriggeredList) and whether the old cell meets the leave conditions. This not only solves the problem of being unable to perform fast handover failure recovery in scenarios where the measurement report is triggered before T310 is activated, but also enables the early activation of T312, thereby achieving early triggering of the reconstruction process.

[0157] For example, in the embodiments of this application, Figure 17 Illustration of a scenario for rapid handover failure recovery Figure 4 ,like Figure 17 As shown, if the measurement report is triggered by T312 before T310 is started, and a wireless link failure is detected, T310 can be started first, while determining whether it is a periodic report from an old cell. If it is a periodic report from an old cell, then T312 can be started, and then fast handover failure recovery can be performed through T312 until T312 times out, at which point the terminal device triggers reconstruction.

[0158] It should be noted that, in the embodiments of this application, if it is determined to be a periodic report from an old cell, then it can be assumed that the number of cells in the cell trigger list cellsTriggeredList corresponding to the measurement identifier measId configured with T312 in the measurement report list VarMeasReportList is not 0, that is, it is determined that the cells in the cell trigger list cellsTriggeredList meet the triggering conditions of the corresponding measurement identifier measId, so T312 can be started directly.

[0159] In other words, in the embodiments of this application, when the cell meets the requirement of periodic reporting, if T310 has already been started, T312 will also be started.

[0160] In contrast, the method for fast handover failure recovery proposed in the embodiments of the present application no longer restricts the sequence between the start of T310 and the triggering of measurement reports. Instead, it determines whether to start the already configured T312 based on whether the old cell in the cell trigger list cellsTriggeredList is for periodic reporting. This not only solves the problem that fast handover failure recovery cannot be performed in the scenario where the measurement configured with T312 triggers the measurement report first and then T310 is started, but also can start T312 in advance. Correspondingly, the triggering of the reconstruction process is realized in advance.

[0161] It can be seen that in the embodiments of the present application, the related art does not involve satisfying the leaving condition or periodic reporting. If T310 has been started, T312 is also started. However, the method for fast handover failure recovery proposed in the embodiments of the present application can further select whether to trigger T312 by combining the determination of whether the leaving condition is satisfied or whether periodic reporting is satisfied, further solving the problem that fast handover failure recovery cannot be performed in some scenarios.

[0162] Further, in the embodiments of the present application, assume that NR cell 1 is the serving cell where the terminal device camps, and NR cell 2 is a neighbor cell of cell 1. When the terminal camps in cell 1, it enters the connected state and establishes a data service, and configures T310 through the configuration message sent by the network device corresponding to cell 1, where the duration of T310 is t0. The terminal device receives a reconfiguration message, and configures the measurement object and A3 event type measurement report for the frequency band where cell 2 is located according to the reconfiguration message, and configures the relevant parameters of T312, where the duration of T312 is t2, and t2 < t0. After triggering the A3 measurement report of cell 2, if the terminal device detects a radio link failure in cell 1, the terminal device can first check the number of cells in the cell trigger list cellsTriggeredList corresponding to the measurement identifier measId configured with T312 in the measurement report list VarMeasReportList. If the number of cells is not 0, the terminal device can start T310 and T312, and trigger reconstruction after T312 times out, that is, trigger RRC connection reconstruction at t2 time after detecting RLF.

[0163] In summary, in the embodiments of this application, a new method for starting the T312 timer is introduced to achieve rapid handover failure recovery. Specifically, after detecting a radio link failure, the terminal device can first check if there are any cells that meet the requirements for rapid handover failure recovery based on the number of cellsTriggeredList corresponding to the measurement identifier measId configured with T312 in the measurement report list VarMeasReportList. If the number is not zero, it indicates that there are cells that meet the rapid recovery conditions, and therefore T312 can be started immediately.

[0164] This application provides a method for rapid handover failure recovery. The terminal device configures a first timer based on a reconfiguration message. After detecting a radio link failure, if the number of cells in the cellsTriggeredList corresponding to the measurement identifier (measId) configured with the first timer in the measurement report list (VarMeasReportList) is not zero, the first timer is started. If the first timer times out, RRC connection reconstruction is triggered. Therefore, in this embodiment, after configuring the first timer, if a radio link failure is detected, the number of cells in the cellsTriggeredList corresponding to the measurement identifier (measId) configured with the first timer can be used to select whether to start the first timer, without restricting or requiring the triggering timing of the measurement report configured with the first timer. As long as the number of cells is not zero, the first timer can be started, thus overcoming the deficiency of not being able to perform rapid handover failure recovery in certain scenarios, thereby shortening the handover interruption time and improving the communication performance of the terminal device.

[0165] In the embodiments of this application, further, Figure 18 This is a schematic diagram of the component structure of the terminal device, such as... Figure 18 As shown, the terminal device 10 proposed in this application embodiment may include a processor 11, a memory 12 storing instructions executable by the processor 11, and further, the terminal device 10 may also include a communication interface 13 and a bus 14 for connecting the processor 11, the memory 12 and the communication interface 13.

[0166] In the embodiments of this application, the processor 11 can be at least one of the following: Application-Specific Integrated Circuit (ASIC), Digital Signal Processor (DSP), Digital Signal Processing Device (DSPD), Programmable Logic Device (PLD), Field-Programmable Gate Array (FPGA), Central Processing Unit (CPU), controller, microcontroller, and microprocessor. It is understood that for different devices, the electronic device used to implement the above-mentioned processor function can also be other types, and this application embodiment does not specifically limit this. The terminal device 10 may also include a memory 12, which can be connected to the processor 11. The memory 12 is used to store executable program code, which includes computer operation instructions. The memory 12 may include high-speed RAM memory and may also include non-volatile memory, such as at least two disk drives.

[0167] In embodiments of this application, bus 14 is used to connect communication interface 13, processor 11, and memory 12, as well as the mutual communication between these devices.

[0168] In embodiments of this application, memory 12 is used to store instructions and data.

[0169] Furthermore, in the embodiments of this application, the processor 11 is configured to configure a first timer according to the reconfiguration message; after detecting a radio link failure, if the number of cells in the cell trigger list cellsTriggeredList corresponding to the measurement identifier measId configured with the first timer in the measurement report list VarMeasReportList is not 0, then the first timer is started; if the first timer times out, then RRC connection reconstruction is triggered.

[0170] In practical applications, the aforementioned memory 12 can be volatile memory, such as random-access memory (RAM); or non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid-state drive (SSD); or a combination of the above types of memory, and provide instructions and data to the processor 11.

[0171] Furthermore, in this embodiment, the functional modules can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional module.

[0172] If the integrated unit is implemented as a software functional module and is not sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this embodiment, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the method of this embodiment. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0173] This application provides a terminal device that configures a first timer based on a reconfiguration message. Upon detecting a radio link failure, if the number of cells in the cellsTriggeredList corresponding to the measurement identifier (measId) configured with the first timer in the measurement report list (VarMeasReportList) is not zero, the first timer is started. If the first timer times out, RRC connection reconstruction is triggered. Therefore, in this application's embodiment, after configuring the first timer, if a radio link failure is detected, the number of cells in the cellsTriggeredList corresponding to the measurement identifier (measId) configured with the first timer can be used to determine whether to start the first timer, without restricting or requiring the triggering timing of the measurement report configured with the first timer. As long as the number of cells is not zero, the first timer can be started, thus overcoming the deficiency of not being able to quickly recover from handover failures in certain scenarios, thereby shortening the handover interruption time and improving the communication performance of the terminal device.

[0174] This application provides a chip, which includes programmable logic circuits and / or program instructions. When the chip is running, it implements the fast switching failure recovery method described above, including the following steps:

[0175] Configure the first timer according to the reconfiguration message;

[0176] After a wireless link failure is detected, if the number of cells in the cellsTriggeredList corresponding to the measurement identifier measId configured with the first timer in the measurement report list VarMeasReportList is not 0, then the first timer is started.

[0177] If the first timer times out, an RRC connection reconstruction is triggered.

[0178] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of hardware embodiments, software embodiments, or embodiments combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0179] This application is described with reference to schematic and / or block diagrams of implementations of methods, apparatus (systems), and computer program products according to embodiments of this application. It should be understood that each block of the schematic and / or block diagrams can be implemented by computer program instructions, and combinations of blocks in the schematic and / or block diagrams can be implemented. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the schematic and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0180] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in the implementation flow diagram. Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0181] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0182] The above description is merely a preferred embodiment of this application and is not intended to limit the scope of protection of this application.

Claims

1. A method for rapid handover failure recovery, characterized in that, The method includes: Configure a first timer according to a reconfiguration message; wherein, the reconfiguration message includes first timer parameters configured independently for different measurement objects and whether to apply the first timer for one or more measurement events; the first timer is T312; After a wireless link failure is detected, if the number of cells in the cellsTriggeredList corresponding to the measurement identifier measId configured with the first timer in the measurement report list VarMeasReportList is not 0, then the first timer is started. If the first timer times out, Radio Resource Control (RRC) connection reconstruction is triggered.

2. The method according to claim 1, characterized in that, The method further includes: After a wireless link failure is detected, a second timer is started.

3. The method according to claim 1, characterized in that, Before configuring the first timer according to the reconfiguration message, the method further includes: Receive the reconfiguration message; wherein the reconfiguration message is used for the configuration of the measurement object and the configuration of the first timer corresponding to the measurement object.

4. The method according to claim 2, characterized in that, The method further includes: After a wireless link failure is detected, if the number of cells in cellsTriggeredList is not 0, then the first timer and the second timer are started.

5. The method according to claim 4, characterized in that, The method further includes: After starting the second timer, start the first timer; or, The first timer and the second timer are started simultaneously.

6. The method according to claim 2, characterized in that, The method further includes: After the second timer is started, if the first cell meets the leave condition and the number of cellsTriggeredList is not 0, then the first timer is started; wherein, the first cell is any cell in cellsTriggeredList.

7. The method according to claim 2, characterized in that, The method further includes: After the second timer is started, if the first cell reports periodically, the first timer is started; wherein the first cell is any cell in the cellsTriggeredList.

8. The method according to any one of claims 2, 4, 5-7, characterized in that, The first timer is T312, and the second timer is T310.

9. The method according to any one of claims 2, 4, 5-7, characterized in that, The duration of the second timer is greater than the duration of the first timer.

10. A chip, characterized in that, The chip includes programmable logic circuitry and / or program instructions, which, when the chip is running, implement the method as described in any one of claims 1-9.

11. A terminal device, characterized in that, The terminal device includes a processor and a memory storing processor-executable instructions, which, when executed by the processor, implement the method as described in any one of claims 1-9.

Images