Method and apparatus for reporting multiple candidate panels

CN116783856BActive Publication Date: 2026-09-25QUALCOMM INC
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202180087937.5
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2021-01-05
Filing Date
2021-12-27
Publication Date
2026-09-25
Estimated Expiration
2041-12-27

Smart Images

  • Figure CN116783856B_ABST
    Figure CN116783856B_ABST
Patent Text Reader

Abstract

Aspects described herein relate to beam failure detection (BFD) for hybrid control and / or control resource sets (CORESETs). In an example, aspects can include identifying one or more CORESET groups, each of the one or more CORESET groups including at least one half duplex (HD) CORESET, a full duplex (FD) CORESET, or a combination thereof; receiving, from a network entity, one or more of the at least one HD CORESET and the FD CORESET of the one or more CORESET groups; performing a BFD measurement procedure with a reference signal associated with at least one CORESET of the one or more CORESET groups; and detecting whether a cell-level failure event or a group-level failure event is triggered based on the BFD measurement procedure.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Cross-reference to related applications

[0002] This patent application claims priority to U.S. Patent Application No. 17 / 141,858, filed January 5, 2021, entitled “TECHNIQUES FOR REPORTING OF MULTIPLE CANDIDATE PANELS PER MEASURED DOWNLINK REFERENCE SIGNALS”, which is assigned to the assignee of this application and is expressly incorporated herein by reference for all purposes. Technical Field

[0003] The aspects of this disclosure generally relate to wireless communication systems, and more particularly to BFD associated with a hybrid control resource set (CORESET) for half-duplex and full-duplex transmission modes when the radio link management (RLM) / beam fault detection (BFD) reference signal (RS) is not explicitly configured via radio resource control (RRC) signaling. Background Technology

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, and broadcasting. These systems can be multiple access systems capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, and Single Carrier Frequency Division Multiple Access (SC-FDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol enabling different wireless devices to communicate at the city, national, regional, and even global levels. For example, fifth-generation (5G) wireless communication technology (which may be referred to as New Radio (NR)) is designed to expand and support a diverse range of use cases and applications relative to current mobile network generations. In one aspect, 5G communication technologies can include: enhanced mobile broadband for human-centric use cases for accessing multimedia content, services, and data; ultra-reliable low latency communication (URLLC) with certain specifications regarding latency and reliability; and massive machine-type communication, which can allow a very large number of connected devices and the transmission of relatively small amounts of non-latency-sensitive information.

[0006] For example, for various communication technologies (such as, but not limited to, NR), if the RLM / BFD RS is not explicitly configured, a complex determination of the implicit BFD is required using a hybrid half-duplex CORESET and FD CORESET. Thus, improvements in wireless communication operation may be desirable. Summary of the Invention

[0007] The following provides a brief overview of one or more aspects to offer a basic understanding of such aspects. This overview is not an exhaustive summary of all conceived aspects, nor is it intended to identify the key or decisive elements of all aspects, nor to define the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as an introduction to the more detailed description that follows.

[0008] According to one example, a method for wireless communication at a user equipment (UE) is provided. The method may include: identifying one or more control resource sets (CORESETs), each of the one or more CORESETs including at least one half-duplex (HD) CORESET, a full-duplex (FD) CORESET, or a combination thereof; receiving from a network entity one or more of the at least one HD CORESET and FD CORESET of the one or more CORESETs; performing a beam fault detection (BFD) measurement procedure using a reference signal associated with at least one CORESET of the one or more CORESETs; and detecting whether a cell-level fault event or a group-level fault event is triggered based on the BFD measurement procedure.

[0009] In a further example, an apparatus for wireless communication is provided, the apparatus including a transceiver, a memory configured to store instructions, and one or more processors communicatively coupled to the transceiver and the memory. The one or more processors are configured to execute instructions to: identify one or more CORESET groups, each of the one or more CORESET groups including at least one HD CORESET, FD CORESET, or a combination thereof; receive from a network entity one or more of the at least one HD CORESET and FD CORESET of the one or more CORESET groups; perform a BFD measurement procedure using a reference signal associated with at least one CORESET of the one or more CORESET groups; and detect whether a cell-level fault event or a group-level fault event is triggered based on the BFD measurement procedure.

[0010] In another aspect, an apparatus for wireless communication is provided, the apparatus comprising: means for identifying one or more CORESET groups, each of the one or more CORESET groups including at least one HD CORESET, FDCORESET, or a combination thereof; means for receiving from a network entity one or more of the at least one HD CORESET and FD CORESET of the one or more CORESET groups; means for performing a BFD measurement procedure using a reference signal associated with at least one CORESET of the one or more CORESET groups; and means for detecting whether a cell-level fault event or a group-level fault event is triggered based on the BFD measurement procedure.

[0011] In another aspect, a non-transient computer-readable medium is provided, comprising code executable by one or more processors to: identify one or more CORESET groups, each of the one or more CORESET groups including at least one HD CORESET, FD CORESET, or a combination thereof; receive from a network entity one or more of the at least one HD CORESET and FD CORESET of the one or more CORESET groups; perform a BFD measurement procedure using a reference signal associated with at least one CORESET of the one or more CORESET groups; and detect whether a cell-level failure event or a group-level failure event is triggered based on the BFD measurement procedure.

[0012] According to another example, a method for wireless communication at a network entity is provided. The method may include: identifying one or more CORESET groups, each of the one or more CORESET groups comprising at least one HD CORESET, FD CORESET, or a combination thereof; transmitting to a UE one or more of the at least one HD CORESET and FD CORESET of the one or more CORESET groups; and receiving a beam fault recovery request from the UE according to at least one of a cell-level fault event or a group-level fault event triggered based on a BFD measurement procedure at the UE.

[0013] In a further example, an apparatus for wireless communication is provided, the apparatus including a transceiver, a memory configured to store instructions, and one or more processors communicatively coupled to the transceiver and the memory. The one or more processors are configured to execute instructions to: determine one or more CORESET groups, each of the one or more CORESET groups including at least one HD CORESET, FD CORESET, or a combination thereof; transmit one or more of the at least one HD CORESET and FD CORESET of the one or more CORESET groups to a UE; and receive a beam fault recovery request from the UE according to at least one of a cell-level fault event or a group-level fault event triggered based on a BFD measurement procedure at the UE.

[0014] In another aspect, an apparatus for wireless communication is provided, the apparatus comprising: means for determining one or more CORESET groups, each of the one or more CORESET groups including at least one HD CORESET, FDCORESET, or a combination thereof; means for transmitting one or more of the at least one HD CORESET and FDCORESET of the one or more CORESET groups to a UE; and means for receiving a beam fault recovery request from the UE according to at least one of a cell-level fault event or a group-level fault event triggered based on a BFD measurement procedure at the UE.

[0015] In another aspect, a non-transient computer-readable medium is provided, comprising code executable by one or more processors to: determine one or more CORESET groups, each of the one or more CORESET groups including at least one HD CORESET, FD CORESET, or a combination thereof; transmit to a UE one or more of the at least one HD CORESET and FD CORESET of the one or more CORESET groups; and receive a beam fault recovery request from the UE according to at least one of a cell-level fault event or a group-level fault event triggered based on a BFD measurement procedure at the UE.

[0016] To achieve the foregoing and related objectives, these one or more aspects include the features fully described below and specifically pointed out in the claims. Certain illustrative features of these one or more aspects are set forth in detail in the following description and drawings. However, these features merely indicate a few of the various ways in which the principles of these various aspects may be employed, and this description is intended to cover all such aspects and their equivalents. Attached Figure Description

[0017] The disclosed aspects will now be described in conjunction with the accompanying drawings, which are provided for illustrative purposes and not for limiting the scope of the disclosure, wherein similar reference numerals denote similar elements, and wherein: Figure 1 Examples of wireless communication systems according to various aspects of this disclosure are explained; Figure 2 It is a block diagram illustrating examples of network entities (also referred to as base stations) according to various aspects of this disclosure; Figure 3 This is a block diagram illustrating examples of user equipment (UE) according to various aspects of this disclosure; Figure 4 This is a flowchart illustrating examples of methods for wireless communication at a UE according to various aspects of this disclosure; Figure 5 This is a flowchart illustrating examples of methods for wireless communication at a network entity according to various aspects of this disclosure; and Figure 6 This is a block diagram illustrating an example of a MIMO communication system including a base station and a UE according to various aspects of this disclosure. Detailed Implementation

[0018] Various aspects will now be described with reference to the accompanying drawings. In the following description, numerous specific details are set forth for illustrative purposes to provide a thorough understanding of one or more aspects. However, it will be apparent that such aspects can be practiced without these specific details.

[0019] The described features generally relate to BFD associated with a hybrid control resource set (CORESET) for both half-duplex and full-duplex transmission modes when the Radio Link Management (RLM) / Beam Failure Detection (BFD) reference signal (RS) is not explicitly configured via Radio Resource Control (RRC) signaling. In one aspect, User Equipment (UE) and the base station can communicate with each other using Tx and Rx beams. For example, the beams can be downlink beams (e.g., on which information can be transmitted from the base station to the UE) or uplink beams (e.g., on which information can be transmitted from the UE to the base station).

[0020] User equipment (UE) and / or base station can communicate in full-duplex mode, in which uplink and downlink communications are exchanged simultaneously or at overlapping times in the same frequency band, or in partially overlapping frequency bands, or in separate frequency bands. The UE and base station can exchange communications using downlink and uplink beam pairs. In half-duplex mode, the UE can perform ongoing uplink or downlink transmissions at different times (via uplink or downlink beams). Compared to half-duplex links, full-duplex links offer increased scalability in terms of data rate. Full-duplex capability can be present in the gNB or the UE, or both. For example, at the UE, uplink transmissions can occur from one panel, while downlink reception can occur in another panel. Full-duplex capability can be conditional on beam separation.

[0021] In a full-duplex link, different antenna elements, subarrays, or antenna panels of a wireless communication device can perform uplink and downlink communication simultaneously or concurrently. The benefits of full-duplex communication include reduced latency (e.g., the possibility of receiving downlink signals in uplink-only slots, resulting in latency savings), enhanced spectral efficiency (e.g., per cell and / or per UE), and more efficient resource utilization.

[0022] The UE can monitor reference signals transmitted by the base station to detect one or more beam failures. Beam failures may occur due to changing channel conditions, obstacles (e.g., physical barriers such as buildings and / or walls that prohibit radio signal transmission), distance from the base station transmitting the beam, interference, etc. The UE can identify a beam failure when the reference signals of a first beam set fail to meet a threshold (e.g., a Qout threshold, which corresponds to a 10% block error rate (BLER) of assumed PDCCH transmission that takes PCFICH errors into account) on a specific number of monitoring times. The UE can perform a beam recovery procedure upon detecting a beam failure, as described in detail elsewhere herein. The reference signals monitored by the UE can be explicitly configured by the base station. If not configured, the reference signals monitored by the UE can be implicitly indicated by RSs in QCL form, which are the same as those in the control channel and can be identified by CORESET.

[0023] Full-duplex communication may present certain challenges compared to half-duplex communication. For example, wireless communication devices (e.g., UEs or base stations) may experience self-interference between uplink and downlink beams or between components of the wireless communication device in a full-duplex link. This self-interference can complicate monitoring reference signals to detect beam faults. Furthermore, self-interference, cross-correlation, etc., that may not occur in a half-duplex link may occur in a full-duplex link. Therefore, due to such self-interference or cross-correlation, the RS (e.g., resource allocation, threshold, etc.) associated with CORESET used for monitoring beam faults in a half-duplex link may be unsuitable or undesirable for monitoring beam faults in a full-duplex link.

[0024] Therefore, this disclosure relates to BFD associated with a hybrid CORESET for both half-duplex and full-duplex transmission modes when the RLM / BFD RS is not explicitly configured via RRC signaling. Specifically, this disclosure provides enhanced bidirectional communication between the UE and a network entity. In one aspect, this disclosure provides apparatus and methods for: identifying one or more CORESET groups, each of the one or more CORESET groups including at least one HD CORESET, FD CORESET, or a combination thereof; receiving from a network entity one or more of the at least one HD CORESET and FD CORESET of the one or more CORESET groups; performing a BFD measurement procedure using a reference signal associated with at least one CORESET of the one or more CORESET groups; and detecting whether a cell-level fault event or a group-level fault event is triggered based on the BFD measurement procedure. In one aspect, this disclosure provides apparatus and methods for: determining one or more CORESET groups, each of the one or more CORESET groups including at least one HD CORESET, FDCORESET, or a combination thereof; transmitting one or more of the at least one HD CORESET and FDCORESET of the one or more CORESET groups to a UE; and receiving a beam fault recovery request from the UE based on at least one of a cell-level fault event or a group-level fault event triggered based on a BFD measurement procedure at the UE.

[0025] The following will refer to Figures 1 to 6 To present the described features in more detail.

[0026] As used herein, the terms “component,” “module,” “system,” and similar terms are intended to include computer-related entities such as, but not limited to, hardware, software, combinations of hardware and software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and / or a computer. For illustration, both an application running on a computing device and the computing device itself can be components. One or more components may reside within a process and / or a thread of execution, and components may be localized on a single computer and / or distributed across two or more computers. Furthermore, these components can be executed from various computer-readable media on which various data structures are stored. These components can communicate by means of local and / or remote processes, such as by means of signals having one or more data packets, such as data from a component interacting with a local system, another component in a distributed system, and / or interacting with other systems across a network such as the Internet. Software should be interpreted broadly as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., regardless of whether it is referred to as software, firmware, middleware, microcode, hardware description languages, or other terms.

[0027] The technologies described herein can be used in various wireless communication systems, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and others. The terms "system" and "network" are generally used interchangeably. CDMA systems can implement radio technologies such as CDMA2000 and Universal Terrestrial Radio Access (UTRA). CDMA2000 encompasses the IS-2000, IS-95, and IS-856 standards. IS-2000 versions 0 and A are commonly referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is commonly referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. TDMA systems can implement radio technologies such as Global System for Mobile Communications (GSM). OFDMA systems can implement radio technologies such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash-OFDM™. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). 3GPP Long Term Evolution (LTE) and LTE Advanced (LTE-A) are newer UMTS versions using E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization called the 3rd Generation Partnership Project (3GPP). CDMA2000 and UMB are described in documents from an organization called the 3rd Generation Partnership Project 2 (3GPP2). The technologies described herein can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies, including cellular communications (e.g., LTE) sharing RF bands. However, the following description describes LTE / LTE-A systems for illustrative purposes, and the term LTE is used in most of the following description, but these technologies can also be applied to applications other than LTE / LTE-A (e.g., to fifth-generation (5G) NR networks or other next-generation communication systems).

