Beam resource pause

Abstract

Aspects relate to a network entity that transmits, to a user equipment (UE), information indicating whether the UE can at least partially suspend beam failing operation on a particular beam resource of a set of beam resources (e.g., for a certain period of time). For example, based on measurement reports received from the UE, the network entity may predict that beam blocking may occur on at least one beam resource of the set of beam resources (e.g., for a period of time).

Description

[0001] The techniques discussed below relate generally to wireless communications, and more particularly to suspension of beam resources. Background Art

[0002] A next generation wireless communication system (e.g., 5GS) may include a 5G core network and a 5G radio access network (RAN) (e.g., new radio (NR)-RAN). NR-RAN supports communication via one or more cells. For example, a wireless communication device such as a user equipment (UE) may access a first cell of a first base station (BS) such as a gNB and / or access a second cell of a second base station.

[0003] Base stations and user equipment (UE) can utilize beamforming to compensate for high path loss and short range. Beamforming is a signal processing technique used with antenna arrays for directional signal transmission and / or reception. Each antenna in the antenna array transmits a signal that is combined with other signals from other antennas of the same array in such a way that signals at certain angles experience constructive interference while other signals experience destructive interference.

[0004] The base station and the UE may select at least one beam pair link (BPL) for communication between the base station and the UE on the downlink and / or uplink. Each BPL includes corresponding transmit and receive beams on the base station and the UE. For example, on the downlink, the BPL includes a transmit beam on the base station and a receive beam on the UE. To increase the data rate, multiple BPLs may be used to facilitate spatial multiplexing of multiple data streams from the base station to the UE. Summary of the invention

[0005] An overview of one or more aspects of the present disclosure is presented below to provide a basic understanding of these aspects. This summary is not an exhaustive overview 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.

[0006] In some examples, a first device for wireless communication may include a processing system. The processing system may be configured to obtain first information from a second device, the first information indicating whether the first device will suspend a beam failure operation for at least one first beam resource among a plurality of beam resources associated with the second device. The processing system may also be configured to at least partially suspend the beam failure operation for the at least one first beam resource based on the first information.

[0007] In some examples, a method for communicating at a user equipment is disclosed. The method may include obtaining first information from a network entity, the first information indicating whether the user equipment is to suspend beam failure operations for at least one first beam resource of a plurality of beam resources associated with the network entity. The method may also include at least partially suspending the beam failure operations for the at least one first beam resource based on the first information.

[0008] In some examples, a first device for communication may include a component for obtaining first information from a second device, the first information indicating whether the first device will suspend a beam failure operation for at least one first beam resource of a plurality of beam resources associated with the second device. The first device may also include a component for at least partially suspending the beam failure operation for the at least one first beam resource based on the first information.

[0009] In some examples, a non-transitory computer-readable medium stores therein instructions executable by a processing system of a first device to: obtain first information from a second device, the first information indicating whether the first device will suspend a beam failure operation for at least one first beam resource of a plurality of beam resources associated with the second device. The computer-readable medium may also store therein instructions executable by the processing system of the first device to: at least partially suspend the beam failure operation for the at least one first beam resource based on the first information.

[0010] In some examples, a first device for wireless communication may include a processing system. The processing system may be configured to obtain, from a second device, signal measurement information associated with at least one first beam resource among a plurality of beam resources associated with the first device. The processing system may also be configured to generate, based on the signal measurement information, first information indicating whether the second device is to at least partially suspend a beam failure operation for the at least one first beam resource. The processing system may be further configured to output the first information indicating whether the second device is to at least partially suspend the beam failure operation for the at least one first beam resource for transmission to the second device.

[0011] In some examples, a method for communicating at a user equipment is disclosed. The method may include obtaining, from a second device, signal measurement information associated with at least one first beam resource of a plurality of beam resources associated with the first device. The method may also include generating, based on the signal measurement information, first information indicating whether the second device is to at least partially suspend a beam failure operation for the at least one first beam resource. The method may also include outputting the first information indicating whether the second device is to at least partially suspend the beam failure operation for the at least one first beam resource for transmission to the second device.

[0012] In some examples, a first device for communication may include a component for obtaining, from a second device, signal measurement information associated with at least one first beam resource among a plurality of beam resources associated with the first device. The first device may also include a component for generating, based on the signal measurement information, first information indicating whether the second device is to at least partially suspend the beam failure operation for the at least one first beam resource. The first device may also include a component for outputting the first information indicating whether the second device is to at least partially suspend the beam failure operation for the at least one first beam resource for transmission to the second device.

[0013] In some examples, a non-transitory computer-readable medium stores therein instructions executable by a processing system of a first device to perform the following: obtain signal measurement information associated with at least one first beam resource among a plurality of beam resources associated with the first device from a second device. The computer-readable medium may also store therein instructions executable by the processing system of the first device to perform the following: generate first information indicating whether the second device is to at least partially suspend the beam failure operation for the at least one first beam resource based on the signal measurement information. The computer-readable medium may also store therein instructions executable by the processing system of the first device to perform the following: output the first information indicating whether the second device is to at least partially suspend the beam failure operation for the at least one first beam resource for sending to the second device.

[0014] In some examples, a user equipment for wireless communication may include a transceiver and a processing system. The processing system may be configured to receive first information from a network entity via the transceiver, the first information indicating whether the user equipment will suspend a beam failure operation for at least one first beam resource in a plurality of beam resources associated with the network entity. The processing system may also be configured to at least partially suspend the beam failure operation for the at least one first beam resource based on the first information.

[0015] After studying the specific embodiments below, these and other aspects of the present disclosure will become more fully understood. After studying the description of the specific example aspects of the present disclosure below in conjunction with the accompanying drawings, other aspects, features and examples of the present disclosure will be apparent to those of ordinary skill in the art. Although the features of the present disclosure may be discussed below with respect to certain examples and drawings, all examples of the present disclosure 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 of the present disclosure discussed herein. In a similar manner, although the example aspects may be discussed below as device, system or method examples, it should be understood that such example aspects may be implemented in various devices, systems and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 is a schematic illustration of a wireless communication system according to some aspects.

[0017] Figure 2 is a conceptual illustration of an example radio access network in accordance with some aspects.

[0018] Figure 3 is a diagram providing a high-level illustration of one example of a configuration of a decomposed base station in accordance with some aspects.

[0019] Figure 4 is a schematic illustration of wireless resources in an air interface utilizing orthogonal frequency division multiplexing (OFDM) in accordance with some aspects.

[0020] Figure 5 is a schematic illustration of an example of an apparatus for communicating according to some aspects.

[0021] Figure 6 is a block diagram illustrating an example of a wireless communication system supporting beamforming communications in accordance with some aspects.

[0022] Figure 7 is a diagram illustrating an example of communications between a radio access network (RAN) node and a wireless communication device using beamforming in accordance with some aspects.

[0023] Figure 8 is a conceptual illustration of an example of beam prediction operations in accordance with some aspects.

[0024] Fig. 9 is a conceptual illustration of an example of beam failure detection in accordance with some aspects.

[0025] Fig.10 is a conceptual illustration of an example of a prediction blocking window in accordance with some aspects.

[0026] Fig.11 is a diagram illustrating an example of a pause operation according to some aspects.

[0027] Fig.12 is a diagram illustrating an example of beam failure triggering operation in accordance with some aspects.

[0028] Fig.13 is a diagram illustrating another example of beam failure triggering operation in accordance with some aspects.

[0029] Fig.14 is a diagram illustrating another example of beam failure triggering operation in accordance with some aspects.

[0030] Fig.15 is a diagram illustrating another example of beam failure triggering operation in accordance with some aspects.

[0031] Fig.16 is a conceptual illustration of examples of conditions for different beam pause parameters in accordance with some aspects.

[0032] Fig.17 is a signaling diagram illustrating an example of beam failure operation suspension in accordance with some aspects.

[0033] Fig.18 is a block diagram conceptually illustrating an example of a hardware implementation for an apparatus (eg, user equipment) employing a processing system in accordance with some aspects.

[0034] Fig.19 is a flow chart illustrating an example communication method involving at least partially suspending beam failure operations in accordance with some aspects.

[0035] Fig. 20 is a block diagram conceptually illustrating an example of a hardware implementation for an apparatus (eg, a network entity) employing a processing system in accordance with some aspects.

[0036] Fig.21 is a flow chart illustrating an example communication method involving signaling information indicating whether beam failure operations are to be at least partially suspended in accordance with some aspects. DETAILED DESCRIPTION

[0037] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is 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 is 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 these concepts.

[0038] 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 use 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, artificial intelligence (AI) enabled devices, etc.). Although some examples may or may not specifically point to use cases or applications, the applicability of a wide range of described innovations may occur. Specific implementations can range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed, or original equipment manufacturer (OEM) devices or systems in conjunction with one or more aspects of the described innovations. In some actual settings, the device incorporating the described aspects and features may also necessarily include additional components and features for the implementation and implementation 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, 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.

[0039] Various aspects of the present disclosure relate to suspending beam failure operations. A UE may monitor (e.g., periodically monitor) a set of beam resources associated with a network entity (such as a base station) and perform beam failure operations to determine whether a beam failure has occurred. In conjunction with the monitoring, the UE may transmit a measurement report to the network entity, the measurement report indicating, for example, received signal strength measured on different beam resources.

[0040] In some aspects, the present disclosure relates to a network entity transmitting information to a UE indicating whether the UE may at least partially suspend beam failure operations on a particular beam resource (e.g., for a certain period of time). For example, based on a measurement report received from the UE, the network entity may predict that beam blocking may occur on at least one beam resource in a set of beam resources (e.g., for a certain period of time).

[0041] In some examples, in the event that beam failure operation is at least partially suspended for at least one beam resource in the set of beam resources (e.g., beam failure detection reference signal resource #0), the UE may use designated beam failure reporting parameters to determine whether to indicate beam failure for one or more other beam resources in the set of beam resources (e.g., beam failure detection reference signal resource #1). In some aspects, these designated beam failure reporting parameters may be different from beam failure reporting parameters used when there is no suspension of beam resources.

[0042] 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.

[0043] 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 in accordance with the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification, commonly referred to as 5G. As another example, the RAN 104 may operate under a mix of 5G NR and an evolved universal terrestrial radio access network (eUTRAN) standard, commonly referred to as Long Term Evolution (LTE). 3GPP refers to such a hybrid RAN as the Next Generation RAN or NG-RAN. In another example, the RAN 104 may operate in accordance with both the LTE and 5G NR standards. Of course, many other examples may be utilized within the scope of the present disclosure.

[0044] 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 eNode B (eNB), a gNode B (gNB), a transmission and 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 in base station 108 may be an LTE base station, and another base station may be a 5G NR base station.

[0045] The radio access network 104 is also illustrated as supporting wireless communications for multiple mobile devices. The mobile device may be referred to as a user equipment (UE) 106 in the 3GPP standard, but may also be referred to 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 mobile phone, a terminal, a user agent, a mobile client, a client, or some other suitable terminology by those skilled in the art. UE 106 may be a device that provides access to network services to a user. In an example where RAN 104 operates according to both LTE and 5G NR standards, UE 106 may be an evolved universal terrestrial radio access network-new radio dual connectivity (EN-DC) UE that is capable of simultaneously connecting to an LTE base station and an NR base station to receive data packets from both the LTE base station and the NR base station.

[0046] In this document, a mobile device does not necessarily have the ability to move and can be stationary. The term mobile device or mobile device refers to a wide variety of devices and technologies. A UE may include multiple hardware structural components whose size, shape, and arrangement facilitate communication; such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. that are electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile devices, 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 variety of embedded systems, for example, corresponding to the Internet of Things (IoT).

[0047] The mobile device may additionally 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 additionally 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, or the like. Table, etc. The mobile device can additionally 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 can provide connected medical or telemedicine support, such as health care at a distance. Telemedicine devices can include telemedicine monitoring devices and telemedicine management devices, whose communications can be given priority or priority access over other types of information, for example, in terms of priority access for the transmission of critical service data and / or related QoS for the transmission of critical service data.

[0048] The wireless communication between RAN 104 and UE 106 can be described as utilizing an air interface. Transmissions from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) over the air interface can be referred to as downlink (DL) transmissions. In some examples, the term downlink can refer to point-to-multipoint transmissions initiated at a base station (e.g., base station 108). Another way to describe this point-to-multipoint transmission scheme can 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) can be referred to as uplink (UL) transmissions. In some examples, the term uplink can refer to point-to-point transmissions originated at a UE (e.g., UE 106).

[0049] In some examples, access to the air interface may be scheduled, where a scheduling entity (e.g., a base station 108) of some other type of network entity 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). That is, for scheduled communications, multiple UEs 106 (which may be scheduled entities) may utilize resources allocated by a scheduling entity (e.g., a base station 108).

[0050] 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 with other UEs in a peer-to-peer or device-to-device manner and / or in a relay configuration.

[0051] like Figure 1 As illustrated, a scheduling entity (e.g., base station 108) may broadcast downlink traffic 112 to one or more scheduled entities (e.g., UE 106). Broadly speaking, a scheduling entity 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 and / or uplink control information 118 from one or more scheduled entities to the scheduling entity. On the other hand, a scheduled entity is a node or device that receives downlink control information 114, which includes, but is 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 a scheduling entity.

[0052] In addition, uplink control information 118, downlink control information 114, downlink traffic 112 and / or uplink traffic 116 may be divided into frames, subframes, time slots and / or symbols by time. As used herein, a symbol may refer to a time unit in which each subcarrier carries one resource element (RE) in an orthogonal frequency division multiplexing (OFDM) waveform. In some examples, 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., 10ms) for wireless transmission, wherein each frame is composed of, for example, 10 subframes of 1ms 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.

[0053] Typically, base stations 108 may include a backhaul interface for communicating with a backhaul 120 of the wireless communication system. Backhaul 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.

[0054] 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.

[0055] Reference now Figure 2 , by way of example and not limitation, a schematic illustration of a radio access network (RAN) 200 is provided. In some examples, the RAN 200 may be similar to the ones described above and in Figure 1 is the same as the RAN 104 illustrated in .

[0056] The geographic area covered by the RAN 200 may be divided into cells that may be uniquely identified by user equipment (UE) based on an identity broadcast from an access point or base station. 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.

[0057] Various base station arrangements can be used. Figure 2 , two base stations 210 and 212 are shown in cells 202 and 204; and 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 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 larger 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 range. The cell size setting may be performed according to the system design and component constraints.

