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

Abstract

A method performed by a user equipment (UE) in a wireless communication system is provided. The method includes receiving, from a base station (BS), a radio resource control (RRC) message including beam failure detection configuration information and beam failure recovery configuration information, detecting a beam failure for at least one transmission reception point (TRP) of a serving cell based on the beam failure detection configuration information, and triggering a beam failure recovery for the serving cell for which the beam failure is detected based on the beam failure recovery configuration information, wherein the beam failure detection configuration information includes at least one beam failure detection reference signal list for the at least one TRP of the serving cell.

Description

Technical Field

[0001] This application generally relates to wireless communication systems, and more specifically, this disclosure relates to handling beam fault recovery in serving cells supporting multiple TRPs. Background Technology

[0002] To meet the increasing demand for wireless data traffic since the deployment of fourth-generation (4G) communication systems, efforts have been made to develop improved fifth-generation (5G) or pre-5G communication systems. 5G or pre-5G communication systems are also referred to as "super-4G networks" or "post-LTE systems." 5G communication systems are considered to be implemented in higher frequency (millimeter-wave) bands (e.g., the 60 GHz band) to achieve higher data rates. To reduce radio wave propagation loss and increase transmission distance, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large antenna technologies for 5G communication systems have been discussed. Furthermore, in 5G communication systems, development is underway for system network improvements based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, cooperative multipoint (CoMP), and receiver interference cancellation. In 5G systems, hybrid frequency shift keying (FSK) and Feher quadrature amplitude modulation (FQAM) and sliding window superposition coding (SWSC) have been developed as advanced coding modulation (ACM), as well as filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies.

[0003] The internet, a human-centric network in which humans generate and consume information, has now evolved into the Internet of Things (IoT), in which distributed entities, such as things, exchange and process information without human intervention. The Internet of Everything (IoE) is a product of combining IoT technology and big data processing technology through connections to cloud servers. Because IoT implementation requires technological elements such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology, recent research has focused on sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC). This IoT environment can provide intelligent internet technology services that create new value for human life by collecting and analyzing data generated between connected things. IoT can be applied to a variety of fields through the convergence and combination of existing information technology (IT) with various industrial applications, including smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.

[0004] Therefore, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, MTC, and M2M communication can be implemented through beamforming, MIMO, and array antennas. The application of cloud RAN as a big data processing technology can also be seen as an example of the connection between 5G and IoT technologies.

[0005] As mentioned above, various services can be provided based on the development of wireless communication systems, and therefore a method for easily providing such services is needed. Summary of the Invention

[0006] [Technical Solution]

[0007] In one embodiment, a method performed by a user equipment (UE) in a wireless communication system is provided. The method includes: triggering beam fault recovery of at least one serving cell via a media access control (MAC) layer; identifying, via the MAC layer, whether candidate beam evaluation for at least one serving cell where beam fault recovery has been triggered and not cancelled has been completed; and generating a MAC control element (CE) for beam fault recovery via the MAC layer based on the identified result, wherein for at least one serving cell where a beam fault has been detected and candidate beam evaluation has been completed, detection information in the MAC CE is set to 1. Attached Figure Description

[0008] To gain a more complete understanding of this disclosure and its advantages, the following description is now taken in conjunction with the accompanying drawings, in which the same reference numerals denote the same parts: Figure 1 An example of a BFR MAC CE according to an embodiment of the present disclosure is shown; Figure 2 An example of a BFR MAC CE according to an embodiment of the present disclosure is shown; Figure 3 An example wireless network according to an embodiment of the present disclosure is shown; Figure 4 This is a flowchart illustrating beam fault detection and beam fault recovery according to embodiments of the present disclosure; Figure 5 This is a flowchart illustrating beam fault detection and beam fault recovery according to embodiments of the present disclosure; Figure 6 An enhanced format of BFR MAC CE according to an embodiment of the present disclosure is shown; Figure 7 An enhanced format of BFR MAC CE according to an embodiment of the present disclosure is shown; Figure 8 An enhanced format of BFR MAC CE according to an embodiment of the present disclosure is shown; Figure 9 An enhanced format of BFR MAC CE according to an embodiment of the present disclosure is shown; Figure 10 An enhanced format of BFR MAC CE according to an embodiment of the present disclosure is shown; Figure 11 An enhanced format of BFR MAC CE according to an embodiment of the present disclosure is shown; Figure 12 An enhanced format of BFR MAC CE according to an embodiment of the present disclosure is shown; Figure 13 An enhanced format of BFR MAC CE according to an embodiment of the present disclosure is shown; Figure 14 A data transmission / reception method for uplink beam transmission between a terminal and a base station is illustrated according to an embodiment of the present disclosure; Figure 15 A data transmission / reception method for uplink beam transmission between a terminal and a base station is illustrated according to an embodiment of the present disclosure; Figure 16 A data transmission / reception method for uplink beam transmission between a terminal and a base station is illustrated according to an embodiment of the present disclosure; Figure 17 A data transmission / reception method for uplink beam transmission between a terminal and a base station is illustrated according to an embodiment of the present disclosure; Figure 18 A data transmission / reception method for uplink beam transmission between a terminal and a base station is illustrated according to an embodiment of the present disclosure; Figure 19 A flowchart illustrating a method performed by a user equipment (UE) in a wireless communication system according to an embodiment of the present disclosure is shown; Figure 20 This is a diagram illustrating a UE 2000 according to an embodiment of this disclosure; and Figure 21 This is a diagram illustrating a base station 2100 according to an embodiment of the present disclosure. Detailed Implementation

[0009] This disclosure relates to handling beam fault recovery in serving cells that support multiple TRPs.

[0010] In one embodiment, a method is provided performed by a user equipment (UE) in a wireless communication system. The method includes: triggering beam fault recovery of at least one serving cell via a media access control (MAC) layer; identifying, via the MAC layer, whether candidate beam evaluation for at least one serving cell where beam fault recovery has been triggered and not cancelled has been completed; and generating a MAC control element (CE) for beam fault recovery via the MAC layer based on the identified result, wherein for at least one serving cell where a beam fault has been detected and candidate beam evaluation has been completed, detection information in the MAC CE is set to 1.

[0011] In another embodiment, a user equipment (UE) is provided in a wireless communication system. The UE includes: a transceiver; and at least one processor connected to the transceiver and configured to: trigger beam fault recovery of at least one serving cell via a media access control (MAC) layer; identify via the MAC layer whether candidate beam evaluation for at least one serving cell for which beam fault recovery has been triggered and not cancelled has been completed; and generate a MAC control element (CE) for beam fault recovery via the MAC layer based on the identified result, wherein for at least one serving cell that has detected a beam fault and completed candidate beam evaluation, the detection information in the MAC CE is set to 1.

[0012] Other technical features will be readily apparent to those skilled in the art from the following figures, description and claims.

[0013] [Invention Model]

[0014] Before proceeding with the detailed description below, it may be advantageous to define certain words and phrases used throughout this patent document. The term “connection” and its derivatives refer to any direct or indirect communication between two or more elements, whether or not these elements are physically in contact with each other. The terms “transmit,” “receive,” and “communicate,” and their derivatives, cover both direct and indirect communication. The terms “comprising” and “including,” and their derivatives, mean unrestricted inclusion. The term “or” is inclusive, indicating and / or. The phrase “associated with” and its derivatives mean including, being included within, interconnected with, comprising, being included in, connected to or connected with, linked to or connected with, capable of communicating with, cooperating with, interleaving, juxtaposed, adjacent to, combined with or combined with, having, possessing characteristics of, having a relationship with, or being related to, etc. The term “controller” means any device, system, or part thereof that controls at least one operation. Such a controller may be implemented in hardware, or a combination of hardware and software and / or firmware. Whether local or remote, the functionality associated with any particular controller can be centralized or distributed. The phrase "at least one of..." when used with a list of items means that different combinations of one or more of the listed items may be used, and it is possible that only one item from the list is needed. For example, "at least one of A, B, and C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.

[0015] Furthermore, the various functions described below can be implemented or supported by one or more computer programs, each computer program being formed by computer-readable program code and embodied in a computer-readable medium. The terms "application program" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation in appropriate computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium accessible by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, optical disc (CD), digital video disc (DVD), or any other type of storage. "Non-transitory" computer-readable media excludes wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable media includes media that can permanently store data, as well as media that can store data and subsequently rewrite it, such as rewritable optical discs or erasable memory devices.

[0016] Definitions of certain other words and phrases are provided throughout this patent document. Those skilled in the art will understand that, in many (if not most) cases, such definitions apply to the prior and future use of the words and phrases thus defined.

[0017] Before proceeding with the detailed description below, it may be advantageous to define certain words and phrases used throughout this patent document: the terms “comprising” and “including” and their derivatives mean including but not limited to; the term “or” is inclusive, meaning and / or; the phrases “associated with” and “associated with” and their derivatives may mean including, contained within, interconnected with, contained, included in, connected to or connected to, linked to or connected to, communicable with, cooperating with, intertwined, juxtaposed, proximate with, bound to or bound to, having, possessing the properties of, etc.; and the term “controller” means any means, system or part thereof that controls at least one operation, such means may be implemented in hardware, firmware or software, or some combination of at least two of them. It should be noted that the functionality associated with any particular controller can be centralized or distributed, local or remote.

[0018] Furthermore, the various functions described below can be implemented or supported by one or more computer programs, each computer program being formed by computer-readable program code and embodied in a computer-readable medium. The terms "application program" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation in appropriate computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium accessible by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, optical disc (CD), digital video disc (DVD), or any other type of storage. "Non-transitory" computer-readable media excludes wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable media includes media that can permanently store data, as well as media that can store data and subsequently rewrite it, such as rewritable optical discs or erasable memory devices.

[0019] Throughout this patent document, definitions of certain words and phrases are provided, and those skilled in the art will understand that, in many (if not most) cases, such definitions apply to the prior and future use of the words and phrases so defined.

[0020] The following discussion Figures 1 to 21The various embodiments described in this patent document to illustrate the principles of this disclosure are merely illustrative and should not be construed as limiting the scope of this disclosure in any way. Those skilled in the art will understand that the principles of this disclosure can be implemented in any suitably arranged system or apparatus.

[0021] Throughout this disclosure, the expression "at least one of a, b, or c" indicates only a; only b; only c; both a and b; both a and c; both b and c; all of a, b, and c, or variations thereof. Throughout the specification, a layer (or layer arrangement) may also be referred to as an entity. The operating principles of this disclosure will be described in detail below with reference to the accompanying drawings. Well-known functions or configurations are not described in detail in the following description, as they would obscure this disclosure with unnecessary detail. The terminology used in this specification is defined with reference to the functions used in this disclosure and may be changed according to the intent or common practice of the user or operator. Therefore, the definitions of the terms should be understood based on the entire description of this specification.

[0022] For the same reason, some elements may be exaggerated, omitted, or roughly shown in the accompanying drawings. Additionally, the size of each element does not exactly correspond to its actual size. In each drawing, the same or corresponding elements are given the same reference numerals.

[0023] The advantages and features of this disclosure, as well as methods for achieving said advantages and features, can be more readily understood by referring to the following detailed description of embodiments and accompanying drawings. However, this disclosure may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concepts of this disclosure to those skilled in the art. Therefore, the scope of this disclosure is defined by the appended claims. Throughout this specification, the same reference numerals refer to the same elements. It will be understood that the blocks in a flowchart or combination of flowcharts can be executed by computer program instructions. Since these computer program instructions can be loaded into a processor of a general-purpose computer, a special-purpose computer, or another programmable data processing apparatus, the instructions, which are executed by the processor of the computer or other programmable data processing apparatus, create units for performing the functions described in the flowchart blocks.

[0024] Computer program instructions can be stored in a computer-usable or computer-readable storage medium capable of directing a computer or other programmable data processing device to perform functions in a particular manner. Therefore, the instructions stored in the computer-usable or computer-readable storage medium can also produce an article of art containing instruction units for performing the functions described in the flowchart block. The computer program instructions can also be loaded into a computer or other programmable data processing device, and thus, instructions for operating the computer or other programmable data processing device by generating a process executed by the computer when a series of operations are performed in the computer or other programmable data processing device can provide operations for performing the functions described in the flowchart block.

[0025] Furthermore, each box can represent a module, section, or part of code, which includes one or more executable instructions for performing a specified logical function. It should also be noted that in some alternative implementations, the functions mentioned in a box can occur out of order. For example, depending on their corresponding functions, two consecutive boxes can be executed simultaneously or in reverse order.

[0026] As used herein, the term "cell" refers to a software element or hardware element, such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC), that performs a specific function. However, the term "cell" is not limited to software or hardware. A "cell" can be formed to be stored in an addressable memory medium or to operate one or more processors. Thus, for example, the term "cell" can include elements (e.g., software elements, object-oriented software elements, class elements, and task elements), processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, or variables.

[0027] The functionality provided by the elements and "units" can be combined into a smaller number of elements and "units," or can be divided into additional elements and "units." Furthermore, elements and "units" can be implemented to reproduce one or more central processing units (CPUs) in a device or secure multimedia card. Additionally, in embodiments of this disclosure, a "unit" may include at least one processor. In the following description of this disclosure, well-known functions or configurations are not described in detail, as such details would obscure this disclosure unnecessarily.

[0028] In the following text, for ease of explanation, this disclosure uses the terms and names defined in the 3GPP LTE standard. However, this disclosure is not limited to the stated terms and names, but may also be applied to systems conforming to other standards.

[0029] In this disclosure, for ease of explanation, the evolved Node B (eNB) can be used interchangeably with the next-generation Node B (gNB). That is, a base station (BS) described by an eNB can represent a gNB. In the following description, the term "base station" refers to an entity used to allocate resources to a user equipment (UE) and can be used interchangeably with at least one of a gNode B, eNode B, Node B, base station (BS), radio access unit, base station controller (BSC), or node on a network. The term "terminal" can be used interchangeably with a user equipment (UE), mobile station (MS), cellular phone, smartphone, computer, or multimedia system capable of performing communication functions. However, this disclosure is not limited to the foregoing examples. Specifically, this disclosure applies to 3GPP New Radio (NR) (or 5th generation (5G)) mobile communication standards. In the following description, for ease of explanation, the term eNB can be used interchangeably with the term gNB. That is, a base station interpreted as an eNB can also indicate a gNB. The term UE can also indicate a mobile phone, NB-IoT device, sensor, and other wireless communication device.

[0030] The following discussion Figures 1 to 21 The various embodiments described in this patent document to illustrate the principles of this disclosure are merely illustrative and should not be construed as limiting the scope of this disclosure in any way. Those skilled in the art will understand that the principles of this disclosure can be implemented in any suitably arranged system or apparatus.

[0031] In recent years, several broadband wireless technologies have been developed to meet the growing number of broadband subscribers and provide more and better applications and services. Second-generation wireless communication systems have been developed to provide voice services while ensuring user mobility. Third-generation wireless communication systems support not only voice services but also data services. Fourth-generation wireless communication systems have been developed in recent years to provide high-speed data services. However, currently, fourth-generation wireless communication systems cannot meet the growing demand for high-speed data services due to insufficient resources. Therefore, fifth-generation wireless communication systems (also known as next-generation radio or NR) are being developed to meet the growing demand for high-speed data services and support ultra-reliable and low-latency applications.

[0032] Fifth-generation (5G) wireless communication systems support not only lower frequency bands but also higher frequency (millimeter-wave) bands, such as the 10 GHz to 100 GHz band, to achieve higher data rates. To mitigate radio wave propagation loss and increase transmission distance, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large antenna technology are considered in 5G wireless communication systems. Furthermore, 5G wireless communication systems are expected to address diverse use cases with vastly different requirements in terms of data rate, latency, reliability, and mobility. However, the air interface design of 5G wireless communication systems is expected to be flexible enough to serve UEs with entirely different performance characteristics, depending on the use cases and market segments the UEs serve for end customers. Several exemplary use cases expected to be addressed by 5G wireless communication systems are enhanced mobile broadband (eMBB), massive machine-type communication (m-MTC), and ultra-reliable low latency communication (URLL). eMBB requirements (such as tens of Gbps data rates, low latency, and high mobility) address market segments representing regular wireless broadband subscribers who actively require internet connectivity anytime, anywhere. m-MTC requirements (such as extremely high connection density, infrequent data transmissions, ultra-long battery life, and low mobility addresses) address the market segment representing the connectivity of billions of devices envisioned for the Internet of Things (IoT) / Internet of Everything (IoE). URLL requirements (such as extremely low latency, extremely high reliability, and variable mobility) address the market segment representing industrial automation applications and vehicle-to-vehicle / vehicle-to-infrastructure communication (which is foreseeable as one of the driving forces behind autonomous vehicles).

[0033] In fifth-generation wireless communication systems operating in higher frequency (millimeter-wave) bands, UEs and gNBs use beamforming to communicate with each other. Beamforming technology is used to mitigate propagation path loss and increase propagation distance for communication at higher frequency bands. Beamforming enhances the transmit and receive performance using high-gain antennas. Beamforming can be classified into transmit (TX) beamforming performed at the transmitter and receive (RX) beamforming performed at the receiver. Generally, TX beamforming increases directivity by using multiple antennas to allow the area to be propagated to be densely located in a specific direction. In this case, the aggregation of multiple antennas can be called an antenna array, and each antenna included in the array can be called an array element. Antenna arrays can be configured in various forms, such as linear arrays, planar arrays, etc. The use of TX beamforming results in increased signal directivity, thereby increasing propagation distance. Furthermore, since the signal is transmitted almost entirely outside the directive direction, signal interference acting on another receiver is significantly reduced. The receiver can perform beamforming on the RX signal by using an RX antenna array. RX beamforming increases the strength of an RX signal transmitted in a specific direction by allowing propagation to be concentrated in that direction, and excludes signals transmitted in directions other than that specific direction from the RX signal, thus providing a blocking effect against interfering signals. By using beamforming technology, a transmitter can generate multiple transmit beam patterns in different directions. Each of these transmit beam patterns can also be referred to as a transmit (TX) beam. High-frequency wireless communication systems use multiple narrow TX beams to transmit signals in a cell, with each narrow TX beam providing coverage to a portion of the cell. The narrower the TX beam, the higher the antenna gain, and therefore the greater the propagation distance of a signal transmitted using beamforming. A receiver can also generate multiple receive (RX) beam patterns in different directions. Each of these receive patterns can also be referred to as a receive (RX) beam.

[0034] Fifth-generation wireless communication systems support independent operating modes and dual connectivity (DC). In DC, multiple Rx / Tx UEs can be configured to utilize resources provided by two different nodes (or NBs) via a non-ideal backhaul connection. One node acts as the primary node (MN), and the other as the secondary node (SN). The MN and SN are connected via a network interface, and at least the MN is connected to the core network. NR also supports multi-RAT dual connectivity (MR-DC) operation, which configures a UE in an RRC connection (RRC_CONNECTED) to utilize radio resources provided by two different schedulers located in two different nodes via a non-ideal backhaul connection, providing E-UTRA (i.e., if the node is an ng-eNB) or NR access (i.e., if the node is a gNB). In NR for a UE in an RRC connection without CA / DC configuration, there is only one serving cell, which includes the primary cell. For a UE in an RRC connection with CA / DC configuration, the term "serving cell" is used to refer to the set of cells consisting of a specific cell and all secondary cells. In NR, the term Primary Cell Group (MCG) refers to the serving cell group associated with the primary node, which includes PCells and optionally one or more SCells. In NR, the term Secondary Cell Group (SCG) refers to the serving cell group associated with the secondary node, which includes PSCells and optionally one or more SCells. In NR, a PCell (primary cell) refers to the serving cell in the MCG operating at the primary frequency, where the UE performs the initial connection establishment procedure or initiates a connection re-establishment procedure. In NR with a UE configured with CA, an Scell ​​is a cell that provides additional radio resources above a specific cell. The primary SCG cell (PSCell) refers to the serving cell in the SCG, where the UE performs random access during reconfiguration with a synchronization procedure. For dual connectivity operations, the term SpCell (i.e., specific cell) refers to either the PCell of the MCG or the PSCell of the SCG; otherwise, the term specific cell refers to the PCell.

[0035] In fifth-generation wireless communication systems, the Physical Downlink Control Channel (PDCCH) is used to schedule DL transmissions on the PDSCH and UL transmissions on the PUSCH. The downlink control information (DCI) on the PDCCH includes: downlink assignment containing at least modulation and coding formats, resource allocation, and hybrid-ARQ information related to the Downlink Shared Channel (DL-SCH); and uplink scheduling permission containing at least modulation and coding formats, resource allocation, and hybrid-ARQ information related to the UL-SCH. Besides scheduling, the PDCCH can also be used for: activating and deactivating configured PUSCH transmissions with configured permission; activating and deactivating PDSCH semi-persistent transmissions; notifying one or more UEs of slot formats; notifying one or more UEs of PRB and OFDM symbols, where the UE may assume there are no transmissions for the UE; transmitting TPC commands for the PUCCH and PUSCH; transmitting one or more TPC commands for SRS transmissions by one or more UEs; switching the active bandwidth portion of a UE; and initiating a random access procedure. Based on the corresponding search space configuration, the UE monitors the PDCCH candidate set during configured monitoring times within one or more configured control resource sets (CORESETs). A CORESET consists of a set of PRBs with a duration of 1 to 3 OFDM symbols. Within a CORESET, resource element groups (REGs) and control channel elements (CCEs) are defined, with each CCE comprising a set of REGs. Control channels are formed by aggregating CCEs. Different code rates for control channels are achieved by aggregating different numbers of CCEs. Interleaved and non-interleaved CCE-to-REG mappings are supported in the CORESET. Polarity coding is used for the PDCCH. Each resource element group carrying the PDCCH carries its own DMRS. QPSK modulation is used for the PDCCH.

