WO2022186816A1

WO2022186816A1 - User equipment-aborted full-duplex communication

Info

Publication number: WO2022186816A1
Application number: PCT/US2021/020319
Authority: WO
Inventors: Jibing Wang; Erik Richard Stauffer
Original assignee: Google Llc
Priority date: 2021-03-01
Filing date: 2021-03-01
Publication date: 2022-09-09

Abstract

A user equipment (111) receives (705), from the base station (120), a schedule (520) indicating air interface resources allocated to the user equipment for full-duplex communication. The user equipment determines (715) to disable full-duplex communication using at least a portion of the air interface resources. The user equipment transmits (720), to the base station, an abort indication (560) indicating that it has disabled full-duplex communication using at least a portion of the air interface resources. In response to receiving (810) the abort indication, the base station reallocates (825) at least some of the air interface resources to a second user equipment (112).

Description

USER EQUIPMENT- ABORTED FULL-DUPLEX COMMUNICATION

BACKGROUND

[0001] The evolution of wireless communication to fifth generation (5G) and sixth generation (6G) standards and technologies provides higher data rates and greater capacity with improved reliability and lower latency, which enhances mobile broadband services. One way in which 5G and 6G technologies can provide greater capacity is through the use of full-duplex (FD) communication.

[0002] In full-duplex communication, a user equipment (UE) and a base station each transmit and receive data using the same air interface resource. More specifically, full-duplex communication allows the UE and base station to transmit and receive data at the same time and using the same frequency. Full-duplex communication makes better use of the available frequency spectrum than half-duplex communication, and provides greater overall capacity as long as a full-duplex wireless communication device can overcome the challenges of self-interference.

SUMMARY

[0003] This document describes techniques and apparatuses for user equipment-aborted full- duplex communication. Abase station allocates air interface resources to a user equipment for full- duplex communication. However, if the user equipment is unable to perform full-duplex communication, then at least some of those resources will be wasted. To prevent such wastage, the user equipment transmits an abort indication to the base station when the user equipment is unable to perform full-duplex communication using some or all of the allocated resources. Upon receiving the abort indication, the base station can reallocate some or all of the air interface resources to another user equipment. Wastage of air interface resources is reduced, and greater utilization of the available frequency spectrum is achieved.

[0004] In a first aspect of the present disclosure, a method performed by a user equipment for full-duplex communication with a base station includes: receiving, from the base station, a schedule identifying air interface resources allocated to the user equipment for full-duplex communication; determining to disable full-duplex communication using at least a portion of the allocated air interface resources; and transmitting, to the base station, an abort indication indicating that the user equipment has disabled full-duplex communication using at least a portion of the allocated air interface resource.

[0005] In a second aspect of the present disclosure, a method performed by a base station for full-duplex communication with a first user equipment includes: transmitting, to the first user equipment, a schedule identifying air interface resources allocated to the first user equipment for full- duplex communication; receiving, from the first user equipment, an abort indication indicating that the first user equipment has disabled full-duplex communication using at least a portion of the allocated air interface resources; and reallocating at least some of the air interface resources for use by a second user equipment.

[0006] The details of one or more implementations of user equipment-aborted full-duplex communication are set forth in the accompanying drawings and the following description. Other features and advantages will be apparent from the description and drawings, and from the claims. This summary is provided to introduce subject matter that is further described in the Detailed Description and Drawings. Accordingly, this summary should not be considered to describe essential features nor used to limit the scope of the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

[0007] The details of one or more aspects of user equipment-aborted full-duplex communication are described below. The use of the same reference numbers in different instances in the description and the figures indicate similar elements:

FIG. 1 illustrates an example operating environment in which various aspects of user equipment-aborted full-duplex communication can be implemented.

FIG. 2 illustrates an example device diagram of network entities that can implement various aspects of user equipment-aborted full-duplex communication.

FIG. 3 illustrates an example block diagram of a wireless network stack model in which various aspects of user equipment-aborted full-duplex communication can be implemented.

FIG. 4 illustrates an example air interface resource that extends between a user equipment and/or a base station and with which various aspects of user equipment-aborted full-duplex communication can be implemented.

FIG. 5 illustrates an example of transactions between a base station and two user equipment in accordance with one or more aspects of user equipment-aborted full-duplex communication.

FIG. 6 illustrates an example of transactions between a base station and two user equipment in accordance with one or more aspects of user equipment-aborted full-duplex communication.

FIG. 7 illustrates an example method performed by a user equipment for user equipment- aborted full-duplex communication in accordance with one or more aspects.

FIG. 8 illustrates an example method performed by a base station for user equipment-aborted full-duplex communication in accordance with one or more aspects. DETAILED DESCRIPTION

[0008] The evolution of wireless communication to 5G and 6G standards and technologies provides higher data rates and greater capacity, with improved reliability and lower latency, which enhances mobile broadband services. One way in which 5G and 6G technologies can provide greater capacity is full-duplex communication. In full-duplex communication, a UE and a base station each transmit and receive data using the same air interface resource. More specifically, full-duplex communication allows the UE and base station to transmit and receive at the same time and using the same frequency. Full-duplex communication as described herein is distinct from frequency-division duplex and time-division duplex, in that the present disclosure relates to true full-duplex communication in which both transmission and reception occur at the same time and on the same frequency. In contrast to true full-duplex communication, frequency-division duplex and time- division duplex merely emulate full-duplex by dividing a communication channel (in the frequency domain or the time domain, respectively) into two half-duplex channels, i.e., an uplink half-duplex channel and a downlink half-duplex channel.

[0009] Full-duplex involves interference cancellation by both the UE and the base station. For example, the UE suppresses self-interference received by its own antenna(s) when it transmits an uplink communication to the base station, so that a downlink communication can be received at the same time and using the same frequency as the uplink communication. Interference cancellation is resource-intensive, particularly for a UE, which typically has fewer available local resources (e.g., processing capability, battery power etc.) than a base station. As such, a UE’s ability to perform full- duplex communication depends on factors such as the level of interference, the received power, the UE transmitter power, UE battery status, front end linearity, an error rate, and/or temperature. For example, the UE may be unable to cancel interference if the level of interference is too high, or if the UE’s transmitter power is high relative to the received power. The UE may be unable to perform full- duplex communication when it is unable to cancel interference. As another example, if a state of charge of a battery of the UE is low, then it may be desirable to conserve power by diverting the UE’s local resources away from interference cancellation and full-duplex communication.

[0010] In a wireless network, a base station allocates air interface resources to UEs. In more detail, the base station allocates a portion of the available time-frequency resources to each UE that it serves. Air interface resources are allocated for half-duplex communication or full-duplex communication. The base station then informs each UE of the air interface resources that have been allocated to it by transmitting a message (interchangeably referred to as a schedule, a scheduling grant, or a resource grant) to each UE. The base station allocates the air interface resources, and transmits the schedule, before the time at which the air interface resources will actually be used by the UE.

[0011] If a UE is unable to perform full-duplex communication using the air interface resources allocated to it, then at least some of those resources will be wasted. The present disclosure is directed to improving the utilization of air interface resources. More specifically, the techniques disclosed herein reduce air interface resource waste when a user equipment can no longer perform full-duplex communication. In implementations, the UE determines that it cannot perform full- duplex communication using at least some of the air interface resources allocated to it, and transmits an abort indication to the base station. The abort indication signals, to the base station, that the UE will not perform full-duplex communication using at least some of the air interface resources that have been allocated to it. Upon receiving the abort indication, the base station can reallocate those air interface resources to another user equipment. In this manner, the other user equipment uses air interface resources that would otherwise be wasted, thus improving the overall utilization of air interface resources.

[0012] In some implementations, the abort indication may identify specific air interface resources that the UE will not use to perform full-duplex communication. For example, the abort indication may identify specific symbols or slots during which the UE will not perform full-duplex communication. In this manner, the UE “throttles” its air interface resource allocation to reflect its ability to perform full-duplex communication. In other words, the UE performs full-duplex communication during symbols or slots in which it has sufficient local resources to do so, while the base station reallocates the remaining symbols or slots to other UEs. As another example, the abort indication may indicate that full-duplex communication should be aborted in either the uplink or downlink direction. In this manner, the UE continues to perform half-duplex communication in the other (non-aborted) direction, while the base station reallocates air interface resources in the aborted direction to other UEs. In both examples, the usage of air interface resources is improved by reducing wastage of air interface resources.

Example Environment

[0013] FIG. 1 illustrates an example environment 100 in which various aspects of user equipment-aborted full-duplex communication can be implemented. The example environment 100 includes multiple user equipment 110 (UE 110), illustrated as UE 111, UE 112 and UE 113. Each UE 110 can communicate with one or more base stations 120 (illustrated as base stations 121 and 122), through one or more wireless communication links 130 (wireless link 130), illustrated as wireless links 131 and 132. Although illustrated as a smartphone, the user equipment 110 may be implemented as any suitable computing or electronic device, such as a mobile communication device, a modem, cellular phone, gaming device, navigation device, media device, laptop computer, desktop computer, tablet computer, smart appliance, or vehicle-based communication system. The base stations 120 (e.g., an Evolved Universal Terrestrial Radio Access Network Node B, E UTRAN Node B, evolved Node B, eNodeB, eNB, Next Generation Node B, gNode B, gNB, a 6G Node B, or the like) may be implemented in a macrocell, microcell, small cell, picocell, and the like, or any combination thereof.

