WO2017111821A1

WO2017111821A1 - Full-duplex capability at user equipments and base stations

Info

Publication number: WO2017111821A1
Application number: PCT/US2015/000379
Authority: WO
Inventors: Ping Wang; Shu-Ping Yeh; Feng Xue; Yang-Seok Choi; Shilpa Talwar
Original assignee: Intel Corporation
Priority date: 2015-12-26
Filing date: 2015-12-26
Publication date: 2017-06-29

Abstract

Technology for a user equipment (UE) with full-duplex capability is disclosed. The UE can receive downlink broadcast information from the eNodeB. The UE can determine that the eNodeB supports a full-duplex mode based on the downlink broadcast information. The UE can identify that the UE supports a full-duplex mode. The UE can transmit a UE capability information message to the eNodeB indicating that the UE supports the full-duplex mode, wherein the UE is configured to communicate with the eNodeB in accordance with the full-duplex mode.

Description

BACKGROUND

10001] Wireless mobile communication technology uses various standards and protocols to transmit data between a node (e.g., a transmission station) and a wireless device (e.g., a mobile device). Some wireless devices communicate using orthogonal frequency-division multiple access (OFDMA) in a downlink (DL) transmission and single carrier frequency division multiple access (SC-FDMA) in an uplink (UL) transmission. Standards and protocols that use orthogonal frequency-division multiplexing (OFDM) for signal transmission include the third generation partnership project (3GPP) long term evolution (LTE), the Institute of Electrical and Electronics Engineers (IEEE) 902.16 standard (e.g., 902.16e, 902.16m), which is commonly known to industry groups as WiMAX

(Worldwide interoperability for Microwave Access), and the IEEE 902.1 1 standard, which is commonly known to industry groups as WiFi.

[0002] In 3GPP radio access network (RAN) LTE systems, the node can be an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node Bs (also commonly denoted as evolved Node Bs, enhanced Node Bs, eNodeBs, or eNBs), which

communicates with the wireless device, known as a user equipment (UE). The downlink (DL) transmission can be a communication from the node (e.g., eNodeB) to the wireless device (e.g., UE), and the uplink (UL) transmission can be a communication from the wireless device to the node.

BRIEF DESCRIPTION OF THE DRAWINGS

|0003] Features and advantages of the disclosure will be apparent from the detailed description which follows, taken in conjunction with the accompanying drawings, which together illustrate, by way of example, features of the disclosure; and, wherein:

|0004] FIG. 1 illustrates capability signaling between a user equipment (UE) and an eNodeB in accordance with an example;

[0005] FIG. 2 illustrates network duplex modes in accordance with an example; [0006] FIG. 3 illustrates user equipment (UE) modes with full duplex capability in accordance with an example;

[0007] FIG. 4 illustrates a cell search procedure performed at a user equipment (UE) in accordance with an example;

[0008] FIG. 5 depicts functionality of a user equipment (UE) with full-duplex capability in accordance with an example;

[0009] FIG. 6 depicts a flowchart of a machine readable storage medium having instructions embodied thereon for communicating full-duplex capability information at a user equipment (UE) in accordance with an example;

[0010] FIG. 7 depicts functionality of an eNodeB with full-duplex capability in accordance with an example;

[0011] FIG. 8 depicts functionality of an eNodeB with full-duplex capability in accordance with an example;

[0012] FIG. 9 illustrates a diagram of a wireless device (e.g., UE) in accordance with an example; and

[0013] FIG. 10 illustrates a diagram of a wireless device (e.g., UE) in accordance with an example.

[0014] Reference will now be made to the exemplary embodiments illustrated, and specific language will be used herein to describe the same. It will nevertheless be understood that no limitation of the scope of the technology is thereby intended.

DETAILED DESCRIPTION

[0015] Before the present technology is disclosed and described, it is to be understood that this technology is not limited to the particular structures, process actions, or materials disclosed herein, but is extended to equivalents thereof as would be recognized by those ordinarily skilled in the relevant arts. It should also be understood that terminology employed herein is used for the purpose of describing particular examples only and is not intended to be limiting. The same reference numerals in different drawings represent the same element. Numbers provided in flow charts and processes are provided for clarity in illustrating actions and operations and do not necessarily indicate a particular order or sequence.

EXAMPLE EMBODIMENTS

|0016] An initial overview of technology embodiments is provided below and then specific technology embodiments are described in further detail later. This initial summary is intended to aid readers in understanding the technology more quickly but is not intended to identify key features or essential features of the technology nor is it intended to limit the scope of the claimed subject matter.

[0017] A duplex communication system is a point-to-point system composed of two connected devices that can communicate with one another in both directions. There are two types of duplex communication systems - full-duplex (FD) and half-duplex (HD). In a full duplex system, both devices can communicate with each other simultaneously at the same time and the same frequency. In a half-duplex system, there are two clearly defined paths or channels, and each device can communicate with the other device but not simultaneously at the same time or the same frequency. In other words, the

communication is one direction at a specific time and frequency in a half-duplex system.

[0018] In wireless communication systems, multiple users can share the same resources using duplexing techniques. Examples of such duplexing techniques can include time- division duplexing (TDD) and frequency division duplexing (FDD). For example, a user equipment (UE) can communicate with a base station (or eNodeB) using TDD or FDD. Both TDD and FDD can emulate a bidirectional communication over a half-duplex communication link. In TDD, time-division multiplexing is applied to separate transmitting and receiving signals. In TDD, the half-duplex communication link is established such that a transmitter and receiver share the same frequency, but signals are transmitted and received separate in time. In FDD, transmitting and receiving radio signals can be associated with different radio frequencies. In other words, in FDD, the half-duplex communication link can be established using two different radio frequencies for the transmitter and the receiver, wherein the two different radio frequencies are separated by a defined frequency gap.

[0019] In one example, cellular networks can be configured with full-duplex (FD) capability, such that the UE and/or the eNodeB are capable of performing full-duplex communications. Full duplex techniques support simultaneous transmissions and receptions in the same frequency at the same time, which can potentially double the spectrum efficiency of the cellular network. Compared to a half-duplex (HD) TDD or FDD system, a full-duplex (FD) system can be associated with significantly more interference between its transmission and receiver chain. However, recent techniques from industry and academics demonstrate more than 120 decibel (dB) interference cancellation for FD systems, thus enabling the potential applications of FD operation in wireless cellular systems. Based on the advances in interference cancellation, in a fifth generation (5G) wireless communication system, FD capability can be implemented at various network nodes, such as a macro or small cell base station, UE, relay node etc.

[0020] As described in greater detail below, in the present technology, a full-duplex (FD) capable UE can report its FD capability to the network. For example, a FD-capable eNodeB can receive an indication of FD capability from the FD-capable UE. In other words, a UE with full-duplex capability can signal this capability (or full-duplex mode) to the eNodeB. In one example, the UE can be capable of communication in a FDD mode and/or a TDD mode and/or a FD mode. In other words, the UE can support older duplexing technologies, such as TDD and/or FDD, as well as FD. In addition, the eNodeB can notify the UE about the network's FD mode (e.g., whether the network supports FD or does not support FD) when the UE initially accesses the cell formed by the eNodeB. When the eNodeB supports the FD mode, it can communicate with a half-duplex

(TDD/FDD) mode UE or a FD mode UE.

[0021] In the present technology, FD communication can occur in either of two scenarios: (1 ) the eNodeB is FD capable and the UE is half-duplex capable (i.e., not capable of FD); or (2) the eNodeB is FD capable and the UE is full-duplex capable. More specifically, when the eNodeB has FD capability, the eNodeB can perform full-duplex

