EP3216275B1

EP3216275B1 - Apparatus, system and method of selecting a mobility mode of a user equipment (ue)

Info

Publication number: EP3216275B1
Application number: EP15858077.9A
Authority: EP
Inventors: Alexander Sirotkin; Jing Zhu; Nageen Himayat
Original assignee: Apple Inc
Current assignee: Apple Inc
Priority date: 2014-11-06
Filing date: 2015-10-06
Publication date: 2022-03-16
Anticipated expiration: 2035-10-06
Also published as: KR20170057396A; US9838957B2; CN106797607A; US20160135120A1; KR102274337B1; EP3216275A4; WO2016073112A1; JP2017537568A; CN106797607B; JP6449471B2; EP3216275A1

Description

TECHNICAL FIELD

Some embodiments described herein generally relate to selecting a mobility mode of a User Equipment (UE).

BACKGROUND

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 Long Term Evolution (LTE) cellular connection, as well as a wireless-local-area-network (WLAN) connection, e.g., a Wireless-Fidelity (WiFi) connection.
There exists a need for solutions to enhance a level of cooperation and/or integration between WLAN and cellular networks.
WO 2014/166101 A1 describes a technique allowing communication via multiple access systems. An apparatus comprises a controller configured to cause control of a transceiver which is configured to communicate via at least two access systems. At least two access control commands are received from distinct sources. A conflict is detected between the two commands. The conflict is resolved by causing to withdraw one of the at least two access control commands based on a priority relation between the two conflicting access control commands.
3GPP TS 24.312 V12.6.1 defines management objects that can be used by the ANDSF and the UE.

SUMMARY OF INVENTION

There is provided a User Equipment, UE, the UE comprising a Wireless Local Area Network, WLAN, transceiver configured to communicate with a WLAN access point; a cellular transceiver (146) configured to communicate with a cellular node; an Access Network Discovery and Selection Function ,ANDSF, client module configured to receive a Management Object ,MO, from an ANDSF server, the MO including a first WLAN mobility priority node (210) including a first WLAN mobility type indicator to indicate a cellular/WLAN aggregation mode, and a first WLAN mobility priority value to indicate a priority of the cellular/WLAN aggregation mode, the MO further including a second WLAN mobility priority node including a second WLAN mobility type indicator to indicate an ANDSF mode, and a second WLAN mobility priority value to indicate a priority of the ANDSF mode; and a controller configured to select between the cellular/WLAN aggregation mode and the ANDSF mode based on a comparison between the first WLAN mobility priority value and the second WLAN mobility priority value when the first WLAN mobility priority value and the second WLAN mobility priority value are within a predefined priority range.

BRIEF DESCRIPTION OF THE DRAWINGS

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.

Fig. 1 is a schematic block diagram illustration of a system, in accordance with some demonstrative embodiments.
Fig. 2 is a schematic illustration of a policy node sub-object of an Access Network Discovery and Selection Function (ANDSF) Management Object (MO), in accordance with some demonstrative embodiments.
Fig. 3 is a schematic flow-chart illustration of a method of selecting a mobility mode of a User Equipment (UE), in accordance with some demonstrative embodiments.
Fig. 4 is a schematic flow-chart illustration of a method of selecting a mobility mode of a UE, in accordance with some demonstrative embodiments.
Fig. 5 is a schematic illustration of a product, in accordance with some demonstrative embodiments.