[0014] The base stations 120 communicate with the user equipment 110 via the wireless links 131 and 132, which may be implemented as any suitable type of wireless link. The wireless links 131 and 132 can include a downlink of control-plane information and user-plane data communicated from the base stations 120 to the user equipment 110, an uplink of other control-plane information and/or user-plane data and communicated from the user equipment 110 to the base stations 120, or both. The wireless links 130 may include one or more wireless links or bearers implemented using any suitable communication protocol or standard, or combination of communication protocols or standards such as 3rd Generation Partnership Project Long-Term Evolution (3GPP LTE), Fifth Generation New Radio (5G NR), 6G, and so forth. Multiple wireless links 130 may be aggregated in a carrier aggregation to provide a higher data rate for the user equipment 110. Multiple wireless links 130 from multiple base stations 120 may be configured for Coordinated Multipoint (CoMP) communication with the user equipment 110. Additionally, multiple wireless links 130 may be configured for single-radio access technology (RAT) (single-RAT) dual connectivity (single-RAT- DC) or multi-RAT dual connectivity (MR-DC).

[0015] The base stations 120 are collectively a Radio Access Network 140 (RAN, Evolved Universal Terrestrial Radio Access Network, E-UTRAN, 5G NR RAN, NR RAN, 6G RAN, and so forth). The base stations 121 and 122 in the RAN 140 are connected to a core network 150. In FIG. 1, the core network 150 is shown to include a Fifth-Generation Core (5GC) network 151 (5GC 151) and an Evolved Packet Core (EPC) network 152 (EPC 152). Alternatively or in addition, the core network 150 may include a 6G core network (not shown in FIG. 1). The base stations 121 and 122 are connected to the 5GC 151. The base station 122 is connected to the EPC 152. Optionally, the base station 121 could be connected to both the 5GC 151 and the EPC 152. The base stations 121 and 122 connect, at 102 and 107 respectively, to the 5GC 151 via an NG2 interface for control-plane signaling and via an NG3 interface for user-plane data communications. The base station 122 connects, at 106, to the EPC 152 using an SI interface for control -plane signaling and user-plane data communications. In addition to connections to core networks, base stations 120 may communicate with each other via an Xn interface, at 105, to exchange user-plane data and control -plane information. The user equipment 110 may also connect, via the core network 150, to public networks, such as the Internet to interact with a remote service (not shown in FIG. 1).

Example Devices

[0016] FIG. 2 illustrates an example device diagram 200 of the UE 110 and one of the base stations 120 that can implement various aspects of user equipment-aborted full-duplex communication in a wireless communication system. The UE 110 and/or the base station 120 may include additional functions and interfaces that are omitted from FIG. 2 for the sake of clarity.

[0017] The UE 110 includes antennas 202, a radio frequency front end 204 (RF front end 204), and a wireless transceiver ( e.g ., an LTE transceiver 206, and/or a 5G NR transceiver 208) for communicating with the base station 120 in the RAN 140. The RF front end 204 of the UE 110 can couple or connect the LTE transceiver 206 and the 5G NR transceiver 208 to the antennas 202 to facilitate various types of wireless communication. The antennas 202 of the UE 110 may include an array of multiple antennas that are configured in a manner similar to or different from each other. The antennas 202 and the RF front end 204 can be tuned to, and/or be tunable to, one or more frequency bands defined by the 3GPP LTE and 5G NR communication standards and implemented by the LTE transceiver 206, and/or the 5G NR transceiver 208. Additionally, the antennas 202, the RF front end 204, the LTE transceiver 206, and/or the 5GNR transceiver 208 may be configured to support beamforming for the transmission and reception of communications with the base station 120. By way of example and not limitation, the antennas 202 and the RF front end 204 can be implemented for operation in sub-gigahertz (GHz) bands, sub-6 GHz bands, and/or above 6 GHz bands that are defined by the 3GPP LTE and 5G NR communication standards.

[0018] The UE 110 also includes processor(s) 210 and computer-readable storage media 212 (CRM 212). The processor 210 may be a single-core processor or a multiple-core processor composed of a variety of materials, such as silicon, polysilicon, high-K dielectric, copper, and so on. The computer-readable storage media described herein excludes propagating signals. CRM 212 may include any suitable memory or storage device such as random-access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), or Flash memory useable to store device data 214 of the UE 110. The device data 214 includes user data, multimedia data, beamforming codebooks, applications, and/or an operating system of the UE 110, some of which are executable by processor(s) 210 to enable user-plane data, control-plane information, and user interaction with the UE 110.

[0019] The CRM 212 of the UE 110 includes a full-duplex manager 216. Alternatively, or additionally, the full-duplex manager 216 may be implemented in whole or part as hardware logic or circuitry integrated with or separate from other components of the UE 110. In aspects, the full-duplex manager 216 of the UE 110 implements the method for user equipment-aborted full-duplex communication shown in FIG. 7. In more detail, the full-duplex manager 216 determines the ability of the user equipment 110 to perform full-duplex communication at a point in time, and indicates reductions or increases to full-duplex communication accordingly. To illustrate, the full-duplex manager 216 generates an abort indication to indicate reductions to full-duplex communication, and generates a resume indication to indicate increases to full-duplex communication. The full-duplex manager 216 then provides the abort indication and/or resume indication to the wireless transceiver 206, 208, which in turn transmits the abort indication and resume indication to the base station 120.

[0020] The UE 110 also includes an interference cancellation circuit 218. The interference cancellation circuit 218 is configured to suppress self-interference received by the antennas 202 when the UE 110 transmits an uplink communication. The interference cancellation circuit 218 enables the UE 110 to perform full-duplex communication by suppressing or cancelling self-interference, which would otherwise prevent the UE 110 receiving and successfully decoding a downlink communication using the same time/frequency resource as the uplink communication. In general, the interference cancellation circuit 218 is operable to subtract a transmitted signal from a received signal. The interference cancellation circuit 218 may be implemented in any suitable manner, using any combination of analog circuitry, digital signal processing circuitry and/or instructions executable by the processor(s) 210. Although the interference circuit 218 is shown as a discrete functional block in FIG. 2, it may be implemented in the RF front end 204, the LTE transceiver 206, the 5G NR. transceiver 208, by instructions stored in the CRM 212, or any combination thereof.

[0021] The device diagram for the base station 120, shown in FIG. 2, includes a single network node ( e.g ., a gNode B). The functionality of the base station 120 may be distributed across multiple network nodes or devices and may be distributed in any fashion suitable to perform the functions described herein. The nomenclature for this split base station functionality varies and includes terms such as Central Unit (CU), Distributed Unit (DU), Baseband Unit (BBU), Remote Radio Head (RRH), and/or Remote Radio Unit (RRU). The base station 120 includes antennas 252, a radio frequency front end 254 (RF front end 254), one or more wireless transceivers (e.g, one or more LTE transceivers 256, and/or one or more 5G NR transceivers 258) for communicating with the UE 110. The RF front end 254 of the base station 120 can couple or connect the LTE transceivers 256 and the 5G R transceivers 258 to the antennas 252 to facilitate various types of wireless communication. The antennas 252 of the base station 120 may include an array of multiple antennas that are configured in a manner similar to, or different from, each other. The antennas 252 and the RF front end 254 can be tuned to, and/or be tunable to, one or more frequency bands defined by the 3GPP LTE and 5G R communication standards, and implemented by the LTE transceivers 256, and/or the 5G R transceivers 258. Additionally, the antennas 252, the RF front end 254, the LTE transceivers 256, and/or the 5G R transceivers 258 may be configured to support beamforming, such as Massive multiple-input, multiple-output (Massive-MIMO), for the transmission and reception of communications with the UE 110.

[0022] The base station 120 also includes processor(s) 260 and computer-readable storage media 262 (CRM 262). The processor 260 may be a single-core processor or a multiple-core processor composed of a variety of materials, such as silicon, polysilicon, high-K dielectric, copper, and so on. CRM 262 may include any suitable memory or storage device such as random-access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read only memory (ROM), or Flash memory useable to store device data 264 of the base station 120. The device data 264 includes network scheduling data, radio resource management data, beamforming codebooks, applications, and/or an operating system of the base station 120, which are executable by processor(s) 260 to enable communication with the UE 110.

[0023] CRM 262 also includes a base station manager 266. Alternatively, or additionally, the base station manager 266 may be implemented in whole or in part as hardware logic or circuitry integrated with or separate from other components of the base station 120. In at least some aspects, the base station manager 266 configures the LTE transceivers 256 and the 5GNR transceivers 258 for communication with the UE 110, as well as communication with a core network, such as the core network 150.

[0024] In aspects, the base station manager 266 implements the method for user equipment- aborted full-duplex communication shown in FIG. 8. The base station manager 266 allocates air interface resources to each UE 110 that is served by the base station 120, as discussed in more detail in relation to FIG. 4. Alternatively or additionally, the base station manager 266 generates a schedule for each UE 110, and provides the schedules to a wireless transceiver 256, 258 for transmission to a respective UE 110. At times, the base station manager 266 allocates air interface resources for full- duplex communication to at least one UE 110. In aspects, the base station manager 266 receives an abort indication or a resume indication from the UE 110. In response to receiving an abort indication, the base station manager 266 may reallocate air interface resources to other UEs 110, and generate a new or updated schedule for those UEs. In response to receiving a resume indication, the base station manager 266 may reallocate air interface resources to the UE 110 from which the resume indication was received, and generate an updated schedule for that UE 110.

[0025] The base station 120 also includes an inter-base station interface 268, such as an Xn and/or X2 interface, which the base station manager 266 configures to exchange user-plane data, control-plane information, and/or other data/information between other base stations, to manage the communication of the base station 120 with the UE 110. The base station 120 includes a core network interface 270 that the base station manager 266 configures to exchange user-plane data, control-plane information, and/or other data/information with core network functions and/or entities.

