WO2018031139A1

WO2018031139A1 - Enhanced lte-wlan aggregation x2 and xw support for handover without wlan termination change

Info

Publication number: WO2018031139A1
Application number: PCT/US2017/039944
Authority: WO
Inventors: Candy YIU; Alexander Sirotkin; Jerome Parron; Shadi Iskander; Umesh PHUYAL; Penny Efraim-Sagi; Ofer Hareuveni
Original assignee: Intel IP Corporation
Priority date: 2016-08-10
Filing date: 2017-06-29
Publication date: 2018-02-15
Also published as: DE112017004004T5

Abstract

Systems and methods of permitting continuous use of a WT are generally described. A target eNB receives a handover request LWA container that contains information for handover without a WT change, including an identity of the WT. In response, the target eNB transmits to the WT a WT addition request that indicates handover of the UE without a WT change via a UE ID. The WT addition request contains IEs that indicate one or more of E-RABs to add, modify and delete during handover. The UE and the WT may continue using a source eNB key until a target eNB key is sent by the target eNB. Once the target eNB key is received, the reception triggers re-association.

Description

ENHANCED LTE-WLAN AGGREGATION X2 AND XW SUPPORT FOR HANDOVER WITHOUT WLAN TERMINATION CHANGE

PRIORITY CLAIM

[0001] This application claims the benefit of priority to United States

Provisional Patent Application Serial No. 62/372,913, filed August 10, 2016, and entitled "ELW A X2 AND XW SUPPORT FOR HANDOVER WITHOUT WT CHANGE," which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

[0002] Embodiments pertain to radio access networks. Some embodiments relate to reference signal measurement in various cellular and wireless local area network (WLAN) networks, including Third Generation Partnership Project Long Term Evolution (3GPP LTE) networks and LTE advanced (LTE-A) networks as well as 4^th generation (4G) networks and 5^th generation (5G) networks. Some embodiments relate to handover in a WLAN, and in particular, handover without a WLAN termination (WT) change. BACKGROUND

[0003] The use of 3GPP LTE systems (including both LTE and LTE-A systems) has increased due to both an increase in the types of devices user equipment (UEs) using network resources as well as the amount of data and bandwidth being used by various applications, such as video streaming, operating on these UEs. LTE networks typically operate in a number of radio frequency (RF) bands licensed to a wireless operator in which base stations (evolved node Bs (eNBs)) and an increasing number and varying type of user equipment (UE) communicate.

[0004] Mobile connectivity is continually important is modem life. To this end, one goal that networks strive for is to provide sufficient signal strength from the radio access network (RAN). Especially in cases in which the UE is moving rapidly or the density of eNBs is high, this may involve multiple handovers between eNBs within the RAN. Each handover involves a variety of control signals between the UE and the RAN and between the RAN and the evolved packet core (EPC). In particular, data destined for the source eNB is stored in the EPC during die process of handover and eventually rerouted to the new source eNB. The current process of data transfer, however, in some cases is problematic due to recent revisions of the 3GPP standard.

BRIEF DESCRIPTION OF THE FIGURES

[0005] In the figures, which are not necessarily drawn to scale, like numerals may describe similar components in different views. Like numerals having different letter suffixes may represent different instances of similar components. The figures illustrate generally, by way of example, but not by way of limitation, various embodiments discussed in the present document.

[0006] FIG. 1 shows an example of a portion of an end-to-end network architecture of a LTE network in accordance with some embodiments.

[0007] FIG. 2 illustrates components of a communication device in accordance with some embodiments.

[0008] FIG. 3 illustrates a block diagram of a communication device in accordance with some embodiments.

[0009] FIG. 4 illustrates another block diagram of a communication device in accordance with some embodiments.

[00010 FIG. 5 illustrates a flow diagram of handover in accordance with some embodiments.

DETAILED DESCRIPTION

[0011] The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.

[0012] FIG. 1 shows an example of a portion of an end-to-end network architecture of a LTE network in accordance with some embodiments. As used herein, an LTE network refers to both LTE and LTE Advanced (LTE-A) networks as well as other versions of LTE networks to be developed. The network 100 may comprise a radio access network (RAN) (e.g., as depicted, the universal mobile telecommunications system (UMTS) terrestrial radio access network (UTRAN) or evolved UTRAN (E-UTRAN)) 101 and core network 120 (e.g., shown as an evolved packet core (EPC)) coupled together through an SI interface 115. For convenience and brevity, only a portion of the core network 120, as well as the RAN 101, is shown in the example.

[0013] The core network 120 may include a mobility management entity

(MME) 122, serving gateway (serving GW) 124, and packet data network gateway (PDN GW) 126. The RAN 101 may include evolved node Bs (eNBs) 104 (which may operate as base stations) for communicating with user equipment (UE) 102. The eNBs 104 may include macro eNBs 104a and low power (LP) eNBs 104b. Other elements, such as a Home Location Register (HLR)/Home Subscriber Server (HSS), a database including subscriber information of a 3 GPP network that may perform configuration storage, identity management and user state storage, and a Policy and Charging Rule Function (PCRF) that performs policy decision for dynamically applying Quality of Service (QoS) and charging policy per service flow, are not shown for convenience.

[0014] The MME 122 may be similar in function to the control plane of legacy Serving GPRS Support Nodes (SGSN). The MME 122 may manage mobility aspects in access such as gateway selection and tracking area list management, performing both mobility management (MM) and session management (SM). The Non- Access Stratum (NAS) is a part of the control plane between a UE 102 and the MME 122. The NAS is used for signaling between the UE 102 and the EPC in the LTE/UMTS protocol stack. The NAS supports UE mobility and session management for establishing and maintaining an IP connection between the UE 102 and PDN GW 126.

[0015] The serving GW 124 may terminate the user plane interface toward the RAN 101, and route data packets between the RAN 101 and the core network 120. In addition, the serving GW 124 may be a local mobility anchor point for inter-eNB handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and policy enforcement, packet routing, idle mode packet buffering, and triggering an MME to page a UE. The serving GW 124 and the MME 122 may be implemented in one physical node or separate physical nodes.

[0016] The PDN GW 126 may terminate a SGi interface toward the packet data network (PDN). The PDN GW 126 may route data packets between the EPC 120 and the external PDN, and may perform policy enforcement and charging data collection UE IP address assignment, packet screening and filtering. The PDN GW 126 may also provide an anchor point for mobility devices with a non-LTE access. The external PDN can be any kind of IP network, as well as an IP Multimedia Subsystem (IMS) domaia The PDN GW 126 and the serving GW 124 may be implemented in a single physical node or separate physical nodes.

[0017] The eNBs 104 (macro and micro) may terminate the air interface protocol and may be the first point of contact for a UE 102. In some embodiments, an eNB 104 may fulfill various logical functions for the RAN 101 including, but not limited to, RNC (radio network controller functions) such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. In accordance with embodiments, UEs 102 may be configured to communicate orthogonal frequency division multiplexed (OFDM) communication signals with an eNB 104 over a multi carrier communication channel in accordance with an OFDMA communication technique. The OFDM signals may comprise a plurality of orthogonal subcarriers.

[0018] The SI interface 115 may be the interface that separates the RAN 101 and the EPC 120. It may be split into two parts: the Sl-U, which may carry traffic data between the eNBs 104 and the serving GW 124, and the SI -MME, which may be a signaling interface between the eNBs 104 and Die MME 122. The X2 interface may be the interface between eNBs 104. TheX2 interface may comprise two parts, the X2-C and X2-U. The X2-C may be the control plane interface between the eNBs 104, while the X2-U may be the user plane interface between the eNBs 104.

[0019] With cellular networks, LP cells 104 b may be typically used to extend coverage to indoor areas where outdoor signals do not reach well, or to add network capacity in areas with dense usage. In particular, it may be desirable to enhance the coverage of a wireless communication system using cells of different sizes, macrocells, microcells, picocells, and femtocells, to boost system performance. The cells of different sizes may operate on the same frequency band, or may operate on different frequency bands with each cell operating in a different frequency band or only cells of different sizes operating on different frequency bands. As used herein, the term LP eNB refers to any suitable relatively LP eNB for implementing a smaller cell (smaller than a macro cell) such as a femtocell, a picocell, or a microcell. Femtocell eNBs may be typically provided by a mobile network operator to its residential or enterprise customers. A femtocell may be typically the size of a residential gateway or smaller and generally connect to a broadband line. The femtocell may connect to the mobile operator's mobile network and provide extra coverage in a range of typically 30 to SO meters. Thus, a LP eNB 104b might be a femtocell eNB. In some embodiments, when the LP eNB 104b is a Home eNB (HeNB), a HeNB Gateway may be provided between the HeNB and the MME/Service Gateway. This HeNB Gateway may control multiple HeNBs and provide user data and signal traffic from the HeNBs towards the MME/Service Gateway. Similarly, a picocell may be a wireless communication system typically covering a small area, such as in-building (offices, shopping malls, train stations, etc.), or more recently in -aircraft A picocell eNB may generally connect through the X2 link to another eNB such as a macro eNB through its base station controller (BSC) functionality and/or connect via an SI interface to an MME/Service Gateway. Thus, LP eNB may be implemented with a picocell eNB since it may be coupled to a macro eNB 104a via an X2 interface. Picocell eNBs or other LP eNBs LP eNB 104b may incorporate some or all functionality of a macro eNB LP eNB 104a. In some cases, this may be referred to as an access point base station or enterprise femtocell.

[0020] The UEs 102 may also be connected with a WLAN 106, which may include an access point (AP). The UEs 102 may thus support multiple

Radio Access Technologies (RATs) for communications. The UEs 102 may use IEEE 802.11 protocols to communicate with the WLAN 106. The WLAN 106 may contain a WLAN termination (WT) 106a, a logical node in the WLAN 106 where the Xw interface between the eNB 104 and the WLAN 106 terminates. The WT 106a may be implemented at an AP, access controller or another physical entity. The WLAN 106 may be connected with the eNBs 104 through an Xw interface over which both user and control plane data are communicated. The WLAN 106 also may be connected with the PDN gateway 126 through an evolved Packet Data Gateway (ePDG) or Trusted WLAN Access Gateway (TWAG) 108. In some embodiments, an un trusted WLAN may be used in conjunction with tunneling and the ePDG 108. In embodiments in which the eNB 104 is the anchor point for both the user and control plane, LTE/WiFi aggregation (LWA) using the WLAN 106 may only be possible when the UE is in the RRC connected state.

[0021] Data plane aggregation may occur at a packet data convergence protocol (PDCP) layer at the eNB 104 and UE 102. The eNB 104 may send a downlink PDCP packet data unit (PDU) over either LTE or WiFi. The eNB 104 may schedule uplink LTE data transmissions and uplink WLAN data transmissions may be initiated by the UE 102. For uplink WLAN transmissions, the UE 102 (or AP to which the UE 102 is connected) may encapsulate the PDCP PDU in a WiFi MAC packet to be transmitted over WiFi. For downlink WLAN transmissions, a WiFi station in the UE 102 may forward the received WiFi packet payload to the UE PDCP layer, using an identifier to specify the presence of an LTE payload.

[0022] FIG. 2 illustrates components of a communication device in accordance with some embodiments. The communication device 200 may be a UE, eNB or other network component as described herein. The communication device 200 may be a stationary, non-mobile device or may be a mobile device. In some embodiments, the UE 200 may include application circuitry 202, baseband circuitry 204, Radio Frequency (RF) circuitry 206, front-end module (FEM) circuitry 208 and one or more antennas 210, coupled together at least as shown. At least some of the baseband circuitry 204, RF circuitry 206, and FEM circuitry 208 may form a transceiver. In some embodiments, other network elements, such as the MME may contain some or all of the components shown in FIG. 2. [0023] The application or processing circuitry 202 may include one or more application processors. For example, the application circuitry 202 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 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. The processing circuitry 202 may generate signals for transmission through an interface to other internal components, such as the transceiver, and then from the transceiver for transmission through the network.

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

[0025] In some embodiments, the baseband circuitry 204 may include elements of a protocol stack such as, for example, elements of an E-UTRAN protocol including, for example, physical (PHY), media access control (MAC), radio link control (RLC), PDCP, radio resource control (RRC) elements, and/or Non-Access Stratum (NAS) elements. A central processing unit (CPU) 204e of the baseband circuitry 204 may be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers, and/or NAS. In some embodiments, the baseband circuitry may include one or more audio digital signal processors) (DSP) 204f. The audio DSP(s) 204f 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 embocliments, some or all of the constituent components of the

