WO2019128975A1

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

Info

Publication number: WO2019128975A1
Application number: PCT/CN2018/123425
Authority: WO
Inventors: Jari Jaakko ISOKANGAS; Ning Yang; Cong SHI
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: 2019-07-04
Anticipated expiration: 2020-06-28
Also published as: CN111418164B; CN111418164A

Abstract

A method and an apparatus for a beam failure recovery in a wireless communication system are provided. The method for the beam failure recovery of a network node includes determining M beam groups where M is an integer equal to or greater than 2, wherein each beam group 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 the plurality of beams of a same beam group of the M beam groups.

Description

METHOD AND APPARATUS FOR A BEAM FAILURE RECOVERY IN A WIRELESS COMMUNICATION SYSTEM

BACKGROUND OF DISCLOSURE

1. Field of Disclosure

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

2. Description of Related Art

It has been agreed in the 3rd generation partnership project (3GPP) that in a new radio (NR) system, such as 5G, beam management, and mobility between beams, can happen without radio resource control (RRC) involvement. That is, changes of a serving beam or a set of beams can be handled by lower protocol layers to avoid RRC level signaling between a user equipment (UE) and a network (NW) . In case of a beam failure, for example, that the UE is not able to receive a downlink (DL) beam anymore, it has been agreed in RAN1#89 and RAN1#90, that contention free random access (CFRA) procedure is used to carry a beam failure recovery request (BFRR) message from the UE to the NW.

There is also discussion about a possibility to use PUCCH scheduling request (SR) and potential contention based random access (CBRA) in case that dedicated uplink (UL) resources cannot be used for CFRA or PUCCH for sending the BFRR. However, when it is required that UE needs to be identified uniquely during a beam recovery process, a usage of CFRA with dedicated PRACH or PUCCH resources obviously is a preferred solution and CBRA could be included as a fallback solution in case that neither of the dedicated resources are available.

To be able to utilize either CFRA or PUCCH for beam recovery, the resources need to be configured beforehand to the UE. In a PUCCH case, the problem is not significant as beam failure happens when the UE is in an RRC connected mode and in that case, PUCCH resources are usually configured. In a CBRA case, the UE can use the same PRACH configuration as for any other CBRA based access for initial access i.e. no additional resources need to be allocated for potential beam failure recovery preparation. However, as the PUCCH resources are usually configured only for serving beam (s) , there are limitations to the usage of PUCCH for beam recovery due to the limited amount of reserved PUCCH resources per UE.

When CFRA is used for this purpose, the dedicated RACH resources (preamble sequences/frequency/time per beam identified either by channel state information reference signal (CSI-RS) or SS block (SSB) ) need to be allocated for each candidate beam that UE could potentially use to send BFRR messages. In NR (5G) , one cell could consist of several transmission points (TRPs) and each TRP could be served by several tens of beams i.e. the number of candidate beams per UE could be quite high and leads to very inefficient RACH resource usage in case that all beams belonging to certain cells are identified as candidate beams (i.e. beams that UE can use for transmitting/receiving inside one cell) . From points of view of a RACH resource allocation and efficiency, more effective solutions are to keep the set of beams where RACH has been allocated as small as possible. However, as the dedicated RACH configuration is passed to UE using RRC signaling, frequent configuration updates will increase the load of the RRC signaling significantly and will generate additional delay compared with lower layer management/signaling mechanisms.

There is a need to provide a new technical solution for a method and an apparatus for a beam failure recovery in a wireless communication system.

SUMMARY

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

In a first aspect of the present disclosure, a network node for a 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, wherein each beam group of the M beam groups includes a plurality of beams, and the processor is configured to allocate M resource configurations to the M beam groups, wherein a same resource configuration of the M resource configurations is allocated to the plurality of beams of a same beam group of the M beam groups.

In a second aspect of the present disclosure, a method for a beam failure recovery of a network node includes determining M beam groups where M is an integer equal to or greater than 2, wherein each beam group 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 the plurality of beams of a same beam group of the M beam groups.

