Power control parameter reset associated with beam failure recovery

By sending a beam fault recovery request signal from the user equipment and receiving a response from the network entity, the beam fault is reset using power control parameters, thus solving the communication interruption problem caused by beam faults in the wireless communication system and achieving reliable communication recovery.

CN119054407APending Publication Date: 2024-11-29QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280094922.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-04-22
Publication Date
2024-11-29

AI Technical Summary

Technical Problem

In wireless communication systems, directional beam failures cause communication interruptions, and existing technologies struggle to effectively recover from beam failures, impacting communication quality and reliability.

Method used

User equipment (UE) achieves communication recovery by sending a beam fault recovery (BFR) request signal, receiving a response from the network entity, and sending an uplink signal according to the assigned power control parameters to reset and recover the beam fault.

Benefits of technology

It effectively solved the communication interruption problem caused by beam failure, improved the reliability and efficiency of the communication system, and ensured normal communication recovery in the event of beam failure.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119054407A_ABST
    Figure CN119054407A_ABST
Patent Text Reader

Abstract

Aspects relate to techniques for beam failure recovery (BFR). The technique includes transmitting, using a transceiver, a beam failure recovery (BFR) request signal having a first transmit-receive beam pair to a network entity; receiving, using the transceiver, a beam failure recovery (BFR) request response from the network entity; and transmitting, using the transceiver, an uplink (UL) signal to the network entity, wherein the transmission of the UL signal is in accordance with the first transmit-receive beam pair and a power control parameter assigned to a beam failure recovery (BFR) procedure.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The techniques discussed below relate generally to wireless communication networks, and more particularly, to power control parameter resetting associated with beam failure recovery. Background Art

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasts. One example telecommunication standard is 5G New Radio (NR). 5G NR is part of the ongoing mobile broadband evolution promulgated by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)), and other requirements.

[0003] In such wireless communication systems, user equipment (UE) may communicate with a network entity (e.g., a base station) using directional beams because they generally provide improved signaling between the two devices. In some cases, the selected directional beam used for communication between the UE and the network entity may fail or be impaired due to many different reasons, such as unfavorable channel conditions, equipment failure or degradation, etc. In order to resolve a failure in the currently selected directional beam, the UE and the network entity may undergo a beam failure recovery (BFR) procedure. Summary of the invention

[0004] An overview of one or more aspects of the present disclosure is presented below to provide a basic understanding of these aspects. This overview is not an extensive review of all expected features of the present disclosure, and is neither intended to identify key or important elements of all aspects of the present disclosure, nor is it intended to describe the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in a form as a preface to a more detailed description presented later.

[0005] In one example, a user equipment (UE) configured for wireless communication is provided. The UE includes: a transceiver; a memory; and a processor coupled to the transceiver and the memory. The processor is configured to: use the transceiver to send a beam failure recovery (BFR) request signal with a first transmit-receive beam pair to a network entity; use the transceiver to receive a beam failure recovery (BFR) request response from the network entity; and use the transceiver to send an uplink (UL) signal to the network entity, wherein the sending of the UL signal is based on the first transmit-receive beam pair and a power control parameter assigned to a beam failure recovery (BFR) procedure.

[0006] Another example provides a method for wireless communication at a user equipment (UE). The method includes: sending a beam failure recovery (BFR) request signal with a first transmit-receive beam pair to a network entity; receiving a beam failure recovery (BFR) request response from the network entity; and sending an uplink (UL) signal to the network entity, wherein the sending of the UL signal is based on the first transmit-receive beam pair and a power control parameter assigned to a beam failure recovery (BFR) procedure.

[0007] These and other aspects will be more fully understood after reading the following detailed description. After reading the following description of specific exemplary aspects in conjunction with the accompanying drawings, other aspects, features and examples will be apparent to those of ordinary skill in the art. Although each feature may be discussed below with respect to certain examples and drawings, all examples may include one or more of the advantageous features discussed herein. In other words, although one or more examples may be discussed as having certain advantageous features, one or more of such features may also be used according to the various examples discussed herein. Similarly, although each example may be discussed below as an example of a device, system or method, it should be understood that such examples may be implemented in various devices, systems and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 is a diagram illustrating an example of a wireless communication system in accordance with some aspects.

[0009] Figure 2 is a diagram illustrating an example of a radio access network (RAN) in accordance with some aspects.

[0010] Figure 3 is a diagram illustrating an example of a frame structure used in a wireless communication network in accordance with some aspects.

[0011] Figure 4 is a diagram of an example control channel element (CCE) structure in a DL control portion of a timeslot in accordance with some aspects.

[0012] Figure 5 is a diagram of multiple example CORESETs for a DL control portion of a time slot in accordance with some aspects.

[0013] Figure 6 is a diagram illustrating an example of a wireless communication system supporting beamforming and / or multiple-input multiple-output (MIMO) in accordance with some aspects.

[0014] Figure 7 is a diagram illustrating an example of communication between a base station and a UE using beamforming in accordance with some aspects.

[0015] Figure 8 is a diagram illustrating a multi-panel UE in accordance with some aspects.

[0016] Fig. 9 is a diagram illustrating an example of communication between a base station and a UE using a previously failed beam and a newly selected beam in accordance with some aspects.

[0017] Fig.10 is a diagram illustrating example signaling related to a beam failure recovery (BFR) procedure involving power control parameter resetting in accordance with some aspects.

[0018] Fig.11 is a block diagram illustrating an example of a hardware implementation of a user equipment (UE) employing a processing system according to some aspects.

[0019] Fig.12 is a flow chart illustrating an example method of resetting power control parameters in accordance with a beam failure recovery procedure in accordance with some aspects. DETAILED DESCRIPTION

[0020] The specific embodiments described below in conjunction with the accompanying drawings are intended as descriptions of various configurations and are not intended to represent the only configurations in which the concepts described herein may be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0021] Although various aspects and examples are described in this application by illustrating some examples, it will be understood by those skilled in the art that additional specific implementations and use cases can be generated in many different arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, various aspects and / or uses can be generated via integrated chip examples and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not specifically point to use cases or applications, the applicability of various types of described innovations may occur. The scope of specific implementations can range from chip-level or module components to non-module, non-chip-level specific implementations, and further to aggregated, distributed or original equipment manufacturer (OEM) devices or systems that incorporate one or more aspects of the described innovations. In some practical settings, the device in combination with the described aspects and features may also necessarily include additional components and features for the specific implementation and practice of the claimed and described examples. For example, the transmission and reception of wireless signals necessarily include several components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains (RF chains), power amplifiers, modulators, buffers, processors, interleavers, adders, summers, etc.). The innovations described herein are intended to be practiced in a variety of devices of different sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, disaggregated arrangements (e.g., base stations and / or UEs), end-user devices, etc.

[0022] The various concepts presented throughout this disclosure may be implemented across a wide variety of telecommunication systems, network architectures, and communication standards. Figure 1 , various aspects of the present disclosure are illustrated with reference to a wireless communication system 100 as an illustrative example and not as a limitation. The wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. By means of the wireless communication system 100, the UE 106 may be enabled to perform data communications with an external data network 110, such as (but not limited to) the Internet.

[0023] The RAN 104 may implement any suitable one or more wireless communication technologies to provide radio access to the UE 106. As an example, the RAN 104 may operate according to the 3rd Generation Partnership Project (3GPP) New Radio (NR) specifications, commonly referred to as 5G. As another example, the RAN 104 may operate according to a hybrid of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, commonly referred to as Long Term Evolution (LTE). 3GPP refers to such a hybrid RAN as the Next Generation RAN or NG-RAN. Of course, many other examples may be utilized within the scope of the present disclosure.

[0024] As illustrated, RAN 104 includes multiple base stations 108. In a broad sense, a base station is a network element in a radio access network that is responsible for radio transmission and reception to or from a UE in one or more cells. In different technologies, standards or contexts, a base station may be referred to as a base transceiver station (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), a node B (NB), an evolved node B (eNB), a next generation node B (gNB), a transmission reception point (TRP) or some other suitable terminology by those skilled in the art. In some examples, a base station may include two or more TRPs that may be co-located or non-co-located. Each TRP may communicate on the same or different carrier frequencies in the same or different frequency bands. In an example where RAN 104 operates according to both LTE and 5G NR standards, one of the base stations may be an LTE base station, and the other base station may be a 5G NR base station.

[0025] RAN 104 is also illustrated as supporting wireless communications for multiple mobile devices. In the 3GPP standards, a mobile device may be referred to as a user equipment (UE), but those skilled in the art may also refer to it as a mobile station (MS), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology. A UE may be a device (e.g., a mobile device) that provides access to network services to a user.

[0026] Within the present disclosure, a "mobile" device does not necessarily need to have the ability to move, but can be stationary. The term mobile device or mobile equipment refers to a wide variety of devices and technologies. A UE may include a plurality of hardware structural components whose size, shape, and arrangement facilitate communication; such components may include antennas, antenna arrays, RF chains, TX chains, amplifiers, one or more processors, etc. electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile stations, cellular (cell) phones, smart phones, session initiation protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smart books, tablet devices, personal digital assistants (PDAs), and a wide range of embedded systems, for example, corresponding to the "Internet of Things" (IoT).

[0027] The mobile device may also be a car or other transportation vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-rotor aircraft, a quadcopter, a remote control device, a consumer and / or wearable device (such as glasses, a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., an MP3 player), a camera, a game console, etc. The mobile device may also be a digital home or smart home device (such as home audio, video and / or multimedia equipment), an appliance, a vending machine, a smart lighting device, a home security system, a smart meter, etc. The mobile device may also be a smart energy device, a security device, a solar panel or solar array, a municipal infrastructure device that controls electrical power (e.g., a smart grid), lighting, water supply, etc., an industrial automation and enterprise device, a logistics controller, and / or agricultural equipment, etc. In addition, the mobile device may provide connected medical or telemedicine support, such as health care at a distance. Telemedicine devices may include telemedicine monitoring devices and telemedicine management devices, and their communications may be given priority or access priority over other types of information, for example, in terms of priority access for the transmission of critical service data and / or associated QoS for the transmission of critical service data.

[0028] Wireless communication between RAN 104 and UE 106 may be described as utilizing an air interface. Transmissions over the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., similar to UE 106) may be referred to as downlink (DL) transmissions. According to certain aspects of the present disclosure, the term downlink may refer to point-to-multipoint transmissions originating from a base station (e.g., base station 108). Another way to describe this scheme may be to use the term "broadcast channel multiplexing". Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) may be referred to as uplink (UL) transmissions. According to further aspects of the present disclosure, the term uplink may refer to point-to-point transmissions originating at a UE (e.g., UE 106).

[0029] In some examples, access to the air interface may be scheduled, wherein a scheduling entity (e.g., a base station 108) allocates resources for communication among some or all devices and equipment within its service area or cell. Within the present disclosure, as discussed further below, a scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities (e.g., UEs 106). That is, for scheduled communications, multiple UEs 106 (which may be scheduled entities) may utilize resources allocated by the scheduling entity 108.

[0030] Base station 108 is not the only entity that can act as a scheduling entity. That is, in some examples, a UE can act as a scheduling entity, scheduling resources for one or more scheduled entities (e.g., one or more other UEs). For example, a UE can communicate directly with other UEs in a peer-to-peer or device-to-device manner and / or in a relay configuration.

[0031] like Figure 1As illustrated, the scheduling entity 108 may broadcast downlink traffic 112 to one or more scheduled entities (e.g., one or more UEs 106). Broadly speaking, the scheduling entity 108 is a node or device responsible for scheduling traffic in a wireless communication network, including downlink traffic 112 and, in some examples, uplink traffic 116 from one or more scheduled entities (e.g., one or more UEs 106) to the scheduling entity 108. On the other hand, a scheduled entity (e.g., a UE 106) is a node or device that receives downlink control 114 information (including, but not limited to, scheduling information (e.g., grants), synchronization or timing information, or other control information) from another entity in the wireless communication network, such as the scheduling entity 108. The scheduled entity (e.g., UE 106) may send uplink control 118 information including one or more uplink control channels to the scheduling entity 108. The uplink control 118 information may include various packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions.

[0032] In addition, uplink and / or downlink control information and / or traffic information may be sent on a waveform that may be divided into frames, subframes, time slots, and / or symbols in time. As used herein, a symbol may refer to a time unit that carries one resource element (RE) per subcarrier in an orthogonal frequency division multiplexing (OFDM) waveform. A time slot may carry 7 or 14 OFDM symbols. A subframe may refer to a duration of 1 millisecond (ms). Multiple subframes or time slots may be grouped together to form a single frame or radio frame. In the present disclosure, a frame may refer to a predetermined duration (e.g., 10 ms) for wireless transmission, wherein each frame is composed of, for example, 10 subframes of 1 ms each. Of course, these definitions are not required, and any suitable scheme for organizing waveforms may be utilized, and the various time divisions of waveforms may have any suitable duration.

[0033] Generally speaking, base stations 108 may include a backhaul interface for communicating with a backhaul portion 120 of wireless communication system 100. Backhaul portion 120 may provide a link between base stations 108 and core network 102. Additionally, in some examples, a backhaul network may provide interconnections between respective base stations 108. Various types of backhaul interfaces may be employed, such as a direct physical connection using any suitable transport network, a virtual network, or the like.

[0034] The core network 102 may be part of the wireless communication system 100 and may be independent of the radio access technology used in the RAN 104. In some examples, the core network 102 may be configured according to 5G standards (e.g., 5GC). In other examples, the core network 102 may be configured according to 4G Evolved Packet Core (EPC) or any other appropriate standard or configuration.

[0035] Reference now Figure 2 , by way of illustrative example and not limitation, a schematic illustration of an example of a radio access network (RAN) 200 according to some aspects of the present disclosure is provided. In some examples, the RAN 200 may be used in conjunction with the RAN described above and in Figure 1 The RAN 104 illustrated is the same.

