CN113271604B - Beam failure recovery method, terminal device, network device and storage medium - Google Patents

Beam failure recovery method, terminal device, network device and storage medium Download PDF

Info

Publication number
CN113271604B
CN113271604B CN202010095317.3A CN202010095317A CN113271604B CN 113271604 B CN113271604 B CN 113271604B CN 202010095317 A CN202010095317 A CN 202010095317A CN 113271604 B CN113271604 B CN 113271604B
Authority
CN
China
Prior art keywords
beam failure
failure recovery
terminal device
information
trp
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202010095317.3A
Other languages
Chinese (zh)
Other versions
CN113271604A (en
Inventor
张萌
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Spreadtrum Communications Shanghai Co Ltd
Original Assignee
Spreadtrum Communications Shanghai Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Spreadtrum Communications Shanghai Co Ltd filed Critical Spreadtrum Communications Shanghai Co Ltd
Priority to CN202010095317.3A priority Critical patent/CN113271604B/en
Priority to PCT/CN2021/075893 priority patent/WO2021160073A1/en
Publication of CN113271604A publication Critical patent/CN113271604A/en
Application granted granted Critical
Publication of CN113271604B publication Critical patent/CN113271604B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W16/00Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/24Cell structures
    • H04W16/28Cell structures using beam steering
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/08Testing, supervising or monitoring using real traffic
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation
    • H04W72/044Wireless resource allocation based on the type of the allocated resource
    • H04W72/046Wireless resource allocation based on the type of the allocated resource the resource being in the space domain, e.g. beams
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/50Allocation or scheduling criteria for wireless resources
    • H04W72/54Allocation or scheduling criteria for wireless resources based on quality criteria
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/50Allocation or scheduling criteria for wireless resources
    • H04W72/54Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/542Allocation or scheduling criteria for wireless resources based on quality criteria using measured or perceived quality
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/18Management of setup rejection or failure
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/19Connection re-establishment

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The embodiment of the application discloses a beam failure recovery method, a terminal device, a network device and a storage medium, wherein the network device is used for performing beam failure recovery management on the terminal device, the terminal device is configured with a plurality of signal Transmitting and Receiving Points (TRP), and the method applied to the terminal device comprises the following steps: detecting a beam failure event; determining whether the TRP with the beam failure meets the beam failure recovery condition or not according to the beam failure event; and if so, acquiring beam failure information and sending the beam failure information to the network equipment, wherein the beam failure information is used for reporting the beam failure event. In a multi-TRP scenario, the terminal device in the embodiment of the present application may implement beam failure recovery by determining whether a TRP in which a beam failure occurs satisfies a beam failure recovery condition, and sending beam failure information to the network device only when the TRP in which the beam failure occurs satisfies the beam failure recovery condition, so that the network device performs beam failure recovery management on the terminal device.

Description

Beam failure recovery method, terminal device, network device and storage medium
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method for recovering a beam failure, a terminal device, a network device, and a storage medium.
Background
In the fifth generation mobile communication technology (5) th Generation mobile communication technology, 5G), beam misalignment between a base station and a terminal device may occur due to severe channel fluctuation. The beam failure recovery can help the base station or the terminal device adjust the current failure beam to the available beam according to the beam measurement result, thereby avoiding frequent radio link failure caused by beam misalignment. At a terminal deviceUnder the scene of configuring a single signal transmitting-receiving Point (TRP), the beam failure recovery mainly includes the steps of beam failure detection, candidate beam identification, beam recovery request transmission, base station response, and the like.
Disclosure of Invention
The technical problem to be solved by the present application is how to implement beam failure recovery in a scenario where a terminal device is configured with a plurality of signal transceiving points.
In a first aspect, the present application provides a method for recovering a beam failure, which is applied to a terminal device, where the terminal device is configured with M signal transmission and reception points TRP, where M is an integer greater than or equal to 2, and the method includes:
the terminal device detects a beam failure event, wherein the beam failure event is used for indicating that TRP configured by the terminal device fails to generate a beam;
according to the wave beam failure event, the terminal equipment determines whether the TRP with the wave beam failure meets the wave beam failure recovery condition;
if so, the terminal equipment acquires beam failure information and sends the beam failure information to network equipment, wherein the beam failure information is used for reporting the beam failure event so that the network equipment performs beam failure recovery management on the terminal equipment.
In a multi-TRP scenario, the terminal device in the embodiment of the present application may implement beam failure recovery by determining whether a TRP in which a beam failure occurs satisfies a beam failure recovery condition, and sending beam failure information to the network device only when the TRP in which the beam failure occurs satisfies the beam failure recovery condition, so that the network device performs beam failure recovery management on the terminal device.
As an alternative embodiment, the beam failure recovery condition is that a beam failure occurs for a specified TRP; the determining, by the terminal device, whether the TRP where the beam failure occurs satisfies the beam failure recovery condition includes:
the terminal equipment judges whether the designated TRP generates beam failure or not;
and if so, the terminal equipment determines that the TRP with the beam failure meets the beam failure recovery condition.
As another alternative, the beam failure recovery condition is that a specified number of TRP beam failures occur; the terminal device determining whether the TRP with the beam failure meets the beam failure recovery condition comprises the following steps:
the terminal equipment determines the number of TRPs in which beam failure occurs;
when it is determined that a specified number of TRPs have beam failures, the terminal device determines whether the TRPs having beam failures satisfy a beam failure recovery condition.
As an optional implementation manner, after the network device receives the beam failure information from the terminal device, the method further includes:
according to the beam failure information, the network equipment determines a beam failure recovery mechanism adopted by the terminal equipment;
correspondingly, the network device acquiring the failure TRP identifier set corresponding to the beam failure information includes:
and according to the beam failure recovery mechanism, the network equipment acquires a failure TRP identifier set corresponding to the beam failure information.
As an optional implementation manner, before the terminal device sends the beam failure information to a network device, the method further includes:
the terminal equipment determines an adopted beam failure recovery mechanism;
correspondingly, the step of sending the beam failure information to the network device by the terminal device includes:
and according to the beam failure recovery mechanism, the terminal equipment sends the beam failure information to network equipment.
As an optional implementation manner, the beam failure recovery mechanism is a random access channel-based beam failure recovery mechanism RACH-based BFR, or a medium access control layer-based beam failure recovery mechanism MAC-CE-based BFR of a control unit.
In a second aspect, the present application provides a beam failure recovery method, which is applied to a network device, where the network device is configured to perform beam failure recovery management on a terminal device, and the terminal device is configured with M signal transmission and reception points TRP, where M is an integer greater than or equal to 2, and the method includes:
the network equipment receives beam failure information from the terminal equipment, wherein the beam failure information is used for indicating that partial or all TRPs in M TRPs configured by the terminal equipment have beam failure;
the network equipment acquires a failure signal transceiving point identifier set corresponding to the beam failure information, wherein the failure signal transceiving point identifier set comprises identifiers of TRPs (transmission power control points) with beam failure in the M TRPs;
and according to the acquired failure signal transceiving point identification set, the network equipment performs beam failure recovery management on the terminal equipment.
In a multi-signal transceiving point scenario, the network device in the embodiment of the present application may implement beam failure recovery by acquiring a failure TRP identifier set, and performing beam failure recovery management on the terminal device according to the failure TRP identifier set.
As an optional implementation manner, after the network device receives the beam failure information from the terminal device, the method further includes:
according to the beam failure information, the network equipment determines a beam failure recovery mechanism adopted by the terminal equipment;
correspondingly, the acquiring, by the network device, a failure signal transceiving point identifier set corresponding to the beam failure information includes:
and according to the beam failure recovery mechanism, the network equipment acquires a failure signal receiving and sending point identification set corresponding to the beam failure information.
As an optional implementation manner, the beam failure recovery mechanism is a random access channel-based beam failure recovery mechanism RACH-based BFR, or a medium access control layer-based beam failure recovery mechanism MAC-CE-based BFR of a control unit.
As an optional implementation, the beam failure recovery mechanism is RACH-based BFR; the beam failure information includes a random access channel preamble RACH preamble identifier, and the network device acquiring a failure TRP identifier set corresponding to the beam failure information includes:
and the network equipment acquires a failure TRP identifier set corresponding to the beam failure information according to the RACH preamble identifier and the corresponding relation between the TRP identifier and the RACH preamble identifier.
As another optional implementation, the beam failure recovery mechanism is RACH-based BFR; the beam failure information includes an RACH preamble identifier, and the network device acquiring a failure TRP identifier set corresponding to the beam failure information includes:
and according to the detected RACH occupancy information of the RACH preamble identifier and the corresponding relation between the TRP identifier and the RACH occupancy information, the network equipment acquires a failure TRP identifier set corresponding to the beam failure information.
As an optional implementation, the beam failure recovery mechanism is a MAC-CE based BFR; the beam failure information includes new beam information, and the network device acquiring a failure TRP identifier set corresponding to the beam failure information includes:
and according to the new beam information and the corresponding relation between the beam information and the TRP identifier, the network equipment determines a failure TRP identifier set corresponding to the beam failure information.
As another optional implementation, the beam failure recovery mechanism is a MAC-CE based BFR; the beam failure information includes a TRP identifier, and the network device acquiring a failure TRP identifier set corresponding to the beam failure information includes:
and according to the TRP identifier, the network equipment generates a failure TRP identifier set corresponding to the beam failure information.
In this embodiment, the receiving, by the network device, the beam failure information from the terminal device includes:
and the network equipment receives a Physical Uplink Shared Channel (PUSCH) from the terminal equipment, wherein the PUSCH carries the beam failure information.
As an optional implementation, the beam failure recovery mechanism is a MAC-CE based BFR; before the network device receives the beam failure information from the terminal device, the method further comprises:
the network equipment receives physical uplink control channel-beam failure recovery PUCCH-BFR information from the terminal equipment, wherein the PUCCH-BFR information comprises beam failure event indication and/or TRP identification;
correspondingly, the acquiring, by the network device, the failure TRP identifier set corresponding to the beam failure information includes:
and according to the TRP identifier, the network equipment generates a failure TRP identifier set corresponding to the beam failure information.
As an optional implementation, the PUCCH-BFR information includes a beam failure event indication and a scheduling request, and the scheduling request includes the TRP identifier.
In a third aspect, the present application provides a terminal device comprising means and means for performing the method of the first aspect and possible method embodiments of the first aspect. Specifically, the terminal device is configured with M signal transmission and reception points TRP, where M is an integer greater than or equal to 2. The network device includes:
a detection module, configured to detect a beam failure event, where the beam failure event is used to indicate that a TRP configured by the terminal device has a beam failure;
a determining module, configured to determine whether the TRP in which the beam failure occurs satisfies a beam failure recovery condition according to the beam failure event;
the device comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring beam failure information when the TRP which generates beam failure is determined to meet a beam failure recovery condition;
a sending module, configured to send the beam failure information to a network device, where the beam failure information is used to report the beam failure event, so that the network device performs beam failure recovery management on the terminal device.
As an alternative embodiment, the beam failure recovery condition is that a beam failure occurs for a specified TRP; the determining module comprises:
the judging unit is used for judging whether the designated TRP generates beam failure or not;
a first determination unit configured to determine that the TRP where the beam failure occurs satisfies a beam failure recovery condition when the TRP is designated for the beam failure.
As another alternative, the beam failure recovery condition is that a specified number of TRP occurrence beam failures; the determining module comprises:
a second determining unit for determining the number of TRPs where a beam failure occurs;
a third determination unit for determining whether the TRP having the beam failure satisfies a beam failure recovery condition when it is determined that the specified number of TRPs have the beam failure.
As an optional implementation manner, the determining module is further configured to:
determining an adopted beam failure recovery mechanism;
correspondingly, the sending module is specifically configured to:
and sending the beam failure information to network equipment according to the beam failure recovery mechanism.
As an optional implementation manner, the beam failure recovery mechanism is a random access channel-based beam failure recovery mechanism RACH-based BFR, or a media access control layer-based beam failure recovery mechanism MAC-CE-based BFR of a control unit.
Based on the same inventive concept, as the principle and the beneficial effects of the terminal device for solving the problems can refer to the method of the first aspect and each possible implementation manner of the first aspect and the beneficial effects brought thereby, the implementation of the terminal device can refer to the method of the first aspect and each possible implementation manner of the first aspect, and repeated details are omitted.
In a fourth aspect, the present application provides a network device comprising means for performing the method of the second aspect and possible method embodiments of the second aspect. Specifically, the network device is configured to perform beam failure recovery management on a terminal device, where the terminal device is configured with M signal transmission and reception points TRP, where M is an integer greater than or equal to 2. The network device includes:
a receiving module, configured to receive beam failure information from the terminal device, where the beam failure information is used to indicate that a beam failure occurs on part or all of M TRPs configured by the terminal device;
an obtaining module, configured to obtain a failure signal transceiving point identifier set corresponding to the beam failure information, where the failure signal transceiving point identifier set includes identifiers of TRPs in which beam failures occur in the M TRPs;
and the management module is used for carrying out beam failure recovery management on the terminal equipment according to the acquired failure signal transceiving point identification set.
As an optional implementation manner, the network device further includes:
a determining module, configured to determine, by the network device, a beam failure recovery mechanism adopted by the terminal device according to the beam failure information;
correspondingly, the obtaining module is specifically configured to:
and acquiring a failure signal receiving and transmitting point identification set corresponding to the beam failure information according to the beam failure recovery mechanism.
As an optional implementation manner, the beam failure recovery mechanism is a random access channel-based beam failure recovery mechanism RACH-based BFR, or a medium access control layer-based beam failure recovery mechanism MAC-CE-based BFR of a control unit.
As an optional implementation, the beam failure recovery mechanism is RACH-based BFR; the beam failure information includes a random access channel preamble RACH preamble identifier, and the acquiring module is specifically configured to:
and acquiring a failure TRP identifier set corresponding to the beam failure information according to the RACH preamble identifier and the corresponding relation between the TRP identifier and the RACH preamble identifier.
As another optional implementation, the beam failure recovery mechanism is RACH-based BFR; the beam failure information includes an RACH preamble identifier, and the acquiring module is specifically configured to:
and according to the detected RACH occupancy information of the RACH preamble identifier and the corresponding relation between the TRP identifier and the RACH occupancy information, the network equipment acquires a failure TRP identifier set corresponding to the beam failure information.
As an optional implementation, the beam failure recovery mechanism is a MAC-CE based BFR; the beam failure information includes new beam information, and the obtaining module is specifically configured to:
and acquiring a failure TRP identifier set corresponding to the beam failure information according to the new beam information and the corresponding relation between the beam information and the TRP identifier.
As an optional implementation, the beam failure recovery mechanism is a MAC-CE based BFR; the beam failure information includes a TRP identifier, and the acquisition module is specifically configured to:
and generating a failure TRP identifier set corresponding to the beam failure information according to the TRP identifier.
As an optional implementation manner, the receiving module is specifically configured to:
and receiving a Physical Uplink Shared Channel (PUSCH) from the terminal equipment, wherein the PUSCH carries the beam failure information.
As an optional implementation manner, the beam failure recovery mechanism is a MAC-CE based BFR; the receiving module is further configured to:
receiving physical uplink control channel-beam failure recovery PUCCH-BFR information from the terminal equipment, wherein the PUCCH-BFR information comprises beam failure event indication and/or TRP identification;
correspondingly, the obtaining module is specifically configured to:
and generating a failure TRP identifier set corresponding to the beam failure information according to the TRP identifier.
As an optional implementation, the PUCCH-BFR information includes a beam failure event indication and a scheduling request, and the scheduling request includes the TRP identifier.
Based on the same inventive concept, as the principle and the beneficial effects of the network device to solve the problem may refer to the second method and each possible implementation manner of the second aspect and the beneficial effects brought thereby, the implementation of the network device may refer to the second method and each possible implementation manner of the second aspect, and repeated details are not repeated.
In a fifth aspect, the present application provides a terminal device, including: a memory for storing one or more programs; the implementation and beneficial effects of the terminal device for solving the problems may refer to the method of the first aspect, each possible implementation and beneficial effects of the first aspect, and repeated parts are not described again.
In a sixth aspect, the present application provides a network device, including: a memory for storing one or more programs; for the implementation and the beneficial effects of the network device for solving the problems, reference may be made to the method of the second aspect, and each possible implementation and the beneficial effects of the second aspect, and repeated details are not described herein.
In a seventh aspect, the present application provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, where the computer program includes computer instructions, and when the computer instructions are executed by a processor, the processor is enabled to execute the method of the first aspect and each possible implementation manner of the first aspect and the beneficial effects brought by the first aspect, and repeated details are omitted here.
In an eighth aspect, the present application provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, where the computer program includes computer instructions, and when the computer instructions are executed by a processor, the processor is enabled to execute the method of the second aspect and each possible implementation manner and the advantageous effects of the second aspect, and repeated details are not repeated.
Drawings
Fig. 1 is a schematic flowchart of a method for recovering from beam failure according to an embodiment of the present application;
fig. 2 is a schematic flow chart of another beam failure recovery method according to an embodiment of the present application;
fig. 3 is a schematic flowchart of another beam failure recovery method according to an embodiment of the present application;
fig. 4 is a schematic flowchart of another beam failure recovery method according to an embodiment of the present application;
fig. 5 is a schematic flowchart of another beam failure recovery method according to an embodiment of the present application;
fig. 6 is a schematic frame diagram of a terminal device according to an embodiment of the present application;
fig. 7 is a schematic diagram of a framework of a network device according to an embodiment of the present application;
fig. 8 is a schematic frame diagram of another terminal device provided in an embodiment of the present application;
fig. 9 is a schematic diagram of a framework of another network device according to an embodiment of the present application.
Detailed Description
The embodiments of the present application will be described in detail below with reference to the drawings.
Referring to fig. 1, fig. 1 is a schematic flow chart of a beam failure recovery method according to an embodiment of the present application. The beam failure recovery method may be specifically applied to a terminal device, where the terminal device may be a Mobile phone (e.g., an Android Mobile phone, an iOS Mobile phone, etc.), a tablet computer, a desktop computer, a Mobile Internet Device (MID), a Personal Digital Assistant (PDA), and the like. The terminal device is configured with M signal transmitting-receiving points (TRPs), wherein M is an integer greater than or equal to 2. As shown in fig. 1, the beam failure recovery method includes the following steps:
s11, the terminal equipment detects a beam failure event.
In this embodiment of the present application, the beam failure event is used to indicate that a beam failure occurs to the TRP configured by the terminal device. Specifically, a TRP beam failure means that the number of consecutive simultaneous failures of the listening beam corresponding to the TRP reaches or exceeds a threshold.
And S12, according to the wave beam failure event, the terminal equipment determines whether the TRP with the wave beam failure meets the wave beam failure recovery condition.
In the embodiment of the present application, the beam failure recovery condition may be a specified TRP beam failure or a specified number of TRP beam failures.
As an optional implementation manner, when the beam failure recovery condition is that a beam failure occurs in a specified TRP, the determining, by the terminal device, whether the beam failure recovery condition is satisfied may specifically include: judging whether the designated TRP generates beam failure or not; and if so, the terminal equipment determines that the beam failure recovery condition is met.
Wherein the designated TRP may be a TRP having a designated identity, such as TRP-0. Alternatively, the designated TRP may be a TRP having a designated meaning, such as a TRP that configures Radio Resource Control (RRC) signaling for the terminal device.
Taking M =2, that is, the terminal device is configured with 2 TRPs, as an example, it is schematically illustrated that the terminal device determines whether the TRP where the beam failure occurs satisfies the beam failure recovery condition. The identifiers of the 2 TRPs are TRP-0 and TRP-1 respectively, wherein the TRP-0 can be a TRP configuring RRC signaling for the terminal equipment or the TRP-0 is a Primary TRP.
In a specific embodiment, the designated TRP may be the lowest numbered TRP or the highest numbered TRP.
In a specific embodiment, the terminal device may determine whether a beam failure occurs to the TRP identified as TRP-0; and if so, the terminal equipment determines that the beam failure recovery condition is met.
In another specific embodiment, the terminal device may determine whether a beam failure occurs to a TRP configuring an RRC signaling for the terminal device by determining whether the TRP includes TRP-0; and if so, the terminal equipment determines that the beam failure recovery condition is met. Optionally, in this embodiment, the terminal device may store in advance a correspondence between a terminal device identifier and an identifier of a TRP configuring an RRC signaling for the terminal device.
As another optional implementation manner, when the beam failure recovery condition is that a specified number of TRPs have beam failures, the determining, by the terminal device, whether the beam failure recovery condition is satisfied may specifically include: the terminal equipment determines the number of TRPs in which beam failure occurs; when it is determined that a specified number of TRPs have beam failure, the terminal device determines that a beam failure recovery condition is satisfied.
Wherein, the TRP with the specified number can be all TRPs (i.e. M TRPs) configured for the terminal device or at least L TRPs, L being a positive integer smaller than M.
Taking M =3, that is, the terminal device is configured with 3 TRPs as an example, how the terminal device determines whether the beam failure recovery condition is satisfied is schematically illustrated. Wherein the 3 TRPs are identified as TRP-0, TRP-1 and TRP2.
In a specific embodiment, the terminal device may determine whether a beam failure occurs in all of TRP-0, TRP-1, and TRP 2; if so, the terminal device may determine that a beam failure recovery condition is satisfied.
In another specific embodiment, the terminal device may determine whether at least 2 TRPs have failed in a beam; if so, the terminal device may determine that a beam failure recovery condition is satisfied.
And S13, when the TRP with the beam failure is determined to meet the beam failure recovery condition, the terminal equipment acquires the beam failure information and sends the beam failure information to the network equipment.
The beam failure information is used for reporting a beam failure event to the network device, so that the network device performs beam failure recovery management on the terminal device.
In this embodiment, the terminal device may send a beam failure recovery request to the network device. The network device performing beam failure recovery management on the terminal device may specifically include: and responding to the beam failure recovery request, and generating a beam failure recovery response by the network equipment and sending the beam failure recovery response to the terminal equipment.
In a Multi-signal transmit-receive point (M-TRP) scenario, a terminal device in an embodiment of the present application may implement beam failure recovery by determining whether a TRP where a beam failure occurs satisfies a beam failure recovery condition, and sending beam failure information to a network device only when the beam failure recovery condition is satisfied, so that the network device performs beam failure recovery management on the terminal device.
Referring to fig. 2, fig. 2 is a schematic flow chart of another beam failure recovery method according to an embodiment of the present application. The beam failure recovery method may be specifically applied to a network device, which may be a mobile communication base station, including but not limited to a macro base station, a micro base station, an omni station, and the like. The network device is used for performing beam failure recovery management on a terminal device, and the terminal device is configured with M TRPs, wherein M is an integer greater than or equal to 2. As shown in fig. 2, the beam failure recovery method includes the following steps:
and S21, the network equipment receives the beam failure information from the terminal equipment.
When a beam failure event is detected, the terminal device may transmit beam failure information to the network device. In this embodiment of the present application, the beam failure information is used to indicate a TRP beam failure configured by the terminal device, that is, one or N TRP beam failures occur in the M TRPs, where N is an integer greater than 1 and less than or equal to M.
And S22, the network equipment acquires a failure TRP identification set corresponding to the beam failure information.
In an embodiment of the present application, the set of failed TRP identities includes identities of TRPs of the M TRPs for which a beam failure occurs. Specifically, the identity of the TRP may be the TRP index.
And S23, according to the acquired failure TRP identifier set, the network equipment performs beam failure recovery management on the terminal equipment.
In this embodiment, the network device may further receive a beam failure recovery request from the terminal device. The performing, by the network device, beam failure recovery management on the terminal device may specifically include: and responding to the beam failure recovery request, and generating a beam failure recovery response by the network equipment and sending the beam failure recovery response to the terminal equipment.
In an M-TRP scenario, a network device in the embodiment of the present application may implement beam failure recovery by acquiring a failure TRP identifier set and performing beam failure recovery management on the terminal device according to the failure TRP identifier set.
The following method embodiments are used to illustrate how the beam failure recovery methods shown in fig. 1 and 2 can be applied to different beam failure recovery mechanisms.
Referring to fig. 3, fig. 3 is a flowchart illustrating another beam failure recovery method according to an embodiment of the present application. The beam failure recovery method can be specifically applied to network equipment. The communication network comprises network equipment and terminal equipment, wherein the network equipment is used for carrying out beam failure recovery management on the terminal equipment, and the terminal equipment is configured with M TRPs. Wherein M is an integer of 2 or more. As shown in fig. 3, the beam failure recovery method includes the following steps:
s31, the terminal device performs Beam Failure Detection (BFD) to detect a Beam failure event.
In the embodiment of the present application, the terminal device may first determine a BFD set of the TRP
Figure BDA0002384599030000091
The BFD set +>
Figure BDA0002384599030000092
Including the identity of a plurality of Reference Signals (RSs). On a single Bandwidth Part (BWP), one->
Figure BDA0002384599030000093
Up to 2 RS identities may be included. Alternatively, the terminal devices may be eachTRP independently configures respective BFD sets +>
Figure BDA0002384599030000094
If a certain TRP
Figure BDA0002384599030000095
The radio link quality corresponding to the identifiers of all the RSs (namely, the radio link quality of all the RSs) in the set is lower than a preset signal quality threshold Q out,LR It indicates that all beams of the TRP have failed at this time, and thus the physical layer transmits beam failure indication information to a higher layer. The radio link quality may specifically be a Block Error Rate (BLER), Q out,LR BLER thresholds, Q, that can be reused for Radio Link Monitoring (RLM) asynchronization out,LR A default value for the higher layer parameter RLM-IS-OOS-threshold config may be set.
In this embodiment of the present application, the physical layer may send the beam failure indication information to the higher layer periodically, and a value range of the sending period T is max [ a,2ms ]]. Wherein a is
Figure BDA0002384599030000096
The shortest period of the RS indicated by the identification in (1). It can be understood that the physical layer needs to transmit the beam failure indication information to the higher layer only when the beam failure occurs.
When receiving the beam failure indication information, the higher layer may record the number of times of beam failure of the TRP in the terminal device. If the number of times of the consecutive beam failures reaches the preset failure threshold, indicating that the TRP has a beam failure event, the terminal device may further execute step S32. The failure threshold may specifically be {1,2,3,4,5,6,8,10}.
As an optional implementation mode, the terminal equipment is configured with a high-level parameter of Beam-Failure-Detection-RS-ResourceConfig. In this embodiment, the RRC signaling configures a periodic Channel State information reference signal (Channel State information r) for the terminal device through a high-level parameter RadioLinkMonitoringRSInterference Signal, CSI-RS) set, which the terminal device may determine as a BFD set of TRPs
Figure BDA0002384599030000101
As another optional implementation way, the terminal equipment is not configured with a high-level parameter Beam-Failure-Detection-RS-ResourceConfig. In this embodiment, the UE determines, as a BFD Set of TRPs, RSs satisfying a Quasi-co-location (QCL) relationship from among RS sets in a Transmission Configuration Indication (TCI) state corresponding to a Control Resource Set (CORESET) of a Physical Downlink Control Channel (PDCCH) to be monitored
Figure BDA0002384599030000102
Wherein->
Figure BDA0002384599030000103
Including periodic CSI-RS resources and/or Synchronization Signal Blocks (SSBs).
In the embodiment of the present application,
Figure BDA0002384599030000104
the RS indicated by the identification in (1) supports only 1 antenna interface.
And S32, the terminal equipment identifies Candidate beams (Candidate beams).
In this embodiment, the terminal device may further determine a candidate beam set of the TRP
Figure BDA0002384599030000105
And will>
Figure BDA0002384599030000106
Associated with a proprietary non-contention based Physical Random Access Channel (PRACH) resource for Beam Failure Recovery (BFR). Optionally, the terminal device may configure a respective candidate beam set ÷ for each TRP independently>
Figure BDA0002384599030000107
Wherein the candidate beam set
Figure BDA0002384599030000108
Including the CSI-RS and/or SSB configured by RRC signaling through a high-layer parameter Candidate-Beam-RS-List.
When the number of times of beam failures continuously occurring on a certain TRP reaches a preset failure threshold, the MAC layer may request a candidate beam from the physical layer. When receiving the request, the physical layer may modify the TRP
Figure BDA0002384599030000109
The beam satisfying the condition of Layer 1-Reference Signal Received Power (L1-RSRP) is determined as a candidate beam and the identification (i.e., index) of the candidate beam is transmitted to the MAC Layer.
Further, the MAC layer may determine a new beam from the candidate beams.
Specifically, if the L1-RSRP of the CSI-RS is scaled by the value provided by the higher layer parameter Pc _ SS, the obtained power value is greater than Q in,LR If the CSI-RS meets the L1-RSRP condition; if the L1-RSRP of the SSB is larger than Q in,LR Then the SSB satisfies the L1-RSRP condition. Wherein Q is in,LR A default value for the high-level parameter Beam-failure-candidate-Beam-threshold may be set.
Optionally, when the number of times of continuous beam failures reaches a preset failure threshold, if the number of times of continuous beam failures reaches the preset failure threshold
Figure BDA00023845990300001010
If there are no beams satisfying the L1-RSRP condition, the terminal device may report to the network device that no candidate beam is found. />
And S33, determining the adopted beam failure recovery mechanism.
In the embodiment of the present application, the Beam failure Recovery mechanism is a Random Access Channel-based Beam-failure-Recovery (RACH-based BFR) mechanism.
S34, according to the Beam failure Recovery mechanism, the terminal equipment sends a Beam failure Recovery Request (BFRQ) to the network equipment.
When a beam failure event is detected and a new beam is determined, the terminal device sends a BFRQ to the network device. Specifically, according to the RACH-based BFR, the terminal device may send a BFRQ on a non-contention-based PRACH channel configured by RRC signaling through a higher layer parameter Beam-failure-recovery-request-RACH-Resource.
The BFRQ may include beam failure information indicating that some or all of the M TRPs configured by the terminal device have beam failure.
And S35, the network equipment acquires a failure TRP identification set corresponding to the beam failure information.
In this embodiment, the network device may acquire a failed TRP identifier set according to the beam failure information.
As an optional implementation, the beam failure information may include at least one Random Access Channel preamble (RACH preamble) identifier. According to the at least one RACH preamble identifier and the correspondence between the TRP identifiers and RACH preamble identifiers stored in advance, the network device may determine an identifier set formed by the TRP identifiers corresponding to the RACH preamble identifiers as a failed TRP identifier set corresponding to the beam failure information.
As another optional implementation, the beam failure information may include at least one RACH preamble identity. According to the detected Random Access Channel Access opportunity (RACH occupancy) information of the RACH preamble identifier and the correspondence between the pre-stored TRP identifiers and RACH occupancy information, the network device may determine an identifier set formed by the TRP identifiers corresponding to the RACH occupancy information as a failed TRP identifier set corresponding to the beam failure information.
As yet another alternative, the beam failure information may include at least one new beam information. The new beam information may be a new beam index. According to the at least one new beam information and the pre-stored correspondence between the TRP identifiers and the beam information, the network device may determine an identifier set formed by the TRP identifiers corresponding to each new beam information as a failed TRP identifier set corresponding to the beam failure information.
In the embodiment of the present application, the at least one new beam message may have a one-to-one correspondence relationship with the at least one RACH preamble identifier or the at least one RACH occasion information.
And S36, according to the acquired failure TRP identifier set, the network equipment performs beam failure recovery management on the terminal equipment.
In this embodiment, the performing, by the network device, beam failure recovery management on the terminal device may specifically include: and responding to the BFRQ, the network equipment generates a beam failure recovery response and sends the beam failure recovery response to the terminal equipment.
The RRC signaling configures a Search Space (Search Space-BFR) for the Beam Failure Recovery through a higher-layer parameter Recovery for the Beam Failure Recovery, and the terminal device may uniquely determine a Control Resource set (Control Resource for Beam Failure Recovery, core-BFR) for the Beam Failure Recovery through the Search Space to monitor the PDCCH. In the embodiment of the present application, the terminal device will assume that the CORESET and the new beam satisfy the same QCL relationship, the CORESET-BFR and the PDSCH scheduled by the CORESET-BFR also satisfy the same QCL relationship, and the CORESET-BFR and the Search Space-BFR have a one-to-one correspondence relationship.
After 4 timeslots for sending BFRQ, the terminal device starts listening for the network device's response to BFRQ within the time window (timewindow) configured by the higher layer parameter BeamFailureRecoveryConfig. When the terminal device successfully receives a response to its BFRQ from the network device within the time window, the beam failure recovery is successful. Specifically, the terminal device may receive the dedicated PDCCH scrambled with a Cell Radio Network Temporary Identifier (C-RNTI) by monitoring the CORESET-BFR.
Before receiving new TCI activation information from the network device, the terminal device will assume that its antenna port and the PDCCH being monitored satisfy the same QCL relationship for the reception of the Physical Downlink Shared Channel (PDSCH).
In addition, after receiving a Random Access Response (RAR) from the network device, the terminal device needs to continuously monitor core set-BFR until the terminal device receives TCI activated by MAC-CE or TCI-States-PDCCH configured by higher layer. Wherein, the TCI-StatesPDCCH comprises TCI-StatesPDCCH-ToAddList and/or TCI-StatesPDCCH-ToReleaseList.
When receiving the beam failure recovery response, the terminal device may transceive information on the new beam.
In an M-TRP scenario, a terminal device in an embodiment of the present application may implement beam failure recovery by determining whether a TRP in which a beam failure occurs satisfies a beam failure recovery condition, and sending beam failure information to a network device only when the beam failure recovery condition is satisfied, so that the network device performs beam failure recovery management on the terminal device.
Referring to fig. 4, fig. 4 is a schematic flowchart illustrating another beam failure recovery method according to an embodiment of the present application. The beam failure recovery method can be particularly applied to a communication network. The communication network comprises network equipment and terminal equipment, wherein the network equipment is used for carrying out beam failure recovery management on the terminal equipment, and the terminal equipment is configured with M TRPs. Wherein M is an integer of 2 or more. As shown in fig. 4, the beam failure recovery method includes the following steps:
s41, the terminal device monitors the Secondary Cell (SCell) Beam quality by measuring the radio link quality of the Beam failure detection Reference Signal (BFD RS) to detect a Beam failure event, and monitors a candidate Beam.
In the embodiment of the present application, each SCell needs to perform Beam Failure Detection (BFD), and each BWP of each SCell is configured with BFD parameters.
Specifically, the terminal device may first determine a BFD set of TRPs
Figure BDA0002384599030000121
The BFD set +>
Figure BDA0002384599030000122
Including the identity of the plurality of BFD RSs. Alternatively, the terminal device may be configured with a respective BFD set ≥ for each TRP independently>
Figure BDA0002384599030000123
Wherein the number of BFD RSs may be 2 or other values.
If a certain TRP
Figure BDA0002384599030000124
The radio link quality corresponding to the identification of all BFD RSs (namely, the radio link quality of all BFD RSs) is lower than a preset signal quality threshold Q out,LR It indicates that all beams of the TRP have failed at this time, and the physical layer transmits beam failure indication information to a higher layer. Wherein the radio link quality may specifically be BLER, Q out,LR A default value for the higher layer parameter RLM-IS-OOS-threshold config may be set.
In this embodiment of the present application, the terminal device is configured with a BFD RS, and a downlink RS for BFD is in a current Component Carrier (CC).
In other embodiments, no BFD RS is configured in the terminal device. In this case, the downlink RS for BFD may be in the current CC or in other CCs.
In this embodiment, the monitoring, by the terminal device, the candidate beams may specifically include: determining a set of candidate beams for a TRP
Figure BDA0002384599030000131
Wherein the candidate beam set +>
Figure BDA0002384599030000132
Including the CSI-RS and/or SSB configured by RRC signaling through a high-layer parameter Candidate-Beam-RS-List. Optionally, the terminal device may configure a respective candidate beam set ÷ for each TRP independently>
Figure BDA0002384599030000133
When the number of times of beam failures continuously occurring on a certain TRP reaches a preset failure threshold, the MAC layer may request a candidate beam from the physical layer. When receiving the request, the physical layer may modify the TRP
Figure BDA0002384599030000134
The beams in which the L1-RSRP condition is satisfied are determined as candidate beams and the identities (i.e., indices) of the candidate beams are sent to the MAC layer.
In the embodiment of the present application, up to 64 candidate beams may be configured in the terminal device. Further, the terminal device may also determine a new beam from the monitored candidate beams. The new beam may be an SSB or a CSI-RS for Beam Management (BM). And, the new beam may be in an active wideband portion within the current CC or other CCs of the same cell.
In the embodiment of the application, when the terminal equipment is configured with the SCell BFR, the new beam RS and its L1-RSRP are forced to be configured.
Optionally, when the number of times of continuous beam failures reaches a preset failure threshold, if the number reaches a preset failure threshold
Figure BDA0002384599030000135
If there are no beams satisfying the L1-RSRP condition, the terminal device may report to the network device that no candidate beam is found.
And S42, when the beam failure occurs, determining the adopted beam failure recovery mechanism.
When receiving the beam failure indication information, the higher layer may record the number of times of beam failure of the TRP in the terminal device. And if the frequency of the continuous beam failure reaches a preset failure threshold value, indicating that the TRP generates a beam failure event.
In this embodiment of the present application, the Beam failure Recovery mechanism is a MAC-CE based Beam-failure-Recovery (MAC-CE based BFR) based on a Control unit (MAC Control Element, MAC CE) of a Medium Access Control (MAC) layer.
S43, according to the Beam Failure recovery mechanism, the terminal device sends PUCCH-BFR (Physical Uplink Control Channel Beam Failure recovery) information to the network device.
Optionally, the PUCCH-BFR is sent only when the terminal device has no Uplink resource (e.g., physical Uplink Shared Channel (PUSCH) resource) to transmit the beam failure message.
The PUCCH-BFR is a PUCCH resource used for transmitting a Scheduling Request (SR), and the SR is used for acquiring an uplink transmission resource. In addition, TRP tags may be included in the SR. Meanwhile, the PUCCH-BFR can have a correlation relation with the beam failure event, and the network equipment can know that the beam failure event occurs after receiving the PUCCH-BFR.
In an embodiment of the present application, the PUCCH-BFR information may include a beam failure event indication.
In other embodiments, the terminal device is not configured with PUCCH-BFR. In this case, the terminal device may send a beam failure event indication to the network device in the scell using a Collision Based Random Access (CBRA). The sPCell includes a Primary Cell (PCell) and a Primary Secondary Cell (PScell).
S44, the network device sends uplink grant (UL-grant) information to the terminal device.
The UL-grant information may include uplink channel information, the uplink channel information may include an identifier of an uplink channel authorized to be used by the terminal device, and the terminal device may transmit a BFRQ on the uplink channel.
And S45, the terminal equipment sends BFRQ to the network equipment through the MAC-CE message.
Upon receiving the UL-grant information, the terminal device may transmit a BFRQ to the network device. The BFRQ may include beam failure information, which may include new beam information, among others.
Specifically, when determining a new beam, the terminal device may send the new beam index as new beam information to the network device.
And S46, the network equipment acquires a failure TRP identification set corresponding to the beam failure information.
As an optional implementation manner, the acquiring, by the network device, a failure TRP identifier set corresponding to the beam failure information may include: and determining a failed TRP identifier set corresponding to the beam failure information according to the new beam information and the corresponding relation between the beam information and the TRP identifier.
As another alternative, the beam failure information may also directly include at least one TRP identifier.
As yet another alternative embodiment, the PUCCH-BFR information may include at least one TRP identity. Specifically, the PUCCH-BFR information may include a TRP flag indicating a sequence number of the TRP where the beam failure occurs. Alternatively, the PUCCH-BFR information may include a plurality of TRP identities indicating sequence numbers of a plurality of TRPs in which a beam failure has occurred.
Optionally, a mapping relationship may exist between different TRP identifications and PUCCH-BFRs. One PUCCH-BFR uniquely corresponds to one TRP serial number or a plurality of TRP serial numbers. Thus, when receiving the PUCCH-BFR resource, the network device can know which TRP or TRPs have a beam failure event.
And S47, according to the acquired failed TRP identifier set, the network equipment performs beam failure recovery management on the terminal equipment.
In this embodiment, the performing, by the network device, beam failure recovery management on the terminal device may specifically include: and responding to the BFRQ, the network equipment generates a beam failure recovery response and sends the beam failure recovery response to the terminal equipment.
When receiving the beam failure recovery response, the terminal device may transceive information on the new beam.
The terminal device in the embodiment of the application may implement beam failure recovery by determining whether the TRP in which the beam failure occurs satisfies a beam failure recovery condition, and sending beam failure information to the network device only when the beam failure recovery condition is satisfied, so that the network device performs beam failure recovery management on the terminal device.
Referring to fig. 5, fig. 5 is a schematic flow chart of another beam failure recovery method according to an embodiment of the present application. The beam failure recovery method can be particularly applied to a communication network. The communication network comprises network equipment and terminal equipment, wherein the network equipment is used for carrying out beam failure recovery management on the terminal equipment, and the terminal equipment is configured with M TRPs. Wherein M is an integer of 2 or more. As shown in fig. 5, the method for recovering from beam failure includes the following steps:
and S51, the terminal equipment monitors the SCell beam quality by measuring the radio link quality of the BFD RS so as to detect a beam failure event, and monitors candidate beams.
In the embodiment of the application, each SCell needs to be BFD, and each BWP of each SCell is configured with BFD parameters.
Specifically, the terminal device may first determine a BFD set of TRPs
Figure BDA0002384599030000151
The BFD set +>
Figure BDA0002384599030000152
Including the identity of the plurality of BFD RSs. Alternatively, the terminal device can configure a respective BFD set &foreach TRP independently>
Figure BDA0002384599030000153
If a certain TRP
Figure BDA0002384599030000154
The radio link quality corresponding to the identification of all BFD RSs (namely, the radio link quality of all BFD RSs) is lower than a preset signal quality threshold Q out,LR It indicates that all beams of the TRP have failed at this time, and the physical layer transmits beam failure indication information to a higher layer.
In this embodiment, the monitoring, by the terminal device, the candidate beams may specifically include: determining a set of candidate beams for a TRP
Figure BDA0002384599030000155
Wherein the candidate beam set ≦>
Figure BDA0002384599030000156
Including the CSI-RS and/or SSB configured by RRC signaling through a high-layer parameter Candidate-Beam-RS-List. Optionally, the terminal device may configure a respective candidate beam set for each TRP independently
Figure BDA0002384599030000157
/>
When the number of consecutive beam failures reaches a preset failure threshold, the MAC layer may request a candidate beam from the physical layer. Upon receiving the request, the physical layer may send the request to the client
Figure BDA0002384599030000158
The beams in which the L1-RSRP condition is satisfied are determined as candidate beams and the identities (i.e., indices) of the candidate beams are sent to the MAC layer.
Further, the terminal device may also determine a new beam from the monitored candidate beams. Wherein the new beam may be an SSB or a CSI-RS for BM.
Optionally, when the number of times of continuous beam failures reaches a preset failure threshold, if the number of times of continuous beam failures reaches the preset failure threshold
Figure BDA0002384599030000159
If there are no beams satisfying the L1-RSRP condition, the terminal device may report to the network device that no candidate beam is found.
S52, when the beam failure occurs, determining the adopted beam failure recovery mechanism.
When receiving the beam failure indication information, the higher layer may record the number of times of beam failure of the TRP in the terminal device. And if the frequency of the continuous wave beam failure reaches a preset failure threshold value, indicating that the wave beam failure event occurs to the TRP.
In the embodiment of the present application, the beam failure recovery mechanism is MAC-CE based BFR.
In a specific embodiment, when the PUSCH resources can be scheduled, the terminal device may continue to perform step S53.
And S53, according to the beam failure recovery mechanism, the terminal equipment sends BFRQ to the network equipment on a PUSCH through a MAC-CE message.
As an alternative embodiment, the MAC-CE message sent by the terminal device may include a TRP sequence number where the beam failure occurs, or the MAC-CE may include a plurality of TRP sequence numbers where the beam failure occurs.
As another optional implementation, there may be a correspondence between the time-frequency resource used by the MAC-CE message sent by the terminal device and the TRP sequence number. After receiving the MAC-CE message, the network device can know which TRP or TRPs have failed in beam through the time-frequency resource carrying the MAC-CE.
In the embodiment of the present application, the BFRQ may include beam failure information, which may include new beam information.
Specifically, when determining a new beam, the terminal device may send the new beam index as new beam information to the network device.
And S54, the network equipment acquires a failure TRP identification set corresponding to the beam failure information.
As an optional implementation manner, the acquiring, by the network device, a failure TRP identifier set corresponding to the beam failure information may include: and determining a failed TRP identifier set corresponding to the beam failure information according to the new beam information and the corresponding relation between the beam information and the TRP identifiers.
As another alternative, the beam failure information may also directly include at least one TRP identifier.
And S55, according to the acquired failed TRP identifier set, the network equipment performs beam failure recovery management on the terminal equipment.
In this embodiment, the performing, by the network device, beam failure recovery management on the terminal device may specifically include: responding to BFRQ, the network device generates a beam failure recovery response and sends the beam failure recovery response to the terminal device.
When receiving the beam failure recovery response, the terminal device may transceive information on the new beam.
In an M-TRP scenario, a terminal device in an embodiment of the present application may implement beam failure recovery by determining whether a TRP in which a beam failure occurs satisfies a beam failure recovery condition, and sending beam failure information to a network device only when the TRP in which the beam failure occurs satisfies the beam failure recovery condition, so that the network device performs beam failure recovery management on the terminal device.
Referring to fig. 6, fig. 6 is a schematic frame diagram of a terminal device according to an embodiment of the present disclosure. The terminal device is configured with M TRPs. Wherein M is an integer of 2 or more. As shown in fig. 6, the terminal device 60 may include a detection module 61, a determination module 62, an acquisition module 63, and a transmission module 64.
The detecting module 61 is configured to detect a beam failure event. In this embodiment of the present application, the beam failure event is used to indicate that a beam failure occurs in a TRP configured by the terminal device.
A determining module 62, configured to determine whether the TRP where the beam failure occurs satisfies a beam failure recovery condition according to the beam failure event.
As an alternative embodiment, the beam failure recovery condition is that a beam failure occurs for a specified TRP; the determining module 62 may include:
a determining unit 621, configured to determine whether a beam failure occurs in the designated TRP;
a first determining unit 622, configured to determine that the TRP where the beam failure occurs satisfies the beam failure recovery condition when the TRP is designated for the beam failure.
As another alternative, the beam failure recovery condition is that a specified number of TRP occurrence beam failures; the determining module 62 may include:
a second determining unit 623 for determining the number of TRPs where beam failure occurs;
a third determining unit 624, configured to determine whether the TRP where the beam failure occurs satisfies the beam failure recovery condition when it is determined that the specified number of TRPs where the beam failure occurs.
An obtaining module 63, configured to obtain the beam failure information when it is determined that the TRP in which the beam failure occurs satisfies the beam failure recovery condition.
A sending module 64, configured to send the beam failure information to a network device. In this embodiment, the beam failure information is used to report the beam failure event, so that the network device performs beam failure recovery management on the terminal device.
As an optional implementation manner, the determining module 62 is further configured to determine a beam failure recovery mechanism to be used.
Correspondingly, the sending module 64 is specifically configured to send the beam failure information to the network device according to the beam failure recovery mechanism.
As an optional implementation manner, the beam failure recovery mechanism is a random access channel-based beam failure recovery mechanism RACH-based BFR, or a medium access control layer-based beam failure recovery mechanism MAC-CE-based BFR of a control unit.
Based on the same inventive concept, the principle and the beneficial effect of the terminal device 60 provided in the embodiment of the present application for solving the problem are similar to those of the embodiment of the beam failure recovery method shown in fig. 1 of the present application, so that the implementation of the terminal device 60 may refer to the implementation of the beam failure recovery method shown in fig. 1, and repeated details are not described again.
Referring to fig. 7, fig. 7 is a schematic diagram of a framework of a network device according to an embodiment of the present application. The network device is used for performing beam failure recovery management on the terminal device, and the terminal device is configured with M TRPs. Wherein M is an integer of 2 or more. As shown in fig. 7, the network device 70 may include a receiving module 71, an obtaining module 72, and a managing module 73.
A receiving module 71, configured to receive the beam failure information from the terminal device. In this embodiment of the present application, the beam failure information is used to indicate that a beam failure occurs on part or all of M TRPs configured by the terminal device;
an obtaining module 72, configured to obtain a failure signal transceiving point identifier set corresponding to the beam failure information. Wherein the set of failed signal transceiving point identities comprises identities of TRPs of the M TRPs where a beam failure occurs.
And the management module 73 is configured to perform beam failure recovery management on the terminal device according to the acquired failure signal transceiving point identifier set.
The network device 70 may further include:
a determining module 74, configured to determine, according to the beam failure information, a beam failure recovery mechanism adopted by the terminal device.
Correspondingly, the obtaining module 72 is specifically configured to, according to the beam failure recovery mechanism, obtain, by the network device, a failure signal transceiving point identifier set corresponding to the beam failure information.
As an optional implementation manner, the beam failure recovery mechanism is a random access channel-based beam failure recovery mechanism RACH-based BFR, or a medium access control layer-based beam failure recovery mechanism MAC-CE-based BFR of a control unit.
As an optional implementation, the beam failure recovery mechanism is RACH-based BFR; the beam failure information includes a random access channel preamble RACH preamble identifier, and the obtaining module 72 is specifically configured to obtain a failure TRP identifier set corresponding to the beam failure information according to the RACH preamble identifier and a corresponding relationship between the TRP identifier and the RACH preamble.
As another optional implementation, the beam failure recovery mechanism is RACH-based BFR; the beam failure information includes an RACH preamble identifier, and the obtaining module 72 is specifically configured to obtain a failed TRP identifier set corresponding to the beam failure information according to the RACH occupancy information detected by the RACH preamble identifier and a corresponding relationship between the TRP identifier and the RACH occupancy information.
As an optional implementation, the beam failure recovery mechanism is MAC-CE based BFR; the beam failure information includes new beam information, and the obtaining module 72 is specifically configured to obtain a failed TRP identifier set corresponding to the beam failure information according to the new beam information and a corresponding relationship between the beam information and the TRP identifier.
As another optional implementation, the beam failure recovery mechanism is a MAC-CE based BFR; the beam failure information includes a TRP identifier, and the obtaining module 72 is specifically configured to generate a set of failed TRP identifiers corresponding to the beam failure information according to the TRP identifier.
As an optional implementation manner, the receiving module 71 is specifically configured to receive a physical uplink shared channel PUSCH from the terminal device, where the PUSCH carries the beam failure information.
As an optional implementation manner, the receiving module 71 is further configured to receive physical uplink control channel-beam failure recovery PUCCH-BFR information from the terminal device. Wherein the PUCCH-BFR information comprises a beam failure event indication and/or a TRP identification.
Correspondingly, the obtaining module 72 is specifically configured to generate a failure TRP identifier set corresponding to the beam failure information according to the TRP identifier.
As an optional embodiment, the PUCCH-BFR information includes a beam failure event indication and a scheduling request, which includes the TRP identity.
Based on the same inventive concept, the principle and the beneficial effect of the network device 70 provided in the embodiment of the present application for solving the problem are similar to those of the embodiment of the beam failure recovery method shown in fig. 2 of the present application, so that the implementation of the network device 70 may refer to the implementation of the beam failure recovery method shown in fig. 2, and repeated details are not described again.
Referring to fig. 8, fig. 8 is a schematic frame diagram of another terminal device 80 according to an embodiment of the present disclosure. The terminal equipment is configured with M TRPs, wherein M is an integer greater than or equal to 2. As shown in fig. 8, the terminal device 80 may include: a bus 81, a processor 82, a memory 83, and an input/output interface 84. The bus 81 is used to connect the processor 82, the memory 83 and the input/output interface 84 to each other and to enable the above elements to communicate with each other. The memory 83 is used to store one or more computer programs comprising computer instructions. The input/output interface 84 is used to control communication connections between the terminal device 80 and other devices, such as network devices.
In particular, the processor 82 is configured to invoke the computer instructions to perform:
detecting a beam failure event, wherein the beam failure event is used for indicating that TRP configured by the terminal equipment has beam failure;
determining whether the TRP with the beam failure meets the beam failure recovery condition or not according to the beam failure event;
if so, acquiring beam failure information and sending the beam failure information to network equipment, wherein the beam failure information is used for reporting the beam failure event so that the network equipment performs beam failure recovery management on the terminal equipment.
As an alternative embodiment, the beam failure recovery condition is that a beam failure occurs for a specified TRP; the processor 82 is configured to invoke the computer instructions to perform the specific steps of determining whether a TRP in which a beam failure occurs satisfies a beam failure recovery condition:
judging whether the designated TRP generates beam failure or not;
and if so, determining that the TRP with the beam failure meets the beam failure recovery condition.
As another alternative, the beam failure recovery condition is that a specified number of TRP occurrence beam failures; the processor 82 is configured to invoke the computer instructions to perform the specific steps of determining whether a TRP in which a beam failure occurs satisfies a beam failure recovery condition:
determining the number of TRPs in which a beam failure occurs;
when it is determined that a specified number of TRPs have beam-failed, it is determined whether the TRP having beam-failed satisfies a beam failure recovery condition.
As an alternative embodiment, after the processor 82 is configured to invoke the computer instructions to execute receiving the beam failure information from the terminal device, the following is also executed:
determining a beam failure recovery mechanism adopted by the terminal equipment according to the beam failure information;
correspondingly, the processor 82 is configured to invoke the computer instruction to perform, when acquiring the failure TRP identifier set corresponding to the beam failure information, specifically:
and acquiring a failure TRP identifier set corresponding to the beam failure information according to the beam failure recovery mechanism.
As an alternative embodiment, before the processor 82 is configured to invoke the computer instructions to perform sending the beam failure information to the network device, the processor 82 is configured to invoke the computer instructions to further perform:
determining an adopted beam failure recovery mechanism;
correspondingly, the processor 82 is configured to invoke the computer instruction to execute when sending the beam failure information to the network device, specifically:
and sending the beam failure information to network equipment according to the beam failure recovery mechanism.
As an optional implementation manner, the beam failure recovery mechanism is a random access channel-based beam failure recovery mechanism RACH-based BFR, or a medium access control layer-based beam failure recovery mechanism MAC-CE-based BFR of a control unit.
The processor 82 may be a Central Processing Unit (CPU). The Memory 83 may be any type of Memory, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a nonvolatile Random Access Memory (RAM), and the like.
Based on the same inventive concept, the principle and the beneficial effect of the terminal device 80 provided in the embodiment of the present application for solving the problem are similar to those of the embodiment of the beam failure recovery method shown in fig. 1 of the present application, so that the implementation of the terminal device 80 may refer to the implementation of the beam failure recovery method shown in fig. 1, and repeated parts are not described again.
Referring to fig. 9, fig. 9 is a schematic diagram of a framework of another network device 90 according to an embodiment of the present application. The network device is used for performing beam failure recovery management on the terminal device, and the terminal device is configured with M TRPs. Wherein M is an integer of 2 or more. As shown in fig. 9, the network device 90 may include: bus 91, processor 92, memory 93, and input/output interface 94. The bus 91 is used for interconnecting the processor 92, the memory 93 and the input/output interface 94, and allowing the above elements to communicate with each other. The memory 93 is used to store one or more computer programs comprising computer instructions. The input/output interface 94 is used to control the communication connection between the network device 90 and other devices, such as terminal devices.
In particular, the processor 92 is configured to invoke the computer instructions to perform:
the network equipment receives beam failure information from the terminal equipment, wherein the beam failure information is used for indicating that partial or all TRPs in M TRPs configured by the terminal equipment have beam failure;
the network equipment acquires a failure signal transceiving point identifier set corresponding to the beam failure information, wherein the failure signal transceiving point identifier set comprises identifiers of TRPs (transmission power nodes) with beam failure in the M TRPs;
and according to the acquired failure signal transceiving point identification set, the network equipment performs beam failure recovery management on the terminal equipment.
As an alternative embodiment, after the processor 92 is configured to invoke the computer instructions to perform receiving the beam failure information from the terminal device, the processor 92 is configured to invoke the computer instructions to further perform:
according to the beam failure information, the network equipment determines a beam failure recovery mechanism adopted by the terminal equipment;
correspondingly, the processor 92 is configured to invoke the computer instruction to execute when acquiring the failure signal transceiver site identifier set corresponding to the beam failure information, specifically:
and acquiring a failure signal receiving and transmitting point identification set corresponding to the beam failure information according to the beam failure recovery mechanism.
As an optional implementation manner, the beam failure recovery mechanism is a random access channel-based beam failure recovery mechanism RACH-based BFR, or a medium access control layer-based beam failure recovery mechanism MAC-CE-based BFR of a control unit.
As an optional implementation, the beam failure recovery mechanism is RACH-based BFR; the beam failure information includes a random access channel preamble RACH preamble identifier, and the processor 92 is configured to specifically execute when invoking the computer instruction to execute obtaining a failure TRP identifier set corresponding to the beam failure information:
and acquiring a failure TRP identifier set corresponding to the beam failure information according to the RACH preamble identifier and the corresponding relation between the TRP identifier and the RACH preamble identifier.
As another optional implementation, the beam failure recovery mechanism is RACH-based BFR; the beam failure information includes a RACH preamble identifier, and the processor 92 is configured to invoke the computer instruction to perform the following specific operations when acquiring the failed TRP identifier set corresponding to the beam failure information:
and acquiring a failed TRP identifier set corresponding to the beam failure information according to the RACH occupancy information of the RACH preamble identifier and the corresponding relation between the TRP identifier and the RACH occupancy information.
As an optional implementation, the beam failure recovery mechanism is a MAC-CE based BFR; the beam failure information includes new beam information, and the processor 92 is configured to invoke the computer instruction to perform, when acquiring a failure TRP identifier set corresponding to the beam failure information, specifically:
and determining a failed TRP identifier set corresponding to the beam failure information according to the new beam information and the corresponding relation between the beam information and the TRP identifiers.
As another optional implementation, the beam failure recovery mechanism is a MAC-CE based BFR; the beam failure information includes a TRP identifier, and the processor 92 is configured to invoke the computer instruction to perform, when acquiring the failure TRP identifier set corresponding to the beam failure information, specifically:
and generating a failure TRP identifier set corresponding to the beam failure information according to the TRP identifier.
In this embodiment, the processor 92 is configured to invoke the computer instructions to perform the following steps when receiving the beam failure information from the terminal device:
and receiving a Physical Uplink Shared Channel (PUSCH) from the terminal equipment, wherein the PUSCH carries the beam failure information.
As an optional implementation, the beam failure recovery mechanism is a MAC-CE based BFR; before the processor 92 is configured to invoke the computer instructions to perform receiving the beam failure information from the terminal device, the processor 92 is configured to invoke the computer instructions to further perform:
receiving physical uplink control channel-beam failure recovery PUCCH-BFR information from the terminal equipment, wherein the PUCCH-BFR information comprises beam failure event indication and/or TRP identification;
correspondingly, the processor 92 is configured to invoke the computer instruction to perform, when acquiring the failure TRP identifier set corresponding to the beam failure information, specifically:
and generating a failure TRP identifier set corresponding to the beam failure information according to the TRP identifier.
As an optional implementation, the PUCCH-BFR information includes a beam failure event indication and a scheduling request, and the scheduling request includes the TRP identifier.
The processor 92 may be a CPU. The memory 93 may be any type of memory such as ROM, RAM, non-volatile random access memory, and the like.
Based on the same inventive concept, the principle and the beneficial effect of the network device 90 provided in the embodiment of the present application for solving the problem are similar to those of the embodiment of the beam failure recovery method shown in fig. 2 of the present application, so that the implementation of the network device 90 may refer to the implementation of the beam failure recovery method shown in fig. 2, and repeated details are not described again.

