1This presentation has been elaborated in the framework of the EU FP6 funded project E2R II, which is part of a linked group of projects within the Wireless World Initiative WWI. This publication/presentation reflects solely the author's views. The Commission/Community is not liable for any use of the information contained therein.

13th International Conference on Telecommunications, 9-12 May 2006, Madeira Portugal

www.e2r.motlabs.com

Self-Configuring Protocols: A UDT Case Study

Panagis MagdalinosEleni Patouni

Nikos Andriopoulos and Nancy Alonistioti

{panagis,elenip,nand, nancy}@di.uoa.gr

University of Athens

ICT 2006- 13th International Conference on Telecommunications9-12 May 2006 (Funchal, Madeira island, Portugal) 2

www.e2r.motlabs.com

Design Assumptions for Component-based Framework

• Dynamic composition of protocol layers to form a

protocol stack• Dynamic composition of component services in fully-

fledged protocol service• Dynamic runtime modification of the protocol stack.

Dynamic replacement of the functionality of concrete protocol layers

Dynamic replacement of distinct protocol components within these protocols.

• Reliable and transparent reconfiguration execution No loss of existing connections and data,

Minimum performance overhead

ICT 2006- 13th International Conference on Telecommunications9-12 May 2006 (Funchal, Madeira island, Portugal) 3

www.e2r.motlabs.com

Dynamic Configuration of Autonomic Protocol Components

Dynamic Binding of Autonomic Protocol ComponentsAutonomic Manager

CompA CompB

1: evaluate initial protocol stack configuration

3: instantiate protocol component

4: ack

5: instantiate protocol component

6: ack

7: check composition

8: establish bindings

9: check composition

10: establish bindings

2: define protocol layers

ICT 2006- 13th International Conference on Telecommunications9-12 May 2006 (Funchal, Madeira island, Portugal) 4

www.e2r.motlabs.com

Dynamic Configuration of Autonomic Protocol Components

Dynamic Replacement of Autonomic Protocol Components

Autonomic Manager Old Component

New Component

2: pause

4: retrieve state

5: instantiate the new component

6: set state

8: establish bindings

3: wait until old component is stopped

7: check composition

1: negotiation for component configuration

ICT 2006- 13th International Conference on Telecommunications9-12 May 2006 (Funchal, Madeira island, Portugal) 5

www.e2r.motlabs.com

UDT Case Study

• UDT is an application level data transport protocol for the emerging distributed data intensive applications over wide area high-speed networks (e.g., 1 Gb/s or above).

• UDT uses UDP to transfer bulk data and it has its own reliability control and congestion control mechanism. This new protocol is not only for private or QoS-enabled links, but also for shared networks.

• UDT is also a composable framework that can accommodate various congestion control algorithms.

• UDT reliability and congestion control mechanisms exist entirely in user space (not kernel space) and thus protocol variables are accessible at run time.

UDT protocol configuration (congestion control algorithm selection) can only be done at compile time.

ICT 2006- 13th International Conference on Telecommunications9-12 May 2006 (Funchal, Madeira island, Portugal) 6

www.e2r.motlabs.com

UDT/CCC Architecture

Figure 1. UDT/CCC Architecture

In this layered architecture, the UDT layer is completely in user space above the network transport layer of UDP, whereas the UDT layer itself provides transport for applications. Meanwhile, applications provide optional control handlers to UDT as callbacks.

ICT 2006- 13th International Conference on Telecommunications9-12 May 2006 (Funchal, Madeira island, Portugal) 7

www.e2r.motlabs.com

Future Work

Check the possibility of incorporating the framework for dynamic binding and replacement of autonomic components with the UDT protocol.

Modify the congestion control part. Three Possible Stages of Integration:

Identification of possible protocol components: a generic UDT component and the congestion control component

Dynamic Binding of protocol components Dynamic replacement of protocol components during runtime

operation and not at compile time.

Possible Demonstration Scenario: in a network/terminal initiated scenario, the congestion control component is dynamically replaced during runtime operation of the UDT protocol.

ICT 2006- 13th International Conference on Telecommunications9-12 May 2006 (Funchal, Madeira island, Portugal) 8

www.e2r.motlabs.com

Thank you!