In a third aspect of the present disclosure, a user equipment of a plurality of user equipment for a 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, wherein each beam group of the M beam groups includes a plurality of beams, and 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 the plurality of beams of a same beam group of the M beam groups.

In a fourth aspect of the present disclosure, a method for a beam failure recovery performed by a user equipment of a plurality of user equipment includes determining M beam groups where M is an integer equal to or greater than 2, wherein each beam group of the M beam groups includes a plurality of beams, and receiving 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 the plurality of beams of a same beam group of the M beam groups.

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

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

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

BRIEF DESCRIPTION OF DRAWINGS

In order to more clearly illustrate the embodiments of the present disclosure or related art, the following figures will be described in the embodiments are briefly introduced. It is obvious that the drawings are merely some embodiments of the present disclosure, a person having ordinary skill in this field can obtain other figures according to these figures without paying the premise.

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

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

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

FIG. 4 is a block diagram of a system for wireless communication according to an embodiment of the present disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

Embodiments of the present disclosure are described in detail with the technical matters, structural features, achieved objects, and effects with reference to the accompanying drawings as follows. Specifically, the terminologies in the embodiments of the present disclosure are merely for describing the purpose of the certain embodiment, but not to limit the disclosure.

FIG. 1 illustrates that, in some embodiments, a user equipment (UE) 10 and a network node 20 for a beam failure recovery in a wireless communication system according to an embodiment 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 include a processor 21, a memory 22 and a transceiver 23. The

processor

11 or 21 may be configured to implement proposed functions, procedures and/or methods described in this description. Layers of radio 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 a variety of 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 a radio signal.

The

processor

11 or 21 may include an application-specific integrated circuit (ASIC) , other chipsets, logic circuit and/or data processing devices. The

memory

12 or 22 may include a read-only memory (ROM) , a random access memory (RAM) , a flash memory, a memory card, a storage medium and/or other storage devices. The

transceiver

13 or 23 may include baseband circuitry to process radio frequency signals. When the embodiments are implemented in software, the techniques described herein can be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. The modules can be stored in the

memory

12 or 22 and executed by the

processor

11 or 21. The

memory

12 or 22 can be implemented within the

processor

11 or 21 or external to the

processor

11 or 21, in which those can be communicatively coupled to the

processor

11 or 21 via various means are known in the art.

The communication between UEs relates to vehicle-to-everything (V2X) communication including vehicle-to-vehicle (V2V) , vehicle-to-pedestrian (V2P) , and vehicle-to-infrastructure/network (V2I/N) according to a sidelink technology developed under 3rd generation partnership project (3GPP) new radio (NR) Release 16 and beyond. UEs communicate with each other directly via a sidelink interface such as a 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 beam group of the M beam groups includes a plurality of beams, and the processor 21 is configured to allocate M resource configurations to the M beam groups, wherein a same resource configuration of the M resource configurations is allocated to the plurality of beams of a same beam group 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 beam group of the M beam groups includes 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 resource configuration of the M resource configurations is allocated to the plurality of beams of a same beam group of the M beam groups.

FIG. 2 illustrates a method 200 for a beam failure recovery of the network node 20 according to an embodiment of the present disclosure. The method 200 includes: at block 202, determining M beam groups where M is an integer equal to or greater than 2, wherein each beam group of the M beam groups includes a plurality of beams, and at block 204, allocating M resource configurations to the M beam groups, wherein a same resource configuration of the M resource configurations is allocated to the plurality of beams of a same beam group of the M beam groups.

FIG. 3 illustrates a method 300 for a beam failure recovery performed by the user equipment 10 of a plurality of user equipment according to an embodiment of the present disclosure. The method 300 includes: at block 302, determining M beam groups where M is an integer equal to or greater than 2, wherein each beam group of the M beam groups includes a plurality of beams, and at block 304, receiving M resource configurations allocated to the M beam groups from the network node 20, wherein a same resource configuration of the M resource configurations is allocated to the plurality of beams of a same beam group of the M beam groups.

