Method for access selection

[0001] This application claims the benefit of Provisional Application No. 60/466,422, filed 30 Apr. 2003. The entire contents of these applications are incorporated herein by reference.

[0002] The present disclosure generally relates to multi-access communication systems based on the Internet Protocol (IP) and in particular to methods and a apparatuses for access selection in such systems.

[0003] Today, IP-based network services are often offered over several types of network technologies, such as General Packet Radio Service (GPRS), Wireless Local Area Network (WLAN), Wideband Code Division Multiple Access (WCDMA), xDSL, cable modem, and Ethernet. Many mobile user devices are provided with multiple access interfaces to be able to make the most of this situation. Multi-access communication systems are generally more flexible than single-access networks but they also introduces an additional degree of complexity and involves a number of new requirements, choices and considerations.

[0004] General aspects of multi-access networks are addressed by the Always Best Connected (ABC) concept [1], [2], which envisions a communication environment where the user is always connected over the best available access network and device. The overall ABC concept can be seen as a framework of requirements:

• • [0005] Always—at any point in time, the user shall obtain the best communication experience.
  • [0006] Best—refers to the user experience. The best experience might, for instance, refer to the cheapest access network, the best application performance, the highest bandwidth, or the best device in combination with access and applications. What is best thus depends on user perception and in technical terms also on a combination of network characteristics, cost, device capabilities, application requirements, operator policies etc.
  • [0007] Connected—it is important to consider both what/whom the user is connected to, for example an application server, a corporate network, the Internet, another person, or another machine, and what/whom the user connected through, such as devices, a personal area network (PAN), access networks, backbones, the Internet etc. All of these entities and networks may affect the user experience.

[0008] Designing solutions for scenarios like ABC includes consideration of different business scenarios, different architecture options, and different technical solutions. Hereby, important areas are: (i) subscription handling and infrastructures for authentication/authorization; (ii) service availability; (iii) service adaptation across multiple different accesses and different devices; (iv) mobility management; (v) distributed terminals/devices—PANs; (vi) access availability; and (vii) how to choose access, including how to define “best” [1]. This document primarily addresses aspects of the last area (vii) of access choice/selection.

[0009] Solutions for access selection in IP-based multi-access communication systems in the prior art often involve an active decision as for which access network to use by the end user effected through the graphical user interface (GUI) of his/her device. Alternatively, or in addition thereto, the multi-access terminal comprises a default priority list that is compared with currently available accesses

[0010] The International Patent Application WO 01/35585 A1 [3] proposes a mechanism for access-selection based on individual user preferences. The end device identifies available access networks and uses an indirect interface, such as a Bluetooth radio interface, to determine their respective access capability (cost of access, available bandwidth, etc.). The determined access capability is compared to a preferred access capability of the end device/user, which is stored at the end device and can be updated by the user. After all available access networks have been checked a best access is selected. The end device may continue to look for new available access networks and reconsider its access decision during a connection.

[0011] The conventional access selection methods are typically associated with rather heavy demands on both the end user and on his/her user equipment. Moreover, for a proper access selection many factors have to be considered and it can often be difficult for the user/terminal to obtain all information needed as well as to analyze complex access situations.

[0012] Particularly demanding arc cases where the mobile multi-access terminal resides in a car or another vehicle. Such vehicle scenarios typically require fast access selections and handoffs in order to maintain optimal access and avoid lost calls/sessions due to changed access situations. An access selection mechanism capable of handling vehicle scenarios satisfactory would thus be very desirable.

[0013] Accordingly, there is a considerable need for an improved method for access selection in multi-access networks.

[0014] In an aspect of the disclosure, an improved method for access selection in IP-based multi-access networks. A specific object is to enable optimized access selection for end users in multi-access networks. Another object is to provide an access selection mechanism suitable for overall multi-access solutions like ABC mechanisms. Still another object is to provide an access selection mechanism suitable for vehicular scenarios.

