AUTHENTICATION IN A WIRELESS COMMUNICATIONS NETWORK

Abstract

A method and apparatus for authenticating a mobile device in a second network when the mobile device is already authenticated in a first network. An authentication device in the first network generates an authentication master key associated with the mobile device using a first nonce generated by the authentication device and a second nonce generated by the mobile device. The generated authentication master key is sent to a second authentication device in the second network, where is usable by the second authentication device to authenticate the mobile device in the second network.

Claims

1. A method of authenticating a mobile device in a second network, the mobile device already being authenticated in a first network, the method comprising, at an authentication device in the first network; generating an authentication master key associated with the mobile device using a first nonce generated by the authentication device and a second nonce generated by the mobile device; sending the generated authentication master key to a second authentication device in the second network; and wherein the generated authentication master key is usable by the second authentication device to authenticate the mobile device in the second network.

2. The method according to claim 1, wherein the authentication master key is a Pairwise Master Key.

3. The method according to claim 1, further comprising: prior to generating the authentication master key, receiving at the first authentication node a request for the authentication master key, the request including the second nonce generated by the mobile device; and sending the generated authentication master key to the second authentication device.

4. The method according to claim 1, further comprising, at the mobile device: receiving from the authentication device in the first network the first nonce; generating the second nonce; after generating the authentication master key using the first and second nonces, sending the second nonce to the authentication device in the first network, the second nonce being usable by the authentication device in the first network to generate the authentication master key.

5. The method according to claim 4, wherein the first nonce is received and the second nonce is sent using any of Extensible Authentication Protocol over Local Area Network, EAPOL, and Wireless Network Management, WNM, Notification signalling.

6. The method according to claim 1, further comprising, at the authentication device in the first network: receiving from the second authentication device a request for the authentication master key; generating the first nonce; sending the first nonce towards the mobile device; receiving from the mobile device the second nonce; generating the authentication master key using the first and second nonces; and sending the generated authentication master key to the second authentication device.

7. The method according to claim 1, wherein the first network is a 3GPP network and the second network is a Wireless Local Area Network.

8. The method according to claim 1, wherein the first network is a Wireless Local Area Network and the second network is a 3GPP network.

9. A method of authenticating a mobile device in a second network, the mobile device already being authenticated in a first network, the method comprising, at an authentication device in the second network; receiving a generated authentication master key from a first network authentication device, the authentication master key having been generated using a first nonce generated by the first network authentication device and a second nonce generated by the mobile device; using the generated authentication master key to authenticate the mobile device in the second network.

10. The method according to claim 9, wherein the authentication master key is a Pairwise Master Key.

11. The method according to claim 9, further comprising: prior to receiving the generated authentication master key, sending to the first network authentication device a request for the authentication master key.

12. A device arranged to generate an authentication master key for authenticating a mobile device in a second network, the mobile device already being authenticated in a first network, the device comprising: a processor arranged to generate the authentication master key associated with the mobile device using a first nonce generated by an authentication device in the first network, and a second nonce generated by the mobile device; and

13. The device according to claim 12, wherein the device is an authentication device in the first network, the authentication device comprising: a receiver arranged to receive a request for the authentication master key, the request including the second nonce generated by the mobile device; and a transmitter arranged to send the generated authentication master key to a second authentication device.

14. The device according to claim 12, wherein the device is the mobile device, the mobile device comprising: a receiver arranged to receive from the authentication device in the first network the first nonce; wherein the processor is further arranged to generate the second nonce; and the transmitter is arranged to send the second nonce towards the authentication device in the first network, the second nonce being usable by the authentication device in the first network to generate the authentication master key.

15. The device according to claim 14, wherein the receiver and transmitter are arranged to receive and send signalling using any of Extensible Authentication Protocol over Local Area Network, EAPOL, and Wireless Network Management, WNM, Notification signalling.

16. The device according to claim 12, wherein the device is an authentication device in the first network, the authentication device comprising: a receiver arranged to receive from the second authentication device a request for the authentication master key; wherein the processor is arranged to generate the first nonce; the transmitter is arranged to send the first nonce towards the mobile device; the receiver is arranged to receive from the mobile device the second nonce; the processor is arranged to generate the authentication master key using the first and second nonces; and the transmitter is arranged to send the generated authentication master key to the second authentication device.

17. The device according to claim 12, wherein the authentication master key is a Pairwise Master Key.

18. A computer program, comprising computer readable code which, when run on an authentication device, causes the authentication device to perform the method as claimed in claim 1.

