Beam Failure Recovery Method, Apparatus and Storage Medium

Abstract

An embodiment of the present application provides a beam failure recovery method, apparatus, and storage medium. The method includes: detecting a first beam failure event, where the first beam failure event is used to indicate that beam failure occurs in one or more BFD RS sets of a first cell set, and the first cell set includes one or more cells; determining a beam failure reporting method corresponding to the first beam failure event, and sending beam failure information representing the first beam failure event to a network-side device through the beam failure reporting method, thereby realizing beam failure event reporting based on the BFD RS set level and enhancing the performance of beam failure recovery.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and in particular, to a beam failure recovery method, apparatus, and storage medium. Background Art

[0002] In a New Radio (NR) system, when high frequency bands are used for transmission, physical channels and physical signals can adopt beamforming technology to improve the transmission quality of data. Through beamforming technology, a network-side device can concentrate the transmission power in a certain direction (for example, the direction where the terminal is located) to increase the power of the received signal. However, when the link between the network-side device and the terminal is blocked, the received power at the terminal side will be greatly reduced, thereby triggering a transmission (beam) failure event. In NR, a Beam Failure Recovery (BFR) mechanism, also called a link recovery mechanism, is defined. Specifically, after the terminal detects a transmission failure event, it reports it to the network-side device, and then the network-side device replaces the serving beam for the terminal to ensure normal transmission.

[0003] However, the current BFR mechanism only has cell-level BFR and there are no other optimization solutions. Summary of the Invention

[0004] Embodiments of this application provide a beam failure recovery method, apparatus, and storage medium to solve the defect that the current BFR mechanism only has cell-level BFR and further enhance the performance of beam failure recovery.

[0005] In a first aspect, embodiments of this application provide a beam failure recovery method, including:

[0006] Detecting a first beam failure event, where the first beam failure event is used to indicate that one or more beam failure detection reference signal sets (BFD RS sets) in a first cell set have beam failures, and the first cell set includes one or more cells;

[0007] Determining a beam failure reporting method corresponding to the first beam failure event;

[0008] Sending beam failure information representing the first beam failure event to a network-side device through the beam failure reporting method.

[0009] Optionally, in the beam failure recovery method according to an embodiment of this application, determining the beam failure reporting method corresponding to the first beam failure event includes any one of the following:

[0010] Report on one or more identified random access RACH resources associated with a new candidate beam indication reference signal NBI RS; or

[0011] Perform contention-based random access CBRA reporting using one or more identified NBI RSs; or

[0012] Report via a physical uplink shared channel PUSCH or CBRA; or

[0013] Perform CBRA reporting on the RACH resources for BFR; or

[0014] Report via the RACH resources associated with the first beam failure event; or

[0015] Report via the RACH resources associated with the NBI RS, and send beam failure recovery BFR medium access control - control element MAC-CE signaling on the resources associated with the RACH resources.

[0016] Optionally, according to a beam failure recovery method of an embodiment of the present application, the BFR MAC-CE signaling includes a first beam failure event, and the first beam failure event includes at least one of the following:

[0017] The number of BFD RS sets in which beam failure occurs in the PCell or PSCell;

[0018] The number of NBI RSs of the PCell or PSCell identified;

[0019] The number of BFD RS sets in which beam failure occurs in the SCell;

[0020] The number of NBI RSs of the SCell identified;

[0021] Whether an NBI RS associated with the first beam failure event is identified.

[0022] Optionally, according to a beam failure recovery method of an embodiment of the present application, the association relationship between the BFD RS set in which beam failure occurs and the RACH resources in the first beam failure event includes any one of the following:

[0023] One BFD RS set is associated with one NBI RS or a set of new candidate beam indication reference signals NBIRSset, and one NBI RS or one NBI RSset is associated with one RACH resource; or

[0024] Multiple BFD RS sets are associated with an NBI RS or an NBI RS set, and an NBI RS or an NBI RS set is associated with a RACH resource; or

[0025] One BFD RS set is associated with multiple NBI RSs or NBI RS sets. Some of the NBI RSs or NBI RS sets are associated with RACH resources, and some of the NBI RSs or NBI RS sets are not associated with RACH resources; or

[0026] Multiple BFD RS sets are associated with an NBI RS or an NBI RS set, and the NBI RS or the NBI RS set is not associated with a RACH resource; or

[0027] One BFD RS set is associated with an NBI RS or an NBI RS set, and the NBI RS or the NBI RS set is not associated with a RACH resource.

[0028] Optionally, according to the beam failure recovery method of an embodiment of the present application, the determining the beam failure reporting method corresponding to the first beam failure event includes:

[0029] If the terminal identifies the NBI RS corresponding to one of the multiple BFD RS sets that have a beam failure, the beam failure reporting method includes any one of the following:

[0030] Report on the RACH resource associated with the identified NBI RS; or

[0031] Report on the RACH resource associated with the identified NBI RS, and perform CBRA reporting for the BFD RS sets for which the NBI RS is not identified; or

[0032] Report through CBRA, and carry the BFR MAC-CE signaling in msgA PUSCH or msg3 PUSCH, where the BFR MAC-CE signaling includes the first beam failure event; or

[0033] Perform CBRA reporting using the identified NBI RS, and report the first beam failure event during the reporting process; or

[0034] Report the BFR MAC-CE signaling through PUSCH, where the BFR MAC-CE signaling includes the first beam failure event; or

[0035] When the identified NBI RS is associated with the first BFD RS set, report on the RACH resource associated with the identified NBI RS; or

[0036] When the identified NBI RS is associated with the second BFD RS set, report the BFR MAC-CE signaling through the PUSCH, where the BFR MAC-CE signaling includes the first beam failure event; or report through the RACH resource associated with the identified NBI RS, and send the BFR MAC-CE signaling on the resource associated with the RACH resource, where the BFR MAC-CE signaling includes the first beam failure event.

[0037] Optionally, for the beam failure recovery method according to an embodiment of the present application, determining the beam failure reporting method corresponding to the first beam failure event includes:

[0038] If the terminal identifies the NBI RS corresponding to multiple BFD RS sets with beam failures, the beam failure reporting method includes any one of the following:

[0039] Select one BFD RS set from multiple BFD RS sets with beam failures and report on the RACH resource corresponding to the selected BFD RS set; or

[0040] Report on the RACH resources corresponding to multiple BFD RS sets with beam failures; or

[0041] If multiple BFD RS sets with beam failures correspond to the same RACH resource, report on the same RACH resource; or

[0042] Report on one or more determined RACH resources, and report beam failure information in the BFR MAC-CE signaling carried on the PUSCH or in the BFR MAC-CE signaling carried in the RACH transmission message;

[0043] Report through the RACH resource associated with the first beam failure event; or

[0044] Report through the RACH resource associated with the NBI RS, and send the BFR MAC-CE signaling on the resource associated with the RACH resource.

[0045] Optionally, for the beam failure recovery method according to an embodiment of the present application, the first beam failure event includes multiple BFD RS sets with beam failures, and at least one BFD RS set among the multiple BFD RS sets with beam failures is associated with a RACH resource;

[0046] Determining the beam failure reporting method corresponding to the first beam failure event includes any of the following:

[0047] For a BFD RS set associated with RACH resources, and when the terminal identifies an NBI RS, report based on the CFRA method on the RACH resources associated with the identified NBI RS; for a BFD RS set without configured RACH resources, report using the CBRA method; or

[0048] Report on the RACH resources associated with the identified NBI RS, and send a BFR MAC-CE signaling on the resources associated with the RACH resources, where the BFR MAC-CE signaling includes the first beam failure event; or

[0049] Report using the CBRA or PUSCH method, and report the first beam failure event during the reporting process; or

[0050] Perform CBRA reporting using the identified NBI RS, and carry the first beam failure event in msg A PUSCH or msg 3 PUSCH; or

[0051] Report using the CBRA method on the RACH resources for BFR; or

[0052] Perform CBRA reporting on the RACH resources associated with the identified NBI RS, and carry the first beam failure event in msg A PUSCH or msg 3 PUSCH; or

[0053] Report through the RACH resources associated with the first beam failure event.

[0054] Optionally, according to the beam failure recovery method of an embodiment of the present application, the first beam failure event is configured with corresponding RACH resources; the first beam failure event includes two or more BFD RS sets having beam failures, or one BFD RS set having a beam failure, etc., and different beam failure events can be configured with different RACH resources; when the first beam failure event includes two or more BFD RS sets having beam failures, the corresponding RACH resources can be associated with at most two NBI RSs, that is, associated with the NBI RSs of at most two TRPs; when the first beam failure event includes one BFD RS set having a beam failure, the corresponding RACH resources can be associated with at most one NBI RS, that is, associated with the NBI RS of at most one TRP.

[0055] Determining the beam failure reporting method corresponding to the first beam failure event includes any of the following:

[0056] If the RACH resource is configured with an associated NBI RS and the terminal detects an associated NBI RS, report on the RACH resource; or

[0057] If the RACH resource is configured with multiple associated NBI RSs and the terminal detects at least one associated NBI RS, report on the RACH resource; or

[0058] If the terminal does not detect an associated NBI RS, report using the PUSCH method or the CBRA method;

[0059] Report through the RACH resource associated with the first beam failure event; or

[0060] Report through the RACH resource associated with the NBI RS, and send the BFRMAC-CE signaling on the resource associated with the RACH resource.

[0061] Optionally, for the beam failure recovery method according to an embodiment of the present application, under the condition that the configuration information or predefined rules of the network-side device include a first association relationship between different beam failure events and random access channel (RACH) resources,

[0062] Determining the beam failure reporting method corresponding to the first beam failure event includes:

[0063] Determine the first RACH resource associated with the first beam failure event according to the first association relationship;

[0064] Report on the first RACH resource.

[0065] Optionally, for the beam failure recovery method according to an embodiment of the present application, the configuration information or predefined rules of the network-side device further include a second association relationship between different beam failure events and random access (RA) opportunities and / or preamble indices;

[0066] The method further includes:

[0067] Determine the RA opportunity and / or preamble index associated with the first beam failure event according to the second association relationship.

[0068] Optionally, for the beam failure recovery method according to an embodiment of the present application, the first cell set includes a primary cell (PCell) and / or a primary and secondary cell (PSCell).

[0069] Optionally, for the beam failure recovery method according to an embodiment of the present application, one or more BFD RS sets of the first cell set include one or more BFD RS sets of the primary cell (PCell) or the primary and secondary cell (PSCell), and one or more BFD RS sets of the secondary cell (SCell);

[0070] Determining the beam failure reporting method corresponding to the first beam failure event includes any one of the following:

[0071] Performing CBRA reporting using a PRACH, and carrying the first beam failure event included in the BFR MAC-CE signaling during the reporting process, where the first beam failure event includes information on one or more BFD RS sets for the SCell; or

[0072] If at least one NBI RS corresponding to a BFD RS set in the PCell or PSCell is recognized, performing CBRA reporting on the RACH resource associated with the recognized NBI RS, and including the first beam failure event in msg A PUSCH or msg3 PUSCH; or

[0073] If at least one NBI RS corresponding to a BFD RS set in the PCell or PSCell is recognized, reporting on the RACH resource associated with the recognized NBI RS, and sending the BFR MAC-CE signaling on the resource associated with the RACH resource; or

[0074] If at least one NBI RS corresponding to a BFD RS set in the PCell or PSCell is recognized, performing CFRA reporting on the RACH resource associated with the recognized NBI RS, and including the first beam failure event in msg A PUSCH or msg3 PUSCH; or

[0075] If at least one NBI RS corresponding to a BFD RS set in the PCell or PSCell is recognized, then reporting on the RACH resource associated with the recognized NBI RS; or

[0076] Performing CFRA reporting, where the BFR MAC-CE signaling carried by the CFRA includes the first beam failure event; or

[0077] Reporting through PUSCH, and reporting the first beam failure event during the reporting process; or

[0078] Reporting through the RACH resource associated with the first beam failure event.

[0079] Second aspect, an embodiment of the present application provides a beam failure recovery method, including:

[0080] Receiving beam failure information for characterizing a first beam failure event, where the first beam failure event is used to indicate that one or more beam failure detection reference signal sets BFD RS set in a first cell set have beam failures, and the first cell set includes one or more cells;

[0081] Performing beam failure recovery according to the beam failure information.

[0082] Optionally, the beam failure recovery method according to an embodiment of the present application further includes: sending configuration information or predefined rules of a network side device to a terminal.

[0083] Optionally, in the configuration information or predefined rules of the network side device according to an embodiment of the present application, it includes:

[0084] One or more groups of random access channel RACH resources corresponding to the first cell, each group of RACH resources includes one or more RACH resources, and each RACH resource is associated with one or more new candidate beam indication reference signals NBI RS; and / or

[0085] A first association relationship between different beam failure events and random access channel RACH resources; and / or

[0086] A second association relationship between different beam failure events and random access RA opportunities and / or preamble indices.

[0087] Optionally, in the configuration information or predefined rules of the network side device according to an embodiment of the present application, it includes a search space set for BFR corresponding to the first cell set, and the search space set is used for the terminal to receive response information sent by the network side device.

[0088] Third aspect, an embodiment of the present application further provides a beam failure recovery device, including:

[0089] A detection unit, configured to detect a first beam failure event, where the first beam failure event is used to indicate that one or more beam failure detection reference signal sets BFD RS set in a first cell set have beam failures, and the first cell set includes one or more cells;

[0090] A determination unit, configured to determine a beam failure reporting method corresponding to the first beam failure event;

[0091] A sending unit, configured to send beam failure information for characterizing the first beam failure event to a network side device through the beam failure reporting method.

[0092] In a fourth aspect, an embodiment of the present application further provides a beam failure recovery apparatus, including:

[0093] a receiving unit, configured to receive beam failure information for characterizing a first beam failure event, where the first beam failure event is used to indicate that one or more beam failure detection reference signal sets BFD RS set in a first cell set have beam failures, and the first cell set includes one or more cells;

[0094] a beam failure recovery unit, configured to perform beam failure recovery according to the beam failure information.

[0095] In a fifth aspect, an embodiment of the present application further provides a beam failure recovery apparatus, including a memory, a transceiver, and a processor, where:

[0096] The memory is configured to store a computer program; the transceiver is configured to transmit and receive data under the control of the processor; the processor is configured to read the computer program in the memory and implement the steps of the beam failure recovery method described in the first aspect above.

[0097] In a sixth aspect, an embodiment of the present application further provides a beam failure recovery apparatus, including a memory, a transceiver, and a processor, where:

[0098] The memory is configured to store a computer program; the transceiver is configured to transmit and receive data under the control of the processor; the processor is configured to read the computer program in the memory and implement the steps of the beam failure recovery method described in the second aspect above.