In some embodiments, each resource configuration of the M resource configurations includes a grant 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. A same GF PUSCH resource configuration allocated to the plurality of beams of the same beam group of the M beam groups is configured to transmit a beam failure recovery request (BFRR) . One or several DMRS sequences 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, to a plurality of user equipment, a same DMRS sequence of the plurality of DMRS sequences, and the processor 21 is configured to use a medium access control control element (MAC CE) or packet payload having a cell radio network temporary identifier (C-RNTI) to distinguish the plurality of user equipment.

In details, the transceiver 23 is configured to transmit, to the plurality of user equipment, the same GF PUSCH resource configuration allocated to the plurality of beams of the same beam group of the M beam groups configured to transmit the BFRR via a dedicated or common signaling.

In some embodiments, the dedicated GF PUSCH resource configuration of the M resource configurations is preconfigured to the plurality of user equipment from the transceiver 23, and the processor 21 is configured to activate the certain beam group of the M beam groups with the dedicated GF PUSCH resource configuration using a list or bitmap. In details, the transceiver 23 is configured to transmit, to the plurality of user equipment, the list or bitmap via a dedicated or common signaling.

In some embodiments, the transceiver 13 is configured to receive a same DMRS sequence of the plurality of DMRS sequences allocated to the plurality of user equipment from the network node 20. In details, the transceiver 13 is configured to receive the same GF PUSCH resource configuration allocated to the plurality of beams of the same beam group of the M beam groups configured to transmit the BFRR via a dedicated or common signaling from the network node 20.

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

To be able to utilize a grant free (GF) physical uplink shared channel (PUSCH) to carry beam failure recovery requests effectively, a GF PUSCH solution need to be enhanced to support multibeam deployment scenarios. A easy solution is to allocate time/frequency/demodulation reference signal (DMRS) sequence resources in the same way as in a cell (single beam) level solution, i.e. separate resources are allocated per beam. However, this solution leads to either huge configuration files or very frequent configuration updates due a UE mobility.

In some embodiments, to reduce a size of configuration files or frequent UE re-configurations if smaller set of beams with allocated GF PUSCH resources are used, and to reduce an amount of needed radio resources for GF PUSCH purposes, the same time/frequency resources and DMRS sequences can be configured to all beams or a set of beams in a cell. A usage of a dedicated DMRS sequence to distinguish UEs can limit a max number of supported UEs when the same time/frequency resource allocation can be used over several beams. As a number of possible DMRS sequences is limited within certain physical resources, a solution is enhanced so that several UEs can share the same DMRS sequence. As each UE has unique C-RNTI in an RRC connected mode, that can be used to distinguish individual UEs in a network side and a UE C-RNTI can be included to MAC CE, header, or actual payload.

In some embodiments, the same GF PUSCH configuration for BFRR purposes can be allocated to all beams in the cell or beams can be divided to 2 or more groups, so that different groups can have different configuration (one beam can belong to one or more beam groups) . The GF PUSCH configuration for BFRR transmission can be passed to UEs with a dedicated signaling or can be broadcasted using system information.

In some embodiments, separate sets of dedicated GF PUSCH resources can be configured to the UEs and the network node 20 can active the separate sets of dedicated GF PUSCH resources based on a UE mobility using either a dedicated signaling or system information messages.

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

1. The same GF PUSCH configuration, i.e. same time/frequency allocation is configured for each beam which belong to a certain beam group.

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

3. One or several DM-RS sequences to be used with dedicated GF PUSCH resources can be coupled to a certain set of beams (abeam group) .

4. When several UEs share the same DM-RS sequence, C-RNTI can be included to a MAC CE or packet payload to be used to distinguish the UEs.

5. The UE, which has a certain beam group configured, can use the dedicated DMRS sequences with allocated physical resources to transmit BFRR.

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

7. The dedicated GF PUSCH resources can be preconfigured to the UEs and the network node can activate a set of beams with dedicated resources using a list or bitmap.

