WO2017111905A1

WO2017111905A1 - Selection of users for full duplex operation in a cellular system and resources partitioning

Info

Publication number: WO2017111905A1
Application number: PCT/US2015/067091
Authority: WO
Inventors: Konstantinos D. DIMOU; Shu-Ping Yeh; Yang-Seok Choi; Feng Xue; Ping Wang; Shilpa Talwar
Original assignee: Intel Corporation
Priority date: 2015-12-21
Filing date: 2015-12-21
Publication date: 2017-06-29

Abstract

Techniques for facilitating selective full duplex (FD) operation in one or more UEs are discussed. One example apparatus employable in base stations comprises: receiver circuitry receiving from UEs a FD capability, a self-interference cancellation level, a DL channel metric, and an UL transmit power metric; a processor identifying a subset of the UEs based on the FD capability and determining, for each UE of the subset, whether to implement FD mode, based on the self-interference cancellation level, the quality metric, and the UL transmit power metric; and transmitter circuitry transmitting data to each of the one or more UEs, wherein the transmitter circuitry and the receiver circuitry communicate via the FD mode with each UE of the subset for which the processor determined to implement the FD mode, and communicate via a half-duplex mode with other UEs of the one or more UEs.

Description

SELECTION OF USERS FOR FULL DUPLEX OPERATION IN A CELLULAR SYSTEM AND RESOURCES PARTITIONING

FIELD

[0001] The present disclosure relates to wireless technology, and more specifically to techniques for implementing full duplex operation.

BACKGROUND

[0002] Conventional third generation (3G) and fourth generation (4G) wireless systems use radio access technologies (RATs) that employ half-duplex communication techniques, such as frequency division duplex (FDD) or time division duplex (TDD). However, mobile data traffic is expected to increase exponentially over the next decade, leading to increased interest in full duplex (FD) communication techniques to help meet mobile data traffic demands.

BRIEF DESCRIPTION OF THE DRAWINGS

[0003] FIG. 1 is a block diagram illustrating an example user equipment (UE) useable in connection with various aspects described herein.

[0004] FIG. 2 is a diagram illustrating two adjacent cells in a wireless network and a plurality of user equipments (UEs) capable of full duplex (FD) operation according to various aspects described herein.

[0005] FIG. 3 is a block diagram of a system employable in an enhanced node B (eNB) or other base station that facilitates selective operation of one or more user equipments (UEs) in a full duplex (FD) mode according to various aspects described herein.

[0006] FIG. 4 is a block diagram of a system employable in a user equipment (UE) or other mobile terminal that facilitates selective operation of the UE in a full duplex (FD) mode according to various aspects described herein.

[0007] FIG. 5 is a flow diagram illustrating a method of facilitating selective FD operation of one or more UEs based on an FD metric according to various aspects described herein.

[0008] FIG. 6 is a flow diagram illustrating a method of facilitating selective FD operation of a FD-capable UE according to various aspects described herein. [0009] FIG. 7 is a flow diagram illustrating an example method of selectively implementing a FD mode at a UE according to various aspects described herein.

[0010] FIG. 8 is a diagram illustrating example information elements that can facilitate selective operation of a FD mode according to various aspects described herein.

[0011] FIG. 9 is a diagram illustrating two adjacent cells in a wireless network and a plurality of UEs selectively operating in a FD mode according to various aspects described herein.

[0012] FIG. 10 is a flow diagram illustrating an example method of implementing fractional frequency reuse (FFR) in connection with selective operation of a FD mode at one or more UEs according to various aspects described herein.

[0013] FIG. 11 is a diagram illustrating two adjacent cells in a wireless network implementing FFR in combination with FD in connection with a first example scenario in which there is no detected BS to BS interference according to various aspects described herein.

[0014] FIG. 12 is a diagram illustrating two adjacent cells in a wireless network implementing FFR in combination with FD in connection with a second example scenario in which there is detected BS to BS interference according to various aspects described herein.

DETAILED DESCRIPTION

[0015] The present disclosure will now be described with reference to the attached drawing figures, wherein like reference numerals are used to refer to like elements throughout, and wherein the illustrated structures and devices are not necessarily drawn to scale. As utilized herein, terms "component," "system," "interface," and the like are intended to refer to a computer-related entity, hardware, software (e.g., in execution), and/or firmware. For example, a component can be a processor (e.g., a microprocessor, a controller, or other processing device), a process running on a processor, a controller, an object, an executable, a program, a storage device, a computer, a tablet PC and/or a user equipment (e.g., mobile phone, etc.) with a processing device. By way of illustration, an application running on a server and the server can also be a component. One or more components can reside within a process, and a component can be localized on one computer and/or distributed between two or more computers. A set of elements or a set of other components can be described herein, in which the term "set" can be interpreted as "one or more."

[0016] Further, these components can execute from various computer readable storage media having various data structures stored thereon such as with a module, for example. The components can communicate via local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network, such as, the Internet, a local area network, a wide area network, or similar network with other systems via the signal).

[0017] As another example, a component can be an apparatus with specific functionality provided by mechanical parts operated by electric or electronic circuitry, in which the electric or electronic circuitry can be operated by a software application or a firmware application executed by one or more processors. The one or more processors can be internal or external to the apparatus and can execute at least a part of the software or firmware application. As yet another example, a component can be an apparatus that provides specific functionality through electronic components without mechanical parts; the electronic components can include one or more processors therein to execute software and/or firmware that confer(s), at least in part, the functionality of the electronic components.

[0018] Use of the word exemplary is intended to present concepts in a concrete fashion. As used in this application, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or". That is, unless specified otherwise, or clear from context, "X employs A or B" is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then "X employs A or B" is satisfied under any of the foregoing instances. In addition, the articles "a" and "an" as used in this application and the appended claims should generally be construed to mean "one or more" unless specified otherwise or clear from context to be directed to a singular form. Furthermore, to the extent that the terms "including", "includes", "having", "has", "with", or variants thereof are used in either the detailed description and the claims, such terms are intended to be inclusive in a manner similar to the term

"comprising."

[0019] As used herein, the term "circuitry" may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some embodiments, circuitry may include logic, at least partially operable in hardware.

[0020] Embodiments described herein may be implemented into a system using any suitably configured hardware and/or software. FIG. 1 illustrates, for one embodiment, example components of a User Equipment (UE) device 100. In some embodiments, the UE device 100 may include application circuitry 102, baseband circuitry 104, Radio Frequency (RF) circuitry 106, front-end module (FEM) circuitry 108 and one or more antennas 1 10, coupled together at least as shown.

[0021] The application circuitry 102 may include one or more application processors. For example, the application circuitry 102 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors may be coupled with and/or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems to run on the system.

[0022] The baseband circuitry 104 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 104 may include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry 106 and to generate baseband signals for a transmit signal path of the RF circuitry 106. Baseband processing circuity 104 may interface with the application circuitry 102 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 106. For example, in some embodiments, the baseband circuitry 104 may include a second generation (2G) baseband processor 104a, third generation (3G) baseband processor 104b, fourth generation (4G) baseband processor 104c, and/or other baseband processor(s) 104d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.). The baseband circuitry 104 (e.g., one or more of baseband processors 104a-d) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 106. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry 104 may include Fast-Fourier Transform (FFT), precoding, and/or constellation

mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry 104 may include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality.

Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

[0023] In some embodiments, the baseband circuitry 104 may include elements of a protocol stack such as, for example, elements of an evolved universal terrestrial radio access network (EUTRAN) protocol including, for example, physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), and/or radio resource control (RRC) elements. A central processing unit (CPU) 104e of the baseband circuitry 104 may be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers. In some embodiments, the baseband circuitry may include one or more audio digital signal processor(s) (DSP) 104f. The audio DSP(s) 104f may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments. Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry 104 and the application circuitry 102 may be implemented together such as, for example, on a system on a chip (SOC).

[0024] In some embodiments, the baseband circuitry 104 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 104 may support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Embodiments in which the baseband circuitry 104 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0025] RF circuitry 106 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 106 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 106 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 108 and provide baseband signals to the baseband circuitry 104. RF circuitry 106 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 1 04 and provide RF output signals to the FEM circuitry 108 for transmission.

[0026] In some embodiments, the RF circuitry 106 may include a receive signal path and a transmit signal path. The receive signal path of the RF circuitry 106 may include mixer circuitry 1 06a, amplifier circuitry 106b and filter circuitry 106c. The transmit signal path of the RF circuitry 106 may include filter circuitry 106c and mixer circuitry 106a. RF circuitry 106 may also include synthesizer circuitry 106d for synthesizing a frequency for use by the mixer circuitry 106a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 106a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 108 based on the synthesized frequency provided by synthesizer circuitry 106d. The amplifier circuitry 106b may be configured to amplify the down-converted signals and the filter circuitry 106c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 104 for further processing. In some embodiments, the output baseband signals may be zero- frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 1 06a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

[0027] In some embodiments, the mixer circuitry 106a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 106d to generate RF output signals for the FEM circuitry 108. The baseband signals may be provided by the baseband circuitry 104 and may be filtered by filter circuitry 1 06c. The filter circuitry 1 06c may include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.

[0028] In some embodiments, the mixer circuitry 106a of the receive signal path and the mixer circuitry 106a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and/or upconversion respectively. In some embodiments, the mixer circuitry 106a of the receive signal path and the mixer circuitry 106a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 1 06a of the receive signal path and the mixer circuitry 106a may be arranged for direct downconversion and/or direct upconversion, respectively. In some embodiments, the mixer circuitry 106a of the receive signal path and the mixer circuitry 106a of the transmit signal path may be configured for super-heterodyne operation.

[0029] In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate embodiments, the RF circuitry 106 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 104 may include a digital baseband interface to communicate with the RF circuitry 106.

[0030] In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the

embodiments is not limited in this respect.

[0031] In some embodiments, the synthesizer circuitry 106d may be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 106d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[0032] The synthesizer circuitry 106d may be configured to synthesize an output frequency for use by the mixer circuitry 106a of the RF circuitry 1 06 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 106d may be a fractional N/N+1 synthesizer.

[0033] In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the baseband circuitry 104 or the applications processor 102 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 1 02.

[0034] Synthesizer circuitry 1 06d of the RF circuitry 106 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by either N or N+1 (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip- flop. In these embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0035] In some embodiments, synthesizer circuitry 1 06d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be a LO frequency (fLO). In some embodiments, the RF circuitry 106 may include an IQ/polar converter.

[0036] FEM circuitry 108 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 1 10, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 106 for further processing. FEM circuitry 108 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 106 for transmission by one or more of the one or more antennas 1 1 0.

[0037] In some embodiments, the FEM circuitry 108 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 106). The transmit signal path of the FEM circuitry 108 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 106), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 1 1 0. [0038] In some embodiments, the UE device 100 may include additional elements such as, for example, memory/storage, display, camera, sensor, and/or input/output (I/O) interface.

[0039] Various embodiments disclosed herein can facilitate selective operation of one or more UEs (or other mobile devices) in a FD mode of operation to efficiently employ FD mode in appropriate situations, and employ a half-duplex mode (e.g., FDD or TDD) in situations in which the FD mode is not appropriate.

[0040] In various aspects, techniques disclosed herein can address the situation in a wireless network in which one or more network nodes (e.g., base stations such as evolved Node Bs (eNBs), relay nodes, etc.) are capable of operating in a full duplex (FD) mode and one or more mobile terminals (e.g., User Equipments (UEs), etc.) are also capable of operating in a FD mode. For example, in a wireless system employing either a Time Division Duplex (TDD) or a Frequency Division Duplex (FDD) mode wherein one or more network nodes and one or more UEs are capable of operation in a FD mode, a decision arises for the network operator as to which UEs (among the ones capable of operating in the FD mode) to select for FD operation.

[0041] Referring to FIG. 2, illustrated is a diagram of two adjacent cells in a wireless network and a plurality of user equipments (UEs) capable of full duplex (FD) operation according to various aspects described herein. Each of the nodes 210, and each of the illustrated UEs 220, can operate in the Full Duplex (FD) mode (in general, such a system can also include one or more additional UEs not capable of the FD mode (not shown)). In the FD mode, each UE 220, can transmit and receive at the same frequency and time slot by canceling the self-interference generated internally. The decision that arises for the entity operating the network (the network operator) is, for each UE 220, supporting the FD mode of operation, whether to employ the FD mode for that UE 220,. In addition, the network operator also faces decisions regarding which resources to grant for the UEs 220, selected to operate in the FD mode.

[0042] These issues arise because, although operation in the FD mode can increase the data rates of users (and consequently, system capacity) and reduce latency, operation in FD mode generates effects at both the network and terminal side that can be difficult to deal with. At the system/network level, FD operation generates a high level of interference at the base station, as well as some additional types of interference such as "Base Station (BS) to BS interference" and "UE to UE interference," which can be challenging to manage when several UEs operate in the FD mode. This increased interference results in lower system capacity and higher service latency. At the mobile terminal level, if UE to UE interference is not managed properly, the number of erroneous transmissions increases, resulting in reduced data rate, increased latency and higher terminal power consumption. An additional challenge is that sometimes the self-interference cancellation level within the UE sufficient for FD mode to be advantageous can be difficult to achieve, which can result in many losses.

[0043] In various embodiments, one or more UEs capable of operation in a FD mode can be selectively operated in the FD mode, wherein the UEs selected for operation in the FD mode can be the UEs for which the FD mode results in higher data rates, lower latency, and higher overall system capacity, and those UEs can cancel the self- interference level to enable advantageous operation in the FD mode. The higher data rates can be achieved via managed (controlled) UE to UE interference and BS to BS interference and via selection for FD mode of the UEs that generate and receive the lowest levels of interference.

[0044] In various aspects, improved data rates and capacity, along with reduced latency, can be achieved via two criteria. First, operation in the FD mode can be selected for those UEs for which the self-interference capabilities exceed the level of self-interference to be canceled for advantageous FD operation by a threshold value (e.g., a SelflnterferenceCancellationRequirementThreshold, etc.) associated with the FD mode (with other FD-capable UEs (e.g., those UEs not capable of canceling sufficient self-interference for advantageous FD operation, etc.) operating in a half- duplex mode such as TDD or FDD). Second, the resources employed for FD operation within neighbor cells can be orthogonal in one or more of time, frequency, space or code resources between the neighbor cells.

