JP6370923B2 - Apparatus, system and method for communicating wireless local area network (WLAN) offloading information between cellular managers - Google Patents

Description

This application claims the benefit and priority of US Provisional Patent Application No. 61 / 990,689, filed May 8, 2014, and entitled “WLAN interworking coordination between LTE and UMTS”. Is hereby incorporated by reference.

  Some embodiments described herein generally relate to communicating wireless local area network (WLAN) offloading information between cellular managers.

  The communication system may be configured to utilize multiple wireless communication technologies including, for example, multiple radio access technologies (RAT).

  For example, a user equipment (UE) device may have a cellular connection, such as a Universal Mobile Telecommunications System (UMTS) cellular connection or a long term evolution (LTE) connection, and a wireless local area network (WLAN) connection, such as And can be configured to utilize a Wireless-Fidelity (WiFi) connection.

  There is a need for efficient interworking, integration, coordination, and / or management of multiple RATs.

For the sake of illustration simplicity and clarity, the elements shown in the figures are not necessarily drawn to scale. For example, some sizes of elements may be exaggerated relative to other elements for clarity of presentation. In addition, reference numbers may be repeated among the figures to indicate corresponding or analogous elements. The figures are listed below.
FIG. 2 is a schematic block diagram illustration of a system in accordance with some illustrative embodiments. 2 is a schematic flowchart illustration of a method of communicating wireless local area network (WLAN) offloading information between cellular managers, in accordance with some illustrative embodiments. FIG. FIG. 3 is a schematic illustration of a product, according to some illustrative embodiments.

  In the following detailed description, specific details are set forth in order to provide a thorough understanding of some embodiments. However, it will be understood by one skilled in the art that some embodiments may be practiced without such 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.

  In this specification, terms such as “process”, “calculate”, “calculate”, “determine”, “establish”, “analyze”, “confirm”, or the like The discussion utilized is a computer register that can store instructions for performing operations and / or processes on data represented as physical (eg, electronic) quantities in a computer register and / or memory. And / or operation of a computer, computing platform, computing system, or other electronic computing device that manipulates and / or converts into other data that is also similarly represented as a physical quantity in memory or other information storage medium And / or process.

  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”, “one embodiment”, “exemplary embodiment”, “various embodiments” and the like refer to specific features, structures, or characteristics of the embodiments so described. It may be included, but indicates that every embodiment does not necessarily include the specific features, structures, or characteristics described above. Further, repeated use of the phrase “in one embodiment” does not necessarily refer to the same embodiment; however, it may be.

  As used herein, unless otherwise specified, the use of the sequential adjectives “first”, “second”, “third”, etc. to describe a common object is a similar object. Only that different instances of are referenced, and the objects so described are in a given sequence, either temporally, spatially, in ranking, or in any other way It does not imply that it must be.

  Some embodiments include various devices and systems such as user equipment (UE), mobile device (MD), wireless station (STA), personal computer (PC), desktop computer, mobile computer, laptop computer, notebook Book computer, tablet computer, smart phone device, server computer, handheld computer, handheld device, personal digital assistant (PDA) device, handheld PDA device, onboard device, offboard device, hybrid device, in-vehicle (vehicular) device, non-in-vehicle device Mobile or portable devices, consumer devices, non-mobile or non-portable devices, wireless communication stations, wireless communication devices, wireless access points (AP), wireless Node, base station (BS), wired or wireless router, wired or wireless modem, video device, audio device, audio video (A / V) device, wired or wireless network, wireless area network, cellular network, cellular node, cellular device Wireless local area network (WLAN), Multiple Input Multiple Output (MIMO) transceiver or device, Single Input Multiple Output (SIMO) transceiver or device, multiple input Multiple Input Single Output (MISO) transceiver or device, device with one or more internal and / or external antennas, digital video broadcast (DVB) device or system, multi-standard wireless device or system, wired The wireless handheld device, for example, a smart phone, Wireless Application Protocol (WAP) device, vending machine, can be used in conjunction such as sales terminal.

Some embodiments include existing 3rd Generation Partnership Project (3GPP) and / or Long Term Evolution (LTE) specifications (3GPP TS 36.300 (3GPP TS 36.300 V11.7.0, September 2013). Technical specifications; 3rd generation partnership project; Technical specifications group radio access network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN) General Description; Stage 2 (Release 11)); 3GPP TS36.331 (3GPP TS36.331 V11.5.0 (September 2013); Technical Specification; Third Generation Partnership Project; Technical Specification Group Radio Access Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol Specification (Release 11)); 3GPP TS36.304 (3GPP TS36.304 V12.0.0 (March 2014) 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) Procedure in Idle Mode (Release 12)); 3GPP TS 25.300 (3GPP TS25.300 V0.1.0 (February 2014); technical specification; third generation partnership project; technical specification group radio access network; UTRAN: general description; stage 2 (release 12)); 3GPP TS 5.304 (3GPP TS25.304 V12.1.0 (March 2014); Technical Specification; Third Generation Partnership Project; Technical Specification Group Radio Access Network; User Equipment (UE) Procedure in Idle Mode and Connected Mode 3GPP TS25.331 (3GPP TS25.331 V12.1.0 (March 2014); technical specification; third generation partnership project; technical specification group radio access network; radio Protocol specifications (Release 12)); 3GPP TS36.413 (3GPP TS36.413 V12.1.0 (March 2014); Technical specifications; 3rd generation partnership project; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP); (Release 12)); and / or 3GPP TS36.423 (3GPP TS36.423 V12.1.0 (2014) 3) Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP); (Release 12)))) and Devices and / or networks operating according to future versions and / or their derivatives, existing Wireless-Gigabit-Alliance (WGA) specifications (wireless Gigabit Anse Inc WiGig MAC and PHY specification version 1.1, April 2011, final specification) and / or devices and / or networks operating in accordance with future versions and / or their derivatives, existing IEEE 802.11 standards (IEEE 802 11-2012, IEEE Standard for Information Technology-Telecommunications and Information Exchange Between Systems Local and Metropolitan Area Networks-Specific Requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications, March 29, 2012) and / or devices and / or networks operating in accordance with future versions and / or derivatives thereof, existing IEEE 802.16 standard (IEEE Standard 802.16 2009 edition, fixed broadband) Air interface for wireless access systems; IEEE standard 802.16e, 2005 edition, physical and medium access control layer for combined fixed and mobile operation in licensed bands; amendments to IEEE standard 802.16-2009 , Developed by task group m) and / or devices and / or networks operating according to future versions and / or derivatives thereof, existing WirelessHD ^™ specifications and / or future versions and / or their variants It can be used in connection with devices and / or networks that operate according to organisms, units and / or devices that are part of the network, etc.

Some embodiments may include one or more types of wireless communication signals and / or systems, eg, radio frequency (RF), frequency division multiplexing (FDM), orthogonal FDM (OFDM), multiple input multiple output (MIMO), Multi-user MIMO (MU-MIMO), 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 (General Packet Radio Service) (GPRS), extended GPRS, code division multiple access (CDMA), wideband CDMA (WCDMA (registered trademark)), CDMA2000, single carrier CDMA, multicarrier CDMA, multicarrier modulation (MDM), Discrete Multi-Tone (DMT) Bluetooth (registered trademark), a global positioning system (GPS),
Wireless Fidelity (Wi-Fi), WiMax (registered trademark), ZigBee ^TM (registered trademark), ultra wide band (UWB), Global System for Mobile Communications (Global System for Mobile communication) ( GSM ( registered trademark)), the second Generation (2G), 2.5G, 3G, 3.5G, 4G, 5th generation (5G) mobile network, 3GPP, Long Term Evolution (LTE), Cellular System, LTE Advanced 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), It can be used in connection with 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 refers to, for example, a device capable of wireless communication, a communication device capable of wireless communication, a communication station capable of wireless communication, a device capable of wireless communication. Includes portable or non-portable devices. In some illustrative embodiments, the wireless device may be a peripheral device (peripheral) integrated in a computer, a peripheral attached to the computer, or may include the peripheral. In some illustrative embodiments, the term “wireless device” may optionally include wireless services.

  The term “communicate” as used herein with respect to a communication signal includes transmitting a communication signal and / or receiving a communication signal. For example, a communication unit or interface capable of communicating a communication signal transmits a communication signal to at least one other communication unit and / or receives a communication signal from at least one other communication unit. A receiver can be included. The verb “communicate” may be used to refer to a send action or a receive action. In one example, the phrase “communicate signal” may refer to an action of transmitting a signal by a first device and does not necessarily include an action of receiving a signal by a second device. In another example, the phrase “communicate signal” may refer to an operation of receiving a signal by a first device and does not necessarily include an action of transmitting a signal by a second device.

  Several illustrative embodiments are described herein with respect to LTE networks. However, other embodiments may be used in any other suitable cellular network or system, eg, Universal Mobile Telecommunications System (UMTS) cellular system, GSM network, 3G cellular network, 4G cellular network, 4.5G network, 5G cellular It may be implemented in a network, a 6G cellular network, a WiMax cellular network, or the like.

  Several illustrative embodiments are described herein with respect to WLAN systems. However, other embodiments may be implemented in any other suitable non-cellular network.

  Several illustrative embodiments are described herein with respect to an access point (AP). However, other embodiments may be implemented in any other WLAN access device, such as an access controller (AC).

  Some illustrative embodiments can be used in connection with a Heterogeneous Network (HetNet), which can be cellular, millimeter wave (mmWave) and / or similar A mixed deployment of technology, frequency, cell size, and / or network architecture can be utilized. In one example, a hetnet may include a radio access network having layers of cells of different sizes, ranging from large macro cells to small cells, eg, pico cells and femto cells.

  Other embodiments can be used in connection with any other suitable wireless communication network.

  The term “antenna” as used herein refers to any suitable configuration, structure, and / or arrangement of one or more antenna elements, components, units, assemblies, and / or arrays. Can be included. In some embodiments, the antenna can implement transmit and receive functionality using separate transmit and receive antenna elements. In some embodiments, the antenna can implement transmit and receive functionality using common and / or integrated transmit / receive elements. The antenna can 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, eg, downlink resources and possibly uplink resources. Resources may be controlled and / or allocated by, for example, a cellular node (also referred to as a “base station”). Linking between the carrier frequency of the downlink resource and the carrier frequency of the uplink resource can be indicated in the system information transmitted on the downlink resource.

  The phrase “access point” (AP) as used herein includes a station (STA) and is distributed over the wireless medium (WM) for the associated station. Entities can be included that provide access to services.

  The term “station” (STA) as used herein is a single addressable instance for the medium access control (MAC) and physical layer (PHY) interfaces to the WM. Can include any logical entity.

  Reference is now made to FIG. FIG. 1 schematically illustrates a block diagram of a system 100 according to some illustrative embodiments.

  As shown in FIG. 1, in some illustrative embodiments, the system 100 is capable of communicating one or more wireless devices capable of communicating content, data, information, and / or signals over one or more wireless media. A communication device can be included.

  In some illustrative embodiments, elements of system 100 can be configured to communicate over, for example, a wireless channel, a cellular channel, an RF channel, a WLAN channel, a wireless fidelity (WiFi) channel, an IR channel, and the like. . One or more elements of system 100 may optionally be able to communicate through any suitable wired communication link.

  In some illustrative embodiments, the system 100 can include a multi-RAT network, where the multi-RAT network utilizes multiple RATs, eg, at least one as described below. One user equipment (UE) 118 can communicate.