[0028] The following description provides examples and is not intended to limit the scope, applicability, or examples set forth in the claims. Changes may be made to the function and arrangement of the elements discussed without departing from the scope of this disclosure. Various procedures or components may be appropriately omitted, substituted, or added to the examples. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Furthermore, features described with reference to some examples may be combined in other examples.

[0029] Various aspects or features will be presented in the form of systems that may include several devices, components, modules, and the like. It should be understood and appreciated that various systems may include additional devices, components, modules, etc., and / or may not include all the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Combinations of these approaches may also be used.

[0030] Figure 1 This is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) may include base station 102, UE 104, evolved packet core (EPC) 160, and / or 5G core (5GC) 190. Base station 102 (which may also be referred to as a network entity) may include macrocells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macrocells may include base stations. Small cells may include femtocells, picocells, and microcells. In one example, base station 102 may also include gNB 180, as further described herein.

[0031] In one example, some nodes (such as base station 102 / gNB 180) may have a modem 240 and a communication component 242, which may (in combination and / or individually) be configured to determine and transmit one or more clusters 248 of cores, including at least one of HD cores 250 and FD cores 252 or a combination thereof, as described herein. Although base station 102 / gNB 180 is shown as having a modem 240 and a communication component 242, this is an illustrative example, and essentially any node or any type of node may include a modem 240 and a communication component 242 to provide the corresponding functionality described herein.

[0032] In one example, a UE (such as UE 104) may have a modem 340 and a communication component 342, which may (in combination and / or individually) be configured to report multiple candidate panels according to the measured downlink reference signal, as described herein. For example, UE 104, in conjunction with modem 340 and / or communication component 342, may receive from base station 102 at least one or more of one or more CORESET groups 248, including at least one HD CORESET 250 and FDCORESET 252, perform a BFD measurement procedure, and transmit a BFD report indicating multiple candidate panels to base station 102. Although UE 104 is shown as having modem 340 and communication component 342, this is an illustrative example, and essentially any node or node of any type may include modem 340 and communication component 342 to provide the corresponding functionality described herein.

