JP7233550B2 - Beam failure recovery method, beam failure handling method, terminal and network side equipment - Google Patents

Description

(Cross reference to related applications)
This application claims priority from Chinese Patent Application No. 201910075898.1 filed in China on January 25, 2019, the entire content of which is incorporated herein by reference.
TECHNICAL FIELD The present invention relates to the field of communication technology, and more particularly to a beam failure recovery method, beam failure handling method, terminal and network-side equipment.

Currently, academia and industry usually use the method of polling to train simulated beamforming vectors. That is, the array elements in each polarization direction of each antenna panel sequentially transmit training signals (i.e., candidate forming vectors) at scheduled times in a time-division multiplex manner, and the terminal feeds back beam reports after making measurements. Then, the network side adopts this training signal to realize simulated beam transmission in the next traffic transmission. The content of the beam report is usually the reference signal resource identifier (eg, channel state information reference signal resource indicator: CSI-RS resource indicator, CRI, or synchronization signal block resource indication: SSB resource used by the optimal multiple transmit beams). indicator, SSBRI) and the measured received power of each transmit beam (eg, L1-RSRP, layer1-RSRP, layer 1 reference signal received power).

In a high-frequency band communication system, since the wavelength of radio signals is short, signal transmission is likely to be interrupted, resulting in interruption of signal transmission. Applying traditional radio link reconstruction takes a long time, so a beam failure recovery BFR (Beam Failure Recovery) mechanism is introduced, which consists of beam failure detection, new candidate beam recognition, beam failure recovery request transmission, The contents are divided into four parts: the terminal monitors the network-side device's response to the beam failure recovery request.

Beam Failure Detection BFD: The terminal measures a beam failure detection reference signal BFD RS (Beam Failure Detection Reference Signal) in the physical layer, and determines whether a beam failure event has occurred from the measurement result. Judgment condition: If the metric value (e.g., PDCCH block error rate) of all serving beams satisfies a predetermined condition (exceeds a predetermined threshold), it is identified as one beam failure instance BFI (Beam Failure Instance). and the terminal's physical layer reports an indication to the terminal's higher layers (eg, Media Access Control (MAC) layer). This reporting process is periodic. The reporting period of BFI is the shortest period of BFD RS, and the lower bound of the shortest period is 2ms. Conversely, when the physical layer of the terminal determines that no beam failure instance will occur, it does not report an indication to higher layers. The higher layers of the terminal count the BFI reported from the physical layer using a counter and a timer, reset the timer each time a BFI is obtained, and recount when the timer times out. and when the counter reaches the network-configured maximum number of times, the terminal declares that a beam failure event has occurred. The MAC layer counters and timers of the terminal in the prior art are set in each of the active band parts active BWP (active Band Width Part), and the activation and maintenance of the counters and timers corresponding to each BWP are independent, that is, each BWP The corresponding counters and timers operate independently, including activation, resetting, counting, timing, and the like.

New candidate beam identification: The physical layer of the terminal measures candidate beam reference signals (candidate beam RS) to search for new candidate beams. This step does not have to be performed after a beam failure event, but may be performed before the beam failure event. When the physical layer of the terminal receives a request, instruction, or notification from the upper layer of the terminal, the measurement result that satisfies a predetermined condition (L1-RSRP, which is a measurement for the candidate beam RS, exceeds a predetermined threshold) is sent to the upper layer of the terminal. layer, the reported content is {beam reference signal index, L1-RSRP}, and the upper layer of the terminal selects candidate beams based on the report of the physical layer.

Beam failure recovery request transmission: The higher layers of the terminal identify Physical Random Access Channel (PRACH) resources based on the selected candidate beams. If the terminal finds a candidate beam and is configured with a contention-free PRACH resource, it uses the contention-free PRACH to send the beam failure recovery request (BFRQ) to the base station. Otherwise, the terminal may use PRACH resources based on contention. Only contention-based PRACH resources are available after the beam failure recovery timer times out. The total number of times the two types of PRACH resources can be used cannot exceed a predetermined count value. Contention-free PRACH resources and other PRACH resources (for example, PRACH resources used for initial access) here are frequency-division multiplexing FDM (Frequency-division multiplexing extended) or code division multiplexing CDM (code division multiplexing auxiliary) can be anything. In addition, the related technology also supports transmission of BFRQ using a physical uplink control channel (PUCCH).

UE monitors gNB response for beam failure recovery request: BFR control resource set (CORESET-BFR) set after the network side equipment receives this BFRQ ) on a dedicated physical downlink control channel (PDCCH) and accompanied by an area radio network temporary identifier C-RNTI (Cell-Radio Network Temporary Identifier), and if Some may include switching to a new beam candidate or restarting beam search or other indications. The CORESET-BFR is a spatial quasi-colocation QCL (Quasi Co Location) with the downlink reference signal (DLRS) of the candidate beam found by the terminal. If the beam failure recovery is unsuccessful, the terminal's physical layer sends an indication to the terminal's upper layers for the upper layers to specify the subsequent radio link failure process.

A multi-carrier scene (Carrier Aggregation CA) may be understood to have multiple carriers, or multiple component carriers CC, or multiple cells. ) in one master cell (for example, a primary cell PCell (Primary cell) in a master cell group MCG (master cell group), or a primary secondary cell PSCell (Primary secondary cell) in a secondary cell group SCG (secondary cell group) ) and at least one secondary cell Scell (Secondary cell).

The current conclusion is that the beam failure recovery process on the secondary cell Scell can be supported and the supported scenes are:
Scenes with downlink and uplink in Scell, and scenes with only downlink in Scell.

The PCell may be in FR1 (Frequency Range 1, band 1) or FR2 (Frequency Range 2, band 2).

In related art, the BFR mechanism in 3GPP Release 15 is based on Pcell, and the BFR mechanism on Scell is under consideration in 3GPP Release 16. There is still no related art study on how to design the BFR mechanism after the introduction of multiple transmission and reception points (TRPs).

Embodiments of the present disclosure provide beam failure recovery methods, beam failure handling methods, terminals and network-side equipment, thereby solving the problem of how to design beam failure recovery mechanisms after multi-TRP introduction.

In order to solve the above technical problems, the present disclosure is implemented as follows.

A beam failure recovery method applied to a terminal, comprising:
obtaining N pieces of configuration information;
transmitting a beam failure recovery request based on the configuration information when determining that a beam failure event has occurred at at least one transmission reception point (TRP), wherein each of the N pieces of configuration information is transmitted and received differently. It provides a beam failure recovery method applied to the point TRP, wherein said configuration information includes parameters for beam failure recovery and N is an integer greater than one.

An embodiment of the present disclosure is a beam failure handling method applied to a network-side device, comprising:
Including setting N pieces of setting information in the terminal,
It further provides a beam failure handling method, wherein each of the N pieces of configuration information is applied to a different transmit/receive point TRP, said configuration information including parameters for beam failure recovery, N being an integer greater than one.

An embodiment of the present disclosure is a terminal comprising:
an acquisition module for acquiring N pieces of setting information;
a request transmission module for transmitting a beam failure recovery request based on the configuration information upon determining that a beam failure event has occurred in at least one TRP;
The terminal is further provided with N pieces of configuration information each applied to a different transmit/receive point TRP, said configuration information including parameters for beam failure recovery, N being an integer greater than one.

An embodiment of the present disclosure is a terminal comprising:
a processor, a memory, and a computer program stored in the memory and executable on the processor;
Here, there is further provided a terminal, wherein said computer program, when executed by said processor, implements the above beam failure recovery method.

An embodiment of the present disclosure is a network-side device comprising:
a setting module for setting N pieces of setting information in the terminal,
Further providing the network-side equipment, wherein each of the N pieces of configuration information is applied to a different transmit/receive point TRP, said configuration information including parameters for beam failure recovery, N being an integer greater than one.

An embodiment of the present disclosure is a network-side device comprising:
a processor, a memory, and a computer program stored in the memory and executable on the processor;
Here, the computer program further provides a network-side device, which, when executed by the processor, implements the above beam failure handling method.

An embodiment of the present disclosure is a computer-readable storage medium comprising:
There is further provided a computer readable storage medium storing a computer program that, when executed by a processor, implements the above beam failure recovery method or the above beam failure handling method.

In the embodiments of the present disclosure, the network configures N configuration information in the terminal, each applied to a different TRP, so that the beam of each TRP in which a beam failure event occurs can be quickly restored, and multiple Solves the problem of beam failure recovery in TRP scenes.

In order to describe the technical means in the embodiments of the present disclosure more clearly, the following briefly describes the drawings necessary for describing the embodiments of the present disclosure. They are only some of the described embodiments, and those skilled in the art can derive other drawings based on these drawings without creative efforts.

1 is a schematic diagram illustrating architecture of a wireless communication system according to an embodiment of the present disclosure; FIG. 4 is a flowchart of steps of a beam failure recovery method according to an embodiment of the present disclosure; FIG. 4 is a schematic diagram of steps of a beam failure handling method according to an embodiment of the present disclosure; FIG. 1 is a first structural schematic diagram of a terminal according to an embodiment of the present disclosure; FIG. 2 is a second structural schematic diagram of a terminal according to an embodiment of the present disclosure; 1 is a schematic diagram of a structure of a network device according to an embodiment of the present disclosure; FIG.