8. The list or bitmap can be passed to the UEs via a dedicated signaling or system information, i.e. broadcasted in predefined areas.

In some embodiments, the solution enables more effective beam failure recovery solution compared to a CFRA solution where dedicated RACH resources need to be allocated for every beam separately for each UE. The proposed solution of the embodiment reduces significantly a size of the configuration files (in a case that a large area configuration scheme has been selected) and decreases an amount of allocated resources for potential BFRR transmission. The proposed solution of the embodiment also reduces a frequency of a BFRR resources of a reconfiguration per UE (in a case that CFRA resources are allocated only to a small set of beams) .

FIG. 4 is a block diagram of an example system 700 for wireless communication according to an embodiment of the present disclosure. Embodiments described herein may be implemented into the system using any suitably configured hardware and/or software. FIG. 4 illustrates the system 700 including a radio frequency (RF) circuitry 710, a baseband circuitry 720, an application circuitry 730, a memory/storage 740, a display 750, a camera 760, a sensor 770, and an input/output (I/O) interface 780, coupled with each other at least as illustrated.

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

The baseband circuitry 720 may include a circuitry, such as, but not limited to, one or more single-core or multi-core processors. The processors may include a baseband processor. The baseband circuitry may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry. The radio control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency shifting, etc. In some embodiments, the baseband circuitry may provide for communication 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 (WMAN) , a wireless local area network (WLAN) , a wireless personal area network (WPAN) . 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, the baseband circuitry 720 may include circuitry to operate with signals that are not strictly considered as being in a baseband frequency. For example, in some embodiments, baseband circuitry may include circuitry to operate with signals having an intermediate frequency, which is between a baseband frequency and a radio frequency.

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

In various embodiments, the RF circuitry 710 may include circuitry to operate with signals that are not strictly considered as being in a radio frequency. For example, in some embodiments, RF circuitry may include circuitry to operate with signals having an intermediate frequency, which is between a baseband frequency and a radio frequency.

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 the RF circuitry, the baseband circuitry, and/or the 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 a memory (shared, dedicated, or group) that execute 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 the circuitry may be implemented by, one or more software or firmware modules.

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

The memory/storage 740 may be used to load and store data and/or instructions, for example, for system. The memory/storage for one embodiment may include any combination of suitable volatile memory, such as dynamic random access memory (DRAM) ) , and/or non-volatile memory, such as flash memory.

In various embodiments, the 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. User interfaces may include, but are not limited to a physical keyboard or keypad, a touchpad, a speaker, a microphone, etc. 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 supply 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 gyro 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, e.g., a global positioning system (GPS) satellite.

In various embodiments, the display 750 may include a display, such as a liquid crystal display and a touch screen display. In various embodiments, the 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, etc. In various embodiments, system may have more or less components, and/or different architectures. Where appropriate, 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 the embodiment of the present disclosure, a method and an apparatus for a beam failure recovery in a wireless communication system are provided. The embodiment of the present disclosure is a combination of techniques/processes that can be adopted in 3GPP specification to create an end product.

A person having ordinary skill in the art understands that each of the units, algorithm, and steps described and disclosed in the embodiments of the present disclosure are realized using electronic hardware or combinations of software for computers and electronic hardware. Whether the functions run in hardware or software depends on the condition of application and design requirement for a technical plan.

A person having ordinary skill in the art can use different ways to realize the function for each specific application while such realizations should not go beyond the scope of the present disclosure. It is understood by a person having ordinary skill in the art that he/she can refer to the working processes of the system, device, and unit in the above-mentioned embodiment since the working processes of the above-mentioned system, device, and unit are basically the same. For easy description and simplicity, these working processes will not be detailed.

It is understood that the disclosed system, device, and method in the embodiments of the present disclosure can be realized with other ways. The above-mentioned embodiments are exemplary only. The division of the units is merely based on logical functions while other divisions exist in realization. It is possible that a plurality of units or components are combined or integrated in another system. It is also possible that some characteristics are omitted or skipped. On the other hand, the displayed or discussed mutual coupling, direct coupling, or communicative coupling operate through some ports, devices, or units whether indirectly or communicatively by ways of electrical, mechanical, or other kinds of forms.

