CN111418164B

CN111418164B - Method and apparatus for beam failure recovery in a wireless communication system

Info

Publication number: CN111418164B
Application number: CN201880077264.3A
Authority: CN
Inventors: 亚里·加可·伊索坎加斯; 杨宁; 石聪
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2017-12-28
Filing date: 2018-12-25
Publication date: 2022-12-20
Anticipated expiration: 2038-12-25
Also published as: WO2019128975A1; CN111418164A

Abstract

Methods and apparatus are provided for beam failure recovery in a wireless communication system. The method for beam failure recovery of a network node comprises: determining M beam groups, where M is an integer equal to or greater than 2, where each of the M beam groups includes a plurality of beams); and allocating M resource configurations to the M beam groups, wherein a same resource configuration of the M resource configurations is allocated to a plurality of beams in a same beam group of the M beam groups.

Description

Method and apparatus for beam failure recovery in a wireless communication system

Background of the disclosure

1. Field of disclosure

The present disclosure relates to the field of communication systems, and more particularly, to methods and apparatus for beam failure recovery in a wireless communication system.

2. Description of the related Art

It has been agreed in the third generation partnership project (3 GPP) that in new air interface (NR) systems (e.g., 5G), beam management and mobility between beams may occur without Radio Resource Control (RRC) involvement. That is, changes in the serving beam or group of beams may be handled by lower protocol layers to avoid RRC level signaling between the User Equipment (UE) and the Network (NW). In case of beam failure (e.g., the UE can no longer receive Downlink (DL) beams), it has been agreed in RAN1#89 and RAN1#90 to use a non-contention random access (CFRA) procedure to carry the Beam Failure Recovery Request (BFRR) message from the UE to the NW.

The possibility of using PUCCH Scheduling Request (SR) and potential Contention Based Random Access (CBRA) in case dedicated Uplink (UL) resources cannot be used for CFRA or Physical Uplink Control Channel (PUCCH) transmission BFRR is also discussed. However, when it is required to uniquely identify a UE during a beam recovery procedure, the use of CFRA with dedicated Physical Random Access Channel (PRACH) or PUCCH resources is clearly a preferred solution, and in case neither dedicated resource is available, CBRA may be included as a backup solution.

In order to perform beam recovery using CFRA or PUCCH, the UE needs to be configured with resources in advance. In the PUCCH case, the problem is not serious if a beam failure occurs while the UE is in RRC connected mode, in which case PUCCH resources are typically configured. In the case of CBRA, for initial access, the UE may use the same PRACH configuration as any other CBRA-based access, i.e., no additional resources need to be allocated in preparation for potential beam failure recovery. However, when PUCCH resources are generally configured only for a serving beam, since the number of PUCCH resources reserved per UE is limited, there is a limit in using PUCCH for beam recovery.

When CFRA is used for this purpose, dedicated RACH resources (frequency/time/preamble sequences per beam identified by channel state information reference signals (CSI-RS) or SS blocks (SSBs)) need to be allocated to each candidate beam that the UE may use to transmit BFRR messages. In NR (5G), one cell may be composed of several transmission points (TRPs), and each TRP may be served by several tens of beams, i.e., the number of candidate beams per UE may be quite high, and very inefficient RACH resource utilization results in case all beams belonging to a particular cell are identified as candidate beams (i.e., beams that the UE can use for transmission/reception within one cell). From the perspective of RACH resource allocation and efficiency, a more efficient solution is to keep the beam set to which the RACH is allocated as small as possible. However, when the dedicated RACH configuration is delivered to the UE using RRC signaling, frequent configuration updates will significantly increase the load of RRC signaling and will create additional delay compared to lower layer management/signaling mechanisms.

There is a need to provide new technical solutions for methods and apparatus for beam failure recovery in a wireless communication system.

SUMMARY

An object of the present disclosure is to propose a method and apparatus for beam failure recovery in a wireless communication system.

