Failure detection and recovery method and device

Abstract

The embodiment of the invention provides a failure detection and recovery method and device. The method comprises the steps that terminal equipment carries out failure detection; and when the terminal equipment detects one of link failure, measurement report failure, cell switching command receiving failure, terminal processing failure and switching failure, recovering by applying the stored configuration and / or reporting the failure to the network equipment through a secondary cell and / or a non-serving cell. According to the embodiment of the invention, when one of link failure, measurement reporting failure, cell switching command receiving failure, terminal processing failure and switching failure is detected, the terminal application stored configuration and / or reporting through the secondary cell / non-serving cell fails, so that failure detection and recovery can be carried out more quickly, the service interruption time is reduced, and the user experience is improved. And user experience is improved.

Description

Failure detection and recovery method and device Technical Field

[0001] The embodiments of the present application relate to the field of communication technologies. Background Art

[0002] Network-controlled mobility applies to connected terminals and can be divided into two types of mobility: cell-level mobility and beam-level mobility.

[0003] The cell-level mobility requirement is triggered by explicit RRC (Radio Resource Control) signaling, that is, handover is triggered by RRC signaling.

[0004] The RRC-triggered handover mechanism requires the UE (User Equipment) to at least reset the MAC (Media Access Control) entity and re-establish the RLC (Radio Link Control), and supports RRC-managed handover with and without re-establishment of the PDCP (Packet Data Convergence Protocol) entity.

[0005] For DRBs (Data Radio Bearers) using RLC AM (Achnowledged Mode), PDCP can re-establish with a security key update or initiate a data recovery procedure "without a key update". For DRBs using RLC UM (Unachnowledged Mode), PDCP can re-establish with a security key update or remain unchanged "without a key update". For SRBs (Signalling Radio Bearers), PDCP can remain unchanged "without a key update", discard stored PDCP PDUs (Packet Data Unit) / SDUs (Service Data Unit), or re-establish with a security key update.

[0006] On the other hand, when a terminal moves from the coverage area of ​​one cell to the coverage area of ​​another, at some point a serving cell change needs to be performed. Currently, serving cell changes are triggered by L3 (Layer 3) measurements and completed by RRC signaling, with the addition of a synchronous reconfiguration (Reconfiguration with Synchronisation) triggered for PCell (Primary Cell) and PSCell (Primary Secondary Cell) changes, and the release of SCells (Secondary Cell), when applicable. All cases involve a complete L2 (Layer 2) (and L1 (Layer 1)) reset, resulting in longer latency, greater overhead and longer interruption time than beam switching mobility. The goal of L1 / L2 mobility enhancements is to ensure that serving cell changes via L1 / L2 signaling reduce latency, overhead and interruption time.

[0007] To reduce mobility delay, the L1 / L2-based inter-cell mobility mechanisms and processes include the following:

[0008] Configuration and maintenance of multiple candidate cells to allow rapid application of candidate cell configurations;

[0009] For potentially applicable scenarios, a dynamic handover mechanism between candidate serving cells (including special cells and secondary cells) based on L1 / L2 signaling;

[0010] L1 enhancements for inter-cell beam management, including L1 measurement and reporting, and beam indication;

[0011] Timed advance management; and

[0012] CU-DU (Centralized Unit-Distributed Unit) interface signaling to support L1 / L2 mobility.

[0013] It should be noted that the above introduction to the technical background is merely intended to provide a clear and complete description of the technical solutions of this application and facilitate understanding by those skilled in the art. Simply because these solutions are described in the background technology section of this application, it should not be assumed that the above technical solutions are well known to those skilled in the art.

[0014] Summary of the Invention

[0015] The inventors discovered that in the L1 / L2-based inter-cell mobility process, some components utilize existing mechanisms to accomplish new tasks, such as using the existing RRC reconfiguration process to complete a new candidate configuration; some components are new processes, such as processing a cell handover command. In both cases, it is currently unknown how to determine failure in these processes and take recovery measures. Furthermore, currently, handover failure, radio link failure, or reconfiguration failure all trigger an RRC connection reestablishment process; reusing this process would cause significant service disruption.

[0016] In response to at least one of the above problems or other similar problems, the embodiments of the present application provide a method and device for failure detection and recovery, which can detect possible failures more quickly and recover from failures more quickly, thereby reducing business interruption time and improving user experience.

[0017] According to one aspect of an embodiment of the present application, a failure detection and recovery device is provided, the device comprising:

[0018] a detection unit that performs failure detection;

[0019] A processing unit, which applies the stored configuration to recover and / or reports the failure to the network device via the secondary cell and / or non-serving cell when the detection unit detects one of a link failure, a measurement reporting failure, a cell switching command reception failure, a terminal processing failure, and a switching failure.

[0020] One of the beneficial effects of the embodiments of the present application is that: according to the embodiments of the present application, when one of link failure, measurement reporting failure, cell switching command reception failure, terminal processing failure and switching failure is detected, the terminal applies the stored configuration and / or reports the failure via the auxiliary cell / non-service cell, thereby enabling faster failure detection and recovery, thereby reducing service interruption time and improving user experience.

[0021] With reference to the following description and accompanying drawings, specific embodiments of the present application are disclosed in detail, indicating the manner in which the principles of the present application can be employed. It should be understood that the embodiments of the present application are not limited in scope. Within the spirit and scope of the appended claims, the embodiments of the present application include many variations, modifications and equivalents.

[0022] Features described and / or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0023] It should be emphasized that the term "include / comprising" when used herein refers to the presence of features, integers, steps or components, but does not exclude the presence or addition of one or more other features, integers, steps or components. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The elements and features described in one figure or one embodiment of the present application can be combined with the elements and features shown in one or more other figures or embodiments. In addition, in the accompanying drawings, similar reference numerals represent corresponding parts in several figures and can be used to indicate corresponding parts used in more than one embodiment.

[0025] FIG1 is a schematic diagram of mobility delay based on L1 / L2 inter-cell mobility;

[0026] FIG2 is a schematic diagram of a deployment scenario of an NG-RAN according to an embodiment of the present application;

[0027] FIG3 is a schematic diagram of a deployment scenario of an IAB according to an embodiment of the present application;

[0028] FIG4 is a schematic diagram of a failure detection and recovery method according to an embodiment of the present application;

[0029] FIG5 is another schematic diagram of the failure detection and recovery method according to an embodiment of the present application;

[0030] FIG6 is another schematic diagram of the failure detection and recovery method according to an embodiment of the present application;

[0031] FIG7 is another schematic diagram of the failure detection and recovery method according to an embodiment of the present application;

[0032] FIG8 is another schematic diagram of the failure detection and recovery method according to an embodiment of the present application;

[0033] FIG9 is another schematic diagram of the failure detection and recovery method according to an embodiment of the present application;

[0034] FIG10 is a schematic diagram of a failure detection and recovery device according to an embodiment of the present application;

[0035] FIG11 is another schematic diagram of the failure detection and recovery device according to an embodiment of the present application;

[0036] FIG12 is a schematic diagram of a terminal device according to an embodiment of the present application;

[0037] FIG13 is a schematic diagram of a network device according to an embodiment of the present application. DETAILED DESCRIPTION

[0038] The above and other features of the present application will become apparent through the following description with reference to the accompanying drawings. In the description and the accompanying drawings, specific embodiments of the present application are disclosed in detail, which illustrate some embodiments in which the principles of the present application can be adopted. It should be understood that the present application is not limited to the described embodiments. On the contrary, the present application includes all modifications, variations and equivalents that fall within the scope of the appended claims.

[0039] In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements from the name, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one and all combinations of one or more of the associated listed terms. The terms "comprising", "including", "having", etc. refer to the presence of the stated features, elements, components or components, but do not exclude the presence or addition of one or more other features, elements, components or components.

[0040] In the embodiments of this application, the singular forms "a," "the," etc. include plural forms and should be broadly understood to mean "a" or "a type" rather than being limited to "one." Furthermore, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. Furthermore, the term "according to" should be understood to mean "at least in part based on...", and the term "based on" should be understood to mean "at least in part based on...", unless the context clearly indicates otherwise.

[0041] In the embodiments of the present application, the term "communication network" or "wireless communication network" may refer to a network that complies with any of the following communication standards, such as Long Term Evolution (LTE), enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0042] Furthermore, communication between devices in the communication system may be carried out according to communication protocols of any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G, New Radio (NR), etc., and / or other communication protocols currently known or to be developed in the future.

[0043] In the embodiments of the present application, the term "network device" refers to, for example, a device in a communication system that connects a terminal device to the communication network and provides services to the terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0044] Base stations may include, but are not limited to, NodeBs (NBs), evolved NodeBs (eNodeBs or eNBs), and 5G base stations (gNBs), among others. They may also include remote radio heads (RRHs), remote radio units (RRUs), relays or low-power nodes (e.g., femeto, pico, etc.), IAB (Integrated Access and Backhaul) nodes, IAB-DUs, or IAB-donors. The term "base station" may include some or all of these functions, and each base station may provide communication coverage for a specific geographic area. The term "cell" may refer to a base station and / or its coverage area, depending on the context in which the term is used. The terms "cell" and "base station" are interchangeable to avoid confusion.

[0045] In the embodiments of the present application, the term "user equipment" (UE) or "terminal equipment" (TE) refers to, for example, a device that accesses a communication network through a network device and receives network services. A terminal device can be fixed or mobile and may also be referred to as a mobile station (MS), terminal, subscriber station (SS), access terminal (AT), IAB-MT (Mobile Terminal), station, etc.

