Beam failure handling

Abstract

Aspects of the disclosure relate to reporting beam failure. Upon detecting a beam failure, a user equipment (UE) can transmit a beam failure recovery request to a base station. If an uplink is working, the UE can transmit the beam failure recovery request via uplink signaling (e.g., via a physical uplink control channel or a physical uplink shared channel). If the uplink is not working or if the beam failure is due to a downlink quality drop, the UE can transmit the beam failure recovery request via a random access channel (RACH) message.

Description

[0001] Cross-reference to related applications

[0002] This patent application claims priority and benefit from the following applications: Pending Non-Provisional Application No. 17 / 357,471, filed June 24, 2021, with the U.S. Patent and Trademark Office; Provisional Application No. 63 / 044,986, filed June 26, 2020, with the U.S. Patent and Trademark Office; Provisional Application No. 63 / 044,992, filed June 26, 2020, with the U.S. Patent and Trademark Office; and Provisional Application No. 63 / 044,996, filed June 26, 2020, each of which has been assigned to the assignee of this application, and the contents of which are expressly incorporated herein by reference as if all applicable purposes were fully set forth below. Technical Field

[0003] In general, the technologies discussed below relate to wireless communication networks, and more specifically, the technologies discussed below relate to beam fault detection in beam-based communication scenarios (e.g., millimeter-wave communication scenarios) and the actions taken when a beam fault is detected. Background Technology

[0004] In wireless communication systems, such as those specified under the 5G New Radio (NR) standard, base stations and user equipment (UEs) 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 array transmits a signal in combination with other signals from other antennas in the same array, where signals at a specific angle undergo constructive interference while other signals undergo destructive interference.

[0005] The base station and the UE can 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 the transmit beam on the base station and the receive beam on the UE. To improve data rate, multiple BPLs can be used to facilitate spatial multiplexing of multiple data streams from the base station to the UE.

[0006] To reduce latency and improve spectral efficiency within a cell, full-duplex (FD) communication can be used in 5G systems. In some examples, FD allows for simultaneous bidirectional communication through spatial multiplexing. With spatial multiplexing in FD, different antenna arrays (e.g., different antenna panels) and beams can operate simultaneously, yet simultaneous FD communication can still be achieved through spatial separation (e.g., by beam direction). The downlink and uplink frequency bands in FD communication can completely overlap, partially overlap, or be separated by guard bands. Summary of the Invention

[0007] To provide a basic understanding of one or more aspects of this disclosure, an overview of those aspects is given below. This disclosure is not an exhaustive summary of all the features considered in this disclosure, nor is it intended to identify key or essential elements of all aspects of this disclosure, nor to describe the scope of any or all aspects of this disclosure. Its sole purpose is to present some concepts of one or more aspects of this disclosure in one form as a prelude to the more detailed description that follows.

[0008] In some examples, a method for full-duplex communication at a user equipment is disclosed. The method may include: receiving uplink transmissions sent by the user equipment; and, when the user equipment is capable of communicating with a base station via an uplink beam, sending a beam fault indication to the base station via an uplink channel of the uplink beam. In some aspects, the beam fault indication can identify a beam fault in the full-duplex communication. In some aspects, the beam fault may be due to interference from the uplink transmissions.

[0009] In some examples, a user equipment (UE) for full-duplex communication may include a transceiver, a memory, and a processor coupled to the transceiver and the memory. The processor and the memory may be configured to: receive uplink transmissions sent by the UE via the transceiver; and, when the UE is able to communicate with a base station via an uplink beam, send a beam fault indication to the base station via the transceiver through the uplink channel of the uplink beam. In some aspects, the beam fault indication can identify a beam fault in the full-duplex communication. In some aspects, the beam fault may be due to interference from the uplink transmissions.

[0010] In some examples, a user equipment (UE) for full-duplex communication may include: a unit for receiving uplink transmissions sent by the UE; and a unit for sending a beam fault indication to the base station via an uplink channel of the uplink beam when the UE is able to communicate with the base station via the uplink beam. In some aspects, the beam fault indication can identify a beam fault in the full-duplex communication. In some aspects, the beam fault may be due to interference from the uplink transmissions.

[0011] In some examples, an article of manufacture for a user equipment (UE) to use in full-duplex communication includes a non-transitory computer-readable medium having instructions stored therein, executable by one or more processors of the UE for: receiving uplink transmissions sent by the UE; and, when the UE is able to communicate with a base station via an uplink beam, sending a beam fault indication to the base station via an uplink channel of the uplink beam. In some aspects, the beam fault indication can identify a beam fault in the full-duplex communication. In some aspects, the beam fault can be due to interference from the uplink transmissions.

[0012] In some examples, a method for full-duplex communication at a user equipment is disclosed. The method may include: receiving uplink transmissions sent by the user equipment; and sending a beam fault indication, identifying a beam fault in the full-duplex communication, to the base station via a random access channel (RACH) message when the user equipment is unable to communicate with the base station via the uplink beam or when the beam fault is due to downlink quality degradation. In some aspects, the beam fault may be due to interference from the uplink transmissions.

[0013] In some examples, a user equipment (UE) for full-duplex communication may include a transceiver, a memory, and a processor coupled to the transceiver and the memory. The processor and the memory may be configured to: receive uplink transmissions sent by the UE via the transceiver; and, when the UE is unable to communicate with the base station via the uplink beam or when the beam failure is due to downlink quality degradation, send a beam failure indication via the transceiver to the base station through a Random Access Channel (RACH) message identifying a beam failure in the full-duplex communication. In some aspects, the beam failure may be due to interference from the uplink transmissions.

[0014] In some examples, a user equipment (UE) for full-duplex communication may include: a unit for receiving uplink transmissions sent by the UE; and a unit for sending a beam fault indication, identifying a beam fault in the full-duplex communication, to the base station via a random access channel (RACH) message when the UE cannot communicate with the base station via the uplink beam or when the beam fault is due to downlink quality degradation. In some aspects, the beam fault may be due to interference from the uplink transmissions.

[0015] In some examples, an article of manufacture for a user equipment (UE) to use for full-duplex communication includes a non-transitory computer-readable medium having instructions stored therein, which are executable by one or more processors of the UE to perform the following operations: receiving uplink transmissions sent by the UE; and sending a beam fault indication identifying a beam fault in the full-duplex communication to the base station via a random access channel (RACH) message when the UE is unable to communicate with the base station via the uplink beam or when the beam fault is due to downlink quality degradation. In some aspects, the beam fault may be due to interference from the uplink transmissions.

[0016] These and other aspects of this disclosure will become more fully understood through the following detailed description. Other aspects, features, and examples of this disclosure will become apparent to those skilled in the art when viewed in conjunction with the accompanying drawings in the following description of specific, exemplary aspects of this disclosure. While features of this disclosure may be discussed with reference to certain examples and figures below, all examples of this disclosure may include one or more advantageous features discussed herein. In other words, although one or more examples may be discussed as having certain preferred features, one or more of these features may also be used in conjunction with the various examples of this disclosure discussed herein. Similarly, while exemplary aspects may be discussed below as examples of apparatus, systems, or methods, it should be understood that these exemplary aspects may be implemented using various apparatuses, systems, and methods. Attached Figure Description

[0017] Figure 1 It is a schematic diagram of a wireless communication system based on some aspects.

[0018] Figure 2 This is a conceptual diagram based on some aspects of wireless access networks.

[0019] Figure 3 This is a schematic diagram of radio resources in an air interface using Orthogonal Frequency Division Multiplexing (OFDM) based on certain aspects.

[0020] Figure 4 This is a block diagram illustrating an example of a wireless communication system that supports beamforming and / or multiple-input multiple-output (MIMO) communication, according to some aspects.

[0021] Figure 5 This is a diagram illustrating an example of communication between a Radio Access Network (RAN) node and a wireless communication device using beamforming, according to some aspects.

[0022] Figure 6A and Figure 6BIt is a diagram depicting communication via two antenna panels, based on several aspects.

[0023] Figure 7A , Figure 7B and Figure 7C This is a schematic diagram of interference sources from various aspects, including base stations and UEs.

[0024] Figure 8 This is a conceptual diagram based on some examples of beam failure.

[0025] Figure 9 This is a signaling diagram illustrating example beam fault-related signaling between the UE and gNB, based on several aspects.

[0026] Figure 10 It is a flowchart of some aspects, example beam fault-related operations.

[0027] Figure 11 This is a flowchart of an example beam fault detection operation based on some aspects.

[0028] Figure 12 This is a flowchart based on some aspects of example beam fault reporting operations.

[0029] Figure 13 This is a signaling diagram illustrating an example random access channel (RACH) procedure based on some aspects.

[0030] Figure 14 This is a flowchart illustrating examples of beam and beam pair identification for full-duplex recovery, based on several aspects.

[0031] Figure 15 This is a flowchart illustrating an example of handling beam fault recovery requests and instructing beam pairs based on certain aspects.

[0032] Figure 16 This is a signaling diagram illustrating example signaling for a modified communication mode, based on some aspects.

[0033] Figure 17 This is a block diagram that conceptually illustrates an example of a hardware implementation of a user device using a processing system, based on some aspects.

[0034] Figure 18 This is a flowchart illustrating an example method for beam fault reporting, based on several aspects.

[0035] Figure 19 This is a flowchart of another example method for beam fault reporting, based on some aspects.

[0036] Figure 20This is a flowchart of another example method for beam fault reporting, based on some aspects.

[0037] Figure 21 This is a flowchart of another example method for beam fault reporting, based on some aspects.

[0038] Figure 22 This is a flowchart illustrating an example method for modifying communication patterns based on certain aspects.

[0039] Figure 23 This is a flowchart of an example method for restoring full-duplex transmission mode, based on several aspects.

[0040] Figure 24 This is a block diagram that conceptually illustrates an example of a hardware implementation of a base station using a processing system, based on some aspects.

[0041] Figure 25 This is a flowchart of an example method for switching operating modes in response to beam failure, based on several aspects.

[0042] Figure 26 This is a flowchart of another example method for switching operating modes in response to beam failure, based on several aspects.

[0043] Figure 27 This is a flowchart of another example method for modifying the communication mode, based on some aspects.

[0044] Figure 28 This is a flowchart of another example method for restoring full-duplex transmission mode, based on some aspects. Detailed Implementation

[0045] The specific embodiments described below, in conjunction with the accompanying drawings, are intended as descriptions of various configurations and not as representing the only configuration for implementing the concepts described herein. Specific details are included in the specific embodiments for the purpose of providing a comprehensive understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be implemented without using these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0046] While aspects and examples have been described in this application by way of illustration of a few examples, those skilled in the art will understand that additional implementations and use cases may arise in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, aspects and / or uses may occur via integrated chip examples and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial devices, retail / purchasing devices, medical devices, devices with artificial intelligence capabilities (AI-enabled devices), etc.). While some examples may or may not be specific to a particular use case or application, broad applicability of the described innovations is possible. Implementations may range from chip-level or modular components to non-modular, non-chip-level implementations, and further involve aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating the described aspects and features may also necessarily include additional components and features for the implementation and execution of the claimed and described examples. For example, the transmission and reception of wireless signals necessarily involve multiple components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders / converters, etc.). The aim is that the innovations described herein can be implemented in a variety of devices, chip-level components, systems, distributed arrangements, end-user equipment, etc., having various sizes, shapes, and constructions.

[0047] This disclosure relates in some respects to the detection of beam faults and actions taken in response to the detection of beam faults. Causes of beam faults may include, for example, downlink (DL) quality degradation, uplink quality degradation (UL), increased self-interference on the downlink during full-duplex (FD) operation, or increased self-interference on the uplink during FD operation.

[0048] In some examples, beam faults caused by self-interference in full-duplex communication scenarios can be detected based on the signal-to-interference-plus-noise ratio (SINR). For example, in addition to measuring the uplink reference signal transmitted by the UE on the uplink beam, the UE can also measure the downlink reference signal transmitted by the base station on the downlink beam on the UE's receive beam. The UE can then combine these measurements (e.g., channel measurements based on the downlink reference signal and self-interference measurements based on the uplink reference signal) to determine whether the downlink quality indicates a beam fault (e.g., by comparing the measured SINR or SINR-based block error rate (BER) with a threshold).

[0049] Upon detecting a beam failure, the UE can send a beam failure recovery request to the base station. In some examples, the beam failure recovery request indicates that all active beams monitored by the UE have failed. An active beam can be defined as a beam selected by the base station for data and control channel transmission (e.g., selected from a set of candidate beams selected and reported by the UE). In some examples, the active beam can be a selected set of control resource sets (CORESET) beam (e.g., two CORESET beams or some other number of CORESET beams). In some examples, the beam failure recovery request indicates that one or more beams monitored by the UE have failed. In the latter case, the beam failure indication can include an identifier for each failed beam. Furthermore, the beam failure recovery request can indicate whether the beam failure is due to downlink quality degradation or self-interference.

[0050] The way a UE sends a beam failure recovery request can depend on whether the uplink from the UE to the base station is currently active. If the uplink is active, the UE can send the beam failure recovery request via uplink signaling (e.g., via the physical uplink control channel or the physical uplink shared channel). If the uplink is not active, or if the beam failure is due to downlink channel degradation, the UE can send the beam failure recovery request via a random access channel (RACH) message. The beam failure recovery request can indicate that all beams monitored by the UE have failed, or that one or more beams monitored by the UE have failed. Furthermore, the beam failure recovery request can indicate whether the beam failure is due to downlink quality degradation or self-interference.

[0051] In some examples, the UE can determine whether the beam failure is due to downlink degradation or self-interference by initially measuring only the downlink reference signal, thus determining whether the downlink quality deterioration is sufficient to cause the beam failure alone. If so, the UE and / or base station can take measures to address the downlink quality deterioration (e.g., select a different downlink beam). On the other hand, if the beam failure is caused by self-interference, the UE and / or base station can take measures to address the self-interference (e.g., switch to half-duplex operation or some other operating mode).

[0052] The various concepts presented throughout this disclosure can be implemented in a wide variety of telecommunications systems, network architectures, and communication standards. Reference is now made to... Figure 1As a non-limiting illustrative example, reference is made to wireless communication system 100, illustrating various aspects of this disclosure. Wireless communication system 100 includes three interaction domains: core network 102, radio access network (RAN) 104, and user equipment (UE) 106. With the aid of wireless communication system 100, UE 106 can communicate data with external data network 110 (such as, but not limited to, the Internet).

[0053] RAN 104 can implement any suitable wireless communication technology or some technology to provide radio access to UE 106. As an example, RAN 104 can operate according to the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification, commonly referred to as 5G. As another example, RAN 104 can operate in a hybrid of 5G NR, commonly referred to as LTE, and the Evolved Universal Terrestrial Radio Access Network (eUTRAN) standard. 3GPP refers to this hybrid RAN as Next Generation RAN or NG-RAN. In yet another example, RAN 104 can operate according to both LTE and 5G NR standards. Of course, many other examples can be used within the scope of this disclosure.

[0054] As shown in the figure, RAN 104 includes multiple base stations 108. Broadly speaking, a base station is a network element in a radio access network responsible for transmitting to or receiving from a UE in one or more cells. In different technologies, standards, or contexts, a base station may also be referred to by those skilled in the art as a base transceiver unit (BTS), radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), access point (AP), node B (NB), eNodeB (eNB), gNode B (gNB), transmit and receive point (TRP), or some other suitable term. In some examples, a base station may include two or more TRPs, which may be co-located or non-co-located. Each TRP may communicate on the same or different carrier frequencies within 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 108 may be an LTE base station, while the other may be a 5G NR base station.

[0055] A radio access network 104 supporting wireless communication for multiple mobile devices is also illustrated. Mobile devices are typically referred to as User Equipment (UE) 106 in 3GPP standards, but may also be referred to by those skilled in the art as mobile station (MS), user station, mobile unit, user cell, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile user station, access terminal (AT), mobile terminal, radio terminal, remote terminal, handheld device, terminal, user agent, mobile client, client, or some other suitable term. UE 106 can be a means of providing users with access to network services. In an example where RAN 104 operates according to both LTE and 5G NR standards, UE 106 can be an Evolved Universal Terrestrial Radio Access Network - New Radio Dual Connectivity (EN-DC) UE, capable of simultaneously connecting to both LTE and NR base stations to receive data packets from both.

[0056] In this document, a mobile device is not necessarily capable of movement and can be stationary. The term mobile device or mobile equipment refers to a wide variety of devices and technologies. A UE may include multiple hardware structural components of different sizes, shapes, and arrangements to facilitate communication; such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc., electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile stations, cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptop computers, personal computers (PCs), notebook computers, netbooks, smartbooks, tablets, personal digital assistants (PDAs), and a wide variety of embedded systems (e.g., corresponding to the "Internet of Things" (IoT)).

[0057] Mobile devices can also be automobiles or other transport vehicles, remote sensors or actuators, robots or robotic equipment, satellite radios, Global Positioning System (GPS) devices, object tracking devices, drones, multi-rotor aircraft, quadcopters, remote control devices, consumer and / or wearable devices such as glasses, wearable cameras, virtual reality devices, smartwatches, health or fitness trackers, digital audio players (e.g., MP3 players), cameras, game consoles, etc. Mobile devices can also be digital home or smart home devices, such as home audio, video and / or multimedia equipment, appliances, vending machines, smart lighting, home security systems, smart meters, etc. Mobile devices can also be smart energy devices, security devices, solar panels or solar arrays, municipal infrastructure equipment controlling electricity (e.g., smart grids), lighting, water, etc.; industrial automation and enterprise equipment; logistics controllers; agricultural equipment, etc. Furthermore, mobile devices can provide connected medical or telemedicine support, i.e., remote healthcare. Telemedicine devices may include telemedicine monitoring devices and telemedicine management devices, whose communications may be given priority processing or priority access to other types of information, such as priority access to the transmission of critical service data and / or QoS related to the transmission of critical service data.

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

[0059] In some examples, access to the air interface can be scheduled, where a scheduling entity (e.g., base station 108) allocates resources for communication between some or all devices and apparatuses within its service area or cell. Within this disclosure, as further discussed below, the scheduling entity may be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more scheduled entities (e.g., UEs). That is, for scheduled communication, multiple UEs 106 (which may be scheduled entities) can use the resources allocated by the scheduling entity 108.

[0060] Base station 108 is not the only entity that can be used as a scheduling entity. That is, in some examples, a UE can be used as a scheduling entity to schedule 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.

[0061] like Figure 1 As shown, scheduling entity 108 can broadcast downlink service 112 to one or more scheduled entities 106. In general, scheduling entity 108 is a node or device responsible for scheduling services in the wireless communication network, including downlink service 112 and, in some examples, uplink service 116 and / or uplink control information 118 from one or more scheduled entities 106 to scheduling entity 108. On the other hand, scheduled entity 106 is a node or device that receives downlink control information 114, which includes, but is not limited to, scheduling information (e.g., permission), synchronization or timing information, or other control information from another entity in the wireless communication network (such as scheduling entity 108).

[0062] Additionally, uplink and / or downlink control information and / or service information can be time-divided into frames, subframes, time slots, and / or symbols. As used herein, a symbol can refer to a time unit in which each subcarrier carries a resource element (RE) in an Orthogonal Frequency Division Multiplexing (OFDM) waveform. In some examples, a time slot can carry 7 or 14 OFDM symbols. A subframe can refer to a duration of 1 millisecond (ms). Multiple subframes or time slots can be grouped together to form a single frame or radio frame. Within this disclosure, a frame can refer to a predetermined duration (e.g., 10 ms) for wireless transmission, where each frame consists, for example, of 10 subframes, each 1 ms long. Of course, these definitions are not required, and any suitable scheme for organizing the waveform can be used, and various time divisions of the waveform can have any suitable duration.

[0063] Typically, base station 108 may include a backhaul interface for communicating with the backhaul section 120 of a wireless communication system. Backhaul 120 provides a link between base station 108 and core network 102. Furthermore, in some examples, the backhaul network can provide interconnection between the individual base stations 108. Various types of backhaul interfaces can be employed, such as direct physical connections using any suitable transport network, virtual networks, etc.

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

[0065] Now refer to Figure 2 A schematic diagram of RAN 200 is provided through examples rather than limitations. In some examples, RAN 200 can be described above and... Figure 1 The same as RAN 104 shown in the figure.

[0066] The geographical area covered by RAN 200 can be divided into cellular areas (cells) that can be uniquely identified by user equipment (UE) based on an identifier broadcast from an access point or base station. Figure 2 Cells 202, 204, 206, and 208 are shown, 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. Radio links within a sector can be identified by a single logical identifier belonging to that sector. In a cell divided into multiple sectors, the multiple sectors within the cell can be formed by antenna groups, with each antenna responsible for communicating with UEs in a portion of the cell.

[0067] Various base station deployment methods can be used. For example, in Figure 2 In the illustration, two base stations 210 and 212 are shown in cells 202 and 204; and a third base station 214 is shown controlling a remote radio head (RRH) 216 in cell 206. That is, the base station can have an integrated antenna, or it can be connected to an antenna or RRH via a feed cable. In the illustrated example, cells 202, 204, and 206 can be referred to as macro cells when base stations 210, 212, and 214 support cells with large sizes. Furthermore, base station 218 is shown in cell 208, which can overlap with one or more macro cells. In this example, since base station 218 supports cells with relatively small sizes, cell 208 can be referred to as a small cell (e.g., microcell, picocell, femtocell, home base station, home node B, home eNode B, etc.). Cell size adjustments can be made according to system design and component constraints.

[0068] It should be understood that the radio access network 200 may include any number of radio base stations and cells. Furthermore, relay nodes can be deployed to extend the size or coverage area of ​​a given cell. Base stations 210, 212, 214, and 218 provide radio 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 used in conjunction with those described above and Figure 1 The base station / scheduling entity 108 shown is the same.

[0069] Figure 2 It also includes an unmanned aerial vehicle (UAV) 220, which can be a drone or a quadcopter. The UAV 220 can be configured to be used as a base station, or more specifically as a mobile base station. That is, in some examples, the cell may not necessarily be stationary, and the geographical area of ​​the cell can move depending on the location of the mobile base station (e.g., the UAV 220).

[0070] Within RAN 200, a cell may include UEs capable of communicating with one or more sectors of each cell. Additionally, each base station 210, 212, 214, and 218 can be configured to provide access to the core network 102 (participating in...) to all UEs in each cell. Figure 1 Access points. For example, UE 222 and UE 224 can communicate with base station 210; UE 226 and UE 228 can communicate with base station 212; UE 230 and UE 232 can communicate with base station 214 via RRH 116; and UE 234 can communicate with base station 218. In some examples, UE 222, 224, 226, 228, 230, 232, 234, 236, 238, 240 and / or 242 can communicate with the access points described above and... Figure 1 The UE / scheduled entity 106 shown is the same. In some examples, the UAV 220 (e.g., a quadcopter) can be a mobile network node and can be configured to act as a UE. For example, the UAV 220 can operate within cell 202 by communicating with base station 210.

[0071] In other examples of RAN 200, sidelink signaling can be used between UEs without relying on scheduling or control information from the base station. Sidelink communication can be used, for example, 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, UE 240, and UE 242) can communicate with each other using sidelink signal 237 without relaying the communication through the base station. In some examples, UE 238, UE 240, and UE 242 can each act as a scheduling entity or transmitting sidelink device and / or a scheduled entity or receiving sidelink device to schedule resources and transmit sidelink signal 237 between them without relying on scheduling or control information from the base station. In other examples, two or more UEs (e.g., UE 226 and UE 228) within the coverage area of ​​a base station (e.g., base station 212) may also transmit sidelink signals 227 via a direct link (sidelink) without transmitting the communication through base station 212. In this example, base station 212 may allocate resources to UE 226 and UE 228 for sidelink communication.

[0072] In a radio access network 200, the ability of a UE to communicate independently of its location while moving is referred to as mobility. Various physical channels between the UE and the radio access network are typically used within the Access and Mobility Management Function (AMF, not shown). Figure 1 Under the control of the core network 102 (part of the core network), the AMF is established, maintained and released. The AMF may include the Security Context Management Function (SCMF) for managing the security context of both the control plane and user plane functions, and the Security Anchor Function (SEAF) for performing authentication.

