WO2017171925A1

WO2017171925A1 - Maintaining a wifi connection during handover of a user equipment in a lte network

Info

Publication number: WO2017171925A1
Application number: PCT/US2016/054509
Authority: WO
Inventors: Shadi Iskander; Alexander Sirotkin; Jerome Parron
Original assignee: Intel IP Corporation
Priority date: 2016-03-31
Filing date: 2016-09-29
Publication date: 2017-10-05
Also published as: EP3437350A1

Abstract

Technology for a multi-connectivity system to provide for a handover mechanism is disclosed. The WiFi connection between a UE and WT can be maintained when the UE is handed over between a source and target eNB. The mechanism can include providing an indication to maintain a Pair-wise Master Key (PMK) of the source eNB during handover. The UE and WT accordingly use a new PMK for use with WiFi communications associated with the target eNB, and the maintained PMK for use with WiFi communications that are associated with the source eNB before the handover.

Description

MAINTAINING A WIFI CONNECTION DURING HANDOVER OF A USER EQUIPMENT IN A LTE NETWORK

BACKGROUND

[0001] In some wireless networks, user equipment (UE) can be capable of supporting multiple wireless technologies concurrently. UEs, for example, can include both Third Generation Partnership Project (3GPP) Long Term Evolved (LTE) and Institute of Electronics and Electrical Engineers (IEEE) 802.11 (WiFi) Radio Access Technologies (RAT) to allow communication over either LTE or WiFi, or both LTE and WiFi concurrently. UEs that support both LTE and WiFi communication can use the advantages of both RATs to increase the speed of communication while decreasing the cost and amount of power used to transfer data.

[0002] However, the WiFi connection between the UE and a Wireless local area network Termination (WT) is not maintained during LTE handovers when the UE moves between Evolved NodeBs (eNB) of the LTE network. In such case, the WiFi connection is terminated and then reconnected. However, terminating the WiFi connection and then reconnecting the WiFi connection during LTE handover can affect service quality and throughput. Accordingly, there is a continuing need for improved handover techniques.

BRIEF DESCRIPTION OF THE DRAWINGS

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

FIGS. 1A and IB depict a wireless multi-connectivity system in accordance with an example;

FIG. 2 depicts functionality of an Evolved NodeB (eNB), as a target of an eNB handover, to facilitate wireless multi-connectivity in accordance with an example; FIG. 3 depicts functionality of an Evolved NodeB (eNB), as a source of an eNB handover, to facilitate wireless multi-connectivity in accordance with an example; FIG. 4 depicts functionality of a User Equipment (UE) to facilitate wireless multi- connectivity in accordance with an example;

FIG. 5 depicts functionality of a Wireless local area network Termination (WT) to facilitate wireless multi-connectivity, in accordance with an example;

FIG. 6 illustrates signaling in a wireless multi-connectivity system in accordance with an example;

FIG. 7 depicts functionality of a UE to facilitate wireless multi-connectivity in accordance with another example;

FIG. 8 depicts functionality of a UE to facilitate wireless multi-connectivity in accordance with yet another example;

FIG. 9 illustrates a diagram of example components of a UE in accordance with an example;

FIG. 10 illustrates a diagram of example components of a UE in accordance with an example; and

FIG. 11 illustrates a diagram of an eNB and UE in accordance with an example.

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

DETAILED DESCRIPTION

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

DEFINITIONS [0006] As used herein, the term "User Equipment (UE)" refers to a computing device capable of wireless digital communication such as a smart phone, a tablet computing device, a laptop computer, a multimedia device such as a television or gaming system, or other type computing device that is configured to provide text, voice, data, or other types of digital communication over wireless communication. The term "User Equipment (UE)" can also be refer to as a "mobile device," "wireless device," of "wireless mobile device."

[0007] As used herein, the term "Wireless local area network Termination (WT)" refers to a device or configured node on a network that allows wireless capable devices and wired networks to connect through a wireless standard, including WiFi, Bluetooth, or other wireless communication protocol.

[0008] As used herein, the term "Evolved NodeB," "eNodeB," or "eNB," refers to a device or configured node of a mobile phone network that is configured to communicate wirelessly with UEs.

[0009] As used herein, the term "cellular telephone network: or "Long Term

Evolved (LTE)" refers to wireless broadband technology developed by the Third Generation Partnership Project (3GPP

[0010] As used herein, the term "WiFi" refers to wireless 802.11 protocol technology developed by the Institute of Electronics and Electrical Engineers (IEEE).

EXAMPLE EMBODIMENTS

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

[0012] In one aspect, wireless multi-connectivity enables User Equipment (UE) to send and receive data on two or more wireless networks. For example, the UE can be used to provide voice communications over a Third Generation Partnership Project (3 GPP) Long Term Evolved (LTE) network, while also sending and receiving text, pictures, video or other types of digital communication over an Institute of Electronics and Electrical Engineers (IEEE) 802.11 (WiFi) network using the same device. In addition, the bandwidth of two or more wireless networks can be aggregated to provide greater bandwidth to the UE. However, when the UE moves from a source Evolved NodeB (eNB) to a target eNB of the LTE network, the connection between the UE and the Wireless local area network Termination (WT) of the WiFi network is not maintained. Instead, after handover in the LTE network, the connection between the UE and the WT needs to be re-established. The re-establishment of the connection between the UE and the WT can be time consuming and use a considerable amount of network resources. In addition, the time period to re-establish a connection between the UE and the WT can affect the bandwidth of the UE. In some scenarios, the down time of the connection between the UE and the WT when an eNB handover occurs can cause a noticeable difference to an end user of the UE.

[0013] In one aspect, the present technology provides for maintaining the WiFi connection between the UE and WT when the UE is handed over between a source and target eNB. In one aspect, during handover an indication to maintain a Pair-wise Master Key (PMK) of the source eNB is provided. The UE and WT accordingly use the currently available PMK and avoid the UE re-associating with the WT.

[0014] FIGS. 1A and IB depict a wireless multi-connectivity system, in accordance with an example. In one aspect, the multi-connectivity system includes a plurality of eNBs 110, 115, one or more WTs 120, and one or more UEs 130. One or more LTE networks can communicatively couple eNBs to UEs, and one or more WiFi networks can communicatively couple WTs to UEs. In one instance, communications between the eNBs and the UEs can be transmitted using a higher layer communication, such as a Radio Resource Control (RRC) communication, a Master Information Block (MIB), a Secondary Information Block (SIB), a Packet Data Convergence Protocol (PDCP), or another desired type of higher layer communication. In one instance, communications between the WTs and UEs can be transmitted across one or more wireless communication links according to an IEEE 802.11 (WiFi) compliant protocol. WiFi compliant protocols include 802.11 (1997), 802.11a (199), 802.11b (1999), 802. l lg (2003), 802.11η (2009), 802.11ac (2013) and 802.11 ad (2012), or future compliant protocols such as 802.11 ax and 802.11 ay. One or more additional networks couple the eNBs to the one or more WTs, and one or more additional networks couple the eNBs to each other. In one instance, the eNBs 110, 115 can be coupled to WTs 120 by one or more wired communication links according to an Xw compliant protocol. In one instance, the eNBs can be coupled together by one or more wired communication links according to an X2 compliant protocol

[0015] In one instance, the eNBs and UEs may include one or more antennas, one or more 3GPP LTE radios to encode/modulate and/or decode/demodulate signals transmitted or received on an air interface, and one or more 3GPP LTE digital processors to process signals transmitted and received on the air interface. In one instance, the UEs and WT may include one or more antennas, one or more WiFi radios to modulate and/or demodulate signals transmitted or received on an air interface, and one or more WiFi digital processors to process signals transmitted and received on the air interface. In one instance, the WTs may each include one or more Access Points (AP). In one instance, the WT can be compliant with an LTE Wireless Aggregation Adaptation Protocol (LWAAP) mode of operation. In one instance, the UE can be a Wireless Node (WN). In one instance, the UEs may include one or more smart phones, tablet computing devices, laptop computers, internet of things (IOT) devices and/or other types of computing devices that provide digital communication including data and/or voice communication.

[0016] An eNB may be a relatively high power node, referred to as a "macro node" or a relatively low power node (LPN). An LPN can include a micro node, pico node, home eNB (HeNB), remote radio head (RRH), remote radio entity (RRE), and the like. The eNB can provide communication coverage for a particular geographic area. The term "cell" can refer to a coverage area of an eNB and/or an eNB subsystem serving this coverage area.

