This deliverable describes the interfaces of the End-user Application Toolkit (EAT) towards the applications and users of the second AQUILA trial.

"The modular End-user Application Toolkit will be made available in time to be used in the development of the applications for the second trial. As a working document for the develop-ment of the end user applications for the second trial, this deliverable will provide a detailed guide of how to apply the End-user Application Toolkit, including a full explanation of the software architecture used for application services. Target audience for this deliverable are the developers of end-user applications." [Technical Annex]

This deliverable therefore focuses on the detailed description of the functionalities offered by the EAT. This includes also some scenarios on how to use the functionalities for so-called Basic Internet Applications as well as for Complex Internet Services.

One of the outcomes of the first trial is that Basic Internet Applications (here also called legacy applications) can be supported by the AQUILA architecture by providing different mechanisms such as Graphical User Interfaces (GUIs), Application Profiles, and Protocol Gateways (her also called Application Level Proxies). However, this support needs the involvement of (human) customers (end-users), because legacy applications cannot be modified in order to be QoS-aware.

Consequently, this deliverable also includes the explanation of the user interfaces the EAT offers. Moreover, user interfaces are an essential part of modern (complex) Internet services that provide multimedia services towards Internet users. In that way, the application and user interfaces, developed for the first trial, can - with some modifications - be reused for the applications of the second trial. More specifically, the application and user support will be based on the following main "pillars":

• An Application Programming Interface (API) for QoS-aware applications,
• Graphical User Interface for manual reservation in different modes,
• Application Profiles to allow QoS mapping from a technical to a user-friendly level, and
• Application Level Proxies to support some special application signalling protocols.

The one responsible middleware that offers all these interface is the EAT, which acts as the only QoS portal to the AQUILA's RCL controlled network.