In some illustrative embodiments, the UE 118 may be, for example, a mobile computer, MD, STA, laptop computer, notebook computer, tablet computer, Ultrabook ^™ computer, mobile internet device, handheld computer, handheld device, Storage device, PDA device, handheld PDA device, on-board device, off-board device, hybrid device (eg, combination of cellular phone functionality and PDA device functionality), consumer device, vehicular device, non-vehicle device Mobile or portable devices, mobile phones, cellular phones, PCS devices, mobile or portable GPS devices, DVB devices, relatively small computing devices, non-desktop computers A “Carry Small Live Large” (CSLL) device, an ultra mobile device (UMD), an ultra mobile PC (UMPC), a mobile Internet device (MID), a “origami” device or a computing device, Video devices, audio devices, A / V devices, gaming devices, media players, smartphones, and the like can be included.

  In some illustrative embodiments, the system 100 can include multiple RAT communication managers that control and / or manage communications within multiple RAT networks. For example, the system 100 may include, for example, one or more cellular managers of one or more types of cellular networks, one or more WLAN managers of one or more WLANs, and / or any other as described below. Any other element capable of controlling and / or managing communications within the RAT network may be included.

  In some illustrative embodiments, the system 100 can include one or more cellular managers that manage communication of one or more cellular networks, eg, as described below.

  In some illustrative embodiments, one or more cellular managers may include one or more Evolved Node B (eNB), eg, eNB 106 and / or eNB 108. For example, eNB 106 and / or eNB 108 may include radio resource management (RRM), radio bearer control, radio admission control (access control), connection mobility management, resource scheduling between UE and eNB radio, eg , Dynamic allocation of resources to UEs in both uplink and downlink, header compression, link encryption of user data stream, packet routing of user data destined to another e.g. another eNB or core network (CN) 150 Configured to perform paging messages, eg, incoming calls and / or connection requests, schedule and / or send, broadcast information coordination, measurement reports, and / or any other action be able to.

  In some exemplary embodiments, the one or more cellular managers may include a UMTS cellular manager. In accordance with the above example, system 100 can include one or more radio network controllers (RNCs) 110, which can control multiple Node B devices 112. For example, Node B equipment 112 may use, for example, wideband code division multiple access (WCDMA) and / or time division synchronous code division multiple access (TD-SCDMA) air interface technology to Can be configured to communicate directly. RNC 110 may include, for example, a UMTS RNC configured to control Node B equipment 112.

  In some illustrative embodiments, the one or more cellular managers may be any other cellular manager, eg, one or more cellular base stations (BS), and / or any other cellular node, network controller, It may include a base station, or any other node or network device, the cellular base station being for example a GSM network.

  In some illustrative embodiments, the system 100 can include one or more WLAN managers that manage communication for one or more WLANs, eg, as described below.

  In some illustrative embodiments, the system 100 can include at least one WLAN access device 116 that manages access to a non-cellular network, eg, a WLAN, eg, a Basic Service Set (BSS).

  In some exemplary embodiments, the WLAN access device 116 may include a WLAN AP. In other embodiments, the WLAN access device 116 may include any other functionality and / or any other capable of controlling and / or managing WLAN wireless access to one or more wired networks. The functionality of the device may be implemented. In one example, the WLAN access device 116 can perform access controller (AC) functionality. In accordance with the above example, the WLAN access device 116 can control a plurality of AP devices, eg, a lightweight access point (LAP) (not shown).

  In some illustrative embodiments, the eNB 106 and / or the eNB 108 may include a network interface 132 that communicates with one or more network elements of the system 100, eg, as described below.

  In some illustrative embodiments, the interface 132 may include an X2 application protocol (X2AP) interface 136 that communicates messages between the eNB 106 and the eNB 108, eg, as described below.

  In some illustrative embodiments, the interface 132 is an S1 application protocol (S1AP) that communicates messages between the eNB 106 and one or more elements of the CN 150, eg, a Mobility Management Entity (MME) 152. An interface 134 may be included.

  In some exemplary embodiments, RNC 110 may include a CN interface 160 that communicates with one or more elements of CN 150. For example, the CN interface 160 may include an interface unit circuit switched (Iu-CS) interface and / or an interface unit packet switched (Iu-PS) interface between the RNC 110 and one or more packet switched or circuit switched CN elements. Can be used as an interface.

  In some exemplary embodiments, eNB 106 and / or eNB 108 may communicate with RNC 110 via CN 150, for example, as described below.

  In some illustrative embodiments, eNB 106, eNB 108, RNC 110, and / or WLAN access device 116 may include interfaces that communicate user plane traffic directly or indirectly with UE 118.

  In some illustrative embodiments, the eNB 106 and / or the eNB 108 may include an air interface, eg, a cellular transceiver (TRx) 144, configured to communicate with the UE 118 via a cellular link.

  In some exemplary embodiments, RNA 110 may communicate user plane traffic with UE 118 via Node B 112. In accordance with these embodiments, RNC 110 may include a Node B interface 170 that communicates between RNC 110 and Node B 112. For example, the Node B interface 170 can include an interface unit b (Iub).

  In some illustrative embodiments, WLAN access device 116 may include an interface that communicates traffic directly or indirectly with UE 118. In some illustrative embodiments, the WLAN access device 116 may communicate directly with the UE 118, for example, when the WLAN access device 116 performs AP functionality. In accordance with such an embodiment, the WLAN access device 116 can direct traffic directly to the UE 118 via, for example, a WLAN link between the WLAN access device 116 and the UE 118 when the WLAN access device 116 performs AP functionality. Communicating WLAN radio (not shown) may be included. In some illustrative embodiments, the WLAN access device 116 may communicate indirectly with the UE 118, for example, when the WLAN access device 116 performs AC functionality. In accordance with such an embodiment, the WLAN access device 116 may include an AP interface (not shown) that communicates traffic with the UE 118, eg, via LAP.

  In some exemplary embodiments, eNB 106, eNB 108, and / or RNC 110 may further include, for example, a processor, a memory unit, and / or any other element, module, or unit. For example, eNB 106 and / or eNB 108 may include memory 140 and / or processor 138 and / or RNC 110 may include memory 166 and / or processor 164. In some illustrative embodiments, eNB 106, eNB 108, and / or RNC 110 may optionally include other suitable hardware and / or software components. In some exemplary embodiments, some or all of the components for one or more of the eNB 106, eNB 108, and / or RNC 110 may be enclosed within a common housing or packaging. May be interconnected or operatively associated with each other using a wired or wireless link. In other embodiments, components for one or more of eNB 106, eNB 108, and / or RNC 110 may be distributed across multiple or separate devices.

  Processors 138 and / or 164 may be, 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 , Multiple processors or controllers, chips, microchips, one or more electrical circuits, circuits, logic units, integrated circuits (ICs), application specific ICs (ASICs), or any other suitable multipurpose or special purpose A processor or controller can be included. For example, processor 138 may execute instructions for eNB 106 operating system and / or one or more suitable applications, for example, and processor 164 may include, for example, RNC 110 operating system (OS) and / or one or more appropriate applications. It is possible to execute commands of various applications.

  The memory units 140 and / or 166 include, for example, random access memory (RAM), read only memory (ROM), dynamic RAM (DRAM), synchronous DRAM (SD-RAM), flash memory, volatile memory, nonvolatile memory, cache A memory, buffer, short-term memory unit, long-term memory unit, or other suitable memory unit is included. For example, the memory unit 140 can store data processed by the eNB 106 and / or the memory unit 166 can store data processed by the RNC 110.

  In some exemplary embodiments, the eNB 106, eNB 108, and / or RNC 110 may include one or more functionalities, communications, corresponding to one or more offloading functionalities, eg, as described below. And / or at least one offload controller that controls the interaction. For example, the eNB 106 and / or the eNB 108 may include an offload controller 130 that controls one or more offloading functionality of the eNB 106 and / or 108, and the RNC 110 may turn off the RNC 110, eg, as described below. An offload controller 162 may be included to control the loading functionality.

  In some illustrative embodiments, offload controller 130 and / or offload controller 162 may include suitable controller circuitry, such as processor circuitry, memory circuitry, and / or any other circuitry, or A controller circuit may be implemented, and the controller circuit may be configured to perform at least some of the functionality of the offload controller 130 and / or offload controller 162. Additionally or alternatively, one or more functionalities of offload controller 130 and / or offload controller 162 may be implemented by logic, for example as described below, where the logic is machine and / or It can be executed by one or more processors.

  In some illustrative embodiments, eNB 106 and / or eNB 108 are configured to generate, process, and / or access one or more messages communicated by eNB 106 and / or eNB 108. A message processor 148 may be included.

  In one example, message processor 148 can be configured to generate one or more messages sent by eNB 106 or eNB 108, and / or message processor 148, for example, as described below. , ENB 106 or eNB 108 may be configured to access and / or process one or more messages received.

  In some illustrative embodiments, the RNC 110 may include a message processor 172 configured to generate, process, and / or access one or more messages communicated by the RNC 110. .

  In one example, the message processor 172 can be configured to generate one or more messages sent by the RNC 110 and / or the message processor 172 can be configured, for example, as described below. Can be configured to access and / or process one or more messages received by.

  In some illustrative embodiments, the message processor 148 and / or 172 may include circuitry configured to perform the functionality of the message processor 148 and / or 172, eg, processor circuitry, memory circuitry, media access control ( MAC) circuitry, physical layer (PHY) circuitry, and / or any other circuitry. Additionally or alternatively, one or more functionalities of proximity estimators message processor 148 and / or 172 may be implemented by logic, for example as described below, where the logic is It can be executed by a machine and / or one or more processors.

  In some illustrative embodiments, at least some of the functionality of the message processor 148 can be implemented as part of the interface 132 and / or the cellular TRX 144 and / or at least of the functionality of the message processor 172. Some may be implemented as part of interface 160 and / or 170.

  In some exemplary embodiments, at least some of the functionality of the message processor 148 can be implemented as part of the offload controller 130 and / or at least some of the functionality of the message processor 172 is It can be implemented as part of the offload controller 162.

  In other embodiments, the functionality of the message processor 148 may be implemented as part of any other element of the eNB 106 and / or the functionality of the message processor 172 may be one of the other elements of the RNC 110. It may be implemented as a part.

  In some illustrative embodiments, a circuit that allows cellular TRx 144 to send and / or receive wireless communication signals, RF signals, frames, blocks, transmission streams, packets, messages, data items, and / or data, and One or more wireless transmitters, receivers, and / or transceivers that include / and logic may be included.

  In some illustrative embodiments, the cellular TRx 144 may include a multiple-input multiple-output (MIMO) transmitter receiver system (not shown), which, if desired, uses an antenna beamforming method. There may be the ability to perform. In other embodiments, cellular TRx 144 may include any other transmitter and / or receiver.

  In some illustrative embodiments, the cellular TRx 144 communicates downlink signals, eg, over the downlink channel between the eNB 106 and the UE 118, and uplink signals over the uplink channel, eg, between the UE 118 and the eNB 106. LTE, WCDMA, and / or TD-SCDMA modulators and / or demodulators (not shown) configured to do so. In other embodiments, cellular TRx 144 may include any other modulator and / or demodulator.

  In some exemplary embodiments, UE 118 may establish a WLAN link with WLAN access device 116. For example, a WLAN link can include an uplink and / or a downlink.

  In some exemplary embodiments, eNB 106, eNB 108, UE 118, WLAN access device 116, and / or Node B 112 may include one or more antennas, or may be associated with one or more antennas. In one example, cellular TRx 144 may be associated with at least two antennas 146 or any other number of antennas, eg, one antenna or more than two antennas, and UE 118 may be associated with at least two antennas or any Other number of antennas, eg, one antenna or more than two antennas, WLAN access device 116 can be associated with more than one antenna, and / or Node B 112 It can be associated with one or more antennas.

  In some illustrative embodiments, antenna 146 includes any type of antenna suitable for transmitting and / or receiving wireless communication signals, blocks, frames, transmission streams, packets, messages, and / or data. be able to. For example, the antenna 146 can include any suitable configuration, structure, and / or arrangement of one or more antenna elements, components, units, assemblies, and / or arrays. For example, the antenna 146 can 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, the antenna 146 can implement transmit and receive functionality using separate transmit and receive antenna elements. In some embodiments, the antenna 146 can implement transmit and receive functionality using common and / or integrated transmit / receive elements.

  In some illustrative embodiments, the UE 118 may have a cellular connection, eg, an LTE cellular connection, a UMTS cellular connection, or any other cellular connection to communicate with the eNB 106, eNB 108, and / or Node B 112, and It can be configured to utilize a WLAN connection, eg, a wireless fidelity (WiFi) connection, a millimeter wave connection, or any other WLAN connection to communicate with the WLAN access device 116.

  In some exemplary embodiments, one or more elements of the system 100 can perform the functionality of a hetnet, which can be a technology, frequency, including, for example, cellular, WLAN, and / or the like. Mixed deployments of cell size and / or network architecture can be utilized.

  For example, a hetnet can be configured to provide service through a first wireless communication environment, eg, a cellular network, and maintain the service when switching to another communication environment, eg, WLAN. The Hetnet architecture enables the utilization of multiple wireless communication environments, for example, a mixture of WLAN and cellular environments, for example, optimally responding to sudden changes in customer demand, reducing power consumption, Costs can be reduced, efficiency can be increased, and / or any other benefit can be achieved.

  In one example, the system 100 is multi-layered (eg, including layers of small cells such as pico, femto, relay stations, WiFiAP, etc.) overlaid on top of a macro cellular deployment to increase network capacity. Multi-tier) Multi-RAT Hetnet architecture can be used.

  In another example, the system 100 may utilize a multi-RAT small cell that integrates multiple radios, such as WiFi and 3GPP air interfaces, etc., into a single infrastructure device.

  In other embodiments, the system 100 may implement any other architecture and / or deployment.

  In some exemplary embodiments, the eNB 106, eNB 108, and / or RNC 110 may be, for example, as described below, eg, between multiple RAT networks, eg, LTE, UMTS, GSM, CDMA, and / or WLAN, It can be configured to allow multi-RAT joint coordination.

  In some illustrative embodiments, the eNB 106, eNB 108, and / or RNC 110 may implement a multi-RAT coordination scheme, eg, the Rel defined in RAN2 as described below, for example. -12 Can be configured to build on top of WLAN / 3GPP wireless interworking solution.

  In some exemplary embodiments, eNB 106, eNB 108, and / or RNC 110 may be configured to perform multi-RAT coordination for at least two networks, eg, a cellular network and a WLAN.

  In some exemplary embodiments, eNB 106, eNB 108, and / or RNC 110 may be configured to perform multi-RAT coordination, eg, simultaneously, for at least three networks.

  In some illustrative embodiments, the at least three networks can include, for example, two cellular networks and a WLAN, eg, a WLAN controlled by a WLAN access device 116.

  In some exemplary embodiments, the two cellular networks are controlled by two LTE networks, eg, a first network controlled by a first eNB, eg, eNB 106, and a second eNB, eg, eNB 108. And a second network.

  In some illustrative embodiments, the two cellular networks include an LTE network, eg, a network controlled by an eNB, eg, eNB 106, and a UMTS network, eg, a network controlled by an RNC, eg, RNC 110 Can do.

  In some illustrative embodiments, the UE 118 may be within the coverage of multiple networks. In one example, the UE 118 may be within the coverage range 114 of the WLAN access device 116, the coverage range 102 of the eNB 106, and the coverage range 104 of at least one other cellular manager, eg, the eNB 108 and / or the RNC 110. .

  In some illustrative embodiments, the UE 118 may be capable of operating according to a WLAN offloading scheme, eg, as described below.

  In some exemplary embodiments, the UE 118 may communicate between cells controlled by multiple eNBs, eg, eNB 106 and eNB 108, and / or cells controlled by an eNB, eg, eNB 106 or eNB 108, and RNC, eg, RNC 110. There may be the ability to perform a handover with a cell controlled by.

  In some exemplary embodiments, eNB 106, eNB 108, and / or RNC 110 are configured to perform one or more offloading and / or load balancing operations, eg, as described below. Can be.

  In some illustrative embodiments, the eNB 106, eNB 108, and / or RNC 110 may be configured to implement a first offloading mechanism (“WLAN offload”), which includes one The above UE, eg UE 118, is configured to be able to offload to WLAN, eg to WLAN access device 116. WLAN offload includes, for example, traffic steering and / or traffic routing of UE traffic, eg, one or more traffic streams, from a cellular network to a WLAN and / or from a WLAN to a cellular network. be able to.

  In some illustrative embodiments, the eNB 106, eNB 108, and / or RNC 110 may be configured to implement a second offloading mechanism (“cellular offload” or “handover”). Is controlled by one or more UEs from one cellular network, e.g. between two cellular managers of the same cellular technology, e.g. between eNB 106 and eNB 108, or between cellular managers of different cellular technologies, e.g. eNB 106 And a cell controlled by the RNC 110 (also referred to as “offload from eNB to RNC”). Cellular offloading may include, for example, traffic steering and / or traffic routing of UE traffic, eg, one or more traffic streams, from one cellular network to another cellular network.

  In some illustrative embodiments, the WLAN offloading mechanism includes UE-centric (also referred to as “UE controlled”) access network selection and / or traffic steering schemes. Where the UE 118 can select an access network to be utilized by the UE 118 and / or select any traffic stream to steer to that access network.

  In some illustrative embodiments, the UE 118 is configured to receive assistance information, eg, Radio Access Network (RAN) assisted WLAN interworking information. The information may include one or more parameters from one or more elements of the system 100 (also referred to as “RAN-assisted WLAN interworking parameters”).

  In some illustrative embodiments, the UE 118 may receive the RAN assisted WLAN interworking parameters from one or more cellular managers. For example, a cellular manager can be configured to determine RAN assisted WLAN interworking parameters corresponding to a cellular network controlled by the cellular manager, eg, as described below.

  In some illustrative embodiments, the offload controller 130 of the eNB 106 is configured to determine RAN assisted WLAN interworking parameters corresponding to a cellular network controlled by the eNB 106, eg, as described below. Can do.

  In some exemplary embodiments, eNB 106 may send UE 118 RAN-assisted WLAN interworking parameters corresponding to the cellular network controlled by eNB 106. For example, the message processor 148 of the eNB 106 generates one or more messages, eg, radio resource control (RRC) broadcast and / or dedicated messages, including RAN-assisted WLAN interworking parameters corresponding to the cellular network controlled by the eNB 106. The cellular TRx 144 may receive a message to be received by one or more UEs, eg, by sending a dedicated RRC message to the UE 118 and / or within the coverage area 102 It can be transmitted by broadcasting one or more messages to be received by the UE.

  In some illustrative embodiments, the eNB 108 may be configured to determine RAN assisted WLAN interworking parameters corresponding to a cellular network controlled by the eNB 108 and may be received by one or more UEs. One or more messages containing RAN-assisted WLAN interworking parameters corresponding to the cellular network controlled by the eNB 108, eg RRC broadcast and / or dedicated messages, eg RRC messages dedicated to the UE 118 It can be sent by sending and / or by broadcasting one or more messages that will be received by UEs in the coverage area 104.

  In some illustrative embodiments, the offload controller 162 of the RNC 110 is configured to determine RAN assisted WLAN interworking parameters corresponding to a cellular network controlled by the RNC 110, eg, as described below. Can do.

  In some exemplary embodiments, RNC 110 may send UE 118 RAN-assisted WLAN interworking parameters corresponding to the cellular network controlled by RNC 110. For example, the message processor 170 of the RNC 110 can generate one or more messages that include RAN-assisted WLAN interworking parameters corresponding to the cellular network controlled by the RNC 110, and the interface 170 can be, for example, via the Node B 112, The message can be sent to the UE 118.

  In some illustrative embodiments, the RAN assisted WLAN interworking parameter may be, for example, at least one cellular parameter threshold, at least one WLAN parameter threshold, at least one offload preference indicator (OPI), And / or any other parameters, indicators and / or thresholds may be included.

  In one example, the at least one cellular parameter threshold can include, for example, a Reference Signal Received Power (RSRP) threshold.

  In another example, the at least one cellular parameter threshold is, for example, a received signal code power (RSCP) threshold, eg, a UMTS common pilot channel (CPICH) RSCP threshold, eg, for frequency division multiplexing, or For example, it may include a UMTS primary common control physical channel (PCCPCH) RSCP threshold for time division multiplexing (TDD).

  In another example, the at least one cellular parameter threshold may include, for example, a Reference Signal Received Quality (RSRQ) threshold.

  In another example, the at least one cellular parameter threshold may be, for example, UMTS CPICH for FDD, for example, Energy Per Chip (Ec) vs. Noise power (No) (Ec / No) threshold. May be included.

  In another example, the at least one cellular parameter threshold may include any other cellular parameter threshold.

  In one example, the at least one WLAN parameter threshold can include, for example, a WLAN channel utilization threshold, which can be, for example, BSS load information as received by the WLAN access device 116, for example. Corresponds to the WLAN channel usage value in the Information Element (IE).

  In another example, the at least one WLAN parameter threshold may include, for example, an available WLAN backhaul capacity threshold, such as an available WLAN DL and UL backhaul data rate threshold.

  In another example, the at least one WLAN parameter threshold is, for example, a WLAN signal strength threshold, such as a Received Signal Strength Indicator (RSSI) threshold, a Beacon Received Signal Strength Indicator ( Includes beacon RSSI threshold, received signal to noise indicator (RSNI) threshold, received channel power indicator (RCPI) threshold, and / or any other WLAN signal strength threshold But you can.

  In another example, the at least one WLAN parameter threshold may include any other WLAN parameter threshold.

  In some illustrative embodiments, the UE 118 may be configured to select an access network to be utilized by the UE 118, for example based on RAN assisted WLAN interworking parameters. For example, the UE 118 selects the access network utilized by the UE 118 based on one or more rules applied to RAN assisted WLAN interworking parameters and one or more measurements related to, for example, one or more networks. Can be configured to.

  In some illustrative embodiments, UE 118 may be connected to a first cellular RAT (“source RAT”) manager.

  In one example, the source RAT can include a network controlled by the eNB 106. In another example, the source RAT may include a network controlled by the eNB 108. In another example, the source RAT may include a network controlled by the RNC 110.

  In some illustrative embodiments, the source RAT manager is overloaded, for example, when the source RAT has an increased load (load), eg, as described below. When the source RAT is approaching an overload situation, when the load of the source RAT approaches a load threshold, and / or based on any other criteria, one or more offloading and / or load balancing operations may be performed. Can be configured to execute.

  In some illustrative embodiments, the source RAT's cellular manager may be configured to select between a WLAN offloading mechanism and a handover mechanism, eg, as described below.

  In some illustrative embodiments, the WLAN offloading mechanism provides UE 118 with the ability to make RAT selection and / or traffic steering decisions, but the source RAT's cellular manager may, for example, provide RAN-assisted WLAN interworking parameters to UE 118. By providing, the RAT selection and / or traffic steering decisions can be influenced, guided and / or controlled, the interworking parameters can be determined based on, for example, the load of the source RAT and / or the UE Can be configured based on categories.

  In one example, the offload controller 130 of the eNB 106 may select to increase the number of UEs that should go to the WLAN. In accordance with the above example, the offload controller 130 of the eNB 106 configures the RAN assisted WLAN interworking parameters provided to the UE 118 to be more “aggressive”, for example, the UE 118 can The probability of choosing to offload can be increased.

  In some illustrative embodiments, the cellular manager of the source RAT may manage the load of the source RAT, eg, by selecting to perform a load balancing operation, for example, when the network load of the source RAT increases. The load balancing operation may be configured, for example, to reduce and / or avoid further increases in source RAT load.

  In some illustrative embodiments, the cellular manager of the source RAT may perform a handover of one or more UEs to another cellular RAT, such as a more “aggressive” parameter, or One or more UEs can be offloaded to the WLAN by choosing between adjusting RAN-assisted WLAN interworking parameters.

  In some illustrative embodiments, the source RAT's cellular manager may be at least within the coverage area of the source RAT, eg, according to an offloading mechanism selected by the source RAT's cellular manager (“selected offloading mechanism”). At least one offloading message may be sent to one UE.

  In some illustrative embodiments, the offloading message can include RAN assisted WLAN interworking information, for example, when the selected offloading mechanism includes a first offloading mechanism, eg, a WLAN offloading mechanism. . For example, as described below, for example, the offload controller 130 of the eNB 106 can determine RAN assisted WLAN interworking information, and the cellular TRx 144 can send a message that includes RAN assisted WLAN interworking information. .

  In some illustrative embodiments, the offloading message triggers offloading of the UE to another cellular network, eg, when the selected offloading mechanism includes a second offloading mechanism, eg, a handover mechanism. An offloading trigger can be included. For example, as described below, for example, the offload controller 130 of the eNB 106 may choose to hand over the UE 118 to a cell controlled by the eNB 108 or RNC 110, and the cellular TRx 144 may be controlled by the eNB 108 or RNC 110, for example. A message including an offloading trigger that triggers offloading of the UE 118 to a cell can be transmitted.

  In some exemplary embodiments, the cellular manager of the source RAT may have some information corresponding to the potential cellular network (“potential target RAT”), and the potential cellular network (“potential target”). RAT ") may be considered for handover of one or more UEs.

  In some illustrative embodiments, the cellular manager of the source RAT may provide load information corresponding to the load of the potential target RAT, for example, an indication of whether the load of the potential target RAT is low, medium, or high. Can be received.

  In some illustrative embodiments, the load information corresponding to the potential target RAT load is efficient, optimal and / or preferred at the source RAT with respect to whether to use a WLAN offloading mechanism or a handover mechanism. It may not be enough to make a decision.

  For example, if the load information corresponding to the load of the potential target RAT indicates that the load in the target RAT is not high, eg, the load is medium, for example, the potential target RAT is a good candidate for handover It may seem that in theory.

  However, in some scenarios, for example, even if load information corresponding to the load of the potential target RAT indicates that the load in the potential target RAT is not high, the potential target RAT is a good candidate for handover. It may not be.

  In one example, for example, if the potential target RAT has already offloaded some UEs to the WLAN, the load in the potential target RAT may not be high.

  In such a case, if the source RAT only takes into account information about the load of the source RAT and the indicated load of the potential target RAT, the source RAT may perform UE handover to the potential target RAT for load balancing of the source RAT. Can start. However, since the target RAT may have already offloaded the UE to the WLAN, the target RAT may be the same UE offloaded from the source RAT to prevent an increase in load on the target RAT. One or more of them may eventually be offloaded to the WLAN.

  In some illustrative embodiments, the cellular manager of the source RAT may select a WLAN offloading mechanism that offloads the UE to the WLAN, for example in situations where the handover offloading mechanism may not be very effective. Can be configured.

  In some illustrative embodiments, the source RAT's cellular manager relates to a potential cellular RAT load, for example, where the source RAT's cellular manager can be handed over at least one neighbor cell, eg, one or more UEs. If information is not provided, optimal, efficient and / or suitable load balancing decisions may not be made.

  In some illustrative embodiments, the source RAT's cellular manager may, for example, use the source RAT's cellular manager to determine the source RAT's RAN-assisted WLAN interworking parameters, eg, If determined independently, optimal, efficient and / or suitable load balancing decisions may not be made.

  In some illustrative embodiments, the source RAT's cellular manager, for example, the source RAT's cellular manager does not take into account, for example, at least one potential cellular RAT's RAN-assisted WLAN interworking parameters. When determining RAN-assisted WLAN interworking parameters, it may not be possible to make optimal, efficient and / or suitable load balancing decisions.

  In some illustrative embodiments, the eNB 106, eNB 108, and / or RNC 110 may be configured such that, for example, as described below, the first cellular manager of the eNB 106, eNB 108, and RNC 110 is at least the first eNB 106, eNB 108, and RNC 110. Can be configured to allow load balancing decisions to be made while taking into account the load of the two cellular managers.

  In some exemplary embodiments, the eNB 106, eNB 108, and / or RNC 110 is one corresponding to the RAN-assisted WLAN interworking parameter used by the eNB 106, eNB 108, and / or RNC 110, eg, as described below. The above WLAN offload parameters can be configured to communicate with each other.

  In some exemplary embodiments, eNB 106 and eNB 108 are used by eNB 106 and / or eNB 108 using, for example, X2AP signaling messages, eg, enhanced X2AP signaling messages, as described below. One or more WLAN offload parameters corresponding to RAN assisted WLAN interworking parameters may be communicated with each other.

  In some exemplary embodiments, the eNB 106 sends an X2AP resource status update (RESOURCE STATUS UPDATE) message to the eNB 108 that includes one or more WLAN offload parameters corresponding to the RAN-assisted WLAN interworking parameters used by the eNB 106. The eNB 108 can send and / or send an X2AP resource status update message to the eNB 106 that includes one or more WLAN offload parameters corresponding to the RAN-assisted WLAN interworking parameters used by the eNB 108.

  In one example, a resource status update message can be sent, for example, by a certain eNB (“eNB2”) to a neighboring eNB (“eNB1”), for example, to report the result of a requested measurement. For example, the resource status update message can include the following format:

いくつかの例証的実施形態において、ｅＮＢ１０６は、ｅＮＢ１０８に、ｅＮＢ１０６により使用されるＲＡＮ支援ＷＬＡＮインターワーキングパラメータに対応する１つ以上のＷＬＡＮオフロードパラメータを含むＸ２ＡＰロード情報（LOAD INFORMATION）メッセージを送ることができ、かつ／あるいは、ｅＮＢ１０８は、ｅＮＢ１０６に、ｅＮＢ１０８により使用されるＲＡＮ支援ＷＬＡＮインターワーキングパラメータに対応する１つ以上のＷＬＡＮオフロードパラメータを含むＸ２ＡＰロード情報メッセージを送ることができる。

In some illustrative embodiments, the eNB 106 sends an eX 108 an X2AP LOAD INFORMATION message that includes one or more WLAN offload parameters corresponding to the RAN-assisted WLAN interworking parameters used by the eNB 106. And / or the eNB 108 may send an X2AP load information message to the eNB 106 that includes one or more WLAN offload parameters corresponding to the RAN-assisted WLAN interworking parameters used by the eNB 108.

  In one example, an X2AP load information message is sent, for example, by one eNB ("eNB1") to one or more neighboring eNBs ("eNB2") to convey, for example, load and interference coordination information Can do. For example, the X2AP load information message may include the following format:

他の実施形態において、ｅＮＢ１０６及び／又はｅＮＢ１０８は、ＲＡＮ支援ＷＬＡＮインターワーキングパラメータに対応する１つ以上のＷＬＡＮオフロードパラメータを、任意の他の専用にされ又は強化されたＸ２ＡＰメッセージの一部として通信することができる。

In other embodiments, the eNB 106 and / or the eNB 108 communicates one or more WLAN offload parameters corresponding to the RAN-assisted WLAN interworking parameters as part of any other dedicated or enhanced X2AP message. can do.

  In some illustrative embodiments, eNB 106 and / or eNB 108 may be configured by eNB 106, eNB 108, and / or RNC 110 using, for example, S1AP signaling messages, eg, enhanced S1AP signaling messages, as described below. One or more WLAN offload parameters corresponding to the RAN assisted WLAN interworking parameters used may be communicated with the RNC 110.

  In some exemplary embodiments, the S1AP signaling message may be sent from eNB 106 and / or eNB 108 to RNC 110 and / or from RNC 110 to eNB 106 and / or eNB 108, eg, via MME 152, eg, RAN Information Management (RIM). Using Transfer as part of a Self Organizing Networks (SON) Transfer RIM application, any other RIM application, and / or using any other application and / or protocol Can be transmitted.

  In some illustrative embodiments, the source RAT's cellular manager sends the target RAT's cellular manager one or more WLAN offload parameters corresponding to the RAN-assisted WLAN interworking parameters used by the source RAT. Can be configured. For example, the cellular manager of the source RAT can communicate one or more WLAN offload parameters to the target RAT, eg, within the RRC container, which sends from the source cell to the target cell, eg, during handover. Can be done.

  In one example, the eNB 106 may eNB 108 to hand over an RRC container that includes one or more WLAN offload parameters corresponding to the RAN assisted WLAN interworking parameters used by the eNB 106, eg, before handing over the UE 118 from the eNB 106 to the eNB 108. Can be sent to.

  In some illustrative embodiments, the cellular manager of the source RAT may correspond to RAN assisted WLAN interworking parameters used by the potential target RAT, eg, from one or more potential target RATs, as described below. One or more WLAN offload parameters may be received. The potential target RAT's WLAN offload parameters may provide an indication of how “potentially” offloading the potential target RAT to the WLAN.

  In some illustrative embodiments, the source RAT's cellular manager may be in addition to other load information, eg, corresponding to the load of the target RAT, eg, when making a load balancing decision, eg, as described below. The WLAN offload parameters of the potential target RAT can be used.

  In one example, the WLAN offload parameter corresponding to the potential target RAT may be aggressive, while the potential target RAT load information indicates that the potential target RAT is moderately loaded. In accordance with the above example, the source RAT's cellular controller may determine that the potential target RAT may not be a good candidate for load balancing handover.

  In some illustrative embodiments, the first cellular manager of eNB 106, eNB 108, and RNC 110 may be the first cellular manager to eNB 106, eNB 108, and second cellular manager of RNC 110, for example, as described below. Can be configured to send one or more WLAN offload parameters corresponding to RAN assisted WLAN interworking parameters corresponding to the first network controlled by.

  In some exemplary embodiments, the one or more WLAN offload parameters may include one or more of the RAN assisted WLAN interworking parameters corresponding to the first network.

  In some exemplary embodiments, the one or more WLAN offload parameters can include parameters, the parameters based on one or more of the RAN-assisted WLAN interworking parameters corresponding to the first network. One or more of the RAN assisted WLAN interworking parameters corresponding to the first network may be indicated, and one or more magnitudes of the RAN assisted WLAN interworking parameters corresponding to the first network ( magnitude), may indicate the direction of change of one or more of the RAN-assisted WLAN interworking parameters corresponding to the first network, eg, increase or decrease, and / or correspond to the first network. RAN support WLAN interworking It may enable determining one or more of the parameters.

  In some illustrative embodiments, the offload controller 130 of the eNB 106 may include one or more RAN assisted WLAN interworking parameters (“first RAN assisted WLAN interworking parameters”) corresponding to the cellular network controlled by the eNB 106. Can be determined.

  In some illustrative embodiments, the eNB 106 may send the first RAN-assisted WLAN interworking parameters to one or more UEs in the coverage area 102. For example, the cellular TRX 144 may send one or more messages to the UE 118 that include a first RAN assisted WLAN interworking parameter.

  In some illustrative embodiments, the eNB 106 is configured to send one or more WLAN offload parameters corresponding to the first RAN-assisted WLAN interworking parameters to one or more other cellular managers. Can do.

  In one example, the eNB 106 is configured to send WLAN offload parameters to another eNB, eg, the eNB 108, to enable, for example, intra-LTE load balancing coordination between the eNB 106 and the eNB 108. Can. For example, eNB 106 may send one or more X2AP messages that include WLAN offload parameters to eNB 108, eg, via X2AP interface 136.

  In another example, the eNB 106 may be configured to send WLAN offload parameters to the RNC, eg, the RNC 110, to enable, for example, LTE-UMTS load balancing coordination between the eNB 106 and the RNC 110. For example, the S1AP interface 134 can send WLAN offload parameters to the RNC 110 using one or more S1 messages, which can be sent to the MME 152.

  In some illustrative embodiments, the eNB 108 may determine one or more RAN assisted WLAN interworking parameters (“second RAN assisted WLAN interworking parameters”) corresponding to the cellular network controlled by the eNB 108. it can.

  In some illustrative embodiments, the eNB 108 may send a second RAN assisted WLAN interworking parameter to one or more UEs within the coverage area of the eNB 108.

  In some exemplary embodiments, the eNB 108 may send one or more WLAN offload parameters corresponding to the second RAN-assisted WLAN interworking parameter to one or more other cellular managers, eg, the eNB 106 and / or It can be configured to send to the RNC 110.

  In some exemplary embodiments, the offload controller 162 of the RNC 110 may include one or more RAN assisted WLAN interworking parameters (“third RAN assisted WLAN interworking parameters”) corresponding to the cellular network controlled by the RNC 110. Can be determined.

  In some illustrative embodiments, the RNC 110 may send a third RAN assisted WLAN interworking parameter to one or more UEs within the RNC 110 coverage area. For example, the interface 170 may send one or more messages that include the third RAN-assisted WLAN interworking parameter to the UE 118, eg, via the Node B 112.

  In some illustrative embodiments, the RNC 110 is configured to send one or more WLAN offload parameters corresponding to a third RAN assisted WLAN interworking parameter to one or more other cellular managers. Can do.

  In one example, the RNC 110 sends WLAN offload parameters to at least one eNB, eg, eNB 106 and / or eNB 108, for example, enabling LTE-UMTS load balancing coordination between the RNC 110 and the eNB 106 and / or eNB 108. Can be configured to For example, CN interface 160 may send WLAN offload parameters to eNB 106 and / or eNB 108 via one or more elements of CN 150.

  In another example, the RNC 110 may send WLAN offload parameters to another RNC (not shown), for example, allowing intra-UMTS (intra-UMTS) load balancing coordination between the RNC 110 and the other RNC. It may be.

  In some illustrative embodiments, the second cellular manager takes into account one or more WLAN offload parameters received from the first cellular manager, while at the same time being controlled by the second cellular manager. RAN assisted WLAN interworking parameters corresponding to two networks may be configured.

  In some illustrative embodiments, the eNB 106 may receive one or more WLAN offload parameters corresponding to the second RAN-assisted WLAN interworking parameter from the eNB 108. For example, the X2AP interface 136 can receive from the eNB 108 one or more X2AP messages that include a WLAN offload parameter corresponding to the second RAN assisted WLAN interworking parameter.

  In some exemplary embodiments, the eNB 106 may receive one or more WLAN offload parameters corresponding to the third RAN assisted WLAN interworking parameter from the RNC 110. For example, the S1AP interface 134 may receive from the MME 152 one or more S1AP messages that include WLAN offload parameters corresponding to a third RAN assisted WLAN interworking parameter.

  In some illustrative embodiments, the offload controller 130 of the eNB 106 may send a first RAN assisted WLAN interworking parameter that is to be sent from the eNB 106 to the UE 118, for example, a second RAN assisted WLAN interface of the eNB 108, for example. Based on the WLAN offload parameter corresponding to the working parameter and / or based on the WLAN offload parameter corresponding to the third RAN assisted WLAN interworking parameter of the RNC 110.

  In some illustrative embodiments, the eNB 108 may receive one or more WLAN offload parameters corresponding to the first RAN-assisted WLAN interworking parameter from the eNB 106.

  In some exemplary embodiments, the eNB 108 may receive one or more WLAN offload parameters corresponding to the third RAN-assisted WLAN interworking parameter from the RNC 110.

  In some exemplary embodiments, the eNB 108 corresponds to a second RAN assisted WLAN interworking parameter that will be sent from the eNB 108 to the UE 118, for example, to the first RAN assisted WLAN interworking parameter of the eNB 106, for example. Based on the WLAN offload parameter and / or based on the WLAN offload parameter corresponding to the third RAN assisted WLAN interworking parameter of RNC 110.

  In some exemplary embodiments, the RNC 110 may receive one or more WLAN offload parameters corresponding to the first and / or second RAN-assisted WLAN interworking parameters from the eNB 106 and / or the eNB 108. it can. For example, CN interface 160 may receive one or more messages from CN 150 that include offload parameters corresponding to the first and / or second RAN assistance WLAN interworking parameters.

  In some illustrative embodiments, the offload controller 162 of the RNC 110 may send a third RAN assisted WLAN interworking parameter that is to be sent from the RNC 110 to the UE 118, for example, the first eNB 106 and / or the first eNB 108, for example. And / or based on a WLAN offload parameter corresponding to a second RAN assisted WLAN interworking parameter and / or based on a WLAN offload parameter corresponding to a RAN assisted WLAN interworking parameter of another RNC. Can do.

  In some exemplary embodiments, for example, as described above, the cellular manager of the first RAT, eg, the source RAT, may receive the RAN-assisted WLAN of the second RAT, eg, from the potential target RAT. Enabling the reception of WLAN offload parameters corresponding to the interworking parameters allows the first RAT's cellular manager, eg, the cellular manager's offload controller, to be efficient, preferred, preferred, and / or Making it possible to make an optimal load balancing decision, for example to choose between a first offloading mechanism, e.g. WLAN offloading, or a second offloading mechanism, e.g. handover to a second RAT Can do.

  In some illustrative embodiments, the cellular manager of the first RAT may determine how “proactively” the second RAT is between the first and second offloading mechanisms, for example. Selection can be based on whether to offload to the WLAN.

  For example, the offload controller 130 of the eNB 106 may select the first offloading mechanism, for example, within the coverage area 102, for example, if the WLAN offload parameter from the RNC 110 represents a WLAN offloading level that is greater than a predetermined threshold. RAN-assisted WLAN interworking parameters provided for the UEs can be updated.

  In other embodiments, the cellular manager of the first RAT is applied to the WLNA offload parameters received from the second RAT between the first offloading mechanism and the second offloading mechanism. The selection may be based on any other criteria. For example, the cellular manager of the first RAT may have one or more policies, potential target RAT types, one or more UE types or categories to be offloaded, and one or more preferred networks. Can be selected between the first offloading mechanism and the second offloading mechanism, while taking into account the definition and / or any other criteria.

  Reference is made to FIG. FIG. 2 schematically illustrates a method for controlling a RAT communication manager, in accordance with some illustrative embodiments. In some embodiments, one or more of the operations of the method of FIG. 2 may be performed by a wireless communication system, eg, system 100 (FIG. 1), a cellular manager, eg, eNB, eg, eNB 106 (FIG. 1), and / or eNB 1018 ( 1), an RNC, eg, RNC 110 (FIG. 1), and / or an offload controller, eg, offload controller 130 (FIG. 1) and / or offload controller 162 (FIG. 1).

  As indicated at block 202, the method includes determining at the first cellular manager of the first cellular network one or more first RAN assisted WLAN interworking parameters corresponding to the first cellular network. obtain. For example, the offload controller 130 (FIG. 1) determines one or more first RAN assisted WLAN interworking parameters corresponding to the network controlled by the eNB 106 (FIG. 1), eg, as described above. Can do.

  As indicated at block 204, the method may include sending one or more WLAN offload parameters corresponding to the first RAN-assisted WLAN interworking parameter to a second cellular manager of the second cellular network. For example, interface 132 (FIG. 1) may communicate with eNB 108 (FIG. 1) and / or RNC 110 (FIG. 1), for example as described above, with one or more WLANs corresponding to the first RAN-assisted WLAN interworking parameter. Offload parameters can be sent.

As indicated at block 206, the method may include sending a first RAN assisted WLAN interworking parameter to at least one UE in the first cellular network. For example, the cellular TRX 144 (FIG. 1) may send a first RAN assisted WLAN interworking parameter to one or more UEs in the coverage area 102 (FIG. 1),
For example, it can be transmitted to UE 118 (FIG. 1).

  As shown in block 208, the method may include receiving one or more WLAN offload parameters at the second cellular manager. For example, as described above, for example, RNC 110 (FIG. 1) can receive WLAN offload parameters from eNB 106 (FIG. 1), for example, via interface 160 (FIG. 1) and / or eNB 108 (FIG. 1) may receive WLAN offload parameters from eNB 106 (FIG. 1), eg, via one or more X2AP signaling messages.

  As shown in block 210, the method includes, at the second cellular manager, a first offloading mechanism for offloading the UE to the WLAN, and at least one UE off from the second cellular network to the first cellular network. Selecting a selected offloading mechanism from a second offloading mechanism to load. For example, as described above, for example, RNC 110 (FIG. 1) chooses between using a WLAN offloading mechanism or a handover mechanism based on WLAN offload parameters received from eNB 106 (FIG. 1). And / or the eNB 108 (FIG. 1) chooses between using the WLNA offloading mechanism or the handover mechanism based on the WLAN offload parameters received from the eNB 106 (FIG. 1).

  As indicated at block 212, the method may send an UE to a second cellular network UE an offloading message according to a selected offloading mechanism, eg, a message including a RAN assisted WLAN interworking parameter according to a WLAN offloading mechanism, or Sending a handover message that triggers a handover of the UE to the first cellular network may be included. In one example, for example, as described above, eNB 108 (FIG. 1) can send a message including RAN-assisted WLAN interworking parameters to UE 118 (FIG. 1), where the interworking parameters are eNB 106 ( Based on the WLAN offload parameters from FIG. 1), or the eNB 108 (FIG. 1) sends a message to the UE 118 (FIG. 1) that triggers a handover of the UE 118 (FIG. 1) to the eNB 106 (FIG. 1). Can do. In another example, for example, as described above, RNC 110 (FIG. 1) sends a message containing RAN-assisted WLAN interworking parameters to UE 118 (FIG. 1), eg, via Node B 112 (FIG. 1). The interworking parameters may be based on the WLAN offload parameters from the eNB 106 (FIG. 1), and the RNC 110 (FIG. 1) sends a message to the UE 118 (FIG. 1) via, for example, the Node B 112 (FIG. 1). Thus, the handover of the UE 118 (FIG. 1) to the eNB 106 (FIG. 1) may be triggered.

  Reference is made to FIG. FIG. 3 schematically illustrates an article of manufacture 300 according to some illustrative embodiments. Product 300 may include non-transitory machine-readable storage medium 302 to store logic 304, which may be, for example, a cellular manager, eg, eNB, eg, eNB 106 (FIG. 1) and / or eNB 108 ( 1), an RNC, eg, RNC 110 (FIG. 1), an offload controller, eg, offload controller 130 (FIG. 1) and / or an offload controller 162 (FIG. 1), and / or a message processor, eg, message processor 148 (FIG. 1) and / or used to perform at least one of the functionality of the message processor 170 (FIG. 1) and / or to perform one or more of the methods of FIG. it can. The phrase “non-transitory machine-readable medium” is intended to include all computer-readable media, the only exception being temporary propagation signals.

In some illustrative embodiments, product 300 and / or machine-readable storage medium 302 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, writable or rewritable memory and the like are included. For example, the machine-readable storage medium 302 includes RAM, DRAM, double data rate DRAM (DDR-DRAM), SDRAM, static RAM (SRAM), ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), electrical Erasable programmable ROM (EEPROM), compact disc ROM (CD-ROM), compact disc recordable (CD-R), compact disc rewritable (CD-RW),
Flash memory (eg NOR or NAND flash memory), content addressable memory (CAM), polymer memory, phase change memory, ferroelectric memory, SONOS (silicon-oxide-nitride-oxide-silicon) memory, disk, floppy disk , Hard drives, optical disks, magnetic disks, cards, magnetic cards, optical cards, tapes, cassettes, and the like. A computer readable storage medium downloads a computer program carried by a data signal embodied in a carrier wave or other propagation medium over a communication link, eg, a modem, wireless or network connection, from a remote computer to a requesting computer or Any suitable medium involved in communicating can be included.

  In some illustrative embodiments, the logic 304 can include instructions, data, and / or code, where the logic 304, when executed by the machine, is on the machine as described herein. A method, process, and / or operation may be performed. A machine can include, for example, any suitable processing platform, computing platform, computing device, processing apparatus, computing system, processing system, computer, processor, or the like, hardware, software, firmware Can be implemented using any suitable combination.

  In some illustrative embodiments, the logic 304 may include or be implemented as software, software modules, applications, programs, subroutines, instructions, instruction sets, computing code, words, values, symbols, and the like. Can. The instructions can 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 can be implemented according to a predetermined computer language, manner, or syntax to instruct the processor to perform a certain function. The instructions may be any suitable high-level, low-level, object-oriented, visual, compiled and / or interpreted programming language such as C, C ++, Java, BASIC, Matlab. (Registered trademark), Pascal, VisualBASIC (registered trademark), assembly language, machine code, and the like.