baseband circuitry 204 and the application circuitry 202 may be

implemented together such as, for example, on a system on a chip (SOC).

[0026] In some embodiments, the baseband circuitry 204 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 204 may support communication with an E-UTRAN 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 204 is configured to support radio communications of more man one wireless protocol may be referred to as multi-mode baseband circuitry. In some embodiments, the device can be configured to operate in accordance with communication standards or other protocols or standards, including Institute of Electrical and Electronic Engineers (IEEE) 802.16 wireless technology (WiMax), IEEE 802.11 wireless technology (WiFi) including IEEE 802.11 ad, which operates in the 60 GHz millimeter wave spectrum, various other wireless technologies such as global system for mobile communications (GSM), enhanced data rates for GSM evolution (EDGE), GSM EDGE radio access network (GERAN), universal mobile telecommunications system (UMTS), UTRAN, E-UTRAN, or other 2G, 3G, 4G, SG, etc. technologies either already developed or to be developed.

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

[0028] In some embodiments, the RF circuitry 206 may include a receive signal path and a transmit signal path. The receive signal path of the RF circuitry 206 may include mixer circuitry 206a, amplifier circuitry 206b and filter circuitry 206c. The transmit signal path of the RF circuitry 206 may include filter circuitry 206c and mixer circuitry 206a. RF circuitry 206 may also include synthesizer circuitry 206d for synthesizing a frequency for use by the mixer circuitry 206a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 206a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 208 based on the synthesized frequency provided by synthesizer circuitry 206d The amplifier circuitry 206b may be configured to amplify the down-converted signals and the filter circuitry 206c 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 204 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 206a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect [0029] In some embodiments, the mixer circuitry 206a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 206d to generate RF output signals for me FEM circuitry 208. The baseband signals may be provided by the baseband circuitry 204 and may be filtered by filter circuitry 206c. The filter circuitry 206c may include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect

[0030] In some embodiments, the mixer circuitry 206a of the receive signal path and the mixer circuitry 206a 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 206a of the receive signal path and the mixer circuitry 206a 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 206a of the receive signal path and the mixer circuitry 206a may be arranged for direct downconversion and/or direct upconversion, respectively. In some embodiments, the mixer circuitry 206a of the receive signal path and the mixer circuitry 206a of the transmit signal path may be configured for super-heterodyne operation.

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

[0032] 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 hmited in this respect

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

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

[0035] In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although mat is not a requirement. Divider control input may be provided by either the baseband circuitry 204 or the applications processor 202 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a lookup table based on a channel indicated by the applications processor 202.

[0036] Synthesizer circuitry 206d of the RF circuitry 206 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 (DP A). 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.