[0026] The base station 120 includes an interference cancellation circuit 272. In some implementations, the interference cancellation circuit 272 suppresses self-interference received by the antennas 252 when the base station 120 transmits a downlink communication. The interference cancellation circuit 272 thus enables the base station 120 to perform full-duplex communication by suppressing or cancelling self-interference. In general, the interference cancellation circuit 272 subtracts a transmitted signal from a received signal. The interference cancellation circuit 272 may be implemented in any suitable manner, using any combination of analog circuitry, digital signal processing circuitry and/or instructions executable by the processor(s) 210. Although the interference circuit 272 is shown as a discrete functional block in FIG. 2, it may be implemented in the RF front end 254, the LTE transceiver(s) 256, the 5GNR transceiver(s) 258, by instructions stored in the CRM 262, or any combination thereof.

Network Stack

[0027] FIG. 3 illustrates an example block diagram 300 of a wireless network stack model 300 (stack 300). The stack 300 characterizes a communication system for the example environment 100, in which various aspects of user equipment-aborted full-duplex communication can be implemented. The stack 300 includes a user plane 302 and a control plane 304. Upper layers of the user plane 302 and the control plane 304 share common lower layers in the stack 300. Wireless devices, such as the UE 110 or the base station 120, implement each layer as an entity for communication with another device using the protocols defined for the layer. For example, a UE 110 uses a Packet Data Convergence Protocol (PDCP) entity to communicate to a peer PDCP entity in a base station 120 using the PDCP.

[0028] The shared lower layers include a physical (PHY) layer 306 (layer- 1), a Medium Access Control (or Media Access Control) (MAC) layer 308 (layer-2), a Radio Link Control (RLC) layer 310 (layer-3), and a PDCP layer 312. The PHY layer 306 provides hardware specifications for devices that communicate with each other. As such, the PHY layer 306 establishes how devices connect to each other, assists in managing how communication resources are shared among devices, and the like.

[0029] The MAC layer 308 specifies how data is transferred between devices. Generally, the MAC layer 308 provides a way in which data packets being transmitted are encoded and decoded into bits as part of a transmission protocol.

[0030] The RLC layer 310 provides data transfer services to higher layers in the stack 300. Generally, the RLC layer 310 provides error correction, packet segmentation and reassembly, and management of data transfers in various modes, such as acknowledged, unacknowledged, or transparent modes.

[0031] The PDCP layer 312 provides data transfer services to higher layers in the stack 300. Generally, the PDCP layer 312 provides transfer of user plane 302 and control plane 304 data, header compression, ciphering, and integrity protection.

[0032] Above the PDCP layer 312, the stack splits into the user-plane 302 and the control- plane 304. Layers of the user plane 302 include an optional Service Data Adaptation Protocol (SDAP) layer 314, an Internet Protocol (IP) layer 316, a Transmission Control Protocol/User Datagram Protocol (TCP/UDP) layer 318, and an application layer 320, which transfers data using the wireless link 106. The optional SDAP layer 314 is present in 5G NR networks. The SDAP layer 314 maps a Quality of Service (QoS) flow for each data radio bearer and marks QoS flow identifiers in uplink and downlink data packets for each packet data session. The IP layer 316 specifies how the data from the application layer 320 is transferred to a destination node. The TCP/UDP layer 318 is used to verify that data packets intended to be transferred to the destination node reached the destination node, using either TCP or UDP for data transfers by the application layer 320. In some implementations, the user plane 302 may also include a data services layer (not shown) that provides data transport services to transport application data, such as IP packets including web browsing content, video content, image content, audio content, or social media content.

[0033] The control plane 304 includes a Radio Resource Control (RRC) layer 324 and a Non- Access Stratum (NAS) layer 326. The RRC layer 324 establishes and releases connections and radio bearers, broadcasts system information, or performs power control. The RRC layer 324 also controls a resource control state of the UE 110 and causes the UE 110 to perform operations according to the resource control state. Example resource control states include a connected state (e.g., an RRC connected state) or a disconnected state, such as an inactive state (e.g., an RRC inactive state) or an idle state (e.g., an RRC idle state). In general, if the UE 110 is in the connected state, the connection with the base station 120 is active. In the inactive state, the connection with the base station 120 is suspended. If the UE 110 is in the idle state, the connection with the base station 120 is released. Generally, the RRC layer 324 supports 3GPP access but does not support non-3GPP access (e.g., WLAN communications).

[0034] The NAS layer 326 provides support for mobility management (e.g., using a Fifth- Generation Mobility Management (5GMM) layer 328) and packet data bearer contexts (e.g., using a Fifth-Generation Session Management (5GSM) layer 330) between the UE 110 and entities or functions in the core network, such as an Access and Mobility Management Function (AMF) of the 5GC 151 or the like. The NAS layer 326 supports both 3GPP access and non-3GPP access.

[0035] In the UE 110, each layer in both the user plane 302 and the control plane 304 of the stack 300 interacts with a corresponding peer layer or entity in the base station 120, a core network entity or function, and/or a remote service, to support user applications and control operation of the UE 110 in the RAN 140.

Air Interface Resources

[0036] FIG. 4 illustrates an air interface resource that extends between a user equipment and a base station and with which various aspects of user equipment-aborted full-duplex communication can be implemented. The air interface resource 402 can be divided into resource units 404, each of which occupies some intersection of frequency spectrum and elapsed time. A portion of the air interface resource 402 is illustrated graphically in a grid or matrix having multiple resource blocks 410, including example resource blocks 411, 412, 413, 414. An example of a resource unit 404 therefore includes at least one resource block 410. As shown, time is depicted along the horizontal dimension as the abscissa axis, and frequency is depicted along the vertical dimension as the ordinate axis. The air interface resource 402, as defined by a given communication protocol or standard, may span any suitable specified frequency range, and/or may be divided into intervals of any specified duration. Increments of time can correspond to, for example, milliseconds (mSec). Increments of frequency can correspond to, for example, megahertz (MHz).

[0037] In example operations generally, the base stations 120 allocate portions ( e.g ., resource units 404) of the air interface resource 402 for uplink and/or downlink communications. As noted previously, full-duplex communicates both uplink and downlink to the same UE on a single air interface resource element 420 while half-duplex communicates either uplink or downlink, but not both, to the same UE on the same air interface resource element 420. Each resource block 410 of network access resources may be allocated to support respective wireless communication links 130 of multiple user equipment 110. In the lower left comer of the grid, the resource block 411 may span, as defined by a given communication protocol, a specified frequency range 406 and includes multiple subcarriers or frequency sub-bands. The resource block 411 may include any suitable number of subcarriers (e.g., 12) that each correspond to a respective portion (e.g, 15 kHz) of the specified frequency range 406 (e.g, 180 kHz). The resource block 411 may also span, as defined by the given communication protocol, a specified time interval 408 or time slot (e.g, lasting approximately one- half millisecond or 7 orthogonal frequency-division multiplexing (OFDM) symbols). The time interval 408 includes subintervals that may each correspond to a symbol, such as an OFDM symbol. As shown in FIG. 4, each resource block 410 may include multiple resource elements 420 (REs) that correspond to, or are defined by, a subcarrier of the frequency range 406 and a subinterval (or symbol) of the time interval 408. Alternatively, a given resource element 420 may span more than one frequency subcarrier or symbol. Thus, a resource unit 404 may include at least one resource block 410, at least one resource element 420, and so forth.

[0038] In example implementations, multiple user equipment 110 (one of which is shown) communicate with the base stations 120 (one of which is shown) through access provided by portions of the air interface resource 302. The base station manager 266 (shown in FIG. 2) may determine a respective data-rate, type of information, or amount of information (e.g., user-plane data or control- plane information) to be communicated (e.g., transmitted) by the user equipment 110. For example, the base station manager 266 determines a different respective transmission data rate and/or a different respective amount of information for each user equipment 110. The base station manager 266 then allocates one or more resource blocks 410 to each user equipment 110 based on the determined data rate or amount of information. [0039] Additionally, or in the alternative to block-level resource grants, the base station manager 266 allocates resource units at an element-level. Thus, the base station manager 266 may allocate one or more resource elements 420 or individual subcarriers to different user equipment 110. This allows the base station manager 266 to allocate (portions of) one resource block 410 to multiple user equipment 110 to facilitate network access. Accordingly, the base station manager 266 may allocate, at various granularities, one or up to all subcarriers or resource elements 420 of a resource block 410 to one user equipment 110 or divided across multiple user equipment 110, thereby enabling higher network utilization or increased spectrum efficiency.

[0040] The base station manager 266 can therefore allocate air interface resource 402 by resource unit 404, resource block 410, frequency carrier, time interval, resource element 420, frequency subcarrier, time subinterval, symbol, spreading code, some combination thereof, and so forth. Based on respective allocations of resource units 404, the base station manager 266 transmits respective messages (each referred to herein as a schedule) to the multiple user equipment 110 indicating the respective allocation of resource units 404 to each user equipment 110. Each message enables a respective user equipment 110 to queue the information or configure the LTE transceiver 206, and/or the 5G NR transceiver 208 to communicate via the allocated resource units 404 of the air interface resource 302.

[0041] While the UE 110 and base station 120 perform full-duplex communication, each transmits and receives using the same resource elements 420. That is, the UE 110 transmits an uplink communication to the base station 120 using one or more subcarriers and during one or more symbols, and receives a downlink communication from the base station 120 using the same one or more subcarriers and during the same one or more symbols. Meanwhile, the base station 120 transmits a downlink communication to, and receives an uplink communication from, the UE 110 using those one or more subcarriers and during those one or more symbols.

User Equipment-Aborted Full-Duplex Communication

