Beam failure handling method and terminal

Abstract

Embodiments of this disclosure provide a beam failure handling method and a terminal. The method includes: triggering (201) transmission of at least one of BFRQ information and a scheduling request SR for BFRQ if a beam failure occurs in an SCell, where the terminal has at least one of the following features related to the SCell: if a first condition is met, triggering transmission of at least one of subsequent BFRQ information and subsequent SRs for BFRQ is forbidden; triggering transmission of at least one SR for BFRQ is allowed; and triggering transmission of BFRQ information is restricted to one time; if a second condition is met, a BFI counter skips or stops counting; and if a third condition is met, a BFI counter is reset, where the third condition includes at least one of the following: beam failure recovery succeeds, triggering transmission of at least one of subsequent BFRQ information and subsequent SRs for BFRQ is forbidden, and the forbidding of the triggering transmission of at least one of subsequent BFRQ information and subsequent SRs for BFRQ is lifted.

Description

Handling methods and terminals for beam failure

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 201910786784.8, filed in China on August 23, 2019, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This disclosure relates to the field of communication technology, and in particular to a method and terminal for handling beam failure. Background Technology

[0004] In some high-frequency communication systems (e.g., 5G systems), the short wavelength of wireless signals makes them susceptible to signal propagation obstruction, leading to signal interruption. Therefore, beam failure recovery (BFR) mechanisms are implemented in some communication systems. However, how to send BFRQ messages when beam failure occurs in a secondary cell (SCell) is undefined, thus preventing BFR from being supported in SCells.

[0005] Summary of the Invention

[0006] This disclosure provides a method and terminal for handling beam failures, to address the problem that the method for sending BFRQ messages when beam failure occurs in the SCell is not yet defined, which prevents BFR from being supported in the SCell.

[0007] In a first aspect, embodiments of this disclosure provide a method for handling beam failure, applied to a terminal, including:

[0008] If a beam failure occurs in the SCell, at least one of the following is triggered: sending a BFRQ message and a BFRQ scheduling request (SR).

[0009] The terminal, for the SCell, possesses at least one of the following features:

[0010] If the first condition is met, then triggering the sending of at least one of the following: subsequent BFRQ information and BFRQ SR;

[0011] Allows triggering the sending of an SR for at least one BFRQ;

[0012] Limit the trigger to send a BFRQ message only once;

[0013] If the second condition is met, the beam failure instance (BFI) counter will not count.

[0014] If the third condition is met, the BFI counter is reset;

[0015] The third condition includes at least one of the following:

[0016] The beam failure recovery is successful, the triggering of at least one of the following BFRQ information and BFRQ SR is prohibited, and the prohibition of triggering the transmission of at least one of the following BFRQ information and BFRQ SR is lifted.

[0017] Secondly, embodiments of this disclosure provide a terminal, including:

[0018] The triggering module is used to trigger at least one of the following if a beam failure occurs in the SCell: sending BFRQ information and BFRQ scheduling request SR.

[0019] The terminal, for the SCell, possesses at least one of the following features:

[0020] If the first condition is met, then triggering the sending of at least one of the following: subsequent BFRQ information and BFRQ SR;

[0021] Allows triggering the sending of an SR for at least one BFRQ;

[0022] Limit the trigger to send a BFRQ message only once;

[0023] If the second condition is met, the BFI counter will not count;

[0024] If the third condition is met, the BFI counter is reset;

[0025] The third condition includes at least one of the following:

[0026] The beam failure recovery is successful, the triggering of at least one of the following BFRQ information and BFRQ SR is prohibited, and the prohibition of triggering the transmission of at least one of the following BFRQ information and BFRQ SR is lifted.

[0027] Thirdly, embodiments of this disclosure provide a terminal, including: a memory, a processor, and a program stored in the memory and executable on the processor, wherein when the program is executed by the processor, it implements the steps in the beam failure handling method provided in embodiments of this disclosure.

[0028] Fourthly, embodiments of this disclosure provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps in the beam failure handling method provided in embodiments of this disclosure.

[0029] In this embodiment of the disclosure, if a beam failure occurs in the SCell, at least one of BFRQ information and a BFRQ scheduling request (SR) is triggered. The terminal, for the SCell, possesses at least one of the following features: if a first condition is met, triggering the transmission of at least one subsequent BFRQ information and BFRQ SR is prohibited; triggering the transmission of at least one BFRQ SR is allowed; triggering the transmission of BFRQ information is restricted to once; if a second condition is met, the BFI counter is not counted; if a third condition is met, the BFI counter is reset. The third condition includes at least one of the following: successful beam failure recovery, prohibition of triggering the transmission of at least one subsequent BFRQ information and BFRQ SR, and lifting the prohibition of triggering the transmission of at least one subsequent BFRQ information and BFRQ SR. This supports BFR in the SCell. Attached Figure Description

[0030] Figure 1 is a structural diagram of a network system that can be applied to an embodiment of this disclosure;

[0031] Figure 2 is a flowchart of a beam failure handling method provided in an embodiment of this disclosure;

[0032] Figure 3 is a structural diagram of a terminal provided in an embodiment of this disclosure;

[0033] Figure 4 is a structural diagram of another terminal provided in an embodiment of this disclosure. Detailed Implementation

[0034] The technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this disclosure. Based on the embodiments of this disclosure, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this disclosure.

[0035] The term "comprising," and any variations thereof, used in the specification and claims of this application, is intended to cover a non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not necessarily limited to those explicitly listed, but may include other steps or units not explicitly listed or inherent to such process, method, product, or apparatus. Furthermore, the use of "and / or" in the specification and claims indicates at least one of the connected objects, such as A and / or B, indicating the inclusion of A alone, B alone, or both A and B.