In a first aspect of the disclosure, a network node for beam failure recovery in a wireless communication system includes a memory, a transceiver, and a processor coupled to the memory and the transceiver. The processor is configured to determine M beam groups, where M is an integer equal to or greater than 2, where each of the M beam groups includes a plurality of beams, and to allocate M resource configurations to the M beam groups, where a same one of the M resource configurations is allocated to a plurality of beams in a same one of the M beam groups.

In a second aspect of the disclosure, a method for beam failure recovery of a network node comprises: determining M beam groups, where M is an integer equal to or greater than 2, where each of the M beam groups comprises a plurality of beams; and allocating M resource configurations to the M beam groups, wherein a same resource configuration of the M resource configurations is allocated to a plurality of beams in a same beam group of the M beam groups.

In a third aspect of the disclosure, a user equipment of a plurality of user equipments for beam failure recovery in a wireless communication system includes a memory, a transceiver, and a processor coupled to the memory and the transceiver. The processor is configured to determine M beam groups, where M is an integer equal to or greater than 2, where each of the M beam groups comprises a plurality of beams, and to control the transceiver to receive, from the network node, M resource configurations allocated to the M beam groups, where a same one of the M resource configurations is allocated to a plurality of beams in a same one of the M beam groups.

In a fourth aspect of the present disclosure, a method of beam failure recovery performed by a user equipment of a plurality of user equipments comprises: the method comprises determining M beam groups, where M is an integer equal to or greater than 2, where each beam group of the M beam groups comprises a plurality of beams, and receiving M resource configurations allocated to the M beam groups from a network node, where a same resource configuration of the M resource configurations is allocated to a plurality of beams in a same beam group of the M beam groups.

In a fifth aspect of the disclosure, a non-transitory machine-readable storage medium has stored thereon instructions which, when executed by a computer, cause the computer to perform the above-described method.

In a sixth aspect of the disclosure, a network node comprises a processor and a memory configured to store a computer program. The processor is configured to execute a computer program stored in the memory to perform the above-described method.

In a seventh aspect of the disclosure, a terminal device includes a processor and a memory configured to store a computer program. The processor is configured to execute a computer program stored in the memory to perform the above-described method.

Drawings

In order to more clearly illustrate embodiments of the present disclosure or related art, the following drawings, which will be described in the embodiments, are briefly introduced. It is apparent that the drawings are only some embodiments of the disclosure and that other drawings can be derived by one of ordinary skill in the art without setting a premise.

Fig. 1 is a block diagram of a user equipment and a network node for beam failure recovery in a wireless communication system according to an embodiment of the disclosure.

Fig. 2 is a flow chart illustrating a method for beam failure recovery of a network node according to an embodiment of the present disclosure.

Fig. 3 is a flowchart illustrating a method of beam failure recovery performed by a user equipment of a plurality of user equipments according to an embodiment of the present disclosure.

Fig. 4 is a block diagram of a wireless communication system in accordance with an embodiment of the present disclosure.

Detailed description of the embodiments

Embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings by technical subject matter, structural features, and objects and effects achieved. In particular, the terminology in the embodiments of the present disclosure is for the purpose of describing certain embodiments only and is not intended to be limiting of the present disclosure.

Fig. 1 illustrates, in some embodiments, a User Equipment (UE) 10 and a network node 20 for beam failure recovery in a wireless communication system according to embodiments of the present disclosure are provided. The UE 10 may include a processor 11, a memory 12, and a transceiver 13. The network node 20 may comprise a processor 21, a memory 22 and a transceiver 23. The

processor

11 or 21 may be configured to implement the proposed functions, processes and/or methods described in this specification. The various layers of the air interface protocol may be implemented in the

processor

11 or 21. The memory 12 or 22 is operatively coupled with the

processor

11 or 21 and stores various information to operate the

processor

11 or 21. The

transceiver

13 or 23 is operatively coupled with the

processor

11 or 21, and the

transceiver

13 or 23 transmits and/or receives radio signals.

The

processor

