1 / 5

QOS Support for Wireless (a personal opinion)

QOS Support for Wireless (a personal opinion). Lixia Zhang UCLA Computer Science Dept IAB Wireless Workshop March 1, 2000. Existing effort in wireless QOS area. as much as I know signaling protocols predict where mobiles moving to, set up reservation in time multiple wireless hops

jeanettec
Download Presentation

QOS Support for Wireless (a personal opinion)

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. QOS Support for Wireless(a personal opinion) Lixia Zhang UCLA Computer Science Dept IAB Wireless Workshop March 1, 2000

  2. Existing effort in wireless QOS area as much as I know • signaling protocols • predict where mobiles moving to, set up reservation in time • multiple wireless hops • channel scheduling algorithms • realtime support • fairness assurance

  3. The real challenge • not wireless • just a poor quality link • but mobility: the end of your data flow moving around • Per flow RSVP for wireless scales much worse than per flow RSVP on wireland • highly dynamic changes

  4. Being Pragmatic (or being real) Diffserv approach to wireless QOS • allocate for QOS traffic class • one more (in addition to datagram) would do • control the amount of QOS traffic injected into the system • someway to adjust the allocated amount gradually over time

  5. A two-tier resource control framework Wireless first hop Wireless first hop • bilateral QOS agreement between neighboring domains (adjusted over time) • each domain responsible for its internal resource management & usage • Payload type independent • Packets carry right DS bits • authorizing the QOS uage: not a new issue

More Related