[0036] In this disclosure, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design described as "exemplary" or "for example" in this disclosure should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0037] The embodiments of this disclosure are described below with reference to the accompanying drawings. The beam failure handling method and terminal provided in the embodiments of this disclosure can be applied to a wireless communication system. The wireless communication system can be a New Radio (NR) system, an Evolved Long Term Evolution (eLTE) system, a Long Term Evolution (LTE) system, or a subsequent evolution communication system, etc.

[0038] Please refer to Figure 1. Figure 1 is a structural diagram of a network system applicable to an embodiment of this disclosure. As shown in Figure 1, it includes a terminal 11 and a network device 12. The terminal 11 can be a user equipment (UE) or other terminal-side device, such as a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), mobile internet device (MID), wearable device, or robot. It should be noted that the specific type of terminal 11 is not limited in this embodiment. The network device 12 can be a 4G base station, a 5G base station, a later version of a base station, or a base station in other communication systems, or referred to as a node B, evolved node B, transmission reception point (TRP), access point (AP), or other terms in the field, as long as the same technical effect is achieved, the network device is not limited to specific technical terms. In addition, the network device 12 can be a master node (MN) or a secondary node (SN). It should be noted that this embodiment only uses a 5G base station as an example, but does not limit the specific type of network equipment.

[0039] Please refer to Figure 2, which is a flowchart of a beam failure handling method provided by an embodiment of this disclosure. The method is applied to a terminal, and as shown in Figure 2, includes the following steps:

[0040] Step 201: If a beam failure occurs in SCell, trigger at least one of the following: transmit BFRQ information and BFRQ scheduling request SR.

[0041] The terminal, for the SCell, possesses at least one of the following features:

[0042] If the first condition is met, then triggering the sending of at least one of the following: subsequent BFRQ information and BFRQ SR;

[0043] Allows triggering the sending of an SR for at least one BFRQ;

[0044] Limit the trigger to send a BFRQ message only once;

[0045] If the second condition is met, the BFI counter (BFI_COUNTER) will not count;

[0046] If the third condition is met, then reset the BFI counter (BFI_COUNTER).

[0047] The third condition includes at least one of the following:

[0048] Beam failure recovery successful;

[0049] Prevent triggering the sending of at least one of the following: subsequent BFRQ messages and BFRQ SRs;

[0050] Remove the prohibition on at least one of the following: triggering the transmission of subsequent BFRQ information and the BFRQ SR.

[0051] Specifically, if a beam failure occurs in the SCell, triggering the transmission of BFRQ information and the SR for BFRQ can be at least one of the following: if a beam failure occurs in the SCell, triggering the transmission of BFRQ information and / or the SR for BFRQ, and transmitting BFRQ information and / or the SR for BFRQ. For example: when the terminal detects a beam failure in the SCell, it triggers the transmission of BFRQ information and / or the SR for BFRQ, and transmits BFRQ information and / or the SR for BFRQ.

[0052] Alternatively, the detection of beam failure in a SCell can be achieved as follows: the terminal physical layer measures the beam failure detection reference signal (BFD RS) of the SCell and reports a BFI indication to the Media Access Control (MAC) layer based on the measurement result. The MAC layer then starts or restarts the beam failure detection timer (beamFailureDetectionTimer) corresponding to that SCell and increments the BFI counter (BFI_COUNTER) by 1. When BFI_COUNTER is greater than or equal to the maximum count value (BFI_COUNTER>=beamFailureInstanceMaxCount), a beam failure event is determined to have occurred in the SCell.

[0053] It should be noted that the embodiments disclosed herein do not limit how beam failure is detected (or determined). For example, a method similar to that defined in the protocol for primary cell (PCell) beam failure can be used, or a method newly introduced in subsequent protocol versions can be used.

[0054] The aforementioned SCell can be a SCell in the Master Cell Group (MCG) or the Secondary Cell Group (SCG).

[0055] The aforementioned BFRQ information may be relevant information used to request beam failure recovery. For example, the BFRQ information may include at least one of the following:

[0056] The index information of the SCell where the beam failure occurred and the information of the new beam.

[0057] The aforementioned new beam information can be information about a new beam selected by the terminal. For example, the terminal physical layer can measure the candidate beam reference signal (RS) of the SCell where beam failure occurs, and search for a new candidate beam (candidate beam) whose quality meets the preset requirements to obtain the aforementioned new beam.

[0058] It should be noted that in this embodiment of the disclosure, the beam can also be referred to as a spatial filter or a spatial domain transmission filter, etc. Beam information can also be represented by other terms, such as transmission configuration indication state (TCI state) information, quasi-colocation (QCL) information, spatial relation information, etc.

[0059] Additionally, the aforementioned BFRQ information can be transmitted within the Media Access Control Element (MAC CE), though this is not a limitation. Furthermore, BFRQ information can also be referred to as BFRQ or BFRQ report.

[0060] The aforementioned BFRQ SR can be an SR used to request network-side scheduling resources. Further, the aforementioned BFRQ SR can be an SR defined in the protocol for requesting network-side scheduling of uplink resources for transmitting data, or an SR defined in the protocol for BFRQ, such as a BFRQ SR for PCell. Alternatively, the aforementioned SR can be a dedicated SR, and the SR is transmitted on a dedicated Physical Uplink Control Channel (PUCCH) resource configured by the network specifically for BFR (dedicated SR-like PUCCH resource). Furthermore, the aforementioned BFRQ SR can be transmitted on PCell, Primary Secondary Cell (PSCell), or SCell.

[0061] It should be noted that the BFRQ information and the BFRQ SR mentioned above can be transmitted in different or the same cells, on different or the same resources, or at different or the same times.