Examples The following examples belong to further embodiments.

  Example 1 includes a first cellular manager that controls a first cellular network, wherein the first cellular manager is one or more wireless local area networks (WLANs) of a second cellular manager of a second cellular network. ) Selected from a first off-loading mechanism and a second off-loading mechanism based on the WLAN offload parameter of the second cellular manager based on the first interface receiving a message including the offload parameter An offload controller for selecting an offloading mechanism, wherein the first offloading mechanism offloads a user equipment (UE) to a WLAN, and the second offloading mechanism sends the UE to the second cellular Offloading the Ttowaku includes offload controller, to the UE, according to the selected off-loading mechanism, and a second interface for sending the off-loading message, the.

  Example 2 includes the subject matter described in Example 1, and in some cases, the offload controller is configured to load the second cellular manager and the WLAN offload parameters of the second cellular manager. Based on this, a selection is made between the first offloading mechanism and the second offloading mechanism.

  Example 3 includes the configuration requirements described in Example 1 or 2, and optionally, if the WLAN offload parameter of the second cellular manager represents a WLAN offloading level greater than a predetermined threshold, the offload controller is The first offloading mechanism is selected.

  Example 4 includes the components described in any one of Examples 1 to 3, and optionally, when the selected offloading mechanism includes the first offloading mechanism, the offloading message is a wireless Contains access network (RAN) support WLAN interworking information.

  Example 5 includes the components described in any one of Examples 1 to 4, and optionally, when the selected offloading mechanism includes the second offloading mechanism, the offloading message is: An offloading trigger for triggering offloading of the UE to the second cellular network;

  Example 6 includes the configuration requirements described in any one of Examples 1-5, and optionally, the WLAN offload parameter of the second cellular manager is a cellular parameter threshold, a WLAN parameter threshold, and an offload. It includes at least one parameter selected from the group including a preference indicator (OPI).

  The first cellular manager according to any one of examples 1-6, wherein, optionally, the WLAN offload parameter is a radio access network (RAN) assisted WLAN interworking parameter of the second cellular manager. Show.

  Example 7 includes the configuration requirements described in any one of Examples 1 to 7, is an evolved Node B (eNB), and the second interface is a cellular that transmits the offloading information to the UE. Includes transceiver.

  Example 8 includes the configuration requirements described in Example 8, and optionally, the second cellular manager includes another eNB and the first interface includes an X2 application protocol (X2AP).

  Example 9 includes the configuration requirements described in Example 8, and optionally the second cellular manager includes a radio network controller (RNC), and the first interface is configured via a mobility management entity (MME). Includes S1 application protocol (S1AP) to communicate with RNC.

  Example 10 includes the configuration requirements described in any one of Examples 1 to 7 and is a radio network controller (RNC), wherein the second cellular manager includes an evolved Node B (eNB), and One interface includes a core network interface that communicates with the eNB via a core network, and the second interface includes a Node B interface that communicates with the UE via a node B.

  Example 11 includes the configuration requirements described in any one of Examples 1 to 11, and includes a memory and a processor.

  Example 12 includes a first cellular manager that controls a first cellular network, wherein the first cellular manager includes an offload controller that determines one or more radio access network (RAN) assisted WLAN interworking parameters; A first interface for sending one or more WLAN offload parameters corresponding to the RAN assisted WLAN interworking parameter to a second cellular manager of the second cellular network; and the RAN assisted WLAN interworking parameter as user equipment A second interface to send to (UE).

  Example 13 includes the configuration requirements described in Example 13, and optionally, the WLAN offload parameter is at least one selected from the group comprising a cellular parameter threshold, a WLAN parameter threshold, and an offload preference indicator (OPI). Contains one parameter.

  Example 14 includes the configuration requirements described in Example 13 or 14, and is an evolved Node B (eNB), wherein the second interface is a cellular transceiver that transmits the RAN-assisted WLAN interworking parameters to the UE. Including.

  Example 15 includes the configuration requirements described in Example 15, and optionally, the second cellular manager includes another eNB and the first interface includes an X2 application protocol (X2AP).

  Example 16 includes the configuration requirements described in Example 15, and optionally the second cellular manager includes a radio network controller (RNC), and the first interface is configured via a mobility management entity (MME). Includes S1 application protocol (S1AP) to communicate with RNC.

  Example 17 includes the configuration requirements described in Example 13 or 14, and is a radio network controller (RNC), the second cellular manager includes an evolved Node B (eNB), and the first interface includes a core A core network interface that communicates with the eNB via a network is included, and the second interface includes a Node B interface that communicates with the UE via a Node B.

  Example 18 includes the configuration requirements set forth in any one of Examples 13-18 and includes a memory and a processor.

  Example 19 includes an evolved Node B (eNB) that controls a first cellular network, where the eNB sets one or more wireless local area network (WLAN) offload parameters of the cellular manager of the second cellular network. A cellular network interface that receives at least one message including: an offload controller that generates an offloading message based on the WLAN offload parameter of the second cellular manager; and the offloading message to a user equipment (UE) A cellular transceiver for transmitting.

  Example 20 includes the configuration requirements described in Example 20, and optionally the offload controller selects a selected offloading mechanism from a WLAN offload mechanism or a cellular offload mechanism based on the WLAN offload parameter. And generating the offloading message based on the selected offloading mechanism.

  Example 21 includes the configuration requirements described in Example 20 or 21, and optionally the offloading message includes radio access network (RAN) assisted WLAN interworking information based on the one or more WLAN offload parameters. .

  Example 22 includes the configuration requirements described in Example 20 or 21, and optionally the offloading message triggers offloading of one or more user equipments (UEs) to the second cellular network. Includes triggers.

  Example 23 includes the configuration requirements set forth in any one of Examples 20-23, and optionally, the WLAN offload parameter includes a cellular parameter threshold, a WLAN parameter threshold, and an offload preference indicator (OPI). Including at least one parameter selected from the group including.

  Example 24 includes the configuration requirements set forth in any one of Examples 20-24, and optionally, the WLAN offload parameter indicates the cellular manager's radio access network (RAN) assisted WLAN interworking parameter.

  Example 25 includes the configuration requirements set forth in any one of Examples 20-25, and optionally the cellular manager includes another eNB and the cellular network interface includes an X2 application protocol (X2AP).

  Example 26 includes the configuration requirements set forth in any one of Examples 20-25, and optionally the cellular manager includes a radio network controller (RNC), and the cellular network interface is a mobility management entity (MME). Including the S1 application protocol (S1AP) that communicates with the RNC via

  Example 27 includes the configuration described in any one of Examples 20 to 27 and includes a memory and a processor.

  Example 28 includes a method performed at a first cellular manager of a first cellular network that includes one or more wireless local area networks (WLANs) of a second cellular manager of a second cellular network. An offloading mechanism selected from a first offloading mechanism and a second offloading mechanism based on the WLAN offloading parameter of the second cellular manager and receiving a message including an offloading parameter; The first offloading mechanism offloads user equipment (UE) to the WLAN, and the second offloading mechanism offloads the UE to the second cellular network; The And-up, to the UE, according to the selected off-loading mechanism, comprising the steps of sending an off-loading message, the.

  Example 29 includes the configuration requirements described in Example 29, and optionally based on the load of the second cellular manager and the WLAN offload parameters of the second cellular manager. And a second offloading mechanism.

  Example 30 includes the configuration requirements described in Example 29 or 30, and optionally the first off if the WLAN offload parameter of the second cellular manager represents a WLAN offloading level that is greater than a predetermined threshold. Selecting a loading mechanism.

  Example 31 includes the configuration requirements set forth in any one of Examples 29-31, and optionally, when the selected offloading mechanism includes the first offloading mechanism, the offloading message is wireless. Contains access network (RAN) support WLAN interworking information.

  Example 32 includes the components set forth in any one of Examples 29-32, and optionally, when the selected offloading mechanism includes the second offloading mechanism, the offloading message is: An offloading trigger for triggering offloading of the UE to the second cellular network;

  Example 33 includes the configuration requirements set forth in any one of Examples 29-33, and optionally, the WLAN offload parameter of the second cellular manager is a cellular parameter threshold, a WLAN parameter threshold, and an offload. It includes at least one parameter selected from the group including a preference indicator (OPI).

  Example 34 includes the configuration requirements set forth in any one of Examples 29-34, and optionally, the WLAN offload parameter is the second cellular manager radio access network (RAN) assisted WLAN interworking parameter. Show.

  Example 35 includes the configuration requirements set forth in any one of Examples 29-35, and optionally the first cellular manager is an evolved Node B (eNB).

  Example 36 includes the configuration requirements described in Example 36, and optionally, the second cellular manager includes another eNB, and receiving the message includes receiving an X2 application protocol (X2AP) message. Including.

  Example 37 includes the configuration requirements described in Example 36, and optionally, the second cellular manager includes a radio network controller (RNC), and receiving the message receives an S1 application protocol (S1AP) message. Including doing.

  Example 38 includes the configuration requirements set forth in any one of Examples 29-35, and optionally, the first cellular manager is a radio network controller (RNC), and receiving the message comprises developing Receiving the message from the type Node B (eNB).

  Example 39 includes a method performed at a first cellular manager of a first cellular network that includes determining one or more radio access network (RAN) assisted WLAN interworking parameters; Sending one or more WLAN offload parameters corresponding to the RAN assisted WLAN interworking parameter to a second cellular manager of a cellular network of the user, and sending the RAN assisted WLAN interworking parameter to a user equipment (UE) And including.

  Example 40 includes the configuration requirements described in Example 40, and optionally the WLAN offload parameter is at least one selected from the group comprising a cellular parameter threshold, a WLAN parameter threshold, and an offload preference indicator (OPI). Contains one parameter.

  Example 41 includes the configuration requirements described in Example 40 or 41, and optionally the first cellular manager is an evolved Node B (eNB).

  Example 42 includes the configuration requirements described in Example 42, and optionally, the second cellular manager includes another eNB, and the step of sending the WLAN offload parameter includes an X2 application protocol that includes the WLAN offload parameter. Including sending (X2AP) messages.

  Example 43 includes the configuration requirements described in Example 42, and optionally, the second cellular manager includes a radio network controller (RNC), and the step of sending the WLAN offload parameters includes an S1 application protocol (S1AP) message. Including sending.

  Example 44 includes the configuration requirements described in Example 40 or 41, and optionally the first cellular manager is a radio network controller (RNC) and the second cellular manager is an evolved Node B (eNB). is there.

  Example 45 includes a method performed in an evolved Node B (eNB) that controls a first cellular network, the method comprising one or more wireless local area networks (WLANs) of a cellular manager of a second cellular network. ) Receiving at least one message including an offload parameter; generating an offloading message based on the WLAN offload parameter of the second cellular manager; and sending the offloading message to a user equipment (UE) Transmitting to.

  Example 46 includes the configuration requirements described in Example 46, optionally selecting a selected offloading mechanism from a WLAN offload mechanism or a cellular offload mechanism based on the WLAN offload parameters, and Generating an offloading message based on the selected offloading mechanism.

  Example 47 includes the configuration requirements described in Example 46 or 47, and optionally, the offloading message includes radio access network (RAN) assisted WLAN interworking information based on the one or more WLAN offload parameters. .

  Example 48 includes the configuration requirements described in Example 46 or 47, and optionally the offloading message triggers offloading of one or more user equipments (UEs) to the second cellular network. Includes triggers.

  Example 49 includes the configuration requirements set forth in any one of Examples 46-49, and optionally, the WLAN offload parameter includes a cellular parameter threshold, a WLAN parameter threshold, and an offload preference indicator (OPI). Including at least one parameter selected from the group including.

  Example 50 includes the configuration requirements set forth in any one of Examples 46-50, and optionally, the WLAN offload parameter indicates the cellular manager's radio access network (RAN) assisted WLAN interworking parameter.

  Example 51 includes the configuration requirements set forth in any one of Examples 46-51. Optionally, the cellular manager includes another eNB, and receiving the at least one message includes the X2 application protocol ( X2AP) message.

  Example 52 includes the configuration requirements set forth in any one of Examples 46-51. Optionally, the cellular manager includes a radio network controller (RNC) and receiving the at least one message includes S1. Receiving an application protocol (S1AP) message.

  Example 53 is a computer operable, when executed by at least one computer processor, to allow the at least one computer processor to perform a method in a first cellular manager of a first cellular network. Including one or more tangible computer-readable non-transitory storage media including executable instructions, the method comprising: one or more wireless local area networks (WLANs) of a second cellular manager of a second cellular network; ) Receiving a message including an offload parameter and, based on the WLAN offload parameter of the second cellular manager, a selected offload from a first offloading mechanism and a second offloading mechanism. The first offloading mechanism offloads user equipment (UE) to the WLAN, and the second offloading mechanism offloads the UE to the second cellular network. And sending an offloading message to the UE according to the selected offloading mechanism.

  Example 54 includes the configuration requirements described in Example 54, and optionally, the method is based on the load of the second cellular manager and the WLAN offload parameters of the second cellular manager. Selecting between a second offloading mechanism and the second offloading mechanism.

  Example 55 includes the configuration requirements described in Example 54 or 55, and optionally, the method includes the above, when the WLAN offload parameter of the second cellular manager represents a WLAN offloading level that is greater than a predetermined threshold. The offload controller includes selecting the first offloading mechanism.

  Example 56 includes the configuration requirements set forth in any one of Examples 54-56, and optionally, when the selected offloading mechanism includes the first offloading mechanism, the offloading message is wireless. Contains access network (RAN) support WLAN interworking information.

  Example 57 includes the components set forth in any one of Examples 54-57, and optionally, when the selected offloading mechanism includes the second offloading mechanism, the offloading message is: An offloading trigger for triggering offloading of the UE to the second cellular network;

  Example 58 includes the configuration requirements set forth in any one of Examples 54-58, and optionally, the WLAN offload parameter of the second cellular manager includes a cellular parameter threshold, a WLAN parameter threshold, and an offload. It includes at least one parameter selected from the group including a preference indicator (OPI).

  Example 59 includes the configuration requirements of any one of Examples 54-59, and optionally, the WLAN offload parameter is the second cellular manager radio access network (RAN) assisted WLAN interworking parameter. Indicates.

  Example 60 includes the configuration requirements described in any one of Examples 54-60, and optionally, the first cellular manager is an evolved Node B (eNB).

  Example 61 includes the configuration requirements described in Example 61, and optionally, the second cellular manager includes another eNB, and receiving the message includes receiving an X2 application protocol (X2AP) message. Including.

  Example 62 includes the configuration requirements described in Example 61, and optionally, the second cellular manager includes a radio network controller (RNC), and receiving the message receives an S1 application protocol (S1AP) message. Including doing.

  Example 63 includes the configuration requirements set forth in any one of Examples 54-60, and optionally, the first cellular manager is a radio network controller (RNC), and receiving the message comprises developing Receiving the message from the type Node B (eNB).

  Example 64 is a computer operable, when executed by at least one computer processor, to allow the at least one computer processor to perform a method in a first cellular manager of a first cellular network. Including a product including one or more tangible computer-readable non-transitory storage media including executable instructions, wherein the method includes determining one or more radio access network (RAN) assisted WLAN interworking parameters; Sending one or more WLAN offload parameters corresponding to the RAN assisted WLAN interworking parameter to a second cellular manager of the two cellular networks; Comprising the steps of: sending to the device (UE).

  Example 65 includes the configuration requirements described in Example 65, and optionally, the WLAN offload parameter is at least one selected from the group comprising a cellular parameter threshold, a WLAN parameter threshold, and an offload preference indicator (OPI). Contains one parameter.

  Example 66 includes the configuration requirements described in Example 65 or 66, and optionally the first cellular manager is an evolved Node B (eNB).

  Example 67 includes the configuration requirements described in Example 67, and optionally, the second cellular manager includes another eNB, and the step of sending the WLAN offload parameter includes an X2 application protocol including the WLAN offload parameter Including sending (X2AP) messages.

  Example 68 includes the configuration requirements set forth in Example 67, and optionally, the second cellular manager includes a radio network controller (RNC), and the step of sending the WLAN offload parameter includes an S1 application protocol (S1AP) message. Including sending.

  Example 69 includes the configuration requirements described in Example 65 or 66, and optionally, the first cellular manager is a radio network controller (RNC) and the second cellular manager is an evolved Node B (eNB). is there.

  Example 70, when executed by at least one computer processor, enables the at least one computer processor to implement an evolved Node B (eNB) method for controlling a first cellular network. Including one or more tangible computer-readable non-transitory storage media containing computer-executable instructions, the method comprising: one or more wireless local area networks of a cellular manager of a second cellular network (WLAN) receiving at least one message including an offload parameter; generating an offloading message based on the WLAN offload parameter of the second cellular manager; and the offloading message And transmitting to the user equipment (UE), a.

  Example 71 includes the configuration requirements described in Example 71, and optionally the method selects a selected offloading mechanism from a WLAN offload mechanism or a cellular offload mechanism based on the WLAN offload parameters. And generating the offloading message based on the selected offloading mechanism.

  Example 72 includes the configuration requirements described in example 71 or 72, and optionally, the offloading message includes radio access network (RAN) assisted WLAN interworking information based on the one or more WLAN offload parameters. .

  Example 73 includes the configuration requirements described in Example 71 or 72, and optionally the offloading message triggers offloading of one or more user equipments (UEs) to the second cellular network. Includes triggers.

  Example 74 includes the configuration requirements set forth in any one of Examples 71-74, and optionally the WLAN offload parameter includes a cellular parameter threshold, a WLAN parameter threshold, and an offload preference indicator (OPI). Including at least one parameter selected from the group including.

  Example 75 includes the configuration requirements set forth in any one of Examples 71-75, and optionally, the WLAN offload parameter indicates the cellular manager's radio access network (RAN) assisted WLAN interworking parameter.

  Example 76 includes the configuration requirements set forth in any one of Examples 71-76, and optionally the cellular manager includes another eNB, and receiving the at least one message includes the X2 application protocol ( X2AP) message.

  Example 77 includes the configuration requirements set forth in any one of Examples 71-76, and optionally, the cellular manager includes a radio network controller (RNC) and receiving the at least one message includes S1 Receiving an application protocol (S1AP) message.

  Example 78 includes an apparatus for cellular communication (apparatus), wherein the apparatus is in a first cellular manager of a first cellular network, one or more wireless local areas of a second cellular manager of a second cellular network. Selected from means for receiving a message including a network (WLAN) offload parameter and a first offloading mechanism and a second offloading mechanism based on the WLAN offload parameter of the second cellular manager. Means for selecting an offloading mechanism, wherein the first offloading mechanism offloads a user equipment (UE) to a WLAN, and the second offloading mechanism sends the UE to the second cellular network. Off-road That includes means, to the UE, according to the selected off-loading mechanism, means for sending an off-loading message, the.

  Example 79 includes the configuration requirements described in Example 79, and optionally, based on the load of the second cellular manager and the WLAN offload parameters of the second cellular manager, the first offloading mechanism. And a means for selecting between said second offloading mechanism.

  Example 80 includes the configuration requirements described in Example 79 or 80, and optionally the first off when the WLAN offload parameter of the second cellular manager represents a WLAN offloading level greater than a predetermined threshold. Means for selecting a loading mechanism.

  Example 81 includes the configuration requirements set forth in any one of Examples 79-81, and optionally, when the selected offloading mechanism includes the first offloading mechanism, the offloading message is wireless. Contains access network (RAN) support WLAN interworking information.

  Example 82 includes the components set forth in any one of Examples 79-82, and optionally, when the selected offloading mechanism includes the second offloading mechanism, the offloading message is: An offloading trigger for triggering offloading of the UE to the second cellular network;

  Example 83 includes the configuration requirements set forth in any one of Examples 79-83, and optionally, the WLAN offload parameter of the second cellular manager is a cellular parameter threshold, a WLAN parameter threshold, and an offload. It includes at least one parameter selected from the group including a preference indicator (OPI).

  Example 84 includes the configuration requirements of any one of Examples 79-84, and optionally, the WLAN offload parameter is the second cellular manager radio access network (RAN) assisted WLAN interworking parameter. Indicates.

  Example 85 includes the configuration requirements set forth in any one of Examples 79-85, and optionally the first cellular manager is an evolved Node B (eNB).

  Example 86 includes the configuration requirements described in Example 86, and optionally, the second cellular manager includes another eNB, and receiving the message includes receiving an X2 application protocol (X2AP) message. Including.

  Example 87 includes the configuration requirements described in Example 86, and optionally, the second cellular manager includes a radio network controller (RNC), and receiving the message receives an S1 application protocol (S1AP) message. Including doing.

  Example 88 includes the configuration requirements set forth in any one of Examples 79-85, and optionally, the first cellular manager is a radio network controller (RNC) and receiving the message is a development Receiving the message from the type Node B (eNB).

  Example 89 includes an apparatus for cellular communication (apparatus), which is a means for determining one or more radio access network (RAN) assisted WLAN interworking parameters at a first cellular manager of a first cellular network. Means for sending one or more WLAN offload parameters corresponding to the RAN assisted WLAN interworking parameter to a second cellular manager of a second cellular network; and the RAN assisted WLAN interworking parameter as user equipment (UE ).

  Example 90 includes the configuration requirements described in Example 90, and optionally, the WLAN offload parameter is at least one selected from the group comprising a cellular parameter threshold, a WLAN parameter threshold, and an offload preference indicator (OPI). Contains one parameter.

  Example 91 includes the configuration requirements described in Example 90 or 91, and optionally the first cellular manager is an evolved Node B (eNB).

  Example 92 includes the configuration requirements described in Example 92, and optionally, the second cellular manager includes another eNB and sending the WLAN offload parameter includes an X2 application protocol including the WLAN offload parameter. Including sending (X2AP) messages.

  Example 93 includes the configuration requirements described in Example 92, and optionally, the second cellular manager includes a radio network controller (RNC), and the step of sending the WLAN offload parameters includes an S1 application protocol (S1AP) message. Including sending.

  Example 94 includes the configuration requirements described in Example 90 or 91, and optionally the first cellular manager is a radio network controller (RNC) and the second cellular manager is an evolved Node B (eNB). is there.

  Example 95 includes an apparatus for cellular communication (apparatus), which is an evolved Node B (eNB) that controls a first cellular network, one or more wireless locals of a cellular manager of a second cellular network. Means for receiving at least one message including an area network (WLAN) offload parameter; means for generating an offloading message based on the WLAN offload parameter of the second cellular manager; and Means for transmitting to a device (UE).

  Example 96 includes the components described in Example 96, and optionally, means for selecting a selected offloading mechanism from a WLAN offload mechanism or a cellular offload mechanism based on the WLAN offload parameters, and Means for generating an offloading message based on the selected offloading mechanism.

  Example 97 includes the configuration requirements described in Example 96 or 97, and optionally, the offloading message includes radio access network (RAN) assisted WLAN interworking information based on the one or more WLAN offload parameters. .

  Example 98 includes the configuration requirements described in Example 96 or 97, and optionally the offloading message triggers offloading of one or more user equipments (UEs) to the second cellular network. Includes triggers.

  Example 99 includes the configuration requirements set forth in any one of Examples 96-99, and optionally, the WLAN offload parameter includes a cellular parameter threshold, a WLAN parameter threshold, and an offload preference indicator (OPI). Including at least one parameter selected from the group including.

  Example 100 includes the configuration requirements set forth in any one of Examples 96-100, and optionally, the WLAN offload parameter indicates the cellular manager's radio access network (RAN) assisted WLAN interworking parameter.

  Example 101 includes the configuration requirements set forth in any one of Examples 96-101, and optionally, the cellular manager includes another eNB and receiving the at least one message is an X2 application protocol ( X2AP) message.

  Example 102 includes the configuration requirements set forth in any one of Examples 96-101, and optionally, the cellular manager includes a radio network controller (RNC), and receiving the at least one message is S1 Receiving an application protocol (S1AP) message.

  A function, operation, component, and / or feature described herein with reference to one or more embodiments is one described with reference to one or more other embodiments herein. It may be combined with these other functions, operations, components, and / or features, or may be used in combination with the one or more other functions, operations, components, and / or features, and vice versa The same is true.

  While particular features have been illustrated and described herein, many modifications, alternatives, changes, and equivalents may occur to those skilled in the art. Accordingly, it is to be understood that the appended claims cover all such modifications and changes as long as they fall within the true spirit of this disclosure.