[0046] Terminal devices may include, but are not limited to, the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smartphones, smart watches, digital cameras, etc.

[0047] For another example, in scenarios such as the Internet of Things (IoT), the terminal device can also be a machine or device for monitoring or measurement, including but not limited to: machine type communication (MTC) terminal, vehicle-mounted communication terminal, device-to-device (D2D) terminal, machine-to-machine (M2M) terminal, and so on.

[0048] In addition, the term "network side" or "network device side" refers to one side of the network, which can be a base station or one or more network devices as described above. The term "user side" or "terminal side" or "terminal device side" refers to the user or terminal side, which can be a UE or one or more terminal devices as described above. Unless otherwise specified herein, "device" can refer to either network equipment or terminal equipment.

[0049] Currently, NR (New Radio) supports a timer-based Handover Failure (HOF) procedure for handover failure detection and recovery. The RRC connection reestablishment procedure is used for handover failure recovery, except in certain CHO (Conditional Handover) or DAPS (Dual Active Protocol Stack) handover scenarios:

[0050] When DAPS handover fails, if the source link has not been released, the UE falls back to the source cell configuration, restores the connection with the source cell, and reports the DAPS handover failure through the source, without triggering RRC connection reestablishment;

[0051] When the initial CHO execution attempt fails or HO handover fails, the UE performs cell selection, and if the selected cell is a CHO candidate and if the network has configured the UE to attempt CHO after handover / CHO failure, the UE attempts CHO execution once, otherwise it performs re-establishment.

[0052] In addition, for the detection and recovery of radio link failure, the UE declares a radio link failure (RLF) when one of the following conditions is met:

[0053] The radio problem timer started after the indication of radio problem from the physical layer expires (if the radio problem is recovered before this timer expires, the UE stops this timer); or

[0054] The timer started when triggering a measurement report for a measurement ID configured with a timer expires while another radio problem timer is running; or

[0055] The random access procedure fails; or

[0056] RLC fails; or

[0057] Detection of a failure of a continuous uplink LBT (listen before talk) operation using a shared spectrum channel access operation; or

[0058] For the IAB-MT, a BH RLF (Backhaul Radio Link Failure) indication is received from its parent node.

[0059] In case of DAPS handover, the UE continues to detect radio link failure in the source cell until the random access procedure to the target cell is successfully completed.

[0060] After the RLF announcement, UE:

[0061] Maintain RRC_CONNECTED;

[0062] In case of DAPS handover, for RLF in the source cell:

[0063] Stop all data transmission or reception over the source link and release the source link, but maintain the source RRC configuration;

[0064] If a handover failure is subsequently detected in the target cell, the UE:

[0065] Select a suitable cell and initiate RRC reestablishment;

[0066] If no suitable cell is found within a certain period of time after the handover failure is declared, the system enters RRC_IDLE. In the case of CHO, for RLF in the source cell:

[0067] Select a suitable cell and if the selected cell is a CHO candidate and if the network has configured UE to attempt CHO after handover / CHO failure, then the UE attempts CHO execution once, otherwise performs re-establishment;

[0068] If no suitable cell is found within a certain period of time after the handover failure is declared, the system enters RRC_IDLE;

[0069] Otherwise, for RLF in the serving cell or in the target cell before releasing the source cell in case of DAPS handover:

[0070] Select a suitable cell and initiate RRC reestablishment;

[0071] If no suitable cell is found within a certain period of time after declaring RLF, it enters RRC_IDLE.

[0072] The inventors have discovered that, currently, the mobility delay of inter-cell mobility based on L1 / L2 includes the components shown in FIG1 , and the meaning of each component is shown in Table 1.

[0073] Table 1:

[0074]

[0075]

[0076] The above time values ​​are just examples.

[0077] As mentioned above, regarding failure detection, in the L1 / L2-based inter-cell mobility process, some components use existing mechanisms to complete new tasks, and some components are new processes. It is unknown how to determine whether the process has failed and take recovery measures. On the other hand, regarding failure recovery, the current failure will initiate the RRC connection re-establishment process. If this process is reused, it will introduce major service interruption.

[0078] This application is proposed to address at least one of the above problems. The embodiments of this application are described below with reference to the accompanying drawings and specific implementation methods.

[0079] In the embodiment of the present application, the scenarios for failure detection and recovery include but are not limited to handover scenarios, CA (carrier aggregation) scenarios, and DC (Dual Connectivity) scenarios. Among them, the handover scenario is the mobility of only the PCell. CA scenarios include, for example: a scenario where the target PCell / target SCell(s) is not the current serving cell, that is, a CA→CA scenario with a PCell change; a scenario where the target PCell is a current SCell; and a scenario where the target SCell is the current PCell. In addition, DC scenarios include scenarios where the PSCell changes (including non-CA scenarios and CA scenarios).

[0080] In the embodiment of the present application, the source cell and the target cell may be synchronous or asynchronous, may be co-frequency or different-frequency, and may operate in FR1 (frequency range 1) and FR2 (frequency range 2).

[0081] Figure 2 illustrates an NG-RAN deployment scenario according to an embodiment of the present application. As shown in Figure 2 , the NG-RAN includes a group of gNBs connected to the 5GC via the NG interface. gNBs can be interconnected via the Xn interface. A gNB includes a gNB-CU and one or more gNB-DUs. A gNB-CU and a gNB-DU are connected via the F1 interface, and a gNB-DU can only be connected to one gNB-CU.

[0082] Figure 3 is a schematic diagram of an IAB deployment scenario according to an embodiment of the present application. As shown in Figure 3, the NG-RAN supports IAB through an IAB-node wirelessly connected to a gNB capable of serving IAB-nodes, known as an IAB-donor. The IAB-donor includes an IAB-donor-CU and one or more IAB-donor-DU(s).

[0083] In the embodiments of this application, unless otherwise specified, all functions defined for gNB-DU are also applicable to IAB-DU and IAB-donor-DU, all functions defined for gNB-CU are also applicable to IAB-donor-CU, and all functions defined for UE are also applicable to IAB-MT.

[0084] In the following description, to avoid confusion, "failure" can be replaced with "recovery required," "if..." can be replaced with "under the circumstances" or "when...", "determining that a failure has occurred..." and "determining that a failure has been detected..." are interchangeable, and "determining whether a failure has occurred..." and "determining whether a failure has been detected..." are interchangeable. Furthermore, in the following description, lower layers refer to the physical layer, RF (Radio Frequency) chain, etc., and higher layers refer to the RRC layer, MAC layer, etc.

[0085] Embodiments of the first aspect

[0086] An embodiment of the present application provides a failure detection and recovery method, which is described from the perspective of a terminal device.

[0087] FIG4 is a schematic diagram of a failure detection and recovery method according to an embodiment of the present application. As shown in FIG4 , the method includes:

[0088] 401, the terminal device performs a failure detection;

[0089] 402. When the terminal device detects one of link failure, measurement reporting failure, cell switching command reception failure, terminal processing failure and switching failure, it applies the stored configuration for recovery and / or reports the failure to the network device via the secondary cell and / or non-service cell.

[0090] It is worth noting that FIG4 above only schematically illustrates an embodiment of the present application, and the present application is not limited thereto. For example, other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above content, and are not limited to the description of FIG4 above.

[0091] In the above embodiment, when one of link failure, measurement reporting failure, cell switching command reception failure, terminal processing failure and switching failure is detected, the terminal applies the stored configuration and / or reports the failure via the auxiliary cell / non-service cell, thereby enabling faster failure detection and recovery, thereby reducing service interruption time and improving user experience.

[0092] In some embodiments, when a terminal device detects one of a link failure, a measurement reporting failure, a failure to receive a cell handover command, a terminal processing failure, and a handover failure, a stored configuration is applied for recovery. If the stored configuration cannot be applied for recovery, the failure is reported to the network device via the secondary cell and / or the non-serving cell. That is, when a failure is detected, the stored configuration is first applied for recovery. If the stored configuration cannot be applied for recovery, for example, there is no stored configuration, or the stored configuration cannot be successfully restored, the failure is then reported to the network device via the secondary cell and / or the non-serving cell. This reduces the recovery latency and saves recovery signaling overhead.

[0093] In the above embodiment, the stored configuration refers to the configuration of the cell or cell group in the RRC reconfiguration message received and stored by the terminal device. For example, the terminal device may store the configuration of the cell or cell group in the RRC reconfiguration message received before detecting the above failure. The terminal device may store this configuration locally and attempt to apply this configuration for recovery when the above failure is detected.

[0094] In the above embodiment, the configuration of a cell or a cell group includes the configuration of a primary cell and / or the configuration of a secondary cell.

[0095] For example, when the above failure is detected or triggered, during the cell selection or reselection process, the terminal finds a suitable cell, which is a primary cell included in the previously received RRC reconfiguration message, and the terminal applies the stored configuration of this cell. Optionally, the terminal may also apply the configuration of the corresponding secondary cell (if any).

[0096] For another example, when the above failure is detected or triggered, if the conditions of a cell or cell group of the previously received RRC reconfiguration message are met, the terminal applies the stored configuration of a cell that meets the conditions; if this cell that meets the conditions is the primary cell, the terminal can optionally also apply the configuration of the corresponding secondary cell.

[0097] In the above embodiment, the configuration of the cell or cell group further includes beam information, and the beam information is, for example, TCI (Transmission Configuration Indication) status information of a downlink channel or an uplink channel or a reference signal.