[0062] It should be noted that in this embodiment of the disclosure, due to beam failure in the SCell, at least one of BFRQ information and a BFRQ SR is triggered. This supports BFR on the SCell because after sending at least one of the BFRQ information and the BFRQ SR, the terminal can complete the BFR process based on at least one of the BFRQ information and the BFRQ SR. It should also be noted that this embodiment of the disclosure does not limit the BFR process; the process can be one already defined in the protocol, such as the BFR process for the PCell, or a BFR process for the SCell newly defined in a subsequent protocol.

[0063] In this embodiment of the disclosure, if the first condition is met, then prohibiting the transmission of at least one of the following: subsequent BFRQ information and BFRQ SR. This can be either prohibiting the triggering of at least one of the following BFRQ and BFRQ SR, or prohibiting the transmission of at least one of the following BFRQ and BFRQ SR, when the first condition is met. Furthermore, the aforementioned subsequent BFRQ information and BFRQ SR can refer to the BFRQ information and BFRQ SR triggered in step 201.

[0064] Optionally, the first condition includes at least one of the following:

[0065] The BFRQ message is triggered, the BFRQ message is sent, the BFRQ message is successfully sent, and the first timer starts running.

[0066] It should be noted that triggering the BFRQ information mentioned above can mean that after triggering the BFRQ information in step 201, at least one of the following should be prohibited from being triggered: sending subsequent BFRQ information or BFRQ SR. In other words, in this case, it is not necessary to perform a judgment that the first condition is met; triggering the BFRQ information indicates that the first condition is met. Therefore, the above-mentioned prohibition of triggering at least one of the following should be triggered if the first condition is met can be: if the BFRQ information is triggered, then at least one of the following should be prohibited from being triggered: sending subsequent BFRQ information or BFRQ SR. For example, if a MAC CE for transmitting BFRQ is triggered, then at least one of the following should be prohibited from being triggered: sending subsequent BFRQ information or BFRQ SR.

[0067] Similarly, sending the BFRQ information described above can be achieved by prohibiting the transmission of at least one of the following: subsequent BFRQ information and BFRQ SR, after sending the BFRQ information in step 201. In other words, in this case, it is not necessary to perform a judgment that the first condition is met; sending the BFRQ information indicates that the first condition is satisfied. Therefore, prohibiting the transmission of at least one of the following: if the first condition is met, then the transmission of at least one of the following: if the BFRQ information is sent, then the transmission of at least one of the following: if the BFRQ information is sent, then the transmission of at least one of the following: if the BFRQ MAC CE is sent, then the transmission of at least one of the following: if the BFRQ is transmitted, then the transmission of at least one of the following: if the BFRQ CE is sent, then the transmission of at least one of the following: if the BFRQ MAC ...

[0068] The activation condition for the aforementioned first timer can be at least one of the following: triggering the BFRQ message, sending the BFRQ message, or successfully sending the BFRQ message. The duration of the first timer can be configured by the network, agreed upon by the protocol, or pre-configured by the terminal. This timer can be understood as a timer used for the aforementioned prohibition purpose.

[0069] Successful transmission of the aforementioned BFRQ information can be achieved by receiving a Hybrid Automatic Repeat request Acknowledgement (HARQ-ACK) message from the network for MAC CE for BFRQ.

[0070] Since the first condition is met, triggering the transmission of at least one of the following BFRQ information and BFRQ SR is prohibited. This ensures that during the SCell BFR process, when a beam failure occurs in the SCell, the terminal's MAC layer is prohibited from triggering the transmission of SR and / or BFRQ information for the beam-failed SCell. This avoids multiple triggerings of SCell SR and / or BFRQ information due to BFI_COUNTER's continuous counting, which could affect the currently ongoing SCell BFR process.

[0071] In addition, the stopping condition of the first timer can be at least one of the following: releasing the SCell, deactivating the SCell, switching the BandWidth Part (BWP), or successfully recovering from beam failure.

[0072] Specifically, releasing the SCell can mean releasing the resources in the SCell, deactivating the SCell can mean performing a deactivation operation on the SCell, and switching the BWP can mean switching the BWP in the SCell.

[0073] Furthermore, after the first timer stops, the prohibition on triggering the transmission of at least one of the following BFRQ information and BFRQ SR can be lifted. This allows the terminal to perform beam failure detection on the SCell again by promptly lifting the prohibition on triggering the transmission of at least one of the following BFRQ information and BFRQ SR. When beam failure occurs again, at least one of the following BFRQ information and BFRQ SR can be sent in a timely manner to perform timely and rapid beam failure recovery.

[0074] It should be noted that, in the embodiments of this disclosure, successful beam failure recovery may include at least one of the following:

[0075] PDCCH beam switching;

[0076] Beam switching of BFD RS;

[0077] Physical downlink shared channel (PDSCH) beam switching;

[0078] Receive the first downlink control information (DCI) from the network side;

[0079] Received the first Radio Resource Control (RRC) signaling from the network side;

[0080] The first MAC CE command was received from the network side.

[0081] Beam switching can be understood as switching to a new beam for channel transmission, which means updating the channel's TCI state or QCL information.

[0082] The aforementioned PDCCH beam switching can be achieved when the terminal receives a MAC CE activation command for the TCI state of the PDCCH or receives higher-level parameters (TCI-StatesPDCCH-ToAddlist and / or TCI-StatesPDCCH-ToReleaseList) in the RRC signaling that configures the TCI state of the PDCCH.

[0083] The aforementioned PDSCH beam switching can be achieved when the terminal receives RRC configuration signaling for the PDSCH TCI state, or MAC CE activation command for the PDSCH TCI state, or DCI indication signaling for the PDSCH TCI state.