19. A computer program, comprising computer readable code which, when run on a mobile device, causes the mobile device to perform the method as claimed in claim 1.

20. A computer program product comprising a non-transitory computer readable medium and a computer program according to claim 18, wherein the computer program is stored on the computer readable medium.

Description

BRIEF DESCRIPTION OF DRAWINGS

[0039] FIG. 1 is a signalling diagram showing an exemplary situation in which a PMK is transferred between entities;

[0040] FIG. 2 is a flow diagram showing exemplary steps;

[0041] FIG. 3 is a flow diagram showing exemplary steps according to a first embodiment;

[0042] FIG. 4 is a signalling diagram showing exemplary signalling according to the first embodiment;

[0043] FIG. 5 is a flow diagram showing exemplary steps according to a second embodiment;

[0044] FIG. 6 is a signalling diagram showing exemplary signalling according to the second embodiment;

[0045] FIG. 7 illustrates schematically in a block diagram an EAPOL-Announcement frame format;

[0046] FIG. 8 illustrates schematically in a block diagram an EAPOL-Announcement-Req frame format;

[0047] FIG. 9 illustrates schematically in a block diagram an exemplary TLV frame format;

[0048] FIG. 10 illustrates schematically in a block diagram a WMN-Notification Action frame;

[0049] FIG. 11 illustrates schematically in a block diagram a WMN-Notification Action frame having vendor specific formatting;

[0050] FIG. 12 illustrates schematically in a block diagram an exemplary authentication device in a first network;

[0051] FIG. 13 illustrates schematically in a block diagram an exemplary mobile device; and

[0052] FIG. 14 illustrates schematically in a block diagram an exemplary authentication device in a second network.

DETAILED DESCRIPTION

[0053] When a mobile device that is already attached to a 3GPP network attaches to a WLAN network (either instead of or in addition to being attached to the 3GPP network), it must be authenticated in the WLAN network. However, this places a signalling and processing burden on backend servers such as the AAA server and the HSS and causes a delay before the mobile device can start to use the WLAN network. It is proposed to allow the WLAN AC to obtain authentication credentials that have been used in the 3GPP network, for example from an MME. The authentication credentials include the PMK used when authenticating the mobile device in the 3GPP network.

[0054] In order to achieve this, an interface is set up between the ROKH (in this example, the WLAN AC) and the MME. This interface is used to transfer the PMK from the MME to the ROKH when the mobile device attempts authentication in the WLAN network. FIG. 1 is a signalling diagram showing a mobile device 1, an AP 2, an AC 3 and an MME 4. The following numbering corresponds to that of FIG. 1.

[0055] S1. The mobile device 1 is authenticated in a 3GPP network and provided with information identifying primary authentication information (PAIR) used to authenticate the device in the 3GPP network. The PAIR comprises an MME identifier and a UE context identifier used in the MME. When the mobile device 1 is attached in the 3GPP network, the PMKROName is provided to the mobile device 1. A possible way to do that is making use of the Security Mode Command procedure, which can be executed at initial 3GPP Attach, but could also be invoked at a later point. Other options including the PMKROName in the Attach accept or authentication messages or in Tracking/Routing Area Accept messages. The last option has the advantage that in case the mobile device 1 moves into coverage of a new MME/SGSN, the new PMKROName will be assigned when that event happens. Further options are to include the PMKROName in RRC messages sent from the eNB to the STA (e.g., RRC Connection Setup). The

[0056] S2. The mobile device 1 receives a Beacon frame revealing (among other parameters) the security features associated with the BSS/ESS the AP 2 belongs to. The format of the beacon frame as well as all the information elements it carries are described in Chapter 8.3.3.2 of IEEE 802.11;

[0057] S3 If the mobile device 1 does not receive a Beacon frame, it generates a Probe Request and sends it to the AP 2. This procedure is called active scanning and by performing it, the mobile device 1 can receive from the AP 2 the same information as it would have from a Beacon message. The Probe Request frame is described in Chapter 8.3.3.9 of IEEE 802.11.

[0058] S4. The AP 2 answers with a Probe Response.

[0059] S5. The mobile device 1 sends an Authentication Request to the target AP 2, the request including the PAIR.

[0060] S6. The AP 2 requests the PMK-R1 from the default ROKH and sends the PAIR. The ROKH is the AC 3. The AC 3 locates the correct MME using the MME identifier part of the PAIR.

