Network control of terminals with respect to multiple radio access networks

Abstract

There is provided a method, in a terminal, for handling connections to two radio access networks, the method comprising receiving (601), from a first radio access network, one or more threshold values and/or conditions for use in determining how the terminal should handle connections to a second radio access network, wherein the one or more threshold values and/or conditions are received in a message field used to carry threshold values and wherein at least one of the threshold values and/or conditions corresponds to a reserved value and/or condition that indicates an action for the terminal to take with respect to the second radio access network; and carrying out one or more actions with respect to the second radio access network, based on the received one or more threshold values and/or conditions (603).

Claims

1. A method, in a terminal, for handling connections to two radio access networks, the method comprising: receiving, from a first radio access network, in a message field used to carry threshold values for use in determining how the terminal should handle connections to a second radio access network, a reserved value that indicates at least one action for the terminal to take with respect to the second radio access network; and carrying out one or more actions with respect to the second radio access network, in response to receiving the reserved value in the message field, without applying the reserved value as a threshold value.

2. The method of claim 1, wherein the one or more actions comprise one or more of the following: establishing or refraining from establishing a connection to the second radio access network; connecting to or disconnecting from the second radio access network; sending or refraining from sending measurement reports regarding the second radio access network to the first radio access network; steering or refraining from the steering of traffic to the second radio access network; moving some or all traffic from the second radio access network to the first radio access network or vice versa; turning on or refraining from turning on terminal access functionality for radio access technology of the type supported by the second radio access network; turning on or turning off terminal access functionality for radio access technology of the type supported by the second radio access network; putting mobile access functionality for radio access technology of the type supported by the second radio access network into or out of a power saving state or mode.

3. The method of claim 1, wherein the one or more actions carried out are further based on a state of the terminal with respect to the second radio access network, such that different states can result in different actions, given the same reserved value.

4. The method of claim 1, further comprising determining that the reserved value indicates an impossible threshold and/or condition, wherein said carrying out of the one or more actions is responsive to said determining.

5. The method of claim 1, wherein said carrying out one or more actions is further conditioned on one or more other controlling mechanisms applicable to the terminal.

6. The method of claim 1, wherein the first radio access network is a cellular telecommunications network and the second radio access network is a wireless local area network.

7. A method, in a network node of a first radio access network, for managing connections of a terminal to a second radio access network, the method comprising: determining, for the terminal, that the terminal should take at least one specific action with respect to the second radio access network; and sending, in a message field used to carry threshold values for use in determining how the terminal should handle connections to a second radio access network, a reserved value that indicates the at least one specific action for the terminal to take, with respect to the second radio access network, wherein the reserved value is sent in the message field instead of a threshold value.

8. The method of claim 7, wherein the at least one specific action comprises one or more of the following: establishing or refraining from establishing a connection to the second radio access network; connecting to or disconnecting from the second radio access network; sending or refraining from sending measurement reports regarding the second radio access network to the first radio access network; steering or refraining from the steering of traffic to the second radio access network; moving some or all traffic from the second radio access network to the first radio access network, or vice versa; turning on or refraining from turning on terminal access functionality for radio access technology of the type supported by the second radio access network; turning on or turning off terminal access functionality for radio access technology of the type supported by the second radio access network; putting mobile access functionality for radio access technology of the type supported by the second radio access network into or out of a power saving state or mode.

9. The method of claim 7, the reserved value indicates an impossible threshold value and/or condition, thereby indicating that the terminal is to take the at least one specific action.

10. The method of claim 7, wherein the first radio access network is a cellular telecommunications network and the second radio access network is a wireless local area network.

11. A terminal apparatus comprising: radio circuitry configured to handle connections to two radio access networks; and a processing circuit configured to: receive, from a first radio access network, in a message field used to carry threshold values for use in determining how the terminal should handle connections to a second radio access network, a reserved value that indicates an action for the terminal to take with respect to the second radio access network; carry out one or more actions with respect to the second radio access network, in response to receiving the reserved value in the message field, without applying the reserved value as a threshold value.

12. A network node adapted for use in a first radio access network, for managing connections of a terminal to a second radio access network, the network node comprising a processing circuit configured to: determine, for the terminal, that the terminal should take at least one specific action with respect to the second radio access network; and send, in a message field used to carry threshold values for use in determining how the terminal should handle connections to a second radio access network, a reserved value that indicates the at least one specific action for the terminal to take, with respect to the second radio access network, wherein the reserved value is sent in the message field instead of a threshold value.

13. The network node of claim 12, wherein the network node is a base station apparatus and the base station apparatus further comprises radio circuitry configured to handle connections to one or more mobile terminals according to the first radio access technology.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) Exemplary embodiments of the techniques introduced in this document are described below with reference to the following figures, in which:

(2) FIGS. 1 and 2 show a simplified architecture of a W-Fi network;

(3) FIGS. 3 and 4 illustrate BSS load and WAN metrics elements;

(4) FIG. 5 illustrates a W-Fi network that is not integrated into a mobile network;