communications with the UE, even when the UE does not have FD capability. For example, when the UE does not have FD capability, the eNodeB can schedule a paired UE. In other words, the eNodeB can configure one half-duplex UE to receive and another half-duplex UE to transmit in the same time/resource, such that the full-duplex capability at the eNodeB is utilized. Therefore, in some cases, both the eNodeB and the UE do not necessarily need to be full-duplex capable in order to communicate in the FD mode. [0022] In the present technology, the eNodeB can notify the UE about the eNodeB's FD capability. Similarly, the UE can notify the eNodeB about the UE's FD capability. When the eNodeB is FD capable and the UE is half-duplex capable, only the eNodeB may send its FD capability to the UE in order to perform a FD communication between the UE and the eNodeB. However, when the eNodeB is FD capable and the UE is full-duplex capable, both the UE and the eNodeB can exchange their respective FD capabilities with each other in order to perform a FD communication between the UE and the eNodeB.

(0023] In previous solutions, when the eNodeB sets up communications with the UE, the eNodeB can become aware of the UE's capability. For example, a UE capability report procedure can transfer UE radio access capability information from the UE to the eNodeB. The 3GPP LTE specifications define a set of feature group indicators (FGI) for single mode UEs (i.e., UEs that support FDD or TDD) or dual mode UEs (i.e., UEs that support both FDD and TDD). The FGI can be signaled from the UE to the network, such that the network is notified of the LTE or radio access technology (RAT) capability supported at the UE at the corresponding duplex mode. UEs in different duplex mode (TDD or FDD) can support different features. For example, some features can be available at one duplex mode, but not supported at the other duplex mode. In another example, some features at one duplex mode may not be certified at the other duplex mode, and therefore, these features are turned off during deployment if the network operates in the other duplex mode. In addition, the network may or may not initiate certain procedures towards the UE based on the UE's capability (i.e., the specific mode supported at the UE). In the 3GPP LTE standard since Release 9, the capability information considers dual-mode UEs (i.e., UEs supporting both TDD and FDD mode) and procedures reporting individual capabilities for different duplex modes (i.e., FDD or TDD).

|0024] In previous solutions, when the UE accesses the network, the UE can receive information about the network's duplex mode. For example, in accordance with the LTE standard, the UE can know whether the network supports TDD or FDD by decoding a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) transmitted from the eNodeB. Based on the relative position of the PSS and the SSS, the UE can determine whether the network supports the TDD mode or the FDD mode. Based on the duplexing mode (TDD or FDD) supported at the network, the UE can read configurations specific to the duplexing mode in system information block (SIB) messages transmitted from the eNodeB.

(0025] FIG. 1 illustrates exemplary capability signaling between a user equipment (UE) 110 and an eNodeB 120. The UE 1 10 can include one or more processors 112 and memory 114, and the eNodeB 120 can include one or more processors 122 and memory 124. The eNodeB 120 can inquire about the UE's capability by sending a UE capability enquiry message to the UE 1 10. The UE capability enquiry message can indicate specific information requested by the eNodeB 120. After receiving the UE capability enquiry message, the UE 110 can report the corresponding capability information to the eNodeB 120 via a 'UE Capability Information' radio resource control (RRC) message or a 'UE Capability Information' information element (IE).

[0026] In one example, UE Evolved Universal Terrestrial Radio Access (EUTRA) capabilities indicated in the 'UE Capability Information' message can include the following categories: access stratum release (UE-EUTRA- Capability.accessStratumRelease), UE category (UE-EUTRA-Capability.ue-Category), packet data convergence protocol (PDCP) parameters and supported robust header compression (ROHC) profiles (UE-EUTRA-Capability.pdcp-

Parameters.supportedROHC-Profiles), radio frequency (RF) parameters and supported band lists (UE-EUTRA-Capability.rf-Parameters.supportedBandListEUTRA), measurement parameters (UE-EUTRA-Capability.measParameters, inter-radio access technology (RAT) parameters (UE-EUTRA-Capability.interRAT-Parameters), and feature group indicators (UE-EUTRA-Capability.featureGroupIndicators).

[0027] In one example, in previous solutions, among the UE EUTRA capabilities, the featureGroupIndicators (FGIs) can specify the message format included in the 'UE Capability Information' message that considers possibilities of different capabilities for TDD mode and/or FDD mode for a dual -mode UE. The dual -mode UE can refer to a UE that supports FDD or TDD. In one example, the FGIs in the 'UE Capability Information' message can indicate common functions supported by both the TDD and FDD modes. If one or more UE capability fields have different values for FDD and TDD, a 'Fdd-Add- UE-EUTRA-Capabilities' parameter or information element (IE) in the 'UE Capability Information' message can be set to include additional functionality applicable for FDD and a 'Tdd-Add-UE-EUTRA-Capabilities' parameter or IE in the 'UE Capability Information' message can be set to include additional functionality applicable for TDD. In other words, the 'UE Capability Information' message communicated from the UE 1 10 to the eNodeB 120 can include FGI sets to indicate whether the UE 1 10 supports the TDD mode and/or the FDD mode.

[0028] In one example, in previous solutions, to support handover of the UE from a first base station that supports the TDD mode and a second base station that supports the FDD mode, or vice versa, two mobility FGI bits can be set to 'true', thereby enabling the handover between the two duplexing modes. A first mobility FGI bit can be related to inter-frequency handover (FGI bit 13), and a second mobility FGI bit can be related to handover between FDD and TDD (FGI bit 30).

[0029] However, in previous solutions, the 'UE Capability Information' message does not include FGIs that address the full-duplex mode capability of the UE. In addition, previous solutions do not address handover capability between an FD mode and a non-FD mode (i.e., a TDD or FDD mode) in the 'UE Capability Information' message. Moreover, in previous solutions, the frame structure (FDD or TDD) can be determined based on different PSS/SSS locations corresponding to FDD or TDD. For example, for TDD, the PSS is located in the 3rd symbol of subframe 1 and 6, while the SSS is located in the last symbol of subframe 0 and 5. The previous solutions do not describe mechanisms for UEs to detect an FD mode frame structure.

[0030) FIG 2 illustrates exemplary network duplex modes when the network supports full-duplex (FD). More specifically, the network can support one of four duplex modes, wherein each mode corresponds to the type(s) of duplex modes (i.e., TDD, FDD and FD) supported at the network. In a first mode, the network can support FDD and FD. In a second mode, the network can support only TDD. In a third mode, the network can support only FDD. In a fourth mode, the network can support TDD and FD.

[0031] For example, the network can have a TDD band, a FDD band or a FD band. The FD band can be a combination of TDD and FD (B4) or a combination of FDD and FD (B l ). In other words, for the FD band, the network can dynamically switch between TDD and FD (B4), or the network can dynamically switch between FDD and FD (B 1 ). The network can switch between TDD and FD or between FDD and FD depending on scheduler decisions based on traffic patterns, interference scenarios, etc. In the TDD band (B2), the network only supports the TDD mode, and in the FDD band (B3), the network only supports the FDD mode.

|0032] In one example, in the FD band (Bl or B4), the network can be statically or semi- statically switching between a conventional half-duplex (HD) mode (i.e., FDD or TDD) and the FD mode. For example, the HD mode can be utilized to convey certain types of messages to the UE in specified subframes. One example includes messages to avoid impact from potential additional interferences due to the FD mode. As described in further detail below, the network can notify the UE about the duplexing mode supported at the network. For example, the network can indicate to the UE whether the TDD, FDD or FD mode is supported at the network.

