1. ISDAP: The Indirect Streaming Data Access Platform

2. Outline Motivation Architecture Centralized P2P Object Diagram

3. Motivation Streaming data are abundant in our surroundings: Length of queue at cafeteria Location of and number of passengers on campus bus Course video/audio for e-learning Live streaming of concerts or games Great demands to access these streaming data at any time, any place

4. A Centralized Architecture Two kinds of entities: Streaming source Streaming sink Matching through centralized servers, e.g. google Bottleneck, controlled access Delivering directly from source to sink Source resource limitation and bottleneck

5. Scenario – Campus Life

6. Centralized Version Server to A Response_HTTP Response_JPG_n Response_JPG_n+1 … Server to B Response_HTTP Response_JPG_n Response_JPG_n+1 … Server n n+1 HTTP Client A n Client B n nn

7. P2P Version Client A n n+1 HTTP Client B n Client C n -1 n A to B (from the a th frame) Response_HTTP Response_JPG_a Response_JPG_a+1 … B to C (from the b th frame, b < a) Response_HTTP Response_JPG_b Response_JPG_b+1 …

8. Object Diagram

9. Centralized, provider

10. Centralized, client

11. P2P, provider P2P indexing network

12. P2P, client P2P indexing network

13. Object Diagram of a Peer

14. Centralized, provider Directory Server publish

15. Centralized, client Directory Server lookup url Media Server HTML, player, media data

16. publish P2P, provider P2P indexing network

17. P2P, client lookup url Supplier HTML, player, media data P2P indexing network

18. Review the Architecture