Abstract:
A method for performing load balancing of data flows from a user equipment (UE) between a first radio access network and a second radio access network, wherein the UE is attached to the said first radio access network, the method comprising providing preference data from the first radio access network to the UE representing radio related parameters, determining the presence of an access network discovery and selection function (ANDSF) of the UE, evaluating, at the UE, including using ANDSF if present, the preference data to determine if a data flow can be offloaded to the second radio access network, and on the basis of the evaluation, offloading a data flow of the UE from the first radio access network.

Description:
TECHNICAL FIELD 
       [0001]    The disclosed embodiments relate generally to wireless network communication, will, more particularly, to multi-radio interworking in heterogeneous wireless communication networks. 
       BACKGROUND 
       [0002]    User communication devices, such as laptops, tablets, smart phones, also known as user equipment (UE) typically support multiple wireless technologies such as WIFI and Cellular Wireless Technologies such as LTE, CDMA and so on. Standard protocols, such as 3GPP, 3GPP2 and so on define control protocols by which the user equipment can select a component access technology. 
         [0003]    Wireless LAN technologies, such as WIFI and WiMAX, are becoming increasingly available as WIFI. These services may be offered by the same operator as the wireless cell operator or by a different operator. Also, cell operators are deploying micro and femto cells in certain locations to increase the capacity and coverage in dense locations. Network selection in the majority of the mobile wireless devices is based on Received Signal Strength or based on the configuration of the best network in the device, and by type of service (voice or data), that the user initiates. For example, on a device that has connectivity to both a radio access network and WIFI networks, when the user initiates a circuit switched (CS) service, such as a voice call or SMS for example, the device uses the RAN. However, when the user initiates packet switched (PS) services, the device uses WLAN. If the device is currently not associated with a WIFI access point (AP), arid if the WWI radio is enabled, the device attempts to connect to the highest priority WLAN/SSID that it successfully connected to previously. 
         [0004]    3GPP standards define Access Network Discovery and Selection (ANDSF) methods by which a mobile device identifies which access network to connect to (Network Selection and inter System Mobility Policy), or which network to route specific IP flows to (Inter System Routing Policy). This framework uses a client application (ANDSF Client) and server (ANDSF Server) in the operator&#39;s core network. However, there is a need for a method and system to enable enhanced operator control for WLAN interworking, and to enable WLAN to be included in an operator&#39;s cellular Radio Resource Management. 
       SUMMARY 
       [0005]    According to an example, there is provided a method for performing load balancing of data flows from a user equipment (UE) between a first radio access network and a second radio access network, wherein the UE is attached to the said first radio access network, the method comprising providing preference data from the first radio access network to the UE representing radio related parameters, determining the presence of an access network discovery and selection function (ANDSF) of the UE, evaluating, at the UE, including using ANDSF if present, the preference data to determine if a data flow can be offloaded to the second radio access network, and 
         [0006]    on the basis of the evaluation, offloading a data flow of the UE from the first radio access network. The preference data can be evaluated at the radio side of the UE (UE access stratum). The preference data can be evaluated at the non-radio side of the UE (UE non-access stratum). The preference data can be provided as an input to an ANDSF module of the UE. The preference data can be provided as an input to a radio signal strength evaluation module for determining a signal strength of a radio communication link between the UE and the first radio access network. A threshold signal strength value can be provided, and offloading a data flow of the UE can be determined on the basis of signal strength compared to the threshold signal strength. The preference data can be forwarded to the UE non-radio side on the basis of a measurement of radio parameters such as signal strength and/or WIFI load. The preference data can be forwarded to the UE non-radio side from the UE radio side without evaluation at the radio side of the UE. A determination as to whether to offload a data flow of the UE from the first radio access network can be made at the UE non-radio side. A determination as to whether to offload a data flow of the UE from the first radio access network can be made at the UE radio side. 
         [0007]    According to an example, there is provided a radio telecommunication system comprising: 
         [0008]    a first radio access network, a second radio access network , a HE attached to the said first radio access network, the system. operable to provide preference data from the first radio access network to the UE representing radio related parameters, determine the presence of an access network discovery and selection function (ANDSF) of the UE, evaluate, at the including using ANDSF if present, the preference data to determine if a data flow can be offloaded to the second radio access network, and on the basis of the evaluation, offload a data flow of the UE from the first radio access network. The UE can be operable to evaluate the preference data at the radio side (UE access stratum) thereof. The UE can be operable to evaluate the preference data at the non-radio side (UE non-access stratum) thereof. According to an example, there is provided a UE operable in accordance with the method as provided above. 
         [0009]    According to an example, there is provided computer program product, comprising a computer usable medium having computer readable program code embodied therein, said computer readable program code adapted to be executed to implement a method, in a radio communication system, for performing load balancing of data flows from a user equipment (UE) between a first radio access network and a second radio access network, wherein the UE is attached to the said first radio access network, the method as provided above. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0010]    Embodiments will now be described, by way of example only, with reference to the accompanying drawings, in which: 
           [0011]      FIG. 1  is a schematic representation of an information flow according to an example; 
           [0012]      FIG. 2  is a schematic representation of another information flow according to an example; 
           [0013]      FIG. 3 a    is a schematic representation of a situation when ANDSF policies are updated to decide whether the RAN preference data should be applied or not according to an example; 
           [0014]      FIG. 3 b    is a further schematic representation of a situation when ANDSF policies are updated to decide whether the RAN preference data should be applied or not according to an example; 
           [0015]      FIG. 4 a    is a schematic representation of a situation when ANDSF policies are further evaluated using WiFi load and 3GPP signal strength according to an example; 
           [0016]      FIG. 4 b    is a further schematic representation of a situation when ANDSF policies are further evaluated using WiFi load mid 3GPP signal strength according to an example; and 
           [0017]      FIG. 5  is a schematic representation of a system according to an example. 
       
    
    
     DETAILED DESCRIPTION 
       [0018]    Example embodiments are described below in sufficient detail to enable those of ordinary skill in the art to embody and implement the systems and processes herein described. It is important to understand that embodiments can be provided in many alternate forms and should not be construed as limited to the examples set forth herein. 
         [0019]    Accordingly, while embodiments can be modified in various ways and take on various alternative forms, specific embodiments thereof are shown in the drawings and described in detail below as examples. There is no intent to limit to the particular forms disclosed. On the contrary, all modifications, equivalents, and alternatives falling within the scope of the appended claims should be included. Elements of the example embodiments are consistently denoted by the same reference numerals throughout the drawings and detailed description where appropriate. 
         [0020]    The terminology used herein to describe embodiments is not intended to limit the scope. The articles “a,” “an,” and “the” are singular in Mat they have a single referent, however the use of the singular form in the present document should not preclude the presence of more than one referent. In other words, elements referred to in the singular can number one or more, unless the context clearly indicates otherwise. It will be anther understood that the terms “comprises,” “comprising,” “includes,” and/or “including,” when used herein, specify the presence of stated features, items, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, items, steps, operations, elements, components, and/or groups thereof. 
         [0021]    Unless otherwise defined, all terms (including technical and scientific terms) used herein are to be interpreted as is customary in the art. It will be further understood that terms in common usage should also be interpreted as is customary in the relevant art and not in an idealized or overly formal sense unless expressly so defined herein. 
         [0022]    In the alternative solution (i.e. solution independent of ANDSF), the radio side of the UE (UE access stratum) performs the load balancing between 3GPP and WLAN. Such load balancing is normally bearer based (i.e. may contain multiple IP flows within it) which may not be what the operator wants (e.g. some special operator IP services should be kept in 3GPP in the non-seamless offload situation) and also it may not align with the decision of ANDSF (if present) resulting in possible ping pong. 
         [0023]    In an example, preference data representing radio access network (RAN) preferences is provided to the ANDSF (if present) or to the non-radio side of the UE (UE non-access stratum (NAS)) to mate the final evaluation on whether to apply the RAN decision/preference of the UE or an IP flow of the UE. The ANDSF includes rules to decide whether a RAN decision/preference should he taken for the UE or an IP flow of the UE. This rule can be whether to override or not or take into consideration further e.g. 3GPP signal strength. WiFi load and roaming/no-roaming case. An operator can decide for each UE or IP flow whether the RAN preference data can override the ANDSF preference. In the case ANDSF is not present, the RAN preference data can be used directly by the NAS to make final decision taking into consideration user preference, local settings etc. 
         [0024]    The RAN preference data sent over the 3GPP RAN either via broadcast or dedicated signalling is arranged in priority order (e.g. 3GPP, WLAN SSID#5, WLAN SSID#2 where 3GPP is highest priority while WLAN SSID#5 is higher priority than WLAN SSID#2 but lower priority than 3GPP). The priority order can be based on network operator preference, load of 3GPP etc. 
         [0025]    There are 2 methods to achieve the above: 
         [0026]      FIG. 1  is a schematic representation of an information flow in which the RAN preference data is provided as an input to the ANDSF module if present or a direct input to the Traffic Steering evaluator module according to an example. The RAN preference data is further evaluated in the ANDSF module whether to be considered for an IP flow/UE. 
         [0027]    In order to prevent conflict with ANDSF (if available), the RAN preference data provides a new routing rules to the active ANDSF policies if they are present (e.g. the policies are provided by the network or statically provisioned by the operator). This also allows the RAN preference data to be used for IP flow traffic sleeting (e.g. for each IP flow or each PDN connection, the ANDSF policy can include within the policy that governed the IP flow or UE whether it will take the RAN preference data into consideration). in the case ANDSF policies are not present, the RAN preference data will be used directly. As the RAN preference data is done on the UE NAS, IP flow traffic steering is still possible (e.g. RAN preference data will govern those IP flows that do not have restrictions by user and application preferences). 
         [0028]    The RAN preference data is decided based on the cell/backhaul load and UE specific factors (e.g. heavy user). In ANDSF policy, RAN preference data can provide (for a UE or IP flow) the access technology priority (e.g. 3GPP is higher priority than WLAN) and for WLAN it can also contain a list of WLAN IDs (e.g. SSID, HESSID etc.) that are high priority or lower priority than 3GPP (e.g. the list can have this priority order WLAN SSID#1, 3GPP, WLAN SSID#2). 
         [0029]    In the case ANDSF is present, the criteria to take into consideration RAN preference datacan include:
       Always override the ANDSF active traffic steering policies (i.e. ISRP and ISMP) for a IP flow   Consider also 3GPP/Win signal strength and/or WLAN load when deciding whether to override the ANDSF preference with the RAN preference data for an IP flow.       
 
         [0032]      FIG. 2  is a schematic representation of an information flow in which the RAN preference data is provided as an input to the ANDSF module if present or a direct input to the Traffic Steering evaluator module according to an example. The RAN preference data is further evaluated in the UE AS whether the UE should take into consideration and the priority order on the WLAN SSIDs provided in the RAN preference data. 
         [0033]    Again to prevent conflict with ANDSF (if available), the RAN preference data is provided as a set of new routing rules to the active ANDSF policies. If ANDSF module is not present, it will be used directly by the Traffic Steering evaluator module, 
         [0034]    Again the RAN preference data is determined based on the ceil/backhaul load and UE specific factors (e.g. heavy user) at the network. At the UE, the RAN preference data is further evaluated at the UE AS based on the 3GPP signal strength. Specific rules can be specified indicating whether to consider the RAN preference data (e.g. if 3GPP signal strength&gt;threshold high for RAN preference data, keep UE in 3GPP or if 3GPP signal strength&lt;threshold_low for RAN preference data, switch UE to WiFi for example). As mentioned above the RAN preference data can contain a list of WLAN IDs which can be ordered based on the WiFi information from the UE WLAN Module. The resultant RAN preference data is then provided to ANDSF (if available) or to the traffic steering evaluator directly. 
         [0035]    With reference to  FIG. 1 , the RAN preference data is provided either as an input to the ANDSF module or directly to the Traffic Steering Evaluator module. In the presence of ANDSF module, the ANDSF policies may either decide whether the preference should be applied or not for an IP flow or further evaluate the preference based on WiFi load and 3GPP/WiFi signal strength whether it should be applied to an IP flow. 
         [0036]    Examples of RAN preference data include: 
         [0037]    a) RAT preference (i.e. either 3GPP or WLAN) 
         [0038]    b) Network preference (i.e. which 3GPP cells and WLAN SSIDs), e.g. {3GPP CID#1, 3GPP CID#5, WLAN SSID#3, WLAN SSID#7} 
         [0039]    The ANDSF can interact with the RAN preference data in a number of ways.  FIGS. 3 a  and 3 b    are examples for the situation when ANDSF policies are updated to decide whether the RAN preference data should be applied or not. More specifically, for ISMP: Whether the RAN preference data will override the Prioritised Access of a rule in the policy ( FIG. 3 a   ), and for ISRP: Whether the RAN preference data will override the RoutingRule of a rule related to a IP flow in the policy ( FIG. 3 b   ). 
         [0040]      FIGS. 4 a  and 4 b    are examples for the situation when ANDSF policies are further evaluated using WiFi load and 3GPP signal strength. More specifically, for ISMP: ANDSF is extended to include RAN parameters such as WiFi load and 3GPP signal strength to decide whether to apply RAN preference data ( FIG. 4 a   ) instead of the Prioritised Access of a rule in the policy. For ISRP: ANDSF is extended to include RAN parameters such as WiFi load and 3GPP signal strength to decide whether to apply RAN preference data ( FIG. 4 b   ) instead of the RoutingRule of a rule related to a IP flow in the policy 
         [0041]    In the case ANDSF is present, the RAN preference data will be an input parameter to the ANDSF function. Based on the user preference, application preference and the ANDSF output, the UE NAS can decide how the UE or a particular IP flow of the UE should move between 3GPP and WLAN. 
         [0042]    Referring to  FIG. 2 , the RAN preference data is first evaluated at the UE AS and the outcome is provided as an input to the ANDSF module or directly to the Traffic Steering Evaluator module. In the presence of ANDSF, the ANDSF policies may decide whether the preference should be applied or not for an IP flow 
         [0043]    The main difference between the methods as described with reference to  FIGS. 1 and 2  is that for the case where consideration of radio parameters is done at the UE AS rather than ANDSF, the UE AS can either (A) determine whether to forward the RAN preference data to UE NAS based on WiFi load and 3GPP/WiFi signal strength and so on, or (B) modify the RAN preference data based on WiFi load and 3GPP/WiFi signal strength before forwarding to UE NAS. 
         [0044]    In the first case, as an example: 
         [0045]    A 3GPP signal strength and WLAN load is used to determine whether a RAN preference data is to be forwarded to UE NAS. For example, if the RAN preference data is to use WLAN, UE will only forward the RAN preference data to UE NAS if the measured radio parameters such as 3GPP signal strength and WLAN load are low. If the RAN preference data is to use 3GPP, UE will only forward the RAN preference data to UE NAS if the measured 3GPP signal strength and WLAN load are high. 
         [0046]    In the second case, as an example: 
         [0047]    RAN preference data is further modified at the UE AS based on radio parameter measurements 3GPP signal strength and WLAN load. For example, the 3GPP signal strength will enable the decision as to whether to forward the RAN preference data to UE NAS while the WLAN load/signal strength will be used to reorder WLAN SSIDs within the preference data. 
         [0048]    Therefore, according to an example, there are two processes that can ensue, either: 
         [0049]    1. UE AS evaluates whether to forward the preference data to UE NAS based on signal strength and WiFi load 
         [0050]    2. If the UE NAS receives the preference data from UE AS 
         [0051]    a. If ANDSF is present, the preference data is an input to the ANDSF and the ANDSF evaluates whether to use the preference data or the ANDSF preference (e.g. just a flag to indicate whether the preference data should override the ANDSF preference) before the UE NAS makes the final decision based on the ANDSF outcome 
         [0052]    b. If ANDSF is not present, the NAS will use the preference data to make final decision. 
         [0053]    Or: 
         [0054]    1. UE AS just forward the preference data to UE NAS 
         [0055]    2. If the UE NAS receives the preference data from UE AS 
         [0056]    a. If ANDSF is present, the preference data is an input to the ANDSF and the ANDSF evaluates whether to use the preference data or the ANDSF preference based, on signal strength and WiFi load before the UE NAS makes the final decision based on the ANDSF outcome 
         [0057]    b. If ANDSF is not present, the UE NAS will use the preference data to make final decision. 
         [0058]    Both methods will use an ANDSF policy if such a module is present. In the case that the UE AS has already performed some evaluation, ANDSF (if present) will determine whether to accept the preference data. Alternatively, ANDSF does all the evaluation. 
         [0059]      FIG. 5  is a schematic representation of a system according to an example. A radio telecommunication system ( 10 ) comprises a first radio access network ( 26 ) and a second radio access network ( 28 ). ADE ( 21 ) is attached to the first radio access network ( 26 ) and UE ( 21 ) can send and receive data to and from the network ( 26 ). The system ( 10 ) is operable to provide preference data ( 50 ) from the first radio access network ( 26 ) to the UE representing radio related parameters ( 51 ). The system ( 10 ) can determine the presence of an access network discovery and selection function (ANDSF) of the UE ( 21 ), and evaluate, at the UE, including using ANDSF if present, the preference data ( 50 ) in order to determine if a data flow can be offloaded to the second radio access network ( 28 ). On the basis of the evaluation, the system can offload a data flow of the UE from the first radio access network ( 26 ). The data flow can be offloaded to the second radio access network. 
         [0060]    The present inventions can be embodied in other specific apparatus and/or methods. The described embodiments are to be considered in all respects as illustrative and not restrictive. In particular, the scope of the invention is indicated by the appended claims rather than by the description and figures herein. All changes that come within the meaning and range of equivalency of the claims are to be embraced within their scope.