[0036] The geographic area covered by the RAN 200 may be divided into a plurality of cellular regions (cells) that may be uniquely identified by a user equipment (UE) based on an identity broadcast from an access point or base station within the geographic area. Figure 2 Cells 202, 204, 206, and 208 are illustrated, each of which may include one or more sectors (not shown). A sector is a sub-area of ​​a cell. All sectors within a cell are served by the same base station. A radio link within a sector may be identified by a single logical identifier belonging to the sector. In a cell divided into sectors, multiple sectors within a cell may be formed by multiple groups of antennas, each of which is responsible for communicating with a UE in a portion of the cell.

[0037] Various base station arrangements can be used. Figure 2 , two base stations (base station 210 and base station 212) are shown in cells 202 and 204. A third base station (base station 214) is shown as controlling a remote radio head (RRH) 216 in cell 206. That is, the base station may have an integrated antenna, or may be connected to an antenna or RRH 216 by a feeder cable. In the illustrated example, cells 202, 204, and 206 may be referred to as macro cells because base stations 210, 212, and 214 support cells with large sizes. In addition, base station 218 is shown in cell 208, which may overlap with one or more macro cells. In this example, cell 208 may be referred to as a small cell (e.g., a micro cell, a pico cell, a femto cell, a home base station, a home node B, a home eNodeB, etc.) because base station 218 supports a cell with a relatively small size. Cell size settings may be performed according to system design and component constraints.

[0038] It is to be understood that RAN 200 may include any number of wireless base stations and cells. In addition, relay nodes may be deployed to extend the size or coverage area of ​​a given cell. Base stations 210, 212, 214, 218 provide wireless access points to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, and / or 218 may be similar to those described above and in Figure 1 The illustrated scheduling entities 108 are the same or similar.

[0039] Figure 2Also included is an unmanned aerial vehicle (UAV) 220, which may be a drone or a quadcopter. UAV 220 may be configured to act as a base station, or more specifically, a mobile base station. That is, in some examples, the cell may not necessarily be stationary, and the geographic area of ​​the cell may move depending on the location of a mobile base station (such as UAV 220).

[0040] Within the RAN 200, cells may include UEs that may communicate with one or more sectors of each cell. In addition, each base station 210, 212, 214, 218, and 220 may be configured to provide access to the core network 102 (see FIG. 1 ) for all UEs in the corresponding cell. Figure 1 ) access point. For example, UEs 222 and 224 may communicate with base station 210; UEs 226 and 228 may communicate with base station 212; UEs 230 and 232 may communicate with base station 214 via RRH 216; UE 234 may communicate with base station 218; and UE 236 may communicate with mobile base station 220. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 may communicate with the base stations described above and in Figure 1 202. In some examples, UAV 220 (e.g., a quadcopter) may be a mobile network node and may be configured to act as a UE. For example, UAV 220 may operate within cell 202 by communicating with base station 210.

[0041] In another aspect of the RAN 200, sidelink signals may be used between UEs without having to rely on scheduling or control information from a base station. Sidelink communications may be utilized in, for example, a device-to-device (D2D) network, a peer-to-peer (P2P) network, a vehicle-to-vehicle (V2V) network, a vehicle-to-everything (V2X) network, and / or other appropriate sidelink networks. For example, two or more UEs (e.g., UEs 238, 240, and 242) may communicate with each other using sidelink signals 237 without relaying the communication through a base station. In some examples, UEs 238, 240, and 242 may each act as a scheduling entity or a transmitting sidelink device and / or a scheduled entity or a receiving sidelink device to schedule resources and communicate sidelink signals 237 between them without relying on scheduling or control information from a base station. In other examples, two or more UEs (e.g., UEs 226 and 228) within the coverage area of ​​a base station (e.g., base station 212) may also communicate sidelink signals 227 via a direct link (sidelink) without routing the communication through base station 212. In this example, base station 212 may allocate resources to UEs 226 and 228 for sidelink communication.

[0042] In order to obtain a low block error rate (BLER) for transmissions over the air interface while still achieving very high data rates, channel coding may be used. That is, wireless communications may typically utilize a suitable error-correcting block code. In a typical block code, an information message or sequence is split into code blocks (CBs), and an encoder (e.g., a codec) at the transmitting device then mathematically adds redundancy to the information message. Utilizing this redundancy in the encoded information message improves the reliability of the message, enabling correction of any bit errors that may occur due to noise.

[0043] Data decoding can be implemented in a variety of ways. In early 5G NR specifications, user data is decoded using quasi-cyclic low-density parity check (LDPC) with two different basemaps: one basemap is used for large code blocks and / or high code rates, and the other basemap is used for other cases. Control information and the physical broadcast channel (PBCH) are decoded based on nested sequences using polar decoding. For these channels, puncturing, shortening, and repetition are used for rate matching.

[0044] Aspects of the present disclosure may be implemented using any suitable channel code. Various implementations of base stations and UEs may include appropriate hardware and capabilities (eg, encoders, decoders, and / or codecs) to utilize one or more of these channel codes for wireless communications.

[0045] In the RAN 200, the ability of a UE to communicate while moving (independent of its location) is called mobility. Each physical channel between the UE and the RAN 200 is generally established, maintained, and released under the control of an access and mobility management function (AMF). In some scenarios, the AMF may include: a security context management function (SCMF) and a security anchor function (SEAF) that performs authentication. The SCMF may manage security contexts for both control plane functionality and user plane functionality in whole or in part.

[0046] In various aspects of the present disclosure, the RAN 200 may utilize DL-based mobility or UL-based mobility to implement mobility and handover (i.e., the transfer of a UE's connection from one radio channel to another). In a network configured for DL-based mobility, during a call with a scheduling entity or at any other time, the UE may monitor various parameters of the signal from its serving cell and various parameters of neighboring cells. Based on the quality of these parameters, the UE may maintain communication with one or more neighboring cells. During this time, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell for a given amount of time, the UE may perform a handover or handover from the serving cell to a neighboring (target) cell. For example, a UE 224 may move from a geographic area corresponding to its serving cell 202 to a geographic area corresponding to a neighboring cell 206. When the signal strength or quality from a neighboring cell 206 exceeds the signal strength and quality of its serving cell 202 for a given amount of time, the UE 224 may send a report message indicating this condition to its serving base station 210. In response, UE 224 may receive the handover command, and the UE may undergo a handover to cell 206 .

[0047] In a network configured for UL-based mobility, the network may select a serving cell for each UE using a UL reference signal from each UE. In some examples, base stations 210, 212, and 214 / 216 may broadcast a unified synchronization signal (e.g., a unified primary synchronization signal (PSS), a unified secondary synchronization signal (SSS), and a unified physical broadcast channel (PBCH)). UEs 222, 224, 226, 228, 230, and 232 may receive the unified synchronization signal, derive carrier frequency and slot timing from the synchronization signal, and send an uplink pilot or reference signal in response to the derived timing. The uplink pilot signal sent by a UE (e.g., UE 224) may be received concurrently by two or more cells (e.g., base stations 210 and 214 / 216) within RAN 200. Each of the cells may measure the strength of the pilot signal, and the radio access network (e.g., one or more of the base stations 210 and 214 / 216 and / or a central node within the core network) may determine a serving cell for the UE 224. As the UE 224 moves through the RAN 200, the RAN 200 may continue to monitor the uplink pilot signals sent by the UE 224. When the signal strength or quality of the pilot signal measured by the neighboring cell exceeds the signal strength or quality measured by the serving cell, the RAN 200 may hand over the UE 224 from the serving cell to the neighboring cell with or without notifying the UE 224.

[0048] Although the synchronization signals transmitted by base stations 210, 212 and 214 / 216 may be uniform, the synchronization signal may not identify a specific cell, but may identify a zone of multiple cells operating on the same frequency and / or using the same timing. Using zones in a 5G network or other next generation communication network implements an uplink-based mobility framework and improves the efficiency of both the UE and the network, because the number of mobility messages that need to be exchanged between the UE and the network can be reduced.

[0049] In various specific implementations, the air interface in the radio access network 200 may utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum generally provides exclusive use of a portion of the spectrum with the help of a mobile network operator purchasing a license from a government regulator. Unlicensed spectrum provides shared use of a portion of the spectrum without the need for a government-granted license. Although it is still generally necessary to comply with some technical rules to access the unlicensed spectrum, generally any operator or device can obtain access. Shared spectrum may fall between licensed spectrum and unlicensed spectrum, where access to the spectrum may require technical rules or restrictions, but the spectrum can still be shared by multiple operators and / or multiple radio access technologies (RATs). For example, a license holder of a portion of a licensed spectrum may provide licensed shared access (LSA) to share the spectrum with other parties (e.g., with appropriate licensee-determined conditions to obtain access).

[0050] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that, although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0051] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4-a or FR4-1 (52.6GHz–71GHz), FR4 (52.6GHz–114.25GHz) and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.

[0052] In view of the above aspects, unless otherwise specifically stated, it should be understood that if used in this article, the term "below 6 GHz" and the like can be broadly referred to as frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" and the like are used in this article, they can be broadly referred to as frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band.