[0036] In fifth-generation wireless communication systems, for each configured BWP, the gNB signals a list of search space configurations, each uniquely identified by an identifier. The gNB explicitly signals the identifier of the search space configuration, which will be used for a specific purpose, such as paging reception, SI reception, or random access response reception. In NR, the search space configuration includes monitoring-symbols-PDCCH-slot, monitoring-offset-PDCCH-slot, and monitoring-symbols-PDCCH-within-slot and duration. The UE uses the parameters PDCCH monitoring periodicity (monitoring-periodicity-PDCCH-slot), PDCCH monitoring offset (monitoring-offset-PDCCH-slot), and PDCCH monitoring mode (monitoring-symbols-PDCCH-within-slot) to determine the PDCCH monitoring timing within a slot. The PDCCH monitoring timing exists within the duration of slot "x" to x+, where the slot with the number "x" in a radio frame with the number "y" satisfies the following Equation 1: [Equation 1] (y) (Number of slots in radio frames) + x - monitoring - offset - PDCCH - slot) mod (monitoring - periodicity - PDCCH - slot) = 0.

[0037] The start symbol of the PDCCH monitoring moment in each time slot with a PDCCH monitoring moment is given by the in-slot-monitor-symbol-PDCCH. The length of the PDCCH monitoring moment (by symbol) is given in the coreset associated with the search space. The search space configuration includes identifiers of the coreset configurations associated with it. For each configured BWP, the gNB signals a list of coreset configurations, where each coreset configuration is uniquely identified by an identifier. For example, each radio frame has a duration of 10 ms. Radio frames are identified by a radio frame number or a system frame number. Each radio frame includes multiple time slots, where the number of time slots in a radio frame and the duration of the time slots depend on the subcarrier spacing. The number of time slots in a radio frame and the duration of the time slots depend on the radio frames of each supported SCS and are predefined in the NR. Each coreset configuration is associated with a list of Transmit Configuration Indicator (TCI) states. Each TCI state configures a DLRS ID (SSB or CSI RS). The gNB signals the list of TCI states corresponding to the coreset configuration via RRC signaling. One of the TCI states in the TCI state list is activated by the gNB and indicated to the UE. The TCI state indication is used by the gNB to transmit the DL TX beam of the PDCCH during the PDCCH monitoring timing in the search space (the DL TX beam is quasi-co-located (QCL) with the SSB / CSIRS of the TCI state).

[0038] In fifth-generation wireless communication systems, bandwidth adaptation (BA) is supported. With BA, the UE's receive and transmit bandwidth does not need to be as large as the cell's bandwidth and can be adjusted: bandwidth can be commanded to change (e.g., shrinking during periods of low activity to save power); its location can be moved in the frequency domain (e.g., to improve scheduling flexibility); and subcarrier spacing can be commanded to change (e.g., to allow different services). A subset of the cell's total bandwidth is called the bandwidth portion (BWP). BA is implemented by configuring a BWP for the RRC-connected UE and informing the UE which configured BWP is currently active. When BA is configured, the UE only needs to monitor the PDCCH on one active BWP; that is, it does not need to monitor the PDCCH on the entire DL frequency of the serving cell. In RRC-connected state, one or more DL and UL BWPs are configured for the UE for each configured serving cell (i.e., PCell or SCell). For an active serving cell, there will always be one active UL and DL BWP at any given time. Serving cell BWP handover is used to simultaneously activate inactive BWPs and deactivate active BWPs. BWP handover is initiated by the PDCCH indicating downlink assignment or uplink permission, and by... bwp-InactivityTimerControl is exercised either by RRC signaling or by the MAC entity itself after the random access procedure is initiated. After adding an SpCell or activating an SCell, control is exercised by… firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id The indicated DL BWP and UL BWP are active and have not received a PDCCH indicating downlink assignment or uplink clearance. The active BWP of the serving cell is indicated by RRC or PDCCH. For unpaired spectrum, the DL BWP is paired with the UL BWP, and BWP handover is shared for both UL and DL. After the BWP inactivity timer expires, the UE will switch the active DL BWP to the default DL BWP or the initial DL BWP (if the default DL BWP is not configured).

[0039] In 5G wireless communication systems, random access (RA) is supported. Random access (RA) is used to achieve uplink (UL) time synchronization. RA is used during the following actions: initial access, handover, radio resource control (RRC) connection re-establishment procedures, scheduling request transmission, secondary cell group (SCG) addition / modification, beam fault recovery, and data or control information transmissions made in UL by asynchronous UEs in RRC connection state. Several types of random access procedures are supported.

[0040] Contention-Based Random Access (CBRA): This is also known as 4-step CBRA. In this type of random access, the UE first transmits a random access preamble (also known as Msg1) and then waits for a random access response (RAR) within the RAR window. The RAR is also known as Msg2. The next-generation node B (gNB) transmits the RAR on the Physical Downlink Shared Channel (PDSCH). The PDCCH that schedules the PDSCH carrying the RAR is addressed to the RA-Radio Network Temporary Identifier (RA-RNTI). The RA-RNTI identifies the time-frequency resource (also known as the Physical RA Channel (PRACH) timing, PRACH Transmission (TX) timing, or RA Channel (RACH) timing) where the gNB detected the RA preamble. The RA-RNTI is calculated as follows: RA-RNTI = 1 + s_id + 14 t_id+14 80 f_id+14 80 8 `ul_carrier_id`, where `s_id` is the index of the first Orthogonal Frequency Division Multiplexing (OFDM) symbol of the PRACH timing, where the UE has transmitted Msg1, i.e., the RA preamble; 0 ≤ `s_id` < 14; `t_id` is the index of the first time slot of the PRACH timing (0 ≤ `t_id` < 80); `f_id` is the index of the PRACH timing within the time slot in the frequency domain (0 ≤ `f_id` < 8), and `ul_carrier_id` is the UL carrier used for Msg1 transmission (0 for normal UL (NUL) carriers and 1 for supplementary UL (SUL) carriers). The gNB can multiplex several RARs of various random access preambles detected by the gNB within the same RAR Media Access Control (MAC) Protocol Data Unit (PDU). If the RAR includes the RA preamble identifier (RAPID) of the RA preamble transmitted by the UE, then the RAR in the MAC PDU corresponds to the UE's RA preamble transmission. If no RAR corresponding to its RA preamble transmission is received during the RAR window, and the UE has not yet transmitted the RA preamble a configurable number of times (configured by the gNB in ​​the RACH configuration), the UE returns to step one, i.e., selects random access resources (preamble / RACH timing) and transmits the RA preamble. A fallback can be applied before returning to step one.

[0041] If a RAR corresponding to its RA preamble transmission is received, the UE transmits message 3 (Msg3) in the UL clearance received in the RAR. Msg3 includes messages such as RRC connection request, RRC connection re-establishment request, RRC handover confirmation, scheduling request, SI request, etc. It may include the UE identity (i.e., Cell Radio Network Temporary Identifier (C-RNTI) or System Architecture Evolution (SAE) - Temporary Mobile Subscriber Identity (S-TMSI) or a random number). After transmitting Msg3, the UE starts a contention resolution timer. While the contention resolution timer is running, if the UE receives a Physical Downlink Control Channel (PDCCH) addressed to the C-RNTI included in Msg3, the contention resolution is considered successful, the contention resolution timer stops, and the RA procedure is completed. While the contention resolution timer is running, if the UE receives a Contention Resolution MAC Control Element (CE) including the UE's contention resolution identity (the first X bits of the Common Control Channel (CCCH) Service Data Unit (SDU) transmitted in Msg3), the contention resolution is considered successful, the contention resolution timer stops, and the RA procedure is completed. If the contention resolution timer expires and the UE has not yet transmitted the RA preamble a configurable number of times, the UE returns to step one, i.e., selects random access resources (preamble / RACH timing) and transmits the RA preamble. A fallback can be applied before returning to step one.

[0042] Contention-Free Random Access (CFRA): This is also known as Traditional CFRA or 4-Step CFRA. The CFRA procedure is used for situations such as handovers requiring low latency, and early timing establishment of secondary cells (Scells). The ENB assigns a dedicated random access preamble to the UE. The UE transmits the dedicated RA preamble. The ENB transmits a RAR on the PDSCH addressed to the RA-RNTI. The RAR conveys the RA preamble identifier and timing alignment information. The RAR may also include UL clearance. The RAR is transmitted in a RAR window similar to the Contention-Based RA (CBRA) procedure. CFRA is considered successfully completed after receiving the RAR including the RA preamble identifier (RAPID) of the RA preamble transmitted by the UE. In the case of initiating RA for beam fault recovery, CFRA is considered successfully completed if a PDCCH addressed to the C-RNTI is received in the search space used for beam fault recovery. If the RAR window expires and the RA is not successfully completed, and the UE has not yet transmitted the RA preamble a configurable number of times (configured by the gNB in ​​the RACH configuration), the UE will retransmit the RA preamble.

[0043] For certain events, such as handover and beam failure recovery, if one or more dedicated preambles are assigned to the UE, the UE determines whether to transmit a dedicated or non-dedicated preamble during the first step of random access, i.e., during random access resource selection for Msg1 transmission. Typically, dedicated preambles are provided for a subset of SSB / CSI-RS. If none of the SSB / CSI RSs for which the gNB has provided contention-free random access resources (i.e., dedicated preambles / ROs) has a DL RSRP above a threshold, the UE selects a non-dedicated preamble. Otherwise, the UE selects a dedicated preamble. Therefore, during RA, one random access attempt can be CFRA, while other random access attempts can be CBRA.

[0044] Two-Step Contention-Based Random Access (2-Step CBRA): In the first step, the UE transmits a random access preamble on the PRACH and a payload (i.e., a MAC PDU) on the PUSCH. The transmission of the random access preamble and payload is also referred to as MsgA. In the second step, after the transmission of MsgA, the UE monitors for responses from the network (i.e., the gNB) within a configured window. These responses are also referred to as MsgB. If a CCCH SDU is transmitted in the MsgA payload, the UE uses the contention resolution information in the MsgB to perform contention resolution. If the contention resolution identity received in the MsgB matches the first 48 bits of the CCCH SDU transmitted in the MsgA, the contention resolution is successful. If a C-RNTI is transmitted in the MsgA payload, the contention resolution is successful if the UE receives a PDCCH addressed to the C-RNTI. If the contention resolution is successful, the random access procedure is considered to have completed successfully. Instead of the contention resolution information corresponding to the transmitted MsgA, MsgB may include backoff information corresponding to the random access preamble transmitted in MsgA. If backoff information is received, the UE transmits Msg3 and performs contention resolution using Msg4 as in the CBRA procedure. If contention resolution is successful, the random access procedure is considered to have completed successfully. If contention resolution fails during backoff (i.e., when transmitting Msg3), the UE retransmits MsgA. If the configurable window for monitoring network responses expires after the UE transmits MsgA and the UE does not receive MsgB including contention resolution or backoff information as described above, the UE retransmits MsgA. If the random access procedure is not successfully completed even after transmitting MsgA a configurable number of times, the UE backoffs to the 4-step RACH procedure, i.e., the UE only transmits the PRACH preamble.

[0045] The MsgA payload may include one or more of the following: Common Control Channel (CCCH) Service Data Unit (SDU), Dedicated Control Channel (DCCH) SDU, Dedicated Flow Channel (DTCH) SDU, Buffer Status Report (BSR) MAC Control Element (CE), Power Headroom Report (PHR) MAC CE, SSB information, C-RNTI MAC CE, or padding. MsgA may include the UE ID (e.g., Random ID, S-TMSI, C-RNTI, Recovery ID, etc.) and the preamble from the first step. The UE ID may be included in the MAC PDU of MsgA. UE IDs such as C-RNTI may be carried in the MAC CE, where the MAC CE is included in the MAC PDU. Other UE IDs (such as Random ID, S-TMSI, C-RNTI, Recovery ID, etc.) may be carried in the CCCH SDU. The UE ID may be one of the following: Random ID, S-TMSI, C-RNTI, Recovery ID, IMSI, Idle Mode ID, Inactive Mode ID, etc. The UE ID may differ in different scenarios in which the UE performs the RA procedure. When a UE performs a Re-Action (RA) after power-on (before being attached to the network), the UE ID is a random ID. When a UE performs an RA in an idle state after being attached to the network, the UE ID is the S-TMSI. If the UE has an assigned C-RNTI (e.g., in a connected state), the UE ID is the C-RNTI. When the UE is in an inactive state, the UE ID is the recovery ID. In addition to the UE ID, some additional Ctrl information can be sent in the MsgA. Control information can be included in the MAC PDU of the MsgA. Control information may include one or more of the following: connection request indication, connection recovery request indication, SI request indication, buffer status indication, beam information (e.g., one or more DL TX beam IDs or SSBIDs), beam failure recovery indication / information, data indicator, cell / BS / TRP handover indication, connection re-establishment indication, reconfiguration complete or handover complete message, etc.

[0046] Two-Step Contention-Free Random Access (2-Step CFRA): In this case, the gNB assigns a dedicated random access preamble and PUSCH resources to the UE for MsgA transmission. It may also indicate the RO (Resource Allocation) for preamble transmission. In the first step, the UE uses the contention-free random access resources (i.e., dedicated preamble / PUSCH resources / RO) to transmit the random access preamble on the PRACH and the payload on the PUSCH. In the second step, after MsgA transmission, the UE monitors the response from the network (i.e., the gNB) within a configured window. If the UE receives a PDCCH addressed to C-RNTI, the random access procedure is considered successfully completed. If the UE receives a backoff message corresponding to its transmitted preamble, the random access procedure is considered successfully completed.

[0047] For certain events, such as handover and beam failure recovery, if dedicated preambles and PUSCH resources are assigned to the UE, the UE determines whether to transmit a dedicated or non-dedicated preamble during the first step of random access, i.e., during the random access resource selection for MsgA transmissions. Typically, dedicated preambles are provided for a subset of SSB / CSI-RS. If none of the SSB / CSI-RS for which the gNB has provided contention-free random access resources (i.e., dedicated preambles / RO / PUSCH resources) has a DL RSRP above a threshold, the UE selects a non-dedicated preamble. Otherwise, the UE selects a dedicated preamble. Therefore, during the RA procedure, one random access attempt can be a 2-step CFRA, while other random access attempts can be a 2-step CBRA.

[0048] When initiating a random access procedure, the UE first selects a carrier (SUL or NUL). If the gNB explicitly signals a carrier for the random access procedure, the UE selects the signaled carrier to perform the random access procedure. If the gNB does not explicitly signal a carrier for the random access procedure; and if the serving cell for the random access procedure has a supplementary uplink configured; and if the downlink path loss reference RSRP is less than rsrp-ThresholdSSB-SUL, the UE selects the SUL carrier to perform the random access procedure. Otherwise, the UE selects the NUL carrier to perform the random access procedure. After selecting the UL carrier, the UE determines the UL and DL BWP for the random access procedure, as specified in the 3GPP standard specification. Then, the UE determines whether to perform a 2-step or 4-step RACH for this random access procedure.

[0049] - If this random access procedure is initiated by a PDCCH command, and if the ra-PreambleIndex explicitly provided by the PDCCH is not 0b000000, then the UE selects the 4-step RACH.

[0050] Otherwise, if the gNB signals a 2-step contention-free random access resource for this random access procedure, the UE selects a 2-step RACH.

[0051] Otherwise, if the gNB signals a 4-step contention-free random access resource for this random access procedure, the UE selects a 4-step RACH.

[0052] Otherwise, if the UL BWP selected for this random access procedure has only 2-step RACH resources, the UE selects 2-step RACH.

[0053] Otherwise, if the UL BWP selected for this random access procedure has only 4-step RACH resources, the UE selects 4-step RACH.

[0054] - Otherwise, if the UL BWP selected for this random access procedure is configured with 2-step and 4-step RACH resources, - If the RSRP referenced for downlink path loss is lower than the configured threshold, the UE selects a 4-step RACH. Otherwise, the UE selects a 2-step RACH.

[0055] In fifth-generation wireless communication systems, the cell broadcast synchronization signal and the node B (gNB) or base station in the PBCH block (SSB) consist of the primary synchronization signal (PSS), the secondary synchronization signal (SSS), and system information. The system information includes common parameters required for communication within the cell.

[0056] In fifth-generation wireless communication systems, RRC can be in one of the following states: RRC_IDLE, RRC_INACTIVE, or RRC_INACTIVE. When an RRC connection is established, the UE is in either the RRC_INACTIVE or RRC_INACTIVE state. If this is not the case, i.e., no RRC connection has been established, the UE is in the RRC_IDLE state. The RRC state can be further characterized as follows: During RRC idle, UE-specific DRX can be configured by the upper layer. The UE monitors short messages transmitted via DCI along with P-RNTI; monitors the paging channel used for CN paging using 5G-S-TMSI; performs neighbor cell measurements and cell (re)selection; obtains system information and can send SI requests (if configured); records available measurements performed by the UE and the location and time of UEs configured to record measurements.

[0057] During RRC inactivity, UE-specific DRX can be configured by the upper layer or by the RRC layer; the UE stores the UE inactivity AS context; the RAN-based notification area is configured by the RRC layer. The UE monitors short messages transmitted via DCI along with P-RNTI; the UE monitors paging channels used for CN paging using 5G-S-TMSI and RAN paging using full I-RNTI; the UE performs neighbor cell measurements and cell (re)selection; the UE performs RAN-based notification area updates periodically and when moving outside the configured RAN-based notification area; the UE obtains system information and can send SI requests (if configured); the UE performs recording of available measurements and the location and time of UEs configured to record measurements.

[0058] In an RRC connection, the UE stores the AS context and unicast data transmissions to / from the UE occur. The UE monitors short messages transmitted via DCI along with P-RNTI (if configured); monitors the control channel associated with the shared data channel to determine if data is scheduled for the UE; provides channel quality and feedback information; monitors the execution of neighboring cell measurements and measurement reports; and acquires system information.

[0059] In an RRC connection, the network can initiate a suspension of the RRC connection by sending an RRCRelease message with a suspension configuration. When an RRC connection is suspended, the UE stores its inactive AS context and any configurations received from the network, and transitions to an RRC inactive state. If the UE has an SCG configured, the UE releases the SCG configuration when initiating the RRC connection recovery procedure. The RRC message used to suspend the RRC connection is integrity protected and encrypted.

[0060] When a UE needs to transition from an RRC inactive state to an RRC connected state, the recovery of the suspended RRC connection is initiated by the upper layer, or by the RRC layer to perform an RNA update, or by a RAN paging from the NG-RAN. When the RRC connection is restored, the network configures the UE according to the RRC connection recovery procedure based on the stored UE inactive AS context and any RRC configuration received from the network. The RRC connection recovery procedure reactivates AS security and rebuilds the SRB and DRB. In response to a request to restore the RRC connection, the network may restore the suspended RRC connection and send the UE to RRC connected mode, or reject the restoration request and send the UE to RRC inactive mode (using a wait timer), or directly re-suspend the RRC connection and send the UE to RRC inactive mode, or directly release the RRC connection and send the UE to RRC idle mode, or instruct the UE to initiate NAS-level recovery (in which case the network sends an RRC setup message).

[0061] After initiating the recovery process, the UE: except in SIB1 In addition to providing the values ​​of the parameters, apply the default L1 parameter values ​​specified in the corresponding physical layer specification; apply the default MAC cell group configuration; apply the CCCH configuration; start timer T319; apply... SIB1 Included timeAlignmentTimerCommon Apply the default SRB1 configuration; set the variables pendingRNA- Update Set as mistake ; Initiate RRCResumeRequest Message or RRCResumeRequest1 The transmission; recovering the RRC configuration, RoHC state, stored QoS flow to DRB mapping rules, and KgNB and KRRCint keys from the stored UE inactive AS context, except for the following: masterCellGroup, mrdc-SecondaryCellGroup (if stored), and pdcp-Config; resumeMAC-I Set to the 16 least significant bits of MAC-I calculated using the following: K in the UE inactive AS context RRCint The key and the previously configured integrity protection algorithm, along with all input bits of COUNT, BEARER, and DIRECTION set to binary one; using the stored... nextHopChainingCount Value, based on the current K gNB Key or NH derived K gNB Key; Export K RRCenc Key, K RRCint Key, K UPint Key and K UPenc Key; using the configured algorithm and K RRCint Key and K UPint The key is configured to apply integrity protection to all signaling radio bearers except SRB0; that is, integrity protection can be applied to all subsequent messages received and sent by the UE. The lower layer is also configured to apply encryption to all signaling radio bearers except SRB0, using the encryption algorithm configured in this sub-clause, K. RRCenc Key and K UPenc The key, i.e., the encryption configuration, can be applied to all subsequent messages received and sent by the UE; reconstruct the PDCP entity for SRB1; restore SRB1; and transmit. RRCResumeRequest or RRCResumeRequest1 .

[0062] Figure 1 and Figure 2 An example of a BFR MAC CE according to an embodiment of the present disclosure is shown. Figure 1An example of a SCell beam fault recovery (BFR) MAC CE is shown, and this MAC entity is configured with beam fault detection (BFD) of the SCell with the highest ServCellIndex The truncated SCell BFR MAC CE is less than 8. Additionally, Figure 2 An example of an SCell BFR MACCE is shown, and the MAC entity is configured with a BFD SCell with the highest... ServCellIndex The truncated SCell BFR MAC CE is equal to or greater than 8.

