Mobile Interactive Stockbroking

1
Mobile Interactive Stockbroking

• Final Year CSE Project
• Group 99P
• July 1999

2
Introduction

• Project Overview
• System Architecture
• Design Details
• Security Issues
• Final Remarks

3
Project Overview

• What is our project about
• Goals
• Motivation
• Why it has not been done before
• Deliverables
• Software
• Documents

4
System Architecture

• System Breakdown
• Server
• Mobile Phone
• SIM Card
• Smart Card

5
Sub-System Responsibilities

• Server
• Mobile Phone
• SIM Card
• Smart Card

6
Sub-System Allocation

• Daniel Attema
• Ashley Roberts
• David Liddle

7
User Classes

• Mobile Phone Users
• System Operators
• Stock Updater (Virtual User)

8
Server Application

• Server Elements
• Database System Elements
• User Elements
• Communication Elements

9
Server Package Diagram
Database
Client
Database
Updater
Controller
Operator
Transaction
Controller
Control
Database System Elements User Elements
Communication Elements
Network
Security
Interface
10
Database System Elements

• Database Package
• Data Manager
• Database Transaction Control
• Storage Control
• Transaction Control Package

Storage Control
Data Manager
Database Transaction Control
Transaction Control
11
User Elements

• System Operator Elements
• Requirements
• Listener task
• Control task

• Mobile Phone User Elements
• Requirements
• Client Control
• Message Routing
• Cleanup

12
Message Routing forMobile Phone Users
Client Control Loop
Message Router
3
2
4
Network Interface
1
5
Mobile Phone
13
Communication Elements

• Hardware / Network Interface
• Cellsite Simulator (Hardware)

14
SIM Card Application

• Command Interpretation / Execution
• Implementation
• Java based development environment
• Small subset of Java

15
Communication Security

• What does Security require?

• Hiding what you are doing from other people

16
Implementing Security

• Hiding what you are doing from other people
• Cryptography
• Different symmetric encryption keys used each
  session
• Symmetric keys are encrypted using Public Key
  encryption

17
Communication Security

• What does Security require?
• Others cannot alter your messages

Buy 10
Buy 1000
18
Implementing Security

• Others cannot alter your messages
• Sign messages with your Private Key
• A signature is created for each message
• The signature can only be created by the private
  key and verified by the public key
• If the signed message is altered then the
  signature will not longer match, so is rejected

19
Communication Security

• What does Security require?
• No-one can impersonate you or the server

20
Implementing Security

• No-one can impersonate you or the server
• Identification
• Using Public Key Cryptography
• If the client can decrypt and verify the messages
  using the servers public-key then the messages
  came from the real server.
• Similarly, the server can recognize the client by
  its messages

21
Communication Security

• What does Security require?
• Others cannot resend your messages

22
Implementing Security

• Others cannot resend your messages
• Each message contains a number
• Each message has a number one more than the
  previous
• The starting number is randomly chosen at the
  start of each session
• If a message contains a number which is not the
  one expected, then the message is rejected.

23
Security Summary

• Other people cannot
• Read your messages
• Alter your messages
• Impersonate you or the server
• Resend your messages

24
Final Remarks

• Project Completion
• Progress
• Documents
• Software

25
Final Remarks

• Any Questions

26
Black Slide