|0033] In one example, a full-duplex capable UE can be capable of communicating with the network in accordance with a FDD mode, TDD mode, or FD mode. The UE can obtain a FD-specific feature group indicators (FGls) set, a TDD-specific FGls set and/or a FDD-specific FGls set, and the UE can signal to the base station at least one of the sets (depending on the UE's capability to support a particular mode). The network can receive, from the UE, signaling of at least one of the FDD specific FGI set or a TDD-specific FGI set or a FD-specific FGI set, and the network can determine the features supported by the UE in at least one of the duplex modes. In addition, the UE can report to the network about its radio access capability for the corresponding network duplex mode, including FGls, mobility functionalities, etc. The network can receive capability signaling from the FD-capable UE in a 'UE Capability Information' message.

|0034] FIG 3 illustrates exemplary user equipment (UE) modes with full duplex capability. In previous solutions, a UE supported a single mode (TDD or FDD) or a dual mode of TDD and FDD. In the present technology, in addition to the legacy modes, the UE can support a dual mode of TDD and FD, a dual mode of FDD or FD, or a triple mode of TDD, FDD and FD. In other words, the UE can be a legacy TDD-mode UE, FDD-mode UE, TDD FDD dual-mode UE, and the UE can be a novel TDD/FD dual- mode UE, FDD FD dual mode UE or TDD FDD FD triple mode UE. In addition, an eNodeB in communication with the UE can have a conventional TDD band, a conventional FDD band, a novel TDD-FD band, or a novel FDD-FD band. |003S] As discussed in further detail below, the UE can transmit a UE capability report to indicate one or more of the FD modes. The UE can undergo handover between eNodeB that support the FD mode or do not support the FD mode, and UE mobility between different duplex modes can result in modifications to the FGI bits in the UE capability report. In addition, the UE can determine the duplex mode of the eNodeB using various mechanisms.

[0036] In one configuration, the 'UE Capability Information' message communicated from the UE to the eNodeB can account for FD-capable UEs. For example, the message format included in the 'UE Capability Information' message for TDD/FDD dual-mode UEs can be specified as follows: (1) common functions supported by both the TDD and FDD mode can be set first, and if one or more of the UE capability fields have a different value for TDD and FDD, then (2) a Fdd-Add-UE-EUTRA-Capabilities parameter or IE can be set to include additional functionality applicable for FDD; and (3) a Tdd-Add-UE- EUTRA-Capabilities parameter or IE can be set to include additional functionality applicable for TDD. In addition, for FD-capable UEs, including TDD FD dual mode UE, FDD/FD dual mode UE or TDD/FDD FD triple mode UE, two additional fields can be added to the 'UE Capability Information' message to specify additional functionality applicable for a TDD/FD mode and a FDD/FD mode. For example, the 'UE Capability Information' message can include a 'tdd-fd-Add-UE-EUTRA-Capabilities-rx' parameter or IE that includes a 'featureGroupIndicators-rx', which is a TDD/FD specific FGI. Here, 'rx' refers to a defined 3GPP LTE release number. In addition, the 'UE Capability Information' message can include a 'fdd-fd-Add-UE-EUTRA-Capabilities-rx' parameter or IE that includes a 'featureGroupIndicators-rx', which is a FDD/FD specific FGI. In other words, the two FGIs are information elements (IEs) that can be transmitted from the UE to the eNodeB in order to inform the eNodeB about the UE's capability. Therefore, by transmitting the 'tdd-fd-Add-UE-EUTRA-Capabilities-rx' parameter or IE that includes the 'featureGroupIndicators-rx' to the eNodeB, the UE informs the eNodeB the additional features or capabilities for TDD/FD mode. Similarly, by transmitting the 'fdd-fd-Add- UE-EUTRA-Capabilities-rx' parameter or IE that includes a 'featureGroupIndicators-rx', to the eNodeB, the UE informs the eNodeB the additional features or capabilities for

FDD/FD mode. As previously described, these two additional FGIs can be included in the 'UE Capability Information' message transmitted from the UE to the eNodeB. By adding these two additional FGIs to the 'UE Capability Information' message, a FD-capable eNodeB can determine the additional UE capabilities specific for the TDD FD or FDD/FD modes in addition to the common capabilities for all modes. When the 'UE Capability Information' message does not include either of these two additional FGIs, the eNodeB can determine that the UE capabilities are only the common functions.

10037] In one example, the two additional fields in the 'UE Capability Information' message can correspond to different values for the TDD/FD and FDD/FD modes, as compared to the common functions. Thus, when the UE communicates to a TDD/FD band in the network, the network can determine the corresponding UE capabilities via common functions and the tdd-fd-Add-UE-EUTRA-Capabilities-rx field. Similarly, when the UE communicates to a FDD/FD band in the network, the network can determine the corresponding UE capabilities via common functions and the fdd-fd-Add-UE-EUTRA- Capabilities-rx field.

(0038] In one example, the 3GPP LTE Release 12 specification can be written to support UE full-duplex (FD) capability as follows:

The UE can:

(1 ) set the contents of the UECapabilitylnformation message as follows:

(2) when the ue-Capability Request includes eutra:

(3) include the UE-EUTRA-Capability within a ue-CapabilityRAT-Container and with the rat-Type set to eutra;

(4) when the UE supports FDD and TDD or TDD and FD, or FDD and FD or FDD and TDD and FD,

(5) set all fields of UECapabilitylnformation, except field fdd-Add-UE-EUTRA- Capabilities and tdd-Add-UE-EUTRA-Capabilities (including their sub-fields), fdd-fd- Add-UE-EUTRA-Capabilities-rx (including their sub-fields), and tdd-fd-Add-UE-

EUTRA-Capabilities-rx (including their sub-fields), to include the values applicable for all FDD and TDD and FD UE modes (i.e., functionality supported by all the modes,

(6) when one or more UE capability fields have a different value for FDD and TDD or FD: (7) when for FDD, the UE supports additional functionality compared to what is indicated by the previous fields of UECapabilitylnformation:

(8) include field fdd-Add-UE-EUTRA-Capabilities and set it to include fields reflecting the additional functionality applicable for FDD;

(9) when for TDD, the UE supports additional functionality compared to what is indicated by the previous fields of UECapabilitylnformation:

(10) include field tdd-Add-UE-EUTRA-Capabilities and set it to include fields reflecting the additional functionality applicable for TDD;

(11) when for TDD-FD, the UE supports additional functionality compared to what is indicated by the previous fields of UECapabilitylnformation:

(12) include field tdd-fd-Add-UE-EUTRA-Capabilities-rx and set it to include fields reflecting the additional functionality applicable for TDD-FD,

(13) when for FDD-FD, the UE supports additional functionality compared to what is indicated by the previous fields of UECapabilitylnformation:

(14) include field fdd-Add-UE-EUTRA-Capabilities-rx and set it to include fields reflecting the additional functionality applicable for FDD-FD.

[0039] In one example, the 'UE Capability Information' can include the XDD-Add-UE- EUTRA-Capabilities field or the XDD-FD-Add-UE-EUTRA-Capabilities-rx field, wherein 'XDD' refers to TDD or FDD. One of the fields can be included when one or more of its sub-fields have a value that is different compared to the value signaled elsewhere within the UE-EUTRA-Capability. The value signaled elsewhere is also referred to as the Common value, which is supported for all XDD and XDD-FD modes). For the fields which are included in XDD-Add-UE-EUTRA-Capabilities, the UE sets: the sub-fields (which are not allowed to be different) the same as the Common value; and the sub-fields that are allowed to be different to a value indicating at least the same functionality as indicated by the Common value. Otherwise, the UE supports a single XDD mode and set all fields of UECapabilitylnformation, except field fdd-Add-UE- EUTRA-Capabilities and tdd-Add-UE-EUTRA-Capabilities (including their sub-fields), fdd-fd-Add-UE-EUTRA-Capabilities-rx (including their sub-fields), and tdd-fd-Add-UE- EUTRA-Capabilities-rx (including their sub-fields), to include the values applicable for the XDD mode supported by the UE.