[0033] Base station 102 configured for 4G LTE (which may be collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via backhaul link 132 (e.g., using the S1 interface). Base station 102 configured for 5G NR (which may be collectively referred to as Next Generation RAN (NG-RAN)) can interface with 5GC 190 via backhaul link 184. Among other functions, base station 102 may also perform one or more of the following functions: user data delivery, radio channel cryptography and cryptography decoding, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of Non-Access Stratum (NAS) messages, NAS node selection, synchronization, Radio Access Network (RAN) sharing, Multimedia Broadcast Multicast Service (MBMS), subscriber and equipment tracking, RAN Information Management (RIM), paging, location, and delivery of alarm messages. Base stations 102 can communicate directly or indirectly (e.g., via EPC 160 or 5GC 190) with each other on backhaul link 134 (e.g., using an X2 interface). Backhaul links 132, 134 and / or 184 can be wired or wireless.

[0034] Base station 102 can wirelessly communicate with one or more UEs 104. Each base station 102 can provide communication coverage for its respective geographical coverage area 110. Overlapping geographical coverage areas 110 may exist. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. The heterogeneous network may also include a Home Evolved B Node (eNB) (HeNB), which can provide services to a restricted group (which may be referred to as a Closed Subscriber Group (CSG)). The communication link 120 between base station 102 and UE 104 may include uplink (UL) (also referred to as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also referred to as forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity. These communication links may use one or more carriers. For each carrier allocated in a total of up to Yx MHz (e.g., for x component carriers) used for transmission in the DL and / or UL directions, base station 102 / UE 104 may use a spectrum with a bandwidth of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.). These carriers may or may not be adjacent to each other. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell), and the secondary component carriers may be referred to as secondary cells (SCells).

[0035] In another example, some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as the Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be achieved through a wide variety of wireless D2D communication systems, such as, for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0036] The wireless communication system may further include a Wi-Fi access point (AP) 150 communicating with a Wi-Fi station (STA) 152 via a communication link 154 in the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) before communication to determine whether the channel is available.

[0037] Small cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell 102' can employ NR and use the same 5 GHz unlicensed spectrum as that used by Wi-Fi AP 150. Small cell 102' employing NR in unlicensed spectrum can enhance access network coverage and / or increase access network capacity.

[0038] Whether it is a small cell 102' or a large cell (e.g., a macro base station), base station 102 may include an eNB, a gB node (gNB), or other types of base stations. Some base stations (such as gNB 180) may operate in conventional sub-6 GHz spectrum, millimeter wave (mmW) frequencies, and / or near-mmW frequencies to communicate with UE 104. When gNB 180 operates in mmW or near-mmW frequencies, gNB 180 may be referred to as an mmW base station. Extremely high frequency (EHF) is a portion of the RF spectrum in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and wavelengths between 1 mm and 10 mm. Radio waves in this band may be referred to as millimeter waves. Near-mmW extends down to 3 GHz frequencies with a wavelength of 100 mm. Ultra-high frequency (SHF) bands extend between 3 GHz and 30 GHz, and are also referred to as centimeter waves. Communication using mmW / near-mmW RF bands has extremely high path loss and short range. mmW base station 180 can utilize beamforming 182 with UE 104 to compensate for extremely high path loss and short range. Base station 102 as referred to herein may include gNB 180.

[0039] EPC 160 may include Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, Multimedia Broadcast Multicast Service (MBMS) Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and Packet Data Network (PDN) Gateway 172. MME 162 may communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Generally, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are delivered through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP Service 176. IP Service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services. The BM-SC 170 provides functionality for MBMS user service provisioning and delivery. The BM-SC 170 can serve as an entry point for content provider MBMS transmissions, authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and schedule MBMS transmissions. The MBMS gateway 168 can be used to distribute MBMS traffic to base station 102 within a Broadcast-Specific Service Single Frequency Network (MBSFN) area, and can be responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0040] 5GC 190 may include AMF 192, other AMFs 193, Session Management Function (SMF) 194, and User Plane Function (UPF) 195. AMF 192 may communicate with Unified Data Management (UDM) 196. AMF 192 may be a control node that processes signaling between UE 104 and 5GC 190. Generally, AMF 192 provides QoS streaming and session management. User Internet Protocol (IP) packets (e.g., from one or more UEs 104) may be transmitted via UPF 195. UPF 195 provides UE IP address allocation for one or more UEs, as well as other functions. UPF 195 connects to IP service 197. IP service 197 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services.

[0041] The base station may also be referred to as gNB, B-node, evolved B-node (eNB), access point, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit / receive point (TRP), or any other suitable term. Base station 102 provides UE 104 with an access point to EPC 160 or 5GC 190. Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptop devices, personal digital assistants (PDAs), satellite radios, positioning systems (e.g., satellite, terrestrial), multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, robots, drones, industrial / manufacturing equipment, wearable devices (e.g., smartwatches, smart clothing, smart glasses, virtual reality eyepieces, smart wristbands, smart jewelry (e.g., smart rings, smart bracelets)), vehicles / vehicle equipment, meters (e.g., parking meters, electricity meters, gas meters, water meters, flow meters), air pumps, large or small kitchen appliances, medical / healthcare devices, implants, sensors / actuators, displays, or any other similar functional devices. Some UE 104 devices may be referred to as IoT devices (e.g., meters, air pumps, monitors, cameras, industrial / manufacturing equipment, appliances, vehicles, robots, drones, etc.). IoT UEs may include MTC / enhanced MTC (eMTC, also known as CAT-M, Cat M1) UEs, NB-IoT (also known as CAT NB1) UEs, and other types of UEs. In this disclosure, eMTC and NB-IoT may refer to technologies that may evolve from or be based on these technologies. For example, eMTC may include FeMTC (further eMTC), eFeMTC (further enhanced eMTC), mMTC (massive MTC), etc., while NB-IoT may include eNB-IoT (enhanced NB-IoT), FeNB-IoT (further enhanced NB-IoT), etc. UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, radio terminal, remote terminal, handheld device, user agent, mobile client, client, or some other suitable term.

[0042] Now go to Figure 2-5 The aspects are depicted with reference to one or more components and one or more methods that can perform the actions or operations described herein, wherein the aspects shown in the dashed lines may be optional. Although the following... Figure 4 and Figure 5The operations described herein are presented in a specific order and / or performed as by the example components, but it should be understood that the order of these actions and the components performing the actions may vary depending on the implementation. Furthermore, it should be understood that the following actions, functions, and / or described components may be performed by a specially programmed processor, a processor executing specially programmed software or a computer-readable medium, or by any other combination of hardware and / or software components capable of performing the described actions or functions.

[0043] Reference Figure 2 An example of an implementation of a node (such as base station 102 (e.g., base station 102 and / or gNB 180, as described above)) may include various components, some of which have been described above and are further described herein, including components such as one or more processors 212 and memory 216 in communication via one or more buses 244 and transceiver 202, which may operate in conjunction with modem 240 and / or communication component 242 for determining and transmitting one or more CORESET groups 248 including at least one of HDCORESET 250 and FD CORESET 252 or a combination thereof.

[0044] In one aspect, one or more processors 212 may include modem 240 and / or may be part of modem 240 using one or more modem processors. Therefore, various functions associated with communication component 242 may be included in modem 240 and / or processor 212, and in one aspect, may be performed by a single processor, while in other aspects, different functions may be performed by a combination of two or more different processors. For example, in one aspect, the one or more processors 212 may include any one or any combination of: modem processor, or baseband processor, or digital signal processor, or transmitter processor, or receiver processor, or transceiver processor associated with transceiver 202. In other aspects, some features of the features of one or more processors 212 and / or modem 240 associated with communication component 242 may be performed by transceiver 202.

[0045] Furthermore, memory 216 may be configured to store data used herein and / or a local version of application 275, or communication component 242 and / or one or more sub-components thereof executed by at least one processor 212. Memory 216 may include any type of computer-readable medium that can be used by a computer or at least one processor 212, such as random access memory (RAM), read-only memory (ROM), tape, magnetic disk, optical disk, volatile memory, non-volatile memory, and any combination thereof. In one aspect, for example, when base station 102 is operating at least one processor 212 to execute communication component 242 and / or one or more sub-components thereof, memory 216 may be a non-transient computer-readable storage medium storing one or more computer-executable codes defining communication component 242 and / or one or more sub-components thereof and / or data associated therewith.

[0046] Transceiver 202 may include at least one receiver 206 and at least one transmitter 208. Receiver 206 may include hardware for receiving data and / or processor-executable software code comprising instructions and stored in memory (e.g., a computer-readable medium). Receiver 206 may be, for example, a radio frequency (RF) receiver. In one aspect, receiver 206 may receive signals transmitted by at least one base station 102. Additionally, receiver 206 may process such received signals and may also obtain measurements of the signals, such as, but not limited to, Ec / Io, signal-to-noise ratio (SNR), reference signal received power (RSRP), received signal strength indicator (RSSI), etc. Transmitter 208 may include hardware for transmitting data and / or processor-executable software, comprising instructions and stored in memory (e.g., a computer-readable medium). Suitable examples of transmitter 208 may include, but are not limited to, RF transmitters.