[0084] The aforementioned beam switching of the BFD RS can include at least one of beam switching of the BFD RS for detecting the PDCCH beam quality and beam switching of the BFD RS for detecting the PDSCH beam quality. Specifically, the beam switching of the BFD RS can be achieved when the terminal receives RRC configuration signaling for the TCI state or QCL information of the BFD RS, or a MAC CE activation command for the TCI state or QCL information of the BFD RS, or a DCI indication signaling for the TCI state or QCL information of the BFD RS.

[0085] In addition, the aforementioned first DCI may have at least one of the following characteristics:

[0086] Transmitted on control resources dedicated to beam failure recovery;

[0087] The first DCI is in the format of a cyclic redundancy check (CRC) scrambled by a radio network temporary identifier (RNTI) used for BFR.

[0088] The first DCI is used to indicate the beam information of the downlink channel or reference signal of the SCell where beam failure has occurred;

[0089] The first DCI is used to instruct beam measurement to be performed in the SCell where beam failure occurs;

[0090] The first DCI is used to transmit confirmation information for the BFRQ information.

[0091] The aforementioned first RRC signaling has at least one of the following characteristics:

[0092] The first RRC signaling includes the release signaling of the SCell that has experienced beam failure;

[0093] The first RRC signaling is used to configure the beam information of the downlink channel or reference signal of the SCell where beam failure has occurred.

[0094] The aforementioned first MAC CE command may have at least one of the following characteristics:

[0095] The first MAC CE command is used to activate the beam information of the downlink channel or reference signal of the SCell where beam failure has occurred;

[0096] The first MAC CE command includes the deactivation signaling of the SCell in which the beam failure occurred;

[0097] The first MAC CE command is used to transmit confirmation information for the BFRQ information.

[0098] It should be noted that, in this embodiment of the disclosure, when the above-mentioned beam switching (at least one of PDCCH beam switching, BFD RS beam switching and PDSCH beam switching) is performed, it can be determined that the beam failure recovery is successful. It can also be determined that the beam failure recovery is successful when at least one of the above-mentioned first DCI, first RRC signaling and first MAC CE command is received.

[0099] Optionally, in the case where, if the first condition is met, the transmission of at least one of the following is prohibited: subsequent BFRQ information and the BFRQ SR.

[0100] If the fourth condition is met, the prohibition on at least one of the following is lifted: triggering the transmission of subsequent BFRQ information and the BFRQ SR.

[0101] The fourth condition may include at least one of the following:

[0102] Release the SCell, deactivate the SCell, BWP switch, beam failure recovery successful.

[0103] In this embodiment, the prohibition of triggering the transmission of at least one of the BFRQ information and the BFRQ SR can be lifted in a timely manner, so that the terminal can perform the beam failure recovery process on the SCell again. That is, when the SCell experiences beam failure again, at least one of the BFRQ information and the BFRQ SR can be sent in a timely manner to perform recovery.

[0104] In this embodiment of the disclosure, the SR that allows triggering the transmission of BFRQ at least once can be limited by restricting the number of times the terminal triggers the transmission of SR, thereby avoiding the terminal from sending too many BFRQ SRs.

[0105] Optionally, allowing the sending of at least one BFRQ SR means that before the BFR is completed, the MAC layer allows the sending of at least one pending SR, and if the BFR is completed, the pending SR is cancelled.

[0106] The above-mentioned permission to trigger the sending of at least one pending SR can be that the MAC layer allows the sending of all or part of the pending SRs.

[0107] This implementation allows the terminal MAC layer to trigger the BFRQ SR transmission at least once based on BFI_COUNTER being greater than or equal to the maximum count value. Here, "at least once" can be network-configured, protocol-defined, or terminal-preconfigured. Because it allows triggering the transmission of at least one pending SR, and cancels the pending SR if the BFR is completed, this avoids the terminal sending too many pending SRs, thus preventing resource waste.

[0108] In this embodiment of the disclosure, limiting the triggering of BFRQ information to one time can be as follows: for a SCell that has experienced beam failure, the terminal is only allowed to trigger the transmission of BFRQ information once; or it can be as follows: during a BFR process of the SCell, only one triggering of BFRQ information is performed, thereby avoiding multiple triggering of BFRQ information due to the continuous counting of BFI_COUNTER, which would affect the currently ongoing SCell BFR process.

[0109] Optionally, the limitation to triggering the sending of BFRQ information once means that the BFRQ information is limited to being sent once before the BFR is completed.

[0110] For example, for a pending MAC CE for BFRQ, before the SCell BFR is completed and after the MAC CE for BFRQ is triggered, the terminal's MAC layer only allows one MAC CE for BFRQ to be sent to the SCell where beam failure has occurred.

[0111] In this implementation, by limiting the triggering of the BFRQ information to once, the multiple triggering of the BFRQ information caused by the continuous counting of BFI_COUNTER can be avoided, which would affect the currently ongoing SCell BFR process.

[0112] In this embodiment of the disclosure, if the second condition is met, the BFI counter will not count. This can be achieved by either not counting the BFI counter or disabling the BFI counter from counting. This can avoid multiple triggering of BFRQ information due to BFI_COUNTER continuously counting, which would affect the currently ongoing SCell BFR process.

[0113] Optionally, the second condition includes at least one of the following:

[0114] Release the SCell, deactivate the SCell, BWP switch, beam failure occurs in the SCell.

[0115] The release of the SCell, deactivation of the SCell, BWP switching, and beam failure occurring in the SCell can be found in the description of the above implementation method, and will not be repeated here.

[0116] In this embodiment of the disclosure, resetting the BFI counter if the third condition is met can be achieved by resetting the BFI counter if certain conditions are met, thereby reducing the resources that trigger beam failures by BFI_COUNTER, thus avoiding sending too much BFRQ information and BFRQ SR, which would affect the currently ongoing SCell BFR process. Furthermore, by resetting the BFI counter, beam failure detection and beam failure recovery can be performed on the SCell again.

