1 / 15

Signalling Requirements for End-to-End IP QoS

Signalling Requirements for End-to-End IP QoS. Martin Dolly /Al Morton AT&T. Scope of Signalling Requirements for End-to-End IP QoS.

dustin
Download Presentation

Signalling Requirements for End-to-End IP QoS

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. Signalling Requirements for End-to-End IP QoS Martin Dolly /Al Morton AT&T

  2. Scope of Signalling Requirements for End-to-End IP QoS • Define requirements and the signalling information elements that will enable the development of a signalling protocol(s) capable of the request, negotiation and ultimately delivery of known IP QoS classes UNI to UNI, spanning NNIs as required • Requirements also address signaling information related to traffic priority and admission control Workshop on End-to-End Quality of Service. What is it? How do we get it?

  3. Scope Continued • To meet the QoS classes of Y.1541, a network provider needs to implement services such as those specified in Y.1221 • To implement the transfer capabilities defined in Y.1221, a network needs to provide specific user plane functionality at UNI, NNI, INI interfaces • A network may be provisioned, statically or dynamically on a per call basis, to meet the performance requirements of Y.1541 Workshop on End-to-End Quality of Service. What is it? How do we get it?

  4. Scope of QoS Signalling Reqts. Workshop on End-to-End Quality of Service. What is it? How do we get it?

  5. UNI NNI GW GW GW GW Network Functional Entities Within the Network (Assumed) • Subscription Verification • Authentication • Call Admission Control • Performance Management Workshop on End-to-End Quality of Service. What is it? How do we get it?

  6. Service Level Parameters • QoS class from Y.1541 • Numerical Objectives for IP Loss Ratio, IP Transfer Delay, and IP Delay Variation may be indicated by specifying the QoS class from Y.1541 as a signalling parameter • Traffic Parameters from Y.1221 • Peak rate (Rp) • Peak bucket size (Bp) • Sustainable rate (Rs) • Sustainable bucket size (Bs) • Maximum allowed packet size (M) • IP DSCP as specified in RFC 2474 Workshop on End-to-End Quality of Service. What is it? How do we get it?

  7. Attributes of QoS Signalling Request • Network QoS Class (i.e. Y.1541/Tbl. 1) • Network capacity required, at both the application and network (I.e., Y.1221) levels • (future) Reliability/Priority Class with which the service is to be sustained • Optional Attributes: • Application type • Quality Category per Application type Workshop on End-to-End Quality of Service. What is it? How do we get it?

  8. Attributes of Network Response to User QoS Requests • An Identification Code for the request exchange, to be used in this response and all messages that follow (such as User ACK, or Release, and also in Network-Network messages). When used together with other information, such as Src address, each request can be uniquely referenced. • The simple acknowledgement and acceptance of user/TE requests. Workshop on End-to-End Quality of Service. What is it? How do we get it?

  9. Attributes of Network Response to User QoS Requests • The expected performance level (optional). • The ability to achieve a performance level that is better than an aspect of the QoS Class response, (optional). • The ability to reject a request and, at the same time, to offer a modified service level that can be met. The response may modify the request and may include commitments to an alternate QoS Class, a lower capacity, and other indications such as performance level estimates. Workshop on End-to-End Quality of Service. What is it? How do we get it?

  10. Other Signalling Requirements • Flow Control for user QoS requests and re-requests • Performance requirements for Network QoS requests and re-requests • Contention resolution • Forward and backward compatibility • User-Initiated QoS Resource Modifications • Reliability/Priority attributes including Emergency Services Workshop on End-to-End Quality of Service. What is it? How do we get it?

  11. Architecture for IP Signalling Workshop on End-to-End Quality of Service. What is it? How do we get it?

  12. Control Plane and Data Plane Mechanisms: Relationship Workshop on End-to-End Quality of Service. What is it? How do we get it?

  13. UNI NNI UNI REQ Network A Network B REQ REQ ACK ACK ACK TEo TEd OR REQ REQ REQ ACK ACK ACK OR REQ REQ REQ ACK ACK ACK Signalling Flows • Request – Ack/Accepted Workshop on End-to-End Quality of Service. What is it? How do we get it?

  14. UNI NNI UNI REQo1 Network A Network B MODo2 ACCo2 REQo2 REQo2 ACK ACK ACK TEo TEd OR REQo1 REQo1 MODo2 MODo2 ACCo2 ACCo2 REQo2 ACK ACK ACK Signalling Flows • BW or Class Modification Workshop on End-to-End Quality of Service. What is it? How do we get it?

  15. Summary/Next Steps • Look to match initial requirements with on-going protocol spec. efforts • Define requirements and signalling information elements that support a Y.1221 “Traffic Contract”, including Y.1541 QoS Classes, for NNI and UNI signalling protocol(s) • Enhance definition of the functional entities within each Network • Consider Additional Signalling flows for errors, policy rejection, etc. Workshop on End-to-End Quality of Service. What is it? How do we get it?

More Related