[0058] It should be understood that the 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 base station / scheduling entity illustrated in is the same.

[0059] Figure 2 Also 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).

[0060] 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, and 218 may be configured to provide a core network 102 (see FIG. 1 ) for all UEs in the respective cells. 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; and UE 234 may communicate with base station 218. 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 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.

[0061] In another aspect of RAN 200, sidelink signals can be used between UEs without relying on scheduling or control information from a base station. Sidelink communications can be utilized in device-to-device (D2D) networks, peer-to-peer (P2P) networks, vehicle-to-vehicle (V2V) networks, vehicle-to-everything (V2X) networks, and / or other suitable sidelink networks. For example, two or more UEs (e.g., UE 238, 240, and 242) can communicate with each other using sidelink signals 237 without relaying the communication through a base station. In some examples, UE 238, 240, and 242 can each act as a scheduling entity or a sender sidelink device and / or a scheduled entity or a receiver 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.

[0062] In RAN 200, the ability for a UE to communicate while moving (independent of its location) is called mobility. This is usually done in an access and mobility management function (AMF, not shown). Figure 1 The AMF establishes, maintains and releases various physical channels between the UE and the radio access network under the control of the AMF (part of the core network 102), where the AMF may include a security context management function (SCMF) that manages the security context of both control plane and user plane functionalities and a security anchor function (SEAF) that performs authentication.

[0063] 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, a UE may monitor various parameters of a 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, UE 224 (illustrated as a vehicle, but any suitable form of UE may be used) may move from a geographic area corresponding to its serving cell (e.g., cell 202) to a geographic area corresponding to a neighboring cell (e.g., cell 206). When the signal strength or quality from a neighboring cell exceeds the signal strength or quality of the serving cell for a given amount of time, UE 224 may send a report message indicating the condition to its serving base station (e.g., base station 210). In response, UE 224 may receive the handover command, and the UE may proceed with the handover to cell 206 .

[0064] In a network configured for UL-based mobility, the network can 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 can 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)). UE222, 224, 226, 228, 230, and 232 can receive a unified synchronization signal, derive a carrier frequency and a time slot timing based on 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) can 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 network may continue to monitor the uplink pilot signal 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.

[0065] 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.

[0066] In various specific implementations, the air interface in the RAN 200 may utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum typically 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).

[0067] The air interface in the RAN 200 may utilize one or more multiplexing 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 known 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 suitable 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.

[0068] In addition, the air interface in the RAN 200 may 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 two 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 emulation 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, at certain times, the channel is dedicated to transmissions in one direction, and at other times, the channel is dedicated to transmissions 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 emulation is often implemented for wireless links by utilizing frequency division duplex (FDD) or space division duplex (SDD). In FDD, transmissions in different directions operate at different carrier frequencies. In SDD, transmissions in different directions on a given channel are separated from each other using space division multiplexing (SDM). In other examples, full-duplex communication can be implemented in an unpaired spectrum (e.g., in a single carrier bandwidth), where transmissions in different directions occur in different sub-bands of the carrier bandwidth. This type of full-duplex communication may be referred to as sub-band full-duplex (SBFD), cross duplex (xDD), or flexible duplex.

[0069] The deployment of a communication system (such as a 5G New Radio (NR) system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station (BS), or one or more units (or one or more components) that perform base station functionality can be implemented in an aggregated architecture or a decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0070] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0071] Base station type operations or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configurations such as those initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0072] Figure 3 A diagram illustrating an example decomposed base station 300 architecture is shown. The decomposed base station 300 architecture may include one or more central units (CUs) 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 325 via an E2 link, or a non-real-time (non-RT) RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more distributed units (DUs) 330 via respective midhaul links, such as an F1 interface. The DU 330 may communicate with one or more radio units (RUs) 340 via respective fronthaul links. The RU 340 may communicate with respective UEs 350 via one or more radio frequency (RF) access links. In some implementations, a UE 350 may be served simultaneously by multiple RUs 340.

[0073] Each of the units (i.e., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RT RIC 315, and SMO framework 305) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of these units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, the unit may include a wired interface configured to receive or send signals to one or more of the other units on a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.

[0074] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, the CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, the CU 310 may be implemented to communicate with a distributed unit (DU) 330 for network control and signaling.

[0075] The DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) based at least in part on functional splits such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, the DU 330 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0076] The lower layer functionality may be implemented by one or more RUs 340. In some deployments, a RU 340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 350. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the implementation of the DU 330 and the CU 310 in a cloud-based RAN architecture (such as a vRAN architecture).

[0077] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 390) to perform network element lifecycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some specific implementations, the SMO framework 305 may communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .

[0078] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or communicate with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0079] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0080] Reference will be made to the OFDM waveform (an example of which is given in Figure 4 Various aspects of the present disclosure are described in detail with reference to Figure 1 (illustrated schematically in Figure 2). 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.

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

[0082] Resource grid 404 can be used to schematically represent the time-frequency resources for a given antenna port. In some examples, an antenna port is a logical entity for mapping a data stream to one or more antennas. Each antenna port can be associated with a reference signal (e.g., this can allow a receiver to distinguish data streams associated with different antenna ports in a received transmission). Antenna ports can be defined so that the channel on which a symbol on the antenna port is transmitted can be inferred from the channel on which another symbol on the same antenna port is transmitted. Therefore, a given antenna port can represent a specific channel model associated with a specific reference signal. In some examples, a given antenna port and a subcarrier spacing (SCS) can be associated with a corresponding resource grid (including REs as discussed above). Here, modulated data symbols from a multiple-input multiple-output (MIMO) layer can be combined and redistributed to each antenna port in the antenna port, and then pre-decoding is applied, and the pre-decoded data symbols are applied to the corresponding REs for generating and transmitting OFDM signals via one or more physical antenna elements. In some examples, the mapping of antenna ports to physical antennas can be based on beamforming (e.g., signals can be sent on certain antenna ports to form a desired beam). Thus, a given antenna port may correspond to a particular set of beamforming parameters (eg, signal phase and / or amplitude).

[0083] In a MIMO implementation with multiple available antenna ports, a corresponding number of resource grids 404 may be available for communication. Resource grid 404 is divided into multiple resource elements (REs) 406. RE (which is 1 subcarrier × 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) 408, 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 408) corresponds entirely to communication in a single direction (transmission or reception for a given device).

[0084] A collection of contiguous or discontinuous 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 typically involves scheduling one or more resource elements 406 within one or more subbands or bandwidth parts (BWPs). Thus, a UE typically utilizes only a subset of a resource grid 404. 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 scheduling entity such as a base station (e.g., a gNB, an eNB, etc.), or may be self-scheduled by a UE implementing D2D sidelink communication.

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

[0086] Each 1 ms subframe 402 may consist of one or more adjacent time slots. Figure 4 In the example shown, as an illustrative example, a subframe 402 includes four time slots 410. 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 micro-slots (sometimes referred to as shortened transmission time intervals (TTIs)) with shorter durations (e.g., one to three OFDM symbols). These micro-slots or shortened transmission time intervals (TTIs) may be transmitted in some cases by occupying resources that are 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.

[0087] An expanded view of one of the time slots 410 illustrates that the time slot 410 includes a control region 412 and a data region 414. In general, the control region 412 may carry control channels, and the data region 414 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 4 The structure illustrated in is merely an example, and different time slot structures may be utilized and may include one or more of each of the control region and the data region.

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

[0089] In some examples, time slot 410 may be utilized 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 receiving devices. Unicast communications may refer to point-to-point transmissions from one device to a single other device.

[0090] In an example of cellular communication on a cellular carrier via a Uu interface, for DL ​​transmission, a scheduling entity (e.g., a base station) may allocate one or more REs 406 (e.g., within a control region 412) 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 a hybrid automatic repeat request (HARQ) feedback transmission, such as an acknowledgement (ACK) or a negative acknowledgement (NACK). HARQ is a technique well known to those of ordinary skill in the art, wherein the integrity of a packet transmission may be checked for accuracy at the receiving side, for example, using any appropriate integrity check 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.

[0091] The base station may also allocate one or more REs 406 (e.g., in the control region 412 or the data region 414) 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, 30ms, 80ms, or 130ms). 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.

[0092] 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, SystemInformationType 1 (SIB1), which may include various additional (remaining) system information. The MIB and SIB1 together provide minimum system information (SI) for initial access. Examples of system information sent in the MIB may include, but are not limited to, subcarrier spacing (e.g., default downlink parameter set), system frame number, configuration of the PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0), cell barring indicator, cell reselection indicator, grid offset, and search space for SIB1. Examples of remaining minimum system information (RMSI) sent in SIB1 may include, but are not limited to, random access search space, paging search space, downlink configuration information, and uplink configuration information. The base station may also send other system information (OSI).

[0093] In UL transmission, the UE may utilize one or more REs 406 to carry UL control information (UCI) to the scheduling entity, and the UL control information (UCI) includes one or more UL control channels, such as a physical uplink control channel (PUCCH). The UCI may include various packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmission. 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., requesting the scheduling entity to schedule uplink transmission. In this article, 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 transmission. The UCI may also include HARQ feedback, channel state feedback (CSF) (such as a CSI report), or any other appropriate UCI.

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

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

[0096] 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 information blocks 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.

[0097] References Figures 1 to 4 The channels or carriers described are not necessarily all channels or carriers that may be utilized between a scheduling entity and a scheduled entity, 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.

[0098] Figure 5 An example apparatus 500 is illustrated in accordance with certain aspects of the present disclosure. In some examples, apparatus 500 may be a network entity, a UE, or some other type of wireless node (e.g., a node that utilizes a wireless spectrum (e.g., an RF spectrum) to communicate with another node or entity). In some examples, apparatus 500 may correspond to Figure 1 , Figure 2 , Figure 3 , Figure 6 , Figure 7 , Figure 8 , Fig.17 , Fig.18 and Fig. 20 Any of the apparatus, UE, scheduled entity, network entity, base station (e.g., gNB), scheduling entity, distributed unit, control unit, RAN node or CN entity shown in any of the.

[0099] The apparatus 500 includes an apparatus 502 (e.g., an integrated circuit) and optionally at least one other component 508. In some aspects, the apparatus 502 may be configured to operate in a wireless communication device (e.g., a UE, a BS, etc.) and perform one or more of the operations described herein. The apparatus 502 includes a processing system 504 and a memory 506 coupled to the processing system 504. Example implementations of the processing system 504 are provided herein. In some examples, Figure 5 The processing system 504 may correspond to Fig.18 of processing system 1814. In some examples, Figure 5 The processing system 504 may correspond to Fig. 20 Processing system 2014.

[0100] In general, processing system 504 is adapted to process, including execute, such programming stored on memory 506. For example, memory 506 may store instructions that, when executed by processing system 504, cause processing system 504 to perform one or more of the operations described herein.

[0101] In some implementations, the device 502 communicates with at least one other component of the device 500 (e.g., a component 508 external to the device 502). To this end, in some implementations, the device 502 may include at least one interface 510 (e.g., a transmit and / or receive interface) coupled to the processing system 504 for outputting and / or obtaining (e.g., transmitting and / or receiving) information (e.g., received information, generated information, decoded information, messages, etc.) between the processing system 504 and the other component 508. In some implementations, the interface 510 may include an interface bus, a bus driver, a bus receiver, a buffer, other suitable circuits, or a combination thereof. In some implementations, the interface 510 may include a radio frequency (RF) circuit (e.g., an RF transmitter and / or an RF receiver). In some implementations, the interface 510 may be configured to connect the device 502 to one or more other components of the device 500 (e.g., an RF transmitter and / or an RF receiver). Figure 5 For example, interface 510 may be configured to connect processing system 504 to a radio frequency (RF) front end (eg, an RF transmitter and / or an RF receiver).

[0102] Device 502 can communicate with other devices in various ways. Figure 5In some cases, the device 502 may have an interface to provide (e.g., output, transmit, send, etc.) information for RF transmission, rather than sending information via RF signaling. For example, the processing system 504 may output information to the RF front end via a bus interface for RF transmission. Similarly, the device 502 may have an interface for obtaining information received by another device, rather than receiving information via RF signaling. For example, the processing system 504 may obtain (e.g., receive) information from an RF receiver that receives information via RF signaling via a bus interface. In some specific implementations, the interface may include multiple interfaces. For example, a bidirectional interface may include a first interface for obtaining and a second interface for outputting.

[0103] A scheduling entity (eg, a network entity) and / or a scheduled entity (eg, a UE) may be configured for beamforming and / or multiple-input multiple-output (MIMO) techniques. Figure 6 An example of a wireless communication system 600 supporting beamforming and / or MIMO is illustrated. In the wireless communication system 600, a transmitter 602 includes a plurality of transmit antennas 604 (e.g., N transmit antennas), and a receiver 606 includes a plurality of 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. Each of the transmitter 602 and the receiver 606 may be implemented, for example, within a scheduling entity, a scheduled entity, or any other suitable wireless communication device.

[0104] The use of such multi-antenna technology enables wireless communication systems to exploit the spatial domain to support spatial multiplexing, 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 of the UEs 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 network entity to identify the source of each spatially precoded data stream.

[0105] The number of data streams or layers corresponds to the rank of transmission. In general, the rank of a wireless communication system 600 (e.g., a MIMO system) is limited to the number of transmit antennas 604 or receive antennas 608 (whichever is lower). In addition, the channel conditions at the UE and other considerations (such as the available resources at the network entity) 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 network entity. 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 network entity may use the RI together with resource information (e.g., available resources and the amount of data to be scheduled for the UE) to assign a transmission rank to the UE.

[0106] In an example (e.g., Figure 6 ), a rank-2 spatial multiplexing transmission on a 2×2 MIMO antenna configuration will send one data stream from each transmit antenna 604. Each data stream arrives at each receive antenna 608 along a different signal path 610. The receiver 606 can then reconstruct the data stream using the received signal from each receive antenna 608.

[0107] Beamforming is a signal processing technique that may be used at the transmitter 602 or the receiver 606 to shape or direct an antenna beam (e.g., a transmit beam or a receive beam) along a spatial path between the transmitter 602 and the receiver 606. Beamforming may be achieved by combining signals communicated via the transmit antennas 604 or the receive antennas 608 (e.g., antenna elements of an antenna array module) so that some of the signals experience constructive interference and other signals experience destructive interference. In order 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 from each of the transmit antennas 604 or received by each of the receive antennas 608.