(5) FIG. 6 illustrates some of the drawbacks of a Wi-Fi-if-coverage strategy method of access network selection;

(6) FIG. 7 is an illustration of integration of Wi-Fi and a mobile cellular network using common authentication;

(7) FIG. 8 is an illustration of user plane integration of Wi-Fi and a mobile cellular network;

(8) FIG. 9 is an architectural overview of E-UTRAN/EPC and S2a integration;

(9) FIG. 10 is a diagram illustrating the overall architecture of an LTE network;

(10) FIG. 11 is a diagram illustrating the functional split between E-UTRAN and EPC;

(11) FIG. 12 illustrates part of a LTE network and a W-Fi network;

(12) FIG. 13 is a process flow diagram illustrating a method in a network and a mobile terminal according to an embodiment;

(13) FIG. 14 is a process flow diagram of a method of operating a mobile terminal according to an embodiment;

(14) FIG. 15 is a process flow diagram of a method of operating a network node according to an embodiment;

(15) FIG. 16 is a block diagram of a mobile terminal according to an embodiment; and

(16) FIG. 17 is a block diagram of a network node according to an embodiment.

DETAILED DESCRIPTION

(17) In the discussion that follows, specific details of particular embodiments of the present invention are set forth for purposes of explanation and not limitation. It will be appreciated by those skilled in the art that other embodiments may be employed apart from these specific details. Furthermore, in some instances detailed descriptions of well-known methods, nodes, interfaces, circuits, and devices are omitted so as not obscure the description with unnecessary detail. Those skilled in the art will appreciate that the functions described may be implemented in one or in several nodes. Some or all of the functions described may be implemented using hardware circuitry, such as analog and/or discrete logic gates interconnected to perform a specialized function, application-specific integrated circuits (ASICs), programmable logic arrays (PLAs), digital signal processors (DSPs), reduced instruction set processors, field programmable gate arrays (FPGAs), state machines capable of performing such functions, etc. Likewise, some or all of the functions may be implemented using software programs and data in conjunction with one or more digital microprocessors or general purpose computers. Where nodes that communicate using the air interface are described, it will be appreciated that those nodes also have suitable radio communications circuitry. Moreover, the technology can additionally be considered to be embodied entirely within any form of computer-readable memory, including non-transitory embodiments such as solid-state memory, magnetic disk, or optical disk containing an appropriate set of computer instructions that would cause a processor to carry out the techniques described herein.

(18) Hardware implementations of the present invention may include or encompass, without limitation, digital signal processor (DSP) hardware, a reduced instruction set processor, hardware (e.g., digital or analog) circuitry including but not limited to application specific integrated circuit(s) (ASIC) and/or field programmable gate array(s) (FPGA(s)), and (where appropriate) state machines capable of performing such functions.

(19) In terms of computer implementation, a computer is generally understood to comprise one or more processors or one or more controllers, and the terms computer, processor, and controller may be employed interchangeably. When provided by a computer, processor, or controller, the functions may be provided by a single dedicated computer or processor or controller, by a single shared computer or processor or controller, or by a plurality of individual computers or processors or controllers, some of which may be shared or distributed. Moreover, the term “processor” or “controller” also refers to other hardware capable of performing such functions and/or executing software, such as the example hardware recited above.

(20) The discussion that follows frequently refers to “mobile terminals,” “terminals,” or “UEs,” the latter of which is the 3GPP term for end user wireless devices. It should be appreciated, however, that the techniques and apparatus described herein are not limited to 3GPP UEs, but are more generally applicable to end user wireless devices (e.g., portable cellular telephones, smartphones, wireless-enabled tablet computers, etc.) that are useable in cellular systems. It should also be noted that the current disclosure relates to end user wireless devices that support both a wireless local area network (WLAN) technology, such as one or more of the IEEE 802.11 standards, and a wide-area cellular technology, such as any of the wide-area radio access standards maintained by 3GPP. End user devices are referred to in Wi-Fi document as “stations”, or “STA”—it should be appreciated that the term “UE” as used herein should be understood to refer to a STA, and vice-versa, unless the context clearly indicates otherwise. It should also be noted that the current disclosure also relates to end user wireless devices that support both a wide-area cellular technology, such as any of the wide-area radio access standards maintained by 3GPP, and a non-3GPP standardized RAT, such as the Global System for Mobile Communications (GSM), and for which improvements to the selection of the access network are desired.

(21) As used herein, a “base station” comprises in a general sense any node transmitting radio signals in the downlink (DL) to a mobile device and/or receiving radio signals in the uplink (UL) from the mobile device. Some example base stations are eNodeB, eNB, Node B, macro/micro/pico/femto radio base station, home eNodeB (also known as femto base station), relay, repeater, sensor, transmitting-only radio nodes or receiving-only radio nodes. A base station may operate or at least perform measurements in one or more frequencies, carrier frequencies or frequency bands and may itself be capable of carrier aggregation. It may also be a single-radio access technology (RAT), multi-RAT, or multi-standard node, e.g., using the same or different base band modules for different RATs. Although the embodiments described below refer to a macrocell base station, it will be appreciated that the teachings of this application are applicable to any type of base station (e.g. femtocell base stations, picocell base stations, microcell base station, etc.) whether deployed in a homogeneous or heterogeneous network.