[0017] In one aspect, the LTE and WiFi radios of the UE can enable the UE to transmit and receive data over both an LTE link and a WiFi link. In one aspect, the multi-connectivity system provides for LTE WiFi Aggregation (LWA) (e.g. , mobile data offload or "Wi-Fi Offloading"). In LWA, data packets (e.g., packet data units "PDUs") can be served on LTE and Wi-Fi radio links. An advantage of LWA is that it can provide increased control and utilization of resources on both links (e.g. , LTE links and Wi-Fi radio links). LWA can be used to increase the aggregate throughput for all users and improve the total system capacity by better managing the radio resources among users. [0018] However, in accordance with the conventional art, new PMKs and new cipher keys are generated when the UE is handed over from a source eNB 110 to a target eNB 115. The PMKs are generated by the UE and WT based on two variables. One variable is configured by the network, the other is specific to the associated eNB. Therefore, when the UE is handed over from the source eNB to the target eNB, the PMKs change. One or more new PMKs and one or more new cipher keys are associated with the target eNB 115, while the one or more previous PMKs and one or more previous cipher keys were associated with the source eNB 110. The new cipher keys cannot be utilized with data packets from the source eNB 110 that are still in flight between the UE 130 and WT 120 after the handover is initiated.

[0019] In the multi -connectivity system of FIGS. 1A and IB, the UE 130 and WT 120 can maintain a first current PMK and a second current PMK. The UE uses the second current PMK, that was used with the source eNB, to maintain a connection with the WT and avoid the need for a new association with the WT.

[0020] FIG. 2 illustrates functionality of an eNB to facilitate wireless multi- connectivity as a target of an eNB handover, in accordance with an example. The functionality of the eNB includes a handover mechanism for concurrent use of an LTE service and a WiFi service. The handover mechanism of the eNB can be implemented by one or more processors and memory, wherein the memory stores one or more sets of instructions, that, when executed by the one or more processors, perform one or more functionalities including the handover mechanism. In one instance, the handover mechanism may be implemented by one or more processors and memory of an application circuitry, a baseband circuitry, and/or Radio Frequency (RF) circuitry of the eNB.

[0021] In one aspect, the functionality of the target eNB can include decoding a handover request received from a source eNB 210. The handover request can be received by the target eNB from the source eNB across an X2 protocol compliant interface. In one instance, the handover can be an intra-eNB handover. In another instance, the handover can be an inter-eNB handover.

[0022] In one aspect, the target eNB can encode, for transmission to a WT, a

WT addition request 220 in response to the handover request. The WT addition request can be transmitted by the target eNB to the WT across an Xw compliant protocol interface. The WT addition request can include an indication to the WT to maintain a first current Pair-wise Master Key (PMK) valid as a second current PMK. The PMK can be a symmetric key bound to the communication session between the given eNB and the UE.

[0023] In accordance with the WT addition request, the second current PMK that was used with the source eNB can be maintained by the WT for use with the target eNB. The source eNB will use the old, second current, PMK it was using on the source eNB for some time to maintain the connection with the WT. The new, first current, PMK generated by the target eNB can be kept to be used for later associations.

[0024] In one aspect, the target eNB can encode, for transmission to the source eNB, a handover acknowledgement 230. In one instance, the handover

acknowledgement includes WiFi configuration parameters. As will be explained further, the WiFi configuration parameters may optionally include an addition, modification or termination of an LWA configuration. The handover request acknowledgement can be received by the target eNB from the source eNB across an X2 protocol compliant interface.

[0025] The handover request and handover acknowledgement are part of handover preparation in accordance with the X2 protocol. Upon receipt of the handover request by the target eNB from the source eNB, if at least one of the requested bearers is admitted to the cell, the target eNB shall reserve necessary resources, and send the handover request acknowledgment message back to the source eNB. The target eNB shall include the bearers for which resources have been prepared at the target cell in the bearer Information Element (IE) of the handover request acknowledgement message that it accepts the proposed forwarding of downlink data for this bearer. For each bearer in the bearers admitted list IE, the target eNB may include the Uplink (UL) General packet radio service Tunneling Protocol (GTP) tunnel endpoint IE of the handover request acknowledgement message that it accepts the proposed forwarding of downlink data for this bearer. Upon reception of the handover request

acknowledgement message the source eNB shall terminate the handover preparation procedure. The source eNB is then defined to have prepared handover for the given X2 UE-associated signaling. [0026] In one aspect, the target eNB can decode a connection request from the UE 240. The connection request initiates a communication session between the target eNB and the UE. The connection request can be received the target eNB from the UE using a higher layer communication, such as a Radio Resource Control (RRC) communication, a Packet Data Convergence Protocol (PDCP), or another desired type of higher layer communication.

[0027] FIG. 3 illustrates functionality of an eNB to facilitate wireless multi- connectivity as a source of an eNB handover, in accordance with an example. The functionality of the eNB includes a handover mechanism for concurrent use of an LTE service and a WiFi service. The handover mechanism of the eNB can be implemented by one or more processors and memory, wherein the memory stores one or more sets of instructions that when executed by the one or more processors perform one or more functionalities including the handover mechanism. In one instance, the handover mechanism may be implemented by one or more processors and memory of an application circuitry, a baseband circuitry, and/or Radio Frequency (RF) circuitry of the eNB.

[0028] In one aspect, the functionality of the source eNB can include encoding a handover request for transmitting to a target eNB 310. The handover request can be encoded for transmission by the source eNB to the source eNB across an X2 protocol compliant interface. In one instance, the handover can be an intra-eNB handover. In another instance, the handover can be an inter-eNB handover.

[0029] In one aspect, the source eNB can decode from the target eNB a handover acknowledgement 320. In one aspect, the handover acknowledgement can include one or more WiFi configuration parameters in a transparent container. In one instance, the WiFi configuration parameters include one or more parameters concerning the WiFi connection between the UE and the WT. The one or more WiFi configuration parameters for example can include one or more modified mobility set configurations and one or more LWA setup configurations for the WT addition request. The one or more WiFi configuration parameters transmitted by the target eNB to the source eNB allows the UE to synchronize to the target eNB and start associating to the WT and apply the one or more WiFi configuration parameters. In one instance, the WiFi configuration parameter are generated by the target eNB to add a new WT or change the configuration of the WT during the handover.

[0030] In one aspect, the source eNB can encode, for transmission to the UE, a connection reconfiguration message 330. The connection reconfiguration message can include an indication to maintain a first current PMK valid for use as a second current PMK. In one instance, the connection reconfiguration message therefore provides an indication to maintain the current PMK associated with the source eNB as a valid PMK for use after initiation of the handover request. The UE uses the second current PMK, that was used with the source eNB, to maintain a connection with the UT and avoid the need for a new association with the WT.

[0031] In one aspect, the source eNB encodes, for transmission to the UE, WiFi configuration parameters 340. The WiFi parameters can include one or more modified mobility set configurations and one or more LWA setup configurations for WT addition. The WiFi parameters can be received from the target eNB in the handover request acknowledgement, as described above.

[0032] In one instance the WiFi configuration parameters can enable an LWA configuration to be loaded for use by the target eNB that did not exist during the source eNB-UE session. In such case the LWA configuration can be provided to the source eNB by the target eNB in the handover request acknowledgement. Similarly, the WiFi configuration parameters can enable modification of the LWA configuration of the source eNB. In such case, the configuration parameters may be provided by either the source eNB or the target eNB. In addition, the WiFi configuration parameters can be utilized to release the LWA configuration of the source eNB if there is no LWA connection at the target eNB.

[0033] FIG. 4 illustrates functionality of a UE to facilitate wireless multi- connectivity, in accordance with an example. The functionality of the UE includes a handover mechanism for concurrent use of an LTE service and a WiFi service. The handover mechanism of the UE can be implemented by one or more processors and memory, wherein the memory stores one or more sets of instructions that when executed by the one or more processors perform one or more functionalities including the handover mechanism. In one instance, the handover mechanism can be implemented by one or more processors and memory of an application circuitry, a baseband circuitry, and/or Radio Frequency (RF) circuitry of the UE.