[0053] Devices communicating in the radio access network 200 may utilize one or more multiplexing techniques and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification provides multiple access for UL transmissions from UEs 222 and 224 to the base station 210, and multiplexing of DL transmissions from the base station 210 to one or more UEs 222 and 224 using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP). In addition, for UL transmissions, the 5G NR specification provides support for discrete Fourier transform spread OFDM (DFT-s-OFDM) with CP (also referred to as single carrier FDMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes, and may be provided using time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource extension multiple access (RSMA), or other appropriate multiple access schemes. In addition, multiplexing of DL transmissions from base station 210 to UEs 222 and 224 may be provided using time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes.

[0054] The equipment in the radio access network 200 may also utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link in which two endpoints can communicate with each other in two directions. Full-duplex means that both endpoints can communicate with each other at the same time. Half-duplex means that only one endpoint can transmit information to the other endpoint at a time. Half-duplex simulation is often implemented for wireless links using time division duplex (TDD). In TDD, transmissions in different directions on a given channel are separated from each other using time division multiplexing. That is, in some scenarios, a channel is dedicated to transmission in one direction, while at other times, the channel is dedicated to transmission in another direction, where the direction can change very quickly, for example, several times per time slot. In wireless links, full-duplex channels generally rely on physical isolation of transmitters and receivers and suitable interference cancellation techniques. Full-duplex simulation is often implemented for wireless links by utilizing frequency division duplex (FDD) or space division duplex (SDD). In FDD, transmissions in different directions can operate at different carrier frequencies (e.g., within a paired spectrum). In SDD, transmissions in different directions on a given channel are separated from each other using spatial division multiplexing (SDM). In other examples, full-duplex communication can be implemented within an unpaired spectrum (e.g., within a single carrier bandwidth), where transmissions in different directions occur within different sub-bands of the carrier bandwidth. This type of full-duplex communication may be referred to herein as sub-band full-duplex (SBFD), also known as flexible duplex.

[0055] Will refer to Figure 3 Various aspects of the present disclosure are described using an orthogonal frequency division multiplexing (OFDM) waveform schematically illustrated in . It should be understood by those skilled in the art that various aspects of the present disclosure can be applied to SC-FDMA waveforms in substantially the same manner as described herein below. That is, while some examples of the present disclosure may focus on OFDM links for clarity, it should be understood that the same principles can also be applied to SC-FDMA waveforms.

[0056] Reference now Figure 3 , illustrates an expanded view of an exemplary subframe 302 showing an OFDM resource grid. However, as will be readily appreciated by those skilled in the art, the physical (PHY) transmission structure for any particular application may differ from the examples described herein depending on any number of factors. Here, time is measured in units of OFDM symbols in the horizontal direction; and frequency is measured in units of subcarriers of a carrier in the vertical direction.

[0057] Resource grid 304 may be used to schematically represent the time-frequency resources for a given antenna port. That is, in a multiple-input multiple-output (MIMO) implementation with multiple available antenna ports, a corresponding plurality of resource grids 304 may be available for communication. Resource grid 304 is divided into a plurality of resource elements (REs) 306. RE (which is 1 subcarrier x 1 symbol) is the smallest discrete portion of the time-frequency grid and contains a single complex value representing data from a physical channel or signal. Depending on the modulation utilized in a particular implementation, each RE may represent one or more bits of information. In some examples, a block of REs may be referred to as a physical resource block (PRB), or more simply a resource block (RB) 308, which may contain any suitable number of consecutive subcarriers in the frequency domain. In one example, an RB may include 12 subcarriers (a number independent of the parameter set used). In some examples, depending on the parameter set, an RB may include any suitable number of consecutive OFDM symbols in the time domain. Within the present disclosure, it is assumed that a single RB such as RB 308 corresponds entirely to communication in a single direction (transmission or reception for a given device).

[0058] A collection of contiguous or non-contiguous resource blocks may be referred to herein as a resource block group (RBG), a subband, or a bandwidth part (BWP). A collection of subbands or BWPs may span the entire bandwidth. Scheduling a scheduled entity (e.g., a UE) for downlink, uplink, or sidelink transmission involves scheduling one or more resource elements 306 within one or more subbands or bandwidth parts (BWPs). Thus, a UE typically utilizes only a subset of a resource grid 304. In some examples, an RB may be the smallest resource unit that may be allocated to a UE. Thus, the more RBs scheduled for a UE, and the higher the modulation scheme selected for the air interface, the higher the data rate for the UE. The RBs may be scheduled by a base station (e.g., a gNB, eNB, etc.), or may be self-scheduled by a UE implementing D2D sidelink communication.

[0059] In this illustration, RB 308 is shown as occupying less than the entire bandwidth of subframe 302, with some subcarriers illustrated above and below RB 308. In a given implementation, subframe 302 may have a bandwidth corresponding to any number of one or more RBs 308. Furthermore, in this illustration, RB 308 is shown as occupying less than the entire duration of subframe 302, but this is just one possible example.

[0060] Each 1 ms subframe 302 may consist of one or more adjacent time slots. Figure 3In the example shown, as an illustrative example, one subframe 302 includes four time slots 310. In some examples, a time slot may be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot may include 7 or 14 OFDM symbols with a nominal CP. Additional examples may include mini-slots (sometimes referred to as shortened transmission time intervals (TTIs)) with shorter durations (e.g., one to three OFDM symbols). These mini-slots or shortened transmission time intervals (TTIs) may be transmitted in some cases by occupying resources scheduled for ongoing time slot transmissions for the same UE or different UEs. Any number of resource blocks may be utilized within a subframe or time slot.

[0061] An expanded view of one of the time slots 310 illustrates the time slot 310 including a control region 312 and a data region 314. Generally speaking, the control region 312 may carry control channels, and the data region 314 may carry data channels. Of course, a time slot may contain full DL, full UL, or at least one DL portion and at least one UL portion. Figure 3 The illustrated structure is merely exemplary in nature and different slot structures may be utilized and may include one or more of each of the control region and the data region.

[0062] Although in Figure 3 Although not illustrated in the figure, each RE 306 within the RB 308 may be scheduled to carry one or more physical channels, including a control channel, a shared channel, a data channel, etc. Other REs 306 within the RB 308 may also carry pilot signals or reference signals. These pilot signals or reference signals may enable a receiving device to perform channel estimation of the corresponding channel, which may enable coherent demodulation / detection of the control channel and / or data channel within the RB 308.

[0063] In some examples, time slot 310 may be used for broadcast, multicast, groupcast, or unicast communications. For example, broadcast, multicast, or groupcast communications may refer to point-to-multipoint transmissions from one device (e.g., a base station, UE, or other similar device) to other devices. Here, broadcast communications are delivered to all devices, while multicast or groupcast communications are delivered to multiple intended recipient devices. Unicast communications may refer to point-to-point transmissions from one device to a single other device.

[0064] In an example of cellular communication over a cellular carrier via a Uu interface, for DL ​​transmission, a scheduling entity (e.g., a base station) may allocate one or more REs 306 (e.g., within a control region 312) to one or more scheduled entities (e.g., UEs) to carry DL control information including one or more DL control channels (such as a physical downlink control channel (PDCCH)). The PDCCH carries downlink control information (DCI), including but not limited to power control commands (e.g., one or more open-loop power control parameters and / or one or more closed-loop power control parameters), scheduling information, grants, and / or assignments of REs for DL ​​transmission and UL transmission. The PDCCH may further carry hybrid automatic repeat request (HARQ) feedback transmissions, such as acknowledgements (ACKs) or negative acknowledgements (NACKs). HARQ is a technique well known to those skilled in the art, in which the integrity of packet transmissions may be checked for accuracy at the receiving side, for example, using any appropriate integrity checking mechanism, such as a checksum or a cyclic redundancy check (CRC). If the integrity of the transmission is confirmed, an ACK may be sent, and if it is not confirmed, a NACK may be sent. In response to the NACK, the sending device may transmit a HARQ retransmission, which may implement trace combining, incremental redundancy, and the like.

[0065] The base station may further allocate one or more REs 306 (e.g., in the control region 312 or the data region 314) to carry other DL signals, such as a demodulation reference signal (DMRS); a phase tracking reference signal (PT-RS); a channel state information (CSI) reference signal (CSI-RS); and a synchronization signal block (SSB). The SSB may be broadcast at regular intervals based on a periodicity (e.g., 5ms, 10ms, 20ms, 40ms, 80ms, or 160ms). The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast control channel (PBCH). The UE may utilize the PSS and SSS to achieve radio frame, subframe, time slot, and symbol synchronization in the time domain, to identify the center of the channel (system) bandwidth in the frequency domain, and to identify the physical cell identity (PCI) of the cell.

[0066] The PBCH in the SSB may also include a master information block (MIB) containing various system information and parameters for decoding a system information block (SIB). The SIB may be, for example, a system information type 1 (SystemInformationType1) (SIB1), which may include various additional system information. The MIB and SIB1 together provide minimum system information (SI) for random access. Examples of system information sent in the MIB may include, but are not limited to, subcarrier spacing (e.g., a default downlink parameter set), a system frame number, a configuration of a PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0), a cell barring indicator, a cell reselection indicator, a grid offset, and a search space for SIB1. Examples of the remaining minimum system information (RMSI) sent in SIB1 may include, but are not limited to, a random access search space, a paging search space, downlink configuration information, and uplink configuration information. The base station may also send other system information (OSI).

[0067] In an UL transmission, a scheduled entity (e.g., a UE) may utilize one or more REs 306 to carry UL control information (UCI) including one or more UL control channels (such as a physical uplink control channel (PUCCH)) to a scheduling entity. The UCI may include various packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions. Examples of uplink reference signals may include sounding reference signals (SRS) and uplink DMRS. In some examples, the UCI may include a scheduling request (SR), i.e., a request to the scheduling entity to schedule an uplink transmission. Here, in response to the SR sent on the UCI, the scheduling entity may send downlink control information (DCI), which may schedule resources for uplink packet transmissions. The UCI may also include HARQ feedback, channel state feedback (CSF) (such as a CSI report), or any other appropriate UCI.

[0068] In addition to control information, one or more REs 306 (e.g., within the data region 314) may also be allocated for data traffic. Such data traffic may be carried on one or more traffic channels, such as a physical downlink shared channel (PDSCH) for DL ​​transmissions or a physical uplink shared channel (PUSCH) for UL transmissions. In some examples, one or more REs 306 within the data region 314 may be configured to carry other signals (such as one or more SIBs and DMRS).

[0069] In an example of sidelink communication on a sidelink carrier via a proximity service (ProSe) PC5 interface, a control region 312 of a time slot 310 may include a physical sidelink control channel (PSCCH) including sidelink control information (SCI) sent by an initiating (transmitting) sidelink device (e.g., a Tx V2X device or other Tx UE) toward a set of one or more other receiving sidelink devices (e.g., an Rx V2X device or other Rx UE). A data region 314 of the time slot 310 may include a physical sidelink shared channel (PSSCH) including sidelink data traffic sent by the initiating (transmitting) sidelink device in resources reserved by the transmitting sidelink device via the SCI on the sidelink carrier. Other information may be further sent via various REs 306 within the time slot 310. For example, HARQ feedback information may be sent from a receiving sidelink device to a transmitting sidelink device in a physical sidelink feedback channel (PSFCH) within the time slot 310. Additionally, one or more reference signals, such as a sidelink SSB, a sidelink CSI-RS, a sidelink SRS, and / or a sidelink positioning reference signal (PRS), may be sent within time slot 310 .

[0070] These physical channels described above are typically multiplexed and mapped to transport channels for processing at the medium access control (MAC) layer. The transport channels carry blocks of information called transport blocks (TBs). Based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission, the transport block size (TBS), which may correspond to the number of information bits, may be a controlled parameter.

[0071] Figure 3 The channels or carriers illustrated are not necessarily all channels or carriers that may be utilized between devices, and one of ordinary skill in the art will recognize that other channels or carriers may be utilized in addition to those illustrated, such as other traffic, control, and feedback channels.

[0072] In some examples, depending on the PDCCH format (or aggregation level), the PDCCH may be constructed from a variable number of control channel elements (CCEs). Each CCE includes a plurality of resource elements (REs) that may be grouped into resource element groups (REGs). Each REG may typically include, for example, twelve consecutive REs (or nine REs and three DMRS REs) within the same OFDM symbol and the same RB. Each PDCCH format (or aggregation level) supports different DCI lengths. In some examples, PDCCH aggregation levels of 1, 2, 4, 8, and 16 corresponding to 1, 2, 4, 8, or 16 consecutive CCEs, respectively, may be supported.

[0073] Since the UE does not know the specific aggregation level of the PDCCH or whether there may be multiple PDCCHs for the UE in a time slot, the UE may perform blind decoding of various PDCCH candidates within the first N control OFDM symbols (as indicated by the time slot format of the time slot) based on the expected RNTI (e.g., UE-specific RNTI or group RNTI). Each PDCCH candidate includes a set of one or more consecutive CCEs based on an assumed DCI length (e.g., PDCCH aggregation level).

[0074] In order to limit the number of blind decodings, a search space defining a UE-specific search space (USS) and a common search space (CSS) may be defined. The search space set configured for the UE (e.g., USS and CSS) limits the number of blind decodings performed by the UE for each PDCCH format combination. The starting point (offset or index) of the UE-specific search space may be different for each UE, and each UE may have multiple UE-specific search spaces (e.g., one search space for each aggregation level). The common search space set includes CCEs for transmitting control information common to a group of UEs or all UEs. Therefore, the common search space set is monitored by multiple UEs in a cell. The starting point (offset or index) of the search space set for group common control information may be the same for all UEs in the group, and there may be multiple search space sets defined for group common control information (e.g., one search space set is defined for each configured aggregation level of a group of UEs). The UE may perform blind decoding on all aggregation levels and corresponding USS or CSS to determine whether there is at least one valid DCI for the UE.

[0075] Figure 4 is a diagram of an example control channel element (CCE) 400 structure in a DL control portion 406 of a time slot according to some aspects. For example, a time slot may correspond to Figure 3 The time slots illustrated. Figure 4 The CCE 400 structure of 400 represents a portion of a DL control portion 406, including a plurality of REs 402 that may be grouped into REGs 404. Each REG 404 may typically include, for example, twelve consecutive REs 402 (or nine REs 402 and three DMRS REs) within the same OFDM symbol and the same RB. In this example, the CCE structure 400 includes at least six REGs 404 distributed across three OFDM symbols. However, as will be readily apparent to those skilled in the art, the CCE 400 structure for any particular application may differ from the example described herein, depending on any number of factors. For example, the CCE 400 structure may include any suitable number of REGs.

[0076] In some examples, the PDCCH may be constructed from a variable number of CCEs depending on the PDCCH format (or aggregation level). Each PDCCH format (or aggregation level) supports a different DCI length. In some examples, PDCCH aggregation levels of 1, 2, 4, 8, and 16 corresponding to 1, 2, 4, 8, or 16 consecutive CCEs, respectively, may be supported.

[0077] Since the UE does not know the specific aggregation level of the PDCCH or whether there may be multiple PDCCHs for the UE in a time slot, the UE may perform blind decoding of various PDCCH candidates within the first N control OFDM symbols (as indicated by the time slot format of the time slot) based on the expected RNTI (e.g., UE-specific RNTI or group RNTI). Each PDCCH candidate includes a set of one or more consecutive CCEs based on an assumed DCI length (e.g., PDCCH aggregation level).

[0078] In order to limit the number of blind decodings, a search space defining a UE-specific search space (USS) and a common search space (CSS) may be defined. The search space set configured for the UE (e.g., USS and CSS) limits the number of blind decodings performed by the UE for each PDCCH format combination. The starting point (offset or index) of the UE-specific search space may be different for each UE, and each UE may have multiple UE-specific search spaces (e.g., one search space for each aggregation level). The common search space set includes CCEs for transmitting control information common to a group of UEs or all UEs. Therefore, the common search space set is monitored by multiple UEs in a cell. The starting point (offset or index) of the search space set for group common control information may be the same for all UEs in the group, and there may be multiple search space sets defined for group common control information (e.g., one search space set is defined for each configured aggregation level of a group of UEs). The UE may perform blind decoding on all aggregation levels and corresponding USS or CSS to determine whether there is at least one valid DCI for the UE.

[0079] Figure 5 is a diagram of multiple example CORESETs 500 of a DL control portion 502 of a time slot according to some aspects. The DL control portion 502 may correspond to, for example, Figure 3 The illustrated DL. CORESET 500 may be configured for group common control information or UE specific control information and may be used to send a PDCCH including group common control information or UE specific control information to a set of one or more UEs. A UE may monitor one or more CORESETs 500 that the UE is configured to monitor for UE specific or group common control information.

[0080] Each CORESET 500 represents a portion of a DL control portion 502 including a plurality of subcarriers in the frequency domain and one or more symbols in the time domain. Figure 5 In the example of , each CORESET 500 includes at least one CCE 504, the CORESET having both frequency and time dimensions, and being sized to span at least three OFDM symbols. A CORESET having a size spanning two or more OFDM symbols may be beneficial for use on a relatively small system bandwidth (e.g., 5 MHz). However, a one symbol CORESET is also possible.

[0081] A plurality of CORESETs 500 indexed as CORESET#1-CORESET#N are shown to occur during three OFDM symbols in the time domain and occupy a first frequency domain resource region in the frequency domain of the DL control portion 502. Figure 5 In the example shown, each CORESET 500 includes four CCEs 504. It should be noted that this is only an example. In another example, each CORESET 500 may include any suitable number of CCEs 504. The number of CCEs 504 for each CORESET 500 and the configuration of the CCEs 504 may depend on, for example, the aggregation level applied to the PDCCH.

[0082] As described above, the search space of a UE is indicated by a set of contiguous CCEs that the UE should monitor for downlink assignments and uplink grants related to a specific component carrier of the UE. Figure 5 In the example shown, multiple CORESETs 500 may form a search space 506, which may be a USS or a CSS. Within a USS, the aggregation level of the PDCCH may be, for example, 1, 2, 4, or 8 consecutive CCEs, and within a CSS, the aggregation level of the PDCCH may be, for example, 4 or 8 consecutive CCEs. In addition, the number of PDCCH candidates within each search space may vary depending on the aggregation level utilized. For example, for a USS with aggregation level 1 or 2, the number of PDCCH candidates may be 6. In this example, the number of CCEs in the USS search space 506 for aggregation level 1 may be 6, and the number of CCEs in the USS search space 506 for aggregation level 2 may be 12. However, for a USS with aggregation level 4 or 8, the number of PDCCH candidates may be 2. In this example, the number of CCEs in the USS search space 506 for aggregation level 4 may be 8, and the number of CCEs in the USS search space 506 for aggregation level 8 may be 16. For the CSS search space 506, the number of CCEs in the search space 506 may be 16 regardless of the aggregation level.