[0045] The first criterion can ensure that that UEs selected to operate in the FD are capable of canceling their self-interference when operating in the FD mode. The second criterion can guarantee that the BS and BS as well as the UE to UE interference are minimal, if not 0.

[0046] Referring to FIG. 3, illustrated is a block diagram of a system 300 employable in an enhanced node B (eNB) or other base station to facilitate selective operation of one or more user equipments (UEs) in a full duplex (FD) mode according to various aspects described herein. System 300 can include receiver circuitry 31 0, a processor 320, transmitter circuitry 330, and memory 340 (which can comprise any of a variety of storage mediums and can store instructions and/or data associated with one or more of receiver circuitry 310, processor 320, or transmitter circuitry 330). In various aspects, system 300 can be included within an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (Evolved Node B, eNodeB, or eNB) or other base station in a wireless communications network. As described in greater detail below, system 300 can facilitate efficient use of a FD mode of operation via selecting one or more UEs to operate in the FD mode.

[0047] Receiver circuitry 310 can receive from one or more FD-capable UEs, a set of information associated with FD operation. In various embodiments, the set of information can be received via an information element (IE) of a radio resource control (RRC) message. For example, this set of information can be received via a RRC message associated with UE capability information, and can be included within an IE dedicated to communication of FD information. In other aspects, capability of FD operation and a minimum self-interference cancellation level can be associated with defined UE categories, and some or all of this information can thus be conveyed via an indication of the category of the UE.

[0048] In some aspects, the set of information received by receiver circuitry 310 can include one or more of an indication that a UE is capable of operating in the FD mode, a level of self-interference that UE is capable of achieving, a reference signal (RS) received power (RSRP) or RS received quality (RSRQ) (or other downlink (DL) channel metric) associated with signals received at the UE from the eNB employing system 300, and an indication of the uplink (UL) transmit power of the UE (e.g., a power headroom (PHR) received via a medium access control (MAC) protocol, etc.). In other aspects, the set of information can include information based on the above. For example, in some embodiments, receiver circuitry 310 can receive an indication of FD capability, a self- interference cancellation level, and a difference between a transmit power of the UE and the RSRP (e.g., the amount by which the UE transmit power exceeds the RSRP, etc.). In another example, receiver circuitry 310 can receive an indication of FD capability, and an amount by which the self-interference cancellation level exceeds the difference between the transmit power of the UE and the RSRP. In a further example, receiver circuitry 310 can receive an indication of FD capability, and an indication of whether the self-interference cancellation level exceeds the difference between the transmit power of the UE and the RSRP by at least a FD threshold value (in various aspects, the FD threshold value can be predetermined, or configured to the UE, such as via higher layer signaling, etc.), or a value indicating an extent to which the self- interference minus the FD threshold value exceeds that difference. In aspects, receiver circuitry 31 0 can receive an indication from one or more additional UEs indicating each of those additional UEs is incapable of the FD mode (alternatively, no such information can be received from the one or more additional UEs, and processor 320 can determine those additional UEs is incapable of the FD mode based on the lack of an indication that those additional UEs are capable of the FD mode).

[0049] Processor 320 can identify the set of FD-capable UEs based on the received indications of FD capability from those UEs. Additionally, processor 320 can determine, for each UE capable of the FD mode, whether to implement the FD mode for that UE, which can be based at least in part on the set of information associated with FD operation received from that UE. In various aspects, processor 320 can calculate a FD metric based at least in part on the received set of information to determine whether to select the FD mode for that UE. The FD metric can involve a calculation of whether a first difference between the self-interference cancellation level of the UE and an FD threshold level (e.g., that can, in aspects, be configured via processor 320) exceeds a second difference between the transmit power of the UE and the RSRP. In some aspects, receiver circuitry 310 can receive an indication of the transmit power of the UE. In other aspects, processor 320 can determine the transmit power of the UE based on the received UL channel metric and known properties of the UE (e.g., given a received PHR value and a known maximum transmit power, the transmit power of the UE can be determined, etc.). In various aspects, processor 320 can employ one or more additional criteria in deciding whether to implement the FD mode for some or all FD-capable UEs. For each FD-capable UE, these additional criteria can include a traffic priority

associated with that UE or power consumption considerations associated with that UE, etc. Processor 320 can select a half-duplex mode for each other UE communicating with the eNB comprising system 300 (e.g., non-FD capable UEs, as well as FD-capable UEs not selected for the FD mode, etc.).

[0050] Transmitter circuitry 330 can transmit an indication of the selected mode (e.g., FD or half-duplex) to some or all of the UEs communicating with system 300 (e.g., those UEs capable of operating in the FD mode, or all communicating UEs, etc.). Transmitter circuitry 330 and receiver circuitry 31 0 can communicate with each UE via the selected mode for that UE.

[0051] Additionally, processor 320 can assign a set of resources for FD operation in the cell (and a different (e.g., orthogonal) set of resources for half-duplex operation in the cell), and can assign UEs selected for the FD mode subsets of those resources. In various aspects, system 300 can communicate with one or more neighboring base stations (e.g., via receiver circuitry 31 0 and transmitter circuitry 330, or via additional receiver circuitry and transmitter circuitry (not shown), over wired backhaul, etc.).

System 300 and the neighboring base stations can coordinate resources assigned for the FD mode, such that resource assignments can be coordinated between system 300 and the neighboring base stations so as to reduce BS to BS interference. For example, messages can be transmitted between system 300 and a neighboring base station to determine a level of interference with the neighboring base station. Processor 320 can calculate whether the determined level of interference exceeds a threshold BS-to-BS interference level, transmitter circuitry 330 can communicate that level of interference or determination, and receiver circuitry 310 can receive a level of interference determined by the neighboring BS or a determination that it exceeds a threshold. If either of the determined levels of interference exceeds the threshold BS-to-BS interference level (e.g., more than minimal interference), processor 320 and the neighboring BS can assign sets of resources for the FD mode that are orthogonal to one another (e.g., in one or more of time, frequency, space, code, etc.). In the event the base station employing system 300 and a neighboring base station have more than minimal interference and are not synchronized, some margin can be provided between the assigned sets of resources to ensure that the resources employed remain orthogonal. On the other hand, if neither of the determined levels of interference does not exceed the threshold BS-to-BS interference level (e.g., minimal interference), processor 320 and the neighboring BS can assign sets of resources for the FD mode that are at least partially non-orthogonal.

[0052] Referring to FIG. 4, illustrated is a block diagram of a system 400 that facilitates selective operation of a UE in a full duplex (FD) mode according to various aspects described herein. System 400 can include receiver circuitry 41 0, a processor 420, transmitter circuitry 430, and a memory 440 (which can comprise any of a variety of storage mediums and can store instructions and/or data associated with one or more of receiver circuitry 410, processor 420, or transmitter circuitry 430). In various aspects, system 400 can be included within a user equipment (UE) or other mobile terminal capable of operating in a FD mode. As described in greater detail below, system 400 can facilitate selective implementation of FD mode based on a set of UE properties. [0053] Receiver circuitry 410 can receive transmissions from an eNB or other base station can that can include one or more reference signals (RSs).