(22) The signalling described is either via direct links or logical links (e.g. via higher layer protocols and/or via one or more network nodes). For example, signalling from a coordinating node may pass another network node, e.g., a radio node.

(23) Overall E-UTRAN Architecture

(24) An exemplary Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) 210 architecture is shown in FIG. 10. The E-UTRAN architecture 210 consists of base stations 220, 230, 240 called enhanced NodeBs (eNBs or eNodeBs), which provide the E-UTRA user plane and control plane protocol terminations towards the User Equipment (UE). The eNBs 220, 230, 240 are interconnected with each other by means of the X2 interface 250, 252, 254. The eNBs 220, 230, 240 are also connected by means of the S1 interface (260, 262, 264, 266) to the EPC (Evolved Packet Core) 270, more specifically to the MME (Mobility Management Entity) 280, 290, by means of the S1-MME interface, and to the Serving Gateway (S-GVV) 280, 290 by means of the S1-U interface. The S1 interface supports many-to-many relations between MMEs/S-GWs and eNBs.

(25) The eNB hosts functionalities such as Radio Resource Management (RRM), radio bearer control, admission control, header compression of user plane data towards serving gateway, and routing of user plane data towards the serving gateway. The MME 280, 290 is the control node that processes the signalling between the UE and the core network 270. The main functions of the MME 280, 290 are related to connection management and bearer management, which are handled via Non Access Stratum (NAS) protocols. The S-GW 280, 290 is the anchor point for UE mobility, and also includes other functionalities such as temporary downlink data buffering while the UE is being paged, packet routing and forwarding the right eNB, gathering of information for charging and lawful interception. A Packet Data Network (PDN) Gateway (P-GW) is the node responsible for UE Internet Protocol (IP) address allocation, as well as Quality of Service (QoS) enforcement. FIG. 11 gives a summary of the functionalities of the different nodes, and the reader is referred to the 3GPP document “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall Description; Stage 2,” 3GPP TS 36.300, v. 11.3.0 (September 2012), available at www.3gpp.org, and the references therein for the details of the functionalities of the different nodes. In FIG. 11, the boxes labelled “eNB,” “MME,” “S-GW,” and “P-GW” depict the logical nodes, the unshaded white boxes within the larger boxes depict the functional entities of the control plane, and the shaded blue boxes within the box labelled “eNB” depict the radio protocol layers.

(26) FIG. 12 illustrates a network where the LTE radio access parts (eNBs) 320, 322 and a Wi-Fi wireless access point 310 are both connected to the same P-GW 340. In the case of the LTE radio access parts, the eNBs 320, 322 are connected to the P-GW 340 via an S-GW 330. A UE 300 is shown that is capable of being served both from the Wi-Fi Access Point 310 and the LTE eNBs 320, 322. Arrows 350 and 352 illustrate the uplink (UL) and downlink (DL) transmissions between the UE 300 and the Wi-Fi AP 310 respectively and arrows 360 and 362 illustrate the uplink (UL) and downlink (DL) transmissions between the UE 300 and the eNBs respectively. FIG. 12 illustrates one possible way of connecting a Wi-Fi access network 302 to the same core network as the 3GPP-specified access network 304. It should be noted that the presently disclosed techniques are not restricted to scenarios where the Wi-Fi access network 302 is connected in this way; scenarios where the networks are more or completely separate, such as shown in FIG. 5, 7, 8 or 9 are also possible.

(27) In the following description of the various solutions provided by the present disclosure, the arrangement shown in FIG. 12 is used as a basis for the explanation, and references in the description below to a terminal/UE, eNB, 3GPP network/RAN/RAT, Wi-Fi AP and WLAN are to the UE 300, eNB 320, 3GPP network/RAN/RAT 304, Wi-Fi AP 310 and WLAN 302 shown in FIG. 12. However, it will be appreciated that the various solutions provided by the present disclosure are not limited to implementation in the arrangement shown in FIG. 12.

(28) As noted above, many smartphones on the market today support Wi-Fi connectivity (or, more generally, WLAN connectivity), in addition to supporting one or more cellular radio-access technologies (RATs), such as the several RATs standardized by 3GPP (e.g. LTE, UMTS, HSPA, GSM, etc.). As will be detailed below, a network (e.g. a 3GPP network) can control how a terminal should handle a WLAN connection, e.g. when to connect to WLAN, by using thresholds and conditions.

(29) Network Control of a Terminal's WLAN Connection

(30) One way to implement 3GPP network control with regards to how a terminal 300 handles WLAN 302 is by use of thresholds and conditions. According to this approach, the 3GPP network 304 signals to the terminal 300 a set of thresholds and conditions which dictate how the terminal 300 should handle a WLAN entity 302. The thresholds could, for example, dictate when a terminal should: send a measurement report to the 3GPP network 304; connect to a WLAN network 302; steer traffic over WLAN 302; etc.