[0042] FIG. 5 illustrates an example transaction diagram 500 among various network entities, such as a first UE 111, a second UE 112, and a base station 120, in accordance with various aspects of user equipment-aborted full-duplex communication. For example, the control transaction diagram 500 may be performed by instance(s) of the base station 120 and the UE 110 of FIG. 1, such as those described with reference to FIGs. 1- 4. [0043] At 510, the base station 120 allocates air interface resources to the first UE 111. In implementations, the base station manager 266 of the base station 120 receives scheduling requests for uplink resources from each UE 110 that is served by the base station. The base station manager 266 also analyses the downlink transmission buffer(s) of the base station 120 to determine what data is to be transmitted to each UE 110. The base station manager 266 then allocates air interface resources to some or all of the UEs 110, to allow communication of uplink and downlink control- plane information and/or user-plane data between the UEs 110 and the base station 120.

[0044] At times, the base station 120 allocates air interface resources to the first UE 111 for full-duplex communication. In more detail, the base station 120 identifies one or more time resources (e.g., slots or symbols) and one or more frequency resources (e.g., subcarriers) for use by the UE 111 for transmitting an uplink communication while receiving a downlink communication on the same time and frequency air interface resources.

[0045] The base station manager 266 can schedule the air interface resources for full-duplex communication dynamically or semi-statically. When using dynamic scheduling, the base station manager 266 allocates resources to a UE for each time interval. For example, the base station manager 266 may allocate resources on a slot-by-slot basis. When using semi-static scheduling, the base station manager 266 allocates resources with a certain periodicity to a UE. To illustrate, the base station manager 266 allocates a periodically-occurring set of slots to a UE. The techniques for user equipment-aborted full-duplex communication disclosed herein can be used in conjunction with either, or both, of dynamic scheduling or semi-static scheduling.

[0046] In response to allocating the air interface resources to each UE 110, the base station 120 transmits a schedule 520 to the first UE 111. The schedule 520 identifies air interface resources allocated to the first UE 111 for full-duplex communication. More specifically, the schedule 520 indicates one or more time resources (e.g., slots or symbols) that are allocated to the first UE 111 for full-duplex communication. The schedule 520 also indicates one or more frequency resources (e.g., subcarriers) that are allocated to the first UE 111 for full-duplex communication during those time resources. The schedule 520 may be a dynamic schedule or a semi-static schedule. The schedule 520 may optionally also allocate air interface resources to the first UE 111 for half-duplex communication.

[0047] The base station 120 may also transmit a schedule (not shown in FIG. 5) to other UEs 110, such as the second UE 112. The schedule transmitted to other UEs 110 may allocate air interface resources for full-duplex communication, half-duplex communication, or a combination of both. [0048] At 525, the first UE 111 and the base station 120 perform full-duplex communication with each other using the air interface resources indicated by the schedule 520, such as that described with reference to FIG. 4. At the same time, the base station may also communicate with other UEs 110, such as the second UE 112.

[0049] At 530, the first UE 111 obtains a first set of values of one or more metrics, where each metric is associated with (or otherwise indicative of) the UE’s full-duplex capability. To illustrate, the first UE 111 obtains any combination of an interference level, status of a battery, component temperature(s), received power, transmitter power, error rate, and/or front-end linearity as further described. The first UE 111 may obtain the first set of values before performing full-duplex communication at 525, or the first UE 111 may obtain the first set of values while performing full- duplex-communication. In implementations, the first UE 111 may repeatedly obtain values of the metrics while performing full-duplex communication at 530. In this case, the values of the metrics may be obtained periodically (e.g., every 100 milliseconds) or aperiodically (e.g., in response to detecting the occurrence of a predefined event at the first UE 111). Obtaining the value of a metric may include measuring the value, or retrieving the value from memory (e.g., by reading a value stored in the device data 214 shown in FIG. 2).

[0050] Some non-limiting examples of metrics associated with a UE’s full-duplex capability will now be described. The one or more metrics may include any, or all, of the following example metrics. Alternatively or in addition, the one or more metrics may include a metric other than those described below.

[0051] A first example of a metric is an interference level. The interference level may be quantified as a signal -to-interference-plus-noise ratio (SINR), or quantified in any other suitable manner. For example, the first UE 111 may measure the power of an interference signal received by its RF front end 204 (shown in FIG. 2). The interference signal may include a self-interference component, which is caused by the antennas 202 (shown in FIG. 2) of the first UE 111 receiving uplink signals transmitted by the first UE 111 to the base station 120. The interference signal may also include other interference components. For example, the interference signal may include a component caused by the serving base station 120, or a neighboring (non-serving) base station, transmitting downlink communications to other UEs 110. As another example, the interference signal may include a component caused by other UEs 110 transmitting uplink communications to the serving base station 120 or a neighboring base station. The interference level may adversely affect the ability of the first UE 111 to perform full-duplex communication because, if the interference level is too great, the interference cancellation circuit 218 may be unable to cancel the interfering signals sufficiently. This, in turn, may prevent the first UE 111 receiving and successfully decoding the downlink portion of a full-duplex communication.

[0052] Another example of a metric is the status of a battery of the first UE 111. For example, the status of the battery may include the state of charge of the battery. Alternatively or additionally, the status of the battery may include other parameters that are relevant to the ability of the first UE 111 to sustain full-duplex communication, such as the voltage across the terminals of the battery or the temperature of the battery. The status of the battery can adversely affect the ability of the first UE 111 to perform full-duplex communication because, at times, the first UE 111 may be configured to reduce full-duplex communication to preserve battery power or otherwise reduce the power drawn from the battery.

[0053] Another example of a metric is the temperature of a component of the first UE 111. The component may be, for example, the interference cancellation circuit 218 or the processor(s) 210 (both shown in FIG. 2). The temperature of the component can adversely affect the ability of the first UE 111 to perform full-duplex communication because, at times, the first UE 111 may be configured to reduce full-duplex communication to prevent the temperature exceeding a temperature limit. For example, the temperature limit may be a maximum operating temperature of the component, above which the component risks being damaged or its performance becomes unreliable.

[0054] Another example of a metric is a received power. The received power may be a reference signal received power (RSRP) or a received signal strength indicator (RSSI), for example. The received power may be measured by any of the RF front end 206, LTE transceiver 206 and/or the 5G NR transceiver 208 (all shown in FIG. 2) of the first UE 110. The received power can adversely affect the ability of the first UE 111 to perform full-duplex communication because, if the received power is too low, the first UE 111 may be unable to receive and successfully decode the downlink portion of a full-duplex communication.

[0055] Another example of a metric is a transmitter power of the first UE 111. The transmitter power may be determined by the current value of a parameter stored in the device data 214. Alternatively or in addition, the transmitter power may be measured by any of the RF front end 206, LTE transceiver 206, and/or the 5G NR transceiver 208 of the first UE 111. The transmitter power can adversely affect the ability of the first UE 111 to perform full-duplex communication because, if the transmitter power is too great, the interference cancellation circuit 218 may be unable to cancel interference sufficiently. This, in turn, may prevent the first UE 111 receiving and successfully decoding the downlink portion of a full-duplex communication.

[0056] Another example of a metric is an error rate. The error rate may be a block error rate, a bit error rate, or any other suitable error measurement. The error rate may be measured by the LTE transceiver 206, and/or the 5G NR transceiver 208 of the first UE 111. Error rate can adversely affect the ability of the first UE 111 to perform full-duplex communication because, if the downlink error rate is too great, the first UE 111 may be unable to decode the downlink portion of a full-duplex communication.

[0057] A further example of a metric is the front end linearity of the first UE 111. Front end linearity generally quantifies the ability of the RF front end 204 to amplify signals without introducing distortion. Front end linearity may vary as a function of, for example, carrier frequency, temperature of the RF front end, reference signal received power, and/or transmitter power. Front end linearity power can adversely affect the ability of the first UE 111 to perform full-duplex communication because distortion introduced by non-linearity of the RF front end 204 can prevent the interference cancellation circuit 218 from sufficiently canceling interference. This, in turn, may prevent the first UE 111 receiving and successfully decoding the downlink portion of a full-duplex communication.

[0058] At 540, the first UE 111 determines whether to disable full-duplex communication for some or all of the air interface resources allocated to full-duplex communication by the UE. In some embodiments, the first UE 111 determines whether to disable full-duplex communication based on the first set of values of the one or more metrics obtained at 530. At times, the first UE 111 compares each value with a respective threshold value to determine whether it can perform full-duplex communication, or whether it should disable full-duplex communication partially or completely.

[0059] For example, the UE may determine to disable full-duplex communication partially or completely when any, or all, of the following conditions apply: the interference level is above a threshold interference level; the state of charge of the battery is below a threshold charge; the temperature of the battery and/or another component of the first UE 111 is above a respective threshold temperature; the received power is below a threshold received power; the transmitter power is above a threshold transmitter power; the error rate is above a threshold error rate; and/or the front end linearity is below a threshold linearity. Other metrics may be taken into account when determining whether to disable full-duplex communication.

[0060] If the first UE 111 determines not to disable full-duplex communication at 540, then the first UE 111 continues to perform full-duplex communication. The first UE 111 may iteratively obtain sets of values of the one or more metrics at 530, and determine whether to disable full-duplex communication at 540 based on each set of values. Iteration of blocks 530 and 540 may end when either the time period covered by the schedule 520 has elapsed, or when the first UE 111 determines to disable full-duplex communication.

[0061] If the first UE 111 determines to disable full-duplex communication at 540, it may disable full-duplex communication completely. The first UE 111 is said to disable full-duplex communication completely when it aborts communication with the base station 120 in either the uplink direction or the downlink direction. Thus, in effect, the first UE 111 performs half-duplex communication (i.e., either uplink-only or downlink-only) using the resources that were assigned to the first UE 111 for full-duplex communication. When the first UE 111 determines to disable full- duplex communication completely, the first UE 111 determines not to use any of the air interface resources allocated to it for full-duplex communication (or may determine not to use any remaining scheduled air interface resources, if full-duplex communication has already begun), and determines to use those air interface resources for half-duplex communication instead. The first UE 111 may completely disable full-duplex communication if any or all of the first set of values is indicative of a condition in which the UE 111 should reduce its use of local resources immediately. For example, the first UE 111 may completely disable full-duplex communication if the temperature of one of its components exceeds a temperature at which the component risks being damaged.