[0034] In one aspect, the functionality of the UE can include decoding a connection reconfiguration message by the UE from a source eNB 410. The connection reconfiguration message can include an indication to maintain a first current Pair-wise Master Key (PMK) valid for use as a second current PMK.

[0035] In one aspect, the functionality of the UE can optionally include decoding a WiFi configuration parameters from the source eNB 420. The WiFi configuration parameters may include one or more modified mobility set configurations and one or more LWA setup configurations for WT addition. The WiFi parameters that were transmitted in the transparent container from the tarte eNB to the source eNB can be transmitted from the source eNB to the UE.

[0036] In one aspect, the UE can encode a connection request, for transmission to the target eNB 430, in response to decoding the connection reconfiguration message. The connection request initiates a communication session between the target eNB and the UE.

[0037] In one aspect, the UE can replace the first current PMK with a new PMK 440, in response to decoding the connection reconfiguration message. Thereafter, the second current PMK that was used with the source eNB can be maintained by the WT for use with the target eNB. The source eNB will use the old, second current, PMK it was using on the source eNB for some time to maintain the connection with the WT. The new, first current, PMK generated by the target eNB can be kept to be used for later associations.

[0038] When the new PMK is generated as a result of handover from the source eNB to the target eNB, ciphering keys similarly change. However, in accordance with PDCP, two cipher keys may be maintained.

[0039] In one aspect, the UE can receive from a WT a packet including an indication to start to use the new cipher key 450. In one instance, the cipher key may be a Packet Data Convergence Protocol (PDCP) cipher key. In one instance, the packet including the indication to use a new cipher key includes one or more bits in a header that indicates use of the new cipher key. Accordingly, the indication in the packet provides a mechanism for the UE to switch to the new cipher key and also to detect which packets were ciphered with which key.

[0040] In one aspect, the UE can decipher one or more of a plurality of packets using a current cipher key until one of the plurality of ciphered packets is determined to include an indication to switch cipher keys. Thereafter, the other packets are deciphered using the new cipher key starting with the one of the plurality of ciphered packets that includes the indication to switch cipher keys.

[0041] In one aspect, the UE can similarly cipher one or more of a plurality of packets using the current cipher key. One or more other packets of the plurality of packets can be ciphered by the UE using the new cipher key. The first one of the other packets ciphered using the new cipher key includes the indication to switch cipher keys.

[0042] In one aspect, at some point the second current PMK can be de- provisioned after a predetermined time 460. The predetermined time can be selected to be longer than packets are in flight between the source eNB and UE after a handover request. In another instance, the second current PMK can be de-provisioned after it is determined that no UE is using it anymore. In yet another instance, the second current PMK can be de-provisioned when preparation for a next handover is initiated.

[0043] FIG. 5 illustrates functionality of a WT to facilitate wireless multi- connectivity in accordance with an example. The functionality of the WT includes a handover mechanism for concurrent use of an LTE service and a WiFi service. The handover mechanism of the WT can be implemented by one or more processors and memory, wherein the memory stores one or more sets of instructions that when executed by the one or more processors perform one or more functionalities including the handover mechanism. In one instance, the handover mechanism may be implemented by one or more processors and memory of an application circuitry, a baseband circuitry, and/or Radio Frequency (RF) circuitry of the WT.

[0044] In one aspect, the functionality of the WT can include decoding a WT addition request received from a target eNB 510. The WT addition request can include an indication to the WT to maintain a first current Pair-wise Master Key (PMK) valid as a second current PMK. [0045] In one aspect, the WT can replace the first current PMK with a new PMK 520, in response to decoding the connection reconfiguration message. Thereafter, the second current PMK that was used with the source eNB can be maintained by the WT. The source WT will use the old, second current, PMK it was using on the source eNB for some time to maintain the connection. The new, first current, PMK generated by the target eNB can be kept to be used for later associations.

[0046] The WT, therefore, can still use the second current PMK when instructed by the target eNB. In such case, the WT and the AP should belong to the currently configured UE WLAN mobility set to maintain, during a specified period of time, the PMKs for the UE. As long as the current WLAN association is active, the second current PMK is used. With the next association, the UE can start using the first current PMK.

[0047] In one aspect, at some point the second current PMK can be de- provisioned after a predetermined time 530, wherein the predetermined time is selected to be longer than packets are in flight between the source eNB and UE after a handover request. In another instance, the second current PMK can be de-provisioned after it is determined that no UE is using it anymore. In yet another instance, the second current PMK can be de-provisioned when preparation for a next handover is initiated.

[0048] FIG. 6 illustrates signaling in a wireless multi-connectivity system, in accordance with an example. In one aspect, a handover request can be encoded 605 by a baseband circuitry of a source eNB 110 and decoded by a baseband circuitry of a target eNB 115. The encoded handover request can be transmitted from an RF circuitry of the source eNB to an RF circuitry of the target eNB across one or more wired communication links according to an X2 complaint protocol.

[0049] In one aspect, a WT addition request 610 can be encoded by a baseband circuitry of the target eNB 1 15 and decoded by a baseband circuitry of a WT 120. The WT addition request can be sent in response to the handover request. The WT addition request can be transmitted from the RF circuitry of the target eNB to an RF circuitry of the WT across one or more wired communication links according to an Xw compliant protocol. The WT addition request can include an indication to the WT to maintain a first current Pair-wise Master Key (PMK) valid as a second current PMK. [0050] In one aspect, a handover request acknowledgement can be encoded 615 by the baseband circuitry of the target eNB 115 and decoded by the baseband processor of the circuitry of a source eNB 110. The handover request

acknowledgement can be sent in response to the handover request. In one instance, the acknowledgement can include a transparent container to be sent to the UE as an RRC message to perform the handover which also includes a modified mobility set configuration and the LWA setup configurations. The handover request

acknowledgement can be transmitted from the RF circuitry of the target eNB to the RF circuitry of source eNB across one or more wired communication links according to an X2 complaint protocol.

[0051] In one aspect, a connection reconfiguration message can be encoded 620 by the baseband circuitry of the source eNB 110 and decoded by a baseband circuitry of a UE 130. The connection reconfiguration message can be sent in response to the handover request acknowledgement. The connection reconfiguration message can include an indication to the WT to maintain a first current Pair-wise Master Key

(PMK) valid as a second current PMK. The connection reconfiguration message can be transmitted from the RF circuitry of the source eNB to the RF circuitry of the UE using a higher layer communication, such as a Radio Resource Control (RRC)

communication, a Master Information Block (MIB), a Secondary Information Block (SIB), a Packet Data Convergence Protocol (PDCP), or another desired type of higher layer communication.

[0052] In one aspect, WiFi configuration parameters can be encoded 625 by the baseband circuitry of the source eNB 110 and decoded by the baseband circuitry of a UE 130. In one instance the WiFi configuration parameters may enable a LWA configuration to be loaded for use by the target eNB that did not exist during the source eNB-UE session. In such case the LWA configuration may be provided to the source eNB by the target eNB in the handover request acknowledgement in a transparent container. Similarly, the WiFi configuration parameters may enable modification of the LWA configuration of the source eNB. In such case, the configuration parameters may be provided by either the source eNB or the target eNB. In addition, the WiFi configuration parameters may be utilized to release the LWA configuration of the source eNB if there is no LWA connection at the target eNB. The connection reconfiguration message can also be encoded, for transmission from the RF circuitry of the source eNB to RF circuitry of the UE, using a higher layer communication, such as a Radio Resource Control (RRC) communication, a Packet Data Convergence Protocol (PDCP), or another desired type of higher layer communication.

[0053] In one aspect, a connection request can be encoded 630 by the baseband circuitry of the UE 130 and decoded by the baseband circuitry of a target eNB 1 15. The connection request can be sent in response to the connection reconfiguration message. The connection request can be transmitted from the RF circuitry of the UE to the RF circuitry of the target eNB using a higher layer communication, such as a Radio Resource Control (RRC) communication, a Packet Data Convergence Protocol (PDCP), or another desired type of higher layer communication.

[0054] In one aspect, a packet including an indication to use a new cipher key can be encoded 635 by the baseband circuitry of the target eNB 115 and decoded by the baseband circuitry of the UE 130. Accordingly, the indication in the packet provides a mechanism for the UE to switch to the new cipher key and also to detect which packets were ciphered with which key. The packet including an indication to use the new cipher key can be transmitted across one or more wireless communication links according to a higher layer communication, such as a Radio Resource Control (RRC) communication, a Master Information Block (MIB), a Secondary Information Block (SIB), a Packet Data Convergence Protocol (PDCP), or another desired type of higher layer communication.

