Application Support by QoS Middleware - TU Dresden

4 downloads 24 Views 788KB Size Report
2. AQUILA. Outline. ▫ Motivation. ▫ QoS Middleware Architecture. ▫ Support of Application Development. ▫ Support of Legacy Applications. ▫ Overall Scenario.

AQUILA

Application Support by QoS Middleware

Falk Kemmel, Anne Thomas (TU Dresden) Sotiris Maniatis, Charilaos Tsetsekas (NTU Athens)

1

Falk Kemmel, Art-QoS, 24-25/03/2003

AQUILA Outline n Motivation n QoS Middleware Architecture n Support of Application Development n Support of Legacy Applications n Overall Scenario n Conclusions & Outlook

2

Falk Kemmel, Art-QoS, 24-25/03/2003

AQUILA Motivation n DiffServ approach as most promising solution for QoS in the Internet n Two disadvantages:

• No QoS guarantees à AQUILA approach • Gap between QoS in the network and the applications à this talk n Need for QoS middleware to access the AQUILA‘s QoS network n Support of different applications types:

• Legacy (non QoS-aware) apps • Newly developed applications and Internet services

3

Falk Kemmel, Art-QoS, 24-25/03/2003

AQUILA Outline n Motivation n QoS Middleware Architecture n Support of Application Development n Support of Legacy Applications n Overall Scenario n Conclusions & Outlook

4

Falk Kemmel, Art-QoS, 24-25/03/2003

AQUILA Architecture n End-user Application Toolkit (EAT) as QoS middleware between • Applications & end-users and • AQUILA Resource Control Layer (RCL) n Requirements from the applications: • Several interfaces towards applications & users • Support of automatic and manual reservations • Different levels of QoS abstraction n Requirements from the RCL: • CORBA interface to Admission Control Agent • Use of network services • Technical requirements concerning reservations etc. 5

Falk Kemmel, Art-QoS, 24-25/03/2003

AQUILA Legacy Applications

Other Application

H.323 Application

SIP Application

QoS aware Application QoS Portal (GUI)

EA T

EAT API

Base Proxy

H.323 Proxy

User & Reservation Management

SIP Proxy

ACA

Application Profiles & Converter

6

Falk Kemmel, Art-QoS, 24-25/03/2003

AQUILA Outline n Motivation n QoS Middleware Architecture n Support of Application Development n Support of Legacy Applications n Overall Scenario n Conclusions & Outlook

7

Falk Kemmel, Art-QoS, 24-25/03/2003

AQUILA Support of Application Development n EAT API provides interfaces & functions for: • User authentication • Service retrieval • Application Profile retrieval • Reservation request & release – at different levels of QoS abstraction – uni-, bi-directional, groups • Accounting information n CORBA-based API n Use of design patterns: composite, abstract factory

8

Falk Kemmel, Art-QoS, 24-25/03/2003

AQUILA EAT API (Extract)

9

Falk Kemmel, Art-QoS, 24-25/03/2003

AQUILA Outline n Motivation n QoS Middleware Architecture n Support of Application Development n Support of Legacy Applications n Overall Scenario n Conclusions & Outlook

10

Falk Kemmel, Art-QoS, 24-25/03/2003

AQUILA Support of Legacy Applications n Manual support • QoS Portal • Application Profiles & EAT Converter n Automatic support • Protocol Gateways (or Proxies)

11

Falk Kemmel, Art-QoS, 24-25/03/2003

AQUILA QoS Portal – Manual Support n Web -based GUI to access the EAT and to use AQUILA QoS 1) 2) 3) or 3)

Login Choose reservation level Do an advanced reservation (mainly for AQUILA people)

Do a regular reservation a) Choose a predefined application (profile) b) Choose a predefined QoS option for each service component App utilisation phase 4) Release the reservation 5) Logout

12

Falk Kemmel, Art-QoS, 24-25/03/2003

