1 / 13
Télécharger la présentation

Ubiquitous Computing: Announcements, Homeworks, Course Project, and Beacon Validation

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. Announcements • HW 3 – Due now • Mid term – Next thursday • HW 4 – Assigned today • Course Project Proposal – Next Tuesday CSCI {4,6}900: Ubiquitous Computing

  2. Beacon1 Beacon4 Beacon3 Beacon5 Beacon2 Files Files Files Files Files Home works 1,2,3 – Central server Server1 Server2 CSCI {4,6}900: Ubiquitous Computing

  3. Beacon1 Beacon4 Beacon3 Beacon5 Beacon2 Files Files Files Files Files Home works 1,2,3 – Peer-to-peer CSCI {4,6}900: Ubiquitous Computing

  4. Home work 4 Simple authorization service In Home work 1, 2, 3 the beacons authenticated with a name:key pair. The system issued an authorization token which was used to receive service. In this home work, we will enforce authorization by validating these tokens. CSCI {4,6}900: Ubiquitous Computing

  5. Home work 4 – Step 1 • Key Server • The key server will provide simple authentication service. • Authenticate(name, key) • Authenticates name:key and returns token. • Token valid for fixed time interval (5 seconds for evaluation) • Validate(token) • If token is valid, return the name that created the token • Else return error message • Revoke(token) • Invalidate a token, even though it might still have some time left. Subsequent requests with this token will fail • Key servers can be centralized or peer-to-peer • Key servers interact with beacons CSCI {4,6}900: Ubiquitous Computing

  6. Beacon1 Beacon4 Beacon3 Beacon5 Beacon2 Files Files Files Files Files Home works 4 – Central key server Server1 Server2 Key Server CSCI {4,6}900: Ubiquitous Computing

  7. Beacon1 Beacon4 Beacon3 Beacon5 Beacon2 Files Files Files Files Files Home works 4 – Peer-to-peer key server Key Server Key Server CSCI {4,6}900: Ubiquitous Computing

  8. Home work 4 – Beacon extensions • Validate(token) • Contacts one or more key servers to validate the token • Extend GET, PUT, SEARCHGET, CLOSE to validate token. • If token is invalid, the user has to OPEN new connection • Robustness, scalability, time dependencies etc.. CSCI {4,6}900: Ubiquitous Computing

  9. Project milestone III • Project proposals due on 27th (next Tuesday) • Proposals should include: • a description of your topic, • a crisp statement of the hypothesis that you will test, • a statement of why you think the topic is important, • a description of the methods you will use to evaluate your ideas, and • references to at least three papers you have obtained with a summary of how they relate to your work. Proposals should not exceed 2 pages in length. CSCI {4,6}900: Ubiquitous Computing

  10. Midterm – Mar 1 • Open book, open notes, individual effort (no electronic communications allowed) CSCI {4,6}900: Ubiquitous Computing

  11. Outline • Time, clocks and the ordering of events in a Distributed System Leslie Lamport CSCI {4,6}900: Ubiquitous Computing

  12. Problem – happens before relationship Happens before relationship is important Needed to ensure tokens are valid for the intended time interval CSCI {4,6}900: Ubiquitous Computing

  13. Discussion CSCI {4,6}900: Ubiquitous Computing

More Related