[0063] Fifth-generation wireless communication systems support beam fault detection and recovery mechanisms at the UE for the serving cell. This includes beam fault detection, identification of new candidate beams, transmission of beam fault recovery requests, and monitoring of responses to beam fault recovery requests. For beam fault detection in the serving cell, the UE is configured with a set of beam fault detection RSs (based on SSB or CSI-RS) for that serving cell. The UE can periodically monitor these RSs. If the number of consecutively detected beam fault instances exceeds the configured maximum number (beamFailureInstanceMaxCount) within a configured time (beamFailureDetectionTimer), a beam fault is detected on the serving cell. A beam fault instance means that the hypothesis PDCCH BLER determined based on measurements from the beam fault detection RSs is higher than the threshold of all beam fault detection RSs. Beam fault detection can be configured for zero or one or more serving cells. In a beam fault instance, the lower layer (i.e., the PHY layer) sends an indication to the MAC layer (i.e., the MAC entity). The MAC entity in the UE configured for beam fault detection in each serving cell can perform the following operations: 1> If a beam fault instance indication has been received from the lower layer: 2> Start or restart beamFailureDetectionTimer ; 2> Make BFI counter Incrementing by 1; 2> If the BFI counter >= beamFailureInstanceMaxCount: 3> If the serving cell is a SCell: 4> Trigger beam fault recovery (BFR) for this serving cell; 3> Otherwise: 4> Initiate a random access procedure on SCell.

[0064] 1> If beamFailureDetectionTimer Expiry date; or

[0065] 1> If reconfigured by the upper layer (i.e., RRC) associated with this serving cell. beamFailureDetectionTimer , beamFailureInstanceMaxCount Or any reference signal used for beam fault detection: 2> BFI counter Set to 0.

[0066] 1> If the serving cell is SpCell and the random access procedure initiated for SpCell beam failure recovery has been successfully completed: 2> Set the BFI counter to 0; 2>Stop beamFailureRecoveryTimer (If configured); 2> It is believed that the beam fault recovery process has been successfully completed.

[0067] 1> Otherwise, if the serving cell is a SCell, and the HARQ procedure for a transmission of a BFR MAC CE 100 containing beam fault recovery information or a truncated BFR MAC CE 100 for this serving cell receives a PDCCH addressed to a C-RNTI indicating uplink clearance for the new transmission; or

[0068] 1> If SCell is disabled: 2> BFI counter Set to 0; 2> It is assumed that the beam fault recovery process has been successfully completed and all triggered BFRs for this serving cell have been cancelled.

[0069] MAC entities can: 1> If the beam fault recovery process determines that at least one BFR has been triggered and not canceled: 2> If the UL-SCH resources are available for new transmissions, and if, as a result of Logical Channel Prioritization (LCP), the UL-SCH resources can accommodate a BFR MAC CE 100 and its sub-headers: 3> Instructions for reuse and assembly processes to generate BFR MAC CE 100.

[0070] 2> Otherwise, if the UL-SCH resource is available for a new transmission, and if, as a result of LCP, the UL-SCH resource can accommodate the truncated BFR MAC CE 100 and its sub-headers: 3> Instruct the reuse and assembly process to generate the truncated BFR MAC CE 100.

[0071] 2> Otherwise: 3> For each SCell where the BFR has been triggered and not canceled, trigger the SR for SCell beam fault recovery.

[0072] When transmitting a MAC PDU, all BFRs triggered before the assembly of the MAC PDU for beam fault recovery of the SCell can be cancelled, and this PDU includes a BFR MAC CE 100 containing beam fault information for that SCell or a truncated BFR MAC CE 100.

[0073] Used for beam fault recovery process beamFailureInstanceMaxCount , beamFailureDetectionTimer and beamFailureRecoveryTimer Specific to the serving cell. A separate BFI counter is maintained for each serving cell configured with beam fault detection.

[0074] BFR's MAC CE includes: -BFR MAC CE 100; or -Truncation of BFR MAC CE 100.

[0075] BFR MAC CE 100 and truncated BFR MAC CE 100 are identified by a MAC subheader with LCID / eLCID.

[0076] Both the BFR MAC CE and the truncated BFR MAC CE have variable sizes. The BFR MAC CE and the truncated BFRMAC CE include bitmaps and based on... ServCellIndex Beam fault recovery information in ascending order, i.e., the eight-bit group of candidate beam availability indication (AC) contained in the SCell indicated in the bitmap. For BFR MAC CE 100, when a beam fault is detected in the highest SCell of that MAC entity... ServCellIndex Use a single octet bitmap when the value is less than 8 (in Figure 1 (as shown in the image), otherwise use four octets (in the image). Figure 2 (As shown in the diagram). A MAC PDU can contain at most one BFR MAC CE.

[0077] For truncated BFR MAC CE, use a single octet bitmap in the following cases, otherwise use four octets: -The highest SCell of the MAC entity that detected the beam fault. ServCellIndex Less than 8; or - When a beam fault is detected by SpCell and SpCell is indicated in the truncated BFR MAC CE, and as a result of LCP, the UL-SCH resources available for transmission cannot accommodate the truncated BFR MAC CE with four octet bitmaps and its sub-headers.

[0078] The fields in BFR MAC CE 100 and 200 are defined as follows: -SP: This field indicates beam fault detection for the SpCell of this MAC entity. The SP field is set to 1 to indicate that a beam fault is detected for the SpCell only if a BFR MAC CE or a truncated BFR MAC CE is included in the MAC PDU as part of the random access procedure; otherwise, it is set to 0. -C i (BFR MAC CE): This field indicates beam fault detection and is used for beamforming... ServCellIndex The existence of an octet containing the AC field in the SCell of i. C is set to 1. i The field indicates that a beam fault has been detected and has ServCellIndex The SCell of i contains an octet containing the AC field. C is set to 0. i The field indicates that no beam fault was detected and has ServCellIndex The SCell of i does not contain an octet containing the AC field. ServCellIndex There are octets containing the AC field in ascending order; -C i (Trunculated BFR MAC CE): This field indicates the pair with... ServCellIndex Beam fault detection for i's SCell. C set to 1. i The field indicates that a beam fault has been detected and may exist for use with ServCellIndex The octet of i's SCell contains the AC field. C is set to 0. i The field indicates that no beam fault was detected and has ServCellIndex The SCell of i does not contain an octet containing the AC field. ServCellIndex Includes octets containing the AC field in ascending order (if any). The number of included octets containing the AC field is maximized, but not exceeding the available license size; -AC: This field indicates the presence of a candidate RS ID field in this octet. If available candidateBeamRSSCellList The SS-RSRP of the SSB is higher than rsrp-ThresholdBFR SSB or candidateBeamRSSCellList The CSI-RSRP in the CSI-RS is higher than rsrp-ThresholdBFR If at least one of the CSI-RS is present, the AC field is set to 1; otherwise, it is set to 0. If the AC field is set to 1, a candidate RS ID field exists. If the AC field is set to 0, an R bit exists instead. - Candidate RS ID: This field is set to candidateBeamRSSCellListThe SS-RSRP of the SSB is higher than rsrp-ThresholdBFR The index of the SSB or candidateBeamRSSCellList The CSI-RSRP in the CSI-RS is higher than rsrp-ThresholdBFR The index of CSI-RS. This field is 6 bits long.

[0079] -R: Reserved bit for setting to 0.

[0080] Figure 3 An example wireless network according to an embodiment of this disclosure is shown.

[0081] The serving cell can support multiple transmit / receive points (TRPs) 310 and 320, and the UE 330 can be served simultaneously by multiple TRPs 310 and 320 to achieve improved data rates and reliability. In the current design, each serving cell has beam fault detection and recovery. For example, each serving cell signals a list of BFD RSs and a list of candidate beam RSs. Figure 3 As shown, if all beams of the serving cell's TRP 320 fail, the beam fault will not be detected, and therefore TRP 320 will be unable to serve UE 330 until all beams of the serving cell's TRPs fail and beam fault recovery is initiated for the serving cell. The beam fault detection and recovery process needs to be enhanced.

[0082] Beam fault detection configuration.

[0083] In one method of this disclosure, for beam fault detection in the serving cell, the gNB (in the RRCReconfiguration message) signals / transmits a beam fault detection configuration including a list of beam fault detection RSs, wherein the list may indicate the TRP associated with each RS. Each BWP (or DL ​​BWP) has this beam fault detection configuration. The parameter “trpIndex” may indicate the TRP associated with each RS. Below is an example of the case where up to two TRPs exist in the serving cell. It should be noted that if only one TRP exists in the serving cell, the parameter “trpIndex” may not be included. In an embodiment where two TRPs (TRP 0 and TRP 1) exist in the serving cell, “trpIndex” may be included for the RS associated with TRP 1, and may not be included for the RS associated with TRP 0. The absence of “trpIndex” may imply that the RS is associated with TRP 0. In embodiments where two TRPs (TRP 1 and TRP 2) exist in the serving cell, the RS associated with the second TRP may include "trpIndex", while the RS associated with the first TRP may not include "trpIndex". The absence of "trpIndex" may imply that the RS is associated with the first TRP.

[0084] [Table 1]

[0085] In the embodiment, the following can be added: radioLinkMonitoringRSPoolIndex (Also known as RS pool index / identifier or RS set index / identifier) ​​instead of trpIndex. Based on this, the UE can identify multiple sets / pools of beam fault detection RSs, where RSs in the same set / pool correspond to the same... radioLinkMonitoringRSPoolIndex / RSSetIndex / RS Pool Index The RS sets corresponding to TRP have the same radioLinkMonitoringRSPoolIndex / RSSetIndex / RS Pool Index .

[0086] In another method disclosed herein, for beam fault detection in the serving cell, the gNB can be configured with signal transmit / transmit beam fault detection, wherein a list of signal transmit BFD RSs is individually transmitted for each TRP of each BWP (or DL ​​BWP) in the serving cell. Below is an example of a case where up to two TRPs exist in the serving cell. failureDetectionResourcesToAddModList and failureDetectionResourcesToAddModList2 can indicate the lists of BFD RSs for different TRPs.

[0087] [Table 2]

[0088] In an alternative embodiment, the gNB can signal RadioLinkMonitoringConfig IE separately for different TRPs of the serving cell. For example, if there are two TRPs, RadioLinkMonitoringConfig and radioLinkMonitoringConfig1 can be signaled separately for the first TRP and the second TRP (in the RRCReconfiguration message) in the BWP-DownlinkDedicated IE of the serving cell.

[0089] Using one of the signaling methods explained above, the gNB can signal beam fault detection configurations for serving cells (in the RRCReconfiguration message) that configure multiple sets / pools of beam fault detection RSs, where each set / pool belongs to a different TRP. After receiving the beam fault detection configuration for the serving cell from the gNB according to one of the signaling methods explained above, the UE can identify the multiple sets / pools of beam fault detection RSs, where each set / pool belongs to a different TRP.

[0090] Beam fault recovery configuration.

[0091] In one method of this disclosure, for beam fault recovery, the gNB can (in the RRCReconfiguration message) signal / transmit a beam fault recovery configuration including a list of candidate beam RSs, where the TRP associated with each RS can be indicated in the list. Each BWP (or DL ​​BWP) has this configuration. The parameter “trpIndex” can indicate the TRP associated with each RS. Below is an example of the case where up to two TRPs exist in the SpCell. It should be noted that if only one TRP exists in the serving cell, the parameter “trpIndex” may not be included. In an embodiment where two TRPs (TRP0 and TRP1) exist in the serving cell, “trpIndex” can be included for the RS associated with TRP1, and may not be included for the RS associated with TRP0. The absence of “trpIndex” can imply that the RS is associated with TRP0. In embodiments where two TRPs (TRP 1 and TRP 2) exist in the serving cell, the RS associated with the second TRP may include "trpIndex", while the RS associated with the first TRP may not include "trpIndex". The absence of "trpIndex" may imply that the RS is associated with the first TRP.

[0092] [Table 3]

[0093] Table 4 below is another example of a case where there are up to two TRPs in the SCell. It should be noted that if there is only one TRP in the serving cell, the parameter "trpIndex" can be omitted.

[0094] [Table 4]

[0095] In the embodiment, the following can be added: ResourceSetIndex (or resource pool index) instead of trpIndex. Based on this, the UE can identify multiple sets / pools of beam fault recovery RSs, where RSs in the same set / pool correspond to the same ResourceSetIndex / Resource pool index. The RS sets corresponding to the TRP have the same... ResourceSetIndex / Resource pool index. In the case of SpCell, the UE can also identify the CFRA resources corresponding to each TRP.

[0096] In another method disclosed herein, for beam fault recovery, the gNB can signal a beam fault recovery configuration, wherein for each TRP of each BWP (or DL ​​BWP) of the serving cell, a list of candidate beam RSs is signaled separately. Table 5 below is an example of the case where there are up to two TRPs in the serving cell. candidateBeamRSList and candidateBeamRSList2 indicate the lists of candidate beam RSs for different TRPs.

[0097] [Table 5]

[0098] In an alternative embodiment, the gNB can signal BeamFailureRecoveryConfig IE separately for different TRPs of the serving cell. For example, if there are two TRPs, BeamFailureRecoveryConfig / BeamFailureRecoverySCellConfig and BeamFailureRecoveryConfig1 / BeamFailureRecoverySCellConfig1 can be signaled in the BWP configuration of the SpCell / SCell for the first TRP and the second TRP respectively (in the RRCReconfiguration message).

[0099] Using one of the signaling methods explained above, the gNB can signal a beam fault recovery configuration for a serving cell (in the RRCReconfiguration message) that can be configured to indicate multiple sets of candidate beam RSs, where each set can belong to a different TRP. After receiving the beam fault recovery configuration for the serving cell from the gNB according to the signaling method explained above, the UE can identify multiple sets / pools of candidate beam RSs, where each set / pool belongs to a different TRP.

[0100] Method 1: Beam fault detection and beam fault recovery triggering in the serving cell: Example 1: Figure 4 This is a flowchart illustrating beam fault detection and beam fault recovery according to embodiments of the present disclosure.

[0101] In the method disclosed herein, beam fault detection and beam fault recovery triggering of the serving cell are... Figure 4As shown in the diagram. For beam fault detection in the serving cell, in step S410, the UE can receive the beam fault detection configuration of the serving cell from the gNB, as previously explained. Each DL BWP of the serving cell has a beam fault detection configuration. In step S415, the UE can determine whether the received beam fault detection configuration for the active DL BWP includes beam fault detection RSs for multiple TRPs.

[0102] In step S420, if the beam fault detection configuration of the active DL BWP includes beam fault detection RSs for multiple TRPs, the UE detects a beam fault and triggers beam fault recovery for one or more TRPs of the serving cell, as follows: In step S425, the UE (i.e., the PHY layer in the UE) periodically measures the beam fault detection RS of the TRP of the serving cell in the beam fault detection configuration.

[0103] In step S430, if all BFD RS of the serving cell's TRP are below a threshold, or if the assumed PDCCH BLER determined based on the measurement of the beam fault detection RS is above the threshold of all beam fault detection RS of the TRP: In step S435, it is determined that a beam failure instance has occurred in the TRP, that is, the PHY layer sends a beam failure instance indication of the TRP to the MAC layer (or MAC entity).

[0104] After receiving a beam fault instance indication from the serving cell's TRP at the PHY layer In step S440, the MAC layer (or MAC entity) starts or restarts the beamFailureDetectionTimer corresponding to the TRP of the serving cell that received the beam failure instance indication from the PHY layer. The beamFailureDetectionTimer is maintained separately for each TRP of the serving cell. The value of the beamFailureDetectionTimer is signaled by the gNB. The value of the beamFailureDetectionTimer can be the same for all TRPs of the serving cell. Alternatively, the value of the beamFailureDetectionTimer can be configured separately for each TRP of the serving cell.

[0105] In step S445, the MAC layer updates the BFI counter corresponding to the TRP of the serving cell that receives the beam fault instance indication from the PHY layer. The BFI counter is maintained separately for each TRP of the serving cell.

[0106] If, for the serving cell's TRP, the BFI counter is >= beamFailureInstanceMaxCount (in step S450), then in step S455, a beam fault of the serving cell's TRP is considered detected, and beam fault recovery for the serving cell's TRP is initiated. The value of beamFailureInstanceMaxCount is transmitted by the gNB via signaling. The value of beamFailureInstanceMaxCount can be the same for all TRPs of the serving cell. Alternatively, the value of beamFailureInstanceMaxCount can be configured individually for each TRP of the serving cell.

[0107] In step S420, if the beam fault detection configuration of the active DL BWP does not include beam fault detection RSs for multiple TRPs, the UE detects a beam fault and triggers beam fault recovery, as follows: In step S460, the UE (PHY layer) periodically measures the beam fault detection RS of the serving cell in the beam fault detection configuration.

[0108] In step S465, if all BFD RS of the serving cell are below a threshold, or if the assumed PDCCH BLER determined based on the measurement of the beam fault detection RS is above the threshold of all beam fault detection RS of the serving cell: In step S470, a beam failure instance is considered to have occurred, that is, the PHY layer sends a beam failure instance indication to the MAC layer (or MAC entity).

[0109] After receiving a beam fault instance indication from the serving cell at the PHY layer, In step S475, the MAC layer starts or restarts the beamFailureDetectionTimer for the serving cell that receives the beam failure instance indication from the PHY layer. One beamFailureDetectionTimer is maintained for the serving cell.

[0110] In step S480, the MAC layer can update the BFI counter of the serving cell that receives the beam fault instance indication from the PHY layer. A BFI counter is maintained for the serving cell.

[0111] If the BFI counter is greater than or equal to beamFailureInstanceMaxCount for the serving cell (in step S485), then in step S490, it is considered that a beam fault has been detected in the serving cell, and beam fault recovery for the serving cell is initiated.

[0112] Example 2: Figure 5 This is a flowchart illustrating beam fault detection and beam fault recovery according to embodiments of the present disclosure.

[0113] In the method disclosed herein, beam fault detection and beam fault recovery triggering of the serving cell are... Figure 5 As shown in the diagram. For beam fault detection in the serving cell, in step S510, the UE can receive the beam fault detection configuration of the serving cell from the gNB, as previously explained. Each DL BWP of the serving cell has a beam fault detection configuration. In step S515, the UE can determine whether the received beam fault detection configuration for the active DL BWP includes multiple sets / pools of beam fault detection RSs.

[0114] In step S520, if the beam fault detection configuration of the active DL BWP includes multiple sets / pools of beam fault detection RSs, the UE detects a beam fault and triggers beam fault recovery for one or more TRPs (i.e., one or more sets / pools of BFD RSs) of the serving cell, as follows: In step S525, the UE (i.e., the PHY layer in the UE) periodically measures the beam fault detection RS in multiple sets / pools of the BFD RS of the serving cell in the beam fault detection configuration.

[0115] In step S530, if all BFD RSs in the set / pool of the serving cell's BFD RSs are below a threshold, or if the assumed PDCCH BLER determined based on measurements of the beam fault detection RSs is higher than the threshold of all beam fault detection RSs in the set / pool of BFD RSs: In step S535, a beam failure instance is considered to have occurred, that is, the PHY sends a beam failure instance indication of the BFDRS set / pool to the MAC layer (or MAC entity).

[0116] After receiving a beam fault instance indication from the PHY layer for the serving cell's BFD RS pool, In step S540, the MAC layer initiates or restarts the beamFailureDetectionTimer corresponding to the set / pool of BFD RSs of the serving cell that received the beam failure instance indication from the PHY. The beamFailureDetectionTimer is maintained individually for each set / pool of BFD RSs in the serving cell. The value of the beamFailureDetectionTimer is transmitted by the gNB via a signal. The value of the beamFailureDetectionTimer can be the same for all sets / pools of BFD RSs in the serving cell. Alternatively, the value of the beamFailureDetectionTimer can be configured individually for each set / pool of BFD RSs in the serving cell.

[0117] In step S545, the MAC layer updates the BFI counter corresponding to the set / pool of BFDRS of the serving cell that receives the beam fault instance indication from the PHY layer. The BFI counter can be maintained individually for each set / pool of BFDRS of the serving cell.

[0118] If, for the BFD RS set / pool of the serving cell, the BFI counter is >= beamFailureInstanceMaxCount (in step S550), then in step S555, it is considered that a beam fault has been detected in the set / pool of the serving cell's BFD RS, and beam fault recovery for the set / pool of the serving cell's BFD RS is initiated. The value of beamFailureInstanceMaxCount is transmitted by the gNB via a signal. The value of beamFailureInstanceMaxCount can be the same for all sets / pools of the serving cell's BFD RS. Alternatively, the value of beamFailureInstanceMaxCount can be configured individually for each set / pool of the serving cell's BFD RS.

[0119] In step S520, if the beam fault detection configuration does not include beam fault detection RSs for multiple sets / pools of BFD RSs, the UE detects a beam fault and triggers beam fault recovery, as follows: In step S560, the UE (PHY layer) can periodically measure the beam fault detection RS of the serving cell in the beam fault detection configuration.

[0120] In step S565, if all BFD RS of the serving cell are below the threshold, or if the assumed PDCCH BLER determined based on the measurement of the beam fault detection RS is above the threshold of all beam fault detection RS of the serving cell: In step S570, a beam failure instance is considered to have occurred, that is, the PHY layer sends a beam failure instance indication to the MAC layer.

[0121] After receiving a beam fault instance indication from the serving cell at the PHY layer, In step S575, the MAC layer starts or restarts the beamFailureDetectionTimer for the serving cell that received the beam failure instance indication from the PHY layer. One beamFailureDetectionTimer is maintained for the serving cell.

[0122] In step S580, the MAC layer updates the BFI counter (BFI_COUNTER) of the serving cell that received the beam fault instance indication from the PHY. A BFI counter is maintained for the serving cell.

[0123] If, for the serving cell, the BFI counter is >= beamFailureInstanceMaxCount (in step S585), then in step S590, it is considered that a beam fault has been detected in the serving cell, and beam fault recovery for the serving cell is initiated. The UE executes the beam fault recovery procedure for the serving cell.

[0124] Beam fault recovery process for SCell supporting multiple TRPs (Note that the embodiments disclosed herein for SCell can also be applied to SpCell): Example 1: Figure 6 and Figure 7 An enhanced format of BFR MAC CE according to an embodiment of the present disclosure is shown. Figure 6 The BFRMAC CE is shown, and the truncated BFRMAC CE with the highest ServCellIndex of the SCell configured with BFD is less than 8. Figure 7 The BFR MAC CE is shown, and the truncated BFR MAC CE with the highest ServCellIndex of the SCell configured with BFD is equal to or greater than 8.

[0125] - In some embodiments, if one or more TRPs of the SCell satisfy the BFD criterion (i.e., BFD of one or more TRPs of the SCell is detected, as previously explained), then the UE: --For the TRP of the SCell where a beam fault is detected, trigger BFR. --SR is triggered if the UL license is unavailable for transmitting a BFR MAC CE or a truncated BFR MAC CE, or if the UL license is available but cannot accommodate a BFR MAC CE and its sub-header or a truncated BFR MAC CE and its sub-header. If the UL license is available and can accommodate a (truncated) BFR MAC CE and its sub-header, a (truncated) BFR MAC CE 600 or 700 is generated and transmitted within the UL license. In an embodiment, the SR triggering, generation, and transmission of the (truncated) BFR MAC CE, as explained above, are performed only if at least one SCell where a BFR has been triggered and not canceled, and the evaluation of candidate beams in the candidate beam list of the TRP that detected the beam fault is completed. The SR configuration (PUCCH resources, SR disable timer, SR counter) of the serving cell's TRP's BFR can be configured separately from the SR configuration of the serving cell's BFR.

[0126] The enhanced format of BFR MAC CE 600 and 700 is in Figure 6 and Figure 7 As shown in the diagram. BFR MAC CE 600 and 700 can be generated by the UE (i.e., the MAC layer or MAC entity in the UE), as follows: --BFR MAC CE 600, 700 may include a bitmap, where each bit corresponds to a serving cell. The bit corresponding to the SCell of the TRP where a beam fault is detected (and completing the evaluation of candidate beams in the candidate beam list of the TRP where a beam fault is detected) is set to 1.

[0127] --Add beam fault recovery information for each faulty TRP in SCell (e.g., candidate beams available or unavailable, candidate beams (if available), TRP identification information, etc.).

[0128] --Beam fault recovery information for the TRP of the SCell where a beam fault was detected: --- Set E to 1 or 0 to indicate whether the following is beam fault recovery information for another TRP in the same serving cell. Note that if the BFR MAC CE includes beam fault recovery information for only one TRP, the E field may not be required or included in the BFR MAC CE.

[0129] ---If there are no RSs (SSB / CSI RSs) with RSRP higher than the threshold among the candidate RSs of this TRP in the serving cell that has detected a beam fault (and initiated recovery): ----Set AC=0; include TRP ID, R bit. Note that if the TRP ID is not explicitly included in the beam fault detection and recovery configuration, include the set ID, pool ID, or list ID corresponding to the different sets / pools of the BFD RS and the candidate beam RS. BFD RS set 0 / pool 0 / list 0 corresponds to candidate beam RS set 0 / pool 0 / list 0, BFD RS set 1 / pool 1 / list 1 corresponds to candidate beam RS set 1 / pool 1 / list 1. BFD RS set n / pool n / list n corresponds to candidate beam RS set n / pool n / list n.

[0130] ---otherwise: -----Set AC=1; Include candidate RS IDs, i.e., the IDs of SSB / CSIRS whose TRP is higher than the threshold for SS-RSRP / CSI-RSRP.

[0131] In an embodiment, the candidate RS ID can be an index of an entry in the candidate RS list corresponding to the SSB / CSI RS of a TRP whose SS-RSRP / CSI-RSRP is above a threshold. If the list is shared by all TRPs, the TRP can be implicitly identified. If the candidate beam RS lists are different for different TRPs, entries in multiple candidate beam RS lists can be sequentially indexed starting from the first list. In an embodiment, in addition to the candidate RS ID, the TRP ID may also be included. It should be noted that in cases where the TRP ID is not explicitly included in the beam fault detection and recovery configuration, the set ID, pool ID, or list ID corresponding to the different sets of BFD RSs and candidate beam RSs is included. BFD RS set 0 / pool 0 / list 0 corresponds to candidate beam RS set 0 / pool 0 / list 0, and BFD RS set 1 / pool 1 / list 1 corresponds to candidate beam RS set 1 / pool 1 / list 1. BFD RS set n / pool n / list n corresponds to candidate beam RS set n / pool n / list n. The bitmap fields in BFR MAC CE 600 and 700 are defined as follows: -SP: This field indicates beam fault detection for the SpCell of this MAC entity. The SP field is set to 1 to indicate that a beam fault was detected for the SpCell. Otherwise, it is set to 0. -C i (BFR MAC CE): This field indicates beam fault detection and is used for beamforming... ServCellIndex The existence of an octet containing the AC field in the SCell of i. C is set to 1. i The field indicates that a beam fault has been detected and that the evaluation of candidate beams in the candidate beam list of the TRP where the beam fault was detected has been completed, and has ServCellIndexThe SCell of i contains an octet containing the AC field. C is set to 0. i The field indicates that no beam fault was detected (or the evaluation of candidate beams in the candidate beam list for the TRP where a beam fault was detected was not completed), and has ServCellIndex The SCell of i does not contain an octet containing the AC field. ServCellIndex There are octets containing the AC field in ascending order; -C i (Trunculated BFR MAC CE): This field indicates the pair with... ServCellIndex Beam fault detection for i's SCell. C set to 1. i The field indicates that a beam fault has been detected and that the evaluation of candidate beams in the candidate beam list of the TRP for which the beam fault was detected has been completed, and that there may be a field for beams with... ServCellIndex The octet of i's SCell contains the AC field. C is set to 0. i The field indicates that no beam fault was detected (or the evaluation of candidate beams in the candidate beam list for the TRP where a beam fault was detected was not completed), and has ServCellIndex The SCell of i does not contain an octet containing the AC field. ServCellIndex Includes octets containing the AC field in ascending order (if any). The number of included octets containing the AC field is maximized, but not exceeding the available license size; In an embodiment, if the SCell is deactivated and the SCell is configured with multiple sets / pools of BFD RS (in an active DLBWP), the UE sets the BFI counter corresponding to each set / pool of BFD RS or corresponding to each TRP to zero; and cancels all triggered BFRs for the set / pool of BFD RS or TRP of this serving cell.

[0132] In an embodiment, for a serving cell, if a PDCCH addressing a C-RNTI indicating a newly transmitted uplink permission is received during a HARQ procedure for a BFR MAC CE or a truncated BFR MAC CE transmission containing beam fault recovery information for a BFD RS set / pool or TRP of the serving cell, then the UE sets the BFI counter corresponding to the BFD RS set / pool or TRP to zero and cancels all triggered BFRs for the BFD RS set / pool or TRP of the serving cell.

[0133] In an embodiment, when a MAC PDU is transmitted and this PDU includes a BFR MAC CE or a truncated BFR MAC CE containing beam fault information for the BFD RS set / pool or TRP of the SCell, all BFRs triggered for the BFD RS set / pool or TRP of the SCell can be cancelled. In an embodiment, for each pending SR not triggered according to the BSR procedure of the serving cell, the MAC entity can: If this SR is triggered by beam fault recovery of the BFD RS pool or TRP of the serving cell (or SCell) and transmits a MAC PDU, and this PDU includes a BFR MAC CE or a truncated BFR MAC CE containing beam fault recovery information of the BFD RS pool or TRP of the serving cell (or SCell); or if this SR is triggered by beam fault recovery of the BFD RS pool or TRP of the SCell and the SCell is deactivated: cancel the pending SR and stop the corresponding sr-ProhibitTimer (if running).

[0134] It should be noted that beam fault recovery of the serving cell's BFD RS pool or TRP can also be referred to as the serving cell's M-TRP BFR, the serving cell's partial BFR, or the serving cell's enhanced BFR.

[0135] Example 1A: Figure 8 and Figure 9 An enhanced format of BFR MAC CE according to an embodiment of the present disclosure is shown. Figure 8 The BFR is shown, and the truncated BFR MAC CE of the SCell configured with BFD for this MAC entity, having the highest ServCellIndex, is less than 8. Additionally, Figure 9 The BFR is shown, and the MAC entity is configured with a BFD SCell with a truncated BFR MAC CE having the highest ServCellIndex equal to or greater than 8.

[0136] - In some embodiments, if one or more sets / pools of the SCell's BFD RS meet the BFD criteria (i.e., a beam fault is detected in one or more sets / pools of the SCell's BFD RS, as previously explained), then the UE: --For one or more sets / pools of the BFD RS of a SCell that detects a beam fault, trigger BFR. --SR is triggered if the UL license is not available for transmitting a BFR MAC CE or a truncated BFR MAC CE, or if the UL license is available but cannot accommodate a BFR MAC CE and its sub-header or a truncated BFR MAC CE and its sub-header. If the UL license is available and can accommodate a (truncated) BFR MAC CE and its sub-header, then the (truncated) BFR MAC CE 800, 900 is transmitted in the UL license. In embodiments, SR triggering and the generation and transmission of the BFR MAC CE, as explained above, are performed only if at least one SCell where the BFR is triggered and not canceled is present and the evaluation of candidate beams in the candidate beam list corresponding to the set / pool of the BFD RS that detected the beam fault is completed. The SR configuration (PUCCH resources, SR disable timer, SR counter) of the BFR of the serving cell's BFD RS set / pool can be configured separately from the SR configuration of the serving cell's BFR.

