Sam Chow

1
C.O.P.S. by Omega Team

• Sam Chow
• Rachel Mueller
• Cedric Tasselin

2
The Problem. . .
How can a person conveniently protect files and
processes, secure email, and maintain privacy on
a personal computer?
3
Our Solution. . .
Automate a screen lock on the PC using a
proximity sensor
4
System Requirements

• Hardware to identify user and interface to PC
• Software to implement screen lock

5
Hardware Requirements(Identification System)

• Little or no interaction from the user
• Fast
• Limited read range
• Inexpensive
• Able to interface to PC

6
Software Requirements

• Communicate with identification system
• Implement screen lock

7
User Identification Possibilities

• Swipe cards
• Voice recognition
• Biometric systems
• Wireless transmitter / receiver
• Infrared
• Microwave
• Radio

8
Specifications Hardware

• Reader
• Operating frequency of 134.2 kHz
• Read time of 70 ms
• Interface to host PC (RS-232)
• Transponder
• Card, keyring
• Reading range of 2 feet
• Lightweight
• Data Transmission
• ASCII protocol
• Secure (must be hard to reproduce / mimic ID)

9
Specifications Software

• Easy to use installation program on Windows
  system
• Ability to define valid IDs for a given system
• Grant / deny access for valid / invalid IDs
• Customizable options for read time(s)
• Ability to lock-out keyboard and mouse functions
  when system is locked
• Provide a password feature for added security
• Ability to manually deactivate system if
  transponder is lost or damaged
• Help documentation provided

10
The Big Picture

• Our solution
• Hardware implementation using the TIRIS low
  frequency evaluation kit
• RFID reader with RS-232 interface
• Various transponders
• Antenna
• Custom software
• Developed using Microsoft Visual Basic
• Windows 95/98/ME compatible

11
TIRIS

• Why TIRIS?
• System matches many of our requirements
• RS-232 interface
• Transponder read ranges
• ASCII and TIRIS bus protocol
• Portability
• Security

12
Security

• How to prevent transponder ID from being stolen
  and / or duplicated?
• TIRIS implementation
• Read-Only transponders are programmed with a
  64-bit identification code.
• Also contain hard-coded header and trailer codes
  on each transponder
• Reader system monitors BOTH 64-bit code AND
  header and trailer codes

13
C.O.P.S. Control Center

• The C.O.P.S. Control Center is a custom software
• application created with Microsoft Visual Basic
  that
• interfaces with the TIRIS S2000 Reader through
  the
• serial port and that is responsible for locking
  and
• unlocking the screen when an authorized /
• unauthorized transponder is detected. The
  program
• also contains certain configurable parameters
  such as
• password protection for added security.

14
C.O.P.S. Control Center

• Standard, Familiar Installation Program

15
C.O.P.S. Control Center

• Password Protected Logon
• Allows User To Change Password

16
C.O.P.S. Control Center

• Configurable COM
• Port, Read Delay,
• Idle Delay
• One-Button
• Activation /
• Deactivation

17
C.O.P.S. Control Center

• Saves Customization In Windows Standard INI File
• Simple Encryption Algorithm For Password And
  Transponder Response

18
C.O.P.S. Control Center

• Explanation Of Screen Lock / Unlock Process
• COM Port The Reader Is Connected To Is Opened
• Single Read Character X Is Sent To The Reader
  Every Specified Number Of Seconds (Read Delay)
• Reader Response String (R Followed By Digits)
  Is Parsed For Authorized Transponder ID

19
C.O.P.S. Control Center

• Explanation Of Screen Lock / Unlock Process
  (Continued)
• If Authorized Transponder Is Present Screen Is
  Unlocked (Fast Task, Task Bar, and Peripherals
  Disabled) And Timer Interval Is Set To Idle Delay
  Before Reading Again
• System Can Be Manually Deactivated By The Same
  Logon Password

20
Project Planning / Timeline
21
Project Testing

• Testing is split into three phases
• Hardware Testing
• Software Testing
• System Integration

22
Test Plan Hardware
Test Function Result
1. Successful transmission/reception of data between transponder and software? Yes
2. Successful transmission/reception of data for ALL transponder types? Yes
3. Are transponder reading ranges acceptable? No
23
Test Plan Hardware, cont.
Transponder Type Read Range (in.)
Badge 2.5
Key-ring 5.7
Disk 1.8
Glass 6.2
Cylinder 12
Metal 6.3
24
Test Plan Software
Test Function Result
Successful synchronization b/w transponder and software? Yes
System access granted for valid transponder(s)? Yes
System locked for invalid transponder(s)? Yes
Successful changing of read/idle times? Yes
25
Test Plan Software, cont.
Test Case Result
Idle/read times occur at correct intervals? Yes
Keyboard functions locked? Yes
Mouse Functions locked? Yes
26
Test Plan System Integration
Test Function Result
Successful program setup execution? Yes
Other programs execute while locked? Yes
Error messages displayed when hardware conflicts encountered? Yes
27
Bug Report
A

• If 2 or more transponders are in the read range,
  the system will lock/remain locked.
• No matter what the idle delay is set as, the
  first read interval will be about 2 s.
• Cannot Sync/Read using the R/W transponders.

28
Ramifications

• Environmental - no batteries
• Health/Safety - low frequency
• Social - positive work environment
• Political - EPIC
• Ethical - privacy concerns
• Manufacturability - software on CD
• Sustainability - easily upgradeable
• Economics - RFID system too expensive

29
C.O.P.S. In The Future

• Manufacture own RFID system (lower costs)
• Provide online documentation
• USB interface
• Other Platforms (Macintosh, Unix, Windows 2000)
• Gate Antenna for increased reading range

30
Special Thanks

• Dr. James Harden
• Dr. Daniel Linder
• Texas Instruments
• Mr. Tony Sabetti