[0062] As an alternative to disabling full-duplex communication completely, the first UE 111 may partially disable full-duplex communication. The first UE 111 is said to disable full-duplex communication partially when the first UE 111 performs full-duplex communication using fewer air interface resources than were allocated for full duplex-communication in the schedule 520. In other words, when the first UE 111 determines to disable full-duplex communication partially, the first UE 111 determines not to use a portion of the air interface resources allocated for full-duplex communication.

[0063] At 550, the first UE 111 selects at least a portion of the allocated air interface resources to abort. In other words, the first UE 111 selects or identifies specific air interface resources that have been allocated to it for full-duplex communication, but which will not be used for full-duplex communication. In aspects, the first UE 111 continues to perform full-duplex communication using air interface resources that are not selected at 550. Some non-limiting examples of disabling full- duplex communication are described in the following paragraphs. [0064] In examples of completely disabling full-duplex communication, the first UE 111 selects the direction in which to abort communication based on various criteria, such as:

• The amount of air interface resources allocated to the uplink relative to the amount of air interface resources allocated to the downlink. For example, if fewer air interface resources (e.g., time slots, subcarriers, or a combination of both) have been allocated to either the uplink direction or the downlink direction, the first UE 111 may abort communication in the direction to which fewer resources have been allocated. Aborting communication in the direction to which fewer resources have been allocated maximizes the overall data throughput of the first UE 111, by allowing the first UE 111 to continue communicating in the direction to which more air interface resources have been allocated. The first UE can determine the relative amounts of air interface resources allocated to the uplink and downlink by analyzing the schedule 520.

• The presence of one or more packets with a high importance and/or low latency requirement in an uplink buffer of the first UE 111. In this case, the first UE 111 may abort the downlink direction of a previously-scheduled full-duplex communication resource. This allows such packets to be transmitted at an early opportunity, thereby satisfying the high importance and/or low latency requirement. In some implementations, the first UE 111 analyzes a packet to determine whether it has a high importance and/or low latency requirement. For example, a header of the packet may contain a field indicating a quality of service associated with the packet. As another example, the packet may contain information designating it as an ultra reliable low-latency communication (URLLC) packet.

• A received indication that the base station 120 has one or more packets with a high importance and/or low latency requirement to transmit to the first UE 111. In this case, the first UE 111 may abort a previously-scheduled full-duplex communication resource in the uplink direction. This allows such packets to be received at an early opportunity, thereby satisfying the high importance and/or low latency requirement. The base station 120 analyzes a packet in its downlink buffer to determine whether it has a high importance and/or low latency requirement, in a similar manner to that described above in respect of the UE, and transmits an indication to the first UE 111 accordingly.

• The status of a buffer of the first UE 111. If the uplink buffer of the first UE 111 is close to full capacity, the first UE 111 may abort a previously-scheduled full-duplex communication resource in the downlink direction. This allows the first UE 111 to continue transmitting data stored in its uplink buffer, and reduces the risk of the buffer reaching full capacity. In some implementations, the first UE 111 may have a buffer occupancy threshold. If the current occupancy of the uplink buffer is greater than (or equal to) the buffer occupancy threshold, the first UE 111 may abort a previously-scheduled full-duplex communication resource in the downlink direction.

• Configuration information provided by the base station 120. The configuration information may instruct the first UE 111 to abort full-duplex communication resources in a specific direction when the UE cannot maintain full-duplex capabilities. The configuration can be provided by the base station 120 to the first UE 111 in any suitable manner, such as in a system information block (SIB) or a radio resource control (RRC) message.

[0065] In an example of partially disabling full-duplex communication, the first UE 111 aborts full-duplex communication with the base station 120 during some, but not all, of the time resources allocated to it. For example, at 550, the first UE 111 selects one or more slots in which to disable full-duplex communication. As another example, the first UE 111 selects one or more symbols in which to disable full-duplex communication. Aborting full-duplex communication in some symbols, while continuing full-duplex communication in other symbols, provides the first UE 111 with fine control over its use of resources.

[0066] In another example of partially disabling full-duplex communication, the first UE 111 aborts communication with the base station 120 in specific resource blocks or specific resource elements. To illustrate, the first UE 111 aborts a resource block, or a resource element, such that remaining (non-aborted) resource blocks or resource elements used for full-duplex communication are far apart in a resource grid. For example, consider the resource grid 430 shown in FIG. 4, and assume that the schedule 520 allocates the whole of resource blocks 411, 412, 413 and 414 to the first UE 111 for full-duplex communication. The first UE 111 may select to discontinue all communication using resource blocks 411 and 413. The first UE 111 may further select to abort the downlink portion of resource block 412 and the uplink portion of resource block 414. The first UE 111 may continue to communicate with the base station 120 using the uplink portion of resource block 412 and the downlink portion of resource block 414. Maintaining communication using resources that are non overlapping in both time and frequency (or either time or frequency, if non-overlapping in both is non-feasible) in the resource grid 430 simplifies interference cancellation at the first UE 111.

[0067] After selecting at least a portion of air interface resources to abort at 550, the first UE 111 transmits an abort indication 560 to the base station 120. The abort indication 560 indicates, to the base station 120, that the first UE 111 disabled full-duplex communication using at least a portion of the air interface resources allocated to it for full-duplex communication. The abort indication 560 may be implemented in various ways, some non-limiting examples of which will now be described.

[0068] In a first example of an abort indication 560, the abort indication 560 uses a single modulation symbol. The abort indication modulation symbol can indicate that the first UE 111 has completely disabled full-duplex communication. A modulation symbol is the smallest unit of information that can be transmitted in a 5G NR or similar communication system. Using a single modulation symbol as the abort indication 560 allows the first UE 111 to rapidly signal to the base station 120 that it has disabled full-duplex communication and is using half-duplex. This, in turn, allows the base station 120 to reallocate resources rapidly to the second UE 112. For example, the UE 111 transmits the abort indication modulation symbol in a time interval between the first UE 111 receiving the schedule 520 and the earliest symbol or slot allocated in the schedule 520. The base station 120 may then reallocate air interface resources to the second UE 112 before the earliest symbol or slot to prevent wastage of air interface resources. As another example, the UE 111 transmits the abort indication modulation symbol in the first symbol of a 14-symbol slot allocated to the first UE 111 in the schedule 520. The base station 120 may then reallocate air interface resources to the second UE 112 during at least one subsequent symbol of the same slot, thereby reducing wastage of air interface resources.

[0069] At times, the abort indication modulation symbol may be transmitted using a Physical Uplink Control Channel (PUCCH). For example, the abort indication modulation symbol may be implemented by a transmission in accordance with a short PUCCH format (e.g., PUCCH format 0, as defined in the 5G NR standards). In some implementations, a first abort indication modulation symbol is used to indicate that the first UE 111 has aborted communication in the uplink direction and, optionally, a second (i.e., different) abort indication modulation symbol is used to indicate that the first UE 111 has aborted communication in the downlink direction. In other implementations, the abort indication modulation symbol indicates only that the first UE has completely disabled full- duplex communication, and a message portion (described below) is used to indicate the direction in which the first UE 111 has aborted full-duplex communication.

[0070] In some implementations, the first UE 111 transmits the abort indication modulation symbol to the base station 120 using an air interface resource allocated to the first UE 111 for receiving a downlink communication. For example, the abort indication modulation symbol may puncture a downlink resource element or, in other words, be transmitted using a resource element that is allocated to the downlink.

[0071] In a second example of an abort indication 560, the abort indication 560 uses a message. The message may indicate specific air interface resources that the first UE 111 will not use for full-duplex communication. To illustrate, the message includes a field that identifies the portion of the scheduled full-duplex air interface resources that was selected to be aborted at 550. For example, the message may indicate that the UE completely disabled full-duplex communication. In this example, the message may identify a direction (i.e., the uplink direction or the downlink direction) in which the first UE 111 has disabled full-duplex communication. Alternatively, the message may not explicitly identify the direction in which the first UE 111 has disabled full-duplex communication. In the absence of an explicit identification of the direction in which the first UE 111 has disabled full- duplex communication, it is assumed that the first UE 111 has disabled communication in a default direction (e.g., the uplink direction). As another example, the message identifies a time resource (e.g., at least one symbol, or at least one slot) during which the first UE 111 has disabled full-duplex communication. As a further example, the message identifies a subset of uplink resources and a subset of downlink resources that the first UE 111 will not use. Continuing this example, the message may identify one or more resource blocks or resource elements in which the first UE 111 has aborted the uplink portion or downlink portion, and/or in which the UE has aborted all full-duplex communication.

[0072] Optionally, the message indicates the reason why the first UE 111 has disabled full- duplex communication. As one example, the message includes a field that identifies the metric(s) whose values have caused the first UE 111 to disable full-duplex communication, such as the interference level, the status of its battery, the temperature of a component, received power, transmitter power, an error rate, and/or front end linearity. The base station 120 may optionally use this information when allocating air interface resources in the future, to alleviate or remove the underlying cause of the first UE 111 disabling full-duplex communication.

[0073] In a third example of an abort indication 560, the abort indication 560 includes both a modulation symbol portion and a message portion. The modulation symbol portion is a single modulation symbol, as described above. The message portion uses a message indicating specific air interface resources that the first UE 111 will not use for full-duplex communication and optionally a reason why the first UE 111 has disabled full-duplex communication, also as described above. The first UE 111 may send the modulation symbol portion to the base station 120 before sending the message portion.

