1 / 7

Illinois Phone

System Architecture. Illinois Phone. Major Components. Windows Phone 7 Mobile Phone Application User – End Perspective Google App Engine Administration Console Handles authentication, user access and relays information Desktop Application Provides the system end gateway for user access.

seanna
Download Presentation

Illinois Phone

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. System Architecture Illinois Phone

  2. Major Components • Windows Phone 7 • Mobile Phone Application • User – End Perspective • Google App Engine • Administration Console • Handles authentication, user access and relays information • Desktop Application • Provides the system end gateway for user access

  3. Structural Architecture XML-RPC

  4. Room Authentication System • QR Code on door contains an encrypted message • Phone takes a photograph and sends encrypted message along with personally identifiable information over encrypted XML-RPC GPS QR Code Device ID

  5. Room Authentication System • Data is sent using a custom encryption protocol that signs the data using the device ID to prevent spoofing of data • Once authorized a reply is sent containing a string and a randomly generated number • String:<message on QR code><random number> • Opens up a time ticket for a specified time (2mins) to allow access to the resources in the room

  6. Room Resource Access • Passcode is received by the desktop client and is allotted for the given session to enable access to resources • Passcode: <private code> + <public code received on phone> • A time ticket session of 2 minutes is kept, once expired the process of authentication needs to be repeated • Data is relayed through Google App Engine

  7. Siebel Integration • Currently using Google App Engine to emulate infrastructure in Siebel Center such as calendaring, e-lock access and user restrictions • E-Locks have no API, but one can be developed in the future • Campus Calendaring system on Exchange Server which is being upgraded • Once transitioned calendaring can be integrated into this system • User restriction can be easily integrated by connecting to the university Active Directory server

More Related