Delay reduction for beam failure recovery

Abstract

This application relates to devices and components, including apparatuses, systems, and methods for latency reduction for beam failure recovery (BFR) specific to a transmission-reception point (TRP) BFR.

Description

Background Technology

[0001] Beam fault detection and candidate beam detection technologies are described in existing 3GPP networks. Beam fault recovery technologies are also described in existing 3GPP networks. These technologies include detecting beam faults, discovering and selecting new beams, and restoring connectivity. Attached Figure Description

[0002] Figure 1 A network environment according to some implementation schemes is shown.

[0003] Figure 2 Examples of UE-specific beam fault recovery (BFR) mechanisms that can be supported in 5G networks according to some implementation schemes are shown.

[0004] Figure 3A An example is shown, illustrating a list of TCI states and candidate BFD RSs according to some implementation schemes.

[0005] Figure 3B An example of a timeline based on some implementation schemes is shown.

[0006] Figure 4A Examples of TCI state activations and candidate BFD RSs are shown according to some implementation schemes.

[0007] Figure 4B Examples of TCI state activations and candidate BFD RSs are shown according to some implementation schemes.

[0008] Figure 5 The operational flow / algorithm structure according to some implementation schemes is shown.

[0009] Figure 6 The operational flow / algorithm structure according to some implementation schemes is shown.

[0010] Figure 7 The operational flow / algorithm structure according to some implementation schemes is shown.

[0011] Figure 8 A beamforming component of a device according to some embodiments is shown.

[0012] Figure 9 User equipment according to some implementation schemes is shown.

[0013] Figure 10 A base station according to some implementation schemes is shown. Detailed Implementation

[0014] The following detailed description relates to the accompanying drawings. The same reference numerals may be used in different drawings to identify the same or similar elements. In the following description, specific details, such as particular structures, architectures, interfaces, technologies, etc., are set forth for illustrative and non-limiting purposes to provide a thorough understanding of various aspects of the various embodiments. However, it will be apparent to those skilled in the art that various aspects of the various embodiments may be practiced in other examples departing from these specific details. In some cases, descriptions of well-known devices, circuits, and methods have been omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of this document, the phrase "A or B" means (A), (B), or (A and B).

[0015] The following is a glossary of terms that may be used in this disclosure.

[0016] As used herein, the term "circuit" refers to, is part of, or includes the following: hardware components such as electronic circuits, logic circuits, processors (shared, dedicated, or grouped) or memories (shared, dedicated, or grouped), application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable system-on-a-chip (SoCs)), digital signal processors (DSPs), etc. In some embodiments, a circuit may execute one or more software or firmware programs to provide at least some of the said functions. The term "circuit" may also refer to a combination of one or more hardware elements and program code for performing the functions (or a combination of circuits used in an electrical or electronic system). In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit.

[0017] As used herein, the term "processor circuit" means, is part of, or includes the following: a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transmitting digital data. The term "processor circuit" may also refer to an application processor, baseband processor, central processing unit (CPU), graphics processing unit, single-core processor, dual-core processor, triple-core processor, quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions (such as program code, software modules, and / or functional procedures).

[0018] As used herein, the term "interface circuit" refers to, is part of, or includes a circuit that enables the exchange of information between two or more components or devices. The term "interface circuit" can refer to one or more hardware interfaces, such as buses, I / O interfaces, peripheral component interfaces, network interface cards, etc.

[0019] As used herein, the term "user equipment" or "UE" refers to equipment of a remote user that has radio communication capabilities and can describe network resources in a communication network. Furthermore, the term "user equipment" or "UE" can be considered synonymous and can be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Additionally, the term "user equipment" or "UE" can include any type of wireless / wired equipment or any computing device that includes a wireless communication interface.

[0020] As used herein, the term "computer system" means any type of interconnected electronic device, computer device, or component thereof. Additionally, the term "computer system" or "system" may refer to the various components of a computer that are communicatively coupled to each other. Furthermore, the term "computer system" or "system" may refer to multiple computer devices or multiple computing systems that are communicatively coupled to each other and configured to share computing resources or network resources.

[0021] As used herein, the term "resource" refers to physical or virtual devices, physical or virtual components within a computing environment, or physical or virtual components within a specific device, such as computer equipment, mechanical equipment, memory space, processor / CPU time, processor / CPU utilization, processor and accelerator load, hardware time or utilization, power supply, input / output operations, port or network sockets, channel / link allocation, throughput, memory utilization, storage, network, databases and applications, units of workload, etc. "Hardware resource" can refer to computing, storage, or networking resources provided by physical hardware components. "Virtualized resource" can refer to computing, storage, or networking resources provided by virtualization infrastructure to applications, devices, systems, etc. The terms "network resource" or "communication resource" can refer to resources that computer equipment / systems can access via a communication network. The term "system resource" can refer to any kind of shared entity providing services and can include computing or network resources. System resources can be considered as a coherent set of functions, network data objects, or services accessible through a server, wherein such system resources reside on a single host or multiple hosts and are clearly identifiable.

[0022] As used herein, the term "channel" refers to any tangible or intangible transmission medium used for transmitting data or data streams. The term "channel" may be synonymous or equivalent with "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," or any other similar term indicating a path or medium through which data is transmitted. Additionally, as used herein, the term "link" refers to a connection between two devices used for transmitting and receiving information.

[0023] As used in this article, the terms "instantiate" and "instantiate" refer to the creation of an instance. "Instance" also refers to the concrete occurrence of an object, which may occur, for example, during the execution of program code.

[0024] The term “connection” can mean that two or more elements at a common communication protocol layer have an established signaling relationship with each other through a communication channel, link, interface, or reference point. The term “obtain” is used to indicate any of its common meanings, such as calculation, derivation, (e.g., from another element or device) receiving, and / or (e.g., from a memory / storage device as described below) retrieval.

[0025] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as networked computers, network hardware, network equipment, network nodes, virtualized network functions, etc.

[0026] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual content of an information element, or the data element that contains that content. An information element may include one or more additional information elements.

[0027] This paper describes techniques for reducing latency in beam fault recovery (BFR) relative to the transmit-receive point (TRP). Figure 1 A network environment 100 according to some implementation schemes is illustrated. Network environment 100 may include a UE 104 and an access node (or “base station”) 108. Access node 108 may provide one or more radio serving cells 112 and 114, such as 3GPP New Radio (NR) cells, through which UE 104 may communicate with access node 108 (e.g., via an NR-Uu interface). In some aspects, access node 108 is a next-generation node B (gNB) providing one or more 3GPP NR cells.

[0028] Access node 108 can transmit information (e.g., data and control signaling) in the downlink direction by mapping logical channels onto transport channels and transport channels onto physical channels. Logical channels can transmit data between the Radio Link Control (RLC) layer and the Media Access Control (MAC) layer; transport channels can transmit data between the MAC and PHY layers; and physical channels can transmit information across the air interface. Physical channels may include the Physical Broadcast Channel (PBCH); the Physical Downlink Shared Channel (PDSCH); and the Physical Downlink Control Channel (PDCCH).