[0117] Optionally, resetting the BFI counter if the third condition is met means: if the second condition is not met, but the third condition is met, then the BFI counter is reset; and / or

[0118] If the BFI counter does not count when the second condition is met, then the BFI counter is deactivated if the third condition is met.

[0119] The aforementioned "disabling the BFI counter from counting" can be either disabling the counter from counting or not disabling the BFI counter from counting, so that it will continue to count when the counter counting conditions are met subsequently.

[0120] Since the third condition is met, the BFI counter is deactivated, which allows for timely detection of any recurring beam failure and prompt transmission of BFRQ information for BFR.

[0121] In this embodiment of the disclosure, if a beam failure occurs in the SCell, at least one of BFRQ information and a BFRQ scheduling request (SR) is triggered. The terminal, for the SCell, possesses at least one of the following features: if a first condition is met, triggering the transmission of at least one subsequent BFRQ information and a BFRQ SR is prohibited; triggering the transmission of at least one BFRQ SR is allowed; triggering the transmission of BFRQ information is restricted to once; if a second condition is met, the BFI counter is not counted; if a third condition is met, the BFI counter is reset; the third condition includes at least one of the following: successful beam failure recovery, prohibition of triggering the transmission of at least one subsequent BFRQ information and a BFRQ SR, and lifting the prohibition of triggering the transmission of at least one subsequent BFRQ information and a BFRQ SR.

[0122] This allows BFR to be performed in SCell.

[0123] Please refer to Figure 3, which is a structural diagram of a terminal provided in an embodiment of this disclosure. As shown in Figure 3, the terminal 300 includes:

[0124] Trigger module 301 is used to trigger at least one of BFRQ information transmission and BFRQ scheduling request SR if beam failure occurs in SCell;

[0125] The terminal, for the SCell, possesses at least one of the following features:

[0126] If the first condition is met, then triggering the sending of at least one of the following: subsequent BFRQ information and BFRQ SR;

[0127] Allows triggering the sending of an SR for at least one BFRQ;

[0128] Limit the trigger to send a BFRQ message only once;

[0129] If the second condition is met, the BFI counter will not count;

[0130] If the third condition is met, the BFI counter is reset;

[0131] The third condition includes at least one of the following:

[0132] The beam failure recovery is successful, the triggering of at least one of the following BFRQ information and BFRQ SR is prohibited, and the prohibition of triggering the transmission of at least one of the following BFRQ information and BFRQ SR is lifted.

[0133] Optionally, the first condition includes at least one of the following:

[0134] The BFRQ message is triggered, the BFRQ message is sent, the BFRQ message is successfully sent, and the first timer starts running.

[0135] Optionally, the start condition for the first timer is at least one of triggering the BFRQ message, sending the BFRQ message, and successfully sending the BFRQ message.

[0136] Optionally, the stopping condition of the first timer is at least one of the following: releasing the SCell, deactivating the SCell, switching the bandwidth portion BWP, or successfully recovering from beam failure.

[0137] Optionally, in the case where, if the first condition is met, triggering the transmission of at least one of the following is prohibited: BFRQ information and BFRQ SR.

[0138] If the fourth condition is met, the prohibition on at least one of the following is lifted: triggering the transmission of subsequent BFRQ information and the BFRQ SR.

[0139] Optionally, the fourth condition includes at least one of the following:

[0140] Release the SCell, deactivate the SCell, BWP switch, beam failure recovery successful.

[0141] Optionally, the second condition includes at least one of the following:

[0142] Release the SCell, deactivate the SCell, switch the bandwidth portion of the BWP, and a beam failure occurs in the SCell.

[0143] Optionally, resetting the BFI counter means: if the third condition is met but the second condition is not met, then resetting the BFI counter; and / or

[0144] If the BFI counter does not count when the second condition is met, then the BFI counter is deactivated if the third condition is met.

[0145] Optionally, successful beam failure recovery includes at least one of the following:

[0146] Physical downlink control channel (PDCCH) beam switching;

[0147] Beam switching of the beam failure detection reference signal (BFD RS);

[0148] Physical Downlink Shared Channel (PDSCH) beam switching;

[0149] Receives the first downlink control information (DCI) from the network side;

[0150] Received the first Radio Resource Control (RRC) signaling from the network side;

[0151] Received the first media access control unit (MAC CE) command from the network side.

[0152] Optionally, the first DCI has at least one of the following features:

[0153] Transmitted on control resources dedicated to beam failure recovery;

[0154] The first DCI is in the format of a cyclic redundancy check (CRC) scrambled by a radio network temporary identifier (RNTI) used for BFR.

[0155] The first DCI is used to indicate the beam information of the downlink channel or reference signal of the SCell where beam failure has occurred;

[0156] The first DCI is used to instruct beam measurement to be performed in the SCell where beam failure occurs;

[0157] The first DCI is used to transmit confirmation information for the BFRQ information;

[0158] and / or

[0159] The first RRC signaling has at least one of the following characteristics:

[0160] The first RRC signaling includes the release signaling of the SCell that has experienced beam failure;

[0161] The first RRC signaling is used to configure the beam information of the downlink channel or reference signal of the SCell where beam failure has occurred;

[0162] and / or

[0163] The first MAC CE command has at least one of the following characteristics:

[0164] The first MAC CE command is used to activate the beam information of the downlink channel or reference signal of the SCell where beam failure has occurred;

[0165] The first MAC CE command includes the deactivation signaling of the SCell in which the beam failure occurred;

[0166] The first MAC CE command is used to transmit confirmation information for the BFRQ information.

[0167] Optionally, the SR is a dedicated SR, and the SR is transmitted on the physical uplink control channel (PUCCH) resources configured in the network for BFR.

