1 / 19

End-to-End QoS Specification Issues in the Wired and Wireless Environment

End-to-End QoS Specification Issues in the Wired and Wireless Environment. 通工所 陳昱豪. OUTLINE. INTRODUCTION QoS SIGNALING PROTOCOLS Existing Protocols The NSIS Approach THE GENERIC SERVICE SPECIFICATION FRAMEWORK Generic Service Specification Schema

fraley
Download Presentation

End-to-End QoS Specification Issues in the Wired and Wireless Environment

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. End-to-End QoS Specification Issues in the Wired and Wireless Environment 通工所 陳昱豪

  2. OUTLINE • INTRODUCTION • QoS SIGNALING PROTOCOLS Existing Protocols The NSIS Approach • THE GENERIC SERVICE SPECIFICATION FRAMEWORK Generic Service Specification Schema Intelligent Mapping Algorithm GSS Schema Language • CONCLUSIONS

  3. INTRODUCTION • QoS is a topic that attains a lot of attention in both wired and wireless worlds • End-to-End QoS provision is not accomplished easily • Need an end-to-end QoS signaling protocols • NSIS Transport Layer Protocol (NTLP) NSIS QoS Signaling Protocol (NSLP)

  4. QoS SIGNALING PROTOCOLS • A common language is needed for communicating end to end the QoS requirements of user traffic • Carry the information specified in the corresponding QoS framework • Separate the signaling protocols from the carried information • Interaction between the signaling and mobility protocols • Loose integration • Tight integration

  5. Existing Protocols • Existing QoS signaling solution seem insufficient: interdomain signaling scalability performance mobility support interworking with policy security mechanism • Resource Reservation protocols (RSVP) • YESSIR, Boomerang, BGRP

  6. The NSIS Approach • The lower layer -- the signaling transport layer (NTLP) • Offer generic signaling functionalities • The upper layer – the signaling application layer (NSLP) • Application-specific • NSLP uses the services offered by the NTLP : QoS provision

  7. THE GENERIC SERVICE SPECIFICATION FRAMEWORK • Service Class “the definition of semantics and parameter of a specific type of QoS” • IntServ-service classes: (guaranteed, controlled load, best effort) • IntServ---DiffServ • UMTS-service classes: (conversational, streaming, interactive, background) • GSS Framework (Offer a generic service class specification schema)

  8. Generic Service Specification Schema(1/4) • GSS schema must define all parameter • Goal-- 1.The appropriate service class matching the profile described in the requested QoS specification must be selected 2.The appropriate traffic parameters must be extracted from the requested QoS specification • Traffic specification • traffic issues: admission control, resource management, traffic policing • parameter: bit rate, packet size, burstiness, greediness, adapticity, duration

  9. Generic Service Specification Schema(2/4) • Bit rate • constant or variable • measured in bits per second • option: very low, low, medium, high, very high, unspecified • Traffic control operation—bucket rate or admission control • Packet size • constant or variable • measured in bytes • option: very small, small, medium, big, very big, unspecified • IP telephony applications usually produce packets of constant size less than 100 bytes • Large one??

  10. Generic Service Specification Schema(3/4) • Burstiness • information regarding the bandwidth requirement • option: very low, low, medium, high, very high, unspecified • The selection of the appropriate service class and traffic-oriented operation • Greediness • flood the connection with as many packets as possible • The flow lowers its bandwidth consumption until it reaches a stable point • option: yes, no, unspecified

  11. Generic Service Specification Schema(4/4) • Adaptivity • a characteristic of the application that produces the flow • The corresponding resource reservation in the network have to be modified to reflect the new condition • Option: yes, no, unspecified • Duration • Traffic-related • information about the nature of a service • Short-living flows—near-real-time transaction (banking) • Option: short living, long living, unspecified

  12. Intelligent Mapping Algorithm • Mapping algorithm is simple • compare one by one • Select the closer service class • Algorithm’s operation depends on parameter defined within the GSS schema • Each parameter of the QoS and traffic specification is associated with a weight • EX: low-delay real-time traffic Maximum transfer delay and maximum delay must have great weight Bit rate (low), packet size (small), burstiness (low) • 11 options for weight from 0---10 • Adds and substracts

  13. GSS Schema Language • Used the Extensible Markup Language (XML) • advantage: offer a standardized text structure, which represents not only the data but also the meta-data • The Data Type definition (DTD)

  14. CONCLUSIONS • Focus on the specification of QoS at the service level • Examine in detail all the important QoS models • On wireless access networks, QoS provisioning is significant

  15. Q&A

  16. Thanks for listening

More Related