[0029] The PBCH can be used to broadcast system information that UE 102 / 104 / 106 can use for initial access to the serving cell. The PBCH can be transmitted together with the Physical Synchronization Signal (PSS) and the Secondary Synchronization Signal (SSS) in the Synchronization Signal (SS) / PBCH block. The SS / PBCH block (SSB) can be used by UE 104 during the cell search process and for beam selection.

[0030] PDSCH can be used to transmit end-user application data, signaling radio bearer (SRB) messages, system information messages (except for, for example, master information block (MIB)), and paging messages.

[0031] The access node (or "base station") 108 of the gNB can use the PDCCH to transmit downlink control information (DCI) to the UE 104. The DCI can provide uplink resource allocation on the Physical Uplink Shared Channel (PUSCH), downlink resource allocation on the PDSCH, and various other control information. The DCI can also be used to provide uplink power control commands, configure time slot formats, or indicate that preemption has occurred.

[0032] Access node 108 can also transmit various reference signals to UE 104. Reference signals (RS) are special signals that exist only at the PHY layer and are not used to deliver any specific information (e.g., data), but their purpose is to provide a reference point for transmit power. RS may include demodulation reference signals (DMRS) for PBCH, PDCCH, and PDSCH. UE 104 can compare the received version of the DMRS with a known sequence of transmitted DMRS to estimate the impact of the propagation channel. UE 104 can then apply the inversion of the propagation channel during the demodulation process corresponding to the physical channel transmission.

[0033] RS may also include a Channel State Information Reference Signal (CSI-RS). CSI-RS can be a multi-purpose downlink transmission used for CSI reporting, beam management, connection mode mobility, radio link failure detection, beam failure detection and recovery, and fine-tuning of time and frequency synchronization. For example, UE 104 can measure SSB and CSI-RS to determine the desired downlink beam pair for transmitting / receiving PDCCH and Physical Downlink Shared Channel (PDSCH) transmissions. UE 104 can use the Physical Uplink Control Channel (PUCCH) to transmit uplink control information (UCI) to access node 108, including, for example, Hybrid Automatic Repeat Request (HARQ) acknowledgments, scheduling requests, and periodic and semi-persistent channel state information (CSI) reports.

[0034] Access node 108 can configure transmit control indicator (TCI) status information for UE 104 to indicate quasi-co-location (QCL) relationships between antenna ports used for RS (e.g., SSB or CSI-RS) and downlink data or control signaling (e.g., PDSCH or PDCCH). Access node 108 can use a combination of radio resource control (RRC) signaling, MAC control element (CE) signaling, and / or downlink information (DCI) to inform UE 104 of these QCL relationships.

[0035] Initially, access node 108 can configure multiple TCI states for UE 104 via RRC signaling. In some implementations, up to 128 TCI states can be configured for PDSCH via, for example, a PDSCH-config information element (IE), and up to 64 TCI states can be configured for PDCCH via, for example, a PDCCH-config IE. Each TCI state may include a Physical Cell ID (PCI), a bandwidth portion ID, an indication of the associated SSB or CSI-RS, and an indication of the QCL type. 3GPP has specified four types of QCLs to indicate which specific channel characteristics are shared. In QCL type A, antenna ports share Doppler drift, Doppler spread, average delay, and delay spread. In QCL type B, antenna ports share Doppler drift, and Doppler spread is shared. In QCL type C, antenna ports share Doppler drift and average delay. In QCL type D, antenna ports share spatial receiver parameters.

[0036] After initial configuration, the TCI state can be set to inactive. Access node 108 can then issue an activation command, for example, via a MAC control element. This activation command can activate up to eight combinations of one or two TCI states, corresponding to eight code points in the TCI field of the DCI. One or more specific TCI states can then be dynamically selected and these TCI states can be signaled using the TCI field in the DCI to indicate which of the active TCI states are suitable for PDSCH resource allocation.

[0037] Access node 108 can use resource elements belonging to a control resource set (CORESET) to transmit PDCCH. Search space configuration can specify a particular CORESET to limit the search space; for example, a specific set of resource blocks and symbols that UE 104 attempts to decode the PDCCH. Access node 108 can configure up to three CORESETs for the active downlink bandwidth portion of the serving cell. A CORESET can be configured by a ControlResourceSet information element, which defines frequency domain resources to indicate the resource blocks allocated to the CORESET, defines a duration (which can be 1, 2, or 3 Orthogonal Frequency Division Multiplexing (OFDM) symbols) to indicate the number of symbols allocated to the CORESET, and defines QCL information to support successful PDCCH reception.

[0038] QCL information in the ControlResourceSet information element can be provided by listing the identities of TCI states. The TCI states identified in the ControlResourceSet information element can be a subset of the TCI states defined in the PDSCH-config within the active downlink bandwidth portion of the CORESET. If the ControlResourceSet information element provides only a single TCI state, UE 104 can assume a QCL relationship between the PDCCH and the RS specified by that TCI state. If multiple TCI states are listed, UE 104 can rely on the activation command as described above to identify the TCI state to apply.

[0039] UE 104 may include enhanced multiple-input multiple-output (eMIMO) capability that supports simultaneous communication from several (or even many) different serving cells via beams. Figure 1 An example of carrier aggregation (CA) is shown, in which UE 104 receives data from serving cell 112 via component carrier (CC) 122 and from serving cell 114 via component carrier (CC) 124, while simultaneously receiving data from access node 108.

[0040] CC 122 may be in a frequency band within frequency range 1 (FR1) or frequency range 2 (FR2). Similarly, CC 124 may be in a frequency band within FR1 or FR2. CC 112 and 124 may be in the same frequency band (intra-band, continuous or discontinuous) or in different frequency bands (inter-band) and within potentially different frequency ranges. For FR1 (e.g., below 7.225 GHz), the transmit antenna of UE 104 is typically implemented as an omnidirectional antenna. For FR2 (e.g., 24.250 GHz and above, also known as mmWave), the transmit antenna of UE 104 may be implemented as a panel with multiple antenna elements. For example, the multiple antenna elements of the panel may be driven as a phased array (e.g., to guide the beam in a desired direction).

[0041] Figure 2 An example of a UE-specific beam fault recovery (BFR) mechanism that can be supported in a 5G network according to some implementation schemes is shown. UE 104 can monitor the beam quality of the PDCCH to determine whether a beam fault has occurred. The UE can monitor beam quality based on an RS configured by gNB 108 for beam fault detection (BFD) (e.g., beam fault detection RS or "BFD RS"). Monitoring beam quality based on BFD-RS may include, for example, measuring the signal-to-interference-plus-noise ratio (SINR), block error rate (BLER), and / or the reference signal received power (RSRP) of the BFD RS. gNB 108 can also configure several other RSs for candidate beam detection.

[0042] After UE 104 declares a beam fault, UE 104 may report candidate beam information based on a Beam Fault Recovery Request (BFRQ). For example, the UE may send a MAC CE for BFR including the BFRQ to the gNB. The gNB 108 may send a response (e.g., a beam fault recovery response or "BFRR") to UE 104 after receiving the BFRQ. Following a predetermined delay period of K (e.g., K=28) symbols after UE 104 receives the gNB's response to the BFRQ, UE 104 may automatically apply the candidate beam to the PDCCH / PUCCH. UE 104 may also update the power control parameters of the PUCCH.