[0055] Accordingly, the handover mechanism enables the UE and WT to maintain WiFi communications while the UE is handed off between eNBs. The handover mechanism also enables the UE to decipher data packets sent via WiFi communications using the ciphering key associated with the source eNB, and switch to the new ciphering key once new packets are received from the target eNB. The eNB handover without WT release enables quick resumption of high throughputs after handover. The handover mechanism advantageously reduces signaling after handover to resume an LWA or similar connection. In particular, the signaling associated with communication channel measurements, WT addition, LWA activation and/or similar functions is reduced. The reduction in signaling can be appreciable because eNB handovers are relatively frequent in a number of operating conditions. [0056] FIG. 7 illustrates functionality of a UE to facilitate wireless multi- connectivity, in accordance with another example. The functionality of the UE includes a handover mechanism for concurrent use of an LTE service and a WiFi service. The handover mechanism of the UE can be implemented by one or more processors and memory, wherein the memory stores one or more sets of instructions that when executed by the one or more processors perform one or more functionalities including the handover mechanism. In one instance, the handover mechanism may be implemented by one or more processors and memory of an application circuitry, a baseband circuitry, and/or Radio Frequency (RF) circuitry of the UE.

[0057] In one aspect, the functionality of the UE can include decoding a connection reconfiguration message received from a source eNB 705. The UE can flush packets from its WiFi packet queue automatically in response to receiving the reconfiguration message received from the source eNB.

[0058] In one aspect, the UE can encode a disassociation message for transmission to a WT 710. The disassociation message can close the WiFi

communication session between the UE and the WT. In one instance, once the WT detects disassociation of the UE, the WT may drop all queued packets to the UE. In another instance, the disassociation message encoded, for transmission to the WT, may optionally include an indication to flush packets from the WiFi packet queue. The indication to flush packets causes the WT to flush packets from its WiFi packet queue. In another instance, the source eNB may encode, before triggering the handover request, an indication to the WT to flush all packets.

[0059] In one aspect, the UE can suspend an LWA configuration 715, in response to the connection reconfiguration message. In one aspect, the UE can encode, for transmission to a target eNB, a connection request message 720. The connection request message initiates creation of an LTE communication session between the UE and the target eNB.

[0060] In one aspect, the UE can generate a new PMK 725, in response to the connection reconfiguration message. In one aspect, the UE can resume the LWA configuration using the new PMK 730. [0061] In one aspect, the UE can encode, for transmission to the WT, a re- association message using the new PMK 735. In one aspect, the UE can decode a re- association response received from the WT using the new PMK 740.

[0062] Accordingly, the handover mechanism enables the UE and WT to maintain WiFi communications while the UE is handed off between eNBs. Suspending the LWA configuration and then restarting with the new PMK advantageously reduces signaling after handover. The reduction in signaling can be appreciable because eNB handovers are relatively frequent in normal operating conditions. The optional indication to flush packets can advantageously ensure that packets associated with the source eNB do not remain after the handover.

[0063] FIG. 8 illustrates functionality of a UE to facilitate wireless multi- connectivity, in accordance with yet another example. The functionality of the UE includes a handover mechanism for concurrent use of an LTE service and a WiFi service. The handover mechanism of the UE can be implemented by one or more processors and memory, wherein the memory stores one or more sets of instructions that when executed by the one or more processors perform one or more functionalities including the handover mechanism. In one instance, the handover mechanism may be implemented by one or more processors and memory of an application circuitry, a baseband circuitry, and/or Radio Frequency (RF) circuitry of the UE.

[0064] In one aspect, the functionality of the UE can include generating a WiFi cipher key 805 from information provided by the source eNB. In one aspect, the UE can also generate an LTE cipher key 810. In one aspect, the UE can decipher a plurality of LTE packets received via WiFi using the WiFi cipher key 815. In one aspect, the UE can decipher a plurality of LTE packets using the LTE cipher key 820.

[0065] In one aspect, the UE can decode a connection reconfiguration message by the UE from a source eNB 825. In one aspect, the UE can encode a connection request, for transmission to the target eNB 830, in response to decoding the connection reconfiguration message. The connection request initiates a communication session between the target eNB and the UE.

[0066] In one aspect, the UE can generate a new LTE cipher key 835, in response to the connection reconfiguration message. In one aspect, the UE can decipher a plurality of LTE packets using the LTE cipher key 840, after receipt of the connection reconfiguration message.

[0067] Accordingly, the handover mechanism may use different ciphering keys for PDCP or LWAAP packets sent over WiFi and LTE. In such case, the eNB ciphers the packets sent over WiFi with the WiFi specific cipher key, and indicates to the UE how to derive the key. The UE can then use the WiFi key to decipher packets received over WiFi regardless of the cellular handover.

[0068] The functionality of the UE can include a mechanism that does not cipher LTE packets sent/received over WiFi. The mechanism of the UE can be implemented by one or more processors and memory, wherein the memory stores one or more sets of instructions that when executed by the one or more processors perform one or more functionalities including the handover mechanism. In one instance, the mechanism may be implemented by one or more processors and memory of an application circuitry, a baseband circuitry, and/or Radio Frequency (RF) circuitry of the UE.

[0069] In one aspect, the eNB can cipher, for transmission to the UE, one or more packets wherein PDCP or LWAAP ciphering is tumed off. In one instance, a bit in the header of one or more packets may be utilized to indicate that the packets are not ciphered.

[0070] In one aspect, the UE can cipher, for transmission to an eNB, one or more packets wherein PDCP or LWAAP ciphering is turned off, instead of performing the functions of 830-845. In one instance, a bit in the header of one or more packets may be utilized to indicate that the packets are not ciphered. However, when PDCP or LWAAP cipher is tumed off, the Xw interface coupling the UE and WT is still typically protected with IPsec and the WLAN air interface is encrypted in LWA. Accordingly, the packets can be exchanged between the UE and WT without PDCP or LWAAP ciphering regardless of the cellular handover, while still provided some security protection from the IPsec and WLAN air interface encryption.

[0071] FIG. 9 illustrates a diagram of a UE 900, in accordance with an example. The UE may be a mobile station (MS), a mobile wireless device, a mobile communication device, a tablet, a handset, or other type of wireless device. In one aspect, the UE 900 can include at least one of an antenna 905, a touch sensitive display screen 910, a speaker 915, a microphone 920, a graphics processor 925, a baseband processor 930, an application processor 935, internal memory 940, a keyboard 945, a non-volatile memory port 950, and combinations thereof.

[0072] The UE can include one or more antennas configured to communicate with a node or transmission station, such as a base station (BS), an evolved Node B (eNB), a baseband unit (BBU), a remote radio head (RRH), a remote radio equipment (RRE), a relay station (RS), a radio equipment (RE), a remote radio unit (RRU), a central processing module (CPM), or other type of wireless wide area network

(WW AN) access point. The wireless device can be configured to communicate using at least one wireless communication standard including 3GPP LTE, WiMAX, High Speed Packet Access (HSPA), Bluetooth, and WiFi. The wireless device can communicate using separate antennas for each wireless communication standard or shared antennas for multiple wireless communication standards. The wireless device can communicate in a wireless local area network (WLAN), a wireless personal area network (WPAN), and/or a WW AN. The mobile device can include a storage medium. In one aspect, the storage medium can be associated with and/or communicate with the application processor, the graphics processor, the display, the non- volatile memory port, and/or internal memory. In one aspect, the application processor and graphics processor are storage mediums.

[0073] FIG. 10 illustrates a diagram of example components of a User Equipment (UE) device in accordance with an example. In some aspects, the UE device 1000 can include application circuitry 1002, baseband circuitry 1004, RF circuitry 1006, front-end module (FEM) circuitry 1008 and one or more antennas 1010, coupled together at least as shown.

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

[0075] The processor(s) can include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors can be coupled with and/or can include a storage medium 1012, and can be configured to execute instructions stored in the storage medium 1012 to enable various applications and/or operating systems to run on the system.

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