[0073] Radio access network 200 can use DL-based mobility or UL-based mobility to achieve mobility and handover (i.e., transferring the UE's connection from one radio channel to another). In a network configured for DL-based mobility, during a call with a scheduling entity or at any other time, the UE can monitor various parameters of the signal from its serving cell and various parameters of neighboring cells. Based on the quality of these parameters, the UE can maintain communication with one or more of these neighboring cells. During this period, 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 can perform a handover or handover from the serving cell to the neighboring (target) cell. For example, UE 224 (shown as a vehicle, although any suitable form of UE can be used) can move from a geographic area corresponding to its serving cell 202 to a geographic area corresponding to a neighboring cell 206. When the signal strength or quality from neighboring cell 206 exceeds the signal strength or quality from serving cell 202 for a given amount of time, UE 224 can send a report message indicating this situation to its serving base station 210. In response, UE 224 can receive a handover command and the UE can undergo a handover to cell 206.

[0074] In a network configured for UL-based mobility, the UL reference signal from each UE can be used by the network to select a serving cell for each UE. In some examples, base stations 210, 212, and 214 / 216 can broadcast uniform synchronization signals (e.g., a uniform primary synchronization signal (PSS), a uniform secondary synchronization signal (SSS), and a uniform physical broadcast channel (PBCH)). UEs 222, 224, 226, 228, 230, and 232 can receive the uniform synchronization signal, derive the carrier frequency and time slot timing from the synchronization signal, and transmit uplink pilots or reference signals in response to the derived timing. The uplink pilot signal transmitted by a UE (e.g., UE 224) can be simultaneously received by two or more cells (e.g., base stations 210 and 214 / 216) within the radio access network 200. Each of these cells can measure the strength of the pilot signal, and the radio access network (e.g., one or more of base stations 210 and 214 / 216 and / or a central node within the core network) can determine the serving cell of UE 224. When UE 224 moves through radio access network 200, the network can continue to monitor the uplink pilot signal transmitted by UE 224. When the signal strength or quality of the pilot signal measured by a neighboring cell exceeds the signal strength or quality of the pilot signal measured by the serving cell, network 200 can switch UE 224 from the serving cell to a neighboring cell, with or without notification to UE 224.

[0075] Although the synchronization signals transmitted by base stations 210, 212, and 214 / 216 can be uniform, the synchronization signals do not need to identify a specific cell, but can identify an area of ​​multiple cells operating on the same frequency and / or using the same timing operation. Because the number of mobility messages that need to be exchanged between the UE and the network can be reduced, the use of areas in 5G networks or other next-generation communication networks enables uplink-based mobility block framing and improves the efficiency of both the UE and the network.

[0076] In various implementations, the air interface in the radio access network 200 can use licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum, typically licensed by mobile network operators from government regulatory agencies, provides a portion of the spectrum for dedicated use. Unlicensed spectrum, which does not require government authorization, provides a portion of the spectrum for shared use. While some technical rules are usually still required to access unlicensed spectrum, access is generally available to any operator or device. Shared spectrum may fall between licensed and unlicensed spectrum, where technical rules or restrictions may be required to access the spectrum, but the spectrum can still be shared by multiple operators and / or multiple radio access technologies (RATs). For example, a licensee of a portion of licensed spectrum may provide licensed shared access (LSA) to share the spectrum with other parties, for example, by obtaining access under conditions determined by the appropriate licensee.

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

[0078] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR studies have identified the operating band for these mid-band frequencies as the frequency range name FR3 (7.125GHz-24.25GHz). Bands falling within FR3 can inherit the characteristics of FR1 and / or FR2, thus effectively extending the characteristics of FR1 and / or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation above 52.6GHz. For example, three higher operating frequency bands have been identified as the frequency range names FR4-a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz), and FR5 (114.25GHz-300GHz). Each of these higher frequency bands belongs to the EHF band.

[0079] In light of the foregoing, unless otherwise expressly stated, it should be understood that the term "below 6 GHz" as used herein can broadly mean frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise expressly stated, it should be understood that the term "millimeter wave," as used herein, can broadly mean frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR4-a, or FR4-1, and / or FR5, or within the EHF band.

[0080] The air interface in the radio access network 200 can use one or more multiplexing and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification provides multiplexing access for UL transmissions from UEs 222 and 224 to base station 210, and utilizes Orthogonal Frequency Division Multiplexing (OFDM) with a Cyclic Prefix (CP) to multiplex DL transmissions from base station 210 to one or more UEs 222 and 224. Additionally, for UL transmissions, the 5G NR specification provides support for Discrete Fourier Transform-Extended-OFDM (DFT-s-OFDM) with CP (also known as Single-Carrier FDMA (SC-FDMA)). However, within the scope of this disclosure, multiplexing and multiple access are not limited to the above schemes and can be provided using Time Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Sparse Code Multiple Access (SCMA), Resource Extended Multiple Access (RSMA), or other suitable multiple access schemes. Alternatively, 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 can be used to provide multiplexing for DL ​​transmission from base station 210 to UE 222 and UE 224.

[0081] The air interface in the radio access network 200 can also use one or more duplex algorithms. Duplex refers to a point-to-point communication link where two endpoints can communicate with each other in both directions. Full-duplex (FD) means that both endpoints can communicate with each other simultaneously. Half-duplex means that only one endpoint can send information to the other endpoint at a time. Half-duplex simulation is often implemented for wireless links using Time Division Duplex (TDD). In TDD, time division multiplexing is used to separate transmissions in different directions on a given channel. 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 the other direction, where the direction can change very rapidly, for example, several times per time slot. In wireless links, full-duplex channels typically rely on physical isolation between the transmitter and receiver, as well as appropriate interference cancellation techniques. Full-duplex simulation is often implemented for wireless links using Frequency Division Duplex (FDD) or Space Division Duplex (SDD). In FDD, transmissions in different directions operate on different carrier frequencies. In SDD, spatial division multiplexing (SDM) is used to separate transmissions in different directions on a given channel from each other. In other examples, full-duplex communication can be implemented in unpaired spectrum (e.g., within a single carrier bandwidth), where transmissions in different directions occur within different subbands of the carrier bandwidth. This type of full-duplex communication can be called subband full-duplex (SBFD), also known as flexible duplex.

[0082] Various aspects of this disclosure will be described with reference to OFDM waveforms, examples of which are provided in [the document / reference]. Figure 3 The following is a schematic illustration. Those skilled in the art should understand that various aspects of this disclosure can be applied to SC-FDMA waveforms in essentially the same manner as described below. That is, although some examples of this disclosure may focus on OFDM links for clarity, it should be understood that the same principles can also be applied to SC-FDMA waveforms.

[0083] Now refer to Figure 3 An extended view of example subframe 302 is shown, illustrating the OFDM resource grid. However, as those skilled in the art will readily recognize, the physical (PHY) layer transport architecture for any particular application can differ from the example described herein based on any number of factors. Here, time is in units of OFDM symbols in the horizontal direction; and frequency is in units of subcarriers or carriers in the vertical direction.

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

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

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

[0087] Each 1ms subframe 302 can consist of one or more adjacent time slots. Figure 3In the example shown, as an illustrative example, a subframe 302 includes four time slots 310. In some examples, time slots can be defined based on 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. Other examples may include micro-time slots with shorter durations (e.g., one to three OFDM symbols), sometimes referred to as shortened transmission time intervals (TTIs). These micro-time slots or shortened transmission time intervals (TTIs) may, in some cases, occupy resources scheduled for ongoing time slot transmissions for the same or different UEs. Any number of resource blocks can be used within a subframe or time slot.

[0088] The expanded diagram of one time slot in time slot 310 shows time slot 310 including control region 312 and data region 314. Typically, control region 312 can carry control channels, and data region 314 can carry data channels. Of course, a time slot can contain all DL, all UL, or at least one DL portion and at least one UL portion. Figure 3 The structure shown is merely an example, and different time slot structures can be used, and may include one or more of each of the control and data regions.

[0089] Despite Figure 3 Not shown, but various REs 306 within RB 308 can be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 306 within RB 308 can also carry pilot or reference signals. These pilot or reference signals can provide the receiving equipment with channel estimation for the corresponding channel, which enables coherent demodulation / detection of the control and / or data channels within RB 308.

[0090] In some examples, time slot 310 can be used for broadcast, multicast, unicast, or unicast communication. For example, broadcast, multicast, or unicast communication can refer to point-to-multipoint transmission from one device (e.g., a base station, UE, or other similar device) to other devices. In this document, broadcast communication is delivered to all devices, while multicast or unicast communication is delivered to multiple intended receiving devices. Unicast communication can refer to point-to-point transmission from one device to a single other device.

[0091] In an example of cellular communication over a cellular carrier via a Uu interface, for DL ​​transmission, a scheduling entity (e.g., a base station) may allocate one or more REs 306 (e.g., within control area 312) to carry DL control information, including one or more DL control channels (e.g., Physical Downlink Control Channel (PDCCH)), to one or more scheduled entities (e.g., UEs). 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, permission, and / or allocation of REs for DL ​​and UL transmissions. The PDCCH may also carry Hybrid Automatic Repeat Request (HARQ) feedback transmissions, such as acknowledgment (ACK) or negative acknowledgment (NACK). HARQ is a technique well-known to those skilled in the art, in which the integrity of packet transmissions can be checked at the receiving side to ensure accuracy, for example, using any suitable integrity checking mechanism, such as checksums or cyclic redundancy check (CRC). If the integrity of the transmission is acknowledged, an ACK can be sent; otherwise, a NACK can be sent. In response to NACK, the transmitting device can send HARQ retransmission, which can achieve catch-up combination, incremental redundancy, etc.

[0092] The base station can also allocate one or more REs 306 (e.g., in control area 312 or data area 314) to carry other DL signals, such as demodulation reference signals (DMRS); phase tracking reference signals (PT-RS); channel state information (CSI) reference signals (CSI-RS); and synchronization signal blocks (SSBs). SSBs can be broadcast periodically at regular intervals based on periods (e.g., 5, 10, 20, 30, 80, or 130 ms). SSBs include the primary synchronization signal (PSS), secondary synchronization signal (SSS), and physical broadcast control channel (PBCH). The UE can utilize PSS and SSS to achieve radio frame, subframe, time slot, and symbol synchronization in the time domain, identify the channel (system) bandwidth center in the frequency domain, and identify the physical cell identifier (PCI) of the cell.

[0093] The PBCH in the SSB may also include a Master Information Block (MIB), which includes various system information and parameters for decoding the System Information Block (SIB). The SIB may be, for example, System Information Type 1 (SIB1), which may include various additional (remaining) system information. Together, the MIB and SIB1 provide minimum system information (SI) for initial access. Examples of system information transmitted in the MIB may include, but are not limited to, subcarrier spacing (e.g., default downlink digital parameters), system frame number, configuration of the PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0), cell prohibition indicator, cell reselection indicator, grid offset, and search space for SIB1. Examples of residual minimum system information (RMSI) transmitted 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 transmit other system information (OSI).

[0094] In UL transmissions, the scheduled entity (e.g., the UE) may use one or more RE 306s to carry UL control information (UCI) including one or more UL control channels (e.g., Physical Uplink Control Channel (PUCCH)) to the scheduling entity. UCIs may include various packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions. Examples of uplink reference signals may include sounding reference signals (SRS) and uplink DMRS. In some examples, the UCI may include a scheduling request (SR), i.e., a request to the scheduling entity to schedule the uplink transmission. In this document, in response to an SR transmitted on the UCI, the scheduling entity may send downlink control information (DCI), which may schedule resources for uplink packet transmissions. UCIs may also include HARQ feedback, channel state feedback (CSF), such as CSI reports, or any other suitable UCI.

[0095] In addition to control information, one or more REs 306 can be allocated for data services (e.g., within data area 314). Such data services can be carried on one or more service channels, such as the Physical Downlink Shared Channel (PDSCH) for DL ​​transmission, or the Physical Uplink Shared Channel (PUSCH) for UL transmission. In some examples, one or more REs 306 within data area 314 can be configured to carry other signals, such as one or more SIBs and DMRS.

[0096] In an example of sidelink communication on a sidelink carrier via the Proximity Service (ProSe) PC5 interface, the control area 312 of time slot 310 may include a Physical Sidelink Control Channel (PSCCH), which includes sidelink control information (SCI) transmitted by an initiating (transmitting) sidelink device (e.g., a Tx V2X device or other Tx UE) to a set of one or more other receiving sidelink devices (e.g., an Rx V2X device or some other Rx UE). The data area 314 of time slot 310 may include a Physical Sidelink Shared Channel (PSSCH), which includes sidelink data traffic transmitted by the initiating (transmitting) sidelink device within reserved resources on the sidelink carrier via the SCI. Other information may also be transmitted via various REs 306 within time slot 310. For example, HARQ feedback information may be transmitted from the receiving sidelink device to the transmitting sidelink device in the Physical Sidelink Feedback Channel (PSFCH) within time slot 310. In addition, one or more reference signals, such as sidelink SSB, sidelink CSI-RS, sidelink SRS and / or sidelink positioning reference signal (PRS), can be transmitted in time slot 310.

[0097] These physical channels are typically multiplexed and mapped to transport channels for processing at the Medium Access Control (MAC) layer. The transport channels carry blocks of information called transport blocks (TBs). The transport block size (TBS), which can correspond to the number of information bits, can be a controlled parameter based on the modulation and coding scheme (MCS) and the number of redundancies (RBs) in a given transmission.

[0098] The above reference Figures 1-3 The channels or carriers described are not necessarily all channels or carriers that can be used between the scheduling entity and the scheduled entity, and those skilled in the art will recognize that other channels or carriers (such as other service, control, and feedback channels) may be used in addition to those shown.

[0099] Figure 4 An example of a wireless communication system 400 supporting beamforming and / or MIMO is shown. In the MIMO system, transmitter 402 includes multiple transmit antennas 404 (e.g., N transmit antennas), and receiver 406 includes multiple receive antennas 408 (e.g., M receive antennas). Therefore, there are N×M signal paths 410 from the transmit antennas 404 to the receive antennas 408. Each of transmitter 402 and receiver 406 can be implemented, for example, within a scheduling entity (e.g., a UE), a scheduled entity (e.g., a base station), or any other suitable wireless communication device.

[0100] The use of such multi-antenna technology enables wireless communication systems to leverage the spatial domain to support spatial multiplexing, beamforming, and transmit diversity. Spatial multiplexing can be used to simultaneously transmit different data streams (also known as layers) on the same time-frequency resources. Data streams can be sent to a single UE to increase the data rate, or to multiple UEs to increase the overall system capacity; the latter is known as 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 transmitting each spatially precoded stream through multiple transmit antennas on the downlink. The spatially precoded data streams arrive at UEs with different spatial signatures, which allow each UE to recover one or more data streams destined for that UE. On the uplink, each UE transmits spatially precoded data streams, allowing the base station to identify the source of each spatially precoded data stream.

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

[0102] In one example, such as Figure 4 As shown, rank-2 spatial multiplexing transmission on a 2x2 MIMO antenna configuration sends a data stream from each transmit antenna 404. Each data stream arrives at each receive antenna 408 along a different signal path 410. Receiver 406 can then reconstruct the data stream using the received signals from each receive antenna 408.

[0103] Transmitter 402 and / or receiver 406 may use beamforming to shape or manipulate the antenna beam (e.g., transmit or receive beam) along the spatial path between transmitter 402 and receiver 406. Beamforming can be achieved by combining signals transmitted via antennas 404 or 408 (e.g., antenna elements of an antenna array module) such that some signals experience constructive interference while others experience destructive interference. To generate the desired constructive / destructive interference, transmitter 402 or receiver 406 may apply amplitude and / or phase shifts to signals transmitted or received from each of the antennas 404 or 408 associated with transmitter 402 or receiver 406.

[0104] In 5G New Radio (NR) systems, especially above 6 GHz or millimeter-wave systems, beamforming signals can be used on most downlink channels, including the Physical Downlink Control Channel (PDCCH) and the Physical Downlink Shared Channel (PDSCH). Additionally, broadcast control information (e.g., SSB, Slot Format Indicator (SFI), and paging information) can be transmitted in a beam-sweep manner so that all scheduled entities (e.g., UEs) within the coverage area of ​​the Transmitter and Receiver Point (TRP) (e.g., gNB) can receive the broadcast control information. Furthermore, for UEs configured with beamforming antenna arrays, beamforming signals can also be used on uplink channels, including the Physical Uplink Control Channel (PUCCH) and the Physical Uplink Shared Channel (PUSCH).

[0105] Base stations (e.g., gNBs) are typically capable of communicating with UEs using transmit beams (e.g., downlink transmit beams) of varying beamwidths. For example, a base station can be configured to use a wider beam when communicating with a moving UE and a narrower beam when communicating with a stationary UE. A UE can also be configured to receive signals from the base station using one or more downlink receive beams. In some examples, to select one or more downlink transmit beams and one or more downlink receive beams for communication with the UE, the base station can transmit a reference signal, such as an SSB or CSI-RS, on each of the multiple downlink transmit beams using beam scanning. The UE can use one or more downlink receive beams on its device to measure the Reference Signal Received Power (RSRP) on each downlink transmit beam and send a beam measurement report to the base station indicating the RSRP of each measured downlink transmit beam. The base station can then select one or more serving downlink beams (e.g., downlink transmit and downlink receive beams) for communication with the UE based on the beam measurement report. The resulting selected downlink transmit and receive beams can form a downlink beampair link. In other examples, when the channel is reciprocal, the base station can derive a specific downlink beam for communication with the UE based on uplink measurements of one or more uplink reference signals (e.g., sounding reference signals (SRS)).

[0106] Similarly, uplink beams (e.g., uplink transmit beams at the UE and uplink receive beams at the base station) can be selected by measuring the RSRP of the 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, the base station can determine the uplink beams via uplink beam management through SRS beam scanning measured at the base station or via downlink beam management through SSB / CSI-RS beam scanning measured at the UE. The selected uplink beams can be indicated by the selected SRS resources (e.g., time-frequency resources for SRS transmission) when implementing uplink beam management, or by the selected SSB / CSI-RS resources when implementing downlink beam management. For example, the selected SSB / CSI-RS resources can have a spatial relationship with the selected uplink transmit beams (e.g., uplink transmit beams for PUCCH, SRS, and / or PUSCH). The selected uplink transmit beam and uplink receive beam can form an uplink beampair link.

[0107] Figure 5This diagram illustrates communication between UE 502 and base station 504 using beamforming signals, according to some aspects. UE 502 can be... Figure 1 , Figure 2 , Figure 4 , Figure 5 , Figure 7A , Figure 7B , Figure 7C , Figure 9 , Figure 13 , Figure 16 and Figure 17 Any UE or scheduled entity shown in any of the diagrams. Base station 504 can be Figure 1 , Figure 2 , Figure 4 , Figure 5 , Figure 7A , Figure 7B , Figure 7C , Figure 9 , Figure 13 , Figure 16 and Figure 24 Any base station (e.g., gNB) or scheduling entity shown.

[0108] exist Figure 5 In the example shown, base station 504 is configured to generate multiple beams 506a-506h, each beam associated with a different beam direction. Furthermore, UE 502 is configured to generate multiple beams 508a-508e, each beam associated with a different beam direction. Base station 504 and UE 502 can use downlink beam management schemes and / or uplink beam management schemes to select one or more beams 506a-506h on base station 504 and one or more beams 508a-508e on UE 502 for transmitting uplink and downlink signals therebetween.

[0109] In an example of a downlink beam management scheme for selecting downlink beams, base station 504 can be configured to scan or transmit on each of a plurality of downlink transmit beams 506a-506h during one or more synchronization time slots. For example, base station 504 can transmit reference signals, such as SSB or CSI-RS, on each beam in a different beam direction during synchronization time slots. The transmission of beam reference signals can occur periodically (e.g., configured by the gNB via Radio Resource Control (RRC) signaling), semi-permanently (e.g., configured by the gNB via RRC signaling and activated / deactivated via Medium Access Control-Control Unit (MAC-CE) signaling), or aperiodically (e.g., triggered by the gNB via Downlink Control Information (DCI)). It should be noted that although some beams are shown to be adjacent to each other, such an arrangement can be different in different aspects. For example, downlink transmit beams 506a-506h transmitted during the same symbol period may not be adjacent to each other. In some examples, base station 504 can transmit more or fewer beams distributed in all directions (e.g., 360 degrees).

[0110] UE 502 is configured to receive downlink beam reference signals on multiple downlink receive beams 508a-508e. In some examples, UE 502 searches for and identifies each of the downlink transmit beams 506a-506h based on the beam reference signals. UE 502 then performs beam measurements (e.g., RSRP, SINR, Reference Signal Receive Quality (RSRQ), etc.) on the beam reference signals on each of the downlink receive beams 508a-508e to determine the corresponding beam quality of each of the downlink transmit beams 506a-506h measured on each of the downlink receive beams 508a-508e.

[0111] UE 502 can generate and send a beam measurement report to base station 504. The beam measurement report includes the corresponding beam index and beam measurement results for each downlink transmit beam 506a-506h on each downlink receive beam 508a-508e. Base station 504 can then select one or more downlink transmit beams to send unicast downlink control information and / or user data services to UE 502. In some examples, the selected downlink transmit beam has the highest gain from the beam measurement report. In some examples, UE 502 can also identify the downlink transmit beam selected by the base station from the beam measurement. The transmission of the beam measurement report can occur periodically (e.g., configured by gNB via RRC signaling), semi-permanently (e.g., configured by gNB via RRC signaling and activated / deactivated via MAC-CE signaling), or non-periodically (e.g., triggered by gNB via DCI).

[0112] Base station 504 or UE 502 can also select a corresponding downlink receive beam on UE 502 for each selected serving downlink transmit beam to form a corresponding downlink beampair (BPL) for each selected serving downlink transmit beam. For example, UE 502 can use beam measurement to select a corresponding downlink receive beam for each serving downlink transmit beam. In some examples, the selected downlink receive beam paired with a particular downlink transmit beam may have the highest gain for that particular downlink transmit beam.

[0113] In one example, a single downlink transmit beam (e.g., beam 506d) on base station 504 and a single downlink receive beam (e.g., beam 508c) on UE can form a single downlink BPL for communication between base station 504 and UE 502. In another example, multiple downlink transmit beams (e.g., beams 506c, 506d, and 506e) on base station 504 and a single downlink receive beam (e.g., beam 508c) on UE 502 can form corresponding downlink BPLs for communication between base station 504 and UE 502. In yet another example, multiple downlink transmit beams (e.g., beams 506c, 506d, and 506e) on base station 504 and multiple downlink receive beams (e.g., beams 508c and 508d) on UE 502 can form multiple downlink BPLs for communication between base station 504 and UE 502. In this example, the first downlink BPL may include a downlink transmit beam 506c and a downlink receive beam 508c, the second downlink BPL may include a downlink transmit beam 508d and a downlink receive beam 508c, and the third downlink BPL may include a downlink transmit beam 508e and a downlink receive beam 508d.

[0114] When the channel is reciprocal, the aforementioned downlink beam management scheme can also be used to select one or more uplink beam management paths (BPLs) for uplink communication from UE 502 to base station 504. For example, the downlink BPL formed by beams 506d and 508e can also be used as an uplink BPL. Here, beam 508c is used as the uplink transmit beam, while beam 506d is used as the uplink receive beam.

[0115] In an example of an uplink beam management scheme, UE 502 can be configured to scan or transmit on each of the multiple uplink transmit beams 508a-508e. For example, UE 502 can transmit SRS on each beam in different beam directions. Furthermore, base station 504 can be configured to receive uplink beam reference signals on multiple uplink receive beams 506a-506h. In some examples, base station 504 searches for and identifies each of the uplink transmit beams 508a-508e based on the beam reference signals. Base station 504 then performs beam measurements (e.g., RSRP, SINR, RSRQ, etc.) on the beam reference signals on each of the uplink receive beams 506a-508h to determine the corresponding beam quality of each of the uplink transmit beams 508a-506e measured on each of the uplink receive beams 506a-508h.