[0040] In one configuration, the feature group indicator (FGI) sets in the 'UE Capability Information' message can be for UE mobility. The FGI sets can include one or more FGI bits that are specific to intra-RAT or iinter-RAT motilities. To support UE mobility between FDD and TDD, two FGI bits can be defined and set to 'true': a first FGI bit relates to inter-frequency handover (bit 13 in FGI) and a second FGI bit relates to handover between FDD and TDD (bit 30 in FGI). More specifically, the handover pertains to the UE being handed from a first eNodeB that supports a first type of duplexing scheme (e.g., TDD or FDD ) to a second eNodeB that supports a second type of duplexing scheme (e.g., FDD or TDD).

[0041] To support handover of the UE between FD (i.e., FDD FD or TDD FD) and TDD FDD, as well as FD to FD (used for FD to support mobility), the following FGI bits can be added to the FGI sets in the 'UE Capability Information' message: a first FGI bit can be added in the 'UE Capability Information' message to indicate that the UE supports handover between FDD and FDD/FD; a second FGI bit can be added in the 'UE

Capability Information' message to indicate that the UE supports handover between TDD and TDD FD; a third FGI bit can be added in the 'UE Capability Information' message to indicate that the UE supports handover between FDD and TDD FD; a fourth FGI bit can be added in the 'UE Capability Information' message to indicate that the UE supports handover between TDD and FDD/TD; and a fifth FGI bit can be added in the 'UE Capability Information' message to indicate that the UE supports handover between FDD/FD and TDD/FD.

[0042] In other words, the first FGI bit can indicate that the UE supports a handover from a first eNodeB that operates in a FDD mode to a second eNodeB that operates in a FDD- FD mode, or vice versa; the second FGI bit can indicate that the UE supports a handover from a first eNodeB that operates in a TDD mode to a second eNodeB that operates in a TDD-FD mode, or vice versa; the third FGI bit can indicate that the UE supports a handover from a first eNodeB that operates in a FDD mode to a second eNodeB that operates in a TDD-FD mode, or vice versa; the fourth FGI bit can indicate that the UE supports a handover from a first eNodeB that operates in a TDD mode to a second eNodeB that operates in a FDD-FD mode, or vice versa; and the fifth FGI bit can indicate that the UE supports a handover from a first eNodeB that operates in a FDD-FD mode to a second eNodeB that operates in a TDD-FD mode, or vice versa.

(0043] In one example, the five additional FGI bits included in the 'UE Capability Information' message can correspond to the network duplex mode (i.e., FDD/FD, TDD, FDD, or TDD/FD). In some cases, there can be variants of the network duplex modes. For example, rather than a mixed TDD/FD and FDD/FD mode, there could be a novel FD mode, in which case the corresponding mobility bits and FGI groups can be adjusted accordingly.

(0044] In one example, the decision to move between duplex modes can partially depend on the UE capabilities, which can be different between different UE modes, in addition to the handover capability FGI itself. The eNodeB can configure a neighbor list and handover parameters, such that the eNodeB can control the mobility criterion based on knowledge of the UE capability with respect to individual duplex modes.

(0045] In one example, when UEs have the same FDD and TDD and FD capabilities, and the UEs move between cells that support TDD and FDD and FD, the eNodeBs may not obtain UE EUTRA capability information. When UEs have different FDD and TDD or FD (e.g., TDD/FD or FDD/FD) capabilities and move between cells that support different duplex mode, the eNodeB can obtain UE EUTRA capability information.

(0046] In one example, when the UE supports multiple duplex modes, the eNodeB can determine whether the UE has the same or different capabilities with respect to different duplex modes. For example, when the UE-EUTRA-Capability IE contains the tdd-Add- UE-EUTRA-Capabilities-r9 IE or fdd-Add-UE-EUTRA-Capabilities-r9 IE, the UE has different FDD and TDD capabilities. When the UE-EUTRA-Capability IE contains the tdd-fd-Add-UE-EUTRA-Capabilities-rx IE or fdd-fd-Add-UE-EUTRA-Capabilities-rx IE, the UE has different FD capabilities. In one example, when the UE-EUTRA- Capability IE contains none of the tdd-Add-UE-EUTRA-Capabilities-r9 IE, fdd-Add-UE- EUTRA-Capabilities-r9 IE or tdd-fd-Add-UE-EUTRA-Capabilities-rx IE, or fdd-fd-Add- UE-EUTRA-Capabilities-rx IE, the UE has the same capabilities for all duplexing modes.

|0047] In one example, the additional overhead caused by the additional IEs and FGI bits due to the introduction of the FD mode is minimal. In addition, the UE capability information may not be sent across the air interface each time the UE transitions from a radio resource control ( RC) idle mode to an RRC connected mode. Rather, a mobility management entity (ΜΜΈ) can store the 'UE Capability Information' during an Evolved Packet System (EPS) connection management (ECM) idle state. The MME can transmit the most recent UE radio capability information to the base station over an SI interface, unless the UE is performing an attach procedure or a tracking area update (TAU). The eNodeB can obtain the UE EUTRA capability information from the MME or the UE, including functions supported by cells in the duplex modes, optional functions supported by TDD cells, optional functions supported by FDD cells, optional functions supported by TDD/FD cells, and optional functions supported by FDD FD cells.

[0048] In one example, the eNodeB can enable the functions supported by the serving cell. For example, during an S 1 or X2 handover from a first cell in a first duplex mode to a second cell in a second duplex mode, a source eNodeB can send a handover request message with the UE-EUTRA-Capability IE to a target eNodeB. In addition, during the SI or X2 handover from the first cell in the first duplex mode to the second cell in the second duplex mode, the target eNodeB can enable functions supported by the duplex modes and the optional functions supported by the duplex mode in the target cell, which are indicated in the UE-EUTRA-Capability IE.

10049] FIG. 4 illustrates an exemplary cell search procedure performed at a user equipment (UE). The UE can detect a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) transmitted from a base station. The UE can decode the PSS and SSS, and based on a location of the PSS and the SSS, the UE can determine whether the base station supports TDD or FDD. More specifically, based on the PSS and SSS detection, the UE can acquire information about a slot timing, a frame timing, a cell identifier (ID), a cyclic prefix (CP) length, and TDD or FDD duplex mode information. In addition, the UE can decode a physical broadcast channel (PBCH), which allows the UE to determine a number of downlink (DL) control symbols. Based on the number DL control symbols, the UE can decode a system information block 1 (SIBl ), a system information block 2 (SIB2) and other SIBs from physical downlink shared channel (PDSCH) location. In addition, the SIBl can include the TDD configuration (e.g., 0 through 6) associated with the base station.

[0050] In one configuration, in order to notify the UE about full-duplex (FD) modes associated with the base station (i.e., notifying the UE that the base station is FD- capable), an approach similar to previous LTE solutions can be utilized. For example, for the TDD/FD mode, the base station can transmit the PSS/SSS at the same location as compared to a base station that supports TDD. For the FDD FD mode, the base station can transmit the PSS/SSS at the same location as compared to a base station that supports FDD. Therefore, after detecting the PSS/SSS and determining the location of the PSS/SSS, the UE can determine whether the accessed cell is a TDD or TDD/FD cell, or whether the accessed cell is a FDD or FDD/FD cell. Afterwards, the network can inform the UE on its FD specific capability via various SIB messages, along with its TDD/FDD specific configurations.

