WO2016167833A1 - Apparatus, system and method of communicating status information between a wlan termination node and a cellular manager - Google Patents

Abstract

Some demonstrative embodiments include devices, systems and/or methods of communicating status information between a Wireless Local Area network (WLAN) Termination (WT) node and a cellular manager. For example, a WT node may be configured to generate a status report message, and to send the status report message 5 to an Evolved Node B (eNB). The status report message may include Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) Radio Access Bearer (E-RAB) status information corresponding to communication of downlink traffic of one or more E-RABs, and UE status information corresponding to a WLAN link 10 with a User Equipment (UE).

Description

APPARATUS, SYSTEM AND METHOD OF COMMUNICATING STATUS INFORMATION BETWEEN A WLAN TERMINATION NODE AND A CELLULAR

MANAGER

CROSS REFERENCE

[001] This application claims the benefit of and priority from US Provisional Patent Application No. 62/147,300 entitled "Alternative Flow Control Mechanism for LTE/WLAN Aggregation", filed April 14, 2015, the entire disclosure of which is incorporated herein by reference.

TECHNICAL FIELD

[002] Some embodiments described herein generally relate to communicating status information between a Wireless Local Area network (WLAN) Termination (WT) node and a cellular manager.

BACKGROUND

[003] A wireless communication device, e.g., a mobile device, may be configured to utilize multiple wireless communication technologies.

[004] For example, a User Equipment (UE) device may be configured to utilize a cellular connection, e.g., a Universal Mobile Telecommunications System (UMTS) cellular connection or a Long Term Evolution (LTE) connection, as well as a wireless-local-area- network (WLAN) connection, e.g., a Wireless-Fidelity (WiFi) connection.

[005] There is a need for efficient interworking, integration and/or management of the cellular and WLAN radio access technologies. BRIEF DESCRIPTION OF THE DRAWINGS

[006] For simplicity and clarity of illustration, elements shown in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity of presentation. Furthermore, reference numerals may be repeated among the figures to indicate corresponding or analogous elements. The figures are listed below.

[007] Fig. 1 is a schematic block diagram illustration of a system, in accordance with some demonstrative embodiments.

[008] Fig. 2 is a schematic flow-chart illustration of a method of communicating status information between a Wireless Local Area Network (WLAN) Termination (WT) node and a cellular manager, in accordance with some demonstrative embodiments.

[009] Fig. 3 is a schematic flow-chart illustration of a method of processing status information communicated between a WT node and a cellular manager, in accordance with some demonstrative embodiments.

[0010] Fig. 4 is a schematic illustration of a product, in accordance with some demonstrative embodiments.

DETAILED DESCRIPTION

[0011] In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of some embodiments. However, it will be understood by persons of ordinary skill in the art that some embodiments may be practiced without these specific details. In other instances, well-known methods, procedures, components, units and/or circuits have not been described in detail so as not to obscure the discussion.

[0012] Discussions herein utilizing terms such as, for example, "processing", "computing", "calculating", "determining", "establishing", "analyzing", "checking", or the like, may refer to operation(s) and/or process(es) of a computer, a computing platform, a computing system, or other electronic computing device, that manipulate and/or transform data represented as physical (e.g., electronic) quantities within the computer's registers and/or memories into other data similarly represented as physical quantities within the computer's registers and/or memories or other information storage medium that may store instructions to perform operations and/or processes.

[0013] The terms "plurality" and "a plurality", as used herein, include, for example, "multiple" or "two or more". For example, "a plurality of items" includes two or more items.

[0014] References to "one embodiment," "an embodiment," "demonstrative embodiment," "various embodiments," etc., indicate that the embodiment(s) so described may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes the particular feature, structure, or characteristic. Further, repeated use of the phrase "in one embodiment" does not necessarily refer to the same embodiment, although it may.

[0015] As used herein, unless otherwise specified the use of the ordinal adjectives "first," "second," "third," etc., to describe a common object, merely indicate that different instances of like objects are being referred to, and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.

[0016] Some embodiments may be used in conjunction with various devices and systems, for example, a Personal Computer (PC), a desktop computer, a mobile computer, a laptop computer, a notebook computer, a tablet computer, a Smartphone device, a server computer, a handheld computer, a handheld device, a Personal Digital Assistant (PDA) device, a handheld PDA device, an on-board device, an off-board device, an Internet of Things (IoT) device, a hybrid device, a vehicular device, a non-vehicular device, a mobile or portable device, a consumer device, a non-mobile or non-portable device, a wireless communication station, a wireless communication device, a wireless Access Point (AP), a wired or wireless router, a wired or wireless modem, a video device, an audio device, an audio-video (A/V) device, a wired or wireless network, a wireless area network, a cellular network, a cellular node, a cellular device, a Wireless Local Area Network (WLAN), a Multiple Input Multiple Output (MIMO) transceiver or device, a Single Input Multiple Output (SIMO) transceiver or device, a Multiple Input Single Output (MISO) transceiver or device, a device having one or more internal antennas and/or external antennas, Digital Video Broadcast (DVB) devices or systems, multi- standard radio devices or systems, a wired or wireless handheld device, e.g., a Smartphone, a Wireless Application Protocol (WAP) device, vending machines, sell terminals, and the like.

[0017] Some embodiments may be used in conjunction with devices and/or networks operating in accordance with existing 3rd Generation Partnership Project (3GPP) and/or Long Term Evolution (LTE) specifications (including 3 GPP TS 36.300 ( "TS 36.300 Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2, version 11.7.0 Release 11 ", September 2013); 3GPP TS 36.463 (TS 36.463 Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and Wireless LAN (WLAN); Xw application protocol (XwAP)); and/or 3 GPP TS 36.425) and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing Wireless-Gigabit-Alliance (WGA) specifications (Wireless Gigabit Alliance, Inc WiGig MAC and PHY Specification Version 1.1, April 2011, Final specification) and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing IEEE 802.11 standards (IEEE 802.11-2012, IEEE Standard for Information technology— Telecommunications and information exchange between systems Local and metropolitan area networks-Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications, March 29, 2012), and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing IEEE 802.16 standards (IEEE-Std 802.16, 2009 Edition, Air Interface for Fixed Broadband Wireless Access Systems; IEEE-Std 802.16e, 2005 Edition, Physical and Medium Access Control Layers for Combined Fixed and Mobile Operation in Licensed Bands; amendment to IEEE Std 802.16-2009, developed by Task Group m) and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing WirelessHD™ specifications and/or future versions and/or derivatives thereof, units and/or devices which are part of the above networks, and the like.

[0018] Some embodiments may be used in conjunction with one or more types of wireless communication signals and/or systems, for example, Radio Frequency (RF), Frequency- Division Multiplexing (FDM), Orthogonal FDM (OFDM), Single Carrier Frequency Division Multiple Access (SC-FDMA), Time-Division Multiplexing (TDM), Time-Division Multiple Access (TDM A), Extended TDMA (E-TDMA), General Packet Radio Service (GPRS), extended GPRS, Code-Division Multiple Access (CDMA), Wideband CDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrier CDMA, Multi-Carrier Modulation (MDM), Discrete Multi-Tone (DMT), Bluetooth®, Global Positioning System (GPS), Wireless Fidelity (Wi-Fi), Wi-Max, ZigBee™, Ultra-Wideband (UWB), Global System for Mobile communication (GSM), second generation (2G), 2.5G, 3G, 3.5G, 4G, Fifth Generation (5G) mobile networks, 3GPP, Long Term Evolution (LTE) cellular system, LTE advance cellular system, High-Speed Downlink Packet Access (HSDPA), High-Speed Uplink Packet Access (HSUPA), High-Speed Packet Access (HSPA), HSPA+, Single Carrier Radio Transmission Technology (1XRTT), Evolution-Data Optimized (EV-DO), Enhanced Data rates for GSM Evolution (EDGE), and the like. Other embodiments may be used in various other devices, systems and/or networks.

[0019] The term "wireless device", as used herein, includes, for example, a device capable of wireless communication, a communication device capable of wireless communication, a communication station capable of wireless communication, a portable or non-portable device capable of wireless communication, or the like. In some demonstrative embodiments, a wireless device may be or may include a peripheral that is integrated with a computer, or a peripheral that is attached to a computer. In some demonstrative embodiments, the term "wireless device" may optionally include a wireless service.

[0020] The term "communicating" as used herein with respect to a communication signal includes transmitting the communication signal and/or receiving the communication signal. For example, a communication unit, which is capable of communicating a communication signal, may include a transmitter to transmit the communication signal to at least one other communication unit, and/or a communication receiver to receive the communication signal from at least one other communication unit. The verb communicating may be used to refer to the action of transmitting or the action of receiving. In one example, the phrase "communicating a signal" may refer to the action of transmitting the signal by a first device, and may not necessarily include the action of receiving the signal by a second device. In another example, the phrase "communicating a signal" may refer to the action of receiving the signal by a first device, and may not necessarily include the action of transmitting the signal by a second device.

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

[0022] The term "antenna", as used herein, may include any suitable configuration, structure and/or arrangement of one or more antenna elements, components, units, assemblies and/or arrays. In some embodiments, the antenna may implement transmit and receive functionalities using separate transmit and receive antenna elements. In some embodiments, the antenna may implement transmit and receive functionalities using common and/or integrated transmit/receive elements. The antenna may include, for example, a phased array antenna, a single element antenna, a dipole antenna, a set of switched beam antennas, and/or the like.

[0023] The term "cell", as used herein, may include a combination of network resources, for example, downlink and optionally uplink resources. The resources may be controlled and/or allocated, for example, by a node (also referred to as a "base station"), or the like. The linking between a carrier frequency of the downlink resources and a carrier frequency of the uplink resources may be indicated in system information transmitted on the downlink resources.

[0024] Some demonstrative embodiments are described herein with respect to a LTE network. However, other embodiments may be implemented in any other suitable cellular network or system, e.g., a Universal Mobile Telecommunications System (UMTS) cellular system, a GSM network, a 3G cellular network, a 4G cellular network, a 4.5G network, a 5G cellular network, a WiMAX cellular network, and the like. [0025] Some demonstrative embodiments are described herein with respect to a WLAN system, a WiFi system, and/or a WiGig system. However, other embodiments may be implemented in any other suitable non-cellular network.

[0026] Some demonstrative embodiments are described herein with respect to a WLAN Termination (WT) node. However, other embodiments may be implemented in any other WLAN access device and/or WLAN access manager node and/or interface.

[0027] Some demonstrative embodiments may be used in conjunction with a Heterogeneous Network (HetNet), which may utilize a deployment of a mix of technologies, frequencies, cell sizes and/or network architectures, e.g., including cellular, millimeter wave ("mmWave" or "mmW"), and/or the like. In one example, the HetNet may include a radio access network having layers of different-sized cells ranging from large macrocells to small cells, for example, picocells and femtocells. Other embodiments may be used in conjunction with any other suitable wireless communication network.

[0028] Other embodiments may be used in conjunction with any other suitable wireless communication network.

[0029] Reference is now made to Fig. 1 , which schematically illustrates a block diagram of a system 100, in accordance with some demonstrative embodiments.

[0030] As shown in Fig. 1, in some demonstrative embodiments, system 100 may include one or more wireless communication devices capable of communicating content, data, information and/or signals via one or more wireless mediums 108. For example, system 100 may include at least one User Equipment (UE) 102 capable of communicating with one or more wireless communication networks, e.g., as described below.

[0031] Wireless mediums 108 may include, for example, a radio channel, a cellular channel, an RF channel, a WiFi channel, an IR channel, and the like. One or more elements of system 100 may optionally be capable of communicating over any suitable wired communication links.

[0032] In some demonstrative embodiments, system 100 may include at least one cellular manager 104 to manage communication of a cellular network, e.g., as described below.

[0033] In some demonstrative embodiments, cellular manager 104 may include, may operate as, and/or may perform the functionality of, an Evolved Node B (eNB). For example, cellular manager 104 may be configured to perform radio resource management (RRM), radio bearer control, radio admission control (access control), connection mobility management, resource scheduling between UEs and eNB radios, e.g., Dynamic allocation of resources to UEs in both uplink and downlink, header compression, link encryption of user data streams, packet routing of user data towards a destination, e.g., another eNB or an Evolved Packet Core (EPC), scheduling and/or transmitting paging messages, e.g., incoming calls and/or connection requests, broadcast information coordination, measurement reporting, and/or any other operations, communications, and/or functionality.