[0099] In a seventh aspect, an embodiment of the present application further provides a processor-readable storage medium, where the processor-readable storage medium stores a computer program, and the computer program is used to cause the processor to execute the steps of the beam failure recovery method described in the first aspect above.

[0100] In an eighth aspect, an embodiment of the present application further provides a processor-readable storage medium, where the processor-readable storage medium stores a computer program, and the computer program is used to cause the processor to execute the steps of the beam failure recovery method described in the second aspect above.

[0101] The beam failure recovery method, apparatus, and storage medium provided by the embodiments of the present application can determine the beam failure reporting method corresponding to a first beam failure event when detecting the first beam failure event, where the first beam failure event is used to indicate that one or more BFD RS sets in a first cell set have beam failures, and the first cell set includes cells. The beam failure information representing the first beam failure event is sent to a network-side device through the beam failure reporting method, thereby realizing the reporting of beam failure events at the BFD RS set level and enhancing the performance of beam failure recovery. BRIEF DESCRIPTION OF THE DRAWINGS

[0102] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following briefly introduces the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0103] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following briefly introduces the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0104] Figure 1 It is a schematic flowchart of the beam failure recovery method provided by the embodiments of the present application;

[0105] Figure 2 It is a schematic flowchart of the beam failure recovery method provided by the embodiments of the present application;

[0106] Figure 3 It is a schematic structural diagram of the beam failure recovery apparatus provided by the embodiments of the present application;

[0107] Figure 4 It is a schematic structural diagram of the beam failure recovery apparatus provided by the embodiments of the present application;

[0108] Figure 5 It is a schematic structural diagram of a terminal device provided by the embodiments of the present application;

[0109] Figure 6 It is a schematic structural diagram of a network-side device provided by the embodiments of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0110] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the following will clearly and completely describe the technical solutions in the embodiments of this application with reference to the accompanying drawings in the embodiments of this application. Apparently, the described embodiments are some, but not all, of the embodiments of this application. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of this application without making creative efforts shall fall within the scope of protection of this application.

[0111] To facilitate a clear description of the technical solutions of the embodiments of this application, in the embodiments of this application, if terms such as "first" and "second" are used to distinguish identical or similar items with basically the same functions and effects, those skilled in the art can understand that terms such as "first" and "second" do not limit the quantity and execution order.

[0112] The term "and / or" in the embodiments of this application describes the association relationship of associated objects and indicates that three relationships may exist. For example, A and / or B may represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally represents an "or" relationship between the associated objects before and after.

[0113] The term "plurality" in the embodiments of this application means two or more, and other quantifiers are similar thereto.

[0114] The following will clearly and completely describe the technical solutions in the embodiments of this application with reference to the accompanying drawings in the embodiments of this application. Apparently, the described embodiments are only some, but not all, of the embodiments of this application. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of this application without making creative efforts shall fall within the scope of protection of this application.

[0115] In the NR system, when high-frequency bands are used for transmission, physical channels and physical signals can adopt beamforming technology to improve the transmission quality of data. Through beamforming technology, the network-side device can concentrate the transmission power in a certain direction (for example, the direction where the terminal is located) to increase the power of the received signal. However, when the link between the network-side device and the terminal is blocked, the received power on the terminal side will be greatly reduced, thus triggering a transmission (beam) failure event. In NR, a BFR mechanism, also called a link recovery mechanism, is defined. The specific method is that the terminal reports to the network-side device after detecting a transmission failure event, and then the network-side device replaces the serving beam for the terminal to ensure normal transmission.

[0116] Specifically, when a beam failure occurs in the primary cell (PCell) or the primary secondary cell group (PSCell), the beam failure event is reported using the Physical Random Access Channel (PRACH). The network device can configure dedicated Random Access Channel (RACH) resources for the terminal to quickly report beam failures. This RACH resource is associated with the New candidate Beam Indication Reference Signal (NBI RS) recognized by the terminal. When the terminal recognizes the NBI RS, it can select the corresponding RACH resource to send the corresponding preamble, also known as Contention Free Random Access (CFRA). After detecting the preamble, the network device can determine that the transmission of the PCell has failed, and the new candidate beam is the SSB or CSI-RS associated with the RACH resource where the preamble is detected. If dedicated RACH resources are not configured for the terminal, after a beam failure occurs in the PCell, the terminal can only initiate Contention Based Random Access (CBRA), using non-dedicated RACH resources to report beam failures. The steps are more cumbersome than CFRA, and the beam failure recovery time will also become longer.

[0117] When beam failure occurs in the SCell, the terminal reports the beam failure event using Medium Access Control (MAC) Control Element (MAC-CE) signaling. The MAC-CE signaling is carried in the Physical Uplink Shared Channel (PUSCH), and includes the cell index where the failure occurs, whether NBIRS is recognized. If NBIRS is recognized, it also includes NBIRS. The NBIRS reported in the MAC-CE signaling is also called qnew. If there is no available PUSCH to carry the MAC-CE signaling, and the network device configures a Scheduling Request (SR) for applying for PUSCH in beam failure recovery for the terminal (corresponding to the high-layer signaling schedulingRequestIDForBFR), the terminal can also first trigger the transmission of the SR to apply for the transmission resource of the MAC-CE signaling. The signal sent by the terminal on the SR resource is also called the Link Recovery Request (LRR).

[0118] In the above embodiments, when a cell includes multiple TRPs and the link quality between one of the TRPs and the terminal is poor, the terminal can use a method similar to the SCell beam failure recovery method to report the beam failure event, that is, use MAC-CE signaling to carry the beam failure event. When beam failure occurs in both TRPs of a cell, how to use MAC-CE signaling to indicate the information of the two TRPs is a problem. In addition, in Rel-15, when beam failure occurs in the PCell or PSCell, RACH resources are used for reporting. If beam failure occurs in both TRPs of the PCell or PSCell, which method to use for reporting and how to report are also unclear.

[0119] For example: If the failure events of two TRPs of the PCell or PSCell are reported using PRACH, and the terminal detects the NBI RS corresponding to the two TRPs, it is not clear which RACH resource the terminal should use for reporting; if the terminal only detects the NBI RS corresponding to one TRP, it is not clear how the network device determines whether a single-TRP beam failure or a two-TRP beam failure has occurred based on the detected preamble sequence; if only one of the two TRPs is configured with a dedicated RACH resource and the other TRP is not configured with a RACH resource, which RACH resource to use and in what form to report when both TRPs fail is also a problem; if a beam failure occurs in one or both TRPs of the PCell and PSCell, and a beam failure occurs in one or more TRPs of the SCell, how to report also needs to be further clarified.

[0120] In view of the above embodiments, the embodiments of the present application provide a beam failure recovery method, apparatus, and storage medium to implement a BFR mechanism when beam failures occur in multiple transmission points (TRPs), so that the terminal can quickly complete beam failure recovery reporting, and the network device can determine the occurred beam failure event based on the reporting of the terminal.

[0121] In the present application, a beam failure may also be a transmission failure, a link failure between a TRP and a terminal, etc. A failure may also be a malfunction, and various descriptions and their meanings can be mutually replaced in the following descriptions. A TRP is a physical transmission point and can be replaced with physical resources, such as the index of a beam failure detection reference signal set (BFD RS set), the index of a subset or group of a control resource set (CORESET), the CORESET-related high-layer parameter (CORESETPoolIndex), the BFR process index, the index of a new candidate beam indication reference signal set (NBI RS set), etc. The present application does not limit this.

[0122] The technical solutions provided by the embodiments of this application can be applied to a variety of systems, especially 5G systems. For example, the applicable systems can be Global System of Mobile Communication (GSM) systems, Code Division Multiple Access (CDMA) systems, Wideband Code Division Multiple Access (WCDMA) General Packet Radio Service (GPRS) systems, Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Long Term Evolution Advanced (LTE-A) systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) systems, 5G New Radio (NR) systems, etc. Both terminal devices and network devices are included in these various systems. The system may also include a core network part, such as an Evolved Packet System (EPS), a 5G System (5GS), etc.

[0123] The network device involved in the embodiments of this application can be a base station, which can include multiple cells that provide services to terminals. Depending on the specific application scenarios, the base station can also be referred to as an access point, or it can be a device in the access network that communicates with wireless terminal devices through one or more sectors over the air interface, or other names. The network device can be used to mutually replace the received air frames and Internet Protocol (IP) packets, and act as a router between the wireless terminal device and the rest of the access network, where the rest of the access network can include an Internet Protocol (IP) communication network. The network device can also coordinate the attribute management of the air interface. For example, the network device involved in the embodiments of this application can be a network device (Base Transceiver Station, BTS) in a Global System for Mobile communications (GSM) or Code Division Multiple Access (CDMA), or it can be a network device (NodeB) in a Wide-band Code Division Multiple Access (WCDMA), or it can also be an evolved network device (evolutional Node B, eNB or e-NodeB) in a Long Term Evolution (LTE) system, a 5G base station (gNB) in a 5G network architecture (next generation system), or it can be a Home evolved Node B (HeNB), a relay node, a femto, a pico, etc. The embodiments of this application do not limit this. In some network structures, the network device can include a centralized unit (centralized unit, CU) node and a distributed unit (distributed unit, DU) node, and the centralized unit and the distributed unit can also be geographically separated.

[0124] The terminal device involved in the embodiments of this application can be a device that provides voice and / or data connectivity to users, such as a handheld device with wireless connection capabilities, or other processing devices connected to a wireless modem, etc. In different systems, the name of the terminal device may also be different. For example, in a 5G system, the terminal device can be called a User Equipment (UE). The wireless terminal device can communicate with one or more core networks (CN) via a Radio Access Network (RAN). The wireless terminal device can be a mobile terminal device, such as a mobile phone (or a "cellular" phone) and a computer with a mobile terminal device. For example, it can be a portable, pocket-sized, handheld, computer-integrated, or vehicle-mounted mobile device that exchanges language and / or data with the wireless access network. For example, devices such as Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistant (PDA). The wireless terminal device can also be called a system, subscriber unit, subscriber station, mobile station, mobile, remote station, access point, remote terminal, access terminal, user terminal, user agent, user device, which is not limited in the embodiments of this application.

[0125] Figure 1 It is a schematic flowchart of the beam failure recovery method provided by the embodiments of this application. This beam failure recovery method can be used for a terminal device. As Figure 1 shown, this beam failure recovery method can include the following steps:

[0126] Step 101, detect a first beam failure event, where the first beam failure event is used to indicate that beam failure occurs in one or more BFD RS sets in the first cell set, and the first cell set includes one or more cells.

[0127] Specifically, the first cell set may include one cell or multiple cells. For example: The first cell set may include a PCell or a PSCell, may also include a PCell and an SCell, or may further include a PSCell and an SCell.

[0128] Each cell in the first cell set may include one or more BFD RS sets, and the BFD RS set where beam failure occurs may be one or more BFD RS sets in a certain cell in the first cell set.

[0129] Step 102: Determine the beam failure reporting method corresponding to the first beam failure event.

[0130] Specifically, since the BFD RS set where beam failure occurs is one or more BFD RS sets of the first cell set, and the first cell set may include one or more cells, multiple different beam failure events may occur. For different beam failure events, it is necessary to determine their corresponding beam failure reporting methods, so that the network-side device can distinguish different beam failure events based on the reports from the terminal. For example: In a possible implementation manner, the PCell includes a first BFD RS set and a second BFD RS set. The BFD RS set where beam failure occurs may be the first BFD RS set, may also be the second BFD RS set, or may be the first BFD RS set and the second BFD RS set. For the first BFD RS set and / or the second BFD RS set where beam failure occurs, it is necessary to determine the beam failure reporting method corresponding to the first BFD RS set and / or the second BFD RS set. It may also be a BFD RS set of the PSCell and a BFD RS set of the SCell. Different beam failure events correspond to different reporting methods or include different reporting contents.

[0131] When reporting, information related to the NBI RS(set) is usually carried. When determining the beam failure reporting method corresponding to the first beam failure event, the association relationship between the BFD RS set where beam failure occurs, the NBI RS or the NBI RS set, and the RACH resource may be determined first, and then the beam failure reporting method corresponding to the beam failure event may be determined.

[0132] Among them, the above association relationship may include:

[0133] One BFD RS set is associated with one NBI RS or one NBI RS set, and one NBI RS or one NBI RS set is associated with one RACH resource; or,

[0134] Multiple BFD RS sets are associated with an NBI RS or an NBI RS set, and an NBI RS or an NBI RS set is associated with a RACH resource; or,

[0135] One BFD RS set is associated with multiple NBI RSs or NBI RS sets, some of the NBI RSs or NBI RS sets are associated with RACH resources, and some of the NBI RSs or NBI RS sets are not associated with RACH resources; or

[0136] Multiple BFD RS sets are associated with an NBI RS or an NBI RS set, and the NBI RS or the NBI RS set is not associated with a RACH resource; or

[0137] One BFD RS set is associated with an NBI RS or an NBI RS set, and the NBI RS or the NBI RS set is not associated with a RACH resource.

[0138] Based on the above association relationships, the beam failure reporting methods may include:

[0139] Report on one or more identified random access RACH resources associated with the new candidate beam indication reference signal NBI RS; or

[0140] Perform contention-based random access CBRA reporting using one or more identified NBI RSs; or

[0141] Report through the physical uplink shared channel PUSCH or CBRA; or report based on CBRA on the RACH resource for BFR; or

[0142] Report through the RACH resource associated with the first beam failure event; or

[0143] Report through the RACH resource associated with the NBI RS, and send beam failure recovery BFR medium access control-control element MAC-CE signaling on the resource associated with the RACH resource. Wherein, the BFR MAC-CE signaling contains a first beam failure event, and the first beam failure event includes at least one of the following: the number of BFD RS sets where beam failure occurs in the PCell or PSCell; the number of NBI RSs of the PCell or PSCell identified; the number of BFD RS sets where beam failure occurs in the SCell; the number of NBI RSs of the SCell identified; whether an NBI RS associated with the first beam failure event is identified.

[0144] In addition, the above-mentioned reporting of contention-based random access (CBRA) using one or more identified NBI RSs means reporting on RACH resources not related to BFR. The RACH resources still carry information related to NBI RSs, and the TCI state related to NBI RSs is used for preamble transmission. Since the identified NBI RS is a beam with relatively high transmission quality in the current uplink and downlink transmission, the purpose of the reporting (preamble) being quickly received and detected by the network-side device can be achieved.