[0061] S7. The ROKH (in this case the AC 3) requests the PMK from the MME 4, including the UE context identifier used in the MME (part of PAIR). The PMK is identified by the the UE context identifier in the MME 4 (again as informed by the mobile device 1 in S5).

[0062] S8. The MME 4 derives the PMK using K.sub.ASME and other parameters and provides the PMK to the AC 3;

[0063] S9. The ROKH computes the PMK-R1 to be used and provides it to the AP 2.

[0064] S10. The AP 2 then responds to the mobile device 1 with an Authentication Response, indicating the FTAA, the RSNE, the MDE and the FTE (which in this case carries also the Authentication Nonce, ANonce, and the ROKH-ID).

[0065] S11. The mobile device 1 re-associates with the target AP 2 within the allowed Re-association Deadline Time, sending a Re-association Request.

[0066] S12. The target AP 2 responds with a Re-association Response.

[0067] S13. The 802.1X controlled port is unblocked and the mobile device 1 can successfully transmit (encrypted) data with the target AP 2.

[0068] S14. The mobile device 1 transmits data over the WLAN.

[0069] The MME 4 generates the PMK from the K.sub.ASME of the currently active EPS security context or from an inactive native EPS security context. The generation is done by applying a key derivation function to the K.sub.ASME.

[0070] The signalling flow of FIG. 1 is one example where a PMK may be transferred between entities (in this case from the MME 4 to the ROKH, in this example the AC 3). As mentioned above, this is a security risk as the authentication and communication privacy could be compromised by a malicious third party.

[0071] In order to address this issue, it is proposed that each time a PMK must be exchanged between network entities (e.g., between the MME 4 and the ROKH 3) a new PMK is derived. In order to achieve this, both the network entity that holds the PMK (e.g., the MME 4) and the mobile device 1 provide arbitrary random input for the derivation of the new PMK.

[0072] FIG. 2 is a flow diagram showing exemplary steps for deriving a new PMK when it is to be exchanged between network entities. The following numbering corresponds to that of FIG. 2.

[0073] S15. A mobile device 1 or authentication device such as an MME 4 generates a PMK using a first nonce generated by the authentication device and a second nonce generated by the mobile device 1.

[0074] S16. The newly generated PMK is sent by the authentication device to a second authentication device in a second network, such as an AC 3 in the case where the mobile device is already authenticated in a 3GPP network and wishes to be authenticated in a WLAN served by the AC 3.

[0075] S17. The second authentication device uses the received PMK to authenticate the mobile device 1.

[0076] An advantage of the steps described above is that, even though an existing PMK has been generated for authentication in the 3GPP network, a “fresh” PMK can be generated independently at the mobile device 1 and the MME 4, and provided to the AC 3. This allows the AC 3 to authenticate the mobile device 1 without needing to send the original 3GPP PMK to the AC 3.

[0077] Two exemplary embodiments are described below. It will be appreciated that the principles described above may be implemented in other ways.

[0078] In the first embodiment, the steps shown in FIG. 1 are used, with some alterations. No new signalling is required compared to the signalling of FIG. 1. In the second embodiment, additional signalling is introduced between the entity that holds the PMK (the MME 4) and the mobile device 1. Both embodiments are described below using the mobile device 1 and the MME 4 as an example in which the PMK is to be sent from the MME 4 to the ROKH (in this case the AC 3) in the network that is to authenticate the mobile device 1. The skilled person will realise that the same techniques may be applied whenever there is a need to communicate a PMK between network entities, for example, from the ROKH to the MME 4, or between different ROKHs (in an example in which the mobile device 1 wishes to authenticate in a further WLAN).

[0079] FIG. 3 shows exemplary steps for the first embodiment. The following numbering corresponds to that of FIG. 3:

[0080] S18. The MME 4 receives a request for a PMK from the AC 3. The request includes a nonce generated by the mobile device 1.

[0081] S19. The MME 4 generates a nonce and a fresh PMK using the generated nonce and the nonce generated by the mobile device.

[0082] S20. The MME 4 sends the fresh PMK to the AC 3 for use by the AC in authenticating the mobile device 1 in the WLAN. The nonce generated by the MME 4 is also sent to the mobile device 1, allowing the mobile device 1 to derive the PMK during the authentication procedure.

[0083] FIG. 4 is a signalling diagram showing exemplary signalling. The following numbering corresponds to that of FIG. 4.

[0084] S21-S25. These steps are the same as steps S1-S5 in FIG. 1. The Authentication Request in step S25 includes SNonce.