[0034] In other embodiments, cellular manager 104 may include any other functionality and/or may perform the functionality of any other cellular node, network controller, base station or any other node or network device.

[0035] In one example, cellular manager 104 may be part of a UMTS. According to this example, cellular manager 104 may perform the functionality of a Radio Network Controller (RNC), which may control a plurality of Node B devices 157. For example, the node B may be configured to communicate directly with UEs, e.g., including UE 102, for example, using a Wideband Code Division Multiple Access (WCDMA) and/or Time Division Synchronous Code Division Multiple Access (TD-SCDMA) air interface technology. The RNC may include, for example, a UMTS RNC configured to control the Node B devices 157.

[0036] In some demonstrative embodiments, system 100 may include a WLAN Termination (WT) node 106, which may be configured to terminate a WLAN network interface, e.g., as described herein.

[0037] In some demonstrative embodiments, WT node 106 may be configured to manage access to a non-cellular network 107, for example, a WLAN, e.g., a Basic Service Set (BSS).

[0038] In some demonstrative embodiments, one or more functionalities of WT node 106 may be implemented, for example, as part of a WLAN access device, for example, as part of a WLAN Access Point (AP), or a WLAN Access Controller (AC), as part of another device, or as a standalone device.

[0039] In other embodiments, WT node 106 may include any other functionality and/or may perform the functionality of any other device capable of controlling and/or managing WLAN radio access to one or more wired networks.

[0040] In one example, WT bode 106 may include, operate as, and/or perform the functionality of, an AP, e.g., configured to communicate directly with UE 102 via a WLAN link. [0041] In another example, WT bode 106 may include, operate as, and/or perform the functionality of, an AC. According to this example, WT node 106 may control a plurality of AP devices, e.g., including Lightweight Access Point (LAP) devices 158.

[0042] In some demonstrative embodiments, UE 102 may include, for example, a Mobile Device (MD), a Station (STA), a mobile computer, a laptop computer, a notebook computer, a tablet computer, an Ultrabook™ computer, an Internet of Things (IoT) device, a wearable device, a sensor device, a mobile internet device, a handheld computer, a handheld device, a storage device, a PDA device, a handheld PDA device, an on-board device, an off-board device, a hybrid device (e.g., combining cellular phone functionalities with PDA device functionalities), a consumer device, a vehicular device, a non-vehicular device, a mobile or portable device, a mobile phone, a cellular telephone, a PCS device, a mobile or portable GPS device, a DVB device, a relatively small computing device, a non-desktop computer, a "Carry Small Live Large" (CSLL) device, an Ultra Mobile Device (UMD), an Ultra Mobile PC (UMPC), a Mobile Internet Device (MID), an "Origami" device or computing device, a video device, an audio device, an A/V device, a gaming device, a media player, a Smartphone, or the like.

[0043] In some demonstrative embodiments, UE 102, cellular manager 104 and/or WT node 106 may include one or more communication interfaces to perform communication between UE 102, cellular manager 104, WT node 106 and/or with one or more other wireless communication devices, e.g., as described below.