mapping/demapping functionality. In some aspects, encoding/decoding circuitry of the baseband circuitry 1004 can include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality. Aspects of modulation/demodulation and encoder/decoder functionality are not limited to these examples and can include other suitable functionality in other aspects.

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

[0078] In some aspects, the baseband circuitry 1004 can provide for

communication compatible with one or more radio technologies. For example, in some aspects, the baseband circuitry 1004 can support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Aspects in which the baseband circuitry 1004 is configured to support radio communications of more than one wireless protocol can be referred to as multi- mode baseband circuitry.

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

[0080] In some aspects, the RF circuitry 1006 can include a receive signal path and a transmit signal path. The receive signal path of the RF circuitry 1006 can include mixer circuitry 1006a, amplifier circuitry 1006b and filter circuitry 1006c. The transmit signal path of the RF circuitry 1006 can include filter circuitry 1006c and mixer circuitry 1006a. RF circuitry 1006 can also include synthesizer circuitry 1006d for synthesizing a frequency for use by the mixer circuitry 1006a of the receive signal path and the transmit signal path. In some aspects, the mixer circuitry 1006a of the receive signal path can be configured to down-convert RF signals received from the FEM circuitry 1008 based on the synthesized frequency provided by synthesizer circuitry 1006d. The amplifier circuitry 1006b can be configured to amplify the down-converted signals and the filter circuitry 1006c can 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 can be provided to the baseband circuitry 1004 for further processing. In some aspects, the output baseband signals can be zero-frequency baseband signals, although the output baseband signals do not have to be zero -frequency baseband signals. In some aspects, mixer circuitry 1006a of the receive signal path can comprise passive mixers, although the scope of the aspects is not limited in this respect.

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

[0082] In some aspects, the mixer circuitry 1006a of the receive signal path and the mixer circuitry 1006a of the transmit signal path can include two or more mixers and can be arranged for quadrature down conversion and/or up conversion respectively. In some aspects, the mixer circuitry 1006a of the receive signal path and the mixer circuitry 1006a of the transmit signal path can include two or more mixers and can be arranged for image rejection (e.g., Hartley image rejection). In some aspects, the mixer circuitry 1006a of the receive signal path and the mixer circuitry 1006a can be arranged for direct down conversion and/or direct up conversion, respectively. In some aspects, the mixer circuitry 1006a of the receive signal path and the mixer circuitry 1006a of the transmit signal path can be configured for super-heterodyne operation.

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

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

embodiments is not limited in this respect.

[0085] In some embodiments, the synthesizer circuitry 1006d can be a fractional-

N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers can be suitable. For example, synthesizer circuitry 1006d can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

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

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

[0088] Synthesizer circuitry 1006d of the RF circuitry 1006 can include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some

embodiments, the divider can be a dual modulus divider (DMD) and the phase accumulator can be a digital phase accumulator (DPA). In some embodiments, the DMD can 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 can 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 can 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.

[0089] In some embodiments, synthesizer circuitry 1006d can be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency can 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 can be a LO frequency (fLO). In some embodiments, the RF circuitry 1006 can include an IQ/polar converter.

[0090] FEM circuitry 1008 can include a receive signal path which can include circuitry configured to operate on RF signals received from one or more antennas 1010, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 1006 for further processing. FEM circuitry 1008 can also include a transmit signal path which can include circuitry configured to amplify signals for transmission provided by the RF circuitry 1006 for transmission by one or more of the one or more antennas 1010.

[0091] In some embodiments, the FEM circuitry 1008 can include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry can include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry can 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 1006). The transmit signal path of the FEM circuitry 1008 can include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 1006), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 1010.

[0092] In some embodiments, the UE device 1000 can include additional elements such as, for example, memory/storage, display, camera, sensor, and/or input/output (I/O) interface.

[0093] FIG. 11 illustrates a diagram 1100 of a node 11 10 (e.g., eNB and/or a base station) and wireless device (e.g., UE) in accordance with an example. The node can include a base station (BS), a Node B (NB), an evolved Node B (eNB), a baseband unit (BBU), a remote radio head (RRH), a remote radio equipment (RRE), a remote radio unit (RRU), or a central processing module (CPM). In one aspect, the node can be a Serving GPRS Support Node. The node 11 10 can include a node device 11 12. The node device 1112 or the node 1110 can be configured to communicate with the wireless device 1120. The node device 11 12 can be configured to implement the technology described. The node device 1112 can include a processing module 1114 and a transceiver module 1116. In one aspect, the node device 1112 can include the transceiver module 1116 and the processing module 11 14 forming a circuitry 11 18 for the node 11 10. In one aspect, the transceiver module 1116 and the processing module 1114 can form a circuitry of the node device 11 12. The processing module 1114 can include one or more processors and memory. In one embodiment, the processing module 1122 can include one or more application processors. The transceiver module 1116 can include a transceiver and one or more processors and memory. In one embodiment, the transceiver module 11 16 can include a baseband processor.

[0094] The wireless device 1120 can include a transceiver module 1124 and a processing module 1 122. The processing module 1122 can include one or more processors and memory. In one embodiment, the processing module 1122 can include one or more application processors. The transceiver module 1124 can include a transceiver and one or more processors and memory. In one embodiment, the transceiver module 1124 can include a baseband processor. The wireless device 1120 can be configured to implement the technology described. The node 1110 and the wireless devices 1 120 can also include one or more storage mediums, such as the transceiver module 1116, 1124 and/or the processing module 1114, 1122. In one aspect, the components described herein of the transceiver module 1116 can be included in one or more separate devices that can be used in a cloud-RAN (C-RAN) environment. EXAMPLES

[0095] The following examples pertain to specific technology embodiments and point out specific features, elements, or steps that can be used or otherwise combined in achieving such embodiments.

[0096] Example 1 includes an apparatus of an Evolved NodeB (eNB), operable as a target eNB of an eNB handover, the apparatus comprising one or more processors and memory configured to: decode a handover request from a source eNB; encode a Wireless Local Area Network Termination (WT) addition request, for transmission to a WT, wherein the WT addition request includes an indication to maintain a first current Pair-wise Master Key (PMK) valid as a second current PMK; encode a handover acknowledgment, for transmission to the source eNB, wherein the handover acknowledgement includes one or more Wireless Local Area Network (WLAN) configuration parameters; and decode a connection request message from a User Equipment (UE).

[0097] Example 2 includes the apparatus according to Example 1, wherein: the first current PMK and the second current PMK are maintained for the source eNB to maintain a connection with the WT and avoid a new association with the WT.

[0098] Example 3 includes the apparatus according to Example 1, wherein the one or more processors and memory are further configured to: decode the handover request from the source eNB including the one or more WLAN configuration parameters, wherein the WLAN configuration parameters are WiFi configuration parameters for a WLAN configured to operate using an Institute of Electronics and Electrical Engineers (IEEE) 802.11 standard.

[0099] Example 4 includes the apparatus according to Example 1, wherein the one or more processors and memory is further configured to: encode, after the handover request acknowledgement, a packet including an indication to use a new Packet Data Convergence Protocol (PDCP) or Long Term Evolution (LTE) Wireless Aggregation Adaptation Protocol (LWAAP) cipher key, for transmission to the UE.

[00100] Example 5 includes the apparatus according to Example 4, wherein the packet including the indication to use a new PDCP or LWAAP cipher key comprises a PDCP Protocol Data Unit (PDU) packet or an LTE LWAAP packet wherein one or more bits in a header indicates use of the new PDCP or LWAAP cipher key.

[00101] Example 6 includes the apparatus according to Example 3, wherein the one or more WiFi configuration parameters include one or more modified mobility set configurations and one or more LTE Wireless Aggregation (LWA) setup configurations for the WT addition request.

[00102] Example 7 includes the apparatus according to Examples 1-5 or 6, wherein: the target eNB communicates with the source eNB using an X2 protocol; the target eNB communicates with the WT using an Xw protocol; and the target eNB communicates with the UE using a Radio Resource Control (RRC) protocol.

[00103] Example 8 includes the apparatus according to Example 3, wherein the one or more WiFi configuration parameters allows the UE to synchronize to the target eNB and start associating to the WT and apply the one or more WiFi configuration parameters.