[0145] The resource associated with the RACH resource may be a PUSCH resource. This solution is an enhanced CFRA reporting method. The PUSCH resource associated with the RACH resource may be a msgA PUSCH, or a msg3 PUSCH, or other PUSCH resources not used for the RACH process, such as a PUSCH with a fixed offset (time-domain and / or frequency-domain offset) from the RACH resource, which is configured by the network device and used to carry BFR MAC CE signaling. It may also be a PUSCH resource allocated by the network-side device according to the terminal's report after the terminal sends a preamble on the RACH resource for BFR. This application does not limit this. Through this reporting method, not only can the beam failure be reported through dedicated RACH resources, but more failure information can also be carried through the PUSCH, enabling the network-side device to quickly recover from the beam failure.

[0146] Step 103: Send beam failure information for characterizing a first beam failure event to the network-side device through a beam failure reporting method.

[0147] As can be seen from the above embodiments, when a first beam failure event is detected, where the first beam failure event is used to indicate that one or more BFD RS sets in a first cell set have a beam failure, and the first cell set includes at least one cell, the beam failure reporting method corresponding to the first beam failure event can be determined, and beam failure information for characterizing the first beam failure event is sent to the network-side device through the beam failure reporting method, thereby realizing the reporting of beam failure events at the BFD RS set level and enhancing the performance of beam failure recovery.

[0148] In one embodiment, the terminal may use the transmission failure event of two or more BFD RS sets in the first cell set sent by PRACH and use PUSCH to send the transmission failure event of one BFD RS set.

[0149] Among them, when transmission fails for two BFD RS sets, both of the two BFD RS sets with beam failure are configured with RACH resources for BFR (i.e., dedicated RACH resources), but the terminal only recognizes the NBI RS corresponding to one of the two BFD RS sets with beam failure. Then, the determined beam failure reporting method may include any one of the following:

[0150] If the terminal recognizes the NBI RS corresponding to one of the BFD RS sets with beam failure, the beam failure reporting method includes any one of the following:

[0151] Report on the RACH resources associated with the recognized NBI RS; or

[0152] Report on the RACH resources associated with the recognized NBI RS, and perform CBRA reporting for the BFD RS set where the NBI RS is not recognized; or

[0153] Report through CBRA, and carry the BFR MAC-CE signaling in msgA PUSCH or msg3 PUSCH, where the BFR MAC-CE signaling includes the first beam failure event; or

[0154] Perform CBRA reporting using the recognized NBI RS, and report the first reported beam failure event during the reporting process (for example, carry BFR MAC CE in the report, and BFR MAC CE is included in msg3 PUSCH or msgA PUSCH); or

[0155] Report the BFR MAC-CE signaling through PUSCH, where the BFR MAC-CE signaling includes the first reported beam failure event; or

[0156] When the recognized NBI RS is associated with the first BFD RS set (for example, the first BFD RS set can be the BFD RS set with the smallest index), report on the RACH resources associated with the recognized NBI RS; or

[0157] When the recognized NBI RS is associated with the second BFD RS set, report the BFR MAC-CE signaling through PUSCH, where the BFR MAC-CE signaling includes the first beam failure event; or

[0158] Report the RACH resources associated with the recognized NBI RS, and send the BFR MAC-CE signaling on the resources associated with the RACH resources, where the BFR MAC-CE signaling includes a first beam failure event.

[0159] In all embodiments of this application, report the BFR MAC-CE signaling through PUSCH. The BFR MAC-CE signaling includes a first beam failure event, which can also be abbreviated as reporting the BFR MAC-CE signaling through PUSCH, or reporting or carrying the first beam failure event through PUSCH, or the BFR MAC-CE signaling carrying the first beam failure event.

[0160] Taking the PCell or PSCell as an example, the above embodiments are described as follows:

[0161] The terminal uses the PRACH to send the transmission failure events of two or more BFD RS sets of the PCell or PSCell, and uses the PUSCH to send the transmission failure event of one BFD RS set.

[0162] When two TRPs (BFD RS set) of the PCell or PSCell have transmission failures and the terminal only recognizes the NBI RS of one TRP, the terminal uses at least one of the following methods to report the transmission failure event:

[0163] The terminal reports the transmission failure event on the RACH resources associated with the recognized NBI RS (to ensure the recovery of at least one BFD RS set or TRP);

[0164] The terminal reports the BFR in the PUSCH (MAC CE) manner, that is, reverts to the single-TRP failure reporting manner;

[0165] If the NBI RS corresponds to the first BFD RS set (for example, it can correspond to the primary TRP), report it in the CFRA manner; if the NBI RS corresponds to the second BFD RS set, report the BFR in the SR+PUSCH manner;

[0166] Report it in the CBRA manner, and the BFR MAC CE carried in msg3 or msgA reports the specific failure situation.

[0167] In one embodiment, if the terminal recognizes the NBI RSs corresponding to multiple BFD RS sets with beam failures, the beam failure reporting method includes any one of the following:

[0168] Select a BFD RS set from multiple BFD RS sets with beam failure occurrences and report it on the RACH resources corresponding to the selected BFD RS set; or

[0169] Report on the RACH resources corresponding to all BFD RS sets with multiple beam failure occurrences; or

[0170] If the BFD RS sets with multiple beam failure occurrences correspond to the same RACH resource, report on the same RACH resource; or

[0171] Report on one or more determined RACH resources, and report beam failure information in the BFR MAC-CE signaling carried on the PUSCH or in the BFR MAC-CE signaling carried in the RACH transmission message;

[0172] Report through the RACH resources associated with the first beam failure event; or

[0173] Report through the RACH resources associated with the NBI RS, and send the BFR MAC-CE signaling on the resources associated with the RACH resources.

[0174] The above embodiments are specifically described below taking the PCell or PSCell as an example:

[0175] When transmission failures occur in 2 TRPs of the PCell or PSCell and the terminal also recognizes the NBI RS of the 2 TRPs, the terminal reports the transmission failure event by using at least one of the following methods:

[0176] The terminal selects the RACH resources corresponding to one TRP to report, and the network-side device only uses the NBI RS carried by the RACH resources for the transmission of one TRP

[0177] The terminal reports on the RACH resources corresponding to the 2 TRPs (equivalent to passing the 2 NBI RS to the gNB)

[0178] The network-side device configures part of the dedicated RACH resources or preamble index for the terminal and associates them with the NBI RS of the 2 TRPs, and associates part of the dedicated RACH resources or preamble index with the NBI RS of 1 TRP (in this method, even if the terminal selects the RACH resources or preamble index associated with the NBI RS of 1 TRP to report, the network-side device will consider that transmission failures have occurred in both 2 TRPs, but only recognizes one NBI RS)

[0179] In one embodiment, the first beam failure event includes multiple BFD RS sets with beam failures, and at least one BFD RS set among the multiple BFD RS sets with beam failures is associated with RACH resources;

[0180] Determining the beam failure reporting method corresponding to the first beam failure event includes any one of the following:

[0181] For a BFD RS set associated with RACH resources, and when the terminal recognizes an NBI RS, report based on the CFRA method on the RACH resources associated with the recognized NBI RS; for a BFD RS set without configured RACH resources, report using the CBRA method; or

[0182] Report on the RACH resources associated with the recognized NBI RS, and send a BFR MAC-CE signaling on the resources associated with the RACH resources, where the BFR MAC-CE signaling includes the first beam failure event; or

[0183] Report using the CBRA or PUSCH method, and report the first beam failure event during the reporting process;

[0184] Use the recognized NBI RS for CBRA reporting, and carry the first beam failure event in the message msg A PUSCH or msg 3 PUSCH; or

[0185] Report using the CBRA method on the RACH resources for BFR;

[0186] Perform CBRA reporting on the RACH resources associated with the recognized NBI RS, and carry the first beam failure event in the msg A PUSCH or msg 3 PUSCH.

[0187] Report through the RACH resources associated with the first beam failure event.

[0188] The association between the BFD RS set and the RACH resources is an association relationship established by the BFD RS set with the RACH resources through the NBI RS set or the RACH resource group, or a direct association between the BFD RS set and the RACH resources.

[0189] The above embodiments are specifically described below taking the PCell or PSCell as an example:

[0190] The terminal uses the PRACH to send the transmission failure event of one or more TRPs of the PCell or PSCell, and the terminal determines the RACH resources using at least one of the following methods:

[0191] Method 1: The network device configures some RACH resources to be associated with the transmission failure of one BFD RS set, and some RACH resources to be associated with the transmission failure of two or more BFD RS sets. When a transmission failure occurs in the PCell or PSCell, the terminal determines the RACH resources according to the number of BFD RS sets with transmission failures and the association relationship between the RACH resources configured by the network device and the BFD RS sets.

[0192] Method 2: The network device configures some preamble indexes to be associated with the transmission failure of one BFD RS set, and some preamble indexes to be associated with the transmission failure of two or more BFD RS sets. When a transmission failure occurs in the PCell or PSCell, the terminal determines the preamble indexes and / or RACH resources according to the number of BFD RS sets with transmission failures and the association relationship between the preamble indexes configured by the network device and the BFD RS sets.

[0193] For example, 2 preamble indexes are configured under an NBI RS, corresponding to the reports in two failure cases respectively.

[0194] The network device only configures dedicated RACH resources for one TRP (such as the primary TRP). When transmission failures occur in two TRPs of the PCell or PSCell, the terminal reports the transmission failure event by using at least one of the following methods:

[0195] The terminal reports separately for the two TRPs by using an independent process (the reporting process has no impact on standardization. Consider whether the subsequent behavior has an impact on standardization again).

[0196] The terminal sends on the dedicated RACH resources. After receiving the response from the gNB, it sends a BFR MAC-CE to further report information.

[0197] Carry detailed transmission failure information in the msg A PUSCH.

[0198] The terminal reports by using the CBRA method.

[0199] The terminal reports by using the CBRA method on the dedicated resources.

[0200] In addition, when the network-side device has configured dedicated RACH resources for only one TRP (e.g., BFD RS set 1), and the other TRP has not configured dedicated RACH resources or has configured the index of the associated NBI RS. When a transmission failure occurs in two TRPs of the PCell or PSCell, the terminal reports the transmission failure event by using at least one of the following methods:

[0201] The terminal reports for two BFD RS sets by using independent procedures.

[0202] If the terminal recognizes that there is a new beam detection value of the NBI RS in the NBI RS set associated with BFD RS set 1 that is greater than the threshold, the terminal sends a transmission failure report on the dedicated RACH resource corresponding to the recognized NBI RS. After the terminal receives the response information from the gNB, it further sends a BFR MAC-CE to report more transmission failure information.

[0203] Regardless of whether the terminal detects the NBI RS corresponding to the first BFD RS set, the terminal reports the transmission failure information of the two BFD RS sets by using the reporting method corresponding to the other BFD RS set. That is, it reports by using CBRA or PUSCH.

[0204] The terminal reports in the CBRA manner on the non-dedicated RACH resource by using the recognized NBI RS, and then reports the specific transmission failure information in the BFR MAC CE carried in msg3 or msgA; or

[0205] The terminal reports in the CBRA manner on the dedicated RACH resource, which is also to carry more information.

[0206] In one embodiment, a corresponding RACH resource is configured for the first beam failure event;

[0207] Determining the beam failure reporting method corresponding to the first beam failure event includes any one of the following:

[0208] If the RACH resource is configured with one associated NBI RS and the terminal recognizes one associated NBI RS, report on the RACH resource; or

[0209] If the RACH resource is configured with multiple associated NBI RSs and the terminal recognizes at least one associated NBI RS, report on the RACH resource; or

[0210] If the terminal does not recognize the associated NBI RS, report by using the PUSCH method or the CBRA method;

[0211] Reporting of RACH resources associated with the first beam failure event; or

[0212] Reporting of RACH resources associated with NBI RS, and sending BFRMAC-CE signaling on the resources associated with the RACH resources.

[0213] In one embodiment, under the condition that the configuration information or predefined rules of the network-side device include the conditions of the first association relationship between different beam failure events and random access channel (RACH) resources;

[0214] Determining the beam failure reporting method corresponding to the first beam failure event includes:

[0215] Determining the first RACH resources associated with the first beam failure event according to the first association relationship;

[0216] Reporting on the first RACH resources.

[0217] The above embodiments are specifically described below by taking the PCell or PSCell as an example:

[0218] When the network-side device configures dedicated RACH resources when transmission failures occur in both 2 TRPs (BFD RS set) of only the PCell or PSCell, the terminal uses at least one of the following methods to report the transmission failure event:

[0219] The network-side device configures an associated NBI RS for each RACH resource. When the terminal recognizes qnew, it uses the corresponding RACH resource to report the transmission failure event; after receiving the report from the terminal, the network-side device applies qnew to the transmission of the physical channel or physical signal associated with the BFDRS set 0, or applies qnew to the transmission of the physical channel or physical signal associated with the 2 BFD RS sets;

[0220] The network-side device configures 2 associated NBI RSs for each RACH resource. When the terminal recognizes that at least one NBI exceeds the threshold, it can report the transmission failure event on the corresponding RACH resource; after receiving the report from the terminal, the network-side device applies qnew to the transmission of the physical channel or physical signal associated with the 2 BFD RS sets;

[0221] If the terminal does not detect that any one of the NBI RSs associated with any RACH resource exceeds the threshold, the terminal can report the transmission failure using PUSCH.

[0222] In one embodiment, the configuration information or predefined rules of the network-side device further include a second association relationship between different beam failure events and random access (RA) opportunities and / or preamble indices; the method further includes: determining the RA opportunities and / or preamble indices associated with a first beam failure event according to the second association relationship.

[0223] The above embodiments are specifically described below by taking the PCell or PSCell as an example:

[0224] When the transmission failure events of one or more transmit receive points (TRPs) of the PCell or PSCell can all be reported in the physical random access channel (PRACH) manner, the terminal determines the RACH resources or RA timing or preamble index at the time of reporting through the following mechanism (with emphasis on the configuration of the network-side device):

[0225] The network-side device configures some RACH resources to be associated with the transmission failure of one BFD RS set, and some RACH resources to be associated with the transmission failure of two or more BFD RS sets. The terminal determines the RACH resources according to the number of BFD RS sets where the failure occurs, whether it recognizes the NBI RS associated with the RACH resources, and the association relationship between the RACH resources configured by the network-side device and the BFD RS set.

[0226] The network-side device configures some preamble indices or RA occasions to be associated with the transmission failure of one BFD RS set, and some preamble indices or RA occasions to be associated with the transmission failure of two or more BFD RS sets; alternatively, the network-side device configures the NBI RS of one RACH resource to be associated with two or more preamble indices or RA occasions, where one preamble index or RA occasion is associated with the transmission failure of one BFD RS set, and the other preamble index or RA occasion is associated with the transmission failure of two BFD RS sets. The terminal determines the preamble index and / or RA occasion and / or RACH resources according to the number of BFD RS sets where the failure occurs and the association relationship between the preamble index or RA occasion configured by the network-side device and the BFD RS set or NBI RS (set) or the RACH resource (group).