[0044] Some demonstrative embodiments include an interface 199 (also referred to as "the access device interface", "the horizontal interface", "the "Xw interface", "the X2-W interface" or "the cellularAVLAN interface"), which may include circuitry and/or logic configured to interface, e.g., directly or indirectly, between a cellular network element, e.g., cellular manager 104, and a WLAN element, e.g., WT node 106, as described in detail below.

[0045] In some demonstrative embodiments, interface 199 may be implemented to interface between an eNB and a WT node, e.g., as described below. However, in other embodiments, the cellularAVLAN interface 199 may be implemented to directly interface between any other cellular device and any other WLAN device. In one example, the cellularAVLAN interface 199 may be implemented to directly interface between an eNB and a WLAN AP or WLAN AC. In another example, the cellularAVLAN interface 199 may be implemented to directly interface between a UMTS RNC and a WT node. In another example, the cellularAVLAN interface 199 may be implemented to directly interface between a UMTS RNC and a WLAN AP or AC.

[0046] In some demonstrative embodiments, interface 199 may be utilized to enhance and/or increase the efficiency of interworking, integration and/or management of the cellular and WLAN radio access technologies, e.g., as described below.

[0047] In some demonstrative embodiments, interface 199 may be configured to perform and/or support one or more aggregation operations and/or functionalities, for example, to transfer traffic, e.g., in addition to transferring control plane information.

[0048] In some demonstrative embodiments, interface 199 may be utilized to improve efficiency of resource management, to provide efficient load balancing, and/or to improve mobility between Radio Access Technology (RAT) networks, e.g., as described below.

[0049] In some demonstrative embodiments, cellular manager 104 may include an interface ("Core Network (CN) interface") 146, e.g., a vertical interface, including circuitry and/or logic configured to communicate with one or more elements of a CN 183, e.g., an Evolved Packet Core (EPC).

[0050] In some demonstrative embodiments, CN interface 146 may include an SI vertical interface configured to communicate between cellular manager 104 and a Serving Gateway (S-GW) 185 according to an SI protocol, e.g., if cellular manager 104 performs the functionality of an eNB, e.g., capable of communicating with a Mobility Management Entity (MME) over an SI interface. According to this example, S-GW 187 may interface between cellular manager 104 and a Packet Data Network (PDN) Gateway (P-GW) 187.

[0051] In other embodiments, CN interface 146 may include any other vertical interface with one or more elements of CN 183. For example, cellular manger 104 may perform the functionality of an RNC, e.g., in a UMTS system. According to this example, CN interface 146 may include an Interface Unit Circuit Switch (Iu-CS) interface and/or an Interface Unit Packet Switch (Iu-PS) interface, to interface between the RNC and one or more packet- switched or circuit- switched CN elements.

[0052] In some demonstrative embodiments, cellular manager 104 may include an interface including circuitry and/or logic to communicate user plane traffic, directly or indirectly, between CN 183 and UE 102. [0053] In some demonstrative embodiments, cellular manager 104 may communicate the user plane traffic directly with UE 102, for example, if cellular manager 104 performs the functionality of an eNB. According to these embodiments, cellular manager 104 may include an air interface, for example, a cellular transceiver (TRx) 167, including circuitry and/or logic configured to communicate with UE 102 via a cellular link.

[0054] In other embodiments, cellular manager 104 may communicate the user plane traffic with UE 102 via Node B 157, e.g., if cellular manager 104 performs the functionality of an RNC. According to these embodiments, cellular manager 104 may include a Node B interface 161 to communicate between the RNC and Node B 157. For example, Node B interface 161 may include an Interface Unit b (Iub).

[0055] In some demonstrative embodiments, cellular manager 104 may include a WT node interface 169 including circuitry and/or logic configured to communicate with WT node 106, e.g., as described below. In one example, interface 169 may include an AP interface, e.g., if WLAN access device 106 performs the functionality of an AP. In another example, interface 169 may include an AC interface, e.g., if WLAN access device 106 performs the functionality of an AC.

[0056] In some demonstrative embodiments, WT node 106 may include a cell manager interface ("the cellular interface") 192 including circuitry and/or logic configured to communicate with cellular manager 104, e.g., as described below. In one example, interface 192 may include an eNB interface, e.g., if cellular manager 104 performs the functionality of an eNB. In another example, interface 192 may include a RNC interface, e.g., if cellular manager 104 performs the functionality of a RNC.

[0057] In some demonstrative embodiments, interfaces 169 and 192 may be configured to communicate between cellular manager 104 and WT node 106 via a direct link of interface 199, e.g., as described below.

[0058] In some demonstrative embodiments, interface 199 may include a Point to Point (P2P) link, e.g., as described below.

[0059] In some demonstrative embodiments, interface 199 may be implemented by any wired and/or wireless link, e.g., using any suitable, Physical Layer (PHY) components and/or protocols.

[0060] In some demonstrative embodiments, interface 199 may include a wired link. [0061] In some demonstrative embodiments, interface 199 may include a wireless link, for example, a microwave link or a WLAN link, a WiFi link, a Bluetooth link, and/or any other wireless link. In some demonstrative embodiments, interface 199 may include any wired link.

[0062] In some demonstrative embodiments, interface 199 may use a Transmission Control Protocol/Internet Protocol (TCP/IP) as a transport protocol. Interface 199 may be configured to use, for example, a Stream Control Transmission Protocol (SCTP), e.g., on top of the transport protocol. Interface 199 may use, for example, an Application Protocol, for example, an Xw Application Protocol (Xw-AP), for example, on top of the SCTP, e.g., for the control plane. Interface 199 may use, for example, a general packet radio service (GPRS) Tunneling Protocol User Plane (GTP-U) protocol, e.g., for the user plane. In other embodiments, interface 199 may use any other additional or alternative protocols.

[0063] In some demonstrative embodiments, WT node 106 may include a network interface 196 including circuitry and/or logic configured to communicate network traffic with a wired network 177, e.g., the Internet or any other network.

[0064] In some demonstrative embodiments, WLAN access device 104 may include a WLAN interface 193 including circuitry and/or logic configured to communicate the network traffic and/or any other traffic with UE 102 via a WLAN, directly or indirectly.

[0065] In some demonstrative embodiments, WT node 106 may communicate directly with UE 102 via WLAN link, for example, if WT node 106 operates as, or performs the functionality of, an AP. According to these embodiments, WLAN interface 193 may include a WLAN radio 194 including circuitry and/or logic configured to communicate the network traffic and/or any other traffic directly with UE 102, e.g., via a WLAN link between WT node 106 and UE 102, for example, if WT node 106 operates as, or performs the functionality of, an AP.

[0066] In some demonstrative embodiments, WT node 106 may indirectly communicate with UE 102, for example, if WT node 106 performs the functionality of an AC, or if WT node is an entity, which is separate from the WLAN AC or WLAN AP. According to these embodiments, WLAN interface 193 may include, for example, an AP interface, e.g., a LAP interface 159, to communicate the network traffic and/or any other traffic with LAP 158.

[0067] In some demonstrative embodiments, WLAN interface 193 may include any other additional or alternative interfaces to directly and/or indirectly communicate via the WLAN. [0068] In some demonstrative embodiments, UE 102 may include a WLAN transceiver (TRx) 163 including circuitry and/or logic configured to communicate with a WLAN device, e.g., with WT node 106 and/or with LAP 158, via the WLAN link.

[0069] In some demonstrative embodiments, UE 102 may include a cellular transceiver (TRx) 165 including circuitry and/or logic configured to communicate with a cellular device, e.g., cellular manager 104 and/or Node B 157, via the cellular link.

[0070] In some demonstrative embodiments, WT node 106 may include at least one controller 149 to control one or more operations, functionalities and/or communications performed by WT node 106; cellular manager 104 may include at least one controller 144 to control one or more operations, functionalities and/or communications performed by cellular manager 104; and/or UE 102 may include at least one controller 145 to control one or more functionalities and/or communications performed by UE 102, e.g., as described below.

[0071] In some demonstrative embodiments, controllers 149, 144 and/or 145 may include, or may be implemented, using suitable circuitry and/or logic, e.g., controller circuitry and/or logic, scheduler circuitry and/or logic, processor circuitry and/or logic, memory circuitry and/or logic, and/or any other circuitry and/or logic, which may be configured to perform at least part of the functionality of controllers 149, 144 and/or 145. Additionally or alternatively, one or more functionalities of controller 149, 144 and/or 145 may be implemented by logic, which may be executed by a machine and/or one or more processors, e.g., as described below.

[0072] In some demonstrative embodiments, WLAN TRx 163, cellular TRx 165, cellular TRx 167 and/or WLAN radio 194 may include one or more wireless transmitters, receivers and/or transceivers including circuitry and/or logic to process, encode, decode, send and/or receive wireless communication signals, RF signals, frames, blocks, transmission streams, packets, messages, data items, and/or data.

[0073] In some demonstrative embodiments, WLAN TRx 167 and/or WLAN radio 194 may include one or more wireless receivers (Rx) including circuitry and/or logic to receive wireless communication signals, RF signals, frames, blocks, transmission streams, packets, messages, data items, and/or data; and/or one or more wireless transmitters (Tx) including circuitry and/or logic to send wireless communication signals, RF signals, frames, blocks, transmission streams, packets, messages, data items, and/or data. For example, WLAN TRx 167 and/or WLAN radio 194 may include circuitry; logic; Radio Frequency (RF) elements, circuitry and/or logic; baseband elements, circuitry and/or logic; modulation elements, circuitry and/or logic; demodulation elements, circuitry and/or logic; amplifiers; analog to digital and/or digital to analog converters; filters; and/or the like.

[0074] In some demonstrative embodiments, cellular TRx 167 and/or cellular TRx 165 may include a multiple input multiple output (MIMO) transmitters receivers system (not shown), which may be capable of performing antenna beamforming methods, if desired. In other embodiments, cellular TRx 167 and/or cellular TRx 165 may include any other transmitters and/or receivers.

[0075] In some demonstrative embodiments, cellular TRx 167 and/or cellular TRx 165 may include LTE, WCDMA and/or TD-SCDMA modulator and/or demodulator circuitry (not shown) configured to modulate and/or demodulate downlink signals to be communicated over downlink channels, e.g., between cellular manager 104 and UE 102, and/or uplink signals to be communicated over uplink channels, e.g., between UE 102 and cellular manager 104. In other embodiments, cellular TRx 167 and/or cellular TRx 165 may include any other modulators and/or demodulators.

[0076] In some demonstrative embodiments, cellular TRx 167 and/or cellular TRx 165 may include a turbo decoder and/or a turbo encoder (not shown) including circuitry and/or logic for encoding and/or decoding data bits into data symbols, if desired. In some demonstrative embodiments, cellular TRx 167 and/or cellular TRx 165 may include OFDM and/or SC- FDMA modulators and/or demodulators (not shown) configured to communicate OFDM signals over downlink (DL) channels, and/or SC-FDMA signals over uplink (UL) channels.

[0077] In some demonstrative embodiments, UE 102 may establish a WLAN link with a WLAN AP. For example, WLAN TRx 163 may perform the functionality of one or more STAs, e.g., one or more WiFi STAs, WLAN STAs, and/or DMG STAs. The WLAN link may include an uplink and/or a downlink. The WLAN downlink may include, for example, a unidirectional link from the WLAN AP to the one or more STAs. The uplink may include, for example, a unidirectional link from a STA to the WLAN AP.

[0078] In some demonstrative embodiments, at least part of the functionality of controller 144 may be implemented by an integrated circuit, for example, a chip, e.g., a System on Chip (SoC). In one example, the chip or SoC may be configured to perform one or more functionalities of cellular transceiver 167 and/or WT node interface 169. For example, the chip or SoC may include one or more elements of controller 144, and/or one or more elements of cellular transceiver 167 and/or WT node interface 169. In one example, controller 144, cellular transceiver 167, and WT node interface 169 may be implemented as part of the chip or SoC.

[0079] In other embodiments, controller 144, cellular transceiver 167 and/or WT node interface 169 may be implemented by one or more additional or alternative elements of cellular manager 104.

[0080] In some demonstrative embodiments, at least part of the functionality of controller 149 may be implemented by an integrated circuit, for example, a chip, e.g., a SoC. In one example, the chip or SoC may be configured to perform one or more functionalities of cellular transceiver WLAN interface 193 and/or cellular manager interface 192. For example, the chip or SoC may include one or more elements of controller 149, and/or one or more elements of WLAN interface 193 and/or cellular manager interface 192. In one example, controller 149, WLAN interface 193 and cellular manager interface 192may be implemented as part of the chip or SoC.

[0081] In other embodiments, controller 149, WLAN interface 193 and/or cellular manager interface 192 may be implemented by one or more additional or alternative elements of WT node 106.

[0082] In some demonstrative embodiments, UE 102, cellular manager 104, and/or WT node 106, may include, or may be associated with, one or more antennas. In one example, WLAN TRx 163 and/or cellular TRx 165 may be associated with at least two antennas, e.g., antennas 112 and 114, or any other number of antennas, e.g., one antenna or more than two antennas; cellular TRx 167 may be associated with at least two antennas, e.g., antennas 132 and 134, or any other number of antennas, e.g., one antenna or more than two antennas; and/or WLAN radio 194 may be associated with one or more antennas 135.

[0083] In some demonstrative embodiments, antennas 112, 114, 132, 134 and/or 135 may include any type of antennas suitable for transmitting and/or receiving wireless communication signals, blocks, frames, transmission streams, packets, messages and/or data. For example, antennas 112, 114, 132, 134 and/or 135 may include any suitable configuration, structure and/or arrangement of one or more antenna elements, components, units, assemblies and/or arrays. For example, antennas 112, 114, 132, 134 and/or 135 may include a phased array antenna, a dipole antenna, a single element antenna, a set of switched beam antennas, and/or the like. [0084] In some embodiments, antennas 112, 114, 132, 134 and/or 135 may implement transmit and receive functionalities using separate transmit and receive antenna elements. In some embodiments, antennas 112, 114, 132, 134 and/or 135 may implement transmit and receive functionalities using common and/or integrated transmit/receive elements.

[0085] In some demonstrative embodiments, cellular manager 104, WT node 106, and/or UE 102 may also include, for example, one or more of a processor, an input unit, an output unit, a memory unit, and/or a storage unit. For example, cellular manager 104 may include a processor 173 and/or a memory 174; WT node 106 may include a processor 175 and/or a memory 176; and/or UE 102 may include a memory 151, a processor 152, an input unit 153, an output unit 154, and/or a storage unit 155. UE 102, cellular manager 104 and/or WT node 106 may optionally include other suitable hardware components and/or software components. In some demonstrative embodiments, some or all of the components of one or more of UE 102, cellular manager 104 and/or WT node 106 may be enclosed in a common housing or packaging, and may be interconnected or operably associated using one or more wired or wireless links. In other embodiments, components of one or more of UE 102, cellular manager 104 and/or WT node 106 may be distributed among multiple or separate devices.

[0086] In some demonstrative embodiments, processors 173, 175 and/or 152 may include, for example, a Central Processing Unit (CPU), a Digital Signal Processor (DSP), one or more processor cores, a single-core processor, a dual-core processor, a multiple-core processor, a microprocessor, a host processor, a controller, a plurality of processors or controllers, a chip, a microchip, one or more circuits, circuitry, a logic unit, an Integrated Circuit (IC), an Application-Specific IC (ASIC), or any other suitable multi-purpose or specific processor or controller. For example, processor 173 may execute instructions, for example, of an Operating System (OS) of cellular manager 104 and/or of one or more suitable applications; processor 175 may execute instructions of an OS of WT node 106 and/or of one or more suitable applications; and/or processor 152 may execute instructions of an OS of UE 102 and/or of one or more suitable applications.

[0087] In some demonstrative embodiments, input unit 153 may include, for example, a keyboard, a keypad, a mouse, a touch-screen, a touch-pad, a track-ball, a stylus, a microphone, or other suitable pointing device or input device. Output unit 154 includes, for example, a monitor, a screen, a touch-screen, a flat panel display, a Light Emitting Diode (LED) display unit, a Liquid Crystal Display (LCD) display unit, a plasma display unit, one or more audio speakers or earphones, or other suitable output devices. [0088] In some demonstrative embodiments, memory unit 174, 176 and/or 151 may include, for example, a Random Access Memory (RAM), a Read Only Memory (ROM), a Dynamic RAM (DRAM), a Synchronous DRAM (SD-RAM), a flash memory, a volatile memory, a non- volatile memory, a cache memory, a buffer, a short term memory unit, a long term memory unit, or other suitable memory units. Storage unit 155 includes, for example, a hard disk drive, a floppy disk drive, a Compact Disk (CD) drive, a CD-ROM drive, a DVD drive, or other suitable removable or non-removable storage units. For example, memory unit 174 may store data processed by cellular manager 104; and/or memory unit 176 may store data processed by WT node 106.

[0089] In some demonstrative embodiments, UE 102 may be configured to utilize a cellular connection, e.g., a LTE cellular connection or any other cellular connection, to communicate with cellular manager 104, and a WLAN connection, e.g., a Wireless-Fidelity (WiFi) connection, a mmWave connection, a wireless P2P connection, or any other WLAN, e.g., WiGig, connection, to communicate with a WLAN AP connected to, or implemented by, WT node 106.

[0090] In some demonstrative embodiments, one or more elements of system 100 may perform the functionality of a HetNet, which may utilize a deployment of a mix of technologies, frequencies, cell sizes and/or network architectures, for example, including cellular, WLAN, and/or the like.

[0091] For example, the HetNet may be configured to provide a service through a first wireless communication environment, e.g., a cellular network, and to maintain the service when switching to another communication environment, e.g., WLAN. The HetNet architecture may enable utilizing a mixture of wireless communication environments, e.g., a WLAN environment and a cellular environment, for example, to optimally respond to rapid changes in customer demand, reduce power consumption, reduce cost, increase efficiency and/or achieve any other benefit.

[0092] In one example, system 100 may utilize a Multi-tier, Multi-Radio Access Technology (Multi-RAT) Het-Net architecture, including a tier of small cells, e.g., pico, femto, relay stations, WiFi APs, and the like, overlaid on top of a macro cellular deployment to augment network capacity.

[0093] In another example, system 100 may utilize Multi-RAT small cells integrating multiple radios such as WiFi and 3 GPP air interfaces in a single infrastructure device. [0094] In other embodiments, system 100 may implement any other architecture and/or deployment.

[0095] In some demonstrative embodiments, cellular manager 104 and/or WT node 106 may be configured to communicate via interface 199, for example, to enhance and/or increase the efficiency of interworking, integration and/or management of the cellular and WLAN radio access technologies, e.g., as described below.

[0096] In some demonstrative embodiments, cellular manager 104 and/or WT node 106 may be configured to communicate via interface 199, for example, at least to control LTE/WLAN aggregation, and/or to communicate traffic for LTE/WLAN aggregation.

[0097] In some demonstrative embodiments, cellular manager 104 and/or WT node 106 may be configured to communicate via interface 199, for example, at least to transport data packets, e.g., Packet Data Convergence Protocol (PDCP) Protocol Data Units (PDUs), between cellular manager 104 and WT node 106, to control aggregation, e.g., from cellular manager 104 to WT node 106, and/or to gather statistics and/or other information, e.g., from WT node 106 to cellular manager 104, e.g., as described below.

[0098] In some demonstrative embodiments, cellular manager 104 and/or WT node 106 may be configured to communicate via interface 199, for example, to improve efficiency of resource management, to provide efficient load balancing, and/or to improve mobility between Radio Access Technology (RAT) networks, e.g., as described below.

[0099] In some demonstrative embodiments, cellular manager 104 and/or WT node 106 may be configured according to a network architecture of a non-collocated LTE/WLAN aggregation, e.g., in which cellular manager 104 and WT node 106 are not collocated as part of an integrated device and/or in which interface 199 is not an internal interface.

[00100] In some demonstrative embodiments, cellular manager 104 and/or WT node 106 may be configured to communicate, e.g., via interface 199, in accordance with an LTE/WLAN aggregation (LWA) architecture, for example, an LWA split bearer architecture, e.g., as described below.

[00101] In some demonstrative embodiments, the LWA split bearer architecture may be configured to enable cellular manager 104 to send packets belonging to a single bearer either directly to UE 102 or via WT node 106. [00102] In some demonstrative embodiments, the LWA split bearer architecture may be configured to support packets in the form of PDCP PDUs.

[00103] In other embodiments, cellular manager 104 and/or WT node 106 may be configured to communicate in accordance with any other additional or alternative architecture.

[00104] In some demonstrative embodiments, controller 144 may control, cause, and/or trigger cellular TRx 167 to communicate with UE 102 traffic of at least one Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) Radio Access Bearer (E-RAB).

[00105] In some demonstrative embodiments, controller 144 may be configured to cause, control and/or trigger cellular manager 104 to route at least part of the traffic of the E-RAB via WT node 106, e.g., as described below.

[00106] In some demonstrative embodiments, cellular manager 104 and/or WT node 106 may be configured to communicate user plane messages and/or control plane messages via interface 199, e.g., as described below.