[0054] Based on the one or more RSs, processor 420 can calculate a DL channel metric such as a RSRP or a RSRQ, etc. In some aspects, processor 420 can optionally calculate one or more quantities. These quantities can include one or more of: a first difference between an uplink (UL) transmit power of system 400 and the DL channel metric, a second difference between a self-interference cancellation level of which the UE employing system 400 is capable and a FD threshold value, an amount by which the self-interference cancellation level exceeds the first difference, or whether (or by how much) the second difference exceeds the first difference. In aspects in which processor 420 calculates one or more quantities involving the FD threshold value, the FD threshold value can be configured to the UE (e.g., via higher layer signaling), or can be predetermined, etc.

[0055] Transmitter circuitry 430 can transmit a set of FD information, which can vary depending on the embodiment. In some embodiments, transmitter circuitry 430 can transmit an indication that system 400 is capable of operating in a FD mode, a self- interference cancellation level, the DL channel metric, and a quantity associated with UL transmit power (e.g., PHR, etc.). In other aspects, one or more of the optional quantities calculated by processor 420 can be transmitted additionally or alternatively to some or all of the self-interference cancellation level, the DL channel metric, and the quantity associated with UL transmit power. In some aspects, some of this information (e.g., capability to operate in the FD mode, self-interference cancellation level, etc.) can be transmitted via indicating a category of the UE employing system 400. In other aspects, some or all of this information can be transmitted via a RRC IE dedicated to signaling FD information.

[0056] Receiver circuitry 410 can receive an indication of a communication mode selected for system 400, which can be the FD mode or can be a half-duplex mode (e.g., FDD or TDD). Receiver circuitry 410 and transmitter circuitry 430 can communicate via the indicated communication mode until a different communication mode is indicated.

[0057] Referring to FIG. 5, illustrated is a flow diagram of a method 500 that facilitates selective FD operation of one or more UEs based on an FD metric according to various aspects described herein. In some aspects, method 500 can be performed at an eNB. In other aspects, a machine readable medium can store instructions associated with method 500 that, when executed, can cause an eNB to perform the acts of method 500.

[0058] At 510, a level of interference with one or more neighboring base stations or eNBs can be determined. This can involve transmitting messages between the eNB implementing method 500 and the one or more neighboring eNBs, from which the level of interference can be determined and compared to a threshold interference level to determine if the level of interference exceeds an acceptable minimum.

[0059] At 520, optionally, resources for FD mode operation can be assigned based on the level(s) of interference optionally determined at 510. For example, if the determined interference is at or below an acceptable minimum based on a threshold, the eNB implementing method 500 and the neighboring eNB can assign overlapping resources for the FD mode. On the other hand, if if the determined interference is at or below an acceptable minimum based on a threshold, the eNB implementing method 500 and the neighboring eNB can assign orthogonal sets of resources (e.g., in time, frequency, space, code, etc.) for the FD mode, to minimize BS-to-BS interference. In the event the BS and the neighboring BS are not synchronized, a margin can be provided between the orthogonal sets to prevent accidental use of non-orthogonal resources.

[0060] At 530, a set of FD information can be received from each of one or more UEs. The set of FD information can indicate whether the associated UE is capable of operating in an FD mode. Additionally, at least from the FD-capable UEs, the set of FD information can include one of an FD metric indicating whether the UE can efficiently operate in the FD mode, or information from which the eNB implementing method 500 can determine the FD metric (e.g., DL channel metric, UL transmit power metric (e.g., PHR), self-interference cancellation level, or quantities derived therefrom).

[0061] At 540, an FD metric can be determined for each FD capable UE if an FD metric was not received from that FD-capable UE. In one example, a first difference can be determined between an UL transmit power (which can itself be calculated from a PHR and a known maximum transmit power of the UE) and a DL channel metric such as an RSRP. A second difference can be calculated between a self-interference cancellation level of the UE and a FD threshold value (e.g., which can be set by the eNB implementing method 500, etc.).

[0062] At 550, FD mode or half-duplex mode can be selected for each FD-capable UE. For example, if the second difference exceeds the first difference, FD mode can be implemented (in aspects, one or more additional criteria can also be considered, as discussed herein).

[0063] At 560, each UE can be communicated with via the selected mode, which can optionally be preceded by, for example, communicating an indication of the selected mode for that UE (e.g., in all situations, or only when the selected mode for a UE differs from a current mode, etc.).

[0064] Referring to FIG. 6, illustrated is a flow diagram of a method 600 that facilitates selective FD operation of a FD-capable UE according to various aspects described herein. In some aspects, method 600 can be performed at a UE. In other aspects, a machine readable medium can store instructions associated with method 600 that, when executed, can cause a UE to perform the acts of method 600.

[0065] At 610, one or more reference signals (RSs) can be received from an eNB.

[0066] At 620, a DL channel metric (e.g., RSRP, RSRQ, etc.) can be calculated based at least in part on the one or more received RSs.

[0067] At 630, an FD metric or one or more associated quantities (e.g., the first difference or the second difference as discussed herein) can be calculated.

[0068] At 640, a set of FD information can be transmitted, which can include an indication that the UE implementing method 600 is FD-capable, as well as either the FD metric or information from which a receiving eNB can calculate the FD metric (e.g., the first difference and second difference; or a self-interference cancellation level, DL channel metric, and UL transmit power metric; etc.).

[0069] At 650, an indication of an operating mode can be received that indicates one of the FD mode or a half-duplex mode (e.g., FDD or TDD).

[0070] At 660, the UE can communicate with the eNB via the indicated mode.

[0071] Referring to FIG. 7, illustrated is a flow diagram of an example method 700 of selectively implementing a FD mode at a UE according to various aspects described herein. In some aspects, method 700 can be performed at an eNB. In other aspects, a machine readable medium can store instructions associated with method 700 that, when executed, can cause an eNB to perform the acts of method 700.

[0072] At 710, the base station (e.g., eNB, etc.) can collect information about the capability of the UE to operate in Full Duplex mode, which can include the UE informing the eNB of a level of self-interference (e.g., SELFIC_Level) that the UE can cancel. In addition, the UE can transmit collected information on the Reference Symbol Received Power (RSRP) measured from the serving cell (e.g., RSRP_serving). The base station (BS) can collect information on the transmitted power level in uplink by the UE as well (e.g., P_Tx_UI).

[0073] At 720, the BS checks whether the difference between the transmitted power in uplink (e.g., P_Tx_UI) and the RSRP from the serving cell (e.g., RSRP_serving) is greater or lesser than the level of self-interference cancellation (e.g., SELFIC_Level) which can be achieved by the UE plus a margin representing an FD threshold value (e.g., delta).

[0074] If the difference between the uplink transmitted power level and the received power level is smaller than the level of self-interference cancellation the UE is able to achieve as modified by the FD threshold value {delta), then the UE can operate at Full Duplex Mode, and the eNB can signal FD mode operation, as seen at 730.

[0075] If the amount of self-interference to be suppressed for FD mode (e.g., the difference between the transmitted {P_Tx_UI) and the received power (RSRP_serving)), is higher than the level of self-interference the UE can suppress as modified by the FD threshold value {delta), then the UE can operates at the half-duplex mode the network supports (either Frequency Division Duplex (FDD) or Time Division Duplex (TDD) mode), and the eNB can signal half-duplex mode operation, as seen at 740.