[0227] In one embodiment, one or more BFD RS sets of the first cell set include one or more BFD RS sets of the primary cell (PCell) or the primary-secondary cell (PSCell), and one or more BFD RS sets of the secondary cell (SCell);

[0228] Determining the beam failure reporting method corresponding to the first beam failure event includes any one of the following:

[0229] Reporting in the CBRA manner using a PRACH, and carrying the first beam failure event included in the BFR MAC-CE signaling during the reporting process, where the first beam failure event includes information for the SCell; or

[0230] If at least one BFD RS set corresponding NBI RS in the PCell or PSCell is recognized, reporting in the CBRA manner on the RACH resource associated with the recognized NBI RS, and including the first beam failure event in msg A PUSCH or msg3 PUSCH; or

[0231] If at least one BFD RS set corresponding NBI RS in the PCell or PSCell is recognized, reporting on the RACH resource associated with the recognized NBI RS, and sending the BFR MAC-CE signaling on the resource associated with the RACH resource; or

[0232] If at least one BFD RS set corresponding NBI RS in the PCell or PSCell is recognized, reporting in the CFRA manner on the RACH resource associated with the recognized NBI RS, and including the first beam failure event in msg A PUSCH or msg3 PUSCH; or

[0233] If at least one BFD RS set corresponding NBI RS in the PCell or PSCell is recognized, then reporting on the RACH resource associated with the recognized NBI RS; or

[0234] Reporting in the CFRA manner, where the BFR MAC-CE signaling carried by the CFRA includes the first beam failure event; or

[0235] Reporting through PUSCH, and reporting the first beam failure event during the reporting process; or

[0236] Reporting through the RACH resource associated with the first beam failure event.

[0237] Figure 2It is a schematic flowchart of the beam failure recovery method provided by an embodiment of the present application. This beam failure recovery method can be used in network-side devices. As Figure 2 shown, the beam failure recovery method may include the following steps:

[0238] Step 201, receive beam failure information for characterizing a first beam failure event. The first beam failure event is used to indicate that one or more BFD RS sets in a first cell set have beam failures. The first cell set includes one or more cells.

[0239] Step 202, perform beam failure recovery according to the beam failure information.

[0240] It can be seen from the above embodiments that when receiving beam failure information for characterizing a first beam failure event, where the first beam failure event is used to indicate that one or more BFD RS sets in a first cell set have beam failures and the first cell set includes one or more cells, beam failure recovery can be performed according to the beam failure information, thereby realizing the reporting of beam failure events at the BFD RS set level and enhancing the performance of beam failure recovery.

[0241] In one embodiment, it further includes: sending the configuration information or predefined rules of the network-side device to the terminal. The configuration information or predefined rules of the network-side device may include:

[0242] One or more groups of random access channel (RACH) resources corresponding to the first cell. Each group of RACH resources includes one or more RACH resources, and each RACH resource is associated with one or more new candidate beam indication reference signals (NBI RS); and / or

[0243] The first association relationship between different beam failure events and random access channel (RACH) resources; and / or

[0244] The second association relationship between different beam failure events and random access (RA) opportunities and / or preamble indices.

[0245] In addition, the configuration information or predefined rules of the network-side device may further include a search space set for BFR corresponding to the first cell set. The search space set is used for the terminal to receive response information sent by the network-side device.

[0246] The implementation process of the above beam failure recovery method will be illustrated by eight specific embodiments below.

[0247] Embodiment 1:

[0248] The network-side device configures one or more sets of dedicated RACH resources for the PCell or PSCell, where each set of RACH resources is associated with a transmission failure event. For example, N sets of dedicated RACH resources are configured, each set includes Mn RACH resources, and each RACH resource is associated with an NBI RS. The PCell and PSCell can also be collectively referred to as SpCell (Special Cell).

[0249] When N = 1, the RACH resources are used for BFR at the PCell or PSCell cell level or BFR for a certain TRP (BFD RS set) (i.e., BFR at the TRP level), specifically depending on other configurations of the network-side device. For example, the cell level is the first level, and the TRP level is the second level. For example, when the network-side device configures 1 BFD RS set for the PCell or PSCell, N = 1 set of RACH resources is used for beam failure recovery corresponding to the BFD RS set or BFR at the first level; when the network-side device configures 2 BFD RS sets for the PCell or PSCell, N = 1 set of RACH resources is used for beam failure recovery corresponding to the 2 BFD RS sets or BFR at the first level; when the network-side device explicitly configures the BFR level as the first level or the second level for the PCell or PSCell, the terminal determines that N = 1 set of RACH resources is used for BFR at the first level or the second level; in addition, it can also be determined according to a predefined method that N = 1 set of RACH resources is used for BFR at the first level or the second level or BFR corresponding to the first BFD RS set, or BFR corresponding to the second BFD RS set, or BFR corresponding to the 2 BFD RS sets. In addition, the network-side device can also configure in the RACH resource configuration that this set of RACH resources is used for one or more BFR levels or BFR corresponding to one or more BFD RS sets.

[0250] When N = 2, the N groups of RACH resources can respectively correspond to the BFR of the first BFD RS set and the BFR of the second BFD RS set of the PCell or PSCell, where the first BFD RS set is the BFD RS set with a lower index value in the BFD RS set of the corresponding cell, and the second BFD RS set is the BFD RS set with a higher index value in the BFD RS set of the corresponding cell; or respectively correspond to the first-level BFR and the second-level BFR; or respectively correspond to the BFR when one BFD RS set (the first BFD RS set or the second BFD RS set) of the PCell or PSCell fails to transmit and the BFR when two BFD RS sets fail to transmit. In addition, similar to when N = 1, the purpose can also be configured for the RACH resources, for example, for the various BFR levels mentioned above, one or two BFD RS sets, the first or second BFD RS set, etc. For example, this purpose can be configured within the RACH resource group or the NBI RS set (corresponding to the high-layer parameter candidateBeamRSSCellList-r16 or candidateBeamRSList, or other NBI RS set-related parameters).

[0251] When N = 3, the N groups of RACH resources can respectively correspond to the BFR of the first BFD RS set, the BFR of the second BFD RS set, and the BFR of two BFD RS sets of the PCell or PSCell. In this application, the BFR of one BFD RS set can also be replaced by the second-level BFR, and the BFR of two BFD RS sets can also be replaced by the first-level BFR. Similarly, the purpose can also be configured for each RACH resource group.

[0252] When the terminal detects that any one BFD RS set or two BFD RS sets have transmission failures, first determine the RACH resources or NBI RS set corresponding to the transmission failure event according to the configuration of the network-side device or predefined rules. For example, the terminal determines according to the predefined rules that the transmission failure events of two BFD RS sets respectively correspond to two NBI RS sets. The first NBI RS set is associated with the RACH resources, that is, the first BFD RS set uses the RACH resources to report when a transmission failure occurs; the second NBI RS set includes NBI RS, but there are no RACH resources, which means that the second BFD RS set uses PUSCH to report when a transmission failure occurs, and the BFR MAC CE is carried in the PUSCH.

[0253] Then the terminal measures the corresponding NBI RS. If there is an NBI RS greater than the threshold, a transmission failure recovery request signal (i.e., preamble) is sent on the RACH resource corresponding to the NBI RS greater than the threshold, or the index of the NBI RS is carried in the BFR MACCE. In addition, different RACH resources or NBI RS sets may correspond to different transmission failure events or different TRPs (it may also be one or more). Therefore, different new candidate beam thresholds can be configured for each NBI RS set or each RACH resource group, corresponding to the high-layer parameter (rsrp-ThresholdSSB) in the protocol.

[0254] In addition, the number of RACH resource groups and the number of NBI RS sets may be the same or different. For example, one NBI RS set (corresponding to the high-layer parameter candidateBeamRSList) may correspond to multiple RACH resource groups; or one RACH resource group may also correspond to multiple NBI RS sets; or, one NBI RS set corresponds to multiple RACH resources, and one RACH resource group also corresponds to multiple RACH resources, but the RACH resources included in the NBI RS set and the RACH resource group are different; the RACH resource group can also be an implicit group of RACH resources. For example, the RACH resources corresponding to a BFD RS set or a transmission failure form a RACH resource group.

[0255] The NBI RS set can be associated with the BFD RS set, and the RACH resource group can be associated with the transmission failure event. The transmission failure event includes not only the transmission failure of the first BFD RS set, the transmission failure of the second BFD RS set, the transmission failure of 2 BFD RS sets, but also the transmission failure of 2 or more BFD RS sets in different cells. This application does not limit this.

[0256] In addition, the index of the NBI RS can be directly included in the NBI RS set of the PCell or PSCell without being associated with the RACH resource.

[0257] When the terminal detects a transmission failure of a TRP (BFD RS set) in the PCell or PSCell, one approach is to report the beam failure using the PRACH method. For example, one NBI RS set corresponds to one RACH resource group, which includes multiple RACH resources, and each BFD RS set is associated with one NBI RS set. When a transmission failure occurs in a BFD RS set, the terminal measures the NBI RSs in the NBI RS set associated with the BFD RS set. If at least one NBI RS is measured to be greater than the configured detection threshold, the upper layer of the terminal will notify a selected NBI RS (i.e., qnew) greater than the configured detection threshold to the physical layer of the terminal. The physical layer of the terminal sends a preamble on the RACH resource associated with qnew. The network-side device determines qnew based on the RACH resource on which the preamble is transmitted, and determines which BFD RS set has a transmission failure based on the association relationship between the NBI RS set where qnew is located and the BFD RS set. Another approach is to report the BFR MAC CE using PUSCH. The BFR MAC CE signaling directly includes the index of the NBI RS (i.e., the higher-layer parameter SSB-Index or NZP-CSI-RS-ResourceId). In this case, the configuration of the NBI RS set does not include dedicated RACH resources.

[0258] In addition to the above two methods, the NBI RS set configuration can include both RACH resources and the index of the NBI RS. In this way, the terminal can report the transmission failure event in the form of PRACH and also report the transmission failure event in the form of PUSCH, which is more flexible. For example, when a transmission failure occurs in a TRP (BFD RS set), the terminal reports the transmission failure event using the PUSCH method, and the BFR MAC CE signaling carries qnew. When transmission failures occur in two TRPs (BFD RS sets), the terminal reports the transmission failure event using the PRACH method. That is, for the same TRP (BFD RS set), under different transmission failure conditions, the terminal can report the index of qnew and also report the transmission failure on the RACH resource associated with qnew. At this time, the signaling configuration of the NBI RS set can be:

[0259] candidateBeamRSSpCellList-r17 ::= SEQUENCE{

[0260] candidateBeamRSListSEQUENCE(SIZE(1..maxNrofCandidateBeams))OF PRACH-ResourceDedicatedBFR

[0261] candidateBeamRSSCellList-r16SEQUENCE

[0262] (SIZE(1..maxNrofCandidateBeams-r16))OF CandidateBeamRS-r16

[0263] }

[0264] In addition, if the terminal detects that the NBI RS corresponding to the RACH resource (i.e., the NBI RS included in PRACH-ResourceDedicatedBFR) is greater than the threshold, it can report a transmission failure using the RACH resource. If the terminal detects that the NBI RS associated with a non-RACH resource (i.e., the NBI RS included in the parameter candidateBeamRSSCellList-r16) is greater than the threshold, it can also report a transmission failure using PUSCH.

[0265] When one or two TRPs (BFD RS set) of the PCell or PSCell experience a transmission failure, the terminal reports the transmission failure event using at least one of the following methods:

[0266] Method 1-1: Report in the CFRA manner on the RACH resource associated with one or more identified NBI RS (qnew).

[0267] Method 1-2: Report in the CBRA manner on the RACH resource that is not (BFR) dedicated using one or more identified NBI RS.

[0268] Method 1-3: Even if dedicated RACH resources are configured, PUSCH or CBRA can be used to report to carry more transmission failure information (such as transmission failure events, identified NBI RS, etc.).

[0269] Method 1-4: Configure the RACH resource or RA opportunity or preamble index to be associated with different transmission failure events, such as being associated with the transmission failure of one BFD RS set, the transmission failure of two BFD RS sets, the transmission failure of the first BFD RS set, the transmission failure of the second BFD RS set, etc. After determining the transmission failure event, the terminal selects the corresponding RACH resource to report.

[0270] Methods 1 - 5: Report using an enhanced CFRA method. For example, send more transmission failure information in msgA PUSCH, or for traditional PRACH - based transmission failure reporting, after sending the preamble, send the BFR MAC CE signaling on the PUSCH transmission resource with a fixed offset (time - domain and / or frequency - domain offset) from the RACH resource. And more transmission failure information is carried in the BFR MAC CE signaling. This method is similar to msg A PUSCH, but the PUSCH resource here is not used for two - step RACH and is only used to carry the BFR MAC CE signaling. Here, msgA is Message A, that is, the information sent in the first step of the two - step RACH process. msg A PUSCH is associated with the RACH resource for sending the preamble, and the association relationship is known to both the network - side device and the terminal. In all embodiments of the present application, CFRA represents the process of sending the preamble on the RACH resource dedicated to transmission failure recovery. The RACH resource dedicated to transmission failure recovery is also the RACH resource for BFR, the RACH resource dedicated to BFR, and the resource configured by the high - layer parameter PRACH - ResourceDedicatedBFR.

[0271] Embodiment 2:

[0272] When transmission failures occur in 2 TRPs (i.e., BFD RS set) of the PCell or PSCell, if dedicated RACH resources are configured for both of the 2 BFD RS sets with transmission failures and the terminal recognizes 2 NBI RSs, the terminal can use one or more of the following methods to report the transmission failure event:

[0273] Method 2-1: The terminal selects and reports the RACH resources corresponding to a BFD RS set. For example, it selects and reports the RACH resources corresponding to the NBI RS in the NBI RS set associated with BFD RS set 0. If the transmission of a single BFD RS set of the PCell or PSCell fails and is reported using the PUSCH method, then after the network device detects the preamble on the RACH resources, it can determine that the transmissions of both BFD RS sets have failed, but can only determine the new candidate beams of one BFD RS set. Subsequently, the new candidate beams carried by the RACH resources will be applied to the transmission of the physical channels or physical signals associated with BFD RS set 0, that is, only the transmission of one TRP is restored to maintain the basic communication function. If the transmission of a single BFD RS set of the PCell or PSCell fails and is also reported using the PRACH method, then the RACH resources associated with BFD RS set 0 are selected for reporting. The network device cannot determine whether the transmissions of both BFD RS sets have failed or only one BFD RS set has failed based on the detected preamble, and other mechanisms need to be defined to distinguish these two events. For the specific mechanism, see Embodiment 6. In all embodiments of this application, the RACH resource (group), BFD RS set, and NBI RS set are all interrelated and are essentially associated with the TRP or the transmission failure event.