[0043] Currently, two schemes are available for configuring the Beam Failure Detection (BFD) RS. In the first scheme, the BFD RS is explicitly configured by RRC signaling. In the second scheme, the BFD RS is derived based on the RS configured in the TCI state of the CORESET. If both RSs are configured in the TCI state, the RS that provides the QCL-TypeD indication is used.

[0044] In version 17 of the 5G specification, support for TRP-specific BFRs is expected, allowing the gNB to configure the UE to perform BFRs individually for each TRP when the UE is configured with a multi-TRP mode. Support for TRP-specific BFRs is expected for both single-DCI-based and multi-DCI-based multi-TRP modes. For multi-DCI mode, the control resource set (CORESET) can be divided into two pools, and the CORESETPoolIndex can be configured in each CORESET. In this case, it can be assumed that CORESETs with the same CORESETPoolIndex come from the same TRP. However, for single-DCI mode, the UE does not have information about the TRP index of the CORESET.

[0045] If the first scheme described above (e.g., BFD RS explicitly configured by RRC signaling) is used for BFD RS configuration, then when the gNB changes the beam of the CORESET via MAC CE or DCI, the gNB can use RRC signaling to reconfigure the BFD RS, and the waiting time caused by the BFD RS reconfiguration may be too long. If the second scheme described above (e.g., deriving BFD RS based on the RS configured in the TCI state of the CORESET) is used for BFD RS configuration, then because the UE does not have information about the TRP of the CORESET, the UE may not be able to determine which TRP has failed. Furthermore, the UE may not be able to determine which CORESET with a newly identified beam can be applied to it after the beam failure is resolved.

[0046] The techniques described below can be implemented to reduce the waiting time for beam fault recovery. Techniques for reducing the waiting time for BFD RS updates can be applied, for example, to TRP-specific BFRs in single-DCI-based multi-TRP modes or generally BFR operations, while techniques for CORESET beam updates after beam fault recovery can be applied to TRP-specific BFRs in single-DCI-based multi-TRP modes.

[0047] In a first example of BFD RS configuration, gNB 108 may be implemented to provide UE 104 with K lists of candidate BFD RSs (e.g., via RRC signaling), where each of the K lists corresponds to a TRP. For example, for a UE in single TRP mode, K may be equal to one, and for a UE in multi-TRP mode, K may be equal to two. The UE may receive an RRC message containing the K lists. In one example, the UE receives an RRC message with an information element (IE) (e.g., a BeamFailureRecoveryConfig IE) containing the K lists. In another example, the UE receives an indication of the number of candidate BFD RS lists to be received (e.g., an indication of the value of K). In this case, the UE may receive an RRC message containing a first list of the K lists from a first TRP (e.g., an RRC message with an information element containing the first list), and the UE may receive an RRC message containing a second list of the K lists from a second TRP (e.g., an RRC message with an information element containing the second list).

[0048] In the first option, K lists can be provided by bandwidth portion (BWP). In the second option, K lists can be provided by CC. In the third option, K lists can be provided for a group of CCs (e.g., CCs sharing the same list are grouped together). CCs within a group can be predefined as CCs within a band or within a band packet. Alternatively, CCs within a group can be configured by RRC signaling.

[0049] For the third option as described above (e.g., providing K lists for a set of CCs), these lists can provide a common reference signal for BFD to the set of CCs (e.g., to all CCs in the group). Alternatively, the lists can provide only a common reference signal identifier for BFD to the set of CCs (e.g., the list provides only a reference signal ID to each CC). In this case, for each CC, the corresponding reference signal with the indicated identifier can be used for BFD.

[0050] As an alternative to providing the UE 104 with a list of K candidate BFD RSs as described above, the gNB 108 may be implemented to indicate the RS associated with each TCI state to be used for BFD. If no such RS is indicated, the RS configured in the TCI state is available for BFD. The RS indication may be based on RRC or MAC CE signaling. In one such example, the gNB 108 may optionally indicate the BFD RS in each TCI state configured by RRC signaling. In another such example, in the MAC CE for TCI activation, the gNB 108 may optionally indicate the BFD RS for each TCI state that is being activated.

[0051] UE 104 can be implemented to perform BFD using RSs from the list described above. It is expected that the RS selected for BFD is quasi-co-located (QCLed) or the same as the RS configured in the TCI state of CORESET. Therefore, the UE can use the QCL relationship between the two reference signals to identify the BFD RS, so that the UE can also identify potential BFD RSs when updating the TCI state.

[0052] It is expected that the RSs in the list are configured with different QCL characteristics. Alternatively, if N RSs in the list are quasi-co-addressable with RSs configured in the TCI state of CORESET, where N is greater than 1, it is expected that one of the following options will be applied to select among the quasi-co-addressable RSs used for BFD.

[0053] In the first option for selecting from N agreed-upon co-located RSs for BFD, priority rules can be defined to select one RS from the N RSs for BFD. Priority can be determined, for example, by periodicity, and / or density, and / or bandwidth, and / or RS index. In one such example, an RS with lower periodicity may be considered to have higher priority. Among RSs that otherwise have the same priority, the RS with the lowest index may be considered to have the highest priority.

[0054] In the second option, used for selecting among the N eligible co-located RSs for BFD, the gNB 108 can indicate which RS is used for BFD via MACCE or DCI signaling. In one such example, in beam indication signaling, the gNB can indicate the RS index of that RS among the N eligible co-located RSs to be used for BFD.

[0055] In the third option for selecting from the N compliant co-located RSs used for BFD, the UE can use any one or all of the N RSs used for BFD, and these N RSs can be counted as one RS used for BFD. For example, the UE can determine the average measurement result of the N RSs. This average measurement result can then be used for BFD.

[0056] Alternatively, the UE may use the RS configured for BFD in the TCI state, but the UE may use an index of a list of candidate BFD RSs containing the configured RS (or an index of a list of candidate BFD RSs containing RSs that are quasi-co-located with the configured RS) to determine the corresponding TRP index.

[0057] Figure 3AThe following is an example of a list of candidate BFD RSs that can be provided to the UE by the gNB (e.g., using RRC signaling), a list of TCI states that can be activated for CORESET, and an example of the association between RSs in these lists and RSs configured in TCI states (as may be indicated by quasi-co-addressing (QCL) features). In this example, list 1 of BFD RSs for TRP 1 indicates that RS1 is quasi-co-addressed with RSs configured in TCI state 1, RS2 is quasi-co-addressed with RSs configured in TCI state 2, and RS5 is quasi-co-addressed with RSs configured in TCI state 3; and list 2 of BFD RSs for TRP 2 indicates that RS9 is quasi-co-addressed with RSs configured in TCI state 5, RS10 is quasi-co-addressed with RSs configured in TCI state 6, and RS11 is quasi-co-addressed with RSs configured in TCI state 7.