[0076] In some aspects, UEs allowed to operate in FD mode within the same cell can be scheduled orthogonally in one or more of frequency, time, code or space resources.

[0077] In the same or other aspects, the comparison at step 720 can be done by using RS Received Quality (RSRQ) values, which take into consideration the

interference received by the UE. The value of the threshold delta) can be updated accordingly. If the uplink reference signals of UEs in the area are known, FD mode can be facilitated at an uplink band or at an uplink slot.

[0078] In various embodiments, for a UE selected to operate in the FD mode that receives high interference (e.g., the UE reports during a time window (T) CQI or CSI values below a threshold, or the UE transmits a number of NACKs above a threshold), the BS can stop the FD operation for that UE.

[0079] In various embodiments, not all the UEs capable of operation in FD mode and for which the metric of method 700 or other metrics indicate FD mode will operate at FD mode. This decision can be made by the scheduler at the network, and can be based on several other criteria, e.g., UE traffic priority, UE power consumption, etc. [0080] The RSRP from the serving base station can be reported from UEs to the network via the Radio Resource Control (RRC) message "Measurement Report," as discussed in § 6.2.2 of the 3GPP (Third Generation Partnership Project) Technical Specification (TS) 36.331 "Radio Resource Control (RRC) Protocol Specification" version 12.4.1 . This information can be contained in the field "MeasResults," which contains the information element (IE), "rsrpResult." A UE can report measurements when an event is triggered. One of the events which can trigger the event reporting can be that the RSRP from the serving BS becomes better than a threshold, which is the event A1 as in § 6.3.5 of the 3GPP TS 36.331 . The configuration of the measurements to be reported can be done with the help of the RRC message "Measurement Control," which contains the IE "reportConfigEUTRA." In addition, the BS can deduce the uplink transmission power level (e.g., P_Tx_Uf) of the UE by knowing the maximum transmission power level of the UE and the power headroom, PHR, which the UE reports via the Medium Access Control (MAC) protocol specification, as in § 5.4.6 of the 3GPP TS 36.321 "Medium Access Control (MAC) Protocol Specification", version 12.4.0. The power headroom is the difference between the nominal UE Tx Power, Pcmax, and the estimated transmission power of the uplink data channel. Different types of power headroom can be reported depending on the carrier aggregation and dual connectivity operation mode. Similarly to RSRP reporting manner, RSRQ can be reported as well in the current 3GPP specifications.

[0081] However, current 3GPP systems do not provide for reporting the UE self- interference suppression capability, and, for UEs capable of suppressing self- interference, the level of it. One method for conveying this information to the network is via the RRC message "UECapabilitylnformation," as discussed in § 5.6.3.1 of the 3GPP TS 36.331 . This message contains the IE "UE-EUTRA-Capability." This IE contains the UE category as well as all of the relevant parameters indicating the UE capabilities in every layer. Information on the capability of FD operation can be added there according to various aspects discussed herein. Referring to FIG. 8, illustrated is an example modified RRC message "UECapabilitylnformation" containing a new information element related to the FD capability of a UE, which can be employed in various embodiments discussed herein.

[0082] Alternatively, the FD capability can be a part of the "UE-Category" information. [0083] In various aspects, a UE can perform the comparison discussed in 720 of method 700 and report the result of the comparison to the network, which can be via one of the new or modified lEs discussed herein.

[0084] An effect of method 700 is that UEs in a zone around the serving BS can be allowed to operate at FD mode, particularly when UEs have comparable self- interference cancellation capabilities. Referring to FIG. 9, illustrated is a diagram showing two adjacent cells in a wireless network and a plurality of UEs 920, operating in a FD mode in an interior zone of each of the two cells and a half-duplex mode in an exterior zone, according to various aspects described herein.

[0085] In FIG. 9, the base stations 910, can operate in the FD mode, as can all of the UEs 920, illustrated (additional UEs not capable of FD mode are not shown for ease of illustration). For the ease of illustration and for simplicity, it is assumed that all of the UEs can suppress the same level of self-interference. The result of method 700 in that situation is that only UEs 920, in a zone around the BSs 91 0, operate in the FD mode. One benefit to this approach is that the UE to UE interference can be easily managed by adjusting the value of the FD threshold value (e.g., the parameter delta in 720). A high (positive) delta value "shrinks" the zone around the BSs 910, in which UEs 920, are allowed to operate in the FD mode. Alternatively, low (positive) delta values result in wider zones in which FD operation is allowed. UEs 920, close to their serving BSs usually transmit at low transmission power levels and as a result generate low levels of other cell interference. In this case, since UE to UE interference is generated only between UEs 920, within neighboring cells, the level of UE to UE interference is usually very low (e.g., negligible), due to the distance of these inner zones and due to low UE transmission power levels. This is a highly advantageous feature of the various embodiments discussed herein, since UE to UE interference can be almost entirely eliminated with little or no coordination between neighbor BSs 910,. In various aspects, neighboring BSs 910, only signal the resources which are used for FD operation to the neighboring BS 910,. This can be done via the X2 Application Protocol messages containing information related to fractional frequency reuse (FFR) such as the "LOAD INFORMATION" message described in § 9.1 .2.1 of the 3GPP TS 36.423 "X2

Application Protocol."

[0086] BS to BS interference detection can be readily included in a manner similar to that employed in TDD network deployments with different UL/DL configurations in neighbor cells. For example, neighbor BSs 910, can transmit and receive known signals at well-defined (e.g., agreed) channels and the received signal strength (interference) can be estimated. This technique or another known technique can be used to detect BS to BS interference, for example, wherein one BS 910, transmits a pilot signal with strength S at an agreed channel and the receiving BS 910, reports the received signal strength (RSS). When the RSS reported from at least one side is higher than a given threshold, then there is BS to BS interference.

[0087] In various aspects, base stations 910, can apply nulling towards neighbor base stations 91 0,. However, for small base stations 910, with no or limited beam nulling capability, the techniques discussed above can be applied.

[0088] Referring to FIG. 10, illustrated is a flow diagram of an example method 1 000 of implementing fractional frequency reuse (FFR) in connection with selective operation of a FD mode at one or more UEs according to various aspects described herein. FIG. 10 discusses the use of Fractional Frequency Reuse (FFR) of the two zones (internal and external) that correspond to the set of FD-capable UEs implementing the FD mode, and the set of UEs not implementing the FD mode, and implementing FFR based upon knowledge of BS to BS interference existence. In some aspects, method 1000 can be performed at an eNB. In other aspects, a machine readable medium can store instructions associated with method 1 000 that, when executed, can cause an eNB to perform the acts of method 1000.

[0089] At 1010, known signal sequences can be exchanged between neighboring base stations to determine a level of interference.

[0090] At 1020, the level of interference can be compared to a threshold value to determine if there is BS to BS interference with the neighbor BS (BS_Neighbor)-

[0091] At 1040, if there is no BS to BS interference, then the internal zones (the UEs selected for FD mode) can use the same resources in neighboring cells and the external zones (the UEs selected for the half-duplex mode) can use another pool of resources.

[0092] At 1030, if there is BS to BS interference, then the internal zones (the UEs selected for FD mode) can use orthogonal resources in neighboring cells and the external zones (the UEs selected for the half-duplex mode) can use the pool of resources not used in the internal zone of that cell.