[0274] Method 2-2: The terminal can also report on the RACH resources corresponding to both BFD RS sets, that is, report separately on the RACH resources corresponding to the two detected qnews. In this way, even if the terminal only detects the preamble on one RACH resource, it can ensure that the transmission of one TRP can be restored.

[0275] Method 2-3: The network device configures one or more RACH resources for the terminal to be associated with two NBI RSs, or associated with two BFD RS sets, or associated with the first-level BFR. When the transmissions of two BFD RS sets fail, if the physical layer or the upper layer of the terminal detects that both NBI RSs associated with one RACH resource are greater than the configured threshold, it can report on such RACH resources. The number of RACH resources that meet the conditions may be many, and how to select one RACH resource specifically can depend on the implementation of the terminal. The network device side can determine that the transmissions of two BFD RS sets have failed based on the detected RACH resources.

[0276] Method 2-4: The network-side device configures one or more RACH resources for the terminal to be associated with two BFD RS sets, or to be associated with a first-level BFR, but only one NBI RS is associated. When a transmission failure occurs in the two BFD RS sets, if the physical layer or the upper layer of the terminal detects that the NBI RS set associated with the RACH resources associated with the two BFD RS sets is greater than the configured threshold, the terminal can report on such RACH resources. In addition, the NBI RS carried by the RACH resources needs to be at least greater than a new candidate beam detection threshold configured by the network device side (when a detection threshold is configured for each of the two TRPs). There may be many RACH resources that meet the conditions. How to select one RACH resource specifically may depend on the implementation of the terminal. The network device side can determine that a transmission failure has occurred in the two BFD RS sets based on the detected RACH resources. However, the network-side device cannot determine which TRP (or BFD RS set) the NBI RS carried by the RACH resource is for, and will apply this NBI RS (i.e., qnew) to the transmission of the physical channels or physical signals associated with the two BFD RS sets. The terminal knows which NBI RS set qnew is the new candidate beam for, so it only needs to use qnew in the transmission of the physical channels or physical signals corresponding to this NBI RS set. In addition, the network device side or the terminal also needs to trigger the reporting of detailed transmission failure information. For example, the terminal reports to the base station which BFD RS set this qnew is for, or the index of qnew associated with the other BFD RS set.

[0277] Method 2-5: Use an enhanced CFRA method for reporting. For example, the terminal uses one or more dedicated RACH resources for reporting, and carries the transmission failure event (a transmission failure occurs in one or two BFD RS sets) and / or the new candidate beam (if any, and one or two identified NBI RSs) through msgA PUSCH or msg3. Here, msg3 is Message 3, that is, the information sent in the third step of the four-step RACH procedure.

[0278] Embodiment 3:

[0279] When a transmission failure occurs in the two TRPs (BFD RS sets) of the PCell or PSCell, if dedicated RACH resources are configured for both of the two BFD RS sets, but the terminal only identifies one NBI RS, the terminal can use at least one of the following methods to report the transmission failure event:

[0280] Method 3-1: The terminal reports a transmission failure event on the RACH resource associated with the identified NBI RS, that is, reports the transmission failure event of the corresponding BFD RS set. Another TRP (BFD RS set) can temporarily stop using this TRP for transmission because no suitable new candidate beam is found. The network-side device can perform subsequent beam scanning or beam measurement to determine a suitable serving beam (TCI state) for another TRP.

[0281] Method 3-2: The terminal reports the transmission failure event of the corresponding BFD RS set on the RACH resource associated with the identified NBI RS, performs CBRA for another TRP (BFD RS set), and determines a new candidate beam for another TRP through this process.

[0282] Method 3-3: Report in the CBRA manner using the identified NBI RS on the non-dedicated RACH resource, and then report the specific transmission failure information in the BFR MAC CE carried in msg3 or msgA, including that transmission failures have occurred for both TRPs (BFD RS sets) and / or only one NBI RS is identified, and the index of the identified NBI RS can also be further reported.

[0283] Method 3-4: The terminal reports BFR in the PUSCH manner, that is, reverts to the single-TRP failure reporting manner, and carries the specific failure information in the BFR MACCE signaling, including that transmission failures have occurred for both TRPs (BFD RS sets) and / or only one NBI RS is identified, and the index of the identified NBI RS can also be further reported. If the dedicated RACH resource configured for the terminal by the network-side device carries the index of the NBI RS (higher-layer parameter SSB-Index or NZP-CSI-RS-ResourceId), or the NBI RS set configuration (such as the higher-layer parameter candidateBeamRSSCellList-r16) configures the index of the NBI RS, the index of the identified qnew can also be carried in the report.

[0284] Method 3-5: If the identified NBI RS corresponds to the first BFD RS set (for example, the primary TRP), report in the CFRA manner on the RACH resource associated with the NBI RS; if the identified NBI RS corresponds to the second BFD RS set, report BFR in the SR+PUSCH manner or the CBRA manner.

[0285] Method 3-6: Report using the enhanced CFRA method. For example, the terminal reports on the RACH resource corresponding to the identified NBI RS, and transmits the transmission failure event (transmission failure occurs for one or two BFD RSsets) and / or new candidate beams in msgA PUSCH or msg3, or no NBI RS is identified for a BFD RS set, etc.

[0286] Embodiment 4:

[0287] When the network side device configures dedicated RACH resources only for one TRP (such as BFD RS set 1) (e.g., configures dedicated RACH resources for the primary TRP), no dedicated RACH resources are configured for another TRP or the index of the associated NBI RS (the high-layer parameter candidateBeamRSSCellList-r16) is configured. When transmission failures occur for two TRPs of the PCell or PSCell, the terminal reports the transmission failure event using at least one of the following methods:

[0288] Method 4-1: The terminal reports for two BFD RSsets using independent processes. That is, if transmission failure occurs for the BFD RS set with dedicated RACH resources configured, and the terminal identifies the NBI RS, the CFRA method is used for reporting, that is, the transmission failure report is sent on the dedicated RACH resource. If transmission failure occurs for another BFD RS set, CBRA (no index or RACH resource of the associated NBI RS is configured) or PUSCH (if the high-layer parameter candidateBeamRSSCellList-r16 is configured) is used for reporting. If transmission failures occur for both BFD RSsets of the PCell or PSCell, the above two transmission failure reporting processes are triggered, that is, CFRA + CBRA (or PUSCH).

[0289] Method 4-2: If the terminal identifies that the new beam detection value of the NBI RS in the NBI RS set associated with BFD RS set 1 is greater than the threshold, the terminal sends a transmission failure report on the dedicated RACH resource corresponding to the identified NBI RS (that is, sends according to the configured preamble index). After the terminal receives the response information from the gNB, it further sends a BFR MAC-CE to report more transmission failure information, such as transmission failures occur for both TRPs, the NBI RS index of another BFD RS set, etc.

[0290] Method 4-3: Whether or not the terminal detects the NBI RS corresponding to the first BFD RS set, the terminal reports the transmission failure information of the two BFD RS sets using the reporting method corresponding to the other BFD RS set. That is, it uses CBRA (such as when the other BFD RS set does not configure the index of the associated NBI RS or RACH resource) or PUSCH (if the high-layer parameter candidateBeamRSSCellList-r16 is configured) for reporting.

[0291] Method 4-4: The terminal reports using the CBRA method with the identified NBI RS on the non-dedicated RACH resource, and then reports the specific transmission failure information in the BFR MAC CE carried in msg3 or msgA.

[0292] Method 4-5: The terminal reports using the CBRA method on the dedicated RACH resource, which is for carrying more information.

[0293] Embodiment 5:

[0294] When the network-side device configures dedicated RACH resources only when transmission failures occur in both of the two TRPs (BFD RS sets), configures one or more NBI RS sets (i.e., the parameter candidateBeamRSSCellList-r16) for a single TRP's transmission failure, and the transmission failure recovery of a single TRP is reported using PUSCH. At this time, each RACH resource may be associated with one or two NBI RSs.

[0295] Method 5-1: When transmission fails for two TRPs of a PCell or a PSCell, if each RACH resource is associated with one NBI RS, then this NBI RS may be associated with one TRP, that is, a new candidate beam for one TRP, or it may be a candidate beam applicable to both TRPs. In this case, it is necessary to consider which TRP or the physical channels or physical signals associated with the BFD RS set the new candidate beam will be applied to after beam failure recovery. If the terminal and the network-side device have inconsistent interpretations of the new candidate beam (i.e., qnew), it will lead to incorrect terminal behavior. For example, the network-side device applies qnew to the channel transmission related to TRP1, while the terminal believes that qnew is used for the transmission related to TRP2. Therefore, a new mechanism is needed to enable the network device side and the terminal to have a common understanding of qnew. At this time, the network-side device and the terminal can pre-agree that qnew is the TCI state or spatial relationship or power control parameter of the physical channels or physical signals associated with BFD RS set 0, or pre-agree that qnew is the TCI state or spatial relationship or power control parameter applicable to the physical channels or physical signals associated with both BFD RS sets;

[0296] Method 5-2: When transmission fails for two TRPs of a PCell or a PSCell, if each RACH resource is associated with two NBI RSs, and if the terminal identifies that the two associated NBI RSs of some RACH resources both exceed the threshold, and one of the associated NBI RSs of some RACH resources exceeds the threshold, the terminal can preferentially select the RACH resources with both associated NBI RSs exceeding the threshold for transmission and report a transmission failure event. After the network-side device identifies the preamble sent by the terminal, it can use both NBI RSs carried by the RACH resource for subsequent physical channel or physical signal transmission. The physical channels can be PDCCH, PDSCH, PUSCH, etc. The physical signals can be CSI-RS, SRS, etc., that is, they are respectively used for the physical channels or physical signals associated with the first BFD RS set and the second BFD RS set. If the terminal only identifies one of the two NBI RS sets associated with some RACH resources, it can also use the RACH resources with this characteristic to send a transmission failure report. The network-side device may always use the receiving beams corresponding to the two NBI RSs to receive the preamble respectively, that is, it may not be able to distinguish which NBI RS the terminal has identified. In this case, the network-side device will use both NBI RSs for subsequent physical channel or physical signal transmission. The terminal can further report further transmission failure information (such as updating qnew corresponding to one or two BFD RS sets, etc.) by carrying a BFR MAC CE on the PUSCH.

[0297] In all of the above cases, that is, when transmission failures occur for both of the two TRPs (BFD RS set) on the network side device, dedicated RACH resources are configured. Each RACH resource is associated with one or two NBI RSs. If the terminal does not detect any NBI RS associated with any RACH resource exceeding the threshold, the terminal can report the transmission failure using PUSCH.

[0298] In addition, the network side device can configure dedicated RACH resources for both of the two TRPs (BFD RS set) when transmission failures occur, and also configure dedicated RACH resources for a single TRP transmission failure. In this case, the reporting behavior of the terminal can refer to Embodiment 6.

[0299] Embodiment 6:

[0300] The terminal uses PRACH to send a transmission failure event of one or more TRPs of the PCell or PSCell, that is, the terminal uses PRACH to send a transmission failure event of one TRP (BFD RS set) of the PCell or PSCell, and also uses PRACH to send an event where transmission failures occur for both of the two TRPs (BFD RS set) of the PCell or PSCell. In this case, a mechanism also needs to be defined so that the network device determines the transmission failure event based on the report from the terminal, for example, determines whether a transmission failure has occurred for one TRP (BFD RS set) of the PCell or PSCell, or whether transmission failures have occurred for both of the two TRPs (BFD RS set).

[0301] First, the terminal can determine the reporting behavior when transmission failures occur for two BFD RS sets according to Method A and Method B of Embodiment 5. At this time, it can be distinguished from the case where transmission failures occur for one BFD RS set.

[0302] In particular, the terminal can also use at least one of the following methods to determine the RACH resources used for reporting (the determination of qnew, etc. refers to Embodiment 5):

[0303] The network-side device configures some RACH resources to be associated with the transmission failure of a BFD RS set (it can be the first BFD RS set or the second BFD RS set), and some RACH resources to be associated with the transmission failure of two or more BFD RS sets. When a transmission failure occurs in the PCell or PSCell, the terminal determines the RACH resources based on the number of BFD RS sets with transmission failures, whether it recognizes the NBI RS associated with the RACH resources (i.e., whether the NBI RS is higher than the detection threshold of the new candidate beam), and the association relationship between the RACH resources configured by the network-side device and the BFD RS set.

[0304] If transmission failures occur in both of the two BFD RS sets, the terminal detects the NBI RS (one or two) associated with the two BFD RS sets. If there is an NBI RS greater than the detection threshold, the terminal sends a preamble on the corresponding RACH resources. When the network-side device detects a preamble on the corresponding RACH resources, it can determine that transmission failures have occurred in both of the two TRPs (BFD RS sets) of the PCell or PSCell. If there is no NBI RS associated with the two BFD RS sets greater than the detection threshold, the terminal can also report using the reporting method when one BFD RS set has a transmission failure, or report using the method in Embodiment 3.

[0305] If a transmission failure occurs in one BFD RS set, such as BFD RS set 1, the terminal detects the NBI RS associated with BFD RS set 1. If there is an NBI RS greater than the detection threshold, the terminal sends a preamble (i.e., reports the transmission failure) on the corresponding RACH resources. If there is no NBI RS greater than the detection threshold, the terminal reports using CBRA or reports using PUSCH. When reporting using CBRA or PUSCH, the index of the NBI RS can be carried in the MAC CE signaling, for example, it is the SSB-Index or NZP-CSI-RS-ResourceId associated with the NBI RS set or the RACH resources.

[0306] The network side device configures some preamble indexes or RA occasions to be associated with the transmission failure of one BFD RS set, and some preamble indexes or RA occasions to be associated with the transmission failure of two or more BFD RS sets; alternatively, the network side device configures an NBI RS of a RACH resource for the terminal to be associated with two or more preamble indexes or RA occasions, where one preamble index or RA occasion is associated with the transmission failure of one BFD RS set, and another preamble index or RA occasion is associated with the transmission failure of two BFD RS sets. When a transmission failure occurs in the PCell or PSCell, the terminal determines the preamble index and / or RA occasion and / or RACH resource according to the number of BFD RS sets with transmission failures and the association relationship between the preamble index or RA occasion configured by the network side device and the BFD RS set or NBI RS (set) or with the RACH resource (group).

[0307] Embodiment 7:

[0308] If transmission failures occur in both the PCell or PSCell and the SCell, and the terminal recognizes the NBI RS of the PCell or PSCell, the terminal can initiate a transmission failure report for the PCell or PSCell and a transmission failure report for the SCell respectively. After introducing the BFR at the TRP level (i.e., the second-level BFR), the reporting and recovery granularity of the BFR is reduced from the cell level to the TRP level, that is, compared with the previous cell-level transmission failure recovery, the transmission failure reports initiated by the terminal will be more frequent. If a transmission failure occurs in at least one TRP (BFD RS set) of the PCell or PSCell and a transmission failure occurs in at least one TRP (BFD RS set) of the SCell, triggering multiple reporting processes will result in low efficiency.

[0309] If the terminal detects that a transmission failure occurs in at least one TRP of the PCell or PSCell and a transmission failure occurs in at least one TRP of the SCell, the terminal uses at least one of the following methods for reporting:

[0310] Method 7-1: Report using the CBRA method, and carry specific transmission failure information in the BFR MAC CE. For example, the transmission of at least one BFD RS set of the PCell or PSCell fails, and the transmission of at least one BFD RS set of the SCell fails.

[0311] Method 7-2: Use the PRACH method to perform CBRA reporting. If at least one NBI RS is detected, the RACH resource associated with the NBI RS can be selected for CBRA reporting, and the BFR MAC CE signaling is carried in msg3, and specific transmission failure information is carried in the BFR MAC CE.

[0312] Method 7-3: If at least one NBI RS corresponding to the BFD RS set of the PCell or PSCell is recognized, report using the RACH method, and carry more transmission failure information in msg A PUSCH; or after receiving the response from the network device, use PUSCH to carry more transmission failure information.

[0313] Embodiment 8:

[0314] If different BFD RS sets are all associated with dedicated RACH resources, two BFR-dedicated search space sets (Search Space set, SS set) can also be configured for the terminal to receive response information sent by the network device. For example, the indexes (recoverySearchSpaceId) of the two SS sets. Each SS set is associated with a TRP (BFD RS set). After the terminal sends a transmission failure report for one of the BFD RS sets, it will receive response information sent by the network device in the SS set associated with the BFD RS set. The response information can be any downlink control information format (Downlink Control Information format, DCI format) scrambled by the cyclic redundancy check (CRC) of the cell radio network temporary identifier (CellRadio Network Temporary Identifier, C-RNTI) or the modulation and coding scheme cell radio network temporary identifier (Modulation and Coding Scheme CellRadio Network Temporary Identifier, MCS-C-RNTI) for the DCI.

[0315] The terminal can also determine which BFD RSset has a transmission failure based on the SS set of the detected response information.

[0316] Figure 3 FIG. 4 is a schematic structural diagram of a beam failure recovery device provided by an embodiment of the present application; the beam failure recovery device can be used for a terminal. As Figure 3 shown, the beam failure recovery device may include:

[0317] A detection unit 31, configured to detect a first beam failure event, where the first beam failure event is used to indicate that one or more beam failure detection reference signal sets (BFD RS sets) in a first cell set have a beam failure, and the first cell set includes one or more cells;

[0318] A determination unit 32, configured to determine a beam failure reporting method corresponding to the first beam failure event;

[0319] A sending unit 33, configured to send beam failure information representing the first beam failure event to a network-side device through the beam failure reporting method.

[0320] Optionally, determining the beam failure reporting method corresponding to the first beam failure event includes any one of the following:

[0321] Reporting on one or more random access (RACH) resources associated with a new candidate beam indication reference signal (NBI RS) that is recognized; or

[0322] Performing contention-based random access (CBRA) reporting using one or more recognized NBI RSs; or

[0323] Reporting through a physical uplink shared channel (PUSCH) or CBRA; or reporting based on CBRA on a RACH resource for BFR; or

[0324] Reporting through a RACH resource associated with the first beam failure event; or

[0325] Reporting through a RACH resource associated with an NBI RS, and sending beam failure recovery (BFR) medium access control - control element (MAC-CE) signaling on a resource associated with the RACH resource.

[0326] Optionally, the BFR MAC-CE signaling includes a first beam failure event, and the first beam failure event includes at least one of the following:

[0327] The number of BFD RS sets for which beam failure occurs in a PCell or PSCel;

[0328] The number of NBI RSs of the PCell or PSCell recognized;

[0329] The number of BFD RS sets in which beam failure occurs in the SCell;

[0330] The number of NBI RSs of the SCell recognized;

[0331] Whether an NBI RS associated with the first beam failure event is recognized.

[0332] Optionally, the association relationship between the BFD RS set in which transmission beam failure occurs and the RACH resource in the first beam failure event includes any one of the following:

[0333] One BFD RS set is associated with one NBI RS or a new candidate beam indication reference signal set NBIRSset, and one NBI RS or NBIRSset is associated with one RACH resource; or

[0334] Multiple BFD RS sets are associated with one NBI RS or one NBI RSset, and one NBI RS or NBI RSset is associated with one RACH resource; or

[0335] One BFD RS set is associated with multiple NBI RSs or NBI RSsets, some NBI RSs or NBI RSsets are associated with RACH resources, and some NBI RSs or NBI RSsets are not associated with RACH resources; or

[0336] Multiple BFD RS sets are associated with one NBI RS or NBI RSset, and the NBI RS or NBI RSset is not associated with a RACH resource; or

[0337] One BFD RS set is associated with one NBI RS or one NBI RSset, and the NBI RS or the NBI RSset is not associated with a RACH resource.

[0338] Optionally, the determining the beam failure reporting method corresponding to the first beam failure event includes:

[0339] If the terminal recognizes an NBI RS corresponding to one BFD RS set in the BFD RS sets in which beam failure occurs, the beam failure reporting method includes any one of the following:

[0340] Report on the RACH resource associated with the recognized NBI RS; or

[0341] Report on the RACH resources associated with the identified NBI RS, and report in the CBRA manner for the BFD RSset where the NBI RS is not identified; or

[0342] Report through CBRA, carry the BFR MAC-CE signaling in msgA PUSCH or msg3 PUSCH, and the BFR MAC-CE signaling includes the first beam failure event; or

[0343] Report through CBRA using the identified NBI RS, and report the first reported beam failure event during the reporting process; or

[0344] Report the BFR MAC-CE signaling through PUSCH, and the BFR MAC-CE signaling includes the first reported beam failure event; or

[0345] When the identified NBI RS is associated with the first BFD RS set, report on the RACH resources associated with the identified NBI RS; or

[0346] When the identified NBI RS is associated with the second BFD RS set, report the BFR MAC-CE signaling through PUSCH, and the BFR MAC-CE signaling includes the first beam failure event; or

[0347] Report through the RACH resources associated with the identified NBI RS, and send the BFR MAC-CE signaling on the resources associated with the RACH resources, and the BFR MAC-CE signaling includes the first beam failure event.

[0348] Optionally, determining the beam failure reporting method corresponding to the first beam failure event includes:

[0349] If the terminal identifies the NBI RS corresponding to multiple BFD RS sets where beam failure occurs, the beam failure reporting method includes any one of the following:

[0350] Select one BFD RS set from multiple BFD RS sets where beam failure occurs and report on the RACH resources corresponding to the selected BFD RS set; or

[0351] Report on the RACH resources corresponding to multiple BFD RS sets where beam failure occurs; or

[0352] If multiple BFD RS sets where beam failure occurs correspond to the same RACH resource, report on the same RACH resource; or

[0353] Report on one or more determined RACH resources, and report beam failure information in the BFR MAC-CE signaling carried on the PUSCH or in the BFR MAC-CE signaling carried in the RACH transmission message;

[0354] Report through the RACH resources associated with the first beam failure event; or

[0355] Report through the RACH resources associated with the NBI RS, and send the BFR MAC-CE signaling on the resources associated with the RACH resources.

[0356] Optionally, the first beam failure event includes multiple BFD RS sets with beam failures, and at least one BFD RS set in the multiple BFD RS sets with beam failures is associated with RACH resources;

[0357] Determining the beam failure reporting method corresponding to the first beam failure event includes any of the following:

[0358] For the BFD RS set associated with RACH resources and when the terminal recognizes the NBI RS, report based on the CFRA method on the RACH resources associated with the recognized NBI RS; for the BFD RS set without configured RACH resources, report using the CBRA method; or

[0359] Report on the RACH resources associated with the recognized NBI RS, and send the BFR MAC-CE signaling on the resources associated with the RACH resources, where the BFR MAC-CE signaling includes the first beam failure event; or

[0360] Report using the CBRA or PUSCH method, and report the first beam failure event during the reporting process;

[0361] Perform CBRA reporting using the recognized NBI RS, and carry the first beam failure event in the message msg A PUSCH or msg 3 PUSCH; or

[0362] Report using the CBRA method on the RACH resources for BFR;

[0363] Perform CBRA reporting on the RACH resources associated with the recognized NBI RS, and carry the first beam failure event in the msg A PUSCH or msg 3 PUSCH; or

[0364] Report through the RACH resources associated with the first beam failure event; or

[0365] Optionally, the first beam failure event is configured with a corresponding RACH resource;

[0366] Determining the beam failure reporting method corresponding to the first beam failure event includes any one of the following:

[0367] If the RACH resource is configured with one associated NBI RS and the terminal identifies one associated NBI RS, report on the RACH resource; or

[0368] If the RACH resource is configured with multiple associated NBI RSs and the terminal identifies at least one associated NBI RS, report on the RACH resource; or

[0369] If the terminal does not identify an associated NBI RS, report using the PUSCH method or the CBRA method;

[0370] Report through the RACH resource associated with the first beam failure event; or

[0371] Report through the RACH resource associated with the NBI RS, and send the BFRMAC-CE signaling on the resource associated with the RACH resource.

[0372] Optionally, when the configuration information or predefined rules of the network-side device include the conditions of the first association relationship between different beam failure events and random access channel RACH resources;

[0373] Determining the beam failure reporting method corresponding to the first beam failure event includes:

[0374] Determine the first RACH resource associated with the first beam failure event according to the first association relationship;

[0375] Report on the first RACH resource.

[0376] Optionally, the configuration information or predefined rules of the network-side device further include a second association relationship between different beam failure events and random access RA opportunities and / or preamble indices;

[0377] The processor further performs the following operations:

[0378] Determine the RA opportunity and / or preamble index associated with the first beam failure event according to the second association relationship.

[0379] Optionally, the first cell set includes a primary cell (PCell) and / or a primary secondary cell (PSCell).

[0380] Optionally, one or more BFD RS sets of the first cell set include one or more BFD RS sets of a primary cell (PCell) or a primary-secondary cell (PSCell), and one or more BFD RS sets of a secondary cell (SCell);

[0381] Determining the beam failure reporting method corresponding to the first beam failure event includes any one of the following:

[0382] Reporting in the CBRA manner using a PRACH, and carrying, in the reporting process, the first beam failure event included in the BFR MAC-CE signaling, where the first beam failure event includes information for the SCell; or

[0383] If at least one BFD RS set corresponding NBI RS in the PCell or PSCell is recognized, reporting in the CBRA manner on the RACH resource associated with the recognized NBI RS, and including the first beam failure event in msg A PUSCH or msg3 PUSCH; or

[0384] If at least one BFD RS set corresponding NBI RS in the PCell or PSCell is recognized, reporting on the RACH resource associated with the recognized NBI RS, and sending BFR MAC-CE signaling on the resource associated with the RACH resource; or

[0385] If at least one BFD RS set corresponding NBI RS in the PCell or PSCell is recognized, reporting in the CFRA manner on the RACH resource associated with the recognized NBI RS, and including the first beam failure event in msg A PUSCH or msg3 PUSCH; or

[0386] If at least one BFD RS set corresponding NBI RS in the PCell or PSCell is recognized, then reporting on the RACH resource associated with the recognized NBI RS; or

[0387] Reporting in the CFRA manner, where the BFR MAC-CE signaling carried by the CFRA includes the first beam failure event; or

[0388] Reporting through a PUSCH, and reporting the first beam failure event in the reporting process; or

[0389] Reporting through the RACH resource associated with the first beam failure event.

[0390] It should be noted that the division of units in the embodiments of the present application is illustrative. It is only a logical function division, and there may be other division methods in actual implementation. In addition, in each embodiment of the present application, each functional unit may be integrated into a processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above integrated unit may be implemented in the form of hardware or in the form of a software functional unit.

[0391] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions to enable a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the methods in the embodiments of the present application. The aforementioned storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical discs that can store program codes.

[0392] It should be noted here that the above device provided in the embodiments of the present application can implement all the method steps implemented by the method embodiments on the terminal device side, and can achieve the same technical effects. The same parts and beneficial effects as those in the method embodiments will not be specifically described in this embodiment.

[0393] Figure 4 It is a schematic structural diagram of a beam failure recovery device provided by an embodiment of the present application; this beam failure recovery device can be used for a network-side device. As Figure 4 shown, this beam failure recovery device may include:

[0394] A receiving unit 41, configured to receive beam failure information for characterizing a first beam failure event, where the first beam failure event is used to indicate that one or more beam failure detection reference signal sets BFD RSset in a first cell set have beam failures, and the first cell set includes one or more cells;

[0395] A beam failure recovery unit 42, configured to perform beam failure recovery according to the beam failure information.

[0396] Further, based on the above device, it further includes:

[0397] A sending unit, configured to send configuration information or predefined rules of a network-side device to a terminal.

[0398] Further, based on the above-mentioned apparatus, the configuration information or predefined rules of the network-side device include:

[0399] One or more sets of random access channel (RACH) resources corresponding to the first cell, each set of RACH resources including one or more RACH resources, and each RACH resource being associated with one or more new candidate beam indication reference signals (NBI RS); and / or

[0400] A first association relationship between different beam failure events and random access channel (RACH) resources; and / or

[0401] A second association relationship between different beam failure events and random access (RA) opportunities and / or preamble indices.

[0402] Further, based on the above-mentioned apparatus, the configuration information or predefined rules of the network-side device include a search space set for beam failure recovery (BFR) corresponding to the first cell set, and the search space set is used for the terminal to receive response information sent by the network-side device.

[0403] It should be noted that the division of units in the embodiments of the present application is illustrative, and is only a logical function division. In actual implementation, there may be other division methods. In addition, in each embodiment of the present application, each functional unit may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of a software functional unit.

[0404] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a processor-readable storage medium. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, may be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the methods in the embodiments of the present application. The foregoing storage medium includes: various media such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disc that can store program codes.

[0405] It should be noted here that the above device provided by the embodiments of the present application can implement all the method steps implemented by the method embodiments on the network side device side, and can achieve the same technical effects. Therefore, the same parts and beneficial effects as those in the method embodiments will not be specifically described in this embodiment.

[0406] Figure 5 is a schematic structural diagram of a terminal device provided by an embodiment of the present application; the terminal device can be used to execute Figure 1 the beam failure recovery method shown in. As Figure 5 shown, the transceiver 500 is used to receive and send data under the control of the processor 510.