[0116] Base station 504 can then select one or more uplink transmit beams on which UE 502 will send unicast downlink control information and / or user data services to base station 504. In some examples, the selected uplink transmit beam has the highest gain. Base station 504 can also select a corresponding uplink receive beam on base station 504 for each selected serving uplink transmit beam to form a corresponding uplink beam pair (BPL) for each selected serving uplink transmit beam. For example, base station 504 can use beam measurement to select a corresponding uplink receive beam for each serving uplink transmit beam. In some examples, the selected uplink receive beam paired with a particular uplink transmit beam may have the highest gain for that particular uplink transmit beam.

[0117] Base station 504 can then notify UE 502 of the selected uplink transmit beam. For example, base station 504 can provide an SRS resource identifier (ID) identifying the SRS transmitted on the selected uplink transmit beam. In some examples, base station 504 can apply each selected uplink transmit beam (and the corresponding uplink receive beam) to uplink signals (e.g., PUCCH, PUSCH, SRS, etc.) and send to UE 502 the corresponding SRS resource ID associated with the selected uplink transmit beam applied to each uplink signal. When the channel is reciprocal, the above uplink beam management scheme can also be used to select one or more downlink BPLs for downlink communication from base station 504 to UE 502. For example, an uplink BPL can also be used as a downlink BPL.

[0118] In some other examples, UE 502 can identify a new UL beam that can be paired with the current DL beam. For example, if the DL beam has a strong beam RSRP, the UE can decide to retain the current DL beam and replace it with a new UL beam. The decision on how to select the beam can be instructed to the UE by the base station or gNB. Alternatively or additionally, the UE can recommend a beam or BPL to the base station or gNB. In some examples, the UE can be configured with a lookup table of candidate beam pairs based on previous measurements, where the UE can recommend new DL and UL beam pairs for full-duplex communication. The gNB or base station can decide which beam to retain and which to replace among the DL and UL beams (e.g., retain the stronger beam and replace the weaker beam).

[0119] As mentioned above, the UE and the base station (e.g., gNB) can use full-duplex communication. Figure 6A This is a schematic diagram depicting an antenna array 600 of a TRP atop a base station 602 according to some aspects of this disclosure. The antenna array 600 is divided into two panels (panel 1604, panel 2606) with a physical separation 608 between them. Each of these panels can be a subarray of antennas. A given panel can transmit and / or receive beams or beam groups. Different numbers of panels may be used in other examples.

[0120] Other types of devices may include multi-panel antenna arrays for full-duplex communication. For example, a UE may have a first panel on one side of the UE and a second panel on the opposite side of the UE. As another example, a UE may have four panels, one at each corner of the UE.