[0051] In one configuration, rather than a multi-mode UE connecting to a network that uses four separate duplexing modes, the multi-mode UE can connect to a network that supports a single FD mode or a subset of the four separate duplexing modes. In this configuration, additional bits can be used to indicate to the UE the possible duplexing modes that are supported by the network. The additional bits can be communicated to the UE via dedicated signaling or broadcast signaling. In other words, rather than the UE determining the network's capability based on the location of the PSS/SSS, the UE can determine the network's capability based on dedicated or broadcast signaling. For example, the network can indicate in the signaling whether full duplex (FD) is supported or not supported at the network. The UE can receive network capability information from the network, and in response, the UE can send UE capability information related to the duplexing modes supported at the network. The UE can send to the network only the information relevant to the network's supported duplexing modes, rather than sending the common and four mode-specific IEs. This approach can prevent the unnecessary upload of capabilities related to non-used duplexing modes at the network, with the cost of adding additional bits from the network to the UE to notify the UE of the network's supported duplexing modes or FD configuration.

[0052J Another example provides functionality 500 of a user equipment (UE) with full- duplex capability, as shown in the flow chart in FIG 5. The UE can comprise one or more processors and memory configured to: receive, at the UE, downlink broadcast information from the eNodeB, as in block 510. The UE can comprise one or more processors and memory configured to: determine, at the UE, the eNodeB supports a full- duplex mode based on the downlink broadcast information, as in block 520. The UE can comprise one or more processors and memory configured to: identify, at the UE, that the UE supports a full-duplex mode, as in block 530. The UE can comprise one or more processors and memory configured to: transmit, from the UE to the eNodeB, a UE capability information message indicating that the UE supports the full-duplex mode, wherein the UE is configured to communicate with the eNodeB in accordance with the . full-duplex mode, as in block 540.

[0053] Another example provides at least one machine readable storage medium having instructions 600 embodied thereon for communicating full-duplex capability information at a user equipment (UE), as shown in the flow chart in FIG. 6. The instructions can be executed on a machine, where the instructions are included on at least one computer readable medium or one non-transitory machine readable storage medium. The instructions when executed perform: determining, using one or more processors at the UE, that an eNodeB supports a full-duplex mode, as in block 610. The instructions when executed perform: identifying, using the one or more processors at the UE, that the UE supports a full-duplex mode, wherein the full-duplex mode is supported by at least one of the UE and the eNodeB, wherein the full-duplex mode enables a simultaneous transmission and reception of data using a same time and frequency resource, as in block 620. The instructions when executed perform: transmitting, using the one or more processors at the UE, a UE capability information message to the eNodeB indicating that the UE supports the full-duplex mode, wherein the UE is configured to communicate with the eNodeB in accordance with the full-duplex mode, as in block 630.

(0054] Another example provides functionality 700 of an eNodeB with full-duplex capability, as shown in the flow chart in FIG 7. The eNodeB can comprise one or more processors and memory configured to: establish a connection between the eNodeB and a user equipment (UE), wherein the UE is configured to determine that the eNodeB supports a full-duplex mode during a connection establishment procedure between the eNodeB and the UE, as in block 710. The eNodeB can comprise one or more processors and memory configured to: receive, from the UE, a UE capability information message indicating that the UE supports a full-duplex mode, wherein the full-duplex mode is supported by at least one of the UE and the eNodeB, wherein the full-duplex mode enables a simultaneous transmission and reception of data using a same time and frequency resource, as in block 720. The eNodeB can comprise one or more processors and memory configured to: perform, at the eNodeB, communications with the UE in accordance with the full-duplex mode, as in block 730.

|0055J Another example provides functionality 800 of an eNodeB with full-duplex capability, as shown in the flow chart in FIG. 8. The eNodeB can comprise one or more processors and memory configured to: process, at the eNodeB, downlink broadcast information for transmission to a user equipment (UE), the downlink broadcast information indicating that the eNodeB supports a full-duplex mode, wherein the UE only supports a half-duplex mode, as in block 810. The eNodeB can comprise one or more processors and memory configured to: perform, at the eNodeB, communications with the UE when the eNodeB supports the full-duplex mode and the UE only supports the half- duplex mode, wherein the eNodeB is configured to schedule a paired UE that only supports the half-duplex mode to utilize the full-duplex capability of the eNodeB, as in block 820.

[0056] FIG 9 provides an example illustration of a user equipment (UE) device 900, such as a wireless device, a mobile station (MS), a mobile wireless device, a mobile communication device, a tablet, a handset, or other type of wireless device. The UE device 900 can include one or more antennas configured to communicate with a node or transmission station, such as a base station (BS), an evolved Node B (eNB), a baseband unit (BBU), a remote radio head ( H), a remote radio equipment ( RE), a relay station (RS), a radio equipment (RE), a remote radio unit (RRU), a central processing module (CPM), or other type of wireless wide area network (W WAN) access point. The UE device 900 can be configured to communicate using at least one wireless communication standard including 3GPP LTE, WiMAX, High Speed Packet Access (HSPA), Bluetooth, and WiFi. The UE device 900 can communicate using separate antennas for each wireless communication standard or shared antennas for multiple wireless communication standards. The UE device 900 can communicate in a wireless local area network (WLAN), a wireless personal area network (WPAN), and/or a WWAN.

|00571 In some embodiments, the UE device 900 may include application circuitry 902, baseband circuitry 904, Radio Frequency (RF) circuitry 906, front-end module (FEM) circuitry 908 and one or more antennas 910, coupled together at least as shown. [0058] The application circuitry 902 may include one or more application processors. For example, the application circuitry 902 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processors ) 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 a storage medium 912 and may be configured to execute instructions stored in the storage medium 912 to enable various applications and/or operating systems to run on the system.

[0059] The baseband circuitry 904 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 904 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 906 and to generate baseband signals for a transmit signal path of the RF circuitry 906. Baseband processing circuity 904 may interface with the application circuitry 902 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 906. For example, in some embodiments, the baseband circuitry 904 may include a second generation (2G) baseband processor 904a, third generation (3G) baseband processor 904b, fourth generation (4G) baseband processor 904c, and/or other baseband processors) 904d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.). The baseband circuitry 904 (e.g., one or more of baseband processors 904a-d) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 906. 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 904 may include Fast-Fourier Transform (FFT), precoding, and/or constellation

mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry 904 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. [0060] In some embodiments, the baseband circuitry 904 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) 904e of the baseband circuitry 904 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) 904f. 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 904 and the application circuitry 902 may be implemented together such as, for example, on a system on a chip (SOC).

10061 ] In some embodiments, the baseband circuitry 904 may provide for

communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 904 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 904 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0062] The RE circuitry 906 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 906 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 906 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 908 and provide baseband signals to the baseband circuitry 904. RF circuitry 906 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 904 and provide RF output signals to the FEM circuitry 908 for transmission. |0063] In some embodiments, the RF circuitry 906 may include a receive signal path and a transmit signal path. The receive signal path of the RF circuitry 906 may include mixer circuitry 906a, amplifier circuitry 906b and filter circuitry 906c, The transmit signal path of the RF circuitry 906 may include filter circuitry 906c and mixer circuitry 906a. RF circuitry 906 may also include synthesizer circuitry 906d for synthesizing a frequency for use by the mixer circuitry 906a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 906a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 908 based on the synthesized frequency provided by synthesizer circuitry 906d. The amplifier circuitry 906b may be configured to amplify the down-converted signals and the filter circuitry 906c 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 904 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 906a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

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

