QoS in COIAS and MECCANO, QUTE '98 Workshop, Heidelberg, 14- 15 October, 1998 1 QoS and CoS...

QoS in COIAS and MECCANO, QUTE '98 Workshop, Heidelberg, 14-15 October, 1998

1

QoS and CoS Developments in COIAS and MECCANO

Peter T. Kirstein

University College London


2

Acknowledgement

• Slides mainly developed by Patrick

Coquet for ACTS COIAS Concertation

Meeting

• Valid equally for COIAS and

MECCANO


3

MECCANO Aims

• MECCANO aims to deploy Medium Quality MM conferences over multicast Internet

• Underlying networks are those that users can get access to in Europe

• Tools include video, audio, shared workspace, media servers

• Networks include research nets, TEN-155, ISDN, DBS and local radio nets

• Mostly use IPv4; some move to IPv6


4

COIAS Aims

• Develop IPv6 for a variety of components• Develop Integrated architecture for a variety

of networks– Same mix as MECCANO, but more emphasis on

DBS satellite and less on deployment

• Apply system to real problems and application developed by Eurocontrol

• Types of Application similar to MECCANO, but extra real-time problems


5

Common Interests

• Variety of multimedia applications

• Universal use of IP - with trend to IPv6

• Variety of underlying networks

• Applications able to signal relative priorities and qualities of service

• Application QoS needs translated to IP CoS

• Network-level IP able to use CoS to give priorities, choose technology, signal QoS


6

IP - the User-User Protocol

ATM

CTV ISDN ATM

ISDNCTV

IEEE

IEEEATM

ATMIEEE

WLAN

WLAN

ATM

IEEEATM

IEEE

IEEEATM

@@@@ @@

@@@@

FR

FR


7

Schematic of DBS Addition

ACCESS

ATM

NON-ATM

ACCESS

G

G

G


8

MECCANO Topology


9

MECCANO Configuration

• UK (UCL and HP on SuperJANET)• Germany (Bremen, Erlangen, Freiburg,

Mannheim, Stuttgart on DFB)• Norway (Oslo on Uninett)• France (INRIA on RENATER)• DBS Up-stations (INRIA and ??)• Downstations & Internet at all sites including

Canada (CRC) and Poland (Cracow) • TEN-155 Connections between countries


10

COIAS Configuration Schematic

BTRL

CAMUCL

ESS

R

R

R

R

INRIAACCESS

SECUNET

DASSAULT

TEN-155

11QoS in COIAS and MECCANO, QUTE '98 Workshop, Heidelberg, 14-15 October, 1998

HIgh Performance NETworks

HIPNET=IPv6 (QoS/CoS+SEC+Mobility+Multicast)

All existing or Future Technologies

Transparency Privacy

Multi-usersNomadism

Mobility

Plug and Play

Flexibility


12

• The ISPs Problem– Provide new services: voice, video, push and inter-

active services...

– In an open market,• Best quality/price for the customers• Best benefit for the ISP

– Require a simple solution• Provide a limited number of traffic quality classes

• Boundary devices can differentiate IP flows– Map on ISP traffic classes and hence ATM QoS

ISPs Interests in IP and ATM


13

Corporate Interest in IP and ATM

• The Corporate Network Problems – Support new services: web, push and inter-active

services …and (if cost effective) voice…and (if the interest is real) video.

– By simple migration of the existing network infrastructure

– With the guaranty that the existing applications will continue to run (at least as well as before!)

• ATM could increase bandwidth capacity– Its QoS is not used, because the applications do not

signal QoS, and IP layers do not signal CoS,


14

Proposed Solutions

• Differentiated IP classes of service on top of ATM QoS classes - Native ATM end stations– Differentiation of application flows at the API level– Intranet CoS policy

Boundary Devices – Mapping of intranet QoS with the ISP CoS

• Dynamic resource reservation. If implemented :– usage limited to intranets– limited to guaranteed traffic


15

Intranet implementation

ApplicationApplicationApplication

QoSAgent

RSVP

TCP/IP

Classifier

Shaper/Scheduler

Classifier

Shaper/Scheduler

Classifier

Shaper/Scheduler

Classifier

Shaper/Scheduler

TCP/IP TCP/IP

ApplicationApplicationApplication

RSVPRSVP

QoSAgent

QoSAgent

Host Router Host

Admissioncontrol

Admissioncontrol

Admissioncontrol

Qo

S P

oli

cy

Co

S/Q

oS

Ass

oci

atio

ns

Qo

S P

oli

cy

Co

S/Q

oS

Ass

oci

atio

ns

Qo

S P

oli

cy

Co

S/Q

oS

Ass

oci

atio

ns

ATM ATMATM ATM

SSM SSM SSM


16

Shaping/Scheduler Overview

• Packets are classified according to the flows to which they belong

• The rate of each class is controlled– maximum throughput per class

• The rate of each station is controlled– maximum throughput per network attachment

• Unused bandwidth is re-allocated according to classes priorities


17

SSM configuration

• Available commands : – class creation, modification,suppression,– statistics per class:

• Number of bits transmitted in the limits, overlimit, discarded.

– set the rate of the station on each subnet,– set each class parameters:

• priority, maximum rate on the subnet,• size of the queue.


18

SSM configuration


19-500

0

500

1000

1500

2000

2500

3000

1 26 51 76 101 126 151 176 201 226 251 276 301 326 351 376 401 426 451 476 501 526 551 576 601 626 651 676 701 726 751 776 801 826 851

Differentiated Services

Assured Audio Traffic

Best Effort Audio traffic

Traffic injection


20

Differentiated Services

Assured Audio Rate

Best Effort UDP traffic

0

500

1000

1500

2000

2500

3000

3500

1 59 117 175 233 291 349 407 465 523 581 639 697 755 813 871 929 987 1045 1103 1161 1219 1277 1335 1393 1451 1509 1567 1625 1683 1741


21

CoS/QoS architecture

APPLICATION

QoS demux

Socket Interface

Classifier

Shaper/Scheduler

ATM QoS (MARS)

QoS/CoS Associations•per port

QoS Policy•Classifier policy•Queuing policy•ATM mapping policy

QoS Agent

Admission ControlRSVP

Userinterface


22

Internet Protocol stack

OS

RSVP

QoS Manager

RIPngRTP

RTCPRM TELNET FTP HTTP

Raw IP UDP TCP

IP ICMP IGMP

IPSEC IP Mobile NDP

Flow Management

LAN ATM CTV Satellite

CONF

Audiovisio

TerminalEmulator

WEBBrowser

MMI

WLAN


23

Conclusion

• Queuing & shaping mechanisms are complementary– necessary and have proved their efficiency

• Diffserv model should be implemented in all nodes • Diffserv model is compatible with the Intserv model

– could be used to guaranty some critical dynamic traffic

• QoS/CoS policy has to be managed at a system level– just as the security policy

• Must define how to distribute the QoS policy objects– just as security policy objets

• Differentiated IP service classes should lead to the use of the ATM QoS classes


24

Practical Demonstrators

• COIAS and MECCANO provide good testbeds to experiment

• Will have mix of technologies - ATM, DBS and ordinary Internet

• TEN-155 promises to allow wide-area experimentation with QoS

• Both projects committed to pilot high quality MM services with real QoS

Date post:	30-Dec-2015
Category:	Documents
Upload:	amberly-laurel-booker
View:	217 times
Download:	0 times

QoS in COIAS and MECCANO, QUTE '98 Workshop, Heidelberg, 14- 15 October, 1998 1 QoS and CoS...

Documents