[0093] Referring to FIG. 11 , illustrated is a diagram of two adjacent cells in a wireless network implementing FFR in combination with FD in connection with a first example scenario in which there is no detected BS to BS interference according to various aspects described herein. Referring to FIG. 12, illustrated is a diagram of two adjacent cells in a wireless network implementing FFR in combination with FD in connection with a second example scenario in which there is detected BS to BS interference according to various aspects described herein. Each of the white regions in FIGS. 1 1 and 12 employs one set of resources, and each of the shaded resources employs another set of resources.

[0094] The selection of resources in FIG. 1 1 (when there is no interference detected) reduces UE to UE interference due to full duplex operation. Users at the external zones of the cells can make use one of the existing inter-cell interference coordination mechanisms available in current 3GPP systems.

[0095] When there is detected BS to BS interference, the resources can be selected to protect base stations from BS to BS interference, since interference at a base station can desensitize the whole cell. In this case, illustrated in FIG. 12, the internal zones in which FD is configured can make use of different physical resource blocks.

[0096] In situations where there is BS to BS interference and the BSs 1 1 10, or 1210, are not synchronized, a margin can be taken between the resource pools for the internal zones of neighboring cells, as orthogonality is not otherwise ensured for neighboring non-synchronized base stations.

[0097] This information can be conveyed between BSs 1 1 10, or 1 210, in any of the X2 Application Protocol messages containing information related to FFR such as the "LOAD INFORMATION" message described in § 9.1 .2.1 of the 3GPP TS 36.423 "X2 Application Protocol."

[0098] Although the examples above involved an FDD system, the techniques, aspects, and embodiments described herein are valid for a TDD system as well; instead of uplink and downlink frequency bands, uplink and downlink time slots can be employed.

[0099] Examples herein can include subject matter such as a method, means for performing acts or blocks of the method, at least one machine-readable medium including executable instructions that, when performed by a machine (e.g., a processor with memory, an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or the like) cause the machine to perform acts of the method or of an apparatus or system for concurrent communication using multiple communication technologies according to embodiments and examples described. [00100] Example 1 is an apparatus configured to be employed within an Evolved NodeB (eNB), comprising receiver circuitry, a processor, and transmitter circuitry. The receiver circuitry is configured to receive, from each of one or more user equipments (UEs), a full duplex (FD) capability indicator, a self-interference cancellation level, a downlink (DL) channel metric, and an uplink (UL) transmit power metric. The processor is operably coupled to the receiver circuitry and configured to identify a subset of the one or more UEs based on the FD capability indicators; and determine, for each UE of the subset, whether to implement the FD mode, based at least in part on the self- interference cancellation level, the DL channel metric, and the UL transmit power metric received from the UE. The transmitter circuitry is configured to transmit data to each of the one or more UEs. The transmitter circuitry and the receiver circuitry are configured to communicate via the FD mode with each UE of the subset for which the processor determined to implement the FD mode, and to communicate via a half-duplex mode with other UEs of the one or more UEs.

[00101 ] Example 2 comprises the subject matter of example 1 , wherein the processor is configured to determine, for each UE of the subset, an UL transmit power level based on the UL transmit power metric and a maximum transmit power of that UE.

[00102] Example 3 comprises the subject matter of example 2, wherein the processor is configured to determine, for each UE of the subset, whether to implement the FD mode based at least in part on whether a first difference between the self-interference cancellation level and a FD threshold value exceeds a second difference between the UL transmit power level and the DL channel metric.

[00103] Example 4 comprises the subject matter of any of examples 1 -3, including or omitting optional features, wherein the DL channel metric is a reference signal (RS) received power (RSRP).

[00104] Example 5 comprises the subject matter of any of examples 1 -3, including or omitting optional features, wherein the DL channel metric is a reference signal (RS) received quality (RSRQ).

[00105] Example 6 comprises the subject matter of any of examples 1 -3, including or omitting optional features, wherein the processor is configured to determine, for each UE of the subset, whether to implement the FD mode based at least in part on a traffic priority associated with that UE.

[00106] Example 7 comprises the subject matter of any of examples 1 -3, including or omitting optional features, wherein the processor is configured to determine, for each UE of the subset, whether to implement the FD mode based at least in part on a power consumption associated with that UE.

[00107] Example 8 comprises the subject matter of any of examples 1 -3, including or omitting optional features, wherein the UL transmit power metrics are power headrooms (PHRs) received via a medium access control (MAC) protocol.

[00108] Example 9 comprises the subject matter of any of examples 1 -3, including or omitting optional features, wherein each UE of the subset for which the processor determined to implement the FD mode is assigned to a set of resources that are orthogonal to the set of resources assigned to each other UE of the subset for which the processor determined to implement the FD mode in at least one of time, frequency, code, or space resources.

[00109] Example 10 comprises the subject matter of any of examples 1 -5, including or omitting optional features, wherein the processor is configured to determine, for each UE of the subset, whether to implement the FD mode based at least in part on a traffic priority associated with that UE.

[001 10] Example 1 1 comprises the subject matter of any of examples 1 -6, including or omitting optional features, wherein the processor is configured to determine, for each UE of the subset, whether to implement the FD mode based at least in part on a power consumption associated with that UE.

[001 11 ] Example 12 comprises the subject matter of any of examples 1 -7, including or omitting optional features, wherein the UL transmit power metrics are power headrooms (PHRs) received via a medium access control (MAC) protocol.

[001 12] Example 13 comprises the subject matter of any of examples 1 -8, including or omitting optional features, wherein each UE of the subset for which the processor determined to implement the FD mode is assigned to a set of resources that are orthogonal to the set of resources assigned to each other UE of the subset for which the processor determined to implement the FD mode in at least one of time, frequency, code, or space resources.

[001 13] Example 14 comprises the subject matter of example 1 , wherein the DL channel metric is a reference signal (RS) received power (RSRP).

[001 14] Example 15 comprises the subject matter of example 1 , wherein the DL channel metric is a reference signal (RS) received quality (RSRQ). [00115] Example 16 comprises the subject matter of example 1 , wherein the processor is configured to determine, for each UE of the subset, whether to implement the FD mode based at least in part on a traffic priority associated with that UE.

[00116] Example 17 comprises the subject matter of example 1 , wherein the processor is configured to determine, for each UE of the subset, whether to implement the FD mode based at least in part on a power consumption associated with that UE.

[00117] Example 18 comprises the subject matter of example 1 , wherein the UL transmit power metrics are power headrooms (PHRs) received via a medium access control (MAC) protocol.

[00118] Example 19 comprises the subject matter of example 1 , wherein each UE of the subset for which the processor determined to implement the FD mode is assigned to a set of resources that are orthogonal to the set of resources assigned to each other UE of the subset for which the processor determined to implement the FD mode in at least one of time, frequency, code, or space resources.

[00119] Example 20 is a machine readable medium comprising instructions that, when executed, cause an evolved NodeB (eNB) to: receive, from each user equipment (UE) of one or more UEs, an indicator of capability to operate in a full duplex (FD) mode, a self-interference cancellation level, a downlink (DL) channel metric, and an uplink (UL) transmit power metric; estimate an uplink transmission power level for each UE of the plurality of based at least in part on the UL transmit power metric; calculate, for each UE, a first difference between the self-interference cancellation level and a FD threshold value and a second difference between the estimated UL transmit power level and the DL channel metric; select the FD mode or a half-duplex mode as a