[0108] In 5G New Radio (NR) systems, especially above 6 GHz or in mmWave systems, beamformed signals can be used for most downlink channels, including the Physical Downlink Control Channel (PDCCH) and the Physical Downlink Shared Channel (PDSCH). In addition, broadcast control information (e.g., SSB, Slot Format Indicator (SFI), and paging information) can be sent in a beam scanning manner so that all scheduled entities (UEs) in the coverage area of ​​the Transmit and Receive Point (TRP) (e.g., gNB) can receive the broadcast control information. In addition, for UEs configured with beamforming antenna arrays, beamformed signals can also be used for uplink channels (including the Physical Uplink Control Channel (PUCCH) and the Physical Uplink Shared Channel (PUSCH)).

[0109] A network entity (e.g., a gNB) may generally be able to communicate with a UE using beams (e.g., downlink transmit beams) of different beam widths. For example, a network entity 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.

[0110] Figure 7 704 and UE 702 using beamformed signals according to some aspects. The network entity 704 may be a Figure 1 , Figure 2 , Figure 3 , Figure 5 , Figure 6 , Figure 8 , Fig.17 and Fig. 20 Any of the network entities (e.g., gNB), CU, DU, RU, or scheduling entities illustrated in any of the figures, and UE 702 may be in Figure 1 , Figure 2 , Figure 3 , Figure 5 , Figure 6 , Figure 8 , Fig.17 and Fig.18 Any of the UEs or scheduled entities illustrated in any of the figures.

[0111] The network entity 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 network entity 704 using one or more receive beams. As used herein, the term transmit beam refers to a beam on the network entity 704 that can be used for downlink or uplink communication with the UE 702. Additionally, the term receive beam refers to a beam on the UE 702 that can be used for downlink or uplink communication with the network entity 704.

[0112] exist Figure 7 In the example shown, the network entity 704 is configured to generate multiple transmit beams 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-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, such an 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 network entity 704 and the UE 702 may each transmit more or less beams distributed in all directions (e.g., 360 degrees) and in three dimensions. In addition, the transmit beams 706a to 706h may include beams with varying beam widths. For example, the network entity 704 may transmit certain signals (e.g., SSB) on a wider beam and other signals (e.g., CSI-RS) on a narrower beam.

[0113] The network entity 704 and the UE 702 may use a beam management process to select one or more transmit beams 706a-706h on the network entity 704 and one or more receive beams 708a-708e on the UE 702 for communicating uplink and downlink signals therebetween. In one example, during initial cell acquisition, the UE 702 may perform a P1 beam management process to scan the multiple transmit beams 706a-706h on the 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) process for initial access to a cell. For example, periodic SSB beam scanning may be implemented at a specific interval (e.g., based on an SSB periodicity) on the network entity 704. Thus, the network entity 704 may be configured to scan or transmit the SSB on each of the plurality of wider transmit beams 706a-706h. The UE may measure the reference signal received power (RSRP) of each SSB transmit beam on each receive beam of the UE and select transmit and receive beams 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.

[0114] After completing the PRACH process, the network entity 704 and the UE 702 may perform a P2 beam management process for beam refinement. For example, the network entity 704 may be configured to scan 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 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 is configured to scan the multiple CSI-RS transmit beams 706a-706h across the multiple receive beams 708a-708e. The UE 702 then performs beam measurements (e.g., 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.

[0115] The UE 702 may then generate and send a layer 1 (L1) measurement report to the network entity 704, which includes a corresponding beam index (e.g., CSI-RS resource indicator (CRI)) and beam measurements (e.g., RSRP) for one or more of the CSI-RS transmit beams 706a-706h on one or more of the receive beams 708a-708e. The network entity 704 may then select one or more CSI-RS transmit beams on which to send unicast downlink control information and / or user data traffic to the UE 702. In some examples, the selected CSI-RS transmit beam has the highest RSRP from the L1 measurement report. The sending 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).

[0116] UE 702 may further select a corresponding receive beam on UE 702 for each selected serving CSI-RS transmit beam to form a corresponding downlink beam pair link (BPL) for each selected serving CSI-RS transmit beam. For example, UE 702 may utilize beam measurements obtained during the P2 process or perform a P3 beam management process 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.

[0117] In some examples, the network entity 704 may configure the UE 702 to perform SSB beam measurements and provide an L1 measurement report containing beam measurements of the SSB transmit beams 706a-706h. For example, the network entity 704 may configure the UE 702 to perform SSB beam measurements and / or CSI-RS beam measurements for beam failure detection (BRD), beam failure recovery (BFR), cell reselection, beam tracking (e.g., for mobile UE 702 and / or network entity 704), or some other beam optimization purpose.

[0118] 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 scan or transmit on each of the multiple receive beams 708a-708e. For example, the UE 702 may send an SRS on each beam in different beam directions. In addition, the network entity 704 may be configured to receive uplink beam reference signals on multiple transmit beams 706a-706h. The network entity 704 then performs beam measurements (e.g., RSRP, SINR, etc.) on 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.

[0119] The network entity 704 may then select one or more transmit beams on which to transmit unicast downlink control information and / or user data traffic to the UE 702. In some examples, the selected transmit beam has the highest RSRP. The UE 702 may then select a corresponding receive beam for each selected service transmit beam using, for example, the P3 beam management process as described above to form a corresponding beam pair link (BPL) for each selected service transmit beam.

[0120] In one example, a single transmit beam (e.g., transmit beam 706d) on the network entity 704 and a single receive beam (e.g., receive beam 708c) on the UE 702 may form a single BPL for communication between the network entity 704 and the UE 702. In another example, multiple transmit beams (e.g., transmit beams 706c, 706d, and 706e) on the network entity 704 and a single receive beam (e.g., receive beam 708c) on the UE 702 may form respective BPLs for communication between the network entity 704 and the UE 702. In another example, multiple transmit beams (e.g., transmit beams 706c, 706d, and 706e) on the network entity 704 and multiple receive beams (e.g., receive beams 708c and 708d) on the UE 702 may form multiple BPLs for communication between the network entity 704 and the UE 702. In this example, the first BPL may include a transmit beam 706c and a receive beam 708c, the second BPL may include a transmit beam 708d and a receive beam 708c, and the third BPL may include a transmit beam 708e and a receive beam 708d.

[0121] In some examples, in order to select one or more downlink transmit beams and one or more downlink receive beams for communication with UE 702, network entity 704 may transmit a reference signal (such as an SSB or a CSI-RS) on each of the multiple downlink transmit beams in a beam scanning manner. UE 702 may measure a reference signal received power (RSRP) on each of the downlink transmit beams using one or more downlink receive beams on UE 702, and transmit a beam measurement report to network entity 704, the beam measurement report indicating the RSRP of each of the measured downlink transmit beams. Network entity 704 may then select one or more serving downlink beams (e.g., a downlink transmit beam and a downlink receive beam) for communication with UE 702 based on the beam measurement report. The resulting selected downlink transmit beam and downlink receive beam may form a downlink beam pair link. In other examples, when the channel is reciprocal, the network entity 704 may derive a particular downlink beam for communicating with the UE 702 based on uplink measurements of one or more uplink reference signals, such as a sounding reference signal (SRS).

[0122] In some examples, an uplink beam (e.g., an uplink transmit beam at UE 702 and an uplink receive beam at network entity 704) may be selected by measuring RSRP of a received uplink reference signal (e.g., SRS) or downlink reference signal (e.g., SSB or CSI-RS) during uplink or downlink beam scanning. For example, network entity 704 may determine the uplink beam by uplink beam management via scanning with measured SRS beams at network entity 704 or by downlink beam management via scanning with measured SSB / CSI-RS beams at UE 702. The selected uplink beam may be indicated by a selected SRS resource (e.g., a time-frequency resource for transmission of an SRS) when uplink beam management is implemented, or by a selected SSB / CSI-RS resource when downlink beam management is implemented. For example, the selected SSB / CSI-RS resources may have a spatial relationship with the 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.

[0123] The UE may monitor (e.g., periodically monitor) a set of beam resources associated with a network entity (such as a base station) and perform a beam failure operation to determine whether a beam failure has occurred. In conjunction with the monitoring, the UE may transmit a measurement report to the network entity indicating, for example, received signal strengths measured on different beam resources.

[0124] In conventional beam management (BM) operations, the UE may identify beam quality and / or beam failure by performing beam measurements. In some examples, in order to achieve good performance, beam management operations may consume relatively large amounts of power and / or involve relatively high overhead. Therefore, in some cases, the accuracy of beam management operations may be limited due to restrictions on power consumption and / or overhead. In addition, in the event of a beam failure, latency and / or throughput in the system may be negatively affected by beam recovery operations (e.g., resuming operations on a beam or switching to another beam).

[0125] In some examples, a network entity may perform predictive beam management based on artificial intelligence and / or machine learning (AI / ML) algorithms. In some aspects, predictive beam management (e.g., in the spatial domain (SD), time domain (TD), or frequency domain (FD)) may reduce power consumption and / or overhead. In some aspects, predictive beam management may provide improvements in one or more of accuracy, latency, or throughput (e.g., compared to non-predictive beam management). For example, by predicting non-measured beam quality, one or more of lower power consumption, lower overhead, or better accuracy may be achieved. As another example, by predicting future beam blockages or failures, better latency and / or throughput may be achieved.

[0126] In some aspects, beam prediction can be a highly nonlinear problem. Therefore, AI / ML-based predictive beam management methods can provide better performance than beam management methods based on conventional statistical signaling processing. For example, the prediction of future transmit beam quality can depend at least in some aspects on the movement speed and / or trajectory of the UE, the receive beam used or to be used, interference on the channel, etc. Given these dependencies, it can be difficult to model beam prediction based on conventional statistical signaling processing methods.

[0127] When beams are predicted via AI / ML at the UE or network entity (e.g., gNB), there may be a tradeoff between performance and UE power. For example, to predict future downlink transmit beam quality, the UE may have more observations (e.g., via measurements) than the network entity (e.g., via UE feedback). Therefore, the prediction at the UE may outperform the prediction at the network entity, but may result in higher UE power consumption due to the inferred operation.

[0128] In addition, training at the network entity or at the UE (e.g., model training) affects the effort in data collection and the effort in UE computation. For training at the network entity, data may be collected via an air interface (e.g., an enhanced air interface) or via an application layer method. For training at the UE, additional UE computation and / or buffering operations may be required (e.g., for both model training and associated data storage).

[0129] Figure 88 is a conceptual illustration of an example of beam prediction operations 800 in accordance with some aspects. A UE (not shown) makes layer 1 (L1) RSRP measurements for a set of beams (e.g., beams 1-8) over time (e.g., periodically) and reports the RSRP measurements 802 to a network entity 804 (such as a gNB). The RSRP measurements 802 are input to a machine learning (ML) model 806. The ML model 806 provides an output that predicts beam failure or blockage for each beam in the set of beams. In some aspects, use of such a beam failure prediction process may provide at least one of: a reduction in UE power, a reduction in UE-specific reference signal overhead, an improvement in latency, or an improvement in throughput compared to other beam failure prediction schemes.

[0130] Fig. 9 9 is a conceptual illustration of an example of beam failure detection operations 900 according to some aspects. In this example, there are two beam resources, beam failure detection reference signal (BFD-RS) resource #0 and BFD-RS resource 1. These beam resources may carry periodic CSI-RS (P-CSI-RS) signaling, SSB signaling, or some other type of signaling.

[0131] At a first operation 902, a UE (not shown) performs a PDCCH block error rate (BLER) calculation for each beam resource. In some examples, the calculation of the BLER involves measuring the RSRP of the received beam and mapping the RSRP value to the BLER value (e.g., based on a table that maps different RSRP values ​​to different BLER values).

[0132] At a second operation 904, if the PDCCH BLER calculated for each beam resource is greater than the target BLER threshold, the beam failure instance counter is incremented. At a third operation 906, if the beam failure instance counter reaches a maximum count (e.g., as defined by a parameter beamFailureInstanceMaxCount) within a defined time period (e.g., as defined by a parameter beamFailureDetectionTimer), the UE sends a beam failure request (BFRQ).

[0133] As described above, the UE may perform signal measurements (such as RSRP measurements and / or received signal strength indication (RSSI) measurements) in conjunction with beam management operations. In the event that a beam is blocked (e.g., due to a pedestrian, vehicle, or some other object), there may be a drop in the measured RSSI or RSRP. The link degradation time may be defined as the time it takes for the RSSI or RSRP to drop from its steady-state value to its minimum value or link loss (whichever arrives sooner). In some examples, RSSI or RSRP degradation due to blockage may result in a relatively slow time scale of change (e.g., it may take several 100ms for the RSSI to drop significantly). In some examples, body blockage measurements (e.g., in the event that a person walks very close to the transmitter and / or receiver) may cause losses (diffraction losses) of approximately 0.4 dB / ms. In some aspects, the present disclosure relates to predicting these and other types of blockages and modifying beam failure operations based on these predictions.

[0134] In one example of BFD-RS configuration, for a specific BWP within a specific serving cell, the reference signal (RS) used to detect beam failure is configured to be BWP-specific via the radioLinkMonitoringConfig parameter, which includes a failureDetectionResourcesToAddModList parameter that includes a set of up to two periodic CSI-RS or SSB resource indices. In some examples, the UE expects the set Includes at most two single-port CSI-RS / SSB resources. In some examples, the UE only expects periodic CSI-RS resources or SSBs. In some examples, if the RS is CSI-RS, the UE only expects a single port.

[0135] If the failureDetectionResourcesToAddModList parameter is not configured, the UE may instead set The P-CSI-RS resource index indicated by the transmission configuration indication (TCI) state (TCI-State) of the corresponding CORESET for the UE to monitor the PDCCH is determined. In some examples, if there are two RS indices in the TCI state, the set The RS index is configured with a qcl-Type that is set to TypeD for the corresponding TCI state. In some examples, the UE expects the set Includes up to two single-port CSI-RS / SSB resources. In some examples, the set Only a single-port CSI-RS in is expected by the UE.