[0137] The enhanced format of BFR MAC CE 800 and 900 is in Figure 8 and Figure 9 As shown in the diagram. BFR MAC CE 800 and 900 are generated by the UE (i.e., the MAC layer or MAC entity in the UE), as follows: --BFR MAC CE 800, 900 includes a bitmap where each bit corresponds to a serving cell. The bit corresponding to the SCell of the set / pool of the BFD RS that detected a beam fault (and completing the evaluation of candidate beams in the candidate beam list corresponding to the set / pool of the BFD RS that detected a beam fault) is set to 1.

[0138] --Add beam fault recovery information for each set / pool of the BFD RS that detects a beam fault (i.e., one AC octet for each set / pool of the BFD RS).

[0139] --Beam fault recovery information for BFD RS pools / cells: --- Set E to 1 or 0 to indicate whether the following is beam fault recovery information for another set / pool of BFD RSs in the same serving cell. Note that if only beam fault recovery information for one TRP needs to be included in the BFR MAC CE, the E field may not be required or included in the BFR MAC CE.

[0140] ---If there are no RSs (SSB / CSI RSs) with RSRP higher than the threshold among the candidate RSs in the set / pool of candidate RSs corresponding to the set / pool of BFD RSs of the serving cell where a beam fault was detected: ---- Set AC=0; including set / pool ID, R bits.

[0141] ---otherwise: ----Set AC=1; Include candidate RS IDs, i.e., the IDs of SSB / CSI RSs whose SS-RSRP / CSI-RSRP is higher than the threshold among the candidate RSs in the set / pool of candidate RSs corresponding to the set / pool of BFD RSs of the serving cell where a beam fault was detected. In this embodiment, the candidate RS ID can be an index of an entry in the candidate beam RS list corresponding to the SSB / CSI RS. If multiple candidate beam RS lists exist, the entries in the multiple candidate beam RS lists can be sequentially indexed starting from the first list. In this embodiment, in addition to the candidate RS ID, a set / pool ID may also be included. The set 0 / pool 0 / list 0 of the BFD RS corresponds to the set 0 / pool 0 / list 0 of the candidate beam RS, and the set 1 / pool 1 / list 1 of the BFD RS corresponds to the set 1 / pool 1 / list 1 of the candidate beam RS. The set n / pool n / list n of the BFD RS corresponds to the set n / pool n / list n of the candidate beam RS.

[0142] The bitmap fields in BFR MAC CE 800 and 900 are defined as follows: -SP: This field indicates beam fault detection for the SpCell of this MAC entity. The SP field is set to 1 to indicate that a beam fault was detected for the SpCell. Otherwise, it is set to 0. -C i (BFR MAC CE): This field indicates beam fault detection and is used for beamforming... ServCellIndex The existence of an octet containing the AC field in the SCell of i. C is set to 1. i The field indicates that a beam fault has been detected and that the evaluation of candidate beams in the candidate beam list corresponding to the set / pool of the BFD RS for which the beam fault was detected has been completed, and has ServCellIndex The SCell of i contains an octet containing the AC field. C is set to 0. i The field indicates that no beam fault was detected (or the evaluation of candidate beams in the candidate beam list corresponding to the set / pool of the BFD RS with the detected beam fault was not completed), and has ServCellIndex The SCell of i does not contain an octet containing the AC field. ServCellIndex There are octets containing the AC field in ascending order; -C i (Trunculated BFR MAC CE): This field indicates the pair with... ServCellIndex Beam fault detection for i's SCell. C set to 1. i The field indicates that a beam fault has been detected and that the evaluation of candidate beams in the candidate beam list corresponding to the set / pool of the BFD RS for which the beam fault was detected has been completed, and there may be a field for beams with... ServCellIndex The octet of i's SCell contains the AC field. C is set to 0. i The field indicates that no beam fault was detected (or the evaluation of candidate beams in the candidate beam list corresponding to the set / pool of the BFD RS with the detected beam fault was not completed), and has ServCellIndex The SCell of i does not contain an octet containing the AC field. ServCellIndex Includes octets containing the AC field in ascending order (if any). The number of included octets containing the AC field is maximized, but not exceeding the available license size; In an embodiment, if the SCell is deactivated and the SCell is configured with multiple sets / pools of BFD RS (in an active DLBWP), the UE sets the BFI counter corresponding to each set / pool of BFD RS or corresponding to each TRP to zero; and cancels all triggered BFRs for the set / pool of BFD RS or TRP of this serving cell.

[0143] In an embodiment, for a serving cell, if a PDCCH addressing a C-RNTI indicating a newly transmitted uplink permission is received during a HARQ procedure for a BFR MAC CE or a truncated BFR MAC CE transmission containing beam fault recovery information for a BFD RS set / pool or TRP of the serving cell, then the UE sets the BFI counter corresponding to the BFD RS set / pool or TRP to zero and cancels all triggered BFRs for the BFD RS set / pool or TRP of the serving cell.

[0144] In an embodiment, when a MAC PDU is transmitted and this PDU includes a BFR MAC CE or a truncated BFR MAC CE containing beam fault information of the BFD RS set / pool or TRP of the SCell, all BFRs triggered for the BFD RS set / pool or TRP of the SCell can be cancelled.

[0145] In this embodiment, for each pending SR not triggered according to the BSR procedure of the serving cell, the MAC entity may: If this SR is triggered by beam fault recovery of the BFD RS pool or TRP of the serving cell (or SCell) and transmits a MAC PDU, and this PDU includes a BFR MAC CE or a truncated BFR MAC CE containing beam fault recovery information of the BFD RS pool or TRP of the serving cell (or SCell); or if this SR is triggered by beam fault recovery of the BFD RS pool or TRP of the SCell and the SCell is deactivated: cancel the pending SR and stop the corresponding sr-ProhibitTimer (if running).

[0146] It should be noted that beam fault recovery of the serving cell's BFD RS pool or TRP can also be referred to as the serving cell's M-TRP BFR, the serving cell's partial BFR, or the serving cell's enhanced BFR.

[0147] Example 2: Figure 10 and Figure 11 An enhanced format of BFR MAC CE according to an embodiment of the present disclosure is shown. Figure 10 The BFR is shown, and the truncated BFR MACCE of the SCell configured with BFD for this MAC entity, having the highest ServCellIndex, is less than 8. Additionally, Figure 11 The BFR is shown, and the MAC entity is configured with a BFD SCell with a truncated BFR MAC CE having the highest ServCellIndex equal to or greater than 8.

[0148] - In some embodiments, if the TRP of the SCell meets the BFD criterion (i.e., a beam fault is detected in the TRP of the SCell and recovery is initiated, as previously explained), then the UE: --Trigger BFR for TRP of SCell - If the UL license is not available for transmitting a BFR MAC CE or a truncated BFR MAC CE, an SR is triggered; or if the UL license is available but cannot accommodate a BFR MAC CE and its sub-headers or a truncated BFR MAC CE and its sub-headers, an SR is triggered. If the UL license is available and can accommodate a (truncated) BFR MAC CE and its sub-headers, -- transmit BFR MAC CE 1000 or 1100 within the UL license.

[0149] In this embodiment, the SR triggering and the generation and transmission of the BFR MAC CE, as explained above, are performed only if at least one SCell where the BFR is triggered and not canceled, and the evaluation of candidate beams in the candidate beam list of the TRP that detected the beam fault is completed. The SR configuration (PUCCH resources, SR disable timer, SR counter) of the BFR of the serving cell's TRP can be configured separately from the SR configuration of the serving cell's BFR.

[0150] Enhanced formats for BFR MAC CE 1000 and 1100 are available in... Figure 10 and Figure 11 As shown in the diagram. BFR MAC CE 1000 and 1100 are generated by the UE (i.e., the MAC layer), as follows: ---BFR MAC CE 1000, 1100 include a bitmap, where each bit corresponds to a serving cell. The bit corresponding to the SCell of the TRP where a beam fault is detected is set to 1.

[0151] ---Indicates that the BFR is for the serving cell's TRP (with T=1 set).

[0152] ---If there are no RSs (SSB / CSI RSs) with RSRPs higher than the threshold among the RSs of the TRPs initiating beam fault recovery in the SCell, then indicate which TRP is faulty in the BFR MAC CE. (AC=0, T=1, TRP ID, R bit)

[0153] ---Otherwise, include the candidate RS ID of the TRP in the BFR MAC CE. (AC=1, T=1, candidate RS ID)

[0154] ---The candidate RS ID is the index of an entry in the candidate RS list corresponding to the SSB / CSI RS of a TRP whose SS-RSRP / CSI-RSRP is above a threshold. The TRP can be implicitly identified because the list is shared by all TRPs. If the candidate beam RS lists differ for different TRPs, entries in multiple candidate beam RS lists can be sequentially indexed starting from the first list. In this embodiment, in addition to the candidate RS ID, the TRP ID is also included (i.e., AC=1, T=1, candidate RS ID, TRP ID).

[0155] In an alternative embodiment, the BFR MAC CE includes: - A bitmap, where each bit corresponds to a serving cell, with the bit corresponding to the serving cell of the TRP where a beam fault is detected set to 1.

[0156] - If there is at least one RS (SSB / CSI RS) with an RSRP higher than the threshold among the candidate beam RSs in the set or pool of the SCell that detected the beam fault and initiated recovery, then AC=1, candidate RS ID, TRP ID, zero or more R bits.

[0157] - If there is no RS (SSB / CSI RS) with RSRP higher than the threshold among the candidate beam RS in the set or pool of the SCell that detected the beam fault and initiated recovery, then AC=0, TRP ID, and zero or more R bits.

[0158] - The MAC subheader of the BFR MAC CE includes a reserved LCID, which is the BFR MAC CE of the BFR used for the TRP of the serving cell. This LCID is different from the LCID included in the MAC subheader of the BFR MAC CE of the serving cell.

[0159] - In some embodiments, if all TRPs of the SCell meet the BFR criterion, then the UE: --For beam fault recovery of this SCell, trigger BFR.

[0160] - An SR is triggered if the UL license is not available for transmitting a BFR MAC CE or a truncated BFR MAC CE, or if the UL license is available but cannot accommodate a BFR MAC CE and its header or a truncated BFR MAC CE and its sub-headers. An SR is triggered if the UL license is available and can accommodate a (truncated) BFR MAC CE and its header. --BFR MAC CE 1000, 1100 are transmitted under UL license. In the embodiment, SR triggering and the generation and transmission of BFR MAC CE as explained above are performed only if at least one SCell where the BFR is triggered and not canceled is present and the evaluation of candidate beams in the candidate beam list of the TRP that detected the beam fault is completed.

[0161] Enhanced formats for BFR MAC CE 1000 and 1100 are available in... Figure 10 and Figure 11 As shown in the diagram. BFR MAC CE 1000 and 1100 are generated by the UE (i.e., the MAC layer), as follows: ---BFR MAC CE 1000, 1100 include a bitmap, where each bit corresponds to a serving cell. The bit corresponding to the SCell where a beam fault is detected is set to 1.

[0162] ---Indicates that BFR is not for TRP (set T=0), that is, it is for the serving cell.

[0163] ---If there are no RSs (SSB / CSI RSs) with RSRP higher than the threshold in the candidate beam RS list of the SCell initiating beam fault recovery.

[0164] ----AC=0, T=0, R bit. In the embodiment, T can be an R bit set to 0.

[0165] ---Otherwise, include RS ID in BFR MAC CE 1000, 1100

[0166] ----AC=1, T=0, candidate RS ID. In this embodiment, T can be an R bit set to 0.

