WO2017142575A1

WO2017142575A1 - Maximum transmission unit (mtu) size reconfiguration for an lwip operation

Info

Publication number: WO2017142575A1
Application number: PCT/US2016/033222
Authority: WO
Inventors: Jing Zhu; Suresh Srinivasan
Original assignee: Intel Corporation
Priority date: 2016-02-19
Filing date: 2016-05-19
Publication date: 2017-08-24

Abstract

Technology for an eNodeB to communicate with a user equipment (UE) reconfiguring a maximum transmission unit (MTU) size for 3GPP LTE WLAN Radio Level Integration with IPsec Tunnel (LWIP) operation within a wireless communication network is disclosed. The eNodeB can determine an encapsulation type for payload data communicated during a wireless local area network (WLAN) radio level integration with IPsec tunnel (LWIP) operation. The eNodeB can set an LWIP maximum transmission unit (MTU) size based on the encapsulation type. The eNodeB can signal a transceiver of the eNodeB to transmit one or more LWIP parameters to the UE to enable the UE to set a size of an MTU based on the size of the LWIP MTU.

Description

MAXIMUM TRANSMISSION UNIT (MTU) SIZE RECONFIGURATION FOR AN LWIP OPERATION

BACKGROUND

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

(Worldwide interoperability for Microwave Access), and the IEEE 802.11 standard, which is commonly known to industry groups as Wi-Fi. In 3GPP radio access network (RAN) LTE systems, the node can be a combination of Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node Bs (also commonly denoted as evolved Node Bs, enhanced Node Bs, eNodeBs, or eNBs) and Radio Network Controllers (RNCs), which communicates with the wireless device, known as a user equipment (UE). The downlink (DL) transmission can be a communication from the node (e.g., eNodeB) to the wireless device (e.g., UE), and the uplink (UL) transmission can be a communication from the wireless device to the node.

[0002] In addition, a wireless multiple-access communications system may include a number of eNodeBs, each simultaneously supporting communication for multiple mobile devices. The eNodeBs may communicate with mobile devices on downstream and upstream links. In some wireless networks, a user equipment (UE) may be capable of supporting multiple wireless technologies concurrently. For example, a UE may simultaneously transmit data over a wireless local area network (WLAN) link and a Long Term Evolution (LTE) link. However, current scalability, deployment, functionality, and protocols for communication between the UE and the eNodeB and/or the WLAN can be inefficient to meet the current demands. For example, challenges arise when delivering l cellular traffic over the WLAN and adding additional tunneling headers to internet protocol (IP) packets. Adding the additional tunneling headers to the IP packets that enable the packets to be offloaded to the WLAN can cause the size of the IP packets to be larger than the WLAN is configured to deliver. Thus, a desire exits for a solution to provide functionality and protocols scalable and efficient to meet the constraints for communication between the UE and the eNodeB and/or the WLAN.

BRIEF DESCRIPTION OF THE DRAWINGS

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

[0004] FIG. 1 depicts an illustrative wireless communications system in accordance with an example;

[0005] FIG. 2a illustrates a diagram of a 3 GPP LTE internet protocol (IP) based wireless local area network (WLAN) radio level integration with IP security protocol (IPSec) tunnel (LWIP) in accordance with an example;

[0006] FIG. 2b illustrates a diagram of LTE-WLAN Radio Access Network (RAN) level integration using IPSec tunneling in accordance with another example;

[0007] FIG. 3 illustrates a diagram of a IP security protocol (IPSec) and user datagram protocol (UDP) encapsulation for LWIP in accordance with an example;

[0008] FIG. 4 illustrates a diagram of an LWIP maximum transmission unit (MTU) size reconfiguration procedure in accordance with an example;

[0009] FIG. 5 illustrates a diagram of configuring a data bearer to be transported over an LWIP tunnel and reconfiguring the LWIP MTU in accordance with an example;

[0010] FIG. 6 depicts additional functionality of an eNodeB operable to communicate with a User Equipment (UE), within a wireless communication network, for

reconfiguring a maximum transmission unit (MTU) size for a 3GPP LTE wireless local area network (WLAN) Radio Level Integration with an IPsec Tunnel (LWIP) operation in accordance with an example; [0011] FIG. 7 depicts functionality of a user equipment (UE) to communicate with an eNodeB, within a wireless communication network, for reconfiguring a maximum transmission unit (MTU) size for 3GPP LTE wireless local area network (WLAN) Radio Level Integration with an IPsec Tunnel (LWIP) operation in accordance with an example;

[0012] FIG. 8 A depicts additional functionality of a user equipment (UE) to communicate with an eNodeB, within a wireless communication network, for reconfiguring a maximum transmission unit (MTU) size for 3GPP LTE wireless local area network (WLAN) Radio Level Integration with an IPsec Tunnel (LWIP) operation in accordance with an example;

[0013] FIG. 8B depicts additional functionality of a user equipment (UE) to communicate with an eNodeB, within a wireless communication network, for resetting a maximum transmission unit (MTU) size back to an original size before performing the 3GPP LTE wireless local area network (WLAN) Radio Level Integration with an IPsec Tunnel (LWIP) operation in accordance with an example

[0014] FIG. 9 illustrates a diagram of example components of a wireless device (e.g. User Equipment "UE") device in accordance with an example;

[0015] FIG. 10 illustrates a diagram of example components of a User Equipment (UE) device in accordance with an example; and

[0016] FIG. 11 illustrates a diagram of a node (e.g., eNB) and wireless device (e.g., UE) in accordance with an example.

[0017] 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

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

EXAMPLE EMBODIMENTS

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

[0020] In one aspect, the present technology provides for an eNodeB to communicate with a user equipment (UE) for reconfiguring a maximum transmission unit (MTU) size for a 3GPP LTE wireless local area network (WLAN) Radio Level Integration with an Internet Protocol security (IPsec) (LWIP) Tunnel operation within a wireless

communication network. The eNodeB can determine an encapsulation type for payload data communicated during an LWIP operation. The eNodeB can set an LWIP maximum transmission unit (MTU) size based on the encapsulation type. The eNodeB can signal a transceiver of the eNodeB to transmit one or more LWIP parameters to the UE to enable the UE to set a size of an MTU (e.g., a cellular MTU) based on the size of the LWIP MTU. In one aspect, the LWIP MTU and the MTU (e.g., a cellular MTU) can be two control parameters. The LWIP-MTU can be defined as the maximum transmission unit size supported by the LWIP tunnel of the eNodeB. The Cellular-MTU can be defined as the MTU size of a cellular interface that an UE is configured with before LWIP is activated.

[0021] In one aspect, the present technology provides for an apparatus of a User Equipment (UE) to decode a signal, received from the eNodeB, to perform a wireless local area network (WLAN) radio level integration with an IPsec (LWIP) tunnel operation activation procedure. The UE can process one or more LWIP MTU parameters received in a message from the eNodeB during the LWIP operation activation procedure, indicating to the UE to set a size of an MTU (e.g., cellular MTU) based on one or more LWIP maximum MTU parameters. The UE can set the size of the MTU according to the one or more LWIP parameters.

[0022] In one aspect, the present technology provides for an apparatus of a User Equipment (UE) to decode a signal, received from the eNodeB, to perform a wireless local area network (WLAN) radio level integration with an IPsec tunnel (LWIP) operation activation procedure. The UE can process one or more LWIP maximum transmission unit (MTU) parameters in a message, received from the eNodeB, during an wireless local area network (WLAN) radio level integration with an IPsec tunnel (LWIP) operation activation procedure, indicating to the UE to set a size of an MTU based on one or more LWIP maximum MTU parameters. The UE can set the size of the MTU equal to the

LWIP MTU according to the one or more LWIP parameters, wherein the LWIP MTU size is a maximum transmission unit size supported by an LWIP tunnel of the eNodeB.

[0023] FIG. 1 illustrates an example of one type of wireless network 100 operable to communicate based on a 3GPP LTE standard. In this example, a node can be illustrated and be a combination of Evolved Universal Terrestrial Radio Access Network (E- UTRAN) Node Bs (also commonly denoted as evolved Node Bs, enhanced Node Bs, eNodeBs, or eNBs) and Radio Network Controllers (RNCs), which communicates with the wireless device, known as a user equipment (UE) 110. As depicted in FIG. 1, the node is illustrated, by way of example only, as an eNodeB 112. Downlink (DL) transmission can be a communication from the eNodeB 112 (e.g., the node) to the wireless device (e.g., UE 110), and the uplink (UL) transmission can be a communication from the wireless device (e.g., UE 110) to the eNodeB 112 (e.g., the node).