Hereinafter, the technical solutions in the embodiments of the present disclosure will be clearly and completely described with reference to the drawings in the embodiments of the present disclosure. not but part. All other embodiments obtained by persons skilled in the art without creative efforts based on the embodiments of the present disclosure belong to the protection scope of the present disclosure.

In the embodiments of the present disclosure, terms such as "exemplary" or "for example" are used for example, illustration, or description. Any embodiment or design that is labeled "exemplary" or "for example" in this disclosure is not to be construed as preferred or advantageous over other embodiments or designs. In particular, use of words such as "exemplary" or "for example" is intended to present the concepts involved in a concrete manner.

Embodiments of the disclosure are described below with reference to the drawings. The beam failure recovery method, beam failure handling method, terminal and network equipment provided by the embodiments of the present invention can be applied to wireless communication systems. This wireless communication system may use a 5G system, or an evolved Long Term Evolution eLTE system, or a subsequent evolution communication system. FIG. 1 is a schematic diagram illustrating the architecture of a wireless communication system according to an embodiment of the present disclosure. As shown in FIG. 1, this wireless communication system may include a network equipment 10 and a terminal (the terminal may be referred to as a user-side equipment), for example, the terminal is denoted as UE11, and UE11 is the network equipment. It may communicate with the device 10 . In actual application, the connections between the devices may be wireless connections, which are indicated by solid lines in FIG. 1 in order to intuitively show the connection relationship between the devices.

It should be noted that the communication system may include multiple UEs, and the network-side device can communicate with multiple UEs.

The network-side device 10 provided by the embodiment of the present invention may be a base station, the base station may be a commonly used base station, and an evolved base station eNB (evolved node base station). There may be network equipment in the 5G system (for example, next generation base station gNB (next generation node base station) or transmission and reception point TRP (transmission and reception point)) or equipment such as a cell.

The terminal provided by the embodiments of the present disclosure may be a mobile phone, a tablet PC, a notebook PC, an ultra-mobile personal computer (UMPC), a netbook, a wearable device (wearable device), an in-vehicle device, or a PDA (Personal Computer). Digital Assistant) or the like. It should be noted that the specific type of terminal is not limited in the embodiments of the present disclosure.

As shown in FIG. 2, the beam failure recovery method applied to the terminal according to an embodiment of the present disclosure includes steps 201 and 202. As shown in FIG.
Step 201: Obtaining N configuration information, each of the N configuration information being applied to a different transmitting/receiving point TRP, said configuration information including parameters for beam failure recovery, N being an integer greater than 1. .
Step 202: Send a beam failure recovery request according to the configuration information when determining that a beam failure event has occurred in at least one TRP.

Optionally, said configuration information includes:
a beam failure detection reference signal;
candidate beam reference signals;
a first resource for transmission of a beam failure recovery request by a terminal;
and a second resource for transmission of the beam failure recovery request response by the network-side device.

As an alternative embodiment, step 202 includes the following.
The terminal determines whether a beam failure event occurs in each TRP by measuring the beam failure detection reference signal included in the configuration information of each TRP, and the determination conditions are the same as those of a single TRP. Therefore, the description is omitted here. Further, the terminal identifies the target candidate beam on the TRP where the beam failure event occurred by measuring the candidate beam reference signal included in the configuration information of the TRP where the beam failure event occurred. Further, the terminal transmits a beam failure recovery request to the TRP in which the beam failure event has occurred, using the first resource for transmitting the beam failure recovery request by the terminal, which is included in the configuration information of the TRP in which the beam failure event has occurred. do.

As an alternative example, different TRPs are
different control resource sets, i.e. different control resource sets to which different configuration information is applied; different control resource set groups, i.e. different control resource set groups to which different configuration information is applied;
different explicitly defined TRPs;
different transmission configuration indication states, i.e. different transmission configuration indication states to which different configuration information is applied;
different transmission configuration indication status lists, i.e. different transmission configuration indication status lists to which different configuration information is applied;
different transmission configuration indication state pools, i.e. different transmission configuration indication state pools to which different configuration information applies;
different QCLs (Quasi Co Locations), i.e. different QCLs to which different configuration information is applied;
different QCL groups, i.e. different QCL groups to which different configuration information is applied;
different spatial relations, i.e. different spatial relations to which different configuration information is applied;
different spatial relationship groups, i.e. different spatial relationship groups to which different configuration information is applied;
Different physical downlink control channel PDCCH (Physical Downlink Control Channel) scramble identifiers, i.e., different PDCCH scramble identifiers to which different configuration information is applied;
different PDCCH scrambling identifier groups, i.e. different PDCCH scrambling identifier groups to which different configuration information is applied;
Different physical downlink shared channel PDSCH (Physical Downlink Shared Channel) scramble identifiers, i.e., different PDSCH scramble identifiers to which different configuration information is applied;
different PDSCH scrambling identifier groups, i.e. different PDSCH scrambling identifier groups to which different configuration information is applied;
different PDCCH configuration signaling elements, i.e. different PDCCH configuration signaling elements to which different configuration information is applied; and different PDSCH configuration signaling elements, i.e. different PDSCH configuration signaling elements to which different configuration information is applied. identified.

Optionally, in the above embodiments of the present disclosure, the configuration information of different TRPs are:
different beam failure detection reference signals;
different candidate beam reference signals;
different first resources for beam failure recovery request transmission by terminals;
the first resource for beam failure recovery request transmission by the terminal is the same;
different second resources for transmission of beam failure recovery request responses by network-side devices;
at least one of the second resource for beam failure recovery request response transmission by the network-side device is the same;

As an alternative embodiment, step 201 includes:
It includes acquiring the N pieces of setting information set in one Band Width Part (BWP) by the network-side device. That is, a plurality of setting information including parameters for beam failure recovery applied to different TRPs are set in the same BWP.
Note that the N pieces of configuration information may be received via one signaling or may be received via a plurality of signalings, and are not particularly limited here.

As an alternative example, if a beam failure event occurs at the first TRP, step 202 of the previous example of the present disclosure includes:
transmitting a beam failure recovery request to the first TRP based on a first resource for beam failure recovery request transmission by a terminal in configuration information corresponding to the first TRP;
or
A first resource for beam failure recovery request transmission by a terminal in configuration information corresponding to a second TRP other than the first TRP, such that the beam failure recovery request is transferred to the first TRP via the second TRP. transmitting a beam failure recovery request to the second TRP based on.

Briefly, embodiments of the present disclosure provide two schemes: directly sending a beam failure recovery request and indirectly sending a beam failure recovery request.

In addition, when a beam failure event occurs in all of a plurality of TRPs, the disclosed embodiment provides two methods of transmitting a beam failure recovery request, method 1 and method 2 below.
Method 1: when a beam failure event occurs in M TRPs, and the first resource for beam failure recovery request transmission by the terminal in the configuration information of the M TRPs is different, M is an integer greater than 1; be.
Step 202 includes sending a beam failure recovery request to each of the M TRPs in which a beam failure event has occurred according to different first resources in the configuration information of the M TRPs.
That is, the terminal transmits each beam failure recovery request using the first resource for transmitting beam failure recovery requests corresponding to different TRPs.
Method 2: when a beam failure event occurs in M TRPs, and the first resource for beam failure recovery request transmission by terminals in the configuration information of the M TRPs is the same, M is greater than 1; is an integer.
Step 202 includes sending a beam failure recovery request to a high priority TRP among the M TRPs in which a beam failure event has occurred, according to the first resource in the configuration information of the M TRPs.
That is, based on the predetermined priority, the terminal will prioritize sending beam failure recovery requests to higher priority TRPs.

Correspondingly, for a scene in which a beam failure event occurs in multiple TRPs, the multiple TRPs in which the beam failure event has occurred may share one second resource for beam failure recovery request response transmission. That is, when a beam failure event occurs in M TRPs, and the second resource for beam failure recovery request response transmission by the network device in the configuration information of the M TRPs is the same (M is 1 is an integer greater than), the method comprising:
Further comprising receiving a beam failure recovery request response sent on a second resource in the configuration information from a higher priority TRP in the M TRPs in which a beam failure event occurred.

The second resource for beam failure recovery request response transmission by the network-side device in the configuration information includes a control resource set CORESET-BFR for beam failure recovery.

That is, when a plurality of TRPs share one CORESET-BFR, when a beam failure event occurs in M TRPs, this CORESET-BFR is used for a TRP with a higher priority based on a predetermined priority. send a beam failure recovery request response.

When a plurality of TRPs share one CORESET-BFR and a beam failure event occurs in one TRP, the TRP in which the beam failure event occurs uses this CORESET-BFR to request beam failure recovery. Send a response.