11 or 21 may comprise an Application Specific Integrated Circuit (ASIC), other chipset, logic circuit and/or data processing device. The memory 12 or 22 may include Read Only Memory (ROM), random Access Memory (RAM), flash memory, memory cards, storage media, and/or other storage devices. The

transceiver

13 or 23 may include a baseband circuit to process radio frequency signals. When an embodiment is implemented in software, the techniques described herein may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. These modules may be stored in memory 12 or 22 and executed by

processor

11 or 21. The memory 12 or 22 may be implemented within the

processor

11 or 21 or external to the

processor

11 or 21, in which case the memory 12 or 22 may be communicatively coupled to the

processor

11 or 21 via various means as is known in the art.

According to sidelink (sidelink) technology developed under third generation partnership project (3 GPP) new air interface (NR) release 16 and beyond, communication between UEs involves vehicle-to-anything (V2X) communication, including vehicle-to-vehicle (V2V), vehicle-to-pedestrian (V2P), and vehicle-to-infrastructure/network (V2I/N). The UEs communicate directly with each other via a sidelink interface (e.g., PC5 interface).

In some embodiments, the processor 21 is configured to determine M beam groups, where M is an integer equal to or greater than 2, wherein each of the M beam groups comprises a plurality of beams, and the processor 21 is configured to allocate M resource configurations to the M beam groups, wherein a same one of the M resource configurations is allocated to a plurality of beams in a same one of the M beam groups.

In some embodiments, the processor 11 is configured to determine M beam groups, where M is an integer equal to or greater than 2, wherein each of the M beam groups comprises a plurality of beams, and the processor 11 is configured to control the transceiver 13 to receive M resource configurations allocated to the M beam groups from the network node 20, wherein a same one of the M resource configurations is allocated to a plurality of beams in a same one of the M beam groups.

Fig. 2 illustrates a method 200 for beam failure recovery of the network node 20 according to an embodiment of the present disclosure. Method 200 includes block 202 and block 204: at block 202, M beam groups are determined, where M is an integer equal to or greater than 2, where each of the M beam groups includes a plurality of beams, and at block 204, M resource configurations are allocated to the M beam groups, where a same one of the M resource configurations is allocated to a plurality of beams in a same one of the M beam groups.

Fig. 3 is a flow chart illustrating a method 300 of beam failure recovery performed by a user equipment 10 of a plurality of user equipments according to an embodiment of the present disclosure. The method 300 includes blocks 302 and 304: at block 302, M beam groups are determined, where M is an integer equal to or greater than 2, where each beam group of the M beam groups comprises a plurality of beams, and at block 304, M resource configurations allocated to the M beam groups are received from the network node 20, where a same resource configuration of the M resource configurations is allocated to a plurality of beams in a same beam group of the M beam groups.

In some embodiments, each of the M resource configurations comprises a scheduling free (GF) Physical Uplink Shared Channel (PUSCH) resource configuration. The GF PUSCH resource configuration includes a plurality of time resources, a plurality of frequency resources, and/or a plurality of demodulation reference signal (DMRS) sequences. The same GF PUSCH resource configuration allocated to multiple beams in the same beam group of the M beam groups is configured to send a Beam Failure Recovery Request (BFRR). One or several of the plurality of DMRS sequences are configured to be used with a dedicated GF PUSCH resource configuration of the M resource configurations and are coupled to a certain beam group of the M beam groups.

In some embodiments, the processor 21 is configured to allocate the same DMRS sequence among the plurality of DMRS sequences to the plurality of user equipments, and the processor 21 is configured to distinguish the plurality of user equipments using a packet payload or a medium access control element (MAC CE) with a cell radio network temporary identity (C-RNTI).

In particular, the transceiver 23 is configured to transmit to the plurality of user equipments the same GF PUSCH resource configuration allocated to a plurality of beams in the same beam group of the M beam groups, the same GF PUSCH resource configuration being configured to transmit BFRR by dedicated or common signaling.