[0136] As above combined Fig. 9 As discussed, for beam failure detection, the UE may monitor the BFD-RS to determine if a beam failure trigger condition is met. At L1, this may involve checking if the PDCCH BLER meets the target BLER level for all beam detection RSs. If so, the L1 process may notify the L2 process about the beam failure instance of the serving cell. In addition, if the L2 process receives a certain number of beam failure instances (e.g., beamFailureInstanceMaxCount parameter configured by RRC) from the L1 process within a certain duration (e.g., beamFailureDetectionTimer parameter configured by RRC), it may trigger the BFRQ transmission.

[0137] In some scenarios, of the BFD-RS resources configured by two network entities, only one of them may be predicted to be blocked. In this case, the network entity may fully or partially suspend the BFD-RS resource. In some examples, the prediction may also specify the duration of the blockage.

[0138] If the certainty level of the prediction (e.g., generated by the ML model) is high, the network entity may request the UE to completely suspend monitoring of the BFD-RS resources predicted to be blocked during the predicted blocking duration. Otherwise, depending on the certainty level associated with the prediction, the network entity may alternatively request the UE to reduce the monitoring frequency (e.g., partially suspend) of the BFD-RS resources predicted to be blocked during the predicted blocking duration.

[0139] In some aspects, the present disclosure relates to adjusting the criteria for determining whether a BFRQ should be sent depending on the detailed suspension of a BFD-RS resource predicted to be blocked. For example, if a first BFD-RS resource is completely suspended, determining whether a BFRQ should be sent may depend solely on the identified PDCCH hypothetical BLER associated with the other remaining BFD-RS. However, if one of the BFD-RS is predicted to be blocked but predicted to be restored soon, the criteria for triggering BFRQ based on the remaining BFD-RS may be more stringent (compared to a complete blocking scenario) because the resources used to send the BFRQ (e.g., contention-free random access (CFRA) resources) may be important (e.g., relatively scarce) resources for the network entity. Here, given that the blocked beam may be restored soon, the free transmission of the BFRQ may be considered undesirable (e.g., a waste of important resources).

[0140] Fig.101000 is a conceptual illustration of an example of a predicted blocking window and a pause condition 1000 according to some aspects. In this example, a predicted blocking window 1002 may be defined for a fully paused BFD-RS resource condition 1004 or for a partially paused BFD-RS resource condition 1006. In the fully paused BFD-RS resource condition 1004, all instances of BFD-RS #0 are completely blocked during the predicted blocking window 1002 (e.g., Fig.10 In the partially paused BFD-RS resource condition 1006, only some instances of BFD-RS #0 are blocked during the predicted blocking window 1002 (e.g., Fig.10 In accordance with the teachings herein, different BFRQ transmission trigger parameters may be defined for these scenarios (eg, different parameters than those used for scenarios in which there is no pause).

[0141] In some aspects, the disclosure relates to signaling enhancements for indicating fully or partially suspended BFD-RS resources and associated suspension behaviors. In some aspects, the disclosure relates to different examples of beam failure triggering conditions that consider full or partial suspension of such BFD-RS resources.