[0098] In some embodiments, if there are more than N TCI status information, the terminal device may apply M TCI status information indicated in the more than N TCI status information or by default or determined through evaluation, where M≤N, and N is 1 or 2, depending on the capabilities of the terminal device.

[0099] For example, if the above-mentioned M TCI status information is indicated or default, then M=N, that is, the terminal device applies the indicated or default M TCI status information; if the above-mentioned M TCI status information is determined by evaluation, then M≤N, that is, the terminal device determines to apply the M TCI status information that meets the conditions through evaluation.

[0100] For example, based on the capabilities of terminal device 1, if there are more than two TCI status information, terminal device 1 may apply at most the first two TCI status information that appear, or apply at most two TCI status information corresponding to beams that meet the candidate beam conditions. For another example, based on the capabilities of terminal device 2, if there are more than one TCI status information, terminal device 2 may apply the first TCI status information that appears, or apply one TCI status information corresponding to a beam that meets the candidate beam conditions.

[0101] In other embodiments, reporting the failure to the network device via the secondary cell and / or the non-serving cell includes: reporting the failure to the network device via the secondary cell; and if the secondary cell is unavailable, reporting the failure to the network device via the non-serving cell. Alternatively, in other embodiments, reporting the failure to the network device via the secondary cell and / or the non-serving cell includes: reporting the failure to the network device via the non-serving cell; and if the non-serving cell is unavailable, reporting the failure to the network device via the secondary cell, for example, the non-serving cell is associated with a special cell.

[0102] For example, when a failure is detected, the stored configuration is first applied for recovery. If the stored configuration cannot be applied for recovery, for example, there is no stored configuration, or the stored configuration cannot be successfully restored, the failure is reported to the network device via the secondary cell. If the secondary cell is unavailable, the failure is reported to the network device via the non-service cell.

[0103] For another example, when a failure is detected, the secondary cell first reports the failure to the network device; if the secondary cell is unavailable, the failure is reported to the network device via the non-service cell; if there is no non-service cell or the non-service cell is unavailable, the stored configuration is applied for recovery.

[0104] The above two examples are just illustrations, and the present application is not limited thereto.

[0105] In the above embodiment, the non-serving cell is a candidate cell for handover, such as a candidate primary cell or a candidate secondary cell; or a cell associated with the current serving cell, such as a cell whose dedicated channel is being used by the terminal device, etc.

[0106] In the above embodiment, the terminal device may report the following content to the network device via the secondary cell and / or the non-serving cell:

[0107] Cell information of the failed cell;

[0108] Cause of failure and / or type of failure;

[0109] Measurement results;

[0110] Expected processing.

[0111] That is, the terminal device reports the failure by reporting at least one of the above contents.

[0112] In the above example, the cell information of the failed cell may include a cell index and / or a cell ID, such as a PCI (Physical Cell Identifier), an NCGI (NR Cell Global Identifier), etc. The cell index may be a serving cell index; or, alternatively, it may be the order in which the cell or cell group to which the cell belongs appears in the configuration of the cell or cell group in the RRC reconfiguration message, for example, the configuration of the first cell or cell group that appears corresponds to an index of 0 (or 1), the configuration of the second cell or cell group that appears corresponds to an index of 1 (or 2), and so on.

[0113] In the above example, the failure cause may be: the corresponding timer timeout, the number of received NACK (Negative Acknowledgement) reaching the maximum value, the number of RAP (Random Access Premble) transmissions reaching the maximum number, etc.; the failure type may be: link failure, measurement reporting failure, failure to receive cell switching command, terminal processing failure, switching failure, etc.

[0114] In the above example, the measurement results may include beam and / or cell measurement results based on L1 measurement or L3 measurement of the failed cell and / or the candidate cell that meets the conditions. For example, the terminal device reports the beam measurement result based on L1 measurement of the failed cell; for another example, the terminal device reports the beam measurement result based on L1 measurement of the candidate cell that meets the conditions, and so on.

[0115] In the above examples, the desired processing may be a beam change or a cell change, but the present application is not limited thereto.

[0116] For example, if the desired processing is beam change, the terminal device may indicate the desired beam or available beam, such as an identifier of a reference signal, such as an SSB index, a CSI-RS ID, or an SRS ID. Optionally, the terminal device also indicates the measurement result of the beam, such as L1 SS-RSRP, L1 SS-SINR, L1 CSI-RSRP, L1 CSI-SINR, etc.

[0117] For another example, if the desired processing is a cell change, the terminal device may indicate the desired cell or available cell, such as a cell identifier or index; the cell identifier may be a PCI or NCGI. Optionally, the terminal device also indicates the measurement result of the cell or the measurement result of the cell reference signal, such as RSRP, RSRQ, SINR, or SS-RSRP, SS-SINR, CSI-RSRP, CSI-SINR, etc.

[0118] In an embodiment of the present application, the terminal device may report the above failure through an RRC message, or may report the above failure through a MAC CE (MAC Control Element). The present application is not limited thereto. For example, depending on the content of the report, the terminal device may report the above failure through both the RRC message and the MAC CE.

[0119] For example, the terminal device reports the above failure through an RRC message. If the terminal device is configured with dual connectivity (such as NR-DC), and if SRB1 is configured as split SRB and pdcp-Duplication is not configured, the terminal device sets the primaryPath reference SCG (Secondary Cell Group) of the PDCP entity of the SRB1, and the RRC message is transmitted through the SRB1; otherwise, if SRB3 is configured and if SCG transmission is not suspended or allowed, the RRC message (embedded in another RRC message, such as ULInformationTransferMRDC message) is transmitted through SRB3. The RRC message can be a FailureInformation message or an MCGFailureInformation message, or a new RRC message.

[0120] For another example, the terminal device reports the above failure through MAC CE. When the secondary cell or non-service cell has available UL-SCH (Uplink Shared Channel) resources, and as a result of LCP (Logical Channel Prioritization), the resources are sufficient to accommodate the MAC CE used to carry the above information, the terminal device generates the MAC CE, otherwise it triggers SR (Scheduling Request). The network can configure a dedicated PUCCH (Physical Uplink Control Channel) resource or SR ID for this SR or make this SR use the PUCCH resource or SR ID of other SRs (such as the SR corresponding to the LCH (Logical Channel), the SR corresponding to the persistent LBT failure MAC CE, or the SR corresponding to the BFR (Beam Failure Recovery) MAC CE). This MAC CE is identified by a MAC subheader containing an LCID (Logical Channel Identification) or eLCID (enhanced LCID).

[0121] The above embodiments are merely exemplary descriptions of the terminal device reporting the above failure to the network device via the secondary cell and / or non-serving cell, but the present application is not limited thereto, and appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used individually, or one or more of the above embodiments may be combined.

[0122] In the embodiments of the present application, in some implementations, when the quality of the wireless link or the quality of the control channel is not good or poor, the terminal device considers that a link failure has occurred.

[0123] In the above embodiment, the radio link quality or the control channel quality is characterized by an L1 measurement result or a filtered L1 measurement result. When the L1 measurement result or the filtered L1 measurement result is worse than a configured threshold, the quality is considered "bad or poor." Similarly, when the L1 measurement result or the filtered L1 measurement result is better than a configured threshold, the quality is considered "good." In the embodiment of the present application, there is no restriction on the value of the threshold, and for example, it can be set according to network deployment.

[0124] In some embodiments, the terminal device performs failure detection, including: the physical layer of the terminal device measures the configured reference signal, provides poor and / or good quality indications to the upper layer, and the upper layer determines whether a link failure has occurred based on the received indications and / or timers.

[0125] In the above embodiments, the reference signal may be a reference signal for beam failure detection configuration (BFD-RS), or a reference signal for radio link monitoring configuration (RLM-RS), or a reference signal for fast or low-layer radio link failure detection configuration, but the present application is not limited thereto.

[0126] In the above embodiment, the reference signal may be configured per serving cell, that is, each serving cell is configured with one or a group of reference signals.

[0127] In the above embodiment, poor and / or good quality may mean that the L1 measurement result is worse or better than a configured threshold (or its equivalent value, referred to as the first threshold) by an offset or a period of time, or that the filtered L1 measurement result is worse or better than a configured threshold (or its equivalent value, referred to as the second threshold) by an offset or a period of time. Here, the L1 measurement result may be L1 RSRP, including SS-RSRP or CSI-RSRP; L1 RSRQ, including SS-RSRQ or CSI-RSRQ; or L1 SINR, including SS-SINR or CSI-SINR.

[0128] In the above embodiment, the filtered L1 measurement result refers to a measurement result obtained after processing (eg, calculating) the L1 measurement result, for example, it may be an average of multiple L1 measurement results within a period of time, or an average of multiple highest L1 measurement results.

[0129] In the above embodiment, the upper layer of the terminal device determines whether a link failure has occurred based on the received indication (poor quality and / or good quality indication) and / or the timer. Here, the upper layer may be the MAC layer and / or the RRC layer.

[0130] For example, when a higher layer of a terminal device receives a poor quality indication, it starts or restarts a first timer. When the first timer times out, it recalculates the number of poor quality indications. When M consecutive poor quality indications are received, it is considered that a link failure has occurred. In other words, whether a link failure has occurred is determined based on the number of poor quality indications.

[0131] For another example, when the upper layer of the terminal device receives M consecutive indications of poor quality, it starts a second timer. When the upper layer of the terminal device receives T indications of good quality, it stops the second timer. When the second timer times out, it is considered that a link failure has occurred. In other words, whether a link failure has occurred is determined based on whether the timer has timed out.