[0047] Furthermore, in one aspect, base station 102 may include an RF front-end 288, which is communicatively operable with one or more antennas 265 and transceiver 202 for receiving and transmitting radio transmissions, such as wireless communications transmitted by at least one base station 102 or wireless transmissions transmitted by UE 104. The RF front-end 288 may be connected to one or more antennas 265 and may include one or more low-noise amplifiers (LNAs) 290, one or more switches 292, one or more power amplifiers (PAs) 298, and one or more filters 296 for transmitting and receiving RF signals. Antennas 265 may include one or more antennas, antenna elements, and / or antenna arrays.

[0048] On one hand, the LNA 290 can amplify the received signal to a desired output level. On another hand, each LNA 290 can have specified minimum and maximum gain values. On yet another hand, the RF front end 288 can use one or more switches 292 to select a particular LNA 290 and its specified gain value based on the desired gain value for a particular application.

[0049] Furthermore, for example, one or more PAs 298 may be used by the RF front end 288 to amplify the signal to obtain an RF output at a desired output power level. In one aspect, each PA 298 may have specified minimum and maximum gain values. In another aspect, the RF front end 288 may use one or more switches 292 to select a particular PA 298 and its specified gain value based on the desired gain value for a particular application.

[0050] Additionally, for example, one or more filters 296 may be used by the RF front end 288 to filter the received signal to obtain the input RF signal. Similarly, in one aspect, for example, a corresponding filter 296 may be used to filter the output from a corresponding PA 298 to produce an output signal for transmission. In one aspect, each filter 296 may be connected to a specific LNA 290 and / or PA 298. In one aspect, the RF front end 288 may use one or more switches 292 to select the transmit or receive path using a specified filter 296, LNA 290, and / or PA 298 based on a configuration as specified by the transceiver 202 and / or processor 212.

[0051] Thus, transceiver 202 can be configured to transmit and receive wireless signals via RF front-end 288 through one or more antennas 265. In one aspect, the transceiver can be tuned to operate at a specified frequency so that UE 104 can, for example, communicate with one or more base stations 102 or one or more cells associated with one or more base stations 102. In another aspect, for example, modem 240 can configure transceiver 202 to operate at a specified frequency and power level based on the UE configuration of UE 104 and the communication protocol used by modem 240.

[0052] In one aspect, modem 240 may be a multi-band, multi-mode modem capable of processing digital data and communicating with transceiver 202 to enable the use of transceiver 202 to transmit and receive digital data. In another aspect, modem 240 may be multi-band and configured to support multiple frequency bands for a specific communication protocol. In another aspect, modem 240 may be multi-mode and configured to support multiple operating networks and communication protocols. In one aspect, modem 240 may control one or more components of UE 104 (e.g., RF front-end 288, transceiver 202) to transmit and / or receive signals from the network based on a specified modem configuration. In one aspect, the modem configuration may be based on the modem's mode and the frequency band used. In another aspect, the modem configuration may be based on UE configuration information associated with UE 104, such as information provided by the network during cell selection and / or cell reselection.

[0053] On one hand, processors 212 may correspond to the combination of Figure 6 The UE describes one or more of the processors. Similarly, memory 216 may correspond to the combination of Figure 6 The memory described by the UE in the text.

[0054] Reference Figure 3 An example of an implementation of UE 104 may include various components, some of which have been described above and are further described herein, including components such as one or more processors 312 and memory 316 communicating via one or more buses 344 and transceiver 202, which may operate in conjunction with modem 340 and / or communication component 342 to identify one or more CORESET groups 248, each of which includes at least one HD CORESET 250, FD CORESET 252 or a combination thereof.

[0055] Transceiver 302, receiver 306, transmitter 308, one or more processors 312, memory 316, application 375, bus 344, RF front end 388, LNA 390, switch 392, filter 396, PA 398, and one or more antennas 365 may be the same as or similar to the corresponding components of base station 102 as described above, but are configured or otherwise programmed for use in base station operation rather than base station operation.

[0056] On one hand, processors 312 may correspond to the combination of Figure 6 The base station described in the text refers to one or more of the processors. Similarly, memory 316 may correspond to the combination of... Figure 6 The memory described by the base station in the text.

[0057] The described features generally relate to BFD associated with a hybrid core set for both half-duplex and full-duplex transmission modes when the RLM / BFD RS is not explicitly configured via RRC signaling. In one aspect, two core set groups can be established. For example, the first group may consist only of HD core sets, while the second group may consist only of FDC core sets. In this example, four core sets can be established. The first group may include two core sets corresponding to HD core sets, while the second group may include two additional core sets corresponding to FD core sets. These groups can be predetermined at the gNB and / or UE.

[0058] In another example, two hybrid HD and FD core set groups can be defined. In this example, four core sets can be established. The first group can include two core sets corresponding to the FD core set and the HD core set. Similarly, the second group can include two core sets corresponding to the FD core set and the HD core set. Different groups can be defined for different Transport Receiver Points (TRPs) or TRP pairs. These groups can be signaled to the UE by the gNB.

[0059] On one hand, for the Channel State Information Reference Signal (CSI-RS) serving as the BFD RS, the UE can determine the TCI state (e.g., the CSI-RS beam) of type D in the corresponding HD or FD CORESET ID, which is of quasi-co-location (QCL) type D. The UE can then perform downlink beam BFD / RRM measurements at the corresponding CSI-RS resource location of the CSI-RS beam corresponding to this TCI state. For FD BFD RS other than CSI-RS, the UL beam needs to be determined (e.g., the probe reference signal (SRS) beam paired with the CSI-RS beam in the corresponding FD CORESET ID). Subsequently, the UE can perform UL beam (e.g., self-interference) BFD / RRM measurements to measure the SRS ID beam in the configured resource. For HD mode, using one or more DL CSI-RS beams, the UE can calculate the L1-RSRP for BFD / RRM. For FD mode, using one or more paired DL CSI-RS and UL SRS beam pairs, the UE can calculate the L1-SINR for BFD / RRM.

[0060] On the one hand, a full-beam fault can correspond to a cell-level fault, while a partial-beam fault can correspond to a group-level fault. For example, for two CORESET groups, a fault in either group can be indicated as a full-beam fault that can be triggered as an event of a cell-level fault. Furthermore, an HD CORESET group can be defined as a partial-beam fault that can be triggered as an event of a group-level fault. Additionally, an FD CORESET group can also be defined as a partial-beam fault that can be triggered as an event of a group-level fault.

[0061] On one hand, for one of the two CORESET groups, a fault in that group can be indicated as a full-beam fault that can be triggered as a cell-level fault event. For example, an HD CORESET group can be defined as a full-beam fault that can be triggered as a cell-level fault event. Conversely, an FD CORESET group can be defined as a partial-beam fault that can be triggered as a group-level fault event. In another example, an FD CORESET group can be defined as a full-beam fault that can be triggered as a cell-level fault event. Furthermore, an HD CORESET group can be defined as a partial-beam fault that can be triggered as a group-level fault event. The determination of how each aspect can be defined can be predetermined. If both aspects are enabled, the gNB can signal this determination for use in BFD.

[0062] Now go to Figure 4 and Figure 5 The aspects are depicted with reference to one or more components and one or more methods that can perform the actions or operations described herein, wherein the aspects shown in the dashed lines may be optional. Although the following... Figure 4 and Figure 5 The operations described herein are presented in a specific order and / or performed as by the example components; however, it should be understood that the order of these actions and the components performing the actions may vary depending on the implementation. Furthermore, it should be understood that references... Figure 1 , Figure 2 , Figure 4 and / or Figure 6 As described herein, the following actions, functions and / or components may be performed by one or more components of a specially programmed processor, a processor executing specially programmed software or a computer-readable medium, or any other combination of hardware and / or software components capable of performing the actions or functions.

[0063] Figure 4 A flowchart illustrating an example of a method 400 for wireless communication at a network entity (such as UE 104) is provided. In one example, UE 104 can use... Figure 1 , Figure 2 , Figure 4 and Figure 6One or more components as described in method 400 are used to perform the functions described in method 400.

[0064] In block 402, method 400 may identify one or more CORESET groups, each of which includes at least one HD CORESET, FD CORESET, or a combination thereof. In one aspect, communication component 342 (e.g., in conjunction with processor 312, memory 316, and / or transceiver 302) may be configured to identify one or more CORESET groups 248, each of which includes at least one HD CORESET 250, FD CORESET 252, or a combination thereof. Therefore, UE 104, processor 312, communication component 342, or one of its sub-components may define means for identifying one or more CORESET groups 248, each of which includes at least one HD CORESET 250, FD CORESET 252, or a combination thereof.

[0065] In some respects, the one or more CORESET groups 248 include a first group containing only one or more HD CORESET 250 and a second group containing only one or more FD CORESET 252.

[0066] In some respects, each of the one or more CORESET groups 248 includes a combination of one or more HD CORESET 250 and one or more FD CORESET 252.