[0015] Briefly, is proposed that the access selection be performed at the network side in order to connect a mobile terminal with multiple access possibilities to the best IP access network. The access network concept can in this context e.g. be based on technology, owner/operator or geography. The network-based access selection is achieved by an access wizard unit, communicating with a profile server, which provides a unified interface to a number of databases in the network. Via the profile server, the access wizard unit collects database information, such as access network properties, operator policies, operator/user prioritization criteria and allowed user subscription profiles based on which it determines a “best” access network. Preferably, the access selection at the access wizard unit is also based on terminal specific information, such as current terminal location and available access networks, received from an access wizard agent in the mobile terminal. A recommendation/indication of the best access is signaled from the access wizard unit to the access wizard agent, and then to an access manager in the terminal associated with means for connecting the best access network.

[0016] An example access selection method contributes to make it possible for users to always be connected to the best access network. The proposed solution enables well-founded access decisions, since many factors related to the user and terminal as well as to the access networks and operators can be considered. The network-based access selection also offers an overall perspective, through which network resources can be better used. Another advantage of the access selection of the invention is that it is capable of handling large data quantities and heavy computations.

[0017] In an embodiment, it is the access manager that performs the final decision as for which access network to use based on the recommendation from the access wizard unit, possibly together with user input and/or a priority list in the terminal. This can be useful e.g. in case the access network selected by the access wizard unit has changed or is down.

[0018] Besides the proposed mechanism for selecting the currently best access network for the terminal, mechanisms for predicting which access network will be best after a predetermined period of time as well as for suggesting an alternative route in case there are no appropriate access networks in the intended route are provided. These solutions are especially advantageous for multi-access terminals in vehicles.

[0019] In accordance with other advantageous embodiments, the access wizard unit assists the security infrastructure for achieving seamless mobility and that applications are adapted at network level (on the network side) through support from the profile server.

[0020] According to other aspects, a server device, a communication system and a mobile terminal with means for access selection are provided.

[0030] As mentioned in the background section, many communication systems of today comprise a plurality of access networks offering alternative access options for mobile terminals with the right capabilities. Such a multi-access communication system is schematically illustrated in FIG. 1. The illustrated communication system 100 comprises mobile terminals 110 with several access alternatives. The terminals 110 can use any of the multiple access networks (ANs) 120 to reach IP-based network services 130, which are offered by content providers 150 (with associated data sources 151) over the Internet 140 or another packet based network. Examples of network services include content distribution network services with content caching, multimedia messaging services (MMS), voice over IP services, etc.

[0031] The disclosed embodiments can be applied in connection with any mobile node/terminal 110 that has at least two access possibilities (also referred to as a multi-access terminal), such as two separate physical access network connections or one connection through which either of two separate access networks can be reached. The access network interfaces of the multi-access terminal can either provide direct external network access to the respective access network or network access via another device that belongs to the same PAN as the multi-access terminal. In the illustrated system 100, the multi-access terminals are represented by a laptop computer 110-1, cellular phones 110-2 and a personal digital assistant (PDA) 110-3.

[0032] The access networks 120 can be wireline or wireless and may for instance use a technology selected from the group of GPRS, WLAN, Ethernet, Bluetooth, Wireless Fidelity (WiFi), xDSL, CDMA, WCDMA, broadcasting, Digital Video Broadcasting (DVB) and cable modem. For the purpose of this document, two networks can e.g. be considered as separate access networks if they use separate access network technologies, such as a GPRS and a WLAN system and/or have different owners. The access network definitions can also be based on geography and/or IP address networks. The properties and characteristics of the access networks 120 may differ a lot in terms of features like capacity dynamics, cost and acceptable load levels.

[0033] An aspect of the disclosure focuses on how to select the best access network. Which access network that is best for the user in a particular situation depends on a number of factors, including:

• • [0034] available access networks and their capabilities (bandwidth, cost, QoS, operator, technology, current load, etc.)
  • [0035] requirements from applications
  • [0036] device capabilities
  • [0037] user preferences and/or subscription
  • [0038] network operator preferences

[0039] As described in the background section, access selection in IP networks according to the prior art is generally user-based, i.e. the user decides what access network to use e.g. through a GUI, and/or terminal-based, i.e. the terminal selects an access network e.g. based on a default priority list, which is checked against currently available accesses. Instead, a method and architecture for network-based access selection in IP-based multi-access communication systems is proposed. Network-based access selection indicates that an entity in the network collects information and suggests the terminal in which access is the best.

[0040] The network-based access selection offers mechanisms by means of which the above-mentioned and other factors can be weighed together into an appropriate access network decision. As will be evident from the following description, even very complex access situations can be handled and the network-based access selection can be combined with terminal/user-based access selection to achieve a very robust system.