[0083] In some aspects of the present disclosure, a scheduling entity (eg, a base station) and / or a scheduled entity (eg, a UE) may be configured for beamforming and / or multiple-input multiple-output (MIMO) techniques. Figure 6 6 is a diagram illustrating an example of a wireless communication system 600 that supports beamforming and / or multiple-input multiple-output (MIMO) according to some aspects. In a MIMO system, a transmitter 602 includes multiple transmit antennas 604 (e.g., N transmit antennas), and a receiver 606 includes multiple receive antennas 608 (e.g., M receive antennas). Therefore, there are N×M signal paths 610 from the transmit antennas 604 to the receive antennas 608. The multiple transmit antennas 604 and the multiple receive antennas 608 can each be configured in a single-panel or multi-panel antenna array. Each of the transmitter 602 and the receiver 606 can be, for example, in a Figure 1 and / or Figure 2 The illustrated scheduling entity (e.g., base station 108), Figure 1 and / or Figure 2 The illustrated scheduled entity (e.g., UE 106) or any other suitable wireless communication device is implemented within the scheduled entity.

[0084] The use of such multi-antenna technology enables the wireless communication system 600 to utilize the spatial domain to support spatial multiplexing, support beamforming and transmit diversity. Spatial multiplexing can be used to simultaneously send different data streams (also referred to as layers) on the same time-frequency resources. These data streams can be sent to a single UE to increase the data rate or to multiple UEs to increase the total system capacity, the latter of which is called multi-user MIMO (MU-MIMO). This is achieved by spatially precoding each data stream (i.e., multiplying the data stream by different weights and phase shifts) and then sending each spatially precoded stream through multiple transmit antennas on the downlink. The spatially precoded data streams arrive at UEs with different spatial characteristics, and the different spatial characteristics enable each UE in the UE to recover one or more data streams destined for the UE. On the uplink, each UE sends a spatially precoded data stream, which enables the base station to identify the source of each spatially precoded data stream.

[0085] The number of data streams or layers corresponds to the rank of transmission. In general, the rank of a MIMO system (e.g., a wireless communication system 600 supporting MIMO) is limited to the lower of the number of transmit or receive antennas 604 or 608. In addition, the channel conditions at the UE and other considerations (such as the available resources at the base station) may also affect the transmission rank. For example, the rank assigned to a particular UE on the downlink (and therefore the number of data streams) may be determined based on a rank indicator (RI) sent from the UE to the base station. The RI may be determined based on the antenna configuration (e.g., the number of transmit and receive antennas) and the signal to interference plus noise ratio (SINR) measured on each receive antenna. For example, the RI may indicate the number of layers that can be supported under the current channel conditions. The base station may use the RI and resource information (e.g., the available resources and amount of data to be scheduled for the UE) to assign a transmission rank to the UE.

[0086] In a time division duplex (TDD) system, UL and DL are reciprocal because they each use different time slots of the same frequency bandwidth. Therefore, in a TDD system, the base station can assign a rank for DL ​​MIMO transmission based on UL SINR measurements (e.g., based on a sounding reference signal (SRS) or other pilot signal sent from the UE). Based on the assigned rank, the base station can then send a CSI-RS using a separate channel state information-reference signal (CSI-RS) sequence for each layer to provide multi-layer channel estimation. Based on the CSI-RS, the UE can measure the channel quality across layers and resource blocks and feed back a channel quality indicator (CQI) and rank indicator (RI) value to the base station for use in updating the rank and assigning REs for future downlink transmissions.

[0087] In one example, if Figure 6 As shown, rank 2 spatial multiplexing transmission on a 2×2 MIMO antenna configuration will transmit one data stream from each of the transmit antennas 604. Each data stream arrives at each of the receive antennas 608 along a different signal path in the signal path 610. The receiver 606 can then reconstruct the data stream using the received signal from each of the receive antennas 608.

[0088] Beamforming is a signal processing technique that may be used at a transmitter 602 or a receiver 606 to shape or direct an antenna beam (e.g., a transmit / receive beam) along a spatial path between the transmitter 602 and the receiver 606. Beamforming may be achieved by combining signals communicated via antennas 604 or 608 (e.g., antenna elements of an antenna array) so that some of the signals experience constructive interference and other signals experience destructive interference. To produce the desired constructive / destructive interference, the transmitter 602 or the receiver 606 may apply an amplitude and / or phase offset to the signal transmitted or received from each of the antennas 604 or 608 associated with the transmitter 602 or the receiver 606.

[0089] A base station (e.g., a gNB) may generally be able to communicate with a UE using transmit beams (e.g., downlink transmit beams) of different beam widths. For example, a base station may be configured to utilize a wider beam when communicating with a UE in motion and a narrower beam when communicating with a stationary UE. A UE may also be configured to utilize one or more downlink receive beams to receive signals from a base station.

[0090] In some examples, in order to select one or more service beams (e.g., one or more downlink transmit beams and one or more downlink receive beams) for communication with a UE, the base station may transmit a reference signal, such as a synchronization signal block (SSB), a tracking reference signal (TRS), or a channel state information reference signal (CSI-RS), on each of the multiple beams (e.g., on each of the multiple downlink transmit beams) in a beam sweeping manner. The UE may measure the reference signal received power (RSRP) on each of the beams (e.g., measure the RSRP on each of the multiple downlink transmit beams) and send a beam measurement report to the base station, which indicates the layer 1 RSRP (L-1 RSRP) of each of the measured beams. The base station may then select a service beam for communication with the UE based on the beam measurement report. In other examples, when the channel is reciprocal, the base station may derive a specific beam (e.g., a specific downlink beam) for communication with the UE based on uplink measurements of one or more uplink reference signals (such as a sounding reference signal (SRS)).

[0091] Similarly, an uplink beam (e.g., an uplink transmit beam at a UE and an uplink receive beam at a base station) may be selected by measuring the RSRP of a received uplink reference signal (e.g., SRS) or a downlink reference signal (e.g., SSB or CSI-RS) during uplink or downlink beam scanning. For example, the base station may determine the uplink beam by uplink beam management via SRS beam scanning measured at the base station or by downlink beam management via SSB / CSI-RS beam scanning measured at the UE. The selected uplink beam may be indicated by a selected SRS resource (e.g., a time-frequency resource for transmission of an SRS) when implementing uplink beam management, or by a selected SSB / CSI-RS resource when implementing downlink beam management. For example, the selected SSB / CSI-RS resource may have a spatial relationship with a selected uplink transmit beam (e.g., an uplink transmit beam for PUCCH, SRS, and / or PUSCH). The resulting selected uplink transmit beam and uplink receive beam may form an uplink beam pair link.

[0092] In 5G New Radio (NR) systems, especially above 6 GHz or in millimeter wave (mmWave) systems (e.g., FR2 or higher), beamformed signals can be used for downlink channels, including the physical downlink control channel (PDCCH) and the physical downlink shared channel (PDSCH). In addition, for UEs configured with beamforming antenna panels, beamformed signals can also be used for uplink channels (including the physical uplink control channel (PUCCH) and the physical uplink shared channel (PUSCH)).

[0093] Figure 7 704 and UE 702 using beamforming according to some aspects. Figure 1 , Figure 2 or Figure 4 Any base station (e.g., gNB) or scheduling entity illustrated, and UE 702 may be Figure 1 , Figure 2 or Figure 4 Any UE or scheduled entity illustrated.

[0094] The base station 704 may generally be capable of communicating with the UE 702 using one or more transmit beams, and the UE 702 may further be capable of communicating with the base station 704 using one or more receive beams. As used herein, the term transmit beam refers to a beam on the base station 704 that can be used for downlink communication or uplink communication with the UE 702. In addition, the term receive beam refers to a beam on the UE 702 that can be used for downlink communication or uplink communication with the base station 704.

[0095] exist Figure 7 In the example shown in , the base station 704 is configured to generate multiple transmit beams 706a, 706b, 706c, 706d, 706e, 706f, 706g and 706h (706a-706h), each of which is associated with a different spatial direction. In addition, the UE 702 is configured to generate multiple receive beams 708a, 708b, 708c, 708d and 708e (708a-708e), each of which is associated with a different spatial direction. It should be noted that although some beams are illustrated as being adjacent to each other, this arrangement may be different in different aspects. For example, the transmit beams 706a-706h transmitted during the same symbol may not be adjacent to each other. In some examples, the base station 704 and the UE 702 may each transmit more or fewer beams distributed in all directions (e.g., 360 degrees) and in three dimensions. In addition, the transmit beams 706a-706h may include beams with varying beam widths. For example, the base station 704 may transmit certain signals (e.g., synchronization signal blocks (SSBs)) on a wider beam and other signals (e.g., CSI-RS) on a narrower beam.

[0096] The base station 704 and the UE 702 may use a beam management procedure to select one or more transmit beams 706a-706h on the base station 704 and one or more receive beams 708a-708e on the UE 702 for communicating uplink signals and downlink signals between the base station and the UE. In one example, during initial cell acquisition, the UE 702 may perform a P1 beam management procedure to scan multiple transmit beams 706a-706h using multiple receive beams 708a-708e to select a beam pair link (e.g., one of the transmit beams 706a-706h and one of the receive beams 708a-708e) for a physical random access channel (PRACH) procedure for initial access to a cell. For example, periodic SSB beam sweeping may be implemented at a specific interval (e.g., based on SSB periodicity) on the base station 704. Thus, the base station 704 may be configured to sweep or transmit an SSB on each of the plurality of wider transmit beams 706a-706h during a beam sweep interval. The UE 702 may measure a reference signal received power (RSRP) of each SSB transmitted on each of the transmit beams 706a-706h or each of the receive beams 708a-708e of the UE 702. The UE 702 may select a transmit beam and a receive beam based on the measured RSRP. In an example, the selected receive beam may be the receive beam on which the highest RSRP is measured, and the selected transmit beam may have the highest RSRP measured on the selected receive beam.

[0097] After completing the PRACH procedure, the base station 704 and the UE 702 may perform a P2 beam management procedure for beam refinement at the base station 704. For example, the base station 704 may be configured to sweep or transmit CSI-RS on each of a plurality of narrower transmit beams 706a-706h. Each of the narrower CSI-RS beams may be a subbeam (not shown) of a selected SSB transmit beam (e.g., within a spatial direction of the SSB transmit beam). Transmission of the CSI-RS transmit beam may occur periodically (e.g., as configured by the gNB via radio resource control (RRC) signaling), semi-persistently (e.g., as configured by the gNB via RRC signaling and activated / deactivated via medium access control-control element (MAC-CE) signaling), or aperiodically (e.g., as triggered by the gNB via downlink control information (DCI)). The UE 702 may be configured to scan multiple CSI-RS transmit beams 706a-706h across multiple receive beams 708a-708e. The UE 702 may then perform beam measurements (e.g., measurements of RSRP, SINR, etc.) on the CSI-RS received on each of the receive beams 708a-708e to determine the respective beam quality of each of the CSI-RS transmit beams 706a-706h, as measured on each of the receive beams 708a-708e.

[0098] The UE 702 may then generate and send a layer 1 (L1) measurement report to the base station 704, which includes a corresponding beam index (e.g., CSI-RS resource indicator (CRI)) and beam measurements (e.g., RSRP or SINR) for one or more of the CSI-RS transmit beams 706a-706h on one or more of the receive beams 708a-708e. The base station 704 may then select one or more CSI-RS transmit beams on which to communicate downlink and / or uplink control and / or data with the UE 702. In some examples, the selected CSI-RS transmit beam has the highest RSRP from the L1 measurement report. The transmission of the L1 measurement report may occur periodically (e.g., as configured by the gNB via RRC signaling), semi-persistently (e.g., as configured by the gNB via RRC signaling and activated / deactivated via MAC-CE signaling), or aperiodically (e.g., triggered by the gNB via DCI).

[0099] UE 702 may further select a corresponding receive beam on UE 702 for each selected serving CSI-RS transmit beam to form a corresponding beam pair link (BPL) for each selected serving CSI-RS transmit beam. For example, UE 702 may utilize beam measurements obtained during a P2 procedure or perform a P3 beam management procedure to obtain new beam measurements for the selected CSI-RS transmit beam to select a corresponding receive beam for each selected transmit beam. In some examples, the selected receive beam to be paired with a particular CSI-RS transmit beam may be the receive beam on which the highest RSRP is measured for the particular CSI-RS transmit beam.

[0100] In some examples, in addition to performing CSI-RS beam measurements, base station 704 may configure UE 702 to perform SSB beam measurements and provide an L1 measurement report including beam measurements of SSB transmit beams 706a-706h. For example, base station 704 may configure UE 702 to perform SSB beam measurements and / or CSI-RS beam measurements for beam failure detection (BFD), beam failure recovery (BFR), cell reselection, beam tracking (e.g., for mobile UE 702 and / or base station 704), or other beam optimization purposes.

[0101] In addition, when the channel is reciprocal, an uplink beam management scheme may be used to select transmit beams and receive beams. In an example, the UE 702 may be configured to sweep or transmit on each of the multiple receive beams 708a-708e. For example, the UE 702 may transmit an SRS on each beam in different beam directions. In addition, the base station 704 may be configured to receive uplink beam reference signals on multiple transmit beams 706a-706h. The base station 704 may then perform beam measurements (e.g., RSRP, SINR, etc.) of the beam reference signals on each of the transmit beams 706a-706h to determine the corresponding beam quality of each of the receive beams 708a-708e as measured on each of the transmit beams 706a-706h.