In some embodiments, a dedicated GF PUSCH resource configuration of the M resource configurations is preconfigured from the transceiver 23 to the plurality of user equipments, and the processor 21 is configured to activate a particular beam group of the M beam groups having the dedicated GF PUSCH resource configuration using a list or bitmap. In particular, the transceiver 23 is configured to send the list or bitmap to a plurality of user equipments through dedicated or common signaling.

In some embodiments, the transceiver 13 is configured to receive from the network node 20 the same DMRS sequence of the plurality of DMRS sequences allocated to the plurality of user devices. In particular, the transceiver 13 is configured to receive from the network node 20 the same GF PUSCH resource configuration allocated to a plurality of beams in the same beam group of the M beam groups, the GF PUSCH resource configuration being configured to transmit BFRRs by dedicated or common signaling.

Furthermore, in some embodiments, the transceiver 13 is configured to receive from the network node 20 a dedicated GF PUSCH resource configuration of the M resource configurations preconfigured to the plurality of user equipments. In particular, the transceiver 13 is configured to receive a list or bitmap from the network node 20 to a plurality of user equipments through dedicated or common signaling.

To be able to efficiently carry beam failure recovery requests with a scheduling free (GF) Physical Uplink Shared Channel (PUSCH), an enhanced GF PUSCH solution is needed to support multi-beam deployment scenarios. One simple solution is to allocate time/frequency/demodulation reference signal (DMRS) sequence resources in the same way as a cell (single beam) level solution, i.e. each beam is allocated separate resources. However, due to the mobility of the UE, this solution either results in a huge profile or very frequent configuration updates.

In some embodiments, to reduce the size of the profile or frequent UE reconfiguration (if smaller beam groups with assigned GF PUSCH are used), and to reduce the amount of radio resources needed for GF PUSCH purposes, the same time/frequency resources and DMRS sequences may be configured to all beams or a set of beams in a cell. When the same time/frequency resource allocation can be used over several beams, using dedicated DMRS sequences to distinguish UEs can limit the maximum number of supported UEs. Since the number of possible DMRS sequences within certain physical resources is limited, the solution is enhanced so that several UEs may share the same DMRS sequence. Since each UE has a unique C-RNTI in RRC connected mode, this can be used to distinguish individual UEs on the network side, and the UE C-RNTI may be included in the MAC CE, header or actual payload.

In some embodiments, the same GF PUSCH configuration for BFRR purposes may be allocated to all beams in a cell, or the beams may be divided into 2 or more groups such that different groups may have different configurations (one beam may belong to one or more beam groups). The GF PUSCH configuration for BFRR transmission may be conveyed to the UE through dedicated signaling or may be broadcast using system information.

In some embodiments, the UE may be configured with individual, grouped, dedicated GF PUSCH resources, and the network node 20 may activate the individual, grouped, dedicated GF PUSCH resources based on the mobility of the UE using dedicated signaling or system information messages.

In some embodiments, GF PUSCH resource allocation and management for beam failure recovery purposes may have the following features.

1. Each beam belonging to a certain beam group is configured with the same GF PUSCH configuration, i.e. the same time/frequency allocation.

2. GF PUSCH resources allocated to beams included in the predefined beam group are used for BFRR transmission.

3. One or several DM-RS sequences to be used with dedicated GF PUSCH resources may be coupled to a specific set of beams (beam set).

4. When several UEs share the same DM-RS sequence, C-RNTI may be included in the MAC CE or packet payload for distinguishing the UEs.

5. A UE configured with a particular beam group may transmit BFRRs using dedicated DMRS sequences and allocated physical resources.

6. The GF PUSCH configuration for BFRR transmission may be communicated to the UE using dedicated or common (system information) signaling.

7. The dedicated GF PUSCH resources may be preconfigured for the UE and the network node may use a list or bitmap to activate the beam groups with dedicated resources.

8. The list or bitmap may be delivered to the UE through dedicated signaling or system information, i.e., broadcast in a predetermined area.