[00107] In some demonstrative embodiments, cellular manager 104 and/or WT node 106 may be configured to communicate via interface 199 user plane packets including user plane traffic corresponding to UE 102, e.g., as described below.

[00108] In some demonstrative embodiments, the user plane packets may include downlink traffic to be provided to UE 102, e.g., as described below.

[00109] In some demonstrative embodiments, controller 144 may be configured to control routing at least part of the downlink traffic to UE 102 via WT node 106, e.g., as described below.

[00110] In some demonstrative embodiments, the downlink traffic may include downlink traffic from CN 183, e.g., as described below.

[00111] In some demonstrative embodiments, the downlink traffic may include PDCP PDUs, e.g., as described below.

[00112] In some demonstrative embodiments, cellular manager 104 may receive the downlink traffic, e.g., via CN interface 146. Cellular manager 104 may cause, trigger and/or control interface 169 to send the downlink traffic to WT node 106. According to these embodiments, WT node 106 may receive the downlink traffic from cellular manager 104, e.g., via interface 192, and may send the downlink traffic to UE 102 via the WLAN. [00113] In one example, WT node 106 may directly transmit the downlink traffic to UE 102, e.g., via WLAN radio 194, for example, if WT node 106 operates as, or performs the functionality of, an AP.

[00114] In another example, WT node 106 may send the CN downlink traffic to UE 102 via a WLAN AP, for example, if WLAN access device 106 does not operate as, or does not perform the functionality of, a WLAN AP.

[00115] In some demonstrative embodiments, transferring the downlink traffic between cellular manager 104 and WT node 106 via interface 199 may at least enable, for example, to enhance, e.g., optimize, mobility of UE 102 between the cellular and WLAN radio networks.

[00116] In some demonstrative embodiments, cellular node 104 and/or WT node 106 may be configured to implement a control flow mechanism, which may be configured to enable cellular manager 104 to control, manage, and/or adjust the flow of PDUs for a particular user, e.g., UE 102, which may be sent to WT node 106 via interface 199, for example, based at least on a WLAN downlink rate, for example, an actual downlink rate via the WLAN to the particular user.

[00117] In some demonstrative embodiments, implementing the flow control mechanism may be important, for example, at least for realizing LTEAVLAN aggregation performance gains, and/or for one or more additional or alternative reasons and/or considerations. For example, simulations show that performance gains of aggregation may degrade substantially, e.g., when flow control mechanisms are not implemented.

[00118] In some cases, general packet radio service (GPRS) Tunneling Protocol User Plane (GTP-U) packets may be used to transfer downlink PDCP PDUs via interface 199 from cellular manager 104 to WT node 106. For example, implementing the GTP-U packets may enable to use flow control mechanisms defined for dual connectivity, for example, in a manner similar to the manner defined in a 3GPPP TS 36.425 Specification and/or any other specification and/or protocol. For example, GTP-U extensions, e.g., as defined in a 3GPPP TS 36.425 Specification and/or any other specification and/or protocol, may be used for LTEAVLAN aggregation, for example, to add sequence numbers to packets sent via interface 199, and/or to communicate downlink delivery status reporting messages from WT node 106 to cellular manager 104. [00119] In some demonstrative embodiments, the control flow mechanism using the GTP-U packets may not be implemented, for example, if a protocol other than GTP-U is used for communicating user plane messages on interface 199.

[00120] In some demonstrative embodiments, cellular manager 104 and WT node 106 may be configured to communicate over interface 199, for example, according to a protocol, which does not implement and/or does not support GTP-U packets, e.g., in accordance with a Generic Routing Encapsulation (GRE) protocol and/or any other protocol.

[00121] In some demonstrative embodiments, cellular manager 104 and WT node 106 may be configured to communicate over interface 199, for example, according to a TCP/IP.

[00122] For example, cellular manager 104 and UE 102 may use TCP/IP to communicate the downlink traffic via WT node 106. According to this example, WT node 106 may be configured to operate as a router.

[00123] In example, interface 169 may be configured to transmit messages to WT node 106 via interface 199 over TCP/IP, and/or to process messages received from WT node 106 via interface 199 over TCP/IP.

[00124] In one example, interface 192 may be configured to transmit messages to cellular manager 104 via interface 199 over TCP/IP, and/or to process messages received from cellular manager 104 via interface 199 over TCP/IP.

[00125] In on example, interface 169 may be configured to transmit messages to WT node 106 via interface 199 according to a tunneling protocol, and/or to process messages received from WT node 106 via interface 199 according to the tunneling protocol; and interface 192 may be configured to transmit messages to cellular manager 104 via interface 199 according to the tunneling protocol, and/or to process messages received from cellular manager 104 via interface 199 according to the tunneling protocol.

[00126] In some demonstrative embodiments, using the TCP/IP to communicate the downlink traffic via WT node 106 may enable, for example, to reduce an impact of WT node 106 to implement LTE/WLAN aggregation.

[00127] In some demonstrative embodiments, cellular node 104 and/or WT node 106 may be configured to implement a control flow mechanism, which may enable communicating one or more messages, e.g., status report messages, for example, even if GTP-U packets are not supported by interface 199, e.g., as described below. [00128] In some demonstrative embodiments, cellular node 104 and/or WT node 106 may be configured to implement a control flow mechanism, which may utilize control plane messages, e.g., Xw-AP messages, which may be used, for example, even in cases case when a non-GTP-U user plane protocol is used on interface 199.

[00129] In some demonstrative embodiments, cellular node 104 and/or WT node 100 may be configured to implement a control flow mechanism, which may utilize control plane messages, e.g., Xw-AP messages, which may be used, for example, even in cases case when interface 199 utilizes a user plane protocol, which does not utilize and/or support a flow control mechanism.

[00130] In some demonstrative embodiments, cellular node 104 and/or WT node 106 may be configured to implement a control flow mechanism, which may utilize control plane messages, e.g., Xw-AP messages, which may be used, for example, even in cases case when interface 199 utilizes a user plane protocol, which does not utilize and/or support sequence numbers.

[00131] In some demonstrative embodiments, cellular node 104 and/or WT node 106 may be configured to implement a control flow mechanism, which may utilize PDCP sequence numbers (SN), for example, instead of user plane protocol sequence numbers.

[00132] In some demonstrative embodiments, WT node 106 may be configured to parse PDCP headers of downlink packets received from cellular node 104 via interface 199, for example, to extract PDCP SN information of PDUs, which are to be sent to UE 102.

[00133] In some demonstrative embodiments, WT node 106 may be configured to generate a message, for example, an Xw-AP message, e.g., a new Xw-AP message or a modified Xw- AP message, which may include feedback information, and to send the message to cellular node 104 via interface 199, e.g., as described below.

[00134] In some demonstrative embodiments, cellular manager 104 may be configured to receive the message from WT node 106 via interface 199, and to schedule decisions for downlink traffic, for example, to route the downlink traffic between LTE and WLAN, e.g., as described below.

[00135] In some demonstrative embodiments, WT node 106 may be configured to generate a status report message and to send the status report message to cellular manager 104 via interface 199, e.g., as described below. [00136] In some demonstrative embodiments, the status report message may be an Xw-AP Downlink Delivery Status Report message, e.g., as described below.

[00137] In some demonstrative embodiments, the status report message may be any other Xw-AP message, for example, an Xw-AP Resource Status Report message.

[00138] In some demonstrative embodiments, the status report message may be configured, for example, for downlink delivery status indication, e.g., as described below.

[00139] In some demonstrative embodiments, WT node 106 may be configured, for example, to use the status report message to report to cellular manager information, which may include, for example, a highest successfully PDCP sequence number, e.g., per UE or per bearer/E-RAB, a desired buffer size, e.g., per UE or per bearer/E-RAB, lost PDCP sequence numbers, e.g., per UE or per bearer/E-RAB, an average link rate, e.g., per UE or per bearer/E-RAB, an average UE rate, an average rate per E-RAB, a per UE parameter, a per bearer/E-RAB parameter, and/or any additional or alternative information, e.g., as described below.

[00140] In some demonstrative embodiments, cellular manager 104 may be configured to perform one or more scheduling and/or routing operations, for example, based at least on the information in the status report message.

[00141] In some demonstrative embodiments, cellular manager 104 may be configured to adjust a rate of packets sent via WLAN, for example, based at least on the information in the status report message, e.g., as described below.

[00142] In some demonstrative embodiments, WT node 106 may be configured to send the status report message to cellular manager 104, e.g., periodically.

[00143] In some demonstrative embodiments, WT node 106 may be configured to send the status report message to cellular manager 104, for example, as a response to a request from cellular manager 104. For example, controller 144 may be configured to trigger cellular manager 104 to send a status report request to WT node 106, and controller 149 may be configured to trigger WT node 106 to send the status report message to cellular manager 104, e.g., in response to the status report request.

[00144] In some demonstrative embodiments, controller 149 may be configured to generate the status report message and to send the status report message to the cellular manager 104 via interface 199. [00145] In some demonstrative embodiments, the status report message may include E-RAB status information corresponding to communication of the downlink traffic of one or more E- RABs to UE 102, e.g., as described below.

[00146] In some demonstrative embodiments, the E-RAB status information may include, or may be arranged in, one or more E-RAB items corresponding to one or more respective E- RABs, e.g., as described below.

[00147] In some demonstrative embodiments, an E-RAB item corresponding to an E-RAB may include, for example, an E-RAB identifier (ID) of the E-RAB, and E-RAB status information corresponding to the E-RAB, e.g., as described below.

[00148] In some demonstrative embodiments, the E-RAB status information may include, for example, delivered and lost Packet Data Convergence Protocol (PDCP) information corresponding to an E-RAB.

[00149] In some demonstrative embodiments, the delivered and lost PDCP information may include, for example, a highest successfully delivered PDCP sequence number (SN) and one or more lost PDCP SN ranges.

[00150] In some demonstrative embodiments, the E-RAB status information may include, for example, a buffer size for an E-RAB.

[00151] In some demonstrative embodiments, the E-RAB status information may include any additional or alternative information, and/or may be arranged and/or structured in any other format.

[00152] In some demonstrative embodiments, the status report message may include UE status information corresponding to a WLAN link with UE 102, e.g., as described below.

[00153] In some demonstrative embodiments, the UE status information may include, for example, a minimum buffer size to communicate with UE 102 the downlink traffic of the one or more E-RABs.

[00154] In some demonstrative embodiments, the UE status information may include, for example, an average data rate corresponding to the WLAN link with UE 102.

[00155] In some demonstrative embodiments, the UE status information may include, for example, an achievable data rate corresponding to the WLAN link with UE 102. [00156] In some demonstrative embodiments, the UE status information may include, for example, link quality information corresponding to the WLAN link with UE 102.

[00157] In some demonstrative embodiments, the status report message may include all or part of the E-RAB status information described above, all or part of the UE status information described above, and/or any other additional or alternative information.

[00158] In some demonstrative embodiments, controller 149 may cause, trigger, and/or control cellular manager interface 192 to send to cellular manager 104 a status report message including E-RAB status information corresponding to one or more E-RABs, which are being utilized for communication between UE 102 and cellular manager 104, and UE status information corresponding a WLAN link, which is utilized for communication between WT node 106 and UE 102.

[00159] In some demonstrative embodiments, access device interface 169 may receive the status report message from WT node 106, e.g., via interface 199, and controller 144 may be configured to process the status information in the status report message.

[00160] In some demonstrative embodiments, WT node 106 and/or cellular manager 104 may be configured to communicate the status report message in the form of a XW-AP Downlink Delivery Status Report, e.g., as described below.

[00161] In some demonstrative embodiments, the Downlink Delivery Status Report may be configured to carry per-bearer information, e.g., corresponding to at least one E-RAB, and/or per-UE information, e.g., corresponding to UE 102, as described below.

[00162] In some demonstrative embodiments, the per-bearer information may include, for example, a Highest successfully delivered PDCP SN.

[00163] In some demonstrative embodiments, the per-bearer information may include, for example, information of a currently desired buffer size at the WLAN AP/AC, e.g., at WT node 106, for transmitting to the UE user data associated with a specific E-RAB configured with a split bearer option.

[00164] In some demonstrative embodiments, the per-bearer information may include, for example, a number of lost PDCP SN ranges.