[0024] The eNodeB 112 can include one or more antennas, one or more radio modules to modulate and/or demodulate signals transmitted or received on an air interface, and one or more digital modules to process signals transmitted and received on the air interface. The eNodeBs can 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 (RRM), remote radio entity (RRE), and the like.

[0025] The eNodeB 112 can provide communication coverage for a particular geographic area. The term "cell" can refer to a coverage area of an eNB 112 and/or an eNB subsystem serving this coverage area. The UE can also be in communication with a wireless local area network (WLAN) access point 114. The eNodeB 112 and the WLAN can be included within a radio access network and in communication with an evolved packet core (EPC) 160.

[0026] The EPC 160 can include a serving gateway (S-GW) 120 and a mobility management entity (MME) 130. The EPC 160 can also include a packet data network (PDN) gateway (P-GW) 142 to couple a serving gateway (S-GW) 120 to the PDN, such as the Internet 180, an intra-net, or other similar network. The S-GW can provide Internet network access and standard network access for the mobile devices associated with the RAN. The S-GW 120 and MME 130 can be in direct communication with each other via cabling, wire, optical fiber, and/or transmission hardware, such a router or repeater. The eNodeB 112 can be connected to one or more user equipments (UE) 110, and the WLAN AP 114, respectively. The eNodeB 112 can be in direct communication with the EPC 160 and each of the components within the EPC 160.

[0027] The EPC 160 can also include a policy and charging rules function (PCRF) node 144 that can be used to determine, in near real time, policy rules in the wireless network. The PCRF node can access subscriber databases and other specialized functions, such as charging systems, as can be appreciated.

[0028] In one aspect, the UE 110 can communicate with a wireless local area network (WLAN) access point (AP) 114. The eNodeB 112 can also be in communication with the WLAN AP 114. In one aspect, the eNodeB 112 and a WLAN AP 114 can provide the UE 110 with access to the evolved packet core 160 using different radio access technologies (RATs). For example, the eNodeB 112 can provide access to the evolved packet core 160 over LTE access technology, such as a 3 GPP LTE air interface, and the WLAN AP 114 can provide access to the eNodeB 112.

[0029] FIG. 2a illustrates a system 200 of a 3 GPP LTE internet protocol (IP) based wireless local area network (WLAN) radio level integration with IP security protocol (IPSec) tunnel (LWIP). In one aspect, FIG. 2 depicts a network architecture for 3GPP LTE Rel. 13 WLAN Radio Level Integration with an IPsec Tunnel (LWIP) having at least one or more of an eNodeB (eNB), a servicing gateway (S-GW), a packet data network gateway (P-GW), a user equipment (UE), a mobility management entity (MME), and/or one or more interfaces, such as, for example, Uu, S l-MME, S l-u, Sl l, and S5/8. [0030] In one aspect, a mobility anchor can be at an eNB, and a WLAN/3GPP link aggregation can be transparent to 3GPP core network elements (e.g. MME, S-GW, P- GW). A UE can establish an Internet Protocol (IP) security protocol (IPSec) tunnel with the eNB via a WLAN. The IPSec tunnel can be used to deliver a UE's (IP) traffic via the WLAN. In one aspect, an LWIP operation can be transparent to a WLAN, and is not constrained to make one or more changes to a legacy WLAN deployment (e.g., any 3GPP LTE release prior to 3GPP LTE Rel. 13). Furthermore, traffic steering and multi-radio access technology (RAT) radio resource management (RRM) can take place over a top of an LTE RAN u-plane protocol stack (e.g., above a packet data convergence protocol "PDCP").

[0031] FIG. 2b provides an additional example 250 illustration of LTE-WLAN Radio Access Network (RAN) level integration using IPSec tunneling. For LTE-WLAN integration using IPSec tunneling. In this example embodiment, the integration can be performed using PDCP SDUs above the PDCP layer. The eNB can be configured to control activation of the integration based on the UE connectivity with a specific WLAN. Once the integration is activated, the eNB can segregate incoming DL packets towards the UE for offloading via the WLAN at a layer above the PDCP. The UL packets from the UE can be aggregated by the eNB at the same logical point.

[0032] In one aspect, an LWIP operation can allow a UE in radio resource connected mode (RRC C ONNECTED) to be configured by the eNB to utilize WLAN radio resources via IPsec tunneling, as illustrated in FIG. 2b. IP Packets can be transferred between the UE and an S-GW, via an S l -u interface, as shown in FIG. 2a. The IP packets can be encapsulated using in order to provide security to the packets that traverse WLAN. The IP packets can then be transported between the S-GW and the eNB. The end to end path between the UE and eNB via the WLAN network can be referred to as the LWIP tunnel. However, the LWIP can be constrained to use IPSec encapsulation when delivering cellular traffic via a WLAN. In addition, additional user datagram protocol (UDP) encapsulation may be used if there is a network address translation (NAT) on the WLAN path. The addition of IPSec and UDP encapsulation can increase the overall packet size.

[0033] FIG. 3 illustrates a diagram of an internet protocol (IP) security protocol (IPSec) and user datagram protocol (UDP) encapsulation for LWIP. A cellular IP packet 302 can be an IP version 4 (IPv4) or IPv6 packet comprised of payload data and an IP header. When this cellular IP packet is configured to send over an IPSec tunnel, additional packetization can occur. For example, an IPSec ESP packet 304 can include an additional IP header, an encapsulation security protocol (ESP) header, the original IP header, the payload data, an ESP trailer, and an ESP authorization. When NAT is used, additional UDP encapsulation 306 can be applied. The UDP encapsulation can further comprise, over packet 304, a new IP header and a UDP header. In each level of encapsulation, the size of the packet can increase, and can become larger than a WLAN standard may be configured for. When the encapsulated packet becomes too large to transmit over a selected standard, such as the Institute of Electronics and Electrical Engineers (IEEE) 802.11 standard, the result can lead to IP fragmentation and performance degradation.

[0034] To overcome this limitation, in one aspect, the eNB can provide the UE with an updated (LWIP-specific) MTU size during the LWIP activation procedure according to an encapsulation type. That is, depending on the type of encapsulation being used, such as IPSec encapsulation, UDP encapsulation (for a network address translator "NAT" traversal), or another type of encapsulation, the eNB can determine an updated LWIP MTU size based on the encapsulation type. The LWIP MTU size can then be

communicated to the UE. The UE can then be configured to adjust a size of the payload data to reduce the overall packet size to be within the limitations of the WLAN standard. In one aspect, the present technology can be implemented in 3GPP LTE Rel. 13 (or subsequent 3GPP LTE defined releases) in integrated multi-RAT (e.g., 3GPP LTE and Wi-Fi) networks.

[0035] In one aspect, it can be assumed that an LWIP-specific MTU size can be known to the eNB (e.g., pre-configured) based on the IPSec tunneling setup. As illustrated in FIG. 3, the encapsulation type (e.g., for a cellular interface), for an IP datagram for performing an LWIP operation, can include an internet protocol (IP) header and payload data, as shown in the IPv4 packet 302. Alternatively, after applying the IP security protocol (IPSec) ESP in the LWIP tunneling for performing the LWIP operation, the IPSec encapsulation type 304 can include an additional IP header, an ESP header, the IP header, the payload data, an ESP trailer, and an ESP authorization, as previously discussed. In another aspect, the encapsulation type, after applying a UDP encapsulation 306 for performing the LWIP operation, can include the additional IP header, a user datagram protocol (UDP) header, the ESP header, the IP header, the payload data, the ESP trailer, and the ESP authorization.

[0036] Accordingly, the eNB can provide the UE an updated (LWIP-specific) MTU size during the LWIP activation procedure according to the encapsulation type. In one aspect, it can be assumed the LWIP-specific MTU size is known to or pre-configured by the eNB based on its IPSec tunneling setup. In one aspect, the LWIP MTU and a cellular MTU can be two control parameters. The LWIP-MTU can be defined as the MTU (maximum transmission unit) size that the eNB's LWIP tunnel supports. The MTU (e.g. a cellular- MTU) can be defined as the MTU size that a UE is configured with its cellular interface before the LWIP is activated.