Claims (28)

1. A method for recovering beam failure is applied to a terminal device, wherein the terminal device is configured with M signal transmitting and receiving points TRP, M is an integer greater than or equal to 2, and the method comprises the following steps:
the terminal equipment detects a beam failure event, wherein the beam failure event represents that TRP configured by the terminal equipment fails to generate a beam;
the terminal equipment sends beam failure information to network equipment, wherein the beam failure information comprises at least one TRP mark and new beam information; the beam failure information is used for reporting the beam failure event so that the network equipment performs beam failure recovery management on the terminal equipment.
2. The method of claim 1, wherein the terminal device detects a beam failure event, comprising:
the terminal equipment detects a beam failure event according to the beam quality of an SCell (Secondary cell), wherein the beam quality of the SCell is determined by the wireless link quality of a beam failure detection reference signal BFD RS.
3. The method of claim 1, wherein the new beam is in an active wideband portion within a current Component Carrier (CC) or other CCs of the same cell.
4. The method of claim 1, wherein before the terminal device sends the beam failure information to a network device, the method further comprises:
the terminal equipment determines an adopted beam failure recovery mechanism;
correspondingly, the sending, by the terminal device, the beam failure information to the network device includes:
and according to the beam failure recovery mechanism, the terminal equipment sends the beam failure information to network equipment.
5. The method according to claim 4, wherein the beam failure recovery mechanism is a random access channel based beam failure recovery mechanism RACH-based BFR or a media access control layer based beam failure recovery mechanism MAC-CE based BFR of a control unit.
6. A beam failure recovery method is applied to a network device, the network device is configured to perform beam failure recovery management on a terminal device, the terminal device is configured with M signal transmitting and receiving points TRP, M is an integer greater than or equal to 2, and the method includes:
the network equipment receives beam failure information from the terminal equipment, wherein the beam failure information comprises at least one TRP mark and new beam information; the beam failure information is used for indicating that beam failure occurs to part or all TRPs in M TRPs configured by the terminal equipment;
the network equipment acquires a failure signal transceiving point identifier set corresponding to the beam failure information, wherein the failure signal transceiving point identifier set comprises the at least one TRP identifier;
and according to the acquired failure signal transceiving point identification set, the network equipment performs beam failure recovery management on the terminal equipment.
7. The method of claim 6, wherein after the network device receives the beam failure information from the terminal device, the method further comprises:
according to the beam failure information, the network equipment determines a beam failure recovery mechanism adopted by the terminal equipment;
correspondingly, the acquiring, by the network device, a failure signal transceiving point identifier set corresponding to the beam failure information includes:
and according to the beam failure recovery mechanism, the network equipment acquires a failure signal transceiving point identification set corresponding to the beam failure information.
8. The method according to claim 7, wherein the beam failure recovery mechanism is a random access channel based beam failure recovery mechanism RACH-based BFR or a media access control layer based beam failure recovery mechanism MAC-CE based BFR of a control unit.
9. The method of claim 8, wherein the network device receiving the beam failure information from the terminal device comprises:
and the network equipment receives a Physical Uplink Shared Channel (PUSCH) from the terminal equipment, wherein the PUSCH carries the beam failure information.
10. The method of claim 8, wherein the beam failure recovery mechanism is a MAC-CE based BFR; before the network device receives the beam failure information from the terminal device, the method further comprises:
and the network equipment receives physical uplink control channel-beam failure recovery PUCCH-BFR information from the terminal equipment, wherein the PUCCH-BFR information comprises beam failure event indication.
11. The method of claim 10, wherein the PUCCH-BFR information comprises a beam failure event indication and a scheduling request.
12. A terminal device, wherein the terminal device is configured with M signal transmission and reception points TRP, where M is an integer greater than or equal to 2, and the terminal device includes:
a detection module, configured to detect a beam failure event, where the beam failure event is used to indicate that a TRP configured by the terminal device has a beam failure;
a determining module, configured to determine whether the TRP in which the beam failure occurs satisfies a beam failure recovery condition according to the beam failure event;
a sending module, configured to send beam failure information to a network device, where the beam failure information includes at least one TRP identifier and new beam information; the beam failure information is used for reporting the beam failure event so that the network equipment performs beam failure recovery management on the terminal equipment.
13. A terminal device according to claim 12, wherein the detecting module is specifically configured to detect a beam failure event based on a secondary cell, SCell, beam quality, which is determined by a radio link quality of a beam failure sounding reference signal, BFD RS.
14. The terminal device of claim 12, wherein the new beam is in an active wideband portion within a current Component Carrier (CC) or other CC of the same cell.
15. The terminal device of claim 12, wherein the determining module is further configured to:
determining an adopted beam failure recovery mechanism;
correspondingly, the sending module is specifically configured to:
and sending the beam failure information to network equipment according to the beam failure recovery mechanism.
16. The terminal device of claim 15, wherein the beam failure recovery mechanism is a random access channel based beam failure recovery mechanism RACH-based BFR, or a media access control layer based beam failure recovery mechanism MAC-CE based BFR of a control unit.
17. A network device, configured to perform beam failure recovery management on a terminal device, where the terminal device is configured with M signal transmission and reception points TRP, where M is an integer greater than or equal to 2, and the network device includes:
a receiving module, configured to receive beam failure information from the terminal device, where the beam failure information includes at least one TRP identifier and new beam information; the beam failure information is used for indicating that beam failure occurs to part or all TRPs in M TRPs configured by the terminal equipment;
an obtaining module, configured to obtain a failure signal transceiver point identifier set corresponding to the beam failure information, where the failure signal transceiver point identifier set includes the at least one TRP identifier;
and the management module is used for carrying out beam failure recovery management on the terminal equipment according to the acquired failure signal transceiving point identification set.
18. The network device of claim 17, wherein the network device further comprises:
a determining module, configured to determine, by the network device, a beam failure recovery mechanism adopted by the terminal device according to the beam failure information;
correspondingly, the obtaining module is specifically configured to:
and acquiring a failure signal receiving and transmitting point identification set corresponding to the beam failure information according to the beam failure recovery mechanism.
19. The network device of claim 18, wherein the beam failure recovery mechanism is a random access channel based beam failure recovery mechanism RACH-based BFR, or a media access control layer based beam failure recovery mechanism MAC-CE based BFR of a control unit.
20. The network device of claim 19, wherein the receiving module is specifically configured to:
and receiving a Physical Uplink Shared Channel (PUSCH) from the terminal equipment, wherein the PUSCH carries the beam failure information.
21. The network device of claim 19, wherein the beam failure recovery mechanism is a MAC-CE based BFR; the receiving module is further configured to:
and receiving physical uplink control channel-beam failure recovery PUCCH-BFR information from the terminal equipment, wherein the PUCCH-BFR information comprises beam failure event indication.
22. The network device of claim 21, wherein the PUCCH-BFR information comprises a beam failure event indication and a scheduling request.
23. A terminal device, characterized in that it comprises means for performing the beam failure recovery method according to any of claims 1 to 5.
24. A network device comprising means for performing the beam failure recovery method of any of claims 6 to 11.
25. A terminal device, characterized in that the terminal device comprises a processor and a memory, the processor and the memory are connected with each other, wherein the processor executes computer instructions in the memory to implement the beam failure recovery method according to any one of claims 1 to 5.
26. A network device, characterized in that the network device comprises a processor and a memory, the processor and the memory being connected to each other, wherein the processor executes computer instructions in the memory to implement the beam failure recovery method according to any one of claims 6 to 11.
27. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program comprising program instructions that, when executed by a processor, cause the processor to carry out the beam failure recovery method according to any one of claims 1 to 5.
28. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program comprising program instructions which, when executed by a processor, cause the processor to carry out the beam failure recovery method according to any one of claims 6 to 11.
CN202010095317.3A 2020-02-14 2020-02-14 Beam failure recovery method, terminal device, network device and storage medium Active CN113271604B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202010095317.3A CN113271604B (en) 2020-02-14 2020-02-14 Beam failure recovery method, terminal device, network device and storage medium
PCT/CN2021/075893 WO2021160073A1 (en) 2020-02-14 2021-02-07 Beam failure recovery method, storage medium, chip and related devices

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010095317.3A CN113271604B (en) 2020-02-14 2020-02-14 Beam failure recovery method, terminal device, network device and storage medium