Optionally, in said embodiment of the present disclosure, said TRP priority is:
index information of the control resource set;
index information of the control resource set group;
explicitly defined TRP identifier information;
Transmission configuration indication state information (e.g., index information, source reference signal information, QCL type information, etc.);
information of the transmission configuration indication status list (eg, index information, source reference signal information, QCL type information, etc.);
transmission configuration indication state pool information (e.g., index information, source reference signal information, QCL type information, etc.);
QCL information (e.g., index information, source reference signal information, QCL type information, etc.); QCL group information (e.g., index information, source reference signal information, QCL type information, etc.);
spatial relationship information (e.g., index information, source reference signal information, etc.);
spatial relationship group information (e.g., index information, source reference signal information, etc.);
PDCCH scrambling identifier information;
PDCCH scrambling identifier group information;
PDSCH scrambling identifier information;
PDSCH scrambling identifier group information;
PDCCH configuration signaling element information;
PDSCH configuration signaling element information.

For example, if different control resource sets identify different TRPs, the priority of control resource set 1 (corresponding to TRP1) is higher than the priority of control resource set 2 (corresponding to TRP2). I won't list them all here. The priority level of that TRP may be predefined by the protocol or network.

Further, in the embodiment of the present disclosure, after the terminal sends a beam failure recovery request, the beam failure recovery method includes:
Further comprising, when a predetermined condition is met, the terminal transmits the PUCCH using spatial relationship information of the PUCCH associated with the TRP in which the beam failure event occurred in a predetermined time period.

That is, in the embodiment of the present disclosure, regarding the resetting of the spatial relationship information of the PUCCH resource, only the spatial relationship information of the PUCCH related to the TRP in which the beam failure event occurs is reset, and for the TRP in which the beam failure event does not occur, , there is no need to reset the spatial relationship information for that PUCCH.

For example, when two TRPs are configured and a failure event occurs in TRP 1 and no failure event occurs in TRP 2, only the PUCCH related to TRP 1 is transmitted, and the network side can receive the PUCCH correctly. In addition, until the network side configures, reconfigures, activates, etc., the spatial relationship information of the PUCCH resource, the terminal determines in advance that the PUCCH spatial relationship information related to TRP1 will be used to transmit the PUCCH. Keep

Or, in the embodiment of the present disclosure, the beam failure recovery method comprises:
If the terminal does not receive downlink information transmitted from the TRP in which the beam failure event has occurred within a third predetermined period after transmitting a beam failure recovery request to the TRP in which the beam failure event has occurred, the terminal transmits PUCCH. Further including not sending.

The predetermined condition is
the terminal receiving downlink information transmitted from a TRP in which a beam failure event occurred;
the terminal sending a beam failure recovery request to the TRP where the beam failure event occurred;
The terminal has transmitted a beam failure recovery request to the TRP in which the beam failure event has occurred, and has not received downlink information transmitted from the TRP in which the beam failure event has occurred within the first predetermined time period. and at least one of

Optionally, in said embodiments of the present disclosure, said downlink information comprises:
the PDCCH in the control resource set CORESET-BFR for beam failure recovery, associated with the TRP in which the beam failure event occurred;
Downlink control information DCI (downlink control information);
A random access response RAR (random access response);
a release command or a deactivation command for releasing a cell in which a beam failure has occurred;
beam measurement and/or beam reporting trigger information for the TRP where the beam failure event occurred;
Trigger information for channel state information (CSI) measurement and/or CSI reporting for the TRP where the beam failure event occurs;
including at least one of acknowledgment information ACK and/or negative acknowledgment NACK corresponding to scheduling information for the TRP in which the beam failure event occurred, wherein said scheduling information includes scheduling information for cross-carrier as-scheduling.

The time starting point of the predetermined time period is
when the predetermined condition is satisfied, or
when a second predetermined time has passed after the predetermined condition is satisfied.

using spatially related information of uplink channels for transmission of beam failure recovery requests in a given cell;
using spatial relationship information or QCL information of a given channel in a given cell;
using spatial relationship information or QCL information of a given reference signal in a given cell;
A beam failure event is caused by one of: using the spatial relationship information or QCL information of a given channel in the primary cell Pcell; and using the spatial relationship information or QCL information of a given reference signal in the primary cell Pcell. The terminal identifies the spatial relationship information of the PUCCH related to the TRP that has been selected.

The predetermined cell may be a TRP cell in which a beam failure event has occurred. The contention-free PRACH is the only uplink channel for transmitting beam failure recovery requests in a given cell. Alternatively, this uplink channel is a contention-free PRACH or a contention PRACH. This uplink channel is PUCCH. Alternatively, this uplink channel is an uplink channel corresponding to MAC CE (MAC layer control unit).

The predetermined channel is one of a physical uplink control channel PUCCH, a physical random access channel PRACH, a physical uplink shared channel PUSCH, a physical downlink control channel PDCCH, and a physical downlink shared channel PDSCH.

The predetermined reference signals include a channel sounding reference signal (SRS), a channel state information reference signal (CSI-RS), a synchronization signal block (SSB), a tracking reference signal (TRS). PTRS (phase tracking reference signal).

In summary, in the embodiments of the present disclosure, the network configures the terminal with N configuration information, each applied to a different TRP, so that the beam of each TRP in which a beam failure event occurs can be quickly restored. It can solve the problem of beam failure recovery in multi-TRP scenes.

As shown in FIG. 3 , the embodiment of the present disclosure further provides a beam failure handling method applied to network-side equipment, which beam failure handling method includes step 301 .
Step 301: Configure N configuration information in the terminal, each of the N configuration information being applied to a different transmission/reception point TRP, the configuration information including parameters for beam failure recovery, N being an integer greater than 1. is.

Optionally, said configuration information includes:
a beam failure detection reference signal;
candidate beam reference signals;
a first resource for transmission of a beam failure recovery request by a terminal;
and a second resource for transmission of the beam failure recovery request response by the network-side device.

Alternatively, the terminal determines whether a beam failure event occurs in each TRP by measuring a beam failure detection reference signal included in the configuration information of each TRP, and the determination condition is that of a single TRP. Since it is the same as the judgment condition, the explanation is omitted here. Further, the terminal identifies the target candidate beam on the TRP where the beam failure event occurred by measuring the candidate beam reference signal included in the configuration information of the TRP where the beam failure event occurred. Further, the terminal transmits a beam failure recovery request to the TRP in which the beam failure event has occurred, using the first resource for transmitting the beam failure recovery request by the terminal, which is included in the configuration information of the TRP in which the beam failure event has occurred. do.

As an alternative example, different TRPs are
different control resource sets, i.e. different control resource sets to which different configuration information is applied; different control resource set groups, i.e. different control resource set groups to which different configuration information is applied;
different explicitly defined TRPs;
different transmission configuration indication states, i.e. different transmission configuration indication states to which different configuration information is applied;
different transmission configuration indication status lists, i.e. different transmission configuration indication status lists to which different configuration information is applied;
different transmission configuration indication state pools, i.e. different transmission configuration indication state pools to which different configuration information applies;
different QCLs, i.e. different QCLs to which different configuration information is applied;
different QCL groups, i.e. different QCL groups to which different configuration information is applied;
different spatial relations, i.e. different spatial relations to which different configuration information is applied;
different spatial relationship groups, i.e. different spatial relationship groups to which different configuration information is applied;
different physical downlink control channel PDCCH scrambling identifiers, i.e. different PDCCH scrambling identifiers to which different configuration information is applied;
different PDCCH scrambling identifier groups, i.e. different PDCCH scrambling identifier groups to which different configuration information is applied;
different physical downlink shared channel PDSCH scrambling identities, i.e. different PDSCH scrambling identities to which different configuration information is applied;
different PDSCH scrambling identifier groups, i.e. different PDSCH scrambling identifier groups to which different configuration information is applied;
different PDCCH configuration signaling elements, i.e. different PDCCH configuration signaling elements to which different configuration information is applied; and different PDSCH configuration signaling elements, i.e. different PDSCH configuration signaling elements to which different configuration information is applied. identified.

Optionally, in the above embodiments of the present disclosure, the configuration information of different TRPs are:
different beam failure detection reference signals;
different candidate beam reference signals;
different first resources for beam failure recovery request transmission by terminals;
the first resource for beam failure recovery request transmission by the terminal is the same;
different second resources for transmission of beam failure recovery request responses by network-side devices;
at least one of the second resource for beam failure recovery request response transmission by the network-side device is the same;

As an alternative embodiment, step 301 includes:
Configuring the N configuration information in one bandwidth part BWP in the terminal, i.e., multiple configuration information including parameters for beam failure recovery, which are applied to different TRPs, are stored in the same BWP Including being set.

Note that the N pieces of configuration information may be transmitted by one signaling or may be transmitted by a plurality of signalings, and are not particularly limited here.

As an alternative embodiment, if a beam failure event occurs at the first TRP, the method comprises:
the network-side device receiving a beam failure recovery request transmitted from the terminal based on the configuration information when it is the first TRP in which a beam failure event has occurred;
or
The network-side device receives a beam failure recovery request transmitted from the terminal based on the setting information when the second TRP is other than the first TRP in which the beam failure event has occurred, and transmits the beam failure recovery request. Further comprising forwarding to the first TRP.