[0102] The base station 704 may then select one or more transmit beams on which to communicate downlink and / or uplink control and / or data with the UE 702. In some examples, the selected transmit beam may have the highest RSRP. The UE 702 may then select a corresponding receive beam for each selected serving transmit beam using, for example, the P3 beam management procedure as described above, to form a respective beam pair link (BPL) for each selected serving transmit beam.

[0103] In one example, a single CSI-RS transmit beam (e.g., transmit beam 706d) on the base station 704 and a single receive beam (e.g., receive beam 708c) on the UE 702 may form a single BPL for communication between the base station 704 and the UE 702. In another example, multiple CSI-RS transmit beams (e.g., transmit beams 706c, 706d, and 706e) on the base station 704 and a single receive beam (e.g., receive beam 708c) on the UE 702 may form respective BPLs for communication between the base station 704 and the UE 702. In another example, multiple CSI-RS transmit beams (e.g., transmit beams 706c, 706d, and 706e) on the base station 704 and multiple receive beams (e.g., receive beams 708c and 708d) on the UE 702 may form multiple BPLs for communication between the base station 704 and the UE 702. In this example, the first BPL may include transmit beam 706c and receive beam 708c, the second BPL may include transmit beam 706d and receive beam 708c, and the third BPL may include transmit beam 706e and receive beam 708d. For example, UE 702 may be configured with multiple antenna panels for communicating with base station 704 on multiple UE beams.

[0104] Figure 8 802 according to some aspects. The MP-UE 802 may include multiple antenna panels (e.g., antenna panels 806a and 806b). For example, antenna panels 806a and 806b may be located at various locations on the UE 802 so that the multiple antenna panels 806a and 806b can cover a sphere around the UE 802. Multiple antenna panels 806a and 806b (or any one of them) may support multiple beams (e.g., beams 808a and 808b). For example, each of the antenna panels 806a and 806b includes multiple antenna elements that can be mapped to antenna ports for generating beams 808a and 808b. Here, the term antenna port refers to a logical port (e.g., beam) on which a signal (e.g., data stream or layer) can be sent.

[0105] The multiple panels may provide flexibility in selecting antennas for wireless communications with a network entity 804 (e.g., a base station such as a gNB). For example, the MP-UE 802 may activate or deactivate one or more panels to improve performance and / or reduce battery consumption. Through activation and deactivation of control panels 806a and 806b, the MP-UE 802 may control various operational aspects, such as maximum permitted exposure (MPE), power consumption, UL interference management, etc. In some aspects, panel selection for UL transmissions may be initiated by the UE 802 and / or the network entity 804.

[0106] In some examples, MP-UE 802 may use different sets of panels 806a and 806b for downlink and uplink communications. In one example, MP-UE 802 may use panel 806a for downlink communications and panel 806b for uplink communications. In other examples, MP-UE 802 may use both panels 806a and 806b for communications in the same direction. For example, MP-UE 802 may use panels 806a and 806b to send or receive multiple beams.

[0107] Generally speaking, two signals sent from the same antenna port should experience the same radio channel, while signals sent from two different antenna ports will experience different radio conditions. In some cases, signals sent from two different antenna ports experience a radio channel with common properties. In such cases, the antenna ports are referred to as quasi-co-located (QCL). If the properties of the channel on which the symbols on one antenna port are transmitted can be inferred from the channel on which the symbols on the other antenna port are transmitted, the two antenna ports can be considered to be quasi-co-located. In 5G NR, the UE is equipped with channel estimation, frequency offset error estimation, and synchronization procedures for processing QCL. For example, if the UE knows that the radio channels corresponding to two different antenna ports are QCL in terms of Doppler shift, the UE can determine the Doppler shift for one antenna port and then apply the result to the two antenna ports for channel estimation. This avoids the UE having to calculate the Doppler shift for the two antenna ports separately.

[0108] Four types of QCL are defined in 5G NR: QCL Type A; QCL Type B; QCL Type C; and QCL Type D. For example, QCL Type A may indicate a downlink reference signal (e.g., SSB or CSI-RS) or an uplink reference signal (e.g., SRS), from which a large-scale channel property (LSCP) of a downlink channel or signal or an uplink channel or signal, such as Doppler shift, Doppler spread, average delay, and / or delay spread, may be inferred. QCL Type B and QCL Type C may also indicate a reference signal (e.g., SSB, CSI-RS, or SRS), from which a specific LSPCP may be inferred (e.g., Doppler shift and / or Doppler spread for QCL Type B and average delay and / or delay spread for QCL Type C). QCL Type D may indicate a spatial RX parameter (e.g., a spatial property of a beam on which a downlink / uplink channel or signal is transmitted). The spatial property of the beam may be inferred from the beam used for transmission of a reference signal (eg, SSB, CSI-RS, or SRS) and may indicate, for example, at least one of a beam direction or a beam width.

[0109] QCL information may be conveyed via a transmission configuration indicator (TCI) state. The TCI state includes or maps to a QCL relationship configuration between one or more reference signals (e.g., SSB, CSI-RS, and SRS) and a downlink (DL) or uplink (UL) transmission. For example, the TCI state may include a DL TCI for downlink-only transmission, a joint DL / UL TCI for both downlink and uplink transmissions, an uplink TCI, or spatial relationship information for UL-only transmission. For example, the TCI state may include one or more reference signal identifiers (IDs), each of which identifies an SSB resource, a CSI-RS resource, or an SRS resource. Each resource (SSB, CSI-RS, or SRS resource) indicates a specific beam, frequency resource, and OFDM symbol on which the corresponding reference signal is conveyed. Thus, in an example where the TCI state indicates a QCL type D for downlink or uplink transmission, the reference signal ID may be used to identify the beam to be used for downlink or uplink transmission based on the QCL relationship with the associated reference signal (e.g., SSB, CSI-RS, or SRS) indicated in the TCI state. The TCI may be a unified TCI.

[0110] Various types of unified TCIs may be used for communication. For example, a first type of unified TCI (e.g., type 1 TCI) may be used to indicate a common beam for at least one downlink channel or reference signal and for at least one uplink channel or reference signal (e.g., a joint downlink-uplink common TCI state). A second type of unified TCI (e.g., type 2 TCI) may be used to indicate a common beam for more than one downlink channel or reference signal (e.g., a separate downlink common TCI state). A third type of unified TCI (e.g., type 3 TCI) may be used to indicate a common beam for more than one uplink channel or reference signal (e.g., a separate uplink common TCI state). A fourth type of unified TCI (e.g., type 4 TCI) may be used to indicate a beam for a single downlink channel or reference signal (e.g., a separate downlink single channel or reference signal TCI). A fifth type of unified TCI (e.g., type 5 TCI) may be used to indicate a beam for a single uplink channel or reference signal (e.g., a separate uplink single channel or reference signal TCI). A sixth type of unified TCI (eg, type 6 TCI) may include uplink spatial relation information (SRI) to indicate a beam for a single uplink channel or reference signal.

[0111] Fig. 9908a to 908e. , the UE 902 may communicate with the network entity (e.g., a base station) 904 using a previously failed beam and a newly selected beam according to some aspects. Similar to the base station 704 discussed previously, the network entity 904 may communicate with the UE 902 using a selected one of a set of directional transmit beams 906a to 906h. In this example, the selected current transmit beam is 906d, as depicted by the darker shaded one of the transmit beam sets 906a to 906h. Similarly, the UE 902 may communicate with the network entity using a selected one of a set of directional receive beams 908a to 908e. In this example, the selected current receive beam is 908c, as depicted by the darker shaded one of the receive beam sets 908a to 908e.

[0112] In many cases, communication between the network entity 904 and the UE 902 using the transmit-receive beam pairs 906d-908c may be adversely affected due to equipment and / or communication channel conditions. For example, one or more of the network entity 904 or the UE 902 may have a transmitter and / or receiver component failure or degradation, which reduces the quality of communication between the network entity 904 and the UE 902 using the transmit-receive beam pairs 906d-908c. Alternatively or additionally, the communication channel between the network entity 904 and the UE 902 using the transmit-receive beam pairs 906d-908c may experience degradation due to various reasons, such as blocking or partial blocking, fading, multipath propagation, etc.

[0113] This degradation of communications between the network entity 904 and the UE 902 using the current transmit-receive beam pair 906d-908c is sometimes referred to in the related art as a "beam failure." In response to the beam failure, the network entity 904 and the UE 902 undergo a beam failure recovery (BFR) procedure for selecting a new transmit-receive beam pair for communicating with each other; the new transmit-receive beam pair does not experience the communication degradation as discussed with respect to the current transmit-receive beam pair 906d-908c. For example, in this example, due to a successful BFR procedure, the network entity 904 and the UE 902 have selected and are now communicating using a new transmit-receive beam pair 906e-908d, as depicted by the lighter shaded pair in the set of transmit beams 906a-906h and receive beams 908a to 908e.

[0114] Fig.10 1 is a diagram illustrating example signaling associated with a beam failure recovery (BFR) procedure 1000 involving power control parameter resetting in accordance with some aspects. The left side of the diagram represents operation of a UE 1002 in accordance with the BFR procedure 1000. The right side of the diagram represents operation of a network entity 1004 in accordance with the BFR procedure 1000.

[0115] According to the BFR procedure 1000, the UE 1002 detects a beam failure associated with the current transmit-receive beam pair (block 1010). For example, the UE 1002 may measure one or more DL signal quality parameters in the beam failure detection resource to detect the beam failure. As an example, if the DL reference signal received power (RSRP) decreases below a certain threshold, the UE 1002 may detect the beam failure. Alternatively or additionally, if the signal to interference plus noise ratio (SINR) of the DL signal decreases below a certain threshold, the UE 1002 may detect the beam failure. Alternatively or additionally, if the block error rate (BLER) associated with the DL signal is higher than a certain threshold, the UE 1002 may detect the beam failure. The DL signal or reference signal mentioned above may refer to SSB, TRS and / or CSI-RS.

[0116] In response to detecting the beam failure, the UE 1002 may select a new transmit-receive beam pair for subsequent communication with the network entity 1004 (block 1012). For example, the UE 1002 may have previously performed a beam management procedure (e.g., a P1, P2, and / or P3 beam management procedure) to determine a set of link quality parameters (e.g., RSRP, SINR, BLER, etc.) associated with a set of receive beams in the new beam candidate reference signal resources. Based on the set of link quality parameters, the UE 1002 selects, for example, a new beam candidate reference signal index q having the highest RSRP and / or SINR, or the lowest BLER, in the set of receive beams in the new beam candidate resources. new The new beam candidate reference signal index q new It can be associated with a unified transmission configuration indicator (TCI) state, which means that the transmit-receive beam pair can be used for transmission and / or reception via multiple DL and / or UL channels or signals.

[0117] Then, when selecting the new beam candidate reference signal index q new After that, UE 1002 transmits a reference signal index q indicating a new beam candidate to network entity 1004. new The network entity 1004 sends a beam failure recovery (BFR) request 1014. The BFR request 1014 may be transmitted via a PUSCH transmission and may have an associated HARQ process number. In response to the BFR request 1014, the network entity 1004 uses the new beam candidate reference signal index q newThe indicated beam transmits a beam failure recovery (BFR) request response 1016 to the UE 1002. The BFR beam failure recovery (BFR) request response 1016 may be transmitted in the PDCCH and may include a DCI that schedules an UL transmission (e.g., a PUSCH transmission). The beam failure recovery (BFR) request response 1016 may include information from which the UE 1002 can discern that it is a response to the beam failure recovery (BFR) request 1014. For example, the beam failure recovery (BFR) request response 1016 may include the same HARQ process number as the PUSCH transmission of the BFR request 1014 and a switched new data assignment (NDI) value indicating that the beam failure recovery (BFR) request 1014 was successfully received.

[0118] Then, after a defined time interval (e.g., a time interval indicated by X OFDM symbols, such as X=28) since receiving the beam failure recovery (BFR) request response 1016, the UE 1002 may monitor the PDCCH in all CORESETs to receive scheduled DL data from the network entity 1004 via the PDSCH (block 1018). The UE 1002 then uses the reference signal index q associated with the new beam candidate to determine the DL data to be scheduled. new The antenna port quasi co-location parameter of the same antenna port quasi co-location parameter is used to receive data via the PDSCH and the reference signal 1020 (eg, an aperiodic CSI-RS in a resource from a CSI-RS resource set).

[0119] Use the new beam candidate reference signal index q new The UE 1002 then determines, based on a predetermined rule, a power control parameter for UL signal transmission assigned to a beam failure recovery (BFR) procedure (block 1022). The power control parameter may include a nominal transmit power that achieves a target signal-to-noise ratio (SNR) or a target received signal power associated with the UL signal at the network entity 1004.

[0120] The power control parameters may also include an estimated signal path loss between the UE 1002 and the network entity 1004, where the estimated signal path loss may be calculated using the new beam candidate information q new In some aspects, the path loss estimation after receiving the BFR request response 1016 is performed with the new beam candidate reference signal index q new The associated reference signal may be a reference signal index q new The path loss reference signal configured with the same antenna port quasi co-location parameters as the reference signal of the same antenna port. In some aspects, the path loss estimation after the BFR request response 1016 is performed with the new beam candidate reference signal index q newThe associated reference signal may be a reference signal index q new In some aspects, the reference signal index q of the new beam candidate is used for path loss estimation after the BFR request response 1016. new The associated reference signal may be the new beam candidate reference signal index q new The reference signal.