communication mode for each UE based at least in part on a comparison between the first difference and the second difference; and communicate with each UE via the selected communication mode for that UE.

[00120] Example 21 comprises the subject matter of example 20, wherein the indicator of capability to operate in the full duplex (FD) mode and the self-interference cancellation level are received via an information element (IE) of a radio resource control (RRC) message.

[00121 ] Example 22 comprises the subject matter of example 21 , wherein the RRC message is a UE Capability Information message. [00122] Example 23 comprises the subject matter of example 21 , wherein the IE of the RRC message is a dedicated FD IE that comprises the indicator of capability to operate in the full duplex (FD) mode and the self-interference cancellation level.

[00123] Example 24 comprises the subject matter of example 21 , wherein the IE of the RRC message is a UE category IE.

[00124] Example 25 comprises the subject matter of any of examples 20-24, including or omitting optional features, wherein the instructions, when executed, further cause the eNB to: receive a message that indicates a set of resources associated with FD operation by a neighboring eNB; determine a level of interference with the neighboring eNB; and compare the determined level of interference to a threshold eNB interference level.

[00125] Example 26 comprises the subject matter of example 25, including or omitting optional features, wherein, in response to the determined level of interference exceeding the threshold eNB interference level, the instructions, when executed, further cause the eNB to assign to the half-duplex mode the set of resources associated with FD operation by the neighboring eNB.

[00126] Example 27 comprises the subject matter of example 26, including or omitting optional features, wherein, in response to the eNB and neighboring eNB being unsynchronized, the instructions, when executed, further cause the eNB to assign to the FD mode a set of resources separated by a margin from the set of resources associated with FD operation by the neighboring eNB.

[00127] Example 28 comprises the subject matter of example 25, including or omitting optional features, wherein, in response to the threshold eNB interference level exceeding the determined level of interference, the instructions, when executed, further cause the eNB to assign to the half-duplex mode the set of resources associated with FD operation by the neighboring eNB.

[00128] Example 29 comprises the subject matter of example 25, including or omitting optional features, wherein, the instructions, when executed, further cause the eNB to transmit to the neighboring eNB a message that indicates whether the determined level of interference exceeds the threshold eNB interference level.

[00129] Example 30 comprises the subject matter of example 20, wherein the instructions, when executed, further cause the eNB to: receive a message that indicates a set of resources associated with FD operation by a neighboring eNB; determine a level of interference with the neighboring eNB; and compare the determined level of interference to a threshold eNB interference level.

[00130] Example 31 is an apparatus configured to be employed within a user equipment (UE), comprising receiver circuitry, a processor, and transmitter circuitry. The receiver circuitry is configured to receive transmissions comprising one or more reference signals (RSs) from an evolved node B (eNB). The processor is operably coupled to the receiver circuitry and configured to calculate a downlink (DL) channel metric based on the one or more RSs. The transmitter circuitry is configured to transmit to the eNB a full duplex (FD) capability indicator, a self-interference cancellation level, the DL channel metric, and an uplink (UL) transmit power metric. The receiver circuitry is further configured to receive a mode selection transmission that indicates whether to operate in a FD mode or a half-duplex mode.

[00131 ] Example 32 comprises the subject matter of example 31 , wherein the transmitter circuitry is configured to transmit the FD capability indicator and the self- interference cancellation level via a radio resource control (RRC) message.

[00132] Example 33 comprises the subject matter of example 32, wherein the transmitter circuitry is configured to transmit the FD capability indicator and the self- interference cancellation level via an information element (IE) that indicates a UE category of the UE.

[00133] Example 34 comprises the subject matter of example 32, wherein the transmitter circuitry is configured to transmit the FD capability indicator and the self- interference cancellation level via a dedicated FD information element (IE).

[00134] Example 35 comprises the subject matter of example 31 , wherein the UL transmit power metric is a power headroom (PHR) transmitted via a medium access control (MAC) protocol.

[00135] Example 36 comprises the subject matter of example 31 , wherein the DL channel metric is one of a reference signal (RS) received power (RSRP) or a RS received quality (RSRQ).

[00136] Example 37 is a machine readable medium comprising instructions that, when executed, cause a user equipment (UE) to: receive transmissions comprising one or more reference signals (RSs) from an evolved node B (eNB); calculate a downlink (DL) channel metric based on the one or more RSs; calculate a first difference between a self-interference cancellation level of the UE and a FD threshold value; calculate a second difference between an uplink (UL) transmit power of the UE and the DL channel metric; determine whether the first difference exceeds the second difference; transmit a signal that indicates whether the first difference exceeds the second difference; and receive, in response to the signal, a mode selection transmission that indicates whether to operate in a FD mode or a half-duplex mode.

[00137] Example 38 comprises the subject matter of example 35, wherein the FD threshold value is configured to the UE by the eNB.

[00138] Example 39 is an apparatus configured to be employed within an Evolved NodeB (eNB), comprising means for receiving, means for processing, and means for transmitting. The means for receiving is configured to receive, from each of one or more user equipments (UEs), a full duplex (FD) capability indicator, a self-interference cancellation level, a downlink (DL) channel metric, and an uplink (UL) transmit power metric. The means for processing is operably coupled to the means for receiving and configured to: identify a subset of the one or more UEs based on the FD capability indicators; and determine, for each UE of the subset, whether to implement the FD mode, based at least in part on the self-interference cancellation level, the DL channel metric, and the UL transmit power metric received from the UE. The means for transmitting is configured to transmit data to each of the one or more UEs. The means for transmitting and the means for receiving are configured to communicate via the FD mode with each UE of the subset for which the means for receiving determined to implement the FD mode, and to communicate via a half-duplex mode with other UEs of the one or more UEs.

[00139] Example 40 is an apparatus configured to be employed within a user equipment (UE), comprising means for receiving, means for processing, and means for transmitting. The means for receiving is configured to receive transmissions comprising one or more reference signals (RSs) from an evolved node B (eNB). The means for processing is operably coupled to the means for receiving and configured to calculate a downlink (DL) channel metric based on the one or more RSs. The means for transmitting is configured to transmit to the eNB a full duplex (FD) capability indicator, a self-interference cancellation level, the DL channel metric, and an uplink (UL) transmit power metric. The means for receiving is further configured to receive a mode selection transmission that indicates whether to operate in a FD mode or a half-duplex mode.

[00140] The above description of illustrated embodiments of the subject disclosure, including what is described in the Abstract, is not intended to be exhaustive or to limit the disclosed embodiments to the precise forms disclosed. While specific embodiments and examples are described herein for illustrative purposes, various modifications are possible that are considered within the scope of such embodiments and examples, as those skilled in the relevant art can recognize.

[00141 ] In this regard, while the disclosed subject matter has been described in connection with various embodiments and corresponding Figures, where applicable, it is to be understood that other similar embodiments can be used or modifications and additions can be made to the described embodiments for performing the same, similar, alternative, or substitute function of the disclosed subject matter without deviating therefrom. Therefore, the disclosed subject matter should not be limited to any single embodiment described herein, but rather should be construed in breadth and scope in accordance with the appended claims below.