[0132] For another example, when the upper layer of the terminal device receives M consecutive indications of poor quality during the operation of the third timer, it is considered that a link failure has occurred. In other words, whether a link failure has occurred is determined based on the indication of poor quality and the timer.

[0133] For another example, if the terminal device's upper layer receives M consecutive poor quality indications, it considers a link failure. If the terminal device's upper layer receives T good quality indications, it recalculates the number of poor quality indications. In other words, whether a link failure has occurred is determined based on the poor quality indications and good quality indications.

[0134] For another example, when the upper layer of the terminal device receives M consecutive indications of poor quality, it is considered that a link failure has occurred. In other words, whether a link failure has occurred is determined only based on the indications of poor quality.

[0135] In the above embodiment, there is no restriction on the value of each timer, and it can be set as needed.

[0136] In other embodiments, the terminal device performs failure detection, including: the terminal device monitors NACK and / or ACK (Acknowledgement, positive feedback) of the HARQ process, and determines whether a link failure occurs based on the monitoring result.

[0137] For example, if S consecutive NACK indications are received within a period of time, it is considered that a link failure has occurred, and / or if no ACK indication is received within a period of time (eg, no S consecutive ACK indications are received), it is considered that a link failure has occurred.

[0138] In the above embodiment, the HARQ process may be a designated HARQ process, or one HARQ process, or all HARQ processes.

[0139] In the above embodiment, the physical layer of the terminal device may monitor the NACK and / or ACK of the HARQ process, or the MAC layer of the terminal device may monitor the NACK and / or ACK of the HARQ process.

[0140] The above embodiments are merely exemplary of how a terminal device determines that a link failure has occurred, but the present application is not limited thereto, and appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used individually, or one or more of the above embodiments may be combined.

[0141] In the embodiment of the present application, in other implementations, when the L1 or L2 signaling carrying the measurement result fails to be successfully sent to the network device, the terminal device considers that a measurement reporting failure has occurred.

[0142] In some embodiments, the terminal device performs failure detection, including: starting a fourth timer when the terminal device generates or submits to the lower layer or sends L1 or L2 signaling carrying measurement results; when the fourth timer times out, it is considered that a measurement reporting failure has occurred.

[0143] For example, when generating or sending L1 signaling carrying measurement results, or when generating L2 signaling carrying measurement results and submitting it to the lower layer, the terminal device starts the fourth timer. When the fourth timer expires, it is considered that a measurement reporting failure has occurred.

[0144] In the above embodiment, when an ACK is received from the above HARQ process (i.e., the HARQ process carrying the L1 or L2 signaling of the measurement result), or an UL authorization for scheduling a new transmission of the HARQ process is received, or a cell switching command is received, it means that the measurement report has been successful, and the above fourth timer can be stopped at this time.

[0145] In the above embodiment, the cell switching command may be carried by DCI (Downlink Control Information), MAC CE, RRC message, etc., but the present application is not limited thereto.

[0146] In other embodiments, the terminal device performs failure detection, including: the terminal device monitors the NACK and / or ACK of the HARQ process of the L1 or L2 signaling carrying the measurement result, and determines whether a measurement reporting failure occurs based on the monitoring result.

[0147] For example, if X consecutive NACK indications are received within a period of time, it is considered that a measurement reporting failure has occurred, and / or if no ACK indication is received within a period of time (eg, no consecutive X ACK indications are received), it is considered that a measurement reporting failure has occurred.

[0148] In the above embodiment, the physical layer of the terminal device may monitor the NACK and / or ACK of the HARQ process of the L1 or L2 signaling carrying the measurement results, or the MAC layer of the terminal device may monitor the NACK and / or ACK of the HARQ process of the L1 or L2 signaling carrying the measurement results.

[0149] In the above embodiment, there is no restriction on the value of the fourth timer, and it can be set as needed.

[0150] The above embodiments are merely exemplary of how a terminal device determines that a measurement reporting failure has occurred, but the present application is not limited thereto, and appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used individually, or one or more of the above embodiments may be combined.

[0151] In the embodiment of the present application, in some further implementations, after the L1 or L2 signaling carrying the measurement result is successfully sent, if the cell switching command is not received within a certain period of time, the terminal device considers that a failure to receive the cell switching command has occurred.

[0152] In some embodiments, the terminal device performs failure detection, including: the terminal device monitors the ACK indication of the HARQ process of the L1 or L2 signaling carrying the measurement result, and when the ACK indication is received, starts the fifth timer, and when the fifth timer times out, it is considered that a failure to receive the cell switching command has occurred.

[0153] That is, for the HARQ process of the L1 or L2 signaling carrying the measurement result, the terminal device starts the fifth timer when receiving the ACK indication, and when the fifth timer times out, it is considered that a failure to receive the cell switching command occurs.

[0154] In the above embodiment, the terminal device stops the fifth timer when receiving the cell switching command.

[0155] In the above embodiment, the cell switching command may be carried by DCI, MAC CE, or RRC message, etc., but the present application is not limited thereto.

[0156] In the above embodiment, there is no restriction on the value of the fifth timer, which can be set as needed.

[0157] The above embodiments are merely exemplary of how a terminal device determines that a cell handover command has failed to be received. However, the present application is not limited thereto, and appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used individually, or one or more of the above embodiments may be combined.

[0158] In the embodiments of the present application, in some further embodiments, when the terminal device fails to comply with (comply with) the RRC reconfiguration message carrying the candidate cell information, or fails to comply with (comply with) the configuration of the PCell in the RRC reconfiguration message carrying the candidate cell information, or fails to comply with (comply with) the PCell indicated by the L1 or L2 cell switching command in the RRC reconfiguration message carrying the candidate cell information, it is considered that a terminal processing failure has occurred.

[0159] In the above embodiment, the terminal processing includes processing the RRC reconfiguration message carrying the candidate cell information and / or the L1 or L2 cell switching command. However, due to terminal capability issues, it may not be able to comply with the above RRC reconfiguration message carrying the candidate cell information and / or the L1 or L2 cell switching command. When it is unable to comply with the above RRC reconfiguration message carrying the candidate cell information and / or the L1 or L2 cell switching command, it is considered that the terminal processing failure has occurred.

[0160] In the above embodiment, the PCell may be the configuration of any PCell in the above RRC reconfiguration message carrying the candidate cell information, or the configuration of a PCell in the above RRC reconfiguration message carrying the candidate cell information, but the present application is not limited thereto.

[0161] In the above embodiment, the configuration package of the PCell includes the configuration of L1, L2 or L3, such as MAC configuration, radio bearer configuration, RF configuration and the like.

[0162] The above embodiments are merely exemplary of how a terminal device determines that a terminal processing failure has occurred, but the present application is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used individually, or one or more of the above embodiments may be combined.

[0163] In the embodiment of the present application, in some further implementations, when the cell change based on L1 or L2 signaling fails, the terminal device considers that a handover failure has occurred.

[0164] In the above embodiment, the terminal device determines whether a handover failure occurs based on whether the cell change of L1 or L2 signaling succeeds or fails.

[0165] In some embodiments, the terminal device determines whether a handover failure has occurred based on a timer (referred to as a sixth timer) used to control a cell change based on L1 or L2 signaling.

[0166] In the above embodiment, the terminal device performs failure detection, including: when the terminal device receives L1 or L2 signaling for triggering a cell change, the terminal device starts a sixth timer, and when the sixth timer times out, it is considered that a handover failure has occurred.

[0167] In the above embodiment, when the terminal device completes the random access process, or the terminal device starts to communicate with the indicated cell, or the terminal device sends information to the target cell to indicate that the handover is completed or successfully switched to the target cell, it means that the handover has been completed. At this time, the terminal device stops the above-mentioned sixth timer.

[0168] In the above embodiment, there is no restriction on the value of the sixth timer, which can be set as needed.

[0169] In other embodiments, the terminal device determines whether a handover failure occurs based on the number of RA preamble transmissions.

[0170] In the above embodiment, the terminal device performs failure detection, including: the terminal device counts the number of RA preamble codes sent, and determines whether a handover failure occurs according to the statistical result.

[0171] For example, if the number of transmitted RA preambles exceeds a threshold (referred to as a third threshold), it is considered that a handover failure has occurred.

[0172] In the above embodiment, there is no restriction on the value of the third threshold, which can be set as needed.

[0173] In yet other embodiments, the terminal device determines whether a handover failure occurs based on the number of received ACK / NACKs.

[0174] In the above embodiment, the terminal device performs failure detection, including: the terminal device monitors the NACK and / or ACK of the HARQ process carrying the first UL data, and determines whether a handover failure occurs according to the monitoring result.

[0175] For example, if Y consecutive NACK indications are received within a period of time, it is considered that a handover failure has occurred; and / or if no ACK indication is received within a period of time (eg, no consecutive Y ACK indications are received), it is considered that a handover failure has occurred.

[0176] The above embodiments are merely exemplary of how a terminal device determines whether a handover failure has occurred, but the present application is not limited thereto, and appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used individually, or one or more of the above embodiments may be combined.

[0177] In an embodiment of the present application, in some implementations, when a failure is detected, the terminal device may also apply the configuration used before receiving the RRC reconfiguration message and / or cell switching command including the configuration of the candidate cell.

[0178] For example, when a link failure or a handover failure is detected, the terminal device may apply the configuration used before receiving the RRC reconfiguration message and / or the cell handover command including the configuration of the candidate cell.

