WP structure

The project will be organized into the following WPs:

• WP1: Project management (WPL: BL)
• WP2: User requirements and architecture design (WPL: PSNC)
• WP3: Media services implementation (WPL: ALKIT)
• WP4: Control services implementation (WPL: KTH)
• WP5: Network services implementation (WPL: i2CAT)
• WP6: Integration and test-beds (WPL: ALU)
• WP7: Demonstration activities (WPL: TID)
• WP8: Dissemination and business impact (WPL: ANDROME)

The overall objective of WP 1 (M1->M24) is the effective management and coordination from a scientific,technical, financial and administrative point of view.

WP 2 (M1->M6) intends to explore the requirements related to HD video conferencing for offices, industries, homes, schools and healthcare centers connected through LANs, xDSL or FTTx.

WP 3, WP 4 and WP 5 (M7->M18) will work in parallel in order to explore different solutions regarding, respectively, the media plane, the control plane and the network plane of the real-time video conferencing sessions.

The main objective of WP 6 (M13->M21) is to design and implement continuously enhanced test-beds of the HD video conferencing platform, in relationship with WP 3, WP 4 and WP 5 and to release a set-top-box (pre-commercial prototype) as the final project outcome.

WP 7 (M16->M24) will implement the HDVIPER platform and will organize demonstrations and trials, while WP 8 (M1->M24) will manage dissemination of HDVIPER results and outcomes.

In summary, within this project the work has been broken down into phases, according to a typical cascade development project (from WP 2 to WP 7), with a set of "horizontal" work packages, all along the whole duration of the project, in charge of the management (WP 1) and dissemination (WP 8) activities.

As a SOA-oriented project, the interdependence between core WPs (from WP 2 to WP 7) follows a cyclic scheme, as drawn in the above figure. This scheme can be explained as follows.

a. By an accurate analysis of user requirements, WP 2 defines the specific nature of services to be implemented in the project.

b. WP 3, WP 4 and WP 5 use results deriving from WP 2 to deploy services (media services, control services and network services) and at the same time generate the corresponding modules in the Snake application.

c. WP 6 and WP 7 unify results from WP 3, WP 4 and WP 5, thus obtaining a first version of the prototype and of the demonstration platform, which are used for test purposes.

d. WP 6 and WP 7 give to WP 2, WP 3, WP 4 and WP 5 feedback for adjustments, so that an enhanced version of the prototype and of the demonstration platform can be obtained.

e. Steps a-d are repeated until the last version of the HDVIPER prototype and of the demonstration platform are obtained.