(0065] In some embodiments, the mixer circuitry 906a of the receive signal path and the mixer circuitry 906a of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and/or up-conversion respectively. In some embodiments, the mixer circuitry 906a of the receive signal path and the mixer circuitry 906a 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 906a of the receive signal path and the mixer circuitry 906a may be arranged for direct down-conversion and/or direct up-conversion, respectively. In some embodiments, the mixer circuitry 906a of the receive signal path and the mixer circuitry 906a of the transmit signal path may be configured for super-heterodyne operation.

|0066] 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 906 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 904 may include a digital baseband interface to communicate with the RF circuitry 906.

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

[0068] In some embodiments, the synthesizer circuitry 906d may be a fractional-N synthesizer or a fractional N N+l 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 906d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[00691 The synthesizer circuitry 906d may be configured to synthesize an output frequency for use by the mixer circuitry 906a of the RF circuitry 906 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 906d may be a fractional N N+l synthesizer.

[0070] 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 904 or the applications processor 902 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 902.

[0071] Synthesizer circuitry 906d of the RF circuitry 906 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+l (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.

[0072] In some embodiments, synthesizer circuitry 906d 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 906 may include an IQ/polar converter.

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

[0074] In some embodiments, the FEM circuitry 908 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 906). The transmit signal path of the FEM circuitry 908 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 906), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 910.

[0075] FIG. 10 provides an example illustration of the wireless device, such as a user equipment (UE), a mobile station (MS), a mobile wireless device, a mobile

communication device, a tablet, a handset, or other type of wireless device. The wireless device can include one or more antennas configured to communicate with a node, macro node, low power node (LPN), or, transmission station, such as a base station (BS), an evolved Node B (eNB), a baseband processing unit (BBU), a remote radio head (RRH), a remote radio equipment (RRE), a relay station (RS), a radio equipment (RE), or other type of wireless wide area network (WWAN) access point. The wireless device can be configured to communicate using at least one wireless communication standard such as, but not limited to, 3GPP LTE, WiMAX, High Speed Packet Access (HSPA), Bluetooth, and WiFi. The wireless device can communicate using separate antennas for each wireless communication standard or shared antennas for multiple wireless communication standards. The wireless device can communicate in a wireless local area network (WLAN), a wireless personal area network (WPAN), and/or a WWAN. The wireless device can also comprise a wireless modem. The wireless modem can comprise, for example, a wireless radio transceiver and baseband circuitry (e.g., a baseband processor). The wireless modem can, in one example, modulate signals that the wireless device transmits via the one or more antennas and demodulate signals that the wireless device receives via the one or more antennas.

|0076] FIG 10 also provides an illustration of a microphone and one or more speakers that can be used for audio input and output from the wireless device. The display screen can be a liquid crystal display (LCD) screen, or other type of display screen such as an organic light emitting diode (OLED) display. The display screen can be configured as a touch screen. The touch screen can use capacitive, resistive, or another type of touch screen technology. An application processor and a graphics processor can be coupled to internal memory to provide processing and display capabilities. A non-volatile memory port can also be used to provide data input/output options to a user. The non-volatile memory port can also be used to expand the memory capabilities of the wireless device. A keyboard can be integrated with the wireless device or wirelessly connected to the wireless device to provide additional user input. A virtual keyboard can also be provided using the touch screen.

Examples |0077] The following examples pertain to specific technology embodiments and point out specific features, elements, or actions that can be used or otherwise combined in achieving such embodiments.

|0078] Example 1 includes an apparatus of a user equipment (UE) with full-duplex capability, the apparatus comprising one or more processors and memory configured to: receive, at the UE, downlink broadcast information from the eNodeB; determine, at the UE, the eNodeB supports a full-duplex mode based on the downlink broadcast information; identify, at the UE, that the UE supports a full-duplex mode; and transmit, from the UE to the eNodeB, a UE capability information message indicating that the UE supports the full-duplex mode, wherein the UE is configured to communicate with the eNodeB in accordance with the full-duplex mode.

|0079] Example 2 includes the apparatus of Example 1, wherein at least one of the UE and the eNodeB supports the full-duplex mode, wherein the full-duplex mode enables a simultaneous transmission and reception of data using a same time and frequency resource at both the UE and the eNodeB or at one of the UE and the eNodeB.

[0080] Example 3 includes the apparatus of any of Examples 1-2, wherein the UE is configured to operate in one of: a dual time division duplexing and full-duplex (TDD-FD) mode, a dual frequency division duplexing and full-duplex (FDD-FD) mode, or a triple TDD-FDD-FD mode.

[0081] Example 4 includes the apparatus of any of Examples 1-3, wherein the UE capability information message includes a time division duplexing (TDD) full-duplex (FD) additional UE Evolved Universal Terrestrial Radio Access (EUTRA) capabilities field that utilizes oiie or more feature group indicator (FGI) bits to indicate that the UE supports a dual TDD-FD mode.

(0082] Example 5 includes the apparatus of any of Examples 1-4, wherein the UE capability information message includes a frequency division duplexing (FDD) full- duplex (FD) additional UE Evolved Universal Terrestrial Radio Access (EUTRA) capabilities field that utilizes one or more feature group indicator (FGI) bits to indicate that the UE supports a dual FDD-FD mode.

[0083] Example 6 includes the apparatus of any of Examples 1-5, wherein the UE capability information message includes one or more feature group indicator (FGI) bits to support UE mobility between cells that support a full-duplex (FDD-FD) mode.

[0084] Example 7 includes the apparatus of any of Examples 1-6, wherein the UE capability information message includes: a first feature group indicator (FGI) bit to support a handover of the UE from a first eNodeB that operates in a frequency division duplexing and full-duplex (FDD-FD) mode to a second eNodeB that operates in a frequency division duplexing (FDD) mode, or vice versa; a second FGI bit to support a handover of the UE from a first eNodeB that operates in a time division duplexing and full-duplex (TDD-FD) mode to a second eNodeB that operates in a TDD mode, or vice versa; a third FGI bit to support a handover of the UE from a first eNodeB that operates in a TDD-FD mode to a second eNodeB that operates in a FDD mode, or vice versa; a fourth FGI bit to support a handover of the UE from a first eNodeB that operates in a FDD-FD mode to a second eNodeB that operates in a TDD mode, or vice versa; and a fifth FGI bit to support a handover of the UE from a first eNodeB that operates in a FDD- FD mode to a second eNodeB that operates in a TDD-FD mode, or vice versa.

[0085] Example 8 includes the apparatus of any of Examples 1-7, wherein the downlink broadcast information received from the eNodeB includes a primary synchronization signal (PSS) and a secondary synchronization signal (SSS), wherein the UE is configured to determine that the eNodeB supports the full-duplex mode based on a location of the PSS and the SSS.

|0086] Example 9 includes the apparatus of any of Examples 1-8, wherein the UE is configured to determine that the eNodeB supports the full-duplex mode based on dedicated signaling received from the eNodeB.

|0087] Example 10 includes the apparatus of any of Examples 1-9, wherein the UE includes at least one of an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, a baseband processor, an internal memory, a non-volatile memory port, and combinations thereof.

|0088| Example 11 includes at least one machine readable storage medium having instructions embodied thereon for communicating full-duplex capability information at a user equipment (UE), the instructions when executed perform the following: determining, using one or more processors at the UE, that an eNodeB supports a full-duplex mode; identifying, using the one or more processors at the UE, that the UE supports a full- duplex mode, wherein the full-duplex mode is supported by at least one of the UE and the eNodeB, wherein the full-duplex mode enables a simultaneous transmission and reception of data using a same time and frequency resource; and transmitting, using the one or more processors at the UE, a UE capability information message to the eNodeB indicating that the UE supports the full-duplex mode, wherein the UE is configured to communicate with the eNodeB in accordance with the full-duplex mode.