[0037] In some embodiments, synthesizer circuitry 206d 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 aLO frequency (fLo). In some embodiments, the RF circuitry 206 may include an IQ/polar converter. [002(81 FEM circuity 208 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 210, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 206 for further processing. FEM circuitry 208 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 206 for transmission by one or more of the one or more antennas 210.

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

[0040] In some embodiments, the coinmunication device 200 may include additional elements such as, for example, memory/storage, display, camera, sensor, and/or input/output (I/O) interface as described in more detail below. In some embodiments, the communication device 200 described herein may be part of a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless

communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), or other device that may receive and/or transmit information wirelessly. In some embodiments, the communication device 200 may include one or more user interfaces designed to enable user interaction with the system and/or peripheral component interfaces designed to enable peripheral component interaction with the system. For example, the communication device 200 may include one or more of a keyboard, a keypad, a touchpad, a display, a sensor, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, a power supply interface, one or more antennas, a graphics processor, an application processor, a speaker, a microphone, and other I/O components. The display may be an LCD or LED screen including a touch screen. The sensor may include a gyro sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may communicate with components of a positioning network, e.g., a global positioning system (GPS) satellite.

[0041] The antennas 210 may comprise one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, nricrostrip antennas or other types of antennas suitable for transmission of RF signals. In some multiple-input multiple-output (MIMO) embodiments, the antennas 210 may be effectively separated to take advantage of spatial diversity and the different channel characteristics mat may result

[0042] Although the communication device 200 is illustrated as having several separate functional elements, one or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements. For example, some elements may comprise one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein. In some embodiments, the functional elements may refer to one or more processes operating on one or more processing elements.

[0043] Embodiments may be implemented in one or a combination of hardware, firmware and software. Embodiments may also be implemented as instructions stored on a computer-readable storage device, which may be read and executed by at least one processor to perform the operations described herein. A computer-readable storage device may include any non-transitory mechanism for storing information in a form readable by a machine (e.g., a computer). For example, a computer-readable storage device may include readonly memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices, and other storage devices and media Some embodiments may include one or more processors and may be configured with instructions stored on a computer-readable storage device.

[0044] FIG. 3 is a block diagram of a communication device in accordance with some embodiments. The device may be a UE, for example, such as the UE shown in FIG. 1. The physical layer circuitry 302 may perform various encoding and decoding functions that may include formation of baseband signals for transmission and decoding of received signals. The communication device 300 may also include medium access control layer (MAC) circuitry 304 for controlling access to the wireless medium. The communication device 300 may also include processing circuitry 306, such as one or more single-core or multi-core processors, and memory 308 arranged to perform the operations described herein. The physical layer circuitry 302, MAC circuitry 304 and processing circuitry 306 may handle various radio control functions that enable communication with one or more radio networks compatible with one or more radio technologies. The communication device 300 may include packet data convergence protocol (PDCP) and radio link control (RLC) circuitry in the physical layer circuitry 302 or another entity. The radio control functions may include signal modulation, encoding, decoding, radio frequency shifting, etc. For example, similar to the device shown in FIG. 2, in some embodiments, communication may be enabled with one or more of a WMAN, a WLAN, and a WPAN. In some embodiments, the communication device 300 can be configured to operate in accordance with 3 GPP standards or other protocols or standards, including WiMax, WiFi, WiGig, GSM, EDGE, GERAN, UMTS, E-UTRAN, UTRAN, or other 3G, 3G, 4G, 5G, etc.

technologies either already developed or to be developed. The communication device 300 may include transceiver circuitry 312 to enable communication with other external devices wirelessly and interfaces 314 to enable wired

communication with other external devices. As another example, the transceiver circuitry 312 may perform various transmission and reception functions such as conversion of signals between a baseband range and a Radio Frequency (RF) range. [0045] The antennas 301 may comprise one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, nticrostrip antennas or other types of antennas suitable for transmission of RF signals. In some MIMO embodiments, the antennas 301 may be effectively separated to take advantage of spatial diversity and the different channel characteristics that may result.

[0046] Although the communication device 300 is illustrated as having several separate functional elements, one or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including DSPs, and/or other hardware elements. For example, some elements may comprise one or more

microprocessors, DSPs, FPGAs, ASICs, RFICs and combinations of various hardware and logic circuitry for peifonning at least the functions described herein. In some embodiments, the functional elements may refer to one or more processes operating on one or more processing elements. Embodiments may be implemented in one or a combination of hardware, firmware and software. Embodiments may also be implemented as instructions stored on a computer- readable storage device, which may be read and executed by at least one processor to perform the operations described herein.

[0047] FIG. 4 illustrates another block diagram of a communication device in accordance with some embodiments. In alternative embodiments, the communication device 400 may operate as a standalone device or may be connected (e.g., networked) to other communication devices. In a networked deployment, the communication device 400 may operate in the capacity of a server communication device, a client communication device, or both in server- client network environments. In an example, the communication device 400 may act as a peer communication device in peer-to-peer (P2P) (or other distributed) network environment The communication device 400 may be a UE, eNB, PC, a tablet PC, a STB, a PDA, a mobile telephone, a smart phone, a web appliance, a network router, switch or bridge, or any communication device capable of executing instructions (sequential or otherwise) that specify actions to be taken by that communication device. Further, while only a single communication device is illustrated, the term ''communication device" shall also be taken to include any collection of communication devices mat individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), other computer cluster configurations.

[0048] Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms. Modules are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner. In an example, circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module. In an example, me whole or part of one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module mat operates to perform specified operations. In an example, the software may reside on a communication device readable medium. In an example, the software, when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.

[0049] Accordingly, the term "module" is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g. , hardwired), or temporarily (e.g., transitorily) configured (e.g. , programmed) to operate in a specified manner or to perform part or all of any operation described herein. Considering examples in which modules are temporarily configured, each of the modules need not be instantiated at any one moment in time. For example, where the modules comprise a general-purpose hardware processor configured using software, the general-purpose hardware processor may be configured as respective different modules at different times. Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.

[0050] Communication device (e.g., computer system) 400 may include a hardware processor 402 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 404 and a static memory 406, some or all of which may communicate with each other via an interlink (e.g., bus) 408. Hie

communication device 400 may further include a display unit 410, an alphanumeric input device 412 (e.g., a keyboard), and a user interface (UI) navigation device 414 (e.g., a mouse). In an example, the display unit 410, input device 412 and UI navigation device 414 may be a touch screen display. The communication device 400 may additionally include a storage device (e.g., drive unit) 416, a signal generation device 418 (e.g., a speaker), a network interface device 420, and one or more sensors 421, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor. The communication device 400 may include an output controller 428, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).

[0051] The storage device 416 may include a communication device readable medium 422 on which is stored one or more sets of data structures or instructions 424 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 424 may also reside, completely or at least partially, within the main memory 404, within static memory 406, or within the hardware processor 402 during execution thereof by the communication device 400. In an example, one or any combination of the hardware processor 402, the main memory 404, the static memory 406, or the storage device 416 may constitute communication device readable media

[0052] While the communication device readable medium 422 is illustrated as a single medium, the term "communication device readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 424.

[0053] The term "communication device readable medium'' may include any medium that is capable of storing, encoding, or carrying instructions for execution by the communication device 400 and that cause the communication device 400 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non-limiting communication device readable medium examples may include solid-state memories, and optical and magnetic media Specific examples of communication device readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (E EPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks;

magneto-optical disks; Random Access Memory (RAM); and CD-ROM and DVD-ROM disks. In some examples, communication device readable media may include non-transitory communication device readable media In some examples, communication device readable media may include communication device readable media that is not a transitory propagating signal.

[0054] The instructions 424 may further be transmitted or received over a communications network 426 using a transmission medium via the network interface device 420 utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks (e.g., IEEE 802.11 family of standards known as WiFi®, IEEE 802.16 family of standards known as WiMax®), IEEE 802.15.4 family of standards, a LTE family of standards, a UMTS family of standards, peer-to-peer (P2P) networks, among others. In an example, the network interface device 420 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 426. In an example, the network interface device 420 may include a plurality of antennas to wirelessly communicate using at least one of single-input multiple-output (SIMO), MEMO, or multiple-input single-output (MISO) techniques. In some examples, the network interface device 420 may wirelessly communicate using Multiple User MIMO techniques. The term "transmission medium" shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the communication device 400, and includes digital or analog communications signals or other intangible medium to facilitate communication of such software.

[0055] As above, Release 14 of the 3GPP LTE specification introduced changes to the handover process. The handover may be an inter- or intra E- UTRAN handover from a source eNB to a target eNB. Independent of whether the handover is intra- or inter-network, the handover process may take a number of operations and it may overall take a significant amount of time to complete the operations involved in the handover process.

[0056] In embodiments in which the UE is connected with a WT, handover may be performed between a source and target eNB while the WLAN that the UE is connected to may remain the same. In some embodiments, the WLAN may remain the same whether or not the AP changes.

