Patent Description:
A wireless communication device, e.g., a mobile device, may be configured to utilize multiple wireless communication technologies.

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.

There is a need for efficient interworking, integration and/or management of the cellular and WLAN radio access technologies.

The following document is relevant: <CIT>, titled "WLAN-to-WWAN handover methods and apparatus using a WLAN support node having a WWAN" which relates generally to handover methods and apparatus between heterogeneous wireless networks, such as WLANs (e.g. IEEE <NUM> based networks) and WWANs (e.g. cellular telecommunication networks), for mobile communication devices. The base station in <CIT> uses the same air interface to communicate with a UE and a WLAN access device.

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.

Aspects or embodiments of the disclosure which do not fall under the scope of the claims are not included in the scope of invention.

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.

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.

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.

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.

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.

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, 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.

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 "TS <NUM> Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage <NUM>, version <NUM>. <NUM> Release <NUM>", September <NUM>) 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 <NUM>, April <NUM>, Final specification) and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing IEEE <NUM> standards (IEEE <NUM>-<NUM>, IEEE Standard for Information technologyTelecommunications and information exchange between systems Local and metropolitan area networks--Specific requirements Part <NUM>: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications, March <NUM>, <NUM>), and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing IEEE <NUM> standards (IEEE-Std <NUM>, <NUM> Edition, Air Interface for Fixed Broadband Wireless Access Systems; IEEE-Std <NUM>. 16e, <NUM> Edition, Physical and Medium Access Control Layers for Combined Fixed and Mobile Operation in Licensed Bands; amendment to IEEE Std <NUM>-<NUM>, 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.

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 (TDMA), Extended TDMA (E-TDMA), General Packet Radio Service (GPRS), extended GPRS, Code-Division Multiple Access (CDMA), Wideband CDMA (WCDMA), CDMA <NUM>, 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 (<NUM>), <NUM>, <NUM>, <NUM>, <NUM>, Fifth Generation (<NUM>) 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.

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.

The term "communicating" as used herein with respect to a wireless communication signal includes transmitting the wireless communication signal and/or receiving the wireless communication signal. For example, a wireless communication unit, which is capable of communicating a wireless communication signal, may include a wireless transmitter to transmit the wireless communication signal to at least one other wireless communication unit, and/or a wireless communication receiver to receive the wireless communication signal from at least one other wireless communication unit.

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 <NUM> cellular network, a <NUM> cellular network, a <NUM> cellular network, a WiMax cellular network, and the like.

Some demonstrative embodiments are described herein with respect to a WLAN system. However, other embodiments may be implemented in any other suitable non-cellular network.

Some demonstrative embodiments are described herein with respect to an Access Point (AP). However, other embodiments may be implemented in any other WLAN access device, for example, an Access Controller (AC).

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, mmWave, 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.

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.

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 cellular 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.

The phrase "access point" (AP), as used herein, may include an entity that includes a station (STA) and provides access to distribution services, via the Wireless Medium (WM) for associated STAs.

The term "station" (STA), as used herein, may include any logical entity that is a singly addressable instance of a medium access control (MAC) and a physical layer (PHY) interface to the WM.

Reference is now made to <FIG>, which schematically illustrates a block diagram of a system <NUM>, in accordance with some demonstrative embodiments.

As shown in <FIG>, in some demonstrative embodiments, system <NUM> may include one or more wireless communication devices capable of communicating content, data, information and/or signals via one or more wireless mediums <NUM>. For example, system <NUM> may include at least one User Equipment (UE) <NUM> capable of communicating with one or more wireless communication networks, e.g., as described below.

Wireless mediums <NUM> may include, for example, a radio channel, a cellular channel, an RF channel, a Wireless Fidelity (WiFi) channel, an IR channel, and the like. One or more elements of system <NUM> may optionally be capable of communicating over any suitable wired communication links.

In some demonstrative embodiments, system <NUM> may include at least one cellular manager <NUM> to manage communication of a cellular network, e.g., as described below.

In some demonstrative embodiments, cellular manager <NUM> may perform the functionality of an Evolved Node B (eNB). For example, cellular manager <NUM> 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.

In other embodiments, cellular manager <NUM> 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.

In one example, cellular manager <NUM> may be part of a UMTS. According to this example, cellular manager <NUM> may perform the functionality of a Radio Network Controller (RNC), which may control a plurality of Node B devices <NUM>. For example, the node B may be configured to communicate directly with UEs, e.g., including UE <NUM>, 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 <NUM>.

In some demonstrative embodiments, system <NUM> may include a WLAN access device <NUM> to manage access to a non-cellular network <NUM>, for example, a WLAN, e.g., a Basic Service Set (BSS).

In some demonstrative embodiments, WLAN access device <NUM> may include a WLAN AP, e.g., as described below.

In other embodiments, WLAN access device <NUM> 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.

In one example, WLAN access device <NUM> may perform the functionality of an Access Controller (AC). According to this example, WLAN access device <NUM> may control a plurality of AP devices, e.g., Lightweight Access Point (LAP) devices <NUM>.

In some demonstrative embodiments, UE <NUM> may include, for example, a mobile computer, a laptop computer, a notebook computer, a tablet computer, an Ultrabook™ computer, 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.

In some demonstrative embodiments, UE <NUM>, cellular manager <NUM> and/or WLAN access device <NUM> may include one or more communication interfaces to perform communication between UE <NUM>, cellular manager <NUM>, WLAN access device <NUM> and/or with one or more other wireless communication devices, e.g., as described below.

Some demonstrative embodiments include an interface (also referred to as "the access device interface", "the horizontal interface", "the Xn-W interface" or "the cellular/WLAN interface"), which may be configured to directly interface between a cellular network element, e.g., cellular manager <NUM>, and a WLAN element, e.g., WLAN access device <NUM>, as described in detail below.

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

In some demonstrative embodiments, the cellular/WLAN interface 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.

In some demonstrative embodiments, the horizontal interface 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.

In some demonstrative embodiments, cellular manager <NUM> includes an interface ("Core Network (CN) interface") <NUM>, e.g., a vertical interface, to communicate with one or more elements of a CN <NUM>, e.g., an Evolved Packet Core (EPC).

In some demonstrative embodiments, CN interface <NUM> may include an S1 vertical interface configured to communicate between cellular manager <NUM> and a Serving Gateway (S-GW) <NUM> according to an S1 protocol, e.g., if cellular manager <NUM> performs the functionality of an eNB. According to this example, S-GW <NUM> may interface between cellular manager <NUM> and a Packet Data Network (PDN) Gateway (P-GW) <NUM>.

In other embodiments, CN interface <NUM> may include any other vertical interface with one or more elements of CN <NUM>. For example, cellular manger <NUM> may perform the functionality of an RNC, e.g., in a UMTS system. According to this example, CN interface <NUM> 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.

In some demonstrative embodiments, cellular manager <NUM> may include an interface to communicate user plane traffic, directly or indirectly, between CN <NUM> and UE <NUM>.

In some demonstrative embodiments, cellular manager <NUM> may communicate the user plane traffic directly with UE <NUM>, for example, if cellular manager <NUM> performs the functionality of an eNB. According to these embodiments, cellular manager <NUM> includes an air interface, for example, a cellular transceiver (TRx) <NUM>, configured to communicate with UE <NUM> via a cellular link.

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

In some demonstrative embodiments, cellular manager <NUM> includes an access device interface <NUM> to communicate directly with WLAN access device <NUM>, e.g., as described below. In one example, interface <NUM> may include an AP interface, e.g., if WLAN access device <NUM> performs the functionality of an AP. In another example, interface <NUM> may include an AC interface, e.g., if WLAN access device <NUM> performs the functionality of an AC.

In some demonstrative embodiments, WLAN access device <NUM> may include a cell manager interface ("the cellular interface") <NUM> to communicate directly with cellular manager <NUM>, e.g., as described below. In one example, interface <NUM> may include an eNB interface, e.g., if cellular manager <NUM> performs the functionality of an eNB. In another example, interface <NUM> may include a RNC interface, e.g., if cellular manager <NUM> performs the functionality of a RNC.

In some demonstrative embodiments, interfaces <NUM> and <NUM> may be configured to communicate between cellular manager <NUM> and WLAN access device <NUM> via a direct link <NUM>, e.g., as described below.

In some demonstrative embodiments, link <NUM> may include a Point to Point (P2P) link, e.g., as described below.

In some demonstrative embodiments, link <NUM> may be implemented by any wired and/or wireless link, e.g., using any suitable, Physical Layer (PHY) components and/or protocols.

In some demonstrative embodiments, link <NUM> may include a wired link.

In some demonstrative embodiments, link <NUM> 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, link <NUM> may include any wired link.

In some demonstrative embodiments, WLAN access device <NUM> may include a network interface <NUM> to communicate network traffic with a wired network <NUM>, e.g., the Internet or any other network.

In some demonstrative embodiments, WLAN access device <NUM> may include an interface to communicate the network traffic and/or any other traffic, directly or indirectly, with UE <NUM>.

In some demonstrative embodiments, WLAN access device <NUM> may communicate directly with UE <NUM>, for example, if WLAN access device <NUM> performs the functionality of an AP. According to these embodiments, WLAN access device <NUM> may include a WLAN radio <NUM> to communicate the network traffic and/or any other traffic directly with UE <NUM>, e.g., via a WLAN link between WLAN access device <NUM> and UE <NUM>, for example, if WLAN access device <NUM> performs the functionality of an AP.

In some demonstrative embodiments, WLAN access device <NUM> may indirectly communicate with UE <NUM>, for example, if WLAN access device <NUM> performs the functionality of an AC. According to these embodiments, WLAN access device <NUM> may include an AP interface, e.g., a LAP interface <NUM>, to communicate the network traffic and/or any other traffic with LAP <NUM>.

In some demonstrative embodiments, UE <NUM> may include a WLAN transceiver (TRx) <NUM> configured to communicate with a WLAN device, e.g., with WLAN access device <NUM> and/or with LAP <NUM>, via the WLAN link.

In some demonstrative embodiments, UE <NUM> may include a cellular transceiver (TRx) <NUM> configured to communicate with a cellular device, e.g., cellular manager <NUM> and/or Node B <NUM>, via the cellular link.

In some demonstrative embodiments, WLAN access device <NUM> may include at least one controller <NUM> to control communications performed by WLAN access device <NUM>, cellular manager <NUM> may include at least one controller <NUM> to control communications performed by cellular manager <NUM>, and/or UE <NUM> may include at least one controller <NUM> to control communications performed by UE <NUM>, e.g., as described below.

In some demonstrative embodiments, WLAN TRx <NUM>, cellular TRx <NUM>, cellular TRx <NUM> and/or WLAN radio <NUM> may include one or more wireless transmitters, receivers and/or transceivers able to send and/or receive wireless communication signals, RF signals, frames, blocks, transmission streams, packets, messages, data items, and/or data.

In some demonstrative embodiments, cellular TRx <NUM> and/or cellular TRx <NUM> 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 <NUM> and/or cellular TRx <NUM> may include any other transmitters and/or receivers.

In some demonstrative embodiments, cellular TRx <NUM> and/or cellular TRx <NUM> may include LTE, WCDMA and/or TD-SCDMA modulators and/or demodulators (not shown) configured to communicate downlink signals over downlink channels, e.g., between cellular manager <NUM> and UE <NUM>, and uplink signals over uplink channels, e.g., between UE <NUM> and cellular manager <NUM>. In other embodiments, cellular TRx <NUM> and/or cellular TRx <NUM> may include any other modulators and/or demodulators.

In some demonstrative embodiments, UE <NUM> may establish a WLAN link with WLAN access device <NUM>. For example, WLAN TRx <NUM> 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 WLAN access device <NUM> to the one or more STAs. The uplink may include, for example, a unidirectional link from a STA to WLAN access device <NUM>.

In some demonstrative embodiments, UE <NUM>, WLAN access device <NUM> and/or cellular manager <NUM> may include, or may be associated with, one or more antennas. In one example, WLAN TRx <NUM> and cellular TRx <NUM> may be associated with at least two antennas, e.g., antennas <NUM> and <NUM>, or any other number of antennas, e.g., one antenna or more than two antennas; cellular TRx <NUM> may be associated with at least two antennas, e.g., antennas <NUM> and <NUM>, or any other number of antennas, e.g., one antenna or more than two antennas; and/or WLAN radio <NUM> may be associated with one or more antennas <NUM>.

In some demonstrative embodiments, antennas <NUM>, <NUM>, <NUM>, <NUM> and/or <NUM> 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 <NUM>, <NUM>, <NUM>, <NUM> and/or <NUM> may include any suitable configuration, structure and/or arrangement of one or more antenna elements, components, units, assemblies and/or arrays. For example, antennas <NUM>, <NUM>, <NUM>, <NUM> and/or <NUM> may include a phased array antenna, a dipole antenna, a single element antenna, a set of switched beam antennas, and/or the like.

In some embodiments, antennas <NUM>, <NUM>, <NUM>, <NUM> and/or <NUM> may implement transmit and receive functionalities using separate transmit and receive antenna elements. In some embodiments, antennas <NUM>, <NUM>, <NUM>, <NUM> and/or <NUM> may implement transmit and receive functionalities using common and/or integrated transmit/receive elements.

In some demonstrative embodiments, cellular manager <NUM>, WLAN access device <NUM>, and/or UE <NUM> 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 <NUM> may include a processor <NUM> and a memory <NUM>; WLAN access device <NUM> may include a processor <NUM> and a memory <NUM>; and/or UE <NUM> may include a memory <NUM>, a processor <NUM>, an input unit <NUM>, an output unit <NUM>, and/or a storage unit <NUM>. UE <NUM>, cellular manager <NUM> and/or WLAN access device <NUM> 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 <NUM>, cellular manager <NUM> and/or WLAN access device <NUM> 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 <NUM>, cellular manager <NUM> and/or WLAN access device <NUM> may be distributed among multiple or separate devices.

Processors <NUM>, <NUM> and/or <NUM> 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 multipurpose or specific processor or controller. For example, processor <NUM> may execute instructions, for example, of an Operating System (OS) of cellular manager 104and/or of one or more suitable applications; processor <NUM> may execute instructions of an OS of WLAN access device <NUM> and/or of one or more suitable applications; and/or processor <NUM> may execute instructions of an OS of UE <NUM> and/or of one or more suitable applications.

Input unit <NUM> includes, 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 <NUM> 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.

Memory unit <NUM>, <NUM> and/or <NUM> includes, for example, a Random Access Memory (RAM), a Read Only Memory (ROM), a Dynamic RAM (DRAM), a Synchronous DRAM (SDRAM), 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 <NUM> 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 <NUM> may store data processed by cellular manager <NUM>; and/or memory unit <NUM> may store data processed by WLAN access device <NUM>.

In some demonstrative embodiments, UE <NUM> may be configured utilize a cellular connection, e.g., a LTE cellular connection or any other cellular connection, to communicate with cellular manager <NUM>, and a WLAN connection, e.g., a Wireless-Fidelity (WiFi) connection, a mmWave connection, a P2P connection, or any other WLAN connection, to communicate with WLAN access device <NUM>.

In some demonstrative embodiments, one or more elements of system <NUM> 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.

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.

In one example, system <NUM> 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.

In another example, system <NUM> may utilize Multi-RAT small cells integrating multiple radios such as WiFi and 3GPP air interfaces in a single infrastructure device.

In other embodiments, system <NUM> may implement any other architecture and/or deployment.

In some demonstrative embodiments, cellular manager <NUM> and WLAN access device <NUM> may be configured to communicate directly via interface <NUM>, 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.

In some demonstrative embodiments, cellular manager <NUM> and WLAN access device <NUM> may be configured to communicate directly via interface <NUM>, 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.

In some demonstrative embodiments, cellular manager <NUM> and WLAN access device <NUM> may be configured to communicate user plane messages and/or control plane messages via interface <NUM>, e.g., as described below.

In some demonstrative embodiments, cellular manager <NUM> and WLAN access device <NUM> may be configured to communicate via interface <NUM> user plane packets including user plane traffic corresponding to UE <NUM>, e.g., as described below.

In some demonstrative embodiments, the user plane packets may include downlink traffic to be provided to UE <NUM>, e.g., as described below.

In some demonstrative embodiments, the downlink traffic includes downlink traffic from CN <NUM> ("the CN downlink traffic"), e.g., as described below.

In some demonstrative embodiments, cellular manager <NUM> may receive the CN downlink traffic, e.g., via CN interface <NUM>. Cellular manager <NUM> may use access device interface <NUM> to send the CN downlink traffic to WLAN access device <NUM>. According to these embodiments, WLAN access device <NUM> may receive the CN download traffic from cellular manager <NUM>, e.g., via interface <NUM>, and may send the CN download traffic to UE <NUM> via the WLAN.

In one example, WLAN access device <NUM> may directly transmit the CN downlink traffic to UE <NUM>, e.g., via WLAN radio <NUM>, for example, if WLAN access device <NUM> performs the functionality of an AP.

In another example, WLAN access device <NUM> may send the CN downlink traffic to UE <NUM> via LAP <NUM>, e.g., via LAP interface <NUM>, for example, if WLAN access device <NUM> performs the functionality of an AC.

In some demonstrative embodiments, the downlink traffic may include downlink traffic from network <NUM> ("the network downlink traffic"), e.g., as described below.

In some demonstrative embodiments, WLAN access device <NUM> may receive the network downlink traffic, e.g., via network interface <NUM>. WLAN access device <NUM> may use interface <NUM> to send the network downlink traffic to cellular manager <NUM>. According to these embodiments, cellular manager <NUM> receives the network download traffic from WLAN access device <NUM>, e.g., via interface <NUM>, and sends the network download traffic to UE <NUM> via the cellular network.

In one example, cellular manager <NUM> may directly transmit the network downlink traffic to UE <NUM>, e.g., via cellular TRx <NUM>, for example, if cellular manager <NUM> performs the functionality of an eNB.

In another example, cellular manager <NUM> may send the network downlink traffic to UE <NUM> via Node B <NUM>, e.g., via interface <NUM>, for example, if cellular manager <NUM> performs the functionality of a RNC.

In some demonstrative embodiments, transferring the downlink traffic between cellular manager <NUM> and WLAN access device <NUM> via interface <NUM> may enable for example, to enhance, e.g., optimize, mobility of UE <NUM> between the cellular and WLAN radio networks.

In some demonstrative embodiments, cellular manager <NUM> and WLAN access device <NUM> may utilize interface <NUM> to forward downlink user packets, for example, during handover of UE <NUM> from a first RAT ("the source RAT") to a second RAT ("the target RAT"). For example, cellular manager <NUM> and WLAN access device <NUM> may utilize interface <NUM> to forward downlink user packets, which may be buffered in the source RAT, to the target RAT, e.g., in order to reduce and/or prevent packet loss.

In one example, the source RAT may include the cellular RAT and the target RAT may include the WLAN RAT, e.g., during handover of UE <NUM> from a cellular node to a WLAN AP. According to this example, cellular manager <NUM> may send the CN downlink traffic to WLAN access device <NUM> via interface <NUM>, for example, during handover of UE <NUM> from the cellular network to the WLAN.

In another example, the source RAT may include the WLAN RAT and the target RAT may include the cellular RAT, e.g., during handover of UE <NUM> from a WLAN AP to a cellular node. According to this example, WLAN access device <NUM> may send the network downlink traffic to cellular manager <NUM> via interface <NUM>, for example, during handover of UE <NUM> from the WLAN to the cellular network.

In some demonstrative embodiments, cellular manager <NUM> and WLAN access device <NUM> may be configured to operate according to an anchor-booster architecture, e.g., as described below.

In some demonstrative embodiments, the anchor-booster architecture is configured to provide to UE <NUM> dual connectivity, for example, to both the cellular RAT and the WLAN RAT, e.g., simultaneously.

In some demonstrative embodiments, when operating according to the anchor-booster architecture, cellular manager may perform the functionality of an anchor cell, which may be configured to route traffic between CN <NUM> and UE <NUM>; and WLAN access device <NUM> may be perform the functionality of a booster cell, which may be configured to forward at least some of the traffic to UE <NUM>, e.g., as described below.

In some demonstrative embodiments, controller <NUM> may select to forward CN downlink traffic ("the forwarded traffic") to WLAN access device <NUM>, for example, if WLAN access is available to UE <NUM>. For example, the forwarded traffic may be sent from cellular manager <NUM> to WLAN access device <NUM> over link <NUM>, e.g., via interfaces <NUM> and <NUM>.

In some demonstrative embodiments, WLAN access device <NUM> may send the forwarded traffic to UE <NUM> via the WLAN. For example, controller <NUM> may control WLAN radio <NUM> to transmit the forwarded traffic to UE <NUM> via the WLAN link, e.g., if WLAN access device <NUM> performs the functionality of an AP. In another example, controller <NUM> may control interface <NUM> the send the forwarded traffic to LAP <NUM>, e.g., if WLAN access device <NUM> performs the functionality of an AC.

In some demonstrative embodiments, the anchor-booster architecture may enable communicating traffic with UE <NUM> via both cellular access and WLAN access simultaneously.

In some demonstrative embodiments, the traffic communicated via the booster cell may utilize WLAN security and/or authentication provided by the WLAN, or cellular security and/or authentication provided by cell manager <NUM>, e.g., depending on a protocol used to split the traffic between the cellular and WLAN RATs.

In some demonstrative embodiments, the anchor-booster architecture may allow selectively splitting the traffic between the cellular and WLAN RATs, for example, on a per-bearer basis, e.g., different bearers may be sent via different RATs, or a single bearer may be split between the WLAN and cellular RATs.

In some demonstrative embodiments, controller <NUM> may dynamically split the CN downlink traffic between the cellular and WLAN RATs. For example, controller <NUM> may select to forward first downlink traffic to UE <NUM> via the booster cell, and to send second downlink traffic via the cellular network.

In some demonstrative embodiments, controller <NUM> may control interface <NUM> to send the first downlink traffic to WLAN access device <NUM>, e.g., via link <NUM>. Controller <NUM> may control cellular TRx <NUM> to transmit the second downlink traffic to UE <NUM> via the cellular link, e.g., if cellular manager <NUM> performs the functionality of an eNB. Controller <NUM> may control interface <NUM> to send the second downlink traffic to Node B <NUM>, e.g., if cellular manager <NUM> performs the functionality of a RNC.

In some demonstrative embodiments, the first and second downlink traffic may include downlink traffic of a same radio bearer. In other embodiments, the first and second downlink traffic may include downlink traffic of different radio bearers.

In some demonstrative embodiments, cellular manager <NUM> and WLAN access device <NUM> may be configured to communicate via interface <NUM> control plane messages to control one or more operations and/or functionalities of cellular manager <NUM> and WLAN access device <NUM>, e.g., as described below.

In some demonstrative embodiments, the control plane messages may include load-related information corresponding to a load of the WLAN and/or the cellular network, e.g., as described below.

In some demonstrative embodiments, WLAN access device <NUM> may send load-related information to cellular manager <NUM> via link <NUM>. The load-related information may include information corresponding to a WLAN load of the WLAN controlled by WLAN access device <NUM>. For example, the load-related information may include an actual load, for example, a Basis Service Set (BSS) load of a BSS controlled by WLAN access device <NUM>, a station count of a number of stations connected to the BSS, a backhaul data rate, interference information, and/or any other information and/or parameters.

In some demonstrative embodiments, WLAN access device <NUM> and cellular manager <NUM> may be configured to communicate the load-related information over link <NUM>, for example, to enhance the efficiency of usage of radio resources and/or to enhance load balancing between the cellular and WLAN RATs.

In some demonstrative embodiments, WLAN access device <NUM> and cellular manager <NUM> may be configured to communicate the load-related information over link <NUM> in a periodic manner. For example, WLAN access device <NUM> may periodically send the load-related information to cellular manger <NUM>.

In some demonstrative embodiments, cellular manager <NUM> may be configured to trigger WLAN access device <NUM> to send the load-related information via link <NUM>. For example, interface <NUM> may send to interface <NUM> a request for a load report via link <NUM>, and interface <NUM> may send to interface <NUM> a load report including the load-related information.

In some demonstrative embodiments, WLAN access device <NUM> may be configured to trigger the sending of the load-related information to cellular manager <NUM> via link <NUM>. For example, controller <NUM> may detect an overload condition corresponding to the WLAN, and controller <NUM> may control interface <NUM> to send to cellular manager <NUM> an indication of an overload start event and/or and overload stop event, e.g. via link <NUM>.

In some demonstrative embodiments, the control plane messages may include configuration information corresponding to a configuration of the cellular and/or WLAN networks.

In some demonstrative embodiments, the control plane messages may include WLAN identification information to identify one or more other WLAN access devices. For example, controller <NUM> may control interface <NUM> to send to cellular manager <NUM> control plane messages including identifiers of one or more other WLAN access devices. The identifiers may include, for example, a Service Set Identifier (SSID), a Hot Spot (HS) <NUM> identifier, and/or any other WLAN identifier.

In some demonstrative embodiments, interface <NUM> may receive the WLAN identification information, and controller <NUM> may utilize the WLAN identification information to configure communication with the one or more WLAN access devices. For example, enabling WLAN access device <NUM> to provide the WLAN identification information to cellular manager <NUM> via link <NUM> may enable, for example, reducing Operations, Administration and Management (OAM) processes.

In some demonstrative embodiments, the control plane messages may include UE context information corresponding to UE <NUM>. For example, controller <NUM> may control interface <NUM> to send to WLAN access device <NUM> UE context information corresponding to UE <NUM>.

In some demonstrative embodiments, the UE context information may include, for example, security information corresponding to UE <NUM>, an IP address assigned to UE <NUM> and/or any other context corresponding to UE <NUM>.

In some demonstrative embodiments, cellular manager <NUM> may send the UE context information to WLAN access device <NUM> via link <NUM>, for example, prior to handover of UE <NUM> to WLAN access device <NUM>.

In some demonstrative embodiments, the ability to transfer the UE context information from cellular manager <NUM> to WLAN access device <NUM> via link <NUM> may enable, for example, to reduce WLAN connection time of UE <NUM>, e.g., during the handover to WLAN access device <NUM>.

In some demonstrative embodiments, the control plane messages may include, for example, one or more booster cell management messages to manage WLAN access device <NUM> as the booster cell, e.g., as described above.

In some demonstrative embodiments, cellular manager <NUM> may send via link <NUM> an indication or request to WLAN access device <NUM> to add or remove WLAN access device <NUM> as a booster cell.

In some demonstrative embodiments, cellular manager <NUM> may use link <NUM> to indicate to WLAN access device <NUM> a configuration of the anchor-booster architecture, for example, to inform WLAN access device <NUM>, which WLAN identifiers are to be used by WLAN access device <NUM>.

In some demonstrative embodiments, WLAN access device <NUM> may use link <NUM> to send to cellular manager a request to reconfigure or remove the functionality of WLAN access device <NUM> as the booster cell.

Reference is made to <FIG>, which schematically illustrates a method of interfacing between a cellular manager and a WLAN access device, in accordance with some demonstrative embodiments. In some embodiments, one or more of the operations of the method of <FIG> may be performed by a wireless communication system e.g., system <NUM> (<FIG>); a cellular manager, e.g., cellular manager <NUM> (<FIG>); a WLAN access device, e.g., WLAN access device <NUM> (<FIG>); an interface, e.g., interface <NUM> (<FIG>), interface <NUM> (<FIG>), interface <NUM> (<FIG>), interface <NUM> (<FIG>), interface <NUM> (<FIG>), and/or interface <NUM> (<FIG>); and/or a controller, e.g., controller <NUM> (<FIG>) and/or controller <NUM> (<FIG>).

As indicated at block <NUM>, the method may include communicating between a cellular manager and a WLAN access device via a direct link between the cellular manager and the WLAN access device. For example, cellular manager <NUM> (<FIG>) may utilize interface <NUM> (<FIG>), and WLAN access device <NUM> (<FIG>) may utilize interface <NUM> (<FIG>), to communicate via direct link <NUM> (<FIG>) between cellular manager <NUM> (<FIG>) and WLAN access device <NUM> (<FIG>), e.g., as described above.

As indicated at block <NUM>, the method may include configuring the direct link between the cellular manager and the WLAN access device. For example, interfaces <NUM> (<FIG>) and <NUM> (<FIG>) may exchange one or more control plane messages to configure link <NUM> (<FIG>), e.g., as described above.

As indicated at block <NUM>, the method may include communicating one or more user plane messages between the cellular manager and the WLAN access device via the direct link between. For example, cellular manager <NUM> (<FIG>) and WLAN access device <NUM> (<FIG>) may communicate one or more user plane messages including traffic corresponding to UE <NUM> (<FIG>) via link <NUM> (<FIG>), e.g., as described above.

As indicated at block <NUM>, communicating the user plane control messages may include communicating downlink traffic during handover of a UE between the cellular manager and the WLAN access device. For example, cellular manager <NUM> (<FIG>) and WLAN access device <NUM> (<FIG>) may communicate downlink traffic for UE <NUM> (<FIG>) during handover of UE <NUM> (<FIG>), e.g., as described above.

As indicated at block <NUM>, communicating the user plane control messages may include sending first CN downlink traffic to the UE via the WLAN access device, and sending second CN downlink traffic to the UE via the cellular network. For example, cellular manager <NUM> (<FIG>) and WLAN access device <NUM> (<FIG>) may route the CN downlink traffic to UE <NUM> (<FIG>) according to the anchor-booster architecture, e.g., as described above.

As indicated at block <NUM>, the method may include communicating one or more control plane messages between the cellular manager and the WLAN access device via the direct link between. For example, cellular manager <NUM> (<FIG>) and WLAN access device <NUM> (<FIG>) may communicate one or more control plane messages via link <NUM> (<FIG>), e.g., as described above.

Reference is made to <FIG>, which schematically illustrates a product of manufacture <NUM>, in accordance with some demonstrative embodiments. Product <NUM> may include a non-transitory machine-readable storage medium <NUM> to store logic <NUM>, which may be used, for example, to perform at least part of the functionality of a cellular manager, e.g., cellular manager <NUM> (<FIG>); a WLAN access device, e.g., WLAN access device <NUM> (<FIG>); an interface, e.g., interface <NUM> (<FIG>), interface <NUM> (<FIG>), interface <NUM> (<FIG>), interface <NUM> (<FIG>), interface <NUM> (<FIG>), and/or interface <NUM> (<FIG>); and/or a controller, e.g., controller <NUM> (<FIG>) and/or controller <NUM> (<FIG>); and/or to perform one or more operations of the method of <FIG>. The phrase "non-transitory machine-readable medium" is directed to include all computer-readable media, with the sole exception being a transitory propagating signal.

In some demonstrative embodiments, product <NUM> and/or machine-readable storage medium <NUM> 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 <NUM> 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.

In some demonstrative embodiments, logic <NUM> 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.

In some demonstrative embodiments, logic <NUM> 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.

Claim 1:
A base station configured to manage communication of a cellular network, the base station comprising:
a vertical interface (<NUM>) to communicate with a Core Network, CN;
an air interface (<NUM>) to communicate with a User Equipment, UE, via a cellular link; and
an access device interface (<NUM>) to communicate directly with a Wireless Local Area Network, WLAN, access device configured for direct communication with the UE using a WLAN radio, the WLAN access device configured to manage access to a WLAN and including a WLAN Access Point, AP, or a WLAN Access Controller, AC;
wherein during handover of said UE from the WLAN to the cellular network:
said access device interface (<NUM>) is to receive from said WLAN access device (<NUM>) network downlink traffic, from a wired network (<NUM>), for said UE (<NUM>); and
the base station configured to directly transmit the network downlink traffic to the UE (<NUM>) via the cellular air interface (<NUM>);
wherein during handover of said UE from said base station to the WLAN access device:
said access device interface (<NUM>) is to send to said WLAN access device (<NUM>) CN downlink traffic, from the CN (<NUM>), for said UE; and
wherein when providing the UE dual connectivity:
said access device interface (<NUM>) is to send to said WLAN access device (<NUM>) first downlink traffic for said UE (<NUM>); and
said air interface (<NUM>) is to send second downlink traffic to said UE via said cellular link.