Abstract:
The present invention refers to a method for managing a network access user policy (UOP) associated to with a user equipment (UE 1 ) for offloading data traffic, using Access Network Discovery and Selection Function (ANDSF), wherein one or more Wi-Fi access points are available for the UE 1  and the UE 1  is in communication with an server through a mobile communications network.

Description:
CROSS REFERENCE TO RELATED APPLICATION 
       [0001]    This application claims priority under 37 U.S.C. §119 to European Patent Office Application No. 13382559.6-1855, filed Dec. 27, 2013, the disclosure of which is incorporated herein by reference. 
       STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT 
       [0002]    Not applicable. 
       SEQUENCE LISTING, TABLE OR COMPUTER PROGRAM ON COMPACT DISC 
       [0003]    Not applicable. 
       TECHNICAL FIELD OF THE INVENTION 
       [0004]    The present invention generally relates to the management of access networks and more specifically to the access to Wi-Fi networks for offloading data traffic according to-user owned policies in an access network discovery and selection function environment. 
       BACKGROUND OF THE INVENTION 
       [0005]    Nowadays, increasingly complex and all-pervasive, mobile networks are dominated by data flows. The recent explosion in data and signalling traffic is leading to the impression that the classic 3 rd  Generation Partnership Project (3GPP) mobile network architecture cannot cope with this traffic surge, fostering the emerging concept of “offloading” low priority data traffic to other radio accesses (i.e. Wi-Fi, Wi-Max) than pure 3GPP, so both voice and data premium services can perform optimally, avoiding congestion of scarce resources. Consequently, Network Operators are deploying small Cells and Wi-Fi Access Points (AP) to facilitate the implementation of this concept. This equipment deployment is complemented by Network Operators with a number of already existing mechanisms and protocols used to perform Wi-Fi offloading. 
         [0006]    Most mobile terminals (User Equipment, UE) are endowed with the capability of connecting to standard Wi-Fi APs, as well as selecting which one to use among the available choices, based on pre-set or user-defined preferences stored on the device. In order to offer Wi-Fi access as an integral part of its mobile solutions, a Network Operator needs to be able to install its own access/selection policies in the UE, and dynamically adapt them to environmental changes. To implement a solution to this problem, 3GPP developed the Access Network Discovery &amp; Selection Function (ANDSF) standard suite (basically the technical specifications TS 23.402, TS 24.302 and TS 24.312). 
         [0007]    The ANDSF procedure supplies a UE with information about available access networks, recognised as such by a Network Operator, which provide connectivity in a certain geographical area, as well as validity conditions and priority rules to be applied when selecting between them. ANDSF is basically built around two basic entities shown in  FIG. 1 : an ANDSF server ( 1 ), located in the Operator Network, which stores the different policies regarding radio access (3GPP, Wi-Fi, Wi-Max); and an ANDSF client installed in the UE ( 2 ) that retrieves and applies the ANDSF policies, decides which network access would be best suited in each circumstance and sends notice to the ANDSF server when an environment change takes place. 
         [0008]    The connection between ANDSF client and server will be opened through any radio access available ( 3 ) at the moment, either 3GPP or non 3GPP, and in this last case, either if it trusted (known and managed by the Network Operator) or untrusted (neither known nor managed by the Network Operator). 
         [0009]    By using ANDSF policy information, the UE can decide if, how and to what network access it should hand over part or all of its incoming/outgoing traffic. This decision process will be ruled by different criteria like for example availability and validity of network access, according to, for instance, location constrains or time/date ranges. 
         [0010]    In order to apply the right set of policies for each user, the ANDSF server must obtain information about the UE&#39;s identity. This identity is not sent directly by the UE, but obtained from a third entity. The basic underlying concept is that prior to any dialogue between the UE and the ANDSF server, both must authenticate to each other in order to avoid impersonation security failures. 
         [0011]    Prior art cover different works based on ANSDF, for example the patent application US20120122422 A1, “ANDSF, Node Distributing Closed Subscriber Group (CSG) Information” relates to a method in an ANDSF node for distributing close subscriber group information (i.e. available only to a restricted set of subscribers). Or the patent application WO2013029672 “Optimizing ANDSF Information Provisioning For Multiple-Radio Terminals”, which is also based on the ANDSF standard and it relates to a new network device within a communication network for provisioning access network information to an UE. Another solution from the prior art (WO2013029672) proposes a system for generating access network discovery information, ANDI, for transmission to a User Equipment, UE, of a network subscriber by an ANDSF. The document “ANDSF Provisioning” (US 2013/0165,131) discloses a provisioning UE in communication with an ANDSF server through an access network includes a network interface unit of the Provisioning User Equipment (PUE) from which a registration request is sent to the ANDSF server through the access network and which receives a successful authentication result and a set of configuration instructions from the ANDSF server. The document US2013754648 “Method and Apparatus for selecting wireless access using application identification information in wireless communication system” defines a method based on ANDSF so that a terminal can find an alternate radio access in case of primary access breakdown/downtime. 
         [0012]    Nowadays, different competitors are working in products related to the ANDSF standard with a marked tendency on how to make aware the ANDSF server of the policies/configuration established by other existing network elements. One of the new features is the inclusion of a policy manager engine to allow flexible prioritization beyond standard, like the solution “In-touch Dynamics Offload” from the company “Greenpacket” or integrations with standard control elements in the Network Operator&#39;s side Interdigital “SmartANDSF”, which as an additional feature includes specific triggers on the UE to initiate the discovery and selection function transparently, followed by a user transparent, zero click, authentication and login process. 
         [0013]    It has to be mentioned the work in integrated environments with other entities related to management and policies enforcement inside the operator network, as offered by main equipment manufacturers like Ericsson, Nokia or Tekelec. They include Wi-Fi Gateways to manage Wi-Fi access points from inside the Core Operator Network and ANDSF server integrated into the network elements for access control (AAA server or HSS) and policy definition (PCRF). 
         [0014]    As defined in 3GPP, the ANDSF standard defines a mechanism for instructing a UE about when, how and in which order, the UE can trigger an offloading process to an available network access. However, it also displays several important drawbacks. ANDSF is a solid first step for addressing the offload of 3GPP mobile traffic to Wi-Fi networks by means of propagating carrier policies to UEs, but it currently stops short of expectation due to ANDSF only allowing “static policies” and not addressing dynamic/real-time policies like those a PCRF server can provide. 
         [0015]    An ANDSF server uses the Trust and non-Trust concept but only stores and manages offloading policies referring to trusted Wi-Fis from the Network Operator&#39;s point of view. Thus, a user cannot define a personal set of policies or include as a network access choice the user&#39;s own trusted Wi-Fi APs (home/corporate Wifi or similar). Additionally, there are not any means of making the WiFi APs a user owns or knows appear in other users&#39; ANDSF policies or inviting them to connect through them, even as guests. 
         [0016]    An ANDSF server is defined as an isolated element, without interfaces to other Network Elements. This makes it difficult for a network operator to apply specific policies per user according to user profiles (no connection to AAA/HSS or PCRFs) especially in response to changes in network conditions (most vendor solutions, as explained above, intend to address this problem. Besides, ANDSF policies are actually advisory, so a user can easily override them and revert to factory defaults/user preferences. 
         [0017]    The ANDSF standard does not consider the management of the required credentials to connect to the Wi-Fi AP while offloading, relying instead on pre-stored credential sets in the UE instead (e.g., EAP). Since this information must be known beforehand, it can turn the offloading procedure into a cumbersome task if the user wanders outside of its normal circuits or simply does not remember the credentials. 
         [0018]    The end user&#39;s involvement in ANDSF policy definition and management arises as one of the most important problems related to this technology. Basically ANDSF specifies a method to indicate to the user which reliable Wi-Fi access points (APs), from the Network Operator&#39;s point of view, are available throughout a certain area and when, how and why traffic should be offloaded to those Wi-Fi AP. However, it does not specify any procedure for involving the end user, apart from the final decision on allowing the offloading or not. Users are neither allowed to define their own policies based on reliable Wi-Fi Aps from the user&#39;s point of view, like Wi-Fi access points at home or corporate environments. Normally, average users will spend most of their waking hours in those two types of locations, whose network accesses may be unknown for the Network Operator, and where the offloading process would be rather useful, because they are normally areas of low 3GPP coverage or prone to congestion. Therefore, ensuring user involvement seems to be crucial for ANDSF&#39;s success because if an improvement is not perceived in user experience, the user could simply disable the ANDSF offloading capability, jeopardising the resolution of congestion problems that are the main point of this standard. 
         [0019]    In conclusion, none of the solutions from the prior art allow defining any sort of end user owned policies, which surely would increase ANDSF&#39;s user experience and satisfaction. Therefore, a good deal of enhancements to the ANDSF entities and protocols are required to address the possibility of a creating, managing and controlling personal offloading policies, which would entail an increase in user satisfaction and perceived Quality of Experience (QoE). 
       SUMMARY OF THE INVENTION 
       [0020]    The present invention solves the aforementioned problems fostering user involvement by allowing definition of personal offloading policies based on the network elements the user consider reliable, for example the Wi-Fi AP at home or those in corporate environments. Therefore, it is presented a method for managing, by a user, a network access user policy (UOP) associated with a user equipment (UE 1 ) for offloading data traffic, using Access Network Discovery and Selection Function (ANDSF), wherein one or more Wi-Fi access points are available for the UE 1 , being the UE 1  in communication with a server through a mobile communications network. The method comprises the steps of:
       a) sending, from the UE 1  to the server, through the mobile communications network, a first message containing an identifier of an available Wi-Fi access point;   b) the server receiving the first message and sending a second message to the UE 1  requiring a trial offloading through the Wi-Fi access point;   c) if the trial offloading is successful, the UE 1  sending, using the Wi-Fi access point, a third message containing certain parameters to the server for setting a UOP;   d) the server setting a UOP for offloading traffic according to the certain parameters;   e) the server storing the UOP in a UOP repository;   f) the server sending a fourth message containing the UOP to the UE 1 ; and   g) the user of UE 1  managing the UOP taking at least one of the following actions: editing the UOP, applying the UOP, distributing the UOP or deleting the UOP.       
 
         [0028]    Additionally, according to one particular embodiment, the step of editing the UOP may further comprise the steps of:
       sending a request message, from the UE 1  to the server, containing a request to edit the UOP;   the server receiving the edition message and sending to the UE 1  another message containing the UOP;   editing one or more parameters of the UOP in the UE 1 ;   sending an edition message containing the edited UOP from the UE 1  to the server;   the server storing the edited UOP in the UOP repository; and   the server sending an updating message containing the edited UOP to the UE 1 .       
 
         [0035]    In one embodiment of the invention, applying the UOP through a determined Wi-Fi access point, may further comprise:
       the UE 1  sending a request message to the server containing an identifier of the determined Wi-Fi access point;   searching, by the server, in the UOP repository for a UOP associated to the identifier;   if the UOP is found, sending a connection message from the server to the       
 
         [0039]    UE 1  containing at least the UOP; and
       the UE 1  connecting to the Wi-Fi access point and offloading content according to the UOP.       
 
         [0041]    Distributing the UOP to a second user equipment (UE 2 ), according to one particular embodiment of the invention, may further comprise:
       sending a first invitation message, from the UE 1  to the server, containing an identifier of the UE 2  and indicating the UOP to be shared;   the server sending a second invitation message to the UE 2  for the UOP shared by UE 1 ;   the UE 2  accepting the invitation for sharing the UOP;   adding the UE 2  to the UOP as an authorized user;   the server storing the UOP in the UOP repository; and   the server sending an updating message containing the UOP to the UE 2 .       
 
         [0048]    Optionally, the present invention may comprise an authorization step wherein the server sends to a network management element to check whether it is allowed/registered/authorized an authorization message containing at least one of: the identifier of the Wi-Fi access point; or an identifier of the user. 
         [0049]    Some embodiments of the invention, wherein a Wi-Fi access point requires certain credentials, further comprises the UE 1  providing said credentials as a parameter to include in the associated UOP. 
         [0050]    A UOP may comprise, according to one embodiment of the invention, information from the following list: list of users allowed to access and manage the UOP, credentials to be used for accessing the UOP, type of operation allowed for each user, identifier of a WI-Fi access point, credentials required to connect to the WI-Fi access point, geographical location and time/date ranges defining a validity for the UOP. 
         [0051]    One embodiment of the invention relates to the UE 1  decision, according to the UOP, about how and to what network access should hand over part or all of incoming/outgoing traffic. This decision process may be ruled by different criteria from the following list:
       Availability and validity of the network access, according, for instance, to location constrains or time/date ranges.   Priority of the network access in a rule list.   If handover has to be carried out for all the traffic or only for specific flows.       
 
         [0055]    In this case, the involved flows have to be characterized along with the list of permitted network access for that flow, which may or may not match the network access list for a different one.
       If handover has to be carried out for all Access Point Names (APNs) or only for specific ones among those concurrently used by the UE 1 .   Internal conditions/events in the UE 1 .   Characteristics of the network access, e.g. connection data, connection technology.       
 
         [0059]    The identifier used for the Wi-Fi access points in the UOP may be the SSID, the HESSID or a BSSID. 
         [0060]    A Wi-Fi access point may support more than one identifier. According to some particular embodiments, the invention may further comprise the step of setting one UOP for each identifier of the Wi-Fi access point with one or more parameters from the following list: desired QoS, bandwidth ceiling, available operator services, and network visibility. 
         [0061]    A second aspect of the invention refers to a system for managing, by a user, a network access user policy (UOP) associated with a user equipment (UE 1 ) for offloading data traffic, using Access Network Discovery and Selection Function (ANDSF), wherein one or more Wi-Fi access points are available for the UE 1 , being the UE 1  in communication with a server through a mobile communications network. The system comprises:
       the UE 1  configured for: sending, through the mobile communications network, messages containing identifiers of available Wi-Fi access points; sending, using the Wi-Fi access point, messages containing certain parameters to the server for managing UOPs; and taking at least one of the following actions: applying the UOP, editing the UOP, deleting the UOP, or distributing the UOP;   a server configured for: receiving messages from the UE 1  and sending messages to the UE 1  requiring a trial offloading through Wi-Fi access points; applying, editing, deleting and distributing UOPs for offloading traffic according to the certain parameters; and sending messages, containing UOPs, to the UE 1 ; and   an UOP repository, in communication with the server, for storing UOPs.       
 
         [0065]    According to one embodiment of the invention, the UE 1  may be further configured for sending a request message to the server, containing a request to edit the UOP; 
         [0066]    editing one or more parameters of the UOP; and sending an edition message containing the edited UOP to the server. The server may be further configured for receiving edition messages and sending to the UE 1  messages containing UOPs and sending updating messages containing edited UOPs to the UE 1 . 
         [0067]    The system of the invention, according to some particular embodiments, may comprise:
       the UE 1  further configured for: sending a request message to the server containing an identifier of the determined Wi-Fi access point; and connecting to the Wi-Fi access point for offloading content through the Wi-Fi access point according to the UOP; and   the server further configured for: searching in the UOP repository for a UOP associated to the identifier; and sending connection messages to the UE 1  containing at least the UOP.       
 
         [0070]    The system of the invention, according to some particular embodiments wherein a second user equipment (UE 2 ) is comprised, may be further configured for accepting invitations for sharing UOPs and wherein:
       the UE 1  is further configured for sending invitation messages to the server, containing an identifier of the UE 2  and indicating the UOP to be shared; and   the server is further configured for: sending invitation messages to the UE 2  for UOPs shared by UE 1 ; adding the UE 2  to the UOP as an authorized user; and sending updating messages containing UOPs to the UE 2 .       
 
         [0073]    The system of the invention, according to some particular embodiments, wherein the server is further configured for sending to a core network an authorization message containing at least one of the identifier of the Wi-Fi access point or an identifier of the user equipment and may further comprise an authorization server in the core network in communication with the server and configured for checking whether the Wi-Fi access point and the user equipment are allowed/registered/authorized. 
         [0074]    In one embodiment of the invention the server is an ANDSF server. 
         [0075]    A last aspect of the invention refers to a computer program product comprising computer program code adapted to perform the method of the invention when said program code is executed on a computer, a digital signal processor, a field-programmable gate array, an application-specific integrated circuit, a micro-processor, a micro-controller, or any other form of programmable hardware. 
         [0076]    By adding the system and method proposed by the present invention, the users are involved in the ANDSF policy definition and can specify their own settings, even including as a valid Wi-Fi AP those they trust regardless of their being known or not by the Network Operator. The process is thus friendlier, increasing flexibility and end user&#39;s confidence. 
         [0077]    The following advantages can be highlighted: 
       From a User&#39;s Point of View, 
       [0000]    
       
         
           
             Allow the creation of UOP for user&#39;s trusted Wi-Fi AP (i.e home Wi-fi, corporate environment . . . ). 
             Wi-Fi AP credentials are not stored in the UE but in the cloud, enabling accessing to that Wi-Fi AP from other devices, without the user having to configure them. 
             User control of access settings (Wi-Fi ID, credential, validity conditions), with network operator in charge of access validation and cloud storage. 
             Allow definition of user groups for granting access to home Wi-Fi environments. 
             Allow definition of user lists for globally and uniquely managing guest access to multiuser Wi-Fi environments (corporate or controlled area). 
             If Wi-Fi AP is endowed with multiple SSID capabilities, the owner can open one of them for external sharing (club WIFI, Phonera . . . ) and distribute credentials/configurations to friends (home Wi-Fi) or guests users (in corporate environments). 
             The transfer of connection parameters and security credentials is carried out by means of the ANDSF Standard (OMA). 
           
         
       
     
       From a Network Operator&#39;s Point of View: 
       [0000]    
       
         
           
             Increases the number of offloading network possibilities, enabling the inclusion of Wi-Fi APs not known to the Network Operator. 
           
         
       
     
         [0086]    The offloading will thus be facilitated in home and corporate environments with reduced 3GPP coverage and/or congestion risk, and usually served by Wi-Fi APs not controlled by the operator, thus improving network flexibility for a user&#39;s optimal offloading experience.
       Allow QoS control by making Network Operator Gateways aware of previously unknown Wi-Fi APs.   Facilitates Operator Services&#39; discovery and access.   Improve user experience and loyalty (private policies are stored in the Network Operator Storage).   Integrated with ANDSF standard.       
 
     
    
     
       DESCRIPTION OF THE DRAWINGS 
         [0091]    To complete the description that is being made and with the object of assisting in a better understanding of the characteristics of the invention, in accordance with a preferred example of a practical embodiment thereof, accompanying said description as an integral part thereof, is a set of drawings wherein, by way of illustration and not restrictively, the following has been represented: 
           [0092]    FIG.  1 .—shows a basic scheme of an ANDSF architecture. 
           [0093]    FIG.  2 .—shows a policy setting and distribution in an ANDSF environment according to one embodiment of the invention. 
           [0094]    FIG.  3 .—shows a policy creation flow according to one embodiment of the invention. 
           [0095]    FIG.  4 .—shows a policy application flow according to one embodiment of the invention. 
           [0096]    FIG.  5 .—shows a policy editing flow according to one embodiment of the invention. 
           [0097]    FIG.  6 .—shows a policy sharing flow according to one embodiment of the invention. 
           [0098]    FIG.  7 .—shows a diagram of one embodiment of the invention sharing surplus bandwidth. 
           [0099]    FIG.  8 .—shows a particular embodiment of the invention using ANDSF as Wi-Fi AP auto-configuration tool in a service environment. 
       
    
    
     DETAILED DESCRIPTION OF THE INVENTION 
       [0100]    The invention describes a process for, in general terms, setting, verifying and distributing User Owned Policies (UOP) in an ANDSF environment. 
         [0101]      FIG. 2  illustrates one embodiment of the invention that comprises a UOP repository ( 21 ) deployed within (or remotely according to other embodiments), an ANDSF server ( 1 ), to store a user&#39;s offloading policy entries, which dialogues with an UE ( 2 ). Those elements are enhanced by adding an UOP Client ( 22 ) to the UE, an UOP server ( 23 ) to the ANDSF server, and an external UOP repository ( 21 ) for UOP storage. 
         [0102]    Each UOP entry may consist of: a) List of users allowed access to the UOP entry plus allowed operations (i.e. lookup total control) along with (optionally) their UOP management credentials; b) the identifier of Access Network, usually a Wi-Fi AP, which will be used as a main example in the following explanation; c) credentials required for connection to the Wi-Fi AP; d) geographical location and time/date validity ranges for the UOP entry. 
         [0103]    In one embodiment of the invention, the ANDSF server also includes an UOP server ( 23 ), able to connect to the UOP repository, add new UOP entries, retrieve those belonging to/authorised for a specific user, or edit/delete existing ones. This UOP Server is also able to connect Network Management Elements (e.g. an AAA/HSS ( 24 ), i.e. Authentication, Authorisation and Accounting server (AAA) or a Home Subscriber Server (HSS) to manage the users&#39; subscription and its right access to network resources and services) to authenticate and validate both users and Wi-Fi AP if necessary. 
         [0104]      FIG. 2  also includes a UOP client ( 31 ) as an enhancement of the standard ANDSF client to apply the credentials needed to the UOP Server and retrieve the UOP entries associated with this user, as well as triggering the Offload if the validity conditions are met. The UOP entries are retrieved by using the S14 interface defined in the ASDNF standard. Additionally, the S14 interface is also extended in order to verify the reachability of the Wi-Fi APs included in the UOP entries and not known yet by ANDSF Server. Lastly, the standard communication method used by the S14 interface is accordingly extended to incorporate the pieces of information required by UOP entries. 
         [0105]    The communication between the UOP Client and the UOP server builds upon the ANDSF standard, so the security levels and reliability of communication assured by this protocol are maintained. 
         [0106]    All location information can be expressed as geographical coordinates, cellular cell ID or area ID, or WLAN location (HESSID, SSID or BSSID). 
         [0107]    In the cases where a user or a Wi-Fi AP need to be validated, the present invention provides embodiments with an interface from the UOP server to Authorisation, Authentication and Accounting (AAA) elements deployed in the core network of the Network Operator. 
         [0108]    Over this architecture, five different main command flows are required for the entire process of one embodiment of the invention:
       Initialize flow. This flow associates the UE and the ANDSF server trough a 3GPP Network Access, validates user&#39;s credentials, retrieves the user&#39;s ANDSF policies and grants access to the UOP repository.   UOP creation. In this flow a new Wi-Fi AP is included in the UOP repository. It requires that ANDSF is enabled in the UE, an open link to the ANDSF server through a 3GPP Network Access and the new Wi-Fi AP to be in UE&#39;s range.   UOP Edition. It allows editing the information stored in a UOP entry. It requires that ANDSF is enabled in the UE and an open link to the ANDSF server through a 3GPP Network Access.   UOP application. The UOP is transferred to the UE and there applied, likely triggering an offload. It requires that ANDSF is enabled in the UE, an open link to the ANDSF server through a 3GPP Network Access and the Wi-Fi AP to be in UE&#39;s range.   UOP Sharing. The UOP is shared with another user/UE. It requires ANDF enabled in both UEs, open links from them to the ANDSF server through a 3GPP Network Access and the Wi-Fi AP to be in at least the invited UE&#39;s Range.       
 
         [0114]    In the initialized flow, the UE has to follow the same process to identify and validate the access used by an ANDSF standard client (TLS session or HTTPS connection with login/password access). From the server point of view, the repository must be looked up in order to include the user&#39;s OUP (if existing) into the initial ANDSF policy configuration to be sent to the UOP client. 
         [0115]      FIG. 3  relates, according to one embodiment of the invention, to the flow for creating a new UOP entry for a user trusted Wi-Fi AP into the UOP repository and its main process. It starts with an UE ( 2 ) which has successfully completed an initialize process, so a communication link to the ANDSF server ( 1 ) via 3GPP network access is enabled. For the UOP creation and validation, it also requires the Wi-Fi AP ( 31 ) to be in UE&#39;s range, so an offloading operation could be completed. After the user has gathered the data related to the UOP, namely an identifier for the Wi-Fi AP (AP ID), UE location and Wi-Fi AP&#39;s credentials, if necessary, the UOP creation process starts by the UE sending ( 33 ) the new AP ID (only the AP ID) to the ANDSF server. The ANDSF checks ( 34 ) with the AAS/HSS ( 24 ) if the proposed Wi-Fi AP/user are allowed and/or they are associated somehow (to the Network Operator&#39;s knowledge). 
         [0116]    This authentication process is an optional process, but for a global Network Operator, it can be useful to check first if the Wi-Fi AP is a registered/authorised/banned Wi-Fi AP connected to their fixed core network. Conversely, the ANDSF can incorporate an internal repository with information about trusted user/authorised Wi-Fi APs or not carry out any authentication (open Wi-Fi AP defined). 
         [0117]    If the authentication check is ok ( 35 ), the ANDSF server builds a new temporary ANDSF policy to force an offloading through the suggested Wi-Fi AP with top priority and a short validity time, basically a timeout, and sends it to the UE ( 36 ), triggering the offloading to the Wi-Fi AP. 
         [0118]    If the UE performs the offloading and the connection to the Wi-Fi AP is successful ( 37 ), the link with the ANDSF server is restarted but now through the Wi Fi AP. After having opened the new connection, the UE sends ( 38 )( 39 ) the remaining pieces of data required for completing the UOP creation and storage: Wifi AP&#39;s user credentials, Wi-Fi AP/UE location, time/hour validity ranges. Then, the ANDSF server inserts ( 40 ) this information into the UOP repository as a permanent UOP entry, the UOP entry is sent back ( 41 ) to the ANDSF server, which refreshes ( 42 ) the UE, through the Wi-Fi gateway ( 32 ), with the updated policies, including the validity data specified in the UOP entry, but not the credentials, thus removing the temporary timeout. 
         [0119]    In the case the timeout expired ( 43 ) without the UE attempting the offloading (UE-ANDSF link not closed) or failed at it (UE-ANDSF link is not reopened) the new Wi-Fi AP and any associated UOP is discarded. If the link from the ANDSF to the UE through the 3GPP Network Access is still open a reject is sent (44) to force the UE to discard the temporary policies. 
         [0120]    According to the ANDSF standard, anytime a UE connects to an ANDSF server, the server sends all the policies associated with the user subscription and the UE location. In order to cover either the transfer of credentials that would allow “seamless” connection with the proposed Wi-Fi AP or the retrieval of UOP policies, the flow is enhanced to allocate room for these pieces of information.  FIG. 4  illustrates the process of one embodiment of the invention, where the flow starts when a UE ( 2 ) has a UE-ANDSF server ( 1 ) link open through a 3GPP network access, a Wi-Fi AP ( 31 ) defined in the user&#39;s UOPs is in UE&#39;s range and the validity conditions (time/location) for the Wi-Fi AP in the UOP are fulfilled. The UE requests ( 45 ) the ANDSF server to lookup ( 46 ) the Wi-Fi AP in the UOP repository ( 21 ) and, if found ( 47 ) there, to send ( 48 ) back both the “connection trigger” (this access is placed at the top of the priority list) and the required access credentials, as well as any update in the UOP information since its creation. The UE then applies the UOP policy, performing ( 49 ) an offloading to the W-Fi AP. 
         [0121]    When UOP validity constraints for that Wi-Fi AP are no longer valid, the UE rolls back ( 50 ) to 3GPP Network Access. 
         [0122]      FIG. 5  depicts the process to edit a UOP according to one embodiment of the invention. If a connection is open between the UE ( 2 ) and the ANDSF server ( 1 ), the flow process to make edits to a UOP stored in the UOP Repository ( 21 ) starts with a request ( 51 ) to the ANDSF server to edit the UOP Entry that stores a Wi-Fi AP ( 31 ) ID. It also requires the UE in the Wi-Fi AP&#39;s range to check the validity of the changes, i.e. the credentials to be used in the Wi-Fi AP connection. 
         [0123]    After the ANDSF server checks ( 52 )( 53 ) with the AAA/HSS server ( 24 ) that the user and the Wi-Fi AP are both allowed, it sends ( 54 ) a message to the UE with the contents of the associated UOP entry. 
         [0124]    The UE collects ( 55 ) the changes in UOP entry and sends ( 56 ) them to the UOP repository through the connection offloaded through the Wi-Fi AP. The ANDSF server validates and saves ( 57 ) the new UOP in the UOP repository and updates ( 58 ) the policies in UE. 
         [0125]    If there were any errors during the process, the ANDSF server would send an error message. 
         [0126]      FIG. 6  depicts the case of policy sharing. Two UEs are now involved, one with access permissions to an UOP entry in the UOP repository and a second one the first UE wishes to share with the original UOP. 
         [0127]    The process is split in two main flows: one for the UOP owner (UE 1  ( 2 )) and a second one for the UE (UE 2  ( 60 )) invited to share the policy. 
         [0128]    UE 1  must be initially linked to the ANDSF server ( 1 ) and initiate ( 61 ) the process for granting UOP lookup rights over the entry to UE 2 . The ANDSF server should validate ( 62 ) ( 63 ) in the UOP repository ( 21 ) that the UE 1  owns that entry and check ( 64 )( 65 ) that both UE 2  and the Wi-Fi AP ( 31 ) are registered/authorised in the core AAA/HSS. If everything is Ok, the ANDSF server sends ( 66 ) to UE 1  a “policy invite OK”, reporting that the invitation process is about to be launched. If any part of this process fails, a user rejected message is sent to UE 1 . 
         [0129]    After a successful UE 2  validation in the Core AAA/HSS, the ANDSF server sends ( 67 ) to UE 2  a message “policy invite” for the UOP entry shared by UE 1 . If UE 2  accepts ( 68 ) the invitation, the new user is added (69)( 70 ) to UE 1 &#39;s UOP user list as a user with lookup rights for this UOP and a policy update is sent (70) to UE 2 . When the validity conditions established in the UOP are met (location or time policy) the UE can request to ANDSF server for the Wi-Fi AP access credentials in order to perform the offloading ( 71 ). 
         [0130]    One particular embodiment of the invention covers the case of adding user&#39;s home Wi-Fi AP to ANDSF policies repository. According to this embodiment, the user adds a UOP entry for the user&#39;s home Wi-Fi AP and defines which other users (e.g. family members, friends) can look up and retrieve the UOP and offload their traffic to the home Wi-Fi AP. In addition, a Network Operator can check if this Wi-Fi AP is managed by their core system, so improved features can be made available on it, like access to subscriber services offered by this Network Operator. 
         [0131]    In order to validate both the user and the Wi-Fi AP, the ANDSF node needs to verify that a valid connection between the Wi-Fi AP and the Core network exists, by means of a link to the ANDSF server opened via the Wi-Fi AP, and also to check user authentication and authorization with the operator systems, if necessary. 
         [0132]    The UOP information can be refined by adding location information (so the offloading is only carried out when trusted UEs are really in the Wi-Fi AP&#39;s vicinity) and time constraints (so it is only valid when the user is expected to be at home). Assigning top priority to this Wi-Fi AP will force an automatic offload once the user reaches home, improving its QoE (greater Bandwidth) and helping reduce the load for the affected 3GPP cells in the area 
         [0133]    By being aware of the Wi-Fi AP&#39;s connection to Core Network, the operator could apply specific user&#39;s policies on the Wi-Fi AP (i.e. subscriber services) and specific tariff/charging strategies. 
         [0134]    Another advantage ensuing from this embodiment is the possibility to add new users as guests without need of explicitly telling them which Wi-Fi AP ID is or what credentials are needed, since these pieces of information are already stored in the cloud (in the UOP repository of the ANDSF server) 
         [0135]      FIG. 7  represents a particular embodiment of using Multi SSID capabilities to share surplus bandwidth. 
         [0136]    According to this embodiment, a private Wi-Fi AP can be integrated into a group of shared public Wi-Fis, in case the Wi-Fi AP supports multiple SSID definitions. This embodiment also makes use of a connection from the Wi-Fi AP to a Network Operator&#39;s Wi-Fi Gateway which is capable of defining and scheduling specific features for each Wi-Fi node. 
         [0137]    The Wi-Fi AP&#39;s owner has to configure it with 2 different identifiers (for example PSSID 1  and PSSID 2 ) and stores both Wi-Fi IDs into an ANDSF server as separate UOPs. In this case, by resorting to the Wi-Fi Gateway in the Core Network, separate network policies can be applied for each Wi-Fi ID, like desired QoS, Bandwidth ceiling, available operator services or network visibility. In  FIG. 8 , PSSID 2  is the main access with bigger bandwidth and access privileges while PSSID 1  is the surplus part with minimum bandwidth just for sharing purposes and without access to subscriber services and advanced network visibility. 
         [0138]    To include the Wi-Fi AP into a shared environment, the owner only needs to define a UOP entry with the SSID and generic user/password to be used by the intended user group. So when a group member with ANDSF enabled in the UE is in the vicinity of the WiFi AP, it will receive all the required connection information (for example, the SSID and credentials) and will automatically proceed to offload to the Wi-Fi AP. 
         [0139]    In corporate environments, this embodiment has clear advantages, since the Wi-Fi AP manager can easily define guest invitations to a SSID with lower priority and fewer privileges than the main trunk for corporate access, so visitors can automatically use the offloading procedure inside the corporate coverage area for connecting to the guest Wi-Fi. The system Wi-Fi administrator, as UOP entry owner of those policies can easily invite visitors to the guest Wi-Fi, following the procedures defined in this invention. 
         [0140]      FIG. 8  represents a particular embodiment of the invention using ANDSF as Wi-Fi AP auto-configuration tool in a service environment. 
         [0141]    According to this embodiment, where the normal procedure for defining a UOP entry involves the validation of the user ( 2 ) and the Wi-Fi AP ( 31 ) before the Network Operator, the ANDSF ( 1 ) alerts network elements ( 24 ) (e.g. HSS/PCRF) of a freshly installed Wi-Fi AP ( 31 ) existence and trigger an auto configuration process of that Wi-Fi AP, overriding the factory settings with operator settings according to the services subscribed/enabled for the Wi-Fi AP location. 
         [0142]    There is a basic advantage ensuing from this procedure: It does not require the intervention of the network support team, either remotely or in the user&#39;s home. 
         [0143]    Simply the validations carried out by the ANDSF are enough to find out the user&#39;s subscription details and apply them as required. 
         [0144]    This document often uses the terms “user” and “user equipment” with no distinction, because the user equipment (UE) is understood as any device used directly by the user to communicate. It can be a mobile phone, smartphone, a laptop computer equipped with a mobile broadband adapter, or any other similar device.