[0057] Release 14 of the 3 GPP LTE specification permits continued data reception and transmission at the UE from/towards the WT during handover if the target eNB is able to accept the same WT configuration as used by the source eNB. This is different from previous releases, in which the WT is associated with the UE and a single eNB. In previous releases, during handover, the source eNB first releases the LWA configuration for the UE and the target eNB then reconfigures the LWA for the UE after the handover is complete. In these embodiments, in response to decoding of a handover command the UE may first de-associate from the WT and subsequently re-associate with the same or a different WT for further commumcatioa This may be problematic, resulting in service interruptions that are visible to the user. It may be beneficial to establish signaling between the various entities to enable continuous cornmuni cation between the UE and E-UTRAN via the WT during handover. This may avoid packet loss during handover. Such procedures may be of particular interest to UEs that are located at the cell edge of a serving eNB and thus may be connected with the E-UTRAN solely through the WT.

[0058] FIG. 5 illustrates a flow diagram of handover in accordance with some embodiments. The flow diagram 500 may include a UE 502, a source eNB 504, a target eNB 506 and a WT 508. Each of the UE 502, source eNB 504, target eNB 506 and WT 508 may have components similar to those shown in FIGS. 2-4. The handover operations 500 shown in FIG. 5 may not be exclusive, other operations, such as communications between the source eNB 504 and MME or serving gateway, may be present but not shown for convenience.

[0059] The operations may include, for example, the UE 502 measuring signal and/or channel qualities of reference signals transmitted by the source eNB 504. The UE S02 may subsequently transmit a report to the source eNB 504. The report may include, for example, signal-to-noise ratio measurements (SINR), signal-to-interference ratio measurements (SIR), error rate, etc.

[0060] The source eNB 504 may determine from the report whether to initiate handover, as well as with which eNB the handover should be performed. If handover is to occur, the source eNB 504 may determine a target eNB 506. The source eNB 504 may then at operation 1 send a handover request containing UE information to the target eNB 506 over the X2 interface. Note that prior to transmission of the handover request, the handover request (as the other transmissions disclosed herein) may be encoded for transmission. The handover request of operation 1 may also include a LWA container that includes the LWA configuration for the UE 502. An embodiment of the handover request is described in more detail below.

[0061] The target eNB 506 may receive the handover request over the

X2 interface. Note that after reception of the handover request, the handover request (as the other transmissions disclosed herein) may be decoded. In response to decoding of the handover request, the target eNB 506 may undertake several actions. A first of these actions is indicated at operation 2, in which the target eNB 506 may send a WT 508 addition request to the WT 508. The addition request may indicate that the target eNB 506 is to be associated with the UE 502, and thus contain UE identification (ID) information in addition to the target eNB 506 ID information.

[0062] The WT 508 may determine that handover of the UE 502 from the source eNB 504 to the target eNB 506 is to occur (or has already occurred, depending on the embodiment) from reception of the WT addition request In response to decoding of the addition request, the WT S08 may determine that the source eNB 504 is already associated with the UE 502. Even though the source eNB 504 and the UE 502 are already associated, the WT 508 may at this point add the association between target eNB 506 and the UE 502 without eliminating the association of die UE 502 with the source eNB 504.

[0063] After adding the new association, the WT 508 may at operation 3 reply to the target eNB 506 with a WT addition request acknowledgement (ACK). In some embodiments, the WT 508 may continue to deliver to the UE 502 packets received from both the source eNB 504 and target eNB 506 until a predetermined event occurs. In other embodiments, after adding the new association the WT 508 may store packets addressed to the UE 502 and received from bom the source eNB 504 and target eNB 506 until the predetermined event occurs.

[0064] The predetermined event may be, in some embodiments, reception of a particular packet The particular packet may be the last packet encrypted by the source eNB key or the first packet encrypted by the target eNB key. The WT 508 may receive from the source eNB 504, target eNB 506 or UE 502 an indication of a packet containing an LWA end-marker that indicates a sequence number (SN) or COUNT of the last packet encrypted by the source eNB key or the first packet encrypted by the target eNB key. In some embodiments, the WT 508 may discard all stored packets from the source eNB 504 that do not meet the criteria indicated (e.g., having a SN number or COUNT greater than that indicated by the LWA end-marker) and transmit packets from the target eNB 506 having a SN number or COUNT greater man that indicated by the LWA end-marker. If stored packets from the source eNB 504 meet the criteria indicated, in some embodiments the WT 508 may transmit the stored packets from the source eNB 504. In some other embodiments, packets from the source eNB 504 that arrive after the packet with the LWA end-marker has been received may simply be discarded, while the packets from the target eNB 504 mat arrive after the packet with the LWA end-marker has been received may be stored until a notification that handover is complete is delivered to the WT 518, at which point the stored packets from the target eNB 504 may be delivered to the UE 502.

[0065] Turning back to the handover operations, the target eNB 506 may respond to reception of the WT addition request ACK from the WT 508 with further communication to the source eNB 504. As shown in FIG. 5, the target eNB 506 may transmit at operation 4 to the source eNB 504 an

acknowledgement to the handover request from the source eNB 504. The handover request ACK may include the forwarding address of the target eNB 506.

[0066] The source eNB 504 may then send allocation and

reconfiguration information to me UE 502 and instruct the UE 502 to perform handover to the target eNB 506. The allocation and reconfiguration information and handover instruction may be sent at operation 5 via a handover command. In some embodiments, the reconfiguration information may be sent in a RRC Connection Reconfiguration message mat may include the handover command (e.g., MobilityControlInfo) and the LWA configuration. The reconfiguration information may include security information of the target eNB 506 (target key). In some embodiments, the source eNB 504 may initiate handover without use of a random access channel (RACH) procedure (e.g., the UE may use a preamble allocated by the source eNB 504). The source eNB 504 may also send a SN transfer message to the target eNB 506 to convey uplink/downlink PDCP SN receiver/transmitter status of at least some radio access bearers associated with the UE 502. The source eNB 504 may also start forwarding data for the UE 502 to the target eNB 506.

[0067] After reception of the RRCConnectionReconfiguration message, the UE 502 may initiate handover. The UE 502 may subsequently detach from the source eNB 504 and attach to the target eNB 506 at operation 6. In some embodiments, the attachment of the UE 502 to the target eNB 506 may involve a RACH procedure. The operations taken by the UE 502 at operation 6 may include synchronization to the target eNB 506. The UE 502 may start using the LWA configuration, including the target eNB key provided in the

RRCCoTmectionReconfigurati on message. The UE 502 may perform WLAN association if the WLAN has changed. In some embodiments, the UE 502 may continue to use the source eNB key during handover until completion of the handover.

[0068] The target eNB 506 may, upon receiving synchronization information from the UE 502, subsequently transmit allocation and timing information to the UE 502. The UE 502 may at operation 7 transmit to the target eNB 506 confirmation that the reconfiguration is complete. The UE S02 may send the confirmation in a RRCConnectionReconfigurationComplete message prior to the UE 502 sending data to the target eNB 506.

[0069] Once the target eNB 506 determines mat the UE S02 is able to communicate, the target eNB 506 may transmit a message to the MME (not shown in FIG. 5) to indicate that the eNB serving the UE 502 has changed. The MME may in response send an update request to the serving gateway to update the user plane, which the serving gateway may use to switch the downlink path from the source eNB 504 to the target eNB 506. The MME may subsequently confirm the update to the target eNB 506 in a response to the switch message, which men may confirm this information with the source eNB 504 through a UE 502 context release message. The source eNB 504 may then release user and control plane related resources associated to theUE 502 context

[0070] The WT 508, in the meantime, may at operation 8 send a WT association confirmation message to the target eNB 506. The WT association confirmation message may indicate to the target eNB 506 that the link between the WT 508 and the target eNB 506 has been established

[0071] At operation 9, the UE 502 may transmit a

WLANConnectionStatus Report to the target eNB 506. This report may provide feedback or flow information to the target eNB 506 related to the WLAN status and operation. The WL ANCormecti on Status Report may include information related to WLAN connection failure or success. When the UE 502 is unable to establish or continue LWA operation, the UE 502 may send to the target eNB 506 a WLANConnectionStatusReport message that indicates a WLAN connection failure. Upon WLAN connection failure, RRC Connection Re- establishment may not be triggered and data reception on WLAN may be suspended. When the UE 502 successfully connects to the WT 508, the UE 502 may send to the target eNB 506, if configured by the target eNB 506, a