(31) The thresholds and conditions could relate to one or more of several measurable parameters, such as received signal strength, received signal quality, load, etc. For instance, in one example implementation the thresholds and conditions can indicate to the terminal 300 that it should connect to a WLAN network 302 if the following conditions are fulfilled: measured 3GPP reference signal received power (RSRP)<Threshold.sub.RSRP, measured WLAN received signal strength indication (RSSI)>Threshold.sub.RSSI, and WLAN Load<Threshold.sub.WLANLoad.
An exemplary set of values for the thresholds are Threshold.sub.RSRP=−105 dBm, Threshold.sub.RSSI=−75 dBm and Threshold.sub.WLANLoad=60%.

(32) The thresholds could be adjusted by the 3GPP network 304 from time to time, in some embodiments of this approach, to control the terminal behaviour. If the 3GPP network 304 wants to avoid a terminal 300 connecting to WLAN 302, it could, for example, set the Threshold.sub.RSRP to a low value (or a lower value than previously), Threshold.sub.RSSI to a large (or a larger value than previously) value, and Threshold.sub.WLANLoad to a low value (or a lower value than previously). If the 3GPP network 304 wants to make a or multiple UEs 300 connect to WLAN 302, it can set the Threshold.sub.RSRP to a high value (or a higher value than previously), Threshold.sub.RSSI to a low value (or a lower value than previously), and Threshold.sub.WLANLoad to a large value (or a higher value than previously).

(33) A threshold can be signalled as a bit string (i.e. a series of 0s and 1s) and where the different values of the bitstring can be mapped to a specific threshold. The table below illustrates how the mapping between the bitstring carrying the Threshold.sub.RSRP can be mapped to different threshold values for RSRP:

(34) TABLE-US-00001 TABLE 1 Example bitstring to RSRP threshold mapping. Bitstring value Threshold.sub.RSRP 0000 −120 dBm 0001 −115 dBm 0010 −110 dBm . . . . . .

(35) Thus, the network can control how a terminal 300 should handle a WLAN connection, e.g. when to connect to WLAN 302, by using thresholds and conditions.

(36) A problem with this procedure is that it will cost unnecessary UE 300 power as the terminal 300 needs to perform the measurements and evaluations even in situations when the terminal 300 is not going to connect to WLAN 302. Performing measurements costs power in the terminal 300 which will reduce user experience as the terminal battery lifetime will be reduced. Therefore to save power it is necessary to allow the terminal 300 to refrain from performing WLAN measurements and evaluations. To enable this, an additional message needs to be introduced, which in turn will increase signalling load in the system.

(37) Embodiments of the present invention therefore include methods allowing the 3GPP network 304 to control when a terminal 300 should perform certain actions with regards to WLAN 302 by using fields used for thresholds. In some cases, this may be done by setting aside (or reserving) one or more values for pre-existing fields in 3GPP messages to be used to indicate actions to be taken with respect to the WLAN 302. For example, a field for indicating a WLAN RSSI-threshold can be set by the 3GPP network 304 to its maximum value to indicate that the terminal 300 should refrain from connecting to a WLAN 302 (with the terminal 30 being configured to interpret the maximum value for this field as instructing the terminal 300 to refrain from connecting to the WLAN 302).

(38) In this document it is described how one network is controlling how a terminal should handle an entity (e.g. a transceiver unit) capable of connecting to another network. Embodiments of the disclosed techniques and apparatus are described herein in the context of a 3GPP network 304 controlling a terminal's WLAN entity (e.g. a transceiver unit for communicating with a WLAN). However, it should be appreciated that the same techniques may be applied also to other types of networks. For instance, it could be that a WLAN network 302 is controlling a terminal's 3GPP entity (e.g. a transceiver unit for communicating with a 3GPP network), a WiMAX network is controlling a terminal's 3GPP connection, etc.

(39) The term terminal is used in many places in this document for describing a device with capability to connect to wireless networks. However, it should be appreciated other terms can be used for the same thing. For example, according to the 3GPP specification the terminal is called user equipment (UE) and according to the WLAN specifications the term stations (STAs) is used for terminals.

(40) As described above, the network may signal to the terminal a set of thresholds represented by a bitstring, where the different (reserved) values of the bitstring can be mapped to different thresholds (i.e. different reserved threshold values) that tell the terminal how it should handle a WLAN entity (e.g. a transceiver unit in the UE), such as under which conditions the terminal 300 should connect to WLAN 302, when it should send measurement reports, etc.

(41) In some embodiments of the present invention a message is sent from the network 304 to the terminal 300 and contains a field used for signalling a threshold (i.e. a threshold value). One value (or set of values or condition(s)) of the field is reserved for indicating to the terminal 300 that the terminal 300 should perform a certain action. One benefit of this embodiment is that the network 304 can indicate to the terminal 300 that it should take a certain action without the need for introducing a specific message or field in a message for indicating this action. This allows for reduced signalling load, since no specific messages or fields in messages are required to be transmitted.

(42) List 1, below, illustrates example actions that could be indicated to the terminal 300 according to these embodiments:

(43) TABLE-US-00002 List 1 Establishing a connection to WLAN (and possibly disconnecting the connection to 3GPP) Refrain from establishing a connection to WLAN (and possibly maintain the connection to 3GPP). Connect to WLAN. Disconnect from WLAN. Send measurement reports regarding WLAN to the network. Refrain from sending measurement reports regarding WLAN to the network. Steer traffic to WLAN. Refrain from steering traffic to WLAN. Move some or all traffic from a 3GPP RAT to WLAN. Move some or all traffic from WLAN to a 3GPP RAT. Turn on the WLAN entity (e.g. a transceiver unit) Refrain from turning the WLAN entity (e.g. a transceiver unit) on. Turn off the WLAN entity (e.g. a transceiver unit). Take the WLAN entity out of a power saving state/mode Put the WLAN entity (e.g. a transceiver unit) in a power saving state/mode.

(44) Note: Some of these actions may share the same (reserved) bitstring value, which can be interpreted differently, depending on the terminal's state. For example, “Refrain from establishing a connection to WLAN” and “Disconnect from WLAN” might share the same bitstring value, in some embodiments. The terminal 300 would, when receiving this indication, disconnect from WLAN 302 if the terminal 300 is connected to WLAN 302. If the terminal 300 is not connected to WLAN 302 when it receives this indication, it would refrain from connecting to WLAN 302.

(45) In one alternative of this embodiment the indication does not mean that the terminal 300 has to perform the indicated action. Instead it means that the terminal 300 is allowed to perform the appropriate action(s) in List 1 (or other actions indicated by the message), if deemed suitable by other controlling mechanisms. For example, the terminal 300 may require the WLAN entity to be turned on to perform WLAN measurements on a private-WLAN (i.e. a WLAN not associated with the 3GPP network operator) and the network 304 may not be aware of this. Hence the network 304 should not prohibit that the terminal 300 keeps the WLAN entity (e.g. a transceiver unit) turned on but rather allow for the terminal 300 to turn off WLAN and the terminal 300 may do so if other controlling mechanisms also deem it suitable.

(46) Regarding the meaning of being connected to WLAN, it can, for example, mean any one or more of the following: 802.11 authentication (Authentication to the WLAN AP) 802.1× EAP-SIM authentication (Authentication to the AAA-servers) Four way hand-shake between the terminal and the WLAN network is completed Getting an IP address assigned in WLAN A PDN connection is established through the WLAN network, i.e. a connection between the terminal and the PDN gateway. Data traffic has been started through the WLAN network.

(47) The network 304 may signal to the terminal 300 more than one field used for signalling thresholds. In an alternative embodiment, the terminal 300 is configured such that it should consider more than one field when determining whether it has received an indication to perform one of the actions listed in List 1. The terminal 300 could, for example, be configured such that only if both the Threshold.sub.RSRP and the Threshold.sub.RSSI are set to certain reserved values the terminal 300 considers the indication to be received. Another example configuration of the terminal 300 is that if either of the Threshold.sub.RSRP or the Threshold.sub.RSSI are set to certain reserved values, then the terminal 300 considers the indication to be received.

(48) In one specific implementation of this invention, a reserved bitstring value is mapped to a value that is not possible to achieve (i.e. a value that will not occur in a practical implementation of the terminal/network). As the value is not possible to achieve, the terminal 300 may take appropriate actions upon receiving this value. For example, if the network 304 has indicated to the terminal 300 that it should connect to a WLAN network 302 if the 3GPP RSRP is equal to or above positive infinity, then it is clear that the terminal 300 would never connect to WLAN 302, since the RSRP cannot reach positive infinity. The terminal 300 may then be configured to turn off WLAN (or take any of the other actions listed in List 1), given such a threshold. Examples of such threshold values which cannot be achieved (or are unrealistic in practice) are given below: Threshold.sub.RSRP of positive infinity Threshold.sub.RSSI of positive infinity Threshold.sub.WLANLoad of 101% Threshold.sub.RSSI of +10 dBm

Example Implementation and Procedures

(49) Examples of possible mappings of a bitstring to thresholds are given below, in Tables 2, 3, and 4:

(50) TABLE-US-00003 TABLE 2 Example bitstring to RSRP threshold mapping. Bitstring value Threshold.sub.RSRP 0000 −120 dBm 0001 −115 dBm 0010 −110 dBm 0011 −105 dBm 0100 −100 dBm . . . . . . 1110  −50 dBm 1111 Disconnect from WLAN

(51) TABLE-US-00004 TABLE 3 Example bitstring to RSSI threshold mapping. Bitstring value Threshold.sub.RSSI 0000 −120 dBm 0001 −115 dBm 0010 −110 dBm . . . . . . 1110  −50 dBm 1111 Disconnect from WLAN

(52) TABLE-US-00005 TABLE 4 Example bitstring to WLAN load mapping. Bitstring value Threshold.sub.WLANLoad 000 14 001 28 010 42 011 57 100 71 101 88 110 100 111 Disconnect from WLAN