AQUILA

13

Falk Kemmel, Art-QoS, 24-25/03/2003

AQUILA

14

Falk Kemmel, Art-QoS, 24-25/03/2003

AQUILA Application Profiles (1) n Syntax to describe applications‘ QoS characteristics n Supports conversation between different levels:

• Network level à AQUILA reservation request • Application level à Implementation issues (service components) • End-user level à QoS Portal n One Application Profile for each app n Several Service Component Profiles

• Audio, Video, Data, etc. n XML profile repository for EAT

15

Falk Kemmel, Art-QoS, 24-25/03/2003

AQUILA Application Profiles (2)

(e.g. video conference, VoIP...)

(e.g. video, image, voice, audio...)

(end-user level, metaphors)

(network level)

16

Falk Kemmel, Art-QoS, 24-25/03/2003

AQUILA Converter n Automatic conversation between Application Profile levels: 1) Preparation of QoS options • Considering the options defined in the Service Component Profile • Considering the end-user‘s SLAs (subscribed network services) 2) Calculation of reservation parameters • Considering the chosen QoS option

17

Falk Kemmel, Art-QoS, 24-25/03/2003

AQUILA Protocol Gateways – Automatic Support n Interception/Sniffing of signalling messages to

• Detect IP addresses and dynamically negotiated port numbers • Analyse multimedia content concerning CODECs n Interworking with EAT management

• Initiation of reservation requests without user involvement à automatic reservation (SIP Proxy)

• Completion of former established manual reservations à half-automatic reservation (H.323 Proxy)

n Extensible Proxy Framework

• Controlled by a Proxy Manager 18

Falk Kemmel, Art-QoS, 24-25/03/2003

AQUILA SIP Proxy ce sour A e R 7) o AC est t u q e r

ACA

EAT Manager 6) EAT Notification 2) INVITE E VIT N I 1) K 0O 0 2 8)

5) 200 OK

19

3) IN VIT E 4) 20 0O K

Falk Kemmel, Art-QoS, 24-25/03/2003

AQUILA Outline n Motivation n QoS Middleware Architecture n Support of Application Development n Support of Legacy Applications n Overall Scenario n Conclusions & Outlook

20

Falk Kemmel, Art-QoS, 24-25/03/2003

AQUILA Overall Scenario HTTP

Access Network

QoS QoS Portal Portal

Core Network CORBA

Host Host

API API

EAT EAT

CORBA

ACA ACA

Converter Converter CORBA

Application Profiles

SIP, H.323, (RSVP)

Proxy Proxy ER ER

Application traffic (TCP, UDP)

21

Falk Kemmel, Art-QoS, 24-25/03/2003

AQUILA Outline n Motivation n QoS Middleware Architecture n Support of Application Development n Support of Legacy Applications n Overall Scenario n Conclusions & Outlook

22

Falk Kemmel, Art-QoS, 24-25/03/2003

AQUILA Conclusions & Outlook (1) n EAT in general • Distributed architecture • Three main interfaces for applications: 1. API • Application development • Specific for AQUILA • Concepts for reuse: reservation groups, etc. 2. QoS Portal • On top of the API • Existing prototype for QoS reservations for AQUILA • Concept for Complex Internet Services like Mediazine 23

Falk Kemmel, Art-QoS, 24-25/03/2003

AQUILA Conclusions & Outlook (2) 3. Proxies • Existing automatic proxy for SIP, half-automatic for H.323 • Idea: new automatic proxies for H.323, RSVP based on the framework • Open: integration of application/codec profiles n Application Profiles & Converter • Used by the API, Portal • Existing profiles for NetMeeting, RealSystem, OIDS Game • New profiles on the base on templates for CODECs

24

Falk Kemmel, Art-QoS, 24-25/03/2003

AQUILA More Information? www.ist-aquila.org

Thank you!

25

Falk Kemmel, Art-QoS, 24-25/03/2003