1 / 22

Integrated Service Mappings for Differentiated Service Networks

Integrated Service Mappings for Differentiated Service Networks. HCNL HONG KI HUN. Introduction. Integrated Service onto Differentiated service network PHB 를 사용하여 Intserv 구현 the aggregate level rather than the per-application-flow level. Intserv Mappings for Diffserv Networks. Components.

dagmar
Download Presentation

Integrated Service Mappings for Differentiated Service Networks

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. Integrated Service Mappings for Differentiated Service Networks HCNL HONG KI HUN

  2. Introduction • Integrated Service onto Differentiated service network • PHB를 사용하여 Intserv 구현 • the aggregate level rather than theper-application-flow level

  3. Intserv Mappings for Diffserv Networks

  4. Components • Traffic scheduling • Traffic Classification • MF Classifier • Policing and shaping • Single shaper (boundary) • Separate shaper • Admission Control

  5. Per Cloud VS. Per Path • With per Cloud provisioning • 충분한 리소스 할당이 가능하여 할당된 PHB 리소스를 넘지 않고 어떤 egress point로 갈 수 있다 • Destination 정보가 필요 없다 • With per Path provisioning • 특정 egress point로 리소스 할당이 가능하여 할당된 PHB 리소스를 넘지 않음 • admission control and resource allocation을 위해 목적지의 정보가 필요 (좀더 효율적)

  6. Implementation of CL using the AF PHB • CL traffic을 Delay class로 분류 • Police the traffic for conformance at the ingress • conforming packets : highest priority forwarding • nonconforming packets : lowest priority forwarding • configure each AF instance • setting the actual queue size • setting the dropping parameters for low priority packets • setting the service rate of the AF instance • Bandwidth should be allocated between AF and BE

  7. Implementation of CL using the EF PHB • 주로 사용 되지 않음 • only one EF scheduling class • EF PHB requires a hard limit on the amount of traffic (nonconformant traffic 를 다루지 못함) • Arriving CL traffic is policed against this Tspec • Nonconformant traffic is either discarded or remarked as BE

  8. Implementation of Guaranteed Service • a strict mathematical assurance of both throughput and queuing delay • traffic scheduling, policing, and shaping functions • network element's error terms • Delay • propagation delay • shaping/reshaping delays at the boundary • queuing delay inside the cloud

  9. Implementation of Guaranteed Service • propagation delay • Cloud의 크기로 구할 수 있다 • Shaping delay • Ingress edge에서 traffic을 shaping하고 egress edge에서 reshaping 한다 • shaping inside the cloud 도 가능

  10. Queuing delay bounds • limited number of hops of any flow (denoted h) • low (bounded) ratio of the load of EF traffic (denoted u) • minimum rate of the shaped aggregate (denoted r_min) • maximum token bucket depth (denoted b_max) • minimum service rate of the EF queue (denoted S) • maximum deviation of the amount of service (denoted E)

  11. RSVP Reservation Aggregation

  12. Introduction • REVP ver.1 은 각각의 reserved session을 하나의 common class로 aggregate 하기에 부족 • 다수의 E2E(end to end) reservation을 다른 하나의 aggregate reservation으로 통합

  13. Aggregation Of E2E Reservations

  14. Aggregation Of E2E Reservations • Problem of E2E reservation • 각 reservation이 많은 양의 메시지 교환과 계산 그리고 메모리 할당을 발생

  15. Proposed solution • the aggregation of several E2E reservations into one larger reservation from ingress to egress • IP Protocol Number at ingress : from RSVP (46) to RSVP-E2E-IGNORE • E2E RSVP 메시지가 aggregationregion 내부에서 무시됨 • Aggregate Path and Resv 메시지를사용해 E2E reservations의 정보 update와 자원 할당 • 각 라우터에서 저장되어야 할 state와 교환되는 signaling 메시지를 줄임

  16. Proposed solution

  17. Procedure • Aggregator가 E2E Path Message를 수신 • Deaggregator를 모르므로 IP proto. Number 변경후 보냄 • Interior router는 단순히 forwarding • Deaggregator는 ADSPEC update • Aggre. Path가 있으면 Aggregate Path 메시지를 사용하여 ADSPEC update • Aggre. Path가 없으면요청 : E2E PathErr 메시지를 NEW-AGGREGATE-NEEDED와 보냄 • E2E PathErr NEW-AGGREGATE-NEEDED를 받은 Aggregator가 aggre. Path 메시지를 deaggregator 에게 전송

  18. Procedure (cont.) • Deaggre. Router는 aggre. Path 메시지를 받으면 bandwidth의 유무를 확인하여 aggre. Resv 메시지를 전송 • Aggre. Router가 Deaggre. Router 에게 aggre. confirm 메시지 전송 • E2E reservation 제거 • PathTear, ResvTear, timeout • Flow spec 정보도 같이 제거 • Aggre. Router는 E2E reserved data를 받아서 reservation을 확인후 알맞은 DSCP를 marking하여 전송 • E2E reserved data의 트래픽을 측정하여 reservation을 넘으면 drop, reshaping, remaking DSCP

  19. Traffic Classification Within The Aggregation Region • RSVP ver.1 은 aggregate session을 인식하지 못함 • Traffic의 class가 DSCP에 표시되고 구별되어 진다 • Service mapping을 위해 Diffserv PHB를 사용 • EF or one or more AF PHBs • Diffserv와 aggregated RSVP를 같이 사용 할 경우 • aggregated RSVP : 하나의 PHB 할당 (AF 1) • Diffserv : 다른 PHB들 할당 (AF2, AF3, AF4)

  20. Size of aggregate reservations • Aggregate reservation >= the sum of the bandwidth of the E2E reservations • Burst capacity >= the sum of their burst capacities • E2E에 따라 빈번히 aggregate 예약이 바뀌는 것은 aggregation의 이점을 살리지 못함 • Bandwidth의 총량을 미리 예측하여 Aggregate reservation 할당

  21. Multi-level aggregation • Protocol number swapping 과 level을 사용하여 확장 • Aggregation level을 router alert field표시 • N level은 N+1 level에서 다시 aggregate 된다

  22. Reservation Resizing

More Related