[0168] Optionally, the BFRQ information includes at least one of the following:

[0169] The index information of the SCell where the beam failure occurred and the information of the new beam.

[0170] Optionally, the SR that allows triggering at least one BFRQ transmission means that before completing the beam failure recovery (BFR), the MAC layer allows triggering at least one waiting SR, and if the BFR is completed, the waiting SR is canceled.

[0171] Optionally, the limitation to triggering the sending of BFRQ information once means that the BFRQ information is limited to being sent once before the BFR is completed.

[0172] The terminal provided in this embodiment can implement the various processes implemented by the terminal in the method embodiment of FIG2. To avoid repetition, they will not be described again here, and it can support BFR in SCell.

[0173] Figure 4 is a schematic diagram of the hardware structure of a terminal implementing various embodiments of the present disclosure.

[0174] The terminal 400 includes, but is not limited to, components such as: a radio frequency unit 401, a network module 402, an audio output unit 403, an input unit 404, a sensor 405, a display unit 406, a user input unit 407, an interface unit 408, a memory 409, a processor 410, and a power supply 411. Those skilled in the art will understand that the terminal structure shown in FIG4 does not constitute a limitation on the terminal; the terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements. In the embodiments of this disclosure, the terminal includes, but is not limited to, mobile phones, tablet computers, laptop computers, PDAs, vehicle terminals, robots, wearable devices, and pedometers.

[0175] Radio frequency unit 401 is used to trigger at least one of BFRQ information and BFRQ scheduling request SR if beam failure occurs in SCell;

[0176] The terminal, for the SCell, possesses at least one of the following features:

[0177] If the first condition is met, then triggering the sending of at least one of the following: subsequent BFRQ information and BFRQ SR;

[0178] Allows triggering the sending of an SR for at least one BFRQ;

[0179] Limit the trigger to send a BFRQ message only once;

[0180] If the second condition is met, the BFI counter will not count;

[0181] If the third condition is met, the BFI counter is reset;

[0182] The third condition includes at least one of the following:

[0183] The beam failure recovery is successful, the triggering of at least one of the following BFRQ information and BFRQ SR is prohibited, and the prohibition of triggering the transmission of at least one of the following BFRQ information and BFRQ SR is lifted.

[0184] Optionally, the first condition includes at least one of the following:

[0185] The BFRQ message is triggered, the BFRQ message is sent, the BFRQ message is successfully sent, and the first timer starts running.

[0186] Optionally, the start condition for the first timer is at least one of triggering the BFRQ message, sending the BFRQ message, and successfully sending the BFRQ message.

[0187] Optionally, the stopping condition of the first timer is at least one of the following: releasing the SCell, deactivating the SCell, switching the bandwidth portion BWP, or successfully recovering from beam failure.

[0188] Optionally, in the case where, if the first condition is met, triggering the transmission of at least one of the following is prohibited: BFRQ information and BFRQ SR.

[0189] If the fourth condition is met, the prohibition on at least one of the following is lifted: triggering the transmission of subsequent BFRQ information and the BFRQ SR.

[0190] Optionally, the fourth condition includes at least one of the following:

[0191] Release the SCell, deactivate the SCell, BWP switch, beam failure recovery successful.

[0192] Optionally, the second condition includes at least one of the following:

[0193] Release the SCell, deactivate the SCell, switch the bandwidth portion of the BWP, and a beam failure occurs in the SCell.

[0194] Optionally, resetting the BFI counter means: if the third condition is met but the second condition is not met, then resetting the BFI counter; and / or

[0195] If the BFI counter does not count when the second condition is met, then if the third condition is met, the BFI counter is deactivated from counting.

[0196] Optionally, successful beam failure recovery includes at least one of the following:

[0197] Physical downlink control channel (PDCCH) beam switching;

[0198] Beam switching of the beam failure detection reference signal (BFD RS);

[0199] Physical Downlink Shared Channel (PDSCH) beam switching;

[0200] Receives the first downlink control information (DCI) from the network side;

[0201] Received the first Radio Resource Control (RRC) signaling from the network side;

[0202] Received the first media access control unit (MAC CE) command from the network side.

[0203] Optionally, the first DCI has at least one of the following features:

[0204] Transmitted on control resources dedicated to beam failure recovery;

[0205] The first DCI is in the format of a cyclic redundancy check (CRC) scrambled by a radio network temporary identifier (RNTI) used for BFR.

[0206] The first DCI is used to indicate the beam information of the downlink channel or reference signal of the SCell where beam failure has occurred;

[0207] The first DCI is used to instruct beam measurement to be performed in the SCell where beam failure occurs;

[0208] The first DCI is used to transmit confirmation information for the BFRQ information;

[0209] and / or

[0210] The first RRC signaling has at least one of the following characteristics:

[0211] The first RRC signaling includes the release signaling of the SCell that has experienced beam failure;

[0212] The first RRC signaling is used to configure the beam information of the downlink channel or reference signal of the SCell where beam failure has occurred;

[0213] and / or

[0214] The first MAC CE command has at least one of the following characteristics:

[0215] The first MAC CE command is used to activate the beam information of the downlink channel or reference signal of the SCell where beam failure has occurred;

[0216] The first MAC CE command includes the deactivation signaling of the SCell in which the beam failure occurred;

[0217] The first MAC CE command is used to transmit confirmation information for the BFRQ information.

[0218] Optionally, the SR is a dedicated SR, and the SR is transmitted on the physical uplink control channel (PUCCH) resources configured in the network for BFR.

[0219] Optionally, the BFRQ information includes at least one of the following:

[0220] The index information of the SCell where the beam failure occurred and the information of the new beam.