[0121] The power control parameters may also include a closed-loop power adjustment component, which is indexed as l. The UL transmit power may be the smaller of the nominal power, the sum of the estimated path loss and the closed-loop adjustment power, or the specified maximum transmit power. If the UL transmission is related to PUSCH, PUCCH, or SRS transmission, the nominal power is indexed as j for PUSCH and q for PUCCH. u , and for SRS is indexed as q s , the reference signal used to estimate the path loss is indexed as q d , and the closed loop power adjustment is indexed as 1. The transmit power of PUSCH, PUCCH and SRS is defined in sections 7.1.1, 7.2.1 and 7.3.1 of 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for control (Release 17) (hereinafter referred to as "Rel.17 NR specifications").

[0122] According to one option (e.g., “Option 1”), the power control parameter may require a selected nominal power index (e.g., j=2) from a set of different (increasing) nominal power indices j∈{0,1,…,J-1}, based on the new beam candidate reference signal index q new (q d =q new ) and the selected closed-loop power adjustment index for PUSCH transmission from a set of different (increasing) closed-loop power adjustment indexes l∈{0,1} (e.g., l=0). According to option 1, the power control parameters may require different (increasing) nominal power indices 0≤q u u The selected nominal power index (e.g., q u =0), based on the new beam candidate reference signal index q new (q d =q new ​) and the selected closed-loop power adjustment index (e.g., l=0) for PUCCH transmission from a set of different (increasing) closed-loop power adjustment indices l∈{0,1}. In addition, according to option 1, the power control parameters may need to be based on the selected resource set (e.g., q s =0), based on the new beam candidate reference signal index q new (q d =q new ) is determined based on an estimated path loss determined based on a reference signal associated with SRS, and a selected closed-loop power adjustment index (e.g., l=0) for SRS transmission from a set of different (increasing) closed-loop power adjustment indexes l∈{0,1}.

[0123] According to another option (e.g., "Option 2"), the power control parameters may require a selected nominal power index for random access PUSCH transmission (e.g., j=0), a selected nominal power index for configuring grants of PUSCH transmission (e.g., j=1), and a selected nominal power index for configuring PUSCH transmissions of dynamic grants (e.g., j=2); based on the new beam candidate reference signal index q new (q d =q new ) associated with the reference signal; and the selected closed-loop power adjustment index for PUSCH transmission (e.g., l=0). According to option 2, the power control parameters may require the selected nominal power index (e.g., q u =0), based on the new beam candidate reference signal index q new (q d =q new ) and the selected closed-loop power adjustment index (e.g., l=0) for PUCCH transmission. In addition, according to option 2, the power control parameter may need to be selected from resource set q s = 0 or 1, based on the new beam candidate reference signal index q new (q d =q new ) and a closed-loop power adjustment index (e.g., l=0) for SRS transmission.

[0124] Therefore, if Option 1 is adopted, the following clauses dealing with Beam Failure Recovery (BFR) in section 6 entitled “Link Restoration Procedure” of Rel.17NR specification or all other subsequent versions adopting the following specifications may be modified as follows:

[0125] If the UE is provided with TCI-State_r17 indicating a unified TCI state, then after X symbols from the last symbol received of a PDCCH with a DCI format scheduling a PUSCH transmission with the same HARQ process number as the first PUSCH transmission and with a switched NDI field value, the UE

[0126] - Monitor the PDCCH in all CORESETs and use the PDCCH associated with the corresponding index q new receiving a PDSCH and an aperiodic CSI-RS in resources from a CSI-RS resource set,

[0127] - Send PUCCH, PUSCH and SRS (which use the same spatial domain filters with the same indicated TCI state as for PUCCH and PUSCH), using the same spatial domain filters as those corresponding to q new The same spatial domain filter as the spatial domain filter (if any) and using the power determined using

[0128] For PUCCH, q u =0,q d =q new , and l = 0,

[0129] For PUSCH, j = 2, q d =q new , l = 0, and

[0130] For SRS, q s =0,q d =q new , and l=0.

[0131] If option 2 is adopted, the following clauses dealing with beam failure recovery (BFR) in section 6 entitled “Link recovery procedures” of Rel.17NR specification or all other subsequent versions may be modified as follows:

[0132] If the UE is provided with TCI-State_r17 indicating a unified TCI state, then after X symbols from the last symbol received of a PDCCH with a DCI format scheduling a PUSCH transmission with the same HARQ process number as the first PUSCH transmission and with a switched NDI field value, the UE

[0133] - Monitor the PDCCH in all CORESETs and use the PDCCH associated with the corresponding index q newreceiving a PDSCH and an aperiodic CSI-RS in resources from a CSI-RS resource set,

[0134] - Send PUCCH, PUSCH and SRS (which use the same spatial domain filters with the same indicated TCI state as for PUCCH and PUSCH), using the same spatial domain filters as those corresponding to q new The same spatial domain filter as the spatial domain filter (if any) and using the power determined using

[0135] For PUCCH, q u =0,q d =q new , and l = 0,

[0136] If the PUSCH is a PUSCH during random access, then j=0, and if the PUSCH is a PUSCH based on a configured grant, then j=1, and if the PUSCH is dynamically granted, then j=2, for PUSCH, q d =q new With and l = 0, and

[0137] For SRS, q s =0,q d =q new , and l=0 or 1.

[0138] It should be understood that the above clauses may include both Option 1 and Option 2.

[0139] Then, according to the beam failure recovery (BFR) procedure, UE 1002 uses the new transmit-receiver beam pair q new The one or more UL signals 1024 are transmitted with power control parameters associated with or assigned to a beam failure recovery (BFR) procedure. As previously discussed, the one or more UL signals 1024 may be PUSCH, PUCCH, and / or SRS transmissions.

[0140] In some aspects, the UE 1002 may further receive a unified TCI indication for the UL TCI or joint TCI state, and the UE 1002 may apply the unified TCI to the corresponding uplink channels, such as PUCCH, PUSCH, and / or SRS. If the configuration of the corresponding nominal transmit power or the corresponding path loss compensation factor is provided by a higher layer or updated based on the applied UL or joint TCI state, the UE 1002 may reset the accumulation of the power control adjustment state of the corresponding uplink channels (PUCCH, PUSCH, and / or SRS) on the active UL BWP of the carrier in the serving cell to zero. For example:

[0141] The UE resets the accumulation of the active UL BWPb of carrier f of serving cell c to f. b,f,c (k, l) = 0, k = 0, 1, ..., i, where i is the transmission opportunity index in the following cases: if the corresponding nominal transmission power P O_UE_PUSCH,b,f,c (j) The value is configured by higher layers or updated based on the UL or joint TCI state of the application; or if the corresponding path loss compensation factor α b,f,c (j) The configuration of the value is provided by higher layers or updated based on the UL or joint TCI status of the application.

[0142] UE resets PUCCH power control adjustment state g b,f,c (k, l) = 0, k = 0, 1, ..., i, where i is the transmission opportunity index in the following case: if the nominal transmission power P corresponding to the PUCCH power control adjustment state l of the active UL BWP b of the carrier f of the primary cell c O_PUCCH,b,f,c (q u ) value is provided by higher layers or updated based on the UL or joint TCI state of the application.

[0143] UE resets SRS power control adjustment state h b,f,c (k, l) = 0, k = 0, 1, ..., i, where i is the transmission opportunity index in the following case: if the nominal transmission power P corresponding to the SRS power control adjustment state l of the active UL BWP b of the carrier f of the serving cell c O_SES,b,f,c (q s ) value or path loss compensation factor α SRS,b,f,c (q s ) value is provided by higher layers or updated based on the UL or joint TCI state of the application.

[0144] Fig.11 1 is a block diagram illustrating an example of a hardware implementation of a user equipment (UE) 1100 employing a processing system 1114 according to some aspects. The UE 1100 may be a Figure 1 , Figure 2 , Figure 5 and / or Figures 6 to 10 Any UE or other scheduled entity illustrated by any one or more of .

[0145] According to various aspects of the present disclosure, a processing system 1114 including one or more processors, such as the processor 1104, may be used to implement an element or any portion of an element or any combination of elements. Examples of the processor 1104 include a microprocessor, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, a gated logic component, a discrete hardware circuit, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. In various examples, the UE 1100 may be configured to perform any one or more of the functions described herein. That is, the processor 1104 as used in the UE 1100 may be used to implement, for example, Fig.10 Any one or more of the methods or processes described and illustrated in.

[0146] In some examples, the processor 1104 may be implemented via a baseband or modem chip, and in other implementations, the processor 1104 may include multiple devices distinct and different from the baseband or modem chip (e.g., in scenarios such as those that may work together to implement the examples discussed herein). And as mentioned above, various hardware arrangements and components outside of the baseband modem processor may be used in implementations, including RF chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc.

[0147] In this example, the processing system 1114 may be implemented using a bus architecture, generally represented by bus 1102. Bus 1102 may include any number of interconnecting buses and bridges, depending on the specific application of the processing system 1114 and the overall design constraints. Bus 1102 communicatively couples together various circuits including one or more processors, generally represented by processor 1104, memory 1105, and computer-readable media, generally represented by computer-readable media 1106. Bus 1102 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further.

[0148] The bus interface 1108 provides an interface between the bus 1102 and the transceiver 1110. The transceiver 1110 may be, for example, a wireless transceiver. The transceiver 1110 provides a device for communicating with various other equipment via a transmission medium (e.g., an air interface). The transceiver 1110 may further be coupled to one or more antenna panels 1120 configured to generate one or more uplink transmit / downlink receive beams. The bus interface 1108 further provides an interface between the bus 1102 and a user interface 1112 (e.g., a keypad, a display, a touch screen, a speaker, a microphone, control features, etc.). Of course, such a user interface 1112 may be omitted in some examples.

[0149] Computer readable medium 1106 may be a non-transitory computer readable medium. By way of example, non-transitory computer readable media include magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips), optical disks (e.g., compact disks (CDs) or digital versatile disks (DVDs)), smart cards, flash memory devices (e.g., card, stick, or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. Computer readable medium 1106 may reside in processing system 1114, be external to processing system 1114, or be distributed across multiple entities including processing system 1114. Computer readable medium 1106 may be embodied in a computer program product. By way of example, a computer program product may include a computer readable medium in a packaging material. In some examples, computer readable medium 1106 may be part of memory 1105. Those skilled in the art will recognize how to best implement the described functionality presented throughout this disclosure, depending on the specific application and the overall design constraints imposed on the overall system. In some examples, computer-readable medium 1106 may be implemented on an article of manufacture, which may also include one or more other elements or circuits, such as processor 1104 and / or memory 1105.

[0150] The computer readable medium 1106 may store computer executable code (e.g., software). Software shall be construed broadly to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures / procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0151] One or more processors, such as processor 1104, may be responsible for managing bus 1102 and general processing, including executing software (e.g., instructions or computer executable code) stored on computer-readable medium 1106. The software, when executed by processor 1104, causes processing system 1114 to perform the various processes and functions described herein for any particular device. Computer-readable medium 1106 and / or memory 1105 may also be used to store data that may be manipulated by processor 1104 when executing the software. For example, memory 1105 may store beam management and power control information 1116 associated with the reception and / or transmission of signals.

[0152] In some aspects of the present disclosure, processor 1104 may include circuits configured for various functions. For example, processor 1104 may include communication and processing circuits 1142 configured to communicate with a network entity (e.g., a base station such as a gNB or eNB). In some examples, communication and processing circuits 1142 may include one or more hardware components that provide a physical structure that performs processes related to wireless communication (e.g., signal reception and / or signal transmission) and signal processing (e.g., processing received signals and / or processing signals for transmission). For example, communication and processing circuits 1142 may include one or more transmit / receive chains.

[0153] In some implementations where communication involves receiving information, the communication and processing circuitry 1142 may obtain information from a component of the UE 1100 (e.g., from a transceiver 1110 that receives information via radio frequency signaling or some other type of signaling suitable for an applicable communication medium), process the information (e.g., decode the information), and output the processed information. For example, the communication and processing circuitry 1142 may output the information to another component of the processor 1104, to the memory 1105, or to the bus interface 1108. In some examples, the communication and processing circuitry 1142 may receive one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 1142 may receive information via one or more channels. In some examples, the communication and processing circuitry 1142 may include functionality for a device for receiving. In some examples, the communication and processing circuitry 1142 may include functionality for a device for processing (including a device for demodulating, a device for decoding, etc.).

[0154] In some implementations where communication involves transmitting (e.g., sending) information, the communication and processing circuitry 1142 may obtain information (e.g., from another component of the processor 1104, the memory 1105, or the bus interface 1108), process the information (e.g., modulate, encode, etc. the information), and output the processed information. For example, the communication and processing circuitry 1142 may output the information to the transceiver 1110 (e.g., the transceiver transmits the information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium). In some examples, the communication and processing circuitry 1142 may transmit one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 1142 may transmit information via one or more channels. In some examples, the communication and processing circuitry 1142 may include functionality for a device for transmitting (e.g., a device for sending). In some examples, the communication and processing circuitry 1142 may include functionality for a device for generating (including a device for modulating, a device for encoding, etc.).

[0155] For example, under the control of the communication and processing instructions 1152 stored in the computer readable medium 1106, the communication and processing circuit 1142 may use the transceiver 1110 and the antenna panel 1120 to use the q new The selected transmit-receive beam pair indicated sends a beam failure recovery (BFR) request to the network entity. Under the control of the communication and processing instructions 1152 stored in the computer-readable medium 1106, the communication and processing circuit 1142 may use the transceiver 1110 and the antenna panel 1120 to use the q new The indicated selected transmit-receive beam pair receives a beam failure recovery (BFR) request response from the network entity.

