Secure e-Payment Portal Solutions Using Mobile Technologies and ...

More documents

Recommendations

Info

3.2 Third Generation Mobile Communications: 3Grather than using proprietary algorithms. Another related improvement arisesfromtheuseoftheKASUMIalgorithn[97][98]fordataciphering (andintegrityprotection) instead of the aging GSM A5/1 algorithm.3.2.3.1 KASUMIKASUMI is one of 3GPP confidentiality and integrity algorithms, which appliesa 64-bit block with an 128-bit key. The process of KASUMI has eightrounds of Feistel ciphers. Each round requires 32-bit input corresponding with32-bit output. KASUMI is not utilised in the proposed system architectureswithin this thesis, therefore for detailed explanation please refer to 3GPP T-S35.202 [98].76
3.2 Third Generation Mobile Communications: 3G3.2.3.2 Authentication and Key Arrangement (AKA) and MILENAGE• An overview of the 3G authentication process in AuC is shown in Figure3.4Figure 3.4: 3G generation of authentication data at AuC/HLR [97]• Anoverview ofthe3GauthenticationprocessinUSIMisshown inFigure3.5In this section the Authentication and Key Arrangement (AKA) is given detailedexplanation,because AKAhasanimportant roleintheproposed systemprotocols in chapter 7.An overview of 3G authentication and key arrangement process is shown inFigure 3.6.77
Page 1 and 2:
Secure e-Payment Portal SolutionsUs
Page 3 and 4:
AcknowledgementsI have taken effort
Page 5 and 6:
PublicationsA number of papers resu
Page 7 and 8:
Contents1 Introduction 161.1 Motiva
Page 9 and 10:
CONTENTS8.3.1 Attack Scenarios . .
Page 11 and 12:
LIST OF FIGURES8.1 NFC m-Payment wi
Page 13 and 14:
Abbreviations2G: Second Generation
Page 15 and 16:
WEP:Wi-Fi:WPA:WWW:Wired Equivalent
Page 17 and 18:
1.1 MotivationNetwork (PAN). PAN te
Page 19 and 20:
1.2 Objectivescurity technology is
Page 21 and 22:
1.3 Organisation of Thesisnecessary
Page 23 and 24:
Chapter 2Background: Near Field Com
Page 26 and 27: 2.2 NFC: BasicsNFC N-Mark:Figure 2.
Page 28 and 29: 2.3 NFC: Specificationsclose to ano
Page 30 and 31: 2.3 NFC: SpecificationsFigure 2.2:
Page 32 and 33: 2.3 NFC: SpecificationsFigure 2.4:
Page 34 and 35: 2.3 NFC: Specificationspearing to a
Page 36 and 37: 2.4 NFC: Mobile Architecture and Se
Page 51 and 52: 2.5 NFC: Applicationscredentials an
Page 53 and 54: 2.5 NFC: ApplicationsFurther exampl
Page 55 and 56: 2.5 NFC: Applicationsyour TV. For d
Page 57 and 58: 2.6 NFC: Security2.6 NFC: SecurityN
Page 59 and 60: 2.6 NFC: Securitytokens.- Data Corr
Page 61 and 62: Chapter 3Background: GSM and 3GCont
Page 63 and 64: 3.1 Global System for Mobile Commun
Page 71 and 72: 3.2 Third Generation Mobile Communi
Page 75: 3.2 Third Generation Mobile Communi
Page 81 and 82: Chapter 4Background: TheCitizenDigi
Page 83 and 84: 4.2 Public Key InfrastructureSignat
Page 85 and 86: 4.2 Public Key Infrastructureproces
Page 87 and 88: 4.2 Public Key Infrastructure4.2.2
Page 89 and 90: 4.2 Public Key Infrastructure4.2.2.
Page 91 and 92: 4.2 Public Key InfrastructureFigure
Page 93 and 94: 4.2 Public Key InfrastructureTable
Page 95 and 96: 4.3 Citizen Digital Certificate: CD
Page 97 and 98: 4.4 Government PKI: GPKICA and GTes
Page 99 and 100: Chapter 5Overview of Mobile Payment
Page 101 and 102: 5.1 IntroductionFigure 5.1 provides
Page 103 and 104: 5.1 Introduction1. Ease-of-use2. Se
Page 105 and 106: 5.1 IntroductionTo overcome these p
Page 107 and 108: graphic primitives, which simplifie
Page 109 and 110: 6.1 Introductionauthentication to t
Page 111 and 112: 6.2 NFC M-PAYMENT SYSTEM BASED ON G
Page 121 and 122: 6.3 PROTOCOL ANALYSISimportant to i
Page 123 and 124: 6.3 PROTOCOL ANALYSIStion. The atta
Page 125 and 126: 6.3 PROTOCOL ANALYSISprocessing and
Page 127 and 128:
6.4 Conclusion6.3.2.2 Disadvantages
Page 129 and 130:
Chapter 7NFC Mobile Payment with 3G
Page 131 and 132:
7.1 Introduction7.1 IntroductionMob
Page 133 and 134:
7.2 NFC M-PAYMENT SYSTEM BASED ON 3
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
7.3 PROTOCOL ANALYSISthat the respo
Page 151 and 152:
7.3 PROTOCOL ANALYSIStomer phone. F
Page 153 and 154:
7.4 Conclusionconnections, while so
Page 155 and 156:
Chapter 8NFC M-Payment with Citizen
Page 157 and 158:
8.1 Introductionmulti-purpose cards
Page 159 and 160:
8.2 NFC M-PAYMENT SYSTEM WITH CDCIn
Page 161 and 162:
8.2 NFC M-PAYMENT SYSTEM WITH CDC8.
Page 163 and 164:
8.2 NFC M-PAYMENT SYSTEM WITH CDCth
Page 165 and 166:
8.2 NFC M-PAYMENT SYSTEM WITH CDCth
Page 167 and 168:
8.2 NFC M-PAYMENT SYSTEM WITH CDCSt
Page 169 and 170:
8.2 NFC M-PAYMENT SYSTEM WITH CDCma
Page 171 and 172:
8.3 PRELIMINARY ANALYSISsame PR are
Page 173 and 174:
8.3 PRELIMINARY ANALYSIS8.3.2 Advan
Page 175 and 176:
8.4 Conclusiona privacy concern tha
Page 177 and 178:
Chapter 9Prototype Implementation o
Page 179 and 180:
9.2 System Overviewa proof-of-conce
Page 181 and 182:
9.4 Nokia 6131- JDK 6u25 windows i5
Page 183 and 184:
9.4 Nokia 6131Thetargettypesvaluess
Page 185 and 186:
9.5 Practical Implementation9.5 Pra
Page 187:
9.5 Practical ImplementationFigure
Page 190 and 191:
9.5 Practical Implementationthe bac
Page 192 and 193:
9.5 Practical ImplementationFigure
Page 194 and 195:
9.5 Practical Implementation(a)(b)F
Page 196 and 197:
9.5 Practical Implementationat the
Page 198 and 199:
9.6 EvaluationFigure 9.21 and 9.22
Page 200 and 201:
9.6 EvaluationFigure 9.24: Statisti
Page 202 and 203:
Chapter 10Overall ConclusionContent
Page 204 and 205:
10.1 ConclusionHowever, by focusing
Page 206 and 207:
10.1 Conclusiontrust mechanism via
Page 208 and 209:
Chapter 11AddendumContents11.1 Addi
Page 210 and 211:
11.1 Additional Information on the
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
BIBLIOGRAPHY[13] Nokia, “Introduc
Page 220 and 221:
BIBLIOGRAPHY[43] Rodolfo Gomes,NXP,
Page 222 and 223:
BIBLIOGRAPHY[68] G. Rose, A precis
Page 224 and 225:
BIBLIOGRAPHY[102] C. Blanchard, Sec
Page 226 and 227:
BIBLIOGRAPHY[130] Government Root C
Page 228 and 229:
BIBLIOGRAPHY[157] “GSM System Ove
show all

Secure e-Payment Portal Solutions Using Mobile Technologies and ...

Create successful ePaper yourself

Delete template?

Save as template?