[0041] The functional architecture of the proposed new mechanism for access selection in multi-access IP networks is illustrated in FIG. 2. The illustrated system 200 includes a mobile multi-access terminal /node 210 communicating with an Always Best Connected (ABC) service network 260 over an IP-based network 240, such as the Internet. The terminal 210 is equipped with a GUI 211 and associated with sensors 212 to provide terminal-specific information related to for example position and velocity. The main access selection functions are performed by an access selection unit (also referred to as access wizard unit)261 and a profile server 262 at the network side as well as an access agent (also referred to as access wizard agent) 213, an access manager 214 and link managers 215 at the terminal side.

[0042] The access wizard unit 261 is a server unit/function arranged at the network side and plays a key role in the network-based access selection. The access wizard agent 213 of the terminal 210 preferably signals information to the access wizard 261 about currently available access networks as well as current location, route and/or velocity of the terminal. The access wizard unit 261 then collects database information through the profile server 262, which provides a unified interface towards a number of databases 263. Based on the information from the profile server 262 and the access wizard agent 213, the access wizard unit 261 selects an access network (120 in FIG. 1) that is considered to be best for and thus is preferred to be used by the terminal 210. This information is signaled from the access wizard unit 261 to the access wizard agent 213. From there it is forwarded to the access manager 214, which executes the actions necessary in order to use the best access.

[0043] An advantage of the for network-based access selection is that the major data transfer occurs on the network side (between the access wizard unit and the profile server) and normally does not have to rely on narrowband wireless links. Thereby, large quantities of database information can be handled. The data/information provided to the access wizard unit via the profile server can for instance refer to specific access networks, user devices, end users and/or operators. It typically includes information about access network availability, operator policies, operator/user prioritization criteria, as well as allowed user subscription profiles.

[0044] Through the profile server 262, the network access selection offers a most efficient solution for handling database information. For an appropriate access selection, the access wizard unit generally needs various types of information that is typically provided in many different formats and languages. Such database information/profiles can be held in many different databases stored at different locations in the network. Before transmitting the respective pieces of database information to the access wizard unit, the profile server checks if they need to be adapted. If so, the profile server adjusts and/or converts the data such that it can be read by the access wizard unit.

[0045] The network-based access selection accomplished by the access wizard unit and the profile server is thus very advantageous. It provides for well-founded access decisions based on various factors related to e.g. the user, terminal, the access networks and operators, and is capable of handling large data quantities and heavy computations. Furthermore, the network-based access selection offers an overall perspective, by means of which network resources can be better utilized. It can for example be used by operators or Internet service providers (ISPs) to control and distribute user traffic in an appropriate manner.

[0046] In an embodiment, the final decision as for which access network that is currently the best lies with the access manager 214. The access manager makes this decision based on information from the access wizard unit, preferably together with information input from the GUI (user intervention) and/or from a profile or priority list stored locally at the terminal. After determining which network is currently the best, the access manager provides corresponding instructions to the link manager(s). There are generally one link manager 215 for each access network interface of the terminal 210 through which the terminal can be connected/disconnected to the respective access network. Another typical function of the link managers 215 is to detect available/current access networks and report this information to the access manager 214, from where it can be passed on to the access wizard unit 261 via the access wizard agent 213.

[0047] An advantage of solutions where the final access selection/determining is performed by the access manager is that the access manager can be used as a fallback mechanism through which access selection can be performed even if some functions for network-based access selection should be down. Moreover, implementations where the access manager normally follows the access recommendation from the access wizard unit but is allowed too choose another access are very useful in situations where the recommended access network has changed or is down. For example, there may be embodiments where a possible active choice by the user through the GUI take precedence, followed by the access recommendation from access wizard unit, and finally a priority-list in the terminal can be used if the access recommendation is absent or not valid.

[0048] Although the access wizard unit preferably receives terminal-specific information, such as information about available access networks and current terminal location, from the access wizard agent, there may be cases where no such information transfer occurs Without knowing which access networks are actually available, the access wizard can still perform the network-based access selection, and send an access recommendation involving one (or a list of several) best access network(s) which has to be checked against available access networks in the terminal.