[0037] Turning now to FIG. 4, an example of an LWIP maximum transmission unit (MTU) size reconfiguration procedure is illustrated. In one aspect, the eNB can provide the UE with an updated (LWIP-specific) MTU size during the LWIP activation procedure. The LWIP-specific MTU size can be known to the eNB and/or pre- configured by the eNB based on the IPSec tunneling setup, which uses a specific type of encapsulation. Accordingly, in step 1, during the LWIP activation procedure, eNB can send one or more provisional LWIP-MTU parameters to the UE either with a new control (e.g., RRC) message and/or a new information element in a legacy control message. In step 2, the UE can configure the MTU size of the UE's cellular interface to be the size of the LWIP-MTU if the LWIP-MTU is less than the Cellular-MTU. That is, the UE can set the size of the MTU equal to the LWIP MTU when the MTU is greater than the size of the LWIP MTU. If the size of MTU of the UE's cellular interface is less than the LWIP-MTU, the UE can keep and/or retain the size of the MTU (e.g., the UE does not reconfigure the size of the cellular MTU). In step 3, the UE can establish the LWIP tunneling with eNB via WLAN, and commence (start) the LWIP operation. In step 4, the UE and/or the eNB can initiate to terminate the LWIP operation. In one aspect, after the LWIP operation is deactivated, the UE can change the MTU size of its cellular interface back to Cellular-MTU.

[0038] Turning now to FIG. 5, an example 500 is provided for configuring a data bearer to be transported over the LWIP tunnel and reconfiguring the LWIP MTU. It should be noted that FIG. 5 depicts one example of applying the reconfiguration LWIP MTU reconfiguration and should not be construed to be limiting to FIG. 5 only. In step 1, the eNB can configure the UE to perform WLAN measurements for LWIP operation. In step 2, the UE can apply the new configuration and reply with an

RRCConnectionReconfligurationComplete" message. In step 3, the UE can send WLAN measurements to the eNB. In step 4, the eNB can send the

RRCConnectionReconflguration message to the UE including the WLAN mobility set. In step 5, the UE can apply a new configuration and reply with an

RRCConnectionReconfligurationComplete" message. In step 6, the UE can associate with the WLAN in consideration of the mobility set, if not already associated. In step 7, the UE can send a confirmation of the WLAN association to the eNB. In step 8, the eNB can send the RRCConnectionReconflguration message to the UE including the necessary parameters to establish an IPSec tunnel over a WLAN and may configure data bearers to utilize the IPsec tunnel and apply the reconfiguration to the LWIP MTU. In step 8, the eNB can send the one or more LWIP MTU parameters in the

RRCConnectionReconflguration message indicating to the UE to set a size of an MTU based on one or more LWIP maximum MTU parameters. In step 9, the UE can apply the new configuration and replies with RRCConnectionReconfligurationComplete message. That is, the UE can signal in the RRCConnectionReconfligurationComplete message that the size of the MTU is set according to the one or more LWIP parameters

[0039] In one aspect, the UE can use the parameters including the one or more LWIP MTU parameters, in a new radio resource configuration (RRC) to setup the IPsec tunnel with the SGW to complete the establishment of the LWIP tunnel with the eNB over the WLAN access. The eNB can add and/or remove data bearers to utilize the LWIP tunnel at any time after the establishment of the LWIP tunnel by sending the RRCConnectionReconfliguration" message to the UE. The LWIP MTU parameters can allow the UE to change the size of the data packets for each LWIP tunnel based on the encapsulation type that is used by the eNB. Changing the size of the data packets can significantly reduce IP fragmentation and performance degradation that can occur when the packets are larger than a packet size that is transmitted by the WLAN.

[0040] Turning now to FIG. 6, an example provides functionality 600 of an eNodeB operable to communicate with a User Equipment (UE) for reconfiguring a maximum transmission unit (MTU) size for 3GPP LTE WLAN Radio Level Integration with an IPsec Tunnel (LWIP) operation, as shown in the flow chart in FIG. 6. The functionality 600 can be implemented as a method or the functionality can be executed as instructions on a machine, where the instructions are included one or more computer readable mediums or one or more non-transitory machine readable storage mediums. The eNodeB can comprise one or more processors and memory configured to:

determine an encapsulation type for payload data communicated during a wireless local area network (WLAN) radio level integration with the IPsec tunnel (LWIP) operation, as in block 610. The eNodeB can comprise one or more processors and memory configured to: set an LWIP maximum transmission unit (MTU) size based on the encapsulation type, as in block 620. The LWIP MTU size can be defined as a maximum transmission unit size of the eNodeB that supports LWIP tunneling. The eNodeB can comprise one or more processors and memory configured to: signal a transceiver of the eNodeB to transmit one or more LWIP parameters to the UE to enable the UE to set a size of an MTU based on the size of the LWIP MTU, as in block 630.

[0041] In one aspect, the functionality 600 can perform one or more of the following examples. In one aspect, the functionality 600 can include the one or more processors and memory of the eNodeB to signal the transceiver of the eNodeB to transmit to the UE the one or more LWIP parameters in either a radio resource control message or an information element (IE) of a control message for setting the size of the MTU based on the size of the LWIP MTU. The eNodeB can comprise one or more processors and memory configured to: signal the transceiver of the eNodeB to transmit to the UE an indication to determine whether the size of the MTU is greater than the size of the LWIP MTU. The eNodeB can comprise one or more processors and memory configured to: signal the transceiver of the eNodeB to transmit to the UE an indication to set the size of the MTU equal to the LWIP MTU when the MTU is greater than the size of the LWIP MTU. The eNodeB can comprise one or more processors and memory configured to: establish LWIP tunneling with the UE via a WLAN during the LWIP operation. The eNodeB can comprise one or more processors and memory configured to: perform the LWIP operation with the UE via the WLAN upon setting the cellular MTU equal to the LWIP MTU. The eNodeB can comprise one or more processors and memory configured to: terminate a LWIP operation with the UE via a WLAN during the LWIP operation upon setting the size of the MTU equal to the size of the LWIP MTU. In one aspect, the encapsulation type includes one of an internet protocol (IP) header and payload data for an IP datagram for performing an LWIP operation, an additional IP header, an encapsulation security protocol (ESP) header, the IP header, the payload data, an ESP trailer, and an ESP authorization after applying IP security protocol (IPSec) ESP in the LWIP tunneling for performing the LWIP operation, and the additional IP header, a user datagram protocol (UDP) header, the ESP header, the IP header, the payload data, the ESP trailer, and the ESP authorization after applying a UDP encapsulation for performing the LWIP operation

[0042] Another example provides functionality 700 of a user equipment (UE) operable to communicate with an eNodeB for reconfiguring a maximum transmission unit (MTU) size for 3 GPP LTE WLAN Radio Level Integration with IPsec Tunnel (LWIP) operation, as shown in the flow chart in FIG. 7. The functionality 700 can be implemented as a method or the functionality can be executed as instructions on a machine, where the instructions are included one or more computer readable mediums or one or more non- transitory machine readable storage mediums. The UE can comprise one or more processors and memory configured to: decode a signal, received from the eNodeB, to perform a wireless local area network (WLAN) radio level integration with an IPsec tunnel (LWIP) operation activation procedure, as in block 710. The UE can comprise one or more processors and memory configured to: process one or more LWIP maximum transmission unit (MTU) parameters in a message, received from the eNodeB, during an wireless local area network (WLAN) radio level integration with an IPsec tunnel (LWIP) operation activation procedure, indicating to the UE to set a size of an MTU based on one or more LWIP maximum MTU parameters, as in block 720. The LWIP MTU size can be defined as a maximum transmission unit size of the eNodeB that supports LWIP tunneling. The UE can comprise one or more processors and memory configured to: set the size of the MTU according to the one or more LWIP parameters, as in block 730.