[0167] The bitmap fields in BFR MAC CE 1000 and 1100 are defined as follows: -SP: This field indicates beam fault detection for the SpCell of this MAC entity. The SP field is set to 1 to indicate that a beam fault was detected for the SpCell. Otherwise, it is set to 0. -C i (BFR MAC CE): This field indicates beam fault detection and is used for beamforming... ServCellIndex The existence of an octet containing the AC field in the SCell of i. C is set to 1. i The field indicates that a beam fault has been detected and that the evaluation of candidate beams in the candidate beam list of the TRP where the beam fault was detected has been completed, and has ServCellIndex The SCell of i contains an octet containing the AC field. C is set to 0. i The field indicates that no beam fault was detected (or the evaluation of candidate beams in the candidate beam list for the TRP where a beam fault was detected was not completed), and has ServCellIndex The SCell of i does not contain an octet containing the AC field. ServCellIndex There are octets containing the AC field in ascending order; -C i (Trunculated BFR MAC CE): This field indicates beam fault detection for an SCell with ServCellIndex i. C set to 1 i The field indicates that a beam fault has been detected and that the evaluation of candidate beams in the candidate beam list of the TRP for which the beam fault was detected has been completed, and that there may be a field for beams with... ServCellIndex The octet of i's SCell contains the AC field. C is set to 0. iThe field indicates that no beam fault was detected (or the evaluation of candidate beams in the candidate beam list for the TRP where a beam fault was detected was not completed), and has ServCellIndex The SCell of i does not contain an octet containing the AC field. ServCellIndex Includes octets containing the AC field in ascending order (if any). The number of included octets containing the AC field is maximized, but not exceeding the available license size; In an embodiment, if the SCell is deactivated and the SCell is configured with multiple sets / pools of BFD RS (in an active DLBWP), the UE sets the BFI counter corresponding to each set / pool of BFD RS or corresponding to each TRP to zero; and cancels all triggered BFRs for the set / pool of BFD RS or TRP of this serving cell.

[0168] In an embodiment, for a serving cell, if a PDCCH addressing a C-RNTI indicating a newly transmitted uplink permission is received during a HARQ procedure for a BFR MAC CE or a truncated BFR MAC CE transmission containing beam fault recovery information for a BFD RS set / pool or TRP of the serving cell, then the UE sets the BFI counter corresponding to the BFD RS set / pool or TRP to zero and cancels all triggered BFRs for the BFD RS set / pool or TRP of the serving cell.

[0169] In an embodiment, when a MAC PDU is transmitted and this PDU includes a BFR MAC CE or a truncated BFR MAC CE containing beam fault information of the BFD RS set / pool or TRP of the SCell, all BFRs triggered for the BFD RS set / pool or TRP of the SCell can be cancelled.

[0170] In this embodiment, for each pending SR not triggered according to the BSR procedure of the serving cell, the MAC entity may: If this SR is triggered by beam fault recovery of the BFD RS pool or TRP of the serving cell (or SCell) and transmits a MAC PDU, and this PDU includes a BFR MAC CE or a truncated BFR MAC CE containing beam fault recovery information of the BFD RS pool or TRP of the serving cell (or SCell); or if this SR is triggered by beam fault recovery of the BFD RS pool or TRP of the SCell and the SCell is deactivated: cancel the pending SR and stop the corresponding sr-ProhibitTimer (if running).

[0171] It should be noted that beam fault recovery of the serving cell's BFD RS pool or TRP can also be referred to as the serving cell's M-TRP BFR, the serving cell's partial BFR, or the serving cell's enhanced BFR.

[0172] Example 2A: Figure 12 and Figure 13 An enhanced format of BFR MAC CE according to an embodiment of the present disclosure is shown. Figure 12 The BFR is shown, and the truncated BFR MACCE of the SCell configured with BFD for this MAC entity, having the highest ServCellIndex, is less than 8. Additionally, Figure 13 The BFR is shown, and the MAC entity is configured with a BFD SCell with a truncated BFR MAC CE having the highest ServCellIndex equal to or greater than 8.

[0173] - In some embodiments, if the set / pool of BFD RSs of SCell meets the BFD criterion (i.e., the BFD RSs in the set / pool of BFD RSs based on SCell detect a beam fault and initiate recovery, as previously explained), then the UE: -- Trigger BFR for the collection / pool of BFD RS for SCell; - An SR is triggered if the UL license is unavailable for transmitting a BFR MAC CE or a truncated BFR MAC CE, or if the UL license is available but cannot accommodate a BFR MAC CE and its header or a truncated BFR MAC CE and its sub-headers. An SR is triggered if the UL license is available and can accommodate a (truncated) BFR MAC CE and its header; and --BFR MAC CE 1200, 1300 are transmitted under UL license. In this embodiment, SR triggering and BFR MAC CE generation and transmission, as explained above, are performed only if at least one SCell where a BFR is triggered and not canceled, and the evaluation of candidate beams in the candidate beam list corresponding to the set / pool of the BFD RS that detected a beam fault, is completed. The SR configuration (PUCCH resources, SR disable timer, SR counter) of the BFR of the set / pool of the serving cell's BFD RS can be configured separately from the SR configuration of the serving cell's BFR.

[0174] The enhanced format of BFR MAC CE 1200 and 1300 is in Figure 12 and Figure 13 As shown in the diagram. BFR MAC CE 1200 and 1300 are generated by the UE (i.e., the MAC layer), as follows: ---BFR MAC CE 1200, 1300 include a bitmap, where each bit corresponds to a serving cell. The bit corresponding to the SCell where a beam fault is detected is set to 1.

[0175] ---Indicates that a beam fault has been detected in one of the multiple collections / pools of BFD RS based on BFD RS (set T=1).

[0176] ---If there are no RSs (SSB / CSI RSs) with RSRP higher than the threshold among the candidate beam RSs in the set / pool of the SCell that detected a beam fault and initiated recovery, then the set / pool based on the BFD RS that detected the beam fault is indicated in the BFR MAC CE. (AC=0, T=1, set / pool ID, R bit).

[0177] ---Otherwise, include the candidate RS ID corresponding to that set / pool in the BFR MAC CE. (AC=1, T=1, candidate RSID).

[0178] ---The candidate RS ID is the index of an entry in the candidate RS list corresponding to the SSB / CSI RS of a set / pool whose SS-RSRP / CSI-RSRP is above a threshold. If the list is shared by all sets / pools, the set / pool can be implicitly identified. In this embodiment, a set / pool ID is also included.

[0179] In an alternative embodiment, the BFR MAC CE includes: - A bitmap, where each bit corresponds to a serving cell, and the bit corresponding to the serving cell where a beam fault is detected is set to 1.

[0180] If at least one RS (SSB / CSI RS) with an RSRP higher than the threshold exists among the candidate beam RSs in the set or pool of the SCell that detects a beam fault and initiates recovery, then AC=1, candidate RS ID, set / pool ID, zero or more R bits.

[0181] - If there is no RS (SSB / CSI RS) with RSRP higher than the threshold among the candidate beam RS of the set or pool of the SCell that detected the beam fault and initiated recovery, then AC=0, set / pool ID, and zero or more R bits.

[0182] - The MAC subheader of the BFR MAC CE includes a reserved LCID, which is the BFR MAC CE for the BFR of the serving cell's set / pool. This LCID is different from the LCID included in the MAC subheader of the BFR MAC CE for the serving cell's BFR.

[0183] - In some embodiments, if all sets / pools of SCell's BFD RS meet the BFR criterion: --For this SCell, trigger SCell BFR.

[0184] - An SR is triggered if the UL license is not available for transmitting a BFR MAC CE or a truncated BFR MAC CE, or if the UL license is available but cannot accommodate a BFR MAC CE and its header or a truncated BFR MAC CE and its sub-headers. An SR is triggered if the UL license is available and can accommodate a (truncated) BFR MAC CE and its header. - Launch BFR MAC CE 1200, 1300 under UL license.

[0185] In the embodiment, the SR triggering and the generation and transmission of the BFR MAC CE as explained above are performed only if at least one SCell is triggered and not canceled and the evaluation of the candidate beams in the candidate beam list corresponding to the set / pool of the BFD RS that detected the beam fault is completed.

[0186] The enhanced format of BFR MAC CE 1200 and 1300 is in Figure 12 and Figure 13 As shown in the diagram. BFR MAC CE 1200 and 1300 are generated by the UE (i.e., the MAC layer), as follows: ---BFR MAC CE 1200, 1300 include a bitmap, where each bit corresponds to a serving cell. The bit corresponding to the SCell where a beam fault is detected is set to 1.

[0187] --- Indicates that BFR is not for a specific set / pool (set T=0).

[0188] ---If there are no RSs (SSB / CSI RSs) with RSRP higher than the threshold in the candidate beam RS list of the SCell that initiates beam fault recovery.

[0189] ----AC=0, T=0, R bit. In the embodiment, T can be an R bit set to 0.

[0190] ---Otherwise, include the RS ID in BFR MAC CE 1200, 1300.

[0191] ----AC=1, T=0, candidate RS ID. In this embodiment, T can be an R bit set to 0.

[0192] The bitmap fields in BFR MAC CE 1200 and 1300 are defined as follows: -SP: This field indicates beam fault detection for the SpCell of this MAC entity. The SP field is set to 1 to indicate that a beam fault was detected for the SpCell. Otherwise, it is set to 0. -C i (BFR MAC CE): This field indicates beam fault detection and is used for beamforming... ServCellIndex The existence of an octet containing the AC field in the SCell of i. C is set to 1. i The field indicates that a beam fault has been detected and that the evaluation of candidate beams in the candidate beam list corresponding to the set / pool of the BFD RS for which the beam fault was detected has been completed, and has ServCellIndex The SCell of i contains an octet containing the AC field. C is set to 0. i The field indicates that no beam fault was detected (or the evaluation of candidate beams in the candidate beam list corresponding to the set / pool of the BFD RS with the detected beam fault was not completed), and has ServCellIndex The SCell of i does not contain an octet containing the AC field. ServCellIndex There are octets containing the AC field in ascending order; -C i (Trunculated BFR MAC CE): This field indicates the pair with... ServCellIndex Beam fault detection for i's SCell. C set to 1. i The field indicates that a beam fault has been detected and that the evaluation of candidate beams in the candidate beam list corresponding to the set / pool of the BFD RS for which the beam fault was detected has been completed, and there may be a field for beams with... ServCellIndex The octet of i's SCell contains the AC field. C is set to 0. i The field indicates that no beam fault was detected (evaluation of candidate beams in the candidate beam list corresponding to the set / pool of the BFD RS for which a beam fault was detected was not completed), and has ServCellIndex The SCell of i does not contain an octet containing the AC field. ServCellIndex Include octets containing the AC field in ascending order (if they exist). The number of octets containing the AC field included is maximized, but does not exceed the available license size.

[0193] In an embodiment, if the SCell is deactivated and the SCell is configured with multiple sets / pools of BFD RS (in an active DLBWP), the UE sets the BFI counter corresponding to each set / pool of BFD RS or corresponding to each TRP to zero; and cancels all triggered BFRs for the set / pool of BFD RS or TRP of this serving cell.

[0194] In an embodiment, for a serving cell, if a PDCCH addressing a C-RNTI indicating a newly transmitted uplink permission is received during a HARQ procedure for a BFR MAC CE or a truncated BFR MAC CE transmission containing beam fault recovery information for a BFD RS set / pool or TRP of the serving cell, then the UE sets the BFI counter corresponding to the BFD RS set / pool or TRP to zero and cancels all triggered BFRs for the BFD RS set / pool or TRP of the serving cell.

[0195] In an embodiment, when a MAC PDU is transmitted and this PDU includes a BFR MAC CE or a truncated BFR MAC CE containing beam fault information of the BFD RS set / pool or TRP of the SCell, all BFRs triggered for the BFD RS set / pool or TRP of the SCell can be cancelled.