In addition, when a beam failure event occurs in all of a plurality of TRPs, the disclosed embodiment provides two methods of transmitting a beam failure recovery request, method 1 and method 2 below.
Method 1: When a beam failure event occurs in M TRPs, and the first resource for beam failure recovery request transmission by the terminal in the configuration information of the M TRPs is different (M is an integer greater than 1 ), the method comprising:
A beam failure recovery request sent to each of the M TRPs in which a beam failure event has occurred, wherein the beam failure recovery request is sent from the terminal on different first resources in configuration information of the M TRPs. , receiving.
That is, the terminal transmits each beam failure recovery request using the first resource for transmitting beam failure recovery requests corresponding to different TRPs.
Method 2: When a beam failure event occurs in M TRPs, and the first resource for beam failure recovery request transmission by the terminal in the configuration information of the M TRPs is the same (M is greater than 1 is a large integer) and the method includes:
A beam failure recovery request sent to a higher priority TRP among the M TRPs in which a beam failure event occurred, sent from the terminal on a first resource in the configuration information of the M TRPs. receiving a beam failure recovery request.

That is, based on the predetermined priority, the terminal will prioritize sending beam failure recovery requests to higher priority TRPs.

Correspondingly, for a scene in which a beam failure event has occurred in multiple TRPs, the multiple TRPs in which the beam failure event has occurred may share a second resource for beam failure recovery request response transmission; That is, when a beam failure event occurs in M TRPs, and the second resource for beam failure recovery request response transmission by the network device in the configuration information of the M TRPs is the same (M is 1 is an integer greater than), the method comprising:
Further comprising a high priority TRP among the M TRPs using a second resource in the configuration information of the TRP to send a beam failure recovery request response to the terminal.

The second resource for beam failure recovery request response transmission by the network-side device in the configuration information includes a control resource set CORESET-BFR for beam failure recovery.

That is, when a plurality of TRPs share one CORESET-BFR, when a beam failure event occurs in M TRPs, this CORESET-BFR is used for a TRP with a higher priority based on a predetermined priority. send a beam failure recovery request response.
When a plurality of TRPs share one CORESET-BFR and a beam failure event occurs in one TRP, the TRP in which the beam failure event occurs uses this CORESET-BFR to request beam failure recovery. Send a response.

Optionally, in said embodiment of the present disclosure, said TRP priority is:
index information of the control resource set;
index information of the control resource set group;
explicitly defined TRP identifier information;
Transmission configuration indication state information (e.g., index information, source reference signal information, QCL type information, etc.);
information of the transmission configuration indication status list (eg, index information, source reference signal information, QCL type information, etc.);
transmission configuration indication state pool information (e.g., index information, source reference signal information, QCL type information, etc.);
QCL information (e.g., index information, source reference signal information, QCL type information, etc.); QCL group information (e.g., index information, source reference signal information, QCL type information, etc.);
spatial relationship information (e.g., index information, source reference signal information, etc.);
spatial relationship group information (e.g., index information, source reference signal information, etc.);
PDCCH scrambling identifier information;
PDCCH scrambling identifier group information;
PDSCH scrambling identifier information;
PDSCH scrambling identifier group information;
PDCCH configuration signaling element information;
PDSCH configuration signaling element information.

For example, if different control resource sets identify different TRPs, the priority of control resource set 1 (corresponding to TRP1) is higher than the priority of control resource set 2 (corresponding to TRP2). I won't list them all here. The priority level of that TRP may be predefined by the protocol or network.

Further, in the embodiment of the present disclosure, after the terminal sends a beam failure recovery request, the method includes:
Receiving a PUCCH transmitted from the terminal in a predetermined time period using the identified spatial relationship information.

In addition, in the embodiment of the present disclosure, regarding the resetting of the spatial relationship information of the PUCCH resource, only the spatial relationship information of the PUCCH related to the TRP in which the beam failure event occurs is reset, and for the TRP in which the beam failure event does not occur, There is no need to reset the spatial relationship information for that PUCCH.

Optionally, using the specified spatial relationship information, receiving a PUCCH transmitted in a predetermined time period from a terminal that satisfies a predetermined condition,
After receiving a beam failure recovery request transmitted from a terminal, do not transmit downlink information, and use the specified spatial relationship information to receive PUCCH transmitted from a terminal that satisfies a predetermined condition in a predetermined time period. matter,
Alternatively, after receiving a beam failure recovery request transmitted from a terminal, downlink information is transmitted, and using the specified spatial relationship information, a PUCCH transmitted in a predetermined time period from a terminal that satisfies a predetermined condition is received. including to do.

Optionally, the identified spatial relationship information is spatial relationship information of PUCCH associated with the TRP in which the beam failure event occurred.

For example, if two TRPs are configured and a failure event occurs in TRP 1 and no failure event occurs in TRP 2, only the PUCCH related to TRP 1 is transmitted, and the network side can receive the PUCCH correctly. As such, until the network side configures, reconfigures, activates, etc., the spatial relationship information of the PUCCH resource, the terminal will use this PUCCH spatial relationship information related to TRP1 to transmit the PUCCH in advance. Confirm.

Optionally, in the embodiments of the present disclosure,
using spatially related information of uplink channels for transmission of beam failure recovery requests in a given cell;
using spatial relationship information or QCL information of a given channel in a given cell;
using spatial relationship information or QCL information of a given reference signal in a given cell;
A beam failure event is caused by one of: using the spatial relationship information or QCL information of a given channel in the primary cell Pcell; and using the spatial relationship information or QCL information of a given reference signal in the primary cell Pcell. The network side specifies the spatial relationship information of the PUCCH related to the TRP.

The predetermined cell may be a TRP cell in which a beam failure event has occurred. The contention-free PRACH is the only uplink channel for transmitting beam failure recovery requests in a given cell. Alternatively, this uplink channel is a contention-free PRACH or a contention PRACH. This uplink channel is PUCCH. Alternatively, this uplink channel is an uplink channel corresponding to MAC CE (MAC layer control unit).

The predetermined channel is one of a physical uplink control channel PUCCH, a physical random access channel PRACH, a physical uplink shared channel PUSCH, a physical downlink control channel PDCCH, and a physical downlink shared channel PDSCH.

The predetermined reference signal is one of a channel sounding reference signal SRS, a channel state information reference signal CSI-RS, a synchronization signal block SSB, a tracking reference signal TRS and a phase tracking reference signal PTRS.

Optionally, said predetermined condition is
the terminal receiving downlink information transmitted from a TRP in which a beam failure event occurred;
the terminal sending a beam failure recovery request to the TRP where the beam failure event occurred;
The terminal has transmitted a beam failure recovery request to the TRP in which the beam failure event has occurred, and has not received downlink information transmitted from the TRP in which the beam failure event has occurred within the first predetermined time period. and at least one of

Here, the downlink information is
the PDCCH in the control resource set CORESET-BFR for beam failure recovery, associated with the TRP in which the beam failure event occurred;
Downlink control information DCI;
a random access response RAR;
a release command or a deactivation command for releasing a cell in which a beam failure has occurred;
beam measurement and/or beam reporting trigger information for the TRP where the beam failure event occurred;
channel state information CSI measurement and/or CSI reporting trigger information for the TRP in which the beam failure event occurred;
It includes at least one of acknowledgment information ACK and/or negative acknowledgment NACK corresponding to scheduling information for the TRP in which the beam failure event occurred.

As an alternative example,
The time starting point of the predetermined time period is
when the predetermined condition is satisfied, or
when a second predetermined time has passed after the predetermined condition is satisfied.

In summary, in the embodiments of the present disclosure, the network configures the terminal with N configuration information, each applied to a different TRP, so that the beam of each TRP in which a beam failure event occurs can be quickly restored. It can solve the problem of beam failure recovery in multi-TRP scenes.

A terminal 400 according to an embodiment of the present disclosure, as shown in FIG.
An acquisition module for acquiring N configuration information, each of the N configuration information being applied to a different transmit/receive point TRP, said configuration information including parameters for beam failure recovery, N being an integer greater than 1 an acquisition module 401 that is
a request transmission module 402 for transmitting a beam failure recovery request based on the configuration information when determining that a beam failure event has occurred in at least one TRP.

Optionally, in the above embodiments of the present disclosure, the different TRPs are
different control resource sets and
different control resource set groups and
different explicitly defined TRPs;
different transmission setting indication states;
a different transmission setting indication status list;
different transmission setting indication state pools;
different quasi-colocation QCLs;
with different QCL groups;
different spatial relationships and
different spatial relationship groups and
a different physical downlink control channel PDCCH scramble identifier;
different PDCCH scrambling identifier groups;
a different physical downlink shared channel PDSCH scrambling identifier;
different PDSCH scrambling identifier groups;
different PDCCH configuration signaling elements;
Different PDSCH configuration signaling elements are identified in at least one manner.

Optionally, in the embodiment of the present disclosure, the configuration information comprises:
a beam failure detection reference signal;
candidate beam reference signals;
a first resource for transmission of a beam failure recovery request by a terminal;
and a second resource for transmission of the beam failure recovery request response by the network-side device.