[00104] Example 9 includes an apparatus of an Evolved NodeB (eNB), operable as a source eNB of an eNB handover, the apparatus comprising one or more processors and memory configured to: encode a handover request for transmission to a target eNB; decode a handover acknowledgment received from the target eNB; and encode a connection reconfiguration message, for transmission to a User Equipment (UE), wherein the connection reconfiguration message includes an indication to maintain a first current Pair-wise Master Key (PMK) valid for use as a second current PMK.

[00105] Example 10 includes the apparatus according to Example 9, wherein: the first current PMK and the second current PMK are maintained for the source eNB to maintain a connection with the WT and avoid a new association with the WT.

[00106] Example 11 includes the apparatus according to Example 9, wherein the one or more processors and memory are further configured to: encode the handover request, for transmission to the target eNB, wherein the handover request includes one or more WiFi configuration parameters.

[00107] Example 12 includes the apparatus according to Example 11, wherein the one or more WiFi configuration parameters encoded, for transmission to the target eNB, allows the UE to synchronize to the target eNB and start associating to the WT and apply the one or more WiFi configuration parameters.

[00108] Example 13 includes the apparatus according to Example 12, wherein the one or more processors and memory are further configured to: decode the handover acknowledgment received from the target eNB including one or more modified mobility set configurations and one or more LTE Wireless Aggregation (LWA) setup configurations for WT addition; and encode a transparent container, for transmission to the UE, wherein the transparent container includes the one or more modified mobility set configurations and one or more LWA setup configurations for WT addition.

[00109] Example 14 includes an apparatus of a User Equipment (UE), operable to maintain a Wireless Local Area Network (WiFi) connection during an Evolved NodeB (eNB) handover, the apparatus comprising one or more processors and memory configured to: decode a connection reconfiguration massage, from a source eNB, wherein the connection reconfiguration message includes an indication to maintain a first current Pair-wise Master Key (PMK) valid for use as a second current PMK;

encode a connection request message for transmission to a target eNB; and replace the first current PMK with a new PMK in response to decoding the connection

reconfiguration massage.

[00110] Example 15 includes the apparatus according to Example 14, wherein: the first current PMK and the second current PMK are maintained for the source eNB to maintain a connection with the WT and avoid a new association with the WT.

[00111] Example 16 includes the apparatus according to Example 14, wherein the one or more processors and memory are further configured to: decode a plurality of ciphered packets from a Wireless Termination (WT); decipher one or more of the plurality of ciphered packets using a current Packet Data Convergence Protocol (PDCP) cipher key until one of the plurality of ciphered packets includes an indication to switch PDCP cipher keys; and decipher one or more other ciphered packets of the plurality of ciphered packets using a new PDCP cipher key starting with the one of the plurality of ciphered packets that includes the indication to switch PDCP cipher keys.

[00112] Example 17 includes the apparatus according to Example 16, wherein the ciphered packet including the indication to use the new PDCP cipher key comprises Packet Data Convergence Protocol (PDCP) Protocol Data Unit (PDU) packet or an LTE Wireless Aggregation Adaptation Protocol (LWAAP) wherein one or more bits in a header indicates use of the new PDCP cipher key.

[00113] Example 18 includes the apparatus according to Example 16, wherein the one or more processors and memory are further configured to: de-provision the second current PMK after a predetermined time.

[00114] Example 19 includes the apparatus according to Example 16, wherein the one or more processors and memory are further configured to: de-provision the second current PMK after it is determined that no UE is using it anymore.

[00115] Example 20 includes the apparatus according to Examples 14-18 or 19, wherein the one or more processors and memory are further configured to: cipher one or more of a plurality of packets using the current PDCP cipher key; cipher one or more other packets of the plurality of packets using the new PDCP cipher key, wherein a first one of the other packets of the plurality of packets ciphered using the new PDCP cipher key includes an indication to switch PDCP cipher keys; and encode the plurality of ciphered packets for transmission to the WT.

[00116] Example 21 includes the apparatus according to Example 16, wherein the WiFi transceiver of the UE encodes to the WT using an 802.11 a or 802.11 ac (WiFi) compliant protocol interface.

[00117] Example 22 includes the apparatus according to Example 14, wherein the apparatus of the UE includes at least one of an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, a baseband processor, an application processor, internal memory, a non-volatile memory port, and combinations thereof.

[00118] Example 23 includes an apparatus of a Wireless local area network Termination (WT), operable to maintain a Wireless Local Area Network WiFi connection during an Evolved NodeB (eNB) handover, the apparatus comprising one or more processors and memory configured to: decode a WT addition request, received from a target eNB, wherein the WT addition request includes an indication to maintain a first current Pair-wise Master Key (PMK) valid as a second current PMK; and replace the first current PMK with a new PMK in response to decoding the WT addition request.

[00119] Example 24 includes the apparatus according to Example 23, wherein: the first current PMK and the second current PMK are maintained for the source eNB to maintain a connection with the WT and avoid a new association with the WT.

[00120] Example 25 includes the apparatus according to Example 23, wherein the one or more processors and memory are further configured to: decode a plurality of ciphered packets received from a User Equipment (UE); decipher one or more of the plurality of ciphered packets using a current PDCP cipher key until one of the plurality of ciphered packets includes an indication to switch PDCP cipher keys; and decipher one or more other ciphered packets of the plurality of ciphered packets using a new PDCP cipher key starting with the one of the plurality of ciphered packets that includes the indication to switch PDCP cipher keys. [00121] Example 26 includes the apparatus according to Example 25, wherein the ciphered packet including the indication to use the new PDCP cipher key comprises Packet Data Convergence Protocol (PDCP) Protocol Data Unit (PDU) packet or wherein one or more bits in a header indicates use of the new PDCP cipher key.

[00122] Example 27 includes the apparatus according to Example 25, wherein the one or more processors and memory are further configured to: de-provision the second current PMK after a predetermined time.

[00123] Example 28 includes the apparatus according to Example 25, wherein the one or more processors and memory are further configured to: de-provision the second current PMK after it is determined that no UE is using it anymore.

[00124] Example 29 includes the apparatus according to Examples 23-27 or 28, wherein the one or more processors and memory are further configured to: cipher one or more of a plurality of packets using the current PDCP cipher key; cipher one or more other packets of the plurality of packets using the new PDCP cipher key, wherein a first one of the other packets of the plurality of packets ciphered using the new PDCP cipher key includes an indication to switch PDCP cipher keys; and encode the plurality of ciphered packets for transmission to the UE.

[00125] Example 30 includes the apparatus according to Example 25, wherein the WiFi transceiver of the WT encodes to the UE using an Institute of Electronics and Electrical Engineers (IEEE) 802.11 a or 802.11 ac (WiFi) compliant protocol interface.

[00126] Example 31 includes an apparatus of an Evolved NodeB (eNB), operable as a target eNB of an eNB handover, the apparatus comprising: a means for decoding a handover request from a source eNB; a means for encoding a Wireless Local Area Network Termination (WT) addition request, for transmission to a WT, wherein the WT addition request includes an indication to maintain a first current Pair- wise Master Key (PMK) valid as a second current PMK; a means for encoding a handover acknowledgment, for transmission to the source eNB, wherein the handover acknowledgement includes one or more Wireless Local Area Network (WLAN) configuration parameters; and a means for decoding a connection request message from a User Equipment (UE). [00127] Example 32 includes the apparatus according to Example 31, wherein: the first current PMK and the second current PMK are maintained for the source eNB to maintain a connection with the WT and avoid a new association with the WT.

[00128] Example 33 includes the apparatus according to Example 31, further comprising: a means for decoding the handover request from the source eNB including the one or more WLAN configuration parameters, wherein the WLAN configuration parameters are WiFi configuration parameters for a WLAN configured to operate using an Institute of Electronics and Electrical Engineers (IEEE) 802.11 standard.

[00129] Example 34 includes the apparatus according to Example 31, further comprising: a means for encoding, after the handover request acknowledgement, a packet including an indication to use a new Packet Data Convergence Protocol (PDCP) or Long Term Evolution (LTE) Wireless Aggregation Adaptation Protocol (LWAAP) cipher key, for transmission to the UE.

[00130] Example 35 includes the apparatus according to Example 34, wherein the packet including the indication to use a new PDCP or LWAAP cipher key comprises a PDCP Protocol Data Unit (PDU) packet or an LTE LWAAP packet wherein one or more bits in a header indicates use of the new PDCP or LWAAP cipher key.