In one aspect, the functionality 700 can perform one or more of the following examples. In one aspect, the functionality 700 can include the one or more processors and memory of the UE to process the one or more LWIP parameters that are received from the eNodeB in either a radio resource control message or an information element (IE) of a control message for setting the size of the MTU based on a size of the LWIP MTU according to the one or more LWIP parameters. The UE can comprise one or more processors and memory configured to: process an indication, received from the eNodeB, to determine whether the size of the MTU is greater than the size of the LWIP MTU. The UE can comprise one or more processors and memory configured to: set the size of the MTU equal to a size of the LWIP MTU, such as setting the size of the MTU equal to the LWIP MTU when the MTU is greater than the size of the LWIP MTU. The UE can comprise one or more processors and memory configured to: establish LWIP tunneling with the eNodeB via a WLAN during the LWIP operation. The UE can comprise one or more processors and memory configured to: perform the LWIP operation with the eNodeB via the WLAN upon setting the size of the MTU equal to a size of the LWIP MTU according to the one or more LWIP parameters. The UE can comprise one or more processors and memory configured to: terminate an LWIP operation with the eNodeB via a WLAN during the LWIP operation. The UE can comprise one or more processors and memory configured to: change the size of the MTU back to an original size of the MTU prior to setting the size of the MTU equal to the size of the LWIP MTU.

[0043] Another example provides functionality 800 of a user equipment (UE) operable to communicate with an eNodeB for reconfiguring a maximum transmission unit (MTU) size for 3 GPP LTE WLAN Radio Level Integration with IPsec Tunnel (LWIP) operation, as shown in the flow chart in FIG. 8A. The functionality 800 can be implemented as a method or the functionality can be executed as instructions on a machine, where the instructions are included one or more computer readable mediums or one or more non- transitory machine readable storage mediums. The UE can comprise one or more processors and memory configured to: decode a signal, received from the eNodeB, to perform a wireless local area network (WLAN) radio level integration with internet protocol security protocol (IPSec) tunnel (LWIP) operation activation procedure, as in block 810. The UE can comprise one or more processors and memory configured to: process one or more LWIP maximum transmission unit (MTU) parameters in a message, received from the eNodeB, during an wireless local area network (WLAN) radio level integration with IPsec tunnel (LWIP) operation activation procedure, indicating to the UE to set a size of an MTU based on one or more LWIP maximum MTU parameters, as in block 820. The UE can comprise one or more processors and memory configured to: set the size of the MTU equal to the LWIP MTU according to the one or more LWIP parameters, wherein the LWIP MTU size is a maximum transmission unit size supported by an LWIP tunnel of the eNodeB, as in block 830. [0044] Another example provides functionality 875 of a user equipment (UE) operable to communicate with an eNodeB for resetting a maximum transmission unit (MTU) size back to an original size before performing the 3GPP LTE wireless local area network (WLAN) Radio Level Integration with an IPsec Tunnel (LWIP) operation, as shown in the flow chart in FIG. 8B. The functionality 875 can be implemented as a method or the functionality can be executed as instructions on a machine, where the instructions are included one or more computer readable mediums or one or more non-transitory machine readable storage mediums. The UE can comprise one or more processors and memory configured to: decode a signal, received from the eNodeB, to perform a wireless local area network (WLAN) radio level integration with internet protocol security protocol (IPSec) tunnel (LWIP) operation deactivation procedure, as in block 840. The UE can comprise one or more processors and memory configured to: reset or restore the size of the MTU back to an original MTU value size that the MTU was prior to and/or before performing the LWIP operation, as in block 850. [0045] FIG. 9 illustrates a diagram of a wireless device (e.g., UE) in accordance with an example. FIG. 9 provides an example illustration of the wireless device, such as a user equipment (UE) UE, 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 wireless device can include 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.

[0046] The wireless device 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 (WWAN) 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 WWAN. 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.

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

[0048] 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 memory /storage 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. [0049] 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. [0050] 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, and/or other baseband processor(s) 1004d 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-d) 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.

[0051] 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) 1004e 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) 1004f. The audio DSP(s) 1004f 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).

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

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

[0054] 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. [0055] 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.

[0056] 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 downconversion and/or upconversion 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

downconversion and/or direct upconversion, 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.

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

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

[0059] 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. [0060] 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.

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

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

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

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

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

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