[0221] Optionally, the SR that allows triggering at least one BFRQ transmission means that before completing the beam failure recovery (BFR), the MAC layer allows triggering at least one waiting SR, and if the BFR is completed, the waiting SR is canceled.

[0222] Optionally, the limitation to triggering the sending of BFRQ information once means that the BFRQ information is limited to being sent once before the BFR is completed.

[0223] The aforementioned terminals can support BFR in SCell.

[0224] It should be understood that in this embodiment of the disclosure, the radio frequency unit 401 can be used for receiving and transmitting signals during information transmission or calls. Specifically, it receives downlink data from the base station and processes it with the processor 410; additionally, it transmits uplink data to the base station. Typically, the radio frequency unit 401 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc. Furthermore, the radio frequency unit 401 can also communicate with networks and other devices through a wireless communication system.

[0225] The terminal provides users with wireless broadband internet access through network module 402, such as helping users send and receive emails, browse web pages, and access streaming media.

[0226] The audio output unit 403 can convert audio data received by the radio frequency unit 401 or the network module 402 or stored in the memory 409 into audio signals and output them as sound. Furthermore, the audio output unit 403 can also provide audio output related to specific functions performed by the terminal 400 (e.g., call signal reception sound, message reception sound, etc.). The audio output unit 403 includes a speaker, a buzzer, and a receiver, etc.

[0227] Input unit 404 is used to receive audio or video signals. Input unit 404 may include a graphics processing unit (GPU) 4041 and a microphone 4042. The GPU 4041 processes image data of still images or videos acquired by an image capture device (such as a camera) in video capture mode or image capture mode. The processed image frames can be displayed on display unit 406. The image frames processed by GPU 4041 can be stored in memory 409 (or other storage medium) or transmitted via radio frequency unit 401 or network module 402. Microphone 4042 can receive sound and process such sound into audio data. The processed audio data can be converted into a format that can be transmitted to a mobile communication base station via radio frequency unit 401 in telephone call mode.

[0228] Terminal 400 also includes at least one sensor 405, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor and a proximity sensor. The ambient light sensor can adjust the brightness of the display panel 4061 according to the ambient light level, and the proximity sensor can turn off the display panel 4061 and / or backlight when the terminal 400 is moved to the ear. As a type of motion sensor, an accelerometer sensor can detect the magnitude of acceleration in various directions (generally three axes). When stationary, it can detect the magnitude and direction of gravity and can be used to identify the terminal's posture (such as landscape / portrait switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc. Sensor 405 may also include fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., which will not be described in detail here.

[0229] The display unit 406 is used to display information input by the user or information provided to the user. The display unit 406 may include a display panel 4061, which may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.

[0230] User input unit 407 can be used to receive input numerical or character information, and generate key signal inputs related to user settings and function control of the terminal. Specifically, user input unit 407 includes a touch panel 4071 and other input devices 4072. Touch panel 4071, also known as a touch screen, can collect touch operations performed by the user on or near it (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near touch panel 4071). Touch panel 4071 may include two parts: a touch detection device and a touch controller. The touch detection device detects the user's touch position and the signal generated by the touch operation, and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into touch point coordinates, and sends it to the processor 410, which receives and executes commands from the processor 410. In addition, touch panel 4071 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. Besides touch panel 4071, user input unit 407 may also include other input devices 4072. Specifically, other input devices 4072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, joysticks, etc., which will not be described in detail here.

[0231] Furthermore, the touch panel 4071 can cover the display panel 4061. When the touch panel 4071 detects a touch operation on or near it, it transmits the information to the processor 410 to determine the type of touch event. Subsequently, the processor 410 provides corresponding visual output on the display panel 4061 according to the type of touch event. Although in Figure 4, the touch panel 4071 and the display panel 4061 are shown as two separate components to implement the input and output functions of the terminal, in some embodiments, the touch panel 4071 and the display panel 4061 can be integrated to implement the input and output functions of the terminal. Specific details are not limited here.

[0232] Interface unit 408 serves as an interface for connecting external devices to terminal 400. For example, external devices may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, an audio input / output (I / O) port, a video I / O port, a headphone port, and so on. Interface unit 408 can be used to receive input from external devices (e.g., data, power, etc.) and transmit the received input to one or more elements within terminal 400, or it can be used to transmit data between terminal 400 and external devices.

[0233] The memory 409 can be used to store software programs and various data. The memory 409 may primarily include a program storage area and a data storage area. The program storage area may store the operating system, applications required for at least one function (such as sound playback, image playback, etc.), etc.; the data storage area may store data created based on the use of the mobile phone (such as audio data, phonebook, etc.). Furthermore, the memory 409 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0234] The processor 410 is the control center of the terminal, connecting various parts of the terminal through various interfaces and lines. It executes software programs and / or modules stored in the memory 409, and calls data stored in the memory 409 to perform various functions and process data, thereby providing overall monitoring of the terminal. The processor 410 may include one or more processing units; optionally, the processor 410 may integrate an application processor and a modem processor. The application processor mainly handles the operating system, user interface, and applications, while the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 410.

[0235] Terminal 400 may also include a power supply 411 (such as a battery) that supplies power to various components. Optionally, the power supply 411 may be logically connected to the processor 410 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system.

[0236] In addition, terminal 400 includes some functional modules not shown, which will not be described in detail here.

[0237] Optionally, this disclosure also provides a terminal, including a processor 410, a memory 409, and a computer program stored in the memory 409 and executable on the processor 410. When the computer program is executed by the processor 410, it implements the various processes of the above-described beam failure handling method embodiments and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0238] This disclosure also provides a computer-readable storage medium storing a computer program. When executed by a processor, this computer program implements the beam failure handling method provided in this disclosure and achieves the same technical effect. To avoid repetition, it will not be described again here. The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0239] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0240] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this disclosure, in essence, or the part that contributes to the related technology, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this disclosure.