|0089] Example 12 includes the at least one machine readable storage medium of Example 1 1 , further comprising instructions which when executed perform the following: determining that the eNodeB supports the full-duplex mode based on a location of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) transmitted from the eNodeB.

(0090] Example 13 includes the at least one machine readable storage medium of any of Examples 11-12, further comprising instructions which when executed perform the following: determining that the eNodeB supports the full-duplex mode based on dedicated signaling or broadcast signaling received from the eNodeB.

|0091] Example 14 includes the at least one machine readable storage medium of any of Examples 1 1 -13, wherein the UE is configured to operate in one of: a dual time division duplexing and full-duplex (TDD-FD) mode, a dual frequency division duplexing and full- duplex (FDD-FD) mode, or a triple TDD-FDD-FD mode.

|0092] Example 15 includes the at least one machine readable storage medium of any of Examples 1 1- 14, wherein the UE capability information message includes a time division duplexing (TDD) full-duplex (FD) additional UE Evolved Universal Terrestrial Radio Access (EUTRA) capabilities field that utilizes one or more feature group indicator (FGI) bits to indicate that the UE supports a dual TDD-FD mode.

|0093] Example 16 includes the at least one machine readable storage medium of any of Examples 11 -15, wherein the UE capability information message includes a frequency division duplexing (FDD) full-duplex (FD) additional UE Evolved Universal Terrestrial Radio Access (EUTRA) capabilities field that utilizes one or more feature group indicator (FGI) bits to indicate that the UE supports a dual FDD-FD mode. |0094] Example 17 includes the at least one machine readable storage medium of any of Examples 11 -16, wherein the UE capability information message includes one or more feature group indicator (FGI) bits to support UE mobility between one of: a first cell that support a full-duplex (FD) mode and a second cell that does not support the FD mode, or vice versa; or a first cell that supports the FD mode and a second cell that supports the FD mode.

|0095] Example 18 includes an apparatus of an eNodeB with full-duplex capability, the apparatus comprising one or more processors and memory configured to: establish a connection between the eNodeB and a user equipment (UE), wherein the UE is configured to determine that the eNodeB supports a full-duplex mode during a connection establishment procedure between the eNodeB and the UE; receive, from the UE, a UE capability information message indicating that the UE supports a full-duplex mode, wherein the full-duplex mode is supported by at least one of the UE and the eNodeB, wherein the full-duplex mode enables a simultaneous transmission and reception of data using a same time and frequency resource; and perform, at the eNodeB, communications with the UE in accordance with the full-duplex mode.

|0096j Example 19 includes the apparatus of Example 18, wherein the eNodeB is configured to operate in one of: a time division duplexing or full-duplex (TDD-FD) mode in which the eNodeB is configured to dynamically switch between TDD and FD; or a frequency division duplexing or full-duplex (FDD-FD) mode in which the eNodeB is configured to dynamically switch between FDD and FD.

|0097] Example 20 includes the apparatus of any of Examples 18-19, wherein the eNodeB is configured to dynamically switch between a half-duplex mode and the full- duplex mode, wherein the half-duplex mode includes time division duplexing (TDD) or frequency division duplexing (FDD).

|0098] Example 21 includes the apparatus of any of Examples 18-20, further configured to transmit, to the UE, a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) to enable the UE to determine that the eNodeB supports the full-duplex mode based on a location of the PSS and the SSS.

10099] Example 22 includes the apparatus of any of Examples 18-21 , further configured to transmit, to the UE, dedicated signaling or broadcast signaling to enable the UE to determine that the eNodeB supports the full-duplex mode.

[00100] Example 23 includes an apparatus of an eNodeB with full-duplex capability, the apparatus comprising one or more processors and memory configured to: process, at the eNodeB, downlink broadcast information for transmission to a user equipment (UE), the downlink broadcast information indicating that the eNodeB supports a full-duplex mode, wherein the UE only supports a half-duplex mode; and perform, at the eNodeB, communications with the UE when the eNodeB supports the full-duplex mode and the UE only supports the half-duplex mode, wherein the eNodeB is configured to schedule a paired UE that only supports the half-duplex mode to utilize the full-duplex capability of the eNodeB.

100101] Example 24 includes the apparatus of Example 23, wherein the eNodeB configures the UE to receive and the paired UE to transmit in a same time or resource to utilize the full-duplex capability of the eNodeB.

(00102] Various techniques, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, compact disc-read-only memory (CD-ROMs), hard drives, non-transitory computer readable storage medium, or any other machine-readable storage medium wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the various techniques. A non-transitory computer readable storage medium can be a computer readable storage medium that does not include signal. In the case of program code execution on programmable computers, the computing device may include a processor, a storage medium readable by the processor (including volatile and non- volatile memory and/or storage elements), at least one input device, and at least one output device. The volatile and non-volatile memory and/or storage elements may be a random-access memory (RAM), erasable

programmable read only memory (EPROM), flash drive, optical drive, magnetic hard drive, solid state drive, or other medium for storing electronic data. The node and wireless device may also include a transceiver module (i.e., transceiver), a counter module (i.e., counter), a processing module (i.e., processor), and/or a clock module (i.e., clock) or timer module (i.e., timer). One or more programs that may implement or utilize the various techniques described herein may use an application programming interface (API), reusable controls, and the like. Such programs may be implemented in a high level procedural or object oriented programming language to communicate with a computer system. However, the program(s) may be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language, and combined with hardware implementations.

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

[00104] It should be understood that many of the functional units described in this specification have been labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very-large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

[00105] Modules may also be implemented in software for execution by various types of processors. An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executabies of an identified module may not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.

[00106] Indeed, a module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The Operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network. The modules may be passive or active, including agents operable to perform desired functions.

100107] Reference throughout this specification to "an example" or "exemplary" means that a particular feature, structure, or characteristic described in connection with the example is included in at least one embodiment of the present technology. Thus, appearances of the phrases "in an example" or the word "exemplary" in various places throughout this specification are not necessarily all referring to the same embodiment.

[00108] As used herein, a plurality of items, structural elements, compositional elements, and/or materials may be presented in a common list for convenience. However^ these lists should be construed as though each member of the list is individually identified as a separate and unique member. Thus, no individual member of such list should be construed as a de facto equivalent of any other member of the same list solely based on their presentation in a common group without indications to the contrary. In addition, various embodiments and example of the present technology may be referred to herein along with alternatives for the various components thereof. It is understood that such embodiments, examples, and alternatives are not to be construed as defacto equivalents of one another, but are to be considered as separate and autonomous representations of the present technology.

[00109] Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided, such as examples of layouts, distances, network examples, etc., to provide a thorough understanding of embodiments of the technology. One skilled in the relevant art will recognize, however, that the technology can be practiced without one or more of the specific details, or with other methods, components, layouts, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the technology. (00110] While the forgoing examples are illustrative of the principles of the present technology in one or more particular applications, it will be apparent to those of ordinary skill in the art that numerous modifications in form, usage and details of implementation can be made without the exercise of inventive faculty, and without departing from the principles and concepts of the technology. Accordingly, it is not intended that the technology be limited, except as by the claims set forth below.

Claims

CLAIMS What is claimed is:

1. An apparatus of a user equipment (UE) with full-duplex capability, the apparatus comprising one or more processors and memory configured to:

process, at the UE, downlink broadcast information received from the eNodeB;

determine, at the UE, the eNodeB supports a full-duplex mode based on the downlink broadcast information;

identify, at the UE, that the UE supports a full-duplex mode; and process, at the UE, a UE capability information message for transmission to the eNodeB that indicates the UE supports the full-duplex mode, wherein the UE is configured to communicate with the eNodeB in accordance with the full- duplex mode.

