MOBILE APPLICATION AND INTERFACE FOR A SMART CARD READER

Transcription

1 MOBILE APPLICATION AND INTERFACE FOR A SMART CARD READER PROJECT INDEX: PRJ026 BY KABUBA DENNIS GACHUGU. F17/1764/2006. SUPERVISOR:DR. J. MBUTHIA. EXAMINER: DR. G.S.O ODHIAMBO. 18 TH MAY 2011.

2 OBJECTIVES Design of a mobile application Implementation of the mobile application Interface of a mobile device with a peripheral device Creation of a central database using SQLite Query the database using one of the fields and retrieve its corresponding record.

3 INTRODUCTION The mobile device chosen was a Huawei IDEOS U8150 Android mobile application platform was chosen The chosen card reader was ASEDIIIe smart card reader.

4 The android platform. Android is the product of the Open Handset Alliance formed to create a better phone with open source software. First android phone released in OHA consists of over 80 members from device manufacturers to phone marketers. Android is a layered environment build upon a linux v2.6 kernel.

5 Android architecture.

6 Smart cards. A smart card is a plastic card which has an integrated circuit embedded with components for storing, transmitting and processing data. Data transmitted using either contact on the cards surface or through EMF fields in contactless cards. Data transmission mode defined by ISO standard ISO standard.

7 Smart card architecture.

8 ISO standard. Defines the content and structure of data commands that are transmitted to and received from the card. Communication consists in sending a command, processing it in the receiving protocol and receiving a response. A data record, unit or object is sent and the card waits for an ATR and protocol selection. A specific command generates a specific response.

9 standard. An APDU consists of a command or a response message sent to or received from a card reader. Both the command and response message may contain data resulting in four outcomes. The message body consists of a sequence of bytes which forms the instruction to and from the card acceptance device.

10 Smart card uses. In mobile telephony. In mass transit system as ID cards. Online identification for internet shopping. Loyalty cards in supermarkets. Access cards to sensitive areas e.g. server room. In financial industry as credit cards.

11 Android application structure. Android applications are composed of activities which are loosely bound by the declared resources. Each user interface / new screen in the application has to be defined by a new activity. Intents used to launch activities. Unlike other platforms, processes are just containers for activities.

12 Application design. The application was designed to contain a central database, a user interface and a query method. SQLite, a tiny but powerful open-source SQL which stores records in a file and is embedded on the android platform created the database. Xml mark-up language, embedded in android, was used to create the user interfaces in the whole application.

13 Application flowchart.

14 Application algorithm. Sequence of execution. Main menu screen called by an intent. Since a smart card reader was not available, the input data stream was assumed to be an entry in one of the fields. The user selects the query database option. A text box appears asking the user to enter the search field. If the record is found, the record is displayed.

15 The maintained database.

16 Results.

17 Conclusion. A central database was maintained containing sample records with four fields. A record of personal details was retrieved from the database and displayed using a single field. A wrong search entry produced no corresponding record.

18 Future work. USB accessory mode was recently announced by Google. This allows android-powered devices to connect to USB host hardware specifically designed for them. The

19 The end. Thank you!!!!