WLANConnectionStatusReport message that indicates a WLAN connection failure. In some embodiments, such as when the WT is unchanged, use of operations 8 and 9 may be avoided.

[0072] As above, the handover request message may be sent by the source eNB to the target eNB to request the preparation of resources for a handover. As above, the handover request of operation 1 may include a LWA container information element (IE) as well as information of the WT 508. An example of a handover request in FIG. 5 is provided below, with the IES listed. The handover request may be sent by the source eNB 504 to the target eNB 506 to request the preparation of resources for a handover. The presence may indicate whether the WLAN or WT EE is mandatory (M) or optional (O) in the handover request. If an IE/EE group is not included in a received message and the presence of the IE/IE group is mandatory, an abstract syntax error may occur due to a missing EE/IE group. The Range information may indicate the allowed number of copies of repetitive EEs/EE groups. The Criticality information may instruct the target eNB that the Assigned Criticality information of the particular IE is to be applied. The Assigned Criticality information may instruct the target eNB how to act when receiving an EE or an EE group that is not comprehended (e.g., unsupported), and may be used in case of the missing IE/EE group abstract syntax error. When the Criticality information indicates that the associated EE is critical, the Assigned Criticality information may indicate whether the target eNB is to reject the EE or ignore the IE (and if so, whether to notify the sender that the EE has been ignored). If a message is received with a. Procedure Code IE marked with "Reject IE" which the receiving node does not comprehend, the receiving node may reject the procedure using an Error Indication procedure defined in 3GPP TS 36.413; if a message is received with & Procedure Code IE marked with "Ignore IE" which the receiving node does not comprehend, the receiving node may ignore the procedure. If rejection is indicated for non- procedure code IEs, the LWA procedure may be rejected or terminated and the rejection reported using a message normally used to report unsuccessful outcome of the procedure, e.g., in a Handover Preparation Failure message.

[0073] As indicated by the handover request, the LWA container EE is optional and may be ignored if unable to be comprehended by the target eNB. The remainder of the EEs associated with the WT, if the Criticality is YES, may be rejected if unsupported, regardless of whether the EE is mandatory or optional. The LWA container EE may include information of the WT associated with the UE. The eNB UE XwAP ID IE may uniquely identify a particular UE over the Xw interface associated with an eNB. The UE Identity may provide the identity of the UE as used by the network. The UE ID length may be dependent on network characteristics, e.g., IPv4 or IPv6. The WLAN security information IE may provide security information to be used by the target eNB to connect with the WLAN, e.g., to ensure that the WLAN is a trusted source. The WLAN security information EE may include WLAN Extensible Authentication Protocol/ Authentication and Key Agreement (EAP/AKA), Wi-Fi Passpoint or Optimized WLAN authentication to be used. As shown, in some embodiments, the WLAN security information EE may be the sole optional EE in the LWA Container IE. However, if present, the WLAN security information IE

[0074] The E-UTRAN Radio Access Bearer (E-RAB) to be added IE may indicated to the target eNB the number of bearers to be added to communicate with the TJE through the WLAN. As shown, in some

embodiments, only a single bearer may be added by the target eNB to accommodate the WT connection. The E-RAB ED may indicate the ED of each E-RAB to be added. The E-RAB level QoS parameters EE may indicate the maximum and guaranteed bit rates of the WLAN E-RABs identified by the E- RAB ID for downlink and uplink. The E-RAB level QoS parameters IE may include the QoS Class Identifier (QCI), Allocation and Retention Priority GBR (the relative importance compared to other E-RABs for allocation and retention of the E-UTRAN Radio Access Bearer, which may include the Priority Level, the Pre-emption Capability, and the Pre-emption Vulnerability) and QoS Information (the maximum and guaranteed bit rates of a GBR E-RAB for downlink). The eNB GTP Tunnel Endpoint IE may identify the Xw transport bearer associated to an E-RAB. The tunnel endpoint may be identified by the Transport Layer Address (the EP address to be used for the Xw user plane transport) and a GTP Tunnel Endpoint Identifier (used for the user plane transport between the eNB and the WT).

[0075] The Mobility Set IE may indicate the WLAN identifiers within which the UE can move without notifying the network. In some embodiments, this may include all APs within the WLAN Mobility Set connected to the same eNB, while in other embodiments fewer than all APs may be within the WLAN Mobility Set (e.g., APs with a higher security level than the UE). The WLAN Mobility Set IE may contain at least one of the BSSED, the SSID, and/or the HESSID IEs of the WLAN. The WT ID IE may be used to identify a WT and may include type 1 and 2 IDs.

Handover Request

[0076] The EEs in the handover request of some embodiments are indicated below:

[0077] As indicated by the ellipses in the above Handover Request IEs, other IEs may be present so that the Handover Request IEs are similar to those indicated in the Handover Request IEs in 3GPP TS 36.413, 3GPP TS 36.423 and 3GPP TS 36.463. Ellipses may also be used in other messages as indicated herein for similar reasons. An example of the container indicated in the handover request IE is provided below.

[0078] Various embodiments of the WT addition request message, sent by the target eNB to the WT to request the preparation of resources for LTE- WLAN aggregation for a specific UE, are provided below. In some embodiments, the WT addition request message specified in TS 36.463 may be reused, with one or more additional IEs used to indicated handover without a WT change. In particular as shown below, the Assigned Criticality of the WT- UE-XwAP ID IE may be adjusted from reject to ignore as an indicator for handover without WT change. The WT UE XwAP ID may be allocated by the WT and uniquely identify a UE over the Xw interlace. The handover-wo- wtchange IE may be an optional IE that may also be used to indicate handover without WT change. The Assigned Criticality of the handover-wo- wtchange IE may be reject, thereby replacing the Assigned Criticality of the WT UE XwAP ID. This may permit the WT to distinguish the new WT addition request message from a standard WT addition request message, as well as determine the UE to be banded over from the source eNB to the target eNB.

[0079] In another embodiment in which the WT addition request message specified in 3GPP TS 36.463 is again reused may use a different indicator to indicate handover without WT change. The id-ENB-UE-XwAP-ID IE may represent the target eNB-UE identity and may be assigned by the target eNB. The WT, in this case, may search for the UE and update the information accordingly. The WT addition request as indicated in section of 9.1.14 of 3 GPP TS 36.463 may be modified to provide an optional handover indicator as shown below:

[0080] The WT Addition Request IEs may be:

[0081] The WT Addition Request IEs may, as above, contain an optional

IE handover-wo-wtchange IE used to indicate handover without WT change. In some embodiments, the handover-wo-wtchange IE may be defined to be a Boolean value - taking a value of 1 , for example, to indicate that the UE to be associated with a target eNB is already associated with the source eNB.

[0082] Alternatively, a new Handover Without Change message may be used for handover without WT change. One embodiment of the new Handover Without Change message may contain the IEs below:

[0083] The new Handover Without Change IEs may differ in a number of ways from the WT Addition Request IEs. In the Handover Without Change IEs embodiment shown, the mandatory id-E-RABs-ToBeAdded-List IE normally found in the WT Addition Request IEs may be replaced with multiple optional E-RAB IEs: id-E-RABs-Aclmitted-ToBeAdded-ModAckList, id-E- RABs-Admitted-ToBeModified-ModAckList, and id-E-RABs-Admitted- ToBeReleased-ModAckList as at least one E-RAB may already be present In addition, the Assigned Criticality of the E-RAB IEs in the Handover Without Change IEs may be ignore, rather than reject (as the E-RAB IE of the WT Addition Request IEs) due to the existence of the E-RABs between the WT and the UE prior to the handover. Each list of E-RABs in the E-RAB IEs is thus related to changes in communications between the WT and the UE, including not only the creation of one or more additional E-RABs, but the modification and/or deletion of existing E-RABs. [0084] In some embodiments, the handover request ACK message may contain the LWA information and forwarding address from the target eNB. The handover request acknowledge message may support an E-RAB admitted list and not admitted list One embodiment of the handover request ACK message is provided below:

[0085] In some embodiments, the handover request ACK message may remain unchanged from the current 3 GPP standard handover request ACK message found in TS 36.423. The existing handover request ACK message may be able to support both an E-RABs admitted list and not admitted list.