DETAILED DESCRIPTION

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 User Equipment (UE), a Mobile Device (MD), a wireless station (STA), 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 wireless node, a base station (BS), 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 Long Term Evolution (LTE) specifications (including 3GPP TS 36.300 ( 3GPP TS 36.300 V11.7.0 (2013-09); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 11)) ; 3GPP TS 36.331 (3GPP TS 36.331 V11.5.0 (2013-09); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification (Release 11) ); 3GPP TS 24.302 ( 3GPP TS 24.302 V12.3.0 (2013-12); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 (Release 12) ); 3GPP 25.331 ( 3GPP TS 25.331 V11.7.0 (2013-09); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Radio Resource Control (RRC); Protocol specification (Release 11) ); 3GPP TS 25.304 ( 3GPP TS 25.304 V11.4.0 (2013-09); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; User Equipment (UE) procedures in idle mode and procedures for cell reselection in connected mode (Release 11)) ; 3GPP TS 23.402 ( 3GPP TS 23.402 V12.3.0 (2013-12); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements for non-3GPP accesses (Release 12) ); and 3GPP TS 24.312 ( 3GPP TS 24.312 V12.3.0 (2013-12); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Access Network Discovery and Selection Function (ANDSF) Management Object (MO) (Release 12))), 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, 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 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, 4.5G, Fifth Generation (5G) mobile networks, 3GPP, Long Term Evolution (LTE) cellular system, LTE advance cellular system, LTE Unlicensed systems, 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. 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.
Some embodiments are described herein with respect to a LTE network. However, other non-claimed 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.
Some embodiments are described herein with respect to a WLAN system. However, other non-claimed embodiments may be implemented in any other suitable non-cellular network.
Some non-claimed 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.
Reference is now made to Fig. 1, which schematically illustrates a block diagram of a system 100, in accordance with some demonstrative embodiments.
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, for example, a radio channel, a cellular channel, an RF channel, a Wireless Fidelity (WiFi) channel, an IR channel, and the like, e.g., as described below. One or more elements of system 100 may optionally be capable of communicating over any suitable wired communication links.
In some demonstrative embodiments, system 100 may include at least one User Equipment (UE) 102 capable of communicating with one or more wired networks 180 via at least one Radio Access Network (RAN) 119, and/or via at least one non-cellular network, e.g., as described below.
In some demonstrative embodiments, UE 102 may include, for example, a mobile computer, a MD, a STA, 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 Internet of Things (loT) 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 non-claimed embodiments, networks 180 may include one or more Packet Data Networks (PDNs). For example, networks 180 may include an Internet network, an IP Multimedia Core Network Subsystem (IMS) network, and/or any other PDN. In other embodiments, networks 180 may include any other suitable additional and/or alternative network.
In some non-claimed embodiments, RAN 119 may include one or more cells controlled by one or more cellular nodes ("nodes"). For example, RAN 119 may include an evolved Node B (eNB) 104, a Node B 196, and/or any other cellular node, e.g., a Base Station (BS), a Base Transceiver Station (BTS), and the like.
In some non-claimed embodiments, eNB 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.
In some non-claimed embodiments, system 100 may include a non-cellular network, for example, a WLAN, e.g., a Basic Service Set (BSS), managed by a WLAN Access Point (AP) 106.
In some non-claimed embodiments, the non-cellular network may at least partially be within a coverage area of RAN 119. For example, AP 106 may be within a coverage area of eNB 104.
In some non-claimed embodiments, system 100 may also include a Core Network (CN or CNW) 160, which may be configured to provide one or more services to UE 102, and/or to setup and/or manage communication between UE 102 and RAN 119 and/or networks 180, e.g., as described below.
In some non-claimed embodiments, CN 160 may include one or more PDN Gateways (PGWs) 173 to support a PDN connection between UE 102 and a PDN of network 180.
A PGW 173 may be associated with an Access Point Name (APN). UE 102 may utilize the APN of a PGW 173, for example, to facilitate a connection to network 180 via the PGW 173.
Core network 160 may include an Access Network Discovery and Selection Function (ANDSF) server 162, which may be configured to assist UE 102 in communicating with and/or steering between one or more steering traffic between Radio Access Technology (RAT) networks, for example, RAN 119 and/or WLAN AP 106, e.g., as described below.
ANDSF server 162 may include an ANDSF policy module 168 to determine one or more ANDSF Management Objects (MOs) 163 including one or more ANDSF policies, e.g., as described below.
ANDSF policy module 168 may include or may be implemented using suitable circuitry and/or logic, e.g., controller 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 module 168. Additionally or alternatively, one or more functionalities of module 168 may be implemented by logic, which may be executed by a machine and/or one or more processors, e.g., as described below.
ANDSF server 162 may include one or more interfaces to interface between ANDSF server 162 and one or more other elements of system 100, e.g., as described below.
ANDSF server 162 may include a communication interface 164 to communicate the one or more ANDSF MOs 163 to UE 102. For example, interface 164 may communicate the ANDSF MOs 163 via RAN 119 and/or via WLAN AP 106. In one example, interface 164 may include an S14 interface to communicate with UE 102 via as S14 reference point, or any other interface.
UE 102 includes an ANDSF client module 148 configured to communicate with ANDSF server 162. For example, ANDSF client module 148 is configured to receive from ANDSF server 162 one or more ANDSF policies, e.g., in one or more ANDSF MOs.
The ANDSF policies may include information configured to assist and/or direct UE 102 to communicate with one or more WLANs, e.g., via WLAN AP 106 and/or one or more other WLAN APs.
UE 102, eNB 104, WLAN AP 106, and/or Node B 196 may include one or more wireless communication units to perform wireless communication between UE 102, RAN 119, AP 106 and/or with one or more other wireless communication devices, e.g., as described below.
UE 102 includes a cellular Transceiver (TRx) 146 to communicate with RAN 119, and a WLAN TRx 147 to communicate with WLAN AP 106.
In a preferred embodiment, cellular TRx 146 and/or WLAN TRx 147 may include, or may be associated with, one or more antennas. In one example, UE 102 may include 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.
Antenna 112, and/or 114 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 and/or 114 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 and/or 114 may include a phased array antenna, a dipole antenna, a single element antenna, a set of switched beam antennas, and/or the like.
Antennas 112 and/or 114 may implement transmit and receive functionalities using separate transmit and receive antenna elements. In some embodiments, antennas 112 and/or 114 may implement transmit and receive functionalities using common and/or integrated transmit/receive elements.
Cellular TRx 146 and/or WLAN TRx 147 may include one or more wireless transmitters, receivers and/or transceivers including circuitry and/or logic able to send and/or receive wireless communication signals, RF signals, frames, blocks, transmission streams, packets, messages, data items, and/or data.
WLAN TRx 147 is configured to communicate with AP 106 over a WLAN link, and cellular transceiver 146 is configured to communicate with RAN 119 over a cellular link.
The WLAN link may include, for example, a Wireless Fidelity (WiFi) link, a Wireless Gigabit (WiGig) link, or any other link. In some non-claimed embodiments, the WLAN link may include, for example, a link over the 2.4 Gigahertz (GHz) or 5GHz frequency band, the 60 GHz frequency band, or any other frequency band.
Cellular TRx 146 may include a multiple input multiple output (MIMO) transmitters receivers system (not shown) including circuitry and/or logic, which may be capable of performing antenna beamforming methods, if desired. In other embodiments, cellular TRx 146 may include any other transmitters and/or receivers.
Cellular TRx 146 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 other embodiments, cellular TRx 146 may include any other encoder and/or decoder.
Cellular TRx 146 may include OFDM and/or SC-FDMA modulators and/or demodulators (not shown) including circuitry and/or logic configured to communicate OFDM signals over downlink channels, e.g., between RAN 119 and UE 102, and SC-FDMA signals over uplink channels, e.g., between UE 102 and RAN 119. In other embodiments, cellular TRx 146 may include any other modulators and/or demodulators.
WLAN TRx 147 may establish a WLAN link with AP 106. For example, WLAN TRx 147 may perform the functionality of one or more STAs, e.g., one or more WiFi STAs, WLAN STAs, and/or millimeter Wave (mmWave) STAs. The WLAN link may include an uplink and/or a downlink. The WLAN downlink may include, for example, a unidirectional link from AP 106 to the one or more STAs. The uplink may include, for example, a unidirectional link from a STA to AP 106.
UE 102 may be configured to utilize a cellular connection, e.g., a Long Term Evolution (LTE) cellular connection, a Universal Mobile Telecommunications System (UMTS) connection or any other cellular connection, to communicate with RAN 119, and a WLAN connection, e.g., a Wireless-Fidelity (WiFi) connection or any other WLAN connection, to communicate with AP 106.
Cellular TRx 146 utilize the cellular link between UE 102 and RAN 119 to communicate traffic of one or more PDN connections, e.g., via one or more PGWs 173.
UE 102 may establish one or more bearers, e.g., one or more Evolved Packet-switched System (EPS) bearers, via the one or more PDN connections between UE 102 and one or more PGWs 173.
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.
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.
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
System 100 may utilize Multi-RAT small cells integrating multiple radios such as WiFi and 3GPP air interfaces in a single infrastructure device.
System 100 may implement any other architecture and/or deployment.
In a preferred embodiment, UE 102 may also include, for example, one or more of a processor 124, an input unit 116, an output unit 118, a memory unit 120, and a storage unit 122. UE 102 may optionally include other suitable hardware components and/or software components. In some demonstrative embodiments, some or all of the components of UE 102 may be enclosed in a common housing or packaging, and may be interconnected or operably associated using one or more wired or wireless links.
ANDSF server 162 may also include, for example, a processor 172 and/or a memory unit 171. ANDSF server 162 may optionally include other suitable hardware components and/or software components. In some non-claimed embodiments, some or all of the components of ANDSF server 162 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 non-claimed embodiments, components of MME 162 may be distributed among multiple or separate devices.
Processor 124 and/or processor 172 includes, 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. Processor 124 executes instructions, for example, of an Operating System (OS) of UE 102 and/or of one or more suitable applications. Processor 172 executes instructions, for example, of an Operating System (OS) of ANDSF server 162 and/or of one or more suitable applications.
Input unit 116 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 118 includes, for example, a monitor, a screen, a touch-screen, a flat panel display, a Cathode Ray Tube (CRT) 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 120 includes, 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 122 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. Memory unit 120 and/or storage unit 122, for example, may store data processed by UE 102. Memory unit 171 may store, for example, data processed by ANDSF server 162.
eNB 104, WLAN AP 106, and/or UE 102 may be configured to enable a tightly coupled cellular-WLAN interworking system architecture, e.g., as described below.
eNB 104 and WLAN AP 106 may be implemented in the form of a coupled eNB/AP.
The coupled eNB/AP may include eNB circuitry configured to perform the functionality of eNB 104, and WLAN AP circuitry, e.g., AP circuitry configured to perform the functionality of WLAN AP 106.
eNB 104 and WLAN AP 106 may be implemented as part of a common device, e.g., an integrated eNB/AP device. In other embodiments, eNB 104 and WLAN AP 106 may be implemented as separate and/or independent units or devices. For example, the coupled eNB/AP may include separate eNB and AP devices, which may be coupled together.
System 100 may implement any other architecture and/or deployment.
eNB 104, WLAN AP 106, and/or UE 102 may be configured to communicate according to a cellular/WLAN protocol aggregation scheme (also referred to as cellular/WLAN aggregation"), e.g., as described below.
The cellular/WLAN aggregation scheme may include, for example, an LTE/WLAN aggregation scheme, for example, if system 100 includes an LTE cellular system.
The cellular/WLAN aggregation scheme may include any other cellular/WLAN aggregation scheme, for example, if system 100 includes any other cellular system.
LTE/WLAN protocol stack aggregation may be configured to enable LTE interworking with a WLAN protocol stack.
The LTE/WLAN protocol stack aggregation may be configured to anchor WLAN mobility at eNB 104.
A WLAN link between UE 102 and WLAN AP 106 may be aggregated above a MAC layer.
The LTE/WLAN protocol stack aggregation may be configured to aggregate the WLAN protocol stack above an LTE Packet Data Convergence Protocol (PDCP) layer.
The LTE protocol stack aggregation may be configured to aggregate the WLAN protocol stack below the LTE PDCP layer.
The LTE/WLAN protocol stack aggregation may include an encapsulation protocol, which may be configured to encapsulate messages between UE 102 and eNB 104, for example, via a tunnel, which may be set up between UE 102 and eNB 104, for example through WLAN AP 106.
eNB 104 and/or UE 102 may be configured to use a control protocol, for example, a Radio Resource Control (RRC) protocol and/or any other protocol, for example, to enable UE 102 and WLAN AP 106 to discover one another, and to set up and/or establish a WLAN link between UE 102 and WLAN AP 106.
UE 102, eNB 104, and/or WLAN AP 106 may be configured to enable UE 102 to operate at a cellular/WLAN aggregation mode, e.g., according to the cellular/WLAN aggregation scheme. For example, UE 102, eNB 104, and/or WLAN AP 106 may be configured to enable UE 102 to operate at a LTE/WLAN aggregation mode, e.g., according to the LTE/WLAN aggregation scheme.
UE 102 may receive from eNB 104 an indication, e.g., via RRC signaling, to indicate to UE 102 to use a WLAN in a cellular/WLAN aggregation mode.
UE 102 may be configured to operate at an ANDSF mode, in which, for example, communication of UE 102 with the WLAN may be controlled, for example, based on an ANDSF policy from ANDSF server 162.
When operating at the cellular/WLAN aggregation mode, the WLAN communication between UE 102 and WLAN AP 106 may be, for example, fully controlled by the cellular network, e.g., the LTE network.
At the cellular/WLAN aggregation mode, UE 102 may communicate with a WLAN access device, e.g., WLAN AP 106, anchored at a cellular node, e.g., eNB 104.
When operating at the cellular/WLAN aggregation mode, UE 102 may be able to perform WLAN communication, for example, even without the need to use the services of ANDSF server 162.
In some scenarios, use-cases and/or implementations, there may be a need to resolve one or more potential coexistence issues, for example, between the cellular/WLAN aggregation scheme and the ANDSF scheme, e.g., as described below.
Some operators may deploy network elements to support an ANDSF scheme, for example, prior to deploying network elements to support a LTE/WLAN aggregation scheme. Accordingly, there may be coexistence issues, which need to be resolved, for example, during an upgrade from the ANDSF scheme to the LTE/WLAN aggregation scheme.
Some operators may deploy network elements to support LTE/WLAN aggregation, for example, in one or more certain areas, while deploying one or more network elements supporting ANDSF, for example, in one or more, e.g., different, areas. In one example, the LTE/WLAN aggregation may be supported in dense areas, and/or 3rd party WLAN service providers with ANDSF may be used in some other areas.
A UE, e.g., UE 102, may have ANDSF policies, and may roam into a network, which may deploy LTE/WLAN aggregation.
Some operators may deploy network elements supporting a RAN-based LTE/WAN aggregation, for example, as well as EPC-based Seamless WLAN offload, e.g., Wi-Fi Offload, e.g. S2a/S2b/S2, in the same area. For example, ANDSF may be used to control which mode a UE should operate in.
One or more potential coexistence issues may be configured to be resolved, for example, between the cellular/WLAN aggregation scheme and the ANDSF scheme, in the implementations listed above and/or in any other scenarios, use-cases and/or implementations.
LTE/WLAN aggregation and ANDSF coexistence issues may be configured to be resolved, for example, by configuring LTE/WLAN aggregation to take precedence over ANDSF policies, for example, to always take precedence over ANDSF policies, e.g., as described below.
LTE/WLAN aggregation and ANDSF coexistence issues may be configured to be resolved, for example, by configuring a UE, e.g., UE 102, which may have an active ANDSF policy, such that the ANDSF policy takes precedence over LTE/WLAN aggregation, for example, such that the ANDSF policy always takes precedence over LTE/WLAN aggregation, e.g., as described below.
The LTE/WLAN aggregation may be used by the UE, for example, only when the UE has no valid ANDSF policy.
LTE/WLAN aggregation and ANDSF coexistence issues may be configured to be resolved, for example, by enhancing ANDSF policies to enable signaling a preference and/or priority between multiple WLAN mobility schemes, e.g., as described below.
ANDSF server 162 may be configured to generate an ANDSF policy, which may be configured to enable an operator to control and/or signal to a UE, for example, when and/or for which UEs LTE/WLAN aggregation is preferable over ANDSF, and/or vise versa, e.g., as described below.
ANDSF server 162 is configured to generate an ANDSF policy, which is configured to enable an operator to control a mode of operation of a UE, for example, when both RAN-based LTE/WLAN aggregation and ANDSF- based mobility, e.g., EPC-based seamless Wi-Fi offload (S2a/S2b/S2c), are supported in the same area, e.g., as described below.
UE 102 may include a controller 145, which may be configured to control a WLAN mobility mode of operation of UE 102, e.g., as described below.
Controller 145 may include or may be implemented using suitable circuitry and/or logic, e.g., controller 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 controller 145. Additionally or alternatively, one or more functionalities of controller 145 may be implemented by logic, which may be executed by a machine and/or one or more processors, e.g., as described below.
Controller 145 may select the WLAN mobility mode to include a cellular/WLAN aggregation mode, e.g., an LTE/WLAN aggregation mode, or an ANDSF mode, e.g., as described below.
Controller 145 may cause UE 102 to communicate with a WLAN, e.g., WLAN AP 106, according to the selected WLAN mobility mode, as determined by controller 145, e.g., as described below.
At the cellular/WLAN aggregation mode, controller 145 may control communication of UE 102 with a WLAN access device, e.g., WLAN AP 106, anchored at a cellular node, e.g., eNB 104, for example, as described above.
At the ANDSF mode, controller 145 may control communication of UE 102 with the WLAN, for example, based on an ANDSF policy from an ANDSF server, e.g., ANDSF server 162.
Controller 145 may be configured to select the WLAN mobility mode from the cellular/WLAN aggregation mode and the ANDSF mode, for example, based on a preconfigured selection criterion, e.g., as described below.
The preconfigured selection criterion may be configured such that the cellular/WLAN aggregation mode may take precedence, e.g., may always take precedence, over the ANDSF mode, e.g., as described below.
The preconfigured selection criterion may include selecting the cellular/WLAN aggregation mode over the ANDSF mode, for example, when UE 102 is instructed by a cellular node, e.g., eNB 104, to use the cellular/WLAN aggregation mode.
Controller 145 may be configured to disable an indication of WLAN presence to ANDSF client 148, for example, when the cellular/WLAN aggregation mode is selected.
Controller 145 may cause UE 102 to avoid informing ANDSF client 148 about WLAN network presence, for example, if the network, e.g., eNB 104, instructs UE 102 to use WLAN in aggregation mode. According to this example, from a perspective of ANDSF client 148, UE 102 would not detect any WLAN networks that ANDSF client may use, for example, whenever LTE/WLAN aggregation is used.
The preconfigured selection criterion may be configured such that the ANDSF mode may take precedence, e.g., may always take precedence, over the cellular/WLAN aggregation mode, e.g., as described below.
The preconfigured selection criterion may include controller 145 selecting the ANDSF mode over the cellular/WLAN aggregation mode, for example, when ANDSF client 148 has an active ANDSF policy.
The preconfigured selection criterion may include controller 145 selecting the cellular/WLAN aggregation mode over the ANDSF mode, for example, only when ANDSF client 148 has no active ANDSF policy.
Controller 145 may cause UE 102 to ignore an indication, e.g., an RRC indication, from RAN 119, e.g., from eNB 104, to use the WLAN in the LTE/WLAN aggregation mode, for example, if UE has an active ANDSF policy, and the preconfigured selection criterion is to select the cellular/WLAN aggregation mode over the ANDSF mode.
UE 102 and/or ANDSF server 162 may be configured to use an ANDSF policy, which may be configured to indicate a preference of the cellular/WLAN aggregation mode or the ANDSF mode, e.g., as described below.
ANDSF policy module 168 may be configured to generate a MO including an ANDSF node ("LTEWLANAggregationPreference") including a WLAN mobility mode preference configured to indicate whether ANDSF or LTE/WLAN Aggregation is to be preferred.
ANDSF policy module 168 may be configured to set the LTEWLANAggregationpreference indication to a first value, e.g., zero, to indicate that the ANDSF mobility mode is to be preferred over the cellular/WLAN aggregation mode; or to a second value, e.g., one, to indicate that the cellular/WLAN aggregation mode is to be preferred over the ANDSF mobility mode.
ANDSF client module 148 may receive from ANDSF server 162 the ANDSF MO including the WLAN mobility mode preference to indicate the preference between the cellular/WLAN aggregation mode and the ANDSF mode.
Controller 145 may select between the cellular/WLAN aggregation mode and the ANDSF mode, for example, based on the WLAN mobility mode preference.
Controller 145 may select the cellular/WLAN aggregation mode over the ANDSF mode, for example, when the WLAN mobility mode preference indicates that the cellular/WLAN aggregation mode is to be preferred, and UE 102 is instructed by eNB 104 to use the cellular/WLAN aggregation mode.
Controller 145 may disable an indication of WLAN presence to the ANDSF client 148, for example, when the WLAN mobility mode preference indicates that the cellular/WLAN aggregation mode is to be preferred, and UE 102 is instructed by eNB 104 to use the cellular/WLAN aggregation mode.
Controller 145 select the ANDSF mode over the cellular/WLAN aggregation mode, for example, when the WLAN mobility mode preference indicates that the ANDSF mode is to be preferred, and the ANDSF client 148 has an active ANDSF policy.
Controller 145 may be configured to, when the WLAN mobility mode preference indicates that the ANDSF mode is to be preferred, select the cellular/WLAN aggregation mode over the ANDSF mode, for example, only when the ANDSF client 148 has no active ANDSF policy.
UE 102 may receive from ANDSF server 162 an MO including the LTEWLANAggregationpreference indication set to 0, and UE 102 may have a valid ANDSF rule, e.g., a valid Inter-System Routing Policy (ISRP) or a valid Inter System Mobility Policy (ISMP). According to this example, controller 145 may be configured to cause UE 102 to route traffic according to ANDSF rule, and not to use LTE/WLAN aggregation. For example, controller 145 may cause UE 102 to report no WLAN measurements to eNB 104, and/or to prevent LTE/WLAN aggregation in any other way, e.g. by sending an appropriate indication to eNB 104.
ANDSF policy module 168 may be configured to determine an ANDSF MO including one or more ANDSF policies, the ANDSF MO including a WLAN mobility priority node, the WLAN mobility priority node including a WLAN mobility type indicator to indicate a cellular/WLAN aggregation mode, and a WLAN mobility priority value to indicate a priority of the cellular/WLAN aggregation mode, e.g., as described below.
The ANDSF MO may include an ANDSF node ("PrioritizedSeamlessWLANMobility") to indicate which WLAN mobility mode, e.g. RAN-based LTE/WLAN aggregation, EPC-based (S2a/b/c) Seamless Wi-Fi offload, or any other mobility mode, that a UE, e.g., UE 102, is to select, for example, when multiple WLAN mobility modes are supported and/or available, for example, in the same area, e.g., as described below.
ANDSF server 162 may send the ANDSF MO to UE 102, and UE 102 may receive the ANDSF MO.
Controller 145 may be configured to select between the cellular/WLAN aggregation mode and the ANDSF mode, for example, based on the WLAN mobility priority value, e.g., as described below.
ANDSF policy module 168 may set the WLAN mobility priority value to include a value within a predefined priority range, e.g., as described below.
In a preferred embodiment, the priority range may be, for example, between 1 and 250, e.g., as described below. In other embodiments, the priority range may include any other range of values.
ANDSF policy module 168 sets the ANDSF MO to include a plurality of WLAN mobility priority nodes to indicate priorities of a plurality of WLAN mobility modes as described below.
ANDSF policy module 168 sets the ANDSF MO to include a first WLAN mobility priority node including a first WLAN mobility type indicator to indicate the cellular/WLAN aggregation mode and a first WLAN mobility priority value to indicate the priority of the cellular/WLAN aggregation mode.
ANDSF policy module 168 sets the ANDSF MO to include at least a second WLAN mobility priority node including a second WLAN mobility type indicator to indicate an ANDSF mode and a second WLAN mobility priority value to indicate a priority of the ANDSF mode.
ANDSF policy module 168 sets the first priority value to include a first value within the predefined priority range, and to set the second priority value to include a second value within the predefined priority range, to indicate that a UE, e.g., UE 102, is to select between the cellular/WLAN aggregation mode and the ANDSF mode based on a comparison between the first and second priority values as described below.
Controller 145 is configured to select between the cellular/WLAN aggregation mode and the ANDSF mode based on a comparison between the WLAN mobility priority value of the cellular/WLAN aggregation mode, the first priority value, and the WLAN mobility priority value of the ANDSF mode, the second priority value.
Controller 145 may be configured to select between the cellular/WLAN aggregation mode and the ANDSF mode, for example, by selecting the WLAN mobility mode corresponding to the lowest priority value between the first and second priority values, e.g., as described below.
ANDSF policy module 168 may set the WLAN mobility priority value to a predefined value ("the restrict-selection value") to indicate that UE 102 is to restrict selection of the cellular/WLAN aggregation mode.
In a preferred embodiment, the restrict-selection value may be 254, or any other value, e.g., which is not within the priority range.
In a preferred embodiment, controller 145 may be configured to restrict selection of the cellular/WLAN aggregation mode by UE 102, for example, when the WLAN mobility priority value includes the restrict-selection value.
ANDSF policy module 168 may set the WLAN mobility priority value to a predefined value ("the forbid-selection value") to indicate that UE 102 is forbidden to select the cellular/WLAN aggregation mode.
In a preferred embodiment, the forbid-selection value may be 255, or any other value, e.g., which is not within the priority range.
In a preferred embodiment, controller 145 may be configured to forbid selection of the cellular/WLAN aggregation mode by UE 102, for example, when the WLAN mobility priority value includes the forbid-selection value.
A roaming UE, e.g., UE 102, may have a valid ISRP or ISMP rule, e.g., from a Home Public Land Mobile Network (HPLMN). The roaming UE 102 may be configured to route traffic according to ANDSF.
When UE 102 is roaming and ANDSF client 148 has a valid ISRP or ISMP rule, e.g., from a HPLMN, controller 145 may select the ANDSF mode over the cellular/WLAN aggregation mode. For example, controller 145 may cause UE 102 to ignore an indication, e.g., an RRC indication, from RAN 119, e.g., from eNB 104, to use the WLAN in the LTE/WLAN aggregation mode.
Fig. 2 is a schematic illustration of a policy node sub-object 200 of an ANDSF MO. For example, node-sub object 200 may be included in an ANDSF MO generated by ANDSF policy module 168 (Fig. 1), an ANDSF MO sent by ANDSF server 162 (Fig. 1), and/or an ANDSF MO received by UE 102 (Fig. 1).
Node sub-object 200 may include a WLAN mobility priority node ("PrioritizedSeamlessWLANMobility") 210 to indicate a priority and/or preference between a plurality of WLAN mobility modes, e.g., as described below.
The WLAN mobility priority node 210 may act as a placeholder for parameters defining priorities of one or more WLAN mobility modes.
WLAN mobility priority node 210 may be defined, e.g., as follows:
<X>/Policy/<X>/PrioritizedAccess/PrioritizedSeamlessWLANMobility

Occurrence: ZeroOrOneOrMore
Format: node
Access Types: Get, Replace
Values: N/A

Node 210 may include a WLAN mobility type indicator (leaf) ("WLANMobilityType") 212 to indicate a WLAN mobility mode that a WLAN may support.
Leaf 212 may be defined, e.g., as follows:
X>/Policy/<X>/PrioritizedAccess/PrioritizedSeamlessWLANMobility/WL ANMobilityType

Occurrence: One
Format: int
Access Types: Get, Replace
Values: <WLAN mobility type>.

The value of the WLAN mobility type leaf 212 may be set, for example, according to the following table, or according to any other predefined set of values:

Table 1: Possible values for the WLANMobilityType leaf

Value	Description
0	Reserved
1	S2a based Seamless WLAN Offload (SaMOG)
2	RAN-based WLAN/3GPP link aggregation (aka eNB-anchored WLAN mobility)
3	S2b based Seamless WLAN Offload
4	S2c based Seamless WLAN Offload
5-255	Reserved

Node 210 may include a WLAN mobility priority indicator (leaf) ("WLANMobilityPriority") 214 to indicate a priority corresponding to the WLAN mobility mode type.
Leaf 214 may be defined, e.g., as follows:
X>/Policy/<X>/PrioritizedAccess/PrioritizedSeamlessWLANMobility/WL ANMobilityType

Occurrence: One
Format: int
Access Types: Get, Replace
Values: <WLAN mobility priority>.

The value of the WLAN mobility priority leaf 214 may be set, for example, according to the following table, or according to any other predefined set of values:

Table 2: Values of WLANMobilityPriority leaf

Value	Description
0	Reserved
1-250	Priority value
251-253	Reserved
254	Restricted access. This WLAN mobility type should be avoided if the current rule is active.
255	Forbidden. UE is not allowed to use this WLAN mobility type if the current rule is active.

The value of WLAN mobility priority leaf 214 corresponding to a WLAN mobility mode type may be set to a value within the range of 1-250, for example, to indicate a priority of the WLAN mobility mode type, for example, relative to priorities of one or more other WLAN mobility mode types.
ANDSF policy module 168 (Fig. 1) may generate an ANDSF MO including the node sub-object 200 including a first WLAN mobility node 210 including a first WLAN mobility type 212, e.g., cellular/WLAN aggregation, and a first priority value 214 within the range 1-250; and a second WLAN mobility node 210 including a second WLAN mobility type 212, e.g., S2aSeamless WLAN offload, and a second priority value 214 within the range 1¬250.
The first WLAN mobility type 212, e.g., cellular/WLAN aggregation, may be prioritized over the second WLAN mobility type 212, e.g., S2aSeamless WLAN offload, for example, if the first priority value is lesser than the second priority value.
Controller 145 (Fig. 1) may be configured to select a WLAN mobility mode from a plurality of available WLAN mobility modes, for example, based on the node sub-object 200.
Controller 145 (Fig. 1) may be configured to prioritize between a plurality of WLAN mobility types, for example, based on the priority values corresponding to the plurality of WLAN mobility types.
More than one WLAN mobility type may be available to UE 102 (Fig. 1). For example, node sub-object 200 may include a plurality of WLAN mobility priority nodes 210.
Two or more WLAN mobility priority nodes 210 may include two or more respective priority WLAN mobility priority leafs 214 having priority values within the range 1-250.
Controller 145 (Fig. 1) may consider the WLAN mobility type, e.g., together with a corresponding access identifier if present, with the lowest WLANMobilityPriority value, as the WLAN mobility mode, e.g., together with the corresponding access identifier if present, having the highest priority, e.g., as defined in Table 2.
ANDSF policy module 268 may set the WLANMobilityPriority value 214 corresponding to a WLAN mobility mode indicated by WLAN mobility type 212 to a "restricted access" value, e.g., 254, to indicate the WLAN mobility mode should not be used by UE 102, for example, to indicate that controller 145 (Fig. 1) should avoid using the WLAN mobility mode, e.g., as described above.
ANDSF policy module 268 may set the WLANMobilityPriority value 214 corresponding to a WLAN mobility mode indicated by WLAN mobility type 212 to a "forbidden access" value, e.g., 255, to indicate the WLAN mobility mode shall not be used by UE 102, for example, to indicate that controller 145 (Fig. 1) is forbidden from using the WLAN mobility mode, e.g., as described above.
The same WLANMobilityPriority value may be used for more than one WLAN mobility type.
More than one WLAN mobility type with the same value of the WLANMobilityPriority may be available for UE 102 (Fig. 1). According to these embodiments, controller 145 (Fig. 1) may be configured to select for UE 102 (Fig. 1) one of the available WLAN mobility types, for example, in an implementation dependent way.
Fig. 3 is a schematic flow-chart illustration of a method of selecting a mobility mode of a UE, 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 UE, e.g., UE 102 (Fig. 1); and/or a controller, e.g., controller 145 (Fig. 1).
As indicated at block 302, the method may include communicating with a cellular node of a cellular network. For example, UE 102 (Fig. 1) may communicate with eNB 104 (Fig. 1), e.g., as described above.
As indicated at block 304, the method may include selecting a WLAN mobility mode from a cellular/WLAN aggregation mode and an ANDSF mode based on a preconfigured selection criterion. For example, controller 145 (Fig. 1) may select between the cellular/WLAN aggregation mode and the ANDSF mode based on a preconfigured selection criterion, e.g., as described above.
As indicated at block 306, selecting the WLAN mobility mode based on the preconfigured selection criterion may include selecting the cellular/WLAN aggregation mode over the ANDSF mode, when the UE is instructed by the cellular node to use the cellular/WLAN aggregation mode. For example, controller 145 (Fig. 1) may select the cellular/WLAN aggregation mode over the ANDSF mode, for example, when UE 102 (Fig. 1) is instructed by eNB 104 (Fig. 1) to use the cellular/WLAN aggregation mode
As indicated at block 308, selecting the WLAN mobility mode based on the preconfigured selection criterion may include selecting the ANDSF mode over the cellular/WLAN aggregation mode, when an active ANDSF policy is available. For example, controller 145 (Fig. 1) may select the ANDSF mode over the cellular/WLAN aggregation mode, for example, when ANDSF client 148 (Fig. 1) has an active ANDSF policy available, e.g., as described above.
As indicated at block 310, the method may include communicating with a WLAN according to the WLAN mobility mode. For example, controller 145 (Fig. 1) cause UE (Fig. 1) to communicate with a WLAN according to the WLAN mobility mode, e.g., as described above.
Fig. 4 is a schematic flow-chart illustration of a method of selecting a mobility mode of a UE, in accordance with some demonstrative embodiments. In some embodiments, one or more of the operations of the method of Fig. 4 may be performed by a wireless communication system e.g., system 100 (Fig. 1); a UE, e.g., UE 102 (Fig. 1); an ANDSF server, e.g., ANDSF server 162 (Fig. 1); an ANDSF policy module, e.g., ANDSF policy module 168 (Fig. 1); and/or a controller, e.g., controller 145 (Fig. 1).
As indicated at block 402, the method may include generating an ANDSF MO including one or more ANDSF policies, the ANDSF MO including a WLAN mobility priority node, the WLAN mobility priority node including a WLAN mobility type indicator to indicate a cellular/WLAN aggregation mode, and a WLAN mobility priority value to indicate a priority of the cellular/WLAN aggregation mode. For example, ANDSF policy module may generate the ANDSF MO including one or more WLAN mobility priority nodes 210 (Fig. 1), e.g., as described above.
As indicated at block 404, the method may include send the ANDSF MO to a UE. For example, ANDSF server 162 may send the ANDSF Mo to UE 102 (Fig. 1), e.g., as described above.
As indicated at block 406, the method includes receiving the ANDSF Mo at the UE. For example, ANDSF client module 148 (Fig. 1) receives the ANDSF Mo from ANDSF server 162 (Fig. 1), as described above.
As indicated at block 408, the method may include selecting between the cellular/WLAN aggregation mode and an ANDSF mode based on the WLAN mobility priority value. For example, controller 145 (Fig. 1) may select between the cellular/WLAN aggregation mode and an ANDSF mode, for example, based on the WLAN mobility priority value, e.g., as described above.
Reference is made to Fig. 5, which schematically illustrates a product of manufacture 500, in accordance with some demonstrative embodiments. Product 500 may include a non- transitory machine-readable storage medium 502 to store logic 504, which may be used, for example, to perform at least part of the functionality of UE 102 (Fig. 1), eNB 104 (Fig. 1), node B 196 (Fig. 1), ANDSF server 162 (Fig. 1), controller 145 (Fig. 1), and/or ANDSF policy module 168 (Fig. 1), and/or to perform one or more operations of the methods of Figs. 3 and/or 4. The phrase "non-transitory machine-readable medium" is directed to include all computer- readable media, with the sole exception being a transitory propagating signal.
Product 500 and/or machine-readable storage medium 502 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 502 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.
Logic 504 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.
Logic 504 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.
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.
While certain features have been illustrated and described herein, many modifications, substitutions, and changes falling within the scope of the claims 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.

Claims

A User Equipment, UE, comprising:
a Wireless Local Area Network, WLAN, transceiver (147) configured to communicate with a WLAN access point (106);

a cellular transceiver (146) configured to communicate with a cellular node (104);

an Access Network Discovery and Selection Function ,ANDSF, client module (148) configured to receive a Management Object ,MO, from an ANDSF server (162), the MO including a first WLAN mobility priority node (210) including a first WLAN mobility type indicator (212) to indicate a cellular/WLAN aggregation mode, and a first WLAN mobility priority value (214) to indicate a priority of the cellular/WLAN aggregation mode, the MO further including a second WLAN mobility priority node (210) including a second WLAN mobility type indicator (212) to indicate an ANDSF mode, and a second WLAN mobility priority value (214) to indicate a priority of the ANDSF mode; and

a controller (145) configured to select between the cellular/WLAN aggregation mode and the ANDSF mode based on a comparison between the first WLAN mobility priority value (214) and the second WLAN mobility priority value (214) when the first WLAN mobility priority value (214) and the second WLAN mobility priority value (214) are within a predefined priority range.
The UE of claim 1, wherein the priority range is between 1 and 250.
The UE of any one of claims 1-2, wherein the controller is further configured to restrict selection of the cellular/ WLAN aggregation mode, when the first WLAN mobility priority value is set to a predefined value.
The UE of claim 3, wherein said predefined value is 254.
The UE of any one of claims 1-2, wherein the controller is further configured to forbid selection of the cellular/ WLAN aggregation mode, when the first WLAN mobility priority value is set to a predefined value.
The UE of claim 5, wherein said predefined value is 255.
The UE of any one of claims 1-2 wherein the UE includes one or more antennas, a memory and a processor.