The units as separating components for explanation are or are not physically separated. The units for display are or are not physical units, that is, located in one place or distributed on a plurality of network units. Some or all of the units are used according to the purposes of the embodiments. Moreover, each of the functional units in each of the embodiments can be integrated in one processing unit, physically independent, or integrated in one processing unit with two or more than two units.

If the software function unit is realized and used and sold as a product, it can be stored in a readable storage medium in a computer. Based on this understanding, the technical plan proposed by the present disclosure can be essentially or partially realized as the form of a software product. Or, one part of the technical plan beneficial to the conventional technology can be realized as the form of a software product. The software product in the computer is stored in a storage medium, including a plurality of commands for a computational device (such as a personal computer, a server, or a network device) to run all or some of the steps disclosed by the embodiments of the present disclosure. The storage medium includes a USB disk, a mobile hard disk, a read-only memory (ROM) , a random access memory (RAM) , a floppy disk, or other kinds of media capable of storing program codes.

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

Claims

A network node for a 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:

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

allocate M resource configurations to the M beam groups, wherein a same resource configuration of the M resource configurations is allocated to the plurality of beams of a same beam group of the M beam groups.
The network node of claim 1, wherein each resource configuration of the M resource configurations comprises a grant free (GF) physical uplink shared channel (PUSCH) resource configuration.
The network node of claim 2, wherein the GF PUSCH resource configuration comprises a plurality of time resources, a plurality of frequency resources, and/or a plurality of demodulation reference signal (DMRS) sequences.
The network node of claim 2 or 3, wherein a same GF PUSCH resource configuration allocated to the plurality of beams of the same beam group of the M beam groups is configured to transmit a beam failure recovery request (BFRR) .
The network node of claim 3 or 4, wherein one or several DMRS sequences 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.
The network node of any one of claims 3 to 5, wherein the processor is configured to allocate, to a plurality of user equipment, a same DMRS sequence of the plurality of DMRS sequences, and the processor is configured to use a medium access control control element (MAC CE) or packet payload having a cell radio network temporary identifier (C-RNTI) to distinguish the plurality of user equipment.
The network node of claim 4, wherein the transceiver is configured to transmit, to a plurality of user equipment, the same GF PUSCH resource configuration allocated to the plurality of beams of the same beam group of the M beam groups configured to transmit the BFRR via a dedicated or common signaling.
The network node of claim 5, wherein the dedicated GF PUSCH resource configuration of the M resource configurations is preconfigured to a plurality of user equipment from the transceiver, and the processor is configured to activate the certain beam group of the M beam groups with the dedicated GF PUSCH resource configuration using a list or bitmap.
The network node of claim 8, wherein the transceiver is configured to transmit, to the plurality of user equipment, the list or bitmap via a dedicated or common signaling.
A method for a beam failure recovery of a network node, comprising:

determining M beam groups where M is an integer equal to or greater than 2, wherein each beam group 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 the plurality of beams of a same beam group of the M beam groups.
The method of claim 10, wherein each resource configuration of the M resource configurations comprises a grant free (GF) physical uplink shared channel (PUSCH) resource configuration.
The method of claim 11, wherein the GF PUSCH resource configuration comprises a plurality of time resources, a plurality of frequency resources, and/or a plurality of demodulation reference signal (DMRS) sequences.
The method of claim 11 or 12, wherein a same GF PUSCH resource configuration allocated to the plurality of beams of the same beam group of the M beam groups is configured to transmit a beam failure recovery request (BFRR) .
The method of claim 12 or 13, wherein one or several DMRS sequences 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.
The method of any one of claims 12 to 14, further comprising allocating, to a plurality of user equipment, a same DMRS sequence of the plurality of DMRS sequences, and using a medium access control control element (MAC CE) or packet payload having a cell radio network temporary identifier (C-RNTI) to distinguish the plurality of user equipment.
The method of claim 13, further comprising transmitting, to a plurality of user equipment, the same GF PUSCH resource configuration allocated to the plurality of beams of the same beam group of the M beam groups configured to transmit the BFRR via a dedicated or common signaling.
The method of claim 14, wherein the dedicated GF PUSCH resource configuration of the M resource configurations is preconfigured to a plurality of user equipment from the network, and the method further comprises activating the certain beam group of the M beam groups with the dedicated GF PUSCH resource configuration using a list or bitmap.
The method of claim 17, further comprising transmitting, to the plurality of user equipment, the list or bitmap via a dedicated or common signaling.
A user equipment of a plurality of user equipment for a 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:

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

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 the plurality of beams of a same beam group of the M beam groups.
The user equipment of claim 19, wherein each resource configuration of the M resource configurations comprises a grant free (GF) physical uplink shared channel (PUSCH) resource configuration.
The user equipment of claim 20, wherein the GF PUSCH resource configuration comprises a plurality of time resources, a plurality of frequency resources, and/or a plurality of demodulation reference signal (DMRS) sequences.
The user equipment of claim 20 or 21, wherein a same GF PUSCH resource configuration allocated to the plurality of beams of the same beam group of the M beam groups is configured to transmit a beam failure recovery request (BFRR) .
The user equipment of claim 21 or 22, wherein one or several DMRS sequences 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.
The user equipment of any one of claims 21 to 23, wherein the transceiver is configured to receive a same DMRS sequence of the plurality of DMRS sequences allocated to the plurality of user equipment from the network node.
The user equipment of claim 23, wherein the transceiver is configured to receive the same GF PUSCH resource configuration allocated to the plurality of beams of the same beam group of the M beam groups configured to transmit the BFRR via a dedicated or common signaling from the network node.
The user equipment of claim 23, wherein the transceiver is configured to receive the dedicated GF PUSCH resource configuration of the M resource configurations preconfigured to the plurality of user equipment from the network node.
The user equipment of claim 23, wherein the transceiver is configured to receive a list or bitmap via a dedicated or common signaling to the plurality of user equipment from the network node.
A method for a beam failure recovery performed by a user equipment of a plurality of user equipment, comprising:

determining M beam groups where M is an integer equal to or greater than 2, wherein 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, wherein a same resource configuration of the M resource configurations is allocated to the plurality of beams of a same beam group of the M beam groups.
The method of claim 28, wherein each resource configuration of the M resource configurations comprises a grant free (GF) physical uplink shared channel (PUSCH) resource configuration.
The method of claim 29, wherein the GF PUSCH resource configuration comprises a plurality of time resources, a plurality of frequency resources, and/or a plurality of demodulation reference signal (DMRS) sequences.
The method of claim 29 or 30, wherein a same GF PUSCH resource configuration allocated to the plurality of beams of the same beam group of the M beam groups is configured to transmit a beam failure recovery request (BFRR) .
The method of claim 30 or 31, wherein one or several DMRS sequences 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.
The method of any one of claims 30 to 32, further comprising receiving a same DMRS sequence of the plurality of DMRS sequences allocated to the plurality of user equipment from the network node.
The method of claim 32, further comprising receiving the same GF PUSCH resource configuration allocated to the plurality of beams of the same beam group of the M beam groups configured to transmit the BFRR via a dedicated or common signaling from the network node.
The method of claim 32, further comprising receiving the dedicated GF PUSCH resource configuration of the M resource configurations preconfigured to the plurality of user equipment from the network node.
The method of claim 32, further comprising receiving a list or bitmap via a dedicated or common signaling to the plurality of user equipment from the network node.
A non-transitory machine-readable storage medium having stored thereon instructions that, when executed by a computer, cause the computer to perform the method of any one of claims 10 to 18 and 28 to 36.
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 one of claims 10 to 15 and 17.
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 one of claims 28 to 32.