Optionally, in the above embodiments of the present disclosure, the configuration information of different TRPs are:
different beam failure detection reference signals;
different candidate beam reference signals;
different first resources for beam failure recovery request transmission by terminals;
the first resource for beam failure recovery request transmission by the terminal is the same;
different second resources for transmission of beam failure recovery request responses by network-side devices;
at least one of the second resource for beam failure recovery request response transmission by the network-side device is the same;

Optionally, in the embodiment of the present disclosure, the acquisition module comprises:
It includes an obtaining sub-module for obtaining the N setting information set in one Band Width Part (BWP) by the network-side device.

Optionally, in the embodiment of the present disclosure, the request sending module comprises:
When a beam failure event occurs in the first TRP, send a beam failure recovery request to the first TRP according to the first resource for beam failure recovery request transmission by the terminal in the configuration information corresponding to the first TRP. or
A first resource for beam failure recovery request transmission by a terminal in configuration information corresponding to a second TRP other than the first TRP, such that the beam failure recovery request is transferred to the first TRP via the second TRP. a third request sending sub-module for sending a beam failure recovery request to the second TRP according to the request.

Optionally, in the embodiment of the present disclosure, the request sending module comprises:
If a beam failure event occurs in M TRPs, and the first resource for beam failure recovery request transmission by the terminal in the configuration information of the M TRPs is different (M is an integer greater than 1); a first request transmission submodule for transmitting a beam failure recovery request to each of the M TRPs in which a beam failure event occurs according to different first resources in configuration information of the M TRPs;

Optionally, in the embodiment of the present disclosure, the request sending module comprises:
If a beam failure event occurs in M TRPs, and the first resource for beam failure recovery request transmission by the terminal in the configuration information of the M TRPs is the same (M is an integer greater than 1 ), a second request transmission submodule for transmitting a beam failure recovery request to a high-priority TRP among the M TRPs in which a beam failure event has occurred, according to the first resource in the configuration information of the M TRPs; include.

Optionally, in the embodiment of the present disclosure, the terminal comprises:
If a beam failure event occurs in M TRPs, and the second resource for beam failure recovery request response transmission by the network-side device in the configuration information of the M TRPs is the same (M is greater than 1 is an integer) and receives a beam failure recovery request response transmitted on the second resource in the configuration information from a higher priority TRP among the M TRPs in which a beam failure event has occurred. .

Optionally, in the embodiment of the present disclosure, the second resource for beam failure recovery request response transmission by the network-side device in the configuration information includes:
Contains the control resource set CORESET-BFR for beam failure recovery.

Optionally, in said embodiment of the present disclosure, said TRP priority is:
index information of the control resource set;
index information of the control resource set group;
explicitly defined TRP identifier information;
information on the transmission setting instruction state;
information on the transmission setting instruction status list;
information in the transmission setting indication state pool;
QCL information and
QCL Group information and
Spatial relationship information and
Spatial relationship group information and
PDCCH scrambling identifier information;
PDCCH scrambling identifier group information;
PDSCH scrambling identifier information;
PDSCH scrambling identifier group information;
PDCCH configuration signaling element information;
PDSCH configuration signaling element information.

Optionally, in the embodiment of the present disclosure, the terminal comprises:
The method further includes a first transmitting module for transmitting the PUCCH using spatial relationship information of the PUCCH associated with the TRP in which the beam failure event occurs in a predetermined time period when a predetermined condition is met.

Optionally, in the embodiment of the present disclosure, the terminal comprises:
After transmitting a beam failure recovery request to the TRP in which the beam failure event has occurred, the processing module does not transmit PUCCH if downlink information transmitted from the TRP in which the beam failure event has occurred is not received within a third predetermined period. further includes

Optionally, in said embodiments of the present disclosure, said predetermined condition is:
the terminal receiving downlink information transmitted from a TRP in which a beam failure event occurred;
the terminal sending a beam failure recovery request to the TRP where the beam failure event occurred;
The terminal has transmitted a beam failure recovery request to the TRP in which the beam failure event has occurred, and has not received downlink information transmitted from the TRP in which the beam failure event has occurred within the first predetermined time period. and at least one of

Optionally, in said embodiments of the present disclosure, said downlink information comprises:
the PDCCH in the control resource set CORESET-BFR for beam failure recovery, associated with the TRP in which the beam failure event occurred;
Downlink control information DCI;
a random access response RAR;
a release command or a deactivation command for releasing a cell in which a beam failure has occurred;
beam measurement and/or beam reporting trigger information for the TRP where the beam failure event occurred;
channel state information CSI measurement and/or CSI reporting trigger information for the TRP in which the beam failure event occurred;
It includes at least one of acknowledgment information ACK and/or negative acknowledgment NACK corresponding to scheduling information for the TRP in which the beam failure event occurred.

Optionally, in the embodiment of the present disclosure, the time origin of the predetermined time period is:
when the predetermined condition is satisfied, or
when a second predetermined time has passed after the predetermined condition is satisfied.

Optionally, in the embodiment of the present disclosure, the terminal comprises:
using spatially related information of uplink channels for transmission of beam failure recovery requests in a given cell;
using spatial relationship information or QCL information of a given channel in a given cell;
using spatial relationship information or QCL information of a given reference signal in a given cell;
A TRP in which a beam failure event has occurred by one of: using the spatial relationship information or QCL information of a given channel in the primary cell; and using the spatial relationship information or QCL information of a given reference signal in the primary cell. further comprising a first information determining module for determining spatial relationship information of PUCCH associated with .

Alternatively, the terminal provided in the embodiment of the present disclosure can implement each process implemented by the terminal in the method embodiment of FIG. 2, which will not be repeated here to avoid duplication.

In summary, in the embodiments of the present disclosure, the network configures the terminal with N configuration information, each applied to a different TRP, so that the beam of each TRP in which a beam failure event occurs can be quickly restored. It can solve the problem of beam failure recovery in multi-TRP scenes.

It should be noted that the terminal provided by the embodiments of the present disclosure is a terminal capable of performing the beam failure recovery method, and all the embodiments of the beam failure recovery method are applied to this terminal, and the same or similar effect can be achieved.

As shown in FIG. 5, which is a schematic diagram showing the hardware structure of a terminal that implements each embodiment of the present disclosure, a terminal 500 includes a radio frequency unit 501, a network module 502, an audio output unit 503, an input unit 504, Including but not limited to sensor 505, display unit 506, user input unit 507, interface unit 508, memory 509, processor 510, power supply 511 and the like. Those skilled in the art will appreciate that the terminal structure shown in FIG. 5 is not a definition of a terminal and that a terminal may contain more or fewer elements, a combination of several elements, or a different arrangement of elements than shown. It can be understood. In embodiments of the present disclosure, terminals include, but are not limited to, mobile phones, tablets, laptops, palmtops, in-vehicle terminals, wearable devices, pedometers, and the like.

Here, the radio frequency unit 501 obtains N configuration information, each of the N configuration information is applied to a different transmit/receive point TRP, said configuration information includes parameters for beam failure recovery, and N is An integer greater than 1.

Processor 510: Transmits a beam failure recovery request on the radio frequency unit 501 according to said configuration information when determining that a beam failure event has occurred in at least one TRP.

In summary, in the embodiments of the present disclosure, the network configures the terminal with N configuration information, each applied to a different TRP, so that the beam of each TRP in which a beam failure event occurs can be quickly restored. It can solve the problem of beam failure recovery in multi-TRP scenes.

It should be noted that the terminal provided by the embodiments of the present disclosure is a terminal capable of performing the beam failure recovery method, and all the embodiments of the beam failure recovery method are applied to this terminal, and the same or similar effect can be achieved.

It should be noted that in the embodiments of the present disclosure, the radio frequency unit 501 may be used for transmitting and receiving information or transmitting and receiving signals during a call, specifically, after receiving downlink data from the base station, the processor 510 and transmit uplink data to the base station. Radio frequency unit 501 typically includes, but is not limited to, an antenna, at least one amplifier, transceiver, coupler, low noise amplifier, duplexer, and the like. Radio frequency unit 501 may also communicate with networks and other devices via a wireless communication system.

Through the network module 502, the terminal provides users with wireless broadband Internet access, such as receiving emails, browsing web pages, and accessing streaming media.

The audio output unit 503 can convert the audio data received by the radio frequency unit 501 or the network module 502 or stored in the memory 509 into an audio signal and output as sound. Audio output unit 503 may also provide audio output associated with particular functions performed by terminal 500 (eg, call tone, message tone, etc.). Audio output unit 503 includes a speaker, buzzer, handset, and the like.

The input unit 504 is used for receiving audio or video signals. The input unit 504 may include a graphics processor GPU (Graphics Processing Unit) 5041 and a microphone 5042, which can process still images or videos obtained by an image capture device such as a camera in video capture mode or image capture mode. Process image data. The processed image frames can be displayed on display unit 506 . Image frames processed by GPU 5041 may be stored in memory 509 (or other storage medium) or may also be transmitted via radio frequency unit 501 or network module 502 . A microphone 5042 can receive speech and process such speech into audio data. The processed audio data can be converted into an output format that can be transmitted to a mobile communication base station via radio frequency unit 501 when in telephone call mode.