[00165] In some demonstrative embodiments, the per-bearer information may include any other additional or alternative information corresponding to the E-RAB. [00166] In some demonstrative embodiments, the per-UE information may include, for example, information of a currently minimum desired buffer size at the WLAN AP/AC, e.g., at WT 106, for transmitting to the UE user data associated with all E-RABs, e.g., configured with a split bearer option.

[00167] In some demonstrative embodiments, the per-UE information may include, for example, an average data rate, e.g., on a WLAN air interface.

[00168] In some demonstrative embodiments, the per-UE information may include, for example, information of WLAN link quality, for example, including parameters such as, for example, a Modulation and Coding Scheme (MCS) used, a Basic Service Set (BSS) load, and/or any other parameter.

[00169] In some demonstrative embodiments, WT node 106 and/or cellular manager 104 may be configured to communicate the status report message in the form of a XW-AP Downlink Delivery Status Report, for example, having a structure including one or more information elements, e.g., as follows:

DOWNLINK DELIVERY STATUS REPORT

This message is sent by the WLAN to the eNB to provide feedback to allow the eNB control the downlink user data flow via the SeNB for the respective E-RAB

Direction: WLAN→ eNB.

IE/Group Presence Rang IE type Semantics Criticality Assigned Name e and description Criticality reference

Message M 9.2.13 YES reject Type

eNB UE M eNB UE Allocated at YES reject X2AP ID X2AP ID the eNB

9.2.24

WLAN UE M eNB UE

X2AP ID X2AP ID

E-RABs 1 YES reject List

>E-RABs 1 .. EACH reject Item <max

noof

Beare

rs>

»E- M 9.2.23

RAB ID

Highest

»>H successfully

ighest delivered

Deliv PDCP SN

ered

PDCP

SN

Desired

»>D buffer size

esired for the E- Buffer RAB

Size

1 .. »>L <max

ost noofR

SNs anges

List >

»»

Start

of

Lost

PDCP

SN

Range

»»

End

of

Lost

PDCP

SN

Range

Minimum Minimum buffer size desired buffer size for the UE

Average

data rate

WLAN link

quality

Table 1 [00170] In other embodiments, the XW-AP Downlink Delivery Status Report may have any other structure and/or include one or more additional or alternative fields.

[00171] In some demonstrative embodiments, the Downlink Delivery Status Report may be initiated by a WLAN AP/AC. In one example, controller 149 may trigger WT node 106 to send the Downlink Delivery Status Report to cellular manager, e.g., at one or more predefined times and/or on a periodic basis.

[00172] In some demonstrative embodiments, the Downlink Delivery Status Report may be initiated by an eNB. In one example, controller 144 may trigger cellular manager 104 to send a XW-AP request message to WT node 106, and controller 149 may trigger WT node 106 to send the Downlink Delivery Status Report to cellular manager, e.g., in response to the XW- AP request message.

[00173] In some demonstrative embodiments, controller 144 may be configured to control routing of the downlink traffic to UE 102 via WT node 106, for example, based at least on the status report message from WT node 106.

[00174] In some demonstrative embodiments, controller 144 may use the status report information, for example, to implement one or more flow control functionalities, for example, to control the amount of packets sent to WT node 106, e.g., based on an amount of traffic that WT node 106 is able to handle. For example, a WLAN air interface may typically be slower than a network interface and, accordingly, if cellular manager 104 will keep sending packets to WT node 106, buffers of WT node 106 may overflow.

[00175] In some demonstrative embodiments, cellular manager 104, e.g., operating as an eNB, may be configured to use the status report message for traffic flow control in a switched bearer scheme (also referred to as "solution 2c"), e.g., as described below.

[00176] In some demonstrative embodiments, cellular manager 104, e.g., operating as an eNB, may be configured to use the status report message for traffic flow control in a bearer- split scheme (also referred to as "solution 3c"), e.g., as described below.

[00177] In some demonstrative embodiments, for example, if the switched bearer scheme is used, controller 144 may be configured to decide, based at least on the information from the Downlink Delivery Status Report, to move a bearer from WLAN back to LTE, e.g., to communicate all traffic of an E-RAB via the cellular network. [00178] In one example, controller 144 may be configured to decide to communicate all traffic of an E-RAB via the cellular network, for example, if the information from the Downlink Delivery Status Report indicates that the WLAN may not be able to properly handle the traffic of the E-RAB.

[00179] In another example, controller 144 may be configured to decide to communicate all traffic of an E-RAB via the WLAN, for example, if the information from the Downlink Delivery Status Report indicates that the WLAN may be able to properly handle the traffic of the E-RAB.

[00180] In some demonstrative embodiments, for example, if the bearer-spilt scheme is used, controller 144 may be configured to use the information from the Downlink Delivery Status Report, for example, to schedule PDCP PDUs on either LTE or WLAN, for example, to enable sending some of the PDCP PDUs via WLAN and sending some of the PDCP PDUs via LTE.

[00181] In some demonstrative embodiments, controller 144 may be configured to control routing of at least part of the downlink traffic to a UE, e.g., UE 102, via WT node 106, for example, based on a flow control mechanism, which may be configured to ensure that to ensure that the WLAN AP/AC has enough packets in the buffers, e.g., as not to "run out"; to ensure that WLAN AP/AC transmission buffers for a given E-RAB do not include too many packets, e.g., to ensure that buffering time does not exceed one or more QoS parameters defined for the E-RAB, e.g., a packet-delay budge; and/or based on any additional or alternative criteria.

[00182] In some demonstrative embodiments, controller 144 may be configured to decide to reduce a rate of PDCP PDUs sent to WT node 106 for transmission to UE 102, for example, when the WLAN average data rate is low, the WLAN link quality is bad, and/or the number of lost PDCP PDUs is high.

[00183] In some demonstrative embodiments, controller 144 may be configured to reduce an amount of downlink traffic of the E-RAB routed via WT node 106, for example, if the status report information from WT node 106 indicates that the buffer size for the E-RAB is larger than an E-RAB buffer threshold.

[00184] In some demonstrative embodiments, controller 144 may be configured to increase an amount of downlink traffic routed to UE 102 via WT node 106, for example, if the status report information from WT node 106 indicates that the minimum buffer size for transmitting to UE 102 via the WLAN is less than a WLAN buffer threshold.

[00185] In some demonstrative embodiments, controller 144 may be configured to control routing of at least part of the downlink traffic to UE 102 via WT node 106 based on any other control mechanism, which utilizes the status report information from WT node 106.

[00186] Reference is made to Fig. 2, which schematically illustrates a method of communicating status information between a WT node and a cellular manager, in accordance with some demonstrative embodiments. In some embodiments, one or more of the operations of the method of Fig. 2 may be performed by a wireless communication system e.g., system 100 (Fig. 1); a WT node, e.g., WT node 106 (Fig. 1); an interface, e.g., interface 192 (Fig. 1), interface 159 (Fig. 1), and/or interface 194 (Fig. 1); and/or a controller, e.g., controller 149 (Fig. 1).

[00187] As indicated at block 202, the method may include generating at a WT node a status report message including E-RAB status information and UE status information. For example, controller 149 (Fig. 1) may generate the status report message including, for example, E- RAB status information corresponding to communication of downlink traffic of one or more E-RABs to UE 102 (Fig. 1), and UE status information corresponding to a WLAN link with UE 102 (Fig. 1), e.g., as described above.

[00188] As indicated at block 204, the method may include sending the status report message from the WT node to a cellular manager. For example, controller 149 (Fig. 1) may cause interface 192 (Fig. 1) to send to cellular manager 104 (Fig. 1) a status report message via interface 199, e.g., as described above.

[00189] Reference is made to Fig. 3, which schematically illustrates a method of processing status information communicated between a WT node and a cellular manager, in accordance with some demonstrative embodiments. In some embodiments, one or more of the operations of the method of Fig. 3 may be performed by a wireless communication system e.g., system 100 (Fig. 1); a cellular manager, e.g., cellular manager 104 (Fig. 1); an interface, e.g., interface 169 (Fig. 1), interface 167 (Fig. 1), and/or interface 161 (Fig. 1); and/or a controller, e.g., controller 144 (Fig. 1).

[00190] As indicated at block 306, the method may include processing information of a status report message received at a cellular manager. For example, controller 144 (Fig. 1) may be configured to process the information in the status report message received from WT node 106 (Fig. 1), e.g., as described above.

[00191] As indicated at block 308, the method may include routing at least part of downlink traffic via the WT node based at least on the status report message from the WT node. For example, controller 144 (Fig. 1) may be configured to control routing of at least part of the downlink traffic to UE 102 (Fig. 1) via WT node 106 (Fig. 1), based at least on the information in the status report message received from WT node 106 (Fig. 1), e.g., as described above.

[00192] Reference is made to Fig. 4, which schematically illustrates a product of manufacture 400, in accordance with some demonstrative embodiments. Product 400 may include a non-transitory machine-readable storage medium 402 to store logic 404, which may be used, for example, to perform at least part of the functionality of a cellular manager, e.g., cellular manager 104 (Fig. 1); a WT node, e.g., WT node 106 (Fig. 1); an interface, e.g., interface 169 (Fig. 1), interface 167 (Fig. 1), interface 192 (Fig. 1), interface 161 (Fig. 1), interface 159 (Fig. 1), and/or interface 194 (Fig. 1); and/or a controller, e.g., controller 144 (Fig. 1) and/or controller 149 (Fig. 1); and/or to perform one or more operations of the methods of Figs. 2 and/or 3, and/or one or more operations and/or functionalities described herein. The phrase "non-transitory machine-readable medium" is directed to include all computer-readable media, with the sole exception being a transitory propagating signal.

[00193] In some demonstrative embodiments, product 400 and/or machine-readable storage medium 402 may include one or more types of computer-readable storage media capable of storing data, including volatile memory, non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writeable or re-writeable memory, and the like. For example, machine-readable storage medium 402 may include, RAM, DRAM, Double- Data-Rate DRAM (DDR-DRAM), SDRAM, static RAM (SRAM), ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), Compact Disk ROM (CD-ROM), Compact Disk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), flash memory (e.g., NOR or NAND flash memory), content addressable memory (CAM), polymer memory, phase-change memory, ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS) memory, a disk, a floppy disk, a hard drive, an optical disk, a magnetic disk, a card, a magnetic card, an optical card, a tape, a cassette, and the like. The computer-readable storage media may include any suitable media involved with downloading or transferring a computer program from a remote computer to a requesting computer carried by data signals embodied in a carrier wave or other propagation medium through a communication link, e.g., a modem, radio or network connection.

[00194] In some demonstrative embodiments, logic 404 may include instructions, data, and/or code, which, if executed by a machine, may cause the machine to perform a method, process and/or operations as described herein. The machine may include, for example, any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, or the like, and may be implemented using any suitable combination of hardware, software, firmware, and the like.

[00195] In some demonstrative embodiments, logic 404 may include, or may be implemented as, software, a software module, an application, a program, a subroutine, instructions, an instruction set, computing code, words, values, symbols, and the like. The instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like. The instructions may be implemented according to a predefined computer language, manner or syntax, for instructing a processor to perform a certain function. The instructions may be implemented using any suitable high-level, low-level, object-oriented, visual, compiled and/or interpreted programming language, such as C, C++, Java, BASIC, Matlab, Pascal, Visual BASIC, assembly language, machine code, and the like.

EXAMPLES

[00196] The following examples pertain to further embodiments.

[00197] Example 1 includes a Wireless Local Area Network (WLAN) Termination (WT) node comprising an Evolved Node B (eNB) interface configured to receive from an eNB downlink traffic of one or more Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) Radio Access Bearers (E-RABs); a WLAN interface configured to send the downlink traffic to a User Equipment (UE) via a WLAN; and a controller configured to generate a status report message and to send the status report message to the eNB via the eNB interface, the status report message comprising E- RAB status information and UE status information, the E-RAB status information comprising information corresponding to communication of the downlink traffic of the one or more E- RABs, and the UE status information comprising information corresponding to a WLAN link with the UE. [00198] Example 2 includes the subject matter of Example 1, and optionally, wherein the E- RAB status information comprises one or more E-RAB items corresponding to respective ones of the one or more E-RABs, an E-RAB item comprising an E-RAB identifier (ID) of an E-RAB, and E-RAB status information corresponding to the E-RAB.

