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.

PROXY BASED AUTHENTICATION LOCALISATION SCHEME FOR HANDOVER<br />

where f is a message authentication function that is only known to the MH and its<br />

HAAA. The HAAA encrypts the FAT contents as listed <strong>in</strong> Equation 6.1 us<strong>in</strong>g the secret<br />

key K hp shared with the correspond<strong>in</strong>g FAP. After every AN on the neighbour access<br />

network list has been produced a FAT, the HAAA builds up an encrypted FAT Vector<br />

(FATV):<br />

EK hm<br />

( FATV[<br />

FAT , IDp1,<br />

FAT2<br />

, IDp<br />

2 ,..., FATt<br />

, ID<br />

1 pt<br />

which <strong>in</strong>cludes every FAT and the correspond<strong>in</strong>g FAP’s identity ID p . The FATV is<br />

protected by the key K hm shared between the MH and its HAAA. Then, the encrypted<br />

FATV is <strong>in</strong>cluded <strong>in</strong> a FAT Response message, and sent back to the MH as shown <strong>in</strong><br />

Figure 6.4. The encryption us<strong>in</strong>g the PSK K hm makes sure that the FATV would not be<br />

disclosed to other parties (<strong>in</strong>clud<strong>in</strong>g the sAN), and only the MH can view it. Although<br />

the MH can decrypt the encrypted FATV, it is unable to learn the contents of <strong>in</strong>dividual<br />

FAP. Each FAT is encrypted with a key ( K hp ) that is only known to the HAAA and the<br />

FAP that it is generated for. Neither the MH nor the sAN can modify the received<br />

FAT’s contents. Once the FAT response is received, the MH <strong>in</strong>crements its SQN m<br />

counter by 1.<br />

MH sAN<br />

HAAA<br />

FAT Request<br />

EK hm<br />

FAT Response<br />

FATV [ FAT , ID , FAT , ID<br />

Initial full authentication via sAN<br />

( Nm<br />

)<br />

EK hm<br />

- 122 -<br />

( Nm<br />

) ,<br />

])<br />

FAT Request<br />

NAN ,...,<br />

�AN , AN AN �<br />

_ IDs<br />

1 2<br />

FAT Response<br />

FATV [ FAT , ID , FAT , ID<br />

, ..., FAT , ID<br />

EK ( hm<br />

1 p1<br />

2 p2<br />

t p3<br />

, ..., FAT , ID<br />

EK ( h<br />

1 p1<br />

2 p2<br />

t p3<br />

Figure 6.4 Fast authentication ticket <strong>generation</strong> procedure<br />

The consequence of the fast authentication ticket <strong>generation</strong> is that a FAT will be<br />

produced for every nearby access network before a handover execution. Note that only<br />

])<br />

t<br />

])

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

Saved successfully!

Ooh no, something went wrong!