[0067] In some respects, each of one or more Transmitting and Receiving Points (TRPs) or TRP pairs includes a different group in the one or more CORESET groups 248. For example, a TRP may correspond to one or more of a UE (such as UE 140) and a network entity (such as base station 102).

[0068] In some respects, the UE 104, processor 312, communication component 342, or any of its sub-components configured to identify the one or more CORESET groups 248 further includes receiving a message from network entity 102 indicating the one or more CORESET groups 248.

[0069] In block 404, method 400 can receive one or more of the at least one HD CORESET and FD CORESET of the one or more CORESET groups from the network entity. In one aspect, communication component 342 (e.g., in conjunction with processor 312, memory 316, and / or transceiver 302) can be configured to receive one or more of the at least one HD CORESET 250 and FD CORESET 252 of the one or more CORESET groups 248 from the network entity 102. Therefore, UE 104, processor 312, communication component 342, or any of its sub-components can define means for receiving one or more of the at least one HD CORESET 250 and FD CORESET 252 of the one or more CORESET groups 248 from the network entity 102.

[0070] In block 406, method 400 may perform a BFD measurement procedure using a reference signal associated with at least one of the CORESETs in the one or more CORESET groups 248. In one aspect, communication component 342 (e.g., in conjunction with processor 312, memory 316, and / or transceiver 302) may be configured to perform a BFD measurement procedure using a reference signal associated with at least one of the CORESETs in the one or more CORESET groups 248. Therefore, UE 104, processor 312, communication component 342, or any of its sub-components may define means for performing a BFD measurement procedure using a reference signal associated with at least one of the CORESETs in the one or more CORESET groups 248.

[0071] In some respects, the UE 104, processor 312, communication component 342, or one of its sub-components configured to perform BFD measurement procedures using a reference signal further includes determining a reference signal associated with a Transmission Configuration Indicator (TCI) state of quasi-co-location (QCL) type D in the corresponding identifier (ID) of the at least one HD CORESET 250 and FD CORESET 252 when the BFD reference signal is not explicitly configured.

[0072] In some respects, this reference signal corresponds to Channel State Information RS (CSI-RS) or SSB.

[0073] In some respects, UE 104, processor 312, communication component 342, or one of its sub-components may be configured to perform downlink BFD / Radio Resource Management (RRM) measurement procedures at one or more CSI-RS resource locations of the CSI-RS beam corresponding to the TCI state.

[0074] In some respects, UE 104, processor 312, communication component 342 or one of its sub-components may be configured to calculate the Layer 1 (L1) reference signal received power (RSRP) for BFD / RRM measurement procedures based on one or more downlink CSI-RS beams.

[0075] In some respects, UE 104, processor 312, communication component 342, or any of its sub-components may be configured to detect an uplink beam corresponding to a probe reference signal (SRS) beam, the SRS beam being matched to a CSI-RS beam corresponding to a bidirectional TCI state of downlink and uplink RS / beam pairs in the corresponding ID of FD CORESET 252; perform uplink BFD / RRM measurement procedures for the SRS uplink beam to measure self-interference; and perform downlink BFD / RRM measurement procedures for the CSI-RS or SSB downlink beam to measure downlink signal quality.

[0076] In some respects, UE 104, processor 312, communication component 342, or one of its sub-components may be configured to calculate the L1 signal-to-interference-plus-noise ratio (SINR) for BFD / RRM measurement procedures based on one or more downlink CSI-RS beams and uplink SRS beam pairs.

[0077] In block 408, method 400 can detect whether a cell-level fault event or a group-level fault event is triggered based on a BFD measurement procedure. In one aspect, communication component 342 (e.g., in conjunction with processors 312, memory 316, and / or transceiver 302) can be configured to detect whether a cell-level fault event or a group-level fault event is triggered based on a BFD measurement procedure. Therefore, UE 104, processors 312, communication component 342, or any of their sub-components can define means for detecting whether a cell-level fault event or a group-level fault event is triggered based on a BFD measurement procedure.

[0078] In some respects, UE 104, processor 312, communication component 342, or any of its sub-components may be configured to perform a fault recovery procedure in response to the detection of at least one of a cell-level fault event or a group-level fault event.

[0079] In some respects, UE 104, processor 312, communication component 342, or any of its sub-components may be configured to detect an uplink beam corresponding to a probe reference signal (SRS) beam, the SRS beam being matched to a CSI-RS beam corresponding to a bidirectional TCI state of downlink and uplink RS / beam pairs in the corresponding ID of FD CORESET 252; perform uplink BFD / RRM measurement procedures for the SRS uplink beam to measure self-interference; and perform downlink BFD / RRM measurement procedures for the CSI-RS or SSB downlink beam to measure downlink signal quality.

[0080] In some respects, UE 104, processor 312, communication component 342, or one of its sub-components may be configured to calculate the L1 signal-to-interference-plus-noise ratio (SINR) for BFD / RRM measurement procedures based on one or more downlink CSI-RS beams and uplink SRS beam pairs.

[0081] In some respects, the UE 104, (a) processor 312, communication component 342 or one of its sub-components configured to detect whether a cell-level fault event or a group-level fault event has been triggered further includes detecting, based on the triggering of a cell-level fault event, that a full-beam fault event has occurred for all CORESET groups in the one or more CORESET groups 248.

[0082] In some aspects, the one or more CORESET groups 248 include HD CORESET groups and FD CORESET groups, and the detection of a full beam failure event for all CORESET groups in the one or more CORESET groups further includes: detecting a first partial beam failure event for the HD CORESET group based on the triggering of a group-level failure event; and detecting a second partial beam failure event for the FD CORESET group based on the triggering of a group-level failure event.

[0083] In some respects, the UE 104, (a) processor 312, communication component 342 or any of its sub-components configured to detect whether a cell-level fault event or a group-level fault event has been triggered further includes detecting, based on the triggering of a cell-level fault event, that a full-beam fault event has occurred for at least one of the one or more CORESET groups 248.

[0084] In some aspects, the at least one CORESET group in the one or more CORESET groups 248 corresponds to an HDCORESET group, and the detection of a full beam failure event for the at least one CORESET group in the one or more CORESET groups further includes detecting a partial beam failure event for the FD CORESET group in the one or more CORESET groups 248 based on the triggering of a group-level failure event.

[0085] In some aspects, the at least one CORESET group in the one or more CORESET groups 248 corresponds to an FDCORESET group, and the detection of a full-beam fault event for the at least one CORESET group in the one or more CORESET groups further includes detecting a partial beam fault event for the HD CORESET group in the one or more CORESET groups 248 based on the triggering of a group-level fault event. In one example, UE 104 can be configured to determine which use case corresponding to the at least one CORESET group in the one or more CORESET groups corresponds to the HDCORESET group or which use case corresponding to the at least one CORESET group in the one or more CORESET groups corresponds to the FD CORESET group in order to perform BFD. In some instances, if both use cases are configured, UE 104 can receive a signal from base station 102 indicating which use case should be used for BFD.

[0086] Figure 5 A flowchart illustrating an example of a method 500 for wireless communication at a network entity (such as network entity 102) is provided. In one example, base station 102 can use... Figure 1 , Figure 2 , Figure 4 and Figure 6 One or more components as described in method 500 are used to perform the functions described in method 500.

[0087] In block 502, method 500 may determine one or more CORESET groups, each of which includes at least one HD CORESET, FD CORESET, or a combination thereof. In one aspect, communication component 242 (e.g., in conjunction with processor 212, memory 216, and / or transceiver 202) may be configured to determine one or more CORESET groups 248, each of which includes at least one HD CORESET 250, FD CORESET 252, or a combination thereof. Therefore, base station 102, processor 212, communication component 242, or any of its sub-components may define means for determining one or more CORESET groups 248, each of which includes at least one HD CORESET 250, FD CORESET 252, or a combination thereof.

[0088] In some respects, the one or more CORESET groups 248 include a first group containing only one or more HD CORESET 250 and a second group containing only one or more FD CORESET 252.

[0089] In some respects, each of the one or more CORESET groups 248 includes a combination of one or more HD CORESET 250 and one or more FD CORESET 252.

[0090] In some respects, each of one or more Transmitting and Receiving Points (TRPs) or TRP pairs includes a different group in the one or more CORESET groups 248. For example, a TRP may correspond to one or more of a UE (such as UE 140) and a network entity (such as base station 102).

[0091] In block 504, method 500 may transmit to the UE one or more of the at least one HD CORESET and FD CORESET of the one or more CORESET groups 248. In one aspect, communication component 242 (e.g., in conjunction with processor 212, memory 216, and / or transceiver 202) may be configured to transmit to the UE 104 one or more of the at least one HD CORESET 250 and FD CORESET 252 of the one or more CORESET groups 248. Therefore, base station 102, processor 212, communication component 242, or any of its sub-components may define means for transmitting to the UE 104 one or more of the at least one HD CORESET 250 and FD CORESET 252 of the one or more CORESET groups 248.