[0058] Figure 3B An example timeline is shown, in which UE 104 applies beam indication signaling in response to gNB 108. Figure 3A The correlation is shown in the diagram. At the first time t1, the UE receives beam indication signaling from gNB 108 (e.g., via MAC CE and / or DCI signaling) to update the TCI states of CORESET 1, CORESET 2, and CORESET 3 to TCI state 1, TCI state 3, and TCI state 5, respectively. For example, gNB activates TCI state 1 for CORESET 1, TCI state 3 for CORESET 2, and TCI state 5 for CORESET 3. Based on the QCL relationship between the RS configured in each activated TCI state and the RS in the BFD RS list for TRP 1 and TRP 2 (e.g., as shown in... Figure 4A (Highlighted in the image), the UE determines that RS 1 and RS 5 will be used as the BFD RS for TRP 1, and RS 9 will be used as the BFD RS for TRP 2. After the action delay, the UE 104 updates the BFD RS for TRP 1 to RS 1 and RS 5, and updates the BFD RS for TRP 2 to RS 9.

[0059] At the second time t2, the UE receives beam indication signaling from gNB 108 (e.g., via MAC CE and / or DCI signaling) to update the TCI states of CORESET 1, CORESET 2, and CORESET 3 to TCI state 2, TCI state 6, and TCI state 7, respectively. For example, gNB activates TCI state 2 for CORESET 1, TCI state 6 for CORESET 2, and TCI state 7 for CORESET 3. This is based on the QCL relationship between the RS configured in each activated TCI state and the RS in the BFDRS list for TRP 1 and TRP 2 (e.g., as in...). Figure 4B (Highlighted in the image), the UE determines that RS 2 will be used as the BFD RS for TRP1, and RS 10 and RS 11 will be used as the BFD RS for TRP2. After the action delay, the UE 104 updates the BFD RS for TRP1 to RS 2 and updates the BFD RS for TRP2 to RS 10 and RS 11.

[0060] As described above (for example, refer to...) Figure 3B After the UE receives beam indication signaling to update the TCI state of the CORESET, the UE can update the BFD RS for the corresponding TRP. The action delay for BFD RS update after the UE receives beam indication signaling to update the TCI state of the CORESET can be configured according to any of several options. In a first option, the action delay for BFD RS update is the same as the beam indication action delay. For example, the UE can update the BFD RS for the TRP after a predetermined delay period (e.g., a predetermined number of milliseconds or time slots) following the last symbol of the UE's acknowledgment (ACK) transmission confirming receipt of the beam indication signaling.

[0061] In the second option for the action delay of BFD RS updates, the gNB can configure the action delay via higher-layer signaling (e.g., via RRC or MAC CE signaling), or the UE can report the action delay as a UE capability (e.g., via capability signaling). In the third option, the action delay for BFD RS updates can depend on the beam fault indication interval. In this case, the UE can apply the new BFD RS at the next beam fault indication interval after the UE changes its beam. In one example, the UE can be configured to evaluate beam fault detection approximately every two milliseconds, such that the delay between the UE changing its beam and updating the BFD RS can be expected to be within approximately two milliseconds.

[0062] The gNB can configure the number of BFD RSs for a TRP and / or the number of BFD RSs across all TRPs, exceeding the UE's capacity (which can be reported to the gNB by the UE via, for example, capacity signaling). If the number of BFD RSs configured for a TRP exceeds the UE's capacity for the maximum number of BFD RSs per TRP, the UE can make a downward selection among the configured BFD RSs according to a priority rule used for BFD RS selection. Priority can be determined by any one or all of a number of factors, which may include, for example, search space periodicity, CORESET index, BFD RS periodicity, BFD RS density, BFD RS bandwidth, or BFD RS index.

[0063] In one example, the UE can determine priority by selecting BFD RSs associated with the active TCI state received by the PDCCH in a CORESET that corresponds to the same list of candidate BFD RSs and is associated with a search space set (e.g., in order starting from the shortest monitoring periodicity). If two or more such CORESETs are associated with search space sets having the same monitoring periodicity, the UE can determine the order of CORESETs according to the highest CORESET index (e.g., the CORESET index p as described in Clause 10.1, v16.5.0 (2021-04) of 3GPP Technical Specification (TS) 38.213 (“5G; NR; Physical Layer Control Procedure”). If the gNB is configured with a number of BFD RSs across a TRP that exceeds the UE’s capacity for a maximum number of BFD RSs across a TRP, the UE can additionally determine priority by the TRP index (e.g., to prioritize BFDs for a TRP, such as the primary TRP).

[0064] The UE can be configured to maintain a beam fault instance counter BFI_COUNTER to count the number of times a beam fault is detected. For example, the UE can be configured to declare a beam fault only after the UE has detected multiple beam fault instances (e.g., to avoid the ping-pong effect). Since the BFD RS can be changed based on lower-layer signaling (e.g., DCI-based beam indication signaling) as described above, it is expected that the beam fault instance counter will be reset in the event of a change in the BFD RS. For example, it is expected that 3GPP TS 38.321 (section 5.17 of “5G; NR; Media Access Control (MAC) Protocol Specification”, v16.4.0 (2021-04)) will be updated as indicated below:

[0065] 1> If any of the reference signals in beamFailureDetectionTimer, beamFailureInstanceMaxCount, or the reference signal used for beam failure detection is reconfigured by the upper layer or Updated from lower level This lower layer is associated with the serving cell:

[0066] 2> Set BFI_COUNTER to 0.

[0067] Following a predetermined number of symbols (e.g., 28 symbols) after the UE receives a response (e.g., BFRR) to a BFRQ from the gNB, the UE can reset the beams used for the CORESET sharing the same BFD RS list as reported in the BFRQ, based on the newly identified beams reported by the UE in the BFRQ. The UE can determine the CORESET sharing the same BFD RS list based on the CORESET beam indication in the time slot with the latest BFRQ (e.g., as included in the MAC CE for BFR). It is expected that a PUCCH scheduled by the corresponding CORESET will be transmitted based on the newly identified beams. It is expected that one or more default power control parameters (e.g., P0, closed-loop index) will be applied to the corresponding TRP. It is expected that the path loss reference signal will be based on the new beam index as reported by the UE in the MAC CE for BFR.

[0068] Figure 5 An operational flow / algorithm structure 500 according to some implementation schemes is shown. The operational flow / algorithm structure 500 may be executed or implemented by a UE such as, for example, UE 104 or UE 900; or by a component of the UE such as a baseband processor 904A.

[0069] The operation flow / algorithm structure 500 may include receiving a first list of candidate BFD RSs for a first TRP at 504. The first list may be for a first BWP, a first CC, a first group of CCs, etc. Structure 500 may also include an indication of the number of candidate BFD RSs to be received in the list.

[0070] The operation flow / algorithm structure 500 may include receiving a second list of candidate BFD RSs for the second TRP at 508. The second list may be for a first BWP, a first CC, a first group of CCs, etc. Structure 500 may also include receiving a third list of candidate BFD RSs for a second BWP, a second CC, a second group of CCs, etc. Additionally or alternatively, structure 500 may include receiving RRC information elements that include both the first and second lists.

[0071] The operation flow / algorithm structure 500 may include receiving a message at 512 activating the TCI state of CORESET. Structure 500 may include resetting the beam fault detection counter based on receiving this message.

[0072] The operation flow / algorithm structure 500 may include, at 516, selecting a BFD RS from a first list or a second list based on RSs configured in the TCI state. This selection may be based on the BFD RS being quasi-co-located (QCLed) with RSs configured in the TCI state. The selection of the BFD RS from multiple BFD RSs may be based on Medium Access Control (MAC) Control Element (CE) or Downlink Control Information (DCI) signaling. Structure 500 may include identifying multiple BFD RSs quasi-co-located with RSs configured in the TCI state; and the selection may be based on the periodicity or density of the BFD RSs. For example, the selection may be based on the minimum periodicity of the BFD RSs among multiple BFD RSs. Structure 500 may include determining that a BFD RS has equal priority with a first BFD RS among multiple BFD RSs, and the selection may further be based on the index of the BFD RS. The BFD RS may be the first BFD RS, and structure 500 may include selecting a second BFD RS from multiple BFD RSs, and monitoring beam quality based on the first BFD RS and the second BFD RS.

[0073] The operational procedure / algorithm structure 500 may also include, at 520, monitoring beam quality based on BFD RS. Structure 500 may include generating a BFRQ (e.g., in MAC CE) to indicate BFD RS; receiving a beam fault request response (BFRR); and, following a predetermined delay period after receiving the BFRR, resetting the beam for CORESET based on the beam identified in the BFRQ. Structure 500 may also include transmitting physical uplink control channel transmissions scheduled by CORESET on the beam identified in the BFRQ.

[0074] Figure 6 An operational flow / algorithm structure 600 according to some implementation schemes is shown. The operational flow / algorithm structure 600 may be executed or implemented by a UE such as, for example, UE 104 or UE 900; or by a component of the UE such as a baseband processor 904A.

[0075] The operation flow / algorithm structure 600 may include, at 604, obtaining a first list of candidate BFD RSs for the first TRP. The first list may be for the first BWP, the first CC, the first group of CCs, etc.

[0076] The operation flow / algorithm structure 600 may include obtaining a second list of candidate BFD RSs for the second TRP at 608. The second list may be for the first BWP, the first CC, the first group of CCs, etc. Structure 600 may also include receiving a third list of candidate BFD RSs for the second BWP, the second CC, the second group of CCs, etc.

[0077] The operation flow / algorithm structure 600 may include obtaining a message at 612 indicating the activation of the TCI state for the TCI state, wherein the message indicates the BFD RS for the TCI state. Structure 600 may include resetting the beam fault detection counter based on the message.

[0078] The operation flow / algorithm structure 600 may include determining the TRP index at 616 based on the correspondence between the BFD RS and a first BFD RS in a first list or a second list. The correspondence may be that the BFD RS and the first BFD RS are the same. Alternatively, the correspondence may be that the BFD RS and the first BFD RS are quasi-co-located.

[0079] Operation flow / algorithm structure 600 may include generating a BFRQ (e.g., in MACCE) at 620 to indicate the TRP index. Structure 600 may include generating an acknowledgment (ACK) for a received message; and applying BFD RS after a predetermined delay period following the transmission of the last symbol of the ACK.

[0080] Structure 600 may include downward selection from candidate BFD RSs in a first list (and / or candidate BFD RSs in a second list) according to a priority rule, wherein the priority rule is based on search space periodicity, CORESET index, BFD RS periodicity, BFD RS density, BFD RS bandwidth, or BFD RS index. The priority rule may be based on the monitoring periodicity of the search space set associated with the CORESET corresponding to the candidate BFD RS in the first list. Additionally or alternatively, the priority rule may be based on the TRP index.

[0081] Figure 7 An operational flow / algorithm structure 700 according to some embodiments is shown. The operational flow / algorithm structure 700 may be executed or implemented by a base station such as base station 108 or 1000; or by a component of the base station such as baseband processor 1004A.

[0082] The operation flow / algorithm structure 700 may include sending a first list of candidate BFD RSs for the first TRP at 704. The first list may be for the first BWP, the first CC, the first group of CCs, etc.

[0083] The operation flow / algorithm structure 700 may include sending a second list of candidate BFD RSs for the second TRP at 708. The second list may be for the first BWP, the first CC, the first group of CCs, etc. Structure 700 may also include sending a third list of candidate BFD RSs for the second BWP, the second CC, the second group of CCs, etc.

[0084] The operation flow / algorithm structure 700 may include sending a message at 712 to activate the TCI state of CORESET. This message may indicate the first BFD RS.

[0085] The operation flow / algorithm structure 700 may include receiving (e.g., in MAC CE) at 716 a BFRQ indicating a BFD RS within a first list or a second list. The BFD RS may be quasi-co-addressable with an RS configured in the TCI state. The BFRQ may indicate a TRP index identifying the first TRP or the second TRP.

[0086] Figure 8 A receiving component 800 of a device according to some embodiments is shown. The device may be UE 104 or serving cell 112 or 114. The receiving component 800 may include a first antenna panel, namely panel 1 804, and a second antenna panel, namely panel 2 808. Each antenna panel may include multiple antenna elements.

[0087] Antenna panels can be coupled to corresponding analog beamforming (BF) components. For example, panel 1 804 can be coupled to analog BF component 812, and panel 2 808 can be coupled to analog BF component 816.

[0088] The analog baseband (BF) component can be coupled to one or more radio frequency (RF) chains. For example, analog BF component 812 can be coupled to one or more RF chains 820, and analog BF component 816 can be coupled to one or more RF chains 824. The RF chains can amplify the received analog RF signal, down-convert the RF signal to baseband, and convert the analog baseband signal into a digital baseband signal that can be provided to the digital BF component 828. The digital BF component 828 can provide a baseband (BB) signal for further baseband (BB) processing.

[0089] In various implementations, control circuitry residing in the baseband processor can provide BF weights to the analog / digital BF components to provide a received beam at the corresponding antenna panel. These BF weights can be determined by the control circuitry based on a received reference signal and corresponding QCL / TCI information as described herein. In some implementations, the BF weights can be phase shift values ​​provided to the phase shifter of the analog BF component 812 or complex weights provided to the digital BF component 828. In some implementations, the BF components and antenna panels can operate together to provide a dynamic phased array capable of guiding the beam in a desired direction.

[0090] In various implementations, beamforming can include analog beamforming, purely digital beamforming, or a hybrid analog-digital beamforming. Digital beamforming can utilize separate RF chains, each corresponding to an antenna element.

[0091] Although beamforming component 800 describes receiving beamforming, other embodiments may include beamforming components that perform transmitting beamforming in a similar manner.

[0092] Figure 9 A UE 900 according to some implementation schemes is shown. The UE 900 may be similar to... Figure 1 The UE104 is essentially interchangeable with it.

[0093] UE 900 can be any mobile or non-mobile computing device, such as, for example, mobile phones, computers, tablets, industrial wireless sensors (e.g., microphones, carbon dioxide sensors, pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, laser scanners, fluid level sensors, stock sensors, voltmeters / ammeters, actuators, etc.), video surveillance / monitoring devices (e.g., cameras, camcorders, etc.), wearable devices (e.g., smartwatches), and loosely coupled IoT devices.

[0094] UE 900 may include a processor 904, RF interface circuitry 908, memory / storage device 912, user interface 916, sensor 920, drive circuitry 922, power management integrated circuit (PMIC) 924, antenna structure 926, and battery 928. Components of UE 900 may be implemented as integrated circuits (ICs), portions of integrated circuits, discrete electronic devices or other modules, logic components, hardware, software, firmware, or combinations thereof. Figure 9 The block diagram is intended to show a high-level view of some of the components of the UE 900. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other specific implementations.

[0095] The components of UE 900 can be coupled to various other components via one or more interconnects 932, which can represent any type of interface, input / output, bus (local, system, or extension), transmission line, trace, optical connector, etc., allowing various circuit components (on common or different chips or chipsets) to interact with each other.

[0096] Processor 904 may include processor circuitry such as baseband processor circuitry (BB) 904A, central processing unit circuitry (CPU) 904B, and graphics processing unit circuitry (GPU) 904C. Processor 904 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions (such as program code, software modules, or functional processes from memory / storage device 912) to cause UE 900 to perform the operations described herein.

[0097] In some implementations, the baseband processor circuitry 904A can access the communication protocol stack 936 in the memory / storage device 912 to communicate over a 3GPP-compliant network. Generally, the baseband processor circuitry 904A can access the communication protocol stack to perform the following operations: user plane functions at the PHY, MAC, RLC, PDCP, SDAP, and PDU layers; and control plane functions at the PHY, MAC, RLC, PDCP, RRC, and non-access layers. In some implementations, PHY layer operations may additionally / optionally be performed by components of the RF interface circuitry 908.

[0098] The baseband processor circuit 904A can generate or process baseband signals or waveforms carrying information in a 3GPP-compliant network. In some implementations, the waveforms used for NR may be based on cyclic prefix OFDM (“CP-OFDM”) in the uplink or downlink, and Discrete Fourier Transform Extended OFDM (“DFT-S-OFDM”) in the uplink.

[0099] Memory / storage device 912 may include one or more non-transitory computer-readable media, including instructions (e.g., communication protocol stack 936) that can be executed by one or more processors in processor 904 to cause UE 900 to perform the various operations described herein. Memory / storage device 912 includes any type of volatile or non-volatile memory that can be distributed throughout UE 900. In some embodiments, some memory / storage devices 912 may be located on processor 904 itself (e.g., L1 cache and L2 cache), while other memory / storage devices 912 may be located external to processor 904 but accessible via a memory interface. Memory / storage device 912 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0100] The RF interface circuitry 908 may include transceiver circuitry and a radio frequency front-end module (RFEM), which allows the UE 900 to communicate with other devices via a radio access network. The RF interface circuitry 908 may include various components arranged in the transmit or receive path. These components may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, control circuitry, etc.

[0101] In the receiving path, the RFEM can receive the radiated signal from the air interface via antenna structure 926 and continue to filter and amplify the signal (using a low-noise amplifier). This signal can be provided to the receiver of the transceiver, which downconverts the RF signal into a baseband signal that is provided to the baseband processor of processor 904.

[0102] In the transmission path, the transceiver's transmitter upconverts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM amplifies the RF signal using a power amplifier before it is radiated across the air interface via antenna 926.

[0103] In various implementations, the RF interface circuit 908 can be configured to transmit / receive signals in a manner compatible with NR access technology.

[0104] Antenna 926 may include antenna elements to convert electrical signals into radio waves to travel through the air and to convert received radio waves back into electrical signals. These antenna elements may be arranged in one or more antenna panels. Antenna 926 may have omnidirectional, directional, or combinations thereof antenna panels to enable beamforming and multiple-input / multiple-output communication. Antenna 926 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, phased array antennas, etc. Antenna 926 may have one or more panels designed for a specific frequency band included in FR1 or FR2.

[0105] User interface circuitry 916 includes various input / output (I / O) devices designed to enable users to interact with UE 900. User interface circuitry 916 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting input, particularly including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, a headset, etc. Output device circuitry includes any physical or virtual means for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). Output device circuitry may include any number or combination of audio or visual displays, particularly including one or more simple visual outputs / indicators (e.g., binary status indicators such as light-emitting diodes "LEDs") and multi-character visual outputs, or more complex outputs such as display devices or touchscreens (e.g., liquid crystal displays "LCDs", LED displays, quantum dot displays, projectors, etc.), wherein the output of characters, graphics, multimedia objects, etc., is generated or produced by the operation of UE 900.