[0407] Among them, in Figure 5 the bus architecture may include any number of interconnected buses and bridges. Specifically, various circuits of one or more processors represented by the processor 510 and the memory represented by the memory 520 are linked together. The bus architecture can also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art. Therefore, they will not be further described herein. The bus interface provides an interface. The transceiver 500 may be multiple elements, that is, including a transmitter and a receiver, and provides a unit for communicating with various other devices on a transmission medium, and these transmission media include wireless channels, wired channels, optical cables, and other transmission media. For different user devices, the user interface 530 may also be an interface capable of externally connecting or internally connecting required devices, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, etc.

[0408] The processor 510 is responsible for managing the bus architecture and general processing, and the memory 520 can store the data used by the processor 500 when executing operations.

[0409] Optionally, the processor 510 may be a CPU (Central Processing Unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a CPLD (Complex Programmable Logic Device), and the processor may also adopt a multi-core architecture.

[0410] The processor is used to execute any method provided by the embodiments of the present application by calling the computer program stored in the memory according to the obtained executable instructions. The processor and the memory may also be physically separated.

[0411] It should be noted here that the above device provided by the embodiments of the present application can implement all the method steps implemented by the above method embodiments and can achieve the same technical effects. Therefore, the same parts and beneficial effects as those in the method embodiments will not be specifically described in this embodiment.

[0412] Figure 6 is a schematic structural diagram of a network-side device provided by an embodiment of the present application; the network-side device can be used to execute Figure 2 the beam failure recovery method shown. As Figure 6 shown, the transceiver 600 is used to receive and send data under the control of the processor 610.

[0413] Among them, in Figure 6 , the bus architecture may include any number of interconnected buses and bridges. Specifically, various circuits of one or more processors represented by the processor 610 and the memory represented by the memory 620 are linked together. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits together, which are well known in the art. Therefore, they will not be further described herein. The bus interface provides an interface. The transceiver 600 may be multiple elements, that is, including a transmitter and a receiver, and provides a unit for communicating with various other devices on a transmission medium, and these transmission mediums include wireless channels, wired channels, optical fiber cables, and other transmission mediums. The processor 610 is responsible for managing the bus architecture and general processing, and the memory 620 can store the data used by the processor 610 when executing operations.

[0414] The processor 610 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.

[0415] On the other hand, an embodiment of the present application also provides a processor-readable storage medium. The processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the above-mentioned execution Figure 1 the beam failure recovery method shown, including:

[0416] detecting a first beam failure event, where the first beam failure event is used to indicate that one or more beam failure detection reference signal sets BFD RS set in a first cell set have beam failures, and the first cell set includes at least one cell;

[0417] Determine the beam failure reporting method corresponding to the first beam failure event;

[0418] Send beam failure information for characterizing the first beam failure event to the network side device through the beam failure reporting method.

[0419] On the other hand, an embodiment of the present application also provides a processor-readable storage medium, and the processor-readable storage medium stores a computer program, and the computer program is used to cause the processor to execute the above execution Figure 2 The beam failure recovery method shown, including:

[0420] Receive beam failure information for characterizing a first beam failure event, where the first beam failure event is used to indicate that one or more beam failure detection reference signal sets BFD RS set in a first cell set have beam failures, and the first cell set includes at least one cell;

[0421] Perform beam failure recovery according to the beam failure information.

[0422] The processor-readable storage medium may be any available medium or data storage device accessible by the processor, including but not limited to magnetic memory (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical memory (such as CDs, DVDs, BDs, HVDs, etc.), and semiconductor memory (such as ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid state drives (SSD)), etc.

[0423] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memory and optical memory, etc.) containing computer-usable program code.

[0424] The present application is described with reference to the flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or block in the flowchart and / or block diagram, and the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing devices generate for implementing in the process Figure 1 One process or multiple processes and / or blocksFigure 1 means for the functions specified in one or more blocks.

[0425] These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the processor-readable memory produce a manufacture including an instruction means that implements the functions specified in one Figure 1 process or a plurality of processes and / or blocks Figure 1 or more blocks.

[0426] These processor-executable instructions may also be loaded onto a computer or other programmable data processing apparatus, such that a series of operational steps are performed on the computer or other programmable apparatus to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable apparatus provide steps for implementing the functions specified in one Figure 1 process or a plurality of processes and / or blocks Figure 1 or more blocks.

[0427] Obviously, those skilled in the art can make various changes and modifications to this application without departing from the spirit and scope of this application. Thus, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalent technologies, this application is also intended to cover these changes and modifications.

Claims

1. A beam failure recovery method, characterized in that, Including: Detecting a first beam failure event, where the first beam failure event is used to indicate that beam failure occurs in one or more beam failure detection reference signal sets (BFD RS sets) in a first cell set, and the first cell set includes one or more cells; the first cell set includes a primary cell (PCell) and / or a primary secondary cell (PSCell); Determining a beam failure reporting method corresponding to the first beam failure event based on the association relationship between the BFD RS set where beam failure occurs, a non-beamforming reference signal (NBI RS) or an NBI RS set, and a random access channel (RACH) resource; Sending, to a network-side device through the beam failure reporting method, beam failure information for characterizing the first beam failure event; determining the beam failure reporting method corresponding to the first beam failure event includes any one of the following: Reporting on one or more identified random access (RACH) resources associated with a new candidate beam indication reference signal (NBI RS); or Performing contention-based random access (CBRA) reporting using one or more identified NBI RSs; or Reporting through CBRA; or Performing CBRA reporting on a RACH resource for beam failure recovery (BFR); or Reporting through a RACH resource associated with the first beam failure event; or Reporting through a RACH resource associated with an NBI RS, and sending a beam failure recovery (BFR) medium access control - control element (MAC-CE) signaling on a resource associated with the RACH resource.

2. The beam failure recovery method according to claim 1, wherein The BFR MAC-CE signaling includes the first beam failure event, and the first beam failure event includes at least one of the following: The number of BFD RS sets where beam failure occurs in the PCell or PSCell; The number of NBI RSs of the PCell or PSCell identified; The number of BFD RS sets where beam failure occurs in a secondary cell (SCell); The number of NBI RSs of the SCell identified; Whether an NBI RS associated with the first beam failure event is identified.

3. The beam failure recovery method according to claim 1, wherein The association relationship between the BFD RS set where beam failure occurs and the RACH resource in the first beam failure event includes any one of the following: One BFD RS set is associated with one NBI RS or one new candidate beam indication reference signal set (NBI RS set), and one NBI RS or one NBI RS set is associated with one RACH resource; or Multiple BFD RS sets are associated with one NBI RS or one NBI RS set, and one NBI RS or one NBI RS set is associated with one RACH resource; or One BFD RS set is associated with multiple NBI RSs or NBI RS sets, and some NBI RSs or NBI RS sets are associated with RACH resources, while some NBI RSs or NBI RS sets are not associated with RACH resources; or Multiple BFD RS sets are associated with an NBI RS or an NBI RS set, and the NBI RS or the NBI RS set is not associated with RACH resources; or One BFD RS set is associated with an NBI RS or an NBI RS set, and the NBI RS or the NBI RS set is not associated with RACH resources.

4. The beam failure recovery method according to any one of claims 1 to 3, characterized in that, The determining the beam failure reporting method corresponding to the first beam failure event includes: If the terminal identifies an NBI RS corresponding to one of the BFD RS sets in which beam failure occurs, the beam failure reporting method includes any one of the following: Report on the RACH resources associated with the identified NBI RS; or Report on the RACH resources associated with the identified NBI RS, and perform CBRA reporting for the BFD RS sets for which the NBI RS is not identified; or Report through CBRA, and carry the BFR MAC-CE signaling in msgA PUSCH or msg3 PUSCH, where the BFR MAC-CE signaling includes the first beam failure event; or Perform CBRA reporting using the identified NBI RS, and report the first beam failure event during the reporting process; or Report the BFR MAC-CE signaling through PUSCH, where the BFR MAC-CE signaling includes the first beam failure event; or When the identified NBI RS is associated with the first BFD RS set, report on the RACH resources associated with the identified NBI RS; or When the identified NBI RS is associated with the second BFD RS set, report the BFR MAC-CE signaling through PUSCH, where the BFR MAC-CE signaling includes the first beam failure event; or report through the RACH resources associated with the identified NBI RS, and send the BFR MAC-CE signaling on the resources associated with the RACH resources, where the BFR MAC-CE signaling includes the first beam failure event.

5. The beam failure recovery method according to any one of claims 1 to 3, characterized in that, The determining the beam failure reporting method corresponding to the first beam failure event includes: If the terminal identifies NBIs RS corresponding to multiple BFD RS sets in which beam failure occurs, the beam failure reporting method includes any one of the following: Select one BFD RS set from the multiple BFD RS sets in which beam failure occurs, and report on the RACH resources corresponding to the selected BFD RS set; or Report on the RACH resources corresponding to the multiple BFD RS sets in which beam failure occurs; or If the multiple BFD RS sets in which beam failure occurs correspond to the same RACH resource, report on the same RACH resource; or Report on one or more determined RACH resources, and report beam failure information in the BFR MAC-CE signaling carried on the PUSCH or in the BFR MAC-CE signaling carried in the RACH transmission message; Report through the RACH resource associated with the first beam failure event; or Report through the RACH resource associated with the NBI RS, and send the BFR MAC-CE signaling on the resource associated with the RACH resource.

6. The beam failure recovery method according to claim 1, wherein The first beam failure event includes multiple BFD RS sets with beam failures, and at least one BFD RS set among the multiple BFD RS sets with beam failures is associated with a RACH resource; Determining the beam failure reporting method corresponding to the first beam failure event includes any of the following: For the BFD RS set associated with a RACH resource and when the terminal identifies the NBI RS, report based on the CFRA method on the RACH resource associated with the identified NBI RS; for the BFD RS set without a configured RACH resource, report using the CBRA method; Or Report on the RACH resource associated with the identified NBI RS, and send the BFR MAC-CE signaling on the resource associated with the RACH resource, where the BFR MAC-CE signaling includes the first beam failure event; or Report using the CBRA or PUSCH method, and report the first beam failure event during the reporting process; or Perform CBRA reporting using the identified NBI RS, and carry the first beam failure event in the msg A PUSCH or msg 3 PUSCH; or Report using the CBRA method on the RACH resource for BFR; or Perform CBRA reporting on the RACH resource associated with the identified NBI RS, and carry the first beam failure event in the msg A PUSCH or msg 3 PUSCH; or Report through the RACH resource associated with the first beam failure event.

7. The beam failure recovery method according to claim 1, wherein The first beam failure event is configured with a corresponding RACH resource; Determining the beam failure reporting method corresponding to the first beam failure event includes any of the following: If the RACH resource is configured with one associated NBI RS and the terminal identifies one associated NBI RS, then report on the RACH resource; or If the RACH resource is configured with multiple associated NBI RSs and the terminal identifies at least one associated NBI RS, then report on the RACH resource; or If the terminal does not identify an associated NBI RS, then report using the PUSCH method or the CBRA method; Report through the RACH resource associated with the first beam failure event; or Report through the RACH resource associated with the NBI RS, and send the BFR MAC-CE signaling on the resource associated with the RACH resource.

8. The beam failure recovery method according to claim 1, wherein Under the condition that a first association relationship between different beam failure events and random access channel (RACH) resources is included in the configuration information or predefined rules of the network side device, determining the beam failure reporting manner corresponding to the first beam failure event includes: determining, according to the first association relationship, a first RACH resource associated with the first beam failure event; reporting on the first RACH resource.

9. The beam failure recovery method according to claim 8, wherein, The configuration information or predefined rules of the network side device further include a second association relationship between different beam failure events and random access (RA) opportunities and / or preamble indices; The method further includes: determining, according to the second association relationship, the RA opportunity and / or preamble index associated with the first beam failure event.

10. The beam failure recovery method according to claim 1, wherein One or more BFD RS sets of the first cell set include one or more BFD RS sets of a primary cell (PCell) or a primary and secondary cell (PSCell), and one or more BFD RS sets of a secondary cell (SCell); determining the beam failure reporting manner corresponding to the first beam failure event includes any one of the following: performing CBRA reporting using a Physical Random Access Channel (PRACH), and carrying, during the reporting process, the first beam failure event included in a BFR MAC - CE signaling, where the first beam failure event includes information on one or more BFD RS sets for the SCell; or if an NBI RS corresponding to at least one BFD RS set in the PCell or PSCell is identified, performing CBRA reporting on the RACH resource associated with the identified NBI RS, and including the first beam failure event in a msg A Physical Uplink Shared Channel (PUSCH) or a msg3 PUSCH; or if an NBI RS corresponding to at least one BFD RS set in the PCell or PSCell is identified, reporting on the RACH resource associated with the identified NBI RS, and sending a BFR MAC - CE signaling on a resource associated with the RACH resource; or if an NBI RS corresponding to at least one BFD RS set in the PCell or PSCell is identified, performing CFRA reporting on the RACH resource associated with the identified NBI RS, and including the first beam failure event in a msg A PUSCH or a msg3 PUSCH; or if an NBI RS corresponding to at least one BFD RS set in the PCell or PSCell is identified, then reporting on the RACH resource associated with the identified NBI RS; or performing CFRA reporting, where the BFR MAC - CE signaling carried by the CFRA includes the first beam failure event; or reporting through a PUSCH, and reporting the first beam failure event during the reporting process; or reporting through the RACH resource associated with the first beam failure event.

11. A beam failure recovery method, characterized in that, including: Receive beam failure information for characterizing a first beam failure event, where the first beam failure event is used to indicate that one or more beam failure detection reference signal sets (BFD RS sets) in a first cell set have beam failures, and the first cell set includes one or more cells; the first cell set includes a primary cell (PCell) and / or a primary secondary cell (PSCell); Perform beam failure recovery according to the beam failure information; The receiving the beam failure information for characterizing the first beam failure event includes: Receiving the beam failure information sent through a beam failure reporting method corresponding to the first beam failure event, where the beam failure reporting method corresponding to the first beam failure event is determined based on the association relationship between the BFD RS set where the beam failure occurs, the NBIRS or NBI RS set, and the RACH resources, and the beam failure reporting method corresponding to the first beam failure event includes any one of the following: Reporting on one or more random access (RACH) resources associated with a new candidate beam indication reference signal (NBI RS) that is identified; or Performing contention-based random access (CBRA) reporting using one or more identified NBI RSs; or Reporting through CBRA; or Performing CBRA reporting on the RACH resources for BFR; or Reporting through the RACH resources associated with the first beam failure event; or Reporting through the RACH resources associated with the NBI RS, and sending beam failure recovery (BFR) medium access control - control element (MAC-CE) signaling on the resources associated with the RACH resources.

12. The beam failure recovery method according to claim 11, wherein It further includes: Sending the configuration information or predefined rules of the network side device to the terminal.

13. The beam failure recovery method according to claim 12, wherein The configuration information or predefined rules of the network side device include: One or more groups of random access channel (RACH) resources corresponding to the first cell, each group of RACH resources includes one or more RACH resources, and each RACH resource is associated with one or more new candidate beam indication reference signals (NBI RSs); and / or The first association relationship between different beam failure events and the random access channel (RACH) resources; and / or The second association relationship between different beam failure events and the random access (RA) opportunity and / or preamble index.

14. The beam failure recovery method according to claim 12 or 13, wherein The configuration information or predefined rules of the network side device include the search space set for BFR corresponding to the first cell set, and the search space set is used for the terminal to receive the response information sent by the network side device.

15. A beam failure recovery device, characterized in that, It includes a memory, a transceiver, and a processor: The memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations: Detect a first beam failure event, where the first beam failure event is used to indicate that one or more beam failure detection reference signal sets (BFD RS sets) in a first cell set have beam failures, and the first cell set includes one or more cells; the first cell set includes a primary cell (PCell) and / or a primary secondary cell (PSCell); Determine the beam failure reporting method corresponding to the first beam failure event based on the association relationship between the BFD RS set, NBI RS or NBI RS set where the beam failure occurs, and the RACH resource; Send beam failure information characterizing the first beam failure event to the network side device through the beam failure reporting method; The determination of the beam failure reporting method corresponding to the first beam failure event includes any one of the following: Report on one or more random access RACH resources associated with the new candidate beam indication reference signal NBI RS identified; or Perform contention-based random access CBRA reporting using one or more identified NBI RSs; or Report through CBRA; or Perform CBRA reporting on the RACH resource for BFR; or Report through the RACH resource associated with the first beam failure event; or Report through the RACH resource associated with the NBI RS, and send beam failure recovery BFR medium access control-control element MAC-CE signaling on the resource associated with the RACH resource.

16. The beam failure recovery device according to claim 15, wherein The BFR MAC-CE signaling contains the first beam failure event, and the first beam failure event includes at least one of the following: The number of BFD RS sets where the beam failure occurs in the PCell or PSCell; The number of NBI RSs of the PCell or PSCell identified; The number of BFD RS sets where the beam failure occurs in the SCell; The number of NBI RSs of the SCell identified; Whether an NBI RS associated with the first beam failure event is identified.

17. The beam failure recovery device according to claim 15, wherein The association relationship between the BFD RS set that sends the beam failure and the RACH resource in the first beam failure event includes any one of the following: One BFD RS set is associated with one NBI RS or a new candidate beam indication reference signal set NBI RSset, and one NBI RS or NBI RSset is associated with one RACH resource; or Multiple BFD RS sets are associated with one NBI RS or one NBI RSset, and one NBI RS or NBI RSset is associated with one RACH resource; or One BFD RS set is associated with multiple NBI RSs or NBI RSsets, and some NBI RSs or NBI RSsets are associated with RACH resources, and some NBI RSs or NBI RSsets are not associated with RACH resources; or Multiple BFD RS sets are associated with one NBI RS or NBI RSset, and the NBI RS or NBI RSset is not associated with RACH resources; or One BFD RS set is associated with one NBI RS or one NBI RSset, and the NBI RS or the NBI RSset is not associated with RACH resources.

18. The beam failure recovery device according to any one of claims 15 to 17, characterized in that, The determination of the beam failure reporting method corresponding to the first beam failure event includes: If the terminal recognizes the NBI RS corresponding to one of the BFD RS sets where beam failure occurs, the beam failure reporting method includes any one of the following: Report on the RACH resource associated with the recognized NBI RS; or Report on the RACH resource associated with the recognized NBI RS, and perform CBRA reporting for the BFD RS sets where NBI RS is not recognized; or Report through CBRA, and carry the BFR MAC-CE signaling including the first beam failure event in msgA PUSCH or msg3 PUSCH; or Perform CBRA reporting using the recognized NBI RS, and report the first beam failure event during the reporting process; or Report the BFR MAC-CE signaling including the first beam failure event through PUSCH; or When the recognized NBI RS is associated with the first BFD RS set, report on the RACH resource associated with the recognized NBI RS; or When the recognized NBI RS is associated with the second BFD RS set, report the BFR MAC-CE signaling including the first beam failure event through PUSCH; or Report through the RACH resource associated with the recognized NBI RS, and send the BFR MAC-CE signaling including the first beam failure event on the resource associated with the RACH resource.

19. The beam failure recovery device according to any one of claims 15 to 17, characterized in that, Determining the beam failure reporting method corresponding to the first beam failure event includes: If the terminal recognizes the NBI RS corresponding to multiple BFD RS sets where beam failure occurs, the beam failure reporting method includes any one of the following: Select one BFD RS set from multiple BFD RS sets where beam failure occurs, and report on the RACH resource corresponding to the selected BFD RS set; or Report on the RACH resources corresponding to multiple BFD RS sets where beam failure occurs; or If multiple BFD RS sets where beam failure occurs correspond to the same RACH resource, report on the same RACH resource; or Report on one or more determined RACH resources, and report the beam failure information in the BFR MAC-CE signaling carried in PUSCH or in the BFR MAC-CE signaling carried in the RACH transmission message; Report through the RACH resource associated with the first beam failure event; or Report through the RACH resource associated with the NBI RS, and send the BFR MAC-CE signaling on the resource associated with the RACH resource.

20. The beam failure recovery device according to claim 15, wherein The first beam failure event includes multiple BFD RS sets with beam failures, and at least one BFD RS set among the multiple BFD RS sets with beam failures is associated with RACH resources; Determining the beam failure reporting mode corresponding to the first beam failure event includes any one of the following: For a BFD RS set associated with RACH resources and when the terminal recognizes an NBI RS, report based on the CFRA mode on the RACH resources associated with the recognized NBI RS; for a BFD RS set without configured RACH resources, report using the CBRA mode; Or Report on the RACH resources associated with the recognized NBI RS, and send a BFR MAC-CE signaling on the resources associated with the RACH resources, where the BFR MAC-CE signaling includes the first beam failure event; or Report using the CBRA or PUSCH mode, and report the first beam failure event during the reporting process; Perform CBRA reporting using the recognized NBI RS, and carry the first beam failure event in the message msg A PUSCH or msg 3 PUSCH; or Report using the CBRA mode on the RACH resources for BFR; Perform CBRA reporting on the RACH resources associated with the recognized NBI RS, and carry the first beam failure event in the msg A PUSCH or msg 3 PUSCH; or Report through the RACH resources associated with the first beam failure event.

21. The beam failure recovery device according to claim 15, wherein The first beam failure event is configured with corresponding RACH resources; Determining the beam failure reporting mode corresponding to the first beam failure event includes any one of the following: If the RACH resources are configured with one associated NBI RS and the terminal recognizes one associated NBI RS, then report on the RACH resources; or If the RACH resources are configured with multiple associated NBI RSs and the terminal recognizes at least one associated NBI RS, then report on the RACH resources; or If the terminal does not recognize an associated NBI RS, then report using the PUSCH mode or the CBRA mode; Report through the RACH resources associated with the first beam failure event; or Report through the RACH resources associated with the NBI RS, and send a BFR MAC-CE signaling on the resources associated with the RACH resources.

22. The beam failure recovery apparatus according to claim 15, wherein Under the condition that the configuration information or predefined rules of the network side device include the first association relationship between different beam failure events and random access channel RACH resources; Determining the beam failure reporting mode corresponding to the first beam failure event includes: Determine the first RACH resources associated with the first beam failure event according to the first association relationship; Report on the first RACH resources.

23. The beam failure recovery apparatus according to claim 22, wherein The configuration information or predefined rules of the network-side device further include a second association relationship between different beam failure events and random access (RA) opportunities and / or preamble indices; The processor further performs the following operations: Determine the RA opportunity and / or preamble index associated with the first beam failure event according to the second association relationship.

24. The beam failure recovery apparatus according to claim 15, wherein One or more BFD RS sets of the first cell set include one or more BFD RS sets of the primary cell (PCell) or the primary and secondary cell (PSCell), and one or more BFD RS sets of the secondary cell (SCell); Determining the beam failure reporting method corresponding to the first beam failure event includes any one of the following: Report in the CBRA manner using a PRACH, and carry the first beam failure event included in the BFR MAC-CE signaling during the reporting process, where the first beam failure event includes information for the SCell; or If at least one BFD RS set corresponding NBI RS in the PCell or PSCell is recognized, report in the CBRA manner on the RACH resource associated with the recognized NBI RS, and include the first beam failure event in the msg A PUSCH or msg3 PUSCH; or If at least one BFD RS set corresponding NBI RS in the PCell or PSCell is recognized, report on the RACH resource associated with the recognized NBI RS, and send the BFR MAC-CE signaling on the resource associated with the RACH resource; or If at least one BFD RS set corresponding NBI RS in the PCell or PSCell is recognized, perform a CFRA report on the RACH resource associated with the recognized NBI RS, and include the first beam failure event in the msg A PUSCH or msg3 PUSCH; or If at least one BFD RS set corresponding NBI RS in the PCell or PSCell is recognized, then report on the RACH resource associated with the recognized NBI RS; or Report in the CFRA manner, and the BFR MAC-CE signaling carried by the CFRA includes the first beam failure event; Or Report through the PUSCH, and report the first beam failure event during the reporting process; or Report through the RACH resource associated with the first beam failure event.

25. A beam failure recovery device, characterized in that, Including a memory, a transceiver, and a processor: The memory is used to store computer programs; the transceiver is used to transmit and receive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations: Receive beam failure information for characterizing a first beam failure event, where the first beam failure event is used to indicate that beam failure occurs in one or more beam failure detection reference signal sets (BFD RS sets) in a first cell set, and the first cell set includes one or more cells; the first cell set includes a primary cell (PCell) and / or a primary secondary cell (PSCell); Perform beam failure recovery according to the beam failure information; The receiving the beam failure information for characterizing the first beam failure event includes: Receive the beam failure information sent through a beam failure reporting manner corresponding to the first beam failure event, where the beam failure reporting manner corresponding to the first beam failure event is determined based on the association relationship between the BFD RS set where beam failure occurs, a non-beamformed interference reference signal (NBIRS) or a non-beamformed interference RS set (NBI RS set), and a random access channel (RACH) resource, and the beam failure reporting manner corresponding to the first beam failure event includes any one of the following: Report on one or more identified random access (RACH) resources associated with a new candidate beam indication reference signal (NBI RS); or Perform contention-based random access (CBRA) reporting using one or more identified NBI RSs; or Report through CBRA; or Perform CBRA reporting on a RACH resource for beam failure recovery (BFR); or Report through a RACH resource associated with the first beam failure event; or Report through a RACH resource associated with an NBI RS, and send beam failure recovery (BFR) medium access control - control element (MAC-CE) signaling on a resource associated with the RACH resource.

26. The beam failure recovery device according to claim 25, wherein It further includes: Send configuration information or predefined rules of a network side device to a terminal.

27. The beam failure recovery device according to claim 26, wherein The configuration information or predefined rules of the network side device include: One or more groups of random access channel (RACH) resources corresponding to the first cell, where each group of RACH resources includes one or more RACH resources, and each RACH resource is associated with one or more new candidate beam indication reference signals (NBI RSs); and / or A first association relationship between different beam failure events and random access channel (RACH) resources; and / or A second association relationship between different beam failure events and random access (RA) opportunities and / or preamble indices.

28. The beam failure recovery device according to claim 26 or 27, characterized in that, The configuration information or predefined rules of the network side device include a search space set for BFR corresponding to the first cell, and the search space set is used for the terminal to receive response information sent by the network side device.

29. A beam failure recovery device, characterized in that It includes: A detection unit, configured to detect a first beam failure event, where the first beam failure event is used to indicate that beam failure occurs in one or more beam failure detection reference signal sets (BFD RS sets) of a first cell set, and the first cell set includes at least one cell; the first cell set includes a primary cell (PCell) and / or a primary secondary cell (PSCell); A determination unit, configured to determine a beam failure reporting manner corresponding to the first beam failure event based on an association relationship between a BFD RS set, an NBI RS, or an NBI RS set where beam failure occurs, and a RACH resource; A sending unit, configured to send, to a network-side device through the beam failure reporting manner, beam failure information for characterizing the first beam failure event; Determining the beam failure reporting manner corresponding to the first beam failure event includes any one of the following: Reporting on one or more identified random access RACH resources associated with a new candidate beam indication reference signal NBI RS; or Performing contention-based random access CBRA reporting by using one or more identified NBI RSs; or Reporting through CBRA; or Performing CBRA reporting on a RACH resource for BFR; or Reporting through a RACH resource associated with the first beam failure event; or Reporting through a RACH resource associated with an NBI RS, and sending beam failure recovery BFR medium access control-control element MAC-CE signaling on a resource associated with the RACH resource.

30. A beam failure recovery device, characterized in that, Including: A receiving unit, configured to receive beam failure information for characterizing a first beam failure event, where the first beam failure event is used to indicate that a beam failure occurs in one or more beam failure detection reference signal sets BFD RS set of a first cell set, and the first cell set includes at least one cell; the first cell set includes a primary cell PCell and / or a primary secondary cell PSCell; A beam failure recovery unit, configured to perform beam failure recovery according to the beam failure information; Receiving the beam failure information for characterizing the first beam failure event includes: Receiving the beam failure information sent through the beam failure reporting manner corresponding to the first beam failure event, where the beam failure reporting manner corresponding to the first beam failure event is determined based on an association relationship between a BFD RS set, an NBIRS or an NBI RS set where beam failure occurs, and a RACH resource, and the beam failure reporting manner corresponding to the first beam failure event includes any one of the following: Reporting on one or more identified random access RACH resources associated with a new candidate beam indication reference signal NBI RS; or Performing contention-based random access CBRA reporting by using one or more identified NBI RSs; or Reporting through CBRA; or Performing CBRA reporting on a RACH resource for BFR; or Reporting through a RACH resource associated with the first beam failure event; or Reporting through a RACH resource associated with an NBI RS, and sending beam failure recovery BFR medium access control-control element MAC-CE signaling on a resource associated with the RACH resource.

31. A processor-readable storage medium, characterized in that, The processor-readable storage medium stores a computer program, and the computer program is used to cause the processor to execute the method according to any one of claims 1 to 10.

32. A processor-readable storage medium, characterized in that, The processor-readable storage medium stores a computer program for causing the processor to execute the method according to any one of claims 11 to 14.

Images