[0085] S26. The AP 2 requests the PMK-R1 from the default ROKH 3 and sends the PAIR. The ROKH is the AC 3. The AC 3 locates the correct MME using the MME identifier part of the PAIR. (as informed by the mobile device 1 in step S25). The AP 2 also sends the SNonce received from the mobile device 1 to the AC 3.

[0086] S27. The ROKH (in this case the AC 3) requests the PMK from the MME 4, including the UE context identifier used in the MME (part of PAIR). The PMK is identified by UE context identifier in the MME 4 (again as informed by the mobile device 1 in step S25). The AC 3 also sends the mobile device SNonce to the MME 4.

[0087] S28. The MME 4 generates an ANonce. Based on the received SNonce, the generated ANonce and the PMK, the MME derives a “fresh” PMK.

[0088] S29. The MME 4 provides the fresh PMK to the AC 3 and also sends the ANonce.

[0089] S30. The ROKH 3 computes PMK-R1 to be used and provides it to the AP 2. The AC 3 also relays the ANonce to the AP 2.

[0090] S31. The AP 2 responds to the mobile device 1 with an Authentication Response, indicating the FTAA, the RSNE, the MDE and the FTE (which in this case carries also the Authentication Nonce, ANonce, and the ROKH-ID). Note that the ANonce in this message is the same ANonce that the was generated by the MME 4 and relayed to the AP 2 via the AC 3.

[0091] S32. The mobile device 1, having the SNonce, the ANonce and the original PMK, derives the same fresh PMK as the MME 4.

[0092] S33. The mobile device 1 re-associates with the target AP 2 within an allowed Re-association Deadline Time, sending a Re-association Request.

[0093] S34 The target AP 2 responds to the mobile device 1 with a Re-association Response.

[0094] S35 The 802.1X controlled port is unblocked and the mobile device 1 can successfully exchange (encrypted) data with the target AP 2.

[0095] S36 The mobile device 1 is successfully transmitting data over WLAN.

[0096] An advantage of the procedure of the first embodiment is in the reuse of the messaging of FIG. 1, which eliminates the need to introduce and implement new communication exchanges between the mobile device 1 and the MME 4.

[0097] Considering now the second embodiment, additional communication between the mobile device 1 and the MME 4 is introduced in order to generate a fresh PMK. FIG. 5 is a flow diagram showing exemplary steps. The following numbering corresponds to that of FIG. 5:

[0098] S37. The authentication device (the MME 4 in this example) receives a request for the PMK from a second authentication device (in this example, the AC 3 controlling the WLAN that the mobile device 1 wishes to be authenticated in).

[0099] S38. The authentication device generates an authentication device nonce.

[0100] S39. The authentication device nonce is sent to the mobile device 1.

[0101] S40. The mobile device generates a mobile device nonce.

[0102] S41. The mobile device generates a fresh PMK using the authentication device nonce, the mobile device nonce and the original PMK.

[0103] S42. The mobile device 1 sends the mobile device nonce towards the authentication device 4.

[0104] S43. The authentication device 4 generates the fresh PMK using the authentication device nonce, the mobile device nonce and the original PMK.

[0105] S44. The fresh PMK is sent to the AC 3 for use in authenticating the mobile device 1 in the WLAN network.

[0106] FIG. 6 is a signalling diagram showing exemplary signalling for the second embodiment when authenticating the mobile device in a WLAN network when the mobile device 1 is already authenticated in the 3GPP network. The following numbering corresponds to that of FIG. 6:

[0107] S45. The same signalling as steps S1 to S7 shown in FIG. 1 is carried out.

[0108] S46. The MME 4 determines that the PMK the AC 3 is requesting has already been used and it is a security threat to use it again. The MME 4 triggers a procedure for the derivation of a “fresh” PMK by generating an MME_Nonce (an arbitrary random number);

[0109] S47. The MME sends a “PMK Renewal Request” towards the mobile device, the request including the MME_Nonce;

[0110] S48. The AC 3 relays the request to the AP 2.

[0111] S49. The AP 2 relays the “PMK Renewal Request” to the mobile device 1.

[0112] S50. The mobile device 1 generates a STA_Nonce (another arbitrary number) and computes a new “fresh” PMK based on the received MME_Nonce and the generated STA_Nonce.

[0113] S51. The mobile device 1 sends a “PMK Renewal Response”, including the MME_Nonce and the STA_Nonce;

[0114] S52. The AP 2 relays the “PMK Renewal Request” to the AC 3.

[0115] S53. The AC 3 relays the “PMK Renewal Request” to the MME 4.