[0092] In block 506, method 500 may receive a beam fault recovery request from the UE based on at least one of a cell-level fault event or a group-level fault event triggered based on a BFD measurement procedure at the UE. In one aspect, communication component 242 (e.g., in conjunction with processor 212, memory 216, and / or transceiver 202) may be configured to receive a beam fault recovery request from the UE 104 based on at least one of a cell-level fault event or a group-level fault event triggered based on a BFD measurement procedure at the UE 104. Therefore, base station 102, processor 212, communication component 242, or any of its sub-components may define means for receiving a beam fault recovery request from the UE 104 based on at least one of a cell-level fault event or a group-level fault event triggered based on a BFD measurement procedure at the UE 104.

[0093] In some respects, base station 102, processor 212, communication component 242 or one of its sub-components may be configured to transmit from network entity 102 a message indicating the one or more CORESET groups 248.

[0094] In some respects, base station 102, processor 212, communication component 242 or one of its sub-components may be configured to determine the bidirectional TCI status of the at least one HD CORESET 250 and FD CORESET 252 in the form of a quasi-co-location (QCL) type D, which may include downlink and uplink RS / beam pairs.

[0095] In some respects, base station 102, processor 212, communication component 242, or one of its sub-components may be configured to receive from UE 104 a BFD report based on the transmission of one or more of the at least one HD CORESET 250 and FD CORESET 252, wherein the BFD report indicates that at least one of a cell-level failure event or a group-level failure event is triggered based on a BFD measurement procedure performed by UE 104.

[0096] In some respects, the BFD report includes L1 RSRP for the BFD / RRM measurement procedure performed by UE 104 based on one or more downlink CSI-RS beams.

[0097] In some respects, the BFD report includes the L1 SINR for the BFD / RRM measurement procedure performed by UE 104 based on one or more downlink CSI-RS beams and uplink SRS beams.

[0098] In some respects, the BFD report indicates that a full-beam failure event has occurred for all CORESET groups in one or more CORESET groups 248, based on the triggering of a cellular-level failure event.

[0099] In some respects, the BFD report indicates that a full-beam failure event has occurred for at least one of the one or more CORESET groups 248, based on the triggering of a cellular-level failure event.

[0100] Figure 6 This is a block diagram of a MIMO communication system 600 including base station 102 and UE 104. The MIMO communication system 600 can be explained by referring to... Figure 1 The wireless communication access network 100 described herein. Base station 102 may be a reference. Figure 1 Examples of various aspects of the described base station 102 are provided. Base station 102 may be equipped with antennas 634 and 635, and UE 104 may be equipped with antennas 652 and 653. In the MIMO communication system 600, base station 102 can transmit data simultaneously on multiple communication links. Each communication link may be referred to as a "layer," and the "rank" of the communication link indicates the number of layers used for communication. For example, in a 2x2 MIMO communication system where base station 102 transmits two "layers," the rank of the communication link between base station 102 and UE 104 is 2.

[0101] At base station 102, transmit (Tx) processor 620 can receive data from a data source. Transmit processor 620 can process this data. Transmit processor 620 can also generate control symbols or reference symbols. Transmit MIMO processor 630 can perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, or reference symbols where applicable, and can provide the output symbol stream to transmit modulators / demodulators 632 and 633. Each modulator / demodulator 632 to 633 can process its respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator / demodulator 632 to 633 can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a DL signal. In one example, the DL signal from modulators / demodulators 632 and 633 can be transmitted via antennas 634 and 635, respectively.

[0102] UE 104 can be a reference Figure 1 and Figure 3Examples of various aspects of the described UE 104. At UE 104, UE antennas 652 and 653 can receive DL signals from base station 102 and can provide the received signals to modulators / demodulators 654 and 655, respectively. Each modulator / demodulator 654 to 655 can condition (e.g., filter, amplify, down-convert, and digitize) its respective received signal to obtain an input sample. Each modulator / demodulator 654 to 655 can further process the input sample (e.g., for OFDM, etc.) to obtain received symbols. MIMO detector 656 can obtain the received symbols from modulators / demodulators 654 and 655, perform MIMO detection on these received symbols where applicable, and provide detected symbols. Receive (Rx) processor 658 can process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide the decoded data to UE 104 to a data output, and provide the decoded control information to processor 680 or memory 682.

[0103] In some cases, processor 680 may execute stored instructions to instantiate communication component 342 (e.g., see...). Figure 1 and 3 ).

[0104] On the uplink (UL), at UE 104, transmit processor 664 can receive and process data from a data source. Transmit processor 664 can also generate reference symbols for a reference signal. Symbols from transmit processor 664 can be pre-encoded by transmit MIMO processor 666 where applicable, further processed by modulators / demodulators 654 and 655 (e.g., for SC-FDMA, etc.), and transmitted to base station 102 according to communication parameters received from base station 102. At base station 102, UL signals from UE 104 can be received by antennas 634 and 635, processed by modulators / demodulators 632 and 633, detected by MIMO detector 636 where applicable, and further processed by receive processor 638. Receive processor 638 can provide decoded data to data output and processor 640 or memory 642.

[0105] In some cases, processor 640 may execute stored instructions to instantiate communication component 242 (e.g., see...). Figure 1 and 2 ).

[0106] Components of UE 104 may be implemented individually or collectively using one or more ASICs adapted to perform some or all of the applicable functions in hardware. Each of the mentioned modules may be means for performing one or more functions related to the operation of the MIMO communication system 600. Similarly, components of base station 102 may be implemented individually or collectively using one or more ASICs adapted to perform some or all of the applicable functions in hardware. Each of the mentioned components may be means for performing one or more functions related to the operation of the MIMO communication system 600.

[0107] Some additional example terms

[0108] Examples of implementations are described in the following numbered clauses: 1. A method for conducting wireless communication at a user equipment (UE), comprising: Identify one or more control resource sets (CORESETs), each of which includes at least one half-duplex (HD) CORESET, a full-duplex (FD) CORESET, or a combination thereof; Receive one or more of the at least one HD CORESET and FD CORESET from the one or more CORESET groups from the network entity; Beam Fault Detection (BFD) measurement procedures are performed using a reference signal associated with at least one CORESET in the group of one or more CORESETs; and Detect whether a cell-level or group-level fault event is triggered based on this BFD measurement procedure.

[0109] 2. The method as described in any of the foregoing clauses, wherein the one or more CORESET groups comprise a first group containing only one or more HD CORESETs and a second group containing only one or more FD CORESETs.

[0110] 3. The method as described in any of the foregoing clauses, wherein each of the one or more CORESET groups comprises a combination of one or more HD CORESETs and one or more FD CORESETs.

[0111] 4. As in any of the foregoing provisions, wherein each of the one or more Transmitting and Receiving Points (TRPs) or TRP pairs comprises a different group within the one or more CORESET groups.

[0112] 5. The method as described in any of the foregoing clauses, wherein identifying the one or more CORESET groups further comprises: receiving a message from a network entity indicating the one or more CORESET groups.

[0113] 6. The method as described in any of the foregoing clauses further includes: performing a fault recovery procedure in response to detecting at least one of a cellular-level fault event or a group-level fault event.

[0114] 7. The method as described in any of the foregoing clauses, wherein performing the BFD measurement procedure using the reference signal further comprises: determining the RS using the Transmission Configuration Indicator (TCI) state of the corresponding identifier (ID) of the at least one HD CORESET and FD CORESET in the form of a quasi-co-located (QCL) type D.

[0115] 8. The method as described in any of the foregoing clauses, wherein the reference signal corresponds to Channel State Information RS (CSI-RS).

[0116] 9. The method as described in any of the foregoing clauses further includes: performing downlink BFD / Radio Resource Management (RRM) measurement procedures at one or more CSI-RS resource locations of the CSI-RS beam corresponding to the TCI state.

[0117] 10. The method as described in any of the foregoing clauses further includes: calculating the Layer 1 (L1) reference signal received power (RSRP) for the BFD / RRM measurement protocol based on one or more downlink CSI-RS beams.

[0118] 11. The methods described in any of the foregoing clauses further include: Detect the uplink beam corresponding to the detection reference signal (SRS) beam, which is matched with the CSI-RS beam corresponding to the TCI state in the corresponding ID of the FDCORESET; and Uplink BFD / RRM measurement procedures were performed on this SRS beam to measure self-interference.

[0119] 12. The method as described in any of the foregoing clauses further includes: calculating the Layer 1 (L1) signal-to-interference-plus-noise ratio (SINR) for the BFD / RRM measurement protocol based on one or more downlink CSI-RS beams and uplink probe reference signal (SRS) beam pairs.