Publications (2)

Publication Number Publication Date
CN113271604A CN113271604A (en) 2021-08-17
CN113271604B true CN113271604B (en) 2023-03-24

Family

ID=77227374

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010095317.3A Active CN113271604B (en) 2020-02-14 2020-02-14 Beam failure recovery method, terminal device, network device and storage medium

Country Status (2)

Country Link
CN (1) CN113271604B (en)
WO (1) WO2021160073A1 (en)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117413610A (en) * 2021-09-15 2024-01-16 Oppo广东移动通信有限公司 Wireless communication method and device, terminal equipment and network equipment
WO2023044827A1 (en) * 2021-09-24 2023-03-30 Nokia Shanghai Bell Co., Ltd. Transceiver point beam failure recovery
WO2023060485A1 (en) * 2021-10-13 2023-04-20 Huawei Technologies Co.,Ltd. Joint beam management in integrated terrestrial/non-terrestrial networks
CN115996416A (en) * 2021-10-18 2023-04-21 夏普株式会社 User equipment method and user equipment
CN115996394A (en) * 2021-10-20 2023-04-21 华为技术有限公司 Beam failure recovery method and communication device
CN117643162A (en) * 2021-10-21 2024-03-01 Oppo广东移动通信有限公司 Beam failure recovery method and device and terminal equipment
CN116156629A (en) * 2021-11-17 2023-05-23 华为技术有限公司 Beam recovery method, beam failure detection method and related device
CN116847388A (en) * 2022-03-23 2023-10-03 维沃移动通信有限公司 Beam failure detection method, device, terminal and storage medium
CN115835265B (en) * 2023-02-10 2023-04-25 广东奎晟信息科技有限公司 Beam fault recovery method and device, computer equipment, medium and product

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110226340A (en) * 2019-04-25 2019-09-10 北京小米移动软件有限公司 Report method, device and the storage medium of wave beam failure
CN110324069A (en) * 2018-03-28 2019-10-11 维沃移动通信有限公司 Wave beam fail processing method, terminal and the network equipment
CN110545580A (en) * 2018-05-28 2019-12-06 华为技术有限公司 Resource allocation method, device and system
WO2020010630A1 (en) * 2018-07-13 2020-01-16 Nec Corporation Beam failure recovery

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111587556B (en) * 2018-01-12 2023-12-29 株式会社Ntt都科摩 User device and wireless communication method
CN116017698A (en) * 2019-04-10 2023-04-25 北京小米移动软件有限公司 Beam failure determination method and device
CN110463264B (en) * 2019-06-17 2021-10-08 北京小米移动软件有限公司 Random access indication method, device and storage medium

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110324069A (en) * 2018-03-28 2019-10-11 维沃移动通信有限公司 Wave beam fail processing method, terminal and the network equipment
CN110545580A (en) * 2018-05-28 2019-12-06 华为技术有限公司 Resource allocation method, device and system
WO2020010630A1 (en) * 2018-07-13 2020-01-16 Nec Corporation Beam failure recovery
CN110226340A (en) * 2019-04-25 2019-09-10 北京小米移动软件有限公司 Report method, device and the storage medium of wave beam failure

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"On Beam Recovery for Partial and Full Control Channel Failure";AT&T;《3GPP tsg_ran\WG1 Meeting NR#3 R1-1716169 》;20170921;正文第1页以及正文第二部分 *
"Remaining issues on beam management enhancements in Rel.16";CATT;《3GPP tsg_ran\wg1 #98bis R1-1910350》;20191005;全文 *

Also Published As

Publication number Publication date
CN113271604A (en) 2021-08-17
WO2021160073A1 (en) 2021-08-19

Similar Documents

Publication Publication Date Title
CN113271604B (en) Beam failure recovery method, terminal device, network device and storage medium
US10743321B2 (en) Default beam for uplink transmission after beam failure recovery
TWI678895B (en) Beam failure recovery methods and user equipment for multi-beam operation
US11949485B2 (en) Secondary cell beam recovery
US10779171B2 (en) Downlink spatial transmission and spatial reception mechanism in multi-beam operation
AU2018407973B2 (en) System and method for periodic beam failure measurements
CN110754106B (en) Wireless link monitoring method and device
US11349547B2 (en) Resource allocation for beam failure recovery procedure
WO2018068724A1 (en) Communication method, apparatus and system
WO2019137346A1 (en) Method and terminal device for monitoring channel quality
JP7459217B2 (en) Link recovery in wireless communications
JPWO2019215381A5 (en)
US11902814B2 (en) Control information transmission method and apparatus
CN116326039A (en) UE operation for beam management in multi-TRP operation
CN116325852A (en) Beam management in multi-TRP operation
CN115669038A (en) Beam management method, device, equipment and storage medium
US20240072878A1 (en) Method and apparatus for beam failure recovery
US20230090317A1 (en) Method and Apparatus for Beam Failure Recovery
CN115334557A (en) Beam failure recovery method, device and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant