1 / 21

Summary Of Previous Discussions and a Proposal For A System Architecture

Summary Of Previous Discussions and a Proposal For A System Architecture. Saleh Al-Harthi. OUTLINE. Project Web site: Temporarily at: http://www-cwc.ucsd.edu/~saleh/adasys/ Summary of Previous Discussions: Presentations Discussion A Proposal For A System Architecture:

walda
Télécharger la présentation

Summary Of Previous Discussions and a Proposal For A System Architecture

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. Summary Of Previous Discussions and a Proposal ForA System Architecture Saleh Al-Harthi

  2. OUTLINE • Project Web site: • Temporarily at: http://www-cwc.ucsd.edu/~saleh/adasys/ • Summary of Previous Discussions: • Presentations • Discussion • A Proposal For A System Architecture: • What is Adaptivity? • System Components • How to Begin?

  3. Summary Of Previous Discussions: Presentations • “Adaptive Applications for Wireless Information Technology” • Debashis Panigrahi • “End-to-End Differentiation of Congestion and Wireless Losses” • Song Cen • “Scheduling Over Wireless Networks” • Kameswari Chebrolu • “Resource Allocations in Wireless Networks” • Arvind Santhanam Applications Physical (Layer) Access Networks Scheduling, Ad Hoc Networks

  4. Summary Of Discussion • Issues: • Applications • Physical (Layer) • Scheduling • Network Type • Test-bed Network Applications Physical (Layer) Access Networks Scheduling, Ad Hoc Networks

  5. Summary Of Discussion • Applications: • Categories: Mainly streaming media (video) and Web browsing. • Develop application “abstractions” and Models • Explore adaptivity in context of existing standards or 4G networks?: Both.

  6. Summary Of Discussion • Physical (Layer) • Models for the Wireless channel • Methods to combat fading • Diversity, coding,…etc.

  7. Summary Of Discussion • Scheduling: What is The Optimal Scheduling? • First, model (possibly mathematically) the traffic categories (or applications) then find the optimal solution. • Want QoS guarantees, High Utilization, and Cost Effective Solution.

  8. Summary Of Discussion • Network Type: Cellular or Ad Hoc? • Adaptivity in “access” to both systems? • Yes, mobile unit could have two (or more) “modes” • Can “Cullular” & “Ad Hoc” be connected? (Next)

  9. Summary Of Discussion • Dual Approach?: Cellular & Ad Hoc • Explore the use of Ad Hoc networks algorithms for basestations?: e.g. Routing • Two separate Systems: Integration of “cellular” and “Ad Hoc”, e.g. “Ad Hoc Relay Stations” (ARS) proposed by H. Wu et. al. [IEEE Journal on Selected Areas in Communications, vol.19, (no.10), IEEE, Oct. 2001. p.2105-15.] • Why ARS (Next)

  10. Summary Of Discussion • Benefits of ARS: Load balancing, Increased Capacity, and Provide Service for Shadow Areas.

  11. Summary Of Discussion • Benefits of ARS: Load balancing, Increased Capacity, and Provide Service for Shadow Areas

  12. Summary Of Discussion • Test-bed Network • In the near future, could use momentum to start with a few “programmable” mobile nodes • Mutual interest between academia and industry could eventually lead to “Adaptive Systems lab” NOT a Replacement For Simulation

  13. A System Architecture • Adaptive System?

  14. A System Architecture • What is Adaptivity?: (Mobile Unit) • Static terminalcharacteristics: Display size, processing capabilities • Dynamic terminal characteristics: Battery reserves, user preferences • Location: Available infrastructure, points of interest to the user • Varying cost of transmission: Access Networks • Applications requirements: e.g. Video “player” vs. “Editor” What about the “System”?

  15. A System Architecture • System Components: “Modularity” is the key: • Dividing a complex problem to sub-problems • Long-term development and survivability • Reconfigurability by software downloads: e.g., the “TRUST” Project Basic System components Wireless Channel

  16. A System Architecture • System Components: The Scheduler Wireless Channel

  17. A System Architecture • System Components: The App. Module Wireless Channel

  18. A System Architecture • System Components: The App. Module- A possible consideration: Wireless Channel

  19. A System Architecture • Other componenets and issues, e.g., Power Control (There may be others?) Wireless Channel Other Possible “explicit” System components

  20. A System Architecture • How to begin? • A slim version first: e.g., • Web-browsing only • Design one instance of the “scheduler” and simulate performance with various applications suite of algorithms • Extend and modify existing research • Hold technical sessions (may be Graduate students)

  21. The End. • Thank you.

More Related