Terminal 500 includes at least one sensor 505, such as a light sensor, motion sensor, or other sensor. Specifically, the light sensor includes an ambient light sensor and a proximity sensor, where the ambient light sensor can adjust the brightness of the display panel 5061 according to the brightness of the ambient light, and the proximity sensor can: The display panel 5061 and/or the backlight can be turned off when the terminal 500 is moved to the ear. As a type of motion sensor, the accelerometer sensor detects the magnitude of acceleration in all directions (usually three axes), detects the magnitude and direction of gravity when stationary, and adjusts the orientation of the device (e.g. landscape vs. portrait). screen switching, related games, magnetometer attitude calibration) and recognition of vibration-related functions (pedometer, knock, etc.). It may include gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., not detailed here.

The display unit 506 is used to display information input by the user or information provided to the user. The display unit 506 may include a display panel 5061 that may be configured in the form of LCD (Liquid Crystal Display), OLED (Organic Light-Emitting Diode), or the like.

A user input unit 507 can be used to receive input digit or character information and generate key signal inputs related to terminal user settings and function controls. Specifically, the user input unit 507 includes a touch panel 5071 and another input device 5072 . The touch panel 5071 is also called a touch screen, and a touch operation by a user on or near the touch panel 5071 (a user's operation on or near the touch panel 5071 with any appropriate object or accessory such as a finger, a stylus, etc.) is performed. collect. The touch panel 5071 may include two parts, a touch sensing device and a touch controller, where the touch sensing device detects the user's touch orientation, detects the signal caused by the touch operation, and sends the signal to the touch controller. The touch controller receives touch information from the touch sensing device, converts it to contact coordinates, sends it to processor 510, and receives and executes commands sent from processor 510. FIG. Also, the touch panel 5071 can be implemented in many types such as resistive, capacitive, infrared, and surface acoustic waves. In addition to touch panel 5071 , user input unit 507 may include other input devices 5072 . Specifically, other input devices 5072 include, but are not limited to, physical keyboards, function keys (eg, volume control keys, switch keys, etc.), trackballs, mice, control levers. , I won't exaggerate here.

Further, the touch panel 5071 may cover the display panel 5061, and after the touch panel 5071 detects a touch operation on or near it, transmits to the processor 510 to identify the type of touch event, and then the processor 510: A corresponding visual output is provided to the display panel 5061 according to the type of touch event. In FIG. 5, the touch panel 5071 and the display panel 5061 function as two independent components that implement the input/output function of the terminal. Although an output function can be realized, it is not particularly limited here.

An interface unit 508 is an interface through which an external device and the terminal 500 are connected. External devices include, for example, wired or wireless headphone ports, external power (or battery charger) ports, wired or wireless data ports, memory card ports, ports for connecting devices equipped with identification modules, audio input/output ( I/O) ports, video I/O ports, headphone ports, and the like. Interface unit 508 receives input (e.g., data information, electrical, etc.) from external devices, transmits received input to one or more elements within terminal 500, and communicates between terminal 500 and external devices. It can be used for sending data.

The memory 509 can be used to store various data as well as software programs. The memory 509 is primarily created based on an operating system, a program storage area storing application programs required for at least one function (e.g., sound reproduction function, image reproduction function, etc.), and mobile phone usage. may include a data storage area storing stored data (eg, audio data, phone books, etc.). Additionally, memory 509 may include high speed random access memory, but may also include at least one disk storage device, non-volatile memory such as a flash memory device, or other volatile solid-state storage device.

A processor 510, which is the control center of the terminal, connects parts of the entire terminal using various interfaces and lines, executes software programs and/or modules stored in memory 509, and executes software programs and/or modules stored in memory 509. By calling the data stored in the terminal, various functions and data processing of the terminal are executed, and the entire terminal is monitored. Processor 510 may include one or more processing units, optionally processor 510 integrates an application processor and a modulation-demodulation processor, where the application processor primarily functions as an operating system, user interface and application processor. It processes programs and the like, and the modulation/demodulation processor mainly processes wireless communications. Note that the modulation and demodulation processor need not be integrated with processor 510 .

Terminal 500 may include a power source 511 (e.g., a battery) that powers the individual components, but alternatively power source 511 is logically connected to processor 510 via a power management system to enable power management. Functions such as charging, discharging, and power management can be managed through the system.

Terminal 500 also includes functional modules (not shown), which will not be described in detail here.

Optionally, embodiments of the present disclosure further provide a terminal, said terminal comprising a processor, a memory, and a computer program stored in said memory and executable on said processor, wherein: executes the computer program to implement each process of the beam failure recovery method embodiment. The terminals can achieve the same technical effect and are not repeated here to avoid duplication.

Embodiments of the present disclosure also provide a computer readable storage medium storing a computer program that, when executed by a processor, implements the various processes of the beam failure recovery method embodiments described above, as well as the The effect can be achieved and will not be repeated here to avoid duplication. Here, the computer-readable storage medium is ROM (Read-Only Memory), RAM (Random Access Memory), magnetic disk, optical disk, or the like.

As shown in FIG. 6, a network-side device 600 according to an embodiment of the present disclosure:
A configuration module for configuring N configuration information in a terminal, each of the N configuration information being applied to a different transmission/reception point TRP, said configuration information including parameters for beam failure recovery, wherein N is greater than 1. Contains a configuration module 601, which is a large integer.

Optionally, in the above embodiments of the present disclosure, the different TRPs are
different control resource sets and
different control resource set groups and
different explicitly defined TRPs;
different transmission setting indication states;
a different transmission setting indication status list;
different transmission setting indication state pools;
different quasi-colocation QCLs;
with different QCL groups;
different spatial relationships and
different spatial relationship groups and
a different physical downlink control channel PDCCH scramble identifier;
different PDCCH scrambling identifier groups;
a different physical downlink shared channel PDSCH scrambling identifier;
different PDSCH scrambling identifier groups;
different PDCCH configuration signaling elements;
Different PDSCH configuration signaling elements are identified in at least one manner.

Optionally, in the embodiment of the present disclosure, the configuration information comprises:
a beam failure detection reference signal;
candidate beam reference signals;
a first resource for transmission of a beam failure recovery request by a terminal;
and a second resource for transmission of the beam failure recovery request response by the network-side device.

Optionally, in the above embodiments of the present disclosure, the configuration information of different TRPs are:
different beam failure detection reference signals;
different candidate beam reference signals;
different first resources for beam failure recovery request transmission by terminals;
the first resource for beam failure recovery request transmission by the terminal is the same;
different second resources for transmission of beam failure recovery request responses by network-side devices;
at least one of the second resource for beam failure recovery request response transmission by the network-side device is the same;

Optionally, in the embodiment of the present disclosure, the configuration module comprises:
A configuration sub-module for configuring the N configuration information in one bandwidth part BWP for the terminal.
Optionally, in the embodiment of the present disclosure, the network-side device comprises:
the network-side device receives a beam failure recovery request transmitted from the terminal based on the configuration information if it is the first TRP in which a beam failure event has occurred;
or
The network-side device receives a beam failure recovery request transmitted from the terminal based on the setting information when the second TRP is other than the first TRP in which the beam failure event has occurred, and transmits the beam failure recovery request. including a request receiving module for forwarding to the first TRP;

Optionally, in the embodiment of the present disclosure, the network-side device comprises:
If a beam failure event occurs in M TRPs, and the first resource for beam failure recovery request transmission by the terminal in the configuration information of the M TRPs is different (M is an integer greater than 1). , a beam failure recovery request sent to each of the M TRPs in which a beam failure event has occurred, wherein the beam failure recovery request is sent from the terminal on different first resources in the configuration information of the M TRPs. further comprising a first receiving module that receives the

Optionally, in the embodiment of the present disclosure, the network-side device comprises:
If a beam failure event occurs in M TRPs, and the first resource for beam failure recovery request transmission by the terminal in the configuration information of the M TRPs is the same (M is an integer greater than 1 Yes), a beam failure recovery request sent to a higher priority TRP among the M TRPs in which a beam failure event has occurred, from the terminal on the first resource in the configuration information of the M TRPs. and a second receiving module for receiving the transmitted beam failure recovery request.

Optionally, in the embodiment of the present disclosure, the network-side device comprises:
If a beam failure event occurs in M TRPs, and the second resource for beam failure recovery request response transmission by the network-side device in the configuration information of the M TRPs is the same (M is greater than 1 is an integer), and a higher priority TRP among the M TRPs further comprises a second transmission module for transmitting a beam failure recovery request response to the terminal using a second resource in the configuration information of the TRP.

Optionally, in the embodiment of the present disclosure, the second resource for beam failure recovery request response transmission by the network-side device in the configuration information includes:
Contains the control resource set CORESET-BFR for beam failure recovery.

Optionally, in said embodiment of the present disclosure, said TRP priority is:
index information of the control resource set;
index information of the control resource set group;
explicitly defined TRP identifier information;
information on the transmission setting instruction state;
information on the transmission setting instruction status list;
information in the transmission setting indication state pool;
QCL information and
QCL Group information and
Spatial relationship information and
Spatial relationship group information and
PDCCH scrambling identifier information;
PDCCH scrambling identifier group information;
PDSCH scrambling identifier information;
PDSCH scrambling identifier group information;
PDCCH configuration signaling element information;
PDSCH configuration signaling element information.

Optionally, in the embodiment of the present disclosure, the network-side device comprises:
It further includes a third receiving module for receiving PUCCH transmitted in a predetermined time period from terminals satisfying a predetermined condition using the identified spatial relationship information.

Optionally, in said embodiment of the present disclosure, said third receiving module comprises:
After receiving a beam failure recovery request transmitted from a terminal, do not transmit downlink information, and use the specified spatial relationship information to receive PUCCH transmitted from a terminal that satisfies a predetermined condition in a predetermined time period. including a first receiving sub-module;

Optionally, in said embodiment of the present disclosure, said third receiving module comprises:
After receiving a beam failure recovery request transmitted from the terminal, downlink information is transmitted, and using the specified spatial relationship information, a PUCCH transmitted in a predetermined time period from a terminal that satisfies a predetermined condition is received. Contains two receiving sub-modules.

Optionally, in the embodiment of the present disclosure, the identified spatial relationship information is the spatial relationship information of the PUCCH associated with the TRP in which the beam failure event occurred.

Optionally, in the embodiment of the present disclosure, the network-side device comprises:
using spatially related information of uplink channels for transmission of beam failure recovery requests in a given cell;
using spatial relationship information or QCL information of a given channel in a given cell;
using spatial relationship information or QCL information of a given reference signal in a given cell;
A TRP in which a beam failure event has occurred by one of: using the spatial relationship information or QCL information of a given channel in the master cell; and using the spatial relationship information or QCL information of a given reference signal in the master cell. further comprising a second information determining module for determining spatial relationship information of PUCCH associated with .

Optionally, in said embodiments of the present disclosure, said predetermined condition is:
the terminal receiving downlink information transmitted from a TRP in which a beam failure event occurred;
the terminal sending a beam failure recovery request to the TRP where the beam failure event occurred;
The terminal has transmitted a beam failure recovery request to the TRP in which the beam failure event has occurred, and has not received downlink information transmitted from the TRP in which the beam failure event has occurred within the first predetermined time period. and at least one of

Optionally, in said embodiments of the present disclosure, said downlink information comprises:
the PDCCH in the control resource set CORESET-BFR for beam failure recovery, associated with the TRP in which the beam failure event occurred;
Downlink control information DCI;
a random access response RAR;
a release command or a deactivation command for releasing a cell in which a beam failure has occurred;
beam measurement and/or beam reporting trigger information for the TRP where the beam failure event occurred;
channel state information CSI measurement and/or CSI reporting trigger information for the TRP in which the beam failure event occurred;
It includes at least one of acknowledgment information ACK and/or negative acknowledgment NACK corresponding to scheduling information for the TRP in which the beam failure event occurred.

Optionally, in the embodiment of the present disclosure, the time origin of the predetermined time period is:
when the predetermined condition is satisfied, or
when a second predetermined time has passed after the predetermined condition is satisfied.

The terminal provided in the embodiment of the present disclosure can implement each process implemented by the terminal in the method embodiment of FIG. 2, which will not be repeated here to avoid duplication.

In summary, in the embodiments of the present disclosure, the network configures the terminal with N configuration information, each applied to a different TRP, so that the beam of each TRP in which a beam failure event occurs can be quickly restored. It can solve the problem of beam failure recovery in multi-TRP scenes.

It should be noted that the network-side equipment provided by the embodiments of the present disclosure is a network-side equipment capable of executing the beam failure handling method, and all the embodiments of the beam failure handling method are implemented in this network-side equipment. applied to achieve the same or similar effects.

Optionally, embodiments of the present disclosure further provide a network-side device, said network-side device comprising a processor, a memory, and a computer program stored in said memory and executable on said processor; Here, when the processor executes the computer program, each process of the beam failure handling method embodiment is realized. The network-side equipment can achieve the same technical effect and will not be repeated here to avoid duplication.

Embodiments of the present disclosure also provide a computer readable storage medium storing a computer program that, when executed by a processor, implements the various processes of the beam failure handling method embodiments described above, as well as The effect can be achieved and will not be repeated here to avoid duplication. Here, the computer-readable storage medium is ROM (Read-Only Memory), RAM (Random Access Memory), magnetic disk, optical disk, or the like.

It should be noted that, as used herein, the terms "include," "comprise," or any other variation thereof are intended to cover non-exclusive inclusion, thus processes, methods, including series of elements. , items, or apparatus may include those elements as well as other elements not expressly recited or specific to such processes, methods, items, or equipment. An element defined by the phrase "includes a", without further limitation, implies that additional identical elements are present in the process, method, article, or device that includes the element. Do not exclude.

From the description of the above embodiments, those skilled in the art can clearly understand that the method of the above examples can be achieved by adding the necessary general-purpose hardware platform to the software plus, of course, It can also be achieved through hardware alone, but in many cases the former is the better implementation. Based on this understanding, the technical means of the present disclosure can be embodied in the form of a computer software product, which essentially or contributes to the related art, and the computer software product includes (ROM/RAM, magnetic stored in a storage medium (such as a disk, optical disk, etc.) to cause a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the methods described in each embodiment of this disclosure. Contains some commands that are used.

Although the embodiments of the present disclosure have been described above with reference to the drawings, the present disclosure is not limited to the above specific embodiments, and the above specific embodiments are merely exemplary. , is not limiting, and many more forms can be made by those skilled in the art in the light of the present disclosure without departing from the spirit of the present disclosure and the scope of protection of the claims, all of which are within the scope of the present disclosure. Belongs within the scope of protection.

The above are only specific embodiments of the present disclosure, but the protection scope of the present disclosure is not limited thereto. , easily conceivable changes or replacements should be covered by the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be based on the protection scope of the above claims.

Claims (14)

A beam failure recovery method applied to a terminal, comprising:
obtaining N pieces of configuration information;
transmitting a beam failure recovery request based on the configuration information when determining that a beam failure event has occurred at at least one transmission reception point (TRP), wherein each of the N pieces of configuration information is applied to different transmit/receive points TRP, the configuration information includes parameters for beam failure recovery, N is an integer greater than 1;
If a beam failure event occurs at M transmitting/receiving points TRP, and the first resource for beam failure recovery request transmission by the terminal in the configuration information of the M transmitting/receiving points TRP is the same (M is greater than 1 is a large integer),
Transmitting a beam failure recovery request based on the configuration information includes:
transmitting a beam failure recovery request to a high-priority transmitting/receiving point TRP among the M transmitting/receiving points TRP where a beam failure event has occurred, according to the first resource in the configuration information of the M transmitting/receiving points TRP; including
The priority of the transmission/reception point TRP is
index information of the control resource set;
index information of the control resource set group;
Identifier information of the explicitly defined transmitting/receiving point TRP;
information on the transmission setting instruction state;
information on the transmission setting instruction status list;
information in the transmission setting indication state pool;
the information of the quasi-collocation QCL;
information of the quasi-collocation QCL group;
Spatial relationship information and
Spatial relationship group information and
Physical downlink control channel PDCCH scramble identifier information;
Physical downlink control channel PDCCH scrambling identifier group information;
Physical downlink shared channel PDSCH scramble identifier information;
Physical downlink shared channel PDSCH scrambling identifier group information;
information on the physical downlink control channel PDCCH setting signaling element;
Physical downlink shared channel PDSCH configuration signaling element information and at least one of
Beam failure recovery method. The different transmit and receive points TRP are
different control resource sets and
different control resource set groups and
different explicitly defined transmit and receive points TRP;
different transmission setting indication states;
a different transmission setting indication status list;
different transmission setting indication state pools;
different quasi-colocation QCLs (Quasi Co Location);
with different quasi-colocated QCL groups;
different spatial relationships and
different spatial relationship groups and
A different physical downlink control channel PDCCH (Physical Downlink Control Channel) scramble identifier;
different physical downlink control channel PDCCH scrambling identifier groups;
A different physical downlink shared channel PDSCH (Physical Downlink Shared Channel) scramble identifier;
different physical downlink shared channel PDSCH scrambling identifier groups;
different physical downlink control channel PDCCH configuration signaling elements;
2. The beam failure recovery method of claim 1, identified in at least one manner from different physical downlink shared channel PDSCH configuration signaling elements. The setting information is
a beam failure detection reference signal;
candidate beam reference signals;
a first resource for transmission of a beam failure recovery request by a terminal;
and a second resource for beam failure recovery request response transmission by the network side equipment. Configuration information for different transmission/reception points TRP is
different beam failure detection reference signals;
different candidate beam reference signals;
different first resources for beam failure recovery request transmission by terminals;
the first resource for beam failure recovery request transmission by the terminal is the same;
different second resources for transmission of beam failure recovery request responses by network-side devices;
The beam failure recovery method according to claim 3, satisfying at least one condition of: the second resource for beam failure recovery request response transmission by the network-side device is the same. Acquiring the N pieces of configuration information includes:
Acquiring the N pieces of setting information set in one bandwidth part BWP (Band Width Part) by the network-side device;
and/or
transmitting a beam failure recovery request based on said configuration information when a beam failure event occurs at the first transmitting/receiving point TRP;
transmitting a beam failure recovery request to the first transmission/reception point TRP based on a first resource for beam failure recovery request transmission by a terminal in configuration information corresponding to the first transmission/reception point TRP;
or
beam failure recovery by the terminal in configuration information corresponding to a second transmission/reception point TRP other than the first transmission/reception point TRP, such that the beam failure recovery request is forwarded to the first transmission/reception point TRP via the second transmission/reception point TRP; The beam failure recovery method according to claim 1, comprising transmitting a beam failure recovery request to said second transmit/receive point TRP based on a first resource for request transmission. If a beam failure event occurs at M transmission/reception points TRP, and the first resource for beam failure recovery request transmission by the terminal in the configuration information of the M transmission/reception points TRP is different (M is an integer greater than 1 is),
transmitting a beam failure recovery request based on said configuration information;
transmitting a beam failure recovery request to each of the M transmitting/receiving points TRP where a beam failure event occurs according to different first resources in the configuration information of the M transmitting/receiving points TRP ;
and /or
If a beam failure event occurs at M transmitting/receiving points TRP, and the second resource for beam failure recovery request response transmission by the network-side device in the configuration information of the M transmitting/receiving points TRP is the same (M is an integer greater than 1), and the beam failure recovery method includes:
further comprising receiving a beam failure recovery request response transmitted on a second resource in the configuration information from a high priority transmission/reception point TRP among the M transmission/reception points TRP where a beam failure event occurred. 2. The beam failure recovery method of claim 1. The second resource for beam failure recovery request response transmission by the network-side device in the configuration information is:
7. The beam failure recovery method of claim 6, comprising a control resource set CORESET-BFR for beam failure recovery. 2. The terminal further comprises transmitting the PUCCH using spatial relationship information of the PUCCH associated with a transmission/reception point TRP where a beam failure event occurs, in a predetermined time period, when a predetermined condition is met. The beam failure recovery method described in . The predetermined condition is
the terminal has received downlink information transmitted from a transmission/reception point TRP where a beam failure event occurred;
the terminal sending a beam failure recovery request to the transmission/reception point TRP where the beam failure event occurred;
The terminal transmits a beam failure recovery request to the transmitting/receiving point TRP where the beam failure event occurred, and receives downlink information transmitted from the transmitting/receiving point TRP where the beam failure event occurred within a first predetermined time period. is at least one of not
and/or
The time starting point of the predetermined time period is
when the predetermined condition is satisfied, or
when a second predetermined time has passed after the predetermined condition is satisfied;
and/or
using spatially related information of uplink channels for transmission of beam failure recovery requests in a given cell;
using spatial relationship information or quasi-colocation QCL information of a given channel in a given cell;
using spatial relationship information or quasi-colocation QCL information of a given reference signal in a given cell;
using spatial relationship information or quasi-colocation QCL information for a given channel in the primary cell; and
determining the spatial relationship information of the PUCCH associated with the transmit/receive point TRP where the beam failure event occurred, by one of using the spatial relationship information of the predetermined reference signal in the primary cell or the quasi-colocation QCL information;
9. The beam failure recovery method of claim 8. The terminal does not receive downlink information transmitted from the transmitting/receiving point TRP at which the beam failure event occurred within a third predetermined period after transmitting the beam failure recovery request to the transmitting/receiving point TRP at which the beam failure event occurred. and not transmitting PUCCH. The downlink information is
a physical downlink control channel PDCCH in the control resource set CORESET-BFR for beam failure recovery associated with the transmit/receive point TRP where the beam failure event occurred;
Downlink control information DCI (downlink control information);
A random access response RAR (random access response);
a release command or a deactivation command for releasing a cell in which a beam failure has occurred;
beam measurement and/or beam reporting trigger information for the transmit/receive point TRP where the beam failure event occurred;
channel state information (CSI) measurement and/or CSI reporting trigger information for a transmission/reception point TRP where a beam failure event has occurred;
Beam failure recovery method according to claim 9 or 10, comprising at least one of acknowledgment information ACK and/or negative acknowledgment NACK corresponding to scheduling information for the transmitting/receiving point TRP where the beam failure event occurred. A beam failure handling method applied to a network-side device, comprising:
Including setting N pieces of setting information in the terminal,
N pieces of configuration information each applied to a different transmit/receive point TRP, said configuration information including parameters for beam failure recovery, N being an integer greater than 1;
If a beam failure event occurs in M TRPs, and the first resource for beam failure recovery request transmission by the terminal in the configuration information of the M TRPs is the same (M is an integer greater than 1 Yes), the method is
A beam failure recovery request sent to a higher priority TRP among the M TRPs in which a beam failure event occurred, sent from the terminal on a first resource in the configuration information of the M TRPs. further comprising receiving a beam failure recovery request;
The priority of the transmission/reception point TRP is
index information of the control resource set;
index information of the control resource set group;
Identifier information of the explicitly defined transmitting/receiving point TRP;
information on the transmission setting instruction state;
information on the transmission setting instruction status list;
information in the transmission setting indication state pool;
the information of the quasi-collocation QCL;
information of the quasi-collocation QCL group;
Spatial relationship information and
Spatial relationship group information and
Physical downlink control channel PDCCH scramble identifier information;
Physical downlink control channel PDCCH scrambling identifier group information;
Physical downlink shared channel PDSCH scramble identifier information;
Physical downlink shared channel PDSCH scrambling identifier group information;
information on the physical downlink control channel PDCCH setting signaling element;
a beam failure handling method, identified based on at least one of information in a physical downlink shared channel PDSCH configuration signaling element. a terminal,
an acquisition module for acquiring N pieces of setting information;
a request transmission module for transmitting a beam failure recovery request based on the configuration information upon determining that a beam failure event has occurred at the at least one transmission/reception point TRP;
each of the N pieces of configuration information is applied to a different transmission/reception point transmission/reception point TRP, said configuration information including parameters for beam failure recovery, N being an integer greater than 1;
the request sending module,
If a beam failure event occurs in M TRPs, and the first resource for beam failure recovery request transmission by the terminal in the configuration information of the M TRPs is the same (M is an integer greater than 1 ), a second request transmission submodule for transmitting a beam failure recovery request to a high-priority TRP among the M TRPs in which a beam failure event has occurred, according to the first resource in the configuration information of the M TRPs; including
The priority of the transmission/reception point TRP is
index information of the control resource set;
index information of the control resource set group;
Identifier information of the explicitly defined transmitting/receiving point TRP;
information on the transmission setting instruction state;
information on the transmission setting instruction status list;
information in the transmission setting indication state pool;
the information of the quasi-collocation QCL;
information of the quasi-collocation QCL group;
Spatial relationship information and
Spatial relationship group information and
Physical downlink control channel PDCCH scramble identifier information;
Physical downlink control channel PDCCH scrambling identifier group information;
Physical downlink shared channel PDSCH scramble identifier information;
Physical downlink shared channel PDSCH scrambling identifier group information;
information on the physical downlink control channel PDCCH setting signaling element;
Physical downlink shared channel PDSCH configuration signaling element information and at least one of
terminal. A device on the network side,
a setting module for setting N pieces of setting information in the terminal,
N pieces of configuration information each applied to a different transmit/receive point TRP, said configuration information including parameters for beam failure recovery, N being an integer greater than 1;
The network-side device is
If a beam failure event occurs in M TRPs, and the first resource for beam failure recovery request transmission by the terminal in the configuration information of the M TRPs is the same (M is an integer greater than 1 Yes), a beam failure recovery request sent to a higher priority TRP among the M TRPs in which a beam failure event has occurred, from the terminal on the first resource in the configuration information of the M TRPs. further comprising a second receiving module for receiving the transmitted beam failure recovery request;
The priority of the transmission/reception point TRP is
index information of the control resource set;
index information of the control resource set group;
Identifier information of the explicitly defined transmitting/receiving point TRP;
information on the transmission setting instruction state;
information on the transmission setting instruction status list;
information in the transmission setting indication state pool;
the information of the quasi-collocation QCL;
information of the quasi-collocation QCL group;
Spatial relationship information and
Spatial relationship group information and
Physical downlink control channel PDCCH scramble identifier information;
Physical downlink control channel PDCCH scrambling identifier group information;
Physical downlink shared channel PDSCH scramble identifier information;
Physical downlink shared channel PDSCH scrambling identifier group information;
information on the physical downlink control channel PDCCH setting signaling element;
Physical downlink shared channel PDSCH configuration signaling element information and at least one of
Network side equipment.

Images