Claims (17)

A first cellular manager controlling a source cellular network,
A first interface for receiving a message including one or more wireless local area network (WLAN) offload parameters of a second cellular manager of the target cellular network;
An offload controller for selecting a selected offloading mechanism from a first offloading mechanism and a second offloading mechanism based on the WLAN offloading parameter of the second cellular manager. An offloading controller that offloads user equipment (UE) to a WLAN, and the second offloading mechanism offloads the UE to the target cellular network;
A second interface for sending an offloading message to the UE according to the selected offloading mechanism;
A first cellular manager comprising:   The offload controller is configured to determine between the first offloading mechanism and the second offloading mechanism based on the load of the second cellular manager and the WLAN offload parameter of the second cellular manager. The first cellular manager of claim 1, wherein   The first cellular manager of claim 1, wherein when the selected offloading mechanism includes the first offloading mechanism, the offloading message includes radio access network (RAN) assistance WLAN interworking information. The offloading message includes an offloading trigger that triggers offloading of the UE to the target cellular network when the selected offloading mechanism includes the second offloading mechanism. The first cellular manager.   The WLAN offload parameter of the second cellular manager comprises at least one parameter selected from the group comprising a cellular parameter threshold, a WLAN parameter threshold, and an offload preference indicator (OPI). The first cellular manager.   The first cellular manager is an evolved Node B (eNB), and the second interface includes a cellular transceiver that transmits the offloading message to the UE. A first cellular manager according to clause.   The first cellular manager of claim 6, wherein the second cellular manager comprises another eNB and the first interface comprises an X2 application protocol (X2AP).   The second cellular manager includes a radio network controller (RNC), and the first interface includes an S1 application protocol (S1AP) that communicates with the RNC via a mobility management entity (MME). The first cellular manager as described.   The first cellular manager is a radio network controller (RNC), the second cellular manager includes an evolved Node B (eNB), and the first interface communicates with the eNB via a core network 6. The first cellular manager according to claim 1, comprising a core network interface, wherein the second interface comprises a Node B interface that communicates with the UE via a Node B. 7.   The first cellular manager according to claim 1, comprising a memory and a processor. A system comprising a first cellular manager according to any one of the preceding claims. A method performed in an evolved Node B (eNB) that controls a source cellular network, comprising:
Receiving at least one message comprising one or more wireless local area networks (WLAN) offload parameters of the second cellular manager of the target cellular network,
Selecting a selected offloading mechanism from a first offloading mechanism and a second offloading mechanism based on the WLAN offload parameters of the second cellular manager, the first offloading mechanism comprising: Selecting an offloading mechanism to offload user equipment (UE) to a WLAN and the second offloading mechanism to offload the UE to the target cellular network;
And generating an off-loading message based on the selected offloading mechanism,
And transmitting the offloading message to the UE,
Including methods. The method of claim 12 , wherein the offloading message includes radio access network (RAN) assisted WLAN interworking information based on the one or more WLAN offload parameters. The method according to claim 12 or 13 , wherein the offloading message comprises an offloading trigger that triggers offloading of one or more user equipments (UEs) to the target cellular network. 15. The WLAN offload parameter according to any one of claims 12 to 14 , wherein the WLAN offload parameter comprises at least one parameter selected from the group comprising a cellular parameter threshold, a WLAN parameter threshold, and an offload preference indicator (OPI). The method described. A computer program for causing a processor to implement the method according to any one of claims 12 to 15. A computer-readable storage medium storing the computer program according to claim 16 .

Images