[00199] Example 3 includes the subject matter of Example 1 or 2, and optionally, wherein the E-RAB status information comprises delivered and lost Packet Data Convergence Protocol (PDCP) information corresponding to an E-RAB.

[00200] Example 4 includes the subject matter of Example 3, and optionally, wherein the delivered and lost PDCP information comprises a highest successfully delivered PDCP sequence number (SN) and one or more lost PDCP SN ranges.

[00201] Example 5 includes the subject matter of any one of Examples 1-4, and optionally, wherein the E-RAB status information comprises a buffer size for an E-RAB.

[00202] Example 6 includes the subject matter of any one of Examples 1-5, and optionally, wherein the UE status information comprises a minimum buffer size to communicate with the UE the downlink traffic of the one or more E-RABs.

[00203] Example 7 includes the subject matter of any one of Examples 1-6, and optionally, wherein the UE status information comprises an average data rate corresponding to the WLAN link.

[00204] Example 8 includes the subject matter of any one of Examples 1-7, and optionally, wherein the UE status information comprises an achievable data rate corresponding to the WLAN link.

[00205] Example 9 includes the subject matter of any one of Examples 1-8, and optionally, wherein the UE status information comprises link quality information corresponding to the WLAN link.

[00206] Example 10 includes the subject matter of any one of Examples 1-9, and optionally, wherein the eNB interface is configured to receive the downlink traffic according to a Transmission Control Protocol/Internet Protocol (TCP/IP).

[00207] Example 11 includes the subject matter of any one of Examples 1-10, and optionally, wherein the eNB interface is configured to receive the downlink traffic according to a tunneling protocol. [00208] Example 12 includes the subject matter of any one of Examples 1-11, and optionally, wherein the status report message comprises a Downlink Delivery Status Report message.

[00209] Example 13 includes the subject matter of any one of Examples 1-12, and optionally, wherein the apparatus is configured to operate as an Access Point (AP), the WLAN interface comprising a WLAN radio configured to transmit the downlink traffic to the UE via a WLAN link.

[00210] Example 14 includes the subject matter of any one of Examples 1-12, and optionally, wherein the apparatus is configured to operate as an Access Controller (AC), the WLAN interface comprising an Access Point (AP) interface configured to send the downlink traffic to an AP.

[00211] Example 15 includes the subject matter of any one of Examples 1-14, and optionally, comprising a memory; and a processor.

[00212] Example 16 includes an evolved Node B (eNB) comprising an air interface configured to communicate with a User Equipment (UE) via a cellular link; a Wireless Local Area Network (WLAN) Termination (WT) node interface configured to communicate with a WT node; and a controller configured to control routing of at least part of downlink traffic to the UE via the WT node based at least on a status report message from the WT node, the downlink traffic comprising downlink traffic of one or more Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) Radio Access Bearers (E-RABs), the status report message comprising E-RAB status information and UE status information, the E-RAB status information comprising information corresponding to communication of the downlink traffic of the one or more E-RABs, and the UE status information comprising information corresponding to a WLAN link with the UE.

[00213] Example 17 includes the subject matter of Example 16, and optionally, wherein the E-RAB status information comprises one or more E-RAB items corresponding to respective ones of the one or more E-RABs, an E-RAB item comprising an E-RAB identifier (ID) of an E-RAB, and E-RAB status information corresponding to the E-RAB.

[00214] Example 18 includes the subject matter of Example 16 or 17, and optionally, wherein the E-RAB status information comprises delivered and lost Packet Data Convergence Protocol (PDCP) information corresponding to an E-RAB. [00215] Example 19 includes the subject matter of Example 18, and optionally, wherein the delivered and lost PDCP information comprises a highest successfully delivered PDCP sequence number (SN) and one or more lost PDCP SN ranges.

[00216] Example 20 includes the subject matter of any one of Examples 16-19, and optionally, wherein the E-RAB status information comprises a buffer size for an E-RAB.

[00217] Example 21 includes the subject matter of Example 20, and optionally, wherein the controller is configured to reduce an amount of downlink traffic of the E-RAB routed via the WT node, if the buffer size for the E-RAB is larger than an E-RAB buffer threshold.

[00218] Example 22 includes the subject matter of any one of Examples 16-21, and optionally, wherein the UE status information comprises a minimum buffer size to communicate with the UE the downlink traffic of the one or more E-RAB s.

[00219] Example 23 includes the subject matter of Example 22, and optionally, wherein the controller is configured to increase an amount of downlink traffic routed to the UE via the WT node, if the minimum buffer size is less than a WLAN buffer threshold.

[00220] Example 24 includes the subject matter of any one of Examples 16-23, and optionally, wherein the UE status information comprises an average data rate corresponding to the WLAN link.

[00221] Example 25 includes the subject matter of any one of Examples 16-24, and optionally, wherein the UE status information comprises an achievable data rate corresponding to the WLAN link.

[00222] Example 26 includes the subject matter of any one of Examples 16-25, and optionally, wherein the UE status information comprises link quality information corresponding to the WLAN link.

[00223] Example 27 includes the subject matter of any one of Examples 16-26, and optionally, wherein the WT node interface is configured to send the downlink traffic to the WT node according to a Transmission Control Protocol/Internet Protocol (TCP/IP).

[00224] Example 28 includes the subject matter of any one of Examples 16-27, and optionally, wherein the WT node interface is configured to send the downlink traffic to the WT node according to a tunneling protocol. [00225] Example 29 includes the subject matter of any one of Examples 16-28, and optionally, wherein the status report message comprises a Downlink Delivery Status Report message.

[00226] Example 30 includes the subject matter of any one of Examples 16-29, and optionally, comprising a plurality of antennas; a memory; and a processor.

[00227] Example 31 includes an apparatus comprising circuitry configured to cause a Wireless Local Area Network (WLAN) Termination (WT) node to receive from an Evolved Node B (eNB) downlink traffic of one or more Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) Radio Access Bearers (E-RABs); send the downlink traffic to a User Equipment (UE) via a WLAN; and generate a status report message and send the status report message to the eNB via the eNB interface, the status report message comprising E-RAB status information and UE status information, the E-RAB status information comprising information corresponding to communication of the downlink traffic of the one or more E-RABs, and the UE status information comprising information corresponding to a WLAN link with the UE.

[00228] Example 32 includes the subject matter of Example 31, and optionally, wherein the E-RAB status information comprises one or more E-RAB items corresponding to respective ones of the one or more E-RABs, an E-RAB item comprising an E-RAB identifier (ID) of an E-RAB, and E-RAB status information corresponding to the E-RAB.

[00229] Example 33 includes the subject matter of Example 31 or 32, and optionally, wherein the E-RAB status information comprises delivered and lost Packet Data Convergence Protocol (PDCP) information corresponding to an E-RAB.

[00230] Example 34 includes the subject matter of Example 33, and optionally, wherein the delivered and lost PDCP information comprises a highest successfully delivered PDCP sequence number (SN) and one or more lost PDCP SN ranges.

[00231] Example 35 includes the subject matter of any one of Examples 31-34, and optionally, wherein the E-RAB status information comprises a buffer size for an E-RAB.

[00232] Example 36 includes the subject matter of any one of Examples 31-35, and optionally, wherein the UE status information comprises a minimum buffer size to communicate with the UE the downlink traffic of the one or more E-RABs. [00233] Example 37 includes the subject matter of any one of Examples 31-36, and optionally, wherein the UE status information comprises an average data rate corresponding to the WLAN link.

[00234] Example 38 includes the subject matter of any one of Examples 31-37, and optionally, wherein the UE status information comprises an achievable data rate corresponding to the WLAN link.

[00235] Example 39 includes the subject matter of any one of Examples 31-38, and optionally, wherein the UE status information comprises link quality information corresponding to the WLAN link.

[00236] Example 40 includes the subject matter of any one of Examples 31-39, and optionally, wherein the apparatus is configured to cause the WT node to process reception of the downlink traffic according to a Transmission Control Protocol/Internet Protocol (TCP/IP).

[00237] Example 41 includes the subject matter of any one of Examples 31-40, and optionally, wherein the apparatus is configured to cause the WT node to process reception of the downlink traffic according to a tunneling protocol.

[00238] Example 42 includes the subject matter of any one of Examples 31-41, and optionally, wherein the status report message comprises a Downlink Delivery Status Report message.

[00239] Example 43 includes the subject matter of any one of Examples 31-42, and optionally, wherein the apparatus is configured to cause the WT node to operate as an Access Point (AP), and to transmit the downlink traffic to the UE via a WLAN link.

[00240] Example 44 includes the subject matter of any one of Examples 31-42, and optionally, wherein the apparatus is configured to cause the WT node to operate as an Access Controller (AC), and to send the downlink traffic to an Access Point (AP).

[00241] Example 45 includes the subject matter of any one of Examples 31-44, and optionally, comprising a memory; and a processor.

[00242] Example 46 includes an apparatus comprising circuitry configured to cause an evolved Node B (eNB) to communicate with a User Equipment (UE) via a cellular link; and control routing of at least part of downlink traffic to the UE via a Wireless Local Area Network (WLAN) Termination (WT) node based at least on a status report message from the WT node, the downlink traffic comprising downlink traffic of one or more Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E- UTRAN) Radio Access Bearers (E-RABs), the status report message comprising E-RAB status information and UE status information, the E-RAB status information comprising information corresponding to communication of the downlink traffic of the one or more E- RABs, and the UE status information comprising information corresponding to a WLAN link with the UE.

[00243] Example 47 includes the subject matter of Example 46, and optionally, wherein the E-RAB status information comprises one or more E-RAB items corresponding to respective ones of the one or more E-RABs, an E-RAB item comprising an E-RAB identifier (ID) of an E-RAB, and E-RAB status information corresponding to the E-RAB.

[00244] Example 48 includes the subject matter of Example 46 or 47, and optionally, wherein the E-RAB status information comprises delivered and lost Packet Data Convergence Protocol (PDCP) information corresponding to an E-RAB.

[00245] Example 49 includes the subject matter of Example 48, and optionally, wherein the delivered and lost PDCP information comprises a highest successfully delivered PDCP sequence number (SN) and one or more lost PDCP SN ranges.

[00246] Example 50 includes the subject matter of any one of Examples 46-49, and optionally, wherein the E-RAB status information comprises a buffer size for an E-RAB.

[00247] Example 51 includes the subject matter of Example 50, and optionally, wherein the apparatus is configured to cause the eNB to reduce an amount of downlink traffic of the E- RAB routed via the WT node, if the buffer size for the E-RAB is larger than an E-RAB buffer threshold.

[00248] Example 52 includes the subject matter of any one of Examples 46-51, and optionally, wherein the UE status information comprises a minimum buffer size to communicate with the UE the downlink traffic of the one or more E-RABs.

[00249] Example 53 includes the subject matter of Example 52, and optionally, wherein the apparatus is configured to cause the eNB to increase an amount of downlink traffic routed to the UE via the WT node, if the minimum buffer size is less than a WLAN buffer threshold. [00250] Example 54 includes the subject matter of any one of Examples 46-53, and optionally, wherein the UE status information comprises an average data rate corresponding to the WLAN link.

[00251] Example 55 includes the subject matter of any one of Examples 46-54, and optionally, wherein the UE status information comprises an achievable data rate corresponding to the WLAN link.

[00252] Example 56 includes the subject matter of any one of Examples 46-55, and optionally, wherein the UE status information comprises link quality information corresponding to the WLAN link.

[00253] Example 57 includes the subject matter of any one of Examples 46-56, and optionally, wherein the apparatus is configured to cause the eNB to send the downlink traffic to the WT node according to a Transmission Control Protocol/Internet Protocol (TCP/IP).

[00254] Example 58 includes the subject matter of any one of Examples 46-57, and optionally, wherein the apparatus is configured to cause the eNB to send the downlink traffic to the WT node according to a tunneling protocol.

[00255] Example 59 includes the subject matter of any one of Examples 46-58, and optionally, wherein the status report message comprises a Downlink Delivery Status Report message.

[00256] Example 60 includes the subject matter of any one of Examples 46-59, and optionally, comprising a plurality of antennas; a memory; and a processor.