[0156] Additionally, under the control of the communication and processing instructions 1152 stored in the computer-readable medium 1106, the communication and processing circuit 1142 may use the transceiver 1110 and the antenna panel 1120 to receive data from the network entity via the PDSCH and a reference signal (e.g., an aperiodic channel state information reference signal (CSI-RS) in a resource from the CSI-RS resource set), the data being received using a reference signal associated with the q new The communication and processing circuit 1142 may use the antenna port quasi-co-location parameters of the selected transmit-receive beam pair indicated by q to obtain the same antenna port quasi-co-location parameters as those of the selected transmit-receive beam pair indicated by q. new One or more UL signals (e.g., PUCCH, PUSCH, SRS, etc.) are sent to the network entity using the indicated selected transmit-receive beam pair and a transmit power according to a power control parameter assigned to a beam failure recovery (BFR) procedure.

[0157] The processor 1104 may also include a beam management circuit 1144. For example, under the control of the beam management instructions 1154 stored in the computer-readable medium 1106, the beam management circuit 1144 may select a transmit-receive beam pair from a set of candidate transmit-receive beam pairs for communicating with a network entity. Under the control of the beam management instructions 1154 stored in the computer-readable medium 1106, the beam management circuit 1144 may receive and process a set of reference signals (e.g., SSB, TRS, CSI-RS, etc.) to generate a set of link quality metrics (e.g., RSRP, SINR, BLER, etc.) associated with the set of candidate transmit-receive beam pairs, respectively. Under the control of the beam management instructions 1154 stored in the computer-readable medium 1106, the beam management circuit 1144 may detect a failure of the currently selected transmit-receive beam pair if the associated link quality (e.g., RSRP, SINR, BLER, etc.) drops below a defined threshold or rises above a defined threshold. In response to detecting a failure of the currently selected transmit-receive beam pair, the beam management circuit 1144, under the control of the beam management instructions 1154 stored in the computer-readable medium 1106, may select another one of the set of candidate transmit-receive beam pairs based on the best link quality metric associated with the candidate transmit-receive beam pair. The beam management circuit 1144 may use the information 1116 stored in the memory 1105 to perform the aforementioned beam management operations.

[0158] Processor 1104 may additionally include transmit (Tx) power control circuitry 1146. For example, under the control of transmit (Tx) power control instructions 1156 stored in computer-readable medium 1106, Tx power control circuitry 1146 may select a nominal transmit power to achieve a target SNR or received signal power associated with the transmission of one or more UL signals at a network entity. The nominal transmit power may depend on the type of UL signal (e.g., PUSCH, PUCCH, SRS, etc.) and additional information about the UL signal (e.g., random access, grant configuration, dynamic grant configuration for PUSCH, or different resource sets for SRS). Under ... newThe Tx power control circuit 1146 may estimate the path loss associated with the transmission of the UL signal to the network entity using a reference signal associated with the selected transmit-receive beam indicated. Under the control of the transmit (Tx) power control instructions 1156 stored in the computer-readable medium 1106, the Tx power control circuit 1146 may determine the closed-loop power adjustment associated with different types of UL signals (e.g., PUSCH, PUCCH, SRS, etc.). The transmit power of one or more UL signals may be related to the sum of the nominal power, the estimated path loss, and the closed-loop power adjustment. The Tx power control circuit 1146 may use the information 1116 stored in the memory 1105 to perform the aforementioned power control operations.

[0159] Fig.12 1 is a flow chart illustrating an exemplary method 1200 for resetting power control parameters in accordance with a beam failure recovery procedure according to some aspects. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required to implement all aspects. In some examples, the method 1200 may be implemented as described herein and in Fig.11 The UE 1100 illustrated in the figure is executed by a processor or a processing system or by any suitable device for performing the described functions.

[0160] At block 1202, the UE sends a beam failure recovery (BFR) request signal having a first transmit-receive beam pair to a network entity. Fig.11 The communication and processing circuitry 1142 as shown and described with the transceiver 1110 and antenna panel 1120 may together provide a means for transmitting a beam failure restoration (BFR) request signal.

[0161] At block 1204, the UE may receive a beam failure recovery (BFR) request response from a network entity. Fig.11 The communication and processing circuitry 1142 as shown and described with the transceiver 1110 and antenna panel 1120 may together provide a means for receiving a beam failure restoration (BFR) request response signal.

[0162] At block 1206, the UE may send an uplink (UL) signal to a network entity according to the power control parameters assigned to the beam failure recovery (BFR) procedure. Fig.11 The communication and processing circuitry 1142 as shown and described, along with the transceiver 1110 and antenna panel 1120, may together provide a means by which a UE may transmit uplink (UL) signals.

[0163] In some examples, the power control parameter is selected by the Tx power control circuit 1146. In some examples, the power control parameter specifies a nominal power for transmission of a UL signal. In some examples, the nominal power is configured to achieve a target signal-to-noise ratio (SNR) or a target received signal power associated with the UL signal at a network entity. In some examples, the UL signal is transmitted via a physical uplink shared channel (PUSCH), and the nominal power parameter has an index j=2 as specified by the Rel.17NR specification. In some examples, the UL signal is transmitted via a physical uplink control channel (PUCCH), and the nominal power parameter has an index q as specified by the Rel.17NR specification. u = 0. In some examples, the UL signal is a sounding reference signal (SRS), and the nominal power parameter has an index q as specified in the Rel. 17 NR specification s =0.

[0164] In some examples, wherein the UL signal is a random access transmitted via a physical uplink shared channel (PUSCH), and wherein the nominal power parameter has an index j=0 as specified by the Rel.17NR specification. In some examples, the UL signal is related to configuring an access grant transmitted via a physical uplink shared channel (PUSCH), and wherein the nominal power parameter has an index j=1 as specified by the Rel.17NR specification. In some examples, the UL signal is related to configuring a dynamic grant transmitted via a physical uplink shared channel (PUSCH), and wherein the nominal power parameter has an index j=2 as specified by the Rel.17NR specification.

[0165] In some examples, the communication and processing circuit 1142 receives a reference signal associated with the first transmit-receive beam pair from the network entity using the transceiver. In some examples, the power control parameter specifies an estimated signal path loss between the UE and the network entity related to the reference signal. In some examples, the Tx power control circuit 1146 may determine an estimated signal path loss between the UE and the network entity based on the reference signal. In some examples, the reference signal is associated with the first transmit-receive beam pair.

[0166] In some examples, the communication and processing circuitry 1142 may monitor a physical downlink control channel (PDCCH) in one or more CORESETs to receive a reference signal after a defined time interval since the processor received a beam failure recovery (BFR) request response from a network entity. In some examples, the defined time interval has a length indicated in orthogonal frequency division multiplexing (OFDM) symbols. In some examples, the length of the defined time interval is 28 OFDM symbols.

[0167] In some examples, the beam management circuit 1144 may detect a failure of a second transmit-receive beam pair for communicating with a network entity, and the communication and processing circuit 1142 may send a beam failure recovery (BFR) request signal in response to the detection of the failure of the second transmit-receive beam pair. In some examples, the beam management circuit 1144 may detect the failure of the second transmit-receive beam pair based on at least one measured link quality parameter associated with a signal received from the network entity via the second transmit-receive beam pair using the transceiver. In some examples, the beam management circuit 1144 may select a first transmit-receive beam pair from a set of candidate transmit-receive beam pairs based on a set of link quality parameters associated with the set of candidate transmit-receive beam pairs, respectively. The beam management circuit 1144 may use the information 1116 stored in the memory 1105 when performing the aforementioned beam management operations.

[0168] In one configuration, UE 1100 includes: means for sending a beam failure recovery (BFR) request signal having a first transmit-receive beam pair to a network entity; means for receiving a beam failure recovery (BFR) request response from the network entity; and means for sending an uplink (UL) signal to the network entity according to the first transmit-receive beam pair and a power control parameter assigned to a beam failure recovery (BFR) procedure. UE 1100 may also include means for specifying a nominal power, estimating a signal path loss, and determining a closed-loop power adjustment based on a type of UL signal to be transmitted. UE 1100 includes means for determining a link quality parameter set for a set of candidate transmit-receive beam pairs, respectively. UE 1100 includes means for detecting a failure of a current transmit-receive beam pair. UE 1100 includes means for selecting a new transmit-receive beam pair from a set of candidate transmit-receive beam pairs, respectively, based on the link quality parameter set.

[0169] Of course, in the above examples, the circuits included in the processor 1104 are provided only as examples, and other devices for performing the functions described may be included in various aspects of the present disclosure, including but not limited to those stored in the computer-readable storage medium 1106 or in the computer-readable storage medium 1106. Figure 1 , Figure 2 and / or Figures 6 to 10 In any other suitable equipment or device described in any of the foregoing and utilizing, for example, Fig.10 and Fig.12 Instructions of the described processes and / or algorithms.

[0170] The following provides an overview of various aspects of the disclosure:

[0171] Aspect 1: A user equipment (UE) configured for wireless communication, the user equipment (UE) comprising: a transceiver; a memory; and a processor, the processor being coupled to the transceiver and the memory, the processor being configured to: use the transceiver to send a beam failure recovery (BFR) request signal having a first transmit-receive beam pair to a network entity; use the transceiver to receive a beam failure recovery (BFR) request response from the network entity; and use the transceiver to send an uplink (UL) signal to the network entity, wherein the UL signal is sent according to the first transmit-receive beam pair and a power control parameter assigned to a beam failure recovery (BFR) procedure.

[0172] Aspect 2: The UE according to aspect 1, wherein the power control parameter specifies a nominal power for transmission of the UL signal.

[0173] Aspect 3: The UE according to aspect 2, wherein the nominal power is configured to achieve a target signal-to-noise ratio (SNR) or a target received signal power associated with the UL signal at the network entity.

[0174] Aspect 4: The UE according to aspect 2 or 3, wherein the UL signal is sent via a physical uplink shared channel (PUSCH), and wherein the nominal power parameter comprises a selected index from a set of different nominal power indices.

[0175] Aspect 5: A UE according to any one of aspects 2 to 4, wherein the UL signal is sent via a physical uplink control channel (PUCCH), and wherein the nominal power parameter has a selected index from a set of different nominal power indices.

[0176] Aspect 6: A UE according to any one of aspects 2 to 5, wherein the UL signal is a sounding reference signal (SRS), and wherein the nominal power parameter is based on a selected resource set of the SRS.

[0177] Aspect 7: A UE according to any one of Aspects 2 to 6, wherein the UL signal is a random access sent via a physical uplink shared channel (PUSCH), and wherein the nominal power parameter comprises a selected index from a set of different nominal power indices.

[0178] Aspect 8: A UE according to any one of Aspects 2 to 7, wherein the UL signal is related to configuring an access grant sent via a physical uplink shared channel (PUSCH), and wherein the nominal power parameter comprises a selected index from a set of different nominal power indices.

[0179] Aspect 9: A UE according to any one of Aspects 2 to 8, wherein the UL signal is related to configuring a dynamic grant sent via a physical uplink shared channel (PUSCH), and wherein the nominal power parameter comprises a selected index from a set of different nominal power indices.

[0180] Aspect 10: A UE according to any one of aspects 2 to 9, wherein the UL signal is a first resource set of a sounding reference signal (SRS), and wherein the nominal power parameter is based on the first resource set of the SRS.

[0181] Aspect 11: The UE according to aspect 10, wherein the UL signal is a second resource set of the SRS, wherein the second resource set of the SRS is different from the first resource set of the SRS, and wherein the nominal power parameter is based on the second resource set of the SRS.

[0182] Aspect 12: The UE according to any one of aspects 1 to 11, wherein the processor is further configured to: receive a reference signal from the network entity using the transceiver.

[0183] Aspect 13: The UE according to aspect 12, wherein the power control parameter specifies an estimated signal path loss between the UE and the network entity related to the reference signal.

[0184] Aspect 14: The UE according to aspect 12 or 13, wherein the reference signal is associated with the first transmit-receive beam pair.

[0185] Aspect 15: A UE according to any one of Aspects 12 to 14, wherein the processor is further configured to: monitor a physical downlink control channel (PDCCH) in one or more CORESETs to receive the reference signal after a defined time interval from the time the processor receives the beam failure recovery (BFR) request response from the network entity.

[0186] Aspect 16: The UE according to aspect 15, wherein the defined time interval has a length indicated in an orthogonal frequency division multiplexing (OFDM) symbol.

[0187] Aspect 17: The UE according to aspect 16, wherein the length of the defined time interval is 28 OFDM symbols.

[0188] Aspect 18: A UE according to any one of Aspects 1 to 17, wherein the processor is further configured to: detect a failure of a second transmit-receive beam pair used to communicate with the network entity, wherein the sending of the beam failure recovery (BFR) request signal is in response to the detection of the failure of the second transmit-receive beam pair.

[0189] Aspect 19: A UE according to Aspect 18, wherein the processor is configured to: detect the failure of the second transmit-receive beam pair based on at least one measured link quality parameter associated with a signal received from the network entity via the second transmit-receive beam pair using the transceiver.

[0190] Aspect 20: A UE according to Aspect 18 or 19, wherein the processor is configured to: select the first transmit-receive beam pair from the set of candidate transmit-receive beam pairs based on a link quality parameter set associated with the set of candidate transmit-receive beam pairs, respectively.

[0191] Aspect 21: A method for performing wireless communications at a user equipment (UE), the method comprising: sending a beam failure recovery (BFR) request signal having a first transmit-receive beam pair to a network entity; receiving a beam failure recovery (BFR) request response from the network entity; and sending an uplink (UL) signal to the network entity, wherein the UL signal is sent according to the first transmit-receive beam pair and a power control parameter assigned to a beam failure recovery (BFR) procedure.

[0192] Aspect 22: The method according to aspect 21, wherein the power control parameter specifies a nominal power for transmission of the UL signal.

[0193] Aspect 23: The method according to aspect 22, wherein the nominal power is configured to achieve a target signal-to-noise ratio (SNR) or a target received signal power associated with the UL signal at the network entity.