[0142] In some aspects, the present disclosure relates to the suspension of a single BFD-RS (e.g., for partial beam blocking). The network entity instructs the UE to suspend determination of a PDCCH hypothesized BLER for a first BFD-RS resource (e.g., BFD-RS resource #0) among a plurality of configured BFD-RS resources. The indication of the suspension may also include a time window for the UE to apply the suspension. The indication of the suspension may include a certainty level (e.g., in %) associated with the suspension. In this case, the UE completely suspends (or partially suspends) determination of the PDCCH hypothesized BLER for the first BFD-RS resource during the time window indicated by the network entity. Such a suspension command may be signaled to the UE from the network entity via MAC-CE signaling, DCI signaling, or some other type of signaling.

[0143] In some aspects, the present disclosure relates to certain conditions to be applied to a full BFD-RS suspension compared to a partial BFD-RS suspension. In some examples, based on a level of certainty indicated by a network entity being above a first threshold, the UE will fully suspend a first BFD-RS resource relative to determining a PDCCH hypothetical BLER. In some examples, based on a level of certainty indicated by the network entity being below a second threshold, the UE will partially suspend the first BFD-RS resource relative to determining a PDCCH hypothetical BLER (e.g., determine the PDCCH BLER less frequently). The first threshold and the second threshold may be the same or different. The first threshold and the second threshold may be predefined based on a standard (e.g., defined by a wireless communication standard such as a 3GPP technical specification) and / or configured by a network entity.

[0144] In some examples, the network entity directly indicates to the UE whether the pause is a full pause or a partial pause. For example, the network entity may compare the level of certainty with at least one threshold to determine whether the pause is a full pause or a partial pause. In this case, the UE does not need to compare the level of certainty with any threshold.

[0145] Fig.11 is a diagram illustrating example suspension operations 1100 in accordance with some aspects. At block 1102, a network entity (such as a gNB) transmits to a UE an indication of full or partial suspension of a first BFD-RS resource (e.g., BFD-RS resource #0) in a set of BFD-RS resources used by the network entity. As represented by block 1104, the indication may indicate a suspension window. As represented by block 1106, the indication may indicate an uncertainty level (e.g., a type of certainty level) of beam blocking (e.g., as indicated by Figure 8 At block 1108, the UE fully or partially suspends the first BFD-RS resource based on the indication.

[0146] In some aspects, the present disclosure relates to a beam failure trigger condition for a complete suspension of a first BFD-RS resource (e.g., for BFD-RS#0). In one example (Example 1, Option 1), once the first BFD-RS resource is completely suspended, a different set of beam failure trigger parameters may be used for other BFD-RS resources.

[0147] For example, a second beam failure trigger condition is used at layer 1 for all PDCCHs assuming BLER associated with any other BFD-RS resource other than the first BFD-RS resource. In some aspects, this second beam failure trigger condition is different from a conventional beam failure trigger condition associated with all configured BFD-RS resources (including the first BFD-RS resource). In this case, once layer 2 receives a specific number of beam failure instances associated with the second beam failure condition within a specific duration, it triggers BFRQ transmission.

[0148] In some examples, such BFRQ may be sent via different UL resources than the UL resources used to send a regular BFRQ associated with all configured BFD-RS resources (including the first BFD-RS resource). For example, a random access channel (RACH) resource different from the RACH resource associated with the regular BFRQ is configured to send such BFRQ (e.g., for the primary cell (PCell)). As another example, for reporting beam failure for a secondary cell (SCell), a different MAC-CE may be used to convey the BFRQ for a suspension scenario compared to the MAC-CE used for a regular BFRQ report (e.g., a non-pause scenario).

[0149] In some examples, the number of beam failure instances specified for the second beam failure trigger condition (e.g., pause scenario) may be different from the number of beam failure instances specified for the first beam failure trigger condition (e.g., non-pause scenario) associated with all configured BFD-RS resources (including the first BFD-RS resource). For example, a beamFailureInstanceMaxCount_Blockage parameter that is different from the conventional RRC configured beamFailureInstanceMaxCount may be an RRC configured for beam failure detection during such a beam blocking period.

[0150] In some examples, the blocking duration specified for the second beam failure trigger condition (e.g., pause scenario) may be a different duration than the duration conventionally configured for all BFD-RS resources (including the first BFD-RS resource). For example, a beamFailureDetectionTimer_Blockage parameter different from the conventional RRC configured beamFailureDetectionTimer may be RRC configured for beam failure detection during such a beam blocking period.

[0151] In some examples, parameters for the second beam failure trigger condition (e.g., a pause scenario) may be defined to reduce the likelihood or frequency of BFRQ transmissions. For example, the beamFailureInstanceMaxCount_Blockage parameter may be greater than the beamFailureInstanceMaxCount parameter. As another example, the beamFailureDetectionTimer_Blockage parameter may be shorter than the beamFailureDetectionTimer parameter. Here, since the prediction indicates that the blocking will likely only occur within a specific duration, it may be desirable to reduce the processing and signaling associated with BFRQ transmissions (and potential beam recovery operations). Therefore, in this case, the network entity may define these parameters to reduce the likelihood that the UE will transmit a BFRQ.

[0152] Fig.12 1 is a diagram illustrating an example (Example 1, Option 1) of beam failure triggering operation 1200 according to some aspects. In this example, a predicted blocking window is indicated for a first BFD-RS resource in a set of BFD-RS resources, where the corresponding suspension is a complete BFD-RS suspension. At block 1202, different BFRQ transmission criteria (e.g., different trigger parameters) may be selected for the scenario. As represented by block 1204, different UL resources may be used to send the BFRQ compared to the UL resources used for conventional (e.g., non-suspended scenario) beam failure reporting. For example, different RACH resources may be used to report Pcell (block 1206) beam blocking, or different MAC-CEs may be used to report SCell (block 1208) beam blocking. As represented by block 1210, different beam failure instance thresholds may be used to determine whether to send the BFRQ compared to the beam failure instance thresholds used for conventional (e.g., non-suspended scenario) beam failure reporting. As represented by block 1212, a different duration threshold may be used to determine whether to send a BFRQ than the duration threshold used for conventional (eg, non-pause scenario) beam failure reporting.

[0153] In another example (Example 1, Option 2), once the first BFD-RS resource is completely suspended, the factor can be applied to the beam failure trigger parameter set to be used for other BFD-RS resources. In this way, different effective beam failure trigger parameters will be used for other BFD-RS resources (e.g., to reduce the possibility of BFRQ transmission).

[0154] For example, when each PDCCH assumption BLER associated with any other BFD-RS resource other than the first BFD-RS resource satisfies the BLER threshold, a second beam failure trigger condition (which is different from the beam failure trigger condition associated with all configured BFD-RS resources including the first BFD-RS resource) is deemed to be satisfied by a factor at layer 1 (e.g., having a value less than 1). In this case, once layer 2 receives a specific number of beam failure instances associated with the second condition within a specific duration, the layer triggers BFRQ transmission.

[0155] In some examples, the factor may be predefined based on a standard. In some examples, a network entity may configure or indicate the factor to the UE. For example, a wireless communication standard (e.g., a 3GPP technical specification) or a network entity may define an association between a factor and a time window relative to the suspension of the first BFD-RS. Here, a longer duration may result in a larger factor (because the remaining BFD-RS becomes more vulnerable). As another example, a standard or a network entity may define an association between a factor and a level of certainty associated with the blocking of the first BFD-RS. In some examples, a standard or a network entity may define an association between a factor and a window (e.g., beamFailureDetectionTimer) for counting PDCCH BLER. In some examples, the factor may be indicated together with an indication of a BFD-RS resource suspension regarding a first BFD-RS resource.

[0156] In this example, the RACH resources, thresholds on the number of beam failures, duration of counting, etc. may all be based on the same RRC configured parameters (e.g., parameters associated with the conventional beam failure detection process such as beamFailureInstanceMaxCount and beamFailureDetectionTimer.) Therefore, no suspension-specific versions of these parameters are required in this case, which may reduce signaling overhead.

[0157] Fig.131 is a diagram illustrating an example (Example 1, Option 2) of beam failure triggering operation 1300 according to some aspects. In this example, a predicted blocking window is indicated for a first BFD-RS resource in a set of BFD-RS resources, where the corresponding pause is a full BFD-RS pause. At block 1302, conventional BFRQ transmission trigger parameters (e.g., beamFailureInstanceMaxCount and beamFailureDetectionTimer) may be used in this example. As represented by block 1404, a factor may be applied to the number of beam failure instances (e.g., thereby reducing the count compared to a conventional count threshold). As represented by block 1406, in some examples, the network entity may signal the factor to the UE. As represented by block 1408, in some examples, the factor may be defined by a wireless communication standard (e.g., 3GPP). As represented by block 1310, in some examples, the factor may be associated with a pause time window. As represented by block 1312, in some examples, the factor may be associated with a blocking certainty level.

[0158] In some aspects, the present disclosure relates to a beam failure trigger condition for a partial suspension of a BFD-RS resource (e.g., a first BFD-RS resource). For predicted blocking with a medium-low certainty level about the first BFD-RS resource, the method introduced in Example 1 (options 1 and 2) may result in an unfairly declared beam failure. This is because the first BFD-RS may not have failed, but the UE did not measure the first BFD-RS resource because the UE assumes that during the time window, the PDCCH BLER check for the first BFD-RS resource will always fail.

[0159] In one example (Example 2.1), during a time window associated with a suspension indicated by a network entity, the UE reduces the PDCCH BLER calculation frequency of the first BFD-RS by a factor K (e.g., K is an integer). In some examples, the value of K can be a predefined standard associated with different certainty levels, or indicated by the network entity together with the first BFD-RS suspension command.

[0160] In some examples, assume that for non-measurement occasions, the PDCCH BLER calculation of the first BFD-RS fails (eg, is greater than a BLER threshold). Conventional beam failure operations (eg, as defined by 3GPP Release 17, etc.) may then be used for the remaining beam failure operations.

[0161] Fig.14is a diagram illustrating an example (Example 2.1) of beam failure triggering operations 1400 according to some aspects. In this example, a predicted blocking window is indicated for a first BFD-RS resource in a set of BFD-RS resources, where the corresponding pause is a partial BFD-RS pause. At block 1402, the PDCCH calculation frequency is reduced by a factor K. At block 1404, it is assumed that non-measurement occasions (e.g., the first, second, fourth, fifth, seventh, and eighth occasions in the window) fail. At block 1406, conventional BFRQ transmission criteria (e.g., as defined in 3GPP Release 17) are followed.

[0162] In another example (Example 2.2), the BFRQ triggering condition of Example 1, Option 1 may be applied to BFD-RSs other than the first BFD-RS. In some aspects, two BFD-RSs are considered independently in this example.

[0163] For example, if the number of beam failure instances has reached a threshold for layer 2 to trigger a BFRQ for other BFD-RS (non-blocked beams), the UE may further evaluate the number of instances in which the PDCCH assumption BLER satisfies the corresponding BLER threshold associated with the measurement instance for the first BFD-RS. If this number relative to the first BFD-RS is below a certain threshold (e.g., beamFailureInstanceMaxCount_Suspension) within a certain window (e.g., beamFailureDecetectionTimer Suspension), then the BFRQ is not sent. Otherwise, the BFRQ is sent.

[0164] Here, the threshold value (e.g., beamFailureInstanceMaxCount_Suspension) relative to the first BFD-RS may be different from the threshold value (e.g., beamFailureInstanceMaxCount_Blockage) introduced in Option 1 relative to Example 1 and / or different from the conventional threshold value (e.g., beamFailureInstanceMaxCount) used to determine whether to perform BFRQ transmission. The threshold value may be predefined based on the standard and / or RRC configuration.

[0165] Fig.15is a diagram illustrating an example (Example 2.2) of beam failure triggering operation 1500 according to some aspects. In this example, a predicted blocking window is indicated for a first BFD-RS resource in a set of BFD-RS resources, where the corresponding pause is a partial BFD-RS pause. At block 1502, a BFRQ triggering condition is evaluated according to Example 1, Option 1 discussed above. At block 1504, a determination is made as to whether a BFRQ should be triggered based on the evaluation of block 1502. If so, at block 1506, a determination is made as to whether a beam failure instance count for the first BFD-RS resource has reached a beam failure instance threshold. If so, a BFRQ is sent (block 1508). If not, a BFRQ is not sent (block 1510).

[0166] In some aspects, the present disclosure relates to extensions to more than two BFD-RS resources (e.g., in future releases, more than two BFD-RS resources may be configured to determine whether a BFRQ should be sent). The UE may be instructed by a network entity to fully or partially suspend multiple BFD-RS resources for determining the PDCCH hypothetical BLER, as in the previous example.

[0167] For an extension to Example 1, Option 1 (all suspended BFD-RS resources are fully suspended), the configured parameters for determining whether to perform BFRQ transmission based on the remaining non-suspended BFD-RS resources may be configured differently for different numbers of suspended BFD-RS resources. For example, in the case where more BFD-RS resources are fully suspended, the associated threshold for the number of beam failure instances that will trigger BFRQ transmission may be lower or higher.

[0168] As an extension to Example 1, Option 2 (all suspended BFD-RS resources are completely suspended), different factors may be predefined by the standard or configured by the network entity for different numbers of suspended BFD-RS resources.

[0169] For an extension to Example 2 (at least one of the suspended BFD-RS resources is partially suspended), the configured parameters for determining whether to perform BFRQ transmission based on the remaining non-suspended BFD-RS resources and the partially suspended BFD-RS resources can be configured differently for the number of fully and partially suspended BFD-RS and the applicable certainty level.

[0170] Fig.16The present invention is a conceptual illustration of an example 1600 for conditions of different parameters according to some aspects. Here, the different parameters in Example 1 and Example 2 can be standard predefined or network entity configured, depending on the number of BFD-RS resources that are fully and / or partially suspended. For example, a first parameter set can be used for a first scenario 1602 in which a single BFD-RS resource is suspended. In contrast, a second parameter set can be used for a second scenario 1604 in which multiple BFD-RS resources are suspended. In addition, a third parameter set can be used for a third scenario 1606 in which at least one BFD-RS resource is partially suspended.

[0171] Fig.17 1700 is a signaling diagram illustrating an example of a wireless communication system including a network entity 1702 and a user equipment 1704. In some examples, the network entity 1702 may correspond to Figure 1 , Figure 2 , Figure 3 , Figure 5 , Figure 6 , Figure 7 , Figure 8 and Fig. 20 In some examples, the user equipment 1704 may correspond to any of the base stations, CUs, DUs, RUs, or scheduling entities shown in any of the examples. Figure 1 , Figure 2 , Figure 3 , Figure 5 , Figure 6 , Figure 7 , Figure 8 and Fig.18 Any of the UEs or scheduled entities shown in any of the .

[0172] exist Fig.17 At #1706 of , network entity 1702 transmits beam failure reporting parameters to user equipment 1706 (e.g., via RRC signaling or some other type of signaling). In some examples, the beam failure reporting parameters may include a first set of parameters (e.g., to be used for conventional beam failure reporting operations) and a second set of parameters (e.g., to be used for beam failure reporting operations in a scenario where at least one beam resource is indicated as at least partially suspended). In some examples, the parameters may include at least one threshold to be compared with a certainty level. In some examples, the parameters may include at least one counting threshold. In some examples, the parameters may include at least one duration threshold. In some examples, the parameters may indicate at least one UL resource for sending a BFRQ.

[0173] At #1708, the network entity 1702 transmits a reference signal to the user equipment 1706. In some examples, the reference signal may include periodic SSB signaling and / or periodic CSI-RS signaling.

[0174] At #1710, the user equipment 1704 transmits measurement information to the network entity 1702. For example, in conjunction with beam management operations, the user equipment 1704 may measure the RSRP of the received SSB signaling and / or CSI-RS signaling and report the information to the network entity 1702.

[0175] At #1712, the network entity 1702 determines whether to at least partially suspend the beam resource (e.g., whether to at least partially suspend the beam failure operation for the beam resource). For example, based on the measurement information received at #1710, the network entity 1702 may predict that beam blocking will occur on the first beam resource in the set of beam resources used by the network entity 1702 for a specific period of time.

[0176] Thus, at #1714, network entity 1702 may transmit beam pause information to user equipment 1704. In some examples, the beam pause information may include a certainty level. In some examples, the beam pause information may include at least one threshold to be compared to the certainty level. In some examples, the beam pause information may include an indication of whether the first beam resource will be partially paused or fully paused.

[0177] At #1716, the user equipment 1704 may determine whether to suspend the beam failure operation on the first beam resource indicated by the beam suspension information. For example, based on the beam suspension information received at #1714, the user equipment 1704 may determine whether to completely suspend or partially suspend the PUCCH BLER calculation for the first beam resource (e.g., BFD-RS#0).

[0178] At #1718, the user equipment 1704 may determine whether to send a BFRQ based on a measurement of a second beam resource (e.g., BFD-RS #1) in the set of beam resources in addition to the first beam resource. As discussed herein, the determination may be based on a second set of parameters (e.g., defined for a beam failure reporting operation in a scenario where at least one beam resource is indicated as at least partially suspended).

[0179] At #1720, depending on the result of the determination of #1718, the user equipment 1704 may transmit a BFRQ to the network entity 1702.

[0180] Fig.18 18 is a block diagram illustrating an example of a hardware implementation of an apparatus 1800 employing a processing system 1814. For example, the apparatus 1800 may be a device configured to communicate wirelessly in a network, such as Figures 1 to 17 In some implementations, the device 1800 may correspond to Figure 1 , Figure 2 , Figure 3 , Figure 5 , Figure 6 , Figure 7 , Figure 8 and Fig.17 Any one of the UEs or scheduled entities shown in any one of .

[0181] According to various aspects of the present disclosure, any combination of elements or any part of elements or elements can be implemented using processing system 1814. Processing system 1814 may include one or more processors 1804. Examples of processor 1804 include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. In various examples, device 1800 may be configured to perform any one or more of the functions described herein. That is, processor 1804 as utilized in device 1800 may be used to implement any one or more of the processes and procedures described herein.

[0182] In this example, the processing system 1814 may be implemented using a bus architecture (generally represented by bus 1802). The bus 1802 may include any number of interconnecting buses and bridges, depending on the specific application of the processing system 1814 and the overall design constraints. The bus 1802 communicatively couples various circuits including one or more processors (generally represented by processor 1804), memory 1805, and computer-readable media (generally represented by computer-readable media 1806). The bus 1802 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. The bus interface 1808 provides an interface between the bus 1802, the transceiver 1810, and the antenna array 1820, and between the bus 1802 and the interface 1830. The transceiver 1810 provides a communication interface or component for communicating with various other devices over a wireless transmission medium. Interface 1830 provides a communication interface or component for communicating with various other devices and equipment (e.g., other devices contained in the same device as device 1800 or other external devices) through an internal bus or an external transmission medium (such as an Ethernet cable). Depending on the nature of the device, interface 1830 may include a user interface (e.g., a keypad, display, speaker, microphone, joystick). Of course, such a user interface is optional and may be omitted in some examples (such as IoT devices).

[0183] The processor 1804 is responsible for managing the bus 1802 and general processing, including executing software stored on the computer-readable medium 1806. The software, when executed by the processor 1804, causes the processing system 1814 to perform various functions described below for any particular device. The computer-readable medium 1806 and the memory 1805 can also be used to store data manipulated by the processor 1804 when executing the software. For example, the memory 1805 can store beam resource information 1815 (e.g., indicating BFD-RS resources) used by the processor 1804 for communication operations described herein.

[0184] One or more processors 1804 in the processing system can execute software. Software should 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, executable files, threads of execution, processes, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. The software may reside on a computer-readable medium 1806.

[0185] Computer readable medium 1806 can be a non-transient computer readable medium. Non-transient computer readable media include, for example, 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., cards, sticks 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 1806 can reside in processing system 1814, be located outside processing system 1814, or be distributed across multiple entities including processing system 1814. Computer readable medium 1806 can be embodied in a computer program product. For example, a computer program product can include a computer readable medium in a packaging material. 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.

[0186] The apparatus 1800 may be configured to perform any one or more of the operations described herein (e.g., as described above in conjunction with Figures 1 to 17 As described and as follows Fig.19 In some aspects of the present disclosure, a processor 1804 as utilized in apparatus 1800 may include circuits configured for various functions.

[0187] Processor 1804 may be configured to generate, schedule, and modify resource assignments or grants of time-frequency resources (e.g., a set of one or more resource elements). For example, processor 1804 may schedule time-frequency resources within multiple time division duplex (TDD) and / or frequency division duplex (FDD) subframes, time slots, and / or mini-slots to carry user data traffic and / or control information to and / or from multiple scheduled entities. Processor 1804 may be configured to schedule resources for transmission of downlink signals. Processor 1804 may be further configured to schedule resources for transmission of uplink signals.

[0188] In some aspects of the present disclosure, the processor 1804 may include a communication and processing circuit 1841. The communication and processing circuit 1841 may be configured to communicate with user equipment. The communication and processing circuit 1841 may include one or more hardware components that provide a physical structure that performs various processes related to communication (e.g., signal reception and / or signal transmission) as described herein. The communication and processing circuit 1841 may also include one or more hardware components that provide a physical structure that performs various processes related to signal processing (e.g., processing received signals and / or processing signals for transmission) as described herein. The communication and processing circuit 1841 may be further configured to execute communication and processing software 1851 included on the computer-readable medium 1806 to implement one or more functions described herein.

[0189] The communication and processing circuit 1841 may be further configured to receive an indication from the UE. For example, the indication may be included in a MAC-CE carried in a Uu PUSCH or PSCCH, or in a Uu RRC message or SL RRC message, or in a dedicated Uu PUCCH or PUSCH. The communication and processing circuit 1841 may be further configured to receive a scheduling request for an uplink grant or a sidelink grant from the UE.

[0190] In some implementations where communication involves receiving information, the communication and processing circuitry 1841 may obtain information from a component of the device 1800 (e.g., from a transceiver 1810 that receives information via radio frequency signaling or some other type of signaling suitable for an applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, the communication and processing circuitry 1841 may output the information to another component of the processor 1804, to the memory 1805, or to the bus interface 1808. In some examples, the communication and processing circuitry 1841 may receive one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 1841 may receive information via one or more channels. In some examples, the communication and processing circuitry 1841 may receive one or more of a signal, a message, SCI, feedback, other information, or any combination thereof. In some examples, the communication and processing circuitry 1841 may receive information via one or more of a PSCCH, a PSSCH, a PSFCH, some other type of channel, or any combination thereof. In some examples, the communication and processing circuitry 1841 and / or the transceiver 1810 may include functionality for components for receiving. In some examples, the communication and processing circuitry 1841 may include functionality for components for decoding. In some examples, the communication and processing circuitry 1841 may include functionality for components for receiving information from a network entity.

[0191] In some implementations where communication involves transmitting (e.g., sending) information, the communication and processing circuit 1841 may obtain information (e.g., from another component of the processor 1804, the memory 1805, or the bus interface 1808), process (e.g., encode) the information, and output the processed information. For example, the communication and processing circuit 1841 may output the information to the transceiver 1810 (e.g., it sends 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 circuit 1841 may transmit one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuit 1841 may transmit information via one or more channels. In some examples, the communication and processing circuit 1841 may transmit one or more of a signal, a message, SCI, feedback, other information, or any combination thereof. In some examples, the communication and processing circuit 1841 may transmit information via one or more of a PSCCH, a PSSCH, a PSFCH, some other type of channel, or any combination thereof. In some examples, the communication and processing circuitry 1841 and / or the transceiver 1810 may include functionality for components for transmitting. In some examples, the communication and processing circuitry 1841 may include functionality for components for encoding. In some examples, the communication and processing circuitry 1841 may include functionality for components for sending signal measurement information to a network entity.

[0192] Processor 1804 may include a processor configured to perform pause-related operations as discussed herein (e.g., as described below in conjunction with Figures 8 to 17 The suspend circuit 1842 may be configured to execute suspend software 1852 included on the computer readable medium 1806 to implement one or more functions described herein.

[0193] The pause circuit 1842 may include functionality for components for obtaining information (e.g., as described above in conjunction with Figures 8 to 17 As described above). For example, the suspension circuit 1842 may receive a MAC-CE or DCI including information indicating whether the beam failure operation is to be suspended from the network entity. As another example, the suspension circuit 1842 may receive at least one beam failure reporting parameter from the network entity. As another example, the suspension circuit 1842 may receive a suspension parameter from the network entity.

[0194] The pause circuit 1842 may include functionality for components for at least partially suspending beam failure operations (e.g., as described above in conjunction with Figures 8 to 17For example, the suspend circuit 1842 may determine whether the PDCCH BLER operation is to be partially suspended or fully suspended based on the received information (and optionally, a comparison with a threshold). The suspend circuit 1842 may then partially suspend or fully suspend the PDCCH BLER operation accordingly (e.g., for a specified time duration).

[0195] The pause circuit 1842 may include the functionality of a component for comparing the certainty level to at least one threshold value (e.g., as described above in conjunction with Figures 8 to 17 For example, the pause circuit 1842 may compare the certainty level received from the network entity with a first threshold or with a first threshold and a second threshold.

[0196] The pause circuit 1842 may include functionality for components used to achieve a certainty level (e.g., as described above in conjunction with Figures 8 to 17 For example, the pause circuit 1842 may receive a MAC-CE or DCI including a level of certainty from a network entity.

[0197] The pause circuit 1842 may include functionality of a component for obtaining at least one threshold value (e.g., as described above in conjunction with Figures 8 to 17 For example, the pause circuit 1842 may receive a MAC-CE or DCI including at least one threshold from a network entity.

[0198] Processor 1804 may include beam failure circuitry 1843 configured to perform beam failure related operations as discussed herein (e.g., as described above in connection with Figures 8 to 17 The beam failure circuit 1843 may be configured to execute the beam failure software 1853 included on the computer readable medium 1806 to implement one or more functions described herein.

[0199] The beam failure circuit 1843 may include functionality for components for performing beam failure operations (e.g., as described above in conjunction with Figures 8 to 17 For example, the beam failure circuit 1843 may perform a PDCCH BLER operation to determine whether a beam failure instance has occurred. As another example, the beam failure circuit 1843 may determine whether a threshold number of beam failure instances have occurred during a defined time period.

[0200] The beam failure circuit 1843 may include functionality for components for outputting a beam failure request message (e.g., as described above in conjunction with Figures 8 to 17 For example, in the event that a threshold number of beam failure instances have occurred during a defined time period, the beam failure circuit 1843 may transmit a BFRQ to the network entity.

[0201] Fig.19 1900 is a flowchart illustrating an example method 1900 for communication according to some aspects of the present disclosure. 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 for all example implementations. In some examples, the method 1900 may be performed by Fig.18 The illustrated device 1800 performs. In some examples, the method 1900 can be performed by any suitable device or component for performing the functions or algorithms described below.

[0202] At block 1902, a first device may obtain first information from a second device indicating whether the first device will suspend beam failure operations for at least one first beam resource of a plurality of beam resources associated with the second device. Fig.18 The pause circuit 1842 shown and described in the embodiment of the present invention may provide a component for obtaining first information from a second device, the first information indicating whether the first device is to suspend beam failure operations for at least one first beam resource of a plurality of beam resources associated with the second device. In some examples, Fig.18 The pause circuit 1842 shown and described in conjunction with the communication and processing circuit 1841 and the transceiver 1810 may provide a means for obtaining first information from a second device, the first information indicating whether the first device will suspend beam failure operations for at least one first beam resource of a plurality of beam resources associated with the second device. In some examples, Fig.18 The communication and processing circuit 1841 and / or transceiver 1810 shown and described may provide a component for obtaining first information from a second device, the first information indicating whether the first device will suspend beam failure operation for at least one first beam resource of a plurality of beam resources associated with the second device.

[0203] At block 1904, the first device may at least partially suspend beam failure operations for at least one first beam resource based on the first information. Fig.18 The pause circuit 1842 shown and described in the accompanying drawings may provide means for at least partially suspending beam failure operations for at least one first beam resource based on the first information.

[0204] In some examples, the beam failure operation can include determining a block error rate associated with a physical downlink control channel. In some examples, the at least partial suspension of the beam failure operation can include a partial suspension or a complete suspension of the beam failure operation.

[0205] In some examples, the first information indicates a suspension period for which the beam failure operation will be at least partially suspended. In some examples, the at least partial suspension of the beam failure operation is maintained for the suspension period.

[0206] In some examples, the first information can include a certainty level indicating whether the beam failure operation is to be at least partially suspended. In some examples, the at least partial suspension of the beam failure operation is based on the certainty level.

[0207] In some examples, the first information specifies whether the beam failure operation is to be fully suspended or partially suspended. In some examples, the at least partial suspension of the beam failure operation may include partially suspending or fully suspending the beam failure operation based on the first information.

[0208] In some examples, the first information may include a certainty level indicating whether the beam failure operation is to be at least partially suspended. In some examples, the first device may compare the certainty level to at least one threshold. In some examples, the at least partial suspension of the beam failure operation is based on the comparison of the certainty level to the at least one threshold.

[0209] In some examples, the first device may obtain the at least one threshold from the second device. In some examples, the at least one threshold is specified by a wireless communication standard.

[0210] In some examples, the first information may include a certainty level indicating whether the beam failure operation will be at least partially suspended. In some examples, the first device may compare the certainty level with a first threshold. In some examples, the first device may conditionally fully suspend the beam failure operation based on the comparison of the certainty level with the first threshold. In some examples, the at least partial suspension of the beam failure operation may include a full suspension based on the comparison of the certainty level with the first threshold. In some examples, the first device may compare the certainty level with a second threshold. In some examples, the first device may conditionally partially suspend the beam failure operation based on the comparison of the certainty level with the second threshold. In some examples, the at least partial suspension of the beam failure operation may include a partial suspension based on the comparison of the certainty level with the second threshold.

[0211] In some examples, the first device may obtain at least one first beam failure reporting parameter to be used for at least one second beam resource among the multiple beam resources when the at least one first beam resource is indicated as completely paused. In some examples, the first device may output a first beam failure request message associated with the at least one second beam resource based on the at least one first beam failure reporting parameter for sending to the second device.

[0212] In some examples, the first beam failure request message is output for transmission via a first uplink resource. In some examples, the first uplink resource is different from a second uplink resource used to output a second beam failure request message associated with no beam resource in the plurality of beam resources being indicated as completely suspended. In some examples, the first uplink resource is different from a second uplink resource configured for a second beam failure request message associated with no beam resource in the plurality of beam resources being indicated as completely suspended.

[0213] In some examples, the at least one first beam failure reporting parameter specifies a first threshold number of beam failure instances. In some examples, the output of the first beam failure request message for transmission is based at least in part on whether the number of beam failure instances associated with the at least one second beam resource exceeds the first threshold number of beam failure instances. In some examples, the first threshold number of beam failure instances is different from a second threshold number of beam failure instances associated with no beam resource in the plurality of beam resources being indicated as fully suspended.

[0214] In some examples, the at least one first beam failure reporting parameter specifies a first pause period. In some examples, the output of the first beam failure request message for transmission is based at least in part on whether a certain number of beam failure instances associated with the at least one second beam resource occurred during the first pause period. In some examples, the first pause period is different from a second pause period associated with no beam resource in the plurality of beam resources being indicated as fully paused.

[0215] In some examples, the at least one first beam failure reporting parameter may include at least one factor to be applied to at least one second beam failure reporting parameter associated with no beam resource in the plurality of beam resources being indicated as fully paused. In some examples, the at least one factor may include at least one of: a first factor associated with a threshold number of beam failure instances, a second factor associated with a pause period, or a third factor associated with a certainty level.

[0216] In some examples, at least partially suspending the beam failure operation may include partially suspending the beam failure operation according to a suspension parameter. In some examples, the partially suspending the beam failure operation may include reducing the frequency of calculating a block error rate associated with a physical downlink control channel. In some examples, the suspension parameter is based on a certainty level. In some examples, the first device may obtain the suspension parameter from the second device. In some examples, the suspension parameter is specified by a wireless communication standard.

[0217] In some examples, the first device may obtain at least one first beam failure reporting parameter to be used for at least one second beam resource among the multiple beam resources when the at least one first beam resource is indicated as partially suspended. In some examples, the first device may output a first beam failure request message associated with the at least one second beam resource based on the at least one first beam failure reporting parameter for sending to the second device.

[0218] In some examples, the first device may obtain at least one second beam failure reporting parameter associated with no beam resource in the plurality of beam resources being indicated as partially paused. In some examples, the at least one second beam failure reporting parameter is different from the at least one first beam failure reporting parameter.

[0219] In some examples, the at least one first beam resource may include a plurality of beam resources. In some examples, the first device may obtain at least one first beam failure reporting parameter to be used for at least one second beam resource in the plurality of beam resources. In some examples, the at least one first beam failure reporting parameter is based on how many beam resources in the plurality of beam resources are indicated as at least partially suspended.

[0220] In some examples, the first device includes a receiver configured to receive the first information, wherein the first device is configured as user equipment.

[0221] Refer again Fig.18 In one configuration, the apparatus 1800 includes: a component for receiving first information from a network entity, the first information indicating whether a user equipment will suspend beam failure operation for at least one first beam resource of a plurality of beam resources associated with the network entity; and a component for at least partially suspending beam failure operation for at least one first beam resource based on the first information. In one aspect, the aforementioned component may be Fig.18 The processor 1804 shown in FIG. 1 is configured to perform the functions recited by the aforementioned components (eg, as discussed above). On the other hand, the aforementioned components may be a circuit or any device configured to perform the functions recited by the aforementioned components.

[0222] Of course, in the above examples, the circuits included in the processor 1804 are provided only as examples, and other components for performing the described functions may be included in various aspects of the present disclosure, including but not limited to instructions stored in the computer-readable medium 1806, or in Figure 1 , Figure 2 , Figure 3 , Figure 5 , Figure 6 , Figure 7 , Figure 8 , Fig.17 and Fig.18 any one or more of the figures described in and using, for example, Fig.19 Any other suitable means or components of the described methods and / or algorithms.

[0223] Fig. 20 is a conceptual diagram illustrating an example of a hardware implementation of an apparatus 2000 employing a processing system 2014. In some implementations, the apparatus 2000 may correspond to Figure 1 , Figure 2 , Figure 3 , Figure 5 , Figure 6 , Figure 7 , Figure 8 and Fig.17 Any of the network entities, CUs, DUs, RUs, base stations, or scheduling entities shown in any of the figures.

[0224] According to various aspects of the present disclosure, the processing system 2014 may be used to implement an element or any part of an element or any combination of elements. The processing system may include one or more processors 2004. The processing system 2014 may be substantially connected to Fig.18 , including a bus interface 2008, a bus 2002, a memory 2005, a processor 2004, a computer-readable medium 2006, a transceiver 2010, and an antenna array 2020. The memory 2005 may store beam resource information 2015 (e.g., indicating BFD-RS resources) used in cooperation with the processor 2004 and the transceiver 2010 to perform communication operations as described herein. In addition, the device 2000 may include an interface 2030 (e.g., a network interface) that provides a component for communicating with at least one other device within the core network and with at least one radio access network.

[0225] The apparatus 2000 may be configured to perform any one or more of the operations described herein (e.g., as described above in conjunction with Figures 1 to 17 As described and as follows Fig.21 In some aspects of the present disclosure, processor 2004 as utilized in apparatus 2000 may include circuits configured for various functions.

[0226] In some aspects of the present disclosure, the processor 2004 may include a communication and processing circuit 2041. The communication and processing circuit 2041 may be configured to communicate with a network entity. The communication and processing circuit 2041 may include one or more hardware components that provide a physical structure that performs various processes related to communication (e.g., signal reception and / or signal transmission) as described herein. The communication and processing circuit 2041 may also include one or more hardware components that provide a physical structure that performs various processes related to signal processing (e.g., processing received signals and / or processing signals for transmission) as described herein. The communication and processing circuit 2041 may be further configured to execute communication and processing software 2051 included on the computer-readable medium 2006 to implement one or more functions described herein.

[0227] In some implementations where communication involves receiving information, the communication and processing circuit 2041 may obtain information from a component of the device 2000 (e.g., from a transceiver 2010 that receives information via radio frequency signaling or some other type of signaling suitable for an applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, the communication and processing circuit 2041 may output the information to another component of the processor 2004, to the memory 2005, or to the bus interface 2008. In some examples, the communication and processing circuit 2041 may receive one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuit 2041 may receive information via one or more channels. In some examples, the communication and processing circuit 2041 and / or the transceiver 2010 may include functionality for components for receiving. In some examples, the communication and processing circuit 2041 may include functionality for components for decoding. In some examples, the communication and processing circuit 2041 may include functionality for components for receiving signal measurement information from a UE.

[0228] In some implementations where communication involves transmitting (e.g., sending) information, the communication and processing circuit 2041 may obtain information (e.g., from another component of the processor 2004, the memory 2005, or the bus interface 2008), process (e.g., encode) the information, and output the processed information. For example, the communication and processing circuit 2041 may output the information to the transceiver 2010 (e.g., it sends 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 circuit 2041 may transmit one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuit 2041 may transmit information via one or more channels. In some examples, the communication and processing circuit 2041 and / or the transceiver 2010 may include functionality for components for sending. In some examples, the communication and processing circuit 2041 may include functionality for components for encoding. In some examples, the communication and processing circuit 2041 may include functionality for components for sending information to the UE.

[0229] Processor 2004 may include a processor configured to perform pause-related operations as discussed herein (e.g., in conjunction with Figures 8 to 17 The suspend circuit 2042 may be configured to execute the suspend software 2052 included on the computer readable medium 2006 to implement one or more functions described herein.

[0230] The pause circuit 2042 may include functionality for components for generating information indicating whether beam failure operations are to be at least partially suspended (e.g., as described above in conjunction with Figures 8 to 17 For example, the suspension circuit 2042 may determine (e.g., based on a comparison of the certainty level with at least one threshold) whether the PDCCH BLER operation is to be partially suspended or fully suspended. The suspension circuit 2042 may then choose to transmit an instruction to the UE to partially suspend or fully suspend the PDCCH BLER operation accordingly (e.g., for a specified time duration).

[0231] The pause circuit 2042 may include functionality for components for outputting information (e.g., as described above in conjunction with Figures 8 to 17 As described above). For example, the suspension circuit 2042 may transmit a MAC-CE or DCI including information indicating whether the beam failure operation is to be at least partially suspended to the UE. As another example, the suspension circuit 2042 may transmit at least one beam failure reporting parameter to the UE. As another example, the suspension circuit 2042 may transmit a suspension parameter to the UE.

[0232] The pause circuit 2042 may include the functionality of a component for comparing the certainty level to at least one threshold value (e.g., as described above in conjunction with Figures 8 to 17 For example, the pause circuit 2042 may compare the certainty level calculated by the machine learning model with a first threshold or with a first threshold and a second threshold.

[0233] The pause circuit 2042 may include functionality for components for outputting a certainty level (e.g., as described above in conjunction with Figures 8 to 17 For example, the suspend circuit 2042 may transmit a MAC-CE or DCI including a certainty level to the UE.

[0234] The pause circuit 2042 may include functionality of a component for outputting at least one threshold value (e.g., as described above in conjunction with Figures 8 to 17 For example, the suspend circuit 2042 may transmit to the UE a MAC-CE or DCI including at least one threshold to be compared with the certainty level.

[0235] The processor 2004 may include a beam failure circuit 2043 configured to perform beam failure related operations as discussed herein (e.g., as described above in connection with Figures 8 to 17 The beam failure circuit 2043 may be configured to execute the beam failure software 2053 included on the computer readable medium 2006 to implement one or more functions described herein.

[0236] The beam failure circuit 2043 may include functionality for components for obtaining signal measurement information (e.g., as described above in conjunction with Figures 8 to 17 As described). For example, the beam failure circuit 2043 may receive measurement reports from the UE indicating RSRP levels of different beams and input this information into the machine learning model.

[0237] The beam failure circuit 2043 may include functionality for components for obtaining a beam failure request message (e.g., as described above in conjunction with Figures 8 to 17 For example, in the event that the UE determines that a threshold number of beam failure instances have occurred during a defined time period, the beam failure circuit 2043 may receive a BFRQ from the UE.

[0238] The beam failure circuit 2043 may include functionality for components for performing beam failure operations (e.g., as described above in conjunction with Figures 8 to 17 For example, the beam failure circuit 2043 may restore a beam for the UE or establish a new beam for the UE after receiving a BFRQ from the UE.

[0239] In some examples, the above is combined with Fig. 20 The apparatus 2000 shown and described may be a decomposed base station. Fig. 20 The apparatus 2000 shown in may include a CU and, optionally, one or more DU / RUs of a decomposed base station. Other DU / RUs associated with the apparatus 2000 may be distributed throughout the network. In some examples, the DU / RU may correspond to a TRP associated with a network entity. In some examples, the CU and / or DU / RU of the decomposed base station (e.g., within the apparatus 2000) may generate information indicating whether the user equipment is to at least partially suspend beam failure operation and provide the information to the user equipment.

[0240] Fig.21 is a flow chart illustrating an example method 2100 for a wireless communication system according to some aspects of the present disclosure. 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 for all example implementations. In some examples, the method 2100 may be performed by Fig. 20 The illustrated device 2000 performs. In some examples, the method 2100 can be performed by any suitable device or component for performing the functions or algorithms described below.

[0241] At block 2102, a first device may obtain, from a second device, signal measurement information associated with at least one first beam resource of a plurality of beam resources associated with the first device. Fig. 20 The communication and processing circuitry 2041 and transceiver 2010 shown and described in the accompanying drawings may provide a means for obtaining, from a second device, signal measurement information associated with at least one first beam resource of a plurality of beam resources associated with a first device. In some examples, Fig. 20 The communication and processing circuit 2041 or transceiver 2010 shown and described in the figure may provide a component for obtaining, from a second device, signal measurement information associated with at least one first beam resource of a plurality of beam resources associated with a first device.

[0242] At block 2104, the first device may generate first information indicating whether the second device is to at least partially suspend beam failure operations for at least one first beam resource based on the signal measurement information. Fig. 20 The pause circuit 2042 shown and described in the specification may provide a means for generating information indicating whether the second device is to at least partially suspend beam failure operations for at least one first beam resource based on the signal measurement information.

[0243] At block 2106, the first device may output first information indicating whether the second device is to at least partially suspend beam failure operations for at least one first beam resource for transmission to the second device. Fig. 20 The pause circuit 2042 shown and described in the embodiment of the present invention may provide a means for outputting information indicating whether the second device is to at least partially suspend beam failure operation for at least one first beam resource for transmission to the second device. In some examples, Fig. 20 The pause circuit 2042 shown and described in conjunction with the communication and processing circuit 2041 and the transceiver 2010 may provide a means for outputting information indicating whether the second device is to at least partially suspend beam failure operation for at least one first beam resource for transmission to the second device. In some examples, Fig. 20 The communication and processing circuitry 2041 and / or transceiver 2010 shown and described may provide means for outputting information indicating whether the second device is to at least partially suspend beam failure operations for at least one first beam resource for transmission to the second device.

[0244] In some examples, the beam failure operation can include determining a block error rate associated with a physical downlink control channel. In some examples, the at least partial suspension of the beam failure operation can include a partial suspension or a complete suspension of the beam failure operation.

[0245] In some examples, the first information indicates a suspension period for which the beam failure operation will be at least partially suspended. In some examples, the first information may include a certainty level indicating whether the beam failure operation will be at least partially suspended. In some examples, the first information specifies whether the beam failure operation will be fully suspended or partially suspended.

[0246] In some examples, the first device may output at least one threshold to the second device. In some examples, the at least one threshold is specified by a wireless communication standard.

[0247] In some examples, the first device may compare the level of certainty to at least one threshold. In some examples, the first information is based on the comparison of the level of certainty to the at least one threshold.

[0248] In some examples, the first device may compare the level of certainty to a first threshold. In some examples, the first device may choose to completely suspend the beam failure operation based on the comparison of the level of certainty to the first threshold. In some examples, the first device may compare the level of certainty to a second threshold. In some examples, the first device may choose to partially suspend the beam failure operation based on the comparison of the level of certainty to the second threshold.

[0249] In some examples, the first device may output at least one first beam failure reporting parameter to be used for at least one second beam resource among the multiple beam resources when the at least one first beam resource is indicated as completely paused. In some examples, the first device may obtain a first beam failure request message associated with at least one second beam resource based on the at least one first beam failure reporting parameter.

[0250] In some examples, the first beam failure request message is obtained via a first uplink resource. In some examples, the first uplink resource is different from a second uplink resource used to obtain a second beam failure request message associated with no beam resource in the plurality of beam resources being indicated as fully suspended.

[0251] In some examples, the at least one first beam failure reporting parameter specifies a first threshold number of beam failure instances. In some examples, obtaining the first beam failure request message is based at least in part on whether a number of beam failure instances associated with the at least one second beam resource exceeds the first threshold number of beam failure instances. In some examples, the first threshold number of beam failure instances is different from a second threshold number of beam failure instances associated with no beam resource in the plurality of beam resources being indicated as fully suspended.

[0252] In some examples, the at least one first beam failure reporting parameter specifies a first pause period. In some examples, obtaining the first beam failure request message is based at least in part on whether a certain number of beam failure instances associated with the at least one second beam resource occurred during the first pause period. In some examples, the first pause period is different from a second pause period associated with no beam resource in the plurality of beam resources being indicated as fully paused.

[0253] In some examples, the at least one first beam failure reporting parameter may include at least one factor to be applied to at least one second beam failure reporting parameter associated with no beam resource in the plurality of beam resources being indicated as fully paused. In some examples, the at least one factor may include at least one of: a first factor associated with a threshold number of beam failure instances, a second factor associated with a pause period, or a third factor associated with a certainty level.

[0254] In some examples, at least partially suspending the beam failure operation may include partially suspending the beam failure operation according to a suspension parameter. In some examples, partially suspending the beam failure operation may include reducing the frequency of calculating a block error rate associated with a physical downlink control channel.

[0255] In some examples, the pause parameter is based on a certainty level. In some examples, the first device may output the pause parameter to the second device. In some examples, the pause parameter is specified by a wireless communication standard.

[0256] In some examples, the first device may output at least one first beam failure reporting parameter to be used for at least one second beam resource among the plurality of beam resources when the at least one first beam resource is indicated as at least partially paused. In some examples, the first device may obtain a first beam failure request message associated with at least one second beam resource based on the at least one first beam failure reporting parameter.

[0257] In some examples, the first device may output at least one second beam failure reporting parameter associated with no beam resource in the plurality of beam resources being indicated as partially paused. In some examples, the at least one second beam failure reporting parameter is different from the at least one first beam failure reporting parameter.

[0258] In some examples, the at least one first beam resource may include a plurality of beam resources. In some examples, the first device may output at least one first beam failure reporting parameter to be used for at least one second beam resource in the plurality of beam resources. In some examples, the at least one first beam failure reporting parameter is based on how many beam resources in the plurality of beam resources are indicated as at least partially suspended.

[0259] In some examples, the first device may include: a receiver configured to receive the signal measurement information; and a transmitter configured to send the information indicating whether the second device is to at least partially suspend the beam failure operation for the at least one first beam resource, wherein the first device is configured as a network entity.

[0260] Reference again Fig. 20 In one configuration, the device 2000 includes: a component for obtaining signal measurement information associated with at least one first beam resource among a plurality of beam resources associated with the first device from a second device; a component for generating first information indicating whether the second device is to at least partially suspend the beam failure operation for the at least one first beam resource based on the signal measurement information; and a component for outputting the first information indicating whether the second device is to at least partially suspend the beam failure operation for the at least one first beam resource for sending to the second device. In one aspect, the aforementioned components may be Fig. 20 The processor 2004 shown in FIG. 2 is configured to perform the functions recited by the aforementioned components (eg, as discussed above). On the other hand, the aforementioned components may be a circuit or any device configured to perform the functions recited by the aforementioned components.

[0261] Of course, in the above examples, the circuits included in the processor 2004 are provided only as examples, and other components for performing the described functions may be included in various aspects of the present disclosure, including but not limited to instructions stored in the computer-readable medium 2006, or in Figure 1 , Figure 2 , Figure 3 , Figure 5 , Figure 6 , Figure 7 , Figure 8 , Fig.17 and Fig. 20 any one or more of the figures described in and using, for example, Fig.21 Any other suitable means or components of the described methods and / or algorithms.

[0262] Fig.19 and Fig.21 The method shown in may include additional aspects, such as any single aspect or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein. A summary of several aspects of the disclosure is provided below.

[0263] Aspect 1: A method for performing wireless communications at a first device (e.g., user equipment), the method comprising: obtaining first information from a second device, the first information indicating whether the first device will suspend a beam failure operation for at least one first beam resource among a plurality of beam resources associated with the second device; and at least partially suspending the beam failure operation for the at least one first beam resource based on the first information.

[0264] Aspect 2: The method according to aspect 1, wherein the beam failure operation includes determining a block error rate associated with a physical downlink control channel.

[0265] Aspect 3: The method according to aspect 1 or 2, wherein the at least partial suspension of the beam failure operation comprises a partial suspension or a complete suspension of the beam failure operation.

[0266] Aspect 4: A method according to any one of Aspects 1 to 3, wherein: the first information indicates a suspension period during which the beam failure operation will be at least partially suspended; and the at least partial suspension of the beam failure operation is maintained for the suspension period.

[0267] Aspect 5: A method according to any one of Aspects 1 to 4, wherein: the first information includes a certainty level indicating whether the beam failure operation will be at least partially suspended; and the at least partial suspension of the beam failure operation is based on the certainty level.

[0268] Aspect 6: A method according to any one of Aspects 1 to 4, wherein: the first information specifies whether the beam failure operation will be fully or partially suspended; and the at least partial suspension of the beam failure operation includes partially or fully suspending the beam failure operation based on the first information.

[0269] Aspect 7: A method according to any one of Aspects 1 to 4, wherein: the first information includes a certainty level indicating whether the beam failure operation will be at least partially suspended; the method also includes comparing the certainty level with at least one threshold; and the at least partial suspension of the beam failure operation is based on the comparison of the certainty level with the at least one threshold.

[0270] Aspect 8: The method according to aspect 7, wherein: the method further comprises obtaining the at least one threshold from the second device; or the at least one threshold is specified by a wireless communication standard.

[0271] Aspect 9: A method according to any one of Aspects 1 to 4, wherein: the first information includes a certainty level indicating whether the beam failure operation will be at least partially suspended; the method also includes comparing the certainty level with a first threshold; and the at least partial suspension of the beam failure operation includes a complete suspension based on the comparison of the certainty level with the first threshold.

[0272] Aspect 10: A method according to Aspect 9, wherein: the method also includes comparing the certainty level with a second threshold; and the at least partial suspension of the beam failure operation includes a partial suspension based on the comparison of the certainty level with the second threshold.

[0273] Aspect 11: According to the method described in any one of Aspects 1 to 10, the method further includes: when the at least one first beam resource is indicated as completely paused, obtaining at least one first beam failure reporting parameter to be used for at least one second beam resource among the multiple beam resources; and based on the at least one first beam failure reporting parameter, outputting a first beam failure request message associated with the at least one second beam resource for sending to the second device.

[0274] Aspect 12: A method according to Aspect 11, wherein: the first beam failure request message is output for transmission via a first uplink resource; and the first uplink resource is different from a second uplink resource configured for a second beam failure request message associated with no beam resource among the multiple beam resources being indicated as being completely paused.

[0275] Aspect 13: A method according to any one of Aspects 11 to 12, wherein: the at least one first beam failure reporting parameter specifies a first threshold number of beam failure instances; and the output of the first beam failure request message to be sent is at least partially based on whether the number of beam failure instances associated with the at least one second beam resource exceeds the first threshold number of beam failure instances.

[0276] Aspect 14: A method according to Aspect 13, wherein: the first threshold number of beam failure instances is different from a second threshold number of beam failure instances associated with no beam resource in the plurality of beam resources being indicated as fully paused.

[0277] Aspect 15: A method according to any one of Aspects 11 to 14, wherein: the at least one first beam failure reporting parameter specifies a first pause period; and the output of the first beam failure request message for sending is at least partially based on whether a certain number of beam failure instances associated with the at least one second beam resource occur during the first pause period.

[0278] Aspect 16: The method according to aspect 15, wherein the first suspension period is different from a second suspension period associated with no beam resource among the plurality of beam resources being indicated as fully suspended.

[0279] Aspect 17: A method according to any one of Aspects 11 to 16, wherein the at least one first beam failure reporting parameter includes at least one factor to be applied to at least one second beam failure reporting parameter associated with no beam resource among the multiple beam resources being indicated as being completely suspended.

[0280] Aspect 18: The method according to Aspect 17, wherein the at least one factor comprises at least one of: a first factor associated with a threshold number of beam failure instances, a second factor associated with a pause period, or a third factor associated with a certainty level.

[0281] Aspect 19: The method according to any one of aspects 1 to 18, wherein at least partially suspending the beam failure operation includes partially suspending the beam failure operation according to a suspension parameter.

[0282] Aspect 20: The method according to aspect 19, wherein the partially suspending the beam failure operation includes reducing the frequency of calculating a block error rate associated with a physical downlink control channel.

[0283] Aspect 21: A method according to any one of Aspects 19 to 20, wherein at least one of the following situations: the pause parameter is based on a certainty level; the method also includes obtaining the pause parameter from the second device; or the pause parameter is specified by a wireless communication standard.

[0284] Aspect 22: According to the method described in any one of Aspects 1 to 21, the method further includes: obtaining at least one first beam failure reporting parameter to be used for at least one second beam resource among the multiple beam resources when the at least one first beam resource is indicated as partially paused; and based on the at least one first beam failure reporting parameter, outputting a first beam failure request message associated with the at least one second beam resource for sending to the second device.

[0285] Aspect 23: A method according to Aspect 22, wherein: the method also includes obtaining at least one second beam failure reporting parameter associated with no beam resource among the multiple beam resources being indicated as partially paused; and the at least one second beam failure reporting parameter is different from the at least one first beam failure reporting parameter.

[0286] Aspect 24: The method according to any one of Aspects 1 to 23, wherein the at least one first beam resource comprises at least two beam resources.

[0287] Aspect 25: A method according to any one of Aspects 1 to 24, wherein: the method also includes obtaining at least one first beam failure reporting parameter to be used for at least one second beam resource among the multiple beam resources; and the at least one first beam failure reporting parameter is based on how many beam resources among the multiple beam resources are indicated as at least partially paused.

[0288] Aspect 26: The method according to any one of aspects 1 to 25, the method further comprising: receiving the first information, wherein the first device is configured as a user equipment.

[0289] Aspect 27: A method for performing wireless communications at a first device (e.g., a network entity), the method comprising: obtaining, from a second device, signal measurement information associated with at least one first beam resource among a plurality of beam resources associated with the first device; generating, based on the signal measurement information, first information indicating whether the second device is to at least partially suspend a beam failure operation for the at least one first beam resource; and outputting the first information indicating whether the second device is to at least partially suspend the beam failure operation for the at least one first beam resource for sending to the second device.

[0290] Aspect 28: According to the method described in Aspect 27, the method also includes: when the beam failure operation for the at least one first beam resource is indicated as at least partially suspended, outputting at least one first beam failure reporting parameter to be used for at least one second beam resource among the multiple beam resources for sending to the second device.

[0291] Aspect 29: The method according to aspect 28, wherein the at least one first beam failure reporting parameter specifies a first threshold number of beam failure instances.

[0292] Aspect 30: A method according to Aspect 29, wherein: the first threshold number of beam failure instances is different from a second threshold number of beam failure instances associated with no beam resource in the plurality of beam resources being indicated as fully paused.

[0293] Aspect 31: A method according to Aspect 28, wherein: the at least one first beam failure reporting parameter specifies a first pause period.

[0294] Aspect 32: The method according to aspect 31, wherein the first suspension period is different from a second suspension period associated with no beam resource in the plurality of beam resources being indicated as fully suspended.

[0295] Aspect 33: A method according to Aspect 28, wherein the at least one first beam failure reporting parameter includes at least one factor to be applied to at least one second beam failure reporting parameter associated with no beam resource in the plurality of beam resources being indicated as fully suspended.

[0296] Aspect 34: A method according to Aspect 33, wherein the at least one factor comprises at least one of: a first factor associated with a threshold number of beam failure instances, a second factor associated with a pause period, or a third factor associated with a certainty level.

[0297] Aspect 35: A method according to any one of aspects 27 to 34, wherein the beam failure operation includes determining a block error rate associated with a physical downlink control channel.

[0298] Aspect 36: The method according to any one of aspects 27 to 35, wherein the at least partial suspension of the beam failure operation comprises a partial suspension or a complete suspension of the beam failure operation.

[0299] Aspect 37: A method according to any one of aspects 27 to 36, wherein the first information indicates a suspension period during which the beam failure operation will be at least partially suspended.

[0300] Aspect 38: A method according to any one of aspects 27 to 37, wherein the first information includes a certainty level indicating whether the beam failure operation is to be at least partially suspended.

[0301] Aspect 39: The method according to aspect 38, wherein the method further comprises outputting at least one threshold value to the second device.

[0302] Aspect 40: The method according to any one of aspects 27 to 37, wherein the first information specifies whether the beam failure operation is to be fully suspended or partially suspended.

[0303] Aspect 41: The method according to aspect 40, wherein the method further comprises comparing the certainty level with at least one threshold to determine whether to fully or partially suspend the beam failure operation.

[0304] Aspect 42: According to the method described in any one of Aspects 27 to 41, the method further includes: obtaining a first beam failure request message via a first uplink resource, wherein the first uplink resource is different from a second uplink resource configured for a second beam failure request message associated with no beam resource among the multiple beam resources being indicated as completely paused.

[0305] Aspect 43: According to the method according to any one of Aspects 27 to 42, the method further includes: outputting a suspension parameter, wherein at least partially suspending the beam failure operation includes partially suspending the beam failure operation according to the suspension parameter.

[0306] Aspect 44: The method of aspect 43, wherein the partially suspending the beam failure operation comprises reducing a frequency of calculating a block error rate associated with a physical downlink control channel.

[0307] Aspect 45: The method according to any one of aspects 43 to 44, wherein at least one of the following situations: the pause parameter is based on a certainty level; or the pause parameter is specified by a wireless communication standard.

[0308] Aspect 46: According to the method described in any one of Aspects 27 to 45, the method also includes: receiving the signal measurement information; and sending the first information indicating whether the second device is to at least partially suspend the beam failure operation for the at least one first beam resource, wherein the first device is configured as a network entity.

[0309] Aspect 47: A user equipment, comprising: at least one transceiver; a memory comprising instructions; and one or more processors, the one or more processors being configured to execute the instructions and cause the user equipment to perform a method according to any one or more of Aspects 1 to 25, wherein the at least one transceiver is configured to receive the first information.

[0310] Aspect 48: A first apparatus configured for communication, the first apparatus comprising at least one component for performing any one or more of aspects 1 to 26.

[0311] Aspect 49: A non-transitory computer-readable medium storing computer-executable code, the non-transitory computer-readable medium comprising code for causing a first device to perform any one or more of aspects 1 to 26.

[0312] Aspect 50: A first device, comprising: a memory, the memory comprising instructions; and one or more processors, the one or more processors configured to execute the instructions and cause the first device to perform the method according to any one or more of Aspects 1 to 25.

[0313] Aspect 47: A network entity, comprising: at least one transceiver; a memory comprising instructions; and one or more processors, the one or more processors configured to execute the instructions and cause the network entity to perform a method according to any one or more of Aspects 27 to 45, wherein the at least one transceiver is configured to receive the first information.

[0314] Aspect 48: A first apparatus configured for communication, the first apparatus comprising at least one component for performing any one or more of aspects 27 to 46.

[0315] Aspect 49: A non-transitory computer-readable medium storing computer-executable code, the non-transitory computer-readable medium comprising code for causing a first device to perform any one or more of aspects 27 to 46.

[0316] Aspect 50: A first device, comprising: a memory, the memory comprising instructions; and one or more processors, the one or more processors configured to execute the instructions and cause the first device to perform the method according to any one or more of Aspects 27 to 45.

[0317] Several aspects of wireless communication networks have been presented with reference to example 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.

[0318] 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 (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 Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.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.

[0319] 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 (where 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 (where these information and instructions, when executed by a processor, implement the execution of the functions described in the present disclosure). As used herein, the term "determining" may include, for example, ascertaining, solving, selecting, choosing, establishing, calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, database or other data structure), etc. In addition, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), etc.

[0320] Figures 1 to 21 One or more of the illustrated components, steps, features and / or functions 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 , Figure 3 , Figure 5 , Figure 6 , Figure 7 , Figure 8 , Fig.17 , Fig.18 and Fig. 20 The apparatus, device and / or component illustrated in the can be configured to perform one or more of the methods, features or steps described herein. The novel algorithms described herein can also be effectively implemented in software and / or embedded in hardware.

[0321] It should be understood that the specific order or hierarchy of steps in the methods disclosed herein is illustrative of example processes. 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 provide elements of various steps in an example order, but are not intended to be limited to the specific order or hierarchy provided unless explicitly stated herein.

[0322] 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. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are currently or hereafter known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, regardless of whether such disclosures are explicitly recited in the claims, anything disclosed herein is not intended to be disclosed to the public.

Claims

1. A first device for wireless communication, the first device comprising: A processing system, the processing system being configured to: obtaining first information from a second device, the first information indicating whether the first device is to suspend a beam failure operation for at least one first beam resource of a plurality of beam resources associated with the second device; as well as The beam failure operation for the at least one first beam resource is at least partially suspended based on the first information.

2. The first apparatus of claim 1, wherein the beam failure operation comprises determining a block error rate associated with a physical downlink control channel. 3 . The first apparatus of claim 1 , wherein the at least partial suspension of the beam failure operation comprises a partial suspension or a complete suspension of the beam failure operation.

4. The first device according to claim 1, wherein: The first information indicates a suspension period during which the beam failure operation is to be at least partially suspended; as well as The at least partial suspension of the beam failure operation is maintained for the suspension period.

5. The first device according to claim 1, wherein: The first information includes a certainty level indicating whether the beam failure operation is to be at least partially suspended; and The at least partial suspension of the beam failure operation is based on the certainty level.

6. The first device according to claim 1, wherein: The first information specifies whether the beam failure operation is to be fully or partially suspended; and The at least partial suspension of the beam failure operation includes partially suspending or completely suspending the beam failure operation based on the first information.

7. The first device according to claim 1, wherein: The first information includes a certainty level indicating whether the beam failure operation is to be at least partially suspended; The processing system is further configured to compare the level of certainty to at least one threshold; and The at least partial suspension of the beam failure operation is based on the comparison of the certainty level to the at least one threshold.

8. The first device according to claim 7, wherein: The processing system is further configured to obtain the at least one threshold value from the second device; or The at least one threshold is specified by a wireless communication standard.

9. The first device according to claim 1, wherein: The first information includes a certainty level indicating whether the beam failure operation is to be at least partially suspended; The processing system is further configured to compare the level of certainty to a first threshold; and The at least partial suspension of the beam failure operation comprises a complete suspension based on the comparison of the certainty level to the first threshold.

10. The first device according to claim 9, wherein: The processing system is further configured to compare the level of certainty to a second threshold; and The at least partial suspension of the beam failure operation comprises a partial suspension based on the comparison of the certainty level to the second threshold.

11. The first device of claim 1 , wherein the processing system is further configured to: In a case where the at least one first beam resource is indicated as being completely paused, obtaining at least one first beam failure reporting parameter to be used for at least one second beam resource among the plurality of beam resources; and Based on the at least one first beam failure reporting parameter, a first beam failure request message associated with the at least one second beam resource is output for sending to the second device.

12. The first device according to claim 11, wherein: outputting the first beam failure request message for transmission via a first uplink resource; and The first uplink resource is different from a second uplink resource configured for a second beam failure request message associated with no beam resource among the plurality of beam resources being indicated as being completely suspended.

13. The first device according to claim 11, wherein: The at least one first beam failure reporting parameter specifies a first threshold number of beam failure instances; and The output of the first beam failure request message for transmission is based at least in part on whether a number of beam failure instances associated with the at least one second beam resource exceeds the first threshold number of beam failure instances.

14. The first apparatus of claim 13, wherein the first threshold number of beam failure instances is different from a second threshold number of beam failure instances associated with no beam resources in the plurality of beam resources being indicated as fully paused.

15. The first device according to claim 11, wherein: The at least one first beam failure reporting parameter specifies a first pause period; and The output of the first beam failure request message for transmission is based at least in part on whether a certain number of beam failure instances associated with the at least one second beam resource occurred during the first pause period. 16 . The first apparatus of claim 15 , wherein the first pause period is different from a second pause period associated with no beam resource among the plurality of beam resources being indicated as fully paused.

17. The first apparatus of claim 11, wherein the at least one first beam failure reporting parameter comprises at least one factor to be applied to at least one second beam failure reporting parameter associated with no beam resource in the plurality of beam resources being indicated as fully suspended.

18. The first device of claim 17, wherein the at least one factor comprises at least one of: a first factor associated with a threshold number of beam failure instances, a second factor associated with a pause period, or a third factor associated with a certainty level.

19. The first apparatus of claim 1, wherein at least partially suspending the beam failure operation comprises partially suspending the beam failure operation according to a suspension parameter.

20. The first apparatus of claim 19, wherein the partially suspending the beam failure operation comprises reducing a frequency of calculating a block error rate associated with a physical downlink control channel.

21. The first device of claim 19, wherein at least one of the following conditions: The suspension parameters are based on a certainty level; The processing system is further configured to obtain the pause parameter from the second device; or The pause parameters are specified by the wireless communication standard.

22. The first device of claim 1, wherein the processing system is further configured to: In a case where the at least one first beam resource is indicated as partially suspended, obtaining at least one first beam failure reporting parameter to be used for at least one second beam resource among the plurality of beam resources; and Based on the at least one first beam failure reporting parameter, a first beam failure request message associated with the at least one second beam resource is output for sending to the second device.

23. The first device according to claim 22, wherein: The processing system is further configured to obtain at least one second beam failure reporting parameter associated with no beam resource in the plurality of beam resources being indicated as partially suspended; and The at least one second beam failure reporting parameter is different from the at least one first beam failure reporting parameter.

24. The first device according to claim 1, wherein the at least one first beam resource includes at least two beam resources.

25. The first device according to claim 1, wherein: The processing system is further configured to obtain at least one first beam failure reporting parameter to be used for at least one second beam resource of the plurality of beam resources; and The at least one first beam failure reporting parameter is based on how many of the plurality of beam resources are indicated as being at least partially suspended.

26. A user equipment for wireless communication, the user equipment comprising: Transceiver; and A processing system, the processing system being configured to: receiving, via the transceiver, first information from a network entity, the first information indicating whether the user equipment is to suspend beam failure operations for at least one first beam resource of a plurality of beam resources associated with the network entity; as well as The beam failure operation for the at least one first beam resource is at least partially suspended based on the first information.

27. A first device for wireless communication, the first device comprising: A processing system, the processing system being configured to: obtaining, from a second device, signal measurement information associated with at least one first beam resource among a plurality of beam resources associated with the first device; generating, based on the signal measurement information, first information indicating whether the second apparatus is to at least partially suspend beam failure operations for the at least one first beam resource; as well as The first information indicating whether the second device is to at least partially suspend the beam failure operation for the at least one first beam resource is output for sending to the second device.

28. The first device of claim 27, wherein the processing system is further configured to: In a case where the beam failure operation for the at least one first beam resource is indicated to be at least partially suspended, at least one first beam failure reporting parameter to be used for at least one second beam resource among the plurality of beam resources is output for sending to the second device.

29. The first apparatus of claim 28, wherein the at least one first beam failure reporting parameter specifies a first pause period.

30. The first device according to claim 27, further comprising: a transceiver configured to receive the signal measurement information and to send the first information indicating whether the second apparatus is to at least partially suspend the beam failure operation for the at least one first beam resource, The first device is configured as a network entity.

Images