[0049] The access wizard agent is thus the functionality of the terminal that communicates with the access wizard unit. It also communicates with other units/functions within terminal for transfer of information between the terminal and the access wizard unit. The access wizard agent can with advantage be implemented through comparatively simple units/functions, the main purpose of which is to forward information to/from the access wizard unit. However, there may be embodiments with more complex access wizard agents as well.

[0050] The signaling between the access wizard unit and access wizard agent is performed over secure links, on application level, e.g. by means of the Hypertext Transfer Protocol (HTTP), or on lower layers.

[0051] The network-based units for access selection can with advantage be parts of an overall multi-access mechanism, such as an ABC service network that provides services related to mobility, security and access handling. The ABC service network is typically managed by a network operator, a mobile virtual network operator (MVNO) or a service/application provider, or provided in a corporate network. Other arrangements are possible, provided that the access wizard unit(s) and the profile server(s) are still network-based (arranged at the network side).

[0052] Still referring to FIG. 2, the illustrated ABC service network 260 further comprises a security server 264 and a mobility server 265. The security server 264 handles security-related matters like authentication and authorization, and can with advantage be implemented as an AAA (authentication, authorization, accounting) server. The databases 263 and profile server 262 are preferably secured through the security server 264. The mobility server 265 performs various mobility-related functions and can for example be based on solutions for Mobile IPv4, Mobile IPv6, SLM (session layer mobility) and/or SIP (session initiated protocol) mobility. Thus, as a terminal changes access network the user/terminal can be authenticated and authorized through the security server 264 and application sessions are maintained during the handoff by means of the mobility server 265 which communicates with mobility clients 216 in the respective multi-access terminals 210.

[0053] The access wizard, profile server, security server and mobility server units/functions preferably belong to the same operator network. Solutions where the profile server is co-located with the security server are particularly advantageous since they facilitate the secure handling of the database information. Furthermore, according to a preferred embodiment of the invention it is proposed that the access wizard unit assists the security infrastructure for achieving seamless mobility. This will be further described below.

[0054] FIG. 3 is a schematic block diagram of a multi-access communication system with access selection according to another example embodiment. FIG. 3 directly corresponds to FIG. 2, except that an application 317 on the terminal side and an application server unit/function 366 on the network side are shown. In accordance with this embodiment, the application server 366, which preferably is arranged in an ABC service network 360, collects/receives database information from the profile 362. The information is used to adapt the application 317 to suit the particular terminal/user. The application may for example be altered in response to the screen size of different user devices 310.

[0055] By adapting applications from the network side, many factors can be allowed to affect how the application is presented to the user. Another advantage is that transfer of unnecessary application information, i.e. information that the terminal cannot use, can be avoided.

[0056] FIG. 4 is a schematic block diagram illustrating access selection according to an example embodiment suitable for vehicle scenarios. In this example system 400, Mobile IPv6 is used for mobility management between a vehicle terminal 410 and an HA 465 located at an MVNO ABC network 460. The security function of the ABC service network 460 comprises an AAAh server 464. The AAA infrastructure for seamless mobility and the mobility client of FIG. 4 can for example correspond to the collection of AAAv and AAAh as described in Diameter MIPv4 application.

[0057] It is assumed that at any point in time at most one access network 420 is used as main access over which the Mobile IPv6 tunnel and signaling/communication between the terminal 410 in the vehicle 418 and the MVNO operator network 460 pass. The choice of access is accomplished through the network-based procedure of the invention, possibly in combination with user/terminal-based access selection. The access wizard unit 461 located at the MVNO operator network 460 is responsible for the network-based access selection, which will now be described more in detail by way of example.

[0058] In the terminal 410, an access wizard agent 413 preferably obtains information from the GPS, route, velocity sensors 412, finds out which application is currently used (e.g. via packet sniffing or from prior explicit signaling), and obtains information about currently available access networks (e.g. through active probes) via an access manager/link manager 414.

[0059] The access wizard agent 413 preferably forwards at least some of this information to the access wizard unit 461 in the ABC network 460, e.g. via a mobility tunnel. The terminal-specific information transmitted from the access wizard agent 413 to the access wizard unit 461 may for instance comprise currently used applications (port numbers/IP addresses), currently available (or visible) access networks 420 to the terminal 410, needed quality of service (QoS), as well as current location (from GPS), velocity, direction and route of the terminal 410.