[0196] In an embodiment, for each pending SR not triggered according to the serving cell's BSR procedure, the MAC entity may: if the SR is triggered by beam fault recovery of the serving cell's (or SCell's) BFD RS pool or TRP and transmit a MAC PDU and the PDU includes a BFR MAC CE or a truncated BFR MAC CE containing beam fault recovery information of the serving cell's (or SCell's) BFD RS pool or TRP; or if the SR is triggered by beam fault recovery of the SCell's BFD RS pool or TRP and the SCell is deactivated: cancel the pending SR and stop the corresponding sr-ProhibitTimer (if running).

[0197] It should be noted that beam fault recovery of the serving cell's BFD RS pool or TRP can also be referred to as the serving cell's M-TRP BFR, the serving cell's partial BFR, or the serving cell's enhanced BFR.

[0198] Beam fault recovery process for SpCell supporting multiple TRPs: Example 1: - In some embodiments, if a beam fault of the TRP of the SpCell is detected, as previously explained, the UE initiates beam fault recovery of the TRP of the SpCell.

[0199] -- Trigger random access on SpCell.

[0200] ---If at least one RS (SSB / CSI RS) with an RSRP higher than a threshold is present among the candidate beam RSs associated with the TRP of the SpCell that initiated beam fault recovery, then CFRA is performed.

[0201] --Otherwise, UE: ---Execute CBRA.

[0202] --- Generate the BFR MAC CE. The BFR MAC CE includes a bitmap, where each bit corresponds to the serving cell. Set the bit corresponding to the SpCell to 1.

[0203] ---Indicate which TRP of SpCell failed in the BFR MAC CE. For example, you can use Figure 6 and Figure 7 The formats shown are those of BFR MAC CE 600 and 700, as well as other formats explained in Example 1 of the beam fault recovery process for a SCell supporting multiple TRPs. The BFR MAC CE includes the TRP ID of the TRP that detected the beam fault.

[0204] - In some embodiments, otherwise, if a beam fault is detected in all TRPs of the SpCell, as previously explained, the UE initiates beam fault recovery for the SpCell: -- Trigger random access on SpCell.

[0205] ---If there is at least one RS (SSB / CSI RS) in the list of candidate beam RSs in SpCell with an RSRP higher than the threshold, then CFRA is performed.

[0206] --Otherwise, UE: ---Execute CBRA.

[0207] ---Generate BFR MAC CE.

[0208] The BFR MAC CE includes a bitmap, where each bit corresponds to the serving cell. The bit corresponding to the SpCell (SP bit) is set to 1.

[0209] ----In this embodiment, beam fault recovery information for SpCell is not included.

[0210] In an alternative embodiment, beam fault recovery information for the failed TRP may be included. For example, it can be used... Figure 6 and Figure 7 The format shown in BFR MAC CE 600 and 700 indicates beam fault recovery information. This can be used in conjunction with... Figure 6 and Figure 7 The fields are set in a similar manner to those used for SCell BFR.

[0211] It should be noted that beam fault recovery of the serving cell's BFD RS pool or TRP can also be referred to as the serving cell's M-TRP BFR, the serving cell's partial BFR, or the serving cell's enhanced BFR.

[0212] Example 1A: - In some embodiments, if a beam fault of the pool / set of the BFD RS of the SpCell is detected, as previously explained, the UE initiates beam fault recovery of the pool / set of the BFD RS: -- Trigger random access on SpCell.

[0213] ---If there is at least one RS (SSB / CSI RS) with an RSRP higher than the threshold among the candidate beam RSs corresponding to the set / pool of the BFD RS of the SpCell that initiates beam fault recovery, then CFRA is performed.

[0214] --Otherwise, UE: ---Execute CBRA.

[0215] --- Generate the BFR MAC CE. The BFR MAC CE includes a bitmap, where each bit corresponds to the serving cell. Set the bit corresponding to the SpCell (SP bit) to 1.

[0216] ---In BFR MAC CE, indicate the set / pool based on the BFD RS that detected the beam fault. For example, it can be used... Figure 8 and Figure 9 The formats shown are those of BFR MAC CE 800 and 900, as well as other formats explained in Example 1A of the beam fault recovery process for SCells supporting multiple TRPs. The BFR MAC CE includes the set / pool ID of the set in which beam faults were detected.

[0217] - In some embodiments, otherwise, if a beam fault is detected in all sets / pools of the SpCell's BFD RS, as previously explained, the UE initiates SpCell beam fault recovery: -- Trigger random access on SpCell.

[0218] ---If there is at least one RS (SSB / CSI RS) in the list of candidate beam RSs in SpCell with an RSRP higher than the threshold, then CFRA is performed.

[0219] --otherwise

[0220] ---Execute CBRA.

[0221] ---Generate BFR MAC CE.

[0222] The BFR MAC CE includes a bitmap, where each bit corresponds to the serving cell. The bit corresponding to the SpCell (SP bit) is set to 1.

[0223] ----In this embodiment, beam fault recovery information for SpCell is not included.

[0224] In an alternative embodiment, beam fault recovery information may be included for the failed TRP (i.e., the set / pool / list of BFD RSs that detected beam faults). For example, beam fault recovery information may be used. Figure 8 and Figure 9 The formats shown are those of BFR MAC CE 800 and 900, as well as other formats explained in Embodiment 1A of the beam fault recovery process for SCells supporting multiple TRPs, to indicate beam fault recovery information. This can be done in conjunction with... Figure 8 and Figure 9 The fields are set in a similar manner to those used for SCell BFR.

[0225] It should be noted that beam fault recovery of the serving cell's BFD RS pool or TRP can also be referred to as the serving cell's M-TRP BFR, the serving cell's partial BFR, or the serving cell's enhanced BFR.

[0226] Example 2: - In some embodiments, if a beam fault is detected in the TRP of the SpCell, as previously explained, then the UE: --Trigger BFR for TRP of SCell.

[0227] - An SR is triggered if the UL license is not available for transmitting a BFR MAC CE or a truncated BFR MAC CE, or if the UL license is available but cannot contain a BFR MAC CE and its sub-headers or a truncated BFR MAC CE and its sub-headers.

[0228] --If UL license is available and can accommodate (truncated) BFR MAC CE and its sub-headers, then transmit (truncated) BFR MAC CE with UL license.

[0229] In this embodiment, the SR triggering and the generation and transmission of the BFR MAC CE, as explained above, are performed only if at least one service is triggered and not canceled and the evaluation of candidate beams in the candidate beam list of the TRP that detected the beam fault is completed.

[0230] Enhanced formats for BFR MAC CE 1000 and 1100 are available in... Figure 10 and Figure 11 As shown in the image. The BFR MAC CE is generated as follows: ---Indicates that BFR is for TRP (set T=1).

[0231] ---If there are no RSs (SSB / CSI RSs) with RSRPs higher than the threshold among the RSs of the TRPs initiating beam fault recovery in the SPCell, then indicate which TRP is faulty in the BFR MAC CE. (AC=0, T=1, TRP ID, R bit).

[0232] ---Otherwise: Include the RS ID of the TRP in the BFR MAC CE. (AC=1, T=1, candidate RS ID)

[0233] ---In an embodiment, the candidate RS ID can be an index of an entry in the candidate RS list corresponding to the SSB / CSIRS of a TRP whose SS-RSRP / CSI-RSRP is above a threshold. If the list is shared by all TRPs, the TRP can be implicitly identified. If the candidate beam RS lists are different for different TRPs, entries in multiple candidate beam RS lists can be sequentially indexed starting from the first list. In an embodiment, in addition to the candidate RS ID, the TRP ID may also be included. It should be noted that in cases where the TRP ID is not explicitly included in the beam fault detection and recovery configuration, the set ID or pool ID or list ID corresponding to the different sets of BFD RSs and candidate beam RSs is included. BFD RS set 0 / pool 0 / list 0 corresponds to candidate beam RS set 0 / pool 0 / list 0, and BFD RS set 1 / pool 1 / list 1 corresponds to candidate beam RS set 1 / pool 1 / list 1.

[0234] In an alternative embodiment, the BFR MAC CE includes: - A bitmap, where each bit corresponds to a serving cell, and the bit corresponding to the SpCell where a beam fault is detected is set to 1.

[0235] If, among the candidate beam RSs of the TRP of the SpCell that detects a beam fault and initiates recovery, there is at least one RS (SSB / CSI RS) with an RSRP higher than the threshold, then AC=1, candidate RS ID, TRP ID, zero or more R bits.

[0236] - If there is no RS (SSB / CSI RS) with an RSRP higher than the threshold among the candidate beam RS of the SpCell that detects a beam fault and initiates recovery, then AC=0, TRP ID, and zero or more R bits.

[0237] - The MAC subheader of the BFR MAC CE includes a reserved LCID, which is the BFR MAC CE of the BFR used for the TRP of the serving cell. This LCID is different from the LCID included in the MAC subheader of the BFR MAC CE of the serving cell.

[0238] - In some embodiments, otherwise, if a beam fault is detected in all TRPs of the SpCell, as previously explained, the UE initiates beam fault recovery for the SpCell: -- Trigger random access on SpCell.

[0239] ---If there is at least one RS (SSB / CSI RS) in the list of candidate beam RSs in SpCell with an RSRP higher than the threshold, then CFRA is performed.

[0240] --Otherwise, UE: ---Execute CBRA.

[0241] ---Generate BFR MAC CE.

[0242] The BFR MAC CE includes a bitmap, where each bit corresponds to the serving cell. The bit corresponding to the SpCell is set to 1.

[0243] ----In this embodiment, beam fault recovery information for SpCell is not included.

[0244] In an alternative embodiment, beam fault recovery information for the failed TRP may be included. For example, it can be used... Figure 6 and Figure 7 The format shown in BFR MAC CE 600 and 700 indicates beam fault recovery information. This can be used in conjunction with... Figure 6 and Figure 7 The fields are set in a manner similar to those used for SCell BFR and other formats as explained in Example 1 of the beam fault recovery process for SCells supporting multiple TRPs.

[0245] It should be noted that, in the embodiments, even in the case of CFRA, a BFR MAC CE can be generated and transmitted in MsgA or Msg3 to include BFR information for another TRP or both TRPs.

[0246] In an embodiment, for the BFR of a TRP or BFD RS set / pool of SpCell, if the HARQ procedure for transmitting a BFR MAC CE or a truncated BFR MAC CE containing beam fault recovery information of the BFD RS set / pool or TRP of this serving cell receives a PDCCH addressed to a C-RNTI indicating a newly transmitted uplink permission, then the UE sets the BFI counter corresponding to the BFD RS set / pool or TRP to zero, cancels all triggered BFRs of the BFD RS set / pool or TRP of this serving cell, and considers the BFR of the TRP or BFD RS set / pool of SpCell to have been successfully completed.

[0247] In an embodiment, when a MAC PDU is transmitted and this PDU includes a BFR MAC CE or a truncated BFR MAC CE containing beam fault information of the BFD RS set / pool or TRP of the SPCell, all BFRs triggered for the BFD RS set / pool or TRP of the SPCell can be cancelled.

[0248] In this embodiment, for each pending SR not triggered according to the BSR procedure of the serving cell, the MAC entity may: If this SR is triggered by beam fault recovery of the BFD SR pool or TRP of the serving cell (or SCell), and transmits a MAC PDU and this PDU includes a BFR MAC CE or a truncated BFR MAC CE containing beam fault information of the BFD SR pool or TRP of the serving cell (or SCell); It should be noted that beam fault recovery of the serving cell's BFD RS pool or TRP can also be referred to as the serving cell's M-TRP BFR, the serving cell's partial BFR, or the serving cell's enhanced BFR.

[0249] Example 2A: - In some embodiments, if a beam fault is detected in the pool / collection of the SpCell's BFD RS, as previously explained, then the UE: -- Trigger BFR for the set / pool of BFD RS for SpCell.

[0250] An SR is triggered if the UL license is not available for transmitting a BFR MAC CE or a truncated BFR MAC CE, or if the UL license is available but cannot accommodate a BFR MAC CE and its header or a truncated BFR MAC CE and its sub-headers. A (truncated) BFR MAC CE and its header can be accommodated.

[0251] --If UL licensing is available and can accommodate (truncated) BFR MAC CE and its header, then transmit the BFR MAC CE with UL licensing. Enhanced formats for BFR MAC CE 1200 and 1300 are available in... Figure 12 and Figure 13 As shown in the image. The BFR MACCE is generated as follows: ---Indicates that a beam fault has been detected in one of the multiple collections / pools of BFD RS (set T=1).

[0252] ---If there is no RS (SSB / CSI RS) with an RSRP higher than the threshold among the candidate RSs corresponding to the set / pool that detected the beam fault and initiated recovery, then the set / pool that detected the beam fault and initiated beam fault recovery is indicated in the BFR MAC CE. (AC=0, T=1, set ID, R bit).

[0253] ---Otherwise, the BFR MAC CE includes the RS ID of the candidate RS from the candidate beam RS of the set / pool where a beam fault was detected. (AC=1, T=1, candidate RS ID)

[0254] ---The candidate RS ID is an index of an entry in the candidate RS list. In an embodiment, the candidate RS ID can be an index of an entry in the candidate RS list corresponding to the SSB / CSI RS of a TRP whose SS-RSRP / CSI-RSRP is above a threshold. If the list is shared by all TRPs, the TRP can be implicitly identified. If the candidate beam RS lists are different for different TRPs, entries in multiple candidate beam RS lists can be sequentially indexed starting from the first list. In an embodiment, in addition to the candidate RS ID, the TRP ID may also be included. It should be noted that in cases where the TRP ID is not explicitly included in the beam fault detection and recovery configuration, the set ID or pool ID or list ID corresponding to the different sets of BFD RSs and candidate beam RSs is included. BFD RS set 0 / pool 0 / list 0 corresponds to candidate beam RS set 0 / pool 0 / list 0, and BFD RS set 1 / pool 1 / list 1 corresponds to candidate beam RS set 1 / pool 1 / list 1.

[0255] In an alternative embodiment, the BFR MAC CE includes: - A bitmap, where each bit corresponds to a serving cell, and the bit corresponding to the SpCell where a beam fault is detected is set to 1.

[0256] If, among the candidate beam RSs in the set or pool of the SpCell that detects a beam fault and initiates recovery, there is at least one RS (SSB / CSI RS) with an RSRP higher than the threshold, then AC=1, candidate RS ID, TRP ID, zero or more R bits.

[0257] - If there is no RS (SSB / CSI RS) with RSRP higher than the threshold among the candidate beam RSs in the set or pool of the SpCell that detected the beam fault and initiated recovery, then AC=0, TRP ID, and zero or more R bits.

[0258] - The MAC subheader of the BFR MAC CE includes a reserved LCID, which is the BFR MAC CE of the BFR used for the TRP of the serving cell. This LCID is different from the LCID included in the MAC subheader of the BFR MAC CE of the serving cell.

[0259] - Otherwise, if a beam fault is detected in all sets / pools of the SpCell's BFD RS, as previously explained, the UE initiates beam fault recovery for the SpCell: -- Trigger random access on SpCell.

[0260] ---If there is at least one RS (SSB / CSI RS) in the list of candidate beam RSs in SpCell with an RSRP higher than the threshold, then CFRA is performed.

[0261] --Otherwise, UE can: ---Execute CBRA.

[0262] ---Generate BFR MAC CE.

[0263] The BFR MAC CE includes a bitmap, where each bit corresponds to the serving cell. The bit corresponding to the SpCell is set to 1.

[0264] ----In this embodiment, beam fault recovery information for SpCell is not included.

[0265] In an alternative embodiment, beam fault recovery information may be included for the failed TRP (i.e., the set / pool / list of BFD RSs that detected beam faults). For example, beam fault recovery information may be used. Figure 12 and Figure 13 The format shown in BFR MAC CE 1200 and 1300 indicates beam fault recovery information. This can be used in conjunction with... Figure 12 and Figure 13 The fields are set in a similar manner to those used for SCell BFR.

[0266] It should be noted that, in the embodiments, even in the case of CFRA, a BFR MAC CE can be generated and transmitted in MsgA or Msg3 to include BFR information from another set / pool or both sets / pools.

[0267] In an embodiment, for the BFR of a TRP or BFD RS set / pool of SpCell, if the HARQ procedure for transmitting a BFR MAC CE or a truncated BFR MAC CE containing beam fault recovery information of the BFD RS set / pool or TRP of this serving cell receives a PDCCH addressed to a C-RNTI indicating a newly transmitted uplink permission, then the UE sets the BFI counter corresponding to the BFD RS set / pool or TRP to zero, cancels all triggered BFRs of the BFD RS set / pool or TRP of this serving cell, and considers the BFR of the TRP or BFD RS set / pool of SpCell to have been successfully completed.

[0268] In an embodiment, when a MAC PDU is transmitted and this PDU includes a BFR MAC CE or a truncated BFR MAC CE containing beam fault information of the BFD RS set / pool or TRP of the SPCell, all BFRs triggered for the BFD RS set / pool or TRP of the SPCell can be cancelled.

[0269] In this embodiment, for each pending SR not triggered according to the BSR procedure of the serving cell, the MAC entity may: If this SR is triggered by beam fault recovery of the BFD SR pool or TRP of the serving cell (or SCell), and transmits a MAC PDU and this PDU includes a BFR MAC CE or a truncated BFR MAC CE containing beam fault information of the BFD SR pool or TRP of the serving cell (or SCell); It should be noted that beam fault recovery of the serving cell's BFD RS pool or TRP can also be referred to as the serving cell's M-TRP BFR, the serving cell's partial BFR, or the serving cell's enhanced BFR.

[0270] It should be noted that beam fault recovery of the serving cell's BFD RS pool or TRP can also be referred to as the serving cell's M-TRP BFR, the serving cell's partial BFR, or the serving cell's enhanced BFR.

[0271] Example 3: - In some embodiments, if a beam fault detection indication for the SpCell's TRP is received a configurable number of times within a timer interval, or if a beam fault is detected in the SpCell's TRP, as previously explained, then the UE: --Trigger BFR for TRP of SCell - If the UL license is not available for transmitting a BFR MAC CE or a truncated BFR MAC CE, an SR is triggered; or if the UL license is available but cannot accommodate a BFR MAC CE and its header or a truncated BFR MAC CE and its sub-headers, an SR is triggered; if it can accommodate a (truncated) BFR MAC CE and its header.

[0272] --If a UL license is available and can accommodate a (truncated) BFR MAC CE and its header, then transmit the BFR MAC CE with a UL license.

[0273] In the embodiment, the SR triggering and the generation and transmission of the BFR MAC CE as explained above are performed only if there is at least one serving cell where the BFR is triggered and not canceled, and the evaluation of the candidate beams in the candidate beam list of the TRP that detected the beam fault is completed.

[0274] The enhanced format of BFR MAC CE 600 and 700 is in Figure 6 and Figure 7 As shown in the image. The BFR MAC CE is generated as follows: ---If there are no RSs (SSB / CSI RSs) with RSRPs higher than the threshold among the RSs of the TRPs initiating beam fault recovery in the SpCell, then indicate which TRP is faulty in the BFR MAC CE. (AC=0, E=0, TRP ID, R bit).

[0275] ---Otherwise: Include the RS ID of the TRP of SpCell in the BFR MAC CE. (AC=1, E=0, candidate RS ID).

[0276] ---The candidate RS ID is the index of the entry in the candidate RS list.

[0277] In an embodiment, the candidate RS ID can be an index of an entry in the candidate RS list corresponding to the SSB / CSI RS of a TRP whose SS-RSRP / CSI-RSRP is above a threshold. If the list is shared by all TRPs, the TRP can be implicitly identified. If the candidate beam RS lists are different for different TRPs, entries in multiple candidate beam RS lists can be sequentially indexed starting from the first list. In an embodiment, in addition to the candidate RS ID, the TRP ID may also be included. It should be noted that in cases where the TRP ID is not explicitly included in the beam fault detection and recovery configuration, the set ID, pool ID, or list ID corresponding to the different sets of BFD RSs and the candidate beam RSs is included. BFD RS set 0 / pool 0 / list 0 corresponds to candidate beam RS set 0 / pool 0 / list 0, and BFD RS set 1 / pool 1 / list 1 corresponds to candidate beam RS set 1 / pool 1 / list 1.

[0278] - Otherwise, if a beam fault detection indication for SpCell is received a configurable number of times within the timer interval, or if beam faults are detected in all TRPs of SpCell, as previously explained, the UE initiates beam fault recovery for SpCell: -- Trigger random access on SpCell.

[0279] ---If there is at least one RS (SSB / CSI RS) in the list of candidate beam RSs in SpCell with an RSRP higher than the threshold, then CFRA is performed.

[0280] --Otherwise, UE can: ---Execute CBRA.

[0281] ---Generate BFR MAC CE. Emit the BFR MAC CE in MsgA or Msg3. Enhanced formats for BFR MAC CE 600 and 700 are available in... Figure 6 and Figure 7 As shown in the image. The BFR MAC CE is generated as follows: The BFR MAC CE includes a bitmap, where each bit corresponds to the serving cell. The bit corresponding to the SpCell is set to 1.

[0282] ----Add beam fault recovery information for each faulty TRP (i.e., one AC octet for each faulty TRP).

[0283] ----Information on beam fault recovery for TRP.

[0284] Set E to 1 or 0 to indicate whether the following is beam fault recovery information for another TRP in the same serving cell.

[0285] ---If there are no RSs (SSB / CSI RSs) with RSRP higher than the threshold among the candidate RSs of the serving cell initiating beam fault recovery: ---- Set AC=0; including TRP ID, R bit.

[0286] ----otherwise: ---- Set AC=1; include candidate RS IDs, i.e., the IDs of SSB / CSIRS whose TRP is higher than the threshold for SS-RSRP / CSI-RSRP.

[0287] ---In an embodiment, the candidate RS ID is the index of an entry in the candidate RS list corresponding to the SSB / CSI RS of a TRP whose SS-RSRP / CSI-RSRP is above a threshold. TRPs can be implicitly identified because the list is shared by all TRPs. In an embodiment, a TRP ID is also included.

[0288] It should be noted that, in the embodiments, even in the case of CFRA, a BFR MAC CE can be generated and transmitted in MsgA or Msg3 to include BFR information for another TRP or both TRPs.

[0289] In an embodiment, for the BFR of a TRP or BFD RS set / pool of SpCell, if the HARQ procedure for transmitting a BFR MAC CE or a truncated BFR MAC CE containing beam fault recovery information of the BFD RS set / pool or TRP of this serving cell receives a PDCCH addressed to a C-RNTI indicating a newly transmitted uplink permission, then the UE sets the BFI counter corresponding to the BFD RS set / pool or TRP to zero, cancels all triggered BFRs of the BFD RS set / pool or TRP of this serving cell, and considers the BFR of the TRP or BFD RS set / pool of SpCell to have been successfully completed.

[0290] In an embodiment, when a MAC PDU is transmitted and this PDU includes a BFR MAC CE or a truncated BFR MAC CE containing beam fault information of the BFD RS set / pool or TRP of the SPCell, all BFRs triggered for the BFD RS set / pool or TRP of the SPCell can be cancelled.

[0291] In this embodiment, for each pending SR not triggered according to the BSR procedure of the serving cell, the MAC entity may: If this SR is triggered by beam fault recovery of the BFD SR pool or TRP of the serving cell (or SCell), and transmits a MAC PDU and this PDU includes a BFR MAC CE or a truncated BFR MAC CE containing beam fault information of the BFD SR pool or TRP of the serving cell (or SCell); It should be noted that beam fault recovery of the serving cell's BFD RS pool or TRP can also be referred to as the serving cell's M-TRP BFR, the serving cell's partial BFR, or the serving cell's enhanced BFR.

[0292] Example 3A: - In some embodiments, if a beam fault detection indication for the pool of SpCell's BFD RS is received a configurable number of times within a timer interval, or if a beam fault for the pool of SpCell's BFD RS is detected, as previously explained, then the UE: -- Trigger BFR for the set / pool of SpCell's BFD RS An SR is triggered if the UL license is not available for transmitting a BFR MAC CE or a truncated BFR MAC CE, or if the UL license is available but cannot accommodate a BFR MAC CE and its header or a truncated BFR MAC CE and its sub-headers. An SR is triggered if the UL license can accommodate a (truncated) BFR MAC CE and its header. --If a UL license is available and can accommodate a (truncated) BFR MAC CE and its header, then transmit the BFR MAC CE with a UL license.

[0293] In the embodiment, the SR triggering and the generation and transmission of the BFR MAC CE as explained above are performed only if there is at least one serving cell where the BFR is triggered and not canceled, and the evaluation of the candidate beams in the candidate beam list corresponding to the set / pool of the BFD RS that detected the beam fault is completed.

[0294] The enhanced format of BFR MAC CE 800 and 900 is in Figure 8 and Figure 9 As shown in the image. The BFR MAC CE is generated as follows: ---If there is no RS (SSB / CSI RS) with an RSRP higher than the threshold among the candidate beam RSs of the SCell that detected a beam fault and initiated recovery, then the BFR MAC CE indicates which set / pool has failed. (AC=0, E=0, set ID / pool ID, R bit).

[0295] ---Otherwise: Include the RS ID, i.e., the ID of the SSB / CSI RS whose SS-RSRP / CSI-RSRP is higher than the threshold among the candidate RSs in the set / pool of candidate RSs corresponding to the set / pool of the serving cell where the beam fault was detected: set AC=1, E=0, candidate RS ID. The candidate RS ID is the index of the entry in the candidate RS list. If the candidate beam RS lists are different for different sets / pools, the entries in multiple candidate beam RS lists can be indexed sequentially starting from the first list. In the embodiment, set I / pool ID may also be included.

[0296] - Otherwise, if a beam fault detection indication for the SpCell is received a configurable number of times within the timer interval, or if a beam fault is detected in all sets / pools of the SpCell's BFD RS, as previously explained, the UE initiates beam fault recovery for the SpCell: -- Trigger random access on SpCell.

[0297] ---If there is at least one RS (SSB / CSI RS) in the list of candidate beam RSs in SpCell with an RSRP higher than the threshold, then CFRA is performed.

[0298] --Otherwise, UE: ---Execute CBRA.

[0299] ---Generate a BFR MAC CE. Emit the BFR MAC CE in MsgA or Msg3. An enhanced format for the BFR MAC CE is... Figure 8 and Figure 9 As shown in the image. The BFR MAC CE is generated as follows: The BFR MAC CE includes a bitmap, where each bit corresponds to the serving cell. The bit corresponding to the SpCell is set to 1.

[0300] ----Add beam fault recovery information for each set / pool of the SCell that detects a beam fault (i.e., one AC octet for each set / pool of the SCell that detects a beam fault).

[0301] ----Beam fault recovery information for the collection / pool of SCells where beam faults are detected.

[0302] ---Set E to 1 or 0 to indicate whether the following are beam fault recovery information for another set / pool of the same serving cell where a beam fault was detected, respectively.

[0303] ---If there are no RSs (SSB / CSI RSs) with RSRP higher than the threshold among the candidate beam RSs in the pool of the SCell that detected a beam fault and initiated recovery: ---- Set AC=0; including set ID / pool ID, R bits.

[0304] ----otherwise: ----Set AC=1; Include candidate RS IDs, i.e., the IDs of SSB / CSI RSs whose SS-RSRP / CSI-RSRP is higher than a threshold among the candidate RSs in the set / pool of candidate RSs corresponding to the BFD RSs of the serving cell where a beam fault was detected. Set AC=1, E=0, and candidate RS IDs. The candidate RS ID is the index of an entry in the candidate RS list. If the candidate beam RS lists are different for different sets / pools, entries in multiple candidate beam RS lists can be sequentially indexed starting from the first list. In this embodiment, set I / pool IDs may also be included.

[0305] It should be noted that, in the embodiments, even in the case of CFRA, a BFR MAC CE can be generated and transmitted in MsgA or Msg3 to include BFR information of the set / pool of BFD RSs of the serving cell that detected a beam fault.

[0306] It should be noted that beam fault recovery of the serving cell's BFD RS pool or TRP can also be referred to as the serving cell's M-TRP BFR, the serving cell's partial BFR, or the serving cell's enhanced BFR.

[0307] In an embodiment, for the BFR of a TRP or BFD RS set / pool of SpCell, if the HARQ procedure for transmitting a BFR MAC CE or a truncated BFR MAC CE containing beam fault recovery information of the BFD RS set / pool or TRP of this serving cell receives a PDCCH addressed to a C-RNTI indicating a newly transmitted uplink permission, then the UE sets the BFI counter corresponding to the BFD RS set / pool or TRP to zero, cancels all triggered BFRs of the BFD RS set / pool or TRP of this serving cell, and considers the BFR of the TRP or BFD RS set / pool of SpCell to have been successfully completed.

[0308] In an embodiment, when a MAC PDU is transmitted and this PDU includes a BFR MAC CE or a truncated BFR MAC CE containing beam fault information of the BFD RS set / pool or TRP of the SPCell, all BFRs triggered for the BFD RS set / pool or TRP of the SPCell can be cancelled.

[0309] In this embodiment, for each pending SR not triggered according to the BSR procedure of the serving cell, the MAC entity may: If this SR is triggered by beam fault recovery of the pool / set or TRP of the BFD SR of the serving cell (or SCell), and transmits a MAC PDU, and this PDU includes a BFR MAC CE or a truncated BFR MAC CE containing beam fault information of the pool / set or TRP of the BFD SR of the serving cell (or SCell).

[0310] It should be noted that beam fault recovery of the serving cell's BFD RS pool or TRP can also be referred to as the serving cell's M-TRP BFR, the serving cell's partial BFR, or the serving cell's enhanced BFR.

[0311] Example 4: - If one or more TRPs of the SCell meet the BFD criterion (i.e., BFD of one or more TRPs of the SpCell is detected, as previously explained), then the UE initiates beam fault recovery for the TRPs of the SpCell: -- Trigger random access on SpCell.

[0312] --Emit BFR MAC CE in Msg3 or MsgA. Enhanced formats for BFR MAC CE 600 and 700 are available in... Figure 6 and Figure 7 As shown in the image. The BFR MAC CE is generated as follows: --BFR MAC CE includes a bitmap, where each bit corresponds to a serving cell. The bit corresponding to the SpCell where a beam fault is detected is set to 1.

[0313] --Add beam fault recovery information for each faulty TRP in SpCell (i.e., one AC octet for each faulty TRP).

[0314] --Beam fault recovery information for SpCell's TRP: --- Set E to 1 or 0 to indicate whether the following is beam fault recovery information for another TRP in the same serving cell. Note that if the BFR MAC CE includes beam fault recovery information for only one TRP, the E field may not be required or included in the BFR MAC CE.

[0315] ---If there are no RSs (SSB / CSI RSs) with RSRP higher than the threshold among the candidate RSs of this TRP in the serving cell that has detected a beam fault (and initiated recovery): ----Set AC=0; include TRP ID, R bit. Note that if the TRP ID is not explicitly included in the beam fault detection and recovery configuration, include the set ID, pool ID, or list ID corresponding to the different sets of BFD RSs and candidate beam RSs. BFD RS set 0 / pool 0 / list 0 corresponds to candidate beam RS set 0 / pool 0 / list 0, and BFD RS set 1 / pool 1 / list 1 corresponds to candidate beam RS set 1 / pool 1 / list 1. BFD RS set n / pool n / list n corresponds to candidate beam RS set n / pool n / list n. ---otherwise: ---- Set AC=1; include candidate RS IDs, i.e., the IDs of SSB / CSIRS whose TRP is higher than the threshold for SS-RSRP / CSI-RSRP.

[0316] In an embodiment, the candidate RS ID can be an index of an entry in the candidate RS list corresponding to the SSB / CSI RS of a TRP whose SS-RSRP / CSI-RSRP is above a threshold. If the list is shared by all TRPs, the TRP can be implicitly identified. If the candidate beam RS lists are different for different TRPs, entries in multiple candidate beam RS lists can be sequentially indexed starting from the first entry in the first list. In an embodiment, a TRP ID may also be included. It should be noted that in cases where the TRP ID is not explicitly included in the beam fault detection and recovery configuration, the set ID, pool ID, or list ID corresponding to the different sets of BFD RSs and candidate beam RSs is included. BFD RS set 0 / pool 0 / list 0 corresponds to candidate beam RS set 0 / pool 0 / list 0, and BFD RS set 1 / pool 1 / list 1 corresponds to candidate beam RS set 1 / pool 1 / list 1.

[0317] Example 4A: - In some embodiments, if one or more sets / pools of the SpCell's BFD RS meet the BFD criteria (i.e., a beam fault is detected in one or more sets / pools of the SpCell's BFD RS, as previously explained), the UE initiates beam fault recovery for one or more sets / pools of the SpCell's BFD RS: -- Trigger random access on SpCell.

[0318] --Emit BFR MAC CE in Msg3 or MsgA. For example, the enhanced format of BFR MAC CE 800, 900 is... Figure 8 and Figure 9 As shown in the diagram. The BFR MAC CE can be generated by the UE, as follows: --BFR MAC CE can include a bitmap, where each bit corresponds to a serving cell. The bit corresponding to the SpCell where a beam fault is detected is set to 1.

[0319] --Add beam fault recovery information for each set / pool of the BFD RS that detects a beam fault (i.e., one AC octet for each set / pool of the BFD RS).

[0320] --Beam fault recovery information for BFD RS pools / cells: --- Set E to 1 or 0 to indicate whether the following is beam fault recovery information for another set / pool of BFD RSs in the same serving cell. Note that if the BFR MAC CE includes beam fault recovery information for only one TRP or one set / pool of BFD RSs, the E field may not be required or included in the BFR MAC CE.

[0321] ---If there are no RSs (SSB / CSI RSs) with RSRP higher than the threshold among the candidate RSs in the set / pool of candidate RSs corresponding to the set / pool of BFD RSs of the serving cell where a beam fault was detected: ---- Set AC=0; including set / pool ID, R bits.

[0322] ---otherwise: ----Set AC=1; Include candidate RS IDs, i.e., the IDs of SSB / CSI RSs whose SS-RSRP / CSI-RSRP is higher than the threshold among the candidate RSs in the set / pool of candidate RSs corresponding to the set / pool of BFD RSs of the serving cell where a beam fault was detected. In this embodiment, the candidate RS ID can be an index of an entry in the candidate RS list corresponding to the SSB / CSI RS. If multiple candidate beam RS lists exist, the entries in the multiple candidate beam RS lists can be sequentially indexed starting from the first entry in the first list. In this embodiment, a set / pool ID may also be included.

[0323] Method 2: Beam fault detection and beam fault recovery triggering in the serving cell: For beam fault detection in the serving cell, the UE can receive the beam fault detection configuration for that serving cell from the gNB, as previously explained. The UE can determine whether the received beam fault detection configuration includes beam fault detection RSs for multiple TRPs.

[0324] If the beam fault detection configuration includes beam fault detection RSs for multiple TRPs (or in other words, multiple sets / pools / groups of beam fault detection RSs), then the UE detects a beam fault and triggers beam fault recovery for the serving cell, as follows: 1. The UE (PHY) periodically measures the beam fault detection RS of the TRP of the serving cell in the beam fault detection configuration (or the beam fault detection RS of all sets / pools / groups of beam fault detection RS).

[0325] 2. If all BFD RS of any TRP in the serving cell are below the threshold, or if the assumed PDCCH BLER determined based on the measurement of beam fault detection RS is above the threshold of all beam fault detection RS of any TRP: - It is assumed that a beam failure instance has occurred, that is, the PHY layer transmits a beam failure instance indication to the MAC layer.

[0326] In other words, if all BFD RSs in any set / pool / group of the serving cell's BFD RSs are below a threshold, or if the assumed PDCCH BLER determined based on measurements of the beam fault detection RSs is higher than the threshold for all beam fault detection RSs in any set / pool / group of the serving cell's BFD RSs: - It is assumed that a beam failure instance has occurred, that is, the PHY layer transmits a beam failure instance indication to the MAC layer.

[0327] 3. After receiving a beam fault instance indication from the serving cell from the PHY layer, -Start or restart the beamFailureDetectionTimer of the serving cell.

[0328] - Update the BFI counter of the serving cell.

[0329] It should be noted that regardless of the number of TRPs in the serving cell, each serving cell maintains only one timer and counter.

[0330] 4. If the BFI counter is greater than or equal to the serving cell's beamFailureInstanceMaxCount: it is considered that a beam fault has been detected in the serving cell, and beam fault recovery for the serving cell is initiated.

[0331] If the beam fault detection configuration does not include beam fault detection RSs for multiple TRPs, the UE detects a beam fault and triggers beam fault recovery, as follows: 1. The UE (PHY) periodically measures the beam fault detection RS of the serving cell in the beam fault detection configuration.

[0332] 2. If all BFD RS of the serving cell are below the threshold, or if the assumed PDCCH BLER determined based on the measurement of beam fault detection RS is higher than the threshold of all beam fault detection RS of the serving cell: - It is assumed that a beam failure instance has occurred, that is, the PHY layer transmits a beam failure instance indication to the MAC layer.

[0333] 3. After receiving a beam fault instance indication from the serving cell from the PHY layer, - Start or restart the beamFailureDetectionTimer for the serving cell that receives a beam failure instance indication from the PHY layer. Maintain one beamFailureDetectionTimer for the serving cell.

[0334] - Update the BFI counter of the serving cell that received the beam fault instance indication from the PHY. Maintain a BFI counter for the serving cell.

[0335] 4. If the BFI counter is greater than or equal to the beamFailureInstanceMaxCount of the serving cell, it can be considered that a beam failure of the serving cell has been detected and beam failure recovery of the serving cell can be initiated.

[0336] Supports beam fault recovery process for serving cells with multiple TRPs: - If the serving cell meets the BFD standard (as explained above). --If the serving cell is SCell, then the UE: --- Trigger SCell BFR.

[0337] ---If the UL-SCH resource is available for new transmission and if, as a result of LCP, the UL-SCH resource can accommodate the BFR MAC CE and its sub-headers: the UE generates the BFR MAC CE and transmits the MAC PDU including the BFR MAC CE to the gNB.

[0338] ---Otherwise, if the UL-SCH resources are available for new transmission and if, as a result of LCP, the UL-SCH resources can accommodate the truncated BFR MAC CE and its sub-headers: the UE generates the truncated BFR MAC CE and the UE transmits the MAC PDU including the truncated BFR MAC CE to the gNB.

[0339] ---Otherwise: The UE triggers the SCell beam fault recovery SR for the SCell.

[0340] --Otherwise, UE: --- Trigger a random access procedure on SpCell.

[0341] --- Generate (truncated) BFR MAC CE and transmit a MAC PDU including the BFR MAC CE in MsgA or Msg3 during the random access procedure.

[0342] - In the embodiment, the enhanced format of BFR MAC CE is in Figure 6 and Figure 7 As shown in the image, the (truncated) BFRMAC CE is generated as follows: --The (truncated) BFR MAC CE can include a bitmap, where each bit corresponds to a serving cell. The bit corresponding to the serving cell where a beam fault is detected is set to 1.

[0343] --Add beam fault recovery information for each faulty TRP in the serving cell (i.e., one AC octet for each faulty TRP), or add beam fault recovery information for each set / pool / list of candidate beam RSs.

[0344] --For candidate beam RS collection / pool / list or TRP beam fault recovery information

[0345] ---Set E to 1 or 0 to indicate whether the following is another beam fault recovery message from the same serving cell, respectively.

[0346] ---If there are no RSs (SSB / CSI RSs) with RSRP higher than the threshold among the candidate RSs of this TRP in the serving cell that has detected a beam fault (and initiated recovery): ----Set AC=0; include TRP ID, R bit. Note that if the TRP ID is not explicitly included in the beam fault detection and recovery configuration, include the set ID, pool ID, or list ID corresponding to the different sets of BFD RSs and candidate beam RSs. BFD RS set 0 / pool 0 / list 0 corresponds to candidate beam RS set 0 / pool 0 / list 0, and BFD RS set 1 / pool 1 / list 1 corresponds to candidate beam RS set 1 / pool 1 / list 1.

[0347] ---otherwise: ---- Set AC=1; include candidate RS IDs, i.e., the IDs of SSB / CSIRS whose TRP is higher than the threshold for SS-RSRP / CSI-RSRP.

[0348] In an embodiment, the candidate RS ID can be an index of an entry in the candidate RS list corresponding to the SSB / CSI RS of a TRP whose SS-RSRP / CSI-RSRP is above a threshold. If the list is shared by all TRPs, the TRP can be implicitly identified. If the candidate beam RS lists are different for different TRPs, entries in multiple candidate beam RS lists can be sequentially indexed starting from the first list. In an embodiment, a TRP ID may also be included. It should be noted that in cases where the TRP ID is not explicitly included in the beam fault detection and recovery configuration, a set ID, pool ID, or list ID corresponding to a different set of BFD RSs and candidate beam RSs is included. BFD RS set 0 / pool 0 / list 0 corresponds to candidate beam RS set 0 / pool 0 / list 0, and BFD RS set 1 / pool 1 / list 1 corresponds to candidate beam RS set 1 / pool 1 / list 1.

[0349] - In an embodiment, a (truncated) BFR MAC CE can be generated as follows: --The (truncated) BFR MAC CE includes a bitmap, where each bit corresponds to a serving cell. The bit corresponding to the serving cell where a beam fault is detected is set to 1.

[0350] --Regardless of whether a fault occurs, add beam fault recovery information for each TRP of the serving cell (i.e., one AC octet per TRP). Alternatively, add beam fault recovery information for each set / pool / list of candidate beam RSs. Beam fault recovery information can be added in ascending order of TRP ID / set ID / pool ID / list ID, etc.

[0351] --For candidate beam RS collection / pool / list or TRP beam fault recovery information

[0352] ---If there are no RSs (SSB / CSI RSs) with RSRP higher than the threshold among the candidate RSs of this TRP in the serving cell that has detected a beam fault (and initiated recovery): ---- Set AC=0; including the R bit.

[0353] ---- (Alternative) Set AC=0; F=0 / 1 to indicate whether a fault exists; R bit.

[0354] ---otherwise: ----Set AC=1; Include candidate RS IDs, i.e., the IDs of SSB / CSI RSs whose SS-RSRP / CSI-RSRP is higher than the threshold TRP, or the IDs of SSB / CSI RSs in the set / pool / list of candidate beam RSs.

[0355] In an embodiment, the candidate RS ID can be an index of an entry in the candidate RS list corresponding to an SSB / CSI RS whose SS-RSRP / CSI-RSRP is higher than a threshold.

[0356] The bitmap fields in the (truncated) BFR MAC CE are defined as follows: -SP: This field indicates beam fault detection for the SpCell of this MAC entity. The SP field is set to 1 to indicate that a beam fault was detected for the SpCell. Otherwise, it is set to 0. -C i (BFR MAC CE): This field indicates beam fault detection and is used for beamforming... ServCellIndex The existence of an octet containing the AC field in the SCell of i. C is set to 1. i The field indicates that a beam fault has been detected and has ServCellIndex The SCell of i contains an octet containing the AC field. C is set to 0. i The field indicates that no beam fault was detected and has ServCellIndex The SCell of i does not contain an octet containing the AC field. ServCellIndex There are octets containing the AC field in ascending order; -C i (Trunculated BFR MAC CE): This field indicates the pair with... ServCellIndex Beam fault detection for i's SCell. C set to 1. i The field indicates that a beam fault has been detected and may exist for use with ServCellIndex The octet of i's SCell contains the AC field. C is set to 0. i The field indicates that no beam fault was detected and has ServCellIndex The SCell of i does not contain an octet containing the AC field. ServCellIndex Includes octets containing the AC field in ascending order (if any). The number of included octets containing the AC field is maximized, but not exceeding the available license size; - In an embodiment, a (truncated) BFR MAC CE can be generated, as explained in Method 1.

[0357] method

[0358] In the exemplary embodiment (Option 1), for the beam fault detection configuration: - A list of BFD RSs for each BWP can be sent using signals. In the case of multiple TRPs, a one-bit TRP indicator can be included to indicate whether the RS is for TRP 0 or TRP 1.

[0359] In an exemplary embodiment, beam fault detection is triggered for the serving cell: - If multiple TRPs are configured in the serving cell, a beam fault is considered detected when all RSs of the TRPs in the serving cell's BFD RS list are below a threshold.

[0360] - Otherwise, a beam fault is considered detected when all RSs in the BFD RS list of the serving cell are below the threshold.

[0361] In an exemplary embodiment, for beam fault recovery of SpCell: - Send a list of candidate beam RS for each BWP using a signal. In the case of multiple TRPs, a TRP indicator can be included to indicate whether the RS is for TRP0 or TRP1.

[0362] - If multiple TRPs are configured: --If a beam fault detection indication from SpCell's TRP is received a configurable number of times within the timer interval: Trigger RA.

[0363] ---If at least one RS (SSB / CSI RS) in the SpCell candidate beam RS list is above the threshold among the RSs associated with the TRP that initiates beam fault recovery, then CFRA is performed.

[0364] --Otherwise, UE: ---Execute CBRA; ---Generate BFR MAC CE; and ---Indicate which TRP of SpCell is faulty in BFR MAC CE Otherwise, UE: --If a beam fault detection indication from SpCell is received a configurable number of times within a timer interval: Trigger RA.

[0365] ---If there is at least one RS (SSB / CSI RS) in the list of candidate beam RSs in SpCell with an RSRP higher than the threshold, then CFRA is performed.

[0366] --Otherwise, UE: ---Execute CBRA; and ---Generate BFR MAC CE.

[0367] In an exemplary embodiment, for beam fault recovery of SCell: - Send a list of candidate beam RS for each BWP using a signal. In the case of multiple TRPs, a TRP indicator can be included to indicate whether the RS is for TRP0 or TRP1.

[0368] - If multiple TRPs are configured: --If a beam fault detection indication from the SCell TRP is received a configurable number of times within a timer interval, the SCell BFR is triggered.

[0369] --If UL license is unavailable, the UE can trigger SR.

[0370] --UE can transmit BFR MAC CE with UL permission.

[0371] ---In an exemplary embodiment, a single AC octet can be used for each SCell.

[0372] If there are no RSs (SSB / CSI RSs) with RSRPs higher than the threshold among the RSs of the TRP initiating beam fault recovery, then the BFR MAC CE indicates which TRP failed. If at least one RS (SSB / CSI RS) with RSRPs higher than the threshold among the RSs of the TRP initiating beam fault recovery, then the RSID is included in the BFR MAC CE.

[0373] ---In another exemplary embodiment, the AC octet for each TRP of each SCell can be used. For example, the first octet can be used for TRP 0, and the second octet can be used for TRP 1.

[0374] ----If TRP is not faulty: AC=0, F=0, 6 R bits

[0375] ----If the TRP fails and no candidate beams are available: AC=0, F=1, 6 R bits.

[0376] ----If the TRP fails and candidate beams are available: AC=1, RS ID.

[0377] -Otherwise, the UE can: --If UL license is unavailable, trigger SR; and --Issuing BFR MAC CE under UL license.

[0378] --Each SCell has a single AC octet.

[0379] ---If no candidate beams are available: AC=0, reserved bit.

[0380] ---If candidate beams are available, then AC=1, RS ID.

[0381] In the exemplary embodiment (Option 2), for the beam fault detection configuration: - A list of BFD RSs can be sent individually for each TRP of each BWP using signals.

[0382] In an embodiment, two lists from a group in the UL BWP configuration can be used instead of a single-bit indicator (e.g., group1 may include a list of candidate beam RS associated with TRP1, and group2 may include a list of candidate beam RS associated with TRP2). This triggers beam fault detection for the serving cell.

[0383] - If multiple TRPs are configured in the serving cell: - When all RSs in the BFD RS list of the serving cell's TRP are below a threshold, a beam fault can be considered detected.

[0384] -otherwise

[0385] --When all RSs in the BFD RS list of the serving cell are below a threshold, a beam fault can be considered detected.

[0386] In an exemplary embodiment, for beam fault recovery of SpCell: - A list of candidate beam RSs can be sent individually with a signal for each TRP of each BWP.

[0387] - If multiple TRPs are configured: --If the UE receives a beam fault detection indication from the SpCell's TRP for a configurable number of times within a timer interval, the UE can trigger RA.

[0388] --If there is at least one RS (SSB / CSI RS) with an RSRP higher than the threshold among the candidate beam RS of the SpCell that initiates beam fault recovery, the UE can perform CFRA.

[0389] --Otherwise, UE can: ---Execute CBRA; ---Generate BFR MAC CE; and ---Indicate which TRP of SpCell is faulty in BFR MAC CE -otherwise --If the UE receives a beam fault detection indication from SpCell a configurable number of times within a timer interval, it can trigger RA.

[0390] --If there is at least one RS (SSB / CSI RS) in the candidate beam RS list of SpCell with an RSRP higher than the threshold, the UE can perform CFRA.

[0391] --Otherwise, UE can: ---Execute CBRA; and ---Generate BFR MAC CE.

[0392] In an exemplary embodiment, for beam fault recovery of SCell: - A list of candidate beam RSs can be sent individually with a signal for each TRP of each BWP.

[0393] - If multiple TRPs are configured: --If a beam fault detection indication from the SCell TRP is received a configurable number of times within a timer interval, the SCell BFR is triggered.

[0394] --If UL license is unavailable, trigger SR; and

[0395] --Issuing BFR MAC CE under UL license.

[0396] ---The AC octet for each TRP of each SCell. For example, the first octet is used for TRP 0, and the second octet is used for TRP 1.

[0397] ----If TRP is not faulty: AC=0, F=0, 6 R bits.

[0398] ----If the TRP fails and no candidate beams are available: AC=0, F=1, 6 R bits.

[0399] ----If the TRP fails and candidate beams are available: AC=1, RS ID.

[0400] -Otherwise, the UE can: --If UL license is unavailable, trigger SR; and --Issuing BFR MAC CE under UL license.

[0401] --- Each SCell has a single AC octet.

[0402] ---If no candidate beams are available: AC=0, reserved bit.

[0403] ---If candidate beams are available, then AC=1, RS ID.

[0404] Other BFR enhancements.

[0405] Upon detecting a beam fault in the SCell, a beam fault response (BFR) can be triggered. After triggering the BFR, the UE can transmit the BFR MAC CE within the earliest available UL clearance that can accommodate a BFR MAC CE according to the LCP. When this UL clearance is available, the UE may not have yet measured the candidate beam RS in the candidate beam RS list. Therefore, the UE can transmit a BFR MAC CE with AC=0, and the network can deactivate the SCell based on this. This is inefficient.

[0406] In an exemplary embodiment (Option 1), the MAC entity (i.e., the MAC entity included in the UE) may: 1> If the beam fault recovery process determines that at least one BFR has been triggered and not canceled; and 1> If the UE has been measured and evaluated candidateBeamRSSCellList Candidate beams in the selection; (or if the UE has already identified beam failure recovery) candidateBeamRSSCellList (Availability of candidate beams in the data) 2> If the UL-SCH resource is available for a new transmission, and if, as a result of LCP, the UL-SCH resource can accommodate the (truncated) BFR MAC CE and its sub-headers: 3> Instructions for reuse and assembly processes to generate BFR MAC CE.

[0407] 2> Otherwise, if the UL-SCH resource is available for a new transmission, and if, as a result of LCP, the UL-SCH resource can accommodate the truncated BFR MAC CE and its sub-headers: 3> Instruct the reuse and assembly process to generate the truncated BFR MAC CE.

[0408] 2> Otherwise: 3> For each SCell where the BFR has been triggered and not canceled, trigger the SR for SCell beam fault recovery.

[0409] In an exemplary embodiment (Option 2), the MAC entity may: 1> If the beam fault recovery process determines that at least one BFR has been triggered and not canceled; and 1> If the UE has measured and evaluated at least one SCell where BFR has been triggered and not canceled. candidateBeamRSSCellList The candidate beam in the list; (or if the UE has already determined the availability of candidate beams in the candidateBeamRSSCellList for beam failure recovery): 2> If the UL-SCH resource is available for a new transmission, and if, as a result of LCP, the UL-SCH resource can accommodate the BFR MAC CE and its sub-headers: 3> Instructions for reuse and assembly processes to generate BFR MAC CE.

[0410] 3> In BFR MAC CE, if a beam fault is detected in an SCell with servingCellIndex i, the UE sets the Ci bit to 1 for that SCell; and the UE measures / evaluates the beam fault of that SCell. candidateBeamRSSCellList Candidate beams in the SCell (or if the UE has already determined the beam fault recovery for that SCell) candidateBeamRSSCellList (Availability of candidate beams in the data) 2> Otherwise, if the UL-SCH resource is available for a new transmission, and if, as a result of LCP, the UL-SCH resource can accommodate the truncated BFR MAC CE and its sub-headers: 3> Instruct the reuse and assembly process to generate the truncated BFR MAC CE.

[0411] 2> Otherwise: 3> For each SCell where the BFR has been triggered and not canceled, trigger the SR for SCell beam fault recovery.

[0412] Based on the above operations, if there are multiple SCells that have been triggered by BFR and have not yet been canceled (e.g., SCell1 and SCell2): - If the evaluation of candidate beams for SCell 1 is completed but the evaluation of candidate beams for SCell 2 is not completed, then a (truncated) BFRMAC CE is generated if the available UL license can accommodate a (truncated) BFRMAC CE and its sub-headers. In this case, in the MAC CE, the Ci bit corresponding to SCell 2 is set to 0, even if a beam fault is detected in SCell 2; the Ci bit corresponding to SCell 1 is set to 1, because a beam fault was detected in SCell 1 and the evaluation of candidate beams has also been completed.

[0413] - If the evaluation of candidate beams for SCell 2 is completed but the evaluation of candidate beams for SCell 1 is not completed, then a (truncated) BFRMAC CE is generated if the available UL license can accommodate a (truncated) BFRMAC CE and its sub-headers. In this case, in the MAC CE, the Ci bit corresponding to SCell 1 is set to 0, even if a beam fault is detected in SCell 1; the Ci bit corresponding to SCell 2 is set to 1, because a beam fault was detected in SCell 2 and the evaluation of candidate beams has also been completed.

[0414] - If the evaluation of candidate beams for SCell 1 is not completed and the evaluation of candidate beams for SCell 2 is not completed, then a (truncated) BFR MAC CE will not be generated.

[0415] Based on the above operations, if there is only one SCell (example SCell1) where BFR has been triggered and has not yet been canceled: - If the evaluation of candidate beams for SCell 1 is completed, a BFR MAC CE is generated if the available UL license can accommodate the (truncated) BFR MAC CE and its sub-headers.

[0416] - If the evaluation of candidate beams for SCell 1 is not completed, a (truncated) BFR MAC CE will not be generated.

[0417] In an exemplary embodiment (option 3), for each serving cell configured for beam fault detection, the MAC entity may: 1> If a beam fault instance indication has been received from the lower layer: 2> Start or restart beamFailureDetectionTimer ; 2> Make BFI counter Incrementing by 1; 2> If BFI counter >= beamFailureInstanceMaxCount : 3> If the serving cell is a SCell: 4> In determining beam fault recovery candidateBeamRSSCellList Once the availability of candidate beams is determined, the BFR for this serving cell is triggered. 3> Otherwise: 4> In determining beam fault recovery candidateBeamRSList Once the availability of candidate beams is determined, a random access procedure is initiated on SpCell.

[0418] CG Type 1 Configuration and UL TX Beam

[0419] Figure 14A data transmission / reception method for uplink beam transmission between a terminal and a base station is illustrated according to an embodiment of the present disclosure.

[0420] For PUSCH transmission, UL TX beam information can be indicated by gNB.

[0421] At step S1410, the UE can transmit SRS using various UL TX beams. The SRS resources used for transmitting SRS using various UL TX beams can be signaled to the UE by the gNB. These resources are identified using SRS Resource Identifiers (SRIs).

[0422] At step S1415, the gNB can map the CG Type 1 configuration to the UL TX beam. At step S1420, the gNB can use an SRI (e.g., SRI X) to indicate the selected UL TX beam. For example, the SRI can be indicated in the DCI used for dynamic licensing and CG Type 2. For example, the SRI can be indicated in the CG Type 1 configuration (see reference). Figure 14 ).