[0086] As is known, uplink data is encrypted and downlink data is decrypted using a key associated with the serving eNB. The serving eNB changes from the source eNB to the target eNB during handover, which may not present a problem with direct communications. However, encryption and decryption of the data when using the WT may be problematic due to the timing of use of the key. The key update at the UE and the WT may occur immediately when the RRCConnectionReconfiguration message containing the target eNB key is received, or may be delayed until after the handover is completed. Thus, in some embodiments, the UE may remain associated with the WLAN whether inter or intra-eNB handover occurs. The UE and the WT may continue using the old keys, until the new key is sent by the target eNB. Once the new key is received, the reception may, in turn, trigger re-association.

[0087] Exemples

[0088] Example 1 is an apparatus of a target evolved NodeB (eNB), the apparatus comprising: a plurality of interfaces over which the target eNB communicates with a source eNB, a user equipment (UE), and a wireless local area network (WLAN) termination (WT); and processing circuitry in communication with the interfaces and arranged to: decode, from the source eNB, a handover request, the handover request comprising a Long Term

Evolution (LTE)/WiFi aggregation (LWA) container information element (IE) group; and in response to decoding of the handover request: encode, for transmission to the source eNB, a handover request acknowledgement (ACK); and encode, for transmission to the WT, a WT addition request for association of the target eNB with the UE.

[0089] In Example 2, the subject matter of Example 1 optionally includes wherein: the WT addition request comprises an indication of handover of the UE without a WT change.

[0090] In Example 3, the subject matter of Example 2 optionally includes wherein: the WT addition request comprises a handover without WT change (handover-wo-wtchange) IE having Assigned Criticality information of reject, the handover-wo-wtchange IE configured to indicate the handover of the UE without a WT change, and the processing circuitry is further configured to optionally include the handover-wo-wtchange IE in a Radio Resource Control (RRC) message.

[0091] In Example 4, the subject matter of any one or more of Examples

2-3 optionally include wherein: the WT addition request comprises a

WTAddiuonRequestlEs group, the WTAdditionRequestlEs group comprising an id-WT-UE-XwAP-ID IE, the id-WT-UE-XwAP-lD ΓΕ configured to indicate a handover without a WT change and to distinguish the WT addition request from a WT addition with a WT change. [0092] In Example 5, the subject matter of Example 4 optionally includes wherein: Assigned Criticaliry information of the WT-UE-XwAP-TD IE is ignore.

[0093] In Example 6, the subject matter of any one or more of Examples 4-5 optionally include wherein: the WT-UE-XwAP-ID IE comprises an ID handover-wo-wtchange IE having Assigned Criticality information of reject, and the processing circuitry is further configured to optionally include the WT-UE- XwAP-ID IE in a RRC message.

[0094] In Example 7, the subject matter of any one or more of Examples 2-6 optionally include wherein: the WT addition request comprises a handoverWOWTChangeRequestlEs group, the

handoverWOWTChangeRequestlE group comprising an optional evolved UTRAN (E-UTRAN) Radio Access Bearer (E-RAB) IE related to an E-RAB between the WT and the UE.

[0095] In Example 8, the subject matter of Example 7 optionally includes wherein: the optional E-RAB IE comprises at least one of an E-RABs- Admitted-ToBeAdded-ModAckList IE, an E-RABs-Admitted-ToBeModified- ModAckList IE, or an E-RABs-Admitted-ToBeReleased-ModAckList IE.

[0096] In Example 9, the subject matter of Example 8 optionally includes wherein: the optional E-RAB IE comprises the E-RABs-Admitted- ToBeAdded-ModAckList IE, the E-RABs-Adraitted-ToBeModified- ModAckList IE, and the E-RABs-Adntitted-ToBeReleased-ModAckList IE.

[0097] In Example 10, the subject matter of any one or more of

Examples 8-9 optionally include wherein: the E-RABs-Admitted- ToBeModified-ModAckList IE indicates an E-RAB between the UE and WT that is to be maintained during handover from the source eNB to the target eNB.

[0098] In Example 11, the subject matter of any one or more of

Examples 1-10 optionally include wherein: the WT addition request comprises an identity of the UE.

[0099] In Example 12, the subject matter of any one or more of

Examples 1-11 optionally include wherein: the LW A container comprises a LWAContainer IE group mat contains information for handover without a WT change, including an identity of the WT. [00100] In Example 13, the subject matter of any one or more of

Examples 1-12 optionally include wherein: the handover request ACK comprises identical information elements (lEs) as a handover request ACK in response to a conventional handover.

[00101] In Example 14, the subject matter of any one or more of

Examples 1-13 optionally include wherein: the handover request indicates Random Access CHannel (RACH)-less handover for die UE.

[00102] In Example IS, the subject matter of any one or more of

Examples 1-14 optionally include wherein: the processing circuitry comprises a baseband processor, and the apparatus further comprises a transceiver configured to communicate with at least one of the target eNB or the WT via one of the interfaces.

[00103] Example 16 is an apparatus of a wireless local area network (WLAN) termination (WT), the apparatus comprising: a plurality of interfaces over which the WT communicates with a target eNB and a user equipment (UE); and processing circuitry in communication with the interfaces and arranged to: decode, from the target eNB, a WT addition request for association of the target eNB with the UE, the WT addition request comprises an indication of handover of the UE without a WT change; and after decoding of the handover request, in response to decoding of the LWA container, encode for transmission to the target eNB, a WT addition request acknowledgement (ACK).

[00104] In Example 17, the subject matter of Example 16 optionally includes wherein: the WT addition request comprises a handover-wo-wtchange information element (IE) having Assigned Criticality information of reject, the handover-wo-wtchange IE configured to indicate the handover of the UE without a WT change.

[00105] In Example 18, the subject matter of any one or more of

Examples 16-17 optionally include wherein: the WT addition request comprises a WTAdditionRequestlEs group, the WTAddiuonRequesHEs group comprising an id-WT-UE-XwAP-ID information element (IE), the id-WT-UE-XwAP-ID IE configured to indicate a handover without a WT change and to distinguish the WT addition request from a WT addition with a WT change. [00106] In Example 19, the subject matter of Example 18 optionally includes wherein: Assigned Criticality information of the WT-UE-XwAP-TD IE is ignore.

[00107] In Example 20, the subject matter of any one or more of

Examples 18-19 optionally include wherein: the WT-UE-XwAP-ID IE comprises an ID handover-wo-wtchange IE having Assigned Criticality information of reject

[00108] In Example 21, the subject matter of any one or more of

Examples 16-20 optionally include wherein: the WT addition request comprises a hand o verWO WTChangeRequestEEs group, the

handoverWOWTChangeRequestlE group comprising an optional evolved UTRAN (E-UTRAN) Radio Access Bearer (E-RAB) information element (IE) rel ated to an E-RAB between the WT and the UE.

[00109] In Example 22, the subject matter of Example 21 optionally includes wherein: the optional E-RAB IE comprises at least one of an E-RABs- Admitted-ToBeAdded-ModAckList IE, an E-RABs-Admitted-ToBeModified- ModAckList IE, or an E-RABs-Adnri tted-ToBeRel eased-ModAckList IE.

[00110] In Example 23, the subject matter of Example 22 optionally includes wherein: the optional E-RAB IE comprises the E-RABs-Admitted- ToBeAdded-ModAckList IE, the E-RABs-Admitted-ToBeModified-

ModAckList IE, and me E-RABs-Admitted-ToBeReleased-ModAckList IE.

[00111] In Example 24, the subject matter of any one or more of

Examples 22-23 optionally include wherein: the E-RABs-Admitted- ToBeModified-ModAckList IE indicates an E-RAB between the UE and WT that is to be maintained during handover from the source eNB to the target eNB.

[00112] In Example 25, the subject matter of any one or more of

Examples 16-24 optionally include wherein: the WT addition request comprises an identity of the UE.

[00113] In Example 26, the subject matter of any one or more of

Examples 16-25 optionally include wherein: the processing circuitry is further configured to transmit a WT association confirmation message after completion of handover of the UE from a source eNB to the target eNB, the WT association confirmation message configured to indicate to the target eNB mat a link between the WT and the target eNB has been established.