[0060] The access wizard 461 in turn collects database information through the profile server 462 and its associated databases 463. The database information typically includes availability/properties of each access network, operator policies, operator/user prioritization criteria, as well as allowed user subscription profiles. The access network specific information transmitted from the profile server to the access wizard may for example include an access identifier, span (x, y), assigned AAAv, allowed port numbers/IP addresses/applications, allowed subscription level, estimated time remaining in access network for handoff to be allowed, allowed QoS, current level of congestion (can be provided to the access wizard from elsewhere), list of access networks, priority rules regarding operator selection criteria versus subscriber selection criteria, and/or operator prioritization of selection criteria. The user subscription profile may for example contain NAI (network access identifier), subscription level, allowed port numbers/IP addresses/applications, allowed QoS and/or subscriber prioritization of selection criteria.

[0061] Based on the collected information the access wizard unit 461 decides which access network 420 is currently best for the user/terminal 410 and signals this back to the access wizard agent 413. Within the terminal 410, the access wizard agent 413 forwards this information to the access manager 414, which executes the actions necessary to use the best access. The described mechanism for determining the currently best access is referred to as current access selection.

[0062] For current access selection, the logic taken within the access wizard unit 461 preferably takes into account both information from the access wizard agent 413 and information from the profile server 462/databases 463 A list of current candidate access networks can e.g. be produced by using the current location (x, y), velocity, direction, route (y=f(x)), and a list of detected available access networks. Thereafter, a prioritization program is run among these candidate accesses, taking into account prioritization regarding operator selection criteria vs. subscriber selection criteria, operator prioritization of selection criteria, and subscriber prioritization of selection criteria. The prioritization procedure results in one suggested current best access. The current best access selected at the ABC service network 460 is communicated (e.g. as an identification number) from the access wizard unit 461 back to the access wizard agent 413 in the terminal 410.

[0063] The network-based access selection procedure of the access wizard unit 461 can either be initiated through a request from the access wizard agent 413 in the terminal 410 or be initiated by the access wizard unit itself. In an embodiment, the access selection algorithm is executed every time the environment changes, such as when another access network becomes available/unavailable, or applications start/stop. Thereby, the best access network is updated to suit the new situation.

[0064] From the current location, route, and velocity information, the access wizard unit 461 can also predict which access network is going to be best for the terminal/user after a predetermined period of time. This is referred to as predictive access selection. The access wizard unit 461 signals the future best access to the access wizard agent 413, whereafter the access manager 414 can execute the actions necessary to use the future best access.

[0065] Also in this case, the logic taken within access wizard unit 461 should preferably take into account both information from the access wizard agent 413 and information from the profile server 462/databases 463. A list of future candidate access networks can e.g. be produced by using the current location (x, y), velocity, direction and route (y=f(x)) and assuming a certain future time. Thereafter, a prioritization program is run among these candidate accesses, taking into account prioritization regarding operator selection criteria vs. subscriber selection criteria, operator prioritization of selection criteria, and subscriber prioritization of selection criteria. The prioritization procedure results in determination of one suggested future best access. The future best access determined at the ABC service network 460 is communicated (e.g. as an identification number) from the access wizard unit 461 back to the access wizard agent 413 in the terminal 410. The future best access can either be sent in advance together with an indication of the assumed future time or, alternatively, the transfer does not occur until the predetermined future time arrives.

[0066] Predictive access selection indicates that the access wizard unit 461 receives some kind of indication of where the user is heading, such as the planned route or the current direction and speed of the mobile terminal 410. Since users in vehicles 418 normally are confined to certain locations (roads, garages, etc.) and are associated with predictive certainties as for the chosen route, direction and speed of the vehicle, predictive access selection works especially well for (but are not limited to) vehicle scenarios.

[0067] According to an embodiment, the access wizard unit 461 also assists the security mechanism, e.g. the AAA infrastructure, in order to achieve seamless mobility. More specifically, the access wizard unit issues the necessary triggers for AAA inter-domain security context transfers. In FIG. 4, it is shown that the access wizard unit 461 sends a triggering message to the AAAh 464. In response to this trigger, the AAAh 464 provides transfer of the necessary security context from the AAAv 471 in the security domain 470 the vehicle 418 is about to leave to the new AAAv. In this way, the new AAAv is prepared for the fact that the mobile terminal 410 will soon be entering its security domain, whereby AAA optimization for fast handoffs can be achieved.