[0423] At step S1425, the UE can use SRI to transmit the RRC reconfiguration completion message to the gNB via the selected UL TX beam.

[0424] At step S1430, the UE can use various UL TX beams to transmit SRS. At step S1435, if the UL TX beam changes, the gNB can update its configuration. For example, the gNB can map the CG type 1 configuration to the changed UL TX beam. At step S1440, if the UL TX beam changes, the gNB can use SRI (e.g., SRI Y) to indicate the selected UL TX beam.

[0425] The problem is that a reconfiguration process is required every time the UL TX beam changes. The following... Figures 15 to 18 This is a diagram illustrating an embodiment of a method for transmitting a UL TX beam related to the aforementioned problems.

[0426] Method 1: Figure 15 A data transmission / reception method for uplink beam transmission between a terminal and a base station is illustrated according to an embodiment of the present disclosure.

[0427] In one method of this disclosure (e.g.) Figure 15As shown, the UE can receive SRS configuration from the gNB. At step S1510, the UE can use various UL TX beams to transmit SRS within the configured SRS resources. At step S1515, the gNB can select a UL TX beam. At step S1520, the gNB can use this UL TX beam to indicate the SRS Resource Identifier (SRI) of the SRS resource used by the UE to transmit SRS. The gNB can use a MAC CE or DCI to indicate / activate the SRI to the UE (e.g., SRI X). If an SRI is received using a MAC CE, the UE can transmit a confirmation MAC CE to the gNB. For subsequent CG Type 1 clearance, the UE can determine the UL TX beam based on this received SRI.