[0074] In the preceding examples, the abort indication 560 is described as indicating which air interface resources have been disabled. Alternatively, the abort indication 560 could indicate which air interface resources have been maintained. For example, if the first UE 111 has aborted communication in either the uplink direction or the downlink direction, the abort indication 560 may indicate the direction in which the first UE 111 will continue to communicate. As another example, if the first UE 111 has selected one or more slots or symbols in which to disable full-duplex communication, the abort indication 560 may indicate the slots and/or symbols in which the first UE 111 will continue to perform full-duplex communication. As a further example, if the first UE 111 has selected one or more resource blocks or resource elements in which to disable full-duplex communication, the abort indication 560 may indicate the resource blocks and/or resource elements in which the first UE 111 will continue to perform full-duplex communication.

[0075] The first UE 111 can transmit the abort indication 560 to the base station 120 using any suitable uplink air interface resources. For example, the abort indication 560 may be transmitted using physical layer (layer-1) signaling, MAC layer (layer-2) signaling, RLC layer (layer-3) signaling, or any combination thereof. In some implementations, the abort indication 560 may be transmitted using only the physical layer. In such implementations, the single modulation symbol is a physical layer signal and/or the message is transmitted using the Physical Uplink Shared Channel (PUSCH). In other implementations, the single modulation symbol is a physical layer signal, while the message is transmitted using a MAC layer and/or RLC layer channel. In yet other implementations, the first UE 111 transmits the message using only a MAC layer or RLC layer channel.

[0076] The first UE 111 can transmit the abort indication 560 to the base station 120 using either the same channel or a different channel in the case of carrier aggregation or dual connectivity. To illustrate, assume the first UE 111 and the base station 120 maintain two wireless links with one another: a first (low-band) wireless link that uses sub-6 GHz frequencies and a second (high-band) wireless link that uses above 6 GHz frequencies. In aspects, the first UE 111 communicates the abort indication 560 to the base station 120 using the first (low-band) wireless link, where the abort indication 560 indicates the first UE 111 has disabled full-duplex communications on air interface resources associated with the second (high-band) wireless link. As another example, assume the first UE 111 operates in a dual -connectivity mode with the (first) base station 120 and a second base station (not illustrated in FIG. 5). In aspects, the first UE 111 communicates the abort indication to the (first) base station 120, where the abort indication 560 indicates the first UE 111 has disabled full-duplex communications on air interface resources associated with the second base station. As yet another example, assume the first UE 111 operates using carrier aggregation. In aspects, the first UE 111 communicates the abort indication to the base station 120 using a first carrier frequency (of the carrier aggregation) to indicate the first UE 111 has disabled full-duplex communications on air interface resources associated with a second carrier frequency (of the carrier aggregation).

[0077] The base station 120 receives the abort indication 560 from the first UE 111. In response to receiving the abort indication 560, at 570 the base station 120 reallocates some or all of the air interface resources that were previously allocated (at 510) to the first UE 111 for full-duplex communication, but which the first UE 111 has indicated (using the abort indication 560) it will not use for full-duplex communication. This reallocation supports base station efficiency in supporting multiple UEs. The base station 120 may reallocate some or all of the unused air interface resources to the second UE 112. Optionally, the base station 120 may reallocate the unused air interface resources to a plurality of UEs, including the second UE 112.

[0078] After reallocating resources to the second UE 112, the base station 120 transmits a schedule 580 to the second UE 112. The schedule 580 identifies the air interface resources that were allocated to the second UE 112 at 570. More specifically, the schedule 580 indicates one or more time resources (e.g., slots or symbols) and one or more frequency resources (e.g., subcarriers) that are allocated to the second UE 112. The schedule 580 may allocate air interfaces resources for full- duplex communication, half-duplex communication, or a combination of both. The schedule 580 may be a dynamic schedule or a semi-static schedule. If the base station 120 reallocated air interface resources to any other UEs 110 in addition to the second UE 112, the base station 120 also transmits a schedule (not shown in FIG. 5) to those UEs. At 585, the second UE 112 and the base station 120 communicate with each other using the air interface resources indicated by the schedule 580. The second UE 112 and the base station 120 communicate at 585 using full-duplex, half-duplex, or a combination of both in accordance with the schedule.

[0079] Optionally, the base station 120 transmits a new schedule 590 to the first UE 111. The schedule 590 identifies the air interface resources that are still allocated to the first UE 111, after the reallocation of air interface resources to the second UE 112 at 570. More specifically, the schedule 590 indicates one or more time resources (e.g., slots or symbols) and one or more frequency resources (e.g., subcarriers) that are allocated to the first UE 111. The schedule 590 may allocate air interfaces resources for full-duplex communication, half-duplex communication, or a combination of both. The schedule 590 may be a dynamic schedule or a semi-static schedule. Optionally, if the schedule 520 was a semi-static schedule, the base station 120 does not transmit the schedule 590 to the first UE 111, because the first UE 111 may derive a new schedule by subtracting any air interface resources identified in the abort indication 560 from the air interface resources identified in the schedule 520.

[0080] At 595, the first UE 111 and the base station 120 communicate with each other using the air interface resources that are still allocated to the first UE 111 for full-duplex communication. Communication between the first UE 111 and the base station 120 at 595 may be full-duplex communication, half-duplex communication, or a combination of both in accordance with the schedule. Communication between the first UE 111 and the base station 120 at 595 takes place at the same time as communication between the second UE 112 and the base station 120 at 585.

[0081] FIG. 6 illustrates an example transaction diagram 600 among various network entities, such as a first UE 111, a second UE 112 and a base station 120, in accordance with various aspects of user equipment-aborted full-duplex communication. For example, the control transaction diagram 600 may be performed by instance(s) of the base station 120 and the UE 110 of FIG. 1, such as those described with reference to FIGs. 1-4. The transactions shown in FIG. 6 are, optionally, performed after the transactions shown in FIG. 5. It is thus assumed that, before performing the transactions shown in FIG. 6, the first UE 111 has transmitted an abort indication 560 to the base station 120, and the base station 120 is communicating with at least the second UE 112 in accordance with the schedule 585.

[0082] At 610, the first UE 111 obtains a second set of values of the one or more metrics. The operations performed at 610 are substantially the same as those described in connection with block 530, so need not be described again.

[0083] At 620, the first UE 111 determines whether to resume full-duplex communication. In more detail, if the first UE 111 determined to disable full-duplex communication completely at 540, the first UE 111 determines to perform full-duplex communication at 620. If the first UE 111 determined to disable full-duplex communication partially at 540, the first UE 111 determines to perform full-duplex communication using more air interface resources at 620. In some embodiments, the first UE 111 determines whether to resume full-duplex communication based on the second set of values of the one or more metrics obtained at 610. At times, the first UE 111 may compare each value with a respective threshold value to determine whether to resume full-duplex communication. For example, the UE may determine to resume full-duplex communication when some, or all, of the following conditions apply: the interference level is below a threshold interference level; the state of charge of the battery is above a threshold charge; the temperature of the battery and/or another component of the first UE 111 is below a respective threshold temperature; the received power is above a threshold received power; the transmitter power is above a threshold transmitter power; the error rate is above a threshold error rate; and/or the front end linearity is above a threshold linearity. In this manner, the first UE 111 can resume full-duplex when the condition that caused it to disable full-duplex communication no longer exists, thus allowing the first UE 111 to increase its data throughput. Other metrics may be taken into account when determining whether to resume full- duplex communication.

[0084] If the first UE 111 determines not to resume full-duplex communication at 620, it may iteratively obtain sets of values of the one or more metrics at 610, and determine whether to resume full-duplex communication at 620 based on each set of values. Iteration of blocks 610 and 620 may end when the first UE 111 determines to resume full-duplex communication.

[0085] At 630, the first UE 111 selects air interface resources with which to resume full- duplex communication. In more detail, the first UE 111 in one implementation selects specific air interface resources that were aborted using the abort indication 560, but which can now be used for full-duplex communication. For example, if the first UE 111 aborted communication in the uplink direction or downlink direction at 550, the first UE 111 determines to resume full-duplex communication in that direction at 630. As another example, if the first UE 111 selected one or more slots or symbols in which to abort full-duplex communication at 550, the first UE 111 determines to resume full-duplex communication on some or all of those symbols or slots. As a further example, if the first UE 111 selected specific resource blocks or resource elements in which to abort communication at 550, the first UE 111 determines to resume full-duplex communication on some or all of those resource blocks or resource elements can now be used for full-duplex communication. In other implementations, the UE analyzes the second set of values to select air interface resources, such as time slots and/or frequency ranges where the UE can adequately cancel self-interference, without referencing any prior abort indication.

[0086] After determining to resume full-duplex communication at 620, and after selecting air interface resources with which to resume full-duplex communication at 630, the first UE 111 transmits a resume indication 640 to the base station 120. The resume indication 640 indicates, to the base station 120, that the first UE 111 can perform full-duplex communication using some or all of the air interface resources that were aborted using the abort indication 560. The resume indication 540 may optionally identify specific air interface resources (as selected at 630) that the first UE 111 can now use to perform full-duplex communication. The first UE 111 transmits the resume indication 640 using physical layer (layer-1) signaling, MAC layer (layer-2) signaling, RLC layer (layer-3) signaling, or any combination thereof.

[0087] The base station 120 receives the resume indication 640 from the first UE 111. In response to receiving the resume indication 640, at 650 the base station 120 reallocates some or all of the air interface resources that were previously allocated to the second UE 112 (and optionally other UEs) at 570. The base station 120 reallocates some or all of the air interface resources to the first UE 111 for full-duplex communication. Optionally, the base station 120 reallocates some of the air interface resources to the first UE 111 for half-duplex communication or assigns new air interface resources to the first UE 111 for either full-duplex or half-duplex communication. As a part of this reallocation, the base station 120 may allocate air interface resources to the second UE 112 for full- duplex communication, half-duplex communication, or a combination of both.