(53) It will be appreciated that the example bitstrings for the three parameters can be communicated to the terminal 300 using respective message fields, or they can be combined into a single bitstring and included in a single (suitably large) message field.

(54) Example Event Flow:

(55) In the example implementation illustrated in the process flow diagram of FIG. 13, at least one of Threshold.sub.RSRP, Threshold.sub.RSSI and Threshold.sub.WLANLoad is required to be set to “Disconnect from WLAN” for the terminal 300 to consider that it has been indicated that it should disconnect from WLAN 302. In alternative implementations, the terminal could consider that it has been indicated that it should disconnect from WLAN 302 if all or multiple ones of the thresholds are set to the appropriate reserved values. It will be appreciated that different actions can be indicated by different ones of the thresholds being set to a reserved value.

(56) It will be appreciated that the process flow diagram of FIG. 13 illustrates the steps performed in the system, and thus includes steps that are performed in the network and in the mobile terminal 300.

(57) In this example implementation, the mobile terminal is configured to connect to a WLAN 302 if certain thresholds and/or conditions are met. The thresholds and/or conditions are: measured 3GPP RSRP<threshold.sub.RSRP measured WLAN RSSI>threshold.sub.RSSI; and WLAN Load<threshold.sub.WLANLoad

(58) In a first step, step 501, the 3GPP network 304 determines the thresholds to be used by the mobile terminal 300 to determine whether to connect to the WLAN 302. In this example, the thresholds and/or conditions to be met in order for the mobile terminal 300 to connect to the WLAN 302 are: measured 3GPP RSRP<−100 dBm measured WLAN RSSI>−90 dBm WLAN Load<57%
(so threshold.sub.RSRP=−100 dBm; threshold.sub.RSSI=−90 dBm; and threshold.sub.WLANLoad=57%).

(59) In a second step, step 503, the network 304 signals the thresholds and/or conditions to the mobile terminal 300 using one or message fields used to signal threshold values to the mobile terminal 300. The network thus signals bitstrings to the mobile terminal 300 with each bitstring representing a respective one of the threshold values.

(60) In step 505, the mobile terminal 300 receives the threshold values and/or conditions, starts to measure the relevant parameters of the 3GPP network 304 (e.g. reference signal received quality (RSRQ), received signal code power (RSCP) and/or RSRP) and the WLAN 302 (i.e. RSSI and load) and determine whether the thresholds and/or conditions are met.

(61) If or once the thresholds and/or conditions are met, the mobile terminal 300 connects to the WLAN 302 (step 507).

(62) If the network 304 subsequently decides that the mobile terminal 300 should disconnect from the WLAN 302 (step 509), the network sends another message to the mobile terminal 300 containing an appropriate value for one or more of the thresholds and/or conditions that is interpreted by the mobile terminal 300 as an instruction from the network 304 to disconnect from the WLAN 302.

(63) The network 304 can therefore signal this action to the mobile terminal 300 using an appropriate threshold value that has been reserved by the network 304 and mobile terminal 300 for this purpose (step 511). An exemplary set of threshold values and/or conditions that can be signalled to the mobile terminal 300 are set out below Threshold.sub.RSRP=<the value that represents: Disconnect from WLAN> Threshold.sub.RSSI=<Any value> Threshold.sub.WLANLoad=<Any value>

(64) On receipt of this message, the mobile terminal 300 reads the threshold value(s) and/or conditions from the message, interprets the value for the Threshold.sub.RSRP as instructing the mobile terminal 300 to disconnect from the WLAN 302 and then disconnects from the WLAN 302 (step 513).

(65) FIG. 14 is a process flow diagram illustrating a method, in a mobile terminal 300, for handling connections to two radio access technologies. It will be appreciated that the illustrated method is a generalization of the techniques detailed above.

(66) As shown at block 601, the method begins with receiving, from a first radio access network (e.g. a network operating according to a first radio access technology, RAT), one or more threshold values and/or conditions for use in determining how the mobile terminal 300 should handle connections to the second radio access network (e.g. a network operating according to a second, possibly different, RAT), where the one or more threshold values and/or conditions are received in a message field that is otherwise used to carry threshold values for regulating the behaviour of the mobile terminal 300. At least one of the possible threshold values and/or conditions correspond to a reserved value and/or condition that is used to indicate an action for the mobile terminal to take with respect to the second radio access network.

(67) In some embodiments, the message field is otherwise used to carry threshold values for regulating the behaviour of the mobile terminal 300 with respect to the first radio access network.

(68) As noted above, one or more values for this field are reserved to indicate that the mobile terminal 300 should take some action with respect to the second radio access network. This indication may be implicit, such as through the use of an impossible threshold value (i.e. a value that will not realistically occur in a practical implementation of the terminal/network), or explicit, in that a particular value is set aside by the first radio access network for the express purpose of indicating the action. The mobile terminal 300 will be configured or arranged to interpret the reserved threshold value(s) and/or conditions as specifying the specific action(s) to take with respect to the second radio access network. In particular, the mobile terminal will be configured to determine whether any received threshold values and/or conditions correspond to a value and/or condition reserved for indicating an action for the mobile terminal to take with respect to the second radio access network, and if so the mobile terminal will be configured to carry out the action indicated by the reserved value and/or condition.