[0106] Sensor 920 may include devices, modules, or subsystems designed to detect events or changes in their environment and transmit information about the detected events (sensor data) to other devices, modules, subsystems, etc. Examples of such sensors include, in particular: inertial measurement units including accelerometers, gyroscopes, or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) including triaxial accelerometers, triaxial gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless aperture sensors); light detection and ranging sensors; proximity sensors (e.g., infrared radiation detectors, etc.); depth sensors; ambient light sensors; ultrasonic transceivers; microphones or other similar audio capture devices; etc.

[0107] The driving circuitry 922 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the UE 900. The driving circuitry 922 may include various drivers that allow other components to interact with or control various input / output (I / O) devices that may exist within or be connected to the UE 900. For example, the driving circuitry 922 may include: a display driver for controlling and allowing access to a display device; a touchscreen driver for controlling and allowing access to a touchscreen interface; a sensor driver for acquiring sensor readings from sensor circuitry 920 and controlling and allowing access to sensor circuitry 920; a driver for acquiring actuator positions of electromechanical components or controlling and allowing access to electromechanical components; a camera driver for controlling and allowing access to an embedded image capture device; and an audio driver for controlling and allowing access to one or more audio devices.

[0108] The PMIC 924 manages the power supplied to various components of the UE 900. Specifically, relative to the processor 904, the PMIC 924 controls power selection, voltage scaling, battery charging, or DC-DC conversion.