[00131] Example 36 includes the apparatus according to Example 33, wherein the one or more WiFi configuration parameters include one or more modified mobility set configurations and one or more LTE Wireless Aggregation (LWA) setup configurations for the WT addition request.

[00132] Example 37 includes the apparatus according to Examples 31 -35 or 36, wherein: the target eNB communicates with the source eNB using an X2 protocol; the target eNB communicates with the WT using an Xw protocol; and the target eNB communicates with the UE using a Radio Resource Control (RRC) protocol.

[00133] Example 38 includes the apparatus according to Example 33, wherein the one or more WiFi configuration parameters allows the UE to synchronize to the target eNB and start associating to the WT and apply the one or more WiFi configuration parameters. [00134] Example 39 includes an apparatus of an Evolved NodeB (eNB), operable as a source eNB of an eNB handover, the apparatus comprising: a means for encoding a handover request for transmission to a target eNB; a means for decoding a handover acknowledgment received from the target eNB; and a means for encoding a connection reconfiguration message, for transmission to a User Equipment (UE), wherein the connection reconfiguration message includes an indication to maintain a first current Pair-wise Master Key (PMK) valid for use as a second current PMK.

[00135] Example 40 includes the apparatus according to Example 39, wherein: the first current PMK and the second current PMK are maintained for the source eNB to maintain a connection with the WT and avoid a new association with the WT.

[00136] Example 41 includes the apparatus according to Example 39, further comprising: a means for encoding the handover request, for transmission to the target eNB, wherein the handover request includes one or more WiFi configuration parameters.

[00137] Example 42 includes the apparatus according to Example 41, wherein the one or more WiFi configuration parameters encoded, for transmission to the target eNB, allows the UE to synchronize to the target eNB and start associating to the WT and apply the one or more WiFi configuration parameters.

[00138] Example 43 includes the apparatus according to Example 42, further comprising: a means for decoding the handover acknowledgment received from the target eNB including one or more modified mobility set configurations and one or more LTE Wireless Aggregation (LWA) setup configurations for WT addition; and a means for encoding a transparent container, for transmission to the UE, wherein the transparent container includes the one or more modified mobility set configurations and one or more LWA setup configurations for WT addition.

[00139] Example 44 includes an apparatus of a User Equipment (UE), operable to maintain a Wireless Local Area Network (WiFi) connection during an Evolved NodeB (eNB) handover, the apparatus comprising: a means for decoding a connection reconfiguration massage, from a source eNB, wherein the connection reconfiguration message includes an indication to maintain a first current Pair-wise Master Key (PMK) valid for use as a second current PMK; a means for encoding a connection request message for transmission to a target eNB; and a means for replacing the first current PMK with a new PMK in response to decoding the connection reconfiguration massage.

[00140] Example 45 includes the apparatus according to Example 44, wherein: the first current PMK and the second current PMK are maintained for the source eNB to maintain a connection with the WT and avoid a new association with the WT.

[00141] Example 46 includes the apparatus according to Example 44, further comprising: a means for decoding a plurality of ciphered packets from a Wireless Termination (WT); a means for deciphering one or more of the plurality of ciphered packets using a current Packet Data Convergence Protocol (PDCP) cipher key until one of the plurality of ciphered packets includes an indication to switch PDCP cipher keys; and a means for deciphering one or more other ciphered packets of the plurality of ciphered packets using a new PDCP cipher key starting with the one of the plurality of ciphered packets that includes the indication to switch PDCP cipher keys.

[00142] Example 47 includes the apparatus according to Example 46, wherein the ciphered packet including the indication to use the new PDCP cipher key comprises Packet Data Convergence Protocol (PDCP) Protocol Data Unit (PDU) packet or an LTE Wireless Aggregation Adaptation Protocol (LWAAP) wherein one or more bits in a header indicates use of the new PDCP cipher key.

[00143] Example 48 includes the apparatus according to Example 46, further comprising: a means for de-provisioning the second current PMK after a predetermined time.

[00144] Example 49 includes the apparatus according to Example 46, further comprising: a means for de-provisioning the second current PMK after it is determined that no UE is using it anymore.

[00145] Example 50 includes the apparatus according to Examples 44-48 or 49, further comprising: a means for ciphering one or more of a plurality of packets using the current PDCP cipher key; a means for ciphering one or more other packets of the plurality of packets using the new PDCP cipher key, wherein a first one of the other packets of the plurality of packets ciphered using the new PDCP cipher key includes an indication to switch PDCP cipher keys; and a means for encoding the plurality of ciphered packets for transmission to the WT. [00146] Example 51 includes the apparatus according to Example 46, wherein the WiFi transceiver of the UE encodes to the WT using an 802.11 a or 802.11 ac (WiFi) compliant protocol interface.

[00147] Example 52 includes the apparatus according to Example 44, wherein the apparatus of the UE includes at least one of an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, a baseband processor, an application processor, internal memory, a non-volatile memory port, and combinations thereof.

[00148] Example 53 includes an apparatus of a Wireless local area network Termination (WT), operable to maintain a Wireless Local Area Network WiFi connection during an Evolved NodeB (eNB) handover, the apparatus comprising: a means for decode a WT addition request, received from a target eNB, wherein the WT addition request includes an indication to maintain a first current Pair-wise Master Key (PMK) valid as a second current PMK; and a means for replacing the first current PMK with a new PMK in response to decoding the WT addition request.

[00149] Example 54 includes the apparatus according to Example 53, wherein: the first current PMK and the second current PMK are maintained for the source eNB to maintain a connection with the WT and avoid a new association with the WT.

[00150] Example 55 includes the apparatus according to Example 53, further comprising: a means for decoding a plurality of ciphered packets received from a User Equipment (UE); a means for deciphering one or more of the plurality of ciphered packets using a current PDCP cipher key until one of the plurality of ciphered packets includes an indication to switch PDCP cipher keys; and a means for deciphering one or more other ciphered packets of the plurality of ciphered packets using a new PDCP cipher key starting with the one of the plurality of ciphered packets that includes the indication to switch PDCP cipher keys.

[00151] Example 56 includes the apparatus according to Example 55, wherein the ciphered packet including the indication to use the new PDCP cipher key comprises Packet Data Convergence Protocol (PDCP) Protocol Data Unit (PDU) packet or wherein one or more bits in a header indicates use of the new PDCP cipher key. [00152] Example 57 includes the apparatus according to Example 55, further comprising: a means for de-provision the second current PMK after a predetermined time.

[00153] Example 58 includes the apparatus according to Example 55, further comprising: a means for de-provision the second current PMK after it is determined that no UE is using it anymore.

[00154] Example 59 includes the apparatus according to Examples 53-57 or 58, further comprising: a means for ciphering one or more of a plurality of packets using the current PDCP cipher key; a means for ciphering one or more other packets of the plurality of packets using the new PDCP cipher key, wherein a first one of the other packets of the plurality of packets ciphered using the new PDCP cipher key includes an indication to switch PDCP cipher keys; and a means for encoding the plurality of ciphered packets for transmission to the UE.

[00155] Example 60 includes the apparatus according to Example 55, wherein the WiFi transceiver of the WT encodes to the UE using an Institute of Electronics and Electrical Engineers (IEEE) 802.11 a or 802.1 l ac (WiFi) compliant protocol interface.

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

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

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

[00158] As used herein, the term processor can include general purpose processors, specialized processors such as VLSI, FPGAs, or other types of specialized processors, as well as base band processors used in transceivers to send, receive, and process wireless communications.

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

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

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

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

[00163] As used herein, a plurality of items, structural elements, compositional elements, and/or materials can be presented in a common list for convenience.

However, these lists should be construed as though each member of the list is individually identified as a separate and unique member. Thus, no individual member of such list should be construed as a de facto equivalent of any other member of the same list solely based on their presentation in a common group without indications to the contrary. In addition, various embodiments and example of the present technology can be referred to herein along with alternatives for the various components thereof. It is understood that such embodiments, examples, and alternatives are not to be construed as de facto equivalents of one another, but are to be considered as separate and autonomous representations of the present technology.

[00164] Furthermore, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided, such as examples of layouts, distances, network examples, etc., to provide a thorough understanding of embodiments of the technology. One skilled in the relevant art will recognize, however, that the technology can be practiced without one or more of the specific details, or with other methods, components, layouts, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the technology.