[0088] After reallocating resources to the first UE 111, the base station 120 transmits a respective schedule 660, 665 to each of the first UE 111 and the second UE 112. Each schedule 660, 665 identifies the air interface resources that were allocated to the respective UE 111, 112 at 650. More specifically, each schedule 660, 665 indicates one or more time resources (e.g., slots or symbols) and one or more frequency resources (e.g., subcarriers) that are allocated to each UE 111, 112. Each schedule 660, 665 may indicate the allocations of the air interfaces resources for full-duplex communication, half-duplex communication, or a combination of both. Each schedule 660, 665 may be a dynamic schedule or a semi-static schedule. If the base station 120 reallocated all of the air interface resources from the second UE 112 to the first UE 111 without allocating new air interface resources to the second UE 112, the schedule 665 may indicate that no resources are allocated to the second UE 112.

[0089] At 670, the first UE 112 and the base station 120 communicate with each other using full-duplex communication in the air interface resources indicated by the schedule 660. At 675, the second UE 112 and the base station 120 communicate with each other using the air interface resources indicated by the schedule 665. However, if the base station 120 reallocated all of the air interface resources from the second UE 112 to the first UE 111 at 650 without allocating new air interface resources to the second UE 112, the second UE 112 and the base station 120 do not communicate at 675. Example Methods

[0090] Example methods 700 and 800 are described with reference to FIGs. 7 and 8 in accordance with one or more aspects of user equipment-aborted full-duplex communication. The order in which the method blocks are described are not intended to be construed as a limitation, and any number of the described method blocks can be skipped, repeated, or combined in any order to implement a method or an alternate method. Generally, any of the components, modules, methods, and operations described herein can be implemented using software, firmware, hardware (e.g., fixed logic circuitry), manual processing, or any combination thereof. Some operations of the example methods may be described in the general context of executable instructions stored on computer- readable storage memory that is local and/or remote to a computer processing system, and implementations can include software applications, programs, functions, and the like. Alternatively or in addition, any of the functionality described herein can be performed, at least in part, by one or more hardware logic components, such as, and without limitation, Field-programmable Gate Arrays (FPGAs), Application-specific Integrated Circuits (ASICs), Application-specific Standard Products (ASSPs), System-on-a-chip systems (SoCs), Complex Programmable Logic Devices (CPLDs), and the like.

[0091] FIG. 7 illustrates example method(s) 700 of user equipment-aborted full-duplex communication. In implementations, a user equipment performs operations included in the method 700, such as the UE 110 described with reference to FIGs. 1-6 (and, in aspects, the first UE 111 described with reference to FIGs. 5 and 6).

[0092] At 705, the UE 110 receives a schedule from the base station 120. The schedule identifies air interface resources that have been allocated to the UE 110, by the base station 120, for full-duplex communication, and optionally half-duplex communication. For example, the schedule is as described with reference to element 520 of FIG. 5. The schedule may be a dynamic schedule or a semi -static schedule.

[0093] At 710, the UE 110 obtains a first set of values of one or more metrics. For example, the UE 110 obtains a first set of values of one or more metrics as described at 530 of FIG. 5. Each metric is associated with the UE’s full-duplex capability. Obtaining the value of a metric may include measuring the value, or retrieving the value from memory. The metrics may include at least one of: an interference level; a status of a battery of the UE 110; a temperature of a component of the UE 110; a received power; a transmitter power of the UE 110; an error rate; and/or a front end linearity ofthe UE 110. [0094] At 715, the UE 110 determines whether to disable full-duplex communication using some or all of the air interface resources allocated to it. For example, the UE 110 determines whether to disable full-duplex communication as described at 540 of FIG. 5. The UE 110 may determine whether to disable full-duplex communication based on the first set of values of the one or more metrics obtained at 710. For example, the UE 110 may compare each value with a respective threshold value to determine whether it can perform full-duplex communication using all of the air interface resources allocated to it, whether it should disable full-duplex communication partially, or whether it should disable full-duplex communication completely. If the UE 110 determines to disable full-duplex communication, it may select some or all of the allocated air interface resources to abort (disable), as described at 550 of FIG. 5. For example, the UE 110 may determine to disable full- duplex communication completely by disabling communication in either the uplink direction or the downlink direction, while continuing to perform half-duplex communication in the other direction. As another example, the UE 110 may determine to disable full-duplex communication partially, by determining to: disable full-duplex communication using a subset of the time resources (e.g., slots or symbols) allocated to it, while continuing to perform full-duplex communication using the remaining time resources; or disable communication using a subset of uplink resources and a subset of downlink resources allocated to it, while continuing to communicate using the remaining uplink and downlink resources.

[0095] At 720, the UE 110 transmits an abort indication to the base station 120. The abort indication indicates that the UE 110 disabled full-duplex communication using at least a portion of the air interface resources allocated to it for full-duplex communication. For example, the abort indication is as described with reference to element 560 of FIG. 5. The abort indication may identify particular air interface resources that the UE 110 has disabled. For example, the abort indication may identify that the UE 110 has disabled communication in a particular direction (i.e., uplink or downlink). As another example, the abort indication may identify at least one symbol or slot in which the UE 110 has disabled full-duplex communication. As another example, the abort indication may identify specific resource blocks and/or resource elements in which the UE 110 has disabled full- duplex communication.

[0096] At 725, the UE 110 obtains a second set of values of the one or more metrics. The UE 110 may obtain the second set of values in the manner previously described in relation to block 710, and/or as described at block 610 of FIG. 6. [0097] At 730, the UE 110 determines to resume full-duplex communication. More specifically, the UE 110 determines to perform full-duplex communication using more air interface resources. The UE 110 may determine resume to disable full-duplex communication based on the second set of values of the one or more metrics obtained at 725. For example, the UE 110 may compare each value with a respective threshold value to determine whether it can now perform full- duplex communication using all of the air interface resources previously allocated to it, whether it can perform full-duplex communication using more (but not all) of the air interface resources that were previously allocated to it, or whether it should maintain full-duplex communication at the current level. The UE 110 may determine whether to resume full-duplex communication as described at 620 of FIG. 6. The UE 110 may select air interface resources with which to resume full-duplex communication as described at 630 of FIG. 6.

[0098] At 735, the UE 110 transmits a resume indication to the base station 120. The resume indication indicates that the UE 110 can perform full-duplex communication using some or all of the air interface resources that were aborted (disabled) by the abort indication. For example, the resume indication is as described with reference to element 640 of FIG. 6. The resume indication may identify specific air interface resources (e.g., air interface resources selected in the manner described at 630 of FIG. 6) that the UE 110 can use to perform full-duplex communication.

[0099] By performing a method 700 as described with reference to FIG. 7 (and as further described with reference to FIGs. 5 and 6), utilization of air interface resources may be improved. The UE 110 transmits an abort indication to the base station 120 when the UE 110 cannot perform full-duplex communication, and the base station 120 can then reallocate air interface resources to another equipment 112. The other user equipment can thus use air interface resources that would otherwise be wasted, and the utilization of air interface resources is improved. The method 700 can also allow the UE 110 to control the use of full-duplex communication in accordance with one or more local conditions at the UE 110 (e.g., battery status, component temperature etc.). For example, the UE 110 can reduce or stop full-duplex communication, by transmitting an abort indication, when the UE’s battery power is low and/or when the temperature of a component of the UE 110 is high. The UE 110 can later increase or fully resume full-duplex communication, by transmitting a resume indication, when the UE’s battery power is higher and/or when the temperature of the component is lower. [0100] FIG. 8 illustrates example method(s) 800 of user equipment-aborted full-duplex communication. In implementations, a base station performs operations included in the method 800, such as the base station 120 described with reference to FIGs. 1-7.

[0101] At 805, the base station 120 transmits a schedule to the UE 110. The schedule identifies air interface resources that the base station 120 has allocated to the UE 110 for full-duplex communication, and optionally half-duplex communication. For example, the schedule is as described with reference to element 520 of FIG. 5.

[0102] At 810, the base station 120 receives an abort indication from the UE 110. The abort indication indicates that the UE 110 disabled full-duplex communication using at least a portion of the air interface resources allocated to it for full-duplex communication. For example, the abort indication is as described with reference to element 560 of FIG. 5.

[0103] At 815, the base station 120 reallocates at least some of the air interface resources that were previously allocated to the UE 110 for full-duplex communication. The base station 120 reallocates the air interface resources to a second UE. For example, the base station 120 reallocates air interface resources as described at 570 of FIG. 5. At times, the base station 120 reallocates the air interface resources to a plurality of UEs, including the second UE.

[0104] At 820, the base station 120 receives a resume indication from the UE 110. The resume indication indicates that the UE 110 can perform full-duplex communication using some or all of the air interface resources that were aborted (disabled) by the abort indication. For example, the resume indication is as described with reference to element 640 of FIG. 6.

[0105] At 825, the base station 120 reallocates at least some air interface resources from the second UE to the UE 110 from which it received the resume indication. For example, the base station 120 reallocates air interface resources as described at 650 of FIG. 6. The base station 120 may reallocate some, or all, of the air interface resources from the second UE and any other UEs to which resources were reallocated at block 815.