(69) In some embodiments, this field is a pre-existing field in a pre-existing message sent by the first radio access network. As shown at block 603, the method continues with carrying out one or more actions with respect to the second radio access network, based on the received one or more threshold values and/or conditions.

(70) As discussed above, e.g., in connection with List 1, the one or more actions carried out by the mobile terminal 300 may include any one or more of the following: establishing or refraining from establishing a connection to the second radio access network; connecting to or disconnecting from the second radio access network; sending or refraining from sending measurement reports regarding the second radio access network to the first radio access network; steering or refraining from the steering of traffic to the second radio access network; moving some or all traffic from the second radio access network to the first radio access network (or vice versa); turning on or refraining from turning on mobile terminal access functionality (i.e. a transceiver unit) for radio access technology of the type supported by the second radio access network; turning on or turning off mobile terminal access functionality (i.e. a transceiver unit) for radio access technology of the type supported by the second radio access network; and putting mobile access functionality (i.e. a transceiver unit) for radio access technology of the type supported by the second radio access network into or out of a power saving state or mode.

(71) In some embodiments, the one or more actions carried out are further based on a state of the mobile terminal 300 with respect to the second radio access network, such that different states can result in different actions, given the same threshold values and/or conditions. For instance, in some embodiments carrying out the one or more actions may comprise, in response to a particular threshold value, disconnecting from the second radio access network if already connected to the second radio access network and otherwise (i.e. if not already connected to the second radio access network) refraining from connecting to the second radio access network.

(72) In some embodiments, the received threshold value or condition indicates an impossible threshold or condition (i.e. a value that will not realistically occur in a practical implementation of the terminal/network), and the mobile terminal carries out the one or more actions in response to determining that the received threshold value or condition indicates an impossible threshold or condition. In these and in other embodiments, the carrying out of the one or more actions may be further conditioned on one or more other controlling mechanisms applicable to the mobile terminal 300.

(73) In some embodiments, the first radio access network is a cellular telecommunications network, such as a 3GPP LTE network, and the second radio access network is a wireless local area network, such as an IEEE 802.11 wireless network.

(74) FIG. 15 is a process flow diagram illustrating a corresponding method, implemented in a network node, for example a base station (e.g. an eNB), of a first radio access network (e.g. a network operating according to a first RAT). The illustrated method begins, as shown at block 701, with determining, for a mobile terminal 300, one or more threshold values and/or conditions for use in determining how the mobile terminal 300 should handle connections to a second radio access network (e.g. a network operating according to a second, possibly different, RAT). The one or more threshold values and/or conditions are then sent to the mobile terminal 300, as shown at block 703. At least one of the possible threshold values and/or conditions correspond to a reserved value and/or condition that is used to indicate an action for the mobile terminal to take with respect to the second radio access network. These threshold values and/or conditions are sent in a message field that is otherwise used to carry threshold values for regulating the behaviour of the mobile terminal 300.

(75) In some embodiments, one or more values for this field are reserved by the first radio access network to indicate that the mobile terminal 300 should take some action with respect to the second radio access network. This indication may be implicit, such as through the use of impossible threshold value (i.e. a value that will not realistically occur in a practical implementation of the terminal/network), or explicit, in that a particular value is set aside for the express purpose of indicating the action. In some embodiments, this field is a pre-existing field in a pre-existing message sent by the first radio access network.

(76) In some embodiments, step 701 can comprise determining how the mobile terminal 300 should handle connections to the second radio access network (i.e. determining a specific action or actions for the mobile terminal 300 to take with respect to the second radio access network), and then determining the appropriate one or more reserved threshold values and/or conditions for the specific action or actions that are to be transmitted to the mobile terminal 300.

(77) In some embodiments, the one or more (reserved) threshold values and/or conditions indicate respective one or more actions to be taken by the mobile terminal 300 with respect to the second wireless (radio) access network, the one or more actions including one or more of the following: establishing or refraining from establishing a connection to the second radio access network; connecting to or disconnecting from the second radio access network; sending or refraining from sending measurement reports regarding the second radio access network to the first radio access network; steering or refraining from the steering of traffic to the second radio access network; moving some or all traffic from the second radio access network to the first radio access network (or vice versa); turning on or refraining from turning on mobile terminal access functionality (i.e. a transceiver unit) for radio access technology of the type supported by the second radio access network; turning on or turning off mobile terminal access functionality (i.e. a transceiver unit) for radio access technology of the type supported by the second radio access network; and putting mobile access functionality (i.e. a transceiver unit) for radio access technology of the type supported by the second radio access network into (or out of) a power saving state or mode.

(78) In some embodiments, determining one or more reserved threshold values and/or conditions comprises determining an impossible threshold value or condition. As was the case for the process flow diagram of FIG. 14, in some embodiments the first radio access network is a cellular telecommunications network, such as a 3GPP LTE network, and the second radio access network is a wireless local area network, such as an IEEE 802.11 wireless network.