[0194] Aspect 24: A method according to aspect 22 or 23, wherein the UL signal is sent via a physical uplink shared channel (PUSCH), and wherein the nominal power parameter has a selected index from a set of different nominal power indices.

[0195] Aspect 25: A method according to any one of aspects 22 to 24, wherein the UL signal is sent via a physical uplink control channel (PUCCH), and wherein the nominal power parameter has a selected index from a set of different nominal power indices.

[0196] Aspect 26: The method according to any one of aspects 22 to 25, wherein the UL signal is a sounding reference signal (SRS), and wherein the nominal power parameter is based on a selected resource set of the SRS.

[0197] Aspect 27: A method according to any one of Aspects 22 to 26, wherein the UL signal is a random access sent via a physical uplink shared channel (PUSCH), and wherein the nominal power parameter has a selected index from a set of different nominal power indices.

[0198] Aspect 28: A method according to any one of Aspects 22 to 27, wherein the UL signal is related to configuring an access grant sent via a physical uplink shared channel (PUSCH), and wherein the nominal power parameter comprises a selected index from a set of different nominal power indices.

[0199] Aspect 29: A method according to any one of Aspects 22 to 28, wherein the UL signal is related to configuring a dynamic grant sent via a physical uplink shared channel (PUSCH), and wherein the nominal power parameter comprises a selected index from a set of different nominal power indices.

[0200] Aspect 30: The method according to any one of aspects 22 to 29, wherein the UL signal is a first resource set of a sounding reference signal (SRS), and wherein the nominal power parameter is based on a selected resource set of the SRS.

[0201] Aspect 31: The method according to aspect 30, wherein the UL signal is a second resource set of the SRS, wherein the second resource set of the SRS is different from the first resource set of the SRS, and wherein the nominal power parameter is based on the second resource set of the SRS.

[0202] Aspect 32: The method according to any one of aspects 21 to 31, further comprising: receiving a reference signal from the network entity.

[0203] Aspect 33: The method according to aspect 32, wherein the power control parameter specifies an estimated signal path loss between the UE and the network entity related to the reference signal.

[0204] Aspect 34: A method according to aspect 32 or 33, wherein the reference signal is associated with the first transmit-receive beam pair.

[0205] Aspect 35: The method according to any one of Aspects 32 to 34 further includes: monitoring a physical downlink control channel (PDCCH) in one or more CORESETs to receive the reference signal after a defined time interval from receiving a beam failure recovery (BFR) request response from the network entity.

[0206] Aspect 36: The method of aspect 35, wherein the defined time interval has a length indicated in an orthogonal frequency division multiplexing (OFDM) symbol.

[0207] Aspect 37: The method according to aspect 36, wherein the length of the defined time interval is 28 OFDM symbols.

[0208] Aspect 38: The method according to any one of Aspects 21 to 37 further includes: detecting a failure of a second transmit-receive beam pair used to communicate with the network entity, wherein the beam fault recovery (BFR) request signal is sent in response to detecting the failure of the second transmit-receive beam pair.

[0209] Aspect 39: A method according to aspect 38, wherein detecting the failure of the second transmit-receive beam pair is based on at least one measured link quality parameter associated with receiving signals from the network entity using the second transmit-receive beam pair.

[0210] Aspect 40: The method according to Aspect 38 or 39 further includes: selecting the first transmit-receive beam pair from the set of candidate transmit-receive beam pairs based on the link quality parameter sets associated with the set of candidate transmit-receive beam pairs.

[0211] Aspect 41: A non-transitory computer readable medium having instructions stored therein, the instructions being executable by one or more processors of a base station to perform the method according to any one of aspects 21 to 40.

[0212] Several aspects of wireless communication networks have been presented with reference to exemplary implementations. As those skilled in the art will readily appreciate, various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures, and communication standards.

[0213] By way of example, various aspects may be implemented within other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile Communications (GSM). Various aspects may also be extended to systems defined by the Third Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolution-Data Optimized (EV-DO). Other examples may be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunication standard, network architecture, and / or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.

[0214] Within the present disclosure, the word "exemplary" is used to mean "serving as an example, instance, or illustration". Any specific implementation or aspect described herein as "exemplary" is not necessarily to be construed as superior or superior to other aspects of the present disclosure. Likewise, the term "aspect" does not require that all aspects of the present disclosure include the discussed features, advantages, or modes of operation. The term "coupled" is used herein to refer to a direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, objects A and C may still be considered to be coupled to each other, even if they are not in direct physical contact with each other. For example, a first object may be coupled to a second object, even if the first object has never been in direct physical contact with the second object. The terms "circuit" and "circuitry" are used broadly, and they are intended to include both hardware implementations of electronic devices and conductors (wherein these electronic devices and conductors, when connected and configured, implement the execution of the functions described in the present disclosure, without limitation on the type of electronic circuits) and software implementations of information and instructions (wherein these information and instructions, when executed by a processor, implement the execution of the functions described in the present disclosure).

[0215] Figure 1 to Figure 1 One or more of the components, steps, features, and / or functions illustrated in 9 may be rearranged and / or combined into a single component, step, feature, or function, or may be embodied in several components, steps, or functions. Additional elements, components, steps, and / or functions may also be added without departing from the novel features disclosed herein. Figure 1 , Figure 2 and Figures 6 to 11 The illustrated apparatus, devices and / or components may be configured to perform one or more of the methods, features, or steps described herein. The novel algorithms described herein may also be effectively implemented in software and / or embedded in hardware.

[0216] It should be understood that the specific order or hierarchy of steps in the disclosed methods is an illustration of an exemplary process. It should be understood that the specific order or hierarchy of steps in these methods can be rearranged based on design preferences. The attached method claims present elements of the various steps in an example order, but are not intended to be limited to the specific order or hierarchy presented unless explicitly stated herein.

[0217] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the various aspects shown herein, but to conform to the full scope consistent with the text of the claims, wherein unless explicitly stated otherwise, reference to an element in the singular form is not intended to mean "one and only one", but "one or more". Unless otherwise specified, the term "some" refers to one or more. The phrase "at least one" referring to a list of items refers to any combination of those items, including a single member. As an example, "at least one of a, b, or c" is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. The composition "A and / or B" is intended to cover A, B, and A and B. The elements of the various aspects described throughout this disclosure are all structurally and functionally equivalent schemes currently or hereafter known to those of ordinary skill in the art, and are expressly incorporated herein by reference, and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be disclosed to the public regardless of whether such disclosure is explicitly recited in the claims. No claim element is to be construed under 35 U.S.C. §112(f) unless the element is expressly recited using the phrase “means for” or, in the case of a method claim, the phrase “step for”.

Claims

1. A user equipment (UE) configured for wireless communication, the user equipment (UE) comprising: Transceiver; Memory; and a processor coupled to the transceiver and the memory, the processor being configured to: sending, using the transceiver, a beam failure recovery (BFR) request signal having a first transmit-receive beam pair to a network entity; receiving, using the transceiver, a beam failure recovery (BFR) request response from the network entity; and An uplink (UL) signal is transmitted to the network entity using the transceiver, wherein the transmission of the UL signal is in accordance with the first transmit-receive beam pair and a power control parameter assigned to a beam failure recovery (BFR) procedure. 2 . The UE of claim 1 , wherein the power control parameter specifies a nominal power for transmission of the UL signal.

3. The UE of claim 2, wherein the nominal power is configured to achieve a target signal-to-noise ratio (SNR) or a target received signal power associated with the UL signal at the network entity.

4. The UE of claim 2, wherein the UL signal is sent via a physical uplink shared channel (PUSCH), and wherein the nominal power parameter has a selected index from a set of different nominal power indices.

5. The UE of claim 2, wherein the UL signal is sent via a physical uplink control channel (PUCCH), and wherein the nominal power parameter has a selected index from a set of different nominal power indices.

6. The UE of claim 2, wherein the UL signal is a sounding reference signal (SRS), and wherein the nominal power parameter is based on a selected resource set of the SRS.

7. The UE of claim 2, wherein the UL signal is a random access transmitted via a physical uplink shared channel (PUSCH), and wherein the nominal power parameter comprises a selected index from a set of different nominal power indices.

8. The UE of claim 2, wherein the UL signal is related to configuring an access grant sent via a physical uplink shared channel (PUSCH), and wherein the nominal power parameter comprises a selected index from a set of different nominal power indices.

9. The UE of claim 2, wherein the UL signal is related to configuring a dynamic grant sent via a physical uplink shared channel (PUSCH), and wherein the nominal power parameter comprises a selected index from a set of different nominal power indices.

10. The UE of claim 2, wherein the UL signal is a first resource set of a sounding reference signal (SRS), and wherein the nominal power parameter is based on the first resource set of the SRS.

11. The UE of claim 10, wherein the UL signal is a second resource set of the SRS, wherein the second resource set of the SRS is different from the first resource set of the SRS, and wherein the nominal power parameter is based on the second resource set of the SRS.

12. The UE of claim 1, wherein the processor is further configured to receive a reference signal from the network entity using the transceiver.

13. The UE of claim 12, wherein the power control parameter specifies an estimated signal path loss between the UE and the network entity associated with the reference signal.

14. The UE of claim 12, wherein the reference signal is associated with the first transmit-receive beam pair.

15. The UE of claim 12, wherein the processor is further configured to: monitor a physical downlink control channel (PDCCH) in one or more CORESETs to receive the reference signal after a defined time interval from when the processor receives the beam failure recovery (BFR) request response from the network entity.

16. The UE of claim 15, wherein the defined time interval has a length indicated in an Orthogonal Frequency Division Multiplexing (OFDM) symbol.

17. The UE of claim 16, wherein the length of the defined time interval is 28 OFDM symbols.

18. A UE according to claim 1, wherein the processor is further configured to: detect a failure of a second transmit-receive beam pair used to communicate with the network entity, wherein the sending of the beam failure recovery (BFR) request signal is in response to the detection of the failure of the second transmit-receive beam pair.

19. The UE of claim 18, wherein the processor is configured to detect the failure of the second transmit-receive beam pair based on at least one measured link quality parameter associated with a signal received from the network entity via the second transmit-receive beam pair using the transceiver.

20. The UE of claim 18, wherein the processor is configured to select the first transmit-receive beam pair from the set of candidate transmit-receive beam pairs based on a set of link quality parameters associated with the set of candidate transmit-receive beam pairs, respectively.

21. A method for wireless communication at a user equipment (UE), the method comprising: sending a beam failure recovery (BFR) request signal having a first transmit-receive beam pair to a network entity; receiving a beam failure recovery (BFR) request response from the network entity; as well as An uplink (UL) signal is transmitted to the network entity, wherein the transmission of the UL signal is based on the first transmit-receive beam pair and a power control parameter assigned to a beam failure recovery (BFR) procedure.

22. The method of claim 21, wherein the power control parameter specifies a nominal power for transmission of the UL signal.

23. The method of claim 22, wherein the nominal power is configured to achieve a target signal-to-noise ratio (SNR) or a target received signal power associated with the UL signal at the network entity.

24. The method of claim 22, wherein the UL signal is sent via a physical uplink shared channel (PUSCH), and wherein the nominal power parameter has a selected index from a set of different nominal power indices.

25. The method of claim 22, wherein the UL signal is sent via a physical uplink control channel (PUCCH), and wherein the nominal power parameter has a selected index from a set of different nominal power indices.

26. The method of claim 22, wherein the UL signal is a sounding reference signal (SRS), and wherein the nominal power parameter is based on a selected set of resources for the SRS.

27. The method of claim 22, wherein the UL signal is a random access sent via a physical uplink shared channel (PUSCH), and wherein the nominal power parameter has a selected index from a set of different nominal power indices.

28. The method of claim 22, wherein the UL signal is related to configuring an access grant sent via a physical uplink shared channel (PUSCH), and wherein the nominal power parameter has a selected index from a set of different nominal power indices.

29. The method of claim 22, wherein the UL signal is related to configuring a dynamic grant sent via a physical uplink shared channel (PUSCH), and wherein the nominal power parameter has a selected index from a set of different nominal power indices.

30. The method of claim 22, wherein the UL signal is a first resource set of a sounding reference signal (SRS), and wherein the nominal power parameter is based on the first resource set of the SRS.

31. The method of claim 30, wherein the UL signal is a second set of resources for the SRS, wherein the second set of resources for the SRS is different from the first set of resources for the SRS, and wherein the nominal power parameter is based on the second set of resources for the SRS.

32. The method of claim 21, further comprising: A reference signal is received from the network entity.

33. The method of claim 32, wherein the power control parameter specifies an estimated signal path loss between the UE and the network entity associated with the reference signal.

34. The method of claim 32, wherein the reference signal is associated with the first transmit-receive beam pair.

35. The method of claim 32, further comprising: A physical downlink control channel (PDCCH) in one or more CORESETs is monitored to receive the reference signal after a defined time interval from receiving a beam failure recovery (BFR) request response from the network entity.

36. The method of claim 35, wherein the defined time interval has a length indicated in an Orthogonal Frequency Division Multiplexing (OFDM) symbol.

37. The method of claim 36, wherein the length of the defined time interval is 28 OFDM symbols.

38. The method of claim 21, further comprising: A failure of a second transmit-receive beam pair used for communicating with the network entity is detected, wherein sending the beam failure recovery (BFR) request signal is responsive to detecting the failure of the second transmit-receive beam pair.

39. The method of claim 38, wherein detecting the failure of the second transmit-receive beam pair is based on at least one measured link quality parameter associated with receiving signals from the network entity using the second transmit-receive beam pair.

40. The method of claim 38, further comprising: The first transmit-receive beam pairs are selected from the set of candidate transmit-receive beam pairs based on a set of link quality parameters associated with the set of candidate transmit-receive beam pairs, respectively.