[0428] At step S1525, the gNB can use the RRC reconfiguration message to configure the configured license type 1. Additionally, at step S1530, the UE can send an RRC reconfiguration complete message to the gNB.

[0429] For UL transmissions permitted in these configurations, at step S1535, the UE may use the UL TX beam that the UE has already used to transmit in the SRS resource identified by the SRI, where the SRI is indicated / activated by the gNB using MAC CE or DCI.

[0430] At step S1540, the UE can use various UL TX beams to transmit SRS. At step S1545, if the UL TX beam changes, the gNB can identify the UL TX beam. At step S1550, the gNB can use the UL TX beam to indicate the SRI (e.g., SRI Y) of the changed SRS resource used by the UE to transmit SRS. If the SRI changes, at step S1555, the UE can apply the last received SRI in the MAC CE or DCI. For CG Type 1 UL transmission, the UE calculates PL based on the SRI indicated by the MAC CE / DCI. It should be noted that for CG Type 2 UL grants and dynamic UL grants, the TCI status or SRI used to determine the UL TX beam and path loss (PL) is indicated in the DCI that schedules those UL grants.

[0431] Figure 16 A data transmission / reception method for uplink beam transmission between a terminal and a base station is illustrated according to an embodiment of the present disclosure.

[0432] In alternative embodiments ( Figure 16 In addition to using SRS transmission to determine the UL TX beam, the gNB can instruct (the instruction can be in the RRC message) the UE to use the active TCI state to determine the UL TX beam instead of SRI.

[0433] At step S1610, the gNB may transmit an RRC message (e.g., an RRC reconfiguration message) including a list of TCI states to the UE. The TCI state may indicate one of the SSB / CSI RSs. The UE may use a UL TX beam that is quasi-co-located with the RX beam of the SSB / CSI RS used to receive the active TCI state. For UL transmission, the UE calculates the PL based on the active TCI state.

[0434] At step S1615, the UE may transmit an L1 / L3 measurement report to the gNB. At step S1620, the gNB may transmit a MAC CE or DCI (e.g., TCI state X) including the TCI state based on the received L1 / L3 measurement report.

[0435] At step S1625, the gNB can use an RRC reconfiguration message to configure the configured license type 1. For UL transmission, the gNB can instruct the UE to use the active TCI state to determine the UL TX beam. The TCI state can indicate one of the SSB / CSIRS. For UL transmission in this configured license of CG type 1, at step S1635, the UE can use a UL TX beam quasi-co-located with the RX beam of the SSB / CSIRS used to receive the active TCI state. For UL transmission in these CG type licenses, the UE can calculate the PL based on the active TCI state. For example, for CG type 2 UL licenses and dynamic UL licenses, the TCI state or SRI used to determine the UL TX beam can be indicated in the DCI scheduling those UL licenses.

[0436] For UL transmissions, if no indication is received from the gNB to determine the UL TX beam using the active TCI state, the UE can use SRI to determine the UL TX beam and path loss, as explained above.

[0437] At step S1640, the UE can transmit an L1 / L3 measurement report to the gNB. At step S1645, in the event of a TCI state change, the gNB can transmit a MAC CE or DCI including the TCI state (e.g., TCI state X) based on the received L1 / L3 measurement report (optional step). At step S1650, the UE can transmit using the UL TX beam within a CG Type 1 license, depending on the active TCI state. (See reference...) Figure 16 When the TCI state changes from TCI state X to TCI state Y, the UE can transmit in CG type 1 license using the UL TX beam according to the activated TCI state Y.

[0438] Method 2: Figure 17 A data transmission / reception method for uplink beam transmission between a terminal and a base station is illustrated according to an embodiment of the present disclosure.

[0439] In another method of this disclosure (such as...) Figure 17 As shown in the diagram, the UE can receive SRS configuration from the gNB. At step S1710, the UE can use various UL TX beams to transmit SRS within the configured SRS resources. At step S1715, the gNB can select a UL TX beam. At step S1720, the gNB can use this UL TX beam to indicate the SRS Resource Identifier (SRI) of the SRS resource used by the UE to transmit SRS. For example, the gNB can use a MAC CE or DCI to indicate / activate the SRI to the UE (e.g., SRIX). If an SRI is received using a MAC CE, the UE can transmit a confirmation MAC CE to the gNB. For subsequent CG Type 1 clearance, the UE can determine the UL TX beam based on this received SRI.

[0440] At step S1725, the gNB can use an RRC reconfiguration message to configure the configured license type 1. The gNB can configure one or more CG type 1 configurations. Each configuration can be mapped to one or more SRIs. The SRI associated with each CG type configuration can be sent by the gNB using signals.

[0441] In step S1730, the UE can send the RRC reconfiguration complete message to the gNB.

[0442] At step S1735, the UE can perform UL transmission within a CG Type 1 license configured to be associated with an activated SRI (i.e., an SRI received in the MAC CE or DCI of the activated SRI) (e.g., SRI X). For UL transmissions within these license configurations, the UE can use a UL TX beam that the UE has already used to transmit in the SRS resource identified by the SRI, where the SRI is indicated / activated by the gNB using a MAC CE or DCI.

[0443] At step S1740, the UE can use various UL TX beams to transmit SRS. At step S1745, if the UL TX beam changes, the gNB can identify the UL TX beam based on the received UL TX beam. At step S1750, the gNB can use the UL TX beam to indicate the SRI (e.g., SRI Y) of the changed SRS resource used by the UE to transmit SRS. If the SRI changes, at step S1755, the UE can apply the last received SRI in the MAC CE or DCI to determine the CG Type 1 configuration or CG Type 1 license to use and also determine the PL.

[0444] For example, for CG Type 2 UL licenses and dynamic UL licenses, the TCI status or SRI used to determine the UL TX beam and PL can be indicated in the DCI that schedules those UL licenses.

[0445] Figure 18 A data transmission / reception method for uplink beam transmission between a terminal and a base station is illustrated according to an embodiment of the present disclosure.

[0446] In alternative embodiments ( Figure 18 In this context, instead of using SRS transmission to determine the UL TX beam, the gNB can instruct (e.g., in an RRC message) that the UE uses the active TCI state to determine the UL TX beam instead of SRI. The TCI state can indicate one of the SSB / CSI RS. The UE can use a UL TX beam that is quasi-co-located with the RX beam of the SSB / CSI RS used to receive the active TCI state.

[0447] At step S1810, the gNB may transmit an RRC message (e.g., an RRC reconfiguration message) including a TCI status list to the UE. At step S1815, the UE may transmit an L1 / L3 measurement report to the gNB. At step S1820, the gNB may transmit a MAC CE or DCI (e.g., SRI X) including SRI based on the received L1 / L3 measurement report.

[0448] At step S1825, the gNB can configure the configured license type 1 using an RRC reconfiguration message. The gNB can configure one or more CG type 1 configurations. Each configuration can be mapped to one or more TCI states. The TCI state associated with each CG type configuration can be signaled by the gNB. For UL transmission, the gNB can instruct the UE to use the active TCI state to determine the UL TX beam. The TCI state can indicate one of the SSB / CSI RS. At step S1835, the UE performs UL transmission in the CG type license of the configuration associated with the active TCI state. For UL transmission in the license of this configuration in CG type 1, the UE uses a UL TX beam that is quasi-co-located with the RX beam of the SSB / CSI RS used to receive the active TCI state. For UL transmission in the license of this configuration in CG type 1, the UE calculates the PL based on the active TCI state. For example, for CG type 2 UL licenses and dynamic UL licenses, the TCI state or SRI used to determine the UL TX beam and PL is indicated in the DCI that schedules those UL licenses.

[0449] Figure 19 A flowchart illustrating a method performed by a user equipment (UE) in a wireless communication system according to an embodiment of the present disclosure is shown.

[0450] In some embodiments, the UE can receive a Radio Resource Control (RRC) message including a beam fault detection configuration from a base station (BS). For example, the beam fault detection configuration may include a list of beam fault detection reference signals, and a TRP indicator in the list may indicate the TRP associated with each beam fault detection reference signal. For example, the beam fault detection configuration may include at least one list of beam fault detection reference signals for each TRP of each BWP of the serving cell. For example, a beam fault detection configuration may be configured for each TRP of the serving cell.

[0451] In some embodiments, the UE can detect beam faults at the transmit-receive point (TRP) of the serving cell through the physical (PHY) layer based on beam fault detection configuration.

[0452] At step S1910, the UE can trigger beam fault recovery of at least one serving cell through the Media Access Control (MAC) layer.

[0453] At step S1920, the UE can identify through the MAC layer whether at least one serving cell in which fault recovery was triggered but not canceled has completed the evaluation of candidate beams.

[0454] At step S1930, the UE can generate a MAC control element (CE) for beam fault recovery based on the identification result through the MAC layer. For example, for at least one serving cell that has detected a beam fault and completed the evaluation of candidate beams, the detection information (i.e., the Ci bit) in the MAC CE is set to 1.

[0455] In some embodiments, the MAC CE may include detection information indicating whether a beam fault has been detected and whether the evaluation of candidate beams has been completed.

[0456] In some embodiments, the detection information may be 1 bit, and when the detection information corresponds to 1, the detection information may indicate that a beam fault has been detected and that the evaluation of candidate beams has been completed.

[0457] In some embodiments, the UE can receive an RRC message including a beam fault recovery configuration from the BS. For example, the beam fault recovery configuration may include a list of candidate beam reference signals, and a TRP indicator in the candidate beam reference signal list may indicate the TRP associated with each beam fault detection reference signal. As another example, the beam fault recovery configuration may include at least one list of candidate beam reference signals for each TRP of each BWP of the serving cell.

[0458] In some embodiments, the UE can start or restart the beam fault detection timer corresponding to the TRP of the serving cell through the MAC layer. Additionally, the UE can update the counter corresponding to the TRP of the serving cell.

[0459] Figure 20 This is a diagram illustrating a UE 2000 according to an embodiment of the present disclosure.

[0460] refer to Figure 20 The UE 2000 may include a processor 2010, a transceiver 2020, and a memory 2030. However, not all of the components shown are necessary. The UE 2000 may be composed of components such as... Figure 20 The implementation can be carried out with more or fewer components. Alternatively, according to another embodiment, the processor 2010, transceiver 2020, and memory 2030 can be implemented as a single chip.

[0461] The above-mentioned components will now be described in detail.

[0462] Processor 2010 may include one or more processors or other processing means that control the provided functions, processes and / or methods. Operation of UE 2000 may be performed by processor 2010.

[0463] Transceiver 2020 can connect to processor 2010 and transmit and / or receive signals. Additionally, transceiver 2020 can receive signals via a wireless channel and output signals to processor 2010. Transceiver 2020 can also transmit signals output from processor 2010 via a wireless channel.

[0464] The memory 2030 may store control information or data included in the signals received by the UE 2000. The memory 2030 may be connected to the processor 2010 and store at least one instruction or protocol or parameter for the provided functions, procedures and / or methods. The memory 2030 may include read-only memory (ROM) and / or random access memory (RAM) and / or hard disk and / or CD-ROM and / or DVD and / or other storage devices.

[0465] Figure 21 This is a diagram illustrating a base station 2100 according to an embodiment of the present disclosure.

[0466] refer to Figure 21 Base station 2100 may include processor 2110, transceiver 2120, and memory 2130. However, not all of the components shown are necessary. Base station 2100 may be composed of... Figure 21 The implementation may involve more or fewer components. Alternatively, according to another embodiment, the processor 2110, transceiver 2120, and memory 2130 may be implemented as a single chip.

[0467] The above-mentioned components will now be described in detail.

[0468] Processor 2110 may include one or more processors or other processing devices that control the provided functions, processes, and / or methods. Operation of base station 2100 may be performed by processor 2110.

[0469] Transceiver 2120 can be connected to processor 2110 and transmit and / or receive signals. Signals may include control information and data. Additionally, transceiver 2120 can receive signals via a wireless channel and output signals to processor 2110. Transceiver 2120 can also transmit signals output from processor 2110 via a wireless channel.

[0470] The memory 2130 may store control information or data included in the signals acquired by the base station 2100. The memory 2130 may be connected to the processor 2110 and store at least one instruction or protocol or parameter for the provided functions, processes and / or methods. The memory 2130 may include read-only memory (ROM) and / or random access memory (RAM) and / or hard disk and / or CD-ROM and / or DVD and / or other storage devices.

[0471] The methods described in the claims of this disclosure or the various embodiments of this disclosure can be implemented in hardware, software, or a combination of hardware and software.

[0472] When implemented in software, a computer-readable storage medium may be provided to store one or more programs (software modules). The one or more programs stored in the computer-readable storage medium are configured to be executed by one or more processors in an electronic device. The one or more programs may include instructions that cause the electronic device to perform methods according to the claims of this disclosure or various embodiments of this disclosure as described in this specification.

[0473] The program (software module, software) can be stored in random access memory (RAM), non-volatile memory including flash memory, read-only memory (ROM), electrically erasable programmable ROM (EEPROM), disk storage devices, compact optical disc-ROM (CD-ROM), digital versatile optical disc (DVD), or other types of optical storage devices and / or magnetic tape cartridges. Alternatively, the program can be stored in a combination of some or all of the memories. Multiple memories may exist.

[0474] The program can also be stored in an attachable storage device, which can be accessed via a communication network including the Internet, intranet, local area network (LAN), wide area network (WAN), or storage area network (SAN), or a combination thereof. The storage device can be connected to a device executing various embodiments of this disclosure via an external port. Additionally, a separate storage device within the communication network can be connected to a device executing various embodiments of this disclosure.

[0475] In various embodiments of this disclosure, components are represented in either a singular or plural form. However, it should be understood that the singular or plural representation is chosen appropriately depending on the presented context for ease of interpretation, and this disclosure is not limited to the singular or plural form of components. Furthermore, a component expressed in a plural form may also imply a singular form, and vice versa.

[0476] Although this disclosure has been described with reference to various embodiments, various changes and modifications will be apparent to those skilled in the art. It is intended that this disclosure cover such changes and modifications that fall within the scope of the appended claims.

Claims

1. A method performed by a user equipment (UE) in a wireless communication system, the method comprising: Receive Radio Resource Control (RRC) messages from base station (BS), the RRC messages containing beam fault detection configuration information and beam fault recovery configuration information; Based on the beam fault detection configuration information, beam faults are detected for at least one Transmitter Receiving Point (TRP) of the serving cell. as well as For the serving cell where a beam fault is detected, beam fault recovery is triggered based on the beam fault recovery configuration information. The beam fault detection configuration information includes a list of at least one beam fault detection reference signals for at least one TRP of the serving cell.

2. The method according to claim 1, in, The TRP indicator in the at least one beam fault detection reference signal list indicates the TRP associated with each beam fault detection reference signal.

3. The method according to claim 1, in, The beam fault detection configuration information and the beam fault recovery configuration information are configured for each TRP of the serving cell.

4. The method according to claim 1, in, The beam fault recovery configuration information includes a list of at least one candidate beam reference signal for the at least one TRP of the serving cell.

5. The method according to claim 4, in, The TRP indicator in the at least one candidate beam reference signal list indicates the TRP associated with each candidate beam reference signal.

6. The method according to claim 1, in, The beam fault detection configuration information includes a beam fault detection timer, and The method also includes: Start or restart the beam fault detection timer corresponding to at least one TRP of the serving cell; and Update the beam fault counter corresponding to at least one TRP of the serving cell.

7. A user equipment (UE) in a wireless communication system, the UE comprising: transceiver; as well as At least one processor, coupled to the transceiver and configured to: Receive Radio Resource Control (RRC) messages from base station (BS), the RRC messages containing beam fault detection configuration information and beam fault recovery configuration information; Based on the beam fault detection configuration information, beam faults are detected for at least one Transmitter Receiving Point (TRP) of the serving cell. as well as For the serving cell where a beam fault is detected, beam fault recovery is triggered based on the beam fault recovery configuration information. The beam fault detection configuration information includes a list of at least one beam fault detection reference signals for at least one TRP of the serving cell.

8. The UE according to claim 7, in, The TRP indicator in the at least one beam fault detection reference signal list indicates the TRP associated with each beam fault detection reference signal.

9. The UE according to claim 7, in, The beam fault detection configuration information and the beam fault recovery configuration information are configured for each TRP of the serving cell.

10. The UE according to claim 7, in, The beam fault recovery configuration information includes a list of at least one candidate beam reference signal for the at least one TRP of the serving cell.

11. The UE according to claim 10, in, The TRP indicator in the at least one candidate beam reference signal list indicates the TRP associated with each candidate beam reference signal.

12. The UE according to claim 7, in, The beam fault detection configuration information includes a beam fault detection timer, and The at least one processor is further configured to: Start or restart the beam fault detection timer corresponding to at least one TRP of the serving cell; and Update the beam fault counter corresponding to at least one TRP of the serving cell.

Images