[0116] S54. The MME 4 derives the same new “fresh” PMK as the mobile device 1, using on the STA_Nonce and the MME_Nonce).

[0117] S55. The same signalling as steps S8 to S14 shown in FIG. 1 is carried out.

[0118] The procedure shown in FIG. 6 could be imitated by the MME 4 on a need basis. The MME may take a decision on when this procedure should be used. In that case, one possible implementation would be to re-use the procedure shown in FIG. 4, reusing the same security key for a certain amount of time (or number of times the PMK has been used). In that case the MME 4 could, for example, keep state of the amount of time (or the number of times) that a particular mobile device 1 has used the same key and if this time (or number of times) is larger than a certain threshold, the MME 4 could initiate the procedure for renewal of the security key.

[0119] The signalling in steps S48 to S52 could use different protocols. For example, this signalling could use existing Extensible Authentication Protocol Over LAN (EAPOL) messages, some other WLAN-specific protocol such as Wireless Network Management (WNM)-Notification frames or Non-Access Stratum (NAS) messages.

[0120] Where EAPOL messages are used, the EAPOL-Announcement and the EAPOL-Announcement-Req can be used. The formats of both frames are shown in FIGS. 7 and 8. The Type Length Value (TLVs) fields are of type 127 (“Organizationally Specific TLVs” as described in Chapter 11.12 of IEEE 802.1X). The organization specific formatting is shown on FIG. 9. In this frame, the “Organizationally defined information string” field includes placeholders for transporting the MME_Nonce and the STA_Nonce. In this example, steps S48 and S49 of FIG. 6 use an EAPOL-Announcement-Req, and steps S51 and S52 of FIG. 6 use an EAPOL-Announcement. The “PMK Renewal Response” messages may be carried using proprietary signalling or over-the-top.

[0121] Alternatively, the signalling between the mobile device 1 and the MME 4 may be implemented using IEEE 802.11 WNM-Notification frames. A WNM-Notification Action frame is shown in FIG. 10. The “Optional Subelement” field shown in FIG. 10 is formatted as a “Vendor specific element”. The resulting frame formatting is shown in FIG. 11. The “Vendor-specific content” field shown in FIG. 11 includes placeholders for transporting the MME_Nonce and the STA_Nonce. In this example, the messages of steps S48 and S49 of FIG. 6 are carried using a WNM-Notification Request, and steps S51 and S52 of FIG. 6 are carried out using a WNM-Notification Response. The “PMK Renewal Response” messages may use a proprietary signalling protocol or be sent over-the-top.

[0122] The examples above all assume that the mobile device 1 is authenticated in a 3GPP network and is subsequently authenticated in a WLAN. It will be appreciated that the same principles can be used when the mobile device is authenticated in a WLAN and subsequently requires authentication in a 3GPP access network. For example, the MME 4 may implement ROKH functionality. In this case, when the mobile device 1 authenticates in a WLAN, the PMK is provided by the HSS to the MME. When the mobile device subsequently attempts to connect to a 3GPP network and requires authentication, the PMK can be re-used. The mobile device sends an attach request to the MME 4 containing the IMSI (or an identity that can be mapped to the IMSI) and the identity of the mobile device 1. The MME 4 sends a RAND and AUTN to the mobile device, which computes a response (RES) to the RAND using the USIM. The RES is returned to the MME 4 which verifies that the RES matches an expected RES. If so, then the mobile device 1 is considered to be authenticated and the MME 4 starts a security mode procedure based on K.sub.ASME. The mobile device 1 calculates K.sub.ASME from the RAND using the USIM and response to the MME. The MME 4 then sends an attach accept message to the mobile device 1 confirming that the mobile device is now authenticated in the 3GPP network.

[0123] In an alternative embodiment in which the mobile device 1 is authenticated with a WLAN and wishes to attach to a 3GPP network, the MME 4 holds the PMK. The mobile device 1 sends an attach request to the MME 4. The attach request contains the identity of the mobile device 1 and the IMSI (or an identifier that can be mapped to the IMSI by the MME 4). The MME 4 sends an attach accept message to the mobile device 1, confirming that the mobile device 1 is authenticated in the 3GPP network.

[0124] It will also be appreciated that the same principles may be used with any other types of network using suitable RATs.