[0179] The method of the embodiment of the present application is exemplarily described below with reference to the accompanying drawings.

[0180] FIG5 is another schematic diagram of the failure detection and recovery method according to an embodiment of the present application. As shown in FIG5 , the method includes:

[0181] 501, the terminal device performs failure detection after receiving the candidate configuration;

[0182] 502. When the terminal device detects a terminal processing failure, it applies a stored configuration and / or reports the failure to a network device via a secondary cell and / or a non-serving cell.

[0183] In the above example, the candidate configuration is, for example, an RRC reconfiguration message carrying candidate cell information.

[0184] In the above example, the method for performing failure detection and the method for reporting failure have been described previously, and their contents are incorporated here and will not be repeated here.

[0185] FIG6 is another schematic diagram of a failure detection and recovery method according to an embodiment of the present application. As shown in FIG6 , the method includes:

[0186] 601, the terminal device performs failure detection after sending the measurement report;

[0187] 602. When the terminal device detects a measurement reporting failure, it applies a stored configuration and / or reports the failure to a network device via a secondary cell and / or a non-serving cell.

[0188] In the above example, the method for performing failure detection and the method for reporting failure have been described previously, and their contents are incorporated here and will not be repeated here.

[0189] FIG7 is another schematic diagram of the failure detection and recovery method according to an embodiment of the present application. As shown in FIG7 , the method includes:

[0190] 701, the terminal device performs failure detection after sending the measurement report;

[0191] 702. When the terminal device detects a failure in receiving a cell switching command, it applies a stored configuration and / or reports the failure to a network device via a secondary cell and / or a non-serving cell.

[0192] In the above example, the method for performing failure detection and the method for reporting failure have been described previously, and their contents are incorporated here and will not be repeated here.

[0193] FIG8 is another schematic diagram of a failure detection and recovery method according to an embodiment of the present application. As shown in FIG8 , the method includes:

[0194] 801, the terminal device performs failure detection after receiving the cell handover command;

[0195] 802. When the terminal device detects a handover failure, it applies a stored configuration and / or reports the failure to a network device via a secondary cell and / or a non-serving cell.

[0196] In the above example, the method for performing failure detection and the method for reporting failure have been described previously, and their contents are incorporated here and will not be repeated here.

[0197] In the above example, optionally, if the terminal device applies the configuration of the cell indicated by the cell switching command, the terminal device may apply the configuration used before receiving the RRC reconfiguration message including the configuration of the candidate cell and / or the cell switching command.

[0198] It is worth noting that Figures 5 to 8 above are merely schematic illustrations of the embodiments of the present application, and the present application is not limited thereto. For example, other operations may be added or some operations may be omitted. Those skilled in the art may make appropriate modifications based on the above content, and are not limited to the descriptions of Figures 5 to 8 above.

[0199] The embodiment of the present application also provides a method for failure detection and recovery, which is explained from the network side, and the content that is the same as the previous text is not repeated.

[0200] FIG9 is a schematic diagram of a failure detection and recovery method according to an embodiment of the present application. As shown in FIG9 , the method includes:

[0201] 901. A network device receives a failure report from a terminal device, where the failure report is one of a link failure detected by the terminal device, a measurement report failure, a cell switching command reception failure, a terminal processing failure, and a switching failure.

[0202] In the above embodiment, the above failure reporting can be reported by the terminal device via the secondary cell or the non-serving cell. The content of failure detection and non-serving cell has been described in detail above and will not be repeated here.

[0203] In some embodiments, the network device may further configure thresholds for the terminal device, such as the first threshold to the third threshold, etc. This application does not limit the specific configuration method.

[0204] In some embodiments, the network device may further configure a timer for the terminal device, such as the aforementioned first to sixth timers, etc. This application does not limit the specific configuration method.

[0205] According to the method of the embodiment of the present application, when one of link failure, measurement reporting failure, cell switching command reception failure, terminal processing failure and switching failure is detected, the terminal applies the stored configuration and / or reports the failure via the auxiliary cell / non-service cell, thereby enabling faster failure detection and recovery, thereby reducing service interruption time and improving user experience.

[0206] Embodiments of the second aspect

[0207] An embodiment of the present application provides a failure detection and recovery device. The device may be, for example, a terminal device, or one or more components or assemblies configured on the terminal device. The device of the embodiment of the present application corresponds to the method of FIG. 4 of the embodiment of the first aspect, and the contents that are the same as those in the embodiment of the first aspect are not repeated here.

[0208] FIG10 is a schematic diagram of an example of a failure detection and recovery device according to an embodiment of the present application. As shown in FIG10 , the failure detection and recovery device 1000 according to an embodiment of the present application includes:

[0209] A detection unit 1001, which performs failure detection;

[0210] The processing unit 1002 applies the stored configuration to recover and / or reports the failure to the network device via the secondary cell and / or non-serving cell when detecting one of link failure, measurement reporting failure, cell switching command reception failure, terminal processing failure and switching failure.

[0211] In some embodiments, when the detection unit 1001 detects one of link failure, measurement reporting failure, cell switching command reception failure, terminal processing failure and switching failure, the processing unit 1002 applies the stored configuration for recovery; if the processing unit 1002 cannot apply the stored configuration for recovery, the processing unit 1002 reports the above failure to the network device via the secondary cell and / or non-service cell.

[0212] In some embodiments, the processing unit 1002 reports the failure to the network device via the secondary cell and / or the non-serving cell, including: reporting the failure to the network device via the secondary cell; if the secondary cell is unavailable, reporting the failure to the network device via the non-serving cell.

[0213] In some embodiments, the stored configuration is the configuration of the cell or cell group in the RRC reconfiguration message received and stored by the terminal device.

[0214] The configuration of the cell or cell group may include the configuration of the primary cell and / or the configuration of the secondary cell and beam information; the beam information is the TCI status information of the downlink channel or uplink channel or reference signal.

[0215] In some embodiments, if there are more than N TCI status information, the processing unit 1002 applies M TCI status information indicated in the more than N TCI status information or by default or determined through evaluation, where M≤N, N is 1 or 2, depending on the capabilities of the terminal device.

[0216] In some embodiments, the non-serving cell is a candidate cell for handover or a cell associated with the serving cell.

[0217] In some embodiments, the processing unit 1002 reports the above failure to the network device via the secondary cell and / or non-serving cell, including reporting at least one of the following: cell information of the failed cell; failure cause and / or failure type; measurement results; and expected processing.

[0218] In the above embodiment, the cell information of the failed cell may include at least one of the following: a cell index and a cell ID.

[0219] In the above embodiment, the failure cause may include at least one of the following: corresponding timer timeout, the number of NACKs received reaches the maximum value, and the RAP transmission reaches the maximum number; the failure type includes at least one of the following: link failure, measurement reporting failure, failure to receive cell switching command, terminal processing failure, and switching failure.

[0220] In the above embodiment, the measurement result may include measurement results of beams and / or cells of the failed cell and / or the candidate cell that meets the conditions, based on L1 measurement or L3 measurement.

[0221] In the above embodiment, the desired processing may include at least one of the following: beam change, cell change.

[0222] In some embodiments, the processing unit 1002 reports the failure via an RRC message or a MAC CE.

[0223] In some embodiments, when the quality of the wireless link or the quality of the control channel is not good or poor, the detection unit 1001 considers that a link failure has occurred.

[0224] For example, the detection unit 1001 (the physical layer of the terminal device) measures the configured reference signal and provides indications of poor and / or good quality to the upper layer; the detection unit 1001 (the upper layer of the terminal device) determines whether a link failure has occurred based on the received indications and / or timers.

[0225] In the above example, the higher layer may be a MAC layer and / or an RRC layer.

[0226] In the above example, the reference signal can be one of the following: a reference signal for beam failure detection configuration (BFD-RS); a reference signal for radio link monitoring configuration (RLM-RS); a reference signal for fast or low-layer radio link failure detection configuration.

[0227] In the above example, the reference signal may be configured per serving cell.

[0228] In the above examples, poor and / or good quality may mean that the L1 measurement result is worse and / or better than a configured first threshold; or that the filtered L1 measurement result is worse and / or better than a configured second threshold.

[0229] In the above example, the L1 measurement result may include at least one of the following: RSRP of L1, including SS-RSRP or CSI-RSRP; RSRQ of L1, including SS-RSRQ or CSI-RSRQ; SINR of L1, including SS-SINR or CSI-SINR.

[0230] In the above example, the filtered L1 measurement result refers to a measurement result obtained after processing the L1 measurement result, and may include, for example, an average value of L1 measurement results within a period of time, or an average value of multiple highest L1 measurement results.

[0231] In some embodiments, when the detection unit 1001 (the upper layer of the terminal device) receives an indication of poor quality, it starts or restarts a first timer; when the first timer times out, the number of indications of poor quality is recalculated; when M consecutive indications of poor quality are received, it is considered that a link failure has occurred.

[0232] In some embodiments, when the detection unit 1001 (the upper layer of the terminal device) receives M consecutive indications of poor quality, the second timer is started; when the detection unit 1001 (the upper layer of the terminal device) receives T indications of good quality, the second timer is stopped; when the second timer times out, it is considered that a link failure has occurred.

[0233] In some implementations, when the detection unit 1001 (a higher layer of the terminal device) receives M consecutive indications of poor quality during the running of the third timer, it is considered that a link failure has occurred.