[00142] In particular regard to the various functions performed by the above described components or structures (assemblies, devices, circuits, systems, etc.), the terms (including a reference to a "means") used to describe such components are intended to correspond, unless otherwise indicated, to any component or structure which performs the specified function of the described component (e.g., that is functionally equivalent), even though not structurally equivalent to the disclosed structure which performs the function in the herein illustrated exemplary implementations. In addition, while a particular feature may have been disclosed with respect to only one of several implementations, such feature may be combined with one or more other features of the other implementations as may be desired and advantageous for any given or particular application.

Claims

CLAIMS What is claimed is:

1 . An apparatus configured to be employed within an Evolved NodeB (eNB), comprising:

receiver circuitry configured to receive, from each of one or more user equipments (UEs), a full duplex (FD) capability indicator, a self-interference cancellation level, a downlink (DL) channel metric, and an uplink (UL) transmit power metric;

a processor operably coupled to the receiver circuitry and configured to:

identify a subset of the one or more UEs based on the FD capability indicators; and

determine, for each UE of the subset, whether to implement the FD mode, based at least in part on the self-interference cancellation level, the DL channel metric, and the UL transmit power metric received from the UE;

transmitter circuitry configured to transmit data to each of the one or more UEs, wherein the transmitter circuitry and the receiver circuitry are configured to communicate via the FD mode with each UE of the subset for which the processor determined to implement the FD mode, and to communicate via a half-duplex mode with other UEs of the one or more UEs.

2. The apparatus of claim 1 , wherein the processor is configured to determine, for each UE of the subset, an UL transmit power level based on the UL transmit power metric and a maximum transmit power of that UE.

3. The apparatus of claim 2, wherein the processor is configured to determine, for each UE of the subset, whether to implement the FD mode based at least in part on whether a first difference between the self-interference cancellation level and a FD threshold value exceeds a second difference between the UL transmit power level and the DL channel metric.

4. The apparatus of any of claims 1 -3, wherein the DL channel metric is a reference signal (RS) received power (RSRP).

5. The apparatus of any of claims 1 -3, wherein the DL channel metric is a reference signal (RS) received quality (RSRQ).

6. The apparatus of any of claims 1 -3, wherein the processor is configured to determine, for each UE of the subset, whether to implement the FD mode based at least in part on a traffic priority associated with that UE.

7. The apparatus of any of claims 1 -3, wherein the processor is configured to determine, for each UE of the subset, whether to implement the FD mode based at least in part on a power consumption associated with that UE.

8. The apparatus of any of claims 1 -3, wherein the UL transmit power metrics are power headrooms (PHRs) received via a medium access control (MAC) protocol.

9. The apparatus of any of claims 1 -3, wherein each UE of the subset for which the processor determined to implement the FD mode is assigned to a set of resources that are orthogonal to the set of resources assigned to each other UE of the subset for which the processor determined to implement the FD mode in at least one of time, frequency, code, or space resources.

10. A machine readable medium comprising instructions that, when executed, cause an evolved NodeB (eNB) to:

receive, from each user equipment (UE) of one or more UEs, an indicator of capability to operate in a full duplex (FD) mode, a self-interference cancellation level, a downlink (DL) channel metric, and an uplink (UL) transmit power metric;

estimate an uplink transmission power level for each UE of the plurality of based at least in part on the UL transmit power metric;

calculate, for each UE, a first difference between the self-interference

cancellation level and a FD threshold value and a second difference between the estimated UL transmit power level and the DL channel metric;

select the FD mode or a half-duplex mode as a communication mode for each UE based at least in part on a comparison between the first difference and the second difference; and

communicate with each UE via the selected communication mode for that UE.

1 1 . The machine readable medium of claim 10, wherein the indicator of capability to operate in the full duplex (FD) mode and the self-interference cancellation level are received via an information element (IE) of a radio resource control (RRC) message.

12. The machine readable medium of claim 1 1 , wherein the RRC message is a UE Capability Information message.

13. The machine readable medium of claim 1 1 , wherein the IE of the RRC message is a dedicated FD IE that comprises the indicator of capability to operate in the full duplex (FD) mode and the self-interference cancellation level.

14. The machine readable medium of claim 1 1 , wherein the IE of the RRC message is a UE category IE.

15. The machine readable medium of any of claims 10-14, wherein the instructions, when executed, further cause the eNB to:

receive a message that indicates a set of resources associated with FD operation by a neighboring eNB;

determine a level of interference with the neighboring eNB; and

compare the determined level of interference to a threshold eNB interference level.

16. The machine readable medium of claim 15, wherein, in response to the determined level of interference exceeding the threshold eNB interference level, the instructions, when executed, further cause the eNB to assign to the half-duplex mode the set of resources associated with FD operation by the neighboring eNB.

17. The machine readable medium of claim 16, wherein, in response to the eNB and neighboring eNB being unsynchronized, the instructions, when executed, further cause the eNB to assign to the FD mode a set of resources separated by a margin from the set of resources associated with FD operation by the neighboring eNB.

18. The machine readable medium of claim 15, wherein, in response to the threshold eNB interference level exceeding the determined level of interference, the instructions, when executed, further cause the eNB to assign to the half-duplex mode the set of resources associated with FD operation by the neighboring eNB.

19. The machine readable medium of claim 15, wherein, the instructions, when executed, further cause the eNB to transmit to the neighboring eNB a message that indicates whether the determined level of interference exceeds the threshold eNB interference level.

20. An apparatus configured to be employed within a user equipment (UE), comprising:

receiver circuitry configured to receive transmissions comprising one or more reference signals (RSs) from an evolved node B (eNB);

a processor operably coupled to the receiver circuitry and configured to calculate a downlink (DL) channel metric based on the one or more RSs; and

transmitter circuitry configured to transmit to the eNB a full duplex (FD) capability indicator, a self-interference cancellation level, the DL channel metric, and an uplink (UL) transmit power metric,

wherein the receiver circuitry is further configured to receive a mode selection transmission that indicates whether to operate in a FD mode or a half-duplex mode.

21 . The apparatus of claim 20, wherein the transmitter circuitry is configured to transmit the FD capability indicator and the self-interference cancellation level via a radio resource control (RRC) message.

22. The apparatus of claim 21 , wherein the transmitter circuitry is configured to transmit the FD capability indicator and the self-interference cancellation level via an information element (IE) that indicates a UE category of the UE.

23. The apparatus of claim 21 , wherein the transmitter circuitry is configured to transmit the FD capability indicator and the self-interference cancellation level via a dedicated FD information element (IE).

24. A machine readable medium comprising instructions that, when executed, cause a user equipment (UE) to:

receive transmissions comprising one or more reference signals (RSs) from an evolved node B (eNB);

calculate a downlink (DL) channel metric based on the one or more RSs;

calculate a first difference between a self-interference cancellation level of the UE and a FD threshold value;

calculate a second difference between an uplink (UL) transmit power of the UE and the DL channel metric; and

determine whether the first difference exceeds the second difference;

transmit a signal that indicates whether the first difference exceeds the second difference; and

receive, in response to the signal, a mode selection transmission that indicates whether to operate in a FD mode or a half-duplex mode.

25. The machine readable medium of claim 24, wherein the FD threshold value is configured to the UE by the eNB.