[0121] Figure 6B It depicts two panels ( Figure 6A A diagram showing the transmit or receive configuration of panels 1604 and 2606 (or two panels on the UE, etc.). Transmit (TX) and receive (RX) configurations of the two panels are depicted for various DL and UL channels, as can be implemented in devices (e.g., scheduling entities or scheduled entities) that implement some aspects of flexible TDD according to this disclosure.

[0122] As mentioned above, flexible TDD can, in some examples, involve operating with two panels in TDD mode (two panels on the gNB and one or more panels on the UE are configured for DL ​​or UL) or SBFD mode (one panel on each gNB and UE is configured for UL, and another panel on each gNB and UE is configured for DL), as referenced below. Figure 6B Described.

[0123] exist Figure 6BOn the left side, when antenna array 600 communicates in only one direction at a time, both panels 1 604 and 2 606 can be configured for unidirectional communication, as an example illustrating TDD mode of DL transmission. For example, both panels 604 and 606 can be configured to transmit DL control 610, DL data 612, and DL data 613 as an example of DL transmission during TDD mode. Figure 6B At the center, when antenna array 600 simultaneously transmits a combination of DL data 615 and DL control 617, and receives UL data (e.g., PUSCH 614) and UL control 618, panel 1 604 can be configured for DL ​​transmission (i.e., TX) and panel 2 606 can be configured for UL reception (i.e., RX). Figure 6B On the right side, when antenna array 600 receives only UL data (e.g., PUSCH 620) and UL control 622, both panel 1 604 and panel 2 606 can be configured for UL reception. Antenna array 600 can therefore be configured for both TDD and full-duplex operation (e.g., flexible TDD). The physical separation 608 between panel 1 604 and panel 2 606 provides improved isolation between panels (e.g., improved isolation greater than approximately 50 dB) compared to two panels without physical separation 608. The above discussion also applies to antenna arrays in another type of device (e.g., UE, with inverted references to DL and UL).

[0124] Figure 7A , Figure 7B and Figure 7C A wireless communication system including a full-duplex gNB 702, a neighboring gNB 704, a half-duplex UE 706, a first full-duplex UE 712, and a second full-duplex UE 708 is illustrated. These figures also show different sources of interference (e.g., cross-beam interference) for the half-duplex UE 706, the first full-duplex UE 712, and the second full-duplex UE 708, as well as different gNB configurations according to some aspects of this disclosure. The half-duplex UE 706, the first full-duplex UE 712, and the second full-duplex UE 708 may correspond to... Figure 1 , Figure 2 , Figure 4 , Figure 5 , Figure 7A , Figure 7B , Figure 7C , Figure 9 , Figure 13 , Figure 16 and Figure 17 Any UE or any of the scheduled entities shown in any of the diagrams.

[0125] exist Figure 7AIn this scenario, a full-duplex gNB 702 (e.g., a scheduling entity) is transmitting to a half-duplex UE 706. During the transmission from the full-duplex gNB 702 to the half-duplex UE 706, the full-duplex gNB 702 receives self-interference 710 transmitted from itself to the half-duplex UE at its receiver (not shown), as well as interference from neighboring gNB 704 and uplink transmissions from the second full-duplex UE 708. The half-duplex UE 706 also receives interference from the second full-duplex UE 708 and its neighboring gNB 704. Because it is a half-duplex UE, the half-duplex UE 706 does not transmit during the transmission from the full-duplex gNB 702 to the half-duplex UE 706, therefore, the half-duplex UE 706 does not receive self-interference. The full-duplex gNB 702 and the neighboring gNB 704 can each correspond to... Figure 1 , Figure 2 , Figure 4 , Figure 5 , Figure 7A , Figure 7B , Figure 7C , Figure 9 , Figure 13 , Figure 16 and Figure 24 Any base station or scheduling entity shown in any of the diagrams.

[0126] exist Figure 7B In this configuration, full-duplex gNB 702 is transmitting downlink data to the first full-duplex UE 712. During this downlink transmission, the full-duplex gNB 702 simultaneously receives uplink data from the first full-duplex UE 712 at its receiver (not shown). Simultaneously with these downlink and uplink transmissions, the first full-duplex UE 712 receives self-interference 714 from its own transmission to the full-duplex gNB 702, as well as interference from its neighboring gNB 704 and interference from the second full-duplex UE 708 at its receiver (not shown).

[0127] Figure 7C A full-duplex gNB configured with multiple TRP base stations including a first TRP 702a and a second TRP 702b is shown. The first TRP 702a is receiving uplink transmissions from a first full-duplex UE 712. While transmitting uplink transmissions to the first TRP 702a, the first full-duplex UE 712 also receives transmissions from the second TRP 702b. In addition to the transmissions received from the second TRP 718b, the first full-duplex UE 712 also receives self-interference 716 at its receiver (not shown) from its own transmissions to the first TRP 702a.

[0128] Conventionally, different frequency bands can be allocated for Figures 7A-7B The transmission is to mitigate the aforementioned interference. For Figure 7A For half-duplex UE 706, if the frequency of interference from neighboring gNB 704 and the second full-duplex UE 708 is different from the frequency occupied by downlink transmission from full-duplex gNB 702 to half-duplex UE 706, the interference can be mitigated. Similarly, for Figure 7B and Figure 7C If the frequencies of the first full-duplex UE 712, the self-interference 716 from the first full-duplex UE 712, the interference from the neighbor gNB 704, and / or the interference from the second full-duplex UE 708 are different from the frequencies occupied by the downlink transmission from the full-duplex gNB 702 to the half-duplex UE 706, then the interference can be mitigated.

[0129] This disclosure relates in several aspects to FD capabilities for wireless communication and interference mitigation for FD communications. Various aspects of this disclosure can be applied to FD operations with simultaneous uplink and downlink transmissions in FR2 and / or other frequency bands, which may be referred to herein as "FD modes". FD modes may include SBFD in flexible TDD, but may also include FDD in paired spectrum, SBFD in unpaired spectrum, partially overlapping spectrum FD, fully overlapping spectrum FD, in-band FD, or other types of full-duplex operation.

[0130] This FD capability can be implemented at the base station (e.g., gNB), the UE, or both. For example, the UE can transmit uplink signals from one panel and receive downlink signals at another panel.

[0131] In some respects, full-duplex performance can depend on beam separation and / or other factors. For example, a first beam pair with more spatial separation than a second beam pair may have less self-interference than a second beam pair.

[0132] In some respects, FD capability can improve (e.g., reduce) latency. For example, compared to half-duplex communication where only a portion of the time slots are reserved for uplink transmission, in FD communication, the UE may not need to wait for available uplink time slots to send uplink information, thus reducing uplink transmission latency. As another example, the UE can receive downlink signals in time slots dedicated solely to uplink transmission, thereby reducing downlink transmission latency.

[0133] In some respects, FD capability can improve spectral efficiency (e.g., per cell, per UE, etc.). For example, in FD communication, the same time slots and / or frequency resources can be used simultaneously for uplink and downlink transmission. Here, the downlink and uplink frequency bands in FD communication can completely overlap, partially overlap, or have guard bands in between.

[0134] In full-duplex scenarios (or other beamforming scenarios) in FR2, beam failures can occur under certain circumstances. For example, if radio conditions change suddenly (e.g., when an end user rounds a corner or a vehicle causes an obstruction), the UE may experience beam failure, and one or more beams used by the UE may become unreliable before the UE is able to switch to a new beam.

[0135] In some examples, beam faults can be detected by repeatedly performing beam measurements. For instance, the UE's physical (PHY) layer can perform radio link monitoring (RLM) measurements on the RLM reference signal (RLM-RS) (e.g., for downlink). In some examples, the downlink RLM-RS may include SSB and CSI-RS. In some examples, the uplink RLM-RS may include SRS and DMRS.

[0136] The PHY layer can pass the results of these measurements to the Access Medium Control (MAC) layer and / or the Radio Resource Control (RRC) layer. In some examples, the RRC layer can be responsible for detecting radio link failures (RLFs), while the MAC layer can be responsible for detecting beam failures.

[0137] The PHY layer can use a quality threshold to trigger a fault indication to the MAC layer. As a specific example, 3GPP Technical Specification (TS) 38.133 v15.8.0, Section 8.5.1 (2019-12) specifies the Qout_LR parameter. This parameter specifies the quality, and for any monitored RLM-RS below this quality, the PHY layer generates a beamFailureInstance parameter. The MAC layer can then combine this indication with the beamFailureInstanceMaxCount and beamFailureDetectionTimer parameters for beam fault detection.

[0138] Once the UE detects a beam fault, it can attempt to recover by initiating a RACH procedure. For example, the UE can initiate a contention-free random access (CFRA) procedure using a configured Beam Fault Recovery Information Element (BFR-IE).

[0139] Before sending the RACH preamble during the RACH procedure, the UE can identify a new target beam based on measurements of one or more candidate beams. Here, the UE can measure the Reference Signal Received Power (RSRP) or some other quality of the candidate beam and select the candidate beam with the best quality (e.g., the highest RSRP). The UE can then use the selected beam for the RACH procedure for beam fault recovery. In some examples, the base station can send an IERadioLinkMonitoringConfig to the UE to configure radio link monitoring to detect beam faults and / or cell radio link faults. In some examples, the IERadioLinkMonitoringConfig specifies the resources (e.g., SSB resources or CSI-RS resources) that the UE monitors for beam quality measurement operations. Additionally, the IERadioLinkMonitoringConfig specifies the beamFailureInstanceMaxCount and beamFailureDetectionTimer parameters, which the UE uses to determine whether to initiate a beam fault recovery operation. For example, if the UE detects that the beam measurement RSRP falls below the threshold beamFailureInstanceMaxCount number of times during the time period specified by the beamFailureDetectionTimer parameter, the UE can initiate a beam failure recovery operation.

[0140] As mentioned above, beam failure can be caused by downlink or uplink quality degradation. However, for full-duplex operation, beam failure can also be caused by downlink beam failure due to increased UE self-interference (e.g., reflections and / or dynamic clutter due to environmental changes) or uplink beam failure due to increased base station (e.g., gNB) self-interference. Therefore, as Figure 8 As shown in Figure 800, in some examples, beam failure 802 may be due to DL quality degradation 804, DL UE self-interference increase 806, UL quality degradation 808, or UL gNB self-interference increase 810.

[0141] This disclosure relates in some respects to beam fault detection considering self-interference in full-duplex scenarios. The procedures and signaling discussed below can be applied to detect downlink and / or uplink beam faults.

[0142] Figure 9 An example of fault detection, fault recovery, and signaling 900 in a wireless communication system including gNB 902 and UE 904 is shown. For illustrative purposes, Figure 9This involves downlink beam fault detection and fault recovery, including new beam selection. It should be understood that the disclosed techniques can also be applied to uplink beam fault detection. UE 904 can correspond to... Figure 1 , Figure 2 , Figure 4 , Figure 5 , Figure 7A , Figure 7B , Figure 7C , Figure 9 , Figure 13 , Figure 16 and Figure 17 Any UE or scheduled entity shown. gNB 902 can correspond to Figure 1 , Figure 2 , Figure 4 , Figure 5 , Figure 7A , Figure 7B , Figure 7C , Figure 9 , Figure 13 and Figure 24 Any base station or scheduling entity shown.

[0143] Figure 9 Block 906 describes several operations for detecting downlink beam faults. This beam fault can be a combination of the above... Figure 8 The discussion covers either a complete failure (e.g., all monitored beams fail) or a partial failure (e.g., not all monitored beams fail).

[0144] During the measurement process, gNB 902 transmits RLS-RS on at least one Channel Measurement Resource (CMR), as generally indicated by lines 908-910. For example, gNB may transmit SSB or CSI-RS on the CMR specified by gNB 902 for downlink beam measurements (e.g., in RadioLinkMonitoringConfig IE).

[0145] In addition, UE 904 transmits and monitors uplink reference signals (typically represented by dashed ellipse 912) on the Interference Measurement Resource (IMR). Figure 9 (Represented by the circular arrow in the diagram). For example, the first panel of UE 904 can transmit a sounding reference signal (SRS) or a demodulated reference signal (DMRS) on the IMR specified by gNB 902 for self-interference measurement (e.g., in RadioLinkMonitoringConfig IE), and the second panel of UE 904 can measure and monitor the SRS or DMRS on the IMR. Figure 9 In the diagram, the monitoring of the uplink reference signal by UE 904 is indicated by the arrow looping back to UE 904.

[0146] In some examples, beam faults in full-duplex communication scenarios can be detected based on the signal-to-interference-plus-noise ratio (SINR). For instance, UE 904 can calculate the SINR parameter based on measured downlink reference signals and measured uplink reference signals. The UE can then determine whether the downlink quality indicates a beam fault (e.g., by comparing the SINR or a SINR-based block error rate to a threshold).

[0147] When a beam fault is detected, the UE can generate a beam fault indication. In some examples, the beam fault indication indicates that all beams monitored by the UE have failed. In some examples, the beam fault indication indicates that one or more beams monitored by the UE have failed. In the latter case, the beam fault indication may include an identifier for each failed beam.

[0148] UE 904 sends a beam failure indication 914 (e.g., a beam failure recovery request) to gNB 902. The manner in which UE 904 sends the beam failure indication 914 can depend on whether the uplink from UE 904 to gNB 902 is currently active. If the uplink is active, UE 904 can send the beam failure indication 914 via uplink signaling (e.g., via the physical uplink control channel or physical uplink shared channel). If the uplink is not active, UE 904 can send the beam failure indication 914 via a random access channel (RACH) message. The beam failure indication 914 can indicate that all beams monitored by UE 904 have failed, or that one or more beams monitored by UE 904 have failed. Furthermore, the beam failure indication 914 can indicate that the beam failure is due to, for example, downlink quality degradation and / or UE self-interference.

[0149] In some examples, UE 904 can determine whether the beam failure is due to downlink degradation or self-interference by initially measuring only the downlink reference signal, thus determining whether the deterioration of downlink quality is sufficient to cause the beam failure alone. If the deterioration of downlink quality is sufficient to cause the beam failure, UE 904 and / or gNB 902 can take temporary remedial measures to address the downlink quality degradation (e.g., by selecting a different downlink beam). On the other hand, if the beam failure is caused by UE self-interference, UE 904 and / or gNB 902 can take measures to temporarily resolve the UE self-interference (e.g., by switching to half-duplex (HD) operation or some other operating modes discussed in more detail below, and eventually returning to full-duplex communication mode).

[0150] Upon receiving a beam failure indication 914 (indicating a failure of all or part of the beams), the gNB 902 can initiate procedure 916 to modify the FD communication mode according to various different modes and conditions. In the example, the gNB 902 can initiate a half-duplex (HD) communication mode for one or more active beams, particularly in the case of a full failure indication. It should be noted that the active beams are the beams selected by the gNB for data and control channel transmission, and can also be beams selected from good candidate beams selected and reported by the UE. In some examples, the active beams can be selected CORESET beams (e.g., two CORESET beams or some other number of CORESET beams).

[0151] In another example, gNB 902 can initiate a hybrid mode, particularly in the case of partial fault indication. The hybrid mode can include operating one or more working beams according to FD communication, where the faulty beam is switched to HD communication mode operation. On the other hand, process 916 can include switching to a backoff or restricted FD mode, where the process backs to FD operation, but in a restricted FD operation mode, as discussed in more detail later. Restricted or backoff FD modes can include implementing UL power backoff for specific service situations (e.g., low priority or lower modulation and coding scheme (MCS) of UL services). Power backoff can be accompanied by UL repetition (e.g., repeated transmission of specific data / control channels). In other aspects, restricted FD mode can include replacing the faulty FD beam pair with a spare FD pair regardless of service priority.

[0152] After selecting one of various temporary or modified communication modes in process 916, the selected communication mode (HD, hybrid, or fallback / restricted FD mode) can be transmitted or indicated to UE 904, as shown in block 918. Based on the selected communication mode, HD, restricted FD, or hybrid communication occurs as shown by arrow 919 (which can be HD or FD communication depending on the specific characteristics of the selected mode).

[0153] After a predetermined operating cycle of the temporary communication mode operation as indicated by arrow 919, a new target beam measurement operation as shown in block 920 is performed.

[0154] Figure 9Block 920 describes an example operation for new target beam measurement, which involves UE 904 determining a new candidate beam and reporting the beam to gNB 902. During the measurement process, gNB 902 transmits beam measurements on the Channel Measurement Resource (CMR) summarized by lines 922-924. For example, gNB can transmit SSB or CSI-RS on the CMR specified by gNB 902 for downlink candidate beam measurement. Furthermore, UE 904 transmits and monitors uplink reference signals (such as...) on the IMR summarized by dashed ellipse 926. Figure 9 (As indicated by the circular arrow in the diagram). For example, the first panel of UE 904 can transmit a sounding reference signal (SRS) on the IMR specified by gNB 902 for cross-beam self-interference measurement, and the second panel of UE 904 can measure and monitor the SRS on the IMR.

[0155] When a beam fault is detected, the UE can generate a beam fault indication. In some examples, the beam fault indication indicates that all beams monitored by the UE have failed. In some examples, the beam fault indication indicates that one or more beams monitored by the UE have failed. In the latter case, the beam fault indication may include an identifier for each failed beam.

[0156] In some examples, beam measurements used to determine signal quality in a full-duplex communication scenario may involve measuring the signal-to-interference-plus-noise ratio (SINR). For example, UE 904 may calculate the SINR parameter based on measured downlink reference signals and measured uplink reference signals. The UE can then determine the downlink quality (e.g., by comparing the SINR or a SINR-based block error rate to a threshold). The UE can then identify candidate target beams or beam pairs for new connections based on the measurement results (e.g., by selecting the beam associated with the highest SINR). In some examples, the UE may identify DL beams paired with at least one current UL beam and may measure candidate DL beams (e.g., up to 64 beams).

[0157] In some examples, the UE can measure SINR by taking self-interference into account, rather than measuring signal quality based on RSRP and / or signal-to-noise ratio (SNR), as is the case for conventional measurements. For example, the UE can use IMR to measure self-interference from each of one or more active UL beams to each candidate DL beam. In some examples, based on these measurements (e.g., when identifying the beam associated with the highest SINR), the UE can identify a new target DL beam to pair with the current UL beam.

[0158] In some examples, the UE can identify a new UL beam that can be paired with the current DL beam. For example, if the DL beam has a strong beam RSRP, the UE can decide to retain the current DL beam and replace it with a new UL beam. The decision on how to select the beam can be instructed to the UE by the gNB. Alternatively or additionally, the UE can recommend a beam or BPL to the gNB. In some examples, the UE can be configured with a lookup table of candidate beam pairs based on previous measurements, where the UE can recommend new DL and UL beam pairs for full-duplex communication. The gNB can decide which beam to retain and which to replace (e.g., retain the stronger beam and replace the weaker beam). In some examples, where different UL beams are used for receiving DL transmissions and transmitting UL transmissions, the UE can switch between one or both of these beams.

[0159] At block 928, the UE can generate and send new beam report information to gNB 902, indicating the recommended new DL and / or UL beams, based on the new target measurements determined at block 920. At block 930, gNB 902 signals the new beam pair selection decision to UE 904 and resumes full-duplex mode.

[0160] As mentioned above, beam failure can be based on downlink signal degradation and / or UE self-interference, and the UE may or may not have a working uplink to its serving gNB. Figure 10 Different beam fault-related procedures that can be used in these different scenarios are shown, as well as full-duplex mode recovery for the UE.

[0161] At block 1002, the UE receives RRC configuration (e.g., RadioLinkMonitoringConfig IE). For example, the UE may receive configuration specifying parameters for beam failure detection and beam failure recovery (e.g., beamFailureInstanceMaxCount parameter, beamFailureDetectionTimer parameter, indication for CMR, indication for IMR, etc.).

[0162] At block 1004, at a certain point in time, the UE determines whether the maximum beam failure count has been reached. As discussed in this paper, in some examples, the UE can determine whether the RSRP or SINR measurement of a beam (or beam set) has fallen below the threshold beamFailureInstanceMaxCount number of times during the time period specified by the beamFailureDetectionTimer parameter.

[0163] If the maximum count is reached, the UE initiates a beam fault detection operation at block 1006. As discussed herein, the UE can indicate to the gNB whether the beam fault is due to downlink quality degradation or self-interference. Furthermore, if the uplink is active, the UE can send a beam fault recovery request to the gNB via uplink signaling. Conversely, if the uplink is not active, the UE can send a beam fault recovery request to the gNB via a RACH message.

[0164] Figure 10 The remaining blocks illustrate different beam fault recovery procedures for these different scenarios. Specifically, blocks 1008-1016 describe beam fault recovery procedures for beam faults caused by downlink quality degradation, blocks 1018-1026 describe beam fault recovery procedures for beam faults caused by UE self-interference when the uplink is not working, and blocks 1028-1036 describe beam fault recovery procedures for beam faults caused by UE self-interference when the uplink is working. These will be discussed in more detail below.

[0165] Figure 10 Blocks 1016 and 1026 can be used when beam failure is due to DL quality degradation or UE self-interference due to UL not being operational. In each of these blocks, a new DL beam is selected (blocks 1008, 1018), and a RACH procedure is initiated in each instance (blocks 1010-1016, 1020-1024). Once the RACH procedure is complete, the UE can perform self-interference measurements and beam pair reselection in blocks 1016 and 1026 respectively for full-duplex communication recovery. The following is combined with... Figures 14-15 Let's discuss more details of these reselection and recovery processes.

[0166] If the beam failure is due to UE self-interference and the UL is active, the UE can send an FD BFRQ at block 1028 and participate in a temporary modification of the communication mode at block 1030 to remedy the effects of the beam failure, eventually restoring operation to the FD communication mode as described above. At block 1032, the UE can perform self-interference measurements and determine new DL and / or UL beam or beam pair selection candidates, then report the new beam candidates at block 1034. After receiving the new beam selection from the gNB, the UE can return to full-duplex mode at block 1036.

[0167] about Figure 10 The blocks 1028 and 1030, in Figure 9 After the beam failure indication 914 is determined and issued, the communication mode can be temporarily modified to remedy the effects of the beam failure and eventually restore operation to FD communication mode (e.g., in...). Figure 9 Block 920 and Figure 10 (at blocks 1032, 1034, and 1036 in the diagram). In one aspect, process 916 may include various different temporary modifications in response to beam failure indication 914.

[0168] On one hand, when the gNB 902 receives a beam fault indication or beam fault recovery request (BFRQ), the gNB 902 can cause a partial or complete switch from FD mode to HD mode. In these cases, the time-division multiplexing (TDM) transmission inherent in HD operation is used to avoid beam faults on the current or active DL and UL beam pairs due to self-interference (SI). In the case of a complete fault where all active beams fail, a switch to full HD communication mode can be made. Alternatively, if only a portion of the active beams fail, the transmission can be selectively or hybridly modified, where those active beams that have failed are switched to HD mode, while the working beams in FD mode remain in FD mode.

[0169] In a further aspect, noting that the transition from FD to HD mode may take some time (e.g., in some cases, several milliseconds), gNB 902 can be configured to decide whether to further drop one of the DL or UL panels, or to terminate the DL and UL panels based on different criteria. Such criteria could include determining to drop DL and / or UL transmissions based on a PHY layer priority field. For example, Ultra-Reliable Low-Latency Communication (URLLC) services prioritized in the PHY layer could be used to determine DL and / or UL dropping, such as dropping other services (and their associated DL or UL transmissions) to support the URLLC service. In other examples, criteria could include determining dropping based on UE auxiliary information, such as the Maximum Allowable Exposure (MPE) level, or the thermal balance and differences between the Tx / UL and Rx / DL antenna arrays in the UE, such as dropping UL transmissions that would exceed MPE limits or cause excessive thermal imbalance, for example, UL transmissions causing more heat generation than DL reception. On the other hand, gNB 902 can be configured to indicate the termination of FD UL services to UE 904. In one example, periodic UL services can be configured. The indication of gNB 902 can be achieved by reserving some HD PDCCH time slots for conveying the indication to UE 904.

[0170] In another aspect, after switching to HD mode (whether full mode or hybrid mode), the gNB 902 can be configured to select which beams will be used for HD communication based on various standards. In one aspect, the gNB can select the same beams as the FD beams, or select beams different from the FD beams for DL ​​and UL transmissions. In an example, beam selection for DL ​​and UL can be based on the strongest beam for each respective transmission (i.e., the selection of UL and DL transmission beams is independently based on the strongest beam in each direction). In another aspect, the determination of the strongest beam can be based on DL or UL RSRP or SNR. In another example, DL and UL can be configured to use the strongest beam among the available DL and UL beams and use that beam for both UL and DL transmissions. In other aspects, the gNB can be configured to directly select the beams for HD configuration independently of the UE, or it can be configured to receive recommended HD beams from the UE instead of having to use the strongest beam.

[0171] On another front, the gNB 902 can be configured to switch to a restricted or backoff FD mode without switching to HD mode after detecting an FD fault. This restricted FD mode is particularly suitable for situations where UL services have low priority, but is not necessarily limited to the situations explained below. On yet another front, the restricted FD mode can include applying UL power backoff in the UE to reduce UL transmit (Tx) power when UL services have low priority or a low modulation and coding scheme (MCS), wherein the power backoff is used to reduce self-interference caused by UL transmissions. Furthermore, the UE can also be configured to utilize UL repetition (i.e., multiple retransmissions of the same service or data) when applying UL power backoff to increase the likelihood of successfully receiving data or services when they are transmitted at lower power levels.

[0172] On the other hand, a faulty FD beam pair can be replaced (by the gNB or UE) with a spare or alternative FD beam pair, regardless of whether the UL service priority is low or high. Additionally, in this case, the UE can be configured not to apply UL power backoff for cases with high UL priority. Alternatively, either the DL or UL beam can be reselected, with the UL beam remaining the same in this restricted FD scheme. Or, if the UL priority is high, the gNB or UE can be configured to switch to the HD or hybrid HD mode discussed above, instead of maintaining or attempting to use the restricted FD mode.

[0173] Note that the aspects of the process for switching to HD, hybrid HD, and restricted FD modes can be implemented in the base station or gNB, UE, or some combination thereof. The following section combines... Figure 16 Further details on the process of modifying these communication modes will be discussed.

[0174] As described above, this disclosure relates in some aspects to downlink beam fault detection for scenarios where downlink beam faults are due to self-interference and / or due to downlink quality degradation. Unlike conventional downlink beam fault detection, which can be based on downlink signal-to-noise ratio (SNR) or RSRP measurements, for full-duplex operation, downlink beam fault detection may be based on SINR measurements performed by the UE (e.g., using IMR for self-interference measurements). As described above, if the beam's SINR measurement does not meet the SINR threshold, the PHY layer can generate a beamFailureInstance indication and send this indication, along with beamFailureInstanceMaxCount and beamFailureDetectionTimer information, to the MAC layer.

[0175] In some examples (e.g., option 1), the beamFailureInstance indication is a complete failure indication. Here, the indication can indicate that all monitored RLM-RS are below a threshold. Therefore, in this case, once it is determined that each monitored beam has failed, the UE can be triggered to generate a beamFailureInstance indication to the MAC layer.

[0176] In some examples (e.g., option 2), the beamFailureInstance indication is a partial failure indication. Here, the indication can indicate that fewer than all monitored RLM-RS are below a threshold. For example, if there are two active CORESET beams for a UE and one of the CORESET beams fails, the UE can be triggered to generate a beamFailureInstance indication to the MAC layer. For the latter example, the MAC layer can maintain different counters and detection timers for different active beams.

[0177] In some examples, the UE can determine whether a beam failure is caused by downlink quality degradation or self-interference. For instance, the UE can detect beam failures caused by downlink quality degradation based solely on CMR measurements. Conversely, the UE can detect beam failures caused by self-interference based on both CMR and Interference Measurement Resource (IMR) measurements.

[0178] Based on the above, the RLM-RS configuration for full-duplex beam quality measurement can specify two types of reference signals: one for CMR (e.g., SSB or CSI-RS) and one for IMR (e.g., SRS or DMRS). For example, IERadioLinkMonitoringConfig can specify the CMR resources (e.g., SSB resources or CSI-RS resources) that the UE monitors for downlink beam quality measurement operations. Additionally, IERadioLinkMonitoringConfig can specify the IMR resources (e.g., SRS resources) that the UE will use for self-interference measurement operations.

[0179] Figure 11 This is a flowchart illustrating an example beam fault recovery method 1100 for a device according to some aspects of this disclosure. As described below, some or all of the illustrated features may be omitted in specific implementations within the scope of this disclosure, and some illustrated features may be unnecessary for all example implementations. In some examples, one or more operations of method 1100 may be performed by a UE or a base station (e.g., gNB). In some examples, method 1100 may be performed by any suitable means or unit for performing the functions or algorithms described below.

[0180] exist Figure 11 In the examples, blocks 1102 to 1108 describe measurement-related operations that can be performed at the device's PHY layer, while blocks 1110 to 1122 describe beam fault-related operations that can be performed at the device's MAC layer. In other examples, one or more of these operations may be performed at different protocol layers.

[0181] At block 1102, a device (e.g., a UE or gNB) can receive downlink signals on the CMR and / or uplink signals on the IMR according to a schedule specified by the gNB (e.g., the schedule can specify time slots and frequency bands for beam measurement). For example, to determine whether a beam failure exists due to downlink quality degradation, the UE can measure the SSB or CSI-RS from the gNB. Furthermore, to determine whether a beam failure exists due to self-interference from the UE, the UE can measure the SSB or CSI-RS from the gNB and measure the SRS or DMRS transmitted by the UE. As another example, to determine whether a beam failure exists due to uplink quality degradation, the gNB can measure the SRS or DMRS transmitted by the UE. Furthermore, to determine whether a beam failure exists due to self-interference from the gNB, the gNB can measure the SRS or DMRS transmitted by the UE and measure the SSB or CSI-RS transmitted by the gNB.

[0182] At block 1104, the device generates a quality metric for a given signal measurement. In some examples, the UE can measure the RSRP of the received downlink reference signal. In this case, the quality metric can simply be the measured RSRP.

[0183] In some examples, the UE can combine its measurements of the downlink reference signal and the uplink reference signal to measure the SINR quality metric of the downlink reference signal. Here, the UE's first panel can transmit the uplink reference signal, and the UE's second panel can measure the downlink reference signal transmitted by the gNB and the uplink reference signal transmitted by the first panel.

[0184] In some examples, the UE can calculate the block error rate (BLER) quality metric based on the measured SINR or some other parameter. In some examples, SINR can be defined as the sum of the signal strength measured on the CMR and the interference strength (e.g., self-interference measured on the IMR) and the background noise strength. In some cases, a fixed value can be specified for the background noise.

[0185] In some examples, the gNB can measure the RSRP of the received uplink reference signal. In this case, the quality metric can simply be the measured RSRP.

[0186] In some examples, the gNB can combine its measurements of the uplink reference signal and the downlink reference signal to measure the SINR quality metric of the uplink signal. Here, the first panel of the gNB can transmit the downlink reference signal, and the second panel of the gNB can measure the uplink reference signal transmitted by the UE and the downlink reference signal transmitted by the first panel.

[0187] In some examples, the gNB can calculate the block error rate (BLER) quality metric based on the measured SINR or some other parameter. In some examples, SINR can be defined as the sum of the signal strength measured on the IMR and the interference strength (e.g., self-interference measured on the CMR) and the background noise strength. In some cases, a fixed value can be specified for the background noise.

[0188] At block 1106, the device determines whether a quality metric (e.g., RSRP, SINR, or BLER) is less than or equal to a threshold. In some examples, the threshold may correspond to a BLER of 10%. Other thresholds may be used in other examples. If the quality metric is not less than or equal to the threshold, the operation returns to block 1102, where the device continues to monitor the reference signal.

[0189] On the other hand, if the quality index is less than or equal to the threshold at block 1106, the operation proceeds to block 1108. At block 1108, the device reports a beam fault indication to the MAC layer. The PHY layer's operation then returns to block 1102 and repeats the operation for the next measurement set. Therefore, each time a beam fault is detected at the PHY layer, the PHY layer sends a beam fault indication to the MAC layer.

[0190] A beam fault indication can indicate a beam fault in one or more beams. For a complete fault indication as discussed above, operations in blocks 1102 to 1106 can be performed for each active beam of the device. In this case, if all beams have failed (e.g., the quality index of each beam is below a threshold), the PHY layer can send a beam fault indication. For a partial fault indication as discussed above, operations in blocks 1102-1108 can be performed independently for each active beam of the device. In this case, if one of these beams has failed (e.g., the quality index of that beam is below a threshold), the PHY layer can send a beam fault indication.

[0191] Whenever the MAC layer receives a beam fault indication from the PHY layer, it executes operations in blocks 1110 to 1114 in the device's MAC layer.

[0192] At block 1110, the MAC layer receives a specific instance of beam fault indication from the PHY layer.

[0193] At block 1112, the device increments a counter as a result of receiving a beam fault indication. For a complete fault indication as discussed above, the counter can track the number of faults across all beams. For a partial fault indication as discussed above, the counter can track the number of faults occurring in a specific beam. In the latter case, the MAC layer can maintain separate counters for different beams (e.g., counter 1 for beam 1, counter 2 for beam 2, etc.).

[0194] At block 1114, the device determines whether the counter incremented at block 1112 has reached the defined maximum count (e.g., beamFailureInstanceMaxCount). If not, the operation flow returns to block 1110, where the MAC layer waits to receive the next instance of beam failure indication from the PHY layer.

[0195] On the other hand, if the counter has reached its defined maximum count at block 1114, the operation proceeds to block 1116. At block 1116, the device generates a Beam Failure Recovery Request (BFRQ). For example, the UE may generate a BFRQ (e.g., indicating whether all active beams have failed or a specific active beam has failed) and send the BFRQ to the gNB serving the UE. As another example, the gNB may generate a BFRQ (e.g., indicating whether all active beams for the UE have failed or a specific active beam for the UE has failed) and send the BFRQ to the UE. In some examples, the BFRQ may include an indication of whether the beam failure is due to downlink quality degradation and / or self-interference. The PHY layer operation then returns to block 1110, where the MAC layer waits for the next instance of a beam failure indication to be received from the PHY layer.

[0196] The MAC layer can also maintain one or more timers (or counters) that control the beam fault detection time. For a complete fault indication as discussed above, a single timer (or counter) can be used. For a partial fault indication as discussed above, multiple timers (or counters) can be used, where one timer can be used for a specific beam. For example, the MAC layer can maintain timer 1 for beam 1, timer 2 for beam 2, and so on.

[0197] At block 1118, the device initiates (e.g., resets) a given timer. At block 1120, the device may repeatedly (e.g., periodically) check if the timer has expired. Once the timer expires (e.g., the time period corresponding to beamFailureDetectionTimer has elapsed since the timer started), the device resets the corresponding counter used at block 1112. For example, a timer for all beams may reset the counter for all beams, a timer for beam 1 may reset the counter for beam 1, a timer for beam 2 may reset the counter for beam 2, and so on. Once the corresponding counter has been reset (or multiple counters have been reset), the operation returns to block 1118. Therefore, if a beam or beam set fails a defined number of times (e.g., beamFailureInstanceMaxCount) for each or all times (e.g., beamFailureDetectionTimer) within a defined time period, the device can thus generate a BFRQ.

[0198] Figure 12This is a flowchart illustrating an example beam fault reporting method 1200 for a UE according to some aspects of this disclosure. As described below, some or all illustrated features may be omitted in certain implementations within the scope of this disclosure, and some illustrated features may be unnecessary for all example implementations. In some examples, method 1200 may be... Figure 17 The UE 1700, or any suitable means or unit for performing the functions or algorithms described below.

[0199] At block 1202, the UE generates a beam fault recovery request (BFRQ). For example, the UE can generate a BFRQ as described above. Figure 11 As described.

[0200] At block 1204, the UE determines whether it can communicate with the base station via the uplink beam (e.g., the UE determines whether the uplink is currently operational). For example, the UE can determine whether the information sent to the base station by the UE has been acknowledged by the base station. For beam failures caused by UE self-interference, both the uplink and downlink can operate completely independently of the other beam. That is, a beam failure may only occur when transmissions exist simultaneously on both beams. In this case, the beam can still function fully under other conditions (e.g., when using half-duplex communication mode).

[0201] At block 1206, the UE selects the transmission technology for sending the BFRQ to the base station based on whether the UE can communicate with the base station via the uplink beam. For example, if the uplink is active, the UE can send the BFRQ to the base station via uplink signaling (e.g., on PUCCH or PUSCH) at block 1208. Conversely, if the uplink is not active, the UE can send the BFRQ to the base station via a BFR RACH message at block 1210. As described above, the BFRQ can indicate whether the beam failure at the UE is due to downlink quality degradation and / or UE self-interference.

[0202] In scenarios where the UE transmits block 1210 of the BFRQ via a BFR RACH message (e.g., a RACH preamble), the UE can select a new target beam for the BFR RACH. As described above, when the uplink is not working, the BFR RACH can be transmitted for beam failures caused by downlink quality degradation, or for beam failures caused by UE self-interference.

[0203] Refer again Figure 10Blocks 1008-1014, for the RACH procedure for beam failure at the UE due to downlink quality degradation, may involve: the UE selecting a new downlink beam at block 1008 and the UE transmitting a BFRQ via a BFR RACH preamble at block 1010 (e.g., without FD). As indicated in block 1010A, in some examples, the preamble may be transmitted repeatedly (e.g., up to N-1 times). This preamble repetition can use receive (Rx) beam scanning to find the optimal beam to pair with the transmit (Tx) beam as a new DL and UL beam pair to restore FD communication. The UE may then monitor Msg2 on the PDCCH at block 1012 and transmit Msg3 to the gNB at block 1014. In some examples, Msg3 may include an indication of the optimal beam pair identified at block 1010A.

[0204] Refer again Figure 10 Blocks 1018-1024, for the RACH procedure for beam failure at the UE due to downlink quality degradation, may involve: the UE selecting a new downlink beam at block 1018 and the UE transmitting a BFRQ via a BFR RACH preamble at block 1020 (e.g., using FD transmission). As indicated in block 1020A, in some examples, the preamble may be transmitted repeatedly (e.g., up to N-1 times). This preamble repetition may use an Rx beam scan to find the optimal beam to pair with the Tx beam as a new DL and UL beam pair to restore FD communication. The UE may then monitor Msg2 on the PDCCH at block 1022 and transmit Msg3 to the gNB at block 1024. In some examples, Msg3 may include an indication of the optimal beam pair identified at block 1020A.

[0205] Figure 13 An example of signaling 1300 for the RACH procedure is shown. The gNB can scan SSBs on designated resources (e.g., resources 1-4 for the first SSB scan, resources 5-8 for the second SSB scan, etc.). Therefore, the UE can identify the gNB to access via the RACH procedure based on the SSBs. As described above, in a scenario where the UE sends a BFRQ via a RACH message (e.g., a RACH preamble), the RACH procedure may involve the UE selecting a target beam for the BFR RACH (e.g., selecting the optimal combination of the SSB Tx beam from the gNB and the Rx beam at the UE).

[0206] In some examples, for the CFRA procedure, the gNB can retain and configure two RACH preambles for each UE to distinguish between regular downlink quality degradation caused by FD self-interference. Specifically, the gNB can configure a first RACH preamble to report beam faults caused by downlink quality degradation. Furthermore, the gNB can configure a second RACH preamble to report beam faults caused by FD self-interference. In this way, the gNB receiving the RACH preamble can determine the cause of the beam fault from the received RACH preamble (e.g., based on the type of the received RACH preamble).

[0207] A similar approach can be used in contention-based random access (CBRA) procedures. For example, the gNB can maintain and configure two sets of RACH preamble pools to distinguish between beam faults caused by downlink quality degradation and beam faults caused by FD self-interference. That is, the gNB can configure a first RACH preamble pool to report beam faults caused by downlink quality degradation. Furthermore, the gNB can configure a second RACH preamble pool to report beam faults caused by FD self-interference. In this way, the gNB receiving the RACH preamble can determine the cause of the beam fault from the received RACH preamble (e.g., based on the physical RACH (PRACH) preamble pool associated with the received RACH preamble).

[0208] exist Figure 13 In the example, to recover FD mode using the new DL and UL beam pairs, the RACH preamble Msg1 (or Msg3 or MsgA) is repeated N-1 times. For example, the UE may transmit Msg1 at RACH timing 1 1302 (e.g., using the first Tx beam 1303), at RACH timing 2 1304 (e.g., using the second Tx beam 1305), and at RACH timing 3 1306 (e.g., using the third Tx beam 1307). In some examples, each of these RACH preambles may include the same information (e.g., the RACH preambles may be identical).

[0209] For each repetition, the UE can use one or more panels to monitor RACH transmission. In some examples, the UE can simultaneously monitor the RACH preamble (e.g., using scans with different beams) to identify the optimal beam. Figure 13In the example, UE panel 2 is shown monitoring RACH timing 1 (e.g., using the first receive beam 1308). UE panel 2 is also shown monitoring RACH timing 2 (e.g., using the second receive beam 1310). Furthermore, UE panel 3 is shown monitoring RACH timing 3 (e.g., using the third receive beam 1312). Here, for each repetition, the UE can select an applicable Rx beam from a set of candidate Rx beams with good (e.g., optimal) SSB RSRP.

[0210] After receiving the Msg1 transmission, the gNB sends Msg2 1313 to the UE (e.g., on the Tx beam corresponding to the Rx beam used by the gNB for successful reception of Msg1). In some examples, Msg2 1313 can identify the RACH timing that leads to the strongest reception of Msg1, so that the UE can identify the optimal UE beam for communicating with the gNB.

[0211] In some examples, the UE can identify the best new UL+DL beam pair with the lowest cross-beam (xBeam) RSRP and send a report identifying the beam pair to the gNB. Such a report can be included in Msg3 1314, in the MsgA payload, or in separate signaling along with the corresponding SSB ID.

[0212] As described above, this disclosure relates in some aspects to identifying one or more new target beam pair candidates during beam failure detection and recovery procedures. The UE may send a request to the base station to restore full-duplex transmission mode, wherein the request includes the identified one or more new target beam pair candidates. In response, the base station may send new downlink and uplink beam pairs to the UE to restore full-duplex transmission mode from the scheduling entity.

[0213] Figure 14 This is a flowchart illustrating an example beam recovery method 1400 for a UE according to some aspects of this disclosure. As described below, some or all illustrated features may be omitted in certain implementations within the scope of this disclosure, and some illustrated features may be unnecessary for all example implementations. In some examples, method 1400 may be... Figure 17 The UE 1700, or any suitable means or unit for performing the functions or algorithms described below.

[0214] Block 1402 indicates a beam fault (e.g., as described above in conjunction with...). Figure 10 (As discussed), the beam failure is due to DL quality degradation or UE self-interference, and the UL is not working or operating. At block 1404, the UE performs the above... Figure 10The RACH procedure is described in blocks 1008-1014 or 1018-1024. In some examples, blocks 1402 and 1404 are optional and can be used only when the UL is not operational and initial connection is required. Once the UL is operational, the UE can determine at decision block 1406 whether a candidate beampair list is stored in memory. The candidate beampair list may include one or more UL and / or DL ​​beampairs from previous measurements that meet or exceed a threshold parameter for sufficiently strong signal quality. If a candidate beampair is determined from the list (yes at block 1406), the process proceeds to block 1414, where the UE reports the new DL and / or UL beam or beampair candidate ID to the gNB and requests full-duplex transmission mode communication.

[0215] If the UE does not identify a candidate beam pair from the table (no at block 1406), the UE performs self-interference measurement at block 1408. Depending on the configuration, the UE may optionally identify a new DL beam paired with the current UL beam at block 1410, or at block 1412. At block 1410, the UE may measure candidate DL beams (e.g., up to 64 beams), using SINR to account for self-interference and IMR to measure from each active UL beam to each candidate DL beam, where the UE will identify one or more candidate DL beams paired with each current UL beam for replacement during recovery. Alternatively, at block 1412, the UE may identify one or more UL beams paired with each of the current DL beams as candidates for replacement during recovery. For example, if the DL has a stronger beam signal (e.g., RSRP), the current (stronger) DL beam may be retained, and the current UL beam will be replaced by a new UL beam. The decision regarding whether to use block 1410 or 1412 can be instructed to the UE by the gNB. Alternatively or additionally, the UE can recommend which option to use to the gNB (e.g., block 1410 or 1412). At block 1414, the UE reports the new DL and / or UL beam or beam pair candidate IDs to the gNB and requests full-duplex transmission mode communication. The gNB responds at block 1416, and the UE receives the final new beam pair for resuming full-duplex transmission mode.

[0216] Figure 15 This is a flowchart illustrating an example beam recovery method 1400 for a UE from the perspective of a gNB, according to some aspects of this disclosure. As described below, some or all illustrated features may be omitted in certain implementations within the scope of this disclosure, and some illustrated features may be unnecessary for all example implementations. In some examples, method 1500 may be... Figure 17The UE 1700, or any suitable means or unit for performing the functions or algorithms described below.

[0217] Method 1500 begins at block 1502, where a beam failure has occurred. At decision block 1504, the gNB determines whether a beam failure recovery request (BFRQ) has been received from the UE. If a BFRQ has been received (yes at block 1504), the process continues to block 1506, where the gNB receives additional data (e.g., via UCI, PUSCH, etc.) indicating the target beam and / or the identification of beam pair candidates. The process then proceeds to block 1510, where the gNB receives a request for a full-duplex transmission mode.

[0218] If the gNB does not receive the BFRQ (no at block 1504), the gNB can subsequently receive the BFRQ along with the target beam and / or beam pair candidate at block 1508. At block 1510, the gNB can then receive a request for a full-duplex transmission mode connection from the UE. At block 1512, the gNB determines the final new beam pair for full-duplex recovery and sends this information back to the UE to establish full-duplex communication.

[0219] As described above, this disclosure relates in some respects to restoring normal FD operation after a beam failure. The base station and / or user equipment (UE) can be configured to temporarily switch from FD communication to half-duplex (HD) operation, where all active beams are used for the UE, and / or the base station is switched to HD operation in the event of a failure in all beams, or a hybrid mode of HD and FD operation in the event of a failure in only a portion of the beams. After detecting a beam failure that implements power back-off or alternative beams to handle the beam failure and restore normal FD operation, the base station or UE may alternatively switch to restricted FD operation.

[0220] Figure 16 This is a signaling diagram 1600 illustrating an example of signaling in a wireless communication system including a base station (BS) 1602 and a user equipment (UE) 1604. In some examples, this signaling can be used to switch from FD communication to one of HD, hybrid HD, or restricted FD communication modes in the event of a beam failure. In some examples, BS 1602 may correspond to... Figure 1 , Figure 2 , Figure 4 , Figure 5 , Figure 7A , Figure 7B , Figure 7C , Figure 9 , Figure 13 and Figure 24 Any base station or scheduling entity shown in any of the diagrams. In some examples, UE 1604 may correspond to... Figure 1 , Figure 2 , Figure 4 , Figure 5 , Figure 7A , Figure 7B , Figure 7C , Figure 9 , Figure 13 and Figure 17 Any UE or scheduled entity shown in any of the diagrams.

[0221] exist Figure 16 At position 1606, UE 1604 can detect beam faults on one or more beams being used to communicate with BS 1602 (e.g., FD communication). For example, UE 1604 can detect beam faults as described above. Figure 11 The subject of discussion.

[0222] At 1608, UE 1604 can send a BFRQ to BS 1602. For example, UE 1604 can do so via the uplink beam (if available) or via a combination of the above. Figure 12 The RACH procedure discussed is used to send BFRQs.

[0223] At 1610, BS 1602 can send a mode indication to UE 1604. In some examples, the mode indication may specify that HD communication mode will be used for each failed beam, and FD communication mode will be used for the remaining beams (e.g., the active beam). In some examples, the mode indication may specify that HD communication mode will be used for all beams (e.g., the active beam and the failed beam). Other communication modes may be specified in other examples.

[0224] As described above, in the event of a complete failure where all active beams fail, a switch to full HD communication mode can be made. Alternatively, if only a subset of active beams fail, selective or hybrid modifications to the transmission can be made, where those failed active beams are switched to HD mode, while the working beams in FD mode remain in FD mode. Furthermore, after switching to HD mode (whether full or hybrid), the BS 1602 can select which beams will be used for HD communication according to various criteria. Also as described above, in some cases, the BS 1602 can choose to switch to restricted or fallback FD mode without switching to HD mode after detecting an FD failure.

[0225] At 1612, UE 1604 switches to the modified communication mode specified by the mode indicator for subsequent communication between BS 1602 and UE 1604. Similarly, at 1614, BS 1602 switches to the modified communication mode specified by the mode indicator for subsequent communication between BS 1602 and UE 1604. Therefore, at 1616, BS 1602 can transmit to UE 1604 using the modified communication mode and / or UE 1604 can transmit to BS 1602 using the modified communication mode.

[0226] At 1618, UE 1604 can select one or more new beams for FD communication with BS 1602. For example, UE 1604 can identify the best available UL / DL beam pair.

[0227] At 1620, UE 1604 can send an indication to BS 1602 of the beam selected at 1618. For example, UE 1604 can send the indication via beam using a modified communication mode.

[0228] At 1622, UE 1604 switches to FD communication mode for subsequent communication between BS 1602 and UE 1604. Similarly, at 1624, UE 1604 switches to FD communication mode for subsequent communication between BS 1602 and UE 1604. Therefore, at 1626, BS 1602 can transmit to UE 1604 using FD communication mode, and UE 1604 can transmit to BS 1602 using FD communication mode.

[0229] Figure 17 This is a block diagram illustrating an example hardware implementation of a user equipment (UE) 1700 using a processing system 1714. For example, the UE 1700 may be a device configured to wirelessly communicate with a base station, such as... Figures 1-16 As discussed in any one or more figures. In some implementations, UE 1700 may correspond to Figure 1 , Figure 2 , Figure 4 , Figure 5 , Figure 7A , Figure 7B , Figure 7C , Figure 9 , Figure 13 and Figure 16 Any UE or scheduled entity shown in any of the diagrams.

[0230] According to various aspects of this disclosure, the processing system 1714 can be used to implement elements or any part of elements or any combination of elements. The processing system 1714 may include one or more processors 1704. Examples of processors 1704 include microprocessors, microcontrollers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuitry, and other suitable hardware configured to perform the various functions described throughout this disclosure. In various examples, UE 1700 may be configured to perform one or more of the functions described herein. That is, processor 1704 (as used in UE 1700) can be used to implement any one or more of the procedures and programs described herein.

[0231] In some cases, processor 1704 may be implemented via a baseband or modem chip, and in other implementations, processor 1704 may include multiple devices that are distinct from the baseband or modem chip (e.g., in such scenarios they may work together to implement the examples discussed herein). As mentioned above, various hardware configurations and components other than the baseband modem processor can be used in the implementation, including RF chains, power amplifiers, modulators, buffers, interleavers, adders / converters, and so on.

[0232] Processing system 1714 can be implemented using a bus architecture typically represented by bus 1702. Bus 1702 may include any number of interconnect buses and bridges, depending on the specific application of processing system 1714 and overall design constraints. Bus 1702 communicatively couples together various circuits including one or more processors (typically represented by processor 1704), memory 1705, and computer-readable media (typically represented by computer-readable media 1706). Bus 1702 may also link together various other circuits such as timing sources, peripheral devices, voltage regulators, and power management circuits, which are well known in the art and will not be described further. Bus interface 1708 provides an interface between bus 1702 and transceiver 1710 and antenna array 1720, and an interface between bus 1702 and interface 1730. Transceiver 1710 provides a communication interface or a unit for communicating with various other devices over a wireless transmission medium. Interface 1730 provides a communication interface or means for communicating with various other devices and equipment (e.g., other devices housed within the same device as UE 1700 or other external devices) via an internal bus or external transmission medium (e.g., an Ethernet cable). Depending on the nature of UE 1700, interface 1730 may include a user interface (e.g., buttons, a display, a speaker, a microphone, a joystick). Of course, such a user interface is optional and may be omitted in some examples (e.g., IoT devices).

[0233] Processor 1704 is responsible for managing bus 1702 and general processing, including executing software stored on computer-readable medium 1706. When processor 1704 executes the software, the software causes processing system 1714 to perform various functions for any particular device. Computer-readable medium 1706 and memory 1705 may also be used to store data manipulated by processor 1704 while executing the software. For example, memory 1705 may store beam information 1715 used by processor 1704 for the communication operations described herein.

[0234] One or more processors 1704 in the processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, software should be broadly interpreted as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, application programs, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc. Software may reside on computer-readable media 1706.

[0235] Computer-readable medium 1706 may be a non-transitory computer-readable medium. For example, non-transitory computer-readable media include magnetic storage devices (e.g., hard disks, floppy disks, magnetic tapes), optical disks (e.g., compact discs (CDs) or digital versatile discs (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 1706 may be located within, outside, or distributed across multiple entities including processing system 1714. Computer-readable medium 1706 may be embodied in a computer program product. For example, a computer program product may include a computer-readable medium within encapsulation material. Those skilled in the art will recognize how the functionality described throughout this disclosure is best implemented, depending on the specific application and the overall design constraints imposed on the system as a whole.

[0236] UE 1700 can be configured to perform any one or more of the operations described herein (e.g., as combined above). Figures 1-16 The description and the following in combination Figures 18-23 (As described). In some aspects of this disclosure, the processor 1704 used in UE1700 may include circuitry configured for various functions.

[0237] Processor 1704 may include communication and processing circuitry 1741. Communication and processing circuitry 1741 may be configured to communicate with a scheduling entity (e.g., a gNB). Communication and processing circuitry 1741 may include one or more hardware components providing a physical structure for performing various processes related to wireless communication (e.g., signal reception and / or signal transmission) as described herein. Communication and processing circuitry 1741 may also include one or more hardware components providing a physical structure for performing various processes related to signal processing (e.g., processing received signals and / or processing signals for transmission) as described herein. In some examples, communication and processing circuitry 1741 may include two or more transmit / receive chains. Communication and processing circuitry 1741 may also be configured to execute communication and processing software 1751 included on computer-readable medium 1706 to implement one or more of the functions described herein.

[0238] In some examples, the communication and processing circuitry 1741 can be configured to receive and process downlink beamforming signals at millimeter-wave frequencies or frequencies below 6 GHz via transceiver 1710 and antenna array 1720. For example, the communication and processing circuitry 1741 can be configured to receive a corresponding reference signal (e.g., SSB or CSI-RS) from the base station on each of a plurality of downlink beams via at least one first antenna panel of antenna array 1720 during downlink beam scanning. The communication and processing circuitry 1741 can also be configured to transmit beam measurement reports to the base station.

[0239] In some examples, the communication and processing circuitry 1741 may also be configured to generate and transmit uplink beamforming signals at millimeter-wave frequencies or frequencies below 6 GHz via transceiver 1710 and antenna array 1720. For example, the communication and processing circuitry 1741 may be configured to transmit a corresponding reference signal (e.g., SRS or DMRS) to the base station on each of a plurality of downlink beams via at least one second antenna panel of antenna array 1720 during uplink beam scanning.

[0240] The communication and processing circuit 1741 can also be configured to control the antenna array 1720 and transceiver 1710 to search for and identify multiple downlink transmit beams during downlink beam scanning. The communication and processing circuit 1741 can also be configured to obtain, via the antenna array 1720, multiple beam measurements for each of the multiple downlink receive beams for each identified downlink transmit beam. The communication and processing circuit 1741 can also be configured to generate a beam measurement report for transmission to a base station.

[0241] The communication and processing circuitry 1741 can also be configured to identify one or more selected uplink beams based on beam measurements obtained from the downlink beam reference signal. In some examples, the communication and processing circuitry 1741 can be configured to compare the corresponding RSRP (or other beam measurements) measured on each downlink receive beam for each serving downlink transmit beam to identify the serving downlink receive beam; and further use the serving downlink receive beam as the selected uplink transmit beam. Each serving downlink receive beam may have the highest measured RSRP (or other beam measurement) for one of the downlink transmit beams.

[0242] The communication and processing circuitry 1741 can be configured to generate one or more uplink transmit beams for transmission during uplink beam scanning. Each uplink transmit beam may carry an uplink reference signal (e.g., SRS) for measurement by the base station. The communication and processing circuitry 1741 can also be configured to identify a selected uplink transmit beam chosen by the base station based on uplink beam measurements. For example, the communication and processing circuitry 1741 can be configured to receive an indication of the selected uplink transmit beam from the base station.

[0243] On the other hand, note that antenna array 1730 can be configured by processor 1704 (and memory 1705 or medium 1706) to implement a first antenna panel and a second antenna panel. Furthermore, processor 1704 (and memory 1705 or medium 1706) can be configured to: use the first antenna panel to transmit a first beam (e.g., a UL transmit beam for FD communication) and use the second antenna panel to receive a second beam (e.g., a DL receive beam for FD communication). The second antenna panel can be used by processor 1704 to measure the self-interference of the UE for FD communication.

[0244] In some implementations where communication involves receiving information, communication and processing circuitry 1741 may obtain information from components of UE 1700 (e.g., from transceiver 1710 receiving information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, communication and processing circuitry 1741 may output information to another component of processor 1704, memory 1705, or bus interface 1708. In some examples, communication and processing circuitry 1741 may receive one or more of the following: signals, messages, other information, or any combination thereof. In some examples, communication and processing circuitry 1741 may receive information via one or more channels. In some examples, communication and processing circuitry 1741 may include the functionality of a unit for receiving information. In some examples, communication and processing circuitry 1741 may include the functionality of a unit for decoding information.

[0245] In some embodiments where communication involves sending (e.g., transmitting) information, communication and processing circuitry 1741 may acquire information (e.g., from another component of processor 1704, memory 1705, or bus interface 1708), process (e.g., encode) the information, and output the processed information. For example, communication and processing circuitry 1741 may output information to transceiver 1710 (e.g., which transmits information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium). In some examples, communication and processing circuitry 1741 may transmit one or more of the following: signals, messages, other information, or any combination thereof. In some examples, communication and processing circuitry 1741 may transmit information via one or more channels. In some examples, communication and processing circuitry 1741 may include the functionality of units for performing transmission (e.g., units for performing transmission). In some examples, communication and processing circuitry 1741 may include the functionality of units for performing encoding.

[0246] In some implementations, the communication and processing circuitry 1741 may include the function of a unit for transmitting at least one uplink reference signal to a base station. For example, the communication and processing circuitry 1741 may be configured to generate SRS and / or DMRS on at least one resource allocated by the base station.

[0247] Processor 1704 may include beam fault detection circuitry 1742, which is configured to perform beam fault detection-related operations discussed herein (e.g., Figure 11 (PHY layer and / or MAC layer beam fault detection operation). Beam fault detection circuit 1742 can be configured to execute beam fault detection software 1752 included on computer-readable medium 1706 to perform one or more of the functions described herein.

[0248] The beam fault detection circuit 1742 may include the functionality of a unit for receiving uplink transmissions. For example, the beam fault detection circuit 1742 may be configured to measure the RSRP of an uplink signal transmitted via another antenna panel of the UE using one antenna panel of the UE.

[0249] The beam fault detection circuit 1742 may include the functionality of a unit for identifying beam faults. For example, the beam fault detection circuit 1742 may include a comparator function that compares at least one measurement reference signal’s RSRP, SINR, or BLER parameter with a beam fault detection threshold.

[0250] Processor 1704 may include beam fault reporting circuitry 1743, which is configured to perform beam fault reporting related operations discussed herein (e.g., Figure 11 (PHY layer and / or MAC layer operation). Beam fault reporting circuit 1743 can be configured to execute beam fault reporting software 1753 included on computer-readable medium 1706 to perform one or more of the functions described herein.

[0251] The beam fault reporting circuit 1743 may include the functionality of a unit for generating a beam fault indication (e.g., BFRQ). For example, the beam fault reporting circuit 1743 may be configured to perform... Figure 11 The MAC layer beam fault recovery request (BFRQ) operation can instruct the UE that all or part of the detected beams in the beam have failed. The BFRQ can include an identifier for each failed beam. The BFRQ can indicate whether the beam failure is due to downlink quality degradation or self-interference.

[0252] Beam Failure Reporting Circuit 1743 may include functionality for generating a beam failure indication (e.g., BFRQ). For example, Beam Failure Reporting Circuit 1743 may be configured to send a Beam Failure Recovery Request (BFRQ) (or beam failure indication) to the base station during full-duplex (FD) communication with the base station. The BFRQ signal may be configured to indicate that at least one active beam has failed in FD communication. In some examples, Beam Failure Reporting Circuit 1743 may be configured to send the BFRQ via a RACH message or via an uplink beam (e.g., via UCI or PUSCH).

[0253] The beam failure reporting circuit 1743 may include the functionality of a unit for receiving mode indication. For example, the beam failure reporting circuit 1743 may be configured to receive a mode indication for a modified communication mode from a base station (e.g., a gNB). In some aspects, the mode indication may be determined at the base station in response to a BFRQ request. In some examples, the beam failure reporting circuit 1743 may be configured to receive a message from the gNB indicating a switch from FD communication mode to HD communication mode or a switch to restricted FD communication mode for at least one active beam.

[0254] The beam fault reporting circuit 1743 may include the function of a unit for sending a request to resume FD transmission. For example, the beam fault reporting circuit 1743 may be configured to send a message to the gNB to rebuild the FD communication mode.

[0255] Processor 1704 may include communication mode modification circuitry 1744 (e.g., beam control circuitry) configured to perform communication mode modification-related operations discussed herein (e.g., Figure 16 (Communication mode modification operation). The communication mode modification circuit 1744 can be configured to execute the communication mode modification software 1754 included on the computer-readable medium 1706 to perform one or more of the functions described herein.

[0256] The communication mode modification circuit 1744 may include the functionality of a unit for switching operating modes (e.g., switching from one communication mode to another). For example, the communication mode modification circuit 1744 may be configured to switch to a half-duplex mode or a different FD mode (e.g., by selecting a different beam). As another example, the communication mode modification circuit 1744 may be configured to switch from an FD communication mode to an HD communication mode and / or to a restricted FD communication mode for at least one active beam. In some examples, the communication mode modification circuit 1744 may be configured to switch from an FD communication mode to a modified communication mode after receiving a mode indication. The modified communication mode may include at least one of a half-duplex (HD) communication mode or a restricted FD communication mode for at least one active beam.

[0257] Processor 1704 may include beam measurement and recovery circuitry 1745, which is configured to perform beam measurement and recovery related operations discussed herein (e.g., Figure 14 (and / or 15 beam measurement and recovery operations). The beam measurement and recovery circuit 1745 can be configured to execute the beam measurement and recovery software 1755 included on the computer-readable medium 1706 to perform one or more of the functions described herein.

[0258] The beam measurement and recovery circuit 1745 may include the functionality of a unit for selecting at least one beam. For example, the beam measurement and recovery circuit 1745 may be configured to select a UL / DL beam pair for FD communication.

[0259] The beam measurement and recovery circuit 1745 may include functionality for identifying candidate beam pairs. For example, the beam measurement and recovery circuit 1745 may be configured to identify new DL / DL beam pairs to recover the FD transmission mode.

[0260] The beam measurement and recovery circuit 1745 may include the functionality of a unit for sending a request to restore the FD transmission mode. For example, the beam measurement and recovery circuit 1745 may be configured to send a message to the gNB to rebuild the FD communication mode. The message may include an indication of one or more new target beam pair candidates identified by the UE.

[0261] The beam measurement and recovery circuit 1745 may include the function of receiving an indication of a beam pair to be used in FD communication mode. For example, the beam measurement and recovery circuit 1745 may be configured to receive an indication from the gNB of a DL / UL beam pair for FD communication with the gNB.

[0262] Figure 18 This is a flowchart illustrating an example full-duplex communication method 1800 according to some aspects. As described below, some or all of the illustrated features may be omitted in specific implementations within the scope of this disclosure, and some illustrated features may be unnecessary for all example implementations. In some examples, method 1800 may be... Figure 17 The method is executed by UE 1700 as shown. In some examples, method 1800 may be executed by any suitable means or unit for performing the functions or algorithms described below.

[0263] At block 1802, the user equipment can receive uplink transmissions sent by that user equipment. In some examples, beam fault detection circuitry 1742 cooperates with communication and processing circuitry 1741 and transceiver 1710, such as... Figure 17 The shown and described unit can be provided for receiving uplink transmissions sent by a user equipment.

[0264] At block 1804, when the user equipment is able to communicate with the base station via the uplink beam, it can send a beam fault indication to the base station via the uplink channel of the uplink beam. The beam fault indication identifies a beam fault in full-duplex communication, and the beam fault is due to interference from the uplink transmission. In some examples, the beam fault reporting circuit 1743 cooperates with the communication and processing circuit 1741 and the transceiver 1710, such as... Figure 17The shown and described unit can be provided for the following operation: when the user equipment is able to communicate with the base station via the uplink beam, it sends a beam fault indication to the base station via the uplink channel of the uplink beam.

[0265] In some examples, interference from uplink transmissions may include self-interference from user equipment measured by an Interference Measurement Resource (IMR) configured in a Radio Resource Control (RRC) Radio Link Monitoring Reference Signal (RLM-RS) configuration for beam fault detection. In some examples, the IMR carries a Sounding Reference Signal (SRS) or Demodulation Reference Signal (DMRS) transmitted from the uplink beam to the downlink beam.

[0266] In some examples, the beam fault indicator indicates that the beam fault is for FD transmissions with the base station. In some examples, the beam fault indicator indicates a beam fault recovery request (BFRQ) for full-duplex communication.

[0267] In some examples, the beam fault indicator indicates a fault in all active beams of the user equipment. In some examples, the beam fault indicator indicates a fault in at least one active beam of the user equipment. In some examples, the beam fault indicator may include an identifier for at least one faulty beam.

[0268] In some examples, a user equipment (UE) can send a beam fault indication to a base station via an uplink control channel. In some examples, to send a beam fault indication to a base station via an uplink channel, the UE can send uplink control information (UCI) or transmit a medium access control-control unit (MAC-CE) via the physical uplink shared channel (PUSCH). In some examples, to send a beam fault indication to a base station via an uplink channel, the UE can determine whether it is able to communicate with the base station via the uplink beam.

[0269] In some examples, the user equipment may measure at least one downlink reference signal, measure at least one uplink reference signal, derive at least one quality parameter from the at least one downlink reference signal and the at least one uplink reference signal, and compare the at least one quality parameter with a threshold. In some examples, the user equipment may generate a beam fault indication based on the comparison (contrast) between the at least one quality parameter and the threshold.

[0270] Figure 19 This is a flowchart illustrating an example full-duplex communication method 1900 according to some aspects. As described below, some or all of the illustrated features may be omitted in specific implementations within the scope of this disclosure, and some illustrated features may be unnecessary for all example implementations. In some examples, method 1900 may be... Figure 17The method is executed by UE 1700 as shown. In some examples, method 1900 may be executed by any suitable means or unit for performing the functions or algorithms described below.

[0271] At block 1902, the user equipment can receive uplink transmissions sent by that user equipment. In some examples, beam fault detection circuitry 1742 cooperates with communication and processing circuitry 1741 and transceiver 1710, such as... Figure 17 The shown and described unit can be provided for receiving uplink transmissions sent by a user equipment.

[0272] At block 1904, the user equipment (UE) can send a beam fault indication via a random access channel (RACH) message to the base station when the UE cannot communicate with the base station via the uplink beam or when the beam fault is due to downlink quality degradation. This beam fault indicates a beam fault in full-duplex communication caused by interference from the uplink transmission. In some examples, the beam fault reporting circuit 1743 cooperates with the communication and processing circuit 1741 and the transceiver 1710, such as... Figure 17 The shown and described unit may be provided for the following operation: when a user equipment is unable to communicate with a base station via an uplink beam or when the beam failure is due to a downlink quality degradation, sending a beam failure indication identifying a beam failure in full-duplex communication to the base station via a random access channel (RACH) message.

[0273] In some examples, interference from uplink transmissions may include self-interference from user equipment measured by the Interference Measurement Resource (IMR) configured in the Radio Resource Control (RRC) Radio Link Monitoring Reference Signal (RLM-RS) configuration for beam fault detection.

[0274] In some examples, the beam fault indicator indicates that the beam fault is affecting full-duplex transmission with the base station. In other examples, the beam fault indicator indicates a beam fault recovery request (BFRQ) for full-duplex communication.

[0275] In some examples, the beam fault indicator indicates a fault in all active beams of the user equipment. In some examples, the beam fault indicator indicates a fault in at least one active beam of the user equipment. In some examples, the beam fault indicator may include an identifier for at least one faulty beam.

[0276] In some examples, in order to send a beam fault indication to the base station via a RACH message, the user equipment can select from two preambles reserved for it to specify a first preamble for beam faults caused by full-duplex self-interference; and send the first preamble as a beam fault recovery request (BFRQ). In some examples, the two preambles reserved for the user equipment may include a second preamble specified for beam faults caused by downlink quality degradation.

[0277] In some examples, in order to send a beam fault indication to the base station via a RACH message, the user equipment can select from two preamble sets a first preamble set designated for beam faults caused by full-duplex self-interference, select a preamble from the first preamble set, and send the preamble as a beam fault recovery request (BFRQ). In some examples, the two preamble sets may include a second preamble set designated for beam faults caused by downlink quality degradation.

[0278] In some examples, the user equipment (UE) can identify uplink and downlink beam pairs to restore full-duplex communication after a RACH procedure for beam failure recovery, where the RACH procedure is a four-step RACH or a two-step RACH. In some examples, to identify the uplink and downlink beam pairs, the UE can transmit a first RACH preamble; transmit a repeated second RACH preamble as the first RACH preamble; receive the first RACH preamble via a first receive beam of the UE; receive the second RACH preamble via a second receive beam of the UE; and select either the first or second receive beam to pair with the identified beam to form the uplink and downlink beam pairs. In some examples, to select either the first or second receive beam to pair with the identified beam that transmitted the first and second RACH preambles, the UE can determine whether the first or second receive beam is associated with lower cross-beam self-interference of the UE.

[0279] In some examples, the user equipment (UE) can identify a first uplink and downlink beam pair with the lowest cross-beam reference signal received power among multiple candidate uplink and downlink beam pairs; and send an indication of the first uplink and downlink beam pair to the base station. In some examples, the UE can send the indication of the first uplink and downlink beam pair via the payload or uplink signaling of Msg3 in a four-step RACH process, MsgA in a two-step RACH process. In some examples, the indication of the first uplink and downlink beam pair may include a synchronization signaling block identifier for the first uplink and downlink beam pair.

[0280] In some examples, the user equipment may measure at least one downlink reference signal, measure at least one uplink reference signal, derive at least one quality parameter from the at least one downlink reference signal and the at least one uplink reference signal, and compare the at least one quality parameter with a threshold. In some examples, the user equipment may generate a beam fault indication based on the comparison (contrast) between the at least one quality parameter and the threshold.

[0281] Figure 20 This is a flowchart illustrating an example wireless communication method 2000 according to some aspects. As described below, some or all illustrated features may be omitted in certain implementations within the scope of this disclosure, and some illustrated features may be unnecessary for all example implementations. In some examples, method 2000 may be... Figure 17 The method is executed by the UE 1700 shown. In some examples, method 2000 can be executed by any suitable means or unit for performing the functions or algorithms described below.

[0282] At block 2002, the user equipment can identify beam faults in FD communication caused by interference from the uplink transmission of the user equipment. In some examples, the beam fault detection circuit 1742 cooperates with the communication and processing circuit 1741 and the transceiver 1710, such as... Figure 17 The shown and described unit can be provided for the following operation: identifying beam faults in FD communication caused by interference from uplink transmissions from user equipment.

[0283] In some examples, interference from uplink transmissions from user equipment (UE) may include self-interference from UE measured by an Interference Measurement Resource (IMR) configured in a Radio Resource Control (RRC) Radio Link Monitoring Reference Signal (RLM-RS) configuration for beam fault detection. In some examples, the IMR carries a Sounding Reference Signal (SRS) or Demodulation Reference Signal (DMRS) transmitted from the uplink beam to the downlink beam.

[0284] At block 2004, the user equipment can generate a beam fault indication for beam faults. In some examples, the above is combined with... Figure 17 The beam fault reporting circuit 1743 shown and described can provide a unit for generating a beam fault indication for beam faults.

[0285] In some examples, the beam fault indicator indicates that the beam fault is for FD transmissions with the base station. In some examples, the beam fault indicator indicates a beam fault recovery request (BFRQ) for FD communication.

[0286] In some examples, the beam fault indicator indicates a beam fault in all active beams of the user equipment. In some examples, the beam fault indicator indicates a beam fault in at least one active beam of the user equipment. In some examples, the beam fault indicator may include an identifier for at least one faulty beam.

[0287] At block 2006, when the user equipment is able to communicate with the base station via the uplink beam, it can send a beam fault indication to the base station via the uplink channel of the uplink beam. In some examples, the beam fault reporting circuit 1743, together with the communication and processing circuit 1741 and the transceiver 1710, as described above... Figure 17 The shown and described unit may be provided for the following operation: when the user equipment is able to communicate with the base station via the uplink beam, sending a beam fault indication to the base station via the uplink channel of the uplink beam.

[0288] In some examples, a user equipment (UE) can send a beam fault indication to a base station via an uplink control channel. In some examples, to send a beam fault indication to a base station via an uplink channel, the UE can send uplink control information (UCI) or transmit a medium access control-control unit (MAC-CE) via the physical uplink shared channel (PUSCH). In some examples, to send a beam fault indication to a base station via an uplink channel, the UE can determine whether it is able to communicate with the base station via the uplink beam.

[0289] In some examples, the user equipment may measure at least one downlink reference signal, measure at least one uplink reference signal, derive at least one quality parameter from the at least one downlink reference signal and the at least one uplink reference signal, and compare the at least one quality parameter with a threshold. In some examples, the user equipment may generate a beam fault indication based on the comparison (contrast) between the at least one quality parameter and the threshold.

[0290] Figure 21 This is a flowchart illustrating an example wireless communication method 2100 according to some aspects. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of this disclosure, and some illustrated features may be unnecessary for all example implementations. In some examples, method 2100 may be... Figure 17 The method is executed by the UE 1700 shown. In some examples, method 2100 can be executed by any suitable means or unit for performing the functions or algorithms described below.

[0291] At block 2102, the user equipment can identify beam faults in FD communication caused by interference from uplink transmissions from the user equipment or by downlink quality degradation. In some examples, the beam fault detection circuit 1742 cooperates with the communication and processing circuit 1741 and the transceiver 1710, such as... Figure 17 The shown and described unit can be provided for the following operation: identifying beam faults in FD communication caused by interference from uplink transmissions from user equipment or by downlink quality degradation.

[0292] In some examples, interference from uplink transmissions from user equipment may include self-interference from user equipment as measured by interference measurement resources (IMR) configured in a Radio Resource Control (RRC) Radio Link Monitoring Reference Signal (RLM-RS) configuration for beam fault detection.

[0293] At block 2104, the user equipment can generate a beam fault indication for beam faults. In some examples, Figure 17 The beam fault detection circuit 1742 shown and described can provide a unit for generating a beam fault indication for beam faults.

[0294] In some examples, the beam fault indicator indicates that the beam fault is for FD transmissions with the base station. In some examples, the beam fault indicator indicates a beam fault recovery request (BFRQ) for FD communication.

[0295] In some examples, the beam fault indicator indicates a beam fault in all active beams of the user equipment. In some examples, the beam fault indicator indicates a beam fault in at least one active beam of the user equipment. In some examples, the beam fault indicator may include an identifier for at least one faulty beam.

[0296] At block 2106, the user equipment can send a beam fault indication to the base station via a random access channel (RACH) message when the user equipment cannot communicate with the base station via the uplink beam or when the beam fault is due to downlink quality degradation. In some examples, the beam fault reporting circuit 1743 cooperates with the communication and processing circuit 1741 and the transceiver 1710, such as... Figure 17 The shown and described unit may be provided for sending a beam failure indication to the base station via a random access channel (RACH) message when a user equipment is unable to communicate with the base station via the uplink beam or when the beam failure is due to downlink quality degradation. In some examples, the user equipment may determine whether it is able to communicate with the base station via the uplink beam.

[0297] In some examples, in order to send a beam fault indication to the base station via a RACH message, the user equipment can select from two preambles reserved for it to specify a first preamble for beam faults caused by FD self-interference; and send the first preamble as a beam fault recovery request (BFRQ). In some examples, the two preambles reserved for the user equipment may include a second preamble specified for beam faults caused by downlink quality degradation.

[0298] In some examples, in order to send a beam fault indication to the base station via a RACH message, the user equipment may select from two preamble sets a first preamble set designated for beam faults caused by full-duplex (FD) self-interference, select a preamble from the first preamble set, and send the preamble as a beam fault recovery request (BFRQ). In some examples, the two preamble sets may include a second preamble set designated for beam faults caused by downlink quality degradation.

[0299] In some examples, the user equipment (UE) can identify uplink and downlink beam pairs to restore FD communication after a RACH procedure for beam failure recovery, where the RACH procedure is a four-step RACH or a two-step RACH. In some examples, to identify the uplink and downlink beam pairs, the UE can transmit a first RACH preamble; transmit a repeated second RACH preamble as the first RACH preamble; receive the first RACH preamble via a first receive beam of the UE; receive the second RACH preamble via a second receive beam of the UE; and select either the first or second receive beam to pair with the identified beam that transmitted the first and second RACH preambles as the identified uplink and downlink beam pairs. In some examples, to select either the first or second receive beam to pair with the identified beam that transmitted the first and second RACH preambles, the UE can determine whether the first or second receive beam is associated with lower cross-beam self-interference of the UE.

[0300] In some examples, the user equipment (UE) can identify a first uplink and downlink beam pair with the lowest cross-beam reference signal received power among multiple candidate uplink and downlink beam pairs; and send an indication of the first uplink and downlink beam pair to the base station. In some examples, the UE can send the indication of the first uplink and downlink beam pair via the payload or uplink signaling of Msg3 in a four-step RACH process, MsgA in a two-step RACH process. In some examples, the indication of the first uplink and downlink beam pair may include a synchronization signaling block identifier for the first uplink and downlink beam pair.

[0301] In some examples, the user equipment may measure at least one downlink reference signal, measure at least one uplink reference signal, derive at least one quality parameter from the at least one downlink reference signal and the at least one uplink reference signal, and compare the at least one quality parameter with a threshold. In some examples, the user equipment may generate a beam fault indication based on the comparison (contrast) between the at least one quality parameter and the threshold.

[0302] Figure 22 This is a flowchart illustrating an example wireless communication method 2200 according to some aspects. As described below, some or all illustrated features may be omitted in certain implementations within the scope of this disclosure, and some illustrated features may be unnecessary for all example implementations. In some examples, method 2200 may be... Figure 17 The method is executed by the UE 1700 shown. In some examples, method 2200 can be executed by any suitable means or unit for performing the functions or algorithms described below.

[0303] At block 2202, the user equipment can send a beam fault recovery request (BFRQ) signal to the base station during full-duplex (FD) communication mode with the base station, wherein the BFRQ signal indicates that at least one beam has failed. In some examples, the beam fault reporting circuit 1743 cooperates with the communication and processing circuit 1741 and the transceiver 1710, such as... Figure 17 The shown and described unit can be provided for the following operation: sending a beam fault recovery request (BFRQ) signal to the base station during full-duplex (FD) communication mode with the base station.

[0304] At block 2204, the user equipment can receive a mode indication of the modified communication mode from the base station. In some examples, the beam fault reporting circuit 1743 cooperates with the communication and processing circuit 1741 and the transceiver 1710, such as... Figure 17 The shown and described unit can be provided for the following operation: receiving a mode indication of a modified communication mode from a base station.

[0305] At block 2206, the user equipment can switch from an FD communication mode to a modified communication mode based on a mode indication. The modified communication mode may include at least one of a half-duplex (HD) communication mode for at least one beam or a restricted FD communication mode. In some examples, the communication mode modification circuitry 1744 cooperates with the communication and processing circuitry 1741 and the transceiver 1710, such as... Figure 17 The shown and described unit can be provided for the following operation: switching from FD communication mode to a modified communication mode based on mode indication.

[0306] In some examples, HD communication mode may include time-division multiplexing (TDM) transmission of at least one beam for at least one of the uplink (UL) or downlink (DL) transmissions between the base station and the user equipment. Switching to HD communication mode can be performed for all active beams or for at least one failed active beam. In the latter case, the user equipment can continue to use FD communication mode for at least one active beam that is currently in operation. The at least one beam may be an active beam selected by the base station for at least one of the data and control channel transmissions.

[0307] In some examples, during the transition period from FD communication mode to HD communication mode, the user equipment can determine whether to terminate the DL beam or the UL beam based on predetermined criteria. These predetermined criteria may include one or more of the Physical Layer (PHY) priority field or UE auxiliary information. Furthermore, the PHY priority field may include a priority ordering or priority indication for Ultra Reliable Low Latency Communication (URLLC) services with low latency requirements. Further, the UE auxiliary information may include at least one of the Maximum Permissible Exposure (MPE) limit or thermal balance differences between the transmit / UL and receive / DL antenna arrays.

[0308] In some examples, the user equipment can receive an indication of termination of DL or UL transmission from the base station. This indication can be sent in one or more Physical Downlink Control Channel (PDCCH) fields or time slots.

[0309] In some examples, the user equipment (UE) can select one or more beams for UL or DL ​​transmission in HD communication mode based on one or more predetermined conditions. Selecting one or more beams for UL or DL ​​transmission in HD communication mode can be based on one or more predetermined conditions, including using the same DL and UL beams as the FD transmission mode for both DL and UL transmissions; or by selecting the strongest beam with the highest RSRP or SNR for both UL and DL transmissions; or by selecting the strongest beam from the available DL and UL transmission beams for both DL and UL transmissions. Furthermore, the UE can receive the selection of one or more beams for HD communication mode from the base station. The UE can also send at least one beam recommendation to the base station, wherein the UE receives the selection of one or more beams for HD communication mode from the base station in part based on the at least one beam recommendation sent from the UE.

[0310] In some examples, during restricted FD communication mode, when the UL service priority is below a predetermined threshold, the user equipment can receive signaling from the base station regarding reducing the UL modulation and coding scheme (MCS). On the other hand, for restricted FD communication mode, when the UL service priority is below a predetermined threshold, the user equipment can receive signaling from the base station regarding reducing the UL modulation and coding scheme (MCS). In still other aspects, for restricted FD communication mode, when the UL service priority is below a first predetermined threshold, the user equipment can receive signaling from the base station regarding reducing the UL transmit power.

[0311] In some examples, the user equipment (UE) can receive signaling from the base station regarding the repeated use of UL transmissions, and then repeat the UL transmissions based on the received signaling. Restricted FD communication may also include identifying a faulty FD communication mode beamp pair and then replacing it with a backup FD communication mode beamp pair. Furthermore, the restricted FD communication mode may include maintaining the UL power level if the UL priority is greater than a second predetermined threshold. Additionally, when the UL priority is greater than the second predetermined threshold, the UE can select to replace the DL beam. In some examples, when the UL priority is greater than the second predetermined threshold, the UE can switch to HD communication mode for at least one beam. Additionally, the restricted FD communication mode may include utilizing the less frequency resource overlap between DL and UL transmissions, or adding a guard band between the DL and UL bands for subband FD communication. On the other hand, to switch to the restricted FD communication mode, the UE can receive signaling from the base station and / or send a recommendation to the base station via RRC / MAC-CE / DCI.

[0312] Figure 23 This is a flowchart illustrating an example wireless communication method 2300 according to some aspects. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of this disclosure, and some illustrated features may be unnecessary for all example implementations. In some examples, method 2300 may be... Figure 17 The method is executed by the UE 1700 shown. In some examples, method 2300 can be executed by any suitable means or unit for performing the functions or algorithms described below.

[0313] At block 2302, the user equipment can identify one or more new target beam pair candidates during beam fault detection and recovery. In some examples, beam measurement and recovery circuitry 1745 cooperates with communication and processing circuitry 1741 and transceiver 1710, such as... Figure 17 The shown and described unit can be provided for the following operation: identifying one or more new target beam pair candidates during beam fault detection and recovery.

[0314] At block 2304, the user equipment can send a request to the scheduling entity to resume full-duplex transmission mode, wherein the request may include one or more identified new target beam pair candidates. In some examples, beam failure reporting circuitry 1743 cooperates with communication and processing circuitry 1741 and transceiver 1710, such as... Figure 17 The unit shown and described can be provided for the following operation: sending a request to the scheduling entity to resume full-duplex transmission mode.

[0315] At block 2306, the user equipment can, in response to sending one or more new target beampair candidates, receive new downlink and uplink beampairs to restore full-duplex transmission mode from the scheduling entity. In some examples, beam measurement and recovery circuitry 1745 cooperates with communication and processing circuitry 1741 and transceiver 1710, such as... Figure 17 The shown and described unit can be provided for the following operation: in response to sending one or more new target beam pair candidates, receiving new downlink and uplink beam pairs from the scheduling entity to restore full-duplex transmission mode.

[0316] In some examples, to identify one or more new target beam pair candidates, a user equipment (UE) can identify one or more new downlink beams paired with one or more current uplink beams. The following aspects may be applicable in this case: In some examples, to identify one or more new target beam pair candidates, the UE can measure downlink channel quality to determine self-interference from one of the one or more uplink beams to one of the one or more new downlink beams. In some examples, downlink channel quality and self-interference measurements may include signal-to-interference-to-noise ratio (SINR). In some examples, to identify one or more new target beam pair candidates, the UE can use at least one channel measurement resource (CMR) to measure the channel quality of each of the identified one or more new downlink beams. In some examples, to identify one or more new target beam pair candidates, the UE can add at least one interference measurement resource (IMR) to measure cross-beam interference from each of the one or more current uplink beams to each of the identified one or more new downlink beams. In some examples, to identify one or more new candidate target beam pairs, the UE can calculate SINR based on CMR and IMR.

[0317] In some examples, to identify one or more new target beam pair candidates, the user equipment (UE) can identify one or more new uplink beam candidates paired with one or more current downlink beams. The following aspects may be applicable in this case: In some examples, to identify one or more new target beam pair candidates, the UE can measure downlink channel quality and measure self-interference from one of the one or more new uplink beams to one of the one or more current downlink beams. In some examples, downlink channel quality and self-interference may include signal-to-interference-and-noise ratio (SINR). In some examples, to identify one or more new target beam pair candidates, the UE can use at least one channel measurement resource (CMR) to measure the channel quality of each of the one or more current downlink beams. In some examples, to identify one or more new target beam pair candidates, the UE can add at least one interference measurement resource (IMR) to measure cross-beam interference from each of the one or more new uplink beams to each of the one or more current downlink beams. In some examples, to identify one or more new candidate target beam pairs, the UE can calculate SINR based on CMR and IMR.

[0318] In some examples, to identify one or more new target beam pair candidates, the user equipment (UE) can identify one or more new downlink beams paired with one or more current uplink beams if the uplink reference signal power is stronger than the downlink reference signal power; and identify one or more new uplink beam candidates paired with one or more current downlink beams if the downlink reference signal power is stronger than the uplink reference signal power. In some examples, the UE can access a lookup table of candidate beam pairs to identify one or more new target beam pair candidates. In some examples, the UE can identify one or more new target beam pair candidates during beam fault detection and recovery before transmitting a beam fault recovery request (BFRQ) and send a BFRQ associated with the identifier of one or more new target beam pair candidates. In some examples, if the beam fault is due to DL quality degradation or self-interference from an inactive UL, the UE can complete the random access channel (RACH) procedure before resuming FD transmission mode. In some examples, if the beam fault is due to self-interference from an active uplink, the UE can switch to half-duplex mode or fallback FD mode before the recovery process.

[0319] In one configuration, UE 1700 includes: a unit for receiving uplink transmissions sent by a user equipment; and a unit for sending a beam fault indication identifying a beam fault in FD communication via an uplink channel of the uplink beam when the user equipment cannot communicate with the base station via the uplink beam, wherein the beam fault is due to interference from the uplink transmission. In another configuration, UE 1700 includes: a unit for receiving uplink transmissions sent by a user equipment; and a unit for sending a beam fault indication identifying a beam fault in FD communication via a random access channel (RACH) message when the user equipment cannot communicate with the base station via the uplink beam or when the beam fault is due to downlink quality degradation, wherein the beam fault is due to interference from the uplink transmission. In one aspect, the above-mentioned unit may be... Figure 17 The processor 1704 shown is configured to perform the functions listed by the above-described units (e.g., as discussed above). Alternatively, the aforementioned units may be circuits or any devices configured to perform the functions described above.

[0320] Of course, the circuitry included in processor 1704 in the above examples is provided only as an example, and other means for performing the described functions may include, but are not limited to, instructions stored in computer-readable medium 1706, or in Figure 1 , Figure 2 , Figure 4 , Figure 5 , Figure 7A , Figure 7B , Figure 7C , Figure 9 , Figure 13 , Figure 16 and Figure 17 Any other suitable device or unit described in any of the figures, and utilizing, for example, those described herein. Figures 18-23 The described method and / or algorithm.

[0321] Figure 24 This is a conceptual diagram illustrating an example hardware implementation of a base station (BS) 2400 using a processing system 2414. In some implementations, the BS 2400 may correspond to... Figure 1 , Figure 2 , Figure 4 , Figure 5 , Figure 7A , Figure 7B , Figure 7C , Figure 9 , Figure 13 and Figure 16 Any BS (e.g., gNB) or scheduling entity shown in any of the diagrams.

[0322] According to various aspects of this disclosure, the processing system 2414 can be used to implement elements, any part of elements, or any combination of elements. The processing system may include one or more processors 2404. The processing system 2414 is substantially compatible with... Figure 17 The processing system 1714 shown herein is identical and includes: a bus interface 2408, a bus 2402, a memory 2405, a processor 2404, a computer-readable medium 2406, a transceiver 2410, and an antenna array 2420. The memory 2405 may store beam information 2415 used by the processor 2404 for the communication operations discussed herein. Furthermore, the BS 2400 may include an interface 2430 (e.g., a network interface) providing a unit for communicating with at least one other device within the core network and with at least one radio access network.

[0323] The BS 2400 can be configured to perform any one or more of the operations described herein (e.g., as combined above). Figures 1-16 The description and the following in combination Figures 25-28 (As described). In some aspects of this disclosure, the processor 2404 used in the BS2400 may include circuitry configured for various functions.

[0324] Processor 2404 can be configured to generate, schedule, and modify resource allocations or permissions for time-frequency resources (e.g., a set of one or more resource elements). For example, processor 2404 can schedule visual-frequency resources within multiple time-division duplex (TDD) and / or frequency-division duplex (FDD) subframes, time slots, and / or micro-time slots to carry user data services and / or control information to multiple UEs and / or carry user data services and / or control information from multiple UEs. Processor 2404 can be configured to schedule resources for downlink signaling transmission and / or resources for uplink signaling transmission.

[0325] Processor 2404 can be configured to schedule resources for downlink reference signal (e.g., SSB or CSI-RS) transmission on multiple downlink beams for downlink beam scanning, based on the number of selected downlink reference signal resources. In some examples, the scheduled resources may be CMRs.

[0326] Processor 2404 can be configured to schedule resources for uplink signal transmission. In some examples, resources may be associated with one or more uplink transmit beams and one or more corresponding receive beams applied to the uplink signal (e.g., based on uplink BPL). Processor 2404 can be configured to schedule resources for uplink transmission of uplink reference signals (e.g., SRS) on multiple uplink beams used for uplink beam scanning. In some examples, the scheduled resources may be IMR.

[0327] In some aspects of this disclosure, processor 2404 may include communication and processing circuitry 2441. Communication and processing circuitry 2441 may be configured to communicate with a UE. Communication and processing circuitry 2441 may include one or more hardware components providing a physical structure for performing various communication-related processes (e.g., signal reception and / or signal transmission) as described herein. Communication and processing circuitry 2441 may also include one or more hardware components providing a physical structure for performing various signal processing-related processes (e.g., processing received signals and / or processing signals for transmission) as described herein. Communication and processing circuitry 2441 may also be configured to execute communication and processing software 2451 included on computer-readable medium 2406 to implement one or more of the functions described herein.

[0328] In some examples, the communication and processing circuitry 2441 may be configured to receive and process uplink beamforming signals at millimeter-wave frequencies or frequencies below 6 GHz via transceiver 2410 and antenna array 2420. For example, the communication and processing circuitry 2441 may be configured to receive a corresponding reference signal (e.g., SRS or DMRS) from the UE on each of a plurality of uplink beams during uplink beam scanning.

[0329] In some examples, the communication and processing circuitry 2441 may also be configured to generate and transmit downlink beamforming signals at millimeter-wave frequencies or frequencies below 6 GHz via transceiver 2410 and antenna array 2420. For example, the communication and processing circuitry 2441 may be configured to transmit a corresponding downlink reference signal (e.g., SSB or CSI-RS) to the UE via at least one first antenna panel of antenna array 2420 on each of a plurality of downlink beams during downlink beam scanning. The communication and processing circuitry 2441 may also be configured to receive beam measurement reports from the UE.

[0330] The communication and processing circuitry 2441 can also be configured to control the antenna array 2420 and transceiver 2410 to generate multiple downlink transmit beams during downlink beam scanning. The communication and processing circuitry 2441 can also be configured to receive beam measurement reports from the UE. The communication and processing circuitry 2441 can also be configured to identify one or more selected uplink beams based on the beam measurement results. In some examples, the communication and processing circuitry 2441 can be configured to compare the corresponding RSRP (or other beam measurement) measured on each downlink receive beam for each serving downlink transmit beam to identify the serving downlink receive beam; and further identify the serving downlink receive beam as a selected uplink transmit beam. Each serving downlink receive beam may have the highest measured RSRP (or other beam measurement result) for one of the downlink transmit beams.

[0331] The communication and processing circuitry 2441 can be configured to receive one or more uplink transmit beams during uplink beam scanning. Each uplink transmit beam may carry an uplink reference signal (e.g., SRS) for measurement by the communication and processing circuitry 2441. The communication and processing circuitry 2441 can also be configured to obtain multiple beam measurements for each of the multiple uplink receive beams of the antenna array 2420 for each uplink transmit beam. The communication and processing circuitry 2441 can also be configured to select a chosen uplink transmit beam and a corresponding uplink receive beam forming each uplink BPL based on the uplink beam measurements.

[0332] On the other hand, note that antenna array 2430 can be configured by processor 2404 (and memory 2405 or medium 2406) to implement a first antenna panel and a second antenna panel. Furthermore, processor 2404 (and memory 2405 or medium 2406) can be configured to: use the first antenna panel to transmit a first beam (e.g., a DL transmit beam for FD communication) and use the second antenna panel to receive a second beam (e.g., a UL receive beam for FD communication). The second antenna panel can be used by processor 2404 to measure the self-interference of BS 2400 for FD communication.

[0333] In some implementations where communication involves receiving information, communication and processing circuitry 2441 may obtain information from components of BS 2400 (e.g., from transceiver 2410 receiving information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, communication and processing circuitry 2441 may output information to another component of processor 2404, memory 2405, or bus interface 2408. In some examples, communication and processing circuitry 2441 may receive one or more of the following: signals, messages, other information, or any combination thereof. In some examples, communication and processing circuitry 2441 may receive information via one or more channels. In some examples, communication and processing circuitry 2441 may include the functionality of units for receiving information. In some examples, communication and processing circuitry 2441 may include the functionality of units for decoding information.

[0334] In some embodiments where communication involves sending (e.g., transmitting) information, communication and processing circuitry 2441 may acquire information (e.g., from another component of processor 2404, memory 2405, or bus interface 2408), process (e.g., encode) the information, and output the processed information. For example, communication and processing circuitry 2441 may output information to transceiver 2410 (e.g., which transmits information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium). In some examples, communication and processing circuitry 2441 may transmit one or more of the following: signals, messages, other information, or any combination thereof. In some examples, communication and processing circuitry 2441 may transmit information via one or more channels. In some examples, communication and processing circuitry 2441 may include the functionality of units for performing transmission (e.g., units for performing transmission). In some examples, communication and processing circuitry 2441 may include the functionality of units for performing encoding.

[0335] In some implementations, the communication and processing circuitry 2441 may include the functionality of a unit for transmitting at least one downlink reference signal. For example, the communication and processing circuitry 2441 may be configured to broadcast an SSB and / or CSI-RS on at least one designated resource.

[0336] Processor 2404 may include beam fault processing circuitry 2442 (e.g., beam fault reporting circuitry) configured to perform beam fault processing related operations discussed herein (e.g. Figure 9 (Beam fault indication operation). The beam fault handling circuit 2442 can be configured to execute beam fault handling software 2452 included on the computer-readable medium 2406 to perform one or more of the functions described herein.

[0337] The beam fault handling circuit 2442 may include the functionality of a unit for receiving beam fault indications. For example, the beam fault handling circuit 2442 may be configured to receive a BFRQ sent by the UE via an uplink beam (e.g., via UCI or PUSCH) or via a RACH message. The BFRQ may indicate that at least one active beam has failed. The BFRQ may include an identifier for each failed beam. The BFRQ may indicate whether the beam fault is due to downlink quality degradation or self-interference.

[0338] The beam failure handling circuit 2442 may include the functionality of a unit for transmission mode indication. For example, the beam failure handling circuit 2442 may be configured to send a message to the UE indicating a switch from FD communication mode to HD communication mode or a switch to restricted FD communication mode for at least one active beam.

[0339] The beam fault handling circuit 2442 may include the functionality of a unit for receiving a request to resume FD transmission. For example, the beam fault handling circuit 2442 may be configured to receive a message from the UE to rebuild the FD communication mode.

[0340] Processor 2404 may include beam selection circuitry 2443, which is configured to perform beam selection-related operations discussed herein (e.g., Figure 14 and / or Figure 15 (Beam selection operation). Beam selection circuit 2443 can be configured to execute beam selection software 2453 included on computer-readable medium 2406 to perform one or more of the functions described herein.

[0341] The beam selection circuit 2443 may include the function of selecting at least one beam. For example, the beam selection circuit 2443 may be configured to select a UL / DL beam pair for FD communication.

[0342] The beam selection circuit 2443 may include the functionality of a unit for receiving beam pair candidates. For example, the beam selection circuit 2443 may be configured to receive one or more new target beam pair candidates identified by the UE.

[0343] Processor 2404 may include communication mode modification circuitry 2444, which is configured to perform communication mode modification-related operations discussed herein (e.g., Figure 16 (Communication mode modification operation). The communication mode modification circuit 2444 can be configured to execute the communication mode modification software 2454 included on the computer-readable medium 2406 to perform one or more of the functions described herein.

[0344] The communication mode modification circuit 2444 (e.g., beam control circuitry) may include the functionality of a unit for switching operating modes (e.g., switching from one communication mode to another). For example, the communication mode modification circuit 2444 may be configured to switch to a half-duplex mode or a different FD mode (e.g., by selecting a different beam). As another example, the communication mode modification circuit 2444 may be configured to switch from an FD communication mode to an HD communication mode and / or to a restricted FD communication mode for at least one active beam. The communication mode modification circuit 2444 may be configured to perform operations such as switching to a temporary HD, hybrid HD, or restricted FD communication mode, as discussed herein. The communication mode modification circuit 2444 may be configured to determine when to select among various publicly disclosed communication modes, and to initiate and / or control the communication and processing circuitry 2441 for power back-off and beam or beam pair reselection, as described herein.

[0345] Processor 2404 may include beam measurement and recovery circuitry 2445, which is configured to perform beam measurement and recovery related operations discussed herein (e.g., Figure 14 (and / or 15 beam measurement and recovery operations). The beam measurement and recovery circuit 2445 can be configured to execute the beam measurement and recovery software 2455 included on the computer-readable medium 2406 to perform one or more of the functions described herein.

[0346] The beam measurement and recovery circuit 2445 may include the function of transmitting an indication of a beam pair to be used in FD communication mode. For example, the beam measurement and recovery circuit 2445 may be configured to process and transmit new DL / DL beam pairs to restore FD transmission mode.

[0347] Figure 25 This is a flowchart illustrating an example wireless communication method 2500 according to some aspects. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of this disclosure, and some illustrated features may be unnecessary for all example implementations. In some examples, method 2500 may be... Figure 24 The method is executed by BS 2400 as shown. In some examples, method 2500 can be executed by any suitable means or unit for performing the functions or algorithms described below.

[0348] At block 2502, the base station can receive a beam fault indication from the user equipment via the uplink channel of the uplink beam, wherein the beam fault indication addresses beam faults in FD communication caused by interference from uplink transmissions from the user equipment. In some examples, the beam fault handling circuit 2442 cooperates with the communication and processing circuit 2441 and the transceiver 2410, such as... Figure 24The shown and described unit can be provided for receiving beam fault indication from user equipment via the uplink channel of the uplink beam.

[0349] In some examples, the beam fault indicator indicates that the beam fault is for FD transmissions with the base station. In some examples, the beam fault indicator indicates a beam fault recovery request (BFRQ) for FD communication.

[0350] In some examples, interference from uplink transmissions from user equipment (UE) may include self-interference from UE measured by an Interference Measurement Resource (IMR) configured in a Radio Resource Control (RRC) Radio Link Monitoring Reference Signal (RLM-RS) configuration for beam fault detection. In some examples, the IMR carries a Sounding Reference Signal (SRS) or Demodulation Reference Signal (DMRS) transmitted from the uplink beam to the downlink beam.

[0351] In some examples, the beam fault indicator indicates a beam fault in all active beams of the user equipment. In some examples, the beam fault indicator indicates a beam fault in at least one active beam of the user equipment. In some examples, the beam fault indicator may include an identifier for at least one faulty beam.

[0352] In some examples, in order to receive beam fault indication, the base station can receive uplink control information (UCI) or receive medium access control-control unit (MAC-CE) via the physical uplink shared channel (PUSCH).

[0353] At block 2504, the base station can switch its operating mode for communicating with user equipment after receiving a beam fault indication. In some examples, the communication mode modification circuit 2444 cooperates with the communication and processing circuit 2441 and the transceiver 2410, such as... Figure 24 The shown and described unit may be provided for switching the operating mode for communicating with user equipment after receiving a beam fault indication. In some examples, the base station may switch to a half-duplex operating mode or switch to a different full-duplex configuration.

[0354] Figure 26 This is a flowchart illustrating an example wireless communication method 2600 according to some aspects. As described below, some or all illustrated features may be omitted in certain implementations within the scope of this disclosure, and some illustrated features may be unnecessary for all example implementations. In some examples, method 2600 may be... Figure 24 The method is executed by BS 2400 as shown. In some examples, method 2600 may be executed by any suitable means or unit for performing the functions or algorithms described below.

[0355] At block 2602, the base station can receive a beam fault indication from the user equipment via a random access channel (RACH) message, wherein the beam fault indication addresses beam faults in FD communication caused by interference from uplink transmissions from the user equipment. In some examples, the beam fault handling circuitry 2442 cooperates with the communication and processing circuitry 2441 and the transceiver 2410, such as... Figure 24 The shown and described unit can be provided for receiving beam fault indication from user equipment via random access channel (RACH) messages.

[0356] In some examples, the beam fault indicator indicates that the beam fault is for FD transmissions with the base station. In some examples, the beam fault indicator indicates a beam fault recovery request (BFRQ) for FD communication.

[0357] In some examples, interference from uplink transmissions from user equipment may include self-interference from user equipment as measured by interference measurement resources (IMR) configured in a Radio Resource Control (RRC) Radio Link Monitoring Reference Signal (RLM-RS) configuration for beam fault detection.

[0358] In some examples, to receive a beam fault indication, the base station may receive a first preamble of two preambles reserved for the user equipment and identify the first preamble as designated for beam faults caused by FD self-interference. In some examples, the two preambles reserved for the user equipment may include a second preamble designated for beam faults caused by downlink quality degradation.

[0359] In some examples, in order to receive a beam fault indication, the base station may receive a first preamble and determine that the first preamble comes from one of two preamble sets specified for a beam fault caused by full-duplex (FD) self-interference. In some examples, the two preamble sets may include a second preamble set specified for a beam fault caused by downlink quality degradation.

[0360] In some examples, the beam fault indicator indicates a beam fault in all active beams of the user equipment. In some examples, the beam fault indicator indicates a beam fault in at least one active beam of the user equipment. In some examples, the beam fault indicator may include an identifier for at least one faulty beam.

[0361] At block 2604, the base station can switch its operating mode for communicating with user equipment after receiving a beam fault indication. In some examples, the communication mode modification circuit 2444 cooperates with the communication and processing circuit 2441 and the transceiver 2410, such as... Figure 24The shown and described unit may be provided for switching the operating mode for communicating with user equipment after receiving a beam fault indication. In some examples, the base station may switch to a half-duplex operating mode or switch to a different full-duplex configuration.

[0362] In some examples, the base station can receive indications of uplink and downlink beam pairs to resume FD communication after a RACH procedure for beam failure recovery. In some examples, the RACH procedure is a four-step RACH or a two-step RACH.

[0363] In some examples, the base station can receive an indication of a first uplink and downlink beam pair among multiple candidate uplink and downlink beam pairs that has the lowest received cross-beam reference signal power. In some examples, to receive the indication of the first uplink and downlink beam pair, the base station can transmit the indication of the first uplink and downlink beam pair via the payload or uplink signaling of Msg3 in a four-step RACH process, MsgA in a two-step RACH process. In some examples, the indication of the first uplink and downlink beam pair may include a synchronization signaling block identifier for the first uplink and downlink beam pair.

[0364] Figure 27 This is a flowchart illustrating an example wireless communication method 2700 according to some aspects. As described below, some or all illustrated features may be omitted in certain implementations within the scope of this disclosure, and some illustrated features may be unnecessary for all example implementations. In some examples, method 2700 may be... Figure 24 The method is executed by BS 2400 as shown. In some examples, method 2700 can be executed by any suitable means or unit for performing the functions or algorithms described below.

[0365] At block 2702, the base station can receive a beam fault recovery request (BFRQ) signal from the user equipment (UE) during full-duplex (FD) communication mode, wherein the BFRQ signal indicates that at least one beam has failed. In some examples, the beam fault handling circuit 2442 cooperates with the communication and processing circuit 2441 and the transceiver 2410, such as Figure 24 The shown and described unit may be provided for receiving beam fault recovery request (BFRQ) signals from a user equipment (UE) during full-duplex (FD) communication mode with the UE.

[0366] At block 2704, the base station can switch from FD communication mode to half-duplex (HD) communication mode for at least one beam after receiving a BFRQ signal, or switch from FD communication mode to restricted FD communication mode after receiving a BFRQ signal. In some examples, the communication mode modification circuit 2444 cooperates with the communication and processing circuit 2441 and the transceiver 2410, such as... Figure 24 The shown and described unit can be provided for switching from FD communication mode to half-duplex (HD) communication mode for at least one beam after receiving a BFRQ signal, or switching from FD communication mode to restricted FD communication mode after receiving a BFRQ signal.

[0367] In some examples, HD communication mode may include time-division multiplexing (TDM) transmission for at least one beam of at least one of uplink (UL) or downlink (DL) transmissions between the base station and the user equipment. In some examples, the base station may switch to HD communication mode for all active beams. In some examples, the base station may switch to HD communication mode for at least one active beam that has failed, and may also continue to use FD communication mode for at least one active beam that is currently in operation.

[0368] In some examples, during the transition period from FD communication mode to HD communication mode, the base station can determine whether to terminate the DL beam or the UL beam based on predetermined criteria. These predetermined criteria include one or more of the Physical Layer (PHY) priority field or UE auxiliary information. The PHY priority field may include a priority ordering or indication of priority for Ultra Reliable Low Latency Communication (URLLC) services with low latency requirements. In other aspects, the UE auxiliary information includes at least one of the Maximum Permissible Exposure (MPE) limit or thermal balance differences between the transmit / UL and receive / DL antenna arrays.

[0369] In some examples, the base station can send an indication to the user equipment (UE) to terminate DL or UL transmission. The base station can send this indication in one or more Physical Downlink Control Channel (PDCCH) fields or time slots. Additionally, the base station can select one or more beams for UL or DL ​​transmission in HD communication mode based on one or more predetermined conditions. Furthermore, the base station can select one or more beams for UL or DL ​​transmission in HD communication mode based on one or more predetermined conditions (including using the same DL and UL beams for FD transmission modes of both DL and UL transmissions), or select the strongest beam for both UL and DL transmissions, or select the strongest beam from the available DL and UL transmission beams for both DL and UL transmissions.

[0370] In some examples, the base station can select one or more beams for HD communication mode. As another example, the base station can select one or more beams for HD communication mode in part based on a beam recommendation received from at least one user equipment.

[0371] Regarding the selection of a restricted FD communication mode after receiving a BFRQ signal, when the UL service priority is lower than a predetermined threshold, the base station can signal the user equipment to reduce the UL modulation and coding scheme (MCS). The restricted FD communication mode may further include: signaling the user equipment to reduce the UL transmit power when the UL service priority is lower than a first predetermined threshold. Additionally, the base station can signal the user equipment to use UL transmission repetition. In another aspect, the restricted FD communication mode may include identifying a faulty FD communication mode beam pair and replacing the faulty FD communication mode beam pair with a spare FD beam pair. Furthermore, in other aspects, the restricted FD mode may include: maintaining the UL power level if the UL priority is greater than a second predetermined threshold and / or selecting an alternative DL beam when the UL priority is greater than the second predetermined threshold. In some examples, when the UL priority is greater than the second predetermined threshold, the base station may switch to HD communication mode for at least one beam.

[0372] In other aspects, restricted FD communication modes may include: utilizing the less frequency resource overlap between DL and UL transmissions, or adding a guard band between the DL and UL bands for subband FD communication. Furthermore, to switch to restricted FD communication mode after receiving a BFRQ signal, the base station may send signaling to the user equipment via RRC / MAC-CE / DCI and / or receive beam recommendations from the user equipment.

[0373] Figure 28 This is a flowchart illustrating an example wireless communication method 2800 according to some aspects. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of this disclosure, and some illustrated features may be unnecessary for all example implementations. In some examples, method 2800 may be... Figure 24 The method is executed by BS 2400 as shown. In some examples, method 2800 can be executed by any suitable means or unit for performing the functions or algorithms described below.

[0374] At block 2802, the base station can receive one or more new target beam pair candidates identified by the scheduled entity during beam failure detection and recovery. In some examples, beam selection circuitry 2443 cooperates with communication and processing circuitry 2441 and transceiver 2410, such as... Figure 24The shown and described unit may be provided for the following operation: receiving one or more new target beam pair candidates identified by the scheduled entity during beam failure detection and recovery.

[0375] At block 2804, the base station can receive a request to resume full-duplex transmission from the scheduled entity, wherein the request may include one or more identified new target beam pair candidates. In some examples, beam failure handling circuitry 2442 cooperates with communication and processing circuitry 2441 and transceiver 2410, such as... Figure 24 The shown and described unit can be provided for the following operation: receiving a request from the scheduled entity to resume full-duplex transmission.

[0376] At block 2806, the base station can process and transmit new downlink and uplink beam pairs based on one or more new target beam pair candidates to restore full-duplex transmission mode for the scheduled entity. In some examples, beam measurement and recovery circuitry 2445 cooperates with communication and processing circuitry 2441 and transceiver 2410, such as... Figure 24 The shown and described unit can be provided for the following operations: processing and transmitting new downlink and uplink beam pairs based on one or more new target beam pair candidates to restore full-duplex transmission mode for the scheduled entity.

[0377] In some examples, the identified one or more new target beam pair candidates may include one or more new downlink beams paired with one or more current uplink beams. The following aspects may apply to this situation: In some examples, the identified one or more new target beam pair candidates may include measured downlink channel quality for determining self-interference from one of the one or more uplink beams to one of the one or more new downlink beams. In some examples, downlink channel quality and self-interference measurements may include signal-to-interference-to-noise ratio (SINR). In some examples, the identified one or more new target beam pair candidates may include at least one channel measurement resource (CMR) for measuring the channel quality of each of the identified one or more new downlink beams. In some examples, the identified one or more new target beam pair candidates may include at least one additional interference measurement resource (IMR) for measuring cross-beam interference from each of the one or more current uplink beams to each of the identified one or more new downlink beams. In some examples, the identified one or more new target beam pair candidates may include SINR calculated based on CMR and IMR.

[0378] In some examples, the identified one or more new target beam pair candidates may include one or more new uplink beam candidates paired with one or more current downlink beams. The following aspects may apply to this situation: In some examples, the identified one or more new target beam pair candidates may include measured downlink channel quality and measured self-interference from one of the one or more uplink beams to one of the one or more current downlink beams. In some examples, downlink channel quality and self-interference may include signal-to-interference-and-noise ratio (SINR). In some examples, the identified one or more new target beam pair candidates may include at least one channel measurement resource (CMR) for measuring the downlink channel quality of each of the one or more current downlink beams. In some examples, the identified one or more new target beam pair candidates may include adding at least one interference measurement resource (IMR) for measuring cross-beam interference from each of the one or more new uplink beams to each of the one or more current downlink beams. In some examples, the identified one or more new target beam pair candidates may include calculating SINR based on CMR and IMR.

[0379] In some examples, identifying one or more new target beam pair candidates may include: one or more identified new downlink beams paired with one or more current uplink beams when the uplink reference signal power is stronger than the downlink reference signal power; and one or more identified new uplink beam candidates paired with one or more current downlink beams when the downlink reference signal power is stronger than the uplink reference signal power. In some examples, identifying one or more new target beam pair candidates may include accessing a lookup table of candidate beam pairs. In some examples, one or more new target beam pair candidates are identified during beam fault detection and recovery prior to a transmit beam fault recovery request (BFRQ), and wherein a BFRQ associated with the identifier of one or more new target beam pair candidates is transmitted.

[0380] In some examples, if the beam failure is due to degraded DL quality or self-interference from an inactive UL, the base station can complete the Random Access Channel (RACH) procedure before resuming FD transmission mode. In some examples, if the beam failure is due to self-interference from an active uplink, the base station can switch to half-duplex mode or fall back to FD mode before the recovery process.

[0381] In one configuration, the BS 2400 includes units for receiving a beam fault indication from a user equipment via an uplink channel of an uplink beam, wherein the beam fault indication addresses beam faults in FD communication caused by interference from uplink transmissions of the user equipment; and units for switching an operating mode for communicating with the user equipment after receiving the beam fault indication. In another configuration, the BS 2400 includes units for receiving a beam fault indication from a user equipment via a random access channel (RACH) message, wherein the beam fault indication addresses beam faults in FD communication caused by interference from uplink transmissions of the user equipment; and units for switching an operating mode for communicating with the user equipment after receiving the beam fault indication. In one aspect, the aforementioned units may be... Figure 24 The processor 2404 shown is configured to perform the functions listed by the above-described units (e.g., as discussed above). Alternatively, the aforementioned units may be circuits or any devices configured to perform the functions described above.

[0382] Of course, the circuitry included in the processor 2404 in the above examples is provided only as an example, and other means for performing the described functions may include, but are not limited to, instructions stored in the computer-readable medium 2406, or in Figure 1 , Figure 2 , Figure 4 , Figure 5 , Figure 7A , Figure 7B , Figure 7C , Figure 9 , Figure 13 , Figure 16 , Figure 17 and Figure 24 Any other suitable device or unit described in any of the figures, and utilizing, for example, those described herein. Figures 25-28 The described method and / or algorithm.

[0383] In one example, a method for wireless communication at a user equipment (UE) in a wireless communication network is disclosed. The method includes: transmitting a beam fault recovery request (BFRQ) signal to a base station during a full-duplex (FD) communication mode with a base station, wherein the BFRQ signal indicates that at least one beam has failed. Furthermore, the method includes: receiving a mode indication from the base station for a modified communication mode, and switching from the FD communication mode to the modified communication mode based on the mode indication, wherein the modified communication mode includes at least one of a half-duplex (HD) communication mode or a restricted FD communication mode for at least one beam.

[0384] In another example, a user equipment (UE) in a wireless communication network is disclosed, wherein the UE includes a wireless transceiver, a memory, and a processor communicatively coupled to the wireless transceiver and the memory. The processor and memory are configured to transmit a beam fault recovery request (BFRQ) signal to the base station during full-duplex (FD) communication mode with the base station, wherein the BFRQ signal indicates that at least one beam has failed. Furthermore, the processor and memory are configured to receive a mode indication from the base station for a modified communication mode, and to switch from the FD communication mode to the modified communication mode based on the mode indication, wherein the modified communication mode includes at least one of a half-duplex (HD) communication mode or a restricted FD communication mode for at least one beam after receiving the BFRQ signal.

[0385] According to another example, a user equipment (UE) in a wireless communication network is disclosed, comprising elements for transmitting a beam fault recovery request (BFRQ) signal to a base station during full-duplex (FD) communication mode with the base station, wherein the BFRQ signal indicates that at least one beam has failed. Additionally, the UE includes elements for receiving a mode indication of a modified communication mode from the base station. Furthermore, the UE has elements for switching from an FD communication mode to the modified communication mode based on the mode indication, wherein the modified communication mode includes at least one of a half-duplex (HD) communication mode for at least one beam after receiving the BFRQ signal or a restricted FD communication mode.

[0386] In yet another example, a non-transitory computer-readable medium includes code for enabling a user equipment (UE) in a wireless communication network to implement multiple procedures. The procedures include: transmitting a beam fault recovery request (BFRQ) signal to a base station during full-duplex (FD) communication with a base station, wherein the BFRQ signal indicates that at least one beam has failed. Furthermore, the procedures include: receiving a mode indication from the base station for a modified communication mode, and switching from the FD communication mode to the modified communication mode based on the mode indication, wherein the modified communication mode includes at least one of a half-duplex (HD) communication mode or a restricted FD communication mode for at least one beam after receiving the BFRQ signal.

[0387] In yet another example, a method for wireless communication at a base station in a wireless communication network is disclosed. The method includes receiving a beam fault recovery request (BFRQ) signal from a user equipment (UE) during full-duplex (FD) communication mode, wherein the BFRQ signal indicates that at least one beam has failed. Additionally, the method includes switching from the FD communication mode to a half-duplex (HD) communication mode for at least one beam after receiving the BFRQ signal, or switching from the FD communication mode to a restricted FD communication mode after receiving the BFRQ signal.

[0388] According to another example, a base station in a wireless communication network is disclosed, the base station having a wireless transceiver, a memory, and a processor communicatively coupled to the wireless transceiver and the memory. The processor and memory are configured to receive a beam fault recovery request (BFRQ) signal from a user equipment (UE) during full-duplex (FD) communication mode, wherein the BFRQ signal indicates that at least one beam has failed. Additionally, the processor and memory are configured to switch from FD communication mode to half-duplex (HD) communication mode for at least one beam after receiving the BFRQ signal, or to switch from FD communication mode to restricted FD communication mode after receiving the BFRQ signal.

[0389] According to another aspect, a base station in a wireless communication network is disclosed. The base station includes: a unit for receiving a beam fault recovery request (BFRQ) signal from a user equipment (UE) during full-duplex (FD) communication mode, wherein the BFRQ signal indicates that at least one beam has failed. Additionally, the base station includes: a unit for switching from FD communication mode to half-duplex (HD) communication mode for at least one beam after receiving the BFRQ signal, or switching from FD communication mode to restricted FD communication mode after receiving the BFRQ signal.

[0390] In yet another example, a non-transitory computer-readable medium includes code for enabling a user equipment (UE) in a wireless communication network to implement multiple procedures. The procedures include: receiving a beam fault recovery request (BFRQ) signal from the UE during full-duplex (FD) communication with the UE, wherein the BFRQ signal indicates that at least one beam has failed. The procedures also include: switching from the FD communication mode to a half-duplex (HD) communication mode for at least one beam after receiving the BFRQ signal, or switching from the FD communication mode to a restricted FD communication mode after receiving the BFRQ signal.

[0391] In some examples, a method for full-duplex (FD) communication at a user equipment may include: identifying beam faults in FD communication due to interference from uplink transmissions from the user equipment; generating a beam fault indication for the beam fault; and sending the beam fault indication to the base station via the uplink channel of the uplink beam when the user equipment is able to communicate with the base station via the uplink beam. As applicable herein, the term "when" does not specify a precise time.

[0392] In some examples, a user equipment (UE) for full-duplex (FD) communication may include a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory. The processor and memory may be configured to: identify beam faults in FD communication due to interference from uplink transmissions from the UE; generate a beam fault indication for the beam fault; and, when the UE is able to communicate with the base station via the uplink beam, send the beam fault indication to the base station via the uplink channel of the uplink beam.

[0393] In some examples, a user equipment for full-duplex (FD) communication may include: a unit for identifying beam faults in FD communication caused by interference from uplink transmissions from the user equipment; a unit for generating a beam fault indication for the beam fault; and a unit for sending the beam fault indication to the base station via the uplink channel of the uplink beam when the user equipment is able to communicate with the base station via the uplink beam.

[0394] In some examples, an article of manufacture for a user equipment to use in full-duplex (FD) communication includes a computer-readable medium having instructions stored therein, the instructions being executable by one or more processors of the user equipment to: identify beam faults in FD communication due to interference from uplink transmissions of the user equipment; generate a beam fault indication for the beam fault; and, when the user equipment is able to communicate with a base station via an uplink beam, send the beam fault indication to the base station via an uplink channel of the uplink beam.

[0395] In some examples, a method for full-duplex (FD) communication at a user equipment may include: identifying beam faults in FD communication caused by interference from uplink transmissions from the user equipment or by downlink quality degradation; generating a beam fault indication for the beam fault; and sending the beam fault indication to the base station via a random access channel (RACH) message when the user equipment is unable to communicate with the base station via the uplink beam or when the beam fault is due to downlink quality degradation.

[0396] In some examples, a user equipment (UE) for full-duplex (FD) communication may include a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory. The processor and memory may be configured to: identify beam faults in FD communication due to interference from uplink transmissions from the UE or due to downlink quality degradation; generate beam fault indications for beam faults; and send beam fault indications to the base station via a random access channel (RACH) message when the UE cannot communicate with the base station via the uplink beam or when the beam fault is due to downlink quality degradation.

[0397] In some examples, a user equipment for full-duplex (FD) communication may include: a unit for identifying beam faults in FD communication caused by interference from uplink transmissions from the user equipment or by downlink quality degradation; a unit for generating a beam fault indication for the beam fault; and a unit for sending a beam fault indication to the base station via a random access channel (RACH) message when the user equipment is unable to communicate with the base station via the uplink beam or when the beam fault is due to downlink quality degradation.

[0398] In some examples, an article of manufacture for a user equipment (UE) to use in full-duplex (FD) communication includes a computer-readable medium having instructions stored therein, which are executable by one or more processors of the UE to: identify beam faults in FD communication due to interference from uplink transmissions from the UE or due to downlink quality degradation; generate a beam fault indication for the beam fault; and send the beam fault indication to the base station via a random access channel (RACH) message when the UE is unable to communicate with the base station via the uplink beam or when the beam fault is due to downlink quality degradation.

[0399] In some examples, a method for full-duplex (FD) communication at a base station may include: receiving a beam fault indication from a user equipment (UE) via an uplink channel of an uplink beam; and switching an operating mode for communicating with the UE after receiving the beam fault indication. The beam fault indication may be for beam faults in FD communication caused by interference from uplink transmissions from the UE.

[0400] In some examples, a base station for full-duplex (FD) communication may include a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory. The processor and memory may be configured to: receive a beam fault indication from a user equipment (UE) via an uplink channel of the uplink beam; and, upon receiving the beam fault indication, switch the operating mode used for communicating with the UE. The beam fault indication may target beam faults in FD communication caused by interference from uplink transmissions from the UE.

[0401] In some examples, a base station for full-duplex (FD) communication may include: a unit for receiving a beam fault indication from a user equipment via an uplink channel through an uplink beam; and a unit for switching an operating mode for communicating with the user equipment after receiving the beam fault indication. The beam fault indication may be for beam faults in FD communication caused by interference from uplink transmissions from the user equipment.

[0402] In some examples, an article of manufacture for a base station to use in full-duplex (FD) communication includes a computer-readable medium having instructions stored therein, which are executable by one or more processors of the base station for: receiving a beam fault indication from a user equipment via an uplink channel of an uplink beam; and switching an operating mode for communicating with the user equipment after receiving the beam fault indication. The beam fault indication can be for beam faults in FD communication caused by interference from uplink transmissions from the user equipment.

[0403] In some examples, a method for full-duplex (FD) communication at a base station may include: receiving a beam fault indication from a user equipment (UE) via an uplink channel of an uplink beam; and switching an operating mode for communicating with the UE after receiving the beam fault indication. The beam fault indication may be for beam faults in FD communication caused by interference from uplink transmissions from the UE.

[0404] In some examples, a base station for full-duplex (FD) communication may include a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory. The processor and memory may be configured to: receive a beam fault indication from a user equipment (UE) via a random access channel (RACH) message; and, upon receiving the beam fault indication, switch the operating mode used for communicating with the UE. The beam fault indication may target beam faults in FD communication caused by interference from uplink transmissions from the UE.

[0405] In some examples, a base station for full-duplex (FD) communication may include: a unit for receiving a beam fault indication from a user equipment via a random access channel (RACH) message; and a unit for switching the operating mode for communicating with the user equipment after receiving the beam fault indication. The beam fault indication may be for beam faults in FD communication caused by interference from uplink transmissions from the user equipment.

[0406] In some examples, an article of manufacture for a base station to use in full-duplex (FD) communication includes a computer-readable medium having instructions stored therein, which are executable by one or more processors of the base station for: receiving a beam fault indication from a user equipment via a random access channel (RACH) message; and switching an operating mode for communicating with the user equipment after receiving the beam fault indication. The beam fault indication can be for beam faults in FD communication caused by interference from uplink transmissions from the user equipment.

[0407] In one example, a method for beam fault recovery in a scheduled entity is disclosed, comprising: identifying one or more new target beam pair candidates via the scheduled entity during beam fault detection and recovery; sending a request to the scheduling entity to restore full-duplex transmission mode, wherein the request includes the identified one or more new target beam pair candidates; and receiving new downlink and uplink beam pairs from the scheduling entity in response to sending the one or more new target beam pair candidates to restore full-duplex transmission mode.

[0408] In another example, a method for beam fault recovery in a scheduling entity is disclosed, comprising: receiving one or more new target beam pair candidates identified by the scheduled entity during beam fault detection and recovery; receiving from the scheduled entity a request to restore full-duplex transmission mode, wherein the request includes the identified one or more new target beam pair candidates; and processing and transmitting new downlink and uplink beam pairs based on the one or more new target beam pair candidates to restore full-duplex transmission mode for the scheduled entity.

[0409] In another example, a scheduled entity in a wireless communication network is disclosed, comprising: a wireless transceiver; a memory; and a processor communicatively coupled to the wireless transceiver and the memory, wherein the processor and the memory are configured to: identify one or more new target beam pair candidates via the scheduled entity during beam failure detection and recovery; send a request to the scheduling entity to restore full-duplex transmission mode, wherein the request includes the identified one or more new target beam pair candidates; and, in response to sending one or more new target beam pair candidates, receive new downlink and uplink beam pairs from the scheduling entity to restore full-duplex transmission mode.

[0410] In another example, a scheduling entity in a wireless communication network is disclosed, comprising: a wireless transceiver; a memory; and a processor communicatively coupled to the wireless transceiver and the memory, wherein the processor and the memory are configured to: receive one or more new target beam pair candidates identified by the scheduled entity during beam failure detection and recovery; receive from the scheduled entity a request to restore full-duplex transmission mode, wherein the request includes the identified one or more new target beam pair candidates; and based on the one or more new target beam pair candidates, process and transmit new downlink and uplink beam pairs to restore full-duplex transmission mode for the scheduled entity.

[0411] Figures 18-23 and Figures 25-28 The methods illustrated may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein. An overview of several aspects of this disclosure is provided below:

[0412] Aspect 1: A method for full-duplex communication at a user equipment, the method comprising: receiving an uplink transmission sent by the user equipment; and when the user equipment is capable of communicating with a base station via an uplink beam, sending a beam fault indication to the base station via an uplink channel of the uplink beam, wherein the beam fault indication identifies a beam fault in the full-duplex communication, and wherein the beam fault is due to interference from the uplink transmission.

[0413] Aspect 2: According to the method of aspect 1, wherein the beam fault indication indicates that the beam fault is related to full-duplex transmission with the base station.

[0414] Aspect 3: The method according to aspect 1 or aspect 2, wherein the beam fault indication indicates a beam fault recovery request (BFRQ) for the full-duplex communication.

[0415] Aspect 4: The method according to any one of Aspects 1 to 3 further includes: transmitting the uplink beam using a first antenna panel; and receiving the downlink beam using a second antenna panel, wherein the interference from the uplink transmission includes self-interference of the user equipment measured via the second antenna panel from an interference measurement resource (IMR) configured in a Radio Resource Control (RRC) Radio Link Monitoring Reference Signal (RLM-RS) configuration for beam failure detection.

[0416] Aspect 5: According to the method of aspect 4, wherein the IMR carries a sounding reference signal (SRS) or demodulation reference signal (DMRS) transmitted from the uplink beam to the downlink beam.

[0417] Aspect 6: The method according to any one of Aspects 4 to 5, wherein the beam fault indication indicates a fault in all active beams of the user equipment.

[0418] Aspect 7: The method according to any one of Aspects 4 to 5, wherein the beam fault indication indicates a fault in at least one active beam of the user equipment.

[0419] Aspect 8: The method according to any one of Aspects 4 to 5, wherein the beam fault indication includes an identifier of at least one faulty beam.

[0420] Aspect 9: The method according to any one of Aspects 1 to 8 further includes: sending the beam fault indication to the base station via an uplink control channel.

[0421] Aspect 10: The method according to any one of Aspects 1 to 9 further includes: transmitting uplink control information (UCI) including the beam failure indication via the physical uplink shared channel (PUSCH) or transmitting a media access control-control unit (MAC-CE) including the beam failure indication.

[0422] Aspect 11: The method according to any one of aspects 1 to 10 further includes: determining whether the user equipment is capable of communicating with the base station via the uplink beam.

[0423] Aspect 12: The method according to any one of Aspects 1 to 11 further includes: measuring at least one downlink reference signal; measuring at least one uplink reference signal; deriving at least one quality parameter from the at least one downlink reference signal and the at least one uplink reference signal; comparing the at least one quality parameter with a threshold; and generating the beam fault indication based on the comparison of the at least one quality parameter with the threshold.

[0424] Aspect 14: A method for full-duplex communication at a user equipment, the method comprising: receiving an uplink transmission sent by the user equipment; and sending a beam fault indication identifying a beam fault in the full-duplex communication via a random access channel (RACH) message to the base station when the user equipment is unable to communicate with the base station via an uplink beam or when the beam fault is due to downlink quality degradation, wherein the beam fault is due to interference from the uplink transmission.

[0425] Aspect 15: The method according to aspect 14, wherein the beam fault indication includes a beam fault recovery request (BFRQ) and indicates that the beam fault is for full-duplex transmission with the base station.

[0426] Aspect 16: The method according to any one of Aspects 14 to 15 further includes: transmitting the uplink beam using the first antenna panel; and receiving the downlink beam using the second antenna panel, wherein the interference from the uplink transmission includes self-interference of the user equipment measured via the second antenna panel from an interference measurement resource (IMR) configured in a Radio Resource Control (RRC) Radio Link Monitoring Reference Signal (RLM-RS) configuration for beam failure detection.

[0427] Aspect 17: The method according to any one of aspects 14 to 16 further includes: selecting from two preambles reserved for the user equipment a first preamble designated for beam fault caused by full-duplex self-interference; and sending the first preamble as a beam fault recovery request (BFRQ).

[0428] Aspect 18: The method according to aspect 17, wherein the two preambles reserved for the user equipment include a second preamble designated for beam failure caused by downlink quality degradation.

[0429] Aspect 19: The method according to any one of aspects 14 to 18 further includes: selecting from two preamble sets a first preamble set designated for beam failure caused by full-duplex self-interference; selecting a first preamble from the first preamble set; and sending the first preamble as a beam failure recovery request (BFRQ).

[0430] Aspect 20: The method according to aspect 19, wherein the two preamble sets include a second preamble set designated for beam failure caused by downlink quality degradation.

[0431] Aspect 21: The method according to any one of aspects 14 to 20, wherein the beam fault indication indicates a fault in all active beams of the user equipment.

[0432] Aspect 22: The method according to any one of aspects 14 to 21, wherein the beam fault indication indicates a fault in at least one active beam of the user equipment.

[0433] Aspect 23: The method according to any one of aspects 14 to 22, wherein the beam fault indication includes an identifier of at least one faulty beam.

[0434] Aspect 24: The method according to any of aspects 14 to 23 further includes: identifying uplink and downlink beam pairs to restore full-duplex communication after a random access channel (RACH) procedure for beam fault recovery, wherein the RACH procedure is a four-step RACH or a two-step RACH.

[0435] Aspect 25: The method according to aspect 24 further includes: transmitting a first RACH preamble; transmitting a second RACH preamble that is a repeat of the first RACH preamble; receiving the first RACH preamble via a first receiving beam of the user equipment; receiving the second RACH preamble via a second receiving beam of the user equipment; and selecting either the first receiving beam or the second receiving beam to pair with an identified beam to form the uplink and downlink beam pair.

[0436] Aspect 26: The method according to aspect 25 further includes: determining whether the first received beam or the second received beam is associated with lower cross-beam self-interference of the user equipment.

[0437] Aspect 27: The method according to any one of aspects 14 to 26 further includes: identifying a first uplink and downlink beam pair among a plurality of candidate uplink and downlink beam pairs having the lowest cross-beam reference signal received power; and sending an indication of the first uplink and downlink beam pair to the base station.

[0438] Aspect 28: The method according to aspect 27 further includes: transmitting an indication of the first uplink and downlink beampair via the payload or uplink signaling of Msg3 in a four-step RACH process or MsgA in a two-step RACH process.

[0439] Aspect 29: The method according to aspect 28, wherein the indication of the first uplink and downlink beam pair includes a synchronization signaling block identifier for the first uplink and downlink beam pair.

[0440] Aspect 30: A user equipment comprising: a transceiver configured to communicate with a radio access network; a memory; and a processor communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to perform any one of aspects 1 to 12.

[0441] Aspect 31: An apparatus configured for wireless communication, comprising at least one unit for performing any one of aspects 1 to 12.

[0442] Aspect 32: A non-transitory computer-readable medium storing computer-executable code, comprising code for causing a device to perform any one of aspects 1 to 12.

[0443] Aspect 33: A user equipment comprising: a transceiver; a memory; and a processor communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to perform any one of aspects 14 to 29.

[0444] Aspect 34: An apparatus configured for wireless communication, comprising at least one unit for performing any one of aspects 14 to 29.

[0445] Aspect 35: A non-transitory computer-readable medium storing computer-executable code, comprising code for causing a device to perform any of aspects 14 to 29.

[0446] Several aspects of wireless communication networks have been described with reference to exemplary embodiments. As will be readily understood by those skilled in the art, the various aspects described throughout this disclosure can be extended to other telecommunications systems, network architectures, and communication standards.

[0447] For example, various aspects can be implemented within other systems defined by 3GPP, such as LTE, Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile Communications (GSM). These aspects can also be extended to systems defined by 3GPP2, such as CDMA2000 and / or Evolved Data Optimized (EV-DO). Other examples can be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunications standards, network architecture, and / or communication standards used will depend on the specific application and the overall design constraints imposed on the system.

[0448] In this disclosure, the term "exemplary" means "serving as an example, instance, or illustration." Any implementation or aspect described herein as "exemplary" is not necessarily to be construed as preferred or superior to other aspects. Similarly, the term "aspect" does not require that all aspects of this disclosure include the features, advantages, or modes of operation discussed. The term "coupled" is used herein to refer to direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, then objects A and C are still considered 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 never has direct physical contact with the second object. The terms "circuit" and "circuit system" are used broadly and are intended to include both hardware implementations of electronic devices and conductors (capable of performing the functions described in this disclosure when connected and configured, without limitation on the type of electronic circuit) and software implementations of information and instructions (capable of performing the functions described in this disclosure when executed by a processor). As used herein, the term "determine" can include, for example, asserting, resolving, selecting, choosing, establishing, calculating, operating, processing, deriving, investigating, searching (e.g., searching in a table, database, or other data structure), and so on. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), and so on.

[0449] Can Figures 1-28 One or more of the components, steps, features, and / or functions shown herein may be rearranged and / or combined into a single component, step, feature, or function, or embodied in several components, steps, features, or functions. Additional elements, components, steps, and / or functions may be added without departing from the novel features disclosed herein. Figure 1 , Figure 2 , Figure 4 , Figure 5 , Figure 7A , Figure 7B , Figure 7C , Figure 9 , Figure 13 , Figure 16 , Figure 17 and Figure 24 The apparatus, devices, and / or components shown herein can be configured to perform one or more of the methods, features, or steps described herein. The novel algorithms described herein can also be efficiently implemented in software and / or embedded in hardware.

[0450] It should be understood that the specific order or hierarchy of steps in the disclosed methods is an illustration of an exemplary process. It should be understood that the specific order or hierarchy of steps in these methods can be rearranged according to design preferences. The appended method claims give the elements of various steps in an exemplary order, and unless specifically stated herein, are not intended to limit us to the given specific order or hierarchy.

[0451] The above description is provided to enable any person skilled in the art to implement 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 limited to the aspects shown herein, but are consistent with the entire scope of protection of the language of the claims, wherein, unless otherwise specified, the singular form of an element does not mean "one and only one," but rather "one or more." Unless otherwise specified, the term "some" refers to one or more. The phrase "at least one" referring to the list of items means any combination of these items, including a single member. For 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 structures and functions known or to be known by one of ordinary skill in the art that are equivalent to the elements throughout the various aspects described herein are expressly incorporated herein by reference and are intended to be included in the claims. Furthermore, whether or not this disclosure is expressly recited in the claims, the disclosure herein is not intended to be offered to the public.

Claims

1. A method at a user equipment, comprising: Receive downlink transmissions during uplink transmissions sent by the user equipment; A downlink beam fault associated with the uplink transmission was detected; Generate beam fault indication; as well as (1) If the user equipment is able to communicate with the base station via the uplink beam, it shall send the beam failure indication to the base station via the uplink channel of the uplink beam, or (2) if the user equipment is unable to communicate with the base station via the uplink beam or if the downlink beam failure is due to downlink quality degradation, it shall send the beam failure indication to the base station via a random access channel (RACH) message.

2. The method according to claim 1, wherein, The beam fault indicator is used to indicate that the downlink beam fault is related to full-duplex transmission with the base station.

3. The method according to claim 1, wherein, The beam fault indicator is used to indicate a beam fault recovery request (BFRQ) for the full-duplex communication.

4. The method according to claim 1, further comprising: The uplink beam is transmitted using the first antenna panel; Use the second antenna panel to receive the downlink beam; as well as The interference from the uplink transmission includes self-interference from the user equipment measured via the second antenna panel from the interference measurement resource (IMR) configured in the Radio Resource Control (RRC) Radio Link Monitoring Reference Signal (RLM-RS) configuration for beam fault detection.

5. The method according to claim 4, wherein, The IMR carries a probe reference signal (SRS) or demodulation reference signal (DMRS) transmitted from the uplink beam to the downlink beam.

6. The method according to claim 4, wherein, The beam fault indicator is used to indicate a fault in all active beams of the user equipment.

7. The method according to claim 4, wherein, The beam fault indicator is used to indicate a fault in at least one active beam of the user equipment.

8. The method according to claim 4, wherein, The beam fault indication includes an identifier for at least one faulty beam.

9. The method according to claim 1, further comprising: The beam fault indication is sent to the base station via the uplink control channel.

10. The method according to claim 1, further comprising: Uplink control information (UCI) including the beam fault indication is transmitted via the Physical Uplink Shared Channel (PUSCH) or a Media Access Control-Control Unit (MAC-CE) including the beam fault indication is transmitted.

11. The method according to claim 1, further comprising: Determine whether the user equipment is able to communicate with the base station via the uplink beam.

12. The method according to claim 1, further comprising: Measure at least one downlink reference signal; Measure at least one uplink reference signal; Derive at least one quality parameter from the at least one downlink reference signal and the at least one uplink reference signal; Compare the at least one quality parameter with a threshold; as well as The beam fault indication is generated based on the comparison between the at least one quality parameter and the threshold.

13. An apparatus for wireless communication, comprising: Memory; as well as One or more processors, coupled to the memory, are configured to perform the method of any one of claims 1 to 12.

Images