[00257] Example 61 includes a method to be performed by a Wireless Local Area Network (WLAN) Termination (WT), the method comprising receiving from an Evolved Node B (eNB) downlink traffic of one or more Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) Radio Access Bearers (E- RABs); sending the downlink traffic to a User Equipment (UE) via a WLAN; and generating a status report message and sending the status report message to the eNB via the eNB interface, the status report message comprising E-RAB status information and UE status information, the E-RAB status information comprising information corresponding to communication of the downlink traffic of the one or more E-RABs, and the UE status information comprising information corresponding to a WLAN link with the UE. [00258] Example 62 includes the subject matter of Example 61, and optionally, wherein the E-RAB status information comprises one or more E-RAB items corresponding to respective ones of the one or more E-RABs, an E-RAB item comprising an E-RAB identifier (ID) of an E-RAB, and E-RAB status information corresponding to the E-RAB.

[00259] Example 63 includes the subject matter of Example 61 or 62, and optionally, wherein the E-RAB status information comprises delivered and lost Packet Data Convergence Protocol (PDCP) information corresponding to an E-RAB.

[00260] Example 64 includes the subject matter of Example 63, and optionally, wherein the delivered and lost PDCP information comprises a highest successfully delivered PDCP sequence number (SN) and one or more lost PDCP SN ranges.

[00261] Example 65 includes the subject matter of any one of Examples 61-64, and optionally, wherein the E-RAB status information comprises a buffer size for an E-RAB.

[00262] Example 66 includes the subject matter of any one of Examples 61-65, and optionally, wherein the UE status information comprises a minimum buffer size to communicate with the UE the downlink traffic of the one or more E-RABs.

[00263] Example 67 includes the subject matter of any one of Examples 61-66, and optionally, wherein the UE status information comprises an average data rate corresponding to the WLAN link.

[00264] Example 68 includes the subject matter of any one of Examples 61-67, and optionally, wherein the UE status information comprises an achievable data rate corresponding to the WLAN link.

[00265] Example 69 includes the subject matter of any one of Examples 61-68, and optionally, wherein the UE status information comprises link quality information corresponding to the WLAN link.

[00266] Example 70 includes the subject matter of any one of Examples 61-69, and optionally, comprising processing reception of the downlink traffic according to a Transmission Control Protocol/Internet Protocol (TCP/IP).

[00267] Example 71 includes the subject matter of any one of Examples 61-70, and optionally, comprising processing reception of the downlink traffic according to a tunneling protocol. [00268] Example 72 includes the subject matter of any one of Examples 61-71, and optionally, wherein the status report message comprises a Downlink Delivery Status Report message.

[00269] Example 73 includes the subject matter of any one of Examples 61-72, and optionally, comprising operating as an Access Point (AP), and transmitting the downlink traffic to the UE via a WLAN link.

[00270] Example 74 includes the subject matter of any one of Examples 61-72, and optionally, comprising operating as an Access Controller (AC), and sending the downlink traffic to an Access Point (AP).

[00271] Example 75 includes a method to be performed by an evolved Node B (eNB), the method comprising communicating with a User Equipment (UE) via a cellular link; and controlling routing of at least part of downlink traffic to the UE via a Wireless Local Area Network (WLAN) Termination (WT) node based at least on a status report message from the WT node, the downlink traffic comprising downlink traffic of one or more Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E- UTRAN) Radio Access Bearers (E-RABs), the status report message comprising E-RAB status information and UE status information, the E-RAB status information comprising information corresponding to communication of the downlink traffic of the one or more E- RABs, and the UE status information comprising information corresponding to a WLAN link with the UE.

[00272] Example 76 includes the subject matter of Example 75, and optionally, wherein the E-RAB status information comprises one or more E-RAB items corresponding to respective ones of the one or more E-RABs, an E-RAB item comprising an E-RAB identifier (ID) of an E-RAB, and E-RAB status information corresponding to the E-RAB.

[00273] Example 77 includes the subject matter of Example 75 or 76, and optionally, wherein the E-RAB status information comprises delivered and lost Packet Data Convergence Protocol (PDCP) information corresponding to an E-RAB.

[00274] Example 78 includes the subject matter of Example 77, and optionally, wherein the delivered and lost PDCP information comprises a highest successfully delivered PDCP sequence number (SN) and one or more lost PDCP SN ranges.

[00275] Example 79 includes the subject matter of any one of Examples 75-78, and optionally, wherein the E-RAB status information comprises a buffer size for an E-RAB. [00276] Example 80 includes the subject matter of Example 79, and optionally, comprising reducing an amount of downlink traffic of the E-RAB routed via the WT node, if the buffer size for the E-RAB is larger than an E-RAB buffer threshold.

[00277] Example 81 includes the subject matter of any one of Examples 75-80, and optionally, wherein the UE status information comprises a minimum buffer size to communicate with the UE the downlink traffic of the one or more E-RAB s.

[00278] Example 82 includes the subject matter of Example 81, and optionally, comprising increasing an amount of downlink traffic routed to the UE via the WT node, if the minimum buffer size is less than a WLAN buffer threshold.

[00279] Example 83 includes the subject matter of any one of Examples 75-82, and optionally, wherein the UE status information comprises an average data rate corresponding to the WLAN link.

[00280] Example 84 includes the subject matter of any one of Examples 75-83, and optionally, wherein the UE status information comprises an achievable data rate corresponding to the WLAN link.

[00281] Example 85 includes the subject matter of any one of Examples 75-84, and optionally, wherein the UE status information comprises link quality information corresponding to the WLAN link.

[00282] Example 86 includes the subject matter of any one of Examples 75-85, and optionally, comprising sending the downlink traffic to the WT node according to a Transmission Control Protocol/Internet Protocol (TCP/IP).

[00283] Example 87 includes the subject matter of any one of Examples 75-86, and optionally, comprising sending the downlink traffic to the WT node according to a tunneling protocol.

[00284] Example 88 includes the subject matter of any one of Examples 75-87, and optionally, wherein the status report message comprises a Downlink Delivery Status Report message.

[00285] Example 89 includes a product comprising one or more tangible computer-readable non-transitory storage media comprising computer-executable instructions operable to, when executed by at least one computer processor, enable the at least one computer processor to implement one or more operations at a Wireless Local Area Network (WLAN) Termination (WT), the operations comprising receiving from an Evolved Node B (eNB) downlink traffic of one or more Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) Radio Access Bearers (E-RABs); sending the downlink traffic to a User Equipment (UE) via a WLAN; and generating a status report message and sending the status report message to the eNB via the eNB interface, the status report message comprising E-RAB status information and UE status information, the E-RAB status information comprising information corresponding to communication of the downlink traffic of the one or more E-RABs, and the UE status information comprising information corresponding to a WLAN link with the UE.

[00286] Example 90 includes the subject matter of Example 89, and optionally, wherein the E-RAB status information comprises one or more E-RAB items corresponding to respective ones of the one or more E-RABs, an E-RAB item comprising an E-RAB identifier (ID) of an E-RAB, and E-RAB status information corresponding to the E-RAB.

[00287] Example 91 includes the subject matter of Example 89 or 90, and optionally, wherein the E-RAB status information comprises delivered and lost Packet Data Convergence Protocol (PDCP) information corresponding to an E-RAB.

[00288] Example 92 includes the subject matter of Example 91, and optionally, wherein the delivered and lost PDCP information comprises a highest successfully delivered PDCP sequence number (SN) and one or more lost PDCP SN ranges.

[00289] Example 93 includes the subject matter of any one of Examples 89-92, and optionally, wherein the E-RAB status information comprises a buffer size for an E-RAB.

[00290] Example 94 includes the subject matter of any one of Examples 89-93, and optionally, wherein the UE status information comprises a minimum buffer size to communicate with the UE the downlink traffic of the one or more E-RABs.

[00291] Example 95 includes the subject matter of any one of Examples 89-94, and optionally, wherein the UE status information comprises an average data rate corresponding to the WLAN link.

[00292] Example 96 includes the subject matter of any one of Examples 89-95, and optionally, wherein the UE status information comprises an achievable data rate corresponding to the WLAN link. [00293] Example 97 includes the subject matter of any one of Examples 89-96, and optionally, wherein the UE status information comprises link quality information corresponding to the WLAN link.

[00294] Example 98 includes the subject matter of any one of Examples 89-97, and optionally, wherein the operations comprise processing reception of the downlink traffic according to a Transmission Control Protocol/Internet Protocol (TCP/IP).

[00295] Example 99 includes the subject matter of any one of Examples 89-98, and optionally, wherein the operations comprise processing reception of the downlink traffic according to a tunneling protocol.

[00296] Example 100 includes the subject matter of any one of Examples 89-99, and optionally, wherein the status report message comprises a Downlink Delivery Status Report message.

[00297] Example 101 includes the subject matter of any one of Examples 89-100, and optionally, wherein the operations comprise operating as an Access Point (AP), and transmitting the downlink traffic to the UE via a WLAN link.

[00298] Example 102 includes the subject matter of any one of Examples 89-100, and optionally, wherein the operations comprise operating as an Access Controller (AC), and sending the downlink traffic to an Access Point (AP).

[00299] Example 103 includes a product comprising one or more tangible computer-readable non-transitory storage media comprising computer-executable instructions operable to, when executed by at least one computer processor, enable the at least one computer processor to implement one or more operations at an evolved Node B (eNB), the operations comprising communicating with a User Equipment (UE) via a cellular link; and controlling routing of at least part of downlink traffic to the UE via a Wireless Local Area Network (WLAN) Termination (WT) node based at least on a status report message from the WT node, the downlink traffic comprising downlink traffic of one or more Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) Radio Access Bearers (E-RABs), the status report message comprising E-RAB status information and UE status information, the E-RAB status information comprising information corresponding to communication of the downlink traffic of the one or more E-RABs, and the UE status information comprising information corresponding to a WLAN link with the UE. [00300] Example 104 includes the subject matter of Example 103, and optionally, wherein the E-RAB status information comprises one or more E-RAB items corresponding to respective ones of the one or more E-RABs, an E-RAB item comprising an E-RAB identifier (ID) of an E-RAB, and E-RAB status information corresponding to the E-RAB.

[00301] Example 105 includes the subject matter of Example 103 or 104, and optionally, wherein the E-RAB status information comprises delivered and lost Packet Data Convergence Protocol (PDCP) information corresponding to an E-RAB.

[00302] Example 106 includes the subject matter of Example 105, and optionally, wherein the delivered and lost PDCP information comprises a highest successfully delivered PDCP sequence number (SN) and one or more lost PDCP SN ranges.

[00303] Example 107 includes the subject matter of any one of Examples 103-106, and optionally, wherein the E-RAB status information comprises a buffer size for an E-RAB.

[00304] Example 108 includes the subject matter of Example 107, and optionally, wherein the operations comprise reducing an amount of downlink traffic of the E-RAB routed via the WT node, if the buffer size for the E-RAB is larger than an E-RAB buffer threshold.

[00305] Example 109 includes the subject matter of any one of Examples 103-108, and optionally, wherein the UE status information comprises a minimum buffer size to communicate with the UE the downlink traffic of the one or more E-RABs.

[00306] Example 110 includes the subject matter of Example 109, and optionally, wherein the operations comprise increasing an amount of downlink traffic routed to the UE via the WT node, if the minimum buffer size is less than a WLAN buffer threshold.

[00307] Example 111 includes the subject matter of any one of Examples 103-110, and optionally, wherein the UE status information comprises an average data rate corresponding to the WLAN link.

[00308] Example 112 includes the subject matter of any one of Examples 103-111, and optionally, wherein the UE status information comprises an achievable data rate corresponding to the WLAN link.

[00309] Example 113 includes the subject matter of any one of Examples 103-112, and optionally, wherein the UE status information comprises link quality information corresponding to the WLAN link. [00310] Example 114 includes the subject matter of any one of Examples 103-113, and optionally, wherein the operations comprise sending the downlink traffic to the WT node according to a Transmission Control Protocol/Internet Protocol (TCP/IP).

[00311] Example 115 includes the subject matter of any one of Examples 103-114, and optionally, wherein the operations comprise sending the downlink traffic to the WT node according to a tunneling protocol.

[00312] Example 116 includes the subject matter of any one of Examples 103-115, and optionally, wherein the status report message comprises a Downlink Delivery Status Report message.