[0106] By performing a method 800 as described with reference to FIG. 8 (and as further described with reference to FIGs. 5 and 6), utilization of air interface resources may be improved. The base station 120 can reallocate air interface resources to at least one other equipment 112 when it receives an abort indication, which indicates that a first user equipment 110 cannot perform full- duplex communication using at least some of the air interface resources allocated to it by the base station 120. The other user equipment 112 can thus use air interface resources that would otherwise be wasted, and the utilization of air interface resources is improved. The method 800 can also reduce latency experienced by the other user equipment 112, by allocating air interface resources to that user equipment sooner than they would have been allocated in accordance with the original schedule 520.

[0107] Further aspects of user equipment-aborted full-duplex communication are disclosed in the following numbered examples.

[0108] Example 1. A method performed by a user equipment for full-duplex communication with a base station, the method comprising: receiving, from the base station, a schedule identifying air interface resources allocated to the user equipment for full-duplex communication; determining to disable full-duplex communication using at least a portion of the allocated air interface resources; and transmitting, to the base station, an abort indication indicating that the user equipment has disabled full-duplex communication using at least a portion of the allocated air interface resources.

[0109] Example 2. The method of example 1, wherein determining to disable full-duplex communication comprises: obtaining, at a first time, a first set of values of one or more metrics associated with full-duplex capability; and determining to disable full-duplex communication based on the first set of values.

[0110] Example 3. The method of example 2, wherein the one or more metrics include at least one of: an interference level; a status of a battery of the user equipment; a temperature of a component of the user equipment; a received power; a transmitter power of the user equipment; or an error rate; a front end linearity of the user equipment.

[0111] Example 4. The method of example 2 or example 3, wherein the method further comprises: obtaining, at a second time occurring after the first time, a second set of values of the one or more metrics; and determining whether or not to resume full-duplex communication based on the second set of values. [0112] Example 5. The method of example 4, further comprising: transmitting a resume indication to the base station in response to determining to resume full- duplex communication, the resume indication indicating that the user equipment can perform full- duplex communication using at least some of the portion of the allocated air interface resources.

[0113] Example 6. The method of example 5, wherein the resume indication identifies at least one symbol or slot in which to perform full-duplex communication.

[0114] Example 7. The method of any of the preceding examples, wherein the abort indication comprises a single modulation symbol.

[0115] Example 8. The method of example 7, further comprising: transmitting the single modulation symbol using an air interface resource allocated to the user equipment for receiving a downlink communication.

[0116] Example 9. The method of example 7 or example 8, further comprising: indicating, using the single modulation symbol, a direction in which the user equipment has disabled or maintained communication with the base station, the direction being one of an uplink direction or a downlink direction.

[0117] Example 10. The method of any of examples 1 to 6, further comprising: identifying, with the abort indication, at least one symbol or slot during which the user- equipment will not perform full-duplex communication.

[0118] Example 11. The method of any of the preceding examples, further comprising: selecting a direction in which to disable communication with the base station, the direction being one of an uplink direction or a downlink direction; and providing, in the abort indication, an indication of one of the direction in which the user equipment has selected to disable communication, or the direction in which the user equipment has not selected to disable communication.

[0119] Example 12. The method of example 11, wherein selecting the direction in which to disable communication comprises: analyzing the schedule to determine whether fewer communication resources are allocated to the uplink direction or the downlink direction; and selecting to disable communication in whichever one of the uplink direction or the downlink direction has fewer resources allocated in the schedule.

[0120] Example 13. The method of example 11, wherein selecting the direction in which to disable communication comprises: identifying a packet with a low latency requirement in an uplink buffer of the user equipment; and selecting to disable communication in the downlink direction in response to identifying the packet with the low latency requirement.

[0121] Example 14. The method of example 11, wherein selecting the direction in which to disable communication comprises: receiving, from the base station, an indication that a packet with a low latency requirement is to be transmitted to the user equipment; and selecting to disable communication in the uplink direction in response to receiving the indication from the base station.

[0122] Example 15. The method of example 11, wherein selecting the direction in which to abort communication comprises: determining that an uplink buffer of the user equipment is filled at or above a threshold; and selecting to disable communication in the downlink direction in response to determining that the uplink buffer is filled at or above the threshold.

[0123] Example 16. The method of any of the preceding examples, further comprising: selecting a subset of uplink resources and a subset of downlink resources from the air interface resources allocated to the user equipment for full-duplex communication; and identifying, in the abort indication, the selected subset of uplink resources and the selected subset of downlink resources.

[0124] Example 17. The method of any of the preceding examples, wherein transmitting the abort indication comprises: transmitting the abort indication in a time interval between receiving the schedule and an earliest symbol or slot identified by the schedule.

[0125] Example 18. A method performed by a base station for full-duplex communication with a first user equipment, the method comprising: transmitting, to the first user equipment, a schedule identifying air interface resources allocated to the first user equipment for full-duplex communication; receiving, from the first user equipment, an abort indication indicating that the first user equipment has disabled full-duplex communication using at least a portion of the allocated air interface resources; and reallocating at least some of the air interface resources for use by a second user equipment. [0126] Example 19. The method of example 18, wherein the abort indication comprises an indication of a direction in which to abort communication, the direction being one of an uplink direction or a downlink direction, and reallocating at least some of the air interface resources comprises: allocating air interface resources to the second user equipment for communication in the direction indicated by the abort indication.

[0127] Example 20. The method of example 19, wherein the abort indication comprises a single modulation symbol.

[0128] Example 21. The method of any of examples 18 to 20, wherein the method further comprises: receiving, from the first user equipment, a resume indication indicating that the first user equipment can resume full-duplex communication; and reallocating air interface resources from the second user equipment to the first user equipment.

[0129] Example 22. A user equipment comprising: a wireless transceiver; a processor; and a computer-readable storage media comprising instructions that, responsive to execution by the processor, cause the user equipment to perform the method of any of examples 1 to 17.

[0130] Example 23. Abase station comprising: a wireless transceiver; a processor; and a computer-readable storage media comprising instructions that, responsive to execution by the processor, cause the base station to perform the method of any of examples 18 to 21.

[0131] A computer-readable storage media comprising instructions that, responsive to execution by a processor, cause an apparatus comprising the processor to perform the method of any one of examples 1 to 21.

[0132] Although aspects of user equipment-aborted full-duplex communication have been described in language specific to features and/or methods, the subject of the appended claims is not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as example implementations of user equipment-aborted full-duplex communication, and other equivalent features and methods are intended to be within the scope of the appended claims. Further, various different aspects are described, and it is to be appreciated that each described aspect can be implemented independently or in connection with one or more other described aspects.

Claims

CLAIMS What is claimed is:

1. A method performed by a user equipment for full-duplex communication with a base station, the method comprising: receiving, from the base station, a schedule identifying air interface resources allocated to the user equipment for full-duplex communication; determining to disable full-duplex communication using at least a portion of the allocated air interface resources; and transmitting, to the base station, an abort indication indicating that the user equipment has disabled full-duplex communication using at least a portion of the allocated air interface resources.

2. The method of claim 1, wherein determining to disable full-duplex communication comprises: obtaining, at a first time, a first set of values of one or more metrics associated with full-duplex capability; and determining to disable full-duplex communication based on the first set of values.

3. The method of claim 1 or claim 2, wherein the method further comprises: obtaining, at a second time occurring after the first time, a second set of values of the one or more metrics; and determining whether or not to resume full-duplex communication based on the second set of values.

4. The method of claim 3, further comprising: transmitting a resume indication to the base station in response to determining to resume full- duplex communication, the resume indication indicating that the user equipment can perform full- duplex communication using at least some of the portion of the allocated air interface resources.

5. The method of any of the preceding claims, wherein the abort indication comprises a single modulation symbol.

6. The method of claim 5, further comprising: indicating, using the single modulation symbol, a direction in which the user equipment has disabled or maintained communication with the base station, the direction being one of an uplink direction or a downlink direction.

7. The method of any of claims 1 to 4, further comprising: identifying, with the abort indication, at least one symbol or slot during which the user- equipment will not perform full-duplex communication.

8. The method of any of the preceding claims, further comprising: selecting a direction in which to disable communication with the base station, the direction being one of an uplink direction or a downlink direction; and providing, in the abort indication, an indication of one of the direction in which the user equipment has selected to disable communication, or the direction in which the user equipment has not selected to disable communication.

9. The method of any of claims 1 to 4, 7 or 8, further comprising: selecting a subset of uplink resources and a subset of downlink resources from the air interface resources allocated to the user equipment for full-duplex communication; and identifying, in the abort indication, the selected subset of uplink resources and the selected subset of downlink resources.

10. A method performed by a base station for full-duplex communication with a first user equipment, the method comprising: transmitting, to the first user equipment, a schedule identifying air interface resources allocated to the first user equipment for full-duplex communication; receiving, from the first user equipment, an abort indication indicating that the first user equipment has disabled full-duplex communication using at least a portion of the allocated air interface resources; and reallocating at least some of the air interface resources for use by a second user equipment.

11. The method of claim 10, wherein the abort indication comprises an indication of a direction in which to abort communication, the direction being one of an uplink direction or a downlink direction, and reallocating at least some of the air interface resources comprises: allocating air interface resources to the second user equipment for communication in the direction indicated by the abort indication.

12. The method of claim 10 or claim 11, wherein the method further comprises: receiving, from the first user equipment, a resume indication indicating that the first user equipment can resume full-duplex communication; and reallocating air interface resources from the second user equipment to the first user equipment.

13. A user equipment comprising: a wireless transceiver; a processor; and a computer-readable storage media comprising instructions that, responsive to execution by the processor, cause the user equipment to perform the method of any of claims 1 to 9.

14. A base station comprising: a wireless transceiver; a processor; and a computer-readable storage media comprising instructions that, responsive to execution by the processor, cause the base station to perform the method of any of claims 10 to 12.

15. A computer-readable storage media comprising instructions that, responsive to execution by a processor, cause an apparatus comprising the processor to perform the method of any one of claims 1 to 12.