[0068] The access wizard unit can issue the necessary triggers for inter-domain transfers of security contexts in connection with both the current access selection and the predictive access selection. The predictive access selection might often result in AAA optimization with even smoother handoffs. FIG. 5 illustrates network-based current access selection and predictive access selection, respectively, according to example embodiments. Exemplary signaling flows are shown for the current access selection, with handoff from an access network assigned under AAAv0 (not shown) to an access network assigned under AAAv1 571-1, and for the predictive access selection, with further handoff from the access network assigned under AAAv1 571-1 to an access/cell assigned under AAAv2 571-2.

[0069] The mobile node/terminal is initially authenticated and registered via the visited security server AAAv0. Prior to the decision regarding the current best access at the access wizard unit 561, terminal specific information, e.g. including the location (GPS), route and velocity of the terminal is transferred from the access wizard agent 513 to the access wizard unit 561 (1). The access wizard 561 queries database information/profiles from the profile server 562 with associated databases (II) and receives a reply containing the requested information from the profile server (III). Based on the information received in (I) and (III) the access wizard determines the currently best access network for the terminal/user, which is communicated to the access wizard agent 513 in the terminal (V). Through a security context transfer request (IV) the access wizard 561 also triggers an AAA security context transfer (VI) between AAAh 564 and AAAv1 571-1 enabling a smooth handoff to an access network assigned under AAAv1 571-1. The request is preferably sent immediately and contains a directive to transfer AAA context information from AAAh to AAAv1. The terminal initiates authentication and registration via AAAv1.

[0070] In the case of predictive access selection, the access wizard unit 561 instead uses the information received in (I) and (III) to determine a future best access for the terminal/user, that is to be valid after a predetermined period of time. As before, the best access is communicated to the access wizard agent 513 (VIII) and an AAA context transfer request is sent from the access wizard unit 561 to the AAAh 564 (VII). However, the AAAh is instead instructed to transfer security information to AAAv2 571-2 (IX) for achieving seamless mobility and this directive may sometimes be sent with a delay. The terminal in this case initiates authentication and registration via AAAv2. The authentication and registration of the terminal towards the AAAv0, AAAv1 and AAAv2, respectively, can for instance be based on EAP/AKA and MIPv6.

[0071] Furthermore, there may be cases where the access wizard unit during the predictive access selection process realizes that no suitable access is available to support the requirements of the subscriber/application/terminal for the given route. In accordance with another embodiment, the access wizard unit in such situations suggests an alternative route, such that there will be less or no service disruptions. This is referred to as proactive access selection.

[0072] The procedure initially follows the one for predictive access selection described above. Thus, a list of future candidate access networks can e.g. be produced by using the current location (x, y), velocity, direction and route (y=f(x)) and assuming a certain future time. Thereafter, a prioritization program is run among these candidate accesses, taking into account prioritization regarding operator selection criteria vs. subscriber selection criteria, operator prioritization of selection criteria, and subscriber prioritization of selection criteria. If there are no candidate access available in at least a portion of the current given route the access wizard unit suggests an alternative route, such that candidate access networks are available for at least a larger portion of the route than for the current route. This may be simplified as displaying subscriber location and possible access networks on a map. The service could also be extended to allow the user to plan possible routes between two locations and with access network availability as new search criteria, e.g. type of service extended with hotspot availability.

[0073] Like the predictive access selection, the proactive access selection indicates that the access wizard receives some kind of indication of where the user is heading. Accordingly, the proactive access selection is particularly advantageous for vehicular scenarios. Generally the current chosen route is given, but in some cases, e.g. some vehicular scenarios, the access wizard may be able to conclude where the user is going by just knowing the current location (and preferably also the direction and speed).

[0074] FIG. 6 illustrates expected behaviors in vehicular scenarios with the current, predictive and proactive access selection according to the example embodiments. The expected behaviors for the current and predictive access selection are demonstrated in A. The vehicle chooses high-priority allowed access networks/cells (solid) when available; low-priority allowed access (dashed) when high-priority access is not available, and avoids the non-allowed areas (dotted). B illustrates the expected behavior for the proactive access selection. Solid, dashed and dotted lines, respectively, still means high-priority, low-priority and non-allowed access networks, respectively. When neither high-priority nor low priority allowed accesses are available along the chosen (current) route, an alternative route is suggested such that the coverage is not interrupted. The vehicular application of the proactive access selection may for example be implemented together with a car navigation system.