[00313] Example 117 includes an apparatus to perform one or more operations by a Wireless Local Area Network (WLAN) Termination (WT), the apparatus comprising means for receiving from an Evolved Node B (eNB) downlink traffic of one or more Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E- UTRAN) Radio Access Bearers (E-RABs); means for sending the downlink traffic to a User Equipment (UE) via a WLAN; and means for generating a status report message and sending the status report message to the eNB via the eNB interface, the status report message comprising E-RAB status information and UE status information, the E-RAB status information comprising information corresponding to communication of the downlink traffic of the one or more E-RABs, and the UE status information comprising information corresponding to a WLAN link with the UE.

[00314] Example 118 includes the subject matter of Example 117, and optionally, wherein the E-RAB status information comprises one or more E-RAB items corresponding to respective ones of the one or more E-RABs, an E-RAB item comprising an E-RAB identifier (ID) of an E-RAB, and E-RAB status information corresponding to the E-RAB.

[00315] Example 119 includes the subject matter of Example 117 or 118, and optionally, wherein the E-RAB status information comprises delivered and lost Packet Data Convergence Protocol (PDCP) information corresponding to an E-RAB.

[00316] Example 120 includes the subject matter of Example 119, and optionally, wherein the delivered and lost PDCP information comprises a highest successfully delivered PDCP sequence number (SN) and one or more lost PDCP SN ranges.

[00317] Example 121 includes the subject matter of any one of Examples 117-120 wherein the E-RAB status information comprises a buffer size for an E-RAB. [00318] Example 122 includes the subject matter of any one of Examples 117-121, and optionally, wherein the UE status information comprises a minimum buffer size to communicate with the UE the downlink traffic of the one or more E-RABs.

[00319] Example 123 includes the subject matter of any one of Examples 117-122, and optionally, wherein the UE status information comprises an average data rate corresponding to the WLAN link.

[00320] Example 124 includes the subject matter of any one of Examples 117-123, and optionally, wherein the UE status information comprises an achievable data rate corresponding to the WLAN link.

[00321] Example 125 includes the subject matter of any one of Examples 117-124, and optionally, wherein the UE status information comprises link quality information corresponding to the WLAN link.

[00322] Example 126 includes the subject matter of any one of Examples 117-125, and optionally, comprising means for processing reception of the downlink traffic according to a Transmission Control Protocol/Internet Protocol (TCP/IP).

[00323] Example 127 includes the subject matter of any one of Examples 117-126, and optionally, comprising means for processing reception of the downlink traffic according to a tunneling protocol.

[00324] Example 128 includes the subject matter of any one of Examples 117-127, and optionally, wherein the status report message comprises a Downlink Delivery Status Report message.

[00325] Example 129 includes the subject matter of any one of Examples 117-128, and optionally, comprising means for operating as an Access Point (AP), and transmitting the downlink traffic to the UE via a WLAN link.

[00326] Example 130 includes the subject matter of any one of Examples 117-128, and optionally, comprising means for operating as an Access Controller (AC), and sending the downlink traffic to an Access Point (AP).

[00327] Example 131 includes an apparatus to perform one or more operations by an evolved Node B (eNB), the apparatus comprising means for communicating with a User Equipment (UE) via a cellular link; and means for controlling routing of at least part of downlink traffic to the UE via a Wireless Local Area Network (WLAN) Termination (WT) node based at least on a status report message from the WT node, the downlink traffic comprising downlink traffic of one or more Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) Radio Access Bearers (E-RABs), the status report message comprising E-RAB status information and UE status information, the E-RAB status information comprising information corresponding to communication of the downlink traffic of the one or more E-RABs, and the UE status information comprising information corresponding to a WLAN link with the UE.

[00328] Example 132 includes the subject matter of Example 131, and optionally, wherein the E-RAB status information comprises one or more E-RAB items corresponding to respective ones of the one or more E-RABs, an E-RAB item comprising an E-RAB identifier (ID) of an E-RAB, and E-RAB status information corresponding to the E-RAB.

[00329] Example 133 includes the subject matter of Example 131 or 132, and optionally, wherein the E-RAB status information comprises delivered and lost Packet Data Convergence Protocol (PDCP) information corresponding to an E-RAB.

[00330] Example 134 includes the subject matter of Example 133, and optionally, wherein the delivered and lost PDCP information comprises a highest successfully delivered PDCP sequence number (SN) and one or more lost PDCP SN ranges.

[00331] Example 135 includes the subject matter of any one of Examples 131-134, and optionally, wherein the E-RAB status information comprises a buffer size for an E-RAB.

[00332] Example 136 includes the subject matter of Example 135, and optionally, comprising means for reducing an amount of downlink traffic of the E-RAB routed via the WT node, if the buffer size for the E-RAB is larger than an E-RAB buffer threshold.

[00333] Example 137 includes the subject matter of any one of Examples 131-136, and optionally, wherein the UE status information comprises a minimum buffer size to communicate with the UE the downlink traffic of the one or more E-RABs.

[00334] Example 138 includes the subject matter of Example 137, and optionally, comprising increasing an amount of downlink traffic routed to the UE via the WT node, if the minimum buffer size is less than a WLAN buffer threshold.

[00335] Example 139 includes the subject matter of any one of Examples 131-138, and optionally, wherein the UE status information comprises an average data rate corresponding to the WLAN link. [00336] Example 140 includes the subject matter of any one of Examples 131-139, and optionally, wherein the UE status information comprises an achievable data rate corresponding to the WLAN link.

[00337] Example 141 includes the subject matter of any one of Examples 131-140, and optionally, wherein the UE status information comprises link quality information corresponding to the WLAN link.

[00338] Example 142 includes the subject matter of any one of Examples 131-141, and optionally, comprising means for sending the downlink traffic to the WT node according to a Transmission Control Protocol/Internet Protocol (TCP/IP).

[00339] Example 143 includes the subject matter of any one of Examples 131-142, and optionally, comprising means for sending the downlink traffic to the WT node according to a tunneling protocol.

[00340] Example 144 includes the subject matter of any one of Examples 131-143, and optionally, wherein the status report message comprises a Downlink Delivery Status Report message.

[00341] Functions, operations, components and/or features described herein with reference to one or more embodiments, may be combined with, or may be utilized in combination with, one or more other functions, operations, components and/or features described herein with reference to one or more other embodiments, or vice versa.

[00342] While certain features have been illustrated and described herein, many modifications, substitutions, changes, and equivalents may occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the disclosure.

Claims

CLAIMS What is claimed is:

1. A Wireless Local Area Network (WLAN) Termination (WT) node comprising: an Evolved Node B (eNB) interface configured to receive from an eNB downlink traffic of one or more Evolved Universal Mobile Telecommunications System (UMTS)

Terrestrial Radio Access Network (E-UTRAN) Radio Access Bearers (E-RABs);

a WLAN interface configured to send the downlink traffic to a User Equipment

(UE) via a WLAN; and

a controller configured to generate a status report message and to send the status report message to the eNB via the eNB interface, the status report message comprising E-

RAB status information and UE status information, the E-RAB status information comprising information corresponding to communication of the downlink traffic of the one or more E-

RABs, and the UE status information comprising information corresponding to a WLAN link with the UE.

2. The WT node of claim 1, wherein the E-RAB status information comprises one or more E-RAB items corresponding to respective ones of the one or more E-RABs, an E-RAB item comprising an E-RAB identifier (ID) of an E-RAB, and E-RAB status information corresponding to the E-RAB.

3. The WT node of claim 1, wherein the E-RAB status information comprises delivered and lost Packet Data Convergence Protocol (PDCP) information corresponding to an E-RAB.

4. The WT node of claim 3, wherein the delivered and lost PDCP information comprises a highest successfully delivered PDCP sequence number (SN) and one or more lost PDCP SN ranges.

5. The WT node of claim 1, wherein the E-RAB status information comprises a buffer size for an E-RAB.

6. The WT node of claim 1 , wherein the UE status information comprises a minimum buffer size to communicate with the UE the downlink traffic of the one or more E-RABs.

7. The WT node of claim 1, wherein the UE status information comprises an average data rate corresponding to the WLAN link.

8. The WT node of claim 1, wherein the UE status information comprises an achievable data rate corresponding to the WLAN link.

9. The WT node of claim 1 , wherein the UE status information comprises link quality information corresponding to the WLAN link.

10. The WT node of any one of claims 1-9, wherein said eNB interface is configured to receive said downlink traffic according to a Transmission Control Protocol/Internet Protocol (TCP/IP).

11. The WT node of any one of claims 1-9, wherein said eNB interface is configured to receive said downlink traffic according to a tunneling protocol.

12. The WT node of any one of claims 1-9, wherein the status report message comprises a Downlink Delivery Status Report message.

13. The WT node of any one of claims 1-9 configured to operate as an Access Point (AP), the WLAN interface comprising a WLAN radio configured to transmit said downlink traffic to said UE via a WLAN link.

14. The WT node of any one of claims 1-9 configured to operate as an Access Controller (AC), the WLAN interface comprising an Access Point (AP) interface configured to send said downlink traffic to an AP.

15. The WT node of any one of claims 1-9 comprising:

a memory; and

a processor.

16. A system of cellular communication comprising an evolved Node B (eNB) comprising, the eNB comprising:

an air interface configured to communicate with a User Equipment (UE) via a cellular link;

a Wireless Local Area Network (WLAN) Termination (WT) node interface configured to communicate with a WT node; and a controller configured to control routing of at least part of downlink traffic to the UE via the WT node based at least on a status report message from the WT node, the downlink traffic comprising downlink traffic of one or more Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) Radio Access Bearers (E-RABs), the status report message comprising E-RAB status information and UE status information, the E-RAB status information comprising information corresponding to communication of the downlink traffic of the one or more E-RABs, and the UE status information comprising information corresponding to a WLAN link with the UE.

17. The system of claim 16, wherein the E-RAB status information comprises a buffer size for an E-RAB.

18. The system of claim 17, wherein the controller is configured to reduce an amount of downlink traffic of the E-RAB routed via the WT node, if the buffer size for the E-RAB is larger than an E-RAB buffer threshold.

19. The system of any one of claims 16-18, wherein the UE status information comprises a minimum buffer size to communicate with the UE the downlink traffic of the one or more E-RABs.

20. The system of claim 19, wherein the controller is configured to increase an amount of downlink traffic routed to the UE via the WT node, if the minimum buffer size is less than a WLAN buffer threshold.

21. A method to be performed by a Wireless Local Area Network (WLAN) Termination (WT), the method comprising:

receiving from an Evolved Node B (eNB) downlink traffic of one or more Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) Radio Access Bearers (E-RABs);

sending the downlink traffic to a User Equipment (UE) via a WLAN; and generating a status report message and sending the status report message to the eNB, the status report message comprising E-RAB status information and UE status information, the E-RAB status information comprising information corresponding to communication of the downlink traffic of the one or more E-RABs, and the UE status information comprising information corresponding to a WLAN link with the UE.

22. The method of claim 21, wherein the E-RAB status information comprises one or more E-RAB items corresponding to respective ones of the one or more E-RABs, an E-RAB item comprising an E-RAB identifier (ID) of an E-RAB, and E-RAB status information corresponding to the E-RAB.

23. A product comprising one or more tangible computer-readable non-transitory storage media comprising computer-executable instructions operable to, when executed by at least one computer processor, enable the at least one computer processor to implement the method of claim 21 or 22.

24. A product comprising one or more tangible computer-readable non-transitory storage media comprising computer-executable instructions operable to, when executed by at least one computer processor, enable the at least one computer processor to implement one or more operations at an evolved Node B (eNB), the operations comprising:

communicating with a User Equipment (UE) via a cellular link; and

controlling routing of at least part of downlink traffic to the UE via a Wireless Local Area Network (WLAN) Termination (WT) node based at least on a status report message from the WT node, the downlink traffic comprising downlink traffic of one or more Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) Radio Access Bearers (E-RABs), the status report message comprising E-RAB status information and UE status information, the E-RAB status information comprising information corresponding to communication of the downlink traffic of the one or more E- RABs, and the UE status information comprising information corresponding to a WLAN link with the UE.

25. The product of claim 24, wherein the E-RAB status information comprises one or more E-RAB items corresponding to respective ones of the one or more E-RABs, an E-RAB item comprising an E-RAB identifier (ID) of an E-RAB, and E-RAB status information corresponding to the E-RAB.