[00114] Example 27 is a computer-readable storage medium that stores instructions for execution by one or more processors, the one or more processors of a target evolved NodeB (eNB) to: decode a handover request from a source eNB, the handover request comprising a Long Term Evolution (LTE)/WiFi aggregation (LWA) container information element (IE) group; and in response to decoding of the LWA container, transmit to the WT a WT addition request for association of the target eNB with the UE, the WT addition request comprising an indication of handover of the UE without a WT change.

[00115] In Example 28, the subject matter of Example 27 optionally includes wherein one of: the WT addition request comprises ahandover-wo- wtchange IE having Assigned Criticality information of reject and whose presence is optional, the handov er-wo-wtchange EE configured to indicate the handover of the UE without a WT change, the WT addition request comprises a WTAdditionRequestTEs group, the WTAddi uonRequestlEs group comprising an id-WT-UE-XwAP-ID IE, the id-WT-UE-XwAP-ID IE configured to indicate a handover without a WT change and to distinguish the WT addition request from a WT addition with a WT change, or the WT addition request comprises a handoverWOWTChangeRequestEEs group, the

[00116] In Example 29, the subject matter of Example 28 optionally includes wherein: Assigned Criticality information of the WT-UE-XwAP-ID IE is ignore and the WT-UE-XwAP- ID IE comprises an CD handover-wo-wtchange IE having Assigned Criticality information of reject

[00117] In Example 30, the subject matter of any one or more of

Examples 28-29 optionally include wherein: the WT addition request comprises a handoverWOWTChangeRequestlEs group, the

handoverWOWTChangeRequestlE group comprising an optional evolved UTRAN (E-UTRAN) Radio Access Bearer (E-RAB) IE related to an E-RAB between the WT and the UE, and the optional E-RAB IE comprises at least one of an E-RABs-Admitted-ToBeAdded-ModAckList IE, an E-RABs-Admitted- ToBeModified-ModAckList IE, or an E-RABs-Admitted-ToBeReleased- ModAckList IE, and the E-RABs-Admitted-ToBeModified-ModAckLi st IE indicates an E-RAB between the UE and WT that is to be maintained during handover from the source eNB to the target eNB.