[0067] FIG. 11 illustrates a diagram 1100 of a node 1110 (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 1110 can include a node device 1112. The node device 1112 or the node 1110 can be configured to communicate with the wireless device 1120. The node device 1112 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 1114 forming a circuitry 1118 for the node 1110. In one aspect, the transceiver module 1116 and the processing module 1114 can form a circuitry of the node device 1112. 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 1116 can include a baseband processor.

[0068] The wireless device 1120 can include a transceiver module 1124 and a processing module 1122. 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 1120 can also include one or more storage mediums, such as the transceiver module 1116, 1124 and/or the processing module 1111 , 1122. In one aspect, the components described herein of the transceiver module 1116 can be included in one or more separate devices that may used in a cloud-RAN (C-RAN) environment. Examples

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

[0070] Example 1 includes an apparatus of an eNodeB, the eNodeB configured to communicate with a User Equipment (UE), the apparatus comprising one or more processors and memory configured to: determine an encapsulation type for pay load data communicated during a wireless local area network (WLAN) radio level integration with IPsec tunnel (LWIP) operation; set an LWIP maximum transmission unit (MTU) size based on the encapsulation type; and signal a transceiver of the eNodeB to transmit one or more LWIP parameters to the UE to enable the UE to set a size of an MTU based on the size of the LWIP MTU.

[0071] Example 2 includes the apparatus of example 1 , wherein the LWIP MTU size is a maximum transmission unit size supported by an LWIP tunnel of the eNodeB.

[0072] Example 3 includes the apparatus of example 1 or 2, wherein the one or more processors and memory are further configured to signal the transceiver of the eNodeB to transmit to the UE the one or more LWIP parameters in either a radio resource control message or an information element (IE) of a control message for setting the size of the MTU based on the size of the LWIP MTU.

[0073] Example 4 includes the apparatus of example 1, wherein the encapsulation type includes one of an internet protocol (IP) header and payload data for an IP datagram for performing an LWIP operation, an additional IP header, an encapsulation security protocol (ESP) header, the IP header, the payload data, an ESP trailer, and an ESP authorization after applying IP security protocol (IPSec) ESP in the LWIP tunneling for performing the LWIP operation, and the additional IP header, a user datagram protocol (UDP) header, the ESP header, the IP header, the payload data, the ESP trailer, and the ESP authorization after applying a UDP encapsulation for performing the LWIP operation.

[0074] Example 5 includes the apparatus of example 1 or 2, wherein the one or more processors and memory are further configured to signal the transceiver of the eNodeB to transmit to the UE an indication to determine whether the size of the MTU is greater than the size of the LWIP MTU.

[0075] Example 6 includes the apparatus of example 5, wherein the one or more processors and memory are further configured to signal the transceiver of the eNodeB to transmit to the UE an indication to set the size of the MTU equal to the LWIP MTU when the MTU is greater than the size of the LWIP MTU.

[0076] Example 7 includes the apparatus of example 5, wherein the one or more processors and memory are further configured to establish LWIP tunneling with the UE via a WLAN during the LWIP operation.

[0077] Example 8 includes the apparatus of example 7, wherein the one or more processors and memory are further configured to perform the LWIP operation with the UE via the WLAN upon setting the cellular MTU equal to the LWIP MTU.

[0078] Example 9 includes the apparatus of example 8, wherein the one or more processors and memory are further configured to terminate a LWIP operation with the UE via a WLAN during the LWIP operation upon setting the size of the MTU equal to the size of the LWIP MTU.

[0079] Example 10 includes an apparatus of a User Equipment (UE), the UE configured to communicate with an eNodeB, the apparatus comprising one or more processors and memory configured to: decode a signal, received from the eNodeB, to perform a wireless local area network (WLAN) radio level integration with IPsec tunnel (LWIP) operation activation procedure; process one or more LWIP maximum transmission unit (MTU) parameters in a message, received from the eNodeB, during an wireless local area network (WLAN) radio level integration with IPsec tunnel (LWIP) operation activation procedure, indicating to the UE to set a size of an MTU based on one or more LWIP MTU parameters; and set the size of the MTU according to the one or more LWIP parameters.

[0080] Example 11 includes the apparatus of example 10, wherein the LWIP MTU size is a maximum transmission unit size supported by an LWIP tunnel of the eNodeB.

[0081] Example 12 includes the apparatus of example 10 or 11, wherein the one or more processors and memory are further configured to process the one or more LWIP parameters that are received from the eNodeB in either a radio resource control message or an information element (IE) of a control message for setting the size of the MTU based on a size of the LWIP MTU according to the one or more LWIP parameters.

[0082] Example 13 includes the apparatus of example 10, wherein the encapsulation type includes one of an internet protocol (IP) header and payload data for an IP datagram for performing an LWIP operation, an additional IP header, an encapsulation security protocol (ESP) header, the IP header, the payload data, an ESP trailer, and an ESP authorization after applying IP security protocol (IPSec) ESP in the LWIP tunneling for performing the LWIP operation, and the additional IP header, a user datagram protocol (UDP) header, the ESP header, the IP header, the payload data, the ESP trailer, and the ESP authorization after applying a UDP encapsulation for performing the LWIP operation.

[0083] Example 14 includes the apparatus of example 10, wherein the one or more processors and memory are further configured to process an indication, received from the eNodeB, to determine whether the size of the MTU is greater than the size of the LWIP MTU.

[0084] Example 15 includes the apparatus of example 10 or 14, wherein the one or more processors and memory are further configured to set the size of the MTU equal to a size of the LWIP MTU.

[0085] Example 16 includes the apparatus of example 10 or 14, wherein the one or more processors and memory are further configured to set the size of the MTU equal to the LWIP MTU when the MTU is greater than the size of the LWIP MTU.

[0086] Example 17 includes the apparatus of example 10, wherein the one or more processors and memory are further configured to establish LWIP tunneling with the eNodeB via a WLAN during the LWIP operation.

[0087] Example 18 includes the apparatus of example 10, wherein the one or more processors and memory are further configured to perform the LWIP operation with the eNodeB via the WLAN upon setting the size of the MTU equal to a size of the LWIP MTU according to the one or more LWIP parameters.

[0088] Example 19 includes the apparatus of example 10 or 18, wherein the one or more processors and memory are further configured to terminate an LWIP operation with the eNodeB via a WLAN during the LWIP operation.

[0089] Example 20 includes the apparatus of example 18, wherein the one or more processors and memory are further configured to change the size of the MTU back to an original size of the MTU prior to setting the size of the MTU equal to the size of the LWIP MTU.

[0090] Example 21 includes at least one machine readable storage medium having instructions embodied thereon for an User Equipment (UE) to communicate with a eNodeB, the instructions when executed cause the UE to: decode a signal, received from the eNodeB, to perform a wireless local area network (WLAN) radio level integration with internet protocol security protocol (IPSec) tunnel (LWIP) operation activation procedure; process one or more LWIP maximum transmission unit (MTU) parameters in a message, received from the eNodeB, during an wireless local area network (WLAN) radio level integration with IPsec tunnel (LWIP) operation activation procedure, indicating to the UE to set a size of an MTU based on one or more LWIP maximum parameters; and set the size of the MTU equal to the LWIP MTU according to the one or more LWIP parameters, wherein the LWIP MTU size is a maximum transmission unit size supported by an LWIP tunnel of the eNodeB. [0091] Example 22 includes the at least one machine readable storage medium of example 21, further comprising instructions which when executed cause the UE to:

process an indication, received from the eNodeB, to determine whether the size of the MTU is greater than the size of the LWIP MTU.

[0092] Example 23 includes the at least one machine readable storage medium of example 21, further comprising instructions which when executed cause the UE to: set the size of the MTU equal to the LWIP MTU when the MTU is greater than the size of the LWIP MTU.

[0093] Example 24 includes the at least one machine readable storage medium of example 21, wherein the encapsulation type includes one of an internet protocol (IP) header and payload data for an IP datagram for performing an LWIP operation, an additional IP header, an encapsulation security protocol (ESP) header, the IP header, the payload data, an ESP trailer, and an ESP authorization after applying IP security protocol (IPSec) ESP in the LWIP tunneling for performing the LWIP operation, and the additional IP header, a user datagram protocol (UDP) header, the ESP header, the IP header, the payload data, the ESP trailer, and the ESP authorization after applying a UDP

encapsulation for performing the LWIP operation.

[0094] Example 25 includes the at least one machine readable storage medium of example 21 or 24, further comprising instructions which when executed cause the eNodeB to: terminate an LWIP operation with the eNodeB via a WLAN during the LWIP operation; or change the size of the MTU back to an original size of the MTU prior to setting the size of the MTU equal to the size of the LWIP MTU.

[0095] Example 26 includes an apparatus of a User Equipment (UE), the UE configured to communicate with an eNodeB, the apparatus comprising one or more processors and memory configured to: decode a signal, received from the eNodeB, to perform a wireless local area network (WLAN) radio level integration with internet protocol security protocol (IPSec) tunnel (LWIP) operation deactivation procedure; and restore the size of the MTU back to an original value size of the MTU prior to performing the LWIP operation

[0096] Example 27 includes the apparatus of example 26, wherein the one or more processors and memory are further configured to: process an indication, received from the eNodeB, to terminate the LWIP operation with the eNodeB via a WLAN during the LWIP operation; or change the size of the MTU back to the original size of the MTU prior to setting the size of the MTU equal to the size of the set the size of the MTU according to one or more LWIP parameters.

[0097] Example 28 includes the apparatus of example 27, wherein the one or more LWIP parameters are received from the eNodeB in either a radio resource control message or an information element (IE) of a control message.

[0098] Example 29 includes an apparatus of an eNodeB, the eNodeB configured to communicate with a User Equipment (UE), the apparatus comprising one or more processors and memory configured to: determine an encapsulation type for pay load data communicated during a wireless local area network (WLAN) radio level integration with IPsec tunnel (LWIP) operation; set an LWIP maximum transmission unit (MTU) size based on the encapsulation type; and signal a transceiver of the eNodeB to transmit one or more LWIP parameters to the UE to enable the UE to set a size of an MTU based on the size of the LWIP MTU.

[0099] Example 30 includes the apparatus of example 29, wherein the LWIP MTU size is a maximum transmission unit size supported by an LWIP tunnel of the eNodeB.

[00100] Example 31 includes the apparatus of example 29, wherein the one or more processors and memory are further configured to signal the transceiver of the eNodeB to transmit to the UE the one or more LWIP parameters in either a radio resource control message or an information element (IE) of a control message for setting the size of the MTU based on the size of the LWIP MTU.

[00101] Example 32 includes the apparatus of example 29, wherein the encapsulation type includes one of an internet protocol (IP) header and payload data for an IP datagram for performing an LWIP operation, an additional IP header, an encapsulation security protocol (ESP) header, the IP header, the payload data, an ESP trailer, and an ESP authorization after applying IP security protocol (IPSec) ESP in the LWIP tunneling for performing the LWIP operation, and the additional IP header, a user datagram protocol (UDP) header, the ESP header, the IP header, the payload data, the ESP trailer, and the ESP authorization after applying a UDP encapsulation for performing the LWIP operation. [00102] Example 33 includes the apparatus of example 29, wherein the one or more processors and memory are further configured to signal the transceiver of the eNodeB to transmit to the UE an indication to determine whether the size of the MTU is greater than the size of the LWIP MTU.

[00103] Example 34 includes the apparatus of example 33, wherein the one or more processors and memory are further configured to signal the transceiver of the eNodeB to transmit to the UE an indication to set the size of the MTU equal to the LWIP MTU when the MTU is greater than the size of the LWIP MTU.

[00104] Example 35 includes the apparatus of example 33, wherein the one or more processors and memory are further configured to establish LWIP tunneling with the UE via a WLAN during the LWIP operation.

[00105] Example 36 includes the apparatus of example 35, wherein the one or more processors and memory are further configured to perform the LWIP operation with the UE via the WLAN upon setting the cellular MTU equal to the LWIP MTU.

[00106] Example 37 includes the apparatus of example 36, wherein the one or more processors and memory are further configured to terminate a LWIP operation with the UE via a WLAN during the LWIP operation upon setting the size of the MTU equal to the size of the LWIP MTU.

[00107] Example 38 includes an apparatus of a User Equipment (UE), the UE configured to communicate with an eNodeB, the apparatus comprising one or more processors and memory configured to: decode a signal, received from the eNodeB, to perform a wireless local area network (WLAN) radio level integration with IPsec tunnel (LWIP) operation activation procedure; process one or more LWIP maximum transmission unit (MTU) parameters in a message, received from the eNodeB, during an wireless local area network (WLAN) radio level integration with IPsec tunnel (LWIP) operation activation procedure, indicating to the UE to set a size of an MTU based on one or more LWIP MTU parameters; and set the size of the MTU according to the one or more LWIP parameters.

[00108] Example 39 includes the apparatus of example 38, wherein the LWIP MTU size is a maximum transmission unit size supported by an LWIP tunnel of the eNodeB. [00109] Example 40 includes the apparatus of example 38 or 39, wherein the one or more processors and memory are further configured to process the one or more LWIP parameters that are received from the eNodeB in either a radio resource control message or an information element (IE) of a control message for setting the size of the MTU based on a size of the LWIP MTU according to the one or more LWIP parameters.

[00110] Example 41 includes the apparatus of example 38, wherein the encapsulation type includes one of an internet protocol (IP) header and payload data for an IP datagram for performing an LWIP operation, an additional IP header, an encapsulation security protocol (ESP) header, the IP header, the payload data, an ESP trailer, and an ESP authorization after applying IP security protocol (IPSec) ESP in the LWIP tunneling for performing the LWIP operation, and the additional IP header, a user datagram protocol (UDP) header, the ESP header, the IP header, the payload data, the ESP trailer, and the ESP authorization after applying a UDP encapsulation for performing the LWIP operation.

[00111] Example 42 includes the apparatus of example 38, wherein the one or more processors and memory are further configured to process an indication, received from the eNodeB, to determine whether the size of the MTU is greater than the size of the LWIP MTU.

[00112] Example 43 includes the apparatus of example 42, wherein the one or more processors and memory are further configured to set the size of the MTU equal to a size of the LWIP MTU.

[00113] Example 44 includes the apparatus of example 43, wherein the one or more processors and memory are further configured to set the size of the MTU equal to the LWIP MTU when the MTU is greater than the size of the LWIP MTU.

[00114] Example 45 includes the apparatus of example 38, wherein the one or more processors and memory are further configured to establish LWIP tunneling with the eNodeB via a WLAN during the LWIP operation.

[00115] Example 46 includes the apparatus of example 38, wherein the one or more processors and memory are further configured to perform the LWIP operation with the eNodeB via the WLAN upon setting the size of the MTU equal to a size of the LWIP MTU according to the one or more LWIP parameters. [00116] Example 47 includes the apparatus of example 46, wherein the one or more processors and memory are further configured to terminate an LWIP operation with the eNodeB via a WLAN during the LWIP operation.

[00117] Example 48 includes the apparatus of example 47, wherein the one or more processors and memory are further configured to change the size of the MTU back to an original size of the MTU prior to setting the size of the MTU equal to the size of the LWIP MTU.

[00118] Example 49 includes at least one non-transitory machine readable storage medium having instructions embodied thereon for an User Equipment (UE) to communicate with a eNodeB, the instructions when executed cause the UE to: decode a signal, received from the eNodeB, to perform a wireless local area network (WLAN) radio level integration with internet protocol security protocol (IPSec) tunnel (LWIP) operation activation procedure; process one or more LWIP maximum transmission unit (MTU) parameters in a message, received from the eNodeB, during an wireless local area network (WLAN) radio level integration with IPsec tunnel (LWIP) operation activation procedure, indicating to the UE to set a size of an MTU based on one or more LWIP maximum parameters; and set the size of the MTU equal to the LWIP MTU according to the one or more LWIP parameters, wherein the LWIP MTU size is a maximum transmission unit size supported by an LWIP tunnel of the eNodeB.

[00119] Example 50 includes the at least one non-transitory machine readable storage medium of claim 49, further comprising instructions which when executed cause the UE to: process an indication, received from the eNodeB, to determine whether the size of the MTU is greater than the size of the LWIP MTU.

[00120] Example 51 includes the at least one non-transitory machine readable storage medium of claim 49, further comprising instructions which when executed cause the UE to: set the size of the MTU equal to the LWIP MTU when the MTU is greater than the size of the LWIP MTU.

[00121] Example 52 includes the at least one non-transitory machine readable storage medium of claim 49, wherein the encapsulation type includes one of an internet protocol (IP) header and payload data for an IP datagram for performing an LWIP operation, an additional IP header, an encapsulation security protocol (ESP) header, the IP header, the payload data, an ESP trailer, and an ESP authorization after applying IP security protocol (IPSec) ESP in the LWIP tunneling for performing the LWIP operation, and the additional IP header, a user datagram protocol (UDP) header, the ESP header, the IP header, the payload data, the ESP trailer, and the ESP authorization after applying a UDP

encapsulation for performing the LWIP operation.

[00122] Example 53 includes the at least one non-transitory machine readable storage medium of claim 52, further comprising instructions which when executed cause the eNodeB to: terminate an LWIP operation with the eNodeB via a WLAN during the LWIP operation; or change the size of the MTU back to an original size of the MTU prior to setting the size of the MTU equal to the size of the LWIP MTU.

[00123] Example 54 includes an apparatus of a User Equipment (UE), the UE configured to communicate with an eNodeB, the apparatus comprising one or more processors and memory configured to: decode a signal, received from the eNodeB, to perform a wireless local area network (WLAN) radio level integration with internet protocol security protocol (IPSec) tunnel (LWIP) operation deactivation procedure; and restore the size of the MTU back to an original value size of the MTU prior to performing the LWIP operation.

[00124] Example 55 includes the apparatus of example 54, wherein the one or more processors and memory are further configured to: process an indication, received from the eNodeB, to terminate the LWIP operation with the eNodeB via a WLAN during the LWIP operation; or change the size of the MTU back to the original size of the MTU prior to setting the size of the MTU equal to the size of the set the size of the MTU according to one or more LWIP parameters.

[00125] Example 56 includes the apparatus of example 55, wherein the one or more LWIP parameters are received from the eNodeB in either a radio resource control message or an information element (IE) of a control message.

[00126] Example 57 includes an apparatus of an eNodeB, the eNodeB configured to communicate with a User Equipment (UE), the apparatus comprising one or more processors and memory configured to: determine an encapsulation type for payload data communicated during a wireless local area network (WLAN) radio level integration with IPsec tunnel (LWIP) operation; set an LWIP maximum transmission unit (MTU) size based on the encapsulation type; and signal a transceiver of the eNodeB to transmit one or more LWIP parameters to the UE to enable the UE to set a size of an MTU based on the size of the LWIP MTU.

[00127] Example 58 includes the apparatus of example 57, wherein the LWIP MTU size is a maximum transmission unit size supported by an LWIP tunnel of the eNodeB, the one or more processors and memory are further configured to signal the transceiver of the eNodeB to transmit to the UE the one or more LWIP parameters in either a radio resource control message or an information element (IE) of a control message for setting the size of the MTU based on the size of the LWIP MTU, or the encapsulation type includes one of an internet protocol (IP) header and payload data for an IP datagram for performing an LWIP operation, an additional IP header, an encapsulation security protocol (ESP) header, the IP header, the payload data, an ESP trailer, and an ESP authorization after applying IP security protocol (IPSec) ESP in the LWIP tunneling for performing the LWIP operation, and the additional IP header, a user datagram protocol (UDP) header, the ESP header, the IP header, the payload data, the ESP trailer, and the ESP authorization after applying a UDP encapsulation for performing the LWIP operation.

[00128] Example 59 includes the apparatus of example 57 or 58, wherein the one or more processors and memory are further configured to: signal the transceiver of the eNodeB to transmit to the UE an indication to determine whether the size of the MTU is greater than the size of the LWIP MTU; signal the transceiver of the eNodeB to transmit to the UE an indication to set the size of the MTU equal to the LWIP MTU when the MTU is greater than the size of the LWIP MTU; establish LWIP tunneling with the UE via a WLAN during the LWIP operation; or perform the LWIP operation with the UE via the WLAN upon setting the cellular MTU equal to the LWIP MTU.

[00129] In Example 60, the subject matter of Example 57 or any of the Examples described herein may further include, wherein the one or more processors and memory are further configured to terminate a LWIP operation with the UE via a WLAN during the LWIP operation upon setting the size of the MTU equal to the size of the LWIP MTU.

[00130] Example 61 includes an apparatus of a User Equipment (UE), the UE configured to communicate with an eNodeB, the apparatus comprising one or more processors and memory configured to: decode a signal, received from the eNodeB, to perform a wireless local area network (WLAN) radio level integration with IPsec tunnel (LWIP) operation activation procedure; process one or more LWIP maximum transmission unit (MTU) parameters in a message, received from the eNodeB, during an wireless local area network (WLAN) radio level integration with IPsec tunnel (LWIP) operation activation procedure, indicating to the UE to set a size of an MTU based on one or more LWIP MTU parameters; and set the size of the MTU according to the one or more LWIP parameters.

[00131] Example 62 includes the apparatus of example 61, wherein the LWIP MTU size is a maximum transmission unit size supported by an LWIP tunnel of the eNodeB, the one or more processors and memory are further configured to process the one or more LWIP parameters that are received from the eNodeB in either a radio resource control message or an information element (IE) of a control message for setting the size of the MTU based on a size of the LWIP MTU according to the one or more LWIP parameters, and the encapsulation type includes one of an internet protocol (IP) header and payload data for an IP datagram for performing an LWIP operation, an additional IP header, an encapsulation security protocol (ESP) header, the IP header, the payload data, an ESP trailer, and an ESP authorization after applying IP security protocol (IPSec) ESP in the LWIP tunneling for performing the LWIP operation, and the additional IP header, a user datagram protocol (UDP) header, the ESP header, the IP header, the payload data, the ESP trailer, and the ESP authorization after applying a UDP encapsulation for performing the LWIP operation.

[00132] Example 63 includes the apparatus of example 61 or 62, wherein the one or more processors and memory are further configured to: process an indication, received from the eNodeB, to determine whether the size of the MTU is greater than the size of the LWIP MTU; set the size of the MTU equal to a size of the LWIP MTU; set the size of the MTU equal to the LWIP MTU when the MTU is greater than the size of the LWIP MTU; establish LWIP tunneling with the eNodeB via a WLAN during the LWIP operation; perform the LWIP operation with the eNodeB via the WLAN upon setting the size of the MTU equal to a size of the LWIP MTU according to the one or more LWIP parameters; terminate an LWIP operation with the eNodeB via a WLAN during the LWIP operation; or change the size of the MTU back to an original size of the MTU prior to setting the size of the MTU equal to the size of the LWIP MTU. [00133] Example 64 includes at least one machine readable storage medium having instructions embodied thereon for an User Equipment (UE) to communicate with a eNodeB, the instructions when executed cause the UE to: decode a signal, received from the eNodeB, to perform a wireless local area network (WLAN) radio level integration with internet protocol security protocol (IPSec) tunnel (LWIP) operation activation procedure; process one or more LWIP maximum transmission unit (MTU) parameters in a message, received from the eNodeB, during an wireless local area network (WLAN) radio level integration with IPsec tunnel (LWIP) operation activation procedure, indicating to the UE to set a size of an MTU based on one or more LWIP maximum parameters; and set the size of the MTU equal to the LWIP MTU according to the one or more LWIP parameters, wherein the LWIP MTU size is a maximum transmission unit size supported by an LWIP tunnel of the eNodeB.

[00134] Example 65 includes the at least one machine readable storage medium of claim 64, further comprising instructions which when executed cause the UE to: process an indication, received from the eNodeB, to determine whether the size of the MTU is greater than the size of the LWIP MTU.

[00135] Example 66 includes the at least one machine readable storage medium of claim 64 or 65, further comprising instructions which when executed cause the UE to: set the size of the MTU equal to the LWIP MTU when the MTU is greater than the size of the LWIP MTU.

[00136] In Example 67, the subject matter of Example 64 or any of the Examples described herein may further include, wherein the encapsulation type includes one of an internet protocol (IP) header and payload data for an IP datagram for performing an LWIP operation, an additional IP header, an encapsulation security protocol (ESP) header, the IP header, the payload data, an ESP trailer, and an ESP authorization after applying IP security protocol (IPSec) ESP in the LWIP tunneling for performing the LWIP operation, and the additional IP header, a user datagram protocol (UDP) header, the ESP header, the IP header, the payload data, the ESP trailer, and the ESP authorization after applying a UDP encapsulation for performing the LWIP operation.

[00137] In Example 68, the subject matter of Example 64 or any of the Examples described herein may further include, further comprising instructions which when executed cause the eNodeB to: terminate an LWIP operation with the eNodeB via a WLAN during the LWIP operation; or change the size of the MTU back to an original size of the MTU prior to setting the size of the MTU equal to the size of the LWIP MTU.

[00138] Example 69 includes an apparatus of a User Equipment (UE), the UE configured to communicate with an eNodeB, the apparatus comprising one or more processors and memory configured to: decode a signal, received from the eNodeB, to perform a wireless local area network (WLAN) radio level integration with internet protocol security protocol (IPSec) tunnel (LWIP) operation deactivation procedure; and restore the size of the MTU back to an original value size of the MTU prior to performing the LWIP operation.

[00139] Example 70 includes the apparatus of example 69, wherein the one or more processors and memory are further configured to: process an indication, received from the eNodeB, to terminate the LWIP operation with the eNodeB via a WLAN during the LWIP operation; or change the size of the MTU back to the original size of the MTU prior to setting the size of the MTU equal to the size of the set the size of the MTU according to one or more LWIP parameters.

[00140] Example 71 includes the apparatus of example 70, wherein the one or more LWIP parameters are received from the eNodeB in either a radio resource control message or an information element (IE) of a control message.

[00141] Example 72 includes a device to communicate with a eNodeB, the device comprising: means for decoding a signal, received from the eNodeB, to perform a wireless local area network (WLAN) radio level integration with internet protocol security protocol (IPSec) tunnel (LWIP) operation activation procedure; means for processing one or more LWIP maximum transmission unit (MTU) parameters in a message, received from the eNodeB, during an wireless local area network (WLAN) radio level integration with IPsec tunnel (LWIP) operation activation procedure, indicating to the UE to set a size of an MTU based on one or more LWIP maximum parameters; and means for setting the size of the MTU equal to the LWIP MTU according to the one or more LWIP parameters, wherein the LWIP MTU size is a maximum transmission unit size supported by an LWIP tunnel of the eNodeB.

[00142] Example 73 includes the device of example 72, further comprising means for processing an indication, received from the eNodeB, to determine whether the size of the MTU is greater than the size of the LWIP MTU.

[00143] Example 74 includes the device of example 72, further comprising means for setting the size of the MTU equal to the LWIP MTU when the MTU is greater than the size of the LWIP MTU.

[00144] Example 75 includes the device of example 72, wherein the encapsulation type includes one of an internet protocol (IP) header and payload data for an IP datagram for performing an LWIP operation, an additional IP header, an encapsulation security protocol (ESP) header, the IP header, the payload data, an ESP trailer, and an ESP authorization after applying IP security protocol (IPSec) ESP in the LWIP tunneling for performing the LWIP operation, and the additional IP header, a user datagram protocol (UDP) header, the ESP header, the IP header, the payload data, the ESP trailer, and the ESP authorization after applying a UDP encapsulation for performing the LWIP operation. [00145] Example 76 includes the device of example 72, further comprising means for: terminating an LWIP operation with the eNodeB via a WLAN during the LWIP operation; or changing the size of the MTU back to an original size of the MTU prior to setting the size of the MTU equal to the size of the LWIP MTU.

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

[00147] Various techniques, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, compact disc-read-only memory (CD-ROMs), hard drives, non-transitory computer readable storage medium, or any other machine-readable storage medium wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the various techniques. 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 may include a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device. The volatile and non-volatile memory and/or storage elements may be a random-access memory (RAM), erasable programmable read only memory (EPROM), flash drive, optical drive, magnetic hard drive, solid state drive, or other medium for storing electronic data. The node and wireless device may also include a transceiver module (i.e., transceiver), a counter module (i.e., counter), a processing module (i.e., processor), and/or a clock module (i.e., clock) or timer module (i.e., timer). One or more programs that may implement or utilize the various techniques described herein may use an application programming interface (API), reusable controls, and the like. Such programs may be implemented in a high level procedural or object oriented programming language to communicate with a computer system. However, the program(s) may be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language, and combined with hardware implementations.

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

[00149] It should be understood that many of the functional units described in this specification have been labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very-large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like. [00150] Modules may also be implemented in software for execution by various types of processors. An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module may not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.

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

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

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

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

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

Claims

CLAIMS What is claimed is:

1. An apparatus of an eNodeB, the eNodeB configured to communicate with a User Equipment (UE), the apparatus comprising one or more processors and memory configured to:

determine an encapsulation type for payload data communicated during a wireless local area network (WLAN) radio level integration with IPsec tunnel (LWIP) operation;

set an LWIP maximum transmission unit (MTU) size based on the encapsulation type; and

signal a transceiver of the eNodeB to transmit one or more LWIP parameters to the UE to enable the UE to set a size of an MTU based on the size of the LWIP MTU.

2. The apparatus of claim 1, wherein the LWIP MTU size is a maximum

transmission unit size supported by an LWIP tunnel of the eNodeB.

3. The apparatus of claim 1 or 2, wherein the one or more processors and

memory are further configured to signal the transceiver of the eNodeB to transmit to the UE the one or more LWIP parameters in either a radio resource control message or an information element (IE) of a control message for setting the size of the MTU based on the size of the LWIP MTU.

4. The apparatus of claim 1, wherein the encapsulation type includes one of an internet protocol (IP) header and payload data for an IP datagram for performing an LWIP operation, an additional IP header, an encapsulation security protocol (ESP) header, the IP header, the payload data, an ESP trailer, and an ESP authorization after applying IP security protocol (IPSec) ESP in the LWIP tunneling for performing the LWIP operation, and the additional IP header, a user datagram protocol (UDP) header, the ESP header, the IP header, the payload data, the ESP trailer, and the ESP authorization after applying a UDP encapsulation for performing the LWIP operation.

5. The apparatus of claim 1 or 2, wherein the one or more processors and

memory are further configured to signal the transceiver of the eNodeB to transmit to the UE an indication to determine whether the size of the MTU is greater than the size of the LWIP MTU.

6. The apparatus of claim 5, wherein the one or more processors and memory are further configured to signal the transceiver of the eNodeB to transmit to the UE an indication to set the size of the MTU equal to the LWIP MTU when the MTU is greater than the size of the LWIP MTU.

7. The apparatus of claim 5, wherein the one or more processors and memory are further configured to establish LWIP tunneling with the UE via a WLAN during the LWIP operation.

8. The apparatus of claim 7, wherein the one or more processors and memory are further configured to perform the LWIP operation with the UE via the WLAN upon setting the cellular MTU equal to the LWIP MTU.

9. The apparatus of claim 8, wherein the one or more processors and memory are further configured to terminate a LWIP operation with the UE via a WLAN during the LWIP operation upon setting the size of the MTU equal to the size of the LWIP MTU.

10. An apparatus of a User Equipment (UE), the UE configured to communicate with an eNodeB, the apparatus comprising one or more processors and memory configured to:

decode a signal, received from the eNodeB, to perform a wireless local area network (WLAN) radio level integration with IPsec tunnel (LWIP) operation activation procedure;

process one or more LWIP maximum transmission unit (MTU) parameters in a message, received from the eNodeB, during an wireless local area network (WLAN) radio level integration with IPsec tunnel (LWIP) operation activation procedure, indicating to the UE to set a size of an MTU based on one or more LWIP MTU parameters; and

set the size of the MTU according to the one or more LWIP parameters.

11. The apparatus of claim 10, wherein the LWIP MTU size is a maximum

transmission unit size supported by an LWIP tunnel of the eNodeB.

12. The apparatus of claim 10 or 11, wherein the one or more processors and memory are further configured to process the one or more LWIP parameters that are received from the eNodeB in either a radio resource control message or an information element (IE) of a control message for setting the size of the MTU based on a size of the LWIP MTU according to the one or more LWIP parameters.

13. The apparatus of claim 10, wherein the encapsulation type includes one of an internet protocol (IP) header and payload data for an IP datagram for performing an LWIP operation, an additional IP header, an encapsulation security protocol (ESP) header, the IP header, the payload data, an ESP trailer, and an ESP authorization after applying IP security protocol (IPSec) ESP in the LWIP tunneling for performing the LWIP operation, and the additional IP header, a user datagram protocol (UDP) header, the ESP header, the IP header, the payload data, the ESP trailer, and the ESP authorization after applying a UDP encapsulation for performing the LWIP operation.

14. The apparatus of claim 10, wherein the one or more processors and memory are further configured to process an indication, received from the eNodeB, to determine whether the size of the MTU is greater than the size of the LWIP MTU.

15. The apparatus of claim 10 or 14, wherein the one or more processors and

memory are further configured to set the size of the MTU equal to a size of the LWIP MTU.

16. The apparatus of claim 10 or 14, wherein the one or more processors and

memory are further configured to set the size of the MTU equal to the LWIP MTU when the MTU is greater than the size of the LWIP MTU.

17. The apparatus of claim 10, wherein the one or more processors and memory are further configured to establish LWIP tunneling with the eNodeB via a WLAN during the LWIP operation.

18. The apparatus of claim 10, wherein the one or more processors and memory are further configured to perform the LWIP operation with the eNodeB via the WLAN upon setting the size of the MTU equal to a size of the LWIP MTU according to the one or more LWIP parameters.

19. The apparatus of claim 10 or 18, wherein the one or more processors and

memory are further configured to terminate an LWIP operation with the eNodeB via a WLAN during the LWIP operation.

20. The apparatus of claim 18, wherein the one or more processors and memory are further configured to change the size of the MTU back to an original size of the MTU prior to setting the size of the MTU equal to the size of the LWIP MTU.

21. A device to communicate with a eNodeB, the instructions when executed cause the UE to:

decode a signal, received from the eNodeB, to perform a wireless local area network (WLAN) radio level integration with internet protocol security protocol (IPSec) tunnel (LWIP) operation activation procedure;

process one or more LWIP maximum transmission unit (MTU) parameters in a message, received from the eNodeB, during an wireless local area network (WLAN) radio level integration with IPsec tunnel (LWIP) operation activation procedure, indicating to the UE to set a size of an MTU based on one or more LWIP maximum parameters; and

set the size of the MTU equal to the LWIP MTU according to the one or more LWIP parameters, wherein the LWIP MTU size is a maximum transmission unit size supported by an LWIP tunnel of the eNodeB.

22. The at least one machine readable storage medium of claim 21, further

comprising instructions which when executed cause the UE to: process an indication, received from the eNodeB, to determine whether the size of the MTU is greater than the size of the LWIP MTU.

23. The at least one machine readable storage medium of claim 21, further

comprising instructions which when executed cause the UE to: set the size of the MTU equal to the LWIP MTU when the MTU is greater than the size of the LWIP MTU.

24. The at least one machine readable storage medium of claim 21, wherein the encapsulation type includes one of an internet protocol (IP) header and payload data for an IP datagram for performing an LWIP operation, an additional IP header, an encapsulation security protocol (ESP) header, the IP header, the payload data, an ESP trailer, and an ESP authorization after applying IP security protocol (IPSec) ESP in the LWIP tunneling for performing the LWIP operation, and the additional IP header, a user datagram protocol (UDP) header, the ESP header, the IP header, the payload data, the ESP trailer, and the ESP authorization after applying a UDP encapsulation for performing the LWIP operation.

25. The at least one machine readable storage medium of claim 21 or 24, further comprising instructions which when executed cause the eNodeB to:

terminate an LWIP operation with the eNodeB via a WLAN during the LWIP operation; or

change the size of the MTU back to an original size of the MTU prior to setting the size of the MTU equal to the size of the LWIP MTU.

26. An apparatus of a User Equipment (UE), the UE configured to communicate with an eNodeB, the apparatus comprising one or more processors and memory configured to:

decode a signal, received from the eNodeB, to perform a wireless local area network (WLAN) radio level integration with internet protocol security protocol (IPSec) tunnel (LWIP) operation deactivation procedure; and

restore the size of the MTU back to an original value size of the MTU prior to performing the LWIP operation.

27. The apparatus of claim 26, wherein the one or more processors and memory are further configured to:

process an indication, received from the eNodeB, to terminate the LWIP operation with the eNodeB via a WLAN during the LWIP operation; or change the size of the MTU back to the original size of the MTU prior to setting the size of the MTU equal to the size of the set the size of the MTU according to one or more LWIP parameters.

28. The apparatus of claim 27, wherein the one or more LWIP parameters are received from the eNodeB in either a radio resource control message or an information element (IE) of a control message.