[0120] 13. The method of any of the foregoing clauses, wherein detecting whether a cell-level fault event or a group-level fault event has been triggered further comprises: detecting, based on the triggering of a cell-level fault event, that a full-beam fault event has occurred for all CORESET groups in the one or more CORESET groups.

[0121] 14. The method as described in any of the foregoing clauses, wherein the one or more CORESET groups include HD CORESET groups and FD CORESET groups, and

[0122] The detection of a full-beam failure event for all CORESET groups in one or more CORESET groups further includes: Detection of the first portion of beam fault events for the HD CORESET group based on the triggering of group-level fault events; and The detection of second-part beam fault events for the FD CORESET group is based on the triggering of group-level fault events.

[0123] 15. The method of any of the foregoing clauses, wherein detecting whether a cell-level fault event or a group-level fault event has been triggered further comprises: detecting, based on the triggering of a cell-level fault event, that a full-beam fault event has occurred for at least one of the one or more CORESET groups.

[0124] 16. The method as described in any of the foregoing clauses, wherein the at least one CORESET group in the one or more CORESET groups corresponds to the HD CORESET group, and

[0125] The detection of a full-beam failure event for at least one of the one or more CORESET groups further includes: This is based on the detection of partial beam fault events for FD CORESET groups within one or more CORESET groups, triggered by group-level fault events.

[0126] 17. The method as described in any of the foregoing clauses, wherein the at least one CORESET group in the one or more CORESET groups corresponds to the FD CORESET group, and

[0127] The detection of a full-beam failure event for at least one of the one or more CORESET groups further includes: This is based on the detection of partial beam failure events for HD CORESET groups within one or more CORESET groups, triggered by group-level failure events.

[0128] 18. A method for wireless communication at a network entity, comprising: Identify one or more control resource sets (CORESETs), each of the one or more CORESETs comprising at least one half-duplex (HD) CORESET, a full-duplex (FD) CORESET, or a combination thereof; Transmit one or more of the at least one HD CoreSet and FDC CoreSet of the one or more CoreSet groups to the User Equipment (UE); and A beam fault recovery request is received from the UE based on at least one of a cell-level fault event or a group-level fault event triggered by a BFD measurement procedure at the UE.

[0129] 19. The method as described in any of the foregoing clauses, wherein the one or more CORESET groups comprise a first group containing only one or more HD CORESETs and a second group containing only one or more FD CORESETs.

[0130] 20. The method as described in any of the foregoing clauses, wherein each of the one or more CORESET groups comprises a combination of one or more HD CORESETs and one or more FD CORESETs.

[0131] 21. As in any of the foregoing provisions, wherein each of the one or more Transmitting and Receiving Points (TRPs) or TRP pairs comprises a different group in the one or more CORESET groups.

[0132] 22. The method as described in any of the foregoing clauses further includes: transmitting a message from the network entity indicating the one or more CORESET groups.

[0133] 23. The method as described in any of the foregoing clauses further includes: determining the Transport Configuration Indicator (TCI) state of the corresponding identifier (ID) of the at least one HD CORESET and FDCORESET, which is of quasi-co-location (QCL) type D.

[0134] 24. The method as described in any of the foregoing provisions further includes: receiving from the UE a beam fault detection (BFD) report based on the transmission of one or more of the at least one HDCORESET and FD CORESET, wherein the BFD report indicates that at least one of a cell-level fault event or a group-level fault event is triggered based on a BFD measurement procedure performed by the UE.

[0135] 25. The method as described in any of the foregoing clauses, wherein the BFD report includes the Layer 1 (L1) reference signal received power (RSRP) for a BFD / Radio Resource Management (RRM) measurement procedure performed by the UE based on one or more downlink channel state information reference signal (CSI-RS) beams.

[0136] 26. The method as described in any of the foregoing clauses, wherein the BFD report includes the Layer 1 (L1) signal-to-interference-plus-noise ratio (SINR) for the BFD / Radio Resource Management (RRM) measurement procedure performed by the UE based on one or more downlink Channel State Information Reference Signal (CSI-RS) beams and uplink Probe Reference Signal (SRS) beams.

[0137] 27. The method of any of the foregoing clauses, wherein the BFD report is based on the triggering of a cell-level failure event to indicate that a full beam failure event has occurred for all CORESET groups in the one or more CORESET groups.

[0138] 28. The method of any of the foregoing clauses, wherein the BFD report indicates that a full beam failure event has occurred for at least one of the one or more CORESET groups based on the triggering of a cellular-level failure event.

[0139] 29. An apparatus for wireless communication, comprising: transceiver; Memory configured to store instructions; and One or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to: Identify one or more control resource sets (CORESETs), each of which includes at least one half-duplex (HD) CORESET, a full-duplex (FD) CORESET, or a combination thereof; Receive one or more of the at least one HD CORESET and FD CORESET from the one or more CORESET groups from the network entity; Beam Fault Detection (BFD) measurement procedures are performed using a reference signal associated with at least one CORESET in the group of one or more CORESETs; and Detect whether a cell-level or group-level fault event is triggered based on this BFD measurement procedure.

[0140] 30. An apparatus for wireless communication, comprising: transceiver; Memory configured to store instructions; and One or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to: Identify one or more control resource sets (CORESETs), each of the one or more CORESETs comprising at least one half-duplex (HD) CORESET, a full-duplex (FD) CORESET, or a combination thereof; Transmit one or more of the at least one HD CoreSet and FDC CoreSet of the one or more CoreSet groups to the User Equipment (UE); and A beam fault recovery request is received from the UE based on at least one of a cell-level fault event or a group-level fault event triggered by a BFD measurement procedure at the UE.

[0141] The detailed description above, in conjunction with the accompanying drawings, describes examples and does not represent only examples that can be implemented or fall within the scope of the claims. The term "example" as used in this description means "serving as an example, instance, or illustration," and not "superior to" or "better than other examples." This detailed description includes specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0142] Information and signals can be represented using any of a wide variety of different techniques and technologies. For example, data, instructions, commands, information, signals, bits, symbols, and chips, which may be referred to throughout the above description, can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, computer-executable code or instructions stored on a computer-readable medium, or any combination thereof.

[0143] The various explanatory frames and components described herein can be implemented or executed using specially programmed devices, such as, but not limited to, processors, digital signal processors (DSPs), ASICs, FPGAs, or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. A specially programmed processor may be a microprocessor, but in alternatives, the processor may be any conventional processor, controller, microcontroller, or state machine. A specially programmed processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration.

[0144] The functions described herein can be implemented in hardware, software, or any combination thereof. If implemented in software executed by a processor, the functions can be stored or transmitted as one or more instructions or code on or via a non-transient computer-readable medium. Other examples and implementations fall within the scope and spirit of this disclosure and the appended claims. For example, due to the nature of software, the aforementioned functions can be implemented using software, hardware, hardwired, or any combination thereof executed by a specially programmed processor. Features implementing the functions can also be physically located in various locations, including being distributed such that portions of the function are implemented at different physical locations. Furthermore, the term “or” is intended to mean inclusive “or” rather than exclusive “or.” That is, unless otherwise specified or clearly apparent from the context, the phrase “X adopts A or B” is intended to mean any naturally possible permutation. That is, for example, the phrase “X adopts A or B” satisfies any of the following instances: X adopts A; X adopts B; or X adopts both A and B. Additionally, as used herein (including in the claims), the “or” used in a list of items followed by “at least one of” indicates a disjunctive list such that a list such as “at least one of A, B or C” represents A or B or C or AB or AC or BC or ABC (A and B and C).

[0145] Computer-readable media includes both computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Storage media can be any available medium accessible to a general-purpose or special-purpose computer. By way of example and not limitation, computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible to a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Similarly, any connection is also legitimately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then such coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of media. As used in this article, disk and disc include compact discs (CDs), laser discs, optical discs, digital multi-purpose discs (DVDs), floppy disks, and Blu-ray discs. Disks often magnetically reproduce data, while discs optically reproduce data using lasers. Combinations of these media are also included within the scope of computer-readable media.

[0146] The prior description of this disclosure is provided to enable those skilled in the art to make or use it. Various modifications to this disclosure will readily be apparent to those skilled in the art, and the common principles defined herein can be applied to other variations without departing from the spirit or scope of this disclosure. Furthermore, although elements of the described aspects and / or embodiments may be described or claimed in the singular, the plural is also contemplated unless explicitly stated to be limited to the singular. Additionally, all or part of any aspect and / or embodiment may be used in conjunction with all or part of any other aspect and / or embodiment unless otherwise stated. Thus, this disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for performing wireless communication at a user equipment (UE), comprising: Identify one or more groups containing multiple control resource sets (CORESETs), the multiple CORESETs including at least one HD CORESET for half-duplex HD mode at the UE, and at least one FD CORESET for full-duplex FD mode at the UE; Receive the at least one HD CORESET and the at least one FD CORESET from the network entity; A beam fault detection (BFD) measurement procedure is performed using a reference signal associated with at least one of the one or more groups containing multiple CORESETs. as well as Detect whether a cell-level failure event of a cellular cell, or a group-level failure event of one of the one or more groups containing multiple CORESETs, is triggered based on the BFD measurement procedure.