[0234] In some embodiments, when the detection unit 1001 (the upper layer of the terminal device) receives M consecutive indications of poor quality, it is considered that a link failure has occurred; when the detection unit 1001 (the upper layer of the terminal device) receives T indications of good quality, the number of indications of poor quality is recalculated.

[0235] In some implementations, when the detection unit 1001 (a higher layer of the terminal device) receives M consecutive indications of poor quality, it is considered that a link failure has occurred.

[0236] For another example, the detection unit 1001 monitors the NACK and / or ACK of the HARQ process; and determines whether a link failure occurs according to the monitoring result.

[0237] In some implementations, if S consecutive NACK indications are received within a period of time, it is considered that a link failure has occurred; and / or if no ACK indication is received within a period of time, it is considered that a link failure has occurred.

[0238] In the above example, the HARQ process may be a designated HARQ process, or one HARQ process, or all HARQ processes.

[0239] In some other embodiments, when the L1 or L2 signaling carrying the measurement result fails to be successfully sent to the network, the detection unit 1001 considers that a measurement reporting failure occurs.

[0240] For example, when the terminal device generates or submits to the lower layer or sends L1 or L2 signaling carrying the measurement result, the detection unit 1001 starts the fourth timer; when the fourth timer times out, it is considered that a measurement reporting failure has occurred.

[0241] In the above example, when the terminal device receives an ACK of the HARQ process carrying L1 or L2 signaling of the measurement result, or receives an UL authorization for scheduling a new transmission of the HARQ process, or receives a cell switching command, the detection unit 1001 stops the fourth timer.

[0242] For another example, the detection unit 1001 monitors the NACK and / or ACK of the HARQ process of the L1 or L2 signaling carrying the measurement result; and determines whether the measurement reporting failure occurs according to the monitoring result.

[0243] In some implementations, if X consecutive NACK indications are received within a period of time, it is considered that a measurement reporting failure has occurred; and / or if no ACK indication is received within a period of time, it is considered that a measurement reporting failure has occurred.

[0244] In some further embodiments, after the L1 or L2 signaling carrying the measurement result is successfully sent, if no cell handover command is received within a certain period of time, the detection unit 1001 considers that a failure to receive the cell handover command occurs.

[0245] For example, for the HARQ process of L1 or L2 signaling carrying measurement results, when the terminal device receives an ACK indication, the detection unit 1001 starts the fifth timer; when the fifth timer times out, it is considered that a failure to receive the cell switching command occurs.

[0246] In the above example, when the terminal device receives the cell switching command, the detection unit 1001 may stop the fifth timer.

[0247] In the above example, the cell switching command may be carried by a DCI, a MAC CE, or an RRC message.

[0248] In some further embodiments, when the terminal device is unable to comply with the RRC reconfiguration message carrying the candidate cell information, or is unable to comply with the configuration of the PCell in the RRC reconfiguration message carrying the candidate cell information, or is unable to comply with the PCell indicated by the L1 or L2 cell switching command in the RRC reconfiguration message carrying the candidate cell information, the detection unit 1001 deems that a terminal processing failure has occurred.

[0249] In the above embodiment, the configuration of the PCell includes the configuration of L1, L2, or L3; the configuration of L1, L2, or L3 includes at least one of MAC configuration, radio bearer configuration, and RF configuration.

[0250] In some further embodiments, when the cell change based on L1 or L2 signaling fails, the detecting unit 1001 considers that a handover failure occurs.

[0251] For example, when the terminal device receives L1 or L2 signaling for triggering a cell change, the detection unit 1001 starts a sixth timer; when the sixth timer times out, it is considered that a handover failure has occurred.

[0252] In the above example, when the terminal device completes the random access process, or the terminal device starts to communicate with the indicated cell, or the terminal device sends information to the target cell to indicate that the handover is completed or successfully switched to the target cell, the detection unit 1001 stops the sixth timer.

[0253] For another example, the detection unit 1001 counts the number of RA preamble codes sent by the terminal device; and determines whether a handover failure occurs based on the statistical result.

[0254] In some implementations, if the number of RA preamble codes sent by the terminal device exceeds a third threshold, the detection unit 1001 considers that a handover failure has occurred.

[0255] For another example, the detection unit 1001 monitors the NACK and / or ACK of the HARQ process carrying the first UL data; and determines whether a handover failure occurs according to the monitoring result.

[0256] In the above example, in some embodiments, if the terminal device receives Y consecutive NACK indications within a period of time, the detection unit 1001 considers that a switching failure has occurred; and / or, if the terminal device does not receive an ACK indication within a period of time, the detection unit 1001 considers that a switching failure has occurred.

[0257] In an embodiment of the present application, optionally, in the event of a failure being detected, the processing unit 1002 may also apply the configuration used by the terminal device before receiving the RRC reconfiguration message and / or the cell switching command including the configuration of the candidate cell.

[0258] The present application provides a failure detection and recovery device. The device may be, for example, a network device, or one or more components or assemblies configured on the network device. The device of the present application corresponds to the method of FIG. 9 of the embodiment of the first aspect, and the contents identical to those of the embodiment of the first aspect are not repeated here.

[0259] FIG11 is a schematic diagram of an example of a failure detection and recovery device according to an embodiment of the present application. As shown in FIG11 , the failure detection and recovery device 1100 according to an embodiment of the present application includes:

[0260] The receiving unit 1101 receives a failure report from a terminal device, where the failure report is one of a link failure detected by the terminal device, a measurement report failure, a cell switching command reception failure, a terminal processing failure, and a switching failure.

[0261] In the above embodiment, the above failure reporting can be reported by the terminal device via the secondary cell or the non-serving cell. The content of failure detection and non-serving cell has been described in detail in the embodiment of the first aspect and will not be repeated here.

[0262] In some embodiments, as shown in FIG11 , the apparatus 1100 further includes:

[0263] The first configuration unit 1102 is used to configure thresholds for the terminal device, such as the first threshold to the third threshold described in the embodiment of the first aspect. The present application does not limit the specific configuration method.

[0264] In some embodiments, as shown in FIG11 , the apparatus 1100 further includes:

[0265] The second configuration unit 1103 is configured to configure a timer for the terminal device, such as the first timer to the sixth timer described in the embodiment of the first aspect. The present application does not limit the specific configuration method.

[0266] The above embodiments of the present application are illustrative, but the present application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0267] It is worth noting that the above description only describes the components or modules relevant to this application, but this application is not limited thereto. The failure detection and recovery devices 1000 and 1100 of the embodiments of this application may also include other components or modules. For the specific contents of these components or modules, reference may be made to the relevant art. In addition, the above components or modules may be implemented using hardware facilities such as processors, memories, transmitters, and receivers; this application is not limited to this.

[0268] The device according to the embodiment of the present application reduces service interruption time and improves user experience.

[0269] Embodiments of the third aspect

[0270] An embodiment of the present application also provides a communication system, including a network device and a terminal device.

[0271] In some embodiments, the terminal device includes the apparatus shown in FIG10 of the embodiment of the second aspect, and is configured to perform the method shown in FIG4 of the embodiment of the first aspect. Since the method has been described in detail in the embodiment of the first aspect, its content is incorporated herein and is not repeated.

[0272] In an embodiment of the present application, a terminal device includes the apparatus shown in FIG11 of the embodiment of the second aspect, and is configured to execute the method shown in FIG9 of the embodiment of the first aspect. Since the method has been described in detail in the embodiment of the first aspect, its content is incorporated herein and will not be repeated. In addition, the network device performs conventional operations of the network device, and the network device may also perform operations corresponding to the operations of the terminal device, such as the network device receiving information / signals from the terminal device and / or the network device sending information / signals to the terminal device, which description is omitted here.

[0273] An embodiment of the present application further provides a terminal device, which may be, for example, a UE, but the present application is not limited thereto and may also be other terminal devices.

[0274] Figure 12 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in Figure 12, terminal device 1200 may include a processor 1201 and a memory 1202. Memory 1202 stores data and programs and is coupled to processor 1201. It should be noted that this diagram is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunication or other functions.

[0275] In some embodiments, the functions of the device of the embodiment of the second aspect can be integrated into the processor 1201, wherein the processor 1201 can be configured to execute a program to implement the method described in the embodiment of the first aspect, the content of which is incorporated herein and will not be repeated here.

[0276] In other embodiments, the apparatus of the embodiment of the second aspect may be configured separately from the processor 1201. For example, the apparatus of the embodiment of the second aspect may be configured as a chip connected to the processor 1201, and the functions of the apparatus of the embodiment of the second aspect may be realized through the control of the processor 1201.

[0277] As shown in Figure 12 , the terminal device 1200 may further include: a communication module 1203, an input unit 1204, a display 1205, and a power supply 1206. The functions of these components are similar to those in the prior art and are not described in detail here. It is worth noting that the terminal device 1200 does not necessarily include all of the components shown in Figure 12 , and these components are not essential. Furthermore, the terminal device 1200 may also include components not shown in Figure 12 , for which reference may be made to related art.

[0278] An embodiment of the present application further provides a network device, which may be, for example, a base station, but the present application is not limited thereto and may also be other network devices.

[0279] Figure 13 is a schematic diagram illustrating the structure of a network device according to an embodiment of the present application. As shown in Figure 13 , network device 1300 may include a processor 1301 and a memory 1302 ; the memory 1302 is coupled to the processor 1301 . The memory 1302 may store various data and information processing programs, which are executed under the control of the processor 1301 .