[0241] The embodiments of this disclosure have been described above with reference to the accompanying drawings. However, this disclosure is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this disclosure without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this disclosure.

Claims

1. A method for handling beam failure, applied to a terminal, comprising: If a beam failure occurs in the secondary cell SCell, at least one of the following is triggered: a beam failure recovery request (BFRQ) message and a BFRQ scheduling request (SR). The terminal, for the SCell, possesses at least one of the following features: If the first condition is met, then triggering the sending of at least one of the following: subsequent BFRQ information and BFRQ SR; Allows triggering the sending of an SR for at least one BFRQ; Limit the trigger to send a BFRQ message only once; If the second condition is met, the BFI counter for beam failure instances will not count; If the third condition is met, the BFI counter is reset; The third condition includes at least one of the following: The beam failure recovery is successful, the triggering of at least one of the following BFRQ information and BFRQ SR is prohibited, and the prohibition of triggering the transmission of at least one of the following BFRQ information and BFRQ SR is lifted.

2. The method as described in claim 1, wherein, The first condition includes at least one of the following: The BFRQ message is triggered, the BFRQ message is sent, the BFRQ message is successfully sent, and the first timer starts running.

3. The method as described in claim 2, wherein, The start condition for the first timer is at least one of the following: triggering the BFRQ message, sending the BFRQ message, and successfully sending the BFRQ message.

4. The method of claim 2, wherein, The stopping condition of the first timer is at least one of the following: releasing the SCell, deactivating the SCell, switching the bandwidth portion of the BWP, or successfully recovering from beam failure.

5. The method of claim 1, wherein, In the case where, if the first condition is met, at least one of the following is prohibited from being triggered: sending subsequent BFRQ information and the BFRQ SR. If the fourth condition is met, the prohibition on at least one of the following is lifted: triggering the transmission of subsequent BFRQ information and the BFRQ SR.

6. The method of claim 5, wherein, The fourth condition includes at least one of the following: Release the SCell, deactivate the SCell, BWP switch, beam failure recovery successful.

7. The method of claim 1, wherein, The second condition includes at least one of the following: Release the SCell, deactivate the SCell, switch the bandwidth portion of the BWP, and a beam failure occurs in the SCell.

8. The method of claim 7, wherein resetting the BFI counter if the third condition is met means: if the second condition is not met, and the third condition is met, then resetting the BFI counter; and / or If the BFI counter does not count when the second condition is met, then the BFI counter is deactivated if the third condition is met.

9. The method of claim 1, wherein, A successful beam failure recovery includes at least one of the following: Physical Downlink Control Channel (PDCCH) beam switching; Beam switching of the beam failure detection reference signal (BFD RS); Physical Downlink Shared Channel (PDSCH) beam switching; Receive the first downlink control information (DCI) from the network side; Received the first Radio Resource Control (RRC) signaling from the network side; Received the first media access control unit (MAC CE) command from the network side.

10. The method of claim 9, wherein, The first DCI has at least one of the following characteristics: Transmitted on control resources dedicated to beam failure recovery; The first DCI is in the format of a cyclic redundancy check (CRC) scrambled by a radio network temporary identifier (RNTI) used for BFR. The first DCI is used to indicate the beam information of the downlink channel or reference signal of the SCell where beam failure has occurred; The first DCI is used to instruct beam measurement to be performed in the SCell where beam failure occurs; The first DCI is used to transmit confirmation information for the BFRQ information; and / or The first RRC signaling has at least one of the following characteristics: The first RRC signaling includes the release signaling of the SCell that has experienced beam failure; The first RRC signaling is used to configure the beam information of the downlink channel or reference signal of the SCell where beam failure has occurred; and / or The first MAC CE command has at least one of the following characteristics: The first MAC CE command is used to activate the beam information of the downlink channel or reference signal of the SCell where beam failure has occurred; The first MAC CE command includes the deactivation signaling of the SCell in which the beam failure occurred; The first MAC CE command is used to transmit confirmation information for the BFRQ information.

11. The method of claim 1, wherein, The SR is a dedicated SR, and the SR is transmitted on the physical uplink control channel (PUCCH) resource configured in the network for BFR.

12. The method of claim 1, wherein, The BFRQ information includes at least one of the following: The index information of the SCell where the beam failure occurred and the information of the new beam.

13. The method of claim 1, wherein, The provision allowing the triggering of at least one BFRQ SR means that before completing the beam failure recovery (BFR), the Media Access Control (MAC) layer allows the triggering of at least one waiting SR, and if the BFR is completed, the waiting SR is cancelled.

14. The method of claim 1, wherein, The restriction to triggering the sending of a BFRQ message once means that the BFRQ message is restricted to being sent only once before the BFR is completed.

15. A terminal, comprising: The triggering module is used to trigger at least one of the following if a beam failure occurs in the SCell: sending BFRQ information and BFRQ scheduling request SR. The terminal, for the SCell, possesses at least one of the following features: If the first condition is met, then triggering the sending of at least one of the following: subsequent BFRQ information and BFRQ SR; Allows triggering the sending of an SR for at least one BFRQ; Limit the trigger to send a BFRQ message only once; If the second condition is met, the BFI counter will not count; If the third condition is met, the BFI counter is reset; The third condition includes at least one of the following: The beam failure recovery is successful, the triggering of at least one of the following BFRQ information and BFRQ SR is prohibited, and the prohibition of triggering the transmission of at least one of the following BFRQ information and BFRQ SR is lifted.

16. A terminal, comprising: A memory, a processor, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the beam failure handling method as described in any one of claims 1 to 14.

17. A computer-readable storage medium, wherein, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the beam failure handling method as described in any one of claims 1 to 14.