2. The method as described in claim 1, wherein, The one or more groups containing multiple CORESETs include a first group containing only one or more HD CORESETs and a second group containing only one or more FD CORESETs, the first group including the at least one HD CORESET and the second group including the at least one FD CORESET.

3. The method as described in claim 1, wherein, Each of the one or more groups containing multiple CORESETs includes a combination of one or more HD CORESETs and one or more FD CORESETs.

4. The method of claim 3, wherein, Each of one or more Transmitter-Receiver Points (TRPs) or TRP pairs includes different groups within the one or more groups containing multiple CORESETs.

5. The method of claim 3, wherein, Identifying the one or more groups containing multiple CORESETs further includes: receiving from the network entity a message indicating the one or more groups containing multiple CORESETs.

6. The method of claim 1, further comprising: A fault recovery procedure is executed in response to the detection of at least one of the cell-level fault event or the group-level fault event.

7. The method of claim 1, wherein, Performing the BFD measurement procedure using the reference signal further includes: determining the reference signal using the Transmission Configuration Indicator (TCI) state of the corresponding identifier ID of the at least one HD CORESET or the at least one FD CORESET, which is of quasi-common QCL type D.

8. The method of claim 7, wherein, The reference signal corresponds to the channel state information RS CSI-RS.

9. The method of claim 8, further comprising: Perform downlink BFD / Radio Resource Management (RRM) measurement procedures at one or more CSI-RS resource locations of the CSI-RS beam corresponding to the TCI state.

10. The method of claim 9, further comprising: The Layer 1 L1 Reference Signal Received Power (RSRP) for the BFD / RRM measurement procedure is calculated based on one or more downlink CSI-RS beams.

11. The method of claim 8, further comprising: The uplink beam corresponding to the detection and probe reference signal (SRS) beam, wherein the SRS beam is matched with the CSI-RS beam corresponding to the TCI state in the corresponding ID of the at least one FD CORESET; as well as Perform uplink BFD / Radio Resource Management (RRM) measurement procedures on the SRS beam to measure self-interference.

12. The method of claim 11, further comprising: The Layer 1 L1 signal-to-interference-plus-noise ratio (SINR) for the BFD / RRM measurement procedure is calculated based on one or more downlink CSI-RS beam pairs and uplink probe reference signal (SRS) beam pairs.

13. The method of claim 1, wherein, Detecting whether the cell-level fault event or the group-level fault event is triggered further includes: detecting, based on the triggering of the cell-level fault event, that a full-beam fault event has occurred in all groups of the one or more groups containing multiple CORESETs.

14. The method of claim 13, wherein, The one or more groups containing multiple cores include HD core group and FD core group, and The detection that the full-beam failure event has occurred in all groups of the one or more groups containing multiple CORESETs further includes: Detection of a first portion of beam fault events for the HD CORESET group based on the triggering of the group-level fault event; and The second beam fault event for the FD CORESET group is detected based on the triggering of the group-level fault event.

15. The method of claim 1, wherein, Detecting whether the cell-level fault event or the group-level fault event is triggered further includes: detecting, based on the triggering of the cell-level fault event, that a full-beam fault event has occurred in at least one of the one or more groups containing multiple CORESETs.

16. The method of claim 15, wherein, At least one of the groups containing multiple CORESETs corresponds to the HD CORESET group, and The detection of a full-beam failure event occurring in at least one of the one or more groups containing multiple CORESETs further includes: The partial beam failure event for the FD CORESET group in one or more groups containing multiple CORESETs is detected based on the triggering of the group-level failure event.

17. The method of claim 15, wherein, At least one of the groups containing multiple CORESETs corresponds to the FD CORESET group, and The detection of a full-beam failure event occurring in at least one of the one or more groups containing multiple CORESETs further includes: The partial beam failure event for an HD CORESET group containing multiple CORESETs is detected based on the triggering of the group-level failure event.

18. A method for wireless communication at a network entity, comprising: Determine one or more groups containing multiple control resource sets CORESET, the multiple CORESET including at least one HD CORESET for half-duplex HD mode at the user equipment UE, and at least one FD CORESET for full-duplex FD mode at the UE; Transmit the at least one HD CORESET and the at least one FD CORESET to the UE; as well as A beam fault recovery request is received from the UE based on at least one of a cell-level fault event triggered by a BFD measurement procedure at the UE, or a group-level fault event of one of the one or more groups containing multiple CORESETs.

19. The method of claim 18, wherein, The one or more groups containing multiple CORESETs include a first group containing only one or more HD CORESETs and a second group containing only one or more FD CORESETs, the first group including the at least one HD CORESET and the second group including the at least one FD CORESET.

20. The method of claim 18, wherein, Each of the one or more groups containing multiple CORESETs includes a combination of one or more HD CORESETs and one or more FD CORESETs.

21. The method of claim 20, wherein, Each of one or more Transmitter-Receiver Points (TRPs) or TRP pairs includes different groups within the one or more groups containing multiple CORESETs.

22. The method of claim 20, further comprising: The network entity transmits a message indicating one or more groups containing multiple CORESETs.

23. The method of claim 18, further comprising: Determine the Transmission Configuration Indicator (TCI) state of the corresponding identifier ID of the at least one HD CORESET or the at least one FD CORESET, which is of quasi-co-located QCL type D.

24. The method of claim 18, further comprising: The UE receives a beam fault detection (BFD) report based on the transmission of one or more of the at least one HDCORESET or the at least one FD CORESET, wherein the BFD report indicates that at least one of the cell-level fault events or group-level fault events is triggered based on a BFD measurement procedure performed by the UE.

25. The method of claim 24, wherein, The BFD report includes the Layer 1 L1 reference signal received power (RSRP) for the BFD / Radio Resource Management (RRM) measurement procedure performed by the UE based on one or more downlink channel state information reference signal (CSI-RS) beams.

26. The method of claim 24, wherein, The BFD report includes the Layer 1 L1 signal-to-interference-plus-noise ratio (SINR) for the BFD / Radio Resource Management (RRM) measurement procedure performed by the UE based on one or more downlink Channel State Information Reference Signal (CSI-RS) beams and uplink Probe Reference Signal (SRS) beams.

27. The method of claim 24, wherein, The BFD report indicates that a full beam failure event has occurred in all of the one or more groups containing multiple CORESETs, based on the triggering of the cellular-level failure event.

28. The method of claim 24, wherein, The BFD report indicates that a full beam failure event has occurred in at least one of the one or more groups containing multiple CORESETs, based on the triggering of the cell-level failure event.

29. An apparatus for wireless communication, comprising: transceiver; A memory configured to store instructions; as well as One or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to: Identify one or more groups containing multiple control resource sets CORESET, the multiple CORESET including at least one HD CORESET for half-duplex HD mode at the device, and at least one FD CORESET for full-duplex FD mode at the device; Receive the at least one HD CORESET and the at least one FD CORESET from the network entity; A beam fault detection (BFD) measurement procedure is performed using a reference signal associated with at least one of the one or more groups containing multiple CORESETs. as well as Detect whether a cell-level failure event of a cellular cell, or a group-level failure event of one of the one or more groups containing multiple CORESETs, is triggered based on the BFD measurement procedure.

30. An apparatus for wireless communication, comprising: transceiver; A memory configured to store instructions; as well as One or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to: Determine one or more groups containing multiple control resource sets CORESET, the multiple CORESET including at least one HD CORESET for half-duplex HD mode at the user equipment UE, and at least one FD CORESET for full-duplex FD mode at the UE; Transmit the at least one HD CORESET and the at least one FD CORESET to the UE; as well as A beam fault recovery request is received from the UE based on at least one of a cell-level fault event triggered by a BFD measurement procedure at the UE, or a group-level fault event of one of the one or more groups containing multiple CORESETs.

31. An apparatus for wireless communication, comprising: transceiver; A memory configured to store instructions; as well as One or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to perform the method as described in any one of claims 2-17.

32. An apparatus for wireless communication, comprising: transceiver; A memory configured to store instructions; as well as One or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to perform the method as described in any one of claims 19-28.

Citation Information

Patent Citations

  • Beam indication for semi-persistent and grant-free transmissions

    US20190306924A1

  • Beam recovery procedure for full duplex operation

    US20200214018A1