Abstract:
Methods of operating a network node in a wireless local area network, a mobile terminal and a server, respectively, are disclosed. Corresponding computer programs, as well as a network node, a mobile terminal and a server are also disclosed. The network node establishes connection with the mobile terminal; and sends at least one network name to the mobile terminal, wherein the at least one network names correspond to possible public land mobile networks, PLMNs, based on the determined AAA information. The mobile terminal can thus display the network name.

Description:
TECHNICAL FIELD 
       [0001]    The present invention generally relates to a mobile terminal, a network node and a server, methods for operating each of them, and computer programs for implementing the methods. 
       BACKGROUND 
     Abbreviations 
       [0000]    
       
         3GPP 3 rd  Generation Partnership Project 
         UMTS Universal Mobile Telecommunication System 
         UTRAN UMTS Terrestrial Radio Access Network 
         GSM Global System for Mobile communication 
         EDGE Enhanced Data for GSM Evolution 
         GERAN GSM EDGE Radio Access Network 
         E-UTRAN Evolved UTRAN 
         UE User Equipment 
         PLMN Public Land Mobile Network 
         IE Information Element 
         MCC Mobile Country Code 
         MNC Mobile Network Code 
         EAP Extensible Authentication Protocol 
         EAP-AKA Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (RFC 4187) 
         EAP-AKA′ Improved Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (RFC 5448) 
         EPC Evolved Packet Core 
         AAA Authentication, Authorisation and Accounting 
         REQ REQuest 
         RSP ReSPonse 
         AKA Authentication and Key Agreement 
         AK Authentication Key 
         RAND RANDom number 
         XRES eXpected RESponse 
         AUTN Authentication TokeN 
         ePDG evolved Packet Data Gateway 
         IKE Internet Key Exchange 
         AUTH AUTHentication 
         NAI Network Access Identifier 
         ID Identity 
         GW Gateway 
         HA Home Agent 
         LTE 3GPP Long Term Evolution 
         HSPA High-Speed Packet Access 
       
     
         [0035]    In 3GPP accesses (i.e. UTRAN, GERAN, E-UTRAN), the UE can be informed about the network name of the registered PLMN. This is particularly useful when the registered PLMN is other than home PLMN of the UE UE roams). The network name is then often presented to the user of the UE, e.g. on a display. The user can then find out whether being at home network or a network accessible by roaming depending of the network name of the registered PLMN on the display. 
         [0036]    3GPP specification 24.008 defines the following information elements: 
         [0037]    9.4.19.1 Full Name for Network 
         [0038]    This IE may be sent by the network. If this IE is sent, the contents of this IE indicate the “full length name of the network” that the network wishes the mobile station to associate with the MCC and MNC contained in the routing area identification of the current cell. 
         [0039]    9.4.19.2 Short Name for Network 
         [0040]    This IE may be sent by the network. If this IE is sent, the contents of this IE indicate the “abbreviated name of the network” that the network wishes the mobile station to associate with the MCC and MNC contained in the routing area identification of the cell the MS is currently in. 
         [0041]    Equivalent IEs are defined for the circuit switched domain in sections 9.2.15a.1 and 9.2.15a.2. The encoding/structure of the network name is defined in section 10.5.3.5a. 
         [0042]    US 2003/0119481 A1 discloses a method of arranging roaming in a telecommunication system comprising a terminal equipment, a public land mobile network (PLMN) and a local area network (LAN). The terminal equipment selects a PLMN by comparison of PLMN identifiers received from PLMNs and PLMN identifiers stored in the terminal equipment. Access can be arranged via the LAN to a network element determined by a network identifier linked with the selected PLMN. A network element identifier linked with a PLMN identifier is a realm identifier which is a part of a network access identifier. A realm identifier is preferably a domain name such as “server_finland.com” which can be used to determine internet protocol address of the server. 
         [0043]    Similarly as in 3GPP access, the UE can select and authenticate via a PLMN other than its home PLMN in non-3GPP accesses. The UE uses EAP as authentication protocol and indicates its identity using Decorated NAI (see 3GPP specification 23.003, section 19.3.3) where the realm is the realm of the PLMN selected in the non-3GPP access. 
         [0044]    Similarly as in 3GPP access, the PLMN selected in non-3GPP access can be interested to provide its network name to the UE so that the UE could display it. However, there is not so far a defined method how the PLMN selected in non-3GPP access could indicate its network name to the UE. 
         [0045]    HotSpot2.0 is a standard with a specification created by the Wi-Fi Alliance to enable mobile users to join and roam among public Wi-Fi networks. The HotSpot2.0 specification defines a method, popularly called “Operator Friendly Name”, how the HotSpot2.0 service provider operating HotSpot2.0 network node can indicate its network name to the UE. HotSpot2.0 network node can be connected to EPC as non-3GPP access. However, when HotSpot2.0 network node is connected to EPC, then PLMN selected in the HotSpot2.0 access network is not necessarily the HotSpot2.0 service provider operating HotSpot2.0 network node. 
         [0046]    E.g. in the following use case, the information provided using HotSpot2.0 signalling does NOT match the PLMN selected in the non-3GPP access: 
         [0047]    HotSpot2.0 network node is operated by a coffeehouse chain. Thus, the network name provided by the HotSpot2.0 network node relates to the name of the coffeehouse chain. 
         [0048]    The coffeehouse chain has contract with a first and a second PLMN operator (which are both 3GPP operators) to provide HotSpot2.0 coverage for them but does not have such a contract with a third PLMN operator (which is also a 3GPP operator) 
         [0049]    The third PLMN operator has 3GPP roaming agreement with the first PLMN operator 
         [0050]    At this coffeehouse chain operated HotSpot2.0 network node, a UE with USIM from the third PLMN operator can select the first PLMN operator and authenticate via the first PLMN operator to a 3GPP AAA server of the third PLMN operator. If so, the first PLMN operator will wish to provide its network name to the UE but cannot due to no defined method. 
         [0051]    It is therefore a desire to provide an approach for alleviating this problem. 
       SUMMARY 
       [0052]    An object of the invention is to at least alleviate the above stated problem. The present invention is based on the understanding that adapting the approach for UE connection can enable the provision of the network name to the UE. 
         [0053]    According to a first aspect, there is provided a method of operating a network node in a wireless local area network comprising establishing connection with a mobile terminal; requesting and receiving identity information from the mobile terminal; determining Authentication, Authorisation and Accounting, AAA, information for the mobile terminal; and sending at least one network name to the mobile terminal, wherein the at least one network names correspond to possible public land mobile networks, PLMNs, based on the determined AAA information. 
         [0054]    The network name may comprise at least one of a full name for the PLMN and a short name for the PLMN. 
         [0055]    The method may further comprise performing authentication of the mobile terminal with aid of one of said PLMNs. The authentication may include sending a message, including the identity information of the mobile terminal, to a server associated to a PLMN, wherein the PLMN is determined based on the determined AAA information; receiving an authentication check message from the server; sending a message based on the authentication check message to the mobile terminal; receiving a response to the message based on the authentication check message from the mobile terminal; sending a message based on the response to the server; and receiving an authentication success message from the server if the authentication succeeded. 
         [0056]    According to an embodiment, the authentication may further include receiving an Internet Key Exchange AUTHorization, IKE_AUTH, message from the mobile terminal, the sent message, including the identity information of the mobile terminal, to the server is an Authenication and Authorization, A&amp;A, Request, the received authentication check message is an A&amp;A Answer, the sent message based on the authentication check message is an IKE_AUTH Response, the received response is an IKE_AUTH Request, the sent message based on the response is an A&amp;A Request, and the authentication success message is an A&amp;A Answer, and the sending of the network name is appended to an IKE_AUTH Response sent to the mobile terminal. 
         [0057]    According to an embodiment, the authentication may further include sending an Extensible Authentication Protocol, EAP, Request for identity and receiving an EAP Response with the identity, and the sent message, including the identity information of the mobile terminal, to the server is an Authenication, Authorization and Accounting, AAA, message including the EAP Response with the identity and appended name of the PLMN, the received authentication check message is an AAA message including EAP Request Authentication and Key Agreement. AKA, Challenge, the sent message based on the authentication check message is an EAP Request and AKA Challenge, the received response is an EAP Response and AKA Challenge, the sent message based on the response is an AAA message including an EAP Response and AKA Challenge Request, and the authentication success message is an AAA message including EAP Success. The sending of the network name may be appended to any of the sent EAP Request and AKA Challenge, a sent EAP Request and AKA Notification, and an EAP Success message sent to the mobile terminal. 
         [0058]    Here, it should be noted that EAP-AKA and EAP-AKA′ are two very similar protocols, where the latter is a newer version of the former. Throughout this disclosure, what applies for EAP-AKA messages applies also for EAP-AKA′ and vice verse, unless explicitly stated otherwise. 
         [0059]    The method may include sending a name of a PLMN available at the network node and for the mobile terminal based on the determined AAA information to the mobile terminal. 
         [0060]    According to a second aspect, there is provided a method of operating a network node in a wire less local area network comprising establishing connection with a mobile terminal; receiving a request from the mobile terminal for available PLMNs; sending names of all available PLMNs at the network node to the mobile terminal; receiving a message from the mobile terminal indicating one of the available PLMNs as selected PLMN; and assigning the selected PLMN for further processing. 
         [0061]    According to one embodiment, the method further comprises requesting and receiving identity information from the mobile terminal. 
         [0062]    According to a third aspect, there is provided a method of operating a mobile terminal for connecting to a network node of a wireless local area network comprising establishing connection with the network node; receiving a request for identity information from the network node; sending identity information to the network node; receiving at least one network name from the network node, wherein the at least one network names correspond to possible public land mobile networks based on Authentication, Authorisation and Accounting, AAA, information associated with the mobile terminal. 
         [0063]    The network name may comprise at least one of a full name for the PLMN and a short name for the PLMN. 
         [0064]    The method may further comprise authenticating the mobile terminal to one of the PLMNs. The authenticating may include receiving an authentication check message from the network node; digesting the authentication check message and generating a response; sending the response to the authentication check message to the network node; and receiving an authentication success message from the network node if the authentication succeeded. 
         [0065]    According to an embodiment, the authenticating may further include sending an Internet Key Exchange AUTHorization, IKE_AUTH, message to the network node, the received authentication check message is an IKE_AUTH Response, the sent response is an IKE_AUTH Request, and the authentication success message is an IKE_AUTH Response sent to the mobile terminal to which the network name is appended. 
         [0066]    According to an embodiment, the authentication may further include receiving an Extensible Authentication Protocol, EAP, Request for identity and sending an EAP Response with the identity, the received authentication check message is an EAP Request and AKA Challenge, the sent response is an EAP Response and AKA Challenge, and the authentication success message is an EAP Success message. The received network name may be appended to any of the received EAP Request and AKA Challenge, a received EAP Request and AKA Notification, and the EAP Success message. 
         [0067]    The received name of a PLMN may be of a PLMN available at the network node and for the mobile terminal based on the AAA information of the mobile terminal. 
         [0068]    According to a fourth aspect, there is provided a method of operating a mobile terminal for connecting to a network node of a wireless local area network comprising establishing connection with the network node; receiving names of all available PLMNs at the network node; selecting one PLMN among the PLMN names; and sending a message to the network node indicating the selected PLMN, wherein the selected PLMN is assigned for further processing. 
         [0069]    According to an embodiment, the method may further comprise receiving a request for identity information from the network node; and sending identity information to the network node. 
         [0070]    According to a fifth aspect, there is provided a method of operating a server in a public land mobile network comprising receiving a network name and an inbound extensible authentication protocol, EAP, message emanating from a mobile terminal established in connection with a network node of a wireless local access area network from the network node of the wireless local area network; generating an outbound EAP message for the mobile terminal including the network name; and transmitting the outbound EAP message to the network node of the wireless local area network. 
         [0071]    The outbound EAP message may be an EAP Request and authentication and key agreement challenge message. 
         [0072]    The outbound EAP message may be an EAP Request and authentication and key agreement notification message. 
         [0073]    The outbound EAP message may be an EAP success message. 
         [0074]    According to a sixth aspect, there is provided a network node in a wireless local area network arranged to establish connection with a mobile terminal; request and receive identity information from the mobile terminal; determine Authentication, Authorisation and Accounting, AAA, information for the mobile terminal; and send at least one network name to the mobile terminal, wherein the at least one network names correspond to possible public land mobile networks, PLMNs, based on the determined AAA information. 
         [0075]    According to a seventh aspect, there is provided a network node in a wireless local area network arranged to establish connection with a mobile terminal; receive a request from the mobile terminal for available public land mobile networks, PLMNs; send names of all available PLMNs at the network node to the mobile terminal; receive a message from the mobile terminal indicating one of the available PLMNs as selected PLMN; and assign the selected PLMN for further processing. 
         [0076]    According to an eighth aspect, there is provided a mobile terminal enabled for connecting to a network node of a wireless local area network, wherein the mobile terminal is arranged to establish connection with the network node; receive a request for identity information from the network node; send identity information to the network node; receive at least one network name from the network node, wherein the at least one network names correspond to possible public land mobile networks based on Authentication, Authorisation and Accounting, AAA, information associated with the mobile terminal. 
         [0077]    According to a ninth aspect, there is provided a mobile terminal enabled for connecting to a network node of a wireless local area network, wherein the mobile terminal is arranged to establish connection with the network node; receive names of all available PLMNs at the network node; select one PLMN among the PLMN names; and send a message to the network node indicating the selected PLMN, wherein the selected PLMN is assigned for further processing. 
         [0078]    According to a tenth aspect, there is provided a server in a public land mobile network arranged to receive a network name and an inbound extensible authentication protocol, EAP, message emanating from a mobile terminal established in connection with a network node of a wireless local access area network from the network node of the wireless local area network; generate an outbound EAP message for the mobile terminal including the network name; and transmit the outbound EAP message to the network node of the wireless local area network. 
         [0079]    According to an eleventh aspect, there is provided a computer program comprising computer code with computer executable instructions which when executed by a processor causes the processor to control an electronic device as of the fourth to sixth aspects to perform the method according to any of the first to third aspects, respectively. 
         [0080]    Other objectives, features and advantages of the present invention will appear from the following detailed disclosure, from the attached dependent claims as well as from the drawings. Generally, all terms used in the claims are to be interpreted according to their ordinary meaning in the technical field, unless explicitly defined otherwise herein. All references to “a/an/the [element, device, component, means, step, etc]” are to be interpreted openly as referring to at least one instance of said element, device, component, means, step, etc., unless explicitly stated otherwise. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless explicitly stated. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0081]    The above, as well as additional objects, features and advantages of the present invention, will be better understood through the following illustrative and non-limiting detailed description of preferred embodiments of the present invention, with reference to the appended drawings. 
           [0082]      FIGS. 1 to 6  are signalling schemes illustrating communications between mobile terminal, network node and entities associated with PLMN according to respective embodiments. 
           [0083]      FIG. 7  is a flow chart illustrating a method for a network node according to an embodiment. 
           [0084]      FIG. 8  is a flow chart illustrating a method for a mobile terminal according to an embodiment. 
           [0085]      FIG. 9  is a flow chart illustrating a method for a server according to an embodiment. 
           [0086]      FIG. 10  is a block diagram which schematically illustrates a mobile terminal according to an embodiment. 
           [0087]      FIG. 11  is a block diagram which schematically illustrates a network node according to an embodiment. 
           [0088]      FIG. 12  is a block diagram which schematically illustrates a server according to an embodiment. 
           [0089]      FIG. 13  schematically illustrates a computer-readable medium and a processor arranged to execute instructions of a computer program stored on the computer-readable medium. 
       
    
    
     DETAILED DESCRIPTION 
       [0090]    A network node, i.e. an entity in non-3GPP wireless access, which the UE authenticates via, is arranged to indicate the Full name for network according to same structure as in 3GPP specification 24.008 or similar and/or the Short name for network according to same structure as in 3GPP specification 24.008 or similar to the UE. This is demonstrated in detail below with reference to a few embodiments wherein the demonstrated details are made with strong reference to corresponding context as specified in the 3GPP specification, whereby a person skilled in the art readily will understand how to apply the inventive contribution. 
         [0091]    As the network node can be connected with 3GPP network using different methods, as defined in the 3GPP specification, different entities provide the Full name for network and/or the Short name for network to the UE in each method. 
         [0092]      FIG. 1  is a signalling scheme illustrating communications between mobile terminal (UE), network node (Non-3GPP Access) and entities associated with PLMN (Proxy AAA, 3GPP AAA Server, HSS) according to an embodiment. It should be noted that  FIG. 1  is based on FIG. 6.2-1 of 3GPP specification 33.402 for the person skilled in the art readily should understand the context of the solution and the contribution, where the transmission of the network name is emphasized by bold text in  FIG. 1 . 
         [0093]    When the 3GPP based access authentication, as specified in 3GPP specifications 23.402, section 4.9.1, and 33.402 section 6.2, is used in the network node connected to EPC, the authenticator in the network node inserts the Full name for network according to same structure as in 3GPP specification 24.008 or similar, and/or the Short name for network according to same structure as in 3GPP specification 24.008 or similar in an EAP Success message sent to the UE. In this method, the Fullname for network and/or the Short name for network are provided without integrity protection. 
         [0094]      FIG. 2  is a signalling scheme illustrating communications between mobile terminal (UE), network node (ePDG) and entities associated with PLMN (3GPP AAA Server, HSS/HLR) according to an embodiment. It should be noted that  FIG. 2  is based on FIG. 82.2-1 of 3GPP specification 33.402 for the person skilled in the art readily should understand the context of the solution and the contribution, where the transmission of the network name is emphasized by bold text in  FIG. 2 , i.e. the Full name for network and/or Short name for network can be provided in transmissions 11 or 15, or both. 
         [0095]    For a network node connected with 3GPP network using a tunnel authentication as specified in 3GPP specifications 23.402, section 4.9.2, and 33.402, section 8.2.2, is used in a network node connected to EPC, the ePDG inserts the Full name for network according to same structure as in 3GPP specification 24.008 or similar and/or the Short name for network according to same structure as in 3GPP specification 24.008 or similar into an IKE_AUTH response message sent to the UE. 
         [0096]      FIG. 3  is a signalling scheme illustrating communications between mobile terminal (UE), network node (PDN GW) and entities associated with PLMN (AAA, HSS) according to an embodiment. For a network node connected with 3GPP network using a tunnel authentication as specified in 3GPP specifications 23.402, section 4.9.2, and 33.402, section 8.2.2, is used in the network node connected to EPC, the P-GW/HA inserts the Full name for network according to same structure as in 3GPP specification 24.008 or similar and/or the Short name for network according to same structure as in 3GPP specification 24.008 or similar into an IKE_AUTH response message sent to the mobile terminal, as indicated in steps 12 or 14 of  FIG. 3 . 
         [0097]      FIG. 4  is a signalling scheme illustrating communications between mobile terminal (up, network node and entities associated with PLMN (3GPP AAA Server, HSS/HLR) according to an embodiment. It should be noted that  FIG. 4  is based on FIG. 4 of 3GPP specification 33.234 for the person skilled in the art readily should understand the context of the solution and the contribution. 
         [0098]    When I-WLAN is used as specified in 3GPP specifications 23.234, section 7.2, and 33.234, section 6.1.1.1, the WLAN access network inserts the Full name for network according to same structure as in 3GPP specification 24.008 or similar and/or the Short name for network according to same structure as in 3GPP specification 24.008 or similar in an EAP Success message sent to the UE. In this method, the Full name for network and/or the Short name for network are provided without integrity protection. 
         [0099]    In the embodiments demonstrated above, the network name emanates from the network node and is sent to the mobile terminal. The network name can also be provided from the network node to a 3GPP AAA server for being arranged in a message provided from the PLMN to the mobile terminal via the network node. Thus, the network node, i.e. entity in non-3GPP wireless access, which the mobile terminal authenticates via, indicates the Full name for network according to same structure as in 3GPP specification 24.008 or similar and/or the Short name for network according to same structure as in 24.008 or similar to the 3GPP AAA Server. The 3GPP AAA Server copies the received Full name for network and/or the received Short name for network to EAP message(s) sent to the mobile terminal via the network node. 
         [0100]      FIG. 5  is a signalling scheme illustrating communications between mobile terminal (UE), network node (Non-3GPP Access) and entities associated with PLMN (Proxy AAA, 3GPP AAA Server, HSS) according to an embodiment. It should be noted that  FIG. 5  is based on FIG. 6.2-1 of 3GPP specification 33.402 for the person skilled in the art readily should understand the context of the solution and the contribution, where the transmission of the network name is emphasized by bold text in  FIG. 5 . 
         [0101]    When the 3GPP based access authentication as specified in 3GPP specifications 23.402, section 4.9.1, and 33.402, section 6.2, is used in the network node connected to EPC, the authenticator in the network node inserts the Full name for network according to same structure as in 24.008 or similar and/or the Short name for network according to same structure as in 24.008 or similar in an AAA message, e.g. along with EAP response and Identity, sent towards the 3GPP AAA server. The 3GPP AAA server copies the received Full name for network and/or the received Short name for network in an EAP message, e.g. EAP Success, EAP Request and AKA Challenge or EAP Request and AKA Notification, sent to the mobile terminal via the network node. In this method, the Full name for network and/or Short name for network can be provided with integrity protection. 
         [0102]      FIG. 6  is a signalling scheme illustrating communications between mobile terminal (UE), network node and entities associated with PLMN (3GPP AAA Server, HSS/HLR) according to an embodiment. It should be noted that  FIG. 6  is based on FIG. 4 of 3GPP specification 33.234 for the person skilled in the art readily should understand the context of the solution and the contribution. 
         [0103]    When I-WLAN is used as specified in 3GPP specifications 23.234, section 7.2, and 33.234, section 6.1.1.1, the WLAN access network inserts the Full name for network according to same structure as in 3GPP specification 24.008 or similar and/or the Short name for network according to same structure as in 3GPP specification 24.008 or similar in an AAA message, e.g. along with EAP Response and Identity, sent towards the 3GPP AAA server. The 3GPP AAA server copies the received Full name for network and/or the received Short name for network in an EAP message, e.g. EAP Success, EAP Request and AKA Challenge, or EAP Request and AKA Notification, which is sent to the mobile terminal via the network node. In this method, the Full name for network and/or the Short name for network can be provided with integrity protection. 
         [0104]    Upon using e.g. a 802.1x wireless access, and when the mobile terminal performs network discovery by authenticating using NAI with unknown realm, e.g. alternative NAI as in 3GPP specification 24.234, section 4.4.1, a local AAA server sends Full name for network according to same structure as in 3GPP specification 24.008 or similar and/or Short name for network according to same structure as in 3GPP specification 24.008 or similar associated with the realm of PLMNs available at the network node. Each realm of an available PLMN can thus be associated with a different Full name for network and/or Short name for network. 
         [0105]    When the mobile terminal performs network discovery by querying network node using 802.11u, the network node sends Full name for network according to same structure as in 3GPP specification 24.008 or similar and/or Short name for network according to same structure as in 3GPP specification 24.008 or similar associated with the realm (or MCC/MNC) of PLMNs available at the network node. Each realm (or MCC/MNC) of an available PLMN can be associated with a different Full name for network and/or Short name for network. 
         [0106]    In contrast to ‘Operator Friendly Name’ defined in the HotSpot2.0 specification, the Full name for network and/or Short name for network is provided for any service provider or for any 3GPP PLMN available at the network node, i.e. not just the service provider operating the network node. 
         [0107]    Below, methods for the respective mobile terminal, network node and PLMN associated server are demonstrated. The methods are demonstrated on a general level for easy understanding of the principles and should be construed together with the signalling embodiments demonstrated above for understanding details of implementation. It should also be understood that the steps are not necessary performed in the order as depicted. The constraint on the order of the steps is only limited by availability to required information, and, optionally, on success in authentication. 
         [0108]      FIG. 7  is a flow chart illustrating a method for a network node according to an embodiment. Connection with a mobile terminal is established  700 . The network node performs  702  requesting of identity of the mobile terminal and receives its identity. This step  702  can be inherent in the connection establishment  700 , or be a separate issue, as can be seen for the different signalling scenarios demonstrated with reference to  FIGS. 1 to 6 . From the received information, the network node determines  704  AAA information for the mobile terminal. Based on this AAA information, the network node sends  708  the network name to the mobile terminal. Optionally, the network node performs authentication  705  on the mobile terminal, and if the authentication succeeds  707 , the processing can continue, or if the authentication fails, the processing can end. 
         [0109]      FIG. 8  is a flow chart illustrating a method for a mobile terminal according to an embodiment. Connection is established  800  with a network node of a wireless local area network. An identity request is received  802 , to which a response is sent  804  with the requested identity. These steps  802 ,  804  can be inherent in the connection establishment  800 , or be a separate issue, as can be seen for the different signalling scenarios demonstrated with reference to  FIGS. 1 to 6 . The network name is received  808  from the network node. Optionally, the mobile terminal can authenticate  805  itself to the network node, which is the physical connecting partner but the authentication is normally just communicating via the network node as indicated in  FIGS. 1 to 6 . If authentication succeeds  807 , a corresponding message is normally received, and if the authentication fails, the procedure normally ends. The network name can be appended to any of the received messages included in the authentication. 
         [0110]      FIG. 9  is a flow chart illustrating a method for a server according to an embodiment. As described with reference to any of  FIG. 5  or  6 , the network name is provided from the network node to the PLMN associated server for being embedded into an EAP message, which then is provided to the mobile terminal via the network node. Thus, the server receives  900  the network name along with inbound EAP message, both included in AAA message, generates  902  an AAA message containing outbound EAP message including the network name and transmits  904  the outbound EAP message to the network node. 
         [0111]      FIG. 10  is a block diagram which schematically illustrates a mobile terminal  1000  according to an embodiment. The mobile terminal  1000  comprises a transceiver  1002  arranged for wireless communication in both WLAN technology and cellular technology, i.e. as specified in the 3GPP specification. The mobile terminal  1000  comprises a processor  1004  arranged to control operation of the mobile terminal  1000 , and particularly arranged to control operation as demonstrated above with reference to  FIGS. 1 to 7 . The mobile terminal  1000  also comprises one or more interfaces  1006 , which can be electrical or optical interfaces for communicating with other circuitry or electronic entities, or a user interface, as known in the art and therefore not further elucidated here. 
         [0112]      FIG. 11  is a block diagram which schematically illustrates a network node  1100  according to an embodiment. The network node  1100  comprises a transceiver  1102  arranged for wireless communication in both WLAN technology. The network node  1100  comprises a processor  1104  arranged to control operation of the network node  1100 , and particularly arranged to control operation as demonstrated above with reference to  FIGS. 1 to 6  and  8 . The network node  1100  also comprises an interface  1106 , which can be electrical or optical interface for communicating with entities of one or more PLMNs, and can use data communication technology as known in the art and therefore not further elucidated here. 
         [0113]      FIG. 12  is a block diagram which schematically illustrates a server  1200 , associated with a PLMN, according to an embodiment. The server  1200  normally comprises a database  1202  for subscriber information to handle security and administration, such as AAA issues. The server  1200  also comprises a processor  1204  arranged to control operation of the server  1200 , and particularly arranged to control operation as demonstrated above with reference to  FIGS. 1 to 6  and  9 . The server  1200  also comprises an interface  1206 , which can be electrical or optical interface for communicating with entities of one or more network nodes or any control and interface circuitry associated with one or more network nodes, and can use data communication technology as known in the art and therefore not further elucidated here. 
         [0114]      FIG. 13  schematically illustrates a computer-readable medium  1300  and a processor  1302  arranged to execute instructions of a computer program stored on the computer-readable medium. The processor  1300  can be any of the processors  1004 ,  1104 ,  1204  demonstrated with reference to  FIGS. 10 to 12 , respectively, above. The instructions of the computer program are thus preferably adapted to the respective utility in the mobile terminal, network node or server. 
         [0115]    The methods according to the present invention is suitable for implementation with aid of processing means, such as computers and/or processors, especially for the cases demonstrated above. Therefore, there is provided computer programs, comprising instructions arranged to cause the processing means, processor, or computer to perform the steps of any of the methods according to any of the embodiments described with reference to  FIGS. 1 to 9 . The computer programs preferably comprises program code which is stored on a computer readable medium  1300 , as illustrated in  FIG. 13 , which can be loaded and executed by a processing means, processor, or computer  1302  to cause it to perform the methods, respectively, according to embodiments of the present invention, preferably as any of the embodiments described with reference to  FIGS. 1 to 9 . The computer readable medium  1300  is preferably non-transitory. The computer  1302  and computer program product  1300  can be arranged to execute the program code sequentially where actions of the any of the methods are performed stepwise. The processing means, processor, or computer  1302  is preferably what normally is referred to as an embedded system. Thus, the depicted computer readable medium  1300  and computer  1302  in  FIG. 13  should be construed to be for illustrative purposes only to provide understanding of the principle, and not to be construed as any direct illustration of the elements. 
         [0116]    The invention has mainly been described above with reference to a few embodiments. However, as is readily appreciated by a person skilled in the art, other embodiments than the ones disclosed above are equally possible within the scope of the invention, as defined by the appended patent claims.