[0109] In some implementations, the PMIC 924 may control or otherwise become part of various power-saving mechanisms of the UE 900, including DRX, as discussed herein.

[0110] Battery 928 can power UE 900, but in some examples, UE 900 may be mounted in a fixed location and may have a power source coupled to the mains. Battery 928 may be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in vehicle-based applications, battery 928 may be a typical lead-acid automotive battery.

[0111] Figure 10 An access node 1000 (e.g., a base station or gNB) according to some implementations is shown. Access node 1000 may be similar to access node 108 and is substantially interchangeable with it.

[0112] Access node 1000 may include processor 1004, RF interface circuit 1008, core network (CN) interface circuit 1012, memory / storage device circuit 1016 and antenna structure 1026.

[0113] The components of access node 1000 can be coupled to various other components via one or more interconnectors 1028.

[0114] The processor 1004, RF interface circuit 1008, memory / storage device circuit 1016 (including communication protocol stack 1010), antenna structure 1026, and interconnect 1028 can be similar to those described above. Figure 9 Similar named elements are shown and described.

[0115] The CN interface circuitry 1012 can provide connectivity to a core network (e.g., a 5GC using a 5G core network (5GC) compatible network interface protocol (such as Carrier Ethernet) or some other suitable protocol). Network connectivity can be provided to / from access node 1000 via fiber optic or wireless backhaul. The CN interface circuitry 1012 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN controller circuitry 1012 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0116] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0117] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods as described in the Examples section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples below. Similarly, circuitry associated with the UE, base station, network element, etc., described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the Examples section below.