[0075] The solutions described with reference to FIGS. 4-6, especially for the predictive and proactive access selections, have primarily been exemplified by and are especially advantageous for situations where the mobile multi-access terminal resides in a vehicle. Nevertheless, it should be understood that scenarios involving other mobile terminals than those in vehicles also lie within the scope of the present invention. The proposed solutions can be used for handling access selection, mobility and security for any mobile multi-access terminal.

[0076] Example methods for the current access selection and for the combined current, predictive and proactive access selections, respectively, are summarized by the example flow charts of FIG. 7 and FIG. 8.

[0077] FIG. 7 is a flow chart of a method for the current access selection according to an embodiment. In a first step S1, the network-based (i.e. arranged at the network side) access selection unit (access wizard unit) receives terminal-specific information from the access agent (access wizard agent) in the mobile multi-access terminal. The access selection unit then collects database information in a step S2 by requesting and receiving data/information/profiles from a profile server, which is associated with a (typically large) number of databases. Based on the information from the profile server/databases and access agent, the access selection unit selects a current best access network for the terminal in a step S3. This can for instance involve executing an access selection algorithm based on predefined prioritization criteria at the access selection unit. In a final step S4, an access network recommendation comprising the current best access network is communicated from the access selection unit to the access agent. Depending on the implementation, the terminal can be forced to always follow the access network recommendation from the access selection unit, or it can use the recommendation as basis for a final access network determining process at the terminal. In the latter case, the network-based access selection at the access selection unit supports the final access selection decision of the terminal.

[0078] FIG. 8 is a flow chart of a method for combined current, predictive and proactive access selection according to another embodiment. The terminal-specific information from the access agent in the first step S1 includes the current (chosen) route for the mobile terminal. The steps S2 to S4 are performed as described with reference to FIG. 7. In a step S5, the access selection unit determines future access candidates, i.e. the access networks that may be possible after a predetermined period of time. Hereby, the access selection unit can for example produce a list of the future access candidates. The access candidates are checked against prioritization criteria and step S6 asks if there are (possible/allowed) candidate access networks available in the current route. If at least a portion of the current route lacks matching candidate access networks, the access selection unit suggests an alternative route for the terminal in a step S7. The alternative route is communicated to the access agent of the terminal in a step S8. This may be achieved in a simple manner by displaying the possible access network areas on a map. Should there, on the other hand, be candidate access networks available in the entire current route one or more future best access networks are selected at the access selection unit in a step S9, preferably by running a prioritization program/executing an access selection algorithm. In a final step S10, an access network recommendation comprising the future best access network(s) is communicated from the access selection unit to the access agent.

[0079] Although the invention has been described with reference to specific illustrated embodiments, it should be emphasized that it also covers equivalents to the disclosed features, as well as modifications and variants obvious to a man skilled in the art. Other embodiments may for instance present differently arranged terminal functionality, network functionality and connections/interfaces than the illustrated examples. Thus, the scope of the invention is only limited by the enclosed claims.

• [0080] [1] Annika Jonsson, Olle Viktorsson, Ericsson Research, “Access Selection in an Always Best Connected Environment”, contribution to the 5^th WWRF Meeting in Tempe, Ariz., Mar. 7-8, 2002.
• [0081] [2] Eva Gustafsson, Annika Jonsson: “Always Best Connected”, IEEE Wireless Communications, Vol. 10, Issue 1, February 2003, pp. 49-55.
• [0082] [3] International Patent Application WO 01/35585 A1, Telefonaktiebolaget LM Ericsson, publication date May 17, 2001.
• [0083] [4] Dave Johnson, Charles Perkins, Jari Arkko: “Mobility Support in IPv6”, IETF Internet draft <draft-ietf-mobileip-ipv6-24.txt>, June 2003.
• [0084] [5] Pat R. Calhoun, Tony Johansson, Charles E. Perkins: “Diameter Mobile IPv4 Application”, IEF Internet draft<draft-ietf-aaa-diameter-mobileip-15.txt>, November 2003.