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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

SECURITY FOR HANDOVER ACROSS HETEROGENEOUS WIRELESS NETWORKS<br />

table is consulted by Diameter agents to f<strong>in</strong>d the message dest<strong>in</strong>ation or the <strong>next</strong> AAA<br />

hop that may reside <strong>in</strong> other realms.<br />

A Diameter node can process a request message locally, or forward the message<br />

accord<strong>in</strong>g to the f<strong>in</strong>al dest<strong>in</strong>ation of that message. The Local Action value of the realm<br />

rout<strong>in</strong>g entry <strong>in</strong> a Diameter node determ<strong>in</strong>es how a message with a specific Dest<strong>in</strong>ation-<br />

Realm AVP is processed. The Diameter base protocol [62] def<strong>in</strong>es four types of actions<br />

that can be imposed on a message: Local, Relay, Proxy and Redirect. It is noted <strong>in</strong> [62]<br />

that Diameter agents must support at least one of the Local, Relay, Proxy and Redirect<br />

modes of operation, but do not support all modes of operation.<br />

Diameter def<strong>in</strong>es relay, proxy, and redirect agents, and requires that agents ma<strong>in</strong>ta<strong>in</strong><br />

transaction state, which is used for failover purposes.<br />

� Relay Agents: accept requests and route messages to other Diameter nodes based<br />

on the Dest<strong>in</strong>ation-Realm of messages. Relay agents can manipulate Diameter<br />

messages through <strong>in</strong>sert<strong>in</strong>g and remov<strong>in</strong>g rout<strong>in</strong>g <strong>in</strong>formation without modify<strong>in</strong>g<br />

any non-rout<strong>in</strong>g AVPs;<br />

� Proxy Agents: route messages us<strong>in</strong>g the realm rout<strong>in</strong>g table as relay agents do.<br />

However, they can modify messages to apply local policies, and add new AVPs to<br />

Diameter messages prior to rout<strong>in</strong>g;<br />

� Redirect Agents: do not route messages, but simply return an answer with the<br />

<strong>in</strong>formation necessary for Diameter agents to communicate directly, without<br />

modify<strong>in</strong>g messages.<br />

As discussed <strong>in</strong> Sec. 3.2, the EAP three-party authentication model is considered as a<br />

standard method to accomplish access control through an AAA protocol <strong>in</strong> modern<br />

<strong>wireless</strong> networks. The Diameter NAS application specification (NASREQ), describ<strong>in</strong>g<br />

the <strong>in</strong>teraction between NAS and Diameter server is standardised <strong>in</strong> IETF RFC 4005<br />

[63]. Along with the Diameter EAP application (RFC 4072) [65], it supports the EAP<br />

authentication through a NAS with a Diameter server. The Diameter NAS application<br />

def<strong>in</strong>es a number of commands and AVPs for authentication and authorisation. The<br />

NAS and Diameter server utilises these commands to conduct operations such as re-<br />

- 54 -

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

Saved successfully!

Ooh no, something went wrong!