(79) Hardware Implementations

(80) Several of the techniques and methods described above may be implemented using radio circuitry and electronic data processing circuitry provided in a terminal. FIG. 16 illustrates features of an example terminal 1500 according to several embodiments of the present invention. Terminal 1500, which may be a UE configured for operation with an LTE network (E-UTRAN) and that also supports Wi-Fi, for example, comprises a transceiver unit 1520 for communicating with one or more base stations as well as a processing circuit 1510 for processing the signals transmitted and received by the transceiver unit 1520. Transceiver unit 1520 includes a transmitter 1525 coupled to one or more transmit antennas 1528 and receiver 1530 coupled to one or more receiver antennas 1533. The same antenna(s) 1528 and 1533 may be used for both transmission and reception. Receiver 1530 and transmitter 1525 use known radio processing and signal processing components and techniques, typically according to a particular telecommunications standard such as the 3GPP standards for LTE. Note also that transmitter unit 1520 may comprise separate radio and/or baseband circuitry for each of two or more different types of radio access network, such as radio/baseband circuitry adapted for E-UTRAN access and separate radio/baseband circuitry adapted for Wi-Fi access. The same applies to the antennas—while in some cases one or more antennas may be used for accessing multiple types of networks, in other cases one or more antennas may be specifically adapted to a particular radio access network or networks. Because the various details and engineering tradeoffs associated with the design and implementation of such circuitry are well known and are unnecessary to a full understanding of the invention, additional details are not shown here.

(81) Processing circuit 1510 comprises one or more processors 1540 coupled to one or more memory devices 1550 that make up a data storage memory 1555 and a program storage memory 1560. Processor 1540, identified as CPU 1540 in FIG. 16, may be a microprocessor, microcontroller, or digital signal processor, in some embodiments. More generally, processing circuit 1510 may comprise a processor/firmware combination, or specialized digital hardware, or a combination thereof. Memory 1550 may comprise one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Because terminal 1500 supports multiple radio access networks, processing circuit 1510 may include separate processing resources dedicated to one or several radio access technologies, in some embodiments. Again, because the various details and engineering tradeoffs associated with the design of baseband processing circuitry for mobile devices are well known and are unnecessary to a full understanding of the invention, additional details are not shown here.

(82) Typical functions of the processing circuit 1510 include modulation and coding of transmitted signals and the demodulation and decoding of received signals. In several embodiments of the present invention, processing circuit 1510 is adapted, using suitable program code stored in program storage memory 1560, for example, to carry out one of the techniques described above for access network selection. Of course, it will be appreciated that not all of the steps of these techniques are necessarily performed in a single microprocessor or even in a single module.

(83) Similarly, several of the techniques and processes described above can be implemented in a network node, such as an eNodeB or other node in a 3GPP network. FIG. 17 is a schematic illustration of a node 2001 in which a method embodying any of the presently described network-based techniques can be implemented. A computer program for controlling the node 2001 to carry out a method embodying the present invention is stored in a program storage 2030, which comprises one or several memory devices. Data used during the performance of a method embodying the present invention is stored in a data storage 2020, which also comprises one or more memory devices. During performance of a method embodying the present invention, program steps are fetched from the program storage 2030 and executed by a Central Processing Unit (CPU) 2010, retrieving data as required from the data storage 2020. Output information resulting from performance of a method embodying the present invention can be stored back in the data storage 2020, or sent to an Input/Output (I/O) interface 2040, which includes a network interface for sending and receiving data to and from other network nodes and which may also include a radio transceiver for communicating with one or more terminals.

(84) Accordingly, in various embodiments of the invention, processing circuits, such as the CPU 2010 in FIG. 17, are configured to carry out one or more of the techniques described in detail above. Likewise, other embodiments include radio network controllers including one or more such processing circuits. In some cases, these processing circuits are configured with appropriate program code, stored in one or more suitable memory devices, to implement one or more of the techniques described herein. Of course, it will be appreciated that not all of the steps of these techniques are necessarily performed in a single microprocessor or even in a single module.

(85) According to the techniques disclosed herein, a network can indicate to the terminal how it should handle the WLAN entity (i.e. transceiver unit) or connections to the WLAN. In some cases, this can be done without the need for signalling additional fields to the terminal. Instead, already existing fields are used. This allows for reduced signalling load.

(86) It will be appreciated by the person of skill in the art that various modifications may be made to the above described embodiments without departing from the scope of the present invention. For example, although embodiments of the present invention have been described with examples that include a communication system compliant to the 3GPP specified LTE standard specification, it should be noted that the solutions presented may be equally well applicable to any other 3GPP specified technology in combination with 802.11 specifications. The specific embodiments described above should therefore be considered exemplary rather than limiting the scope of the invention. Because it is not possible, of course, to describe every conceivable combination of components or techniques, those skilled in the art will appreciate that the present invention can be implemented in other ways than those specifically set forth herein, without departing from essential characteristics of the invention. The present embodiments are thus to be considered in all respects as illustrative and not restrictive.