[0118] Example

[0119] Further exemplary implementations are provided in the following sections.

[0120] Example 1 includes a method for operating a UE, the method comprising: receiving a first list of candidate BFD RSs for a first TRP; receiving a second list of candidate BFD RSs for a second TRP; receiving a message indicating a CORESET TCI state; selecting a BFD RS within the first list or the second list based on an RS configured in the TCI state; and generating a BFRQ to indicate the BFD RS. Example 1 may include receiving an indication of the number of candidate BFD RSs to be received. Additionally or alternatively, Example 1 may include receiving an RRC information element (IE) including the first list and the second list.

[0121] Example 2 includes the method according to Example 1 or some other embodiments herein, wherein the first list is for a first BWP, and the processing circuitry is further configured to receive a third list of candidate BFD RSs for a second BWP.

[0122] Example 3 includes the method according to Example 1 or some other embodiments herein, wherein the first list is for a first CC, and the processing circuitry is further configured to receive a third list of candidate BFD RSs for a second CC.

[0123] Example 4 includes the method according to Example 1 or some other embodiments herein, wherein the first list is for a first group of CCs, and the processing circuitry is further configured to receive a third list of candidate BFD RSs for a second group of CCs.

[0124] Example 5 includes the method according to Example 1 or some other embodiments herein, the method further comprising: selecting the BFD RS based on the BFD RS being quasi-co-located with the RS configured in the TCI state.

[0125] Example 6 includes the method according to Example 5 or some other embodiments herein, the method further comprising: identifying and configuring a plurality of BFD RSs quasi-co-located in the TCI state; and selecting the BFD RS from the plurality of BFD RSs based on the periodicity of the BFD RS or the density of the BFD RS.

[0126] Example 7 includes the method according to Example 6 or some other embodiments herein, the method further comprising: selecting the BFD RS based on the minimum periodicity of the plurality of BFD RSs; or determining that the BFD RS has equal priority to a first BFD RS among the plurality of BFD RSs, and further selecting the BFD RS based on the index of the BFD RS.

[0127] Example 8 includes the method according to Example 5 or some other embodiments herein, the method further comprising: selecting the BFD RS from the plurality of BFD RSs based on MAC CE or DCI signaling.

[0128] Example 9 includes the method according to Example 5 or some other embodiments herein, wherein the BFD RS is a first BFD RS, and the method further includes: selecting a second BFD RS from the plurality of BFD RSs; and monitoring the beam quality on the first BFD RS and the beam quality on the second BFD RS.

[0129] Example 10 includes the method according to Example 1 or some other embodiments herein, wherein the method further includes: resetting the beam fault detection counter based on receiving the message.

[0130] Example 11 includes the method according to Example 1 or some other embodiments herein, wherein the method further includes: generating a BFRQ for indicating the BFD RS; receiving a BFRR; and resetting the beam for the CORESET based on the beam identified in the BFRQ after a predetermined delay period following the receipt of the BFRR.

[0131] Example 12 includes the method according to Example 11 or some other embodiments herein, wherein the method further includes: transmitting a physical uplink control channel scheduled by the CORESET on the beam identified in the BFRQ.

[0132] Example 13 includes an apparatus (e.g., a UE) comprising: processing circuitry configured to: obtain a first list of candidate BFD RSs for a first TRP; obtain a second list of candidate BFD RSs for a second TRP; obtain a message indicating a TCI state activating a CORESET, wherein the message indicates a BFD RS for the TCI state; determine a TRP index based on a correspondence between the BFD RS and a first BFD RS in the first list or the second list; and a memory coupled to the processing circuitry for storing the first list and the second list. The processing circuitry may also be configured to generate a BFRQ indicating the TRP index.

[0133] Example 14 includes user equipment according to Example 13 or some other embodiments herein, wherein the correspondence is that the BFD RS is the same as the first BFD RS, or the correspondence is that the BFD RS and the first BFD RS are quasi-co-located.

[0134] Example 15 includes the user equipment described according to Example 13 or some other embodiments herein, wherein the processing circuitry is further configured to: generate an ACK for receiving the message; and apply the BFD RS after a predetermined delay period following the transmission of the last symbol of the ACK.

[0135] Example 16 includes user equipment according to Example 13 or some other embodiments herein, wherein the processing circuitry is further configured to: reset the beam fault detection counter based on the message.

[0136] Example 17 includes the user equipment described according to Example 13 or some other embodiments herein, wherein the processing circuitry is further configured to: select downwards from the candidate BFD RS in the first list according to a priority rule, wherein the priority rule is based on search space periodicity, CORESET index, BFD RS periodicity, BFD RS density, BFD RS bandwidth, or BFD RS index.

[0137] Example 18 includes user equipment according to Example 17 or some other embodiments herein, wherein the priority rule is based on the monitoring periodicity of a search space set associated with a CORESET corresponding to candidate BFD RS in the first list.

[0138] Example 19 includes user equipment according to Example 17 or some other embodiments herein, wherein the priority rule is based on the TRP index.

[0139] Example 20 includes one or more computer-readable media, the one or more computer-readable media including instructions that, when executed by one or more processors, cause a base station to: transmit a first list of BFD RSs for a first TRP; transmit a second list of candidate BFD RSs for a second TRP; transmit a message activating the TCI state of CORESET; and receive a BFRQ indicating a BFD RS in the first list or the second list.

[0140] Example 21 includes one or more computer-readable media according to Example 20 or some other embodiments herein, wherein: the first list is for a first BWP, and the instructions, when executed by the one or more processors, further cause the base station to transmit a third list of candidate BFD RSs for a second BWP.

[0141] Example 22 includes one or more computer-readable media according to Example 20 or some other embodiments herein, wherein: the first list is for a first CC, and the instructions, when executed by the one or more processors, further cause the base station to transmit a third list of candidate BFD RSs for a second CC.

[0142] Example 23 includes one or more computer-readable media according to Example 20 or some other embodiments herein, wherein the BFD RS is quasi-co-addressed with an RS configured in the TCI state.

[0143] Example 24 includes one or more computer-readable media according to Example 20 or some other embodiments herein, wherein the BFRQ indicates a TRP index that identifies the first TRP or the second TRP.

[0144] Example 25 includes one or more computer-readable media according to Example 20 or some other embodiments herein, wherein the message indicates a first BFD RS.

[0145] Example 26 may include an apparatus comprising means for performing one or more elements of the method or process described or associated with any of Examples 1 to 25 or any other method or process described herein.

[0146] Example 27 may include one or more non-transitory computer-readable media, the one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of the method or any other method or process described herein according to any one of Examples 1 to 25 or related thereto.

[0147] Example 28 may include an apparatus comprising one or more elements of a logic component, module, or circuit for performing a method or process described or associated with any of Examples 1 to 25 or any other method or process described herein.