[00118] Example 31 is a method of providing handover by a target evolved NodeB (eNB), the method comprising: decoding a handover request from a source eNB, the handover request comprising a Long Term Evolution (LTEyWiFi aggregation (LWA) container information element (IE) group; and in response to decoding of the LWA container, transrmtting to the WT aWT addition request for association of the target eNB with the UE, the WT addition request comprising an indication of handover of the UE without a WT change.

[00119] In Example 32, the subject matter of Example 31 optionally includes wherein one of: the WT addition request comprises a handover- wo- wtchange IE having Assigned Criticality information of reject and whose presence is optional, the handover-wo- wtchange IE configured to indicate the handover of the UE without a WT change, the WT addition request comprises a WTAdditionRequestlEs group, the WTAdditionRequestlEs group comprising an id-WT-UE-XwAP-ID IE, the id-WT-UE-X wAP-ID IE configured to indicate a handover without a WT change and to distinguish the WT addition request from a WT addition with a WT change, or the WT addition request comprises a handoverWOWTChangeRequestEEs group, the

[00120] In Example 33, the subject matter of any one or more of

Examples 31-32 optionally include wherein: Assigned Criticality information of the WT-UE-XwAP-ID IE is ignore and the WT-UE-XwAP-ID IE comprises an ID handover-wo- wtchange IE having Assigned Criticality information of reject

[00121] In Example 34, the subject matter of any one or more of

Examples 31-33 optionally include wherein: the WT addition request comprises a handoverWOWTChangeRequestlEs group, the

handoverWOWTChangeRequestlE group comprising an optional evolved UTRAN (E-UTRAN) Radio Access Bearer (E-RAB) IE related to an E-RAB between the WT and the UE, and die optional E-RAB IE comprises at least one of an E-RABs-Admitted-ToBeAdded-ModAckList IE, an E-RABs-Admitted- ToBeModified-ModAckList IE, or an E-RABs-Admitted-ToBeReleased- ModAckList IE, and the E-RABs-Admitted-ToBeModified-ModAckList IE indicates an E-RAB between Ihe UE and WT that is to be maintained during handover from the source eNB to the target eNB.

[00122] Example 35 is an apparatus of a target evolved NodeB (eNB), the apparatus comprising: means for decoding a handover request from a source eNB, the handover request comprising a Long Term Evolution (LTE)/WiFi aggregation (LWA) container information element (IE) group; and in response to decoding of the LWA container, means for transmitting to the WT a WT addition request for association of the target eNB with the UE, the WT addition request comprising an indication of handover of the UE without a WT change.

[00123] In Example 36, the subject matter of Example 35 optionally includes wherein one of: the WT addition request comprises a handover-wo- wtchange IE having Assigned Criticality information of reject and whose presence is optional, the handover-wo-wtchange EE configured to indicate the handover of the UE without a WT change, ihe WT addition request comprises a WTAdditi onRequestlEs group, (he WTAdditionRequestlEs group comprising an id-WT-UE-XwAP-ID IE, the id-WT-UE-XwAP-lD IE configured to indicate a handover without a WT change and to distinguish the WT addition request from a WT addition with a WT change, or the WT addition request comprises a handoverWOWTChangeRequestlEs group, the

handoverWOWTChangeRequestEE group comprising an optional evolved UTRAN (E-UTRAN) Radio Access Bearer (E-RAB) IE related to an E-RAB between the WT and the UE.

[00124] In Example 37, the subject matter of any one or more of

Examples 35-36 optionally include wherein: Assigned Criticality information of the WT-UE-XwAP-ID IE is ignore and the WT-UE-XwAP-ID IE comprises an ID handov er- wo-wtchange IE having Assigned Criticality information of reject

[00125] In Example 38, the subject matter of any one or more of

Examples 35-37 optionally include wherein: the WT addition request comprises a handover WO WTChangeRequestEEs group, the

handoverWOWTChangeRequestlE group comprising an optional evolved UTRAN (E-UTRAN) Radio Access Bearer (E-RAB) IE related to an E-RAB between the WT and the UE, and the optional E-RAB IE comprises at least one of an E-RABs-Admitted-ToBeAdded-ModAckList IE, an E-RABs-Admitted- ToBeModified-ModAckList IE, or an E-RABs-Admitted-ToBeReleased- ModAckList IE, and the E-RABs-Admitted-ToBeModified-ModAckList IE indicates an E-RAB between the UE and WT that is to be maintained during handover from the source eNB to the target eNB.

[00126] Although an embodiment has been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader scope of the present disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The

accompanying drawings that form a part hereof show, by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced The ernbodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.

[00127] The subject matter may be referred to herein, individually and/or collectively, by the term "embodiment" merely for convenience and without intending to voluntarily limit the scope of this application to any single inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodimaits, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description.

[00128] In this document, the terms "a" or "a" are used, as is common in patent documents, to include one or more than one, independent of any other instances or usages of "at least one" or "one or more." In this document, the term "or" is used to refer to a nonexclusive or, such that "A or B" includes "A but not B," "B but not A," and "A and B," unless otherwise indicated. In this document, the terms "including" and "in which" are used as the plain-English equivalents of the respective terms "comprising" and "wherein." Also, in the following claims, the terms "including" and "comprising" are open-ended, that is, a system, UE, article, composition, formulation, or process mat includes elements in addition to those listed after such a term in a claim are still deemed to fall within the scope of that claim Moreover, in the following claims, the terms "first," "second," and "third," etc. are used merely as labels, and are not intended to impose numerical requirements on their objects.

[00129] The Abstract of the Disclosure is provided to comply with 37 C.F.R. §1.72(b), requiring an abstract that will allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen mat various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention mat the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subj ect matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment

Claims

What is claimed is:

1. An apparatus of a target evolved NodeB (eNB), the apparatus comprising:

a plurality of interfaces over which the target eNB communicates with a source eNB, a user equipment (UE), and a wireless local area network (WLAN) termination (WT); and

processing circuitry in communication with the interfaces and arranged to:

decode, from the source eNB, a handover request, the handover request comprising a Long Term Evolution (LTE)AViFi aggregation (LWA) container information element (IE) group; and

in response to decoding of the handover request:

encode, for transmission to the source eNB, a handover request acknowledgement (ACK); and

encode, for transmission to the WT, a WT addition request for association of the target eNB with the UE. 2. The apparatus of claim 1, wherein:

the WT addition request comprises an indication of handover of the UE without a WT change.

3. The apparatus of claim 2, wherein:

the WT addition request comprises a handover without WT change

(handover-wo-wtchange) IE having Assigned Criticality information of reject, the handover-wo-wtchange IE configured to indicate the handover of the UE without a WT change, and

the processing circuitry is further configured to optionally include the handover-wo-wtchange IE in a Radio Resource Control (RRC) message.

4. The apparatus of claim 2, wherein: the WT addition request comprises a WTAdditionRequestlEs group, the WTAdditionRequestlEs group comprising an id-WT-UE-XwAP-ID IE, Hie id- WT-UE-XwAP-ID IE configured to indicate a handover without a WT change and to distinguish the WT addition request from a WT addition with a WT change.

5. The apparatus of claim 4, wherein:

Assigned Criticality information of the WT-UE-XwAP-ID IE is ignore. 6. The apparatus of claim 4, wherein:

the WT-UE-XwAP-ID IE comprises an ID handover-wo-wtchange IE having Assigned Criticality information of reject, and

the processing circuitry is further configured to optionally include the WT-UE-XwAP-ID IE in a RRC message.

7. The apparatus of claim 2, wherein:

the WT addition request comprises ahandoverWOWTChangeRequestlEs group, the handoverWOWTChangeRequestlE group comprising an optional evolved UTRAN (E-UTRAN) Radio Access Bearer (E-RAB) IE related to an E- RAB between the WT and the UE.

8. The apparatus of claim 7, wherein:

the optional E-RAB IE comprises at least one of an E-RABs-Admitted- ToBeAdded-ModAckList IE, an E-RABs-Admitted-ToBeModified-ModAckList IE, or an E-RABs-Admitted-ToBeReleased-ModAckList IE.

9. The apparatus of claim 8, wherein:

the optional E-RAB IE comprises the E-RABs-Adimtted-ToBeAdded- ModAckList IE, the E-RABs-Admitted-ToBeModified-ModAckList IE, and the E-RABs-Admitted-ToBeReleased-ModAckList IE.

The apparatus of claim 8, wherein: the E-RABs-Admitted-ToBeModified-ModAckList IE indicates an E- RAB between die UE and WT that is to be maintained during handover from the source eNB to the target eNB. 11. The apparatus of any one or more of claims 1-10, wherein:

the WT addition request comprises an identity of the UE.

12. The apparatus of any one or more of claims 1-10, wherein:

the LWA container comprises a LWAContainer IE group that contains information for handover without a WT change, including an identity of the WT.

13. The apparatus of any one or more of claims 1-10, wherein:

the handover request ACK comprises identical information elements (lEs) as a handover request ACK in response to a conventional handover.

14. The apparatus of any one or more of claims 1-10, wherein:

the handover request indicates Random Access CHannel (RACH)-less handover for the UE. IS. The apparatus of any one or more of claims 1-10, wherein:

the processing circuitry comprises a baseband processor, and

the apparatus further comprises a transceiver configured to communicate with at least one of the target eNB or the WT via one of the interfaces. 16. An apparatus of a wireless local area network (WLAN) termination (WT), the apparatus comprising:

a plurality of interfaces over which the WT communicates with a target eNB and a user equipment (UE); and

processing circuitry in communication with the interfaces and arranged to:

decode, from the target eNB, a WT addition request for association of the target eNB with the UE, the WT addition request comprises an indication of handover of the UE without a WT change; and

after decoding of the handover request, in response to decoding of the LWA container, encode for transmission to the target eNB, a WT addition request acknowledgement (ACK).

17. The apparatus of claim 16, wherein:

the WT addition request comprises a handover-wo-wtchange information element (IE) having Assigned Criticaliry information of reject, the handover-wo- wtchange IE configured to indicate the handover of the UE without a WT change.

18. The apparatus of claim 16, wherein:

the WT addition request comprises a WTAdditionRequestlEs group, the WTAdditionRequestlEs group comprising an id-WT-UE-XwAP-ID information element (IE), the id-WT-UE-XwAP-ID IE configured to indicate a handover without a WT change and to distinguish the WT addition request from a WT addition with a WT change. 19. The apparatus of claim 18, wherein:

Assigned Criticaliry information of the WT-UE-XwAP-ID IE is ignore.

20. The apparatus of claim 18, wherein:

the WT- UE-X wAP-lD IE comprises an ID handover-wo-wtchange IE having Assigned Criticality information of rej ect

21. The apparatus of claim 16, wherein:

the WT addition request comprises a handoverWOWTChangeRequestlEs group, the handoverWOWTChangeRequestlE group comprising an optional evolved UTRAN (E-TJTRAN) Radio Access Bearer (E-RAB) information element (IE) related to an E-RAB between the WT and the UE.

22. The apparatus of claim 21, wherein: the optional E-RAB IE comprises at least one of an E-RABs-Admitted- ToBeAdded-ModAckList IE, an E-RABs-Admitted-ToBeModified-ModAckList IE, or an E-RABs-Adraitted-ToBeReleased-ModAckList IE. 23. The apparatus of claim 22, wherein:

the optional E-RAB IE comprises the E-RABs-Adimtted-ToBeAdded- ModAckList IE, the E-RABs- Admitted-ToBeModifi ed-ModAckList IE, and the E-RABs-Admitted-ToBeReleased-ModAckList IE. 24. The apparatus of claim 22, wherein:

the E-RABs-Admitted-ToBeModified-ModAckList IE indicates an E- RAB between the UE and WT that is to be maintained during handover from the source eNB to the target eNB. 25. The apparatus of any one or more of claims 16-24, wherein:

the WT addition request comprises an identity of the UE.

26. The apparatus of any one or more of claims 16-24, wherein:

the processing circuitry is further configured to transmit a WT association confirmation message after completion of handover of the UE from a source eNB to the target eNB, the WT association confirmation message configured to indicate to the target eNB that a link between the WT and the target eNB has been established. 27. A computer-readable storage medium that stores instructions for execution by one or more processors, the one or more processors of a target evolved NodeB (eNB) to:

decode a handover request from a source eNB, the handover request comprising a Long Term Evolution (LTE)/WiFi aggregation (LWA) container information element (IE) group; and

in response to decoding of the LWA container transmit to the WT a WT addition request for association of the target eNB with the UE, the WT addition request comprising an indication of handover of the UE without a WT change.

28. The medium of claim 27, wherein one of:

the WT addition request comprises a handover-wo-wtchange IE having Assigned Criticality information of reject and whose presence is optional, the handover-wo-wtchange IE configured to indicate the handover of the UE without a WT change,

the WT addition request comprises a WTAdditionRequestlEs group, the WTAdditionRequestlEs group comprising an id-WT-UE-XwAP-ID IE, the id- WT-UE-XwAP-TD IE configured to indicate a handover without a WT change and to distinguish the WT addition request from a WT addition with a WT change, or

the WT addition request comprises a

handoverWOWTChangeRequestEEs group, the

29. The medium of claim 28, wherein:

Assigned Criticality information of the WT-UE-XwAP-ID IE is ignore and

the WT-UE-XwAP-ID IE comprises an ID handover-wo-wtchange IE having Assigned Criticality information of reject.

30. The medium of claim 28, wherein:

the WT addition request comprises a nandoverWOWTChangeRequestlEs group, the handoverWOWTChangeRequestlE group comprising an optional evolved UTRAN (E-UTRAN) Radio Access Bearer (E-RAB) IE related to an E- RAB between the WT and the UE, and

the optional E-RAB IE comprises at least one of an E-RABs-Admitted- ToBeAdded-ModAckList IE, an E-RABs-Admitted-ToBeModified-ModAckList IE, or an E-RABs-Admitted-ToBeReleased-ModAckList IE, and the E-RABs- Admitted-ToBeModified-ModAckList IE indicates an E-RAB between the UE and WT that is to be maintained during handover from the source eNB to the target eNB.