2. The apparatus of claim 1 , wherein at least one of the UE and the eNodeB supports the full-duplex mode, wherein the full-duplex mode enables a simultaneous transmission and reception of data using a same time and frequency resource at both the UE and the eNodeB or at one of the UE and the eNodeB.

3. The apparatus of any of claims 1 to 2, wherein the UE is configured to operate in one of: a dual time division duplexing and full-duplex (TDD-FD) mode, a dual frequency division duplexing and full-duplex (FDD-FD) mode, or a triple TDD- FDD-FD mode.

4. The apparatus of claim 1, wherein the UE capability information message includes a time division duplexing (TDD) full-duplex (FD) additional UE Evolved Universal Terrestrial Radio Access (EUTRA) capabilities field that utilizes one or more feature group indicator (FGI) bits to indicate that the UE supports a dual TDD-FD mode.

5. The apparatus of claim 1 , wherein the UE capability information message includes a frequency division duplexing (FDD) full-duplex (FD) additional UE Evolved Universal Terrestrial Radio Access (EUTRA) capabilities field that utilizes one or more feature group indicator (FGI) bits to indicate that the UE supports a dual FDD-FD mode.

6. The apparatus of claim 1, wherein the UE capability information message includes one or more feature group indicator (FGI) bits to support UE mobility between cells that support a full-duplex (FDD-FD) mode.

7. The apparatus of any of claims 4 to 6, wherein the UE capability information message includes:

a first feature group indicator (FGI) bit to support a handover of the UE from a first eNodeB that operates in a frequency division duplexing and full- duplex (FDD-FD) mode to a second eNodeB that operates in a frequency division duplexing (FDD) mode, or vice versa;

a second FGI bit to support a handover of the UE from a first eNodeB that operates in a time division duplexing and full-duplex (TDD-FD) mode to a second eNodeB that operates in a TDD mode, or vice versa;

a third FGI bit to support a handover of the UE from a first eNodeB that operates in a TDD-FD mode to a second eNodeB that operates in a FDD mode, or vice versa;

a fourth FGI bit to support a handover of the UE from a first eNodeB that operates in a FDD-FD mode to a second eNodeB that operates in a TDD mode, or vice versa; and

a fifth FGI bit to support a handover of the UE from a first eNodeB that operates in a FDD-FD mode to a second eNodeB that operates in a TDD-FD mode, or vice versa.

8. The apparatus of claim 1, wherein the downlink broadcast information received from the eNodeB includes a primary synchronization signal (PSS) and a secondary synchronization signal (SSS), wherein the UE is configured to determine that the eNodeB supports the full-duplex mode based on a location of the PSS and the SSS.

9. The apparatus of claim 1 , wherein the UE is configured to determine that the eNodeB supports the full-duplex mode based on dedicated signaling received from the eNodeB.

:

10. The apparatus of claim 1, wherein the UE includes at least one of an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, a baseband processor, an internal memory, a non- volatile memory port, and combinations thereof.

11. At least one machine readable storage medium having instructions embodied thereon for communicating full-duplex capability information at a user equipment (UE), the instructions when executed perform the following:

determining, using one or more processors at the UE, that an eNodeB supports a full-duplex mode;

identifying, using the one or more processors at the UE, that the UE supports a full-duplex mode, wherein the full-duplex mode is supported by at least one of the UE and the eNodeB, wherein the full-duplex mode enables a simultaneous transmission and reception of data using a same time and frequency resource; and

processing, using the one or more processors at the UE, a UE capability information message for transmission to the eNodeB, wherein the UE capability information message indicates that the UE supports the full-duplex mode, wherein the UE is configured to communicate with the eNodeB in accordance with the full-duplex mode.

12. The at least one machine readable storage medium of claim 1 1 , further comprising instructions which when executed perform the following: determining that the eNodeB supports the full-duplex mode based on a location of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) transmitted from the eNodeB.

13. The at least one machine readable storage medium of claim 1 1 , further comprising instructions which when executed perform the following: determining that the eNodeB supports the full-duplex mode based on dedicated signaling or broadcast^■_ signaling received from the eNodeB.

14. The at least one machine readable storage medium of claim 1 1, wherein the UE is configured to operate in one of: a dual time division duplexing and full-duplex (TDD-FD) mode, a dual frequency division duplexing and full-duplex (FDD-FD) mode, or a triple TDD-FDD-FD mode.

15. The at least one machine readable storage medium of claim 1 1 , wherein the UE capability information message includes a time division duplexing (TDD) full- duplex (FD) additional UE Evolved Universal Terrestrial Radio Access (EUTRA) capabilities field that utilizes one or more feature group indicator (FGI) bits to indicate that the UE supports a dual TDD-FD mode.

16. The at least one machine readable storage medium of any of claims 1 1 to 15, wherein the UE capability information message includes a frequency division duplexing (FDD) full-duplex (FD) additional UE Evolved Universal Terrestrial Radio Access (EUTRA) capabilities field that utilizes one or more feature group indicator (FGI) bits to indicate that the UE supports a dual FDD-FD mode.

17. The at least one machine readable storage medium of claim 1 1 , wherein the UE capability information message includes one or more feature group indicator (FGI) bits to support UE mobility between one of:

a first cell that support a full-duplex (FD) mode and a second cell that does not support the FD mode, or vice versa; or

a first cell that supports the FD mode and a second cell that supports the FD mode.

18. An apparatus of an eNodeB with full-duplex capability, the apparatus comprising one or more processors and memory configured to: establish a connection between the eNodeB and a user equipment (UE), wherein the UE is configured to determine that the eNodeB supports a full-duplex mode during a connection establishment procedure between the eNodeB and the UE;

process, at the eNodeB, a UE capability information message received from the UE, the UE capability information message indicating that the UE supports a full-duplex mode, wherein the full-duplex mode is supported by at least one of the UE and the eNodeB, wherein the full-duplex mode enables a simultaneous transmission and reception of data using a same time and frequency resource; and

perform, at the eNodeB, communications with the UE in accordance with the full-duplex mode.

19. The apparatus of claim 18, wherein the eNodeB is configured to operate in one of:

a time division duplexing or full-duplex (TDD-FD) mode in which the eNodeB is configured to dynamically switch between TDD and FD; or

a frequency division duplexing or full-duplex (FDD-FD) mode in which the eNodeB is configured to dynamically switch between FDD and FD.

20. The apparatus of any of claims 18 to 19, wherein the eNodeB is configured to dynamically switch between a half-duplex mode and the full-duplex mode, wherein the half-duplex mode includes time division duplexing (TDD) or frequency division duplexing (FDD).

21. The apparatus of claim 18, further configured to transmit, to the UE, a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) to enable the UE to determine that the eNodeB supports the full-duplex mode based on a location of the PSS and the SSS.

22. The apparatus of claim 18, further configured to transmit, to the UE, dedicated signaling or broadcast signaling to enable the UE to determine that the eNodeB supports the full-duplex mode.

23. An apparatus of an eNodeB with full-duplex capability, the apparatus comprising one or more processors and memory configured to:

process, at the eNodeB, downlink broadcast information for transmission to a user equipment (UE), the downlink broadcast information indicating that the eNodeB supports a full-duplex mode, wherein the UE only supports a half-duplex mode; and

perform, at the eNodeB, communications with the UE when the eNodeB supports the full-duplex mode and the UE only supports the half-duplex mode, wherein the eNodeB is configured to schedule a paired UE that only supports the half-duplex mode to utilize the full-duplex capability of the eNodeB.

24. The apparatus of claim 23, wherein the eNodeB configures the UE to receive and the paired UE to transmit in a same time or resource to utilize the full-duplex capability of the eNodeB.