[0280] In some embodiments, the functions of the device 1100 of the embodiment of the second aspect can be integrated into the processor 1301, wherein the processor 1301 can be configured to execute a program to implement the method described in Figure 9 of the embodiment of the first aspect, the content of which is incorporated herein and will not be repeated here.

[0281] In other embodiments, the device 1100 of the embodiment of the second aspect can be configured separately from the processor 1301. For example, the device 1100 of the embodiment of the second aspect can be configured as a chip connected to the processor 1301, and the functions of the device 1100 of the embodiment of the second aspect can be realized through the control of the processor 1301.

[0282] Furthermore, as shown in FIG13 , network device 1300 may further include transceivers 1303 and 1304. The functions of these components are similar to those in the prior art and are not further described here. It is worth noting that network device 1300 does not necessarily include all of the components shown in FIG13 ; furthermore, network device 1300 may also include components not shown in FIG13 , for which reference may be made to the prior art.

[0283] An embodiment of the present application further provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to execute the method described in the embodiment of the first aspect.

[0284] An embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program enables a terminal device to execute the method described in the embodiment of the first aspect.

[0285] The above devices and methods of the present application can be implemented by hardware or by a combination of hardware and software. The present application relates to such a computer-readable program that, when executed by a logic component, enables the logic component to implement the devices or components described above, or enables the logic component to implement the various methods or steps described above. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0286] The method / device described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figure and / or one or more combinations of functional block diagrams can correspond to various software modules of the computer program flow or to various hardware modules. These software modules can respectively correspond to the various steps shown in the figure. These hardware modules can be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).

[0287] The software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0288] One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may be implemented as a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any appropriate combination thereof for performing the functions described in this application. One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0289] The present application has been described above in conjunction with specific embodiments. However, those skilled in the art should understand that these descriptions are merely illustrative and are not intended to limit the scope of protection of the present application. Those skilled in the art may make various modifications and variations to the present application based on the spirit and principles of the present application, and such modifications and variations are also within the scope of the present application.

[0290] Regarding the implementation methods including the above embodiments, the following additional notes are also disclosed:

[0291] 1. A failure detection and recovery method, comprising:

[0292] The terminal device performs failure detection;

[0293] When the terminal device detects one of link failure, measurement reporting failure, cell switching command reception failure, terminal processing failure and switching failure, it applies the stored configuration and / or reports the failure to the network device via the secondary cell and / or non-serving cell.

[0294] 2. The method according to Supplement 1, wherein:

[0295] When the terminal device detects one of link failure, measurement reporting failure, cell handover command reception failure, terminal processing failure, and handover failure, applying the stored configuration;

[0296] If the stored configuration cannot be applied for recovery, the failure is reported to the network device via the secondary cell and / or the non-serving cell.

[0297] 3. The method according to note 1 or 2, wherein reporting the failure to the network device via the secondary cell and / or the non-serving cell comprises:

[0298] reporting the failure to the network device via the secondary cell;

[0299] If the secondary cell is unavailable, the failure is reported to the network device via a non-serving cell.

[0300] 4. The method according to Supplement 1, wherein:

[0301] The stored configuration is the configuration of the cell or cell group in the RRC reconfiguration message received and stored by the terminal device.

[0302] 5. The method according to Supplement 4, wherein:

[0303] The configuration of the cell or cell group includes the configuration of the primary cell and / or the configuration of the secondary cell and beam information;

[0304] The beam information is TCI status information of the downlink channel or uplink channel or reference signal.

[0305] 6. The method according to Supplementary Note 5, wherein:

[0306] If there are more than N TCI status information, the terminal device applies M TCI status information indicated in the more than N TCI status information or by default or determined through evaluation, where M≤N, N is 1 or 2, depending on the capability of the terminal device.

[0307] 7. The method according to Supplement 1, wherein:

[0308] The non-serving cell is a candidate cell for handover or a cell associated with the serving cell.

[0309] 8. The method according to note 1 or 7, wherein reporting the failure to the network device via the secondary cell and / or the non-serving cell comprises reporting at least one of the following:

[0310] Cell information of the failed cell;

[0311] Cause of failure and / or type of failure;

[0312] measurement results; and

[0313] Expected processing.

[0314] 9. The method according to Supplementary Note 8, wherein:

[0315] The cell information of the failed cell includes at least one of the following: a cell index and a cell ID.

[0316] 10. The method according to Supplementary Note 8, wherein:

[0317] The failure reason includes at least one of the following: the corresponding timer expires, the number of NACKs received reaches the maximum, and the number of RAP transmissions reaches the maximum;

[0318] The failure type includes at least one of the following: link failure, measurement reporting failure, cell handover command reception failure, terminal processing failure, and handover failure.

[0319] 11. The method according to Supplementary Note 8, wherein:

[0320] The measurement results include measurement results of beams and / or cells of failed cells and / or candidate cells that meet the conditions, based on L1 measurement or L3 measurement.

[0321] 12. The method according to Supplementary Note 8, wherein:

[0322] The desired processing includes at least one of the following: beam change, cell change.

[0323] 13. The method according to any one of Notes 1, 7-12, wherein the terminal device reports the failure via an RRC message or MAC CE.

[0324] 14. The method according to Supplement 1, wherein:

[0325] When the quality of the wireless link or the quality of the control channel is not good or poor, the terminal device determines that a link failure is detected.

[0326] 15. The method according to note 1 or 14, wherein the terminal device performs failure detection, comprising:

[0327] The physical layer of the terminal device measures the configured reference signal and provides an indication of poor quality and / or good quality to the upper layer of the terminal device;

[0328] The upper layer of the terminal device determines whether a link failure is detected based on the received indication and / or timer.

[0329] 16. The method according to Supplement 15, wherein:

[0330] The higher layer is the MAC layer and / or the RRC layer.

[0331] 17. The method according to Supplementary Note 15, wherein the reference signal is one of the following:

[0332] Reference signal for beam failure detection configuration (BFD-RS);

[0333] Reference signal for radio link monitoring configuration (RLM-RS);

[0334] Reference signals configured for fast or low-layer radio link failure detection.

[0335] 18. The method according to Supplement 17, wherein:

[0336] The reference signal is configured per serving cell.

[0337] 19. The method according to Supplement 15, wherein poor quality and / or good quality refers to:

[0338] The L1 measurement result is worse and / or better than a configured first threshold; or

[0339] The filtered L1 measurement result is worse and / or better than a configured second threshold.

[0340] 20. The method according to Supplementary Note 19, wherein the L1 measurement result includes at least one of the following:

[0341] L1 RSRP, including SS-RSRP or CSI-RSRP;

[0342] L1 RSRQ, including SS-RSRQ or CSI-RSRQ;

[0343] L1 SINR, including SS-SINR or CSI-SINR.

[0344] 21. The method according to Supplement 19, wherein:

[0345] The filtered L1 measurement result refers to a measurement result obtained after processing the L1 measurement result, including: an average value of L1 measurement results within a period of time, or an average value of multiple highest L1 measurement results.

[0346] 22. The method according to Note 15, wherein:

[0347] When the upper layer of the terminal device receives the indication of poor quality, start or restart a first timer; when the first timer times out, recalculate the number of indications of poor quality; when M consecutive indications of poor quality are received, determine that a link failure is detected; or

[0348] When the upper layer of the terminal device receives M consecutive indications of poor quality, the second timer is started; when the upper layer of the terminal device receives T indications of good quality, the second timer is stopped; when the second timer times out, it is determined that a link failure is detected; or

[0349] When the upper layer of the terminal device receives M consecutive indications of poor quality during the running of the third timer, it is determined that a link failure is detected; or

[0350] When the upper layer of the terminal device receives M consecutive indications of poor quality, it is determined that a link failure is detected; when the upper layer of the terminal device receives T indications of good quality, the number of indications of poor quality is recalculated; or

[0351] When the upper layer of the terminal device receives M consecutive indications of poor quality, it is determined that a link failure is detected.

[0352] 23. The method according to note 1 or 14, wherein the terminal device performs failure detection, comprising:

[0353] The terminal device monitors NACK and / or ACK of the HARQ process;

[0354] The terminal device determines whether a link failure is detected based on the monitoring result.

[0355] 24. The method according to supplementary note 23, wherein determining whether a link failure is detected according to the monitoring result comprises:

[0356] If S consecutive NACK indications are received within a period of time, it is determined that a link failure is detected; and / or,

[0357] If no ACK indication is received within a period of time, it is determined that a link failure is detected.

[0358] 25. The method according to Note 23 or 24, wherein:

[0359] The HARQ process is a designated HARQ process, or one HARQ process, or all HARQ processes.

[0360] 26. The method according to Supplement 1, wherein:

[0361] When the L1 or L2 signaling carrying the measurement result fails to be successfully sent to the network, the terminal device determines that a measurement reporting failure is detected.

[0362] 27. The method according to note 1 or 26, wherein the terminal device performs failure detection, comprising:

[0363] When generating or submitting to a lower layer or sending L1 or L2 signaling carrying a measurement result, the terminal device starts a fourth timer;

[0364] When the fourth timer times out, the terminal device determines that a measurement reporting failure has been detected.

[0365] 28. The method according to Supplementary Note 27, wherein:

[0366] The fourth timer is stopped when an ACK of the HARQ process carrying the L1 or L2 signaling of the measurement result is received, or an UL grant for scheduling a new transmission of the HARQ process is received, or a cell handover command is received.

[0367] 29. The method according to note 1 or 26, wherein the terminal device performs failure detection, comprising:

[0368] The terminal device monitors NACK and / or ACK of the HARQ process of the L1 or L2 signaling carrying the measurement result;

[0369] The terminal device determines whether measurement reporting failure is detected based on the monitoring result.

[0370] 30. The method according to supplementary note 29, wherein determining whether measurement reporting failure is detected according to the monitoring result comprises:

[0371] If X consecutive NACK indications are received within a period of time, it is determined that a measurement reporting failure has been detected; and / or,

[0372] If no ACK indication is received within a period of time, it is determined that a measurement reporting failure is detected.

[0373] 31. The method according to Supplement 1, wherein:

[0374] After the L1 or L2 signaling carrying the measurement result is successfully sent, if no cell switching command is received within a certain period of time, the terminal device determines that a failure in receiving the cell switching command is detected.

[0375] 32. The method according to note 1 or 31, wherein the terminal device performs failure detection, comprising:

[0376] The terminal device starts a fifth timer when receiving an ACK indication for the HARQ process of the L1 or L2 signaling carrying the measurement result;

[0377] When the fifth timer times out, the terminal device determines that a failure to receive a cell switching command has been detected.

[0378] 33. The method according to Note 32, wherein:

[0379] When the cell switching command is received, the fifth timer is stopped.

[0380] 34. The method according to Note 32, wherein:

[0381] The cell switching command is carried by DCI, MAC CE or RRC message.

[0382] 35. The method according to Note 1, wherein:

[0383] When the terminal device cannot comply with the RRC reconfiguration message carrying the candidate cell information, or cannot comply with the configuration of the PCell in the RRC reconfiguration message carrying the candidate cell information, or cannot comply with the PCell indicated by the L1 or L2 cell switching command in the RRC reconfiguration message carrying the candidate cell information, the terminal device determines that the terminal processing failure is detected.

[0384] 36. The method according to Note 35, wherein:

[0385] The configuration of the PCell includes a configuration of L1, L2, or L3;

[0386] The configuration of L1, L2 or L3 includes at least one of MAC configuration, radio bearer configuration and RF configuration.

[0387] 37. The method according to Note 1, wherein:

[0388] When the cell change based on L1 or L2 signaling fails, the terminal device determines that a handover failure is detected.

[0389] 38. The method according to note 1 or 37, wherein the terminal device performs failure detection, comprising:

[0390] The terminal device starts a sixth timer when receiving L1 or L2 signaling for triggering a cell change;

[0391] When the sixth timer times out, the terminal device determines that a switching failure is detected.

[0392] 39. The method according to Supplement 38, wherein:

[0393] When the terminal device completes the random access process, or the terminal device starts to communicate with the indicated cell, or the terminal device sends information to the target cell to indicate the completion of the handover or successful handover to the target cell, the terminal device stops the sixth timer.

[0394] 40. The method according to Supplement 1 or 37, wherein the terminal device performs failure detection, comprising:

[0395] The terminal device counts the number of sent RA preamble codes;

[0396] The terminal device determines whether a handover failure is detected based on the statistical result.

[0397] 41. The method according to supplementary note 40, wherein determining whether a handover failure is detected based on the statistical result comprises:

[0398] If the number of transmitted RA preambles exceeds a third threshold, it is determined that handover failure is detected.

[0399] 42. The method according to Supplement 1 or 37, wherein the terminal device performs failure detection, comprising:

[0400] The terminal device monitors the NACK and / or ACK of the HARQ process carrying the first UL data;

[0401] The terminal device determines whether a switching failure is detected based on the monitoring result.

[0402] 43. The method according to supplementary note 42, wherein determining whether a handover failure is detected according to the monitoring result comprises:

[0403] If Y consecutive NACK indications are received within a period of time, it is determined that a handover failure is detected; and / or,

[0404] If no ACK indication is received within a period of time, it is determined that a handover failure is detected.

[0405] 44. The method according to any one of Notes 1 to 43, wherein the method further comprises:

[0406] The terminal device application receives the configuration used before the RRC reconfiguration message and / or the cell switching command including the configuration of the candidate cell.

[0407] 45. A terminal device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method as described in any one of Notes 1 to 44.

[0408] 46. ​​A communication system comprising a network device and the terminal device described in Note 45.

Claims

1. A failure detection and recovery device, wherein: The device comprises: a detection unit that performs failure detection; A processing unit, when the detection unit detects one of a link failure, a measurement reporting failure, a failure to receive a cell switching command, a terminal processing failure, and a switching failure, the processing unit applies a stored configuration and / or reports the failure to a network device via a secondary cell and / or a non-serving cell.

2. The device according to claim 1, wherein The stored configuration is the configuration of the cell or cell group in the radio resource control reconfiguration message received and stored by the terminal device.

3. The device according to claim 2, wherein The configuration of the cell or cell group includes the configuration of the primary cell and / or the configuration of the secondary cell and beam information; The beam information is transmission configuration indication status information of a downlink channel or an uplink channel or a reference signal.

4. The device according to claim 1, wherein The non-serving cell is a candidate cell for handover or a cell associated with the serving cell.

5. The device according to claim 1, wherein Reporting the failure to the network device via the secondary cell and / or the non-serving cell includes reporting at least one of the following: Cell information of the failed cell; Cause of failure and / or type of failure; measurement results; and Expected processing.

6. The device according to claim 5, wherein The failure reason includes at least one of the following: the corresponding timer timeout, the number of received negative feedback reaches the maximum value, and the random access preamble code transmission reaches the maximum number; The failure type includes at least one of the following: link failure, measurement reporting failure, cell handover command reception failure, terminal processing failure, and handover failure.

7. The device according to claim 5, wherein The desired processing includes at least one of the following: beam change, cell change.

8. The device according to claim 1, wherein The detection unit performs failure detection, including: The detection unit measures the configured reference signal at the physical layer of the terminal device and provides an indication of poor quality and / or good quality to the upper layer of the terminal device; The detection unit determines whether a link failure is detected based on the received indication and / or timer at a higher layer of the terminal device.

9. The device according to claim 8, wherein The reference signal is one of the following: Reference signals for beam failure detection configuration; Reference signal for wireless link monitoring configuration; Reference signals configured for fast or low-layer radio link failure detection.

10. The device according to claim 8, wherein When the upper layer of the terminal device receives the indication of poor quality, the detection unit starts or restarts a first timer; when the first timer times out, the detection unit recalculates the number of indications of poor quality; when the upper layer of the terminal device receives M consecutive indications of poor quality, the detection unit determines that a link failure is detected; or When the upper layer of the terminal device receives M consecutive indications of poor quality, the detection unit starts a second timer; when the upper layer of the terminal device receives T indications of good quality, the detection unit stops the second timer; when the second timer times out, the detection unit determines that a link failure has been detected; or When the upper layer of the terminal device receives M consecutive indications of poor quality during the operation of the third timer, the detection unit determines that a link failure is detected; or When the upper layer of the terminal device receives M consecutive indications of poor quality, the detection unit determines that a link failure is detected; when the upper layer of the terminal device receives T indications of good quality, the detection unit recalculates the number of indications of poor quality; or When the upper layer of the terminal device receives M consecutive indications of poor quality, the detection unit determines that a link failure is detected.

11. The device according to claim 1, wherein The detection unit performs failure detection, including: The detection unit monitors negative feedback and / or positive feedback of the hybrid automatic repeat request process; The detection unit determines whether a link failure is detected according to the monitoring result.

12. The device according to claim 11, wherein Determine whether a link failure is detected based on the monitoring results, including: If S consecutive negative feedback indications are received within a period of time, it is determined that a link failure is detected; and / or, If no positive feedback indication is received within a period of time, it is determined that a link failure is detected.

13. The device according to claim 1, wherein When the layer 1 or layer 2 signaling carrying the measurement result fails to be successfully sent to the network, the detection unit determines that a measurement reporting failure is detected.

14. The device according to claim 1, wherein After the layer 1 or layer 2 signaling carrying the measurement result is successfully sent, if no cell handover command is received within a certain period of time, the detection unit determines that a failure in receiving the cell handover command is detected.

15. The device according to claim 1, wherein When the terminal device is unable to comply with the wireless resource control reconfiguration message carrying the candidate cell information, or is unable to comply with the configuration of the primary cell in the wireless resource control reconfiguration message carrying the candidate cell information, or is unable to comply with the primary cell indicated by the layer 1 or layer 2 cell switching command in the wireless resource control reconfiguration message carrying the candidate cell information, the detection unit determines that the terminal processing failure is detected.

16. The device according to claim 1, wherein The detection unit performs failure detection, including: When the terminal device receives layer 1 or layer 2 signaling for triggering a cell change, the detection unit starts a sixth timer; When the sixth timer times out, the detection unit determines that a handover failure is detected.

17. The device according to claim 1, wherein The detection unit performs failure detection, including: The detection unit counts the number of random access preamble codes sent; The detection unit determines whether a handover failure is detected according to the statistical result.

18. The device according to claim 17, wherein Determine whether a handover failure is detected based on the statistical results, including: If the number of transmitted random access preambles exceeds a third threshold, it is determined that handover failure is detected.

19. The device according to claim 1, wherein The detection unit performs failure detection, including: The detection unit monitors the negative feedback and / or positive feedback of the hybrid automatic repeat request process carrying the first uplink data; The detection unit determines whether a handover failure is detected according to the monitoring result.

20. The device according to claim 1, wherein The processing unit applies the configuration used before receiving the radio resource control reconfiguration message and / or the cell handover command including the configuration of the candidate cell.

Images