[0125] Referring to FIG. 12 herein, there is illustrated schematically an exemplary first authentication device 4 for use in the first network. Examples of such an authentication device include an MME 4 where the first network is a 3GPP network, or an AC where the first network is a WLAN network. The first authentication device 4 is provided with a processor 5 arranged to generate the authentication master key (such as a PMK) associated with the mobile device 1 using a first nonce generated by the authentication device 4 in the first network, and a second nonce generated by the mobile device 4. A receiver 6 is provided that is arranged to receive a request for the authentication master key, the request including the second nonce generated by the mobile device, and a transmitter 7 is provided that is arranged to send the generated authentication master key towards a second authentication device in the second network.

[0126] A non-transitory computer-readable medium in the form of a memory 8 is provided that can be used to store a computer program 9 which, when executed by the processor 5, causes the processor 5 to perform the steps described above. Note that the computer program may be provided on an external non-transitory computer readable medium 10, or on a carrier signal.

[0127] In the example of FIG. 12, the authentication device generates the authentication master key.

[0128] Turning now to FIG. 13, there is illustrated schematically in a block diagram an exemplary mobile device 1. The mobile device is provided with a processor 11 arranged to generate the authentication master key associated with the mobile device 1 using a first nonce generated by an authentication device 4 in the first network, and a second nonce generated by the mobile device 1. A receiver 12 is arranged to receive from the authentication device in the first network the first nonce. The transmitter 13 is arranged to send the second nonce towards the authentication device 4 in the first network, the second nonce being usable by the authentication device in the first network to generate the authentication master key.

[0129] A non-transitory computer-readable medium in the form of a memory 14 is provided that can be used to store a computer program 15 which, when executed by the processor 11, causes the processor 11 to perform the steps described above. Note that the computer program may be provided on an external non-transitory computer readable medium 16, or on a carrier signal.

[0130] Turning now to FIG. 14, there is illustrated a second authentication device for use in the second network. In the example where the first network is a 3GPP network and the second network is a WLAN network, the second authentication device may be an AC 3. Note, however, that the first network may be a WLAN network and the second network may be a 3GPP network, in which case the second authentication device may be an MME 4. Other types of network are also possible. In this example, the second authentication device is assumed to be an AC 3.

[0131] The second authentication device 3 is provided with a receiver 17 arranged to receive a generated authentication master key from the first network authentication device 4 or a second nonce from which the authentication master key can be generated. A processor 18 is provided, arranged to use the generated authentication master key to authenticate the mobile device 1 in the second network. A transmitter 19 may be provided, which is arranged to, prior to receiving the generated authentication master key, send to the first network authentication device mobile a request for the authentication master key.

[0132] A non-transitory computer-readable medium in the form of a memory 20 is provided that can be used to store a computer program 21 which, when executed by the processor 18, causes the processor 18 to perform the steps described above. Note that the computer program may be provided on an external non-transitory computer readable medium 22, or on a carrier signal.

[0133] By generating a fresh PMK when a second authentication device wishes to authenticate the mobile terminal 4, the security risk of sending a PMK from an MME 4 to an ROKH (such as an AC 3), or between ROKHs, is minimized.

[0134] It will be appreciated by the person of skill in the art that various modifications may be made to the above-described embodiments without departing from the scope of the present invention. For example, the above description gives the example of sending a fresh PMK from an MME to an AC, but it will be appreciated that the same techniques may be used whenever it is required to send a PMK between devices over a communication network regardless of the RAT of the first network and the second network.

[0135] The following abbreviations have been used in the above description:

[0136] 3GPP 3rd Generation Partnership Project

[0137] AAA Authentication, Authorization and Accounting

[0138] AC Access Controller

[0139] AP Access Point

[0140] AKA Authentication and Key Agreement

[0141] AuC Authentication Centre

[0142] AV Authentication Vector

[0143] EAP Extensible Authentication Protocol

[0144] EAPOL EAP over LAN

[0145] eNB eNodeB

[0146] GTK Group Temporal Key

[0147] HLR Home Location Register

[0148] HSS Home Subscriber Server

[0149] IMSI International Mobile Subscriber Identity

[0150] LAN Local Area Network

[0151] LTE Long Term Evolution

[0152] MME Mobility Management Entity

[0153] NAS Non-Access Stratum

[0154] NH Next Hop

[0155] NCC Next Hop Chaining Counter

[0156] PMK Pairwise Master Key

[0157] PTK Pairwise Temporal Key

[0158] RBS Radio Base Station

[0159] SMS Short Message Service

[0160] STA Station

[0161] UE User Equipment

[0162] USIM Universal Subscriber Identity Module

[0163] WLAN Wireless Local Area Network

[0164] WNM Wireless Network Management