[00165] While the forgoing examples are illustrative of the principles of the present technology in one or more particular applications, it will be apparent to those of ordinary skill in the art that numerous modifications in form, usage and details of implementation can be made without the exercise of inventive faculty, and without departing from the principles and concepts of the technology. Accordingly, it is not intended that the technology be limited, except as by the claims set forth below.

Claims

What is claimed is:

1. An apparatus of an Evolved NodeB (eNB), operable as a target eNB of an eNB handover, the apparatus comprising one or more processors and memory configured to: decode a handover request from a source eNB;

encode a Wireless Local Area Network Termination (WT) addition request, for transmission to a WT, wherein the WT addition request includes an indication to maintain a first current Pair-wise Master Key (PMK) valid as a second current PMK;

encode a handover acknowledgment, for transmission to the source eNB, wherein the handover acknowledgement includes one or more Wireless Local Area Network (WLAN) configuration parameters; and

decode a connection request message from a User Equipment (UE).

2. The apparatus according to claim 1, wherein:

the first current PMK and the second current PMK are maintained for the source eNB to maintain a connection with the WT and avoid a new association with the WT.

3. The apparatus according to claim 1, wherein the one or more processors and memory are further configured to:

decode the handover request from the source eNB including the one or more WLAN configuration parameters, wherein the WLAN configuration parameters are WiFi configuration parameters for a WLAN configured to operate using an Institute of Electronics and Electrical Engineers (IEEE) 802.11 standard.

4. The apparatus according to claim 1, wherein the one or more processors and memory is further configured to:

encode, after the handover request acknowledgement, a packet including an indication to use a new Packet Data Convergence Protocol (PDCP) or Long Term Evolution (LTE) Wireless Aggregation Adaptation Protocol (LWAAP) cipher key, for transmission to the UE.

5. The apparatus according to claim 4, wherein the packet including the indication to use a new PDCP or LWAAP cipher key comprises a PDCP Protocol Data Unit (PDU) packet or an LTE LWAAP packet wherein one or more bits in a header indicates use of the new PDCP or LWAAP cipher key.

6. The apparatus according to claim 3, wherein the one or more WiFi configuration parameters include one or more modified mobility set configurations and one or more LTE Wireless Aggregation (LWA) setup configurations for the WT addition request.

7. The apparatus according to claims 1 -5 or 6, wherein:

the target eNB communicates with the source eNB using an X2 protocol;

the target eNB communicates with the WT using an Xw protocol; and the target eNB communicates with the UE using a Radio Resource Control (RRC) protocol.

8. The apparatus according to claim 3, wherein the one or more WiFi configuration parameters allows the UE to synchronize to the target eNB and start associating to the WT and apply the one or more WiFi configuration parameters.

9. An apparatus of an Evolved NodeB (eNB), operable as a source eNB of an eNB handover, the apparatus comprising one or more processors and memory configured to:

encode a handover request for transmission to a target eNB;

decode a handover acknowledgment received from the target eNB; and encode a connection reconfiguration message, for transmission to a User

Equipment (UE), wherein the connection reconfiguration message includes an indication to maintain a first current Pair-wise Master Key (PMK) valid for use as a second current PMK.

10. The apparatus according to claim 9, wherein:

11. The apparatus according to claim 9, wherein the one or more processors and memory are further configured to:

encode the handover request, for transmission to the target eNB, wherein the handover request includes one or more WiFi configuration parameters.

12. The apparatus according to claim 11, wherein the one or more WiFi configuration parameters encoded, for transmission to the target eNB, allows the UE to synchronize to the target eNB and start associating to the WT and apply the one or more WiFi configuration parameters.

13. The apparatus according to claim 12, wherein the one or more processors and memory are further configured to:

decode the handover acknowledgment received from the target eNB including one or more modified mobility set configurations and one or more LTE Wireless Aggregation (LWA) setup configurations for WT addition; and

encode a transparent container, for transmission to the UE, wherein the transparent container includes the one or more modified mobility set configurations and one or more LWA setup configurations for WT addition.

14. An apparatus of a User Equipment (UE), operable to maintain a Wireless Local Area Network (WiFi) connection during an Evolved NodeB (eNB) handover, the apparatus comprising one or more processors and memory configured to:

decode a connection reconfiguration massage, from a source eNB, wherein the connection reconfiguration message includes an indication to maintain a first current Pair- wise Master Key (PMK) valid for use as a second current PMK;

encode a connection request message for transmission to a target eNB; and replace the first current PMK with a new PMK in response to decoding the connection reconfiguration massage.

15. The apparatus according to claim 14, wherein:

16. The apparatus according to claim 14, wherein the one or more processors and memory are further configured to:

decode a plurality of ciphered packets from a Wireless Termination (WT);

decipher one or more of the plurality of ciphered packets using a current Packet Data Convergence Protocol (PDCP) cipher key until one of the plurality of ciphered packets includes an indication to switch PDCP cipher keys; and

decipher one or more other ciphered packets of the plurality of ciphered packets using a new PDCP cipher key starting with the one of the plurality of ciphered packets that includes the indication to switch PDCP cipher keys.

17. The apparatus according to claim 16, wherein the ciphered packet including the indication to use the new PDCP cipher key comprises Packet Data Convergence Protocol (PDCP) Protocol Data Unit (PDU) packet or an LTE Wireless Aggregation Adaptation Protocol (LWAAP) wherein one or more bits in a header indicates use of the new PDCP cipher key.

18. The apparatus according to claim 16, wherein the one or more processors and memory are further configured to: de-provision the second current PMK after a predetermined time.

19. The apparatus according to claim 16, wherein the one or more processors and memory are further configured to: de-provision the second current PMK after it is determined that no UE is using it anymore.

20. The apparatus according to claims 14-18 or 19, wherein the one or more processors and memory are further configured to:

cipher one or more of a plurality of packets using the current PDCP cipher key; cipher one or more other packets of the plurality of packets using the new PDCP cipher key, wherein a first one of the other packets of the plurality of packets ciphered using the new PDCP cipher key includes an indication to switch PDCP cipher keys; and encode the plurality of ciphered packets for transmission to the WT.

21. The apparatus according to claim 16, wherein the WiFi transceiver of the UE encodes to the WT using an 802.11 a or 802.1 1 ac (WiFi) compliant protocol interface.

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

23. An apparatus of a Wireless local area network Termination (WT), operable to maintain a Wireless Local Area Network WiFi connection during an Evolved NodeB (eNB) handover, the apparatus comprising one or more processors and memory configured to:

decode a WT addition request, received from a target eNB, wherein the WT addition request includes an indication to maintain a first current Pair-wise Master Key (PMK) valid as a second current PMK; and

replace the first current PMK with a new PMK in response to decoding the WT addition request.

24. The apparatus according to claim 23, wherein:

25. The apparatus according to claim 23, wherein the one or more processors and memory are further configured to:

decode a plurality of ciphered packets received from a User Equipment (UE); decipher one or more of the plurality of ciphered packets using a current PDCP cipher key until one of the plurality of ciphered packets includes an indication to switch PDCP cipher keys; and

26. The apparatus according to claim 25, wherein the ciphered packet including the indication to use the new PDCP cipher key comprises Packet Data Convergence Protocol (PDCP) Protocol Data Unit (PDU) packet or wherein one or more bits in a header indicates use of the new PDCP cipher key.

27. The apparatus according to claim 25, wherein the one or more processors and memory are further configured to: de-provision the second current PMK after a predetermined time.

28. The apparatus according to claim 25, wherein the one or more processors and memory are further configured to:

de-provision the second current PMK after it is determined that no UE is using it anymore.

29. The apparatus according to claims 23-27 or 28, wherein the one or more processors and memory are further configured to:

cipher one or more of a plurality of packets using the current PDCP cipher key; cipher one or more other packets of the plurality of packets using the new PDCP cipher key, wherein a first one of the other packets of the plurality of packets ciphered using the new PDCP cipher key includes an indication to switch PDCP cipher keys; and encode the plurality of ciphered packets for transmission to the UE.

30. The apparatus according to claim 25, wherein the WiFi transceiver of the WT encodes to the UE using an Institute of Electronics and Electrical Engineers (IEEE)

802.11 a or 802.1 1 ac (WiFi) compliant protocol interface.