02.11.2012 Views

Handover mechanisms in next generation heterogeneous wireless ...

Handover mechanisms in next generation heterogeneous wireless ...

Handover mechanisms in next generation heterogeneous wireless ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

SECURITY FOR HANDOVER ACROSS HETEROGENEOUS WIRELESS NETWORKS<br />

authenticator controls communications <strong>in</strong>to and out of the wired network, and acts as a<br />

protocol divid<strong>in</strong>g po<strong>in</strong>t [40]. As a result, the communications between the authenticator<br />

and the authentication server can use a standard protocol, e.g. Extensible Authentication<br />

Protocol (EAP) [18], to carry authentication messages. The protocols for<br />

communications between the authenticator and the supplicant may vary accord<strong>in</strong>g to the<br />

type of access technology <strong>in</strong>volved. For example, IEEE standard 802.1x [17] can be<br />

employed for a IEEE 802.11 WLAN to do a four-way handshake exchange between a<br />

STA and an Access Po<strong>in</strong>t (AP). With the mediat<strong>in</strong>g of an authenticator, the<br />

authentication across <strong>heterogeneous</strong> <strong>wireless</strong> systems is supported.<br />

Authorisation<br />

Authorisation is the process of grant<strong>in</strong>g a particular privilege for the access to a service<br />

or <strong>in</strong>formation based on a user’s presented credential. While authentication attempts to<br />

establish a level of confidence that a certa<strong>in</strong> th<strong>in</strong>g holds true, authorisation decides what<br />

a user is allowed to do. For example, a mobile user purchases a pre-paid SIM card that<br />

is supposed to <strong>in</strong>clude the credits for 60 m<strong>in</strong>s phone calls. Every time the user requests<br />

to make a phone call, the network must check to see whether there is sufficient credit<br />

left on the user’s account before allow<strong>in</strong>g the user to connect. The decision on<br />

authorisation may be restricted by a number of factors: e.g. key lifetimes, Service Set<br />

Identifier (SSID) restrictions, called-station-ID restrictions suggested for IEEE 802.11<br />

<strong>in</strong> [43].<br />

A simple authorisation process is described as follows. Upon receiv<strong>in</strong>g the request for<br />

access attachment, the network operator first consults an authorisation server that holds<br />

user profiles. A good example of the authorisation server is the Home Location Register<br />

(HLR) <strong>in</strong> a GSM network. Then, the network makes a decision on whether the user is<br />

authorised to use the service it has requested. Authorisation requests are processed after<br />

the user has been authenticated. It makes sense that both authentication and<br />

authorisation functions could be implemented <strong>in</strong> the same server.<br />

The authorisation example shown above assumes that the access request is made<br />

through a network that is adm<strong>in</strong>istered by the same network operator. In a more<br />

complex case, the mobile user may be served by a foreign network operator. This<br />

- 35 -

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!