[0148] Example 29 may include a method, technique, or process, or a part or component thereof, described or associated with any of Examples 1 to 25.

[0149] Example 30 may include an apparatus comprising one or more processors and one or more computer-readable media, the one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process or part thereof according to or related to any one of Examples 1 to 25.

[0150] Example 31 may include a signal, or a portion thereof, described or associated with any of Examples 1 to 25.

[0151] Example 32 may include datagrams, information, elements, packets, frames, segments, PDUs or messages, or portions or components thereof, as described or otherwise in this disclosure, according to any one of Examples 1 to 25.

[0152] Example 33 may include a signal encoded with data, or a portion or component thereof, as described or associated with any of Examples 1 to 25, or otherwise described in this disclosure.

[0153] Example 34 may include a signal, or a portion or component thereof, encoded as a datagram, IE, packet, frame, segment, PDU, or message, as described or associated with any of Examples 1 to 25, or otherwise described in this disclosure.

[0154] Example 35 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process or part thereof as described or associated with any of Examples 1 to 25.

[0155] Example 36 may include a computer program comprising instructions, wherein execution of the program by a processing element will cause the processing element to perform a method, technique, or process or part thereof as described or associated with any one of Examples 1 to 25.

[0156] Example 37 may include signals in a wireless network as shown and described herein.

[0157] Example 38 may include methods for communicating in a wireless network as shown and described herein.

[0158] Example 39 may include a system for providing wireless communication as shown and described herein.

[0159] Example 40 may include a device for providing wireless communication as shown and described herein.

[0160] Unless otherwise expressly stated, any of the examples above may be combined with any other example (or combination of examples). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. In light of the teachings above, modifications and variations are possible, or modifications and variations may be derived from practice of various embodiments.

[0161] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the disclosure is fully understood. This disclosure is intended to render the following claims as encompassing all such variations and modifications.

Claims

1. A method for operating user equipment (UE), the method comprising: Receive configuration information from the network, the configuration information including a first list of beam fault detection (BFD) reference signals (RS) for the bandwidth portion (BWP) of the serving cell and a second list of BFD RS for the BWP of the serving cell; The network receives a Media Access Control (MAC) control element (CE), the MAC CE being used to indicate a BFD RS within the first list or the second list that will be used for BFD; and Use the indicated BFD RS to monitor beam quality.

2. The method of claim 1, wherein the BWP is a first BWP, and wherein: The first list is for the first BWP, and The method further includes receiving a third list of BFD RS for the second BWP.

3. The method according to claim 1, wherein: The first list is for the first component carrier (CC), and The method further includes receiving a third list of BFD RS for the second CC.

4. The method according to claim 1, wherein: The first list is for the first component quantity carrier (CC), and The method further includes receiving a third list of BFD RS for the second group of CCs.

5. The method according to any one of claims 1 to 4, wherein the BFD RS is a first BFD RS, and the method further comprises: The second BFD RS is selected based on the BFD RS and the RS quasi-co-addressed (QCLed) configured in the transmit configuration indicator (TCI) state.

6. The method according to claim 5, further comprising: Identify and configure multiple BFD RSs that are quasi-co-located with the RSs in the TCI state; as well as The BFDRS is selected from the plurality of BFDRS based on the periodicity or density of the BFDRS.

7. The method according to claim 6, further comprising: The fourth BFD RS is selected based on the minimum periodicity of the plurality of BFD RSs; or The fourth BFD RS is determined to have equal priority with the fifth BFD RS among the plurality of BFD RSs, and the fourth BFD RS is further selected based on the index of the fourth BFD RS.

8. The method of claim 1, wherein the MAC CE includes an index of the BFD RS to be used for BFD within the first list or the second list.

9. The method according to any one of claims 1 to 4, wherein the method further comprises: Generate a beam fault recovery request (BFRQ) to instruct the BFD RS. Receive beam fault request response (BFRR); as well as Following a predetermined delay period after receiving the BFRR, the beam used for the control resource set (CORESET) is reset based on the beam identified in the BFRQ.

10. The method of claim 9, wherein the method further comprises: Transmit on the beam identified in the BFRQ via the physical uplink control channel scheduled by the CORESET.

11. The method according to any one of claims 1 to 4, wherein the method further comprises: Receive a Radio Resource Control (RRC) information element that includes the configuration information.

12. An apparatus comprising: Processing circuit, the processing circuit being used for: Configuration information is obtained from the network, which is used to configure: a first list of beam fault detection (BFD) reference signals (RS) for the bandwidth portion (BWP) of the serving cell and a second list of BFD RS for the BWP of the serving cell; Obtain a Media Access Control (MAC) control element (CE) received from the network, wherein the MAC CE indicates a BFD RS that will be used for BFD within the first list or the second list; Determine whether a beam fault has been detected based on the indicated BFD RS; as well as A beam fault recovery request (BFRQ) is generated when a beam fault is detected. and A memory coupled to the processing circuitry, the memory being used to store the configuration information.

13. The apparatus of claim 12, wherein the processing circuitry is further configured to: Generate an acknowledgment (ACK) of receipt of the MAC CE; and The BFD RS is applied after a predetermined delay period following the transmission of the last symbol of the ACK.

14. The apparatus according to any one of claims 12 to 13, wherein the processing circuitry is further configured to: reset the beam fault detection counter based on the MAC CE.

15. The apparatus of any one of claims 12 to 13, wherein the processing circuitry is further configured to: select downwards from the BFD RS in the first list according to a priority rule, wherein the priority rule is based on search space periodicity, CORESET index, BFD RS periodicity, BFD RS density, BFD RS bandwidth, or BFD RS index.

16. The apparatus of claim 15, wherein the priority rule is based on the monitoring periodicity of a search space set associated with a CORESET corresponding to a candidate BFD RS in the first list.

17. One or more computer-readable media, the one or more computer-readable media comprising instructions that, when executed by one or more processors, cause a base station to: Send configuration information to the user equipment (UE), the configuration information including a first list of beam fault detection (BFD) reference signals (RS) for the bandwidth portion (BWP) of the serving cell and a second list of BFD RS for the BWP of the serving cell; Determine the BFD RS that will be used for BFD in the first list or the second list; Send a Media Access Control (MAC) control element (CE) to indicate a BFD RS determined from the first list or the second list; as well as Receive beam fault recovery request (BFRQ), which is based on the indicated BFD RS indicating BFD information.

18. The one or more computer-readable media of claim 17, wherein the BWP is a first BWP, and wherein: The first list is for the first BWP, and When executed by the one or more processors, the instructions further cause the base station to send a third list of BFD RS for the second BWP.

19. One or more computer-readable media according to claim 17 or 18, wherein: The first list is for the first component carrier (CC), and When executed by the one or more processors, the instructions further cause the base station to send a third list of BFD RS for the second CC.

20. One or more computer-readable media according to claim 17 or 18, wherein the BFD RS is quasi-co-addressed with an RS configured in a transmit configuration indicator (TCI) state.

21. One or more computer-readable media according to claim 17 or 18, wherein the BFR MAC CE indicates a serving cell index.

22. One or more computer-readable media according to claim 17 or 18, wherein the MAC CE indicates a first BFD RS.

Images