In some embodiments, this solution enables a more efficient beam failure recovery solution than the CFRA solution that requires separate allocation of dedicated RACH resources for each beam of each UE. The solution proposed by the embodiments significantly reduces the size of the configuration file (in case a large area configuration is chosen) and reduces the amount of resources allocated for potential BFRR transmission. The proposed solution of embodiments also reduces the frequency of reconfigured BFRR resources per UE (in case CFRA resources are allocated to only a small set of beams).

Fig. 4 is a block diagram of an example system 700 for wireless communication in accordance with an embodiment of the present disclosure. The embodiments described herein may be implemented as a system using any suitably configured hardware and/or software. Fig. 4 shows a system 700 that includes Radio Frequency (RF) circuitry 710, baseband circuitry 720, application circuitry 730, memory/storage 740, display 750, camera 760, sensors 770, and input/output (I/O) interface 780 coupled to each other at least as shown.

The application circuitry 730 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor may include any combination of general-purpose processors and special-purpose processors (e.g., a graphics processor and an application processor). The processor may be coupled with the memory/storage and configured to execute instructions stored in the memory/storage to implement various applications and/or operating systems running on the system.

The baseband circuitry 720 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor may comprise a baseband processor. The baseband circuitry may handle various radio control functions that enable communication with one or more radio networks through the RF circuitry. The radio control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency shifting, and the like. In some embodiments, the baseband circuitry may provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry may support communication with an Evolved Universal Terrestrial Radio Access Network (EUTRAN) and/or other Wireless Metropolitan Area Networks (WMANs), wireless Local Area Networks (WLANs), wireless Personal Area Networks (WPANs). Embodiments in which the baseband circuitry is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

In various embodiments, baseband circuitry 720 may include circuitry to operate with signals that are not strictly considered to be at baseband frequencies. For example, in some embodiments, the baseband circuitry may include circuitry that operates with signals having an intermediate frequency between the baseband frequency and the radio frequency.

RF circuitry 710 may enable communication with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry may include switches, filters, amplifiers, and the like to facilitate communication with the wireless network.

In various embodiments, RF circuitry 710 may include circuitry that operates on signals that are not strictly considered to be at radio frequencies. For example, in some embodiments, the RF circuitry may include circuitry that operates with signals having an intermediate frequency between baseband and radio frequencies.

In various embodiments, the transmitter circuitry, control circuitry, or receiver circuitry discussed above with respect to the user equipment, eNB, or gNB may be embodied in whole or in part in one or more of RF circuitry, baseband circuitry, and/or application circuitry. As used herein, "circuitry" may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group) that executes one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the electronic device circuitry may be implemented in, or functions associated with, one or more software or firmware modules.

In some embodiments, some or all of the constituent components in the baseband circuitry, application circuitry, and/or memory/storage may be implemented together on a system on a chip (SOC).

Memory/storage 740 may be used to load and store data and/or instructions (e.g., for a system). The memory/storage of one embodiment may comprise any combination of suitable volatile memory (e.g., dynamic Random Access Memory (DRAM)) and/or non-volatile memory (e.g., flash memory).

In various embodiments, I/O interface 780 may include one or more user interfaces designed to enable user interaction with the system and/or peripheral component interfaces designed to enable peripheral component interaction with the system. The user interface may include, but is not limited to, a physical keyboard or keypad, a touchpad, a speaker, a microphone, and the like. The peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a Universal Serial Bus (USB) port, an audio jack, and a power interface.

In various embodiments, the sensor 770 may include one or more sensing devices to determine environmental conditions and/or location information related to the system. In some embodiments, the sensors may include, but are not limited to, a gyroscope sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may also be part of or interact with the baseband circuitry and/or RF circuitry to communicate with components of a positioning network, such as Global Positioning System (GPS) satellites.

In various embodiments, display 750 may include displays such as liquid crystal displays and touch screen displays. In various embodiments, system 700 may be a mobile computing device, such as, but not limited to, a laptop computing device, a tablet computing device, a netbook, an ultrabook, a smartphone, and the like. In various embodiments, the system may have more or fewer components and/or different architectures. Where appropriate, the methods described herein may be implemented as a computer program. The computer program may be stored on a storage medium, such as a non-transitory storage medium.

In an embodiment of the present disclosure, a method and apparatus for beam failure recovery in a wireless communication system are provided. Embodiments of the present disclosure are a combination of techniques/processes that may be employed in 3GPP specifications to create an end product.

Those of ordinary skill in the art will appreciate that each of the elements, algorithms, and steps described and disclosed in the embodiments of the present disclosure is implemented using electronic hardware, or a combination of computer software and electronic hardware. Whether a function is run in hardware or software depends on the application conditions and design requirements of the solution.

Those of ordinary skill in the art may implement the functionality of each particular application in different ways without departing from the scope of the present disclosure. A person skilled in the art will understand that he/she may refer to the working processes of the systems, devices and units in the above embodiments, since the working processes of the systems, devices and units are substantially the same. For ease of description and simplicity, these operations will not be described in detail.

It should be understood that the systems, devices, and methods disclosed in embodiments of the present disclosure may be implemented in other ways. The above embodiments are merely exemplary. The division of cells is based solely on logic functions, while other divisions exist in implementations. Multiple units or components may be combined or integrated in another system. It is also possible to omit or skip certain features. On the other hand, the mutual coupling, direct coupling or communicative coupling shown or discussed can be achieved indirectly or communicatively via some port, device or element, whether electrically, mechanically or otherwise.

The elements that are separate components for explanation may or may not be physically separate. The unit for displaying is a physical unit or not, i.e. located in one place or distributed over a plurality of network units. Some or all of the units are used according to the purpose of the embodiment. Furthermore, each functional unit in each embodiment may be integrated in one processing unit, physically separated, or integrated in one processing unit having two or more units.

If the software functional unit is implemented, used, or sold as a product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solutions proposed by the present disclosure can be implemented substantially or partially in the form of software products. Alternatively, portions of the technical solutions that are advantageous for the conventional techniques may be implemented in the form of software products. The software product in the computer is stored in a storage medium and includes a plurality of commands for a computing device (e.g., a personal computer, server, or network device) to execute all or some of the steps disclosed by embodiments of the present disclosure. The storage medium includes a U disk, a removable hard disk, a Read Only Memory (ROM), a Random Access Memory (RAM), a floppy disk or other type of medium capable of storing program code.

While the present disclosure has been described in connection with what is presently considered to be the most practical and preferred embodiment, it is to be understood that the disclosure is not to be limited to the disclosed embodiment, but is intended to cover various arrangements made without departing from the scope of the broadest interpretation of the appended claims.

Claims

1. A network node for beam failure recovery in a wireless communication system, comprising:

a memory;

a transceiver; and

a processor coupled to the memory and the transceiver,

wherein the processor is configured to:

determining M beam groups, wherein M is an integer equal to or greater than 2, wherein each of the M beam groups comprises a plurality of beams; and

allocating M resource configurations to the M beam groups, wherein a same resource configuration of the M resource configurations is allocated to a plurality of beams in a same beam group of the M beam groups; wherein each of the M resource configurations comprises a scheduling-exempt GF Physical Uplink Shared Channel (PUSCH) resource configuration;

transmitting, to a plurality of user equipments, a same GF PUSCH resource configuration allocated to a plurality of beams in a same beam group of the M beam groups, the GF PUSCH resource configuration configured to transmit a beam failure recovery request BFRR over dedicated or common signaling; wherein the GF PUSCH resource configuration comprises a plurality of time resources, a plurality of frequency resources, and a plurality of demodulation reference signal (DMRS) sequences; wherein the plurality of DMRS sequences include the same DMRS sequence and include a cell radio network temporary identity, C-RNTI, in a packet payload or a media access control element, MAC CE to distinguish the plurality of user equipments.

2. The network node of claim 1, wherein one or more of the plurality of DMRS sequences are configured for use with a dedicated GF PUSCH resource configuration of the M resource configurations and are coupled to a certain beam group of the M beam groups.

3. The network node according to claim 2, wherein a dedicated GF PUSCH resource configuration of the M resource configurations is preconfigured from the transceiver to a plurality of user equipments, and the processor is configured to activate the certain beam group of the M beam groups having a dedicated GF PUSCH resource configuration using a list or a bitmap.

4. The network node of claim 3, wherein the transceiver is configured to transmit the list or bitmap to the plurality of user equipments through dedicated or common signaling.

5. A method for beam failure recovery of a network node, comprising:

6. The method of claim 5, wherein one or more of the plurality of DMRS sequences are configured for use with a dedicated GF PUSCH resource configuration of the M resource configurations and are coupled to a certain beam group of the M beam groups.

7. The method according to claim 6, wherein a dedicated GF PUSCH resource configuration of the M resource configurations is preconfigured from the network node to a plurality of user equipments, and the method further comprises activating the certain beam group of the M beam groups with dedicated GF PUSCH resource configuration using a list or a bitmap.

8. The method of claim 7, further comprising transmitting the list or bitmap to the plurality of user equipments through dedicated or common signaling.

9. A user equipment of a plurality of user equipments for beam failure recovery in a wireless communication system, comprising:

a memory;

a transceiver; and

a processor coupled to the memory and the transceiver,

wherein the processor is configured to:

control the transceiver to receive M resource configurations allocated to the M beam groups from a network node, wherein a same resource configuration of the M resource configurations is allocated to a plurality of beams in a same beam group of the M beam groups; wherein each of the M resource configurations comprises a scheduling-exempt GF Physical Uplink Shared Channel (PUSCH) resource configuration;

receiving, from the network node, a same GF PUSCH resource configuration allocated to a plurality of beams in a same beam group of the M beam groups, the GF PUSCH resource configuration configured to transmit a Beam Failure Recovery Request (BFRR) over dedicated or common signaling; wherein the GF PUSCH resource configuration comprises a plurality of time resources, a plurality of frequency resources, and a plurality of demodulation reference signal (DMRS) sequences; wherein the plurality of DMRS sequences include the same DMRS sequence and include a cell radio network temporary identity, C-RNTI, in a packet payload or a media access control element, MAC CE to distinguish the plurality of user equipments.

10. The user equipment of claim 9, wherein one or more of the plurality of DMRS sequences are configured for use with a dedicated GF PUSCH resource configuration of the M resource configurations and are coupled to a certain beam group of the M beam groups.

11. The user equipment according to claim 10, wherein the transceiver is configured to receive from the network node a dedicated GF PUSCH resource configuration of the M resource configurations preconfigured to the plurality of user equipments.

12. The user equipment of claim 10, wherein the transceiver is configured to receive a list or bitmap from the network node to the plurality of user equipments through dedicated or common signaling.

13. A method of beam failure recovery performed by a user equipment of a plurality of user equipments, comprising:

receiving, from a network node, M resource configurations allocated to the M beam groups, wherein a same resource configuration of the M resource configurations is allocated to a plurality of beams in a same beam group of the M beam groups; wherein each of the M resource configurations comprises a scheduling-exempt GF Physical Uplink Shared Channel (PUSCH) resource configuration;

14. The method of claim 13, wherein one or more of the plurality of DMRS sequences are configured for use with a dedicated GF PUSCH resource configuration of the M resource configurations and are coupled to a certain beam group of the M beam groups.

15. The method according to claim 14, further comprising receiving from the network node a dedicated GF PUSCH resource configuration of the M resource configurations preconfigured to the plurality of user equipments.

16. The method of claim 14, further comprising receiving a list or bitmap from the network node to the plurality of user equipments through dedicated or common signaling.

17. A non-transitory machine-readable storage medium having instructions stored thereon, which when executed by a computer, cause the computer to perform the method of any of claims 5-8 and 13-16.

18. A network node, comprising: a processor and a memory configured to store a computer program, the processor configured to execute the computer program stored in the memory to perform the method of any of claims 5 to 8.

19. A terminal device, comprising: a processor and a memory configured to store